XEDIA-SYSTEM-MIB :: xsysNumResets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › XEDIA-SYSTEM-MIB › xsysNumResets

xsysNumResets

Module: XEDIA-SYSTEM-MIB

OID (symbolic): XEDIA-SYSTEM-MIB::xsysNumResets

OID (numeric): 1.3.6.1.4.1.838.3.1.1.1.7

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: A count of the number of times the system has been reset either via a hardware switch, via the software xsysResetControl object, or via any other means (cable seeking backhoe, software spasm, etc.) Note that a manager can use this object to determine if it has missed any warmStart or coldStart traps and to detect counter discontinuities.

What is xsysNumResets?

Running count of how many times the system has been reset, whether by hardware switch, the xsysResetControl object, or any other cause; an NMS can use it to detect a reboot it might otherwise have missed via warmStart/coldStart traps.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.838.3.1.1.1.7
snmpwalk -v2c -c public <target> XEDIA-SYSTEM-MIB::xsysNumResets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.838.3.1.1.1.7.1
snmpget -v2c -c public <target> XEDIA-SYSTEM-MIB::xsysNumResets.1

Start monitoring Xedia Corporation routers (boot-image priority/running-image-version status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XEDIA-SYSTEM-MIB::xsysNumResets OID value, configure state conditions and alerts, and monitor any Xedia Corporation routers (boot-image priority/running-image-version status) from a single console.

How to Use in IPNetwork Monitor

Select a Xedia Corporation router (boot-image priority/running-image-version 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 xsysNumResets into the Find box to locate it in the OID tree, then select it and click OK. It reports a count of the number of times the system has been reset either via a hardware switch, via the software xsysResetControl object, or via any other means (cable seeking backhoe, software spasm, etc.) Note that a manager can use this object to. 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 (8 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.838xediaXEDIA-REG
1.3.6.1.4.1.838.3xediaMibsXEDIA-REG
Numeric OIDNameModule
1.3.6.1.4.1.838.3.1xediaSystemMIBXEDIA-SYSTEM-MIB
1.3.6.1.4.1.838.3.1.1xsysObjectsXEDIA-SYSTEM-MIB
1.3.6.1.4.1.838.3.1.1.1xsysGeneralXEDIA-SYSTEM-MIB
1.3.6.1.4.1.838.3.1.1.1.7xsysNumResetsXEDIA-SYSTEM-MIB