Best way is to simply modify the config. Don't REMOVE anything. In other words .. tackle a ticket as if you are sitting in a production environment. Take the approach you would adopt then.
That's how I personally did it and passed where as second last attempt I did all the tickets yet failed cause I didn't adopt the right approach. Hope this helps. Regards, Samir. On Monday, June 25, 2012, Thomas Raabo - Zitcom A/S <[email protected]> wrote: > I passed TS both my attempts. > > The key thing I see and hear about guys either passing or failing TS is the removal/editing part! > > So like OSPFv3 blocked by acl. > > 1. add a deny log statement to the acl > 2. add all the all the traffic that’s trying to communicate so that the ACL is as specific as possible :) > > I do it this way because i´am too dumb to remember every single port and multicast address ;) > > Med venlig hilsen | Best regards > Thomas Raabo > Senior Network Engineer CCIE #33466 > > > > _____________________________________________ > [email protected] | Direkte: +45 69 10 60 18 | Tlf.: +45 70 23 55 66 > > > -----Oprindelig meddelelse----- > Fra: [email protected] [mailto: [email protected]] På vegne af Marko Milivojevic > Sendt: 24. juni 2012 21:07 > Til: marc abel > Cc: [email protected]; Ray Courtney > Emne: Re: [OSL | CCIE_RS] what to do with existing int erface configs on lab kit > > I would say with an extremely high degree of certainty that removing the configuration instead of fixing the underlying problem is a sure way not to get any points in the lab these days. > > -- > Marko Milivojevic - CCIE #18427 (SP R&S) Senior CCIE Instructor - IPexpert > > On Sun, Jun 24, 2012 at 1:36 PM, marc abel <[email protected]> wrote: >> I agree with Bob on TS. On my pass I changed access-lists rather than >> removing them. In one scenario I asked the proctor a clarifying >> question since I had two ways to solve the task. He steered me away >> from removing any configuration. >> >> On Sun, Jun 24, 2012 at 12:29 PM, Bob McCouch <[email protected]> wrote: >> >>> 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 >>> >> _______________________________________________ > -- Samir Idris _______________________________________________ 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
