When a problem occurs with the SOV CMIC, the CMIC configured as the failover CMIC temporarily assumes the role of the SOV CMIC. To maintain the same functionality, the failed over CMIC must have the same LAN configuration as the active CMIC. For example, if the SOV CMIC has a customer LAN connection, the failover CMIC should also have a customer LAN connection.
When failover occurs, SMWeb displays the following warning message: The SOV CMIC has failed over. Please launch a new SM Client from the failover SOV CMIC. Click the https secure link to continue to the failover SOV CMIC.
The SMWeb Home page reports when a CMIC is in failover and options that are not available on the Home page are grayed out.
When you start SMClient on the failover CMIC, the following warning message displays: The SOV CMIC has failed over. Some of the features will not be available and generated data will not be restored once the failed CMIC becomes active. In addition, the title bar reads: Connected to failover SOV CMIC.
- Any user-created data does not migrate back to the original CMIC when it fails back.
- Configuration changes cannot be made, except to change the Functionality status of the CMIC.
- Changes to alert subscriptions are not allowed.
- Maintenance windows can still be created, updated, and deleted.
- TVI files (Alerts, Reports, Assets, and Heartbeat) continue to be sent to the TVI backend through the SWS.
- From the SMWeb Home page, the Users and Groups and TVI Connection options are not available.
- If you are running a CLI when failover occurs, a message prompts you to restart the command.
When the original SOV CMIC is restored, SMWeb displays the following warning message: The failed SOV CMIC has been restored. Please launch a new SM Client from the original SOV CMIC. Click the https secure link to continue to the restored CMIC.