Exeltech KC SNMP MIB reference
Exeltech Software Downloads · Download KCSNMPV2.mib
KCSNMPV2.mib describes what the monitor card of an Exeltech KC power system reports over SNMP, and the settings an SNMP manager can change. This page lists every object and trap in it, with its full OID, and what to watch for.
| Item | Value |
|---|---|
| Module | EXELTECH-MIB |
| File | KCSNMPV2.mib (dated 29 July 2024) |
| Enterprise | 1.3.6.1.4.1.30320 (Exeltech) |
| Objects | 1.3.6.1.4.1.30320.2.0, below called … |
| Format | SMIv1 objects (OBJECT-TYPE) and SNMPv1 traps (TRAP-TYPE) |
Using the MIB
- Load it into your SNMP manager or MIB browser. It imports
RFC1155-SMI,RFC-1212,RFC-1215andSNMPv2-TC, which managers usually have already. Its comment says it was validated with Muonics' smicheck. - Every object is a scalar: read it with the instance
.0, for example1.3.6.1.4.1.30320.2.0.1.1.0for the battery voltage. - Communities: StatusBoost reads with
publicand writes withprivate, over SNMP v2c on UDP port 161. - Traps go to the trap managers set in
trap-target-ip1totrap-target-ip3. - Many settings are easier to change in StatusBoost: its Network Feature Setup sets the trap managers, the network settings, SNTP and the all-good trap. The alarm configuration is set with StatusBoost's System Configuration or the Alarm Configuration Tool.
Objects
Battery: ….1
| OID | Name | Access | Meaning |
|---|---|---|---|
….1.1 |
batDCV |
read-only | Battery voltage, in tenths of a volt: divide by 10 |
….1.2 |
batDCI |
read-only | Battery current, A |
….1.3 |
batABUS |
read-only | A bus DC voltage, V, if the system has one |
….1.4 |
batBBUS |
read-only | B bus DC voltage, V, if the system has one |
Phases 1 to 3: ….2, ….3, ….4
Each phase has the same eight objects: phase 1 under ….2, phase 2 under ….3, phase 3 under ….4. In the names, n is the phase number.
| OID (phase 1) | Name | Access | The MIB's description |
|---|---|---|---|
….2.1 |
utilityAcvLn |
read-only | Inverter AC voltage, V. See known issue 1 |
….2.2 |
utilityAciLn |
read-only | Inverter current, A. See known issue 1 |
….2.3 |
utilityFrqLn |
read-only | Inverter frequency, Hz. See known issue 1 |
….2.4 |
inverterAcvLn |
read-only | Utility AC voltage, V. See known issue 1 |
….2.5 |
inverterAciLn |
read-only | Utility current, A. See known issue 1 |
….2.6 |
inverterFrqLn |
read-only | Utility frequency, Hz. See known issue 1 |
….2.7 |
line1AcvOut, line2ACVOut, line3ACVOut |
read-only | Output voltage, V |
….2.8 |
temperatureSTSLn |
read-only | SCR (transfer switch) temperature, °C |
Alarms: ….5
| OID | Name | Access | Meaning |
|---|---|---|---|
….5.1 |
systemAlarms |
read-only | The conditions present now, one bit each: see the bits |
….5.2 |
slotAlarms |
read-only | Module slots not communicating: bit 0 (0x001) is slot 1, up to bit 10 (0x400), slot 11 |
….5.3 |
alarmOne |
read-only | Alarm 1, the minor alarm: 1 when a condition configured for Alarm 1 is present, else 0 |
….5.4 |
alarmTwo |
read-only | Alarm 2, the major alarm: 1 when a condition configured for Alarm 2 is present, else 0 |
The bits of systemAlarms
Bits 0 to 15 are the power system's conditions, and bits 16 to 31 the transfer switch's. The last column is the name StatusBoost and the Alarm Configuration Tool show for the same condition, where they show one.
| Bit | Mask | The MIB's text | In StatusBoost |
|---|---|---|---|
| 0 | 0x00000001 |
Low DC Volt Alarm | Module Low DCV Detected |
| 1 | 0x00000002 |
Power Module Fail | Module Overload Detected (see known issue 3) |
| 2 | 0x00000004 |
NA | |
| 3 | 0x00000008 |
PowerLvlIndicator | Module Marginal Load Level Detected |
| 4 | 0x00000010 |
Module Temperature Warning | Module Temp Warning Detected |
| 5 | 0x00000020 |
Module Local Disable | Module Offline Detected (see known issue 3) |
| 6 | 0x00000040 |
cage comm failure detected | Inverter System Cage Comm Degraded |
| 7 | 0x00000080 |
AB Bus Fail Detect | Inverter System AB Bus Fault Detected |
| 8 | 0x00000100 |
System Disable | Inverter System Offline Detected |
| 9 | 0x00000200 |
Power Module fail detected | Module Fault Detected |
| 10 | 0x00000400 |
Slot Not Detected fault | Module Not Detected |
| 11 | 0x00000800 |
Ph1 on Ref2 | Phase 1 on Reference 2 |
| 12 | 0x00001000 |
Ph1 on Ref2 (see known issue 2) | Phase 2 on Reference 2 |
| 13 | 0x00002000 |
Ph1 on Ref2 (see known issue 2) | Phase 3 on Reference 2 |
| 14 | 0x00004000 |
NA | Cage Not Detected (see known issue 3) |
| 15 | 0x00008000 |
NA | |
| 16 | 0x00010000 |
Utility Primary | Utility Primary |
| 17 | 0x00020000 |
Inverter source fault | Bad Inverter Source |
| 18 | 0x00040000 |
Utility source fault | Bad Utility Source |
| 19 | 0x00080000 |
MBS Lockout Asserted | MBS Lockout Asserted |
| 20 | 0x00100000 |
Sources not sync | Sources Not Sync'd |
| 21 | 0x00200000 |
Fan fault detect STS PowerSwitch | PowerSwitch Fan Fault Detected |
| 22 | 0x00400000 |
Warm Temp STS PowerSwitch | PowerSwitch Warm Temp |
| 23 | 0x00800000 |
Overtemp STS PowerSwitch | PowerSwitch Over Temp |
| 24 | 0x01000000 |
SCR Active (Legacy) | |
| 25 | 0x02000000 |
Utility SCR Driving | PowerSwitch Utility Source Engaged |
| 26 | 0x04000000 |
STS Backfeed protection enabled | STS Backfeed Protection Engaged |
| 27 | 0x08000000 |
Line 2 Line fail | Line to Line Fault Detected |
| 28 | 0x10000000 |
STS Forced Inverter State | Forced Inverter State Detected |
| 29 | 0x20000000 |
STS Forced Utility State | Forced Utility State Detected |
| 30 | 0x40000000 |
STS Forced Contactor Open | Forced Contactor Open |
| 31 | 0x80000000 |
STS Contactor Open Detected | Contactor Open Detected |
Settings: ….6
| OID | Name | Access | Meaning |
|---|---|---|---|
….6.1 |
dCVLow |
read-write | Low battery voltage limit for lowDCtrap, in tenths of a volt: multiply the voltage by 10 |
….6.2 |
dCVHigh |
read-write | High battery voltage limit for highDCtrap, in tenths of a volt |
….6.3 |
alarm1Configuration |
read-only | Which systemAlarms bits raise Alarm 1, as a mask of the same bits. The MIB says to change it with ProductStatus; today that is StatusBoost's System Configuration or the Alarm Configuration Tool |
….6.4 |
alarm2Configuration |
read-only | Which systemAlarms bits raise Alarm 2, the same way |
….6.5 |
slotConfiguration |
read-only | Which module slots are configured, one bit each as in slotAlarms |
….6.6 |
trap-target-ip1 |
read-write | IP address of the first trap manager. 0.0.0.0 stops all traps |
….6.7 |
trap-target-ip2 |
read-write | IP address of the second trap manager; 0.0.0.0 removes it |
….6.8 |
trap-target-ip3 |
read-write | IP address of the third trap manager; 0.0.0.0 removes it |
….6.9 |
ipAddressStatic |
read-write | The static IP address |
….6.10 |
subnetMaskStatic |
read-write | The static subnet mask |
….6.11 |
defaultGatewayStatic |
read-write | The static default gateway |
….6.12 |
setNetworkConfig |
read-write | Network options, one bit each: 0x01 DHCP or 0x02 static address, 0x04 SNMP, 0x08 SNTP, 0x10 web server. Writing it restarts the network card; clearing 0x04 turns off SNMP |
….6.13 |
ntp-ip1 |
read-write | IP address of the SNTP server |
….6.14 |
ntp-set |
read-write | The time zone for SNTP. Set it with StatusBoost's Network Feature Setup |
….6.15 |
traps-config |
read-write | The all-good trap: one every 30 s × the value (0 to 255); 0 turns it off |
….6.16 |
logging-config |
read-write | Factory use only |
System and modules: ….7
| OID | Name | Access | Meaning |
|---|---|---|---|
….7.1 |
systemName |
read-write | The system's part number, from its barcode |
….7.2 |
systemSerial |
read-write | The system's serial number |
….7.3 |
monitorName |
read-only | The monitor card's part number, from its barcode |
….7.4 |
monitorSer |
read-only | The monitor card's serial number |
….7.5 to ….7.70 |
slot1Name … slot11Out |
read-only | Six objects for each module slot, 1 to 11 (below) |
The systemName and systemSerial are set at the factory.
Slot s (1 to 11) starts at ….7.(6s − 1): slot 1 at ….7.5, slot 2 at ….7.11, up to slot 11 at ….7.65. From there:
| OID (slot 1) | Name | Meaning |
|---|---|---|
….7.5 |
slotsName |
The module's part number, from its barcode |
….7.6 |
slotsSer |
The module's serial number |
….7.7 |
slotsFan |
The module's fan speed |
….7.8 |
slotsTemp |
The module's temperature |
….7.9 |
slotsSt |
The module's status bits |
….7.10 |
slotsOut |
The module's output level |
In the names, s is the slot number, for example slot7Temp at ….7.44.
Traps
The traps are SNMPv1 traps. A manager that receives them as SNMPv2 notifications sees the trap OID enterprise.0.number (RFC 3584), shown in the last column.
| Trap | Enterprise | Number | Variables | When | SNMPv2 trap OID |
|---|---|---|---|---|---|
lowDCtrap |
batDCV (….1.1) |
1 | batDCV, dCVLow |
The battery voltage fell below the low limit | ….1.1.0.1 |
highDCtrap |
batDCV (….1.1) |
2 | batDCV, dCVHigh |
The battery voltage rose above the high limit | ….1.1.0.2 |
alarmConfig1trap |
alarms (….5) |
3 | alarm1Configuration, systemAlarms |
Alarm 1, the minor alarm, was raised | ….5.0.3 |
alarmConfig2trap |
alarms (….5) |
4 | alarm2Configuration, systemAlarms |
Alarm 2, the major alarm, was raised | ….5.0.4 |
generalAlarmtrap |
alarms (….5) |
5 | alarmOne, alarmTwo |
A general status update | ….5.0.5 |
slotAlarmtrap |
alarms (….5) |
6 | slotAlarms |
A module slot status update (see known issue 4) | ….5.0.6 |
Known issues
- Utility or inverter: the phase objects' names and descriptions disagree. Objects 1 to 3 of each phase are named
utility…, but described as inverter values; objects 4 to 6 are namedinverter…, but described as utility values. Which is right is being checked. Until then, compare a reading with what StatusBoost shows before relying on it. - Bits 11, 12 and 13 of
systemAlarmsall read "Ph1 on Ref2" in the MIB. They are phase 1, phase 2 and phase 3 on Reference 2. - Bits 1, 5 and 14 of
systemAlarmshave different names in the MIB and in StatusBoost: "Power Module Fail" and Module Overload Detected; "Module Local Disable" and Module Offline Detected; "NA" and Cage Not Detected. The table above shows both. slotAlarmtraphas the same description asgeneralAlarmtrap, "A general Status update". It carriesslotAlarms, so it reports the module slots.- The bit masks are signed.
systemAlarmsand the configuration objects areINTEGER, a signed 32-bit number, so a manager shows a value with bit 31 (Contactor Open Detected) set as negative. Read them as unsigned 32-bit numbers.
These are notes about the MIB's text. The MIB file is published as it is, so the object names and OIDs that managers already use stay the same.