cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1369
Views
10
Helpful
5
Replies

Quick BGP Question - Path Selection

ksbolton1
Level 1
Level 1

Hello all. I'm doing a BGP lab and I'm a bit curious about the best path selection I see on one of the routers. Basically, I'm used to the best path algorithm being Next-hop reachable? - Weight - Local preference - Locally injected? - AS path length - Origin - MED - Network type - IGP metric to next hop.

In the pic below, the path chosen for prefix 17.1.1.0/24 is via 8.1.2.1. The next path is via 8.1.1.1. It makes sense when you look at the actual network diagram as this router (ISP4 in the diagram) has a direct link to 8.1.2.1, however based on the tie breaker used between the paths (local preference since weight is the same), why wouldn't the 8.1.1.1 next-hop path be chosen? It has a higher local preference and everything else matches.

Annotation 2019-11-30 215555.jpgAnnotation 2019-11-30 215608.jpg

1 Accepted Solution

Accepted Solutions

Francesco Molino
VIP Alumni
VIP Alumni
Hi

The local-pref for the 8.1.1.1 has a value of 100 which is the default value.
If you do a sh ip bgp 17.1.1.1 you'll see the detail of all paths and confirm local-pref is the same.

Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question

View solution in original post

5 Replies 5

Francesco Molino
VIP Alumni
VIP Alumni
Hi

The local-pref for the 8.1.1.1 has a value of 100 which is the default value.
If you do a sh ip bgp 17.1.1.1 you'll see the detail of all paths and confirm local-pref is the same.

Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question

Ah, thank you for clearing that up. I assumed that the default value local preference value was only 100 for iBGP learned routes, but I see they're the same when I drill down as you've suggested. I imagine the tie breaker then becomes eBGP vs iBGP with the former winning that tie.

"I imagine the tie breaker then becomes eBGP vs iBGP with the former winning that tie."

Normally, yes.

By default, Cisco assigns a "better: AD value or eBGP routes over iBGP routes.

Harold Ritter
Spotlight
Spotlight

Can you attach the output of a "show bgp ipv4 uni 17.1.1.0 255.255.255.0".

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Thank you for your quick reply. I had made a couple changes in the time since I made this post but I think I see what's caused the specific path to be selected. As Francesco outlined, the tie breaker wasn't local pref as I thought, it was the neighbor type.

BGP routing table entry for 17.1.1.0/24, version 28
Paths: (2 available, best #1, table default)
Advertised to update-groups:
1
Refresh Epoch 1
65003 65000
8.1.10.1 (metric 3) from 8.8.8.3 (8.8.8.3)
Origin IGP, metric 0, localpref 100, weight 150, valid, internal, best
Originator: 8.8.8.4, Cluster list: 8.8.8.3
rx pathid: 0, tx pathid: 0x0
Refresh Epoch 1
65000
8.1.1.1 from 8.1.1.1 (17.17.17.2)
Origin IGP, metric 0, localpref 100, valid, external
rx pathid: 0, tx pathid: 0
Review Cisco Networking for a $25 gift card