Cisco 7604 Configuration Manual page 269

Chapter 14 Configuring Failover
The following commands are replicated to the standby unit:
•
•
•
•
•
•
•
The following commands are not replicated to the standby unit:
•
•
•
•
•
•
•
•
•
You can use the write standby command to resynchronize configurations that have become out of sync.
For Active/Active failover, the write standby command behaves as follows:
•
•
Replicated commands are not saved to the Flash memory when replicated to the peer unit. They are
added to the running configuration. To save replicated commands to Flash memory on both units, use
the write memory or copy running-config startup-config command on the unit that you made the
changes on. The command will be replicated to the peer unit and cause the configuration to be saved to
Flash memory on the peer unit.
Failover Triggers
In Active/Active failover, failover can be triggered at the unit level if one of the following events occurs:
•
•
•
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide using ASDM
OL-20748-01
all configuration commands except for the mode and failover lan unit commands
copy running-config startup-config
delete
mkdir
rename
rmdir
write memory
all forms of the copy command except for copy running-config startup config
all forms of the write command except for write memory
asdm disconnect
debug
failover lan unit
failover suspend-config-sync
mode
show
ssh disconnect
If you enter the write standby command in the system execution space, the system configuration
and the configurations for all of the security contexts on FWSM is written to the peer unit. This
includes configuration information for security contexts that are in the standby state. You must enter
the command in the system execution space on the unit that has failover group 1 in the active state.
If you enter the write standby command in a security context, only the configuration for the security
context is written to the peer unit. You must enter the command in the security context on the unit
where the security context appears in the active state.
The unit has a hardware failure.
The unit has a power failure.
The unit has a software failure.
The no failover active or the failover active command is entered in the system execution space.
Understanding Failover
14-15