I can't see why shutting down that link would be a problem, Richard. Just DON'T forget to reenable it. :-)
Depending on what debug command you are using, you may also want to add an ACL to the debug command (to minimise input). I also wouldn't expect your lab backbone routers to have as many routes as we chose to include, although I can't guarantee that (I don't write the labs for Cisco). Cheers, Jared Scrivener CCIE2 #16983 (R&S, Security), CISSP Technical Instructor - IPexpert, Inc. Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Mailto: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] Blog: jaredscrivener.com <http://www.jaredscrivener.com> _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Meraz, Richard Sent: Tuesday, 8 July 2008 6:52 PM To: [email protected] Subject: [OSL | CCIE_RS] Debugs, troubleshooting, and the Cisco BB Router I just finished the RIP lab and got killed on my debugs because of the number of updates coming from the BB router. I know it's best to ensure you can telnet to the router on which you are doing the debug so you can turn it off if need be, but how about shutting down the interface to the Cisco BB router during the lab while initially configuring your routing protocols to ensure your changes are taking affect more easily, and then once complete turning up the interface pointing to the BB up. Just a thought. Rich
