Cisco Support Community
Community Member

5500 logging severity "32" for default and current after upgrade.

Hey all,

I was wondering if someone could shed some light on this one for me.

After upgrading 5500s to 6.2(2) not to long ago, I noticed that some of our 5500s changed the reported severity level in sh logging, and started reporting all logging as if it were in debug mode. However, the "server severity:" setting reported that "warning(4)" was set. If you looked at the logging buffer, debug messages were being reported (severity level 7 and below messages).

[I've included a cut and paste of the output below from a sho logging]

All 5500s were at the same CatOS code before the upgrade, and all were upgraded to the same code from the same image on the same TFTP server... Any ideas why this happened?

Also, the resolve appears to just set the logging level default back to 4 with the

'set logging level all 4 default'

Atleast, that has worked so far.

Thanks for any thoughts in advance, I've included the output below...

<snip output of sho logging>

Logging buffer size: 500

timestamp option: enabled

Logging history size: 1

Logging console: disabled

Logging telnet: disabled

Logging server: enabled


server facility: LOCAL7

server severity: warnings(4)

Current Logging Session: disabled

Facility Default Severity Current Session Severity

------------- ----------------------- ------------------------

cdp 32 32

cops 32 32

drip 32 32

dtp 32 32

earl 32 32

fddi 32 32

filesys 32 32


Cisco Employee

Re: 5500 logging severity "32" for default and current after upg

Definetly smells like a bug, but I could not find any. What version did you upgrade from. I'll see if it's reproducible

CreatePlease to create content