Brocade Communications Systems ICX 7250 series, Руководство по настройке

Страница: 279 / 483

marker that indicates it has received all of the BGP4 route updates, it recomputes the new routes and replaces the stale routes in the
route map with the newly computed routes. If the device does not come back up within the time configured for the purge timer, the stale
routes are removed.
NOTE
BGP4 restart is supported in ICX switches in a stack.
The implementation of BGP4 Restart supports the following Internet Draft:
• Draft-ietf-idr-restart-10.txt: restart mechanism for BGP4
BGP4 Peer notification during a management module switchover
The BGP4 Peer notification process restores BGP4 adjacency quickly and allows packet forwarding between the newly active
management module and the BGP4 peers. The handling of TCP packets with an MD5 digest prevents the silent dropping of TCP
packets without triggering a RESET packet.
The BGP4 peer notification process operates effectively when implemented for the following processes that involve the intentional
switching of the active status from one management module to another:
• System Reload - When a device undergoes the reload process, both management modules and all interface modules are
rebooted. All BGP4 sessions are terminated BEFORE the system triggers the hardware reset.
• Switchover Requested by User - Switching over to a standby management module can be triggered by the switchover , reset ,
reload , and hitless-reload commands. When these commands are executed, the active management module resets the
BGP4/TCP sessions with BGP4 neighbors before transferring control to the standby management module.
NOTE
Restart-enabled BGP4 sessions are not reset. The BGP4 restart protocol allows a BGP4 session to reconnect gracefully
without going through the normal process.
This example describes the procedure used between the management modules in a device and a BGP4 neighbor device.
BGP4 restart
Brocade FastIron Layer 3 Routing Configuration Guide
53-1003903-04 279