CISCO-APS-MIB :: cApsCommandSwitch

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-APS-MIB › cApsCommandSwitch

cApsCommandSwitch

Module: CISCO-APS-MIB

OID (symbolic): CISCO-APS-MIB::cApsCommandSwitch

OID (numeric): 1.3.6.1.4.1.9.10.71.1.5.1.1

Node type: OBJECT-TYPE

Type: CApsSwitchCommand

Access: read-write

Description: Allows the initiation of an APS switch command on the APS group and channel specified by the index values.

If the APS switch command cannot be executed because an equal or higer priority request is in effect, an error is returned.

When read this object returns the last command written or noCmd if no command has been written to this channel since initialization. The return of the last command written does not imply that this command is currently in effect. This request may have been preempted by a higher priority local or remote request. In order to determine the current state of the APS group it is necessary to read the objects cApsStatusK1K2Rcv and cApsStatusK1K2Trans.

The value lockoutOfProtection should only be applied to the protection line channel since that switch command prevents any of the working channels from switching to the protection line. Following the same logic, forcedSwitchProtectToWork and manualSwitchProtectToWork should only be applied to the protection line channel.

forcedSwitchWorkToProtect and manualSwitchWorkToProtect should only be applied to a working channel.

What is cApsCommandSwitch?

This write-triggered object lets an admin manually issue an APS switch command (such as forcing traffic onto or off of the protection line) for the specific group and channel identified by this row's index values, and if a competing request of equal or higher priority is already active, the write attempt fails with an error rather than silently being accepted. Reading this object back doesn't necessarily reflect current live status -- it returns the last command the admin actually wrote (or noCmd if none has been written since the device last initialized), which an admin should not mistake for the channel's real-time protection state. For example, an admin performing planned maintenance on a working channel's line card would write a forced-switch command here to proactively move that channel's traffic onto protection before pulling the card, and if a higher-priority automatic signal failure request happened to already be in effect for the same channel, that manual command would be rejected with an error instead.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.71.1.5.1.1
snmpwalk -v2c -c public <target> CISCO-APS-MIB::cApsCommandSwitch

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.71.1.5.1.1.1
snmpget -v2c -c public <target> CISCO-APS-MIB::cApsCommandSwitch.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.10.71.1.5.1.1.1 s <value>

Start monitoring Cisco optical/SONET-SDH transport equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-APS-MIB::cApsCommandSwitch OID value, configure state conditions and alerts, and monitor any Cisco optical/SONET-SDH transport equipment from a single console.

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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.71cApsMIBCISCO-APS-MIB
1.3.6.1.4.1.9.10.71.1cApsMIBObjectsCISCO-APS-MIB
1.3.6.1.4.1.9.10.71.1.5cApsCommandTableCISCO-APS-MIB
1.3.6.1.4.1.9.10.71.1.5.1cApsCommandEntryCISCO-APS-MIB
1.3.6.1.4.1.9.10.71.1.5.1.1cApsCommandSwitchCISCO-APS-MIB