Hi Chris, The approach you suggest is reasonable for the real TS lab because of the 30+ device topology. In the Ipx case due to practical realities of the physical topology and number of devices, in TS there is potentially more interdependencies between tasks so don't get too discouraged about it - that said in the real lab there's a chance that some tickets are interdependent it's just less likely. Good luck with your studies.
Cheers, Adam Booth > On 30 Jan 2014, at 2:42 pm, Christopher Lemish <[email protected]> > wrote: > > Can anyone advise on the best way to approach the T-shooting section? > > I've been doing the recommended method by reading each task. I've assigned > which tasks are categorized by Layer2 or Layer3, etc. and then I begin > resolving the tickets starting with all L2 tasks first. > > Well, I've gotten to Lab 9 T-shoot and I approached it Task2 first (L2), Task > 3 (L3) and Task4 could not be completed until you completed Task 1. Task 1 > looks like a L3 problem, but it turns out that there is some L2 switching > vlan issues on the ports. > > Task 4 you are given ridiculous requirements about "no virtual links b/t > Cat1-Cat2, 2 Virtual links allowed in total and all devices need to reach > 12.12.12.12" (This could be redistribution, or a million other things) > > My question is, what is the best approach to resolve the most amount of > tickets in 7-8 minutes per ticket? > > Thank you, > Chris > > > _______________________________________________ > Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: > > iPexpert on YouTube: www.youtube.com/ipexpertinc _______________________________________________ Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: iPexpert on YouTube: www.youtube.com/ipexpertinc
