All MIBs › RFC1315-MIB
Category: Frame Relay
Description:
Management Information Base for Frame Relay DTEs, defining objects for monitoring Frame Relay DLCMI, virtual circuits (DLCIs), and error conditions on Frame Relay interfaces.
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC-1215
| TRAP-TYPE |
From RFC1155-SMI
| Counter | |
| TimeTicks |
From RFC1213-MIB
| transmission |
What Is RFC1315-MIB?
RFC1315-MIB is the IETF standards-based Frame Relay DTE MIB (RFC 1315), a vendor-neutral module for managing Frame Relay Data Terminal Equipment. It defines objects for the Frame Relay Data Link Connection Management Interface (DLCMI) and per-virtual-circuit (DLCI) status and statistics on Frame Relay-attached interfaces. Its central monitoring purpose is fault and performance visibility into Frame Relay links: tracking DLCMI state, individual DLCI operational status (active/inactive), and error/discard counters that reveal a failed or congested permanent virtual circuit. It is closely tied to the generic IF-MIB/MIB-II interfaces group, since Frame Relay interfaces and their DLCIs are typically indexed against standard interface objects, and it was later complemented by the Frame Relay DTE/DCE MIB (RFC 2115) and related extensions. It was widely deployed on routers and Frame Relay access devices connecting to carrier Frame Relay WAN services in the 1990s and 2000s. Network engineers scripting Frame Relay polling often build against a published RFC1315-MIB OID list to map each DLCMI and per-DLCI object to its correct table position without needing the original RFC text.
IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1315-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
What Can Be Monitored
- Frame Relay DLCMI status
- per-DLCI (virtual circuit) operational state
- Frame Relay error/discard counters
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- Frame Relay-attached router/FRAD (Frame Relay Access Device)
Monitoring Examples
No object or table names were provided in the supplied data (sample_objects is empty), so specific OIDs can't be cited, but based on the documented RFC 1315 scope, an operator would poll the Frame Relay circuit table indexed by DLCI to check each virtual circuit's operational status and error/discard counts, catching a DLCI that has gone inactive or is dropping frames due to congestion.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| frame_relay | 1.3.6.1.2.1.10.32 | |||
| NTF frDLCIStatusChange | 1.3.6.1.2.1.10.32.0.1 | This trap indicates that the indicated Virtual Circuit has changed state. It has either been created or invalidated, or has toggled between the active and inactive states. | ||
| frDlcmiTable | 1.3.6.1.2.1.10.32.1 | not-accessible | The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface. | |
| frDlcmiEntry | 1.3.6.1.2.1.10.32.1.1 | not-accessible | The Parameters for a particular Data Link Con- nection Management Interface. | |
| IND frDlcmiIfIndex | 1.3.6.1.2.1.10.32.1.1.1 | Index | read-only | The ifIndex value of the corresponding ifEn- try. |
| INT frDlcmiState | 1.3.6.1.2.1.10.32.1.1.2 | INTEGER | read-write | This variable states which Data Link Connec- tion Management scheme is active (and by impli- cation, what DLCI it uses) on the Frame Relay interface. |
| INT frDlcmiAddress | 1.3.6.1.2.1.10.32.1.1.3 | INTEGER | read-write | This variable states which address format is in use on the Frame Relay interface. |
| INT frDlcmiAddressLen | 1.3.6.1.2.1.10.32.1.1.4 | INTEGER | read-write | This variable states which address length in octets. In the case of Q922 format, the length indicates the entire length of the address in- cluding the control portion. |
| INT frDlcmiPollingInterval | 1.3.6.1.2.1.10.32.1.1.5 | INTEGER | read-write | This is the number of seconds between succes- sive status enquiry messages. |
| INT frDlcmiFullEnquiryInterval | 1.3.6.1.2.1.10.32.1.1.6 | INTEGER | read-write | Number of status enquiry intervals that pass before issuance of a full status enquiry mes- sage. |
| INT frDlcmiErrorThreshold | 1.3.6.1.2.1.10.32.1.1.7 | INTEGER | read-write | This is the maximum number of unanswered Status Enquiries the equipment shall accept be- fore declaring the interface down. |
| INT frDlcmiMonitoredEvents | 1.3.6.1.2.1.10.32.1.1.8 | INTEGER | read-write | This is the number of status polling intervals over which the error threshold is counted. For example, if within 'MonitoredEvents' number of events the station receives 'ErrorThreshold' number of errors, the interface is marked as down. |
| INT frDlcmiMaxSupportedVCs | 1.3.6.1.2.1.10.32.1.1.9 | INTEGER | read-write | The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. In response to a SET, if a value less than zero or higher than the agent's maximal capability is configured, the agent should respond bad- Value |
| INT frDlcmiMulticast | 1.3.6.1.2.1.10.32.1.1.10 | INTEGER | read-write | This indicates whether the Frame Relay inter- face is using a multicast service. |
| frCircuitTable | 1.3.6.1.2.1.10.32.2 | not-accessible | A table containing information about specific Data Link Connection Identifiers and corresponding virtual circuits. | |
| frCircuitEntry | 1.3.6.1.2.1.10.32.2.1 | not-accessible | The information regarding a single Data Link Connection Identifier. | |
| IND frCircuitIfIndex | 1.3.6.1.2.1.10.32.2.1.1 | Index | read-only | The ifIndex Value of the ifEntry this virtual circuit is layered onto. |
| DLC frCircuitDlci | 1.3.6.1.2.1.10.32.2.1.2 | DLCI | read-only | The Data Link Connection Identifier for this virtual circuit. |
| INT frCircuitState | 1.3.6.1.2.1.10.32.2.1.3 | INTEGER | read-write | Indicates whether the particular virtual cir- cuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by set- ting virtual circuit state to 'active', or deleted by changing Circuit state to 'invalid'. Whether or not the row actually disappears is left to the implementation, so this object may actually read as 'invalid' for some arbitrary length of time. It is also legal to set the state of a virtual circuit to 'inactive' to temporarily disable a given circuit. |
| CTR frCircuitReceivedFECNs | 1.3.6.1.2.1.10.32.2.1.4 | Counter | read-only | Number of frames received from the network in- dicating forward congestion since the virtual circuit was created. |
| CTR frCircuitReceivedBECNs | 1.3.6.1.2.1.10.32.2.1.5 | Counter | read-only | Number of frames received from the network in- dicating backward congestion since the virtual circuit was created. |
| CTR frCircuitSentFrames | 1.3.6.1.2.1.10.32.2.1.6 | Counter | read-only | The number of frames sent from this virtual circuit since it was created. |
| CTR frCircuitSentOctets | 1.3.6.1.2.1.10.32.2.1.7 | Counter | read-only | The number of octets sent from this virtual circuit since it was created. |
| CTR frCircuitReceivedFrames | 1.3.6.1.2.1.10.32.2.1.8 | Counter | read-only | Number of frames received over this virtual circuit since it was created. |
| CTR frCircuitReceivedOctets | 1.3.6.1.2.1.10.32.2.1.9 | Counter | read-only | Number of octets received over this virtual circuit since it was created. |
| TIK frCircuitCreationTime | 1.3.6.1.2.1.10.32.2.1.10 | TimeTicks | read-only | The value of sysUpTime when the virtual cir- cuit was created, whether by the Data Link Con- nection Management Interface or by a SetRe- quest. |
| TIK frCircuitLastTimeChange | 1.3.6.1.2.1.10.32.2.1.11 | TimeTicks | read-only | The value of sysUpTime when last there was a change in the virtual circuit state |
| INT frCircuitCommittedBurst | 1.3.6.1.2.1.10.32.2.1.12 | INTEGER | read-write | This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval. |
| INT frCircuitExcessBurst | 1.3.6.1.2.1.10.32.2.1.13 | INTEGER | read-write | This variable indicates the maximum amount of uncommitted data bits that the network will at- tempt to deliver over the measurement interval. By default, if not configured when creating the entry, the Excess Information Burst Size is set to the value of ifSpeed. |
| INT frCircuitThroughput | 1.3.6.1.2.1.10.32.2.1.14 | INTEGER | read-write | Throughput is the average number of 'Frame Re- lay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement inter- val. If the configured committed burst rate and throughput are both non-zero, the measurement interval T=frCircuitCommittedBurst/frCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement in- terval T=frCircuitExcessBurst/ifSpeed. |
| frErrTable | 1.3.6.1.2.1.10.32.3 | not-accessible | A table containing information about Errors on the Frame Relay interface. | |
| frErrEntry | 1.3.6.1.2.1.10.32.3.1 | not-accessible | The error information for a single frame relay interface. | |
| IND frErrIfIndex | 1.3.6.1.2.1.10.32.3.1.1 | Index | read-only | The ifIndex Value of the corresponding ifEn- try. |
| INT frErrType | 1.3.6.1.2.1.10.32.3.1.2 | INTEGER | read-only | The type of error that was last seen on this interface. |
| OCT frErrData | 1.3.6.1.2.1.10.32.3.1.3 | OCTET STRING | read-only | An octet string containing as much of the er- ror packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all in- formation up to the PDU. |
| TIK frErrTime | 1.3.6.1.2.1.10.32.3.1.4 | TimeTicks | read-only | The value of sysUpTime at which the error was detected. |
| frame_relay_globals | 1.3.6.1.2.1.10.32.4 | |||
| INT frTrapState | 1.3.6.1.2.1.10.32.4.1 | INTEGER | read-write | This variable indicates whether the system produces the frDLCIStatusChange trap. |
RFC description
Defines Frame Relay DTE management objects per RFC 1315, including DLCMI configuration, circuit management, and error reporting.
Start monitoring vendor-neutral, standards-based Frame Relay DTE MIB, router/FRAD with Frame Relay interfaces with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.