Bgp clear and show commands, Bgp clear and show commands -122, Bgp clear and show commands clear ip bgp – Enterasys Networks X-Pedition XSR CLI User Manual
Page 318
BGP Clear and Show Commands
6-122 Configuring the Border Gateway Protocol
Example
The following example configures the weight parameter in the context of configuring route map 1
and applying it to updates arriving from two remote neighbors:
XSR(config)#ip as-path access-list 67 permit “^101 .*”
XSR(config)#ip as-path access-list 57 permit “^102 .*”
XSR(config)#route-map 1 permit 1
XSR(config-route-map)#match as-path 67
XSR(config-route-map)#set weight 6000
XSR(config-route-map)#exit
XSR(config)#route-map 1 permit 2
XSR(config-route-map)#match as-path 57
XSR(config-route-map)#set weight 5000
XSR(config-route-map)#exit
XSR(config)#router bgp 100
XSR(config-router)#neighbor 192.168.1.1 remote-as 101
XSR(config-router)#neighbor 192.168.2.1 remote-as 102
XSR(config-router)#
XSR(config-router)#neighbor 192.168.1.1 route-map 1 in
XSR(config-router)#neighbor 192.168.2.1 route-map 1 in
The two instances of route map 1 perform a match on IP as‐path access lists 67 and 57, in that
order with a weight of 6000 for updates matching ACL 67, and 5000 for updates matching ACL 57.
If the same destinations are advertised by all two remote neighbors, the outbound traffic from this
router will be directed to the neighbor who had a match on ACL 67, as those routes will have the
highest value of the weight parameter.
BGP Clear and Show Commands
clear ip bgp
This command resets one or more BGP connections, by either a hard or soft reset. Soft resets are
preferred because they are less disruptive overall to internetworking. BGP connections must be
reset whenever the BGP routing policy is changed by means of one of the following:
•
BGP‐related access lists
•
BGP‐related weights
•
BGP‐related distribution lists
•
Specification of the BGP timer
•
BGP administrative distance
•
BGP‐related route maps
•
BGP neighbor configuration
Two options for soft reset are:
•
Route refresh is supported depending on whether the route refresh capability has been
negotiated during the OPEN session
•
Stored updates (explicit
neighbor soft-reconfiguration
)