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)'.
Parsed from file xsys.mib.txt
Company: None
Module: XEDIA-SYSTEM-MIB
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)'.
Parsed from file XEDIA-SYSTEM-MIB.mib
Module: XEDIA-SYSTEM-MIB
Vendor: Xedia Corporation
Module: XEDIA-SYSTEM-MIB
[Automatically extracted from oidview.com]
xsysSubsystemResetControl OBJECT-TYPE SYNTAX INTEGER { ready(1), defaultConfig(2), reset(3), resetToDefaults(4), purgeRecords(5) } MAX-ACCESS read-write STATUS current 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)'." DEFVAL { ready } ::= { xsysSubsystemEntry 2 }
xsysSubsystemResetControl OBJECT-TYPE SYNTAX INTEGER { ready(1), defaultConfig(2), reset(3), resetToDefaults(4), purgeRecords(5) } MAX-ACCESS read-write STATUS current 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)'." DEFVAL { ready } ::= { xsysSubsystemEntry 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.1.1.2.3.1.1 | xsysSubsystemName | 0 | 0 | The name that uniquely identifies the subsystem. |