Technical FAQs

Ask a Question

RFC1628 MIB Compatibility with UPS Network Management Card 2 (AP9630/AP9631)


Issue

RFC1628 MIB Compatibility with UPS Network Management Card 2 (AP9630/AP9631)


Product Line

  • Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH

 

Environment

  • All serial numbers
  • Firmware applications sumx and sy v5.1.7 or higher


Cause

This article outlines compatibility with APC UPS systems and the RFC1628 Generic UPS MIB.


Resolution

The autonomous MIB defines the standard managed objects for Uninterruptible Power Supplies which are to be manageable via SNMP. Currently, Schneider Electric only supports this MIB with AP9630/AP9631 with sumx and sy APPs v5.1.7 and higher. The autonomous MIB does not support many newer, advanced features such as outlet groups, thus Schneider Electric recommends using its own PowerNet MIB to take full advantage of the monitoring and manageability of APC UPSs and other APC specific devices.

In order for the autonomous MIB to work properly, you will also need to have RFC1215, RFC1212, SNMPv2-TC, SNMPv2-SMI MIBs/files loaded in your SNMP NMS or MIB Browser. The upsMIB is located at .iso.org.dod.internet.mgmt.mib-2.upsMIB (.1.3.6.1.2.1.33.)

In regards to traps, a Network Management Card supports up to (6) trap receivers. Each individual trap receiver can only be configured to send autonomous MIB traps OR Schneider Electric's PowerNet MIB traps. You can set two trap receivers as the same host/IP and configure one for autonomous traps and one for PowerNet MIB traps if you wish to receive both.  If you have both autonomous MIB and PowerNet MIB loaded, you may receive two traps for a particular alarm - (1) sent referencing upsAlarmDescr and the particular condition outlined in upsWellKnownAlarms (.1.3.6.1.2.1.33.1.6.3) and (1) sent that has been mapped through the PowerNet MIB from the autonomous MIB.

Also, please take note that the autonomous alarms are named by an autonomous OID, upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. 

Within the Network Management Card, the autonomous MIB events are informational and disabled by default.

 

Was this helpful?
What can we do to improve the information ?