MIBs Depot

FRAME-RELAY-DTE-MIB

Registered at
1.3.6.1.2.1.10.32
Last updated
1997-05-01 02:29
Organization
IETF IPLPDN Working Group
Revisions
1997-05-01 02:29, 1992-04-01 00:00
Namespace
standard
Source file
FRAME-RELAY-DTE-MIB
Digest
sha256:8b7c828e7295d6a5a9e6b2c5a31a8a308196d239f29634100e8b0b7d58a28e18

Description

The MIB module to describe the use of a Frame Relay interface by a DTE.

Contact

Caralyn Brown Postal: Cadia Networks, Inc. 1 Corporate Drive Andover, Massachusetts 01810 Tel: +1 508 689 2400 x133 E-Mail: cbrown@cadia.com Fred Baker Postal: Cisco Systems 519 Lado Drive Santa Barbara, California 93111 Tel: +1 408 526 425 E-Mail: fred@cisco.com

Imports

FromSymbols
IF-MIBInterfaceIndex
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter32, Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso, transmission
SNMPv2-TCDisplayString, RowStatus, TEXTUAL-CONVENTION, TimeStamp

Imported by

1 module(s) in this corpus import this one.

Load order

Every file a consumer needs in order to load this module, dependencies first.

FRAME-RELAY-DTE-MIB
IANAifType-MIB
IF-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC

Textual conventions

NameOIDSyntaxAccessStatus
DLCI
TEXTUAL-CONVENTION
The range of DLCI values. Note that this varies by interface configuration; normally, interfaces may use 0..1023, but may be configured to use ranges as large as 0..2^23.
current

Objects

