APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-28 06:19 AM . Last Modified: 2024-03-18 02:30 AM
For AP86**, the specific id is 752 in the SNMP trap packet if a critical event occurs. I can only find the event type from the sixth variable (trap text message). In product, I think it is not an elegant behavior to get the event type through parsing the text.
Can I get the event type by taking other methods? Does anyone have error number list?
rpduWarningCondition TRAP-TYPE
ENTERPRISE apc
VARIABLES { mtrapargsString02, mtrapargsString03, mtrapargsInteger, mtrapargsInteger02, mtrapargsInteger03, mtrapargsString }
DESCRIPTION
"WARNING: A RPDU warning condition has been detected.
The first variable is the serial number.
The second variable is the device name.
The third variable is *the error number*.
The fourth variable is the device number.
The fifth variable is the instance number.
The sixth variable is the trap text message."
--#TYPE "RPDU: A warning condition has been detected."
--#SUMMARY "A warning condition has been detected."
--#SEVERITY WARNING
--#TIMEINDEX 1
--#HELP ""
--#HELPTAG 0
--#STATE DEGRADED
::= 752
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-28 06:19 AM . Last Modified: 2024-03-18 02:29 AM
i also received this message internally via a different channel and this forum post was referenced so i am sure you will get all of the additional information we are able to provide based on your subsequent questions.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-28 06:19 AM . Last Modified: 2024-03-18 02:30 AM
this particular trap is built from variable data so unfortunately, it could be any warning condition on the unit - not necessarily always the same warning message.
here is how it is explained:
WARNING: A RPDU warning condition has been detected.
The first variable is the serial number.
The second variable is the device name.
The third variable is the error number.
The fourth variable is the device number.
The fifth variable is the instance number.
The sixth variable is the trap text message.
there is also the same thing for a critical alarm. If you download the config.ini, you can view all the possible events under the [EventActionConfig] section to see all of the critical and warning alerts that could come up.
directions on downloading config.ini -> http://nam-en.apc.com/app/answers/detail/a_id/9321
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-28 06:19 AM . Last Modified: 2024-03-18 02:30 AM
Great, thanks for your answer. It is very helpful.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-28 06:19 AM . Last Modified: 2024-03-18 02:29 AM
i also received this message internally via a different channel and this forum post was referenced so i am sure you will get all of the additional information we are able to provide based on your subsequent questions.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.