draft-ietf-adslmib-gbond-mib-01.txt   draft-ietf-adslmib-gbond-mib-02.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Intended status: Standards Track M. Morgenstern Intended status: Standards Track M. Morgenstern
Expires: May 21, 2008 ECI Telecom Expires: March 5, 2009 ECI Telecom
N. Nair N. Nair
Wipro Technologies Wipro Technologies
November 18, 2007 September 01, 2008
xDSL multi-pair bonding (G.Bond) MIB xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-01.txt draft-ietf-adslmib-gbond-mib-02.txt
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 21, 2008. This Internet-Draft will expire on March 5, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines Management Information Base (MIB) module for This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP-based internets. use with network management protocols in TCP/IP-based internets.
This document proposes an extension to the Interfaces Group MIB with This document proposes an extension to the Interfaces Group MIB with
a set of common objects for managing multi-pair bonded Digital a set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations
G.998.1, G.998.2 and G.998.3. The MIB modules specific to each G.998.1, G.998.2 and G.998.3. The MIB modules specific to each
bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and
skipping to change at page 2, line 23 skipping to change at page 2, line 20
4. Relationship to Other MIB modules . . . . . . . . . . . . . . 4 4. Relationship to Other MIB modules . . . . . . . . . . . . . . 4
4.1. Relationship to Interfaces Group MIB module . . . . . . . 5 4.1. Relationship to Interfaces Group MIB module . . . . . . . 5
4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5 4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5
4.1.2. G.Bond Aggregation Function (GAF) . . . . . . . . . . 7 4.1.2. G.Bond Aggregation Function (GAF) . . . . . . . . . . 7
4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9 4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9
4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
4.2. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11 4.2. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11
5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 11 5.2. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 12
6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 13 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 33 7. Security Considerations . . . . . . . . . . . . . . . . . . . 36
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 35 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.1. Normative References . . . . . . . . . . . . . . . . . . . 35 10.1. Normative References . . . . . . . . . . . . . . . . . . . 38
10.2. Informative References . . . . . . . . . . . . . . . . . . 36 10.2. Informative References . . . . . . . . . . . . . . . . . . 39
1. Introduction 1. Introduction
The xDSL Multi-Pair Bonding, allows a service provider to provide The xDSL Multi-Pair Bonding, allows a service provider to provide
high bandwidth services to business and residential customers over high bandwidth services to business and residential customers over
multiple xDSL lines, with greater speed and resiliency, than the multiple xDSL lines, with greater speed and resiliency, than the
service over a single xDSL line, bridging the gap between xDSL and service over a single xDSL line, bridging the gap between xDSL and
fiber-based transport. fiber-based transport.
There are three xDSL Multi-Pair Bonding schemes, also known under There are three xDSL Multi-Pair Bonding schemes, also known under
skipping to change at page 5, line 37 skipping to change at page 5, line 37
Generic Bonded Sub-layer (GBS) and to the channel sub-layer as Generic Bonded Sub-layer (GBS) and to the channel sub-layer as
Bonding Channel Entity (BCE). Bonding Channel Entity (BCE).
A generic G.Bond device can have a number of GBS ports, each A generic G.Bond device can have a number of GBS ports, each
connected to a particular upper layer (e.g., Media Access Control connected to a particular upper layer (e.g., Media Access Control
(MAC) interface for G.998.2 scheme), while simultaneously cross- (MAC) interface for G.998.2 scheme), while simultaneously cross-
connected to a number of underlying BCEs, with a single GBS per BCE connected to a number of underlying BCEs, with a single GBS per BCE
relationship. relationship.
A GBS port is represented in the Interface table (ifTable) as a A GBS port is represented in the Interface table (ifTable) as a
separate interface with an ifType of 'gBond'. separate interface with an ifType of g9981, g9982 or g9983 for a
particular bonding scheme.
Each BCE in the aggregated GBS port is represented in the ifTable as Each BCE in the aggregated GBS port is represented in the ifTable as
a separate interface with an ifType relevant to a particular xDSL a separate interface with an ifType relevant to a particular xDSL
technology, e.g., shdsl(169) or vdsl(97). The ifType values are technology, e.g., shdsl(169) or vdsl(97). The ifType values are
defined in [IANAifType-MIB]. defined in [IANAifType-MIB].
The following figure shows the layering diagram and corresponding use The following figure shows the layering diagram and corresponding use
of ifTable for the bonded xDSL interfaces: of ifTable for the bonded xDSL interfaces:
.-----------------------------. - .-----------------------------. -
| GBS | ^ 1 ifEntry | GBS | ^ 1 ifEntry
| (TPS-TC) | v ifType: gBond | (TPS-TC) | v ifType: g9981, g9982 or g9983
+-----------------+---+-------+ - +-----------------+---+-------+ -
| TPS-TC \ | | | ^ | TPS-TC \ | | | ^
+---------\ | | | | +---------\ | | | |
| PMS-TC )BCE 1 |...| BCE N | ) N ifEntry (N=1..32) | PMS-TC )BCE 1 |...| BCE N | ) N ifEntry (N=1..32)
+---------/ | | | | ifType: adsl(94), shdsl(169), +---------/ | | | | ifType: adsl(94), shdsl(169),
| PMD / | | | v vdsl(97), etc. | PMD / | | | v vdsl(97), etc.
'-----------------+---+-------' - '-----------------+---+-------' -
BCE - Bonding Channel Entity BCE - Bonding Channel Entity
GBS - Generic Bonded Sub-layer GBS - Generic Bonded Sub-layer
skipping to change at page 7, line 18 skipping to change at page 7, line 18
the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface. connected to run on top of a particular interface.
4.1.2. G.Bond Aggregation Function (GAF) 4.1.2. G.Bond Aggregation Function (GAF)
The G.Bond Aggregation Function (GAF) allows a number of BCEs to be The G.Bond Aggregation Function (GAF) allows a number of BCEs to be
aggregated onto a GBS port, by fragmenting the Ethernet frames, aggregated onto a single logical GBS port, by splitting the incoming
transmitting the fragments over multiple BCEs and assembling the traffic into multiple streams, transmitting each stream over a
original frames at the remote GBS port. GAF is OPTIONAL, meaning specific BCE and combining the streams at the remote GBS port,
that a device with a single BCE MAY perform fragmentation and re- preserving the original traffic order.
assembly if this function is supported by the device. Note however
that the agent is REQUIRED to report on the GAF capability for all Big Ethernet frames MAY be fragmented before the transmission and
types of G.Bond ports (ATM, Ethernet and TDIM). reassembled at the remote end to minimize transportation delay.
GAF is OPTIONAL, meaning that a device with a single BCE MAY perform
fragmentation and re-assembly if this function is supported by the
device. The agent is REQUIRED to report on the GAF capability for
all types of G.Bond ports (ATM, Ethernet and TDIM).
The GBOND-MIB module allows a Network Management application to query The GBOND-MIB module allows a Network Management application to query
GAF capability and enable/disable it if supported. Note that GAF capability and enable/disable it if supported. Note that
enabling GAF effectively turns on fragmentation and re-assembly, even enabling GAF effectively turns on fragmentation and re-assembly, even
on a single-BCE port. on a single-BCE port.
4.1.3. Discovery Operation 4.1.3. Discovery Operation
The G.Bond ports may optionally support discovery operation, whereby The G.Bond ports may optionally support discovery operation, whereby
BCEs, during initialization, exchange information about their BCEs, during initialization, exchange information about their
skipping to change at page 10, line 8 skipping to change at page 10, line 13
pair. Sometimes, when the copper line is too long or the noise on pair. Sometimes, when the copper line is too long or the noise on
the line is too high, that 'training' process may fail to achieve a the line is too high, that 'training' process may fail to achieve a
specific target rate with required characteristics. specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state The ifAdminStatus object from the IF-MIB, controls the desired state
of a GBS with all the BCEs connected to it or of an individual BCE of a GBS with all the BCEs connected to it or of an individual BCE
port. Setting this object to 'up' instructs a particular GBS or a port. Setting this object to 'up' instructs a particular GBS or a
BCE to start initialization process, which may take tens of seconds BCE to start initialization process, which may take tens of seconds
for G.Bond ports. The ifOperStatus object shows the operational for G.Bond ports. The ifOperStatus object shows the operational
state of an interface (extended by ifMauMediaAvailable object from state of an interface (extended by ifMauMediaAvailable object from
MAU-MIB for GBS and *Status object from a relevant line MIB for BCE MAU-MIB [RFC4836] for GBS and *Status object from a relevant line MIB
interfaces). for BCE interfaces).
A disconnected BCE may be initialized by changing the ifAdminState A disconnected BCE may be initialized by changing the ifAdminState
from 'down' to 'up'. Changing the ifAdminState to 'up' on the GBS from 'down' to 'up'. Changing the ifAdminState to 'up' on the GBS
initializes all BCEs connected to that particular GBS. Note that in initializes all BCEs connected to that particular GBS. Note that in
case of bonding some interfaces may fail to initialize while others case of bonding some interfaces may fail to initialize while others
succeed. The GBS is considered operationally 'up' if at least one succeed. The GBS is considered operationally 'up' if at least one
bonded BCE is operationally 'up'. When all BCEs connected to the GBS bonded BCE is operationally 'up'. When all BCEs connected to the GBS
are 'down' the GBS SHALL be considered operationally are 'down' the GBS SHALL be considered operationally
'lowerLayerDown'. The GBS SHALL be considered operationally 'lowerLayerDown'. The GBS SHALL be considered operationally
'notPresent' if it is not connected to any BCE. The GBS/BCE 'notPresent' if it is not connected to any BCE. The GBS/BCE
skipping to change at page 10, line 41 skipping to change at page 10, line 46
ifGeneralInformationGroup: ifGeneralInformationGroup:
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| IF-MIB object | G.Bond interpretation | | IF-MIB object | G.Bond interpretation |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each BCE and each GBS | | ifIndex | Interface index. Note that each BCE and each GBS |
| | in the G.Bond PHY MUST have a unique index, as | | | in the G.Bond PHY MUST have a unique index, as |
| | there some GBS and BCE specific attributes | | | there some GBS and BCE specific attributes |
| | accessible only on the GBS or BCE level. | | | accessible only on the GBS or BCE level. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifType | gBond(TBD) for GBS, shdsl(169) for G.SHDSL BCE, | | ifType | g9981, g9982 or g9982 for the ATM, Ethernet or |
| | vdsl(97) for VDSL BCE etc. | | | TDIM GBS respectively, shdsl(169) for G.SHDSL |
| | BCE, vdsl(97) for VDSL BCE etc. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifSpeed | Operating data rate for the BCE. For the GBS it | | ifSpeed | Operating data rate for the BCE. For the GBS it |
| | is the sum of the current operating data rates of | | | is the sum of the current operating data rates of |
| | all BCEs in the aggregation group, without the | | | all BCEs in the aggregation group, without the |
| | encapsulation overhead and G.Bond overhead, but | | | encapsulation overhead and G.Bond overhead, but |
| | accounting for the Inter-Frame Gaps (IFG). When a | | | accounting for the Inter-Frame Gaps (IFG). When a |
| | GBS or a BCE is operating in an assymetrical | | | GBS or a BCE is operating in an assymetrical |
| | fashion (upstream data rate differs from the | | | fashion (upstream data rate differs from the |
| | downstream one) the lowest of the values is | | | downstream one) the lowest of the values is |
skipping to change at page 11, line 40 skipping to change at page 11, line 40
[RFC3440] for ADSL, ADSL2-LINE-MIB [RFC4706] for ADSL2, VDSL-LINE-MIB [RFC3440] for ADSL, ADSL2-LINE-MIB [RFC4706] for ADSL2, VDSL-LINE-MIB
[RFC3728] for VDSL or VDSL2-LINE-MIB [I-D.ietf-adslmib-vdsl2-mib] for [RFC3728] for VDSL or VDSL2-LINE-MIB [I-D.ietf-adslmib-vdsl2-mib] for
VDSL2. VDSL2.
These MIBs are used to manage individual xDSL lines/channels (BCEs). These MIBs are used to manage individual xDSL lines/channels (BCEs).
5. MIB Structure 5. MIB Structure
5.1. Overview 5.1. Overview
The main management objects defined in the GBOND-MIB module are split
into 2 groups:
o gBondPort - containing objects for configuration, capabilities,
status and notifications, common to all G.Bond ports (GBS).
o gBondBce - containing a single common object for configuration of
the remote discovery code per BCE. Note that the rest of the
objects for BCE configuration, capabilities, status and
notifications, is located in relevant xDSL line MIB modules as
well as in the bonding scheme specific MIB modules.
5.2. Mapping of DSL Forum WT-159 Managed Objects 5.2. Mapping of DSL Forum WT-159 Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [WT-159] and managed objects defined in this (attributes) defined in [WT-159] and managed objects defined in this
document and in associated MIB modules, i.e., the IF-MIB [RFC2863]. document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| G.Bond Managed Object | Corresponding SNMP Object | | G.Bond Managed Object | Corresponding SNMP Object |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| oBondingGroup - Basic | | | oBondingGroup - Basic Package | |
| Package (Mandatory) | | | (Mandatory) | |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupID | ifIndex (IF-MIB) | | aGroupID | ifIndex (IF-MIB) |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupBondSchemesSupported | gBondSchemesSupported | | aGroupBondSchemesSupported | gBondSchemesSupported |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupBondPeerSchemesSupported | gBondPeerSchemesSupported |
+--------------------------------+----------------------------------+
| aGroupAdminBondScheme | gBondAdminScheme | | aGroupAdminBondScheme | gBondAdminScheme |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupOperBondScheme | gBondOperScheme | | aGroupOperBondScheme | gBondOperScheme |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupPeerOperBondScheme | gBondPeerOperScheme | | aGroupPeerOperBondScheme | gBondPeerOperScheme |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupEnd | gBondPortSide | | aGroupEnd | gBondPortSide |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupOperState | ifOperStatus (IF-MIB) | | aGroupOperState | ifOperStatus (IF-MIB) |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupAdminState | ifAdminStatus (IF-MIB) | | aGroupAdminState | ifAdminStatus (IF-MIB) |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupStatus | gBondFltStatus | | aGroupStatus | gBondFltStatus |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupCapacity | gBondCapacity | | aGroupCapacity | gBondCapacity |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupPeerCapacity | gBondPeerCapacity | | aGroupPeerCapacity | gBondPeerCapacity |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupNumChannels | gBondNumBCEs | | aGroupNumChannels | gBondNumBCEs |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupName | ifName (IF-MIB) | | aGroupName | ifName (IF-MIB) |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupDiscoveryCode | gBondDiscoveryCode |
+--------------------------------+----------------------------------+
| aGroupUpRate | gBondUpDataRate | | aGroupUpRate | gBondUpDataRate |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupDownRate | gBondDownDataRate | | aGroupDownRate | gBondDownDataRate |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupTargetUpRate | gBondTargetUpDataRate | | aGroupTargetUpRate | gBondTargetUpDataRate |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupTargetDownRate | gBondTargetDownDataRate | | aGroupTargetDownRate | gBondTargetDownDataRate |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupCapacity | gBondCapacity |
+-----------------------------+-------------------------------------+
| aGroupPeerCapacity | gBondPeerCapacity |
+-----------------------------+-------------------------------------+
| aGroupThreshLowUpRate | gBondThreshLowUpRate | | aGroupThreshLowUpRate | gBondThreshLowUpRate |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupThreshLowDownRate | gBondThreshLowDownRate | | aGroupThreshLowDownRate | gBondThreshLowDownRate |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable | | aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing | | nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| nGroupLowDownRateCrossing | gBondLowDownRateCrossing | | nGroupLowDownRateCrossing | gBondLowDownRateCrossing |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB doesn't | | aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB |
| | provide a control for the | | | doesn't provide a control for |
| | linkUp/linkDown notifications. Can | | | the linkUp/linkDown |
| | we define a control in one MIB | | | notifications. Can we define a |
| | module while the notifications are | | | control in one MIB module while |
| | in another?_ | | | the notifications are in |
+-----------------------------+-------------------------------------+ | | another?_ |
+--------------------------------+----------------------------------+
| nGroupLinkUp | linkDown (IF-MIB) | | nGroupLinkUp | linkDown (IF-MIB) |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| nGroupLinkDown | linkUp (IF-MIB) | | nGroupLinkDown | linkUp (IF-MIB) |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| oLine - Basic Package | | | oLine - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aLineID | ifIndex (IF-MIB) |
+--------------------------------+----------------------------------+
| aLineType | ifType (IF-MIB) |
+--------------------------------+----------------------------------+
| aLineOperState | ifOperStatus (IF-MIB) |
+--------------------------------+----------------------------------+
| aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) |
+--------------------------------+----------------------------------+
| aLineEnd | *dsl*Side (*DSL-LINE-MIB) |
+--------------------------------+----------------------------------+
| aLineAdminState | ifAdminStatus (IF-MIB) |
+--------------------------------+----------------------------------+
| aLineRemoteDiscoveryCode | gBondBceRemoteDiscoveryCode | | aLineRemoteDiscoveryCode | gBondBceRemoteDiscoveryCode |
+-----------------------------+-------------------------------------+ +--------------------------------+----------------------------------+
| aLineUpDownEnable | _EdNote: Currently IF-MIB |
| | doesn't provide a control for |
| | the linkUp/linkDown |
| | notifications. Can we define a |
| | control in one MIB module while |
| | the notifications are in |
| | another?_ |
+--------------------------------+----------------------------------+
| nLineUp | linkUp (IF-MIB) |
+--------------------------------+----------------------------------+
| nLineDown | linkDown (IF-MIB) |
+--------------------------------+----------------------------------+
Table 2: Mapping of WT-159 Managed Objects Table 2: Mapping of WT-159 Managed Objects
6. xDSL Multi-pair Bonding MIB Definitions 6. xDSL Multi-pair Bonding MIB Definitions
GBOND-MIB DEFINITIONS ::= BEGIN GBOND-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Gauge32, mib-2 Unsigned32, Gauge32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, PhysAddress TEXTUAL-CONVENTION, TruthValue, PhysAddress
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
ifIndex ifIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
; ;
gBondMIB MODULE-IDENTITY gBondMIB MODULE-IDENTITY
LAST-UPDATED "200711180000Z" -- November 18, 2007 LAST-UPDATED "200809010000Z" -- Sep 01, 2008
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/adslmib-charter.html http://www.ietf.org/html.charters/adslmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: adslmib@ietf.org General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Menachem Dodge Chair: Menachem Dodge
Postal: ECI Telecom, Ltd. Postal: ECI Telecom, Ltd.
30 Hasivim St., 30 Hasivim St.,
Petach-Tikva 49517 Petach-Tikva 49517
Israel Israel
skipping to change at page 15, line 19 skipping to change at page 16, line 43
[G.998.2] refers to: [G.998.2] refers to:
ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
bonding', January 2005. bonding', January 2005.
[G.998.3] refers to: [G.998.3] refers to:
ITU-T Recommendation G.998.3: 'Multi-pair bonding using ITU-T Recommendation G.998.3: 'Multi-pair bonding using
time-division inverse multiplexing', January 2005. time-division inverse multiplexing', January 2005.
[WT-159] refers to: [WT-159] refers to:
DSL Forum Technical Report: 'Management Framework for xDSL DSL Forum Technical Report: 'Management Framework for xDSL
Bonding', January 2007. Bonding', September 2008.
Naming Conventions: Naming Conventions:
BCE - Bonding Channel Entity BCE - Bonding Channel Entity
CO - Central Office CO - Central Office
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer GBS - Generic Bonding Sublayer
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
Copyright (C) The IETF Trust (2008).
This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices."
Copyright (C) The Internet Society (2007). This version REVISION "200809010000Z" -- Sep 01, 2008
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200711180000Z" -- November 18, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 ZZZ } ::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is -- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 16, line 17 skipping to change at page 17, line 43
GBondSchemeList ::= TEXTUAL-CONVENTION GBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention defines a bitmap of possible ITU-T "This textual convention defines a bitmap of possible ITU-T
G.998 (G.Bond) bonding schemes. Currently there are 3 bonding G.998 (G.Bond) bonding schemes. Currently there are 3 bonding
schemes defined: G.998.1, G.998.2 and G.998.3, identified by schemes defined: G.998.1, G.998.2 and G.998.3, identified by
bit values g9981(1), g9982(2) and g9983(3), respectively. bit values g9981(1), g9982(2) and g9983(3), respectively.
An additional value of unknown(0), can be returned as a result An additional value of unknown(0), can be returned as a result
of GET operation, when an value of the object cannot be of GET operation, when an value of the object cannot be
determined." determined, for example a peer GBS cannot be reached or it
does not support any kind of bonding."
SYNTAX BITS { SYNTAX BITS {
unknown(0), unknown(0),
g9981(1), g9981(1),
g9982(2), g9982(2),
g9983(3) g9983(3)
} }
GBondScheme ::= TEXTUAL-CONVENTION GBondScheme ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme "This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are: values. Possible values are:
unknown(0) - undefined or unknown unknown(0) - undefined or unknown
g9981(1) - G.998.1 (G.Bond/ATM) g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernt) g9982(2) - G.998.2 (G.Bond/Ethernt)
g9983(3) - G.998.3 (G.Bond/TDIM)." g9983(3) - G.998.3 (G.Bond/TDIM)."
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 18, line 30 skipping to change at page 20, line 9
micro-interruption may temporarily drop one or more BCEs in micro-interruption may temporarily drop one or more BCEs in
the aggregation group, causing a rate degradation of the the aggregation group, causing a rate degradation of the
aggregated G.Bond link. The dropped BCEs would then try to aggregated G.Bond link. The dropped BCEs would then try to
re-initialize, possibly at a lower rate than before, re-initialize, possibly at a lower rate than before,
adjusting the rate to provide required target SNR margin. adjusting the rate to provide required target SNR margin.
Generation of this notification is controlled by the Generation of this notification is controlled by the
gBondLowRateCrossingEnable object. gBondLowRateCrossingEnable object.
This object maps to the WT-159 notification This object maps to the WT-159 notification
nGroupLowUpRateCrossing." nGroupLowDownRateCrossing."
REFERENCE REFERENCE
"[WT-159] 5.5.1.25" "[WT-159] 5.5.1.25"
::= { gBondPortNotifications 2} ::= { gBondPortNotifications 2}
-- G.Bond Port (GBS) group -- G.Bond Port (GBS) group
gBondPortConfTable OBJECT-TYPE gBondPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortConfEntry SYNTAX SEQUENCE OF GBondPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 19, line 4 skipping to change at page 20, line 32
table MUST be maintained in a persistent manner" table MUST be maintained in a persistent manner"
::= { gBondPort 1 } ::= { gBondPort 1 }
gBondPortConfEntry OBJECT-TYPE gBondPortConfEntry OBJECT-TYPE
SYNTAX GBondPortConfEntry SYNTAX GBondPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Configuration table. "An entry in the G.Bond Port Configuration table.
Each entry represents an G.Bond port indexed by the ifIndex. Each entry represents an G.Bond port indexed by the ifIndex.
Note that an G.Bond GBS port runs on top of a single Note that an G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex." or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { gBondPortConfTable 1 } ::= { gBondPortConfTable 1 }
GBondPortConfEntry ::= GBondPortConfEntry ::=
SEQUENCE { SEQUENCE {
gBondAdminScheme GBondScheme, gBondAdminScheme GBondScheme,
gBondPeerAdminScheme GBondScheme,
gBondDiscoveryCode PhysAddress, gBondDiscoveryCode PhysAddress,
gBondTargetUpDataRate Unsigned32, gBondTargetUpDataRate Unsigned32,
gBondTargetDownDataRate Unsigned32, gBondTargetDownDataRate Unsigned32,
gBondThreshLowUpRate Unsigned32, gBondThreshLowUpRate Unsigned32,
gBondThreshLowDownRate Unsigned32, gBondThreshLowDownRate Unsigned32,
gBondLowRateCrossingEnable TruthValue gBondLowRateCrossingEnable TruthValue
} }
gBondAdminScheme OBJECT-TYPE gBondAdminScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired bonding scheme for a G.Bond port. "A desired bonding scheme for a G.Bond GBS port.
The following values instruct the port to use corresponding The following values instruct the port to use corresponding
bonding scheme if supported: bonding scheme if supported:
g998.1(1) - instructs the port to use G.998.1 bonding g9981(1) - instructs the port to use G.998.1 bonding
g998.2(2) - instructs the port to use G.998.2 bonding g9982(2) - instructs the port to use G.998.2 bonding
g998.3(3) - instructs the port to use G.998.3 bonding g9983(3) - instructs the port to use G.998.3 bonding
Changing of the gBondAdminScheme MUST be performed when the Changing of the gBondAdminScheme MUST be performed when the
link is Down. Attempts to change this object MUST be rejected link is Down. Attempts to change this object MUST be rejected
(in case of SNMP with the error inconsistentValue), if the (in case of SNMP with the error inconsistentValue), if the
link is Up or Initializing. Attempts to change this object to link is Up or Initializing. Attempts to change this object to
an unsupported bonding scheme (see gBondSchemesSupported) an unsupported bonding scheme (see gBondSchemesSupported)
SHALL be rejected (in case of SNMP with the error wrongValue). SHALL be rejected (in case of SNMP with the error wrongValue).
This object MUST be maintained in a persistent manner. This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupAdminBondScheme." aGroupAdminBondScheme."
REFERENCE REFERENCE
"[WT-159] 5.5.1.6" "[WT-159] 5.5.1.6"
::= { gBondPortConfEntry 1 } ::= { gBondPortConfEntry 1 }
gBondPeerAdminScheme OBJECT-TYPE
SYNTAX GBondScheme
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A desired bonding scheme for a peer (link partner) G.Bond
port (GBS).
The following values instruct the peer port to use
corresponding bonding scheme if supported:
g9981(1) - instructs the port to use G.998.1 bonding
g9982(2) - instructs the port to use G.998.2 bonding
g9983(3) - instructs the port to use G.998.3 bonding
Changing of the gBondAdminScheme MUST be performed when the
link is Down. Attempts to change this object MUST be rejected
(in case of SNMP with the error inconsistentValue), if the
link is Up or Initializing. Attempts to change this object to
an unsupported bonding scheme (see gBondPeerSchemesSupported)
SHALL be rejected (in case of SNMP with the error wrongValue).
This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute
aGroupPeerAdminBondScheme."
REFERENCE
"[WT-159] 5.5.1.7"
::= { gBondPortConfEntry 2 }
gBondDiscoveryCode OBJECT-TYPE gBondDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6)) SYNTAX PhysAddress (SIZE(6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Discovery Code of the G.Bond port (GBS). "A Discovery Code of the G.Bond port (GBS).
A unique 6 octet long code used by the Discovery function. A unique 6 octet long code used by the Discovery function.
This object MUST be instantiated for the -O subtype GBS before This object MUST be instantiated for the -O subtype GBS before
writing operations on the gBondBceRemoteDiscoveryCode writing operations on the gBondBceRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by BCEs (Set_if_Clear and Clear_if_Same) are performed by BCEs
skipping to change at page 20, line 28 skipping to change at page 22, line 36
Discovery MUST be performed when the link is Down. Discovery MUST be performed when the link is Down.
Attempts to change this object MUST be rejected (in case of Attempts to change this object MUST be rejected (in case of
SNMP with the error inconsistentValue), if the link is Up or SNMP with the error inconsistentValue), if the link is Up or
Initializing. Initializing.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupDiscoveryCode." aGroupDiscoveryCode."
REFERENCE REFERENCE
"[WT-159] 5.5.1.20; [802.3] 61.2.2.8.3, 61.2.2.8.4, "[WT-159] 5.5.1.20; [802.3] 61.2.2.8.3, 61.2.2.8.4,
45.2.6.6.1, 45.2.6.8, 61A.2" 45.2.6.6.1, 45.2.6.8, 61A.2"
::= { gBondPortConfEntry 2 } ::= { gBondPortConfEntry 3 }
gBondTargetUpDataRate OBJECT-TYPE gBondTargetUpDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999) SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired G.Bond port Data Rate in the upstream direction, "A desired G.Bond port Data Rate in the upstream direction,
in Kbps, to be achieved during initialization, under in Kbps, to be achieved during initialization, under
restrictions placed upon the member BCEs by their respective restrictions placed upon the member BCEs by their respective
skipping to change at page 21, line 34 skipping to change at page 23, line 41
when the link is Down. Attempts to change this object MUST be when the link is Down. Attempts to change this object MUST be
rejected (In case of SNMP with the error inconsistentValue), rejected (In case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. if the link is Up or Initializing.
This object MUST be maintained in a persistent manner. This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupTargetUpRate." aGroupTargetUpRate."
REFERENCE REFERENCE
"[WT-159] 5.5.1.17" "[WT-159] 5.5.1.17"
::= { gBondPortConfEntry 3 } ::= { gBondPortConfEntry 4 }
gBondTargetDownDataRate OBJECT-TYPE gBondTargetDownDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999) SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired G.Bond port Data Rate in the downstream direction, "A desired G.Bond port Data Rate in the downstream direction,
in Kbps, to be achieved during initialization, under in Kbps, to be achieved during initialization, under
restrictions placed upon the member BCEs by their respective restrictions placed upon the member BCEs by their respective
skipping to change at page 22, line 38 skipping to change at page 24, line 46
when the link is Down. Attempts to change this object MUST be when the link is Down. Attempts to change this object MUST be
rejected (In case of SNMP with the error inconsistentValue), rejected (In case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. if the link is Up or Initializing.
This object MUST be maintained in a persistent manner. This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupTargetDownRate." aGroupTargetDownRate."
REFERENCE REFERENCE
"[WT-159] 5.5.1.18" "[WT-159] 5.5.1.18"
::= { gBondPortConfEntry 4 } ::= { gBondPortConfEntry 5 }
gBondThreshLowUpRate OBJECT-TYPE gBondThreshLowUpRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000) SYNTAX Unsigned32(1..1000000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the G.Bond port low upstream rate "This object configures the G.Bond port low upstream rate
crossing alarm threshold. When the current value of crossing alarm threshold. When the current value of
gBondUpDataRate for this port reaches/drops below or exceeds gBondUpDataRate for this port reaches/drops below or exceeds
skipping to change at page 23, line 14 skipping to change at page 25, line 21
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner. This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupthreshLowUpRate." aGroupthreshLowUpRate."
REFERENCE REFERENCE
"[WT-159] 5.5.1.21" "[WT-159] 5.5.1.21"
::= { gBondPortConfEntry 5 } ::= { gBondPortConfEntry 6 }
gBondThreshLowDownRate OBJECT-TYPE gBondThreshLowDownRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000) SYNTAX Unsigned32(1..1000000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the G.Bond port low downstream rate "This object configures the G.Bond port low downstream rate
crossing alarm threshold. When the current value of crossing alarm threshold. When the current value of
gBondDownDataRate for this port reaches/drops below or exceeds gBondDownDataRate for this port reaches/drops below or exceeds
skipping to change at page 23, line 37 skipping to change at page 25, line 44
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner. This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupThreshDownUpRate." aGroupThreshDownUpRate."
REFERENCE REFERENCE
"[WT-159] 5.5.1.22" "[WT-159] 5.5.1.22"
::= { gBondPortConfEntry 6 } ::= { gBondPortConfEntry 7 }
gBondLowRateCrossingEnable OBJECT-TYPE gBondLowRateCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether gBondLowUpRateCrossing and "Indicates whether gBondLowUpRateCrossing and
gBondLowDownRateCrossing notifications should be generated gBondLowDownRateCrossing notifications should be generated
for this interface. for this interface.
skipping to change at page 24, line 12 skipping to change at page 26, line 20
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner. This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupLowRateCrossingEnable." aGroupLowRateCrossingEnable."
REFERENCE REFERENCE
"[WT-159] 5.5.1.23" "[WT-159] 5.5.1.23"
::= { gBondPortConfEntry 7 } ::= { gBondPortConfEntry 8 }
gBondPortCapabilityTable OBJECT-TYPE gBondPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortCapabilityEntry SYNTAX SEQUENCE OF GBondPortCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Capabilities of G.Bond Ports. Entries in this table "Table for Capabilities of G.Bond Ports. Entries in this table
MUST be maintained in a persistent manner" MUST be maintained in a persistent manner"
::= { gBondPort 2 } ::= { gBondPort 2 }
skipping to change at page 24, line 38 skipping to change at page 26, line 46
"An entry in the G.Bond Port Capability table. "An entry in the G.Bond Port Capability table.
Each entry represents an G.Bond port indexed by the ifIndex. Each entry represents an G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex." or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { gBondPortCapabilityTable 1 } ::= { gBondPortCapabilityTable 1 }
GBondPortCapabilityEntry ::= GBondPortCapabilityEntry ::=
SEQUENCE { SEQUENCE {
gBondSchemesSupported GBondSchemeList, gBondSchemesSupported GBondSchemeList,
gBondPeerSchemesSupported GBondSchemeList,
gBondCapacity Unsigned32, gBondCapacity Unsigned32,
gBondPeerCapacity Unsigned32 gBondPeerCapacity Unsigned32
} }
gBondSchemesSupported OBJECT-TYPE gBondSchemesSupported OBJECT-TYPE
SYNTAX GBondSchemeList SYNTAX GBondSchemeList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bonding Capability of the G.Bond port (GBS). This is a "Bonding Capability of the G.Bond port (GBS). This is a
read-only bitmap of the possible bonding schemes supported by read-only bitmap of the possible bonding schemes supported by
the GBS. the GBS. The various bit-positions are:
g9981(1) - GBS is capable of G.998.1 bonding
g9982(2) - GBS is capable of G.998.2 bonding
g9983(3) - GBS is capable of G.998.3 bonding
Note that for ports supporting multiple bonding schemes the Note that for ports supporting multiple bonding schemes the
actual administrative scheme is set via gBondAdminScheme actual administrative scheme is set via gBondAdminScheme
object. The current operating bonding scheme is reflected in object. The current operating bonding scheme is reflected in
the gBondOperScheme. the gBondOperScheme.
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupBondSchemesSupported." aGroupBondSchemesSupported."
REFERENCE REFERENCE
"[WT-159] 5.5.1.1" "[WT-159] 5.5.1.2"
::= { gBondPortCapabilityEntry 1 } ::= { gBondPortCapabilityEntry 1 }
gBondPeerSchemesSupported OBJECT-TYPE
SYNTAX GBondSchemeList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Bonding Capability of the peer G.Bond port (GBS). This is a
read-only bitmap of the possible bonding schemes supported by
the link partner GBS. The various bit-positions are:
unknown(0) - GBS does not support bonding or
the peer unit could not be reached.
g9981(1) - GBS is capable of G.998.1 bonding
g9982(2) - GBS is capable of G.998.2 bonding
g9983(3) - GBS is capable of G.998.3 bonding
Note that for ports supporting multiple bonding schemes the
actual administrative scheme is set via gBondPeerAdminScheme
object. The current operating bonding scheme is reflected in
the gBondPeerOperScheme.
This object maps to the WT-159 attribute
aGroupBondPeerSchemesSupported."
REFERENCE
"[WT-159] 5.5.1.3"
::= { gBondPortCapabilityEntry 2 }
gBondCapacity OBJECT-TYPE gBondCapacity OBJECT-TYPE
SYNTAX Unsigned32 (1..32) SYNTAX Unsigned32 (1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of BCEs that can be aggregated by the local GBS. "Number of BCEs that can be aggregated by the local GBS.
The number of BCEs currently assigned to a particular G.Bond The number of BCEs currently assigned to a particular G.Bond
port (gBondNumBCEs) is never greater than gBondCapacity. port (gBondNumBCEs) is never greater than gBondCapacity.
This object maps to the WT-159 attribute aGroupCapacity." This object maps to the WT-159 attribute aGroupCapacity."
REFERENCE REFERENCE
"[WT-159] 5.5.1.12" "[WT-159] 5.5.1.12"
::= { gBondPortCapabilityEntry 2 } ::= { gBondPortCapabilityEntry 3 }
gBondPeerCapacity OBJECT-TYPE gBondPeerCapacity OBJECT-TYPE
SYNTAX Unsigned32 (0|1..32) SYNTAX Unsigned32 (0|1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of BCEs that can be aggregated by the peer GBS port. "Number of BCEs that can be aggregated by the peer GBS port.
Value of 0 is returned when peer Bonding Capacity is unknown Value of 0 is returned when peer Bonding Capacity is unknown
(peer cannot be reached). (peer cannot be reached).
This object maps to the WT-159 attribute aGroupPeerCapacity." This object maps to the WT-159 attribute aGroupPeerCapacity."
REFERENCE REFERENCE
"[WT-159] 5.5.1.13" "[WT-159] 5.5.1.13"
::= { gBondPortCapabilityEntry 3 } ::= { gBondPortCapabilityEntry 4 }
gBondPortStatusTable OBJECT-TYPE gBondPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortStatusEntry SYNTAX SEQUENCE OF GBondPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides overall status information of G.Bond "This table provides overall status information of G.Bond
ports, complementing the generic status information from the ports, complementing the generic status information from the
ifTable of IF-MIB. Additional status information about ifTable of IF-MIB. Additional status information about
connected BCEs is available from the relevant line MIBs connected BCEs is available from the relevant line MIBs
skipping to change at page 26, line 38 skipping to change at page 29, line 29
gBondNumBCEs Unsigned32 gBondNumBCEs Unsigned32
} }
gBondOperScheme OBJECT-TYPE gBondOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current operating bonding scheme of a G.Bond port. "Current operating bonding scheme of a G.Bond port.
The possible values are: The possible values are:
g998.1(1) - G.998.1 bonding g9981(1) - G.998.1 bonding
g998.2(2) - G.998.2 bonding g9982(2) - G.998.2 bonding
g998.3(3) - G.998.3 bonding g9983(3) - G.998.3 bonding
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupOperBondScheme." aGroupOperBondScheme."
REFERENCE REFERENCE
"[WT-159] 5.5.1.4" "[WT-159] 5.5.1.4"
::= { gBondPortStatusEntry 1 } ::= { gBondPortStatusEntry 1 }
gBondPeerOperScheme OBJECT-TYPE gBondPeerOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Curent operating bonding scheme of a G.Bond port link "Curent operating bonding scheme of a G.Bond port link
partner. partner.
The possible values are: The possible values are:
unknown(0) - peer cannot be reached due to the link unknown(0) - peer cannot be reached due to the link
state state
g998.1(1) - G.998.1 bonding g9981(1) - G.998.1 bonding
g998.2(2) - G.998.2 bonding g9982(2) - G.998.2 bonding
g998.3(3) - G.998.3 bonding g9983(3) - G.998.3 bonding
This object maps to the WT-159 attribute This object maps to the WT-159 attribute
aGroupPeerOperBondScheme." aGroupPeerOperBondScheme."
REFERENCE REFERENCE
"[WT-159] 5.5.1.5" "[WT-159] 5.5.1.5"
::= { gBondPortStatusEntry 2 } ::= { gBondPortStatusEntry 2 }
gBondUpDataRate OBJECT-TYPE gBondUpDataRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "bps" UNITS "bps"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 32, line 20 skipping to change at page 35, line 10
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects supporting OPTIONAL G.Bond discovery "A collection of objects supporting OPTIONAL G.Bond discovery
in G.Bond ports." in G.Bond ports."
::= { gBondGroups 2 } ::= { gBondGroups 2 }
gBondMultiSchemeGroup OBJECT-GROUP gBondMultiSchemeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondSchemeSupported, gBondSchemeSupported,
gBondAdminScheme gBondPeerSchemeSupported,
gBondAdminScheme,
gBondPeerAdminScheme
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing OPTIONAL management "A collection of objects providing OPTIONAL management
information for G.Bond ports supporting multiple bonding information for G.Bond ports supporting multiple bonding
schemes." schemes."
::= { gBondGroups 3 } ::= { gBondGroups 3 }
gBondAlarmConfGroup OBJECT-GROUP gBondAlarmConfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 34, line 21 skipping to change at page 37, line 12
MAY lead to a wrongful discovery, for example when two CO ports MAY lead to a wrongful discovery, for example when two CO ports
are connected to the same multi-channel RT port, while both CO are connected to the same multi-channel RT port, while both CO
ports have the same Discovery register value. ports have the same Discovery register value.
o Changing GBS configuration parameters (e.g., profile of a GBS via o Changing GBS configuration parameters (e.g., profile of a GBS via
gBondAdminProfile) MAY lead to anything from link quality and rate gBondAdminProfile) MAY lead to anything from link quality and rate
degradation to a complete link initialization failure, as ability degradation to a complete link initialization failure, as ability
of an G.Bond port to support a particular configuration depends on of an G.Bond port to support a particular configuration depends on
the copper environment. the copper environment.
o Activation of a specific line/channel can cause a severe o Activation of a specific line/channel MAY cause a severe
degradation of service for another G.Bond port, whose channel(s) degradation of service for another G.Bond port, whose channel(s)
MAY be affected by the cross-talk from the newly activated MAY be affected by the cross-talk from the newly activated
channel. channel.
o Removal of a channel from an operationally 'up' G.Bond port, o Removal of a channel from an operationally 'up' G.Bond port,
aggregating several channels, MAY cause port's rate degradation aggregating several channels, MAY cause port's rate degradation
The user of the GBOND-MIB module must therefore be aware that support The user of the GBOND-MIB module must therefore be aware that support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
skipping to change at page 35, line 22 skipping to change at page 38, line 13
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
A new IANAifType value of 'gBond' SHALL be defined by the IANA [1] in Three new values of IANAifType: g9981, g9982 and g9982 SHALL be
the IANAifType-MIB module [IANAifType-MIB], before this document is defined by the IANA [1] in the IANAifType-MIB module
published as an RFC. [IANAifType-MIB], before this document is published as an RFC.
Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL
be allocated by IANA in the MIB-2 transmission sub-tree, before this be allocated by IANA in the MIB-2 transmission sub-tree, before this
document is published. document is published.
9. Acknowledgments 9. Acknowledgments
This document was produced by the [ADSLMIB] working group. This document was produced by the [ADSLMIB] working group.
10. References 10. References
skipping to change at page 36, line 18 skipping to change at page 39, line 9
Statements for SMIv2", STD 58, Statements for SMIv2", STD 58,
RFC 2580, April 1999. RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, [RFC2863] McCloghrie, K. and F. Kastenholz,
"The Interfaces Group MIB", "The Interfaces Group MIB",
RFC 2863, June 2000. RFC 2863, June 2000.
[WT-159] Morgenstern, M., Beili, E., and N. [WT-159] Morgenstern, M., Beili, E., and N.
Nair, "Management Framework for Nair, "Management Framework for
xDSL Bonding", DSL Forum technical xDSL Bonding", DSL Forum technical
report WT-159, Nov 2007. report WT-159, August 2008.
10.2. Informative References 10.2. Informative References
[802.3] IEEE, "IEEE Standard for [802.3] IEEE, "IEEE Standard for
Information technology - Information technology -
Telecommunications and information Telecommunications and information
exchange between systems - Local exchange between systems - Local
and metropolitan area networks - and metropolitan area networks -
Specific requirements - Part 3: Specific requirements - Part 3:
Carrier Sense Multiple Access with Carrier Sense Multiple Access with
skipping to change at page 37, line 24 skipping to change at page 40, line 14
January 2005, <http://www.itu.int/ January 2005, <http://www.itu.int/
rec/T-REC-G.998.2/en>. rec/T-REC-G.998.2/en>.
[G.998.3] ITU-T, "Multi-pair bonding using [G.998.3] ITU-T, "Multi-pair bonding using
time-division inverse time-division inverse
multiplexing", ITU-T multiplexing", ITU-T
Recommendation G.998.3, Recommendation G.998.3,
January 2005, <http://www.itu.int/ January 2005, <http://www.itu.int/
rec/T-REC-G.998.3/en>. rec/T-REC-G.998.3/en>.
[I-D.ietf-adslmib-gbond-atm-mib] Morgenstern, M. and N. Nair, "ATM- [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., Morgenstern, M., and N.
based xDSL Bonded Interfaces MIB", Nair, "ATM-based xDSL Bonded
draft-ietf-adslmib-gbond-atm-mib- Interfaces MIB", draft-ietf-
01 (work in progress), adslmib-gbond-atm-mib-02 (work in
November 2007. progress), September 2008.
[I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern, [I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern,
"Ethernet-based xDSL Bonded "Ethernet-based xDSL Bonded
Interfaces MIB", draft-ietf- Interfaces MIB", draft-ietf-
adslmib-gbond-eth-mib-01 (work in adslmib-gbond-eth-mib-02 (work in
progress), November 2007. progress), September 2008.
[I-D.ietf-adslmib-gbond-tdim-mib] Beili, E. and N. Nair, "TDIM-based [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E. and N. Nair, "TDIM-based
xDSL Bonded Interfaces MIB", draft xDSL Bonded Interfaces MIB", draft
-ietf-adslmib-gbond-tdim-mib-01 -ietf-adslmib-gbond-tdim-mib-02
(work in progress), November 2006. (work in progress),
September 2008.
[I-D.ietf-adslmib-vdsl2-mib] Morgenstern, M., Baillie, S., and [I-D.ietf-adslmib-vdsl2-mib] Morgenstern, M., Baillie, S., and
U. Bonollo, "Definitions of U. Bonollo, "Definitions of
Managed Objects for Very High Managed Objects for Very High
Speed Digital Subscriber Line 2 Speed Digital Subscriber Line 2
(VDSL2)", (VDSL2)",
draft-ietf-adslmib-vdsl2-03 (work draft-ietf-adslmib-vdsl2-06 (work
in progress), October 2007. in progress), July 2008.
[IANAifType-MIB] Internet Assigned Numbers [IANAifType-MIB] Internet Assigned Numbers
Authority (IANA), "IANAifType Authority (IANA), "IANAifType
Textual Convention definition", <h Textual Convention definition", <h
ttp://www.iana.org/assignments/ ttp://www.iana.org/assignments/
ianaiftype-mib>. ianaiftype-mib>.
[RFC2864] McCloghrie, K. and G. Hanson, "The [RFC2864] McCloghrie, K. and G. Hanson, "The
Inverted Stack Table Extension to Inverted Stack Table Extension to
the Interfaces Group MIB", the Interfaces Group MIB",
skipping to change at page 38, line 24 skipping to change at page 41, line 16
Internet-Standard Management Internet-Standard Management
Framework", RFC 3410, Framework", RFC 3410,
December 2002. December 2002.
[RFC3440] Ly, F. and G. Bathrick, [RFC3440] Ly, F. and G. Bathrick,
"Definitions of Extension Managed "Definitions of Extension Managed
Objects for Asymmetric Digital Objects for Asymmetric Digital
Subscriber Lines", RFC 3440, Subscriber Lines", RFC 3440,
December 2002. December 2002.
[RFC3635] Flick, J., "Definitions of Managed
Objects for the Ethernet-like
Interface Types", RFC 3635,
September 2003.
[RFC3728] Ray, B. and R. Abbi, "Definitions [RFC3728] Ray, B. and R. Abbi, "Definitions
of Managed Objects for Very High of Managed Objects for Very High
Speed Digital Subscriber Lines Speed Digital Subscriber Lines
(VDSL)", RFC 3728, February 2004. (VDSL)", RFC 3728, February 2004.
[RFC4181] Heard, C., "Guidelines for Authors [RFC4181] Heard, C., "Guidelines for Authors
and Reviewers of MIB Documents", and Reviewers of MIB Documents",
BCP 111, RFC 4181, September 2005. BCP 111, RFC 4181, September 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, [RFC4319] Sikes, C., Ray, B., and R. Abbi,
skipping to change at page 41, line 7 skipping to change at page 43, line 7
Wipro Technologies Wipro Technologies
Keonics Electronics City Keonics Electronics City
Bangalore 560 100 Bangalore 560 100
India India
Phone: +91-80-2852-0408 x85338 Phone: +91-80-2852-0408 x85338
EMail: narendranath.nair@wipro.com EMail: narendranath.nair@wipro.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 41, line 44 skipping to change at line 1961
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 78 change blocks. 
129 lines changed or deleted 221 lines changed or added

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