Monitoring Cisco Virtualized Packet Core

The following topics provide an overview of Cisco Virtualized Packet Core (VPC) and describe the two configurations of VPC.

Overview of Cisco Virtualized Packet Core (VPC)

Cisco VPC is the industry's first hardware platform and hypervisor-independent solution that combines network functions virtualization (NfV) and software-defined networking (SDN). Cisco Virtualized Packet Core (VPC) provides a single solution for all the packet core services (4G, 3G, 2G, Wi-Fi, and small cell networks). As the network functions are provided as virtualized services, VPC enables a user to scale capacity and introduce new services in a faster and cost-effective manner.

Cisco VPC is based on the same proven StarOS software used in Cisco ASR 5000 Series platforms. VPC is mainly designed to distribute and orchestrate packet core functions across physical and virtual resources to enable users to perform the transition from physical to virtualized packet core services, or use both simultaneously.

The configurations supported by VPC:

  • SI (Single instance)
  • DI (Distributed instance)

VPC–SI

With a single VM per virtual node, the VPC-SI is used as a solution for small to medium instances. Based on the StarOS, each VM deployed on the device supports a single function mapped to it. In general, VPC-SI supports SAE-GW, PGW, SGW, SGSN, and HNBGW services, and all the other mobility services that are supported by Cisco ASR5000.

Identifying VPC–SI VNE

To identify a VPC –SI device, follow the steps provided below:


Step 1blank.gif Click the VNE.

Step 2blank.gif In the VNE Inventory window, verify if Device series is Virtual ASR 5K SI Series Mobile-Gateway.

Step 3blank.gif Verify if the Element type is Virtual ASR 5K SI Mobile-Gateway.

Step 4blank.gif Verify if the Virtual device property is set to True.

 

Figure 31-1 Deployment of VPC -SI VNE

 
VPC-3.jpg

 

VPC–DI

The VPC-DI supports larger instances using multiple VMs. This capability is achieved by creating a distributed infrastructure by combining all the VMs in the virtual node to perform a single or multiple services. However, the VPC-DI is designed in such a way that the VMs have a single point of management. Based on StarOS, the VPC-DI supports distributed services (load balancing) across all VMs using a single service address.

At least one among the VMs is a MIO VM, and one or more VMs act as Fabric VMs and Service VMs. However, with StarOS 17, in the future releases, the fabric VM functionality will be intercoupled within the service VM and will not exist as separate VM.

Identifying VPC–DI VNE

To identify a VPC–DI device, follow the steps provided below:


Step 1blank.gif Click on the VNE.

Step 2blank.gif In the VNE inventory window, verify if Device series is Virtual ASR 5K DI Series Mobile-Gateway.

Step 3blank.gif Verify if the Element type is Virtual ASR 5K DI Mobile-Gateway.

Step 4blank.gif Verify if the Virtual device property is set to True.

Figure 31-2 Deployment of VPC -DI VNE

 

 

364053.eps

UUID Support in Prime Network

In the absence of infrastructure monitoring tools like VCenter, the associations (hyperlinks) between Cisco Virtualized Packet Core (CvPC) VNE and the corresponding VCenter and UCS are not displayed in Prime Network. To identify a VM in the CvPC setup, UUID (a textual representation) is added in the physical inventory at the card level for all the virtual cards.

Viewing UUID Properties in Physical Inventory

To view UUID properties in the physical inventory:


Step 1blank.gif In the Vision client, double-click the device in which the CvPC is configured.

Step 2blank.gif In the VNE inventory window, expand the Physical Inventory node.

Step 3blank.gif Choose Chassis > Server <Number>: Card A9K-VSM-500. The server configuration details are displayed in the content pane.

Step 4blank.gif Choose Server <Number>: Card A9K-VSM-500 > Subslot <Number>: Subcard -A9K-MODULEv. The slot details configured with UUID details is displayed in the content pane.


 

Cisco Virtual Gateway Fault Correlation

The following table describes the fault correlations between CVPC devices and VMs:

Root Cause Alarm
Correlating Alarm

HostShutdown

HostConnectionLostEvent

HostDisconnectedEvent

VM out

VMDisconnectedEvent

PossiblyVMMigratedEvent

Card out/Device Unreachable

HostRemoved

HostConnectionLostEvent

HostDisconnectedEvent

VM out

VMDisconnectedEvent

Card out/Device Unreachable

HostConnectionLostEvent

HostConnectionLostEvent

VM out

VMDisconnectedEvent

PossiblyVMMigratedEvent

Card out/Device Unreachable

HostDisconnected

HostDisconnectedEvent

VM out

VMDisconnectedEvent

VMPoweredOff

VM out

VMPoweredOff

Card out/Device Unreachable

note.gif

Noteblank.gif The faults correlations described in the above table are applicable only for virtual machines hosted in VMWare.