SNMP monitoring by third party software

[Sibin S S]

The implementation project which I am working now is having a centralized management software from Siemens (MSI). This system is monitoring most of the ELV systems. They also want to monitor the network and came up , they can interact with network through SNMP. Their software supports OPC, BACNET and SNMP. As we support SNMP we thought we will go for it and for this have to load the MIBs into their system and did that. 

During the test phase we saw that the way of monitoring by this system is like when ever a hit of any trap occur the value of that trap increment by 1. Say we are using envmon trap and is monitoring the power supply the number will increment when:

1. power is switched off (initial)

2. power is switched off (final)

3. redundant power supply is removed

4. power is on

ie. a single trap is triggered in different cases. the client wants it in either two status like good/bad, Healthy/unhealthy, on/off , 0/1 for a single trap. As I know there system is not capable of telnet/ssh/http(s) to poll and get the status.

Does anyone faced similar issue in integrating with other software. Does this have a solution.

Thank You!!

[Simon Brooks]

Why not just SNMP GET the device frequently rather than sending traps? Then you can configure your monitoring server to set whatever it wants.

[Sibin S S]

Thankyou Simon !! Is there any way to get the specific OIDs for the traps.

[Yermander]

You have OID's wrong - an OID (object identifier) is a value you poll to get status so you could poll the OID of the power supply on the device you're interested in and then I am sure your NMS would have a way to translate the numberis value returned to a human readable 'down, up, missing' etc. Here's a good resource...

http://snmp.cloudapps.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=cseSysCPUUtilization&translate=Translate&submitValue=SUBMIT&submitClicked=true

[Yermander]

BTW you could do a MIB walk on the device to learn what OID's are available to poll on the device

[Palani Mohan · Accepted solution]

Hi Sibin

The notifications (traps) generated by CISCO-ENVMON-MIB are defined here:

ftp://ftp.cisco.com/pub/mibs/traps/CISCO-ENVMON-MIB.traps

Looking at the cmd reference here, looks like your customer needs to configure snmp-server enable traps envmon [shutdown] alone?

The contents are interpreted and presented by the applications that receive them. Given this, unless you approach the support forum for that 3rd party application, it is going to be hard for us, here in Cisco/Support Forums to help you interpret. Notifications in the raw form (pkt captures are the best and accurate) speak truth. So, if you can capture and upload the pkts, we can definitely help you.

Kind regards .... Palani

[Sibin S S]

Hi Palani,

Thanks for the support. We plan to monitor like the table provided below. But when the trap is received it is having a value at the end eg: 1.3.6.1.4.1.9.9.13.1.5.1.3.1061 . This 1061 will sometimes be 1058 or 1062 ... . Since the whole OID is not constant for a particular trap the software is having difficulty in identifying the fault. What this numbers for and is there any way to make them constant?

ALARM	OID	Normal value	Status change value
Voltage	1.3.6.1.4.1.9.9.13.1.2.1.7	1	2/3/4
Temperature	1.3.6.1.4.1.9.9.13.1.3.1.6	1	2/3/4
Fan	1.3.6.1.4.1.9.9.13.1.4.1.3	1	2/3/4
Power Supply	1.3.6.1.4.1.9.9.13.1.5.1.3	1	2/3/4