02-21-2013 10:00 AM
We are trying to incorporate our IP cameras (2500 series) into a Nagios/Nagvis reporting server with maps and so on. (pardon me if my terminology is bad) I set the SNMP trap destination and community name. We are getting responses that don't follow the standard OID format. Is this because Cisco doesn't support some MIB's OID's? Could anyone confirm this? Here is an example of the info we get. The number or ID changes and almost seem random in creation. (I omitted the specific names and IP address's)
Thu Feb 21 11:38:38 2013: Unknown trap (.1361465141) received from (our server name) at:
Value 0: (server name)
Value 1: (server IP address)
Value 2: 289:0:31:37.62
Value 3: .1361465141
Value 4: (server ip address)
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.28196.2.0.7
Ent Value 1: .1.3.6.1.4.1.28196.2.1.1=p_s1_(camera name)_1
Thu Feb 21 11:28:38 2013: Unknown trap (.1361464541) received from (server name)at:
Value 0: (server name)
Value 1: (server IP)
Value 2: 289:0:21:37.57
Value 3: .1361464541
Value 4: (server IP)
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.28196.2.0.7
Ent Value 1: .1.3.6.1.4.1.28196.2.1.1=p_s1_(camera name)_1
Thanks for the help!
02-21-2013 01:14 PM
Hi Dean,
The cameras do not send standard snmp traps that would be useful for your 3rd party monitoring. The VSMS (media server) sends snmp traps when a camera is disconnected (misses 3 heartbeats), archive recording fails, etc. You would have better success using the MIB for the VSMS server to report issues with cameras.
My recommendation is to give your Nagios expert the downloaded MIB from the following location:
http://
I hope that helps,
Jim
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