[c-nsp] Catalyst 4500 syslog

[Josh Duffek]

If TAC can't figure it out pretty quick then it probably is a bug.  But
for grins I'm curious what "sh run | i log" looks like.

Thanks,

josh duffek    network engineer
consultantjd16 at ridemetro.org

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Alban Dani
> Sent: Thursday, March 10, 2005 4:02 PM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Catalyst 4500 syslog
> 
> Hi,
> 
> I have a catalyst 4500 runnin native os ( Version 12.2(18)EW) with a
> sup2+.
> 
> I can not get the box to log anything anywhere.
> I've tried all sorts of log level settings, no dice.
> 
> the show log command output is;
> cat4500.cc#sh log
> cat4500.cc#sh logging
> Syslog logging: enabled (0 messages dropped, 0 messages rate-limited,
> 2 flushes, 0 overruns)
>     Console logging: level notifications, 1942 messages logged
>     Monitor logging: level debugging, 10 messages logged
>     Buffer logging: level debugging, 13 messages logged
>     Exception Logging: size (8192 bytes)
>     Count and timestamp logging messages: disabled
>     Trap logging: level notifications, 1863 message lines logged
>         Logging to 154.244.14.14, 1844 message lines logged
>         Logging to 154.244.14.16, 24 message lines logged
> 
> Log Buffer (6000 bytes):
> 
> Cisco TAC has not found anything yet.
> 
> Is this a bug?
> 
> Thanks
> 
> Alban
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/