Oh watch out with assuming anything in the CCIE lab :-)
There can be so many things that you can fall into a habit when practicing, but this is very dangerous.
As long as it's not asked for, don't configure it! That's the basic rule to follow, just do what the question says to do.
And like I said, be as specific as possible as you could run into problems further down when there are other requirements that are broken by your previous 'best practice' configuration.
Keep this is mind while studying, it's something I definitely had to change, since I also had a lot of 'best practices' that I automatically configured when some thing was asked, but this can have strange outcomes :-)
Happy Studying!
-- Regards, Rick Mur CCIE2 #21946 (R&S / Service Provider) Sr. Support Engineer IPexpert, Inc. URL: http://www.IPexpert.com On 3 jan 2010, at 16:03, Nuno Reis wrote: > Well, I was not aware of that. I assumed that there are "best practices" to follow, besides what was asked on tasks. Great to hear that. > > Thanks again, > NR > > > -----Original Message----- > From: Rick Mur [mailto:rmur_at_ipexpert.com] > Sent: Sunday, January 03, 2010 2:58 PM > To: Nuno Reis > Cc: ccielab_at_groupstudy.com > Subject: Re: Injecting loopback > > That's not really an issue right? As long as you have connectivity and the task doesn't ask you to have traffic take any specific or optimal path, you should do anything about it. Connectivity is the requirement and by doing other things, you might get yourself in trouble later on. So keep it simple :-) > > > -- > Regards, > > Rick Mur > CCIE2 #21946 (R&S / Service Provider) > Sr. Support Engineer - IPexpert, Inc. > URL: http://www.IPexpert.com > > On 3 jan 2010, at 15:46, Nuno Reis wrote: > >> Got it. It is not a task requirement, but I was getting sup-optimal paths when "tracing" loopback address. >> >> Thanks Rick. >> >> -----Original Message----- >> From: Rick Mur [mailto:rmur_at_ipexpert.com] >> Sent: Sunday, January 03, 2010 2:39 PM >> To: Nuno Reis >> Cc: ccielab_at_groupstudy.com >> Subject: Re: Injecting loopback >> >> Definitely not, it's the right approach. >> It's the only way to get the loopback addresses to be an internal address, if that is a task requirement. >> >> If it's not and it's not specifically asked in a question to inject the loopback, but you do have a full reach ability requirement, I would use redistribute connected with a route-map matching all interfaces that are not in a routing protocol yet. >> >> >> -- >> Regards, >> >> Rick Mur >> CCIE2 #21946 (R&S / Service Provider) >> Sr. Support Engineer - IPexpert, Inc. >> URL: http://www.IPexpert.com >> >> On 3 jan 2010, at 15:26, Nuno Reis wrote: >> >>> Hi, >>> >>> To fix a routing issue on my lab, on one router, I injected the loopback >>> address on two routing protocols at the same time to be seen as internal on >>> two different routing domains. Is it a wrong approach? >>> >>> Thanks, >>> NR >>> >>> >>> Blogs and organic groups at http://www.ccie.net >>> >>> _______________________________________________________________________ >>> Subscription information may be found at: >>> http://www.groupstudy.com/list/CCIELab.html Blogs and organic groups at http://www.ccie.netReceived on Sun Jan 03 2010 - 18:03:29 ART
This archive was generated by hypermail 2.2.0 : Thu Feb 04 2010 - 20:28:41 ART