Administrator Guide

Layer 3 Routing Commands 1401
Example
console(config)# router bgp 65000
console(config-router)# neighbor 172.20.1.2 remote-as 65001
console(config-router)# neighbor 172.20.2.2 remote-as 65001
console(config-router)# template peer AGGR
console(config-rtr-tmplt)# timers 3 9
console(config-rtr-tmplt)# address-family ipv4
console(config-rtr-tmplt-af)# send-community
console(config-rtr-tmplt-af)# route-map RM4-IN in
console(config-rtr-tmplt-af)# route-map RM4-OUT out
console(config-rtr-tmplt-af)# exit
console(config-rtr-tmplt)# address-family ipv6
console(config-rtr-tmplt-af)# send-community
console(config-rtr-tmplt-af)# route-map RM6-IN in
console(config-rtr-tmplt-af)# route-map RM6-OUT out
console(config-rtr-tmplt-af)# exit
console(config-rtr-tmplt)# exit
console(config-router)# neighbor 172.20.1.2 inherit peer AGGR
console(config-router)# neighbor 172.20.2.2 inherit peer AGGR
console(config-router)# address-family ipv6
console(config-router)# neighbor 172.20.1.2 activate
console(config-router)# neighbor 172.20.2.2 activate
timers bgp
The timers bgp command configures the default keepalive and hold timers
that BGP uses for all neighbors unless specifically overridden by the neighbor
timers command.
Syntax
timers bgp keepalive holdtime
no timers bgp
• keepalive —The time, in seconds, between BGP KEEPALIVE packets sent
to a neighbor. The range is 0 to 65,535 seconds. An small internal jitter is
applied to the keepalive interval timer in order to reduce the CPU load
that may occur when multiple timers expire simultaneously.
•
holdtime —The time, in seconds, that BGP continues to consider a
neighbor to be alive without receiving a BGP KEEPALIVE or UPDATE
packet from the neighbor. If no KEEPALIVE is received from a neighbor
2CSNXXX_SWUM204.book Page 1401 Monday, January 25, 2016 1:25 PM