EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-02 02:37 PM . Last Modified: 2024-04-09 04:08 AM
I want to forward my traps to an NNM server and I would like to use the SNMP V3 Inform under "Alarm Configuration" > "Network Management System Intergration".
However the NNM team needs to know what my "Engine ID" is. How can I find that out?
Regards,
J
(CID:99157782)
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: 2020-07-02 02:37 PM . Last Modified: 2024-04-09 04:08 AM
Dear John,
StruxureWare has the ability to send traps using the "Alarm Action" functionality as well as the "Network Management System Integration" feature. These traps can be sent based upon both manually configured thresholds under the "Threshold Alarm Configurations" tab as well as the normally APC device's pre-created alerts (Essential alerts) that are on the "Device Alarm Configurations tab.
If you are using the "Network Management Systems Integration" feature, these traps are sent using the powernet mib. This is the regular APC mib. There will be version related info as well so the file name may be something like Powernet411.mib. All of the APC traps are listed under:
.iso.org.dod.internet.private.enterprises.apc.apc#
.1.3.6.1.4.1.318.0
All the traps and clearing traps for StruxureWare are based on the severity levels of the events such as warning or informational such as:
.iso.org.dod.internet.private.enterprises.apc.apc#.isxcInformationalAlarm
.1.3.6.1.4.1.318.0.740
.iso.org.dod.internet.private.enterprises.apc.apc#.isxcWarningAlarm
.1.3.6.1.4.1.318.0.742
The traps also provide additional information / arguments as described in the mib:
INFORMATIONAL: An ISXC Alarm exists.
- The first argument is the unique ISXC alarm ID.
- The second argument is the ISXC alarm label as a UTF8 string.
- The third argument is the ISXC alarm code.
- The fourth argument is the unique ISXC device ID.
- The fifth argument is the ISXC device label as a UTF8 string.
- The sixth argument is the ISXC parent host.
- The seventh argument is the ISXC device type as a UTF8 string.
- The eighth argument is the device serial number.
- The ninth argument is the device model number.
- The tenth argument is the device host.
- The eleventh argument is the device location as a UTF8 string.
- The twelfth argument is the device contact as a UTF8 string.
- The thirteenth argument is the unique ISXC sensor ID.
- The fourteenth argument is the ISXC sensor label as a UTF8 string.
- The fifteenth argument is the sensor value as a UTF8 string.
- The sixteenth argument is the ISXC alarm start time.
- The seventeenth argument is the ISXC alarm resolution time.
- The eighteenth argument is the description as a UTF8 string.
I hope this helps.
(CID:99157792)
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: 2020-07-02 02:37 PM . Last Modified: 2024-04-09 04:08 AM
Thanks but NNM needs the Engine ID to identify DCE among other agents. Is it just the standard 'DCEIP#161' or is it different/custom for DCE?
(CID:99157858)
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: 2020-07-02 02:37 PM . Last Modified: 2024-04-09 04:08 AM
Do you mean Sender OID?
All of the APC traps are listed under:
.iso.org.dod.internet.private.enterprises.apc.apc#
.1.3.6.1.4.1.318.0
All the traps and clearing traps for StruxureWare are based on the severity levels of the events such as warning or informational such as:
.iso.org.dod.internet.private.enterprises.apc.apc#.isxcInformationalAlarm
.1.3.6.1.4.1.318.0.740
.iso.org.dod.internet.private.enterprises.apc.apc#.isxcWarningAlarm
.1.3.6.1.4.1.318.0.742
Here is an example of SNMP Trap from DCE to Trap Receiver:
I think Your NMS team can work on the information which is provided here along with the DCE IP address to map. As far as I know, they need your DCE IP address to discover and they will use the SNMP OID to map.
(CID:99157798)
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: 2020-07-02 02:37 PM . Last Modified: 2024-04-09 04:08 AM
I believe you are using SNMPV1 Traps. I am requesting information on SNMP V3 Inform, which should require a handshake between devices.
(CID:100340148)
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: 2020-07-02 02:37 PM . Last Modified: 2023-10-31 10:59 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
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.