topic RE: XMC APC-UPS-Traps config in ExtremeCloud IQ- Site Engine Management Center

XMC APC-UPS-Traps config

Eisi1 — Wed, 06 Mar 2019 18:01:00 GMT

Hello,

I need alarms in XMC from APC-UPS-Traps. I added this to trapd.conf:

OID_ALIAS apc .1.3.6.1.4.1.318

EVENT upsDiagnosticsPassed .1.3.6.1.4.1.318.6.10 "Status Alarms" Warning
FORMAT upsDiagnosticsPassed: $1
SDESC
Test!!!!!!!!!!!!!!!!!!!!!
INFORMATIONAL: The UPS passed its internal self-test
EDESC

Then I restarted XMC and have done the alarm-config for the trap. But I get no alarm, I only see the trap in
trap-Log. How can I solve this? Anybody already have this working and can share the right config?

RE: XMC APC-UPS-Traps config

Ronald_Dvorak — Thu, 07 Mar 2019 18:21:00 GMT

Please post screenshots of the alarm config.

RE: XMC APC-UPS-Traps config

Eisi1 — Thu, 07 Mar 2019 22:40:00 GMT

RE: XMC APC-UPS-Traps config

Ronald_Dvorak — Thu, 07 Mar 2019 23:06:00 GMT

Looks OK, could you please doubleclick the apc trap that you get in the trap tab of XMC Console and provide a screenshot (example below).

RE: XMC APC-UPS-Traps config

Eisi1 — Fri, 08 Mar 2019 17:00:00 GMT

RE: XMC APC-UPS-Traps config

Ronald_Dvorak — Fri, 08 Mar 2019 17:28:00 GMT

For me it looks like that you've created an alarm for 1.3.6.1.4.1.318.6.10 but the trap that is received is 1.3.6.1.4.1.318.2.3.3.0 - in that case the alarm is not triggered.

I think the easy way to do it would be a trigger on the text "UPS: Passed internal self-test."

-Ron

RE: XMC APC-UPS-Traps config

Eisi1 — Fri, 08 Mar 2019 18:12:00 GMT

Hello Ronald,

thanks for your hints. I have tested with 1.3.6.1.4.1.318.2.3.3.0 but it's also not working. This oid is for retrieving the text string "UPS: Passed internal self-test."
Wireshark show me this trap-data:
enterprise: 1.3.6.1.4.1.318 (iso.3.6.1.4.1.318)
generic-trap: enterpriseSpecific (6)
specific-trap: 10
My problem is, I dont know how to specify generic-trap-code and specific-trap-code in trapd.conf.
I have already tested to created an alarm with text-match in trap-log. This is working, but I think it's better to do it with mapping the trap to the alarm. But how?