All MIBs › CISCO-WAN-AXIPOP-MIB › axisImaGroupFeState
axisImaGroupFeState
Module: CISCO-WAN-AXIPOP-MIB
OID (symbolic): CISCO-WAN-AXIPOP-MIB::axisImaGroupFeState
OID (numeric): 1.3.6.1.4.1.351.110.5.2.1.4.1.1.13
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The current operational state of the far-end IMA group state machine
1) notConfigured : The Group doesn't exist.This is the GSM initial state. 2) startUp : On UM configuring the IMA group,GSM comes to this state. 3) startUpAck : On getting the Start-up-ack from FE(this info from received ICP cell. i.e. FE accepting the proposed group parameters by this END.), GSM goes to this state. 4) configAbortUnsupportedM : This state is entered when FE is not accepting the parameter M. 5) configAbortIncompatibleSymmetry : When Group symmetry is not supported by the FE,this group is entered. 6) configAbortOther : If any of the other group parameters are not supported by the FE,then this state is entered. 7) insufficientLinks : On getting one of the following events from FE, when GSM is in startUpAck state,GSM moves to insufficientLinks state. evens : 1) Start-up-ack 2) insufficient links 3) Blocked or operational 8) blocked : For to maintenance purpose,if group is blcoked (inhibited by UM),GSM goes to this state. 9) operational : When the group has sufficient links in both Tx and Rx directions GSM goes to this state.
What is axisImaGroupFeState?
This read-only enumerated value reports the current state of the far-end (remote) IMA group's state machine (GSM), progressing through stages such as notConfigured, startUp, and startUpAck as the group is negotiated, or landing in an abort/failure state like configAbortUnsupportedM if the remote group's M-value or symmetry settings are incompatible. An admin uses this to see exactly where the far end's IMA negotiation stalled or failed, which is critical since IMA setup requires agreement between both ends. For example, if the far end is stuck in startUp rather than reaching operational, the admin knows the near end has configured the group but the remote side has not yet acknowledged it.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.1.4.1.1.13 snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::axisImaGroupFeState
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.1.4.1.1.13.1 snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::axisImaGroupFeState.1
Start monitoring Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-AXIPOP-MIB::axisImaGroupFeState OID value, configure state conditions and alerts, and monitor any Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) from a single console.
OID Breakdown
Upper-level ancestors (11 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.351 | stratacom | CISCOWAN-SMI |
| 1.3.6.1.4.1.351.110 | basis | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5 | basisServices | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.2 | atm | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.2.1 | ausmPort | BASIS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.5.2.1.4 | ausmPortStateImaGrp | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.2.1.4.1 | ausmPortStateImaGrpTable | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.2.1.4.1.1 | ausmPortStateImaGrpEntry | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.2.1.4.1.1.13 | axisImaGroupFeState | CISCO-WAN-AXIPOP-MIB |