SPIDCOM-ALARM-MIB :: neAlarmTrapCounter

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSPIDCOM-ALARM-MIBneAlarmTrapCounter

neAlarmTrapCounter

Module: SPIDCOM-ALARM-MIB

OID (symbolic): SPIDCOM-ALARM-MIB::neAlarmTrapCounter

OID (numeric): 1.3.6.1.4.1.22764.2.1.10.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This object counts only the traps sent under node neAlarmTrap.

What is neAlarmTrapCounter?

This counter tracks the number of traps the device has sent specifically under the neAlarmTrap notification branch. An admin uses it to confirm the device's alarm trap mechanism is actively sending notifications, and to detect gaps by comparing counter values over time. For example, a stalled neAlarmTrapCounter despite known new alarms occurring would suggest the trap sending mechanism has stopped working, even if alarms are still being logged in neAlarmTable.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.22764.2.1.10.2
snmpwalk -v2c -c public <target> SPIDCOM-ALARM-MIB::neAlarmTrapCounter

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.22764.2.1.10.2.1
snmpget -v2c -c public <target> SPIDCOM-ALARM-MIB::neAlarmTrapCounter.1

Start monitoring SPiDCOM powerline communication (PLC) modem/adapter (alarm/threshold fault status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SPIDCOM-ALARM-MIB::neAlarmTrapCounter OID value, configure state conditions and alerts, and monitor any SPiDCOM powerline communication (PLC) modem/adapter (alarm/threshold fault status) from a single console.

How to Use in IPNetwork Monitor

Select a SPiDCOM powerline communication (PLC) modem/adapter (alarm/threshold fault status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type neAlarmTrapCounter into the Find box to locate it in the OID tree, then select it and click OK. This object counts only the traps sent under node neAlarmTrap. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.22764spidcomSPIDCOM-MIB
Numeric OIDNameModule
1.3.6.1.4.1.22764.2.1neAlarmSPIDCOM-ALARM-MIB
1.3.6.1.4.1.22764.2.1.10neAlarmTrapSPIDCOM-ALARM-MIB
1.3.6.1.4.1.22764.2.1.10.2neAlarmTrapCounterSPIDCOM-ALARM-MIB