In this section:

Related articles:

The Ribbon Virtual Network Function Manager (VNFM) is an ETSI standards-aligned virtualized application you can use to orchestrate SBC SWe deployments in an OpenStack cloud environment. If you use VNFM to orchestrate a VNF, you can subsequently use it 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 lifecycle management specifically for SBC VNFs deployed using VNFM. 

Heartbeat Monitoring

As the SBC VNF completes orchestration and initializes for the first time, the SBC 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. Migration might be needed when a host system is undergoing maintenance. During the migration procedure you must select a new flavor size for the migrated VM. 

An SBC node should only be migrated when it is in standby mode. Use the EMS to determine whether the node you want to migrate is active or standby, or log into the SBC CLI and issue the following command to check the output for the parameter currentRole:  

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. The Migrate VM window opens.
  4. Select a new flavor for the migrated node from the Flavor drop-down list. The flavor you select can be the same size or a larger size than the current flavor for the VM, but it must be different.
  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

Check the VNF Status window to determine the current, overall status for any deployed SBC VNF. Then click on the VNF to open the Generic VM Details window (shown in the preceding figure) and see the status of the individual VMs within the VNF.

When the SBC application goes out of service on a VM, the status of that VM initially changes to "Maintenance." If the VM status remains as "Maintenance" for longer than 20 minutes, its status transitions to "Failed." The overall status of the VNF changes to "Degraded" if any of the VMs within it have a status of "Maintenance or "Failed." Thus, when the overall status of a VNF changes to "Degraded," it is an indication that there is an issue with one of its VMs. 

If needed, VNFM can attempt to repair the impacted VM node in a process referred to as healing. The healing process offers multiple options you can use to repair 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 with 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. There are five options offered for repairing the VM. The options are shown and explained in the following figure. For additional details on the options refer to Repairing a VNF in VNFM documentation. 

    Warning

    Do not execute the "Recreate_destroy" option on a VM that has DHCP enabled. When the Recreate_destroy option is executed on a VM that has DHCP enabled the VM is provided new IP addresses which causes that VM to be unable to re-join in the cluster. 

    VNFM Healing Options

  3. Click the radio button adjacent to the healing option you want to use. If you select Rebuild,also select an Image you want to use to rebuild the VM. 
  4. Click Heal VM. 
  5. When prompted, confirm that you want to heal the VM. VNFM begins the healing process. During the repair process the VM status changes. When the process completes successfully the VM node status changes to "Available." 
  6. 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.