CME-MIB :: bladePowerServiceResetCmd

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBbladePowerServiceResetCmd

bladePowerServiceResetCmd

Module: CME-MIB

OID (symbolic): CME-MIB::bladePowerServiceResetCmd

OID (numeric): 1.3.6.1.4.1.2.3.51.2.23.10.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: NOTE: Do not perform this service reset operation on a node that is currently in a maintenance mode state. See bladeHealthState in bladeSystemStatusTable for maintMode(12) value.

To reset the auxiliary power on a blade component, set this object to resetVirtualReseatOperation(1). This will toggle the auxiliary power to the blade and simulate a physical removal and insertion. During the operation, auxiliary power is removed from the component and is then restored. For nodes, the power state will remain off and the user will need to manually power on the node.

To perform a hard restart on the blade component, set this object to resetHardRestartOperation(2). This will toggle the reset line to the service processor causing it to re-initialize. The service processor on the component is directly reset, but the power state of the component will not be affected by this operation.

This object is intended to be write-only.

The component will experience a temporary loss of communication and the power state will change. Prior to executing this action, perform any operations needed to protect user data.

Reading this object will always return the value of noOperation(0).

What is bladePowerServiceResetCmd?

This object lets an admin remotely toggle a blade's auxiliary power to simulate a physical removal and reinsertion, or perform a hard restart, with an explicit warning not to use it on a blade currently in maintenance mode per bladeHealthState. An admin trying to recover a stuck blade without physically removing it from the chassis sets this object to trigger the reseat remotely. For example, an admin would set this to resetVirtualReseatOperation on a hung blade after first confirming via bladeSystemStatusTable that it isn't flagged as being in maintenance mode.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.23.10.1.1.4
snmpwalk -v2c -c public <target> CME-MIB::bladePowerServiceResetCmd

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.23.10.1.1.4.1
snmpget -v2c -c public <target> CME-MIB::bladePowerServiceResetCmd.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.23.10.1.1.4.1 i <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> bladePowerServiceResetCmd.1

Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::bladePowerServiceResetCmd OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.

OID Breakdown

Upper-level ancestors (10 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.2ibmBLADE-MIB
1.3.6.1.4.1.2.3ibmAgentsBLADE-MIB
1.3.6.1.4.1.2.3.51netfinitySupportProcessorAgentBLADE-MIB
1.3.6.1.4.1.2.3.51.2bladeCenterSnmpMIBBLADE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.3.51.2.23serviceCME-MIB
1.3.6.1.4.1.2.3.51.2.23.10componentPowerServiceResetCME-MIB
1.3.6.1.4.1.2.3.51.2.23.10.1bladePowerServiceResetTableCME-MIB
1.3.6.1.4.1.2.3.51.2.23.10.1.1bladePowerServiceResetEntryCME-MIB
1.3.6.1.4.1.2.3.51.2.23.10.1.1.4bladePowerServiceResetCmdCME-MIB