This section provides instructions to enable the SM/MG VM failure and 50% appliance failure automation use case in NSP for the MAG-c appliance NE. It also explains the workflow behavior under different NE scenarios.

Ensure that the following prerequisites have been met before attempting to enable the SM/MG VM failure and 50% appliance failure automation:

• The MAG-c NE model is installed.

• The LSO_Magc_Appliance_Partial_Failure workflow is present in NSP.

This use case includes the following scenarios.

SM/MG VM failure

MAG-c Appliance systems are configured with six SM/MG VMs, with three expected to be active at any given time.

A tmnxEqCardFailure trap is generated whenever an SM/MG VM fails.

An ICR (Graceful) Switchover is triggered if the configured value for the variable magcApplPartialFailureSmVmCount is 3 or less.

An ICR (Forceful) Switchover is triggered if the configured value for the variable magcApplPartialFailureSmVmCount is more than 3.

50% Appliance failure

An ICR (Graceful/Forceful) Switchover is triggered when 1 OAM VM + 1 LB VM + 3 SM/MG-VM + 1 DB VM is down (which is 50% Appliance failure) when user configures a magcApplPartialFailureSmVmCount value of more than 3.

Graceful ICR switchover

If the SM/MG VM down count is less than or equal to 3, the MAG-c NE accepts the graceful switchover command, and is as below:

A:Dut-V# admin redundancy mc-mobile-switchover mobile-gateway 1 peer A:Dut-V#

Forceful ICR switchover

If the SM/MG VM down count is greater than 3, the graceful switchover command gives output as below:

A:Dut-V# admin redundancy mc-mobile-switchover mobile-gateway 1 peer MINOR: MCMOB #3565 Cannot perform Force switchover - ICR Sync state not Hot

At this time, the operator is expected to execute a forceful switchover command as below:

A:Dut-V# admin redundancy mc-mobile-switchover mobile-gateway 1 peer now Switchover will be executed but new Master node may have incomplete UE records, proceed (y/n)?y