I ran into this strange problem while doing Mock Lab 6, and I thought it warranted an article because it highlights why the order of operations that IOS performs certain tasks is important.
I finished Mock Lab 6 yesterday. I think i did better than the last mock lab. Going through the solution guide this morning, i got a few things wrong. Most of these were really stupid errors that I’m gonna blame on my brain being mush at around the 6 hour mark. 8 hours is still a killer for me to sit down in one stretch. I was reading on Slashdot the other day how scientists are using brain performance enhancing drugs…my first thought was “Where do i get some?! That would really help studying for a CCIE!” lol.
In my previous article on split horizon we looked at some of the problems with running a distance vector routing protocol like RIP or EIGRP over a frame relay hub and spoke topology. In this article we will be exploring the problems that split horizon might cause in an ethernet based topology. Specifically we will be looking at redistribution issues and some of the problems secondary addresses can cause….
I was reading through Troubleshooting IP Routing Protocols by Cisco Press and came across an example of when to disable Split Horizon on an interface. This particular example involved secondary interfaces, and RIP. After reading about it I tried to go through in my mind all the circumstances in which one might need to disable or troubleshoot split horizon. I labbed up a couple of these scenarios in Dynamips and came up with the following scenarios: Using Distance Vector Routing protocol with Hub and Spoke Frame Relay, Using Distance Vector Routing protocols with Ethernet topologies, Using a Distance Vector Routing protocol with secondary addresses and Redistribution issues with Split Horizon. It is these scenarios that we will be having a look at in the next couple of articles….