>the rule of thumb is do what they say, but if something is not expressly >forbidden, it is fair game.
True.. >the idea that some successful Lab takers all tend to agree on, is that >going >into the Lab you want to have a lot of tools at your disposal. So you can >filter redistribution using route tagging, or distribute lists or route >maps, for example. the Lab is notorious for presenting you with some >underhanded or devious requirement, one which is inside out from the way >you >might normally do things. after two times through, I am also under the >impression that there comes a point where the CCIE Lab designers realize >that something is being analyzed to death in the study materials and >newsgroups, so they take it out, and put in something else. I have study >materials that emphasized things like gateway discovery protocol, and other >obscure things. I presume a lot of this kind of stuff shows up in the >study >materials because of loose lips. Well, they certainly aren't treating the Written Qualification test the same way, otherwise they would really like to change "all" Que's since most of what cisco tests you on already appears on more popular practice tests. >to get back to your question, your Lab book will present you with a general >instruction that will say something like "do not do A, B, or C, unless >otherwise instructed" Then a particular requirement might say "you may do C >to accomplish this" or "do not do X to accomplish this" > >In the case of the particular practice lab, the instruction was "do not use >the default-network command" which got me to wondering what are some other >ways to get a default network into IGRP. Can't use quad zero. can't use a >default network. policy routing, and in particular local-policy was the >only >other thing I could come up with. and it is a real hack. or rather, it can >take some real planning. True again. If its not asking for too much, can you let me know a plan that I can follow to crack the lab (already passed the written) I know its difficult to create a plan without actually knowing what I know, and you might say that "one size doesnt fit all" thats true as well, but there would be a list of Do's & donts and a sequence where one should begin and where to end (if there is one :) Also, a list of absolute must technologies that one must know back to front (specially ATM & Voice, how much should we concentrate on, isnt Cisco ATM solutions an overkill ?) Thanx Nick >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of >Nick S. >Sent: Wednesday, December 12, 2001 8:11 PM >To: [EMAIL PROTECTED] >Subject: RE: The old "how to get routes into IGRP" qu [7:29021] > > >Chuck > >Just curious, from what I have read/heard, we are not supposed to use >Static/Default routes (unless explicitly mentioned/specified). I agree that >in some cases of VLSM/FLSM redistributions, it may be required and may be >asked for as well. So using a glorified "default/static" route in the form >of policy route wouldnt be a violation, would it ? > >Thanks >Nick _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=29174&t=29021 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
