Disabling Configuration Synchronization; Failover Triggers; Failover Actions - Cisco Catalyst 6500 Series Configuration Manual

Understanding Failover

Disabling Configuration Synchronization

Management applications may lose connectivity when upgrading the FWSM with complex
configurations. This can result in incomplete configuration files being applied to the standby FWSM.
You can disable the automatic configuration synchronization in order to avoid incomplete configurations
being applied to the standby FWSM. You need to disable configuration synchronization when upgrading
a software image or changing the configuration on the active FWSM to verify that the configuration files
are complete before the configuration is synchronized with the standby FWSM configuration. After you
verify that the configuration is complete, reenable configuration synchronization
To disable configuration synchronization, enter this command:
fwsm(config)# failover suspend-config-sync
To reenable configuration synchronization, use the no form of the this command.

Failover Triggers

The module can fail if one of the following events occurs:
•
•
•
See the
interface is considered to be failed.

Failover Actions

Table 15-1
Table 15-1 Failover Behavior
Failure Event
Active module failed (power
or hardware)
Formerly active module
recovers
Standby module failed (power
or hardware)
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide
15-12
The module has a hardware failure or a power failure.
The module has a software failure.
Too many monitored interfaces fail.
Because the FWSM can have a large number of interfaces, it cannot monitor every interface. Rather,
you configure the FWSM to monitor a subset of interfaces. The FWSM fails over when a certain
number of monitored interfaces fails; you configure the failure threshold to be an absolute value or
a percentage of the total number of monitored interfaces.
"Failover Monitoring" section on page 15-13
shows the failover action for each failure event.
Policy Active Action
Failover n/a
No failover Become standby
No failover Mark standby as
failed
for more information about when a module or
Standby Action Notes
Become active No hello messages are received on
any monitored interface or the
Mark active as
failover link.
failed
No action None.
n/a When the standby module is
marked as failed, then the active
module will not attempt to fail
over, even if the interface failure
threshold is surpassed.
Chapter 15 Using Failover
OL-6392-01