All MIBs › TIMETRA-APS-MIB › tApsMcApsCtlLinkState
tApsMcApsCtlLinkState
Module: TIMETRA-APS-MIB
OID (symbolic): TIMETRA-APS-MIB::tApsMcApsCtlLinkState
OID (numeric): 1.3.6.1.4.1.6527.3.1.2.29.4.1.1
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The value of tApsMcApsCtlLinkState indicates the current state of the 7x50 Multi-Chassis (MC) APS Group Control Link.
Note that for a Single-Chassis APS group the state is always up.
The state 'up' indicates that the 7x50 MC-APS controller has received a valid control message from its neighboring router within the last tApsMcHoldTime interval, and the MC-APS control link is considered as operational.
The state 'dnSignalingFailure' indicates that the 7x50 MC-APS controller hasn't received any control message from its neighboring router or vice-versa within the last tApsMcHoldTime interval.The MC-APS control link is considered as operationally down.
The state 'dnIncompatibleNbr' indicates that the 7x50 MC-APS controller has received a control message from a neighboring router within the last tApsMcHoldTime interval, but the member circuit type (i.e. working/protection) of the neighboring router is not compatible with that of the local router. The MC-APS control link is considered as operationally down.
What is tApsMcApsCtlLinkState?
This value reports the operational state of the Multi-Chassis APS group control link: up(0) if a valid control message was received from the neighbor within the tApsMcHoldTime window, dnSignalingFailure(1) if no control message was received in time, or dnIncompatibleNbr(2) if a message was received but the neighbor's circuit role (working/protect) is incompatible; a Single-Chassis APS group is always reported as up. An admin checks this to diagnose why Multi-Chassis protection switching isn't coordinating correctly between the two routers hosting the working and protect circuits. A value of dnIncompatibleNbr(2) tells the admin the neighbor router's circuit configuration conflicts with this router's, rather than there being a simple connectivity loss.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.29.4.1.1 snmpwalk -v2c -c public <target> TIMETRA-APS-MIB::tApsMcApsCtlLinkState
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.29.4.1.1.1 snmpget -v2c -c public <target> TIMETRA-APS-MIB::tApsMcApsCtlLinkState.1
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::tApsMcApsCtlLinkState 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 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.6527 | timetra | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3 | timetraProducts | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1 | tmnxSRMIB | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1.2 | tmnxSRObjs | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6527.3.1.2.29 | tApsMIBObjs | TIMETRA-APS-MIB |
| 1.3.6.1.4.1.6527.3.1.2.29.4 | tApsMcStatusTable | TIMETRA-APS-MIB |
| 1.3.6.1.4.1.6527.3.1.2.29.4.1 | tApsMcStatusEntry | TIMETRA-APS-MIB |
| 1.3.6.1.4.1.6527.3.1.2.29.4.1.1 | tApsMcApsCtlLinkState | TIMETRA-APS-MIB |