REDSTONE-FRAME-RELAY-MIB

All MIBs › REDSTONE-FRAME-RELAY-MIB

Organization: Redstone Communications, Inc.

Last Updated: 1999-06-01

Category: DSL and Broadband Access

Description: Manages Frame Relay interface configuration, DLCI parameters, and performance on Redstone routers.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is REDSTONE-FRAME-RELAY-MIB?

REDSTONE-FRAME-RELAY-MIB is a Redstone Communications enterprise MIB for their router products that manages Frame Relay interface configuration and DLCI (Data Link Connection Identifier) parameters via the standard DLCMI (Data Link Connection Management Interface) model. It exposes per-interface Frame Relay signaling state, addressing, polling/enquiry intervals, error thresholds, monitored event counts, and the maximum number of supported virtual circuits. Its monitoring focus is on WAN link software/protocol status rather than physical chassis hardware: an operator tracks whether the Frame Relay DLCMI signaling state is up, whether polling/keepalive intervals are healthy, and whether error thresholds are being exceeded, which reveals WAN circuit instability or provider-side signaling problems. It follows the general structure of the standard Frame Relay DTE/DCE interface management model though implemented as a Redstone-specific enterprise MIB rather than the IETF Frame Relay DTE MIB itself. It would have been deployed on Redstone Communications routers providing Frame Relay WAN connectivity in enterprise or carrier access networks. Engineers can download the REDSTONE-FRAME-RELAY-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in REDSTONE-FRAME-RELAY-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.

Supported Devices

Redstone Communications routers with Frame Relay WAN interfaces

Monitoring Examples

An operator would poll rsFrDlcmiTable/rsFrDlcmiEntry, keyed by rsFrDlcmiIfIndex, to check rsFrDlcmiState for signaling status and rsFrDlcmiPollingInterval/rsFrDlcmiFullEnquiryInterval for keepalive timing. A rising rsFrDlcmiErrorThreshold breach or unexpected changes in rsFrDlcmiMonitoredEvents would indicate DLCMI signaling instability on that interface, potentially due to a carrier-side issue. rsFrDlcmiMaxSupportedVCs helps confirm whether the interface is nearing its virtual-circuit capacity, useful when planning additional DLCIs.

What Can Be Monitored

Frame Relay DLCMI signaling state per interface
polling/full-enquiry interval timing
DLCMI error threshold and monitored event counts
maximum supported virtual circuits per interface

Imported Objects

From FRAME-RELAY-DTE-MIB

DLCI

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From REDSTONE-SMI

rsMgmt

OBJECT-IDENTITY

From REDSTONE-TC

RsNextIfIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

RowStatus
TimeStamp

How to Use in IPNetwork Monitor

Example using rsFrDlcmiStatsDteEnquiries OID:

