[c-nsp] Problems with Catalyst 3550

Bjørn Mork bjorn at mork.no
Sat May 7 04:52:12 EDT 2005


"Alexandra Alvarado" <aaaa at telconet.net> writes:

> Today I have problem with the network, it went down, the trap server
> collected too many messages like this:
>
>  
>
> CISCO-SYSLOG-MIB::clogHistFacility.694919 "SYS" SNMPv2-MIB::snmpTrapOID.0
> CISCO-SYSLOG-MIB::clogMessageGenerated
> CISCO-SYSLOG-MIB::clogHistSeverity.694919 critical SNMPv2-MIB::snmpTrapOID.0
> CISCO-SYSLOG-MIB::clogMessageGenerated
> CISCO-SYSLOG-MIB::clogHistMsgName.694919 "MALLOCFAIL"

A wild guess would be out of memory...

> SNMPv2-MIB::snmpTrapOID.0 CISCO-SYSLOG-MIB::clogMessageGenerated
> CISCO-SYSLOG-MIB::clogHistMsgText.694919 "4D 65 6D 6F 72 79 20 61 6C 6C 6F
> 63 61 74 69 6F SNMPv2-MIB::snmpTrapOID.0

Memory allocatio

> CISCO-SYSLOG-MIB::clogMessageGenerated 6E 20 6F 66 20 37 35 36 20 62 79 74
> 65 73 20 66 

n of 756 bytes f

> SNMPv2-MIB::snmpTrapOID.0 CISCO-SYSLOG-MIB::clogMessageGenerated
> 61 69 6C 65 64 20 66 72 6F 6D 20 30 78 31 36 34

ailed from 0x164

> Can somebody help me to understand this log, what is the meaning of that
> numbers?

Run something like

  perl -e 'for (@ARGV) {print chr hex}' 4D 65 6D 6F 72 79 

etc


Bjørn



More information about the cisco-nsp mailing list