The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This feature simulates a hardware reset line (similar to the support available on the ASR 5500) during the StarOS Control Function (CF) active/standby switchover event. The simulation occurs by requesting the UEM to perform a VM reboot operation for the currently active CF VDU instance with the VNFM.
This section describes how this feature works.
The sequential workflow of this feature is as follows:
The original Standby CF that is in an active role informs the UEM.
The original Standby CF is now in the process of becoming the new Active CF.
The UEM initiates the VM recovery operations with the ESC for the original Active CF.
The ESC reboots the original Active CF.
The UEM sends a switchover accept response to the original Standby CF.
The original Standby CF then becomes the new Active CF.
The UEM ignores all the requests from the original Active CF until the ESC reports VM Alive (that is, the ESC successfully reboots the original Active CF).
The ESC informs the UEM about the successful reboot of original Active CF.
After the ESC successfully reboots the original active CF, the original Active CF now becomes the new Standby CF.
The new Standby CF informs the UEM that it is now the new Standby CF. Then, the UEM starts accepting the request from the new Standby CF.
This release introduces an optional UPP parameter "VNFM_PROXY_ARBITRATION" to control the operation of this feature. This feature gets disabled by default. The feature requires explicit configuration of this parameter. Set this parameter value to 1 to enable this feature.
 Note |
Leaving the parameter unconfigured or setting the parameter value to 0 disables this feature. |
Use the following command to verify the feature configuration on StarOS.
show cloud configuration The following is a sample output of the show command:
[local]qvpc-di# show cloud configuration 1
Card 1:
Config Disk Params:
-------------------------
CARDSLOT=1
CPUID=0
CARDTYPE=0x40010100
DI_INTERFACE=BOND:TYPE:ixgbevf-1,TYPE:ixgbevf-2
DI_INTERFACE_VLANID=1020
VNFM_INTERFACE=MAC:fa:16:3e:1f:19:fc
VNFM_PROXY_ADDRS=30.101.14.11,30.101.14.16
MGMT_INTERFACE=MAC:fa:16:3e:9f:75:46
VNFM_IPV4_ENABLE=true
VNFM_IPV4_DHCP_ENABLE=true
VNFD_NAME=rtice_autovnf-vPC-DI-rtice
VNFM_PROXY_ARBITRATION=1
Local Params:
-------------------------
CARDSLOT=1
CARDTYPE=0x40010100
CPUID=0
Feedback