07-02-2012 05:32 PM
An unknown bug which has OID as such:
EVENT ID = 00005CX
TIME = Thu 28-Jun-2012 16:32:13 SGT
STATUS = Active
SEVERITY = Informational
MANAGED OBJECT = Device_Hostnamexxxxxx
MANAGED OBJECT TYPE = Switches and Hubs
EVENT DESCRIPTION = InformAlarm::Component=xxxx.xxxx.com:
Unidentified Trap Generic Trap:6 Specific Trap:1
EnterpriseOid:.1.3.6.1.4.1.9.9.41.2;Description=Generic Trap:6 Specific Trap:1
VarBinds:{ .1.3.6.1.4.1.9.9.41.1.2.3.1.2.544239:LINEPROTO,
.1.3.6.1.4.1.9.9.41.1.2.3.1.3.544239:6,
.1.3.6.1.4.1.9.9.41.1.2.3.1.4.544239:UPDOWN,
.1.3.6.1.4.1.9.9.41.1.2.3.1.5.544239:Line protocol on Interface FastEthernet3/48,
changed state to down, .1.3.6.1.4.1.9.9.41.1.2.3.1.6.544239:975111759 };
NOTIFICATION ORIGINATOR = Fault Management Module
07-03-2012 04:33 PM
It simply means the traps can't be processed by LMS and or unmanaged by LMS but its receiving the traps.
11-08-2013 10:05 AM
So how do we get rid of these?
Unidentified Trap Generic Trap:enterpriseSpecific Specific Trap:1 EnterpriseOid:.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt41.2
How can we begin to identify which traps LMS won't recognize?
Thanks!
03-11-2014 08:02 AM
So what do we do about these alerts that often get triggered?
Unidentified Trap Generic Trap:enterpriseSpecific Specific Trap:1 EnterpriseOid:.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.41.2 | |
Description | Generic Trap:6 Specific Trap:1 VarBinds:{ .1.3.6.1.4.1.9.9.41.1.2.3.1.2.23652:LINK, .1.3.6.1.4.1.9.9.41.1.2.3.1.3.23652:4, .1.3.6.1.4.1.9.9.41.1.2.3.1.4.23652:UPDOWN, .1.3.6.1.4.1.9.9.41.1.2.3.1.5.23652:Interface FastEthernet1/0/39, changed state to up, . |
on the interface I have configured "no snmp trap link-status," but I keep getting these info alarms.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide