All MIBs › XEDIA-SYSTEM-MIB › xsysSubsystemResetControl
xsysSubsystemResetControl
Module: XEDIA-SYSTEM-MIB
OID (symbolic): XEDIA-SYSTEM-MIB::xsysSubsystemResetControl
OID (numeric): 1.3.6.1.4.1.838.3.1.1.2.3.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Setting this object causes individual subsystems to take action, as defined below. Not all subsystems support all of the actions available. Valid actions for each subsystem can be set without errors. If an action is invalid for a subsystem, then an error PDU of 'BadValue' is returned.
o ready - NoOp. No action is taken by the subsystem.
o defaultConfig - All configuration records associated with the particular subsystem are deleted. The subsystem will restore to default configuration if possible, or it continues to run using its runtime values. On the next node boot, default records will be written to the configuration memory.
o reset - The subsystem will be restarted using its existing configuration memory.
o resetToDefaults - All configuration records associated with the particular subsystem are deleted. The subsystem is then restarted, causing default records to be written to configuration memory.
o purgeRecords - All old configuration records associated with the particular subsystem are deleted. Some subsystems maintain old configuration records. This allows you to downgrade without losing configuration information. These old configuration records consume configuration memory. Purging old configuration records frees the associated configuration memory for current use.
When read, the value of the object is always 'ready(1)'.
What is xsysSubsystemResetControl?
Per-subsystem control action: defaultConfig deletes that subsystem's saved config (falling back to defaults on next boot), reset restarts the subsystem with its existing config, resetToDefaults deletes its config and restarts immediately with defaults, and purgeRecords clears old/legacy config records the subsystem kept around to free up configuration memory. Reading it always returns ready(1), and not every action is valid for every subsystem.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.838.3.1.1.2.3.1.2 snmpwalk -v2c -c public <target> XEDIA-SYSTEM-MIB::xsysSubsystemResetControl
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.838.3.1.1.2.3.1.2.1 snmpget -v2c -c public <target> XEDIA-SYSTEM-MIB::xsysSubsystemResetControl.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.838.3.1.1.2.3.1.2.1 i <value>
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::xsysSubsystemResetControl OID value, configure state conditions and alerts, and monitor any Xedia Corporation routers (boot-image priority/running-image-version status) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.838 | xedia | XEDIA-REG |
| 1.3.6.1.4.1.838.3 | xediaMibs | XEDIA-REG |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.838.3.1 | xediaSystemMIB | XEDIA-SYSTEM-MIB |
| 1.3.6.1.4.1.838.3.1.1 | xsysObjects | XEDIA-SYSTEM-MIB |
| 1.3.6.1.4.1.838.3.1.1.2 | xsysConfigParams | XEDIA-SYSTEM-MIB |
| 1.3.6.1.4.1.838.3.1.1.2.3 | xsysSubsystemTable | XEDIA-SYSTEM-MIB |
| 1.3.6.1.4.1.838.3.1.1.2.3.1 | xsysSubsystemEntry | XEDIA-SYSTEM-MIB |
| 1.3.6.1.4.1.838.3.1.1.2.3.1.2 | xsysSubsystemResetControl | XEDIA-SYSTEM-MIB |