Hello,
I have a specific need regarding the reception of SNMP traps on the SensorProbe2+.
I need to be able to process a trap received from an Alcatel Oxe IPBX and convert it into a contact relay.
My SNMP trap arrives successfully on the SensorProbe2+, but I don't know exactly what to enter in the input fields.
My OID is : 1.3.6.1.4.1.637.64.10.1.2
The value I need to analyze in the trap is located under:
1.3.6.1.4.1.637.64.101.1.8:1367
1367 is the value to analyze to trigger the action on the virtual sensor in order to open or close the contact.
Sorry for my English.
Bests regards
- Candidat asked 2 months ago
- You must login to post comments
Dear AKCP Customer,
Thank you for questions on the SP2+ SNMP trap receiver feature.
For example, if you are using SNMPv2, this has changed how traps are formatted by replacing the old “Specific Trap” header with a variable binding (snmpTrapOID.0).
Because our SP2+ Virtual Sensor Trap Receiver uses standard SNMPv1-style logic to maintain a simple interface, as an example, we just need to mathematically split the SNMPv2 Trap OID (1.3.6.1.4.1.637.64.0.10.1.2) into two parts to make it work.
Here is an example of exactly how you would configure the Virtual Sensor:
OID: .1.3.6.1.4.1.637.64.0.10.1 (We drop the last digit from your trap OID to define the base Enterprise OID)
Specific: 2 (This is the last digit of your trap OID)
Value for the normal state: 1368 (Your clear value)
How the SP2+ handles the 1367 / 1368 alarm values
You might be wondering how the SP2+ knows to look at that specific variable binding (.10.1.1.8) to find the 1367 or 1368 value.
To keep the configuration simple, the SP2+ doesn’t require you to map out the exact varbind OID.
Instead, when a trap matches your OID and Specific numbers, the SP2+ automatically scans the entire payload (all 13 variable bindings in your capture) looking for the “Value for the normal state” you defined.
When your device sends the trap with 1367, the SP2+ scans the payload, does not find “1368”, and sets the sensor to an Alarm/Critical state.
When the alarm disappears and the device sends the trap with 1368, the SP2+ finds that match in the payload and immediately returns the sensor to Normal.
Please apply these settings to your SP2+ Virtual Sensor Trap Receiver and trigger a test alarm on your system. If you are still having this issue, please contact out support team directly (support@akcp.com).
You can also use the free third party utility called IReasoning MIB Browser to test the traps being received. This utility can be used to check the SNMP traps being sent and received and to verify the values needed.
Thanks again,
Best regards,
AKCP Support Team
- AKCP Support Team answered 2 months ago
- You must login to post comments
Please login first to submit.