draft-ietf-frnetmib-mfrmib-02.txt   draft-ietf-frnetmib-mfrmib-03.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
April 4, 2000 September 6, 2000
draft-ietf-frnetmib-mfrmib-02.txt draft-ietf-frnetmib-mfrmib-03
Prayson Pate/Bob Lynch Prayson Pate
Larscom Overture Networks
pate@larscom.com prayson.pate@overturenetworks.com
Bob Lynch
Larscom Incorporated
blynch@larscom.com
Kenneth Rehbehn Kenneth Rehbehn
Visual Networks Megisto Systems, Inc.
krehbehn@visualnetworks.com 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 is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 3, line 24 skipping to change at page 3, line 24
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 ........................ 8 2.3.1 Relationship With Interface Table ........................ 8
2.3.1.1 Bundle Links ........................................... 8 2.3.1.1 Bundle Links ........................................... 8
2.3.1.2 Bundles ................................................ 8 2.3.1.2 Bundles ................................................ 8
2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 9 2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 9
2.3.1.4 ifTable Objects ........................................ 9 2.3.1.4 ifTable Objects ........................................ 9
2.3.2 Relationship With Interface Stack Table .................. 9 2.3.2 Relationship With Interface Stack Table .................. 10
2.3.3 Relationship With Frame Relay DTE MIB .................... 10 2.3.3 Relationship With Frame Relay DTE MIB .................... 10
2.3.4 Relationship With Frame Relay Service MIB ................ 10 2.3.4 Relationship With Frame Relay Service MIB ................ 10
2.3.5 Example .................................................. 10 2.3.5 Example .................................................. 10
2.4 Creation Of Bundles and Bundle Links ....................... 12 2.4 Creation Of Bundles and Bundle Links ....................... 12
2.4.1 Creation Of Bundles ...................................... 12 2.4.1 Creation Of Bundles ...................................... 12
2.4.2 Creation Of Bundle Links ................................. 12 2.4.2 Creation Of Bundle Links ................................. 12
2.5 Notifications .............................................. 12 2.5 Notifications .............................................. 12
2.5.1 Bundle ................................................... 12 2.5.1 Bundle ................................................... 12
2.5.1.1 linkUp ................................................. 12 2.5.1.1 linkUp ................................................. 12
2.5.1.2 linkDown ............................................... 12 2.5.1.2 linkDown ............................................... 13
2.5.2 Bundle Link .............................................. 12 2.5.2 Bundle Link .............................................. 13
2.5.2.1 linkUp ................................................. 13 2.5.2.1 linkUp ................................................. 13
2.5.2.2 linkDown ............................................... 13 2.5.2.2 linkDown ............................................... 13
2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 13 2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 13
3 Object Definitions ........................................... 14 3 Object Definitions ........................................... 14
4 Acknowledgments .............................................. 34 4 Acknowledgments .............................................. 34
5 References ................................................... 35 5 References ................................................... 35
6 Security Considerations ...................................... 37 6 Security Considerations ...................................... 38
7 Authors' Addresses ........................................... 38 7 Authors' Addresses ........................................... 39
8 Copyright Section ............................................ 38 8 Full Copyright Section ....................................... 39
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 UNI/NNI Multilink Frame Relay interfaces. monitoring and controlling the UNI/NNI Multilink Frame Relay
The agreement on which this MIB is based was defined and documented function. The agreement on which this MIB is based was defined and
by the Frame Relay Forum in the Frame Relay Forum Document FRF.16 documented 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
links", aggregated together into a single "bundle" of bandwidth. links", aggregated together into a single "bundle" of bandwidth.
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".
skipping to change at page 6, line 39 skipping to change at page 6, line 39
| | / \ \ | | | | / \ \ | |
| +--------------------\ \------------+ | | +--------------------\ \------------+ |
| _________\_______/ Bundle /_ | | _________\_______/ Bundle /_ |
| /\ / / \ | | /\ / / \ |
+-------------| Bundle Link / / |------------------+ +-------------| Bundle Link / / |------------------+
\/_____________/ /____/ \/_____________/ /____/
\/__________/ \/__________/
Figure 1: MFR Reference Diagram Figure 1: MFR Reference Diagram
Note 1: C-Plane operation 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 Note 2: Multiple frame acknowledged information fransfer 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.
skipping to change at page 8, line 7 skipping to change at page 8, line 7
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 bundleIndex. It is indexed by ifIndex and contains
these columns: these columns:
- bundleIfIndexMapping Integer32 - bundleIfIndexMapping Integer32
2.2.5. bundleLinkTable 2.2.5. bundleLinkTable
This table provides a means to configure and monitor bundles. It is This table provides a means to configure and monitor bundle links.
indexed by ifIndex and contains these columns: It is indexed by ifIndex and contains these columns:
- bundleLinkRowStatus RowStatus - bundleLinkRowStatus RowStatus
- bundleLinkConfigBundleIndex Integer32 - bundleLinkConfigBundleIndex Integer32
- bundleLinkNearEndName SnmpAdminString - bundleLinkNearEndName SnmpAdminString
- bundleLinkState BundleLinkState - bundleLinkState BundleLinkState
- bundleLinkFarEndName SnmpAdminString - bundleLinkFarEndName SnmpAdminString
- bundleLinkFarEndBundleName SnmpAdminString - bundleLinkFarEndBundleName SnmpAdminString
- bundleLinkDelay Integer32 - bundleLinkDelay Integer32
- bundleLinkFramesControlTx Counter32 - bundleLinkFramesControlTx Counter32
- bundleLinkFramesControlRx Counter32 - bundleLinkFramesControlRx Counter32
skipping to change at page 9, line 25 skipping to change at page 9, line 25
interface of that type, then that media-specific MIB should interface of that type, then that media-specific MIB should
include an appropriate RowStatus object (see the ATM LAN- include an appropriate RowStatus object (see the ATM LAN-
Emulation Client MIB [ATMLANE] for an example of a MIB which Emulation Client MIB [ATMLANE] for an example of a MIB which
does this). Typically, when such a RowStatus object is does this). Typically, when such a RowStatus object is
created/deleted, then the conceptual row in the ifTable created/deleted, then the conceptual row in the ifTable
appears/disappears as a by-product, and an ifIndex value (chosen appears/disappears as a by-product, and an ifIndex value (chosen
by the agent) is stored in an appropriate object in the media- by the agent) is stored in an appropriate object in 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. Looking at the examples we have, and the so does the IMA MIB [ATMIMA]. Looking at the examples we have, and
statements from RFC, it seems better to have two indices. This gives the statements from RFC, it seems better to have two indices. This
the SNMP agent implementor the freedom to manage their ifIndex in the gives the SNMP agent implementor the freedom to manage their ifIndex
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 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 bundleTable (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
See the DESCRIPTION clauses for the bundleTable and bundleLinkTable The bundle configuration and status table. There is a one-to-one
for a description of how they relate to the ifTable [RFC1573]. correspondence between a bundle and an interface represented in the
ifTable.
The following objects of the ifTable have specific meaning for an MFR
bundle:
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
The following objects of the ifTable have specific meaning for an MFR
bundle link:
ifAdminStatus - the bundle link admin status
ifOperStatus - the bundle link operational 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
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 logical port defined in RFC1604 [RFC1604]. There frame relay service logical port defined in RFC1604 [RFC1604].
is no other relationship between these MIBs.
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 bundleIndex of 10 and 20 respectively.
+-------------------------+ +-------------------------+
| Frame Relay Service | | Frame Relay Service |
+-----+-------------+-----+ +-----+-------------+-----+
skipping to change at page 11, line 29 skipping to change at page 11, line 41
7 | 0 7 | 0
The bundleIfIndexMappingTable shows the relationship between the The bundleIfIndexMappingTable shows the relationship between the
ifTable ifIndex and the bundleIndex: ifTable ifIndex and the bundleIndex:
ifIndex | bundleIfIndexMappingIndex ifIndex | bundleIfIndexMappingIndex
--------+-------------------------- --------+--------------------------
2 | 10 2 | 10
3 | 20 3 | 20
The bundleConfigTable shows the relationship between the bundleIndex The bundleTable shows the relationship between the bundleIndex and
and the ifIndex: the ifIndex:
bundleIndex | bundleIfIndex bundleIndex | bundleIfIndex
-------------+-------------- -------------+--------------
10 | 2 10 | 2
20 | 3 20 | 3
The bundleLinkTable shows the relationship between the bundles and
The bundleLinkConfigTable shows the relationship between the bundles bundle links:
and bundle links:
bundleIndex | bundleLinkIfIndex bundleIndex | bundleLinkIfIndex
------------+------------------ ------------+------------------
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 bundle is created using the bundleConfigRowStatus RowStatus object. A new bundle is created by setting a createAndGo(4) value in the
There is no minimum set of objects required in order to create a new bundleRowStatus RowStatus object. Optionally, an agent could also
bundle i.e. all of the parameters can assume default values. support setting a value of createAndWait(5) followed by a set to the
value active(1).
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
value of bundleIfIndex.
2.4.2. Creation Of Bundle Links 2.4.2. Creation Of Bundle Links
A bundle link is created using the bundleLinkConfigRowStatus A new bundle link is created by setting a createAndGo(4) value in the
RowStatus object. There is no minimum set of objects required in bundleLinkRowStatus RowStatus object.
order to create a new bundle link i.e. all of the parameters can
assume default values.
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 physical interface. The uses the ifIndex of the physical interface. The bundleLinkEntry row
bundleLinkEntry row objects may be created after or during creation objects may be created after or during creation of the physical
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 bundleIndex must exist at time of
bundle link creation. 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
skipping to change at page 13, line 7 skipping to change at page 13, line 20
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 bundleActivationClass and bundleThreshold) are in the
operationally up state. 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 bundle link transitions into the up state. This trap is sent when a bundleLinkState object transitions to the
value bundleLinkStateUp.
2.5.2.2. linkDown 2.5.2.2. linkDown
This trap is sent when a bundle link transitions from the up state. This trap is sent when a bundleLinkState object transitions from the
value bundleLinkStateUp.
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 - bundleNearEndName: configured name of near end bundle
- bundleFarEndName: previously reported name of far - bundleFarEndName: previously reported name of far
end bundle end bundle
- bundleLinkNearEndName: configured name of near end bundle - bundleLinkNearEndName: configured name of near end bundle
skipping to change at page 14, 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 "0003090000Z" LAST-UPDATED "0009050000Z"
ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group"
CONTACT-INFO CONTACT-INFO
"WG Charter: http://www.ietf.org/html.charters/frnetmib-charter.html "WG Charter: http://www.ietf.org/html.charters/frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
Chair: Andy Malis Chair: Andy Malis
Lucent Technologies Lucent Technologies
Email: amalis@lucent.com Email: Andy.Malis@vivacenetworks.com
WG editor: Prayson Pate WG editor: Prayson Pate
Larscom Overture Networks
Email: pate@larscom.com Email: prayson.pate@overturenetworks.com
Co-author: Bob Lynch Co-author: Bob Lynch
Larscom Larscom Incorporated
EMail: blynch@larscom.com EMail: blynch@larscom.com
Co-author: Kenneth Rehbehn Co-author: Kenneth Rehbehn
Visual Networks Megisto Systems, Inc.
EMail: krehbehn@visualnetworks.com" EMail: krehbehn@megisto.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 "0003090000Z" REVISION "0009050000Z"
DESCRIPTION DESCRIPTION
"Initial version of the FRF.16 UNI/NNI Multilink "Initial version of the FRF.16 UNI/NNI Multilink
Frame Relay MIB. Published as RFC [RFC-EDITOR: Enter RFC # here]." Frame Relay MIB. Published as RFC [RFC-EDITOR: Enter RFC # here]."
REVISION "0004040000Z" REVISION "0009050000Z"
DESCRIPTION DESCRIPTION
"[RFC-EDITOR: Remove this and all following REVISION "[RFC-EDITOR: Remove this and all following REVISION
statements prior to publication as an RFC] statements prior to publication as an RFC]
Changes from draft-ietf-frnetmib-mfrmib-01.txt from IETF-47: Changes after review by Dan Romascanu.
"
REVISION "0004040000Z"
DESCRIPTION
"Changes from draft-ietf-frnetmib-mfrmib-01.txt from IETF-47:
o Fixed display of sample ifStackTable o Fixed display of sample ifStackTable
o Changed bundleIfIndexMappingIndex from InterfaceIndex to Integer32 o Changed bundleIfIndexMappingIndex from InterfaceIndex
to Integer32
" "
REVISION "0003090000Z" REVISION "0003090000Z"
DESCRIPTION DESCRIPTION
"Changes from draft-ietf-frnetmib-mfrmib-00.txt "Changes from draft-ietf-frnetmib-mfrmib-00.txt
o changed experimental number to IANA-approved 105. o changed experimental number to IANA-approved 105.
o changed interface type for frf16MfrBundle to IANA-approved 163. o changed interface type for frf16MfrBundle to IANA-approved 163.
" "
REVISION "9912061700Z" REVISION "9912061700Z"
skipping to change at page 16, line 31 skipping to change at page 16, line 37
one table each for bundles and bundle links one table each for bundles and bundle links
o added new objects for o added new objects for
- maximum number of bundles - maximum number of bundles
- maximum fragment size - maximum fragment size
- size of sequence number - size of sequence number
o added notifications o added notifications
o added conformance information" o added conformance information"
REVISION "9910011440Z" REVISION "9910011440Z"
DESCRIPTION DESCRIPTION
"Initial version submitted to the Frame Relay Forum "The initial version of this MIB was originally submitted
October meeting in Huntsville as FRFTC/99-151." to the Frame Relay Forum October 1999 meeting in Huntsville
as FRFTC/99-151."
::= { experimental 105 } ::= { experimental 105 }
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- --------------------------------------------------------- -- ---------------------------------------------------------
-- --------------------------------------------------------- -- ---------------------------------------------------------
BundleLinkState ::= TEXTUAL-CONVENTION BundleLinkState ::= TEXTUAL-CONVENTION
skipping to change at page 18, line 25 skipping to change at page 18, line 32
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 following objects of the ifTable have specific The following objects of the ifTable have specific
meaning for a MFR bundle: meaning for an 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
ifInUcastPkts - the number of frames received ifInUcastPkts - the number of frames received
on the bundle on the bundle
ifOutUcastPkts - the number of frames transmitted ifOutUcastPkts - the number of frames transmitted
on the bundle on the bundle
ifInErrors - frame (not fragment) errors ifInErrors - frame (not fragment) errors
ifOutErrors - frame (not fragment) errors ifOutErrors - frame (not fragment) errors
" "
skipping to change at page 20, line 8 skipping to change at page 20, line 14
need not match that of the ifIndex in the ifTable. need not match that of the ifIndex in the ifTable.
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 must match an entry in the interface
table. The ifType should be set to frf16MfrBundle(163). table whose ifType must 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 and an ifType of 163."
::= { 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"
skipping to change at page 22, line 5 skipping to change at page 22, line 12
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."
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),
bundleActivationClassB (2), -- all links must be up bundleActivationClassB (2),
bundleActivationClassC (3), -- a certain number must be up bundleActivationClassC (3),
bundleActivationClassD (4) -- custom 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 the conditions under which the bundle is activated.
The following settings are available: The following settings are available:
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.
skipping to change at page 25, line 44 skipping to change at page 25, line 50
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 a 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 ifSpeed - the bandwidth of the bundle
link interface link interface
ifInUcastPkts - the number of frames received ifInUcastPkts - the number of frames received
on the bundle link on the bundle link
ifOutUcastPkts - the number of frames transmitted ifOutUcastPkts - the number of frames transmitted
on the bundle link on the bundle link
skipping to change at page 36, line 42 skipping to change at page 36, line 42
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
Specification Version 2.0" AF-LANE-0093.000, ATM Forum, Specification Version 2.0" AF-LANE-0093.000, ATM Forum,
October, 1998 October, 1998
[ATMIMA] R. Vallee, ed., "Inverse Multiplexing for ATM Specification
Version 1.1" (Appendix A) AF-PHY-0086.001, ATM Forum, March,
1999
[RFC2115] C. Brown, F. Baker, "Management Information Base for Frame [RFC2115] C. Brown, F. Baker, "Management Information Base for Frame
Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco
Systems, September 1997. Systems, September 1997.
[RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces [RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces
Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software, Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software,
January 1994. January 1994.
6. Security Considerations 6. Security Considerations
skipping to change at page 38, line 7 skipping to change at page 39, 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/Bob Lynch Prayson Pate
Larscom Overture Networks
P. O. Box 14864
RTP, NC, USA 27709
Phone: +1 919 302 5145
EMail: prayson.pate@overturenetworks.com
Bob Lynch
Larscom Incorporated
P. O. Box 14993 P. O. Box 14993
RTP, NC, USA 27560 RTP, NC, USA 27560
Phone: +1 919 991-9000 Phone: +1 919 991-9062
EMail: pate@larscom.com/blynch@larscom.com EMail: blynch@larscom.com
Kenneth Rehbehn Kenneth Rehbehn
Visual Networks Megisto Systems, Inc.
2092 Gaither Road 20251 Century Boulevard
Rockville, MD, USA 20850 Germantown, MD, USA 20874
Phone: +1 301 296-2325 Phone: +1 301 529-4427
EMail: krehbehn@visualnetworks.com EMail: krehbehn@megisto.com
8. Copyright Section 8. Full Copyright Section
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
 End of changes. 45 change blocks. 
79 lines changed or deleted 128 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/