Print
|
|
|
Triggering Failback
SEL-MCP3 uses manual failback. Unlike the initial failover, which transfers control automatically, you must explicitly restore service to the primary module.
When an operator issues a failback command (as in Returning to Full Functionality ), the updated service transfers from the backup module to the original primary module. The controller module updates the protection status for the primary and backup modules, and updates the data flows in the connection table, restoring the role of the primary module. The primary module resumes ownership of the configuration and status values for its slot. The controller module restores the original configuration values for the backup module.
Manual service restoration avoids a potential situation where a service repeatedly switches between an intermittently defective primary module and its backup. Also, manual operation lets you schedule the service restoration, which can cause a brief service interruption.
Note: For a backup module to have its original configuration restored after performing a failback, DejaView must be enabled on its slot.
|
© 2018 Imagine Communications Corp. Proprietary and Confidential |
Return to Top |