Home/Catalog/Juniper-FRAME-RELAY-MIB

Juniper-FRAME-RELAY-MIB

AI MIB Summary

The Juniper-FRAME-RELAY-MIB enables monitoring of Frame Relay virtual circuit states, interface statistics, and DLCI (Data Link Connection Identifier) configurations on Juniper Networks routers. It provides access to critical performance counters and error metrics, such as FECN/BECN flags, CIR (Committed Information Rate) parameters, and PVC (Permanent Virtual Circuit) status, for managing legacy WAN connectivity.

The Frame Relay MIB for the Juniper Networks enterprise.
Main OID:
juniFrameRelayMIB.1.3.6.1.4.1.4874.2.2.10
105
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

105 total
Object Name
juniFrameRelayMIBThe Frame Relay MIB for the Juniper Networks enterprise.
MODULE-IDENTITY
.1.3.6.1.4.1.4874.2.2.10
juniFrObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.1
juniFrIfLayer
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.1.1
juniFrNextIfIndexCoordinate ifIndex value allocation for entries in juniFrDlcmiTable. 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.ro
JuniNextIfIndex (Juniper-TC)
.1.3.6.1.4.1.4874.2.2.10.1.1.1
juniFrDlcmiTableThe 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 the FRAME-RELAY-DTE-MIB. In particular, it adds attributes that permit the interface to operate as a network-side (DCE) interface.
SEQUENCE OF JuniFrDlcmiEntry
.1.3.6.1.4.1.4874.2.2.10.1.1.2
juniFrDlcmiEntryThe 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/juniIfTable, and juniFrDlcmiStatsTable. Creating/deleting user-side (DTE) entries in this table also causes coresponding entries to be created/deleted in FRAME-RELAY-DTE-MIB.frDlcmiTable. The organization and definitions of objects in this table are intentionally aligned closely to those in FRAME-RELAY-DTE-MIB.
JuniFrDlcmiEntry
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1
juniFrDlcmiIfIndexThe ifIndex value of the corresponding ifEntry.ro
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.1
juniFrDlcmiStateThis variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.rw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.2
juniFrDlcmiAddressThis variable states which address format is in use on the Frame Relay interface.rw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.3
juniFrDlcmiAddressLenThis 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.rw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.4
juniFrDlcmiPollingIntervalThis 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.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.5
juniFrDlcmiFullEnquiryIntervalNumber 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.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.6
juniFrDlcmiErrorThresholdThe minimum number of errors that must be observed within the number of events specified by juniFrDlcmiMonitoredEvents, 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.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.7
juniFrDlcmiMonitoredEventsThe 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 juniFrDlcmiPollingInterval. Pertains to DTE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DTE or NNI.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.8
juniFrDlcmiMaxSupportedVCsThe 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.rw
DLCI (FRAME-RELAY-DTE-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.9
juniFrDlcmiMulticastThis indicates whether the Frame Relay interface is using a multicast service.rw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.10
juniFrDlcmiStatusThis 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.ro
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.11
juniFrDlcmiRowStatusControls 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: juniFrDlcmiRowStatus juniFrDlcmiState juniFrDlcmiMaxSupportedVCs juniFrDlcmiLowerIfIndex juniFrDlcmiRole juniFrDlcmiMultilinkFrBundleName (Only for multilink frame relay) In addition, when creating an entry the following conditions must hold: A value for juniFrDlcmiIndex must have been determined previously, by reading juniFrNextIfIndex. The interface identified by juniFrDlcmiLowerIfIndex must exist, and must be an interface type that permits layering of Frame Relay above it. A corresponding entry in ifTable/ifXTable/juniIfTable is created/ destroyed as a result of creating/destroying an entry in this table. If juniFrDlcmiRole is dte(0), a corresponding entry is created/deleted in frDlcmiTable.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.12
juniFrDlcmiLowerIfIndexThe 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. In case of multilink frame relay support, it will be multilink frame relay interface's ifIndex.rw
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.13
juniFrDlcmiRoleSpecifies the role this interface assumes with respect to the remote end. When acting as a DTE, the following objects are not relevant: juniFrDlcmiDcePollingInterval juniFrDlcmiDceErrorThreshold juniFrDlcmiDceMonitoredEvents When acting as a DCE, the following objects are not relevant: juniFrDlcmiPollingInterval juniFrDlcmiFullEnquiryInterval juniFrDlcmiErrorThreshold juniFrDlcmiMonitoredEventsrw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.14
juniFrDlcmiDcePollingIntervalThe 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.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.15
juniFrDlcmiDceErrorThresholdThe minimum number of errors that must be observed within the number of events specified by juniFrDlcmiDceMonitoredEvents, to declare the interface down. 'error' is lack of receipt of a Status Enquiry within the interval specified by juniFrDlcmiDcePollingInterval (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.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.16
juniFrDlcmiDceMonitoredEventsThe number of DCE polling intervals over which accumulated errors are counted against the threshold specified in juniFrDlcmiDceErrorThreshold. 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 juniFrDlcmiDcePollingInterval. Pertains to DCE/NNI operation only. This parameter can be reconfigured only when the Frame Relay interface is acting as a DCE or NNI.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.17
juniFrDlcmiMultilinkFrBundleNameThis represents multilink frame relay bundle name. This object must be configured to associate the bundle name to the frame relay major interface to support the multilink frame relay encapsulation. For non-multilink frame relay, bundle name configuration is not valid and will be ignored.rw
JuniFrMlFrBundleName
.1.3.6.1.4.1.4874.2.2.10.1.1.2.1.18
juniFrDlcmiStatsTableThe statistics for the Data Link Connection Management Interface for the frame relay service on this interface.
SEQUENCE OF JuniFrDlcmiStatsEntry
.1.3.6.1.4.1.4874.2.2.10.1.1.3
juniFrDlcmiStatsEntryThe statistics for a particular Data Link Connection Management Interface. Statistics are not relevant while the juniFrDlcmiState has the value 'noLmiConfigured'. The DTE statistics are relevant when the corresponding juniFrDlcmiRole is DTE. The DTE statistics are relevant when the corresponding juniFrDlcmiRole is DCE.
JuniFrDlcmiStatsEntry
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1
juniFrDlcmiStatsDteEnquiriesNumber of Status Enquiries sent (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.1
juniFrDlcmiStatsDteFullEnquiriesNumber of Full Enquiries sent (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.2
juniFrDlcmiStatsDteEnquiryResponsesNumber of Status Enquiry responses received (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.3
juniFrDlcmiStatsDteFullEnquiryResponsesNumber of Full Enquiry responses received (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.4
juniFrDlcmiStatsDteAsyncUpdatesNumber of Asynchronous Updates received (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.5
juniFrDlcmiStatsDteUnknownRxMessagesNumber of unknown messages received (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.6
juniFrDlcmiStatsDteLossOfSequencesNumber of times a discontinuity in sequence numbering of received messages was detected (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.7
juniFrDlcmiStatsDteNoResponseTimeoutsNumber of timer expirations awaiting a Status message (as DTE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.8
juniFrDlcmiStatsDceEnquiriesNumber of Status Enquiries received (as DCE.)ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.9
juniFrDlcmiStatsDceFullEnquiriesNumber of Full Enquiries received (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.10
juniFrDlcmiStatsDceEnquiryResponsesNumber of Status Enquiry responses sent (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.11
juniFrDlcmiStatsDceFullEnquiryResponsesNumber of Full Enquiry responses sent (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.12
juniFrDlcmiStatsDceAsyncUpdatesNumber of Asynchronous Updates sent (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.13
juniFrDlcmiStatsDceUnknownRxMessagesNumber of unknown messages received (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.14
juniFrDlcmiStatsDceLossOfSequencesNumber of times a discontinuity in sequence numbering of received messages was detected (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.15
juniFrDlcmiStatsDceNoResponseTimeoutsNumber of timer expirations awaiting a Status Enquiry (as DCE).ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.16
juniFrDlcmiStatsDiscontinuityTimeValue 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 juniFrDlcmiState. Reconfiguration of juniFrDlcmiRole. 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.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.4874.2.2.10.1.1.3.1.17
juniFrCircuitTableA table containing information about specific Data Link Connections (DLC) or virtual circuits. This table mirrors the structure of FRAME-RELAY-DTE-MIB.frCircuitTable, for the purpose of enumerating circuits on both DTE and DCE Frame Relay interfaces.
SEQUENCE OF JuniFrCircuitEntry
.1.3.6.1.4.1.4874.2.2.10.1.1.4
juniFrCircuitEntryThe information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in juniFrCircuitCreationTime.
JuniFrCircuitEntry
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1
juniFrCircuitIfIndexThe ifIndex Value of the ifEntry this virtual circuit is layered onto.
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.1
juniFrCircuitDlciThe Data Link Connection Identifier for this virtual circuit.
DLCI (FRAME-RELAY-DTE-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.2
juniFrCircuitStateIndicates 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 juniFrCircuitRowStatus.rw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.3
juniFrCircuitReceivedFECNsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.4
juniFrCircuitReceivedBECNsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.5
juniFrCircuitSentFramesThe number of frames sent from this virtual circuit since it was created.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.6
juniFrCircuitSentOctetsThe 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.7
juniFrCircuitReceivedFramesNumber of frames received over this virtual circuit since it was created.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.8
juniFrCircuitReceivedOctetsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.9
juniFrCircuitCreationTimeThe value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.10
juniFrCircuitLastTimeChangeThe value of sysUpTime when last there was a change in the virtual circuit statero
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.11
juniFrCircuitCommittedBurstThis variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval. A value of zero (the default) indicates no commitment.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.12
juniFrCircuitExcessBurstThis 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.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.13
juniFrCircuitThroughputThroughput 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 = juniFrCircuitCommittedBurst / juniFrCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T = juniFrCircuitExcessBurst / ifSpeed A value of zero (the default) for throughput indicates no commitment.rw
Integer32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.14
juniFrCircuitMulticastThis indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to.rw
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.15
juniFrCircuitTypeIndication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.ro
Enumeration
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.16
juniFrCircuitDiscardsThe number of inbound frames dropped because of format errors, or because the VC is inactive.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.17
juniFrCircuitReceivedDEsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.18
juniFrCircuitSentDEsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.19
juniFrCircuitLogicalIfIndexNormally 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.rw
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.20
juniFrCircuitRowStatusThis 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.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.21
juniFrCircuitSentFECNsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.22
juniFrCircuitSentBECNsNumber 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.ro
Counter32
.1.3.6.1.4.1.4874.2.2.10.1.1.4.1.23
juniFrSubIfLayer
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.1.2
juniFrSubIfNextIfIndexCoordinate ifIndex value allocation for entries in juniFrSubIfTable. 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.ro
JuniNextIfIndex (Juniper-TC)
.1.3.6.1.4.1.4874.2.2.10.1.2.1
juniFrSubIfTableThis table contains entries for Frame Relay Subinterfaces present in the system.
SEQUENCE OF JuniFrSubIfEntry
.1.3.6.1.4.1.4874.2.2.10.1.2.2
juniFrSubIfEntryEach 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/juniIfTable.
JuniFrSubIfEntry
.1.3.6.1.4.1.4874.2.2.10.1.2.2.1
juniFrSubIfIndexThe ifIndex of the Frame Relay Subinterface. When creating entries in this table, suitable values for this object are determined by reading juniFrSubNextIfIndex.
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.2.2.1.1
juniFrSubIfRowStatusControls 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: juniFrSubIfRowStatus juniFrSubIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for juniFrSubIfIndex must have been determined previously, by reading juniFrSubIfNextIfIndex. The interface identified by juniFrSubIfLowerIfIndex must exist, and must be a Frame Relay interface. A positive value configured for juniFrSubIfId must not already be assigned to another subinterface layered onto the same underlying Frame Relay interface. A corresponding entry in ifTable/ifXTable/juniIfTable is created/ destroyed as a result of creating/destroying an entry in this table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.2.2.1.2
juniFrSubIfLowerIfIndexThe 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.rw
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.2.2.1.3
juniFrSubIfIdAn 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.rw
Integer32 (-1..2147483647)
.1.3.6.1.4.1.4874.2.2.10.1.2.2.1.4
juniFrSubIfCktTableThis 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.
SEQUENCE OF JuniFrSubIfCktEntry
.1.3.6.1.4.1.4874.2.2.10.1.2.3
juniFrSubIfCktEntryEach entry describes the characteristics of a Frame Relay Subinterface circuit.
JuniFrSubIfCktEntry
.1.3.6.1.4.1.4874.2.2.10.1.2.3.1
juniFrSubIfCktDlciThe DLCI of the Frame Relay circuit used by this subinterface.
DLCI (FRAME-RELAY-DTE-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.2.3.1.1
juniFrSubIfCktRowStatusControls 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: juniFrSubIfCktRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.2.3.1.2
juniFrMlFr
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.1.3
juniFrMlFrBundleTableThis table contains entries for MLFR bundles present in the system.
SEQUENCE OF JuniFrMlFrBundleEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.1
juniFrMlFrBundleEntryEach entry describes the characteristics of a Multilink bundle.
JuniFrMlFrBundleEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.1.1
juniFrMlFrBundleNameThe administrative name of the multilink bundle associated with this Frame Relay major interface.
JuniFrMlFrBundleName
.1.3.6.1.4.1.4874.2.2.10.1.3.1.1.1
juniFrMlFrBundleRowStatusThe rowStatus for this entry. The following sets are supported: createAndGo(4), destroy(6) The following values can be read from this object: active(1)rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.3.1.1.2
juniFrMlFrNextLinkIfIndexCoordinate ifIndex value allocation for entries in juniFrMlFrLinkConfigTable. 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.ro
JuniNextIfIndex (Juniper-TC)
.1.3.6.1.4.1.4874.2.2.10.1.3.2
juniFrMlFrLinkConfigTableThis table contains entries for FR link interfaces present in the system to be added to the multilink bundles.
SEQUENCE OF JuniFrMlFrLinkConfigEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.3
juniFrMlFrLinkConfigEntryEach entry describes the characteristics of FR link interface. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable.
JuniFrMlFrLinkConfigEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.3.1
juniFrMlFrLinkConfigIfIndexThe ifIndex of the FR link interface. When creating entries in this table, suitable values for this object are determined by reading juniFrMlFrNextLinkIfIndex.
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.3.3.1.1
juniFrMlFrLinkConfigLowerIfIndexThe ifIndex of an interface over which this FR link interface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a non-zero value be configured at entry creation.rw
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.3.3.1.2
juniFrMlFrLinkConfigRowStatusControls 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: juniFrMlFrLinkConfigRowStatus juniFrMlFrLinkConfigLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for juniFrMlFrLinkConfigIfIndex must have been determined previously, by reading juniFrMlFrNextIfIndex. The interface identified by juniFrMlFrLinkConfigLowerIfIndex must exist. A corresponding entry in ifTable/ifXTable/juniIfTable is created/ destroyed as a result of creating/destroying an entry in this table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.3.3.1.3
juniFrMlFrMajorConfigTableThis table contains entries for FR major interfaces present in the system which are associated with multilink bundles.
SEQUENCE OF JuniFrMlFrMajorConfigEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.4
juniFrMlFrMajorConfigEntryEach entry describes the characteristics of FR major interface which have association with the MLFR bundles. Creating/deleting entries in this table causes corresponding entries for be created/deleted in ifTable/ifXTable/juniIfTable.
JuniFrMlFrMajorConfigEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.4.1
juniFrMlFrMajorConfigIfIndexThe ifIndex of the FR Major interface. When creating entries in this table, suitable values for this object are determined by reading already created FR Major interface values. Each multilink bundle will be associated with one FR major interface. This association will be done at the creation of FR major interface (juniFrDlcmiTable) specifying its lower interfce binding as FR link ifIndex(juniFrMlFrLinkConfigTable) and the multilink bundle name.
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.3.4.1.1
juniFrMlFrMajorConfigLowerIfIndexThe ifIndex of a FR link interface over which this FR Major interface is to be layered. On sets, the value of this object must equal on of the previously created FR link interfaces created in the juniFrMlFrLinkConfigTable. On gets, the value of this object is the lexicographically least FR link interface in a potential bundle of FR link interfaces.rw
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.3.4.1.2
juniFrMlFrMajorBundleNameThe MLFR bundle name administratively assigned.rw
JuniFrMlFrBundleName
.1.3.6.1.4.1.4874.2.2.10.1.3.4.1.3
juniFrMlFrMajorRowStatusControls 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: juniFrMlFrMajorConfigLowerIfIndex juniFrMlFrMajorBundleName juniFrMlFrMajorConfigRowStatus In addition, when creating an entry the following conditions must hold: The interface identified by juniFrMlFrMajorConfigIndex must exist by a creation request to the juniFrDlcmiTable. The interface identified by juniFrMlFrMajorConfigLowerIfIndex must exist by a creation request to the juniFrMlFrLinkConfigTable. The bundleName specified in juniFrMlFrMajorBundleName must have been created first in the juniFrMlFrBundleTable. A corresponding entry in ifTable/ifXTable/juniIfTable is created/ destroyed as a result of creating/destroying an entry in this table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.3.4.1.4
juniFrMlFrLinkBindTableThis table contains entries for FR Link interfaces to FR major interfaces bindings associated with multilink bundles.
SEQUENCE OF JuniFrMlFrLinkBindEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.5
juniFrMlFrLinkBindEntryEach entry describes the FR link interface to FR major interface bindingsi associated with multilink bundles.
JuniFrMlFrLinkBindEntry
.1.3.6.1.4.1.4874.2.2.10.1.3.5.1
juniFrMlFrBindMajorIfIndexThe ifIndex of the FR major interface associated with multilink.
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.3.5.1.1
juniFrMlFrBindLinkIfIndexThe ifIndex of a FR link interface bound by the FR major interface defined by juniFrMlFrBindMajorIfIndex.
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.4874.2.2.10.1.3.5.1.2
juniFrMlFrBindRowStatusControls 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: juniFrMlFrBindRowStatus In addition, when creating an entry the following conditions must hold: The interfaces identified by juniFrMlFrBindNetworkIfIndex and juniFrMlFrBindLinkIfIndex must be created in the juniFrMlFrMajorConfigTable and juniFrMlFrLinkConfigTable respectively. A MLFR bundle must be associated with the juniFrMlFrMajorIfIndex and exist in the juniFrMibFrBundleTable. A corresponding entry in ifStackTable is created/destroyed as a result of creating/destroying an entry in this table. Note: This table is read-only table for now. To add links to bundle make use of juniFrMlFrMajorConfigTable.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.4874.2.2.10.1.3.5.1.3
juniFrConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.4
juniFrCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.4.1
juniFrGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.4874.2.2.10.4.2
Juniper-FRAME-RELAY-MIB - SNMP MIB Reference | MIBs Explorer