Configuration Guide User guide

102 FastIron Configuration Guide
53-1002494-02
Hitless management on the FSX 800 and FSX 1600
• Layer 3 IP forwarding information – This includes the routing table, IP cache table, and ARP
table, as well as static and connected routes.
• Layer 3 routing protocols are not copied to the standby management module, but remain in init
state on the standby module until a switchover occurs. Peer adjacency will be restored after a
switchover. If BGP4 or OSPF graceful restart are enabled during a switchover, the standby
management module (new active module) will initiate a graceful restart and a new set of
routes will be relearned. The new set of routes will be the same as the old routes, except in the
case of a network change.
As baseline synchronization is performed, the console of the active management module displays
the progress of the synchronization.
ACTIVE: Detected Stdby heart-beat
ACTIVE: Standby is ready for baseline synchronization.
ACTIVE: Baseline SYNC is completed. Protocol Sync is in progress.
ACTIVE: State synchronization is complete.
The first message indicates that the active management module has detected the standby
management module. The second message indicates that the standby module has been
hot-inserted and is ready for baseline synchronization. The third message is seen when baseline
synchronization is completed, and the fourth message is seen when protocol synchronization is
completed.
The console of the standby management module also displays the progress of the synchronization.
STBY: Baseline SYNC is completed. Protocol Sync is in progress.
STBY: State synchronization is complete.
The first message indicates that baseline synchronization is completed, and the second message
indicates that protocol sychronization is completed.
When control protocols are synchronized and protocol synchronization timers expire, the standby
management module will be in hot-standby mode, meaning the standby module is ready to take
over as the active management module. In the event of a switchover, the standby module will pick
up where the active module left off, without interrupting data traffic.
After baseline synchronization, any new events that occur on the active CPU will be dynamically
synchronized on the standby CPU. Examples of such events include:
• CLI/HTTP/SNMP configurations
• CPU receive packets
• Link events
• Interrupts
• Layer 2 and Layer 3 forwarding table updates
• Dynamic user authentication updates such as 802.1X or multi-device port authentication
Dynamic events are synchronized in such a way that if the active CPU fails before fully executing an
event, the standby CPU (newly active CPU) will execute the event after the failover. Also, if the active
CPU aborts the event, the standby CPU will abort the event as well.