draft-ietf-frnetmib-mfrmib-00.txt   draft-ietf-frnetmib-mfrmib-01.txt 
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
December 6, 1999 March 9, 2000
draft-ietf-frnetmib-mfrmib-00.txt draft-ietf-frnetmib-mfrmib-01
Prayson Pate/Bob Lynch Prayson Pate/Bob Lynch
Larscom Larscom
pate@larscom.com pate@larscom.com
Kenneth Rehbehn Kenneth Rehbehn
Visual Networks Visual Networks
krehbehn@visualnetworks.com krehbehn@visualnetworks.com
Status of this Memo Status of this Memo
skipping to change at page 2, line 14 skipping to change at page 2, line 14
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 include conformance and
notification information. notification information.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Table of Contents Table of Contents
1 The SNMP Management Framework ................................ 4 1 The SNMP Management Framework ................................ 4
2 Overview ..................................................... 5 2 Overview ..................................................... 5
2.1 Multilink Frame Relay Background ........................... 5 2.1 Multilink Frame Relay Background ........................... 5
2.1.1 Terminology .............................................. 5 2.1.1 Terminology .............................................. 5
2.1.2 Reference Model .......................................... 6 2.1.2 Reference Model .......................................... 6
2.2 Structure of the MIB ....................................... 7 2.2 Structure of the MIB ....................................... 7
2.2.1 bundleMaxNumBundles ...................................... 7 2.2.1 bundleMaxNumBundles ...................................... 7
2.2.2 bundleNextIndex .......................................... 7 2.2.2 bundleNextIndex .......................................... 7
2.2.3 bundleTable .............................................. 7 2.2.3 bundleTable .............................................. 7
2.2.4 Bundle-to-ifIndex Mapping Table .......................... 7 2.2.4 Bundle-to-ifIndex Mapping Table .......................... 7
2.2.5 bundleLinkTable .......................................... 8 2.2.5 bundleLinkTable .......................................... 8
2.3 Relationship With Other MIBS and Tables .................... 8 2.3 Relationship With Other MIBS and Tables .................... 8
2.3.1 Relationship With Interface Table ........................ 9 2.3.1 Relationship With Interface Table ........................ 8
2.3.1.1 Bundle Links ........................................... 9 2.3.1.1 Bundle Links ........................................... 8
2.3.1.2 Bundles ................................................ 9 2.3.1.2 Bundles ................................................ 8
2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 10 2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 9
2.3.1.4 ifTable Objects ........................................ 10 2.3.1.4 ifTable Objects ........................................ 9
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 .................... 11 2.3.3 Relationship With Frame Relay DTE MIB .................... 10
2.3.4 Relationship With Frame Relay Service MIB ................ 11 2.3.4 Relationship With Frame Relay Service MIB ................ 10
2.3.5 Example .................................................. 11 2.3.5 Example .................................................. 10
2.4 Creation Of Bundles and Bundle Links ....................... 13 2.4 Creation Of Bundles and Bundle Links ....................... 12
2.4.1 Creation Of Bundles ...................................... 13 2.4.1 Creation Of Bundles ...................................... 12
2.4.2 Creation Of Bundle Links ................................. 13 2.4.2 Creation Of Bundle Links ................................. 12
2.5 Notifications .............................................. 13 2.5 Notifications .............................................. 12
2.5.1 Bundle ................................................... 13 2.5.1 Bundle ................................................... 12
2.5.1.1 linkUp ................................................. 13 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 ................................................. 13
2.5.2.2 linkDown ............................................... 14 2.5.2.2 linkDown ............................................... 13
2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 14 2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 13
3 Object Definitions ........................................... 15 3 Object Definitions ........................................... 14
4 Acknowledgments .............................................. 33 4 Acknowledgments .............................................. 34
5 References ................................................... 34 5 References ................................................... 35
6 Security Considerations ...................................... 36 6 Security Considerations ...................................... 37
7 Authors' Addresses ........................................... 37 7 Authors' Addresses ........................................... 38
8 Copyright Section ............................................ 37 8 Copyright Section ............................................ 38
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
skipping to change at page 5, line 9 skipping to change at page 5, line 9
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 a UNI/NNI Multilink Frame Relay function. monitoring and controlling UNI/NNI Multilink Frame Relay interfaces.
The agreement on which this MIB is based was defined and documented The agreement on which this MIB is based was defined and documented
by the Frame Relay Forum in the Frame Relay Forum Document FRF.16 by the Frame Relay Forum in the Frame Relay Forum Document FRF.16
[FRF.16]. [FRF.16].
2.1. Multilink Frame Relay Background 2.1. Multilink Frame Relay Background
Multilink Frame Relay (MFR) for the User-to-Network Interface (UNI) Multilink Frame Relay (MFR) for the User-to-Network Interface (UNI)
and the Network-to-Network Interface (NNI) provides physical and the Network-to-Network Interface (NNI) provides physical
interface emulation for frame relay devices. The emulated physical interface emulation for frame relay devices. The emulated physical
interface consists of one or more physical links, called "bundle interface consists of one or more physical links, called "bundle
skipping to change at page 7, line 7 skipping to change at page 7, line 7
[FRF.4] [FRF.4]
Note 2: Multiple frame acknowledged information fransfer mode Note 2: Multiple frame acknowledged information fransfer mode
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 three tables and two The UNI/NNI MFR managed objects consist of two scalar objects and
scalars. three tables.
2.2.1. bundleMaxNumBundles 2.2.1. bundleMaxNumBundles
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. bundleNextIndex
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 bundleIndex during row creation. It can also be used to avoid race
skipping to change at page 8, line 27 skipping to change at page 8, line 27
- bundleLinkFramesControlTx Counter32 - bundleLinkFramesControlTx Counter32
- bundleLinkFramesControlRx Counter32 - bundleLinkFramesControlRx Counter32
- bundleLinkFramesControlInvalid Counter32 - bundleLinkFramesControlInvalid Counter32
- bundleLinkTimerExpiredCount Counter32 - bundleLinkTimerExpiredCount Counter32
- bundleLinkLoopbackSuspected Counter32 - bundleLinkLoopbackSuspected Counter32
- bundleLinkUnexpectedSequence Counter32 - bundleLinkUnexpectedSequence Counter32
- bundleLinkMismatch Counter32 - bundleLinkMismatch Counter32
2.3. Relationship With Other MIBS and Tables 2.3. Relationship With Other MIBS and Tables
Figure 2 (adapted from RFC 1604 [RFC1604]) shows the relationship of
this MIB with other MIBs.
____________________________________________________
| | | | |
| | | SIP | RFC1490 |
| | X.25 MIB | Relay | (no applic.|
| | for IW/Encap.| MIB | MIB) |
| | | | |
| MIB II |-----------------------------------|
| | |
| ifTable | Frame Relay Service MIB |
| ifXTable |___________________________________|
| ifStackTable | |
| | FRF.16 MFR MIB |
| |___________________________________|
| | | |
| | Physical Layer MIBs | ATM MIB |
| | e.g., DS1/E1 MIB, |---------|
| | RS232-like MIB | Phy. |
| | | Layer |
| | | MIB |
|______________|_________________________|_________|
Figure 2: Relationship With Other MIBs
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
skipping to change at page 10, line 16 skipping to change at page 9, line 40
2.3.1.3. Mapping Between ifIndex and bundleIndex 2.3.1.3. Mapping Between ifIndex and bundleIndex
The bundleIfIndexMappingTable is indexed by ifIndex and provides the The bundleIfIndexMappingTable is indexed by ifIndex and provides the
means to map a given ifIndex into the corresponding bundleIndex. The means to map a given ifIndex into the corresponding bundleIndex. The
bundleIfIndexMapping object in the bundleConfigTable (indexed by bundleIfIndexMapping object in the bundleConfigTable (indexed by
bundleIndex) provides the reverse mapping of a bundleIndex to the bundleIndex) provides the reverse mapping of a bundleIndex to the
corresponding ifIndex in the ifTable. corresponding ifIndex in the ifTable.
2.3.1.4. ifTable Objects 2.3.1.4. ifTable Objects
The table below summarizes the objects in the ifTable [RFC1573] and See the DESCRIPTION clauses for the bundleTable and bundleLinkTable
how they relate to bundles and bundle links. for a description of how they relate to the ifTable [RFC1573].
ifTable Column | Bundle Use | Bundle Link Use
------------------+--------------------+---------------------
ifIndex |no special meaning |no special meaning
ifDescr |no special meaning |no special meaning
ifType |TBD |TBD
ifMtu |no special meaning |no special meaning
ifSpeed |sum of bundle speeds|no special meaning
ifPhysAddress |no special meaning |no special meaning
ifAdminStatus |control of bundle |control of bundle link
ifOperStatus |status of bundle |status of bundle link
ifLastChange |no special meaning |no special meaning
ifInOctets |no special meaning |no special meaning
ifInUcastPkts |count of frames |count of fragments
ifInNUcastPkts |deprecated |deprecated
ifInDiscards |no special meaning |no special meaning
ifInErrors |no special meaning |no special meaning
ifInUnknownProtos |no special meaning |no special meaning
ifOutOctets |no special meaning |no special meaning
ifOutUcastPkts |no special meaning |no special meaning
ifOutNUcastPkts |deprecated |deprecated
ifOutDiscards |no special meaning |no special meaning
ifOutErrors |no special meaning |no special meaning
ifOutQLen |deprecated |deprecated
ifSpecific |deprecated |deprecated
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 2233 [RFC2233]. 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 defined in RFC1604 [RFC1604]. There is no other frame relay service logical port defined in RFC1604 [RFC1604]. There
relationship between these MIBs. is no other relationship between these MIBs.
2.3.5. Example 2.3.5. Example
Figure three 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 bundleIndex 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 3: 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 ifIndex | Description | ifType
--------+---------------------------------------- --------+----------------------------+----------------------
1 | FrameRelayService (type 44) 1 | FrameRelayService | frameRelayService(44)
2 | MFR Bundle #10 (type TBD) 2 | MFR Bundle #10 | frf16MfrBundle(163)
3 | MFR Bundle #20 (type TBD) 3 | MFR Bundle #20 | frf16MfrBundle(163)
4 | ds1 #1/MFR Bundle Link #1 (type 18) 4 | ds1 #1/MFR Bundle Link #1 | ds1(18)
5 | ds1 #2/MFR Bundle Link #2 (type 18) 5 | ds1 #2/MFR Bundle Link #2 | ds1(18)
6 | ds1 #3/MFR Bundle Link #3 (type 18) 6 | ds1 #3/MFR Bundle Link #3 | ds1(18)
7 | ds1 #4/MFR Bundle Link #4 (type 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
2 | 3 2 | 3
2 | 4 2 | 4
3 | 5 3 | 5
skipping to change at page 13, line 16 skipping to change at page 12, line 16
2.4.1. Creation Of Bundles 2.4.1. Creation Of Bundles
A bundle is created using the bundleConfigRowStatus RowStatus object. A bundle is created using the bundleConfigRowStatus RowStatus object.
There is no minimum set of objects required in order to create a new There is no minimum set of objects required in order to create a new
bundle i.e. all of the parameters can assume default values. bundle i.e. all of the parameters can assume default values.
2.4.2. Creation Of Bundle Links 2.4.2. Creation Of Bundle Links
A bundle link is created using the bundleLinkConfigRowStatus A bundle link is created using the bundleLinkConfigRowStatus
RowStatus object. It must be created as a part of an existing RowStatus object. There is no minimum set of objects required in
bundle. There is no minimum set of objects required in order to order to create a new bundle link i.e. all of the parameters can
create a new bundle link i.e. all of the parameters can assume assume default values.
default values. The only requirement is that the owner bundle
(specified by bundleIndex) be in existence. The bundle link is associated with a specific physical interface and
uses the ifIndex of the physical physical interface. The
bundleLinkEntry row objects may be created after or during creation
of the physical interface's ifEntry row objects.
The bundle identified in the object bundleIndex must exist at time 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 1573 [RFC1573].
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
skipping to change at page 15, line 33 skipping to change at page 14, line 33
TEXTUAL-CONVENTION, TestAndIncr, RowStatus TEXTUAL-CONVENTION, TestAndIncr, RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
InterfaceIndex, ifIndex InterfaceIndex, ifIndex
FROM IF-MIB; FROM IF-MIB;
mfrMib MODULE-IDENTITY mfrMib MODULE-IDENTITY
LAST-UPDATED "9910191300Z" LAST-UPDATED "0003090000Z"
ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group"
CONTACT-INFO CONTACT-INFO
"Prayson Pate/Bob Lynch "WG Charter: http://www.ietf.org/html.charters/frnetmib-charter.html
Postal: Larscom WG-email: frnetmib@sunroof.eng.sun.com
P. O. Box 14993 Subscribe: frnetmib-request@sunroof.eng.sun.com
RTP, NC, USA 27560 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
Phone: +1 919 991-9000
EMail: pate@larscom.com/blynch@larscom.com
Kenneth Rehbehn Chair: Andy Malis
Postal: Visual Networks Lucent Technologies
2092 Gaither Road Email: amalis@lucent.com
Rockville, MD USA 20850
Tel: +1 301 296 2325 WG editor: Prayson Pate
Fax: +1 301 296 2302 Larscom
E-mail: krehbehn@visualnetworks.com" Email: pate@larscom.com
Co-author: Bob Lynch
Larscom
EMail: blynch@larscom.com
Co-author: Kenneth Rehbehn
Visual Networks
EMail: krehbehn@visualnetworks.com"
DESCRIPTION DESCRIPTION
"This is the MIB used to control and monitor the multilink frame "This is the MIB used to control and monitor the multilink frame
relay (MFR) function described in FRF.16. This was originally relay (MFR) function described in FRF.16. This was originally
submitted to the Frame Relay Forum as contribution FRFTC 99-151 submitted to the Frame Relay Forum as contribution FRFTC 99-151
and then updated as FRFTC 99-193." and then updated as FRFTC 99-193."
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Revision History -- Revision History
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
REVISION "9910011440Z" REVISION "0003090000Z"
DESCRIPTION DESCRIPTION
"Initial version submitted to the Frame Relay Forum "Initial version of the FRF.16 UNI/NNI Multilink
October meeting in Huntsville as FRFTC/99-151." Frame Relay MIB. Published as RFC [RFC-EDITOR: Enter RFC # here]."
REVISION "9910151300Z" REVISION "0003090000Z"
DESCRIPTION DESCRIPTION
"Updated after review at the October meeting in Huntsville: "[RFC-EDITOR: Remove this and all following REVISION
o removed log table statements prior to publication as an RFC]
o removed several columns from each table
o combined configuration, status and error tables into Changes from draft-ietf-frnetmib-mfrmib-00.txt
one table each for bundles and bundle links o changed experimental number to IANA-approved 105.
o added new objects for o changed interface type for frf16MfrBundle to IANA-approved 163.
- maximum number of bundles "
- maximum fragment size
- size of sequence number REVISION "9912061700Z"
o added notifications DESCRIPTION
o added conformance information" "Updates:
o changed name to draft-ietf-frnetmib-mfrmib-00
o updated text to match last MIB revisions
o corrected description of bundleIfIndexMappingTable
o added objects to show configured and current bundle links.
"
REVISION "9910212020Z" REVISION "9910212020Z"
DESCRIPTION DESCRIPTION
"Updated after comments from Michael Allen and Ken Rehben. "Updated after comments from Michael Allen and Ken Rehben.
o corrected options for sequence number length o corrected options for sequence number length
o changed frf16Mfr prefix to mfr o changed frf16Mfr prefix to mfr
o created a sub-group for scalars o created a sub-group for scalars
o created an entry in the bundleTable for maximum links per bundle o created an entry in the bundleTable for maximum links per bundle
o changed indices to not-accessible o changed indices to not-accessible
o changed DisplayString to SnmpAdminString o changed DisplayString to SnmpAdminString
o updated some of the object descriptions o updated some of the object descriptions
o added a -EXP to the name of the MIB o added a -EXP to the name of the MIB
o added some DEFVAL and REFERENCE clauses" o added some DEFVAL and REFERENCE clauses"
REVISION "9912061700Z" REVISION "9910151300Z"
DESCRIPTION DESCRIPTION
"Updates: "Updated after review at the October meeting in Huntsville:
o changed name to draft-ietf-frnetmib-mfrmib-00 o removed log table
o updated text to match last MIB revisions o removed several columns from each table
o corrected description of bundleIfIndexMappingTable o combined configuration, status and error tables into
o added objects to show configured and current bundle links. one table each for bundles and bundle links
" o added new objects for
::= { experimental 555 } - maximum number of bundles
- maximum fragment size
- size of sequence number
o added notifications
o added conformance information"
REVISION "9910011440Z"
DESCRIPTION
"Initial version submitted to the Frame Relay Forum
October meeting in Huntsville as FRFTC/99-151."
::= { experimental 105 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
BundleLinkState ::= TEXTUAL-CONVENTION BundleLinkState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 18, line 41 skipping to change at page 18, line 15
-- --------------------------------------------------------- -- ---------------------------------------------------------
bundleTable OBJECT-TYPE bundleTable OBJECT-TYPE
SYNTAX SEQUENCE OF BundleEntry SYNTAX SEQUENCE OF BundleEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundle configuration and status table. There "The bundle configuration and status table. There
is a one-to-one correspondence between a bundle is a one-to-one correspondence between a bundle
and an interface represented in the ifTable. and an interface represented in the ifTable.
The manager can use the following entries in the ifTable:
The following objects of the ifTable have specific
meaning for a MFR 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
ifInErrors - packet (not fragment) errors ifInUcastPkts - the number of frames received
etc." on the bundle
ifOutUcastPkts - the number of frames transmitted
on the bundle
ifInErrors - frame (not fragment) errors
ifOutErrors - frame (not fragment) errors
"
::= { mfrMibBundleObjects 3 } ::= { mfrMibBundleObjects 3 }
bundleEntry OBJECT-TYPE bundleEntry OBJECT-TYPE
SYNTAX BundleEntry SYNTAX BundleEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the bundle table." "An entry in the bundle table."
INDEX { bundleIndex } INDEX { bundleIndex }
::= { bundleTable 1 } ::= { bundleTable 1 }
skipping to change at page 20, line 20 skipping to change at page 19, line 50
A manager can use bundleNextIndex to select a unique A manager can use bundleNextIndex to select a unique
bundleIndex for creating a new row." bundleIndex for creating a new row."
::= { bundleEntry 1 } ::= { bundleEntry 1 }
bundleIfIndex OBJECT-TYPE bundleIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value should match an entry in the interface "The value should match an entry in the interface
table. The ifType should be set to frame-relay. table. The ifType should be set to frf16MfrBundle(163).
For example: if the value of bundleIfIndex is 10, For example: if the value of bundleIfIndex is 10,
then a corresponding entry should be present in then a corresponding entry should be present in
the ifTable with an index of 10." the ifTable with an index of 10."
::= { bundleEntry 2 } ::= { bundleEntry 2 }
bundleRowStatus OBJECT-TYPE bundleRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundleRowStatus object allows create, change, "The bundleRowStatus object allows create, change,
and delete operations on bundle entries." and delete operations on bundle entries."
REFERENCE "RFC 1903" REFERENCE "RFC 1903"
::= { bundleEntry 3 } ::= { bundleEntry 3 }
bundleNearEndName OBJECT-TYPE bundleNearEndName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..50)) SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured name of the bundle." "The configured name of the bundle."
REFERENCE "FRF.16 section 3.4.1" REFERENCE "FRF.16 section 3.4.1"
::= { bundleEntry 4 } ::= { bundleEntry 4 }
bundleFragmentation OBJECT-TYPE bundleFragmentation OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enable (1), enable (1),
disable (2) disable (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Controls whether the bundle performs/accepts "Controls whether the bundle performs/accepts
fragmentation and re-assembly." fragmentation and re-assembly. The possible
values are:
enable(1) - Bundle links will fragment frames
disable(2) - Bundle links will not fragment
frames."
DEFVAL { disable } DEFVAL { disable }
::= { bundleEntry 5 } ::= { bundleEntry 5 }
bundleMaxFragSize OBJECT-TYPE bundleMaxFragSize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (-1..8184)
UNITS "Octets"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum fragment size supported. Note that this "The maximum fragment size supported. Note that this
is only valid if bundleFragmentation is set to enable(1). is only valid if bundleFragmentation is set to enable(1).
Otherwise, it should be reported as -1."
Zero is not a valid fragment size.
A bundle that does not support fragmentation must be
set to -1."
DEFVAL { -1 } DEFVAL { -1 }
::= { bundleEntry 6 } ::= { bundleEntry 6 }
bundleTimerHello OBJECT-TYPE bundleTimerHello OBJECT-TYPE
SYNTAX INTEGER (1..180) SYNTAX INTEGER (1..180)
UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured MFR Hello Timer value (in seconds). "The configured MFR Hello Timer value."
The default value is 10."
REFERENCE "FRF.16 section 4.3.8.1" REFERENCE "FRF.16 section 4.3.8.1"
DEFVAL { 10 } DEFVAL { 10 }
::= { bundleEntry 7 } ::= { bundleEntry 7 }
bundleTimerAck OBJECT-TYPE bundleTimerAck OBJECT-TYPE
SYNTAX INTEGER (1..10) SYNTAX INTEGER (1..10)
UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured MFR T_ACK value (in seconds). "The configured MFR T_ACK value."
The default value is 4."
REFERENCE "FRF.16 section 4.3.8.2" REFERENCE "FRF.16 section 4.3.8.2"
DEFVAL { 4 } DEFVAL { 4 }
::= { bundleEntry 8 } ::= { bundleEntry 8 }
bundleCountMaxRetry OBJECT-TYPE bundleCountMaxRetry OBJECT-TYPE
SYNTAX INTEGER (1..5) SYNTAX INTEGER (1..5)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MFR N_MAX_RETRY value. "The MFR N_MAX_RETRY value."
The default value is 2."
REFERENCE "FRF.16 section 4.3.8.3" REFERENCE "FRF.16 section 4.3.8.3"
DEFVAL { 2 } DEFVAL { 2 }
::= { bundleEntry 9 } ::= { bundleEntry 9 }
bundleActivationClass OBJECT-TYPE bundleActivationClass OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bundleActivationClassA (1), -- at least one must link up bundleActivationClassA (1), -- at least one must link up
bundleActivationClassB (2), -- all links must be up bundleActivationClassB (2), -- all links must be up
bundleActivationClassC (3), -- a certain number must be up bundleActivationClassC (3), -- a certain number must be up
bundleActivationClassD (4) -- custom bundleActivationClassD (4) -- custom
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 14 skipping to change at page 22, line 6
bundleActivationClass OBJECT-TYPE bundleActivationClass OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bundleActivationClassA (1), -- at least one must link up bundleActivationClassA (1), -- at least one must link up
bundleActivationClassB (2), -- all links must be up bundleActivationClassB (2), -- all links must be up
bundleActivationClassC (3), -- a certain number must be up bundleActivationClassC (3), -- a certain number must be up
bundleActivationClassD (4) -- custom bundleActivationClassD (4) -- custom
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Controls the conditions under which the bundle is activated." "Controls the conditions under which the bundle is activated.
The following settings are available:
bundleActivationClassA(1) - at least one must link up
bundleActivationClassB(2) - all links must be up
bundleActivationClassC(3) - a certain number must be up.
Refer to bundleThreshold for
the required number.
bundleActivationClassD(4) - custom (implementation
specific)."
REFERENCE "FRF.16 section 4.2.2.1" REFERENCE "FRF.16 section 4.2.2.1"
DEFVAL { bundleActivationClassA } DEFVAL { bundleActivationClassA }
::= { bundleEntry 10 } ::= { bundleEntry 10 }
bundleThreshold OBJECT-TYPE bundleThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Bundle Links"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the number of links that must be in operational "Specifies the number of links that must be in operational
'up' state before the bundle will transition to an 'up' state before the bundle will transition to an
operational up/active state. If the number of operational up/active state. If the number of
operational 'up' links falls below this value, operational 'up' links falls below this value,
then the bundle will transition to an inactive then the bundle will transition to an inactive
state. state.
Note - this is only valid when bundleActivationClass Note - this is only valid when bundleActivationClass
is set to bundleActivationClassC or to bundleActivationClassD." is set to bundleActivationClassC or, depending upon the
implementation, to bundleActivationClassD."
REFERENCE "FRF.16 section 4.2.2.1" REFERENCE "FRF.16 section 4.2.2.1"
DEFVAL { -1 } DEFVAL { -1 }
::= { bundleEntry 11 } ::= { bundleEntry 11 }
bundleMaxDiffDelay OBJECT-TYPE bundleMaxDiffDelay OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum delay difference between the bundle "The maximum delay difference between the bundle
links. The unit of measure is milliseconds." links."
DEFVAL { -1 } DEFVAL { -1 }
::= { bundleEntry 12 } ::= { bundleEntry 12 }
bundleSeqNumSize OBJECT-TYPE bundleSeqNumSize OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
seqNumSize12bit (1), seqNumSize12bit (1),
seqNumSize24bit (2) seqNumSize24bit (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Controls whether the standard FRF.12 12-bit "Controls whether the standard FRF.12 12-bit
sequence number is used or the optional 24-bit sequence number is used or the optional 24-bit
sequence number." sequence number."
REFERENCE "FRFTC/99-194" REFERENCE "FRFTC/99-194"
DEFVAL { seqNumSize12bit } DEFVAL { seqNumSize12bit }
::= { bundleEntry 13 } ::= { bundleEntry 13 }
bundleMaxBundleLinks OBJECT-TYPE bundleMaxBundleLinks OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Bundle Links"
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 maximum number of bundle links supported for this bundle."
::= { bundleEntry 14 } ::= { bundleEntry 14 }
bundleLinksConfigured OBJECT-TYPE bundleLinksConfigured OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Bundle Links"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of links configured for the bundle." "The number of links configured for the bundle."
::= { bundleEntry 15 } ::= { bundleEntry 15 }
bundleLinksActive OBJECT-TYPE bundleLinksActive OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Bundle Links"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of links that are active." "The number of links that are active."
::= { bundleEntry 16 } ::= { bundleEntry 16 }
bundleBandwidth OBJECT-TYPE bundleBandwidth OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Bits/Sec"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of available bandwidth in bits/sec." "The amount of available bandwidth on the bundle"
::= { bundleEntry 17 } ::= { bundleEntry 17 }
bundleFarEndName OBJECT-TYPE bundleFarEndName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..50)) SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Name of the bundle received from the far end." "Name of the bundle received from the far end."
REFERENCE "FRF.16 section 3.4.1" REFERENCE "FRF.16 section 3.4.1"
::= { bundleEntry 18 } ::= { bundleEntry 18 }
bundleResequencingErrors OBJECT-TYPE bundleResequencingErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "Error Events"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of resequncing errors. Each event "A count of the number of resequncing errors. Each event
may correspond to multiple lost frames. Example: may correspond to multiple lost frames. Example:
Say sequence number 56, 59 and 60 is received for DLCI 100. 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. It is decided by some means that sequence 57 and 58 is lost.
This counter should then be incremented by ONE, even though This counter should then be incremented by ONE, even though
two frames were lost." two frames were lost."
::= { bundleEntry 19 } ::= { bundleEntry 19 }
skipping to change at page 25, line 26 skipping to change at page 25, line 35
SYNTAX SEQUENCE OF BundleLinkEntry SYNTAX SEQUENCE OF BundleLinkEntry
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 manager can use the following entries in the ifTable: The following objects of the ifTable have specific
meaning for a MFR bundle link:
ifAdminStatus - the bundle link admin status ifAdminStatus - the bundle link admin status
ifOperStatus - the bundle link operationl status ifOperStatus - the bundle link operational
ifSpeed - the bandwidth of the bundle link status
ifInErrors - frame/fragment errors ifSpeed - the bandwidth of the bundle
etc." 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 } ::= { mfrMibBundleLinkObjects 1 }
bundleLinkEntry OBJECT-TYPE bundleLinkEntry OBJECT-TYPE
SYNTAX BundleLinkEntry SYNTAX BundleLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the bundle link table." "An entry in the bundle link table."
INDEX { ifIndex } INDEX { ifIndex }
::= { bundleLinkTable 1 } ::= { bundleLinkTable 1 }
skipping to change at page 26, line 32 skipping to change at page 26, line 49
bundleLinkMismatch bundleLinkMismatch
Counter32 Counter32
} }
bundleLinkRowStatus OBJECT-TYPE bundleLinkRowStatus 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 bundleLinkRowStatus object allows create, change,
and delete operations on bundleLink entries." and delete operations on bundleLink entries.
The create operation must fail if no physical interface
is associated with the bundle link."
::= { bundleLinkEntry 1 } ::= { bundleLinkEntry 1 }
bundleLinkConfigBundleIndex OBJECT-TYPE bundleLinkConfigBundleIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bundleLinkConfigBundleIndex object allows "The bundleLinkConfigBundleIndex 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 bundleIndex
in this field, then we could put the bundleLink row in in this field, then we could put the bundleLink row in
NOT_IN_SERVICE or ACTIVE rowStatus." NOT_IN_SERVICE or ACTIVE rowStatus."
::= { bundleLinkEntry 2 } ::= { bundleLinkEntry 2 }
bundleLinkNearEndName OBJECT-TYPE bundleLinkNearEndName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..50)) 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 } ::= { bundleLinkEntry 3 }
bundleLinkState OBJECT-TYPE bundleLinkState OBJECT-TYPE
SYNTAX BundleLinkState SYNTAX BundleLinkState
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 } ::= { bundleLinkEntry 4 }
bundleLinkFarEndName OBJECT-TYPE bundleLinkFarEndName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..50)) 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 } ::= { bundleLinkEntry 5 }
bundleLinkFarEndBundleName OBJECT-TYPE bundleLinkFarEndBundleName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..50)) 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 } ::= { bundleLinkEntry 6 }
bundleLinkDelay OBJECT-TYPE bundleLinkDelay OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current round-trip delay for this bundle link." "Current round-trip delay for this bundle link. The value -1
is returned when an implementation does not support measurement
of the bundle link delay."
REFERENCE "FRF.16 section 3.4.4" REFERENCE "FRF.16 section 3.4.4"
::= { bundleLinkEntry 7 } ::= { bundleLinkEntry 7 }
bundleLinkFramesControlTx OBJECT-TYPE bundleLinkFramesControlTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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"
::= { bundleLinkEntry 8 } ::= { bundleLinkEntry 8 }
bundleLinkFramesControlRx OBJECT-TYPE bundleLinkFramesControlRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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"
::= { bundleLinkEntry 9 } ::= { bundleLinkEntry 9 }
bundleLinkFramesControlInvalid OBJECT-TYPE bundleLinkFramesControlInvalid OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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"
::= { bundleLinkEntry 10 } ::= { bundleLinkEntry 10 }
bundleLinkTimerExpiredCount OBJECT-TYPE bundleLinkTimerExpiredCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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"
::= { bundleLinkEntry 11 } ::= { bundleLinkEntry 11 }
bundleLinkLoopbackSuspected OBJECT-TYPE bundleLinkLoopbackSuspected OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 } ::= { bundleLinkEntry 12 }
bundleLinkUnexpectedSequence OBJECT-TYPE bundleLinkUnexpectedSequence OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 } ::= { bundleLinkEntry 13 }
bundleLinkMismatch OBJECT-TYPE bundleLinkMismatch OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 detected a mismatch between "The number of times that the unit has been notified by the
the near end and far end bundles." remote peer that the bundle name is inconsistent with other
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 } ::= { bundleLinkEntry 14 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Notifications/Traps -- Notifications/Traps
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE
skipping to change at page 29, line 34 skipping to change at page 30, line 20
bundleNearEndName, bundleNearEndName,
bundleFarEndName, bundleFarEndName,
bundleLinkNearEndName, bundleLinkNearEndName,
bundleLinkFarEndName, bundleLinkFarEndName,
bundleLinkFarEndBundleName bundleLinkFarEndBundleName
} }
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
- bundleFarEndName: previously reported name of far end bundle bundleNearEndName: configured name of near end bundle
- bundleLinkNearEndName: configured name of near end bundle
- bundleLinkFarEndName: reported name of far end bundle bundleFarEndName: previously reported name of
- bundleLinkFarEndBundleName: currently reported name of
far end bundle far end bundle
bundleLinkNearEndName: configured name of near end bundle
bundleLinkFarEndName: reported name of far end bundle
bundleLinkFarEndBundleName: currently reported name of
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 bundleLinkMismatch counter is incremented when
the trap is sent." the trap is sent."
REFERENCE "FRF.16 section 4.3.2.4" REFERENCE "FRF.16 section 4.3.2.4"
::= { mfrMibTrapsPrefix 1 } ::= { mfrMibTrapsPrefix 1 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Conformance/Compliance -- Conformance/Compliance
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
skipping to change at page 31, line 4 skipping to change at page 31, line 47
"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." A value of -1 indicates that the value is not applicable."
::= { mfrMibCompliances 1 } ::= { mfrMibCompliances 1 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Units of Conformance -- Units of Conformance
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
mfrMibBundleGroup OBJECT-GROUP mfrMibBundleGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bundleMaxNumBundles, bundleMaxNumBundles,
bundleNextIndex,
bundleIfIndex, bundleIfIndex,
bundleRowStatus, bundleRowStatus,
bundleNearEndName, bundleNearEndName,
bundleFragmentation, bundleFragmentation,
bundleMaxFragSize, bundleMaxFragSize,
bundleTimerHello, bundleTimerHello,
bundleTimerAck, bundleTimerAck,
bundleCountMaxRetry, bundleCountMaxRetry,
bundleActivationClass, bundleActivationClass,
bundleThreshold, bundleThreshold,
bundleMaxDiffDelay, bundleMaxDiffDelay,
bundleMaxBundleLinks, bundleMaxBundleLinks,
bundleLinksConfigured,
bundleLinksActive,
bundleBandwidth,
bundleSeqNumSize, bundleSeqNumSize,
bundleFarEndName, bundleFarEndName,
bundleResequencingErrors, bundleResequencingErrors,
bundleIfIndexMappingIndex, bundleIfIndexMappingIndex
bundleNextIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects describing bundles." "Group of objects describing bundles."
::= { mfrMibGroups 1 } ::= { mfrMibGroups 1 }
mfrMibBundleLinkGroup OBJECT-GROUP mfrMibBundleLinkGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bundleLinkRowStatus, bundleLinkRowStatus,
bundleLinkConfigBundleIndex, bundleLinkConfigBundleIndex,
skipping to change at page 35, line 28 skipping to change at page 36, line 28
Frame Mode Basic Call Control" Frame Mode Basic Call Control"
[FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC [FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC
Implementation Agreement" January 5, 1994. Implementation Agreement" January 5, 1994.
[FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay [FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay
Interworking Implementation Agreement" August 20, 1999. Interworking Implementation Agreement" August 20, 1999.
[RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay [RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay
Service" RFC 1604, Bell Communications Research, March 1994. Service" RFC 1604, Bell Communications Research, March 1994.
[RFC-EDITOR: Update to current RFC that replaces RFC1604]
[RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and [RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and
DS0 Bundle Interface Type" RFC 2494, Newbridge Networks, DS0 Bundle Interface Type" RFC 2494, Newbridge Networks,
November 1997. November 1997.
[RFC2233] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB [RFC2233] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB
using SMIv2" RFC 2233, Cisco Systems, FTP Software, November using SMIv2" RFC 2233, Cisco Systems, FTP Software, November
1997. 1997.
[ATMLANE] T. Newton, ed., "LAN Emulation Client Management [ATMLANE] T. Newton, ed., "LAN Emulation Client Management
skipping to change at page 37, line 27 skipping to change at page 38, line 27
Visual Networks Visual Networks
2092 Gaither Road 2092 Gaither Road
Rockville, MD, USA 20850 Rockville, MD, USA 20850
Phone: +1 301 296-2325 Phone: +1 301 296-2325
EMail: krehbehn@visualnetworks.com EMail: krehbehn@visualnetworks.com
8. Copyright Section 8. Copyright Section
Copyright (C) The Internet Society (1999). 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
 End of changes. 81 change blocks. 
178 lines changed or deleted 233 lines changed or added

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