This section provides instructions to enable the DB VM failure automation use case in NSP for MAG-c appliance NEs. It also explains workflow behavior under different NE scenarios.

Ensure that the following prerequisites have been met before attempting to enable the DB VM failure automation:

• The MAG-c NE model is installed.

• The DB VM failure workflow LSO_Magc_DBVM_Failure is present in NSP.

Two traps are involved in this use case: TmnxMobDbStatusChanged and TmnxMobDbRedRoleActive. The TmnxMobDbStatusChanged trap is the trigger point for DB VM workflow execution.

Redundant DB VM setup

MAG-c systems are configured with two DB VMs. One VM is Active (redundancy role) at any time; the other is Standby.

When the Active DB VM goes down, the TmnxMobDbStatusChanged alarm is raised. The Standby DB VM takes the active role and raises the TmnxMobDbRedRoleActive alarm, so both alarms appear in sequence.

If the TmnxMobDbRedRoleActive alarm is received within two seconds of hold time on NSP, ICR switchover follows the configurable option enableSWToAvoidSubsChurn (default false).

When enableSWToAvoidSubsChurn is true, ICR switchover is executed. When it is false, ICR switchover is not executed.

If the TmnxMobDbRedRoleActive alarm is not received within two seconds, ICR switchover is executed regardless of the value of enableSWToAvoidSubsChurn.

Note: If the Standby DB VM goes down while the Active DB VM is up, ICR switchover is still triggered because of a limitation in determining whether the received trap came from the active or standby database on a MAG-c appliance.

Non-redundant DB VM setup

MAG-c systems are configured with one DB VM, which is always Active (redundancy role).

When the DB VM goes down, only the TmnxMobDbStatusChanged alarm is raised. ICR switchover is executed regardless of the value of enableSWToAvoidSubsChurn.