CISCO-WAN-AXIPOP-MIB :: imaPortState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBimaPortState

imaPortState

Module: CISCO-WAN-AXIPOP-MIB

OID (symbolic): CISCO-WAN-AXIPOP-MIB::imaPortState

OID (numeric): 1.3.6.1.4.1.351.110.5.2.1.4.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indicates the state of the IMA port. The following error conditions are currently reported: 1 - Unconfigured state 2 - Active state 3 - Bandwidth changed due to addition/deletion of links. The addition/deletion can be triggered by either end 4 - FailedDueToACPTimeout (indicates that a timeout occurred due to non-arrival of an ACP cell) 5 - FailedDueToMajorAlarmOnIMAGroup (issued when the bandwidth of an IMA group falls below a certain threshold due to loss of links from an IMA group) 6 - FailedDueToImaSigFailure (this indicates configuration mismatch or non-arrival of LCP cells during set up of an IMA group) 7 - FailedDueToBadDiffDelay (indicates that the differential delay exceeded the maximum threshold) 8 - FailedDueToArbConflict (indicates that the IMA-ID could not be resolved between the 2 ends of the IMA pipe) 9 - Receiving Local OAM AIS from peer IMA node (valid only for network modules) 10- Receiving LOAM RDI from peer IMA node (valud only for network modules) 20- Failed due to ILMI signalling failure This object does not have any default value

What is imaPortState?

This read-only enumerated value reports the current operating state of an IMA port, distinguishing a healthy active port from ones that are unconfigured, have had bandwidth change due to link addition/deletion, or have failed for a specific reason such as an ACP cell timeout or a major alarm from insufficient bandwidth. An administrator uses this field as the primary at-a-glance health indicator for the IMA port, since the specific failure code (e.g., failedDueToAcpTimeout vs. failedDueToBadDiffDelay) tells them whether to investigate cell timing, differential delay between links, or configuration mismatches. For example, seeing imaPortState report failedDueToMajorAlmonImaGrp tells the admin the group's usable bandwidth has dropped below the configured minimum-links threshold, likely because one or more physical links failed.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.1.4.1.1.2
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::imaPortState

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.2.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::imaPortState.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::imaPortState 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 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.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.2atmBASIS-MIB
1.3.6.1.4.1.351.110.5.2.1ausmPortBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.2.1.4ausmPortStateImaGrpCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.2.1.4.1ausmPortStateImaGrpTableCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.2.1.4.1.1ausmPortStateImaGrpEntryCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.2.1.4.1.1.2imaPortStateCISCO-WAN-AXIPOP-MIB