Lifecycle Management using VNFM

The Ribbon Virtual Network Function Manager (VNFM) is an ETSI standards-aligned virtualized application you can use to orchestrate and manage the lifecycle of distributed SBC deployments in an OpenStack environment. Beyond the initial orchestration of a VNF, you can use VNFM to manage the remainder of the VNF's lifecycle. VNFM regularly monitors the health of VNFs through a heartbeat mechanism and regularly reports VNF status on its VNF Status page. VNFM can also be used to migrate, manually heal, and upgrade VNFs. For general information on VNFM and its VNF lifecycle management capabilities refer to the VNFM User Guide. The following sections provide details on VNFM lifecycle management of SBC VNFs. 

Heartbeat Monitoring

As the SBC VNF completes orchestration and initializes for the first time, it registers with VNFM and they begin to exchange heartbeat messages. This heartbeat mechanism regularly monitors the connection between the SBC nodes and VNFM. If the SBC fails to receive a heartbeat message for greater than 30 seconds it triggers an SNMP trap and alarm. The trap is cleared when the SBC resumes receiving the heartbeat messages. Refer to VNFM Alarms for more information on the alarms.  

SBC VNF Migration

VNFM provides an option to move an SBC node from one cloud location to another in a process referred to as migration. Migrating might be needed when a host system is undergoing maintenance. 

Only a standby SBC node should be migrated. Use the EMS to determine whether the node you want to migrate is active or standby, or log into the CLI and issue the following command to check the output for the parameter assignedRole:  

show status system rgStatus

If the node is active, then switch over the node so it becomes the standby node before initiating the migration.

To migrate an SBC VM:

1. Click on VNF Status in the VNFM left pane. The VNF Status window opens.

2. Click on the cluster containing the VM node you want to migrate. The Deployed VNF Summary window opens showing a Generic VM Details section that contains detailed information on the VM nodes within the VNF. 

   Generic VM Details Window - Migration

   

3. In the Select Action list, click Migrate VM. The Migrate VM window appears.
4. Select a flavor from the Select Flavor drop-down menu.
5. When prompted, confirm that you want to migrate the VM. VNFM begins the migration process. During this process the status shown for the VM changes as the migration progresses. When the process completes, the VM status changes to "Available." 

SBC Healing

VNFM shows the current status for any deployed SBC VNFs in its VNF Status window. The status of the VNF changes to "Degraded" when there is an issue with an SBC node. When this occurs VNFM can rebuild the impacted VM node in a process referred to as healing. The healing process re-instantiates and restarts the SBC VM node in an effort to restore it to service.

To heal an SBC VM when the VNF status appears as degraded:

1. Click on the degraded cluster in the VNF Status window. The Deployed VNF Summary window opens showing a Generic VM Details section that contains detailed information on the VM nodes within the VNF. In the following figure the status of the "ribbon-sbc-2" node appears as "Failed." 

   Generic VM Details Window - Healing

   

2. In the Select Action list adjacent to the failed node, click Heal VM. The Heal VM window appears.
3. Select a flavor for the node from the Select Flavor drop-down menu.
4. When prompted, confirm that you want to heal the VM. VNFM begins the healing process. During the process the VM status changes as it rebuilds. When the process completes successfully the VM node status changes to "Available." 
5. Click on VNF Status in the VNFM left pane. In the VNF Status window, the status for the VNF appears as "Ready."  

SBC Upgrades using VNFM

You can use VNFM to perform software upgrades on the SBC VNFs you orchestrate through VNFM. Refer to: Upgrading SBC SWe Cloud Instances using VNFM.