Troubleshooting BGP 413
[SwitchC] acl number 2000
[SwitchC-acl-basic-2000] rule permit source 1.0.0.0 0.255.255.255
[SwitchC-acl-basic-2000] quit
# Configure a routing policy named localpref on Switch C, setting the local
preference of route 1.0.0.0/8 to 200 (the default is 100).
[SwitchC] route-policy localpref permit node 10
[SwitchC-route-policy] if-match acl 2000
[SwitchC-route-policy] apply local-preference 200
[SwitchC-route-policy] quit
# Apply routing policy localpref to routes from peer 193.1.1.1.
[SwitchC] bgp 200
[SwitchC-bgp] peer 193.1.1.1 route-policy localpref import
[SwitchC-bgp] quit
# Display the routing table on Switch D.
[SwitchD] display bgp routing-table
Total Number of Routes: 2
BGP Local router ID is 194.1.1.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal,s-suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 1.0.0.0 193.1.1.1 0 200 0 100i
* i 192.1.1.1 0 100 0 100i
You can find route 1.0.0.0/8 from Switch D to Switch C is the optimal.
Troubleshooting BGP
No BGP Peer
Relationship Established
Symptom
Display BGP peer information using the display bgp peer command. The state of
the connection to a peer cannot become established.
Analysis
To become BGP peers, any two routers need to establish a TCP session using port
179 and exchange open messages successfully.
Solution
1 Use the display current-configuration command to verify the peer’s AS number.
2 Use the display bgp peer command to verify the peer’s IP address.
3 If the loopback interface is used, check whether the peer connect-interface
command is configured.
4 If the peer is a non-direct EBGP peer, check whether the peer ebgp-max-hop
command is configured.
5 Check whether a route to the peer is available in the routing table.
To Next Page
Loading...
