Cisco Cisco Packet Data Interworking Function (PDIF)
Security Gateway Overview
▀ Product Overview
▄ SecGW Administration Guide, StarOS Release 17
16
PCI Port ID
CPU
ASR 9000 TenG
VPC Slot/Port
VM
Application IF
C2:0.0
3
TenGx/y/z/9
1/10
VM4
Uplink
C2:0.1
TenGx/y/z/10
1/11
Downlink
C8:0.0
TenGx/y/z/11
1/1
Management
C8:0.1
—
—
—
Unused
For all VMs except VM1, the NICs are allocated from the corresponding socket. But in VM1, the third NIC
(42:0.0) is picked from a different socket. To achieve maximum throughput, that NIC is used as the
management port and the other two are used for the service.
management port and the other two are used for the service.
To make the interface-to-port mapping symmetric across all the VMs, the third NIC is always used as the
management port.
VPC-VSM
Virtualized Packet Core for VSM (VPC-VSM) consists of the set virtualized mobility functions that implement mobility
specific services and applications within the core of the network. VPC-VSM is essentially StarOS running within a
Virtual Machine (VM).
specific services and applications within the core of the network. VPC-VSM is essentially StarOS running within a
Virtual Machine (VM).
VPC-VSM only interacts with supported hypervisors. It has little or no knowledge of physical devices.
Each VPC-VSM VM takes on the roles of an entire StarOS system. The only interfaces exposed outside the VM are
those for external management and service traffic. Each VM is managed independently.
those for external management and service traffic. Each VM is managed independently.
Each VPC-VSM VM performs the following StarOS functions:
Controller tasks
Out-of-band management for CLI and Logging
Local context (management)
NPU simulation via fastpath and slowpath
Non-local context (subscriber traffic)
Crypto processing (IPSec)
For a complete description of VPC-VSM functionality, refer to the VPC-VSM System Administration Guide.
Important:
Up to four instances of VPC-VSM can run on an ASR 9000 VSM. Each VSM CPU supports only
one VPC-VSM instance. VSM resources are allocated to each SecGW VM; no other application VM is supported on
any VSM CPU. vNICs must be passed to the SecGW VMs from RSP.
any VSM CPU. vNICs must be passed to the SecGW VMs from RSP.