< draft-ietf-adslmib-gbond-mib-10.txt   draft-ietf-adslmib-gbond-mib-11.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: September 13, 2012 ECI Telecom Expires: January 17, 2013 ECI Telecom
Mar 12, 2012 Jul 16, 2012
xDSL multi-pair bonding (G.Bond) MIB xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-10.txt draft-ietf-adslmib-gbond-mib-11.txt
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 defines an extension to the Interfaces Group MIB with a
a set of common objects for managing multi-pair bonded Digital 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 textual conventions defining the
bonding technology are defined in G9981-MIB, G9982-MIB and G9983-MIB bonding schemes are contained in a separate Internet Assigned Number
respectively. Authority (IANA) maintained MIB module. The MIB modules specific to
each bonding technology are defined in G9981-MIB, G9982-MIB and
G9983-MIB respectively.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on September 13, 2012. This Internet-Draft will expire on January 17, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 25
3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4
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. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7 4.1.2. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7
4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 10 4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 10
4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules . . . 11 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules . . . 11
4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 12 4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 12
4.4. Addition of new bonding schemes . . . . . . . . . . . . . 12
5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 12 5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 13
5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 13 5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 13
6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 17 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 62 7. IANA-maintained G.Bond TC Definitions . . . . . . . . . . . . 62
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 8. Security Considerations . . . . . . . . . . . . . . . . . . . 64
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 66
10.1. Normative References . . . . . . . . . . . . . . . . . . . 64 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67
10.2. Informative References . . . . . . . . . . . . . . . . . . 66 11.1. Normative References . . . . . . . . . . . . . . . . . . . 67
11.2. Informative References . . . . . . . . . . . . . . . . . . 68
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 Currently there are three xDSL Multi-Pair Bonding schemes, also known
collective name G.Bond: under collective name G.Bond:
o The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1 o The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1
recommendation [G.998.1], which defines a method for bonding (or recommendation [G.998.1], which defines a method for bonding (or
aggregating) of multiple xDSL lines (or individual bearer channels aggregating) of multiple xDSL lines (or individual bearer channels
in multiple xDSL lines) into a single bi-directional logical link in multiple xDSL lines) into a single bi-directional logical link
carrying an ATM stream. This specification can be viewed as an carrying an ATM stream. This specification can be viewed as an
evolution of the legacy Inverse Multiplexing over ATM (IMA) evolution of the legacy Inverse Multiplexing over ATM (IMA)
technology [af-phy-0086], applied to xDSL with variable rates on technology [af-phy-0086], applied to xDSL with variable rates on
each line/bearer channel. each line/bearer channel.
skipping to change at page 4, line 12 skipping to change at page 4, line 12
layers with variable rates, providing common functionality for the layers with variable rates, providing common functionality for the
configuration, initialization, operation and monitoring of the bonded configuration, initialization, operation and monitoring of the bonded
link. link.
This document defines a MIB module common to all 3 schemes. This document defines a MIB module common to all 3 schemes.
Additional managed objects, specific to each bonding technology, are Additional managed objects, specific to each bonding technology, are
defined in G9981-MIB [I-D.ietf-adslmib-gbond-atm-mib], G9982-MIB defined in G9981-MIB [I-D.ietf-adslmib-gbond-atm-mib], G9982-MIB
[I-D.ietf-adslmib-gbond-eth-mib] and G9983-MIB [I-D.ietf-adslmib-gbond-eth-mib] and G9983-MIB
[I-D.ietf-adslmib-gbond-tdim-mib] modules. [I-D.ietf-adslmib-gbond-tdim-mib] modules.
The textual conventions listing the bonding schemes are defined in a
separate, IANA-maintained MIB module, first version of which is
provided in this document. This arrangement would allow for future
bonding schemes to be easily supported, without the need to update
the common GBOND-MIB module,
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 5, line 37 skipping to change at page 5, line 40
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 g9981(263), g9982(264) or separate interface with an ifType reflecting a particular bonding
g9983(265) for a particular bonding scheme. scheme, e.g., g9981(263), g9982(264) or g9983(265).
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: g9981(263), g9982(264) | (TPS-TC) | v ifType: g9981(263), g9982(264)
+-----------------+---+-------+ - or g9983(265) +-----------------+---+-------+ - g9983(265), etc.
| TPS-TC \ | | | ^ | TPS-TC \ | | | ^
+---------\ | | | | N ifEntry (N=1..32) +---------\ | | | | N ifEntry (N=1..32)
| PMS-TC )BCE 1 |...| BCE N | ) ifType: adsl(94), shdsl(169), | PMS-TC )BCE 1 |...| BCE N | ) ifType: adsl(94), shdsl(169),
+---------/ | | | | vdsl(97), vdsl2(251), +---------/ | | | | vdsl(97), vdsl2(251),
| PMD / | | | v etc. | PMD / | | | v etc.
'-----------------+---+-------' - '-----------------+---+-------' -
BCE - Bonding Channel Entity BCE - Bonding Channel Entity
GBS - Generic Bonded Sub-layer GBS - Generic Bonded Sub-layer
PMD - Physical Medium Dependent PMD - Physical Medium Dependent
skipping to change at page 7, line 32 skipping to change at page 7, line 32
The Ethernet frames MAY be fragmented before the transmission and The Ethernet frames MAY be fragmented before the transmission and
reassembled at the remote end to minimize transportation delay. The reassembled at the remote end to minimize transportation delay. The
G.998.2 (G.Bond/Ethernet) ports with multiple BCEs MUST perform the G.998.2 (G.Bond/Ethernet) ports with multiple BCEs MUST perform the
fragmentation and reassembly of the Ethernet frames. However for a fragmentation and reassembly of the Ethernet frames. However for a
single-BCE G.998.2 ports this function MAY be omitted (a.k.a. bonding single-BCE G.998.2 ports this function MAY be omitted (a.k.a. bonding
bypass), to minimize fragmentation overhead and additional processing bypass), to minimize fragmentation overhead and additional processing
delay as well as to be able to interoperate with non-G.998 DSL delay as well as to be able to interoperate with non-G.998 DSL
equipment. equipment.
The agent is REQUIRED to indicate all supported bonding schemes (ATM, The agent is REQUIRED to indicate all supported bonding schemes (for
Ethernet and TDIM), including OPTIONAL support for the bonding bypass example ATM, Ethernet and TDIM), including OPTIONAL support for the
in G.998.2 single-BCE ports. bonding bypass in G.998.2 single-BCE ports.
The GBOND-MIB module allows a Network Management application to query The GBOND-MIB module allows a Network Management application to query
Bonding capability and enable/disable it if supported. Note that Bonding capability and enable/disable it if supported. Note that
enabling Bonding (by setting the value of gBondPortConfAdminScheme enabling Bonding (by setting the value of gBondPortConfAdminScheme
and gBondPortConfAdminScheme objects to any supported bonding scheme and gBondPortConfAdminScheme objects to any supported bonding scheme
other than 'none') effectively turns on fragmentation and re-assembly other than 'none') effectively turns on fragmentation and re-assembly
function, even on a single-BCE port. function, even on a single-BCE port.
4.1.3. Discovery Operation 4.1.3. Discovery Operation
skipping to change at page 11, line 46 skipping to change at page 11, line 46
| | the real operational status of a BCE/GBS port, | | | the real operational status of a BCE/GBS port, |
| | e.g. a GBS port may be operationally 'up' with | | | e.g. a GBS port may be operationally 'up' with |
| | gBondPortStatFltStatus indicating lowRate(4) | | | gBondPortStatFltStatus indicating lowRate(4) |
| | fault condition, or 'down' with no gBond faults. | | | fault condition, or 'down' with no gBond faults. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1: G.Bond interpretation of IF-MIB objects Table 1: G.Bond interpretation of IF-MIB objects
4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules
The MIB module defined in this document is common to all three G.998 The MIB module defined in this document is common to all G.998
bonding schemes. It MUST be used in conjunction with a bonding bonding schemes. It MUST be used in conjunction with a bonding
scheme-specific MIB module: scheme-specific MIB module:
o G9981-MIB [I-D.ietf-adslmib-gbond-atm-mib] for a G.998.1 bonded o G9981-MIB [I-D.ietf-adslmib-gbond-atm-mib] for a G.998.1 bonded
interface. interface.
o G9982-MIB [I-D.ietf-adslmib-gbond-eth-mib] for a G.998.2 bonded o G9982-MIB [I-D.ietf-adslmib-gbond-eth-mib] for a G.998.2 bonded
interface. interface.
o G9983-MIB [I-D.ietf-adslmib-gbond-tdim-mib] for a G.998.3 bonded o G9983-MIB [I-D.ietf-adslmib-gbond-tdim-mib] for a G.998.3 bonded
skipping to change at page 12, line 21 skipping to change at page 12, line 21
4.3. Relationship to xDSL MIB modules 4.3. Relationship to xDSL MIB modules
Each xDSL technology is described in a relevant xDSL line MIB module: Each xDSL technology is described in a relevant xDSL line MIB module:
e.g., HDSL2-SHDSL-LINE-MIB [RFC4319] for G.SHDSL, ADSL-LINE-EXT-MIB e.g., HDSL2-SHDSL-LINE-MIB [RFC4319] for G.SHDSL, ADSL-LINE-EXT-MIB
[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 [RFC5650] for VDSL2. [RFC3728] for VDSL or VDSL2-LINE-MIB [RFC5650] for VDSL2.
These MIB moduless are used to manage individual xDSL lines/channels These MIB moduless are used to manage individual xDSL lines/channels
(BCEs). (BCEs).
4.4. Addition of new bonding schemes
In case a new bonding scheme is introduced in a revision of G.998,
IANA can update the IANA-maintained MIB module, adding the
corresponding new value, to the IANAgBondScheme and
IANAgBondSchemeList textual conventions, as well as listing the new
scheme-specific MIB module's name (e.g. G998x-MIB).
Any scheme-specific aspect of an existing GBOND-MIB object SHALL be
described in the corresponding G998x-MIB module, to prevent an
unnesessary re-issue of the GBOND-MIB module. For example, an exact
definition of an Errored Second (ES) or a Severely Errored Second
(SES) can be bonding-scheme specific, see the definition for
gBondPortPmCurES and gBondPortPmCurSES objects.
5. MIB Structure 5. MIB Structure
5.1. Overview 5.1. Overview
The main management objects defined in the GBOND-MIB module are split The main management objects defined in the GBOND-MIB module are split
into 2 groups, structured as recommended by RFC 4181 [RFC4181]: into 2 groups, structured as recommended by RFC 4181 [RFC4181]:
o gBondPort - containing objects for configuration, capabilities, o gBondPort - containing objects for configuration, capabilities,
status, historical performance monitoring and notifications, status, historical performance monitoring and notifications,
common to all G.Bond ports (GBS). common to all G.Bond ports (GBS).
skipping to change at page 13, line 37 skipping to change at page 14, line 4
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 Package | | | oBondingGroup - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupID | ifIndex (IF-MIB) | | aGroupID | ifIndex (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
+-------------------------------+-----------------------------------+
| aGroupBondSchemesSupported | gBondPortCapSchemesSupported | | aGroupBondSchemesSupported | gBondPortCapSchemesSupported |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPeerBondSchemesSupporte | gBondPortCapPeerSchemesSupported | | aGroupPeerBondSchemesSupporte | gBondPortCapPeerSchemesSupported |
| d | | | d | |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupAdminBondScheme | gBondPortConfAdminScheme | | aGroupAdminBondScheme | gBondPortConfAdminScheme |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPeerAdminBondScheme | gBondPortConfPeerAdminScheme | | aGroupPeerAdminBondScheme | gBondPortConfPeerAdminScheme |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupOperBondScheme | gBondPortStatOperScheme | | aGroupOperBondScheme | gBondPortStatOperScheme |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPeerOperBondScheme | gBondPortStatPeerOperScheme | | aGroupPeerOperBondScheme | gBondPortStatPeerOperScheme |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupEnd | gBondPortStatSide | | aGroupEnd | gBondPortStatSide |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
+-------------------------------+-----------------------------------+
| aGroupOperState | ifOperStatus (IF-MIB) | | aGroupOperState | ifOperStatus (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupAdminState | ifAdminStatus (IF-MIB) | | aGroupAdminState | ifAdminStatus (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupStatus | gBondPortStatFltStatus | | aGroupStatus | gBondPortStatFltStatus |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupCapacity | gBondPortCapCapacity | | aGroupCapacity | gBondPortCapCapacity |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPeerCapacity | gBondPortCapPeerCapacity | | aGroupPeerCapacity | gBondPortCapPeerCapacity |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
skipping to change at page 14, line 37 skipping to change at page 15, line 4
| aGroupTargetDownRate | gBondPortConfTargetDnDataRate | | aGroupTargetDownRate | gBondPortConfTargetDnDataRate |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupThreshLowUpRate | gBondPortConfThreshLowUpRate | | aGroupThreshLowUpRate | gBondPortConfThreshLowUpRate |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupThreshLowDownRate | gBondPortConfThreshLowDnRate | | aGroupThreshLowDownRate | gBondPortConfThreshLowDnRate |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupLowRateCrossingEnable | gBondPortConfLowRateCrossingEnabl | | aGroupLowRateCrossingEnable | gBondPortConfLowRateCrossingEnabl |
| | e | | | e |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing | | nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+-------------------------------+-----------------------------------+
| nGroupLowDownRateCrossing | gBondLowDnRateCrossing | | nGroupLowDownRateCrossing | gBondLowDnRateCrossing |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupLinkUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) | | aGroupLinkUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupLinkUp | linkDown (IF-MIB) | | nGroupLinkUp | linkDown (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupLinkDown | linkUp (IF-MIB) | | nGroupLinkDown | linkUp (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| oBondingGroup - PM Package | | | oBondingGroup - PM Package | |
| (Optional) | | | (Optional) | |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfES | gBondPortPmCurES | | aGroupPerfES | gBondPortPmCurES |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfSES | gBondPortPmCurSES | | aGroupPerfSES | gBondPortPmCurSES |
+-------------------------------+-----------------------------------+
| aGroupPerfUAS | gBondPortPmCurUAS | | aGroupPerfUAS | gBondPortPmCurUAS |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf15MinValidIntervals | gBondPortPmCur15MinValidIntervals | | aGroupPerf15MinValidIntervals | gBondPortPmCur15MinValidIntervals |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf15MinInvalidInterva | gBondPortPmCur15MinInvalidInterva | | aGroupPerf15MinInvalidInterva | gBondPortPmCur15MinInvalidInterva |
| ls | ls | | ls | ls |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfCurr15MinTimeElapse | gBondPortPmCur15MinTimeElapsed | | aGroupPerfCurr15MinTimeElapse | gBondPortPmCur15MinTimeElapsed |
| d | | | d | |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
skipping to change at page 15, line 37 skipping to change at page 16, line 4
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfThreshold15MinUAS | gBondPortPmTcaProfileThresh15MinU | | aGroupPerfThreshold15MinUAS | gBondPortPmTcaProfileThresh15MinU |
| | AS | | | AS |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupPerfTca15MinES | gBondPmTca15MinESCrossing | | nGroupPerfTca15MinES | gBondPmTca15MinESCrossing |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupPerfTca15MinSES | gBondPmTca15MinSESCrossing | | nGroupPerfTca15MinSES | gBondPmTca15MinSESCrossing |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupPerfTca15MinUAS | gBondPmTca15MinUASCrossing | | nGroupPerfTca15MinUAS | gBondPmTca15MinUASCrossing |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
+-------------------------------+-----------------------------------+
| aGroupPerf1DayValidIntervals | gBondPortPmCur1DayValidIntervals | | aGroupPerf1DayValidIntervals | gBondPortPmCur1DayValidIntervals |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf1DayInvalidInterval | gBondPortPmCur1DayInvalidInterval | | aGroupPerf1DayInvalidInterval | gBondPortPmCur1DayInvalidInterval |
| s | s | | s | s |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfCurr1DayTimeElapsed | gBondPortPmCur1DayTimeElapsed | | aGroupPerfCurr1DayTimeElapsed | gBondPortPmCur1DayTimeElapsed |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfCurr1DayES | gBondPortPmCur1DayIntervalES | | aGroupPerfCurr1DayES | gBondPortPmCur1DayIntervalES |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfCurr1DaySES | gBondPortPmCur1DayIntervalSES | | aGroupPerfCurr1DaySES | gBondPortPmCur1DayIntervalSES |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfCurr1DayUAS | gBondPortPmCur1DayIntervalUAS | | aGroupPerfCurr1DayUAS | gBondPortPmCur1DayIntervalUAS |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfThreshold1DayES | gBondPortPmTcaProfileThresh1DayES | | aGroupPerfThreshold1DayES | gBondPortPmTcaProfileThresh1DayES |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
+-------------------------------+-----------------------------------+
| aGroupPerfThreshold1DaySES | gBondPortPmTcaProfileThresh1DaySE | | aGroupPerfThreshold1DaySES | gBondPortPmTcaProfileThresh1DaySE |
| | S | | | S |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerfThreshold1DayUAS | gBondPortPmTcaProfileThresh1DayUA | | aGroupPerfThreshold1DayUAS | gBondPortPmTcaProfileThresh1DayUA |
| | S | | | S |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupPerfTca1DayES | gBondPmTca1DayESCrossing | | nGroupPerfTca1DayES | gBondPmTca1DayESCrossing |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nGroupPerfTca1DaySES | gBondPmTca1DaySESCrossing | | nGroupPerfTca1DaySES | gBondPmTca1DaySESCrossing |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
skipping to change at page 16, line 37 skipping to change at page 17, line 4
| aGroupPerf1DayIntervalNumber | gBondPortPm1DayIntervalIndex | | aGroupPerf1DayIntervalNumber | gBondPortPm1DayIntervalIndex |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf1DayIntervalValid | gBondPortPm1DayIntervalValid | | aGroupPerf1DayIntervalValid | gBondPortPm1DayIntervalValid |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf1DayIntervalMoniSec | gBondPortPm1DayIntervalMoniTime | | aGroupPerf1DayIntervalMoniSec | gBondPortPm1DayIntervalMoniTime |
| s | | | s | |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf1DayIntervalES | gBondPortPm1DayIntervalES | | aGroupPerf1DayIntervalES | gBondPortPm1DayIntervalES |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aGroupPerf1DayIntervalSES | gBondPortPm1DayIntervalSES | | aGroupPerf1DayIntervalSES | gBondPortPm1DayIntervalSES |
+-------------------------------+-----------------------------------+
| aGroupPerf1DayIntervalUAS | gBondPortPm1DayIntervalUAS | | aGroupPerf1DayIntervalUAS | gBondPortPm1DayIntervalUAS |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| oLine - Basic Package | | | oLine - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineID | ifIndex (IF-MIB) | | aLineID | ifIndex (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineType | ifType (IF-MIB) | | aLineType | ifType (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineOperState | ifOperStatus (IF-MIB) | | aLineOperState | ifOperStatus (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) | | aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineEnd | *dsl*Side (*DSL-LINE-MIB) | | aLineEnd | *dsl*Side (*DSL-LINE-MIB) |
+-------------------------------+-----------------------------------+
| aLineAdminState | ifAdminStatus (IF-MIB) | | aLineAdminState | ifAdminStatus (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineRemoteDiscoveryCode | gBondBceConfRemoteDiscoveryCode | | aLineRemoteDiscoveryCode | gBondBceConfRemoteDiscoveryCode |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| aLineUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) | | aLineUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nLineUp | linkUp (IF-MIB) | | nLineUp | linkUp (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
| nLineDown | linkDown (IF-MIB) | | nLineDown | linkDown (IF-MIB) |
+-------------------------------+-----------------------------------+ +-------------------------------+-----------------------------------+
skipping to change at page 18, line 17 skipping to change at page 18, line 32
ifIndex ifIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
HCPerfCurrentCount, HCPerfCurrentCount,
HCPerfIntervalCount, HCPerfIntervalCount,
HCPerfIntervalThreshold, HCPerfIntervalThreshold,
HCPerfValidIntervals, HCPerfValidIntervals,
HCPerfInvalidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed, HCPerfTimeElapsed,
HCPerfTotalCount HCPerfTotalCount
FROM HC-PerfHist-TC-MIB -- [RFC3705] FROM HC-PerfHist-TC-MIB -- [RFC3705]
IANAgBondScheme,
IANAgBondSchemeList
FROM IANA-GBOND-TC-MIB
; ;
------------------------------------------------------------------------ ------------------------------------------------------------------------
gBondMIB MODULE-IDENTITY gBondMIB MODULE-IDENTITY
LAST-UPDATED "201203120000Z" -- Mar 12, 2012 LAST-UPDATED "201207160000Z" -- Jul 16, 2012
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
skipping to change at page 19, line 51 skipping to change at page 20, line 21
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer GBS - Generic Bonding Sublayer
PM - Performance Monitoring PM - Performance Monitoring
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCA - Threshold Crossing Alert TCA - Threshold Crossing Alert
Copyright (C) The IETF Trust (2012). Copyright (C) The IETF Trust (2012).
This version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "201203120000Z" -- Mar 12, 2012 REVISION "201207160000Z" -- Jul 16, 2012
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.
-- Sections of the module -- Sections of the module
-- Structured as recommended by [RFC4181], Appendix D -- Structured as recommended by [RFC4181], Appendix D
skipping to change at page 20, line 27 skipping to change at page 20, line 47
gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 } gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 }
-- Groups in the module -- Groups in the module
gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 } gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 }
gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 } gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 }
-- Textual Conventions -- Textual Conventions
GBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines a bitmap of possible ITU-T
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
bit values g9981(1), g9982(2) and g9983(3), respectively.
An additional value of none(0), can be returned as a result
of GET operation, when an value of the object cannot be
determined (for example a peer GBS cannot be reached), the port
does not support any kind of bonding or when a single-BCE
G.998.2 GBS supports bonding (frame fragmentation/reassembly)
bypass."
SYNTAX BITS {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
GBondScheme ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are:
none(0) - no bonding (e.g. on single-BCE G.998.2 GBS) or
unknown
g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernet)
g9983(3) - G.998.3 (G.Bond/TDIM)."
SYNTAX INTEGER {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention defines a range of values that may be "This textual convention defines a range of values that may be
set in a fault threshold alarm control for a 1-day performance set in a fault threshold alarm control for a 1-day performance
monitoring interval. monitoring interval.
As the number of seconds in a 1-day interval numbers at most As the number of seconds in a 1-day interval numbers at most
86400, objects of this type may have a range of 0...86400, 86400, objects of this type may have a range of 0...86400,
where the value of 0 disables the alarm." where the value of 0 disables the alarm."
skipping to change at page 21, line 41 skipping to change at page 21, line 22
gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 } gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 }
gBondLowUpRateCrossing NOTIFICATION-TYPE gBondLowUpRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific GBS -- ifIndex is not needed here since we are under specific GBS
gBondPortStatUpDataRate, gBondPortStatUpDataRate,
gBondPortConfThreshLowUpRate gBondPortConfThreshLowUpRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the G.Bond port' upstream "This notification indicates that the G.Bond port's upstream
data rate has reached/dropped below or exceeded the low data rate has reached/dropped below or exceeded the low
upstream rate threshold, specified by upstream rate threshold, specified by
gBondPortConfThreshLowUpRate. gBondPortConfThreshLowUpRate.
This notification MAY be sent for the -O subtype ports This notification MAY be sent for the -O subtype ports
while the port is up, on the crossing event in both while the port is up, on the crossing event in both
directions: from normal (rate is above the threshold) to low directions: from normal (rate is above the threshold) to low
(rate equals the threshold or below it) and from low to (rate equals the threshold or below it) and from low to
normal. This notification is not applicable to the -R normal. This notification is not applicable to the -R
subtypes. subtypes.
skipping to change at page 22, line 36 skipping to change at page 22, line 19
::= { gBondPortNotifications 1 } ::= { gBondPortNotifications 1 }
gBondLowDnRateCrossing NOTIFICATION-TYPE gBondLowDnRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific GBS -- ifIndex is not needed here since we are under specific GBS
gBondPortStatDnDataRate, gBondPortStatDnDataRate,
gBondPortConfThreshLowDnRate gBondPortConfThreshLowDnRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the G.Bond port' downstream "This notification indicates that the G.Bond port's downstream
data rate has reached/dropped below or exceeded the low data rate has reached/dropped below or exceeded the low
downstream rate threshold, specified by downstream rate threshold, specified by
gBondPortConfThreshLowDnRate. gBondPortConfThreshLowDnRate.
This notification MAY be sent for the -O subtype ports This notification MAY be sent for the -O subtype ports
while the port is up, on the crossing event in both while the port is up, on the crossing event in both
directions: from normal (rate is above the threshold) to low directions: from normal (rate is above the threshold) to low
(rate equals the threshold or below it) and from low to (rate equals the threshold or below it) and from low to
normal. This notification is not applicable to the -R normal. This notification is not applicable to the -R
subtypes. subtypes.
skipping to change at page 26, line 36 skipping to change at page 26, line 17
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Configuration table. "An entry in the G.Bond Port Configuration table.
Each entry represents a G.Bond port indexed by the ifIndex. Each entry represents a 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 }
::= { gBondPortConfTable 1 } ::= { gBondPortConfTable 1 }
GBondPortConfEntry ::= GBondPortConfEntry ::=
SEQUENCE { SEQUENCE {
gBondPortConfAdminScheme GBondScheme, gBondPortConfAdminScheme IANAgBondScheme,
gBondPortConfPeerAdminScheme GBondScheme, gBondPortConfPeerAdminScheme IANAgBondScheme,
gBondPortConfDiscoveryCode PhysAddress, gBondPortConfDiscoveryCode PhysAddress,
gBondPortConfTargetUpDataRate Unsigned32, gBondPortConfTargetUpDataRate Unsigned32,
gBondPortConfTargetDnDataRate Unsigned32, gBondPortConfTargetDnDataRate Unsigned32,
gBondPortConfThreshLowUpRate Unsigned32, gBondPortConfThreshLowUpRate Unsigned32,
gBondPortConfThreshLowDnRate Unsigned32, gBondPortConfThreshLowDnRate Unsigned32,
gBondPortConfLowRateCrossingEnable TruthValue, gBondPortConfLowRateCrossingEnable TruthValue,
gBondPortConfPmTcaConfProfile SnmpAdminString, gBondPortConfPmTcaConfProfile SnmpAdminString,
gBondPortConfPmTcaEnable TruthValue gBondPortConfPmTcaEnable TruthValue
} }
gBondPortConfAdminScheme OBJECT-TYPE gBondPortConfAdminScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX IANAgBondScheme
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired bonding scheme for a G.Bond GBS 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:
none(0) - instructs the port not to use bonding none(0) - instructs the port not to use bonding
(only on single-BCE G.998.2 GBS) (only on single-BCE G.998.2 GBS)
g9981(1) - instructs the port to use G.998.1 bonding g9981(1) - instructs the port to use G.998.1 bonding
g9982(2) - instructs the port to use G.998.2 bonding g9982(2) - instructs the port to use G.998.2 bonding
skipping to change at page 27, line 30 skipping to change at page 27, line 12
rejected (in case of SNMP with the error wrongValue). rejected (in case of SNMP with the error wrongValue).
Setting this object to the value of 'none' must be rejected for Setting this object to the value of 'none' must be rejected for
GBS ports with multiple BCEs (with the error inconsistentValue). GBS ports with multiple BCEs (with the error inconsistentValue).
This object maps to the TR-159 attribute aGroupAdminBondScheme." This object maps to the TR-159 attribute aGroupAdminBondScheme."
REFERENCE REFERENCE
"[TR-159] 5.5.1.6; IF-MIB, ifAdminStatus" "[TR-159] 5.5.1.6; IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 1 } ::= { gBondPortConfEntry 1 }
gBondPortConfPeerAdminScheme OBJECT-TYPE gBondPortConfPeerAdminScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX IANAgBondScheme
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired bonding scheme for a peer (link partner) G.Bond "A desired bonding scheme for a peer (link partner) G.Bond
port (GBS). port (GBS).
The following values instruct the peer port to use The following values instruct the peer port to use
corresponding bonding scheme if supported: corresponding bonding scheme if supported:
none(0) - instructs the port not to use bonding none(0) - instructs the port not to use bonding
(only on single-BCE G.998.2 GBS) (only on single-BCE G.998.2 GBS)
g9981(1) - instructs the port to use G.998.1 bonding g9981(1) - instructs the port to use G.998.1 bonding
skipping to change at page 33, line 42 skipping to change at page 33, line 25
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Capability table. "An entry in the G.Bond Port Capability table.
Each entry represents a G.Bond port indexed by the ifIndex. Each entry represents a 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 }
::= { gBondPortCapTable 1 } ::= { gBondPortCapTable 1 }
GBondPortCapEntry ::= GBondPortCapEntry ::=
SEQUENCE { SEQUENCE {
gBondPortCapSchemesSupported GBondSchemeList, gBondPortCapSchemesSupported IANAgBondSchemeList,
gBondPortCapPeerSchemesSupported GBondSchemeList, gBondPortCapPeerSchemesSupported IANAgBondSchemeList,
gBondPortCapCapacity Unsigned32, gBondPortCapCapacity Unsigned32,
gBondPortCapPeerCapacity Unsigned32 gBondPortCapPeerCapacity Unsigned32
} }
gBondPortCapSchemesSupported OBJECT-TYPE gBondPortCapSchemesSupported OBJECT-TYPE
SYNTAX GBondSchemeList SYNTAX IANAgBondSchemeList
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 various bit-positions are: the GBS. The various bit-positions are:
none(0) - GBS is capable of bonding bypass on a none(0) - GBS is capable of bonding bypass on a
single-BCE (G.998.2 only) single-BCE (G.998.2 only)
g9981(1) - GBS is capable of G.998.1 bonding g9981(1) - GBS is capable of G.998.1 bonding
g9982(2) - GBS is capable of G.998.2 bonding g9982(2) - GBS is capable of G.998.2 bonding
skipping to change at page 34, line 22 skipping to change at page 34, line 4
g9982(2) - GBS is capable of G.998.2 bonding g9982(2) - GBS is capable of G.998.2 bonding
g9983(3) - GBS is capable of G.998.3 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 gBondPortConfAdminScheme actual administrative scheme is set via gBondPortConfAdminScheme
object. The current operating bonding scheme is reflected in object. The current operating bonding scheme is reflected in
the gBondPortStatOperScheme. the gBondPortStatOperScheme.
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupBondSchemesSupported." aGroupBondSchemesSupported."
REFERENCE REFERENCE
"[TR-159] 5.5.1.2" "[TR-159] 5.5.1.2"
::= { gBondPortCapEntry 1 } ::= { gBondPortCapEntry 1 }
gBondPortCapPeerSchemesSupported OBJECT-TYPE gBondPortCapPeerSchemesSupported OBJECT-TYPE
SYNTAX GBondSchemeList SYNTAX IANAgBondSchemeList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bonding Capability of the peer G.Bond port (GBS). This is a "Bonding Capability of the peer 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 link partner GBS. The various bit-positions are: the link partner GBS. The various bit-positions are:
none(0) - peer GBS does not support bonding or none(0) - peer GBS does not support bonding or
the peer unit could not be reached or the peer unit could not be reached or
peer GBS is capable of bonding bypass on a peer GBS is capable of bonding bypass on a
single-BCE (G.998.2 only) single-BCE (G.998.2 only)
skipping to change at page 36, line 14 skipping to change at page 35, line 44
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Status table. "An entry in the G.Bond Port Status table.
Each entry represents a G.Bond port indexed by the ifIndex. Each entry represents a 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 }
::= { gBondPortStatTable 1 } ::= { gBondPortStatTable 1 }
GBondPortStatEntry ::= GBondPortStatEntry ::=
SEQUENCE { SEQUENCE {
gBondPortStatOperScheme GBondScheme, gBondPortStatOperScheme IANAgBondScheme,
gBondPortStatPeerOperScheme GBondScheme, gBondPortStatPeerOperScheme IANAgBondScheme,
gBondPortStatUpDataRate Gauge32, gBondPortStatUpDataRate Gauge32,
gBondPortStatDnDataRate Gauge32, gBondPortStatDnDataRate Gauge32,
gBondPortStatFltStatus BITS, gBondPortStatFltStatus BITS,
gBondPortStatSide INTEGER, gBondPortStatSide INTEGER,
gBondPortStatNumBCEs Unsigned32 gBondPortStatNumBCEs Unsigned32
} }
gBondPortStatOperScheme OBJECT-TYPE gBondPortStatOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX IANAgBondScheme
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:
none(0) - bonding bypass on a single-BCE (G.998.2 only) none(0) - bonding bypass on a single-BCE (G.998.2 only)
g9981(1) - G.998.1 bonding g9981(1) - G.998.1 bonding
g9982(2) - G.998.2 bonding g9982(2) - G.998.2 bonding
g9983(3) - G.998.3 bonding g9983(3) - G.998.3 bonding
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupOperBondScheme." aGroupOperBondScheme."
REFERENCE REFERENCE
"[TR-159] 5.5.1.4" "[TR-159] 5.5.1.4"
::= { gBondPortStatEntry 1 } ::= { gBondPortStatEntry 1 }
gBondPortStatPeerOperScheme OBJECT-TYPE gBondPortStatPeerOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX IANAgBondScheme
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current operating bonding scheme of a G.Bond port link partner. "Current operating bonding scheme of a G.Bond port link partner.
The possible values are: The possible values are:
unknown(0) - peer cannot be reached due to the link state or unknown(0) - peer cannot be reached due to the link state or
bonding bypass on a single-BCE (G.998.2 only) bonding bypass on a single-BCE (G.998.2 only)
g9981(1) - G.998.1 bonding g9981(1) - G.998.1 bonding
g9982(2) - G.998.2 bonding g9982(2) - G.998.2 bonding
g9983(3) - G.998.3 bonding g9983(3) - G.998.3 bonding
skipping to change at page 62, line 23 skipping to change at page 62, line 6
supporting Performance Monitoring Threshold Crossing Alert supporting Performance Monitoring Threshold Crossing Alert
notifications." notifications."
GROUP gBondPmTcaNotificationGroup GROUP gBondPmTcaNotificationGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting Performance Monitoring Threshold Crossing Alert supporting Performance Monitoring Threshold Crossing Alert
notifications." notifications."
OBJECT gBondPortCapSchemesSupported OBJECT gBondPortCapSchemesSupported
SYNTAX GBondSchemeList SYNTAX IANAgBondSchemeList
DESCRIPTION DESCRIPTION
"Support for all bonding Schemes types is not required. "Support for all bonding Schemes types is not required.
However at least one value SHALL be supported" However at least one value SHALL be supported"
OBJECT gBondPortCapPeerSchemesSupported OBJECT gBondPortCapPeerSchemesSupported
SYNTAX GBondSchemeList SYNTAX IANAgBondSchemeList
DESCRIPTION DESCRIPTION
"Support for all bonding Schemes types is not required. "Support for all bonding Schemes types is not required.
However at least one value SHALL be supported" However at least one value SHALL be supported"
::= { gBondCompliances 1 } ::= { gBondCompliances 1 }
END END
7. Security Considerations 7. IANA-maintained G.Bond TC Definitions
IANA-GBOND-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
;
------------------------------------------------------------------------
ianaGBondTcMIB MODULE-IDENTITY
LAST-UPDATED "201207160000Z" -- July 16, 2012
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1-310-823-9358
EMail: iana@iana.org"
DESCRIPTION
"This MIB module defines IANAgBondScheme and IANAgBondSchemeList
TEXTUAL-CONVENTIONs, specifying enumerated values of the
gBondPortConfAdminScheme, gBondPortConfPeerAdminScheme,
gBondPortStatOperScheme, gBondPortStatPeerOperScheme and
gBondPortCapSchemesSupported, gBondPortCapPeerSchemesSupported
objects respectively, defined in the GBOND-MIB.
It is intended that each new bonding scheme defined by the
ITU-T Q4/SG15 working group and approved for publication in a
revision of ITU-T G.998 specification will be added to this MIB
module, provided that it is suitable for being managed by the base
objects in the GBOND-MIB. An Expert Review, as defined in
RFC 5226 [RFC5226], is REQUIRED for such additions.
The following references are used throughout this MIB module:
[G.998.1] refers to:
ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding',
January 2005.
[G.998.2] refers to:
ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
bonding', January 2005.
[G.998.3] refers to:
ITU-T Recommendation G.998.3: 'Multi-pair bonding using
time-division inverse multiplexing', January 2005.
Naming Conventions:
BCE - Bonding Channel Entity
GBS - Generic Bonding Sublayer
These references should be updated as appropriate when a new
bonding scheme is added to this MIB module.
Copyright (C) The IETF Trust (2012).
The initial version of this MIB module was published in
RFC XXXX; for full legal notices see the RFC itself.
Supplementary information may be available at:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "201207160000Z" -- Jul 16, 2012
DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note
::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note.
-- Textual Conventions
IANAgBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines a bitmap of possible ITU-T
G.998 (G.Bond) bonding schemes. Currently the following values
are defined for the corresponding bonding schemes:
g9981(1) - G.998.1, (G.Bond/ATM, see G9981-MIB)
g9982(2) - G.998.2, (G.Bond/Ethernet, see G9982-MIB)
g9983(3) - G.998.3, (G.Bond/TDIM, see G9983-MIB)
An additional value of none(0), can be returned as a result
of GET operation, when an value of the object cannot be
determined (for example a peer GBS cannot be reached), the port
does not support any kind of bonding or when a single-BCE
G.998.2 GBS supports bonding (frame fragmentation/reassembly)
bypass."
SYNTAX BITS {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
IANAgBondScheme ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are:
none(0) - no bonding (e.g. on single-BCE G.998.2 GBS) or
unknown
g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernet)
g9983(3) - G.998.3 (G.Bond/TDIM)."
SYNTAX INTEGER {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
END
8. Security Considerations
There is a number of managed objects defined in this MIB module with There is a number of managed objects defined in this MIB module with
a MAX-ACCESS clause of read-write and/or read-create. Such objects a MAX-ACCESS clause of read-write and/or read-create. Such objects
may be considered sensitive or vulnerable in some network may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o Changing of gBondPortConfAdminScheme may lead to a potential o Changing of gBondPortConfAdminScheme may lead to a potential
skipping to change at page 64, line 19 skipping to change at page 66, line 26
[RFC5592] or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
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 9. IANA Considerations
Three new values of IANAifType: g9981(263), g9982(264) and g9983(265) Three new values of IANAifType: g9981(263), g9982(264) and g9983(265)
have been allocated by IANA [1] in the IANAifType-MIB module have been allocated by IANA [1] in the IANAifType-MIB module
[IANAifType-MIB]. [IANAifType-MIB].
An object identifier for gBondMIB MODULE-IDENTITY SHALL be allocated An object identifier for gBondMIB MODULE-IDENTITY SHALL be allocated
by IANA in the MIB-2 transmission sub-tree, before this document is by IANA in the MIB-2 transmission sub-tree, before this document is
published. published.
9. Acknowledgments This document defines the first version of the IANA-maintained IANA-
GBOND-MIB module. It is intended that each new G.998 bonding scheme
defined by the ITU-T Q4/SG15 working group and approved for
publication in a revision of ITU-T G.998.x is added to the IANA-
maintaned MIB module, provided that it is suitable for being managed
by the base objects in the GBOND-MIB module.
For each new bonding scheme added, a short description of the bonding
protocol and, wherever possible, a reference to a publicly available
specification SHOULD be specified. An Expert Review, as defined in
[RFC5226]., is REQUIRED, for each modification.
10. Acknowledgments
This document was produced by the [ADSLMIB] working group. This document was produced by the [ADSLMIB] working group.
Special thanks to Dan Romascanu for his meticulous review of this Special thanks to Dan Romascanu for his meticulous review of this
text. text.
10. References 11. References
10.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in [RFC2119] Bradner, S., "Key words for use in
RFCs to Indicate Requirement RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, Levels", BCP 14, RFC 2119,
March 1997. March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., [RFC2578] McCloghrie, K., Ed., Perkins, D.,
Ed., and J. Schoenwaelder, Ed., Ed., and J. Schoenwaelder, Ed.,
"Structure of Management "Structure of Management
Information Version 2 (SMIv2)", Information Version 2 (SMIv2)",
skipping to change at page 65, line 45 skipping to change at page 68, line 15
Intervals", RFC 3705, Intervals", RFC 3705,
February 2004. February 2004.
[RFC3826] Blumenthal, U., Maino, F., and K. [RFC3826] Blumenthal, U., Maino, F., and K.
McCloghrie, "The Advanced McCloghrie, "The Advanced
Encryption Standard (AES) Cipher Encryption Standard (AES) Cipher
Algorithm in the SNMP User-based Algorithm in the SNMP User-based
Security Model", RFC 3826, Security Model", RFC 3826,
June 2004. June 2004.
[RFC5226] Narten, T. and H. Alvestrand,
"Guidelines for Writing an IANA
Considerations Section in RFCs",
BCP 26, RFC 5226, May 2008.
[TR-159] Beili, E. and M. Morgenstern, [TR-159] Beili, E. and M. Morgenstern,
"Management Framework for xDSL "Management Framework for xDSL
Bonding", Broadband Forum Bonding", Broadband Forum
technical report TR-159, technical report TR-159,
December 2008. December 2008.
10.2. Informative References 11.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
Collision Detection (CSMA/CD) Collision Detection (CSMA/CD)
Access Method and Physical Layer Access Method and Physical Layer
skipping to change at page 67, line 22 skipping to change at page 69, line 45
rec/T-REC-G.998.3/en>. rec/T-REC-G.998.3/en>.
[I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded
Interfaces MIB", draft-ietf- Interfaces MIB", draft-ietf-
adslmib-gbond-atm-mib-06 (work in adslmib-gbond-atm-mib-06 (work in
progress), March 2012. progress), March 2012.
[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-06 (work in adslmib-gbond-eth-mib-07 (work in
progress), March 2012. progress), July 2012.
[I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded
Interfaces MIB", draft-ietf- Interfaces MIB", draft-ietf-
adslmib-gbond-tdim-mib-08 (work in adslmib-gbond-tdim-mib-08 (work in
progress), March 2012. progress), March 2012.
[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/
 End of changes. 51 change blocks. 
93 lines changed or deleted 223 lines changed or added

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