You are the senior networking engineer working for a huge comic book provider. Your network (AS 100) is connected to 2 different service providers and normally all traffic is being sent to your main ISP which is AS 300. However there is a certain network that is being sent to AS 200 which is your backup ISP. All traffic should be sent towards AS300, is this a cheap trick from your backup ISP to make more money? Or is there something else going on? Time for justice!
- All IP addresses are preconfigured as specified in the topology picture.
- Configure EBGP between AS 100 and AS 200.
- Configure EBGP between AS 100 and AS 300, make sure you have a neighbor relationship between router Spiderman and Superman as well as between router Spiderman and Ironman.
- Configure IBGP within AS 300.
- Make sure all neighbor relationships are working, advertise the correct networks in BGP to achieve full connectivity.
- Router Batman AND Superman have the same IP address on the loopback1 interface, advertise this in BGP on both routers.
- Ensure you can ping the 22.214.171.124 address from router Spiderman.
- Take a look at the BGP table with ‘show ip bgp’ on router Spiderman.
- Which path is being used for the 126.96.36.199 network?
- Configure router Ironman and Superman so they send a MED of 50 for the 188.8.131.52 network towards router Spiderman.
- Configure router Batman so it sends a MED of 150 for the 184.108.40.206 network towards router Spiderman.
- Check router Spiderman with ‘show ip bgp’ to see the changes you just made, if not do a ‘clear ip bgp *’
- Even though the MED from AS 300 is better, why is traffic towards 220.127.116.11 still being sent towards AS 200?
- Configure router Spiderman so traffic towards 18.104.22.168 is sent towards AS 300, the only attribute you are allowed to change is MED.
It took me 1000s of hours reading books and doing labs, making mistakes over and over again until I mastered all the protocols for CCNP.
Would you like to be a master of networking too? In a short time without having to read 900 page books or google the answers to your questions and browsing through forums?
I collected all my knowledge and created a single ebook for you that has everything you need to know to become a master of CCNP.
You will learn all the secrets about BGP, attributes and more.
Does this sound interesting to you? Take a look here and let me show you how to Master CCNP ROUTE!
Configuration FilesYou need to register to download the GNS3 topology file. (Registration is free!)
Once you are logged in you will find the configuration files right here.
thanks Rene. I just finished this lab. took me a while but I understand a few things as a result. this is my final Spiderman config.
router bgp 100
neighbor 192.168.12.2 remote-as 200
neighbor 192.168.13.3 remote-as 300
neighbor 192.168.14.4 remote-as 300
and this is my final Batman config.
router bgp 200
network 22.214.171.124 mask 255.255.255.255
neighbor 192.168.12.1 remote-as 100
neighbor 192.168.12.1 route-map policy1 out
access-list 1 permit 126.96.36.199 0.0.0.0
route-map policy1 permit 10
match ip address 1
set metric 150
Rene, are you able to help me explain why it prefers the path through Batman for the 188.8.131.52 network (if “bgp always-compare-med” is not added to Spiderman)?
Still can’t figure out.
Let me help you a bit…first of all these are the BGP attributes:
W Weight (Highest)
L Local_Pref (Highest)
O Originate (local originate)
AS As_Path (shortest)
O Origin Code (IGP < EGP < Incomplete) M MED (lowest) P Paths (External Paths preferred Over Internal) R Router ID (lowest) By default MED is only compared when you have multiple links to the SAME AS. When you configure the "always compare MED" it'll compare MED even when it's from different AS'es. Walk through the attribute list and try to see why it prefers one route over another 🙂
Can you please explain why Router Spiderman prefer Batman as the best path for 184.108.40.206 before adding always-compare-med on spiderman.
After adding always-compare-med on spiderman and resetting BGP on the routers . It took Ironman as the bestpath for 220.127.116.11 and then after restting the BGP for couple of times it is considering superman as the best path for 18.104.22.168. The route for 22.214.171.124 on spiderman flapps after resetting the bgp.
I went through the BGP attributes but I could not makeout by spiderman is taking Batman as the bestpath for 126.96.36.199.
I am new to BGP . Your labs are very useful to unsderstand the topics in detail.
thanks Rene. I think I got it which one =) cheers. on to the next lab…
Very good 🙂 Just walk down the BGP attribute list whenever you are in doubt and you’ll find the answer. Keep in mind that this list can change…an example of this is when you enable BGP Load-balancing. By default BGP only uses a single path but you can enable load balancing which means the list will change/shift 😉
Rene, would it benefit to set the ‘bgp determistic-med’ bgp subcommand? Your labs are great.
Very nice, I was stopped at
Network Next Hop Metric LocPrf Weight Path
* 188.8.131.52/32 192.168.13.3 50 0 300 ?
* 192.168.14.4 50 0 300 ?
*> 192.168.12.2 150 0 200 ?
WOW, better med and no best path :O
These kind of think you won’t think it happen until you face them
Sorry I cannot edit my comment so I asked to delete it, but I think, lower med is better . In my lab is going through Superman
Superman – 50
Batman – 150
Ironman – 50
After that I used “bgp always-compare-med” under router bgp 100 and nothing changed.
And I guess that this “Configure router Spiderman so traffic towards 184.108.40.206 is sent towards AS 300, the only attribute you are allowed to change is MED.” is done with an incoming route map that enforces to change the MED received from Superman to be lower than 50 and all is done.
Very interesting lab.
First let me explain the difference between BGP deterministic-med and BGP always-compare med.
BGP deterministic-med will make sure that MED variable will be compared when a route is advertised by different peers in the same AS.
BGP always-compare will make sure that you compare MED for peers in different AS’es.
If you want to influence the MED the best thing to do is create a route-map and match/set the prefix 🙂
Glad you guys like the labs!
I did it like that, with set metric in the route-map (metric = med)
I wouldn’t have got the #bgp always-compare-med without the hint, in fact it did switch to AS300 when I reset Batman, but not Spiderman, I suppose in 30 mins time that would of changed.
Nice route-map practice.;)
glad you liked it!
Thanks, I remember glancing over the bgp always-compare-med and bgp deterministic-med in my studies. This lab definitely clears it up for me. 😀
You are welcome! Thanks.
You are Fantastic Rene… Nice Lab!!
Great lab! Thanks, Rene!
Please someone tell me what to do with this error! I think I’m using the right IOS!!!!!!!!!!!!
Spiderman: error from server localhost:7200: 208-unable to find object ‘Spiderman’
Batman: error from server localhost:7200: 208-unable to find object ‘Batman’
Superman: error from server localhost:7200: 208-unable to find object ‘Superman’
Ironman: error from server localhost:7200: 208-unable to find object ‘Ironman’
Hello…for Ameen Shaik’s question…why does Spiderman prefers the path toward Batman…it comes down to comparing “R Router ID (lowest)” as Rene said in the BGP metric list …
Batman has 220.127.116.11 and Ironman and Superman have 18.104.22.168 and 22.214.171.124
very good lab.
Great Lab. Thanks Rene.
Don’t understand why we need this step (below), when 126.96.36.199 is advertised from other AS’s.?
Configure router Spiderman so traffic towards 188.8.131.52 is sent towards AS 300, the only attribute you are allowed to change is MED.
On another note, it was lowest router-id that was influencing route via Ironman Vs Superman, right?
Let me know.
Great labs, for one of the Advance BGP title lab, i had stent 8 hours to resolve (90% tasks) 🙂
Comments are closed.