TIMETRA-APS-MIB :: tApsAnnexBCommandSwitch

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-APS-MIB › tApsAnnexBCommandSwitch

tApsAnnexBCommandSwitch

Module: TIMETRA-APS-MIB

OID (symbolic): TIMETRA-APS-MIB::tApsAnnexBCommandSwitch

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.29.6.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The value of tApsAnnexBCommandSwitch specifies the Annex B supported APS switch command applied to the APS group.

The supported values:

'noCmd(1)' -- no command was applied to the group since system -- initialization. 'lockout(2)' -- lockout the APS group. 'clearLockout(3)' -- clear the lockout.

Sets to value 'lockout(2)' or 'clearLockout(3)' will be rejected with error inconsistentValue if APS-MIB::apsConfigMode is not equal to 'onePlusOneOptimized(4)'. If 'noCmd(1)' is used in a write operation a wrongValue error is returned.

When read this object returns the last command written or 'noCmd(1)'.

What is tApsAnnexBCommandSwitch?

This value applies an Annex B APS protection switch command to the group: noCmd(1), meaning no command has been applied since system initialization, lockout(2), locking out protection switching, or clearLockout(3), removing a lockout; lockout and clearLockout are rejected with an inconsistentValue error unless the group's apsConfigMode is onePlusOneOptimized(4), and writing noCmd(1) itself returns a wrongValue error. An admin sets this to lockout(2) to prevent protection switching during planned maintenance on the working circuit, then clearLockout(3) once maintenance is complete. Setting tApsAnnexBCommandSwitch to lockout(2) on a group not configured for onePlusOneOptimized mode will be rejected with an inconsistentValue error rather than silently taking effect.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.29.6.1.1
snmpwalk -v2c -c public <target> TIMETRA-APS-MIB::tApsAnnexBCommandSwitch

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.29.6.1.1.1
snmpget -v2c -c public <target> TIMETRA-APS-MIB::tApsAnnexBCommandSwitch.1

Set instance 1 (SNMPv2c):

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

Start monitoring Nokia/Alcatel-Lucent 7750 SR (SROS) router with SONET/SDH interfaces (APS protection-channel/failover status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-APS-MIB::tApsAnnexBCommandSwitch OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR (SROS) router with SONET/SDH interfaces (APS protection-channel/failover status) 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.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.29tApsMIBObjsTIMETRA-APS-MIB
1.3.6.1.4.1.6527.3.1.2.29.6tApsGroupCommandTableTIMETRA-APS-MIB
1.3.6.1.4.1.6527.3.1.2.29.6.1tApsGroupCommandEntryTIMETRA-APS-MIB
1.3.6.1.4.1.6527.3.1.2.29.6.1.1tApsAnnexBCommandSwitchTIMETRA-APS-MIB