F3215-HP Load Balancing Module Network Management Configuration Guide-6PW101

307
[RouterC] route-policy localpref permit node 10
[RouterC-route-policy] if-match acl 2000
[RouterC-route-policy] apply local-preference 200
[RouterC-route-policy] quit
# Apply the routing policy localpref to the route from the peer 193.1.1.1 on Router C.
[RouterC] bgp 200
[RouterC-bgp] peer 193.1.1.1 route-policy localpref import
[RouterC-bgp] quit
# Display the BGP routing table on LB.
[LB] display bgp routing-table
Total Number of Routes: 2
BGP Local router ID is 194.1.1.1
Status codes: * - valid, ^ - VPNv4 best, > - 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
The route 1.0.0.0/8 learned from Router C is the optimal.
Troubleshooting BGP
BGP peer relationship not established
1. Symptom
Display BGP peer information by using the display bgp peer command. The state of the connection
to a peer cannot become established.
2. Analysis
To become BGP peers, any two routers must establish a TCP session using port 179 and exchange
Open messages successfully.
3. Solution
a. Use the display current-configuration command to verify that the peer's AS number is correct.
b. Use the display bgp peer command to verify that the peer's IP address is correct.
c. If a loopback interface is used, verify that the loopback interface is specified with the peer
connect-interface command.
d. If the peer is a non-direct EBGP peer, verify that the peer ebgp-max-hop command is
configured.
e. If the peer ttl-security hops command is configured, verify that the command is configured on
the peer, and the hop-count values configured on them are greater than the number of hops
between them.
f. Verify that a valid route to the peer is available.
g. Use the ping command to verify the connectivity to the peer.