Information Technology Reference
In-Depth Information
Example 5-16 R4 Selecting the Path from R5 (Continued)
65102
172.16.6.1 (metric 409600) from 172.16.6.1 (172.16.6.1)
Origin IGP, metric 0, localpref 100, valid, internal
65102
172.17.2.2 from 172.17.2.2 (172.16.7.1)
Origin IGP, metric 0, localpref 100, valid, external
65102
172.17.2.1 from 172.17.2.1 (172.16.5.1)
Origin IGP, metric 0, localpref 100, valid, external, best
172.16.7.1
172.16.5.1
best
Example 5-17 R6 Selecting the Path from R5
R6#show ip bgp 10.2.0.0
BGP routing table entry for 10.2.0.0/16, version 8
Paths: (3 available, best #3, table Default-IP-Routing-Table)
Flag: 0x210
Advertised to peer-groups:
internal
Advertised to non peer-group peers:
172.17.2.2
65102
172.17.2.2 from 172.17.2.2 (172.16.7.1)
Origin IGP, metric 0, localpref 100, valid, external
65102
172.16.4.1 (metric 409600) from 172.16.4.1 (172.16.4.1)
Origin IGP, metric 0, localpref 100, valid, internal
65102
172.17.2.1 from 172.17.2.1 (172.16.5.1)
Origin IGP, metric 0, localpref 100, valid, external, best
172.16.7.1
172.16.5.1
best
Enabling eBGP multipath on both R4 and R6 allows traffic to be load-shared between R5
and R7 instead of only one of them being chosen to receive all traffic inbound to AS 65102.
Examples 5-18 and 5-19 show the changes.
Example 5-18 R4 Load-Balancing Between R5 and R7
R4#show ip bgp 10.2.0.0
BGP routing table entry for 10.2.0.0/16, version 10
Paths: (3 available, best #2, table Default-IP-Routing-Table)
Advertised to peer-groups:
internal
Advertised to non peer-group peers:
172.17.2.1
65102
172.16.6.1 (metric 409600) from 172.16.6.1 (172.16.6.1)
Origin IGP, metric 0, localpref 100, valid, internal
Search WWH ::




Custom Search