Why is the network 2.2.2.2/32 preferring the next-hop 192.168.1.10 even though the next-hop 192.168.2.22 as-path is shorter?
show ip bgp
BGP table version is 2, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>2.2.2.2/32 192.168.1.10 150 100 0 (65050) 100 i
* 192.168.2.22 50 100 0 100 i
Exploring the Splunk Web Interface | Major Features and Preferences Welcome
to this in-depth guide to the Splunk Web interface! In this video, we
explore...
2 months ago
2 comments:
The path through 192.168.1.10 is coming from the same confederation and is not accounted for. So they are considered as if having the same as-path length. And since the local pref is higher for 192.168.1.10 it wins.
Thats right
This could cause you headaches while troubleshooting if you are not aware of what is happening.
Post a Comment