One thing to be careful with show run is that they could put in fake access-lists, route-maps, etc. These take you some time to figure out they aren't actually causing your problem.
Maybe you see an access-list that denies OSPF. Ah ha! you think, surely this is why my neighbor isn't coming up. A minute later you find that the access-list isn't called anywhere. Now you have spent an extra minute and are still no closer to a solution. That said, sometimes the fastest way to find the issue is show run. For instance I think that a "show run int s0/1" is a great way to start troubleshooting a frame relay problem. On Wed, May 30, 2012 at 7:39 AM, Jay McMickle <[email protected]>wrote: > No limitations. > > I think Marc Abel said it the other day about ACL's, too. Don't remove > them if they are the issue. Simply prepend the appropriate statement in a > higher sequence to make it work. > > Troubleshooting is a difficult area to state don't use "sh run". However, > it should be the last measure. If you are told to reach a router from a > router, think routing protocols, tables, and reachability. A sh ip route x > x, or a sh run | s router or sh ip protocols would be your first check. If > the route exists, go to the next item- remote device route filtering, > interface ACL, traceroute, etc. > > An instructor once told me- Take a quick guess after thinking about a top > 3 issues list. Take a quick look, and then think about what type of command > it would be that would cause the issue. Is it a global command or interface > command. That idea was the best single piece of advice I received. > > In summary- think about the sections of the config that would be the > problem, after thinking about the technology that would enable it. Then, > view only those sections and resolve it and move on. > > The secret of my success was repetition, multiple vendors, and labbing, > labbing, followed by labbing. I logged 150+ hours of actual rack time the 5 > weeks leading up to my lab, with no days off. I was labbing 4+ hours a day, > and it paid off. Don't get relaxed about fulfilling your dream. Go get it- > sleep later! > > Happy labbing! > > Regards, > Jay McMickle- CCIE #35355 (R&S) > Sent from iJay > > On May 30, 2012, at 4:30 AM, George Leslie <[email protected]> > wrote: > > > > > > > > > > > Hi all,Very simple question! On the troubleshooting section of the real > exam, are you barred from using "show runn" or "show start"? Reason I ask > is that lots of verification you see in the lab books and the videos tend > to shy away from using show runn etc. I just wondered if this was to try > and build good habits, or out of necessity due to show runn being not > allowed? Regards, George. > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, > please visit www.ipexpert.com > > > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > > > http://onlinestudylist.com/mailman/listinfo/ccie_rs > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > http://onlinestudylist.com/mailman/listinfo/ccie_rs > -- Marc Abel CCIE #35470 (Routing and Switching) _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
