Netgear XCM8806 Chassis User Manual - Page 70

NETGEAR 8800 User Manual Table 12. Protocol Support for Hitless Failover Protocol Behavior Hitless Border Gateway Protocol If you configure BGP graceful restart, by default the route manager does Yes (BGP) not delete BGP routes until 120 seconds after failover occurs. There is no traffic interruption. However, after BGP comes up after restart, BGP re-establishes sessions with its neighbors and relearns routes from all of them. This causes an increase in control traffic onto the network. If you do not configure graceful restart, the route manager deletes all BGP routes 1 second after the failover occurs, which results in a traffic interruption in addition to the increased control traffic. Connectivity Fault Management (IEEE 802.1ag) An XCM8800 process running on the active MSM/MM should continuously Yes send the MEP state changes to the backup. Replicating the protocol packets from an active MSM/MM to a backup may be a huge overhead if CCMs are to be initiated/received in the CPU and if the CCM interval is in the order of milliseconds. RMEP timeout does not occur on a remote node during the hitless failover. RMEP expiry time on the new master node in case of double failures, when the REMP expiry timer is already in progress, is as follows:  RMEP Expiry Time = elapsed expiry time on the master node + 3.5 * ccmIntervaltime + MSM convergence time. Link Aggregation Control If the backup node becomes the primary node, there is no traffic disruption. Yes Protocol (LACP) Link Layer Discovery Protocol (LLDP) Since LLDP is more of a tool than a protocol, there is no hitless failover No support. LLDP is also a MIB interface to query the information learned. After a failover, it takes 30 seconds or greater before the MIB database is fully populated again. Multicast Source Discovery Protocol (MSDP) If the active MSM/MM fails, the MSDP process loses all state information No and the standby MSM/MM becomes active. However, the failover from the active MSM/MM to the standby MSM/MM causes MSDP to lose all state information and dynamic data, so it is not a hitless failover. Network Login 802.1x Authentication Yes Authenticated clients continue to remain authenticated after failover. However, 1 second after failover, all authenticated clients are forced to re-authenticate themselves. Information about unauthenticated clients is not checkpointed so any such clients that were in the process of being authenticated at the instant of failover must go through the authentication process again from the beginning after failover. Network Login Continued MAC-Based Authentication Yes Authenticated clients continue to remain authenticated after failover so the failover is transparent to them. Information about unauthenticated clients is not checkpointed so any such clients that were in the process of being authenticated at the instant of failover must go through the authentication process again from the beginning after failover. In the case of MAC-Based authentication, the authentication process is very short with only a single packet being sent to the switch so it is expected to be transparent to the client stations. 70 | Chapter 3. Managing the Switch