Helpful lab: OSPF/EIGRP Redistribution controlled with route-maps, prefix lists & AD
Hi all,
I've been finding the Cisco Networking Academy lab manual for ROUTE very helpful. but I felt it lacked a more in depth redistribution lab. I though the "Comprehensive Example of Controlling Routing Updates" from page 398 of the FLG would be a good lab, so I created it in GNS3 and added a fourth router to make it slightly more complicated.
It's given me a solid three days of practice with various different combos of route-maps and prefix lists, changing AD on various routers etc. I thought some of you might find it useful too. I've attached the diagram, feel free to pm me if you want the GNS3 files.
When you create the initial lab with just R1, R2 and R3 you'll have a routing loop. Then after you fix that you'll still have a sub-optimal routing path for a few routes. Following that, add in R4 which flips things upside-down again.
Make sure you remove any feedback (redistributed routes being re-advertised into their native protocol)
I saw a few TE posts that said that route tags were locally significant, however I proved this to be incorrect. Once you have R4 configured if you do a #sh ip route 192.168.254.0 you will see "Route tag 1000" at the bottom of the output. R4 is only redistributing one connected route from the loopback and I didn't configure any route-maps on it.
TCL script to verify:
foreach address {
10.3.7.1
10.2.7.1
192.168.2.1
172.16.31.2
172.20.20.1
10.3.7.2
10.2.7.2
192.168.1.1
172.16.31.1
192.168.2.2
192.168.1.2
192.168.254.1
192.168.253.1
} {
ping $address
}
I've been finding the Cisco Networking Academy lab manual for ROUTE very helpful. but I felt it lacked a more in depth redistribution lab. I though the "Comprehensive Example of Controlling Routing Updates" from page 398 of the FLG would be a good lab, so I created it in GNS3 and added a fourth router to make it slightly more complicated.
It's given me a solid three days of practice with various different combos of route-maps and prefix lists, changing AD on various routers etc. I thought some of you might find it useful too. I've attached the diagram, feel free to pm me if you want the GNS3 files.
When you create the initial lab with just R1, R2 and R3 you'll have a routing loop. Then after you fix that you'll still have a sub-optimal routing path for a few routes. Following that, add in R4 which flips things upside-down again.
Make sure you remove any feedback (redistributed routes being re-advertised into their native protocol)
I saw a few TE posts that said that route tags were locally significant, however I proved this to be incorrect. Once you have R4 configured if you do a #sh ip route 192.168.254.0 you will see "Route tag 1000" at the bottom of the output. R4 is only redistributing one connected route from the loopback and I didn't configure any route-maps on it.
TCL script to verify:
foreach address {
10.3.7.1
10.2.7.1
192.168.2.1
172.16.31.2
172.20.20.1
10.3.7.2
10.2.7.2
192.168.1.1
172.16.31.1
192.168.2.2
192.168.1.2
192.168.254.1
192.168.253.1
} {
ping $address
}
ROUTE Passed 1 May 2012
SWITCH Passed 25 September 2012
TSHOOT Passed 23 October 2012
Taking CCNA Security in April 2013 then studying for the CISSP
Comments
-
Nate--IRL--
Member Posts: 103 ■■□□□□□□□□
Just getting to grips with redistribution now myself - that lab looks useful - I have the FLG too and I think I'll create something similar myself.
Nate -
fsanyee
Member Posts: 171
I'm just reading the Newtork Warrior, and I remember a very similar screnario like this. -
wave
Member Posts: 342
I'm just reading the Newtork Warrior, and I remember a very similar screnario like this.
Good to know! I plan on reading Network Warrior at some point.
ROUTE Passed 1 May 2012
SWITCH Passed 25 September 2012
TSHOOT Passed 23 October 2012
Taking CCNA Security in April 2013 then studying for the CISSP