rfc-1315

Management Information Base for Frame Relay DTEs

C. Brown, F. Baker, C. Carvalho
date1992-04 streamIETF areartg wgiplpdn statusPROPOSED STANDARD pages19 canonicalhttps://www.rfc-editor.org/rfc/rfc1315 doi10.17487/RFC1315
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Frame Relay. [STANDARDS-TRACK]

obsoleted by

Extracted elements (27)

design-rationale §3.1

Frame Relay is modeled as a multi-access media rather than a group of point-to-point connections. This treats the physical connection as a single interface with many virtual destinations, enabling a network manager to group all virtual circuits with their corresponding physical connection for simpler diagnostics.

snmp, yang

design-rationale §3.2

Textual conventions Index (range 1..ifNumber) and DLCI (range 0..DLCINumber) are introduced purely for readability and have no effect on syntax or semantics of managed objects. Objects defined using these types are always encoded as their underlying primitive types, requiring no changes to SMI or SNMP.

snmp

interoperability-note §3.3

Each ifEntry in the standard MIB Interface Table with an ifType of Frame Relay represents a Q.922 interface. Zero or more virtual circuit entries in frCircuitTable are layered onto this ifEntry and are correlated via the Index textual convention (range 1..ifNumber).

snmp

normative-requirement §4.3 MUST

frErrData MUST contain at minimum the Q.922 Address of the erroneous frame or as much as was delivered; it is desirable to include all information up to the PDU.

snmp

normative-requirement §4.1 SHOULD

If a SET on frDlcmiMaxSupportedVCs specifies a value less than zero or higher than the agent's maximal capability, the agent SHOULD respond with badValue.

snmp

protocol-element §4.2

frCircuitCommittedBurst (default 0, meaning no commitment) indicates the maximum data in bits the network agrees to transfer under normal conditions during the measurement interval, per T1.617-1991 Section 6.5.19.

snmp, qos

protocol-element §4.2

frCircuitCreationTime and frCircuitLastTimeChange are TimeTicks objects recording the sysUpTime at which the virtual circuit was created (via DLCMI or SetRequest) and at which its state last changed, respectively.

snmp

protocol-element §4.2

frCircuitExcessBurst indicates the maximum uncommitted data bits the network will attempt to deliver over the measurement interval. If not configured at entry creation, it defaults to the value of ifSpeed.

snmp, qos

protocol-element §4.2

frCircuitReceivedBECNs is a Counter of frames received with the Backward Explicit Congestion Notification bit set since the virtual circuit was created, as defined in T1.618-1991 Section 3.3.4.

snmp, congestion

protocol-element §4.2

frCircuitReceivedFECNs is a Counter of frames received from the network with the Forward Explicit Congestion Notification bit set since the virtual circuit was created, as defined in T1.618-1991 Section 3.3.3.

snmp, congestion

protocol-element §4.2

frCircuitTable (frame-relay 2) contains information about individual DLCIs and their corresponding virtual circuits, indexed by frCircuitIfIndex and frCircuitDlci. Each entry tracks state, congestion counters, traffic statistics, timestamps, and traffic-contract parameters.

snmp

protocol-element §4.2

frCircuitThroughput (default 0, meaning no commitment) is the average Frame Relay Information Field bits per second across the UNI. The measurement interval T is derived as frCircuitCommittedBurst/frCircuitThroughput when both are non-zero, or frCircuitExcessBurst/ifSpeed when both are zero.

snmp, qos

protocol-element §4

frDLCIStatusChange is an enterprise trap (enterprise frame-relay, trap number 1) carrying frCircuitIfIndex, frCircuitDlci, and frCircuitState. It fires when a virtual circuit is created, invalidated, or transitions between active and inactive states, serving as the Frame Relay analogue to the SNMP Link Up/Link Down traps.

snmp

protocol-element §4.1

frDlcmiAddress specifies the Q.922 address format in use: q921(1) with 13-bit DLCI, q922March90(2) with 11-bit DLCI, q922November90(3) with 10-bit DLCI, or q922(4) for the final standard. This determines how DLCIs are encoded on the interface.

snmp

protocol-element §4.1

frDlcmiAddressLen indicates the address field length in octets: two-octets(2), three-octets(3), or four-octets(4). For Q.922 format, the length covers the entire address including the control portion.

snmp

protocol-element §4.1

frDlcmiErrorThreshold (range 1..10, default 3) is the maximum number of unanswered Status Enquiries the equipment accepts before declaring the interface down, corresponding to ANSI T1.617-1991 Counter N392.

snmp

protocol-element §4.1

frDlcmiFullEnquiryInterval (range 1..255, default 6) is the number of status enquiry intervals that must pass before a full status enquiry message is issued, corresponding to ANSI T1.617-1991 Counter N391.

snmp

protocol-element §4.1

frDlcmiMonitoredEvents (range 1..10, default 4) is the number of status polling intervals over which the error threshold is counted. If ErrorThreshold errors occur within MonitoredEvents intervals, the interface is marked down; corresponds to ANSI T1.617-1991 Counter N393.

snmp

protocol-element §4.1

frDlcmiMulticast indicates whether the Frame Relay interface uses a multicast service: nonBroadcast(1) or broadcast(2).

snmp, multicast

protocol-element §4.1

frDlcmiPollingInterval (range 5..30 seconds, default 10) is the interval between successive status enquiry messages, corresponding to ANSI T1.617-1991 Timer T391.

snmp

protocol-element §4.1

frDlcmiState selects the active DLCI Management scheme on a Frame Relay interface: noLmiConfigured(1), lmiRev1(2), ansiT1-617-D(3), or ansiT1-617-B(4). The chosen scheme also implies which DLCI is used for management traffic.

snmp

protocol-element §4.1

frDlcmiTable (frame-relay 1) contains per-interface parameters for the Data Link Connection Management Interface, indexed by frDlcmiIfIndex. It configures LMI scheme, address format, polling timers, error thresholds, maximum VCs, and multicast capability.

snmp

protocol-element §4.3

frErrTable (frame-relay 3) contains per-interface error information, indexed by frErrIfIndex. Each entry records the type of the last error, up to a full copy of the erroneous frame, and the sysUpTime at detection.

snmp

protocol-element §4.3

frErrType enumerates the last error seen on a Frame Relay interface: unknownError(1), receiveShort(2), receiveLong(3), illegalDLCI(4), unknownDLCI(5), dlcmiProtoErr(6), dlcmiUnknownIE(7), dlcmiSequenceErr(8), dlcmiUnknownRpt(9), noErrorSinceReset(10).

snmp

protocol-element §4

frTrapState (frame-relay-globals 1, default disabled) is a read-write object that controls whether the system generates the frDLCIStatusChange trap. Values are enabled(1) and disabled(2).

snmp

security-consideration §7

Security issues are explicitly not discussed in this memo. The MIB includes read-write objects (DLCMI configuration, circuit state, traffic contract parameters) accessible via SNMP, but no access-control or authentication guidance is provided.

snmp, security

state-machine §4.2

frCircuitState defines three states for a virtual circuit: active(2), inactive(3), and invalid(1). In the absence of a DLCMI, rows may be created by setting state to active and deleted by setting state to invalid; setting inactive temporarily disables a circuit without removing its row.

snmp