Print

Previous Topic

Next Topic

Triggering Failover

The controller module monitors primary modules for change in status. When a primary module ceases operating normally, this triggers a failover:

  • The controller module copies the primary module's configuration to the selected backup module. This includes all parameter values for the primary module's slot. As long as the backup module carries the failed primary module's service, the controller module copies updated configuration values for the primary slot to the backup.
  • In addition to slot-based configuration, the controller module uses the connection table to adjust data flows for the new slot assignments.

On failover, the connection table information is unchanged, however, internally, connections are re-routed from the primary module to the backup module such that the duties and obligations of the primary module can be performed by the backup module.  If a protection router is configured (see page Configuring Module Redundancy), the controller will also re-configure the protection router to route signals of the primary module to the backup module.  If a failed primary module remains out of service after a reset, the controller module will invoke the failover action again.

Note: DejaView must be enabled on the primary slot for the backup module to take on the settings of the primary slot.