R3166-R3206-HP High-End Firewalls Network Management Configuration Guide-6PW101

373
[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 Firewall.
[Firewall] 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
The route 1.0.0.0/8 learned from Router 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; in other words, BGP peer relationship cannot be established.
Analysis
To become BGP peers, any two routers must 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.
6. Use the ping command to check connectivity.