All MIBs › CXFrameRelayATMIWF-MIB › frpAtmNIFailureReason
frpAtmNIFailureReason
Module: CXFrameRelayATMIWF-MIB
OID (symbolic): CXFrameRelayATMIWF-MIB::frpAtmNIFailureReason
OID (numeric): 1.3.6.1.4.1.495.2.1.6.3.52.1.3
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 only between attempts to establish the connection, 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.
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 frpAtmNIFailureReason?
This object reports the specific reason a Frame Relay to ATM Network Interworking connection attempt failed, distinguishing causes such as insufficient local or remote memory allocation, a missing SAP, a down or busy remote PVC, failed flow-control or data-size negotiation, or a stalled route setup. An admin checks this whenever frpAtmNISapState isn't reaching connected(4), to know exactly which layer of the connection setup is failing. For example, remotePvcDown(8) tells the admin the problem is on the far end's PVC rather than local configuration.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.495.2.1.6.3.52.1.3 snmpwalk -v2c -c public <target> CXFrameRelayATMIWF-MIB::frpAtmNIFailureReason
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.495.2.1.6.3.52.1.3.1 snmpget -v2c -c public <target> CXFrameRelayATMIWF-MIB::frpAtmNIFailureReason.1
Start monitoring Legacy Crosscomm CX900/CX1000 router (Frame Relay/ATM interworking) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CXFrameRelayATMIWF-MIB::frpAtmNIFailureReason OID value, configure state conditions and alerts, and monitor any Legacy Crosscomm CX900/CX1000 router (Frame Relay/ATM interworking) 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.495 | memotec | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2 | memotecProducts | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2.1 | cxProduct | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2.1.6 | cxApplication | CXProduct-SMI |
| 1.3.6.1.4.1.495.2.1.6.3 | cxFrameRelay | CXProduct-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.495.2.1.6.3.52 | frpAtmNISapTable | CXFrameRelayATMIWF-MIB |
| 1.3.6.1.4.1.495.2.1.6.3.52.1 | frpAtmNISapEntry | CXFrameRelayATMIWF-MIB |
| 1.3.6.1.4.1.495.2.1.6.3.52.1.3 | frpAtmNIFailureReason | CXFrameRelayATMIWF-MIB |