Okay to leave console debugging on in the lab?

From: Gregory Gombas (ggombas@gmail.com)
Date: Mon Nov 12 2007 - 13:49:54 ART


For those of you who are as paranoid as I am, I just thought of
something that might screw us in the lab.
Let say you leave console debugging on (which is a good idea to have
on because you want to know whats going on in your topology at all
times).

At the end of the day HAL 2000 (or whatever automated program) is
running show commands to make sure you configured the task properly
with the minimum number of commands and sees this:

R2#show ip route eigrp
2.0.0.0/24 is subnetted, 1 subnets
%SEC-6-IPACCESSLOGP: list 101 denied udp 202.168.56.133(43597) ->
124.187.11.168(16461), 1 packet
D EX 2.2.2.0 [170/2297856] via 10.0.2.2, 00:09:33, Serial1/1
3.0.0.0/24 is subnetted, 1 subnets
D 3.3.3.0 [90/2172416] via 10.0.2.2, 00:01:13, Serial1/1
9.0.0.0/24 is subnetted, 1 subnets

Uh-oh! An access-list log entry just interrupted the show ip route
eigrp output!
Now HAL 2000 is either confused by the output, or thinks there is an
extra route in your routing table.

Do you think HAL 2000 has logic built in to deal with such issues, or
will he mark you wrong?
Do you think its best practice to disable console logging at the end
of your lab?

Thanks,
Greg



This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:29 ART