LMS 4.2.3 Unidentified Trap Generic Trap:6 Specific Trap:1 EnterpriseOid:.1.3.6.1.4.1.9.9.41.2

[ChannaBasava Kalapurmath]

Hi All,

We are seeing unidentified traps continuously on the LMS 4.2.3.

Unidentified Trap Generic Trap:6 Specific Trap:1 EnterpriseOid:.1.3.6.1.4.1.9.9.41.2

What are these traps and how to avoid the same. as these traps are coming from all the devices in the network.

Regards,

Channa

[AFROJ AHMAD · Accepted solution]

Hello Channa,

the 'Unidentified Trap' Alerts that you provided :

NOTIFICATION ORIGINATOR = Fault Management Module

 The EnterpriseOid in this Alert tells me that this is the cisco syslog trap :

.1.3.6.1.4.1.9.9.41.2.0.1
clogMessageGenerated OBJECT-TYPE
        -- FROM CISCO-SYSLOG-MIB
        TRAP
        VARBINDS       { clogHistFacility, clogHistSeverity,
clogHistMsgName, clogHistMsgText, clogHistTimestamp }
        DESCRIPTION    "When a syslog message is generated by the device a
               clogMessageGenerated notification is sent.  The
               sending of these notifications can be enabled/disabled
               via the clogNotificationsEnabled object."

This tells me that you have configured this device with 'snmp-server enable trap syslog' , which means that every syslog message that is generated on the device will also be sent as an snmp trap.
Is there a specific reason why the sending of syslog messages as an snmp trap has been enabled on this device (and others) ?

To stop LMS generating an Alert for every syslog message I would recommend that you disable this device from sending syslog traps to LMS.  If there are multiple devices sending syslog traps to LMS then the sending of these traps to LMS should be disabled on all such devices.

Thanks-

Afroz

***Ratings Encourages Contributors ****

[ChannaBasava Kalapurmath]

Hi Afroj,

Thanks for your reply.

i believe we have enable all the traps available on the device.i will check on the configuration and get back to you.

meanwhile could you please let us know can we have enable lms to have IPSLA alarms.

attaching the screenshot of messages which are not reflected on the LMS.

Regards,

Channa

[AFROJ AHMAD]

Hi Channa,

I don't think LMS support IPSLA  traps.

You can configure the collectors and run the reports for those operation.

http://www.cisco.com/c/en/us/td/docs/net_mgmt/ciscoworks_lan_management_solution/4-0/user/guide/monitoring_troubleshooting/mntug/mnt-collectors.html

Thanks-

Afroz

[ChannaBasava Kalapurmath]

Hi Afroj,

Thanks for your reply. i have found the syslog trap was enabled on the devices.

We will disable and check the behaviour.

Regards,

Channa

[ChannaBasava Kalapurmath]

Hi Afroj,

I am seeing other two OID as found as Unidentified traps on the LMS. the OID are below.

1. OID 1.3.6.1.4.1.9.9.109.2.0.1
   description:  "A cpmCPURisingThreshold notification is sent
   when configured rising CPU utilization threshold
   (cpmCPURisingThresholdValue) is reached and
   CPU utilization remained above the threshold
   for configured interval(cpmCPURisingThresholdPeriod)
   and such a notification is requested.
   The cpmProcExtUtil5SecRev and cpmProcessTimeCreated
   objects can be repeated multiple times
   in a notification indicating the top users of CPU."

3. Oid:.1.3.6.1.4.1.9      

Description : it is for mgmt and indicate that it generated by Cisco devices.

Why these OIDs are shown as unidentified on the LMS. Are these OID are not supported by the LMS ??

what has to be done for to appear well in the LMS?

I'm running below IOS on the device.

s72033-ipservicesk9_wan-mz.122-33.SXI7.bin

Please suggests..

Regards,

Channa

[AFROJ AHMAD]

Hi Channa,

check if this devices is managed properly in LMS, try to delete and re-add the device (if possible) to fix the issue.

 Unidentified Traps

DFM may display an event as an Unidentified Trap. Normally an Unidentified Trap is reported when an event occurs on a device that is being discovered by DFM. To get more information on an Unidentified Trap see the corresponding Events page.
Clearing an Unidentified Trap

You can manually clear Unidentified Traps from the DFM. To do this:

Step 1 Select the Unidentified Trap and click Clear

A message appears prompting you to confirm the clearing

Step 2 Enter your user ID.

This will be used as a reference to identify who cleared the Unidentified Trap.

Step 3 Click OK to confirm

The Unidentified trap is cleared

To retain the trap click Cancel .

Thanks-

Afroz

[ChannaBasava Kalapurmath]

Hi Afroj,

Its happening for more than 1 device. and its not feasible to re-add all affected devices. though i will check by re-adding one device.

Are there any workaround for this.

Regards,

Channa

[ChannaBasava Kalapurmath]

Hi Afroj,

Any suggestions please ??

Regards,

Channa

[AFROJ AHMAD]

Hi Channa,

Did you tried it for one device ? how it went ?

Thanks-

[ChannaBasava Kalapurmath]

Hi Afroj,

We are scheduling the activity, i will let you know the results.

Regards,

Channa

[AFROJ AHMAD]

Hi ,

Before you do that ,

try to rediscover those devices instead of deleting them::

Go to Admin > Collection Settings > Fault > Fault Monitoring Device Administration

select those devices

click "Rediscover"

Thanks-

Afroz

[ChannaBasava Kalapurmath]

Hi Afroj,

I have tried both the options

1.rediscovering the device

2. re-adding the device

but the issue persists.

kindly let me know any other suggestions.

Regards,

Channa