Skip navigation
3062 Views 2 Replies Latest reply: Jul 20, 2012 5:46 AM by Andreas Falk RSS
Andreas Falk Rank: White Belt 12 posts since
Jul 9, 2012
Currently Being Moderated

Jul 9, 2012 10:48 AM

Collect snmptrap from cisco ncs.

Hi,

 

I'm struggling with snmptraps again.

I tried to sen snmptraps northbound to zenoss from our ncs.
And only when an accesspoint is disconnected.

 

The event that I get from the server is:

snmp trap ciscoMgmt.712.0.1
Device:     ncs.domain.loc
Component:     
Event Class:     /Unknown
Status:     0
Start Time:     2012/07/09 16:21:01.000
Stop Time:     2012/07/09 16:21:01.000
Count:     1
Message:     snmp trap ciscoMgmt.712.0.1
Systems:     
Groups:     
Location:     
Device Class:     /Server/Linux
Production State:     Production
Device Priority:     Normal
Hide details
agent     zentrap
clearid     
component     
count     1
dedupid     ncs.domain.loc||||3|snmp trap ciscoMgmt.712.0.1
device     ncs.domain.loc
DeviceClass     /Server/Linux
DeviceGroups     |
DevicePriority     3
eventClass     /Unknown
eventClassKey     ciscoMgmt.712.0.1
eventClassMapping     
eventGroup     trap
eventKey     
eventState     0
evid     8a7716b8-bd37-4ab0-9f04-8e3271cad3e6
facility     unknown
firstTime     2012/07/09 16:21:01.000
ipAddress     192.168.1.2
lastTime     2012/07/09 16:21:01.000
Location     
manager     localhost
message     snmp trap ciscoMgmt.712.0.1
monitor     localhost
ntevid     0
ownerid     
priority     -1
prodState     1000
severity     3
stateChange     2012/07/09 16:21:23.000
summary     snmp trap ciscoMgmt.712.0.1
suppid     
Systems     |
Event Details
ciscoMgmt     
ciscoMgmt.712.1.1.2.1.10     AP 'IT-LAB-2' disassociated from Controller '192.168.1.254'.
ciscoMgmt.712.1.1.2.1.11     3
ciscoMgmt.712.1.1.2.1.12     eventType=AP_DISASSOCIATED(5),applicationSpecificAlarmID=UnifiedAp!c0:62:6b:84:c6:80,reportingEntityAddress=192.168.1.254,lastModifiedTimestamp=Mon Jul 09 16:21:00 CEST 2012,alarmCreationTime=2012-04-03 08:29:03.09,eventCount=1,mayBeAutoCleared=false,inst
ciscoMgmt.712.1.1.2.1.14     
ciscoMgmt.712.1.1.2.1.2     2012-04-03T08:29:03.000+02:00
ciscoMgmt.712.1.1.2.1.3     2012-07-09T16:21:00.900+02:00
ciscoMgmt.712.1.1.2.1.4     UnifiedAp!c0:62:6b:84:c6:80
ciscoMgmt.712.1.1.2.1.5     2
ciscoMgmt.712.1.1.2.1.6     AP disassociated from controller
ciscoMgmt.712.1.1.2.1.7     1
ciscoMgmt.712.1.1.2.1.8     192.168.1.254
ciscoMgmt.712.1.1.2.1.9     IT-LAB-2,c0:62:6b:84:c6:80
community     ******
oid     1.3.6.1.4.1.9.9.712.0.1
sysUpTimeInstance     364641801
LOG

 

How would you attack this problem?

Any ideas where I could start to handle these events?

 

The optimal solution should be that the event is critical, and that you see what AP is affected in the summary.

 

Is this even doable?

 

--

Regards Falk

 

Some cleanup..

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points