SPC200 :: bootstatsBoot

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SPC200 › bootstatsBoot

bootstatsBoot

Module: SPC200

OID (symbolic): SPC200::bootstatsBoot

OID (numeric): 1.3.6.1.4.1.22764.1.1.1.5.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Boot

What is bootstatsBoot?

A Counter32 counting how many times this SPC200 chip has booted since it was last reset to zero (e.g. at manufacture or a counter reset). A rising boot count between polls that wasn't caused by the admin is a sign of unexpected power loss or firmware crashes.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.22764.1.1.1.5.1
snmpwalk -v2c -c public <target> SPC200::bootstatsBoot

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.22764.1.1.1.5.1.1
snmpget -v2c -c public <target> SPC200::bootstatsBoot.1

Start monitoring powerline communication (PLC) network adapter/bridge (master/slave BSS role, sync-band/Ethernet interface status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SPC200::bootstatsBoot OID value, configure state conditions and alerts, and monitor any powerline communication (PLC) network adapter/bridge (master/slave BSS role, sync-band/Ethernet interface status) from a single console.

How to Use in IPNetwork Monitor

Select a powerline communication (PLC) network adapter/bridge (master/slave BSS role, sync-band/Ethernet interface 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 bootstatsBoot into the Find box to locate it in the OID tree, then select it and click OK. It reports the boot. 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.1spc200MIBSPC200
1.3.6.1.4.1.22764.1.1plcSPC200
1.3.6.1.4.1.22764.1.1.1statsSPC200
1.3.6.1.4.1.22764.1.1.1.5bootstatsSPC200
1.3.6.1.4.1.22764.1.1.1.5.1bootstatsBootSPC200