Conguring BGP4 Restart stale routes timer
Use the following command to specify the maximum amount of time a helper device will wait for an end-of-RIB message from a peer
before deleting routes from that peer.
device(config-bgp)# graceful-restart stale-routes-time 120
Syntax: [no] graceful-restart stale-routes-time seconds
The seconds variable sets the maximum time before a helper device cleans up stale routes. Possible values are 1 through 3600
seconds. The default value is 360 seconds.
Conguring BGP4 Restart purge timer
Use the following command to specify the maximum amount of time a device will maintain stale routes in its routing table before purging
them.
device(config-bgp)# graceful-restart purge-time 900
Syntax: [no] graceful-restart purge-time seconds
The seconds variable sets the maximum time before a restarting device cleans up stale routes. Possible values are 1 - 3600 seconds.
The default value is 600 seconds.
BGP4 null0 routing
BGP4 considers the null0 route in the routing table (for example, static route) as a valid route, and can use the null0 route to resolve the
next hop. If the next hop for BGP4 resolves into a null0 route, the BGP4 route is also installed as a null0 route in the routing table.
The null0 routing feature allows network administrators to block certain network
prexes using null0 routes and route-maps, directing a
remote device to drop all trac for a network prex by redistributing a null0 route into BGP4.
This example shows a topology for a null0 routing application example.
Conguring BGP4 restart
FastIron Ethernet Switch Layer 3 Routing
396 53-1003627-04
To Next Page
Loading...
Need help?
General
