draft-ietf-frnetmib-mfrmib-03.txt   rfc3020.txt 
Internet Draft MIB For FRF.16 UNI/NNI MFR September 2000 Network Working Group P. Pate
Request for Comments: 3020 B. Lynch
Category: Standards Track Overture Networks
K. Rehbehn
Megisto Systems, Inc.
December 2000
Definitions of Managed Objects Definitions of Managed Objects
for Monitoring and Controlling the for Monitoring and Controlling the
UNI/NNI Multilink Frame Relay Function UNI/NNI Multilink Frame Relay Function
September 6, 2000
draft-ietf-frnetmib-mfrmib-03
Prayson Pate
Overture Networks
prayson.pate@overturenetworks.com
Bob Lynch
Larscom Incorporated
blynch@larscom.com
Kenneth Rehbehn
Megisto Systems, Inc.
krehbehn@megisto.com
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC 2026. Internet-Drafts are Internet community, and requests discussion and suggestions for
working documents of the Internet Engineering Task Force (IETF), its improvements. Please refer to the current edition of the "Internet
areas, and its working groups. Note that other groups may also Official Protocol Standards" (STD 1) for the standardization state
distribute working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2000). All Rights Reserved.
http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a Management Information Base (MIB) for monitoring This memo defines a Management Information Base (MIB) for monitoring
and controlling a UNI/NNI Multilink Frame Relay Function as defined and controlling a UNI/NNI Multilink Frame Relay Function as defined
in Frame Relay Forum FRF.16. This MIB also include conformance and in Frame Relay Forum FRF.16. This MIB also includes conformance and
notification information. notification information.
Copyright Notice Table of Contents
Copyright (C) The Internet Society (2000). All Rights Reserved.
Table of Contents
1 The SNMP Management Framework ................................ 4 1 The SNMP Management Framework ................................ 2
2 Overview ..................................................... 5 2 Overview ..................................................... 3
2.1 Multilink Frame Relay Background ........................... 5 2.1 Multilink Frame Relay Background ........................... 3
2.1.1 Terminology .............................................. 5 2.1.1 Terminology .............................................. 4
2.1.2 Reference Model .......................................... 6 2.1.2 Reference Model .......................................... 5
2.2 Structure of the MIB ....................................... 7 2.2 Structure of the MIB ....................................... 5
2.2.1 bundleMaxNumBundles ...................................... 7 2.2.1 mfrBundleMaxNumBundles ................................... 6
2.2.2 bundleNextIndex .......................................... 7 2.2.2 mfrBundleNextIndex ....................................... 6
2.2.3 bundleTable .............................................. 7 2.2.3 mfrBundleTable ........................................... 6
2.2.4 Bundle-to-ifIndex Mapping Table .......................... 7 2.2.4 Bundle-to-ifIndex Mapping Table .......................... 6
2.2.5 bundleLinkTable .......................................... 8 2.2.5 mfrBundleLinkTable ....................................... 6
2.3 Relationship With Other MIBS and Tables .................... 8 2.3 Relationship With Other MIBS and Tables .................... 7
2.3.1 Relationship With Interface Table ........................ 8 2.3.1 Relationship With Interface Table ........................ 7
2.3.1.1 Bundle Links ........................................... 8 2.3.1.1 Bundle Links ........................................... 7
2.3.1.2 Bundles ................................................ 8 2.3.1.2 Bundles ................................................ 7
2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 9 2.3.1.3 Mapping Between ifIndex and mfrBundleIndex ............. 8
2.3.1.4 ifTable Objects ........................................ 9 2.3.1.4 ifTable Objects ........................................ 8
2.3.2 Relationship With Interface Stack Table .................. 10 2.3.2 Relationship With Interface Stack Table .................. 9
2.3.3 Relationship With Frame Relay DTE MIB .................... 10 2.3.3 Relationship With Frame Relay DTE MIB .................... 9
2.3.4 Relationship With Frame Relay Service MIB ................ 10 2.3.4 Relationship With Frame Relay Service MIB ................ 9
2.3.5 Example .................................................. 10 2.3.5 Example .................................................. 9
2.4 Creation Of Bundles and Bundle Links ....................... 12 2.4 Creation Of Bundles and Bundle Links ....................... 11
2.4.1 Creation Of Bundles ...................................... 12 2.4.1 Creation Of Bundles ...................................... 11
2.4.2 Creation Of Bundle Links ................................. 12 2.4.2 Creation Of Bundle Links ................................. 11
2.5 Notifications .............................................. 12 2.5 Notifications .............................................. 11
2.5.1 Bundle ................................................... 12 2.5.1 Bundle ................................................... 11
2.5.1.1 linkUp ................................................. 12 2.5.1.1 linkUp ................................................. 12
2.5.1.2 linkDown ............................................... 13 2.5.1.2 linkDown ............................................... 12
2.5.2 Bundle Link .............................................. 13 2.5.2 Bundle Link .............................................. 12
2.5.2.1 linkUp ................................................. 13 2.5.2.1 linkUp ................................................. 12
2.5.2.2 linkDown ............................................... 13 2.5.2.2 linkDown ............................................... 12
2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 13 2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 12
3 Object Definitions ........................................... 14 3 Object Definitions ........................................... 13
4 Acknowledgments .............................................. 34 4 Acknowledgments .............................................. 32
5 References ................................................... 35 5 References ................................................... 32
6 Security Considerations ...................................... 38 6 Security Considerations ...................................... 34
7 Authors' Addresses ........................................... 39 7 Authors' Addresses ........................................... 35
8 Full Copyright Section ....................................... 39 8 Full Copyright Statement ..................................... 36
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in STD
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
1215 [RFC1215]. The second version, called SMIv2, is described [RFC1215]. The second version, called SMIv2, is described in STD
in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 58: RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580].
[RFC2580].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of the described in STD 15, RFC 1157 [RFC1157]. A second version of the
SNMP message protocol, which is not an Internet standards track SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
and RFC 1906 [RFC1906]. The third version of the message and RFC 1906 [RFC1906]. The third version of the message protocol
protocol is called SNMPv3 and described in RFC 1906 [RFC1906], is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572
RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of described in STD 15, RFC 1157 [RFC1157]. A second set of protocol
protocol operations and associated PDU formats is described in operations and associated PDU formats is described in RFC 1905
RFC 1905 [RFC1905]. [RFC1905].
o A set of fundamental applications described in RFC 2573 o A set of fundamental applications described in RFC 2573 [RFC2573]
[RFC2573] and the view-based access control mechanism described and the view-based access control mechanism described in RFC 2575
in RFC 2575 [RFC2575]. [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570]. can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Overview 2. Overview
This document defines a Management Information Base (MIB) for This document defines a Management Information Base (MIB) for
monitoring and controlling the UNI/NNI Multilink Frame Relay monitoring and controlling the UNI/NNI Multilink Frame Relay
function. The agreement on which this MIB is based was defined and function. The agreement on which this MIB is based was defined and
documented by the Frame Relay Forum in the Frame Relay Forum Document documented by the Frame Relay Forum in the Frame Relay Forum Document
FRF.16 [FRF.16]. FRF.16 [FRF.16].
skipping to change at page 5, line 31 skipping to change at page 4, line 12
This service provides a frame-based inverse multiplexing function, This service provides a frame-based inverse multiplexing function,
sometimes referred to as an "IMUX". sometimes referred to as an "IMUX".
The bundle provides the same order-preserving service as a physical The bundle provides the same order-preserving service as a physical
layer for frames sent on a data link connection. In addition, the layer for frames sent on a data link connection. In addition, the
bundle provides support for all Frame Relay services based on UNI and bundle provides support for all Frame Relay services based on UNI and
NNI standards. NNI standards.
2.1.1. Terminology 2.1.1. Terminology
Physical Link -- A single physical interface that interconnects two Physical Link -- A single physical interface that interconnects
devices in a frame relay network (e.g. DS1, DS0, two devices in a frame relay network (e.g., DS1,
Bearer channel, refer to FRF.14). DS0, Bearer channel, refer to FRF.14).
Bundle -- A grouping of one or more physical links using the Bundle -- A grouping of one or more physical links using
formats and procedures of multilink frame relay. the formats and procedures of multilink frame
The bundle operates as a logical interface function relay. The bundle operates as a logical
that emulates a single physical interface to the interface function that emulates a single
Q.922 data link layer. physical interface to the Q.922 data link layer.
Bundle Link -- A MFR sub-component that controls operation of one Bundle Link -- A MFR sub-component that controls operation of
of the bundle's physical links. one of the bundle's physical links.
2.1.2. Reference Model 2.1.2. Reference Model
+--------------------------+ +--------------------------+ +--------------------------+ +--------------------------+
| Switching Layer -OR- | | Switching Layer -OR- | | Switching Layer -OR- | | Switching Layer -OR- |
| Higher-Level Applications| | Higher-Level Applications| | Higher-Level Applications| | Higher-Level Applications|
+--------------------------+ +--------------------------+ +--------------------------+ +--------------------------+
| |C-Plane - Q.933| | |C-Plane - Q.933| | |C-Plane - Q.933| | |C-Plane - Q.933|
| U-Plane | (Note 1) | | U-Plane | (Note 1) | | U-Plane | (Note 1) | | U-Plane | (Note 1) |
| (Note 3) |---------------| | (Note 3) |---------------| | (Note 3) |---------------| | (Note 3) |---------------|
| |Q.922 (Note 2) | | |Q.922 (Note 2) | | |Q.922 (Note 2) | | |Q.922 (Note 2) |
+--------------------------+ +--------------------------+ +--------------------------+ +--------------------------+
| Data Link Layer (Q.922) | | Data Link Layer (Q.922) | | Data Link Layer (Q.922) | | Data Link Layer (Q.922) |
+--------------------------+ +--------------------------+ +--------------------------+ +--------------------------+
| Bundle (B) | | Bundle (B) | | Bundle (B) | | Bundle (B) |
+--------------------------+ +--------------------------+ +--------------------------+ +--------------------------+
| Bundle | Bundle | Bundle | | Bundle | Bundle | Bundle | | Bundle | Bundle | Bundle | | Bundle | Bundle | Bundle |
| Link | Link | Link | | Link | Link | Link | | Link | Link | Link | | Link | Link | Link |
| (BL) | (BL) | (BL) | | (BL) | (BL) | (BL) | | (BL) | (BL) | (BL) | | (BL) | (BL) | (BL) |
+--------+--------+--------+ +--------+--------+--------+ +--------+--------+--------+ +--------+--------+--------+
|Physical|Physical|Physical| |Physical|Physical|Physical| |Physical|Physical|Physical| |Physical|Physical|Physical|
| (PH) | (PH) | (PH) | ___________ | (PH) | (PH) | (PH) | | (PH) | (PH) | (PH) | __________ | (PH) | (PH) | (PH) |
+----+---+----+---+----+---+ /\ \ +----+---+----+---+----+---+ +----+---+----+---+----+---+ /\ \ +----+---+----+---+----+---+
| | | / \ \ | | | | | | / \ \ | | |
| | +---------\ \-----+ | | | | +--------\ \-----+ | |
| | / \ \ | | | | / \ \ | |
| +--------------------\ \------------+ | | +-------------------\ \------------+ |
| _________\_______/ Bundle /_ | | _________\_______/ Bundle /_ |
| /\ / / \ | | /\ / / \ |
+-------------| Bundle Link / / |------------------+ +------------| Bundle Link / / |------------------+
\/_____________/ /____/ \/_____________/ /____/
\/__________/ \/__________/
Figure 1: MFR Reference Diagram Figure 1: MFR Reference Diagram
Note 1: C-Plane operation as described in Q.933 [Q.933] and FRF.4 Note 1: C-Plane operation as described in Q.933 [Q.933] and FRF.4
[FRF.4] [FRF.4]
Note 2: Multiple frame acknowledged information fransfer mode as Note 2: Multiple frame acknowledged information transfer mode as
described in Q.922 [Q.922] described in Q.922 [Q.922]
Note 3: Core aspects for use with frame relay bearer service as Note 3: Core aspects for use with frame relay bearer service as
described in Q.922, Annex A [Q.922] described in Q.922, Annex A [Q.922]
2.2. Structure of the MIB 2.2. Structure of the MIB
The UNI/NNI MFR managed objects consist of two scalar objects and The UNI/NNI MFR managed objects consist of two scalar objects and
three tables. three tables.
2.2.1. bundleMaxNumBundles 2.2.1. mfrBundleMaxNumBundles
This scalar is used to inform the manager of the maximum number of This scalar is used to inform the manager of the maximum number of
bundles supported by this device. bundles supported by this device.
2.2.2. bundleNextIndex 2.2.2. mfrBundleNextIndex
This scalar is used to assist the manager in selecting a value for This scalar is used to assist the manager in selecting a value for
bundleIndex during row creation. It can also be used to avoid race mfrBundleIndex during row creation. It can also be used to avoid
conditions with multiple managers trying to create rows in the table race conditions with multiple managers trying to create rows in the
(see RFC 2494 [RFC2494] for one such alogrithm). table (see RFC 2494 [RFC2494] for one such algorithm).
2.2.3. bundleTable 2.2.3. mfrBundleTable
This table provides a means to configure and monitor bundles. It is This table provides a means to configure and monitor bundles. It is
indexed by bundleIndex and contains these columns: indexed by mfrBundleIndex and contains these columns:
- bundleIndex Integer32 - mfrBundleIndex Integer32
- bundleIfIndex InterfaceIndex - mfrBundleIfIndex InterfaceIndex
- bundleRowStatus RowStatus - mfrBundleRowStatus RowStatus
- bundleNearEndName SnmpAdminString - mfrBundleNearEndName SnmpAdminString
- bundleFragmentation INTEGER - mfrBundleFragmentation INTEGER
- bundleMaxFragSize Integer32 - mfrBundleMaxFragSize Integer32
- bundleTimerHello INTEGER - mfrBundleTimerHello INTEGER
- bundleTimerAck INTEGER - mfrBundleTimerAck INTEGER
- bundleCountMaxRetry INTEGER - mfrBundleCountMaxRetry INTEGER
- bundleActivationClass INTEGER - mfrBundleActivationClass INTEGER
- bundleThreshold Integer32 - mfrBundleThreshold Integer32
- bundleMaxDiffDelay Integer32 - mfrBundleMaxDiffDelay Integer32
- bundleSeqNumSize INTEGER - mfrBundleSeqNumSize INTEGER
- bundleLinksConfigured Integer32 - mfrBundleLinksConfigured Integer32
- bundleLinksActive Integer32 - mfrBundleLinksActive Integer32
- bundleBandwidth Integer32 - mfrBundleBandwidth Integer32
- bundleFarEndName SnmpAdminString - mfrBundleFarEndName SnmpAdminString
- bundleResequencingErrors Counter32 - mfrBundleResequencingErrors Counter32
2.2.4. Bundle-to-ifIndex Mapping Table 2.2.4. Bundle-to-ifIndex Mapping Table
This table provides a means to take an ifIndex and find the This table provides a means to take an ifIndex and find the
corresponding bundleIndex. It is indexed by ifIndex and contains corresponding mfrBundleIndex. It is indexed by ifIndex and contains
these columns: these columns:
- bundleIfIndexMapping Integer32 - mfrBundleIfIndexMapping Integer32
2.2.5. bundleLinkTable 2.2.5. mfrBundleLinkTable
This table provides a means to configure and monitor bundle links. This table provides a means to configure and monitor bundle links.
It is indexed by ifIndex and contains these columns: It is indexed by ifIndex and contains these columns:
- bundleLinkRowStatus RowStatus - mfrBundleLinkRowStatus RowStatus
- bundleLinkConfigBundleIndex Integer32 - mfrBundleLinkConfigBundleIndex Integer32
- bundleLinkNearEndName SnmpAdminString - mfrBundleLinkNearEndName SnmpAdminString
- bundleLinkState BundleLinkState - mfrBundleLinkState MfrBundleLinkState
- bundleLinkFarEndName SnmpAdminString - mfrBundleLinkFarEndName SnmpAdminString
- bundleLinkFarEndBundleName SnmpAdminString - mfrBundleLinkFarEndBundleName SnmpAdminString
- bundleLinkDelay Integer32 - mfrBundleLinkDelay Integer32
- bundleLinkFramesControlTx Counter32 - mfrBundleLinkFramesControlTx Counter32
- bundleLinkFramesControlRx Counter32 - mfrBundleLinkFramesControlRx Counter32
- bundleLinkFramesControlInvalid Counter32 - mfrBundleLinkFramesControlInvalid Counter32
- bundleLinkTimerExpiredCount Counter32 - mfrBundleLinkTimerExpiredCount Counter32
- bundleLinkLoopbackSuspected Counter32 - mfrBundleLinkLoopbackSuspected Counter32
- bundleLinkUnexpectedSequence Counter32 - mfrBundleLinkUnexpectedSequence Counter32
- bundleLinkMismatch Counter32 - mfrBundleLinkMismatch Counter32
2.3. Relationship With Other MIBS and Tables 2.3. Relationship With Other MIBS and Tables
2.3.1. Relationship With Interface Table 2.3.1. Relationship With Interface Table
2.3.1.1. Bundle Links 2.3.1.1. Bundle Links
Each bundle link will appear as an interface in the ifTable. The Each bundle link will appear as an interface in the ifTable. The
ifIndex that appears in the ifTable is used for indexing the bundle ifIndex that appears in the ifTable is used for indexing the bundle
link tables in the UNI-NNI MFR MIB. link tables in the UNI-NNI MFR MIB.
2.3.1.2. Bundles 2.3.1.2. Bundles
Each bundle will appear as an interface in the ifTable. There will Each bundle will appear as an interface in the ifTable. There will
be corresponding bundleIndex which may be different than the ifIndex be corresponding mfrBundleIndex which may be different than the
of the bundle. ifIndex of the bundle.
The reason is best summarized in RFC 2494 [RFC2494], which describes The reason is best summarized in RFC 2494 [RFC2494], which describes
frame relay bundle of DS0. It says: frame relay bundle of DS0. It says:
This table is not indexed by ifIndex because the manager has to This table is not indexed by ifIndex because the manager has to
choose the index in a createable row and the agent must be choose the index in a createable row and the agent must be allowed
allowed to select ifIndex values. to select ifIndex values.
The rows in the ifEntry table are not creatable as they do not have The rows in the ifEntry table are not createable as they do not have
row status. RFC 2233 [RFC2233] suggests that the ifIndex should be row status. RFC 2863 [RFC2863] suggests that the ifIndex should be
chosen by the agent. Here is its statement regarding row creation chosen by the agent. Here is its statement regarding row creation
and deletion: and deletion:
While some interfaces, for example, most physical interfaces, While some interfaces, for example, most physical interfaces,
cannot be created via network management, other interfaces such cannot be created via network management, other interfaces such as
as logical interfaces sometimes can be. The ifTable contains logical interfaces sometimes can be. The ifTable contains only
only generic information about an interface. Almost all generic information about an interface. Almost all 'create-able'
'create-able' interfaces have other, media-specific, information interfaces have other, media-specific, information through which
through which configuration parameters may be supplied prior to configuration parameters may be supplied prior to creating such an
creating such an interface. Thus, the ifTable does not itself interface. Thus, the ifTable does not itself support the creation
support the creation or deletion of an interface (specifically, or deletion of an interface (specifically, it has no RowStatus
it has no RowStatus column). Rather, if a particular interface column). Rather, if a particular interface type supports the
type supports the dynamic creation and/or deletion of an dynamic creation and/or deletion of an interface of that type,
interface of that type, then that media-specific MIB should then that media-specific MIB should include an appropriate
include an appropriate RowStatus object (see the ATM LAN- RowStatus object (see the ATM LAN-Emulation Client MIB [ATMLANE]
Emulation Client MIB [ATMLANE] for an example of a MIB which for an example of a MIB which does this). Typically, when such a
does this). Typically, when such a RowStatus object is RowStatus object is created/deleted, then the conceptual row in
created/deleted, then the conceptual row in the ifTable the ifTable appears/disappears as a by-product, and an ifIndex
appears/disappears as a by-product, and an ifIndex value (chosen value (chosen by the agent) is stored in an appropriate object in
by the agent) is stored in an appropriate object in the media- the media-specific MIB.
specific MIB.
The ATM LAN-Emulation Client MIB [ATMLANE] uses different indices and The ATM LAN-Emulation Client MIB [ATMLANE] uses different indices and
so does the IMA MIB [ATMIMA]. Looking at the examples we have, and so does the IMA MIB [ATMIMA]. Looking at the examples we have, and
the statements from RFC, it seems better to have two indices. This the statements from RFC, it seems better to have two indices. This
gives the SNMP agent implementor the freedom to manage their ifIndex gives the SNMP agent implementor the freedom to manage their ifIndex
in the way they like. in the way they like.
2.3.1.3. Mapping Between ifIndex and bundleIndex 2.3.1.3. Mapping Between ifIndex and mfrBundleIndex
The bundleIfIndexMappingTable is indexed by ifIndex and provides the The mfrBundleIfIndexMappingTable is indexed by ifIndex and provides
means to map a given ifIndex into the corresponding bundleIndex. The the means to map a given ifIndex into the corresponding
bundleIfIndexMapping object in the bundleTable (indexed by mfrBundleIndex. The mfrBundleIfIndexMapping object in the
bundleIndex) provides the reverse mapping of a bundleIndex to the mfrBundleTable (indexed by mfrBundleIndex) provides the reverse
corresponding ifIndex in the ifTable. mapping of a mfrBundleIndex to the corresponding ifIndex in the
ifTable.
2.3.1.4. ifTable Objects 2.3.1.4. ifTable Objects
The bundle configuration and status table. There is a one-to-one The bundle configuration and status table. There is a one-to-one
correspondence between a bundle and an interface represented in the correspondence between a bundle and an interface represented in the
ifTable. ifTable.
The following objects of the ifTable have specific meaning for an MFR The following objects of the ifTable have specific meaning for an MFR
bundle: bundle:
ifAdminStatus - the bundle admin status ifAdminStatus - the bundle admin status
ifOperStatus - the bundle operational status ifOperStatus - the bundle operational status
ifSpeed - the current bandwidth of the bundle ifSpeed - the current bandwidth of the bundle
ifInUcastPkts - the number of frames received on the bundle ifInUcastPkts - the number of frames received on the bundle
ifOutUcastPkts - the number of frames transmitted on the bundle ifOutUcastPkts - the number of frames transmitted on the bundle
ifInErrors - frame (not fragment) errors ifInErrors - frame (not fragment) errors
ifOutErrors - frame (not fragment) errors ifOutErrors - frame (not fragment) errors
The following objects of the ifTable have specific meaning for an MFR The following objects of the ifTable have specific meaning for an MFR
bundle link: bundle link:
ifAdminStatus - the bundle link admin status ifAdminStatus - the bundle link admin status
ifOperStatus - the bundle link operational status ifOperStatus - the bundle link operational status
ifSpeed - the bandwidth of the bundle link interface ifSpeed - the bandwidth of the bundle link interface
ifInUcastPkts - the number of frames received on the bundle link ifInUcastPkts - the number of frames received on the bundle link
ifOutUcastPkts - the number of frames transmitted on the bundle link ifOutUcastPkts - the number of frames transmitted on the bundle
ifInErrors - frame and fragment errors link
ifOutErrors - frame and fragment errors ifInErrors - frame and fragment errors
ifOutErrors - frame and fragment errors
2.3.2. Relationship With Interface Stack Table 2.3.2. Relationship With Interface Stack Table
The bundles and bundle links will appear in the ifStackTable defined The bundles and bundle links will appear in the ifStackTable defined
in RFC 2233 [RFC2233]. Each bundle link will appear a lower layer to in RFC 2863 [RFC2863]. Each bundle link will appear a lower layer to
its owner bundle. The bundle will appear as a higher layer to the its owner bundle. The bundle will appear as a higher layer to the
bundle links and as a lower layer to a frame relay service or UNI. bundle links and as a lower layer to a frame relay service or UNI.
2.3.3. Relationship With Frame Relay DTE MIB 2.3.3. Relationship With Frame Relay DTE MIB
The bundle will have a one-to-one correspondence with a DLCMI or UNI The bundle will have a one-to-one correspondence with a DLCMI or UNI
that appear in the DTE MIB tables [RFC2115]. that appear in the DTE MIB tables [RFC2115].
2.3.4. Relationship With Frame Relay Service MIB 2.3.4. Relationship With Frame Relay Service MIB
There is a one-to-one relationship between the MFR bundle and the There is a one-to-one relationship between the MFR bundle and the
frame relay service logical port defined in RFC1604 [RFC1604]. frame relay service logical port defined in RFC1604 [RFC1604].
2.3.5. Example 2.3.5. Example
Figure two shows an example of how the various tables are related. Figure two shows an example of how the various tables are related.
This example shows two bundles composed of 2 T1s each. The bundles This example shows two bundles composed of 2 T1s each. The bundles
have a bundleIndex of 10 and 20 respectively. have a mfrBundleIndex of 10 and 20 respectively.
+-------------------------+ +-------------------------+
| Frame Relay Service | | Frame Relay Service |
+-----+-------------+-----+ +-----+-------------+-----+
| | | |
+-----+------+------+-----+ +-----+------+------+-----+
| MFR Bundle | MFR Bundle | | MFR Bundle | MFR Bundle |
| 10 | 20 | | 10 | 20 |
+--+-----+---+---+-----+--+ +--+-----+---+---+-----+--+
| | | | | | | |
+-+-+ +-+-+ +-+-+ +-+-+ +-+-+ +-+-+ +-+-+ +-+-+
|T1 | |T1 | |T1 | |T1 | |T1 | |T1 | |T1 | |T1 |
+---+ +---+ +-+-+ +---+ +---+ +---+ +-+-+ +---+
Figure 2: Frame Relay Service Being Carried on 4 T1s Figure 2: Frame Relay Service Being Carried on 4 T1s
The assignment of the ifTable index values could for example be: The assignment of the ifTable index values could for example be:
ifIndex | Description | ifType ifIndex | Description | ifType
--------+----------------------------+---------------------- --------+----------------------------+----------------------
1 | FrameRelayService | frameRelayService(44) 1 | FrameRelayService | frameRelayService(44)
2 | MFR Bundle #10 | frf16MfrBundle(163) 2 | MFR Bundle #10 | frf16MfrBundle(163)
3 | MFR Bundle #20 | frf16MfrBundle(163) 3 | MFR Bundle #20 | frf16MfrBundle(163)
4 | ds1 #1/MFR Bundle Link #1 | ds1(18) 4 | ds1 #1/MFR Bundle Link #1 | ds1(18)
5 | ds1 #2/MFR Bundle Link #2 | ds1(18) 5 | ds1 #2/MFR Bundle Link #2 | ds1(18)
6 | ds1 #3/MFR Bundle Link #3 | ds1(18) 6 | ds1 #3/MFR Bundle Link #3 | ds1(18)
7 | ds1 #4/MFR Bundle Link #4 | ds1(18) 7 | ds1 #4/MFR Bundle Link #4 | ds1(18)
The ifStackTable is then used to show the relationships between the The ifStackTable is then used to show the relationships between the
various interfaces. various interfaces.
HigherLayer | LowerLayer HigherLayer | LowerLayer
------------+----------- ------------+-----------
0 | 1 0 | 1
1 | 2 1 | 2
1 | 3 1 | 3
2 | 4 2 | 4
2 | 5 2 | 5
3 | 6 3 | 6
3 | 7 3 | 7
4 | 0 4 | 0
5 | 0 5 | 0
6 | 0 6 | 0
7 | 0 7 | 0
The bundleIfIndexMappingTable shows the relationship between the The mfrBundleIfIndexMappingTable shows the relationship between the
ifTable ifIndex and the bundleIndex: ifTable ifIndex and the mfrBundleIndex:
ifIndex | bundleIfIndexMappingIndex ifIndex | mfrBundleIfIndexMappingIndex
--------+-------------------------- --------+-----------------------------
2 | 10 2 | 10
3 | 20 3 | 20
The bundleTable shows the relationship between the bundleIndex and The mfrBundleTable shows the relationship between the mfrBundleIndex
the ifIndex: and the ifIndex:
bundleIndex | bundleIfIndex mfrBundleIndex | mfrBundleIfIndex
-------------+-------------- ---------------+-----------------
10 | 2 10 | 2
20 | 3 20 | 3
The bundleLinkTable shows the relationship between the bundles and The mfrBundleLinkTable shows the relationship between the bundles and
bundle links: bundle links:
bundleIndex | bundleLinkIfIndex mfrBundleIndex | mfrBundleLinkIfIndex
------------+------------------ ---------------+---------------------
10 | 4 10 | 4
10 | 5 10 | 5
20 | 6 20 | 6
20 | 7 20 | 7
2.4. Creation Of Bundles and Bundle Links 2.4. Creation Of Bundles and Bundle Links
2.4.1. Creation Of Bundles 2.4.1. Creation Of Bundles
A new bundle is created by setting a createAndGo(4) value in the A new bundle is created by setting a createAndGo(4) value in the
bundleRowStatus RowStatus object. Optionally, an agent could also mfrBundleRowStatus RowStatus object. Optionally, an agent could also
support setting a value of createAndWait(5) followed by a set to the support setting a value of createAndWait(5) followed by a set to the
value active(1). value active(1).
When a bundle is created, the agent must create a new interface in When a bundle is created, the agent must create a new interface in
the ifTable. The ifIndex for this new interface is used for the the ifTable. The ifIndex for this new interface is used for the
value of bundleIfIndex. value of mfrBundleIfIndex.
2.4.2. Creation Of Bundle Links 2.4.2. Creation Of Bundle Links
A new bundle link is created by setting a createAndGo(4) value in the A new bundle link is created by setting a createAndGo(4) value in the
bundleLinkRowStatus RowStatus object. mfrBundleLinkRowStatus RowStatus object.
The bundle link is associated with a specific physical interface and The bundle link is associated with a specific physical interface and
uses the ifIndex of the physical interface. The bundleLinkEntry row uses the ifIndex of the physical interface. The mfrBundleLinkEntry
objects may be created after or during creation of the physical row objects may be created after or during creation of the physical
interface's ifEntry row objects. interface's ifEntry row objects.
The bundle identified in the object bundleIndex must exist at time of The bundle identified in the object mfrBundleIndex must exist at time
bundle link creation. of bundle link creation.
2.5. Notifications 2.5. Notifications
The linkUp and linkDown traps are defined in RFC 1573 [RFC1573]. The linkUp and linkDown traps are defined in RFC 2223 [RFC2223].
2.5.1. Bundle 2.5.1. Bundle
The following SNMP traps are defined for MFR bundles. The following SNMP traps are defined for MFR bundles.
2.5.1.1. linkUp 2.5.1.1. linkUp
This trap is sent when the ifOperStatus of a bundle transitions from This trap is sent when the ifOperStatus of a bundle transitions from
down to up. This occurs when a sufficient number of links down to up. This occurs when a sufficient number of links
(determined by bundleActivationClass and bundleThreshold) are in the (determined by mfrBundleActivationClass and mfrBundleThreshold) are
operationally up state. in the operationally up state.
2.5.1.2. linkDown 2.5.1.2. linkDown
This trap is sent when the ifOperStatus of a bundle transitions from This trap is sent when the ifOperStatus of a bundle transitions from
up to down. This occurs when a insufficient number of links up to down. This occurs when a insufficient number of links
(determined by bundleActivationClass and bundleThreshold) are in the (determined by mfrBundleActivationClass and mfrBundleThreshold) are
operationally up state. in the operationally up state.
2.5.2. Bundle Link 2.5.2. Bundle Link
The following SNMP traps are defined for MFR bundle links. The following SNMP traps are defined for MFR bundle links.
2.5.2.1. linkUp 2.5.2.1. linkUp
This trap is sent when a bundleLinkState object transitions to the This trap is sent when a mfrBundleLinkState object transitions to the
value bundleLinkStateUp. value mfrBundleLinkStateUp.
2.5.2.2. linkDown 2.5.2.2. linkDown
This trap is sent when a bundleLinkState object transitions from the This trap is sent when a mfrBundleLinkState object transitions from
value bundleLinkStateUp. the value mfrBundleLinkStateUp.
2.5.2.3. mfrMibTrapBundleLinkMismatch 2.5.2.3. mfrMibTrapBundleLinkMismatch
This trap indicates that a bundle link mismatch has been detected. This trap indicates that a bundle link mismatch has been detected.
The following objects are reported: The following objects are reported:
- bundleNearEndName: configured name of near end bundle - mfrBundleNearEndName: configured name of near end bundle
- bundleFarEndName: previously reported name of far - mfrBundleFarEndName: previously reported name of far
end bundle end bundle
- bundleLinkNearEndName: configured name of near end bundle - mfrBundleLinkNearEndName: configured name of near end bundle
- bundleLinkFarEndName: reported name of far end bundle - mfrBundleLinkFarEndName: reported name of far end bundle
- bundleLinkFarEndBundleName: currently reported name of far - mfrBundleLinkFarEndBundleName: currently reported name of far
end bundle end bundle
Note that the configured items may have been configured Note that the configured items may have been configured
automatically. Note also that the bundleLinkMismatch counter is automatically. Note also that the mfrBundleLinkMismatch counter is
incremented when the trap is sent. incremented when the trap is sent.
3. Object Definitions 3. Object Definitions
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to refer to the often use a textual string, termed the descriptor, to refer to the
object type. object type.
FRF16-MFR-MIB-EXP DEFINITIONS ::= BEGIN FR-MFR-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32,
NOTIFICATION-TYPE, experimental
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TestAndIncr, RowStatus
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
InterfaceIndex, ifIndex
FROM IF-MIB;
mfrMib MODULE-IDENTITY IMPORTS
LAST-UPDATED "0009050000Z" MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32,
ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" NOTIFICATION-TYPE, transmission
CONTACT-INFO FROM SNMPv2-SMI
"WG Charter: http://www.ietf.org/html.charters/frnetmib-charter.html TEXTUAL-CONVENTION, TestAndIncr, RowStatus
WG-email: frnetmib@sunroof.eng.sun.com FROM SNMPv2-TC
Subscribe: frnetmib-request@sunroof.eng.sun.com MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib FROM SNMPv2-CONF
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
InterfaceIndex, ifIndex
FROM IF-MIB;
Chair: Andy Malis mfrMib MODULE-IDENTITY
Lucent Technologies LAST-UPDATED "200011300000Z"
Email: Andy.Malis@vivacenetworks.com ORGANIZATION "IETF Frame Relay Service MIB (frnetmib)
Working Group"
CONTACT-INFO
"WG Charter:
http://www.ietf.org/html.charters/frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
WG editor: Prayson Pate Chair: Andy Malis
Overture Networks Vivace Networks
Email: prayson.pate@overturenetworks.com Email: Andy.Malis@vivacenetworks.com
Co-author: Bob Lynch WG editor: Prayson Pate
Larscom Incorporated Overture Networks
EMail: blynch@larscom.com Email: prayson.pate@overturenetworks.com
Co-author: Kenneth Rehbehn Co-author: Bob Lynch
Megisto Systems, Inc. Overture Networks
EMail: krehbehn@megisto.com"
DESCRIPTION EMail: bob.lynch@overturenetworks.com
"This is the MIB used to control and monitor the multilink frame
relay (MFR) function described in FRF.16. This was originally
submitted to the Frame Relay Forum as contribution FRFTC 99-151
and then updated as FRFTC 99-193."
-- --------------------------------------------------------- Co-author: Kenneth Rehbehn
-- --------------------------------------------------------- Megisto Systems, Inc.
-- Revision History EMail: krehbehn@megisto.com"
-- ---------------------------------------------------------
-- ---------------------------------------------------------
REVISION "0009050000Z" DESCRIPTION
DESCRIPTION "This is the MIB used to control and monitor the multilink
"Initial version of the FRF.16 UNI/NNI Multilink frame relay (MFR) function described in FRF.16."
Frame Relay MIB. Published as RFC [RFC-EDITOR: Enter RFC # here]."
REVISION "0009050000Z" -- ---------------------------------------------------------
DESCRIPTION -- ---------------------------------------------------------
"[RFC-EDITOR: Remove this and all following REVISION -- Revision History
statements prior to publication as an RFC] -- ---------------------------------------------------------
-- ---------------------------------------------------------
Changes after review by Dan Romascanu. REVISION "200011300000Z"
" DESCRIPTION
"Published as RFC 3020."
REVISION "0004040000Z" ::= { transmission 47 }
DESCRIPTION
"Changes from draft-ietf-frnetmib-mfrmib-01.txt from IETF-47:
o Fixed display of sample ifStackTable
o Changed bundleIfIndexMappingIndex from InterfaceIndex
to Integer32
"
REVISION "0003090000Z" -- ---------------------------------------------------------
DESCRIPTION -- ---------------------------------------------------------
"Changes from draft-ietf-frnetmib-mfrmib-00.txt -- Textual Conventions
o changed experimental number to IANA-approved 105. -- ---------------------------------------------------------
o changed interface type for frf16MfrBundle to IANA-approved 163. -- ---------------------------------------------------------
"
REVISION "9912061700Z" MfrBundleLinkState ::= TEXTUAL-CONVENTION
DESCRIPTION STATUS current
"Updates: DESCRIPTION
o changed name to draft-ietf-frnetmib-mfrmib-00 "The possible states for a bundle link, as defined in
o updated text to match last MIB revisions Annex A of FRF.16."
o corrected description of bundleIfIndexMappingTable REFERENCE "FRF.16 Annex A"
o added objects to show configured and current bundle links. SYNTAX INTEGER {
" mfrBundleLinkStateAddSent (1),
mfrBundleLinkStateAddRx (2),
mfrBundleLinkStateAddAckRx (3),
mfrBundleLinkStateUp (4),
mfrBundleLinkStateIdlePending (5),
mfrBundleLinkStateIdle (6),
mfrBundleLinkStateDown (7),
mfrBundleLinkStateDownIdle (8)
}
REVISION "9910212020Z" -- ---------------------------------------------------------
DESCRIPTION -- ---------------------------------------------------------
"Updated after comments from Michael Allen and Ken Rehben. -- Object Identifiers
o corrected options for sequence number length -- ---------------------------------------------------------
o changed frf16Mfr prefix to mfr -- ---------------------------------------------------------
o created a sub-group for scalars
o created an entry in the bundleTable for maximum links per bundle
o changed indices to not-accessible
o changed DisplayString to SnmpAdminString
o updated some of the object descriptions
o added a -EXP to the name of the MIB
o added some DEFVAL and REFERENCE clauses"
REVISION "9910151300Z" mfrMibScalarObjects OBJECT IDENTIFIER ::= { mfrMib 1 }
DESCRIPTION mfrMibBundleObjects OBJECT IDENTIFIER ::= { mfrMib 2 }
"Updated after review at the October meeting in Huntsville: mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMib 3 }
o removed log table mfrMibTraps OBJECT IDENTIFIER ::= { mfrMib 4 }
o removed several columns from each table mfrMibConformance OBJECT IDENTIFIER ::= { mfrMib 5 }
o combined configuration, status and error tables into
one table each for bundles and bundle links
o added new objects for
- maximum number of bundles
- maximum fragment size
- size of sequence number
o added notifications
o added conformance information"
REVISION "9910011440Z" mfrMibTrapsPrefix OBJECT IDENTIFIER ::= { mfrMibTraps 0 }
DESCRIPTION
"The initial version of this MIB was originally submitted
to the Frame Relay Forum October 1999 meeting in Huntsville
as FRFTC/99-151."
::= { experimental 105 } mfrMibGroups OBJECT IDENTIFIER ::= { mfrMibConformance 1 }
mfrMibCompliances OBJECT IDENTIFIER ::= { mfrMibConformance 2 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Textual Conventions -- Scalars
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
BundleLinkState ::= TEXTUAL-CONVENTION mfrBundleMaxNumBundles OBJECT-TYPE
STATUS current SYNTAX Integer32
DESCRIPTION MAX-ACCESS read-only
"The possible states for a bundle link, as defined in STATUS current
Annex A of FRF.16." DESCRIPTION
REFERENCE "FRF.16 Annex A" "This object is used to inform the manager of the
SYNTAX INTEGER { maximum number of bundles supported by this device."
bundleLinkStateAddSent (1), ::= { mfrMibScalarObjects 1 }
bundleLinkStateAddRx (2),
bundleLinkStateAddAckRx (3),
bundleLinkStateUp (4),
bundleLinkStateIdlePending (5),
bundleLinkStateIdle (6),
bundleLinkStateDown (7),
bundleLinkStateDownIdle (8)
}
-- --------------------------------------------------------- mfrBundleNextIndex OBJECT-TYPE
-- --------------------------------------------------------- SYNTAX TestAndIncr
-- Object Identifers MAX-ACCESS read-write
-- --------------------------------------------------------- STATUS current
-- --------------------------------------------------------- DESCRIPTION
"This object is used to assist the manager in
selecting a value for mfrBundleIndex during row creation
in the mfrBundleTable. It can also be used to avoid race
conditions with multiple managers trying to create
rows in the table (see RFC 2494 [RFC2494] for one such
alogrithm)."
REFERENCE "RFC 2494"
::= { mfrMibScalarObjects 2 }
mfrMibObjects OBJECT IDENTIFIER ::= { mfrMib 1 } -- ---------------------------------------------------------
mfrMibTraps OBJECT IDENTIFIER ::= { mfrMib 2 } -- ---------------------------------------------------------
mfrMibConformance OBJECT IDENTIFIER ::= { mfrMib 3 } -- Bundle Table
-- ---------------------------------------------------------
-- ---------------------------------------------------------
mfrBundleTable OBJECT-TYPE
SYNTAX SEQUENCE OF MfrBundleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The bundle configuration and status table. There
is a one-to-one correspondence between a bundle
and an interface represented in the ifTable.
mfrMibScalarObjects OBJECT IDENTIFIER ::= { mfrMibObjects 1 } The following objects of the ifTable have specific
mfrMibBundleObjects OBJECT IDENTIFIER ::= { mfrMibObjects 2 } meaning for an MFR bundle:
mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMibObjects 3 } ifAdminStatus - the bundle admin status
ifOperStatus - the bundle operational status
ifSpeed - the current bandwidth of the bundle
ifInUcastPkts - the number of frames received
on the bundle
ifOutUcastPkts - the number of frames transmitted
on the bundle
ifInErrors - frame (not fragment) errors
ifOutErrors - frame (not fragment) errors
"
::= { mfrMibBundleObjects 3 }
mfrMibTrapsPrefix OBJECT IDENTIFIER ::= { mfrMibTraps 0 } mfrBundleEntry OBJECT-TYPE
SYNTAX MfrBundleEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the bundle table."
INDEX { mfrBundleIndex }
::= { mfrBundleTable 1 }
mfrMibGroups OBJECT IDENTIFIER ::= { mfrMibConformance 1 } MfrBundleEntry ::=
mfrMibCompliances OBJECT IDENTIFIER ::= { mfrMibConformance 2 } SEQUENCE {
mfrBundleIndex
Integer32,
mfrBundleIfIndex
InterfaceIndex,
mfrBundleRowStatus
RowStatus,
mfrBundleNearEndName
SnmpAdminString,
mfrBundleFragmentation
INTEGER,
mfrBundleMaxFragSize
Integer32,
mfrBundleTimerHello
INTEGER,
-- --------------------------------------------------------- mfrBundleTimerAck
-- --------------------------------------------------------- INTEGER,
-- Scalars mfrBundleCountMaxRetry
-- --------------------------------------------------------- INTEGER,
-- --------------------------------------------------------- mfrBundleActivationClass
INTEGER,
mfrBundleThreshold
Integer32,
mfrBundleMaxDiffDelay
Integer32,
mfrBundleSeqNumSize
INTEGER,
mfrBundleMaxBundleLinks
Integer32,
mfrBundleLinksConfigured
Integer32,
mfrBundleLinksActive
Integer32,
mfrBundleBandwidth
Integer32,
mfrBundleFarEndName
SnmpAdminString,
mfrBundleResequencingErrors
Counter32
}
bundleMaxNumBundles OBJECT-TYPE mfrBundleIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to inform the manager of the "The index into the table. While this corresponds
maximum number of bundles supported by this device." to an entry in the ifTable, the value of mfrBundleIndex
::= { mfrMibScalarObjects 1 } need not match that of the ifIndex in the ifTable.
A manager can use mfrBundleNextIndex to select a unique
mfrBundleIndex for creating a new row."
::= { mfrBundleEntry 1 }
bundleNextIndex OBJECT-TYPE mfrBundleIfIndex OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX InterfaceIndex
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to assist the manager in "The value must match an entry in the interface
selecting a value for bundleIndex during row creation table whose ifType must be set to frf16MfrBundle(163).
in the bundleTable. It can also be used to avoid race
conditions with multiple managers trying to create
rows in the table (see RFC 2494 [RFC2494] for one such
alogrithm)."
REFERENCE "RFC 2494"
::= { mfrMibScalarObjects 2 }
-- --------------------------------------------------------- For example: if the value of mfrBundleIfIndex is 10,
-- --------------------------------------------------------- then a corresponding entry should be present in
-- Bundle Table the ifTable with an index of 10 and an ifType of 163."
-- --------------------------------------------------------- ::= { mfrBundleEntry 2 }
-- ---------------------------------------------------------
bundleTable OBJECT-TYPE mfrBundleRowStatus OBJECT-TYPE
SYNTAX SEQUENCE OF BundleEntry SYNTAX RowStatus
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundle configuration and status table. There "The mfrBundleRowStatus object allows create, change,
is a one-to-one correspondence between a bundle and delete operations on bundle entries."
and an interface represented in the ifTable. REFERENCE "RFC 1903"
::= { mfrBundleEntry 3 }
The following objects of the ifTable have specific mfrBundleNearEndName OBJECT-TYPE
meaning for an MFR bundle: SYNTAX SnmpAdminString
ifAdminStatus - the bundle admin status MAX-ACCESS read-create
ifOperStatus - the bundle operational status STATUS current
ifSpeed - the current bandwidth of the bundle DESCRIPTION
ifInUcastPkts - the number of frames received "The configured name of the bundle."
on the bundle REFERENCE "FRF.16 section 3.4.1"
ifOutUcastPkts - the number of frames transmitted ::= { mfrBundleEntry 4 }
on the bundle
ifInErrors - frame (not fragment) errors
ifOutErrors - frame (not fragment) errors
"
::= { mfrMibBundleObjects 3 }
bundleEntry OBJECT-TYPE mfrBundleFragmentation OBJECT-TYPE
SYNTAX BundleEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible enable (1),
STATUS current disable (2)
DESCRIPTION }
"An entry in the bundle table." MAX-ACCESS read-create
INDEX { bundleIndex } STATUS current
::= { bundleTable 1 } DESCRIPTION
"Controls whether the bundle performs/accepts
fragmentation and re-assembly. The possible
values are:
BundleEntry ::= enable(1) - Bundle links will fragment frames
SEQUENCE {
bundleIndex
Integer32,
bundleIfIndex
InterfaceIndex,
bundleRowStatus
RowStatus,
bundleNearEndName
SnmpAdminString,
bundleFragmentation
INTEGER,
bundleMaxFragSize
Integer32,
bundleTimerHello
INTEGER,
bundleTimerAck
INTEGER,
bundleCountMaxRetry
INTEGER,
bundleActivationClass
INTEGER,
bundleThreshold
Integer32,
bundleMaxDiffDelay
Integer32,
bundleSeqNumSize
INTEGER,
bundleMaxBundleLinks
Integer32,
bundleLinksConfigured
Integer32,
bundleLinksActive
Integer32,
bundleBandwidth
Integer32,
bundleFarEndName
SnmpAdminString,
bundleResequencingErrors
Counter32
}
bundleIndex OBJECT-TYPE disable(2) - Bundle links will not fragment
SYNTAX Integer32 (1..2147483647) frames."
MAX-ACCESS not-accessible DEFVAL { disable }
STATUS current ::= { mfrBundleEntry 5 }
DESCRIPTION
"The index into the table. While this corresponds
to an entry in the ifTable, the value of bundleIndex
need not match that of the ifIndex in the ifTable.
A manager can use bundleNextIndex to select a unique
bundleIndex for creating a new row."
::= { bundleEntry 1 }
bundleIfIndex OBJECT-TYPE mfrBundleMaxFragSize OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX Integer32 (-1..8184)
MAX-ACCESS read-only UNITS "Octets"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"The value must match an entry in the interface DESCRIPTION
table whose ifType must be set to frf16MfrBundle(163). "The maximum fragment size supported. Note that this
is only valid if mfrBundleFragmentation is set to enable(1).
For example: if the value of bundleIfIndex is 10, Zero is not a valid fragment size.
then a corresponding entry should be present in
the ifTable with an index of 10 and an ifType of 163."
::= { bundleEntry 2 }
bundleRowStatus OBJECT-TYPE A bundle that does not support fragmentation must return
SYNTAX RowStatus this object with a value of -1."
MAX-ACCESS read-create DEFVAL { -1 }
STATUS current ::= { mfrBundleEntry 6 }
DESCRIPTION
"The bundleRowStatus object allows create, change,
and delete operations on bundle entries."
REFERENCE "RFC 1903"
::= { bundleEntry 3 }
bundleNearEndName OBJECT-TYPE mfrBundleTimerHello OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX INTEGER (1..180)
MAX-ACCESS read-create UNITS "Seconds"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"The configured name of the bundle." DESCRIPTION
REFERENCE "FRF.16 section 3.4.1" "The configured MFR Hello Timer value."
::= { bundleEntry 4 } REFERENCE "FRF.16 section 4.3.8.1"
DEFVAL { 10 }
::= { mfrBundleEntry 7 }
bundleFragmentation OBJECT-TYPE mfrBundleTimerAck OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER (1..10)
enable (1), UNITS "Seconds"
disable (2) MAX-ACCESS read-create
} STATUS current
MAX-ACCESS read-create DESCRIPTION
STATUS current "The configured MFR T_ACK value."
DESCRIPTION REFERENCE "FRF.16 section 4.3.8.2"
"Controls whether the bundle performs/accepts DEFVAL { 4 }
fragmentation and re-assembly. The possible ::= { mfrBundleEntry 8 }
values are:
enable(1) - Bundle links will fragment frames mfrBundleCountMaxRetry OBJECT-TYPE
SYNTAX INTEGER (1..5)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The MFR N_MAX_RETRY value."
REFERENCE "FRF.16 section 4.3.8.3"
DEFVAL { 2 }
::= { mfrBundleEntry 9 }
disable(2) - Bundle links will not fragment mfrBundleActivationClass OBJECT-TYPE
frames." SYNTAX INTEGER {
DEFVAL { disable } mfrBundleActivationClassA (1),
::= { bundleEntry 5 } mfrBundleActivationClassB (2),
mfrBundleActivationClassC (3),
mfrBundleActivationClassD (4)
}
bundleMaxFragSize OBJECT-TYPE MAX-ACCESS read-create
SYNTAX Integer32 (-1..8184) STATUS current
UNITS "Octets" DESCRIPTION
MAX-ACCESS read-create "Controls the conditions under which the bundle is activated.
STATUS current The following settings are available:
DESCRIPTION
"The maximum fragment size supported. Note that this
is only valid if bundleFragmentation is set to enable(1).
Zero is not a valid fragment size. mfrBundleActivationClassA(1) - at least one must link up
mfrBundleActivationClassB(2) - all links must be up
mfrBundleActivationClassC(3) - a certain number must be
up. Refer to
mfrBundleThreshold for
the required number.
mfrBundleActivationClassD(4) - custom (implementation
specific)."
REFERENCE "FRF.16 section 4.2.2.1"
DEFVAL { mfrBundleActivationClassA }
::= { mfrBundleEntry 10 }
A bundle that does not support fragmentation must be mfrBundleThreshold OBJECT-TYPE
set to -1." SYNTAX Integer32 (-1..2147483647)
DEFVAL { -1 } UNITS "Bundle Links"
::= { bundleEntry 6 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the number of links that must be in operational
'up' state before the bundle will transition to an
operational up/active state. If the number of
operational 'up' links falls below this value,
then the bundle will transition to an inactive
state.
bundleTimerHello OBJECT-TYPE Note - this is only valid when mfrBundleActivationClass
SYNTAX INTEGER (1..180) is set to mfrBundleActivationClassC or, depending upon the
UNITS "Seconds" implementation, to mfrBundleActivationClassD. A bundle that
MAX-ACCESS read-create is not set to one of these must return this object with a
STATUS current value of -1."
DESCRIPTION REFERENCE "FRF.16 section 4.2.2.1"
"The configured MFR Hello Timer value." DEFVAL { -1 }
REFERENCE "FRF.16 section 4.3.8.1" ::= { mfrBundleEntry 11 }
DEFVAL { 10 }
::= { bundleEntry 7 }
bundleTimerAck OBJECT-TYPE mfrBundleMaxDiffDelay OBJECT-TYPE
SYNTAX INTEGER (1..10) SYNTAX Integer32 (-1..2147483647)
UNITS "Seconds" UNITS "Milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured MFR T_ACK value." "The maximum delay difference between the bundle
REFERENCE "FRF.16 section 4.3.8.2" links.
DEFVAL { 4 }
::= { bundleEntry 8 }
bundleCountMaxRetry OBJECT-TYPE A value of -1 indicates that this object does not contain
SYNTAX INTEGER (1..5) a valid value"
MAX-ACCESS read-create DEFVAL { -1 }
STATUS current ::= { mfrBundleEntry 12 }
DESCRIPTION
"The MFR N_MAX_RETRY value."
REFERENCE "FRF.16 section 4.3.8.3"
DEFVAL { 2 }
::= { bundleEntry 9 }
bundleActivationClass OBJECT-TYPE mfrBundleSeqNumSize OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bundleActivationClassA (1), seqNumSize12bit (1),
bundleActivationClassB (2), seqNumSize24bit (2)
bundleActivationClassC (3),
bundleActivationClassD (4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Controls the conditions under which the bundle is activated. "Controls whether the standard FRF.12 12-bit
The following settings are available: sequence number is used or the optional 24-bit
sequence number."
bundleActivationClassA(1) - at least one must link up REFERENCE "FRFTC/99-194"
bundleActivationClassB(2) - all links must be up DEFVAL { seqNumSize12bit }
bundleActivationClassC(3) - a certain number must be up. ::= { mfrBundleEntry 13 }
Refer to bundleThreshold for
the required number.
bundleActivationClassD(4) - custom (implementation
specific)."
REFERENCE "FRF.16 section 4.2.2.1"
DEFVAL { bundleActivationClassA }
::= { bundleEntry 10 }
bundleThreshold OBJECT-TYPE
SYNTAX Integer32
UNITS "Bundle Links"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the number of links that must be in operational
'up' state before the bundle will transition to an
operational up/active state. If the number of
operational 'up' links falls below this value,
then the bundle will transition to an inactive
state.
Note - this is only valid when bundleActivationClass mfrBundleMaxBundleLinks OBJECT-TYPE
is set to bundleActivationClassC or, depending upon the SYNTAX Integer32 (1..2147483647)
implementation, to bundleActivationClassD." UNITS "Bundle Links"
REFERENCE "FRF.16 section 4.2.2.1" MAX-ACCESS read-only
DEFVAL { -1 } STATUS current
::= { bundleEntry 11 } DESCRIPTION
"The maximum number of bundle links supported for
this bundle."
::= { mfrBundleEntry 14 }
bundleMaxDiffDelay OBJECT-TYPE mfrBundleLinksConfigured OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
UNITS "Milliseconds" UNITS "Bundle Links"
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum delay difference between the bundle "The number of links configured for the bundle."
links." ::= { mfrBundleEntry 15 }
DEFVAL { -1 }
::= { bundleEntry 12 }
bundleSeqNumSize OBJECT-TYPE mfrBundleLinksActive OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (-1..2147483647)
seqNumSize12bit (1), UNITS "Bundle Links"
seqNumSize24bit (2) MAX-ACCESS read-only
} STATUS current
MAX-ACCESS read-create DESCRIPTION
STATUS current "The number of links that are active."
DESCRIPTION ::= { mfrBundleEntry 16 }
"Controls whether the standard FRF.12 12-bit
sequence number is used or the optional 24-bit
sequence number."
REFERENCE "FRFTC/99-194"
DEFVAL { seqNumSize12bit }
::= { bundleEntry 13 }
bundleMaxBundleLinks OBJECT-TYPE mfrBundleBandwidth OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Bundle Links" UNITS "Bits/Sec"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of bundle links supported for this bundle." "The amount of available bandwidth on the bundle"
::= { bundleEntry 14 } ::= { mfrBundleEntry 17 }
bundleLinksConfigured OBJECT-TYPE
SYNTAX Integer32
UNITS "Bundle Links"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of links configured for the bundle."
::= { bundleEntry 15 }
bundleLinksActive OBJECT-TYPE
SYNTAX Integer32
UNITS "Bundle Links"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of links that are active."
::= { bundleEntry 16 }
bundleBandwidth OBJECT-TYPE mfrBundleFarEndName OBJECT-TYPE
SYNTAX Integer32 SYNTAX SnmpAdminString
UNITS "Bits/Sec" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "Name of the bundle received from the far end."
"The amount of available bandwidth on the bundle" REFERENCE "FRF.16 section 3.4.1"
::= { bundleEntry 17 } ::= { mfrBundleEntry 18 }
bundleFarEndName OBJECT-TYPE mfrBundleResequencingErrors OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX Counter32
MAX-ACCESS read-only UNITS "Error Events"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"Name of the bundle received from the far end." DESCRIPTION
REFERENCE "FRF.16 section 3.4.1" "A count of the number of resequencing errors. Each event
::= { bundleEntry 18 } may correspond to multiple lost frames. Example:
Say sequence number 56, 59 and 60 is received for DLCI 100.
It is decided by some means that sequence 57 and 58 is lost.
This counter should then be incremented by ONE, even though
two frames were lost."
::= { mfrBundleEntry 19 }
bundleResequencingErrors OBJECT-TYPE -- ---------------------------------------------------------
SYNTAX Counter32 -- ---------------------------------------------------------
UNITS "Error Events" -- ifIndex Mapping to Bundle Index Table
MAX-ACCESS read-only -- ---------------------------------------------------------
STATUS current -- ---------------------------------------------------------
DESCRIPTION
"A count of the number of resequncing errors. Each event
may correspond to multiple lost frames. Example:
Say sequence number 56, 59 and 60 is received for DLCI 100.
It is decided by some means that sequence 57 and 58 is lost.
This counter should then be incremented by ONE, even though
two frames were lost."
::= { bundleEntry 19 }
-- --------------------------------------------------------- mfrBundleIfIndexMappingTable OBJECT-TYPE
-- --------------------------------------------------------- SYNTAX SEQUENCE OF MfrBundleIfIndexMappingEntry
-- ifIndex Mapping to Bundle Index Table MAX-ACCESS not-accessible
-- --------------------------------------------------------- STATUS current
-- --------------------------------------------------------- DESCRIPTION
"A table mapping the values of ifIndex to the
mfrBundleIndex. This is required in order to find
the mfrBundleIndex given an ifIndex. The mapping of
mfrBundleIndex to ifIndex is provided by the
mfrBundleIfIndex entry in the mfrBundleTable."
bundleIfIndexMappingTable OBJECT-TYPE ::= { mfrMibBundleObjects 4 }
SYNTAX SEQUENCE OF BundleIfIndexMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table mapping the values of ifIndex to the
bundleIndex. This is required in order to find
the bundleIndex given an ifIndex. The mapping of
bundleIndex to ifIndex is provided by the bundleIfIndex
entry in the bundleTable."
::= { mfrMibBundleObjects 4 }
bundleIfIndexMappingEntry OBJECT-TYPE mfrBundleIfIndexMappingEntry OBJECT-TYPE
SYNTAX BundleIfIndexMappingEntry SYNTAX MfrBundleIfIndexMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row describes one ifIndex to bundleIndex mapping." "Each row describes one ifIndex to mfrBundleIndex mapping."
INDEX { ifIndex } INDEX { ifIndex }
::= { bundleIfIndexMappingTable 1 } ::= { mfrBundleIfIndexMappingTable 1 }
BundleIfIndexMappingEntry ::= MfrBundleIfIndexMappingEntry ::=
SEQUENCE { SEQUENCE {
bundleIfIndexMappingIndex mfrBundleIfIndexMappingIndex
Integer32 Integer32
} }
bundleIfIndexMappingIndex OBJECT-TYPE mfrBundleIfIndexMappingIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundleIndex of the given ifIndex." "The mfrBundleIndex of the given ifIndex."
::= { bundleIfIndexMappingEntry 2 } ::= { mfrBundleIfIndexMappingEntry 2 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Bundle Link Table -- Bundle Link Table
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
bundleLinkTable OBJECT-TYPE mfrBundleLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF BundleLinkEntry SYNTAX SEQUENCE OF MfrBundleLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundle link configuration and status table. There "The bundle link configuration and status table. There
is a one-to-one correspondence between a bundle link is a one-to-one correspondence between a bundle link
and a physical interface represented in the ifTable. The and a physical interface represented in the ifTable. The
ifIndex of the physical interface is used to index the ifIndex of the physical interface is used to index the
bundle link table, and to create rows. bundle link table, and to create rows.
The following objects of the ifTable have specific The following objects of the ifTable have specific
meaning for an MFR bundle link: meaning for an MFR bundle link:
ifAdminStatus - the bundle link admin status ifAdminStatus - the bundle link admin status
ifOperStatus - the bundle link operational ifOperStatus - the bundle link operational
status status
ifSpeed - the bandwidth of the bundle
link interface
ifInUcastPkts - the number of frames received
on the bundle link
ifOutUcastPkts - the number of frames transmitted
on the bundle link
ifInErrors - frame and fragment errors
ifOutErrors - frame and fragment errors"
::= { mfrMibBundleLinkObjects 1 }
bundleLinkEntry OBJECT-TYPE ifSpeed - the bandwidth of the bundle
SYNTAX BundleLinkEntry link interface
MAX-ACCESS not-accessible ifInUcastPkts - the number of frames received
STATUS current on the bundle link
DESCRIPTION ifOutUcastPkts - the number of frames transmitted
"An entry in the bundle link table." on the bundle link
INDEX { ifIndex } ifInErrors - frame and fragment errors
::= { bundleLinkTable 1 } ifOutErrors - frame and fragment errors"
::= { mfrMibBundleLinkObjects 1 }
BundleLinkEntry ::= mfrBundleLinkEntry OBJECT-TYPE
SEQUENCE { SYNTAX MfrBundleLinkEntry
bundleLinkRowStatus MAX-ACCESS not-accessible
RowStatus, STATUS current
bundleLinkConfigBundleIndex DESCRIPTION
Integer32, "An entry in the bundle link table."
bundleLinkNearEndName INDEX { ifIndex }
SnmpAdminString, ::= { mfrBundleLinkTable 1 }
bundleLinkState
BundleLinkState,
bundleLinkFarEndName
SnmpAdminString,
bundleLinkFarEndBundleName
SnmpAdminString,
bundleLinkDelay
Integer32,
bundleLinkFramesControlTx
Counter32,
bundleLinkFramesControlRx
Counter32,
bundleLinkFramesControlInvalid
Counter32,
bundleLinkTimerExpiredCount
Counter32,
bundleLinkLoopbackSuspected
Counter32,
bundleLinkUnexpectedSequence
Counter32,
bundleLinkMismatch MfrBundleLinkEntry ::=
Counter32 SEQUENCE {
} mfrBundleLinkRowStatus
RowStatus,
mfrBundleLinkConfigBundleIndex
Integer32,
mfrBundleLinkNearEndName
SnmpAdminString,
mfrBundleLinkState
MfrBundleLinkState,
mfrBundleLinkFarEndName
SnmpAdminString,
mfrBundleLinkFarEndBundleName
SnmpAdminString,
mfrBundleLinkDelay
Integer32,
mfrBundleLinkFramesControlTx
Counter32,
mfrBundleLinkFramesControlRx
Counter32,
mfrBundleLinkFramesControlInvalid
Counter32,
mfrBundleLinkTimerExpiredCount
Counter32,
mfrBundleLinkLoopbackSuspected
Counter32,
mfrBundleLinkUnexpectedSequence
Counter32,
mfrBundleLinkMismatch
Counter32
}
bundleLinkRowStatus OBJECT-TYPE mfrBundleLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundleLinkRowStatus object allows create, change, "The mfrBundleLinkRowStatus object allows create, change,
and delete operations on bundleLink entries. and delete operations on mfrBundleLink entries.
The create operation must fail if no physical interface The create operation must fail if no physical interface
is associated with the bundle link." is associated with the bundle link."
::= { bundleLinkEntry 1 } ::= { mfrBundleLinkEntry 1 }
bundleLinkConfigBundleIndex OBJECT-TYPE mfrBundleLinkConfigBundleIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundleLinkConfigBundleIndex object allows "The mfrBundleLinkConfigBundleIndex object allows
the manager to control the bundle to which the bundle the manager to control the bundle to which the bundle
link is assigned. If no value were in this field, then link is assigned. If no value were in this field, then
the bundle would remain in NOT_READY rowStatus and be the bundle would remain in NOT_READY rowStatus and be
unable to go to active. With an appropriate bundleIndex unable to go to active. With an appropriate mfrBundleIndex
in this field, then we could put the bundleLink row in in this field, then we could put the mfrBundleLink row in
NOT_IN_SERVICE or ACTIVE rowStatus." NOT_IN_SERVICE or ACTIVE rowStatus."
::= { bundleLinkEntry 2 } ::= { mfrBundleLinkEntry 2 }
bundleLinkNearEndName OBJECT-TYPE mfrBundleLinkNearEndName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured bundle link name that is sent to the far end." "The configured bundle link name that is sent to the far end."
::= { bundleLinkEntry 3 } ::= { mfrBundleLinkEntry 3 }
bundleLinkState OBJECT-TYPE mfrBundleLinkState OBJECT-TYPE
SYNTAX BundleLinkState SYNTAX MfrBundleLinkState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current bundle link state as defined by the MFR protocol "Current bundle link state as defined by the MFR protocol
described in Annex A of FRF.16." described in Annex A of FRF.16."
REFERENCE "FRF.16 Annex A" REFERENCE "FRF.16 Annex A"
::= { bundleLinkEntry 4 } ::= { mfrBundleLinkEntry 4 }
bundleLinkFarEndName OBJECT-TYPE mfrBundleLinkFarEndName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Name of bundle link received from far end." "Name of bundle link received from far end."
REFERENCE "FRF.16 section 3.4.2" REFERENCE "FRF.16 section 3.4.2"
::= { bundleLinkEntry 5 } ::= { mfrBundleLinkEntry 5 }
bundleLinkFarEndBundleName OBJECT-TYPE mfrBundleLinkFarEndBundleName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Name of far end bundle for this link received from far end." "Name of far end bundle for this link received from far end."
REFERENCE "FRF.16 section 3.4.1" REFERENCE "FRF.16 section 3.4.1"
::= { bundleLinkEntry 6 } ::= { mfrBundleLinkEntry 6 }
bundleLinkDelay OBJECT-TYPE mfrBundleLinkDelay OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (-1..2147483647)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current round-trip delay for this bundle link. The value -1 "Current round-trip delay for this bundle link. The
is returned when an implementation does not support measurement value -1 is returned when an implementation does not
of the bundle link delay." support measurement of the bundle link delay."
REFERENCE "FRF.16 section 3.4.4" REFERENCE "FRF.16 section 3.4.4"
::= { bundleLinkEntry 7 } ::= { mfrBundleLinkEntry 7 }
bundleLinkFramesControlTx OBJECT-TYPE mfrBundleLinkFramesControlTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Frames" UNITS "Frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of MFR control frames sent." "Number of MFR control frames sent."
REFERENCE "FRF.16 section 3.2" REFERENCE "FRF.16 section 3.2"
::= { bundleLinkEntry 8 } ::= { mfrBundleLinkEntry 8 }
bundleLinkFramesControlRx OBJECT-TYPE mfrBundleLinkFramesControlRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Frames" UNITS "Frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of valid MFR control frames received." "Number of valid MFR control frames received."
REFERENCE "FRF.16 section 3.2" REFERENCE "FRF.16 section 3.2"
::= { bundleLinkEntry 9 } ::= { mfrBundleLinkEntry 9 }
bundleLinkFramesControlInvalid OBJECT-TYPE mfrBundleLinkFramesControlInvalid OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Frames" UNITS "Frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of invalid MFR control frames received." "The number of invalid MFR control frames received."
REFERENCE "FRF.16 section 3.2" REFERENCE "FRF.16 section 3.2"
::= { bundleLinkEntry 10 } ::= { mfrBundleLinkEntry 10 }
bundleLinkTimerExpiredCount OBJECT-TYPE mfrBundleLinkTimerExpiredCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Timer Expiration Events" UNITS "Timer Expiration Events"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of times the T_HELLO or T_ACK timers expired." "Number of times the T_HELLO or T_ACK timers expired."
REFERENCE "FRF.16 section 4.3.8.1 and 4.3.8.2" REFERENCE "FRF.16 section 4.3.8.1 and 4.3.8.2"
::= { bundleLinkEntry 11 } ::= { mfrBundleLinkEntry 11 }
bundleLinkLoopbackSuspected OBJECT-TYPE mfrBundleLinkLoopbackSuspected OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Loopback Suspected Events" UNITS "Loopback Suspected Events"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times a loopback has been suspected "The number of times a loopback has been suspected
(based upon the use of magic numbers)." (based upon the use of magic numbers)."
REFERENCE "FRF.16 section 4.3.7" REFERENCE "FRF.16 section 4.3.7"
::= { bundleLinkEntry 12 } ::= { mfrBundleLinkEntry 12 }
bundleLinkUnexpectedSequence OBJECT-TYPE mfrBundleLinkUnexpectedSequence OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Frames" UNITS "Frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of data MFR frames discarded because the sequence "The number of data MFR frames discarded because the sequence
number of the frame for a DLCI was less than (delayed frame) number of the frame for a DLCI was less than (delayed frame)
or equal to (duplicate frame) the one expected for that DLCI. or equal to (duplicate frame) the one expected for that DLCI.
Example: Example:
Say frames with sequence numbers 56, 58, 59 is received for Say frames with sequence numbers 56, 58, 59 is received for
DLCI 100. While waiting for sequence number 57 another frame DLCI 100. While waiting for sequence number 57 another frame
with sequence number 58 arrives. Frame 58 is discarded and with sequence number 58 arrives. Frame 58 is discarded and
the counter is incremented." the counter is incremented."
REFERENCE "FRF.16 section 4.2.3.2" REFERENCE "FRF.16 section 4.2.3.2"
::= { bundleLinkEntry 13 } ::= { mfrBundleLinkEntry 13 }
bundleLinkMismatch OBJECT-TYPE mfrBundleLinkMismatch OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Bundle Name Mismatch Events" UNITS "Bundle Name Mismatch Events"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times that the unit has been notified by the "The number of times that the unit has been notified by the
remote peer that the bundle name is inconsistent with other remote peer that the bundle name is inconsistent with other
bundle links attached to the far-end bundle." bundle links attached to the far-end bundle."
REFERENCE "FRF.16 section 4.3.2.4" REFERENCE "FRF.16 section 4.3.2.4"
::= { bundleLinkEntry 14 } ::= { mfrBundleLinkEntry 14 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Notifications/Traps -- Notifications/Traps
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE
OBJECTS { OBJECTS {
bundleNearEndName, mfrBundleNearEndName,
bundleFarEndName, mfrBundleFarEndName,
bundleLinkNearEndName, mfrBundleLinkNearEndName,
bundleLinkFarEndName, mfrBundleLinkFarEndName,
bundleLinkFarEndBundleName mfrBundleLinkFarEndBundleName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap indicates that a bundle link mismatch has "This trap indicates that a bundle link mismatch has
been detected. The following objects are reported: been detected. The following objects are reported:
bundleNearEndName: configured name of near end bundle mfrBundleNearEndName: configured name of near end bundle
bundleFarEndName: previously reported name of mfrBundleFarEndName: previously reported name of
far end bundle far end bundle
bundleLinkNearEndName: configured name of near end bundle mfrBundleLinkNearEndName: configured name of near end bundle
bundleLinkFarEndName: reported name of far end bundle mfrBundleLinkFarEndName: reported name of far end bundle
bundleLinkFarEndBundleName: currently reported name of mfrBundleLinkFarEndBundleName: currently reported name of
far end bundle far end bundle
Note: that the configured items may have been configured Note: that the configured items may have been configured
automatically. automatically.
Note: The bundleLinkMismatch counter is incremented when Note: The mfrBundleLinkMismatch counter is incremented when
the trap is sent." the trap is sent."
REFERENCE "FRF.16 section 4.3.2.4"
::= { mfrMibTrapsPrefix 1 }
-- --------------------------------------------------------- REFERENCE "FRF.16 section 4.3.2.4"
-- --------------------------------------------------------- ::= { mfrMibTrapsPrefix 1 }
-- Conformance/Compliance
-- ---------------------------------------------------------
-- ---------------------------------------------------------
mfrMibCompliance MODULE-COMPLIANCE -- ---------------------------------------------------------
STATUS current -- ---------------------------------------------------------
DESCRIPTION -- Conformance/Compliance
"The compliance statement for equipment that implements -- ---------------------------------------------------------
the FRF16 MIB. All of the current groups are mandatory, -- ---------------------------------------------------------
but a number of objects may be read-only if the
implementation does not allow configuration."
MODULE -- this module
MANDATORY-GROUPS {
mfrMibBundleGroup,
mfrMibBundleLinkGroup,
mfrMibTrapGroup
}
OBJECT bundleFragmentation mfrMibCompliance MODULE-COMPLIANCE
MIN-ACCESS read-only STATUS current
DESCRIPTION DESCRIPTION
"Write access is not required, but the value used must be reported." "The compliance statement for equipment that implements
the FRF16 MIB. All of the current groups are mandatory,
but a number of objects may be read-only if the
implementation does not allow configuration."
MODULE -- this module
MANDATORY-GROUPS {
mfrMibBundleGroup,
mfrMibBundleLinkGroup,
mfrMibTrapGroup
}
OBJECT bundleMaxFragSize OBJECT mfrBundleFragmentation
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, but the value used must be reported. "Write access is not required, but the value used must be
A value of -1 indicates that the value is not applicable." reported."
OBJECT bundleThreshold OBJECT mfrBundleMaxFragSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, but the value used must be reported. "Write access is not required, but the value used must be
A value of -1 indicates that the value is not applicable." reported.
A value of -1 indicates that the value is not applicable."
OBJECT bundleMaxDiffDelay OBJECT mfrBundleThreshold
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, but the value used must be reported." "Write access is not required, but the value used must be
reported.
A value of -1 indicates that the value is not applicable."
OBJECT bundleSeqNumSize OBJECT mfrBundleMaxDiffDelay
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, but the value used must be reported. "Write access is not required, but the value used must be
A value of -1 indicates that the value is not applicable." reported."
::= { mfrMibCompliances 1 } OBJECT mfrBundleSeqNumSize
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, but the value used must be
reported.
A value of -1 indicates that the value is not applicable."
-- --------------------------------------------------------- ::= { mfrMibCompliances 1 }
-- ---------------------------------------------------------
-- Units of Conformance
-- ---------------------------------------------------------
-- ---------------------------------------------------------
mfrMibBundleGroup OBJECT-GROUP -- ---------------------------------------------------------
OBJECTS { -- ---------------------------------------------------------
bundleMaxNumBundles, -- Units of Conformance
bundleNextIndex, -- ---------------------------------------------------------
bundleIfIndex, -- ---------------------------------------------------------
bundleRowStatus,
bundleNearEndName,
bundleFragmentation,
bundleMaxFragSize,
bundleTimerHello,
bundleTimerAck,
bundleCountMaxRetry,
bundleActivationClass,
bundleThreshold,
bundleMaxDiffDelay,
bundleMaxBundleLinks,
bundleLinksConfigured,
bundleLinksActive,
bundleBandwidth,
bundleSeqNumSize,
bundleFarEndName,
bundleResequencingErrors,
bundleIfIndexMappingIndex
}
STATUS current
DESCRIPTION
"Group of objects describing bundles."
::= { mfrMibGroups 1 }
mfrMibBundleLinkGroup OBJECT-GROUP mfrMibBundleGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bundleLinkRowStatus, mfrBundleMaxNumBundles,
bundleLinkConfigBundleIndex, mfrBundleNextIndex,
bundleLinkNearEndName, mfrBundleIfIndex,
bundleLinkState, mfrBundleRowStatus,
bundleLinkFarEndName, mfrBundleNearEndName,
bundleLinkFarEndBundleName, mfrBundleFragmentation,
bundleLinkDelay, mfrBundleMaxFragSize,
bundleLinkFramesControlTx, mfrBundleTimerHello,
bundleLinkFramesControlRx, mfrBundleTimerAck,
bundleLinkFramesControlInvalid, mfrBundleCountMaxRetry,
bundleLinkTimerExpiredCount, mfrBundleActivationClass,
bundleLinkLoopbackSuspected, mfrBundleThreshold,
bundleLinkUnexpectedSequence, mfrBundleMaxDiffDelay,
bundleLinkMismatch mfrBundleMaxBundleLinks,
} mfrBundleLinksConfigured,
STATUS current mfrBundleLinksActive,
DESCRIPTION mfrBundleBandwidth,
"Group of objects describing bundle links." mfrBundleSeqNumSize,
::= { mfrMibGroups 2 } mfrBundleFarEndName,
mfrBundleResequencingErrors,
mfrBundleIfIndexMappingIndex
}
STATUS current
DESCRIPTION
"Group of objects describing bundles."
::= { mfrMibGroups 1 }
mfrMibTrapGroup NOTIFICATION-GROUP mfrMibBundleLinkGroup OBJECT-GROUP
NOTIFICATIONS { OBJECTS {
mfrMibTrapBundleLinkMismatch mfrBundleLinkRowStatus,
} mfrBundleLinkConfigBundleIndex,
STATUS current mfrBundleLinkNearEndName,
DESCRIPTION mfrBundleLinkState,
"Group of objects describing notifications (traps)." mfrBundleLinkFarEndName,
::= { mfrMibGroups 3 } mfrBundleLinkFarEndBundleName,
mfrBundleLinkDelay,
mfrBundleLinkFramesControlTx,
mfrBundleLinkFramesControlRx,
mfrBundleLinkFramesControlInvalid,
mfrBundleLinkTimerExpiredCount,
mfrBundleLinkLoopbackSuspected,
mfrBundleLinkUnexpectedSequence,
mfrBundleLinkMismatch
}
STATUS current
DESCRIPTION
"Group of objects describing bundle links."
::= { mfrMibGroups 2 }
END mfrMibTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mfrMibTrapBundleLinkMismatch
}
STATUS current
DESCRIPTION
"Group of objects describing notifications (traps)."
::= { mfrMibGroups 3 }
END
4. Acknowledgments 4. Acknowledgments
This document was produced by the Frame Relay MFR MIB Working Group. This document was produced by the Frame Relay Service MIB (frnetmib)
Working Group in conjunction with the Frame Relay Forum.
5. References 5. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April for Describing SNMP Management Frameworks", RFC 2571, April
1999 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification
16, RFC 1212, March 1991 of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD
SNMP", RFC 1215, March 1991 16, RFC 1212, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC1215] Rose, M., "A Convention for Defining Traps for use with the
Rose, M., and S. Waldbusser, "Structure of Management SNMP", RFC 1215, March 1991.
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Structure of Management
SMIv2", STD 58, RFC 2579, April 1999 Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2580, April 1999 SMIv2", STD 58, RFC 2579, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Network Management Protocol", STD 15, RFC 1157, May 1990. Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
"Introduction to Community-based SNMPv2", RFC 1901, January Network Management Protocol", STD 15, RFC 1157, May 1990.
1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Introduction to Community-based SNMPv2", RFC 1901, January
Management Protocol (SNMPv2)", RFC 1906, January 1996. 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Processing and Dispatching for the Simple Network Management "Transport Mappings for Version 2 of the Simple Network
Protocol (SNMP)", RFC 2572, April 1999 Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
(USM) for version 3 of the Simple Network Management Processing and Dispatching for the Simple Network
Protocol (SNMPv3)", RFC 2574, April 1999 Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
"Protocol Operations for Version 2 of the Simple Network (USM) for version 3 of the Simple Network Management
Management Protocol (SNMPv2)", RFC 1905, January 1996. Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
RFC 2573, April 1999 "Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
Access Control Model (VACM) for the Simple Network RFC 2573, April 1999.
Management Protocol (SNMP)", RFC 2575, April 1999
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
"Introduction to Version 3 of the Internet-standard Network Access Control Model (VACM) for the Simple Network
Management Framework", RFC 2570, April 1999 Management Protocol (SNMP)", RFC 2575, April 1999.
[Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
Specification For Frame Mode Bearer Services" "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
[Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For [Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer
Frame Mode Basic Call Control" Specification For Frame Mode Bearer Services"
[FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC [Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For
Implementation Agreement" January 5, 1994. Frame Mode Basic Call Control"
[FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay [FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC
Interworking Implementation Agreement" August 20, 1999. Implementation Agreement" January 5, 1994.
[RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay [FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay
Service" RFC 1604, Bell Communications Research, March 1994. Interworking Implementation Agreement" August 20, 1999.
[RFC-EDITOR: Update to current RFC that replaces RFC1604]
[RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and [RFC1604] Rehbehn, K. and D. Fowler, "Definitions of Managed Objects
DS0 Bundle Interface Type" RFC 2494, Newbridge Networks, for Frame Relay Service", RFC 2954, October 2000.
November 1997.
[RFC2233] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB [RFC2494] Fowler, D., "Definitions of Managed Objects for the DS0 and
using SMIv2" RFC 2233, Cisco Systems, FTP Software, November DS0 Bundle Interface Type", RFC 2494, November 1997.
1997.
[ATMLANE] T. Newton, ed., "LAN Emulation Client Management [RFC2863] McCloghrie, D. and F. Kastenholz, "The Interfaces Group MIB
Specification Version 2.0" AF-LANE-0093.000, ATM Forum, using SMIv2", RFC 2233, June 2000.
October, 1998
[ATMIMA] R. Vallee, ed., "Inverse Multiplexing for ATM Specification [ATMLANE] T. Newton, ed., "LAN Emulation Client Management
Version 1.1" (Appendix A) AF-PHY-0086.001, ATM Forum, March, Specification Version 2.0" AF-LANE-0093.000, ATM Forum,
1999 October, 1998
[RFC2115] C. Brown, F. Baker, "Management Information Base for Frame [ATMIMA] R. Vallee, ed., "Inverse Multiplexing for ATM Specification
Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco Version 1.1" (Appendix A) AF-PHY-0086.001, ATM Forum,
Systems, September 1997. March, 1999
[RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces [RFC2115] Brown, C. and F. Baker, "Management Information Base for
Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software, Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
January 1994.
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
skipping to change at page 39, line 7 skipping to change at page 35, line 7
based Access Control Model RFC 2575 [RFC2575] is recommended. based Access Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
7. Authors' Addresses 7. Authors' Addresses
Prayson Pate Prayson Pate
Overture Networks Overture Networks
P. O. Box 14864 P. O. Box 14864
RTP, NC, USA 27709 RTP, NC, USA 27709
Phone: +1 919 302 5145
EMail: prayson.pate@overturenetworks.com
Bob Lynch
Larscom Incorporated
P. O. Box 14993
RTP, NC, USA 27560
Phone: +1 919 991-9062 Phone: +1 919 558 2200
EMail: prayson.pate@overturenetworks.com
EMail: blynch@larscom.com Bob Lynch
Overture Networks
P. O. Box 14864
RTP, NC, USA 27709
Kenneth Rehbehn Phone: +1 919 558-2200
Megisto Systems, Inc. EMail: bob.lynch@overturenetworks.com
20251 Century Boulevard
Germantown, MD, USA 20874
Phone: +1 301 529-4427 Kenneth Rehbehn
Megisto Systems, Inc.
20251 Century Boulevard
Germantown, MD, USA 20874
EMail: krehbehn@megisto.com Phone: +1 301 529-4427
EMail: krehbehn@megisto.com
8. Full Copyright Section 8. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 213 change blocks. 
1243 lines changed or deleted 1159 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/