NameOIDSyntaxAccessStatus
frameRelayTraps
OBJECT-IDENTITY
1.3.6.1.2.1.10.32.0
frDlcmiTable
OBJECT-TYPE
The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.
1.3.6.1.2.1.10.32.1not-accessiblecurrent
frDlcmiEntry
OBJECT-TYPE
The Parameters for a particular Data Link Connection Management Interface.
1.3.6.1.2.1.10.32.1.1not-accessiblecurrent
frDlcmiIfIndex
OBJECT-TYPE
The ifIndex value of the corresponding ifEntry.
1.3.6.1.2.1.10.32.1.1.1InterfaceIndexread-onlycurrent
frDlcmiState
OBJECT-TYPE
This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.
1.3.6.1.2.1.10.32.1.1.2INTEGER {noLmiConfigured(1), lmiRev1(2), ansiT1617D(3), ansiT1617B(4), itut933A(5), ansiT1617D1994(6)}read-createcurrent
frDlcmiAddress
OBJECT-TYPE
This variable states which address format is in use on the Frame Relay interface.
1.3.6.1.2.1.10.32.1.1.3INTEGER {q921(1), q922March90(2), q922November90(3), q922(4)}read-createcurrent
frDlcmiAddressLen
OBJECT-TYPE
This variable states the address length in octets. In the case of Q922 format, the length indicates the entire length of the address including the control portion.
1.3.6.1.2.1.10.32.1.1.4INTEGER {twoOctets(2), threeOctets(3), fourOctets(4)}read-createcurrent
frDlcmiPollingInterval
OBJECT-TYPE
This is the number of seconds between successive status enquiry messages.
1.3.6.1.2.1.10.32.1.1.5Integer32 (5..30)read-createcurrent
frDlcmiFullEnquiryInterval
OBJECT-TYPE
Number of status enquiry intervals that pass before issuance of a full status enquiry message.
1.3.6.1.2.1.10.32.1.1.6Integer32 (1..255)read-createcurrent
frDlcmiErrorThreshold
OBJECT-TYPE
This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down.
1.3.6.1.2.1.10.32.1.1.7Integer32 (1..10)read-createcurrent
frDlcmiMonitoredEvents
OBJECT-TYPE
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.
1.3.6.1.2.1.10.32.1.1.8Integer32 (1..10)read-createcurrent
frDlcmiMaxSupportedVCs
OBJECT-TYPE
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 badValue
1.3.6.1.2.1.10.32.1.1.9DLCIread-createcurrent
frDlcmiMulticast
OBJECT-TYPE
This indicates whether the Frame Relay interface is using a multicast service.
1.3.6.1.2.1.10.32.1.1.10INTEGER {nonBroadcast(1), broadcast(2)}read-createcurrent
frDlcmiStatus
OBJECT-TYPE
This indicates the status of the Frame Relay interface as determined by the performance of the dlcmi. If no dlcmi is running, the Frame Relay interface will stay in the running state indefinitely.
1.3.6.1.2.1.10.32.1.1.11INTEGER {running(1), fault(2), initializing(3)}read-onlycurrent
frDlcmiRowStatus
OBJECT-TYPE
SNMP Version 2 Row Status Variable. Writable objects in the table may be written in any RowStatus state.
1.3.6.1.2.1.10.32.1.1.12RowStatusread-createcurrent
frCircuitTable
OBJECT-TYPE
A table containing information about specific Data Link Connections (DLC) or virtual circuits.
1.3.6.1.2.1.10.32.2not-accessiblecurrent
frCircuitEntry
OBJECT-TYPE
The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in frCircuitCreationTime.
1.3.6.1.2.1.10.32.2.1not-accessiblecurrent
frCircuitIfIndex
OBJECT-TYPE
The ifIndex Value of the ifEntry this virtual circuit is layered onto.
1.3.6.1.2.1.10.32.2.1.1InterfaceIndexread-onlycurrent
frCircuitDlci
OBJECT-TYPE
The Data Link Connection Identifier for this virtual circuit.
1.3.6.1.2.1.10.32.2.1.2DLCIread-onlycurrent
frCircuitState
OBJECT-TYPE
Indicates whether the particular virtual circuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by setting 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. The use of 'invalid' is deprecated in this SNMP Version 2 MIB, in favor of frCircuitRowStatus.
1.3.6.1.2.1.10.32.2.1.3INTEGER {invalid(1), active(2), inactive(3)}read-createcurrent
frCircuitReceivedFECNs
OBJECT-TYPE
Number of frames received from the network indicating forward congestion since the virtual circuit was created. This occurs when the remote DTE sets the FECN flag, or when a switch in the network enqueues the frame to a trunk whose transmission queue is congested.
1.3.6.1.2.1.10.32.2.1.4Counter32read-onlycurrent
frCircuitReceivedBECNs
OBJECT-TYPE
Number of frames received from the network indicating backward congestion since the virtual circuit was created. This occurs when the remote DTE sets the BECN flag, or when a switch in the network receives the frame from a trunk whose transmission queue is congested.
1.3.6.1.2.1.10.32.2.1.5Counter32read-onlycurrent
frCircuitSentFrames
OBJECT-TYPE
The number of frames sent from this virtual circuit since it was created.
1.3.6.1.2.1.10.32.2.1.6Counter32read-onlycurrent
frCircuitSentOctets
OBJECT-TYPE
The number of octets sent from this virtual circuit since it was created. Octets counted are the full frame relay header and the payload, but do not include the flag characters or CRC.
1.3.6.1.2.1.10.32.2.1.7Counter32read-onlycurrent
frCircuitReceivedFrames
OBJECT-TYPE
Number of frames received over this virtual circuit since it was created.
1.3.6.1.2.1.10.32.2.1.8Counter32read-onlycurrent
frCircuitReceivedOctets
OBJECT-TYPE
Number of octets received over this virtual circuit since it was created. Octets counted include the full frame relay header, but do not include the flag characters or the CRC.
1.3.6.1.2.1.10.32.2.1.9Counter32read-onlycurrent
frCircuitCreationTime
OBJECT-TYPE
The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.
1.3.6.1.2.1.10.32.2.1.10TimeStampread-onlycurrent
frCircuitLastTimeChange
OBJECT-TYPE
The value of sysUpTime when last there was a change in the virtual circuit state
1.3.6.1.2.1.10.32.2.1.11TimeStampread-onlycurrent
frCircuitCommittedBurst
OBJECT-TYPE
This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
1.3.6.1.2.1.10.32.2.1.12Integer32 (0..2147483647)read-createcurrent
frCircuitExcessBurst
OBJECT-TYPE
This variable indicates the maximum amount of uncommitted data bits that the network will attempt 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.
1.3.6.1.2.1.10.32.2.1.13Integer32 (0..2147483647)read-createcurrent
frCircuitThroughput
OBJECT-TYPE
Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. If the configured committed burst rate and throughput are both non-zero, the measurement interval, T, is T=frCircuitCommittedBurst/frCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T=frCircuitExcessBurst/ifSpeed.
1.3.6.1.2.1.10.32.2.1.14Integer32 (0..2147483647)read-createcurrent
frCircuitMulticast
OBJECT-TYPE
This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to
1.3.6.1.2.1.10.32.2.1.15INTEGER {unicast(1), oneWay(2), twoWay(3), nWay(4)}read-createcurrent
frCircuitType
OBJECT-TYPE
Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.
1.3.6.1.2.1.10.32.2.1.16INTEGER {static(1), dynamic(2)}read-onlycurrent
frCircuitDiscards
OBJECT-TYPE
The number of inbound frames dropped because of format errors, or because the VC is inactive.
1.3.6.1.2.1.10.32.2.1.17Counter32read-onlycurrent
frCircuitReceivedDEs
OBJECT-TYPE
Number of frames received from the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the remote DTE sets the DE flag, or when in remote DTE's switch detects that the frame was received as Excess Burst data.
1.3.6.1.2.1.10.32.2.1.18Counter32read-onlycurrent
frCircuitSentDEs
OBJECT-TYPE
Number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the local DTE sets the DE flag, indicating that during Network congestion situations those frames should be discarded in preference of other frames sent without the DE bit set.
1.3.6.1.2.1.10.32.2.1.19Counter32read-onlycurrent
frCircuitLogicalIfIndex
OBJECT-TYPE
Normally the same value as frDlcmiIfIndex, but different when an implementation associates a virtual ifEntry with a DLC or set of DLCs in order to associate higher layer objects such as the ipAddrEntry with a subset of the virtual circuits on a Frame Relay interface. The type of such ifEntries is defined by the higher layer object; for example, if PPP/Frame Relay is implemented, the ifType of this ifEntry would be PPP. If it is not so defined, as would be the case with an ipAddrEntry, it should be of type Other.
1.3.6.1.2.1.10.32.2.1.20InterfaceIndexread-createcurrent
frCircuitRowStatus
OBJECT-TYPE
This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.
1.3.6.1.2.1.10.32.2.1.21RowStatusread-createcurrent
frErrTable
OBJECT-TYPE
A table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.
1.3.6.1.2.1.10.32.3not-accessiblecurrent
frErrEntry
OBJECT-TYPE
The error information for a single frame relay interface.
1.3.6.1.2.1.10.32.3.1not-accessiblecurrent
frErrIfIndex
OBJECT-TYPE
The ifIndex Value of the corresponding ifEntry.
1.3.6.1.2.1.10.32.3.1.1InterfaceIndexread-onlycurrent
frErrType
OBJECT-TYPE
The type of error that was last seen on this interface: receiveShort: frame was not long enough to allow demultiplexing - the address field was incomplete, or for virtual circuits using Multiprotocol over Frame Relay, the protocol identifier was missing or incomplete. receiveLong: frame exceeded maximum length configured for this interface. illegalAddress: address field did not match configured format. unknownAddress: frame received on a virtual circuit which was not active or administratively disabled. dlcmiProtoErr: unspecified error occurred when attempting to interpret link maintenance frame. dlcmiUnknownIE: link maintenance frame contained an Information Element type which is not valid for the configured link maintenance protocol. dlcmiSequenceErr: link maintenance frame contained a sequence number other than the expected value. dlcmiUnknownRpt: link maintenance frame contained a Report Type Information Element whose value was not valid for the configured link maintenance protocol. noErrorSinceReset: no errors have been detected since the last cold start or warm start.
1.3.6.1.2.1.10.32.3.1.2INTEGER {unknownError(1), receiveShort(2), receiveLong(3), illegalAddress(4), unknownAddress(5), dlcmiProtoErr(6), dlcmiUnknownIE(7), dlcmiSequenceErr(8), dlcmiUnknownRpt(9), noErrorSinceReset(10)}read-onlycurrent
frErrData
OBJECT-TYPE
An octet string containing as much of the error 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 header and demultiplexing information.
1.3.6.1.2.1.10.32.3.1.3OCTET STRING (SIZE(1..1600))read-onlycurrent
frErrTime
OBJECT-TYPE
The value of sysUpTime at which the error was detected.
1.3.6.1.2.1.10.32.3.1.4TimeStampread-onlycurrent
frErrFaults
OBJECT-TYPE
The number of times the interface has gone down since it was initialized.
1.3.6.1.2.1.10.32.3.1.5Counter32read-onlycurrent
frErrFaultTime
OBJECT-TYPE
The value of sysUpTime at the time when the interface was taken down due to excessive errors. Excessive errors is defined as the time when a DLCMI exceeds the frDlcmiErrorThreshold number of errors within frDlcmiMonitoredEvents. See FrDlcmiEntry for further details.
1.3.6.1.2.1.10.32.3.1.6TimeStampread-onlycurrent
frameRelayTrapControl
OBJECT-IDENTITY
1.3.6.1.2.1.10.32.4
frTrapState
OBJECT-TYPE
This variable indicates whether the system produces the frDLCIStatusChange trap.
1.3.6.1.2.1.10.32.4.1INTEGER {enabled(1), disabled(2)}read-writecurrent
frTrapMaxRate
OBJECT-TYPE
This variable indicates the number of milliseconds that must elapse between trap emissions. If events occur more rapidly, the impementation may simply fail to trap, or may queue traps until an appropriate time.
1.3.6.1.2.1.10.32.4.2Integer32 (0..3600000)read-writecurrent
frConformance
OBJECT-IDENTITY
1.3.6.1.2.1.10.32.6
frGroups
OBJECT-IDENTITY
1.3.6.1.2.1.10.32.6.1
frCompliances
OBJECT-IDENTITY
1.3.6.1.2.1.10.32.6.2

