0% found this document useful (0 votes)
6 views

3rd bullet item

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views

3rd bullet item

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

3rd bullet item:

On R3:

R3(config-if)#router bgp 200


R3(config-router)#nei 13.1.1.1 remot 100
R3(config-router)#netw 3.3.3.3 mask 255.255.255.255

On R1:
R1(config-if)#router bgp 100
R1(config-router)#nei 13.1.1.3 remote 200
R1(config-router)#nei 12.1.1.2 remote 200

On R2:
R2(config)#router bgp 200
R2(config-router)#nei 12.1.1.1 remote 100

On R1:
R1#sh ip bgp | b Net

Network Next Hop Metric LocPrf Weight Path


*> 3.3.3.3/32 13.1.1.3 0 0 200 i

On R2:
R2#sh ip bgp | b Net
R2#

Why is it that R2 doesn't have the route in its BGP table? Let's do a debug and find out:
R2#deb ip bgp updates
BGP updates debugging is on for address family: IPv4 Unicast

R2#clear ip bgp * soft in

BGP(0): 12.1.1.1 rcv UPDATE about 3.3.3.3/32 -- DENIED due to: AS-PATH
contains our own AS;

OK, we can see the problem. This can be fixed using the "Neighbor 12.1.1.1 allowas-in" or on R1,
we can use the "neighbor 12.1.1.2 as-override". In this case we will use the second option:

On R1:
R1(config)#router bgp 100
R1(config-router)#neighbor 12.1.1.2 as-override

R1#clear ip bgp * so

On R2:

R2#sh ip bgp | b Net

Network Next Hop Metric LocPrf Weight Path


*> 3.3.3.3/32 12.1.1.1 0 100 100 i

You might also like