RFC1315-MIB

MIB Reference — IPNetwork Monitor

All MIBsRFC1315-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 symbolicOID numericTypeAccessDescription
frame_relay1.3.6.1.2.1.10.32
NTF frDLCIStatusChange1.3.6.1.2.1.10.32.0.1This 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.
frDlcmiTable1.3.6.1.2.1.10.32.1not-accessibleThe Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.
frDlcmiEntry1.3.6.1.2.1.10.32.1.1not-accessibleThe Parameters for a particular Data Link Con- nection Management Interface.
IND frDlcmiIfIndex1.3.6.1.2.1.10.32.1.1.1Indexread-onlyThe ifIndex value of the corresponding ifEn- try.
INT frDlcmiState1.3.6.1.2.1.10.32.1.1.2INTEGERread-writeThis 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 frDlcmiAddress1.3.6.1.2.1.10.32.1.1.3INTEGERread-writeThis variable states which address format is in use on the Frame Relay interface.
INT frDlcmiAddressLen1.3.6.1.2.1.10.32.1.1.4INTEGERread-writeThis 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 frDlcmiPollingInterval1.3.6.1.2.1.10.32.1.1.5INTEGERread-writeThis is the number of seconds between succes- sive status enquiry messages.
INT frDlcmiFullEnquiryInterval1.3.6.1.2.1.10.32.1.1.6INTEGERread-writeNumber of status enquiry intervals that pass before issuance of a full status enquiry mes- sage.
INT frDlcmiErrorThreshold1.3.6.1.2.1.10.32.1.1.7INTEGERread-writeThis is the maximum number of unanswered Status Enquiries the equipment shall accept be- fore declaring the interface down.
INT frDlcmiMonitoredEvents1.3.6.1.2.1.10.32.1.1.8INTEGERread-writeThis 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 frDlcmiMaxSupportedVCs1.3.6.1.2.1.10.32.1.1.9INTEGERread-writeThe 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 frDlcmiMulticast1.3.6.1.2.1.10.32.1.1.10INTEGERread-writeThis indicates whether the Frame Relay inter- face is using a multicast service.
frCircuitTable1.3.6.1.2.1.10.32.2not-accessibleA table containing information about specific Data Link Connection Identifiers and corresponding virtual circuits.
frCircuitEntry1.3.6.1.2.1.10.32.2.1not-accessibleThe information regarding a single Data Link Connection Identifier.
IND frCircuitIfIndex1.3.6.1.2.1.10.32.2.1.1Indexread-onlyThe ifIndex Value of the ifEntry this virtual circuit is layered onto.
DLC frCircuitDlci1.3.6.1.2.1.10.32.2.1.2DLCIread-onlyThe Data Link Connection Identifier for this virtual circuit.
INT frCircuitState1.3.6.1.2.1.10.32.2.1.3INTEGERread-writeIndicates 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 frCircuitReceivedFECNs1.3.6.1.2.1.10.32.2.1.4Counterread-onlyNumber of frames received from the network in- dicating forward congestion since the virtual circuit was created.
CTR frCircuitReceivedBECNs1.3.6.1.2.1.10.32.2.1.5Counterread-onlyNumber of frames received from the network in- dicating backward congestion since the virtual circuit was created.
CTR frCircuitSentFrames1.3.6.1.2.1.10.32.2.1.6Counterread-onlyThe number of frames sent from this virtual circuit since it was created.
CTR frCircuitSentOctets1.3.6.1.2.1.10.32.2.1.7Counterread-onlyThe number of octets sent from this virtual circuit since it was created.
CTR frCircuitReceivedFrames1.3.6.1.2.1.10.32.2.1.8Counterread-onlyNumber of frames received over this virtual circuit since it was created.
CTR frCircuitReceivedOctets1.3.6.1.2.1.10.32.2.1.9Counterread-onlyNumber of octets received over this virtual circuit since it was created.
TIK frCircuitCreationTime1.3.6.1.2.1.10.32.2.1.10TimeTicksread-onlyThe 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 frCircuitLastTimeChange1.3.6.1.2.1.10.32.2.1.11TimeTicksread-onlyThe value of sysUpTime when last there was a change in the virtual circuit state
INT frCircuitCommittedBurst1.3.6.1.2.1.10.32.2.1.12INTEGERread-writeThis variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
INT frCircuitExcessBurst1.3.6.1.2.1.10.32.2.1.13INTEGERread-writeThis 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 frCircuitThroughput1.3.6.1.2.1.10.32.2.1.14INTEGERread-writeThroughput 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.
frErrTable1.3.6.1.2.1.10.32.3not-accessibleA table containing information about Errors on the Frame Relay interface.
frErrEntry1.3.6.1.2.1.10.32.3.1not-accessibleThe error information for a single frame relay interface.
IND frErrIfIndex1.3.6.1.2.1.10.32.3.1.1Indexread-onlyThe ifIndex Value of the corresponding ifEn- try.
INT frErrType1.3.6.1.2.1.10.32.3.1.2INTEGERread-onlyThe type of error that was last seen on this interface.
OCT frErrData1.3.6.1.2.1.10.32.3.1.3OCTET STRINGread-onlyAn 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 frErrTime1.3.6.1.2.1.10.32.3.1.4TimeTicksread-onlyThe value of sysUpTime at which the error was detected.
frame_relay_globals1.3.6.1.2.1.10.32.4
INT frTrapState1.3.6.1.2.1.10.32.4.1INTEGERread-writeThis 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.

Download RFC1315-MIB