Notifications

NameOIDStatus
frDLCIStatusChange
NOTIFICATION-TYPE
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. If, however, the reason for the state change is due to the DLCMI going down, per-DLCI traps should not be generated.
1.3.6.1.2.1.10.32.0.1current

Conformance

NameOIDStatus
frPortGroup
OBJECT-GROUP
The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface.
1.3.6.1.2.1.10.32.6.1.1current
frCircuitGroup
OBJECT-GROUP
The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface.
1.3.6.1.2.1.10.32.6.1.2current
frTrapGroup
OBJECT-GROUP
The objects necessary to control a Frame Relay Interface's notification messages.
1.3.6.1.2.1.10.32.6.1.3current
frErrGroup
OBJECT-GROUP
Objects designed to assist in debugging Frame Relay Interfaces.
1.3.6.1.2.1.10.32.6.1.4current
frNotificationGroup
NOTIFICATION-GROUP
Traps which may be used to enhance event driven management of the interface.
1.3.6.1.2.1.10.32.6.1.5current
frPortGroup0
OBJECT-GROUP
The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface from RFC 1315.
1.3.6.1.2.1.10.32.6.1.6current
frCircuitGroup0
OBJECT-GROUP
The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface from RFC 1315.
1.3.6.1.2.1.10.32.6.1.7current
frErrGroup0
OBJECT-GROUP
Objects designed to assist in debugging Frame Relay Interfaces from RFC 1315.
1.3.6.1.2.1.10.32.6.1.8current
frTrapGroup0
OBJECT-GROUP
The objects necessary to control a Frame Relay Interface's notification messages from RFC 1315.
1.3.6.1.2.1.10.32.6.1.9current
frCompliance
MODULE-COMPLIANCE
The compliance statement
1.3.6.1.2.1.10.32.6.2.1current
frCompliance0
MODULE-COMPLIANCE
The compliance statement for objects and the trap defined in RFC 1315.
1.3.6.1.2.1.10.32.6.2.2current