At Cisco Live I did a full-day mock lab with Bruno van de Verve, and he reiterated multiple times the importance of not just removing a feature in TS if there was any way to repair it.
ACL blocking traffic? Add a permit statement, don't remove the ACL. NTP authentication busted? Fix it, don't disable it. Unicast RPF blocking something? Exempt it, don't turn off RPF. My first lab is coming up next month so I can't provide any feedback from the real thing yet, but Bruno stressed this point heavily, and it was also explicitly stated in the "Guidelines and Restrictions" help in the lab UI. Sent from my iPad On Jun 24, 2012, at 9:10 AM, Jay McMickle <[email protected]> wrote: > IMO- for TS, remove only what is required to solve the issue. If I removed > something, and it didn't resolve it, I put it back (if I remembered). It's > pretty clear, cut, and dry, though. My guess is that you have not made a lab > attempt with this type of question. Nothing wrong with the question, as it is > valid for a first timer. I used my first attempt to preview what I needed to > know. > > Regards, > Jay McMickle- CCIE #35355 (R&S) > Sent from iJay > > On Jun 24, 2012, at 7:14 AM, "Arista Wirawan" <[email protected]> wrote: > >> >> >> Are you talking about config or ts part? >> >> On TS, I removed the "suspected" config that may causing issue. >> Some people in forum said we should not totally remove it but modify it to >> allow it works. >> On my past experience, i really do not have time to think about it, so i >> just remove it. Unless cisco specify it that you cannot do that. Otherwise >> it should be save to remove it. >> >> >> >> Aris CCIE #35534 >> Sent from my HTC >> >> ----- Reply message ----- >> From: "Ray Courtney" <[email protected]> >> To: <[email protected]> >> Subject: [OSL | CCIE_RS] what to do with existing interface configs on lab >> kit >> Date: Mon, Jun 18, 2012 3:58 PM >> >> >> Hi, >> >> On your lab should you be shy about removing any existing, unused interface >> configurations on your kit? >> >> I dimly recall parts of questions such as: make sure that no other routes >> are present in the routing table.... As I tended to leave anything in place >> that hadn't put there, might any routes from existing connected interfaces >> have counted as "other routes"? >> >> Would being tentative have been the wrong approach? >> >> Cheers >> >> Ray >> _______________________________________________ >> 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 > _______________________________________________ > 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
