All MIBs › CISCO-APS-MIB › cApsStatusCurrent
cApsStatusCurrent
Module: CISCO-APS-MIB
OID (symbolic): CISCO-APS-MIB::cApsStatusCurrent
OID (numeric): 1.3.6.1.4.1.9.10.71.1.2.1.3
Node type: OBJECT-TYPE
Type: Bits
Access: read-only
Description: The current status of the APS group.
modeMismatch
Modes other than 1+1 unidirectional monitor protection line K2 bit 5, which indicates the architecture and K2 bits 6-8, which indicate if the mode is unidirectional or bidirectional. A conflict between the current local mode and the received K2 mode information constitutes a mode mismatch.
channelMismatch
This bit indicates a mismatch between the transmitted K1 channel and the received K2 channel has been detected.
psbf
This bit indicates a Protection Switch Byte Failure (PSBF) is in effect. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames.
feplf
Modes other than 1+1 unidirectional monitor the K1 byte for Far-End Protection-Line failures. A Far-End Protection-Line defect is declared based on receiving SF on the protection line.
extraTraffic
This bit indicates whether extra traffic is currently being accepted on the protection line.
What is cApsStatusCurrent?
This BITS-valued object reports the current status of the APS group as a set of independently-settable flags, including modeMismatch (a conflict between this device's configured architecture/directionality and what the far end's K2 byte indicates), channelMismatch, PSBF (Protection Switch Byte Failure), FEPLF (Far-End Protection-Line Failure), and whether extra traffic is currently active, among others. Because it's a bit field rather than a single enumerated value, multiple conditions can be flagged simultaneously, so an admin needs to check each relevant bit individually rather than assuming only one condition can be active at a time. For example, a group could simultaneously show both modeMismatch and psbf set if the far end is sending an inconsistent K2 mode indication and its K1 byte is also failing consistency checks, pointing to a broader signaling problem with that far-end connection rather than a single isolated issue.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.71.1.2.1.3 snmpwalk -v2c -c public <target> CISCO-APS-MIB::cApsStatusCurrent
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.71.1.2.1.3.1 snmpget -v2c -c public <target> CISCO-APS-MIB::cApsStatusCurrent.1
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::cApsStatusCurrent 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 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.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.10 | ciscoExperiment | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.10.71 | cApsMIB | CISCO-APS-MIB |
| 1.3.6.1.4.1.9.10.71.1 | cApsMIBObjects | CISCO-APS-MIB |
| 1.3.6.1.4.1.9.10.71.1.2 | cApsStatusTable | CISCO-APS-MIB |
| 1.3.6.1.4.1.9.10.71.1.2.1 | cApsStatusEntry | CISCO-APS-MIB |
| 1.3.6.1.4.1.9.10.71.1.2.1.3 | cApsStatusCurrent | CISCO-APS-MIB |