Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

IDS-4260 SNMP TRAPS SUPPORT....

Hello,

I received the following traps while disconnecting the fiber from the IDS:

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (97610796) 11 days,

7:08:27.96

SNMPv2-MIB::snmpTrapOID.0 = OID:

SNMPv2-SMI::enterprises.9.9.138.2.0.1

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.3 = Gauge32: 4

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.4 = Gauge32: 3

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.5 = INTEGER: 4

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.6 = Gauge32: 97610796

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (97611029) 11 days,

7:08:30.29

SNMPv2-MIB::snmpTrapOID.0 = OID:

SNMPv2-SMI::enterprises.9.9.138.2.0.1

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.3 = Gauge32: 4

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.4 = Gauge32: 1

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.5 = INTEGER: 4

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.6 = Gauge32: 97611029

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (97611229) 11 days,

7:08:32.29

SNMPv2-MIB::snmpTrapOID.0 = OID:

SNMPv2-SMI::enterprises.9.9.138.2.0.1

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.3 = Gauge32: 4

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.4 = Gauge32: 2

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.5 = INTEGER: 4

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.6 = Gauge32: 97611229

I am not being able to decode the message using de CIDS-MIB, does anybody know what else do I need???

Regards,

2 REPLIES
Cisco Employee

Re: IDS-4260 SNMP TRAPS SUPPORT....

Hi Javier,

This should help:

http://jaguar.ir.miami.edu/~marcus/snmptrans.html

replace: "SNMPv2-SMI::enterprises" in any of these objects with ".1.3.6.1.4.1" and you'll be able to see what that trap is. For instance, let's look at:

SNMPv2-SMI::enterprises.9.9.138.1.3.3.1.3=Gauge32:4

I'll go to the OID translator, and in the "Object Identifier or Object Name" field, I put in:

.1.3.6.1.4.1.9.9.138.1.3.3.1.3

and it returns the following:

.1.3.6.1.4.1.9.9.138.1.3.3.1.3

ceAlarmHistEntPhysicalIndex OBJECT-TYPE

-- FROM CISCO-ENTITY-ALARM-MIB

-- TEXTUAL CONVENTION PhysicalIndex

SYNTAX Integer (1..2147483647)

MAX-ACCESS read-only

STATUS Current

DESCRIPTION "This object specifies the physical entity that generated

the alarm."

::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEntityAlarmMIB(138) ciscoEntityAlarmMIBObjects(1) ceAlarmHistory(3) ceAlarmHistTable(3) ceAlarmHistEntry(1) 3 }

Anyway, you can look up each of those in the same way.

These are all part of the CISCO-ENTITY-ALARM-MIB

Regards,

-Joe

New Member

Re: IDS-4260 SNMP TRAPS SUPPORT....

It seems to be that the NMS is not being able to decode the trap properly. Is there any way to enable the usual LinkUP/LinkDown traps for the sensing interfaces of a IDS-4200 v6.0? That's what the trap I posted was about.

Many thanks,

481
Views
0
Helpful
2
Replies