Select a Redstone Communications router with Frame Relay WAN interface (DLCI/DLCMI signaling status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type rsFrDlcmiStatsDteEnquiries into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the number of Status Enquiries sent (as DTE). On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
rsFrameRelayMIB	1.3.6.1.4.1.2773.2.10			The Frame Relay MIB for the Redstone Communications Inc. enterprise.
I32 rsFrCircuitCommittedBurst	1.3.6.1.4.1.2773.2.10.1.1.4.1.12	Integer32	read-create	This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
TIM rsFrCircuitCreationTime	1.3.6.1.4.1.2773.2.10.1.1.4.1.10	TimeStamp	read-only	The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.
C32 rsFrCircuitDiscards	1.3.6.1.4.1.2773.2.10.1.1.4.1.17	Counter32	read-only	The number of inbound frames dropped because of format errors, or because the VC is inactive.
DLC rsFrCircuitDlci	1.3.6.1.4.1.2773.2.10.1.1.4.1.2	DLCI	not-accessible	The Data Link Connection Identifier for this virtual circuit.
rsFrCircuitEntry	1.3.6.1.4.1.2773.2.10.1.1.4.1		not-accessible	The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in rsFrCircuitCreationTime.
I32 rsFrCircuitExcessBurst	1.3.6.1.4.1.2773.2.10.1.1.4.1.13	Integer32	read-create	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.
NUM rsFrCircuitIfIndex	1.3.6.1.4.1.2773.2.10.1.1.4.1.1	InterfaceIndex	not-accessible	The ifIndex Value of the ifEntry this virtual circuit is layered onto.
TIM rsFrCircuitLastTimeChange	1.3.6.1.4.1.2773.2.10.1.1.4.1.11	TimeStamp	read-only	The value of sysUpTime when last there was a change in the virtual circuit state
NUM rsFrCircuitLogicalIfIndex	1.3.6.1.4.1.2773.2.10.1.1.4.1.20	InterfaceIndex	read-create	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.
INT rsFrCircuitMulticast	1.3.6.1.4.1.2773.2.10.1.1.4.1.15	INTEGER	read-create	This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to
C32 rsFrCircuitReceivedBECNs	1.3.6.1.4.1.2773.2.10.1.1.4.1.5	Counter32	read-only	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.
C32 rsFrCircuitReceivedDEs	1.3.6.1.4.1.2773.2.10.1.1.4.1.18	Counter32	read-only	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.
C32 rsFrCircuitReceivedFECNs	1.3.6.1.4.1.2773.2.10.1.1.4.1.4	Counter32	read-only	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.
C32 rsFrCircuitReceivedFrames	1.3.6.1.4.1.2773.2.10.1.1.4.1.8	Counter32	read-only	Number of frames received over this virtual circuit since it was created.
C32 rsFrCircuitReceivedOctets	1.3.6.1.4.1.2773.2.10.1.1.4.1.9	Counter32	read-only	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.
ROW rsFrCircuitRowStatus	1.3.6.1.4.1.2773.2.10.1.1.4.1.21	RowStatus	read-create	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.
C32 rsFrCircuitSentBECNs	1.3.6.1.4.1.2773.2.10.1.1.4.1.23	Counter32	read-only	Number of frames sent to 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.
C32 rsFrCircuitSentDEs	1.3.6.1.4.1.2773.2.10.1.1.4.1.19	Counter32	read-only	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.
C32 rsFrCircuitSentFECNs	1.3.6.1.4.1.2773.2.10.1.1.4.1.22	Counter32	read-only	Number of frames sent to 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.
C32 rsFrCircuitSentFrames	1.3.6.1.4.1.2773.2.10.1.1.4.1.6	Counter32	read-only	The number of frames sent from this virtual circuit since it was created.
C32 rsFrCircuitSentOctets	1.3.6.1.4.1.2773.2.10.1.1.4.1.7	Counter32	read-only	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.
INT rsFrCircuitState	1.3.6.1.4.1.2773.2.10.1.1.4.1.3	INTEGER	read-create	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 rsFrCircuitRowStatus.
rsFrCircuitTable	1.3.6.1.4.1.2773.2.10.1.1.4		not-accessible	A table containing information about specific Data Link Connections (DLC) or virtual circuits. This table mirrors the structure of RFC2115 FRAME-RELAY-DTE-MIB frCircuitTable, for the purpose of enumerating circuits on both DTE and DCE Frame Relay interfaces.
I32 rsFrCircuitThroughput	1.3.6.1.4.1.2773.2.10.1.1.4.1.14	Integer32	read-create	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=rsFrCircuitCommittedBurst/rsFrCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T=rsFrCircuitExcessBurst/ifSpeed.
INT rsFrCircuitType	1.3.6.1.4.1.2773.2.10.1.1.4.1.16	INTEGER	read-only	Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.
rsFrCompliance	1.3.6.1.4.1.2773.2.10.4.1.1			The compliance statement for entities which implement the Redstone Frame Relay MIB.
rsFrCompliances	1.3.6.1.4.1.2773.2.10.4.1
rsFrConformance	1.3.6.1.4.1.2773.2.10.4
INT rsFrDlcmiAddress	1.3.6.1.4.1.2773.2.10.1.1.2.1.3	INTEGER	read-create	This variable states which address format is in use on the Frame Relay interface.
INT rsFrDlcmiAddressLen	1.3.6.1.4.1.2773.2.10.1.1.2.1.4	INTEGER	read-create	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.
I32 rsFrDlcmiDceErrorThreshold	1.3.6.1.4.1.2773.2.10.1.1.2.1.16	Integer32	read-create	The minimum number of errors that must be observed within the number of events specified by rsFrDlcmiDceMonitoredEvents, to declare the interface down. 'error' is lack of receipt of a Status Enquiry within the interval specified by rsFrDlcmiDcePollingInterval (T392). Pertains to DCE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DCE or NNI.
I32 rsFrDlcmiDceMonitoredEvents	1.3.6.1.4.1.2773.2.10.1.1.2.1.17	Integer32	read-create	The number of DCE polling intervals over which accumulated errors are counted against the threshold specified in rsFrDlcmiDceErrorThreshold. If, within this number of events, the number of errors equals or exceeds the threshold, the interface is declared down. The 'DCE polling interval' is specified by rsFrDlcmiDcePollingInterval. Pertains to DCE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DCE or NNI.
I32 rsFrDlcmiDcePollingInterval	1.3.6.1.4.1.2773.2.10.1.1.2.1.15	Integer32	read-create	The number of seconds within which a DCE expects to receive a Status Enquiry from the DTE. This value corresponds to the T392 timer. Pertains to DCE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DCE or NNI.
rsFrDlcmiEntry	1.3.6.1.4.1.2773.2.10.1.1.2.1		not-accessible	The Parameters for a particular Data Link Connection Management Interface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/rsIfTable, and rsFrDlcmiStatsTable. Creating/deleting user-side (DTE) entries in this table also causes coresponding entries to be created/deleted in RFC2115 frDlcmiTable. The organization and definitions of objects in this table are intentionally aligned closely to those in RFC2115.
I32 rsFrDlcmiErrorThreshold	1.3.6.1.4.1.2773.2.10.1.1.2.1.7	Integer32	read-create	The minimum number of errors that must be observed within the number of events specified by rsFrDlcmiMonitoredEvents, to declare the interface down. 'error' is lack of receipt of a Status, in response to an issued Status Enquiry, within the Polling Interval (T391). Pertains to DTE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DTE or NNI.
I32 rsFrDlcmiFullEnquiryInterval	1.3.6.1.4.1.2773.2.10.1.1.2.1.6	Integer32	read-create	Number of status enquiry intervals that pass before issuance of a full status enquiry message. Pertains to DTE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DTE or NNI.
NUM rsFrDlcmiIfIndex	1.3.6.1.4.1.2773.2.10.1.1.2.1.1	InterfaceIndex	read-only	The ifIndex value of the corresponding ifEntry.
NUM rsFrDlcmiLowerIfIndex	1.3.6.1.4.1.2773.2.10.1.1.2.1.13	InterfaceIndexOrZero	read-create	The ifIndex of an interface over which this Frame Relay interface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.
DLC rsFrDlcmiMaxSupportedVCs	1.3.6.1.4.1.2773.2.10.1.1.2.1.9	DLCI	read-create	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.
I32 rsFrDlcmiMonitoredEvents	1.3.6.1.4.1.2773.2.10.1.1.2.1.8	Integer32	read-create	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. 'status polling interval' is specified by rsFrDlcmiPollingInterval. Pertains to DTE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DTE or NNI.
INT rsFrDlcmiMulticast	1.3.6.1.4.1.2773.2.10.1.1.2.1.10	INTEGER	read-create	This indicates whether the Frame Relay interface is using a multicast service.
I32 rsFrDlcmiPollingInterval	1.3.6.1.4.1.2773.2.10.1.1.2.1.5	Integer32	read-create	This is the number of seconds between successive status enquiry messages sent by the DTE. Pertains to DTE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DTE or NNI.
INT rsFrDlcmiRole	1.3.6.1.4.1.2773.2.10.1.1.2.1.14	INTEGER	read-create	Specifies the role this interface assumes with respect to the remote end. When acting as a DTE, the following objects are not relevant: rsFrDlcmiDcePollingInterval rsFrDlcmiDceErrorThreshold rsFrDlcmiDceMonitoredEvents When acting as a DCE, the following objects are not relevant: rsFrDlcmiPollingInterval rsFrDlcmiFullEnquiryInterval rsFrDlcmiErrorThreshold rsFrDlcmiMonitoredEvents
ROW rsFrDlcmiRowStatus	1.3.6.1.4.1.2773.2.10.1.1.2.1.12	RowStatus	read-create	Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: rsFrDlcmiRowStatus rsFrDlcmiState rsFrDlcmiMaxSupportedVCs rsFrDlcmiLowerIfIndex rsFrDlcmiRole In addition, when creating an entry the following conditions must hold: A value for rsFrDlcmiIndex must have been determined previously, by reading rsFrNextIfIndex. The interface identified by rsFrDlcmiLowerIfIndex must exist, and must be an interface type that permits layering of Frame Relay above it. A corresponding entry in ifTable/ifXTable/rsIfTable is created/destroyed as a result of creating/destroying an entry in this table. If rsFrDlcmiRole is dte(0), a corresponding entry is created/deleted in frDlcmiTable.
INT rsFrDlcmiState	1.3.6.1.4.1.2773.2.10.1.1.2.1.2	INTEGER	read-create	This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.
C32 rsFrDlcmiStatsDceAsyncUpdates	1.3.6.1.4.1.2773.2.10.1.1.3.1.13	Counter32	read-only	Number of Asynchronous Updates sent (as DCE).
C32 rsFrDlcmiStatsDceEnquiries	1.3.6.1.4.1.2773.2.10.1.1.3.1.9	Counter32	read-only	Number of Status Enquiries received (as DCE.)
C32 rsFrDlcmiStatsDceEnquiryResponses	1.3.6.1.4.1.2773.2.10.1.1.3.1.11	Counter32	read-only	Number of Status Enquiry responses sent (as DCE).
C32 rsFrDlcmiStatsDceFullEnquiries	1.3.6.1.4.1.2773.2.10.1.1.3.1.10	Counter32	read-only	Number of Full Enquiries received (as DCE).
C32 rsFrDlcmiStatsDceFullEnquiryResponses	1.3.6.1.4.1.2773.2.10.1.1.3.1.12	Counter32	read-only	Number of Full Enquiry responses sent (as DCE).
C32 rsFrDlcmiStatsDceLossOfSequences	1.3.6.1.4.1.2773.2.10.1.1.3.1.15	Counter32	read-only	Number of times a discontinuity in sequence numbering of received messages was detected (as DCE).
C32 rsFrDlcmiStatsDceNoResponseTimeouts	1.3.6.1.4.1.2773.2.10.1.1.3.1.16	Counter32	read-only	Number of timer expirations awaiting a Status Enquiry (as DCE).
C32 rsFrDlcmiStatsDceUnknownRxMessages	1.3.6.1.4.1.2773.2.10.1.1.3.1.14	Counter32	read-only	Number of unknown messages received (as DCE).
TIK rsFrDlcmiStatsDiscontinuityTime	1.3.6.1.4.1.2773.2.10.1.1.3.1.17	TimeTicks	read-only	Value of sysUpTime at the most recent event that caused a discontinuity in the monotonic operation of any of the counters in this entry. Such disruption might be caused by: Hardware insertion/removal. Reconfiguration of rsFrDlcmiState. Reconfiguration of rsFrDlcmiRole. Conclusions can be drawn from successive polls of an entry's counters only if the value of this object, simultaneously retrieved in those polls, remains unchanged.
C32 rsFrDlcmiStatsDteAsyncUpdates	1.3.6.1.4.1.2773.2.10.1.1.3.1.5	Counter32	read-only	Number of Asynchronous Updates received (as DTE).
C32 rsFrDlcmiStatsDteEnquiriesEx	1.3.6.1.4.1.2773.2.10.1.1.3.1.1	Counter32	read-only	Number of Status Enquiries sent (as DTE).
C32 rsFrDlcmiStatsDteEnquiryResponses	1.3.6.1.4.1.2773.2.10.1.1.3.1.3	Counter32	read-only	Number of Status Enquiry responses received (as DTE).
C32 rsFrDlcmiStatsDteFullEnquiries	1.3.6.1.4.1.2773.2.10.1.1.3.1.2	Counter32	read-only	Number of Full Enquiries sent (as DTE).
C32 rsFrDlcmiStatsDteFullEnquiryResponses	1.3.6.1.4.1.2773.2.10.1.1.3.1.4	Counter32	read-only	Number of Full Enquiry responses received (as DTE).
C32 rsFrDlcmiStatsDteLossOfSequences	1.3.6.1.4.1.2773.2.10.1.1.3.1.7	Counter32	read-only	Number of times a discontinuity in sequence numbering of received messages was detected (as DTE).
C32 rsFrDlcmiStatsDteNoResponseTimeouts	1.3.6.1.4.1.2773.2.10.1.1.3.1.8	Counter32	read-only	Number of timer expirations awaiting a Status message (as DTE).
C32 rsFrDlcmiStatsDteUnknownRxMessages	1.3.6.1.4.1.2773.2.10.1.1.3.1.6	Counter32	read-only	Number of unknown messages received (as DTE).
rsFrDlcmiStatsEntry	1.3.6.1.4.1.2773.2.10.1.1.3.1		not-accessible	The statistics for a particular Data Link Connection Management Interface. Statistics are not relevant while the rsFrDlcmiState has the value 'noLmiConfigured'. The DTE statistics are relevant when the corresponding rsFrDlcmiRole is DTE. The DTE statistics are relevant when the corresponding rsFrDlcmiRole is DCE.
rsFrDlcmiStatsTable	1.3.6.1.4.1.2773.2.10.1.1.3		not-accessible	The statistics for the Data Link Connection Management Interface for the frame relay service on this interface.
INT rsFrDlcmiStatus	1.3.6.1.4.1.2773.2.10.1.1.2.1.11	INTEGER	read-only	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.
rsFrDlcmiTable	1.3.6.1.4.1.2773.2.10.1.1.2		not-accessible	The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface. This table represents a superset of functionality specified in RFC2115 FRAME-RELAY-DTE-MIB. In particular, it adds attributes that permit the interface to operate as a network-side (DCE) interface.
rsFrGroup	1.3.6.1.4.1.2773.2.10.4.2.1			A collection of objects providing management of Frame Relay interfaces in a Redstone product.
rsFrGroups	1.3.6.1.4.1.2773.2.10.4.2
rsFrIfLayer	1.3.6.1.4.1.2773.2.10.1.1
RSN rsFrNextIfIndex	1.3.6.1.4.1.2773.2.10.1.1.1	RsNextIfIndex	read-only	Coordinate ifIndex value allocation for entries in rsFrDlcmiTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.
rsFrObjects	1.3.6.1.4.1.2773.2.10.1
DLC rsFrSubIfCktDlci	1.3.6.1.4.1.2773.2.10.1.2.3.1.1	DLCI	not-accessible	The DLCI of the Frame Relay circuit used by this subinterface.
rsFrSubIfCktEntry	1.3.6.1.4.1.2773.2.10.1.2.3.1		not-accessible	Each entry describes the characteristics of a Frame Relay Subinterface circuit.
ROW rsFrSubIfCktRowStatus	1.3.6.1.4.1.2773.2.10.1.2.3.1.2	RowStatus	read-create	Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: rsFrSubIfCktRowStatus
rsFrSubIfCktTable	1.3.6.1.4.1.2773.2.10.1.2.3		not-accessible	This table contains entries for Frame Relay circuits configured on Frame Relay Subinterfaces present in the system. An implementation may constrain the number of circuits permitted to be configured per Frame Relay Subinterface; in particular, an implementation may restrict each Frame Relay Subinterface to have a single circuit. Attributes in this entry can only be configured at entry creation, and remain fixed for the lifetime of the entry.
rsFrSubIfEntry	1.3.6.1.4.1.2773.2.10.1.2.2.1		not-accessible	Each entry describes the characteristics of a Frame Relay Subinterface. Creating/deleting entries in this table causes corresponding entries for be created /deleted in ifTable/ifXTable/rsIfTable.
rsFrSubIfGroup	1.3.6.1.4.1.2773.2.10.4.2.2			A collection of objects providing management of Frame Relay subinterfaces in a Redstone product.
I32 rsFrSubIfId	1.3.6.1.4.1.2773.2.10.1.2.2.1.4	Integer32	read-create	An integer identifier for the Frame Relay subinterface, used in conjunction with the command-line interface. It is provided here for cross-reference purposes only. The value must be unique among subinterfaces configured on the same underlying Frame Relay interface. If this object is not configured, or is configured with a value of -1, a nonzero value will be allocated internally and can be retrieved from this object after table entry creation has succeeded. A value of zero for this object is reserved for future use.
NUM rsFrSubIfIndex	1.3.6.1.4.1.2773.2.10.1.2.2.1.1	InterfaceIndex	not-accessible	The ifIndex of the Frame Relay Subinterface. When creating entries in this table, suitable values for this object are determined by reading rsFrSubNextIfIndex.
rsFrSubIfLayer	1.3.6.1.4.1.2773.2.10.1.2
NUM rsFrSubIfLowerIfIndex	1.3.6.1.4.1.2773.2.10.1.2.2.1.3	InterfaceIndexOrZero	read-create	The ifIndex of a Frame Relay interface over which this Frame Relay Subinterface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.
RSN rsFrSubIfNextIfIndex	1.3.6.1.4.1.2773.2.10.1.2.1	RsNextIfIndex	read-only	Coordinate ifIndex value allocation for entries in rsFrSubIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.
ROW rsFrSubIfRowStatus	1.3.6.1.4.1.2773.2.10.1.2.2.1.2	RowStatus	read-create	Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: rsFrSubIfRowStatus rsFrSubIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for rsFrSubIfIndex must have been determined previously, by reading rsFrSubIfNextIfIndex. The interface identified by rsFrSubIfLowerIfIndex must exist, and must be a Frame Relay interface. A positive value configured for rsFrSubIfId must not already be assigned to another subinterface layered onto the same underlying Frame Relay interface. A corresponding entry in ifTable/ifXTable/rsIfTable is created/destroyed as a result of creating/destroying an entry in this table.
rsFrSubIfTable	1.3.6.1.4.1.2773.2.10.1.2.2		not-accessible	This table contains entries for Frame Relay Subinterfaces present in the system.

RFC description

Manages Frame Relay interfaces and subinterfaces on Redstone Communications edge routers including DTE and NNI modes.

Start monitoring Redstone Communications router with Frame Relay WAN interfaces (DLCI/DLCMI signaling status) 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 REDSTONE-FRAME-RELAY-MIB