All MIBs › CXFrameRelayInterfaceModule-MIB › frimSRClearStatus
frimSRClearStatus
Module: CXFrameRelayInterfaceModule-MIB
OID (symbolic): CXFrameRelayInterfaceModule-MIB::frimSRClearStatus
OID (numeric): 1.3.6.1.4.1.495.2.1.6.2.6.1.16
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Indicates the reason for a connection failure on the system route. This status is meaningful only between attempts to establish a system route. Successive failed attempts may or may not change the displayed value.
Options: noFailure (1): no failure (connection has occurred)
internalError (2): internal system error
localAllocFailure (3): not enough memory in local device to establish system route at current time
remoteAllocFailure (4): not enough memory in remote device to establish system route at current time
localNoAccess (5): PVC in local device not configured
remoteNoAccess (6): PVC in remote dcevice not configured
localPvcDown (7): PVC in local device reported down
remotePvcDown (8): PVC in remote device reported down
localPvcBusy (9): PVC in local device is busy (PVC is SPE or PVC is MPE but 'frimSRSubRef' is in use)
remotePvcBusy (10): PVC in remote device is busy (PVC is SPE or PVC is MPE but 'frimSRSubRef' is in use)
localFcnFailure (11): local device does not support flow control type
remoteFcnFailure (12): remote device does not support flow control type
localDsnFailure (13): local device could not negotiate size of data unit because remote's maximum data unit was zero
localRefInUse (14): 'frimSRSubRef' in use in local device
remoteAliasNotFound (15): no PVC in the local device has this destination alias
remoteNoPvcService (16): remote device does not support PVCs
Default Value: none
What is frimSRClearStatus?
Reports the specific reason (from 16 enumerated causes such as localPvcDown, remoteAllocFailure, or localRefInUse) that a system route connection attempt failed, meaningful only between connection attempts. An admin reads this value when frimSRRouteStatus shows notConnected to diagnose why the route won't come up.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.495.2.1.6.2.6.1.16 snmpwalk -v2c -c public <target> CXFrameRelayInterfaceModule-MIB::frimSRClearStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.495.2.1.6.2.6.1.16.1 snmpget -v2c -c public <target> CXFrameRelayInterfaceModule-MIB::frimSRClearStatus.1
Start monitoring Legacy Crosscomm CX900/CX1000 router (Frame Relay SAP) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CXFrameRelayInterfaceModule-MIB::frimSRClearStatus OID value, configure state conditions and alerts, and monitor any Legacy Crosscomm CX900/CX1000 router (Frame Relay SAP) 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.2 | cxFrameRelayInterfaceModule | CXProduct-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.495.2.1.6.2.6 | frimSRTable | CXFrameRelayInterfaceModule-MIB |
| 1.3.6.1.4.1.495.2.1.6.2.6.1 | frimSREntry | CXFrameRelayInterfaceModule-MIB |
| 1.3.6.1.4.1.495.2.1.6.2.6.1.16 | frimSRClearStatus | CXFrameRelayInterfaceModule-MIB |