CXAtmDxi-MIB :: atmDxiSRFailureReason

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › CXAtmDxi-MIB › atmDxiSRFailureReason

atmDxiSRFailureReason

Module: CXAtmDxi-MIB

OID (symbolic): CXAtmDxi-MIB::atmDxiSRFailureReason

OID (numeric): 1.3.6.1.4.1.495.2.1.6.58.12.1.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indicates the status of a failed connection. The value of this object is only valid between attempts to establish the route connection atmDxiSRRouteState = notConnected), and may or may not change after successive failed attempts.

Options: noFailure (1): Once a system route has been successfully connected, this value is maintained for the duration of the connection.

internalError (2): An internal error has occurred.

localAllocFailure (3): There is insufficient memory available for ATM DXI to establish this connection.

remoteAllocFailure (4): There is insufficient memory available for the destination protocol layer to establish this connection.

localNoAccess (5): This route is associated with a SAP that does not exist.

remoteNoAccess (6): This route is associated with a SAP that does not exist at the destination layer.

remotePvcDown (8): The PVC at the destination protocol layer is down.

remotePvcBusy (10): The destination associated with this route is already connected. This typically occurs when the route is a non-MPE (PVC consolidating) circuit.

localFcnFailure (11): Flow control negotiation failed.

remoteFcnFailure (12): Flow control negotiation failed at the destination protocol layer.

localDsnFailure (13): Data size negotiation failed.

remoteAliasNotFound (15): The destination alias (atmDxiSRDestAlias) does not exist.

remoteNoPvcService (16): The destination protocol layer does not support PVC service.

mpeInvalidSubref (17): The value of atmDxiSRSubRef is invalid at the destination protocol layer. (i.e., atmDxiSRSubRef is set to '0' and the destination circuit is configured for PVC consolidation).

routeStalled (18): An invalid control packet exchange has occurred during the route setup procedure. The route is temporarily stalled but will recover within 5 seconds.

What is atmDxiSRFailureReason?

When a route fails to connect (atmDxiSRRouteState = notConnected), reports why — for example localAllocFailure/remoteAllocFailure (out of memory), remotePvcDown, or remoteAliasNotFound (the destination alias doesn't exist) — narrowing down whether the problem is local, remote, or a configuration mismatch.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.495.2.1.6.58.12.1.11
snmpwalk -v2c -c public <target> CXAtmDxi-MIB::atmDxiSRFailureReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.495.2.1.6.58.12.1.11.1
snmpget -v2c -c public <target> CXAtmDxi-MIB::atmDxiSRFailureReason.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> atmDxiSRFailureReason.1

Start monitoring CX Memotec WAN access gateway (ATM-DXI) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CXAtmDxi-MIB::atmDxiSRFailureReason OID value, configure state conditions and alerts, and monitor any CX Memotec WAN access gateway (ATM-DXI) 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.495memotecMEMOTEC-SMI
1.3.6.1.4.1.495.2memotecProductsMEMOTEC-SMI
1.3.6.1.4.1.495.2.1cxProductMEMOTEC-SMI
1.3.6.1.4.1.495.2.1.6cxApplicationCXProduct-SMI
1.3.6.1.4.1.495.2.1.6.58cxAtmDxiCXProduct-SMI
Numeric OIDNameModule
1.3.6.1.4.1.495.2.1.6.58.12atmDxiSysRouteTableCXAtmDxi-MIB
1.3.6.1.4.1.495.2.1.6.58.12.1atmDxiSysRouteEntryCXAtmDxi-MIB
1.3.6.1.4.1.495.2.1.6.58.12.1.11atmDxiSRFailureReasonCXAtmDxi-MIB