draft-ietf-adslmib-gbond-atm-mib-06.txt   rfc6768.txt 
Network Working Group E. Beili Internet Engineering Task Force (IETF) E. Beili
Internet-Draft Actelis Networks Request for Comments: 6768 Actelis Networks
Intended status: Standards Track March 12, 2012 Category: Standards Track February 2013
Expires: September 13, 2012 ISSN: 2070-1721
ATM-Based xDSL Bonded Interfaces MIB ATM-Based xDSL Bonded Interfaces MIB
draft-ietf-adslmib-gbond-atm-mib-06.txt
Abstract Abstract
This document defines Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in TCP/IP based networks. This use with network management protocols in TCP/IP-based internets.
document proposes an extension to the GBOND-MIB module with a set of This document proposes an extension to the GBOND-MIB module with a
objects for managing ATM-based multi-pair bonded xDSL interfaces, set of objects for managing ATM-based multi-pair bonded xDSL
defined in ITU-T recommendation G.998.1. interfaces, as defined in ITU-T Recommendation G.998.1.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on September 13, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6768.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework ......................3
3. The DSL Forum Management Framework for xDSL Bonding . . . . . 3 3. The Broadband Forum Management Framework for xDSL Bonding .......3
4. Relationship to other MIB modules . . . . . . . . . . . . . . 4 4. Relationship to Other MIB Modules ...............................3
4.1. Relationship to Interfaces Group MIB module . . . . . . . 4 4.1. Relationship to Interfaces Group MIB Module ................3
4.2. Relationship to G.Bond MIB module . . . . . . . . . . . . 4 4.2. Relationship to G.Bond MIB Module ..........................3
4.3. Relationship to ATM MIB module . . . . . . . . . . . . . . 4 4.3. Relationship to ATM MIB Module .............................4
5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 4 5. MIB Structure ...................................................4
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Overview ...................................................4
5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 5 5.2. Performance Monitoring .....................................4
5.3. Mapping of Broadband Forum TR-159 Managed Objects . . . . 5 5.3. Mapping of Broadband Forum TR-159 Managed Objects ..........5
6. G.Bond/ATM MIB Definitions . . . . . . . . . . . . . . . . . . 6 6. G.Bond/ATM MIB Definitions ......................................7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 30 7. Security Considerations ........................................31
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 8. IANA Considerations ............................................32
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 9. Acknowledgments ................................................32
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 10. References ....................................................32
10.1. Normative References . . . . . . . . . . . . . . . . . . . 31 10.1. Normative References .....................................32
10.2. Informative References . . . . . . . . . . . . . . . . . . 32 10.2. Informative References ...................................33
1. Introduction 1. Introduction
The ATM-Based Multi-Pair Bonding, a.k.a. G.Bond/ATM, is specified in ATM-Based Multi-Pair Bonding, a.k.a. G.Bond/ATM, is specified in
ITU-T G.998.1 recommendation [G.998.1], which defines a method for ITU-T Recommendation G.998.1 [G.998.1], which defines a method for
bonding (or aggregating) of multiple xDSL lines (or individual bearer bonding (or aggregating) multiple xDSL lines (or individual bearer
channels in multiple xDSL lines) into a single bi-directional logical channels in multiple xDSL lines) into a single bidirectional logical
link carrying an ATM stream. link carrying an ATM stream.
This specification can be viewed as an evolution of the legacy This specification can be viewed as an evolution of the legacy
Inverse Multiplexing over ATM (IMA) technology [af-phy-0086], applied Inverse Multiplexing for ATM (IMA) technology [AF-PHY-0086], applied
to xDSL with variable rates on each line/bearer channel. As with the to xDSL with variable rates on each line/bearer channel. As with the
other bonding schemes, ATM bonding also allows bonding of up to 32 other bonding schemes, ATM bonding also allows bonding of up to 32
individual sub-layers with variable rates, providing common individual sub-layers with variable rates, providing common
functionality for the configuration, initialization, operation and functionality for the configuration, initialization, operation, and
monitoring of the bonded link. monitoring of the bonded link.
The MIB module, defined in this document, defines a set of managed The MIB module defined in this document defines a set of managed
objects for the management of G.998.1 bonded interfaces, extending objects for the management of G.998.1 bonded interfaces, extending
the common objects specified in the GBOND-MIB the common objects specified in the GBOND-MIB module [RFC6765].
[I-D.ietf-adslmib-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
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in
2119 [RFC2119]. BCP 14, RFC 2119 [RFC2119].
3. The DSL Forum Management Framework for xDSL Bonding 3. The Broadband Forum Management Framework for xDSL Bonding
This document makes use of the DSL Forum technical report Management This document makes use of the Broadband Forum technical report
Framework for xDSL Bonding [TR-159], defining a management model and "Management Framework for xDSL Bonding" [TR-159], defining a
a hierarchy of management objects for the bonded xDSL interfaces. management model and a hierarchy of management objects for the bonded
xDSL interfaces.
4. Relationship to other MIB modules 4. Relationship to Other MIB Modules
This section outlines the relationship of the MIB modules defined in This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs. this document with other MIB modules described in the relevant RFCs.
Specifically, the following MIB modules are discussed: Interfaces Specifically, the following MIB modules are discussed: the Interfaces
Group MIB (IF-MIB) and G.Bond MIB (GBOND-MIB). Group MIB (IF-MIB) and the G.Bond MIB (GBOND-MIB).
4.1. Relationship to Interfaces Group MIB module 4.1. Relationship to Interfaces Group MIB Module
A G.Bond/ATM port is a private case of a Bonded multi-pair xDSL A G.Bond/ATM port is a private case of a bonded multi-pair xDSL
interface and as such is managed using generic interface management interface and as such is managed using generic interface management
objects defined in the IF-MIB [RFC2863]. In particular an interface objects defined in the IF-MIB [RFC2863]. In particular, an interface
index (ifIndex) is used to index instances of G.Bond/ATM ports, as index (ifIndex) is used to index instances of G.Bond/ATM ports, as
well as xDSL lines/channels, in a managed system. well as xDSL lines/channels, in a managed system.
4.2. Relationship to G.Bond MIB module 4.2. Relationship to G.Bond MIB Module
GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management The GBOND-MIB module [RFC6765] defines management objects common for
objects common for all Bonded multi-pair xDSL interfaces. In all bonded multi-pair xDSL interfaces. In particular, it describes
particular it describes the bonding management, bonded port and the bonding management, bonded port and channel configuration,
channel configuration, initialization sequence etc. initialization sequence, etc.
Both GBOND-MIB and G9981-MIB modules are REQUIRED to manage a G.Bond/ Both the GBOND-MIB and G9981-MIB modules are REQUIRED to manage a
ATM port. G.Bond/ATM port.
4.3. Relationship to ATM MIB module 4.3. Relationship to ATM MIB Module
ATM-MIB [RFC2515] module defines management objects for an ATM The ATM-MIB [RFC2515] module defines management objects for an ATM
interface. interface.
ATM-MIB module can be used to manage the ATM aspects of a G.Bond/ATM The ATM-MIB module can be used to manage the ATM aspects of a G.Bond/
port. ATM port.
5. MIB Structure 5. MIB Structure
5.1. Overview 5.1. Overview
All management objects defined in the G9981-MIB module are contained All management objects defined in the G9981-MIB module are contained
in a single group g9981Port. This group is further split into 4 sub- in a single group g9981Port. This group is further split into 4
groups, structured as recommended by RFC 4181 [RFC4181]: sub-groups, structured as recommended by RFC 4181 [RFC4181]:
o g9981PortNotifications - containing notifications (Up/Downstream o g9981PortNotifications - containing notifications (Up/Downstream
Differential Delay Tolerance Exceeded). Differential Delay Tolerance Exceeded).
o g9981PortConfTable - containing objects for configuration of a o g9981PortConfTable - containing objects for configuration of a
G.Bond/ATM port. G.Bond/ATM port.
o g9981PortStatusTable - containing objects providing overall status o g9981PortStatusTable - containing objects providing overall status
information of a G.Bond/ATM port, complementing the generic status information of a G.Bond/ATM port, complementing the generic status
information from the ifTable of IF-MIB and gBondFltStatus of information from the ifTable of the IF-MIB and the gBondFltStatus
GBOND-MIB. of the GBOND-MIB.
o g9981PM - containing objects providing historical performance o g9981PM - containing objects providing historical Performance
monitoring (PM) information of a G.Bond/ATM port, complementing Monitoring (PM) information of a G.Bond/ATM port, complementing
the PM information from the gBondPortPM of GBOND-MIB. the PM information from the gBondPortPM of the GBOND-MIB.
Note that the rest of the objects for the Generic Bonded Sub-layer Note that the rest of the objects for the Generic Bonding Sub-layer
(GBS) port configuration, capabilities, status, notifications and (GBS) port configuration, capabilities, status, notifications, and
performance monitoring is located in the GBOND-MIB module. Performance Monitoring are located in the GBOND-MIB module.
5.2. Performance Monitoring 5.2. Performance Monitoring
The OPTIONAL performance monitoring counters, thresholds and history The OPTIONAL Performance Monitoring counters, thresholds, and history
buckets (interval-counters) are implemented using the textual buckets (interval-counters) are implemented using the textual
conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. The HC- conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. The
PerfHist-TC-MIB defines 64-bit versions of the textual conventions HC-PerfHist-TC-MIB defines 64-bit versions of the textual conventions
found in PerfHist-TC-MIB [RFC3593]. found in the PerfHist-TC-MIB [RFC3593].
The agent SHOULD align the beginning of each interval to a fifteen The agent SHOULD align the beginning of each interval to a fifteen-
minute boundary of a wall clock. Likewise, the beginning of each one minute boundary of a wall clock. Likewise, the beginning of each
day intervals SHOULD be aligned with the start of a day. one-day interval SHOULD be aligned with the start of a day.
Counters are not reset when a GBS is reinitialized, but rather only Counters are not reset when a GBS is re-initialized, but rather only
when the agent is reset or reinitialized. when the agent is reset or re-initialized.
Note that the accumulation of certain performance events for a Note that the accumulation of certain performance events for a
monitored entity is inhibited (counting stops) during periods of monitored entity is inhibited (counting stops) during periods of
service unavailability on that entity. The DESCRIPTION clause of service unavailability on that entity. The DESCRIPTION clause of
performance monitoring counters in this MIB module specifies which of Performance Monitoring counters in this MIB module specifies which of
the counters are inhibited during periods of service unavailability. the counters are inhibited during periods of service unavailability.
5.3. Mapping of Broadband Forum TR-159 Managed Objects 5.3. Mapping of Broadband Forum TR-159 Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [TR-159] and the managed objects defined in (attributes) defined in [TR-159] and the managed objects defined in
this document. this document.
+-----------------------------+-------------------------------------+ +-----------------------------+-------------------------------------+
| TR-159 Managed Object | Corresponding SNMP Object | | TR-159 Managed Object | Corresponding SNMP Object |
skipping to change at page 6, line 35 skipping to change at page 6, line 5
+-----------------------------+-------------------------------------+ +-----------------------------+-------------------------------------+
| nIMAUpDiffDelayToleranceExc | g9981UpDiffDelayToleranceExceeded | | nIMAUpDiffDelayToleranceExc | g9981UpDiffDelayToleranceExceeded |
| eeded | | | eeded | |
+-----------------------------+-------------------------------------+ +-----------------------------+-------------------------------------+
| nIMADownDiffDelayToleranceE | g9981DnDiffDelayToleranceExceeded | | nIMADownDiffDelayToleranceE | g9981DnDiffDelayToleranceExceeded |
| xceeded | | | xceeded | |
+-----------------------------+-------------------------------------+ +-----------------------------+-------------------------------------+
Table 1: Mapping of TR-159 Managed Objects Table 1: Mapping of TR-159 Managed Objects
Note that some of the mapping between the objects defined in TR-159
and the ones defined in this MIB module is not one-to-one; for
example, while TR-159 PM attributes aGroupPerf* map to the
corresponding gBondPortPm* objects of the GBOND-MIB module, there are
no dedicated PM attributes for the g9981PortPm* objects introduced in
this MIB module. However, since their definition is identical to the
definition of gBondPortPm* objects of the GBOND-MIB module, we can
map g9981PortPm* to the relevant aGroupPerf* attributes of TR-159 and
use the term 'partial mapping' to denote the fact that this mapping
is not one-to-one.
6. G.Bond/ATM MIB Definitions 6. G.Bond/ATM MIB Definitions
The G9981-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], and
HC-PerfHist-TC-MIB [RFC3705]. The module has been structured as
recommended by [RFC4181].
G9981-MIB DEFINITIONS ::= BEGIN G9981-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
mib-2, mib-2,
Unsigned32, Unsigned32,
Counter32 Counter32
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
TruthValue TruthValue
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580
ifIndex ifIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- RFC 2863
HCPerfCurrentCount, HCPerfCurrentCount,
HCPerfIntervalCount, HCPerfIntervalCount,
HCPerfValidIntervals, HCPerfValidIntervals,
HCPerfInvalidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed HCPerfTimeElapsed
FROM HC-PerfHist-TC-MIB -- [RFC3705] FROM HC-PerfHist-TC-MIB -- RFC 3705
; ;
------------------------------------------------------------------------ ------------------------------------------------------------------------
g9981MIB MODULE-IDENTITY g9981MIB MODULE-IDENTITY
LAST-UPDATED "201203120000Z" -- Mar 12, 2012 LAST-UPDATED "201302200000Z" -- 20 February 2013
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://datatracker.ietf.org/wg/adslmib/charter/
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 4951169 Petach-Tikva 4951169
Israel Israel
Phone: +972-3-926-8421 Phone: +972-3-926-8421
EMail: menachem.dodge@ecitele.com EMail: menachemdodge1@gmail.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks, Inc. Postal: Actelis Networks, Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 49103 Petach-Tikva 49103
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
EMail: edward.beili@actelis.com" EMail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage the "The objects in this MIB module are used to manage the
multi-pair bonded xDSL Interfaces using ATM inverse multi-pair bonded xDSL interfaces using ATM inverse
multiplexing, defined in ITU-T recommendation G.998.1 multiplexing, as defined in ITU-T Recommendation G.998.1
(G.Bond/ATM). (G.Bond/ATM).
This MIB module MUST be used in conjunction with GBOND-MIB This MIB module MUST be used in conjunction with the GBOND-MIB
module, common to all G.Bond technologies. module, common to all G.Bond technologies.
The following references are used throughout this MIB module: The following references are used throughout this MIB module:
[G.998.1] refers to: [G.998.1] refers to:
ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding',
January 2005. January 2005.
[TR-159] refers to: [TR-159] refers to:
Broadband Forum Technical Report: 'Management Framework for Broadband Forum Technical Report: 'Management Framework for
xDSL Bonding', December 2008. xDSL Bonding', December 2008.
Naming Conventions: Naming Conventions:
ATM - Asynchronous Transfer Mode ATM - Asynchronous Transfer Mode
BCE - Bonding Channel Entity BCE - Bonding Channel Entity
BTU - Bonding Terminating Unit BTU - Bonding Terminating Unit
CO - Central Office CO - Central Office
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer GBS - Generic Bonding Sub-layer
GBS-C - Generic Bonded Sub-layer, CO side GBS-C - Generic Bonding Sub-layer, CO side
GBS-R - Generic Bonded Sub-layer, RT (or CPE) side GBS-R - Generic Bonding Sub-layer, RT (or CPE) side
PM - Performance Monitoring PM - Performance Monitoring
RT - Remote Terminal RT - Remote Terminal
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
SES - Severely Errored Seconds SES - Severely Errored Seconds
US - Unavailable Seconds UAS - Unavailable Seconds
Copyright (C) The IETF Trust (2012).
This version of this MIB module is part of RFC YYYY;
see the RFC itself for full legal notices."
REVISION "201203120000Z" -- Mar 12, 2012 Copyright (c) 2013 IETF Trust and the persons identified as
DESCRIPTION "Initial version, published as RFC YYYY." authors of the code. All rights reserved.
-- EdNote: Replace YYYY with the actual RFC number & Redistribution and use in source and binary forms, with or without
-- remove this note modification, is permitted pursuant to, and subject to the license
terms contained in, the Simplified BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
::= { mib-2 ZZZ } REVISION "201302200000Z" -- 20 February 2013
DESCRIPTION "Initial version, published as RFC 6768."
-- EdNote: Replace ZZZ with a real OID once it is ::= { mib-2 208 }
-- allocated & remove this note.
-- Sections of the module -- Sections of the module
-- Structured as recommended by [RFC4181], Appendix D -- Structured as recommended by RFC 4181, Appendix D
g9981Objects OBJECT IDENTIFIER ::= { g9981MIB 1 } g9981Objects OBJECT IDENTIFIER ::= { g9981MIB 1 }
g9981Conformance OBJECT IDENTIFIER ::= { g9981MIB 2 } g9981Conformance OBJECT IDENTIFIER ::= { g9981MIB 2 }
-- Groups in the module -- Groups in the module
g9981Port OBJECT IDENTIFIER ::= { g9981Objects 1 } g9981Port OBJECT IDENTIFIER ::= { g9981Objects 1 }
-- Textual Conventions -- Textual Conventions
MilliSeconds ::= TEXTUAL-CONVENTION MilliSeconds ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents time unit value in milliseconds." "Represents time unit value in milliseconds."
SYNTAX Unsigned32 SYNTAX Unsigned32
-- Port Notifications Group -- Port Notifications group
g9981PortNotifications OBJECT IDENTIFIER g9981PortNotifications OBJECT IDENTIFIER
::= { g9981Port 0 } ::= { g9981Port 0 }
g9981UpDiffDelayToleranceExceeded NOTIFICATION-TYPE g9981UpDiffDelayToleranceExceeded 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
g9981PortConfUpDiffDelayTolerance, g9981PortConfUpDiffDelayTolerance,
g9981PortStatMaxUpDiffDelay g9981PortStatMaxUpDiffDelay
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the maximum upstream "This notification indicates that the maximum upstream
differential delay has exceeded the max upstream differential differential delay has exceeded the max upstream differential
delay threshold, specified by delay threshold, specified by
g9981PortConfUpDiffDelayTolerance. g9981PortConfUpDiffDelayTolerance.
This notification MAY be sent for the GBS-C ports while the This notification MAY be sent for the GBS-C ports while the
port is up, on the crossing event in both directions: from port is 'up', on the crossing event in both directions: from
normal (diff. delay is above the threshold) to low (diff. normal (diff. delay is above the threshold) to low (diff.
delay equals the threshold or below it) and from low to delay equals the threshold or is below it) and from low to
normal. This notification is not applicable to the GBS-R normal. This notification is not applicable to the GBS-R
ports. ports.
Generation of this notification is controlled by the Generation of this notification is controlled by the
g9981PortConfDiffDelayToleranceExceededEnable attribute. g9981PortConfDiffDelayToleranceExceededEnable attribute.
This object maps to the TR-159 notification This object maps to the TR-159 notification
nIMAUpDiffDelayToleranceExceeded." nIMAUpDiffDelayToleranceExceeded."
REFERENCE REFERENCE
"[TR-159] 5.5.2.8" "[TR-159], Section 5.5.2.8"
::= { g9981PortNotifications 1 } ::= { g9981PortNotifications 1 }
g9981DnDiffDelayToleranceExceeded NOTIFICATION-TYPE g9981DnDiffDelayToleranceExceeded 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
g9981PortConfDnDiffDelayTolerance, g9981PortConfDnDiffDelayTolerance,
g9981PortStatMaxDnDiffDelay g9981PortStatMaxDnDiffDelay
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the maximum downstream "This notification indicates that the maximum downstream
differential delay has exceeded the max downstream differential delay has exceeded the max downstream
differential delay threshold, specified by differential delay threshold, specified by
g9981PortConfDnDiffDelayTolerance. g9981PortConfDnDiffDelayTolerance.
This notification MAY be sent for the GBS-C ports while the This notification MAY be sent for the GBS-C ports while the
port is up, on the crossing event in both directions: from port is 'up', on the crossing event in both directions: from
normal (diff. delay is above the threshold) to low (diff. normal (diff. delay is above the threshold) to low (diff.
delay equals the threshold or below it) and from low to delay equals the threshold or is below it) and from low to
normal. This notification is not applicable to the GBS-R normal. This notification is not applicable to the GBS-R
ports. ports.
Generation of this notification is controlled by the Generation of this notification is controlled by the
g9981PortConfDiffDelayToleranceExceededEnable attribute. g9981PortConfDiffDelayToleranceExceededEnable attribute.
This object maps to the TR-159 notification This object maps to the TR-159 notification
nIMADownDiffDelayToleranceExceeded." nIMADownDiffDelayToleranceExceeded."
REFERENCE REFERENCE
"[TR-159] 5.5.2.9" "[TR-159], Section 5.5.2.9"
::= { g9981PortNotifications 2 } ::= { g9981PortNotifications 2 }
-- G.Bond/ATM Port group -- G.Bond/ATM Port group
g9981PortConfTable OBJECT-TYPE g9981PortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF G9981PortConfEntry SYNTAX SEQUENCE OF G9981PortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of G.Bond/ATM ports. Entries in "Table for configuration of G.Bond/ATM ports. Entries in
this table MUST be maintained in a persistent manner" this table MUST be maintained in a persistent manner."
::= { g9981Port 1 } ::= { g9981Port 1 }
g9981PortConfEntry OBJECT-TYPE g9981PortConfEntry OBJECT-TYPE
SYNTAX G9981PortConfEntry SYNTAX G9981PortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond/ATM Port Configuration table. "An entry in the G.Bond/ATM Port Configuration table.
Each entry represents a G.Bond/ATM port indexed by the Each entry represents a G.Bond/ATM port indexed by the
ifIndex. Additional configuration parameters are available ifIndex. Additional configuration parameters are available
via the gBondPortConfEntry of GBOND-MIB. via the gBondPortConfEntry of the GBOND-MIB.
Note that a G.Bond/ATM port runs on top of a single or Note that a G.Bond/ATM port runs on top of a single or
multiple BCE port(s), which are also indexed by ifIndex." multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { g9981PortConfTable 1 } ::= { g9981PortConfTable 1 }
G9981PortConfEntry ::= G9981PortConfEntry ::=
SEQUENCE { SEQUENCE {
g9981PortConfUpDiffDelayTolerance MilliSeconds, g9981PortConfUpDiffDelayTolerance MilliSeconds,
g9981PortConfDnDiffDelayTolerance MilliSeconds, g9981PortConfDnDiffDelayTolerance MilliSeconds,
g9981PortConfDiffDelayToleranceExceededEnable TruthValue g9981PortConfDiffDelayToleranceExceededEnable TruthValue
} }
g9981PortConfUpDiffDelayTolerance OBJECT-TYPE g9981PortConfUpDiffDelayTolerance OBJECT-TYPE
SYNTAX MilliSeconds(0..2047) SYNTAX MilliSeconds (0..2047)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A maximum tolerated upstream differential delay (among "A maximum tolerated upstream differential delay (among
the member BCEs) of a G.Bond/ATM port, expressed in ms. the member BCEs) of a G.Bond/ATM port, expressed in ms.
This object is read-write for the GBS-C ports. This object is read-write for the GBS-C ports.
It is irrelevant for the GBS-R ports - an attempt to read or It is irrelevant for the GBS-R ports -- an attempt to read or
change this object MUST be rejected (in case of SNMP with the change this object MUST be rejected (in the case of SNMP, with
error inconsistentValue). the error inconsistentValue).
This object maps to TR-159 attribute This object maps to the TR-159 attribute
aIMAUpDiffDelayTolerance" aIMAUpDiffDelayTolerance."
REFERENCE REFERENCE
"[TR-159] 5.5.2.5; [G.998.1] 11.4.1 (6)" "[TR-159], Section 5.5.2.5; [G.998.1], Section 11.4.1 (6)"
::= { g9981PortConfEntry 1 } ::= { g9981PortConfEntry 1 }
g9981PortConfDnDiffDelayTolerance OBJECT-TYPE g9981PortConfDnDiffDelayTolerance OBJECT-TYPE
SYNTAX MilliSeconds(0..2047) SYNTAX MilliSeconds (0..2047)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A maximum tolerated downstream differential delay (among "A maximum tolerated downstream differential delay (among
the member BCEs) of a G.Bond/ATM port, expressed in ms. the member BCEs) of a G.Bond/ATM port, expressed in ms.
This object is read-write for the GBS-C ports. This object is read-write for the GBS-C ports.
It is irrelevant for the GBS-R ports - an attempt to read or It is irrelevant for the GBS-R ports -- an attempt to read or
change this object MUST be rejected (in case of SNMP with the change this object MUST be rejected (in the case of SNMP, with
error inconsistentValue). the error inconsistentValue).
This object maps to TR-159 attribute This object maps to the TR-159 attribute
aIMADownDiffDelayTolerance" aIMADownDiffDelayTolerance."
REFERENCE REFERENCE
"[TR-159] 5.5.2.6; [G.998.1] 11.4.1 (6)" "[TR-159], Section 5.5.2.6; [G.998.1], Section 11.4.1 (6)"
::= { g9981PortConfEntry 2 } ::= { g9981PortConfEntry 2 }
g9981PortConfDiffDelayToleranceExceededEnable OBJECT-TYPE g9981PortConfDiffDelayToleranceExceededEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether g9981UpDiffDelayToleranceExceeded and "Indicates whether g9981UpDiffDelayToleranceExceeded and
g9981DnDiffDelayToleranceExceeded notifications should g9981DnDiffDelayToleranceExceeded notifications should
be generated for G.Bond/ATM port. be generated for G.Bond/ATM port.
Value of true(1) indicates that the notifications are enabled. A value of true(1) indicates that the notifications are enabled.
Value of false(2) indicates that the notifications are A value of false(2) indicates that the notifications are
disabled. disabled.
This object is read-write for the GBS-C. This object is read-write for the GBS-C.
It is irrelevant for the GBS-R ports - an attempt to read or It is irrelevant for the GBS-R ports -- an attempt to read or
change this object MUST be rejected (in case of SNMP with the change this object MUST be rejected (in the case of SNMP, with
error inconsistentValue). the error inconsistentValue).
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aIMADiffDelayToleranceExceededEnable." aIMADiffDelayToleranceExceededEnable."
REFERENCE REFERENCE
"[TR-159] 5.5.5.7" "[TR-159], Section 5.5.5.7"
::= { g9981PortConfEntry 3 } ::= { g9981PortConfEntry 3 }
g9981PortStatTable OBJECT-TYPE g9981PortStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF G9981PortStatEntry SYNTAX SEQUENCE OF G9981PortStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides overall status information of G.Bond/ATM "This table provides overall status information of G.Bond/ATM
ports, complementing the generic status information from the ports, complementing the generic status information from the
ifTable of IF-MIB and gBondFltStatus of GBOND-MIB. ifTable of the IF-MIB and the gBondFltStatus of the GBOND-MIB.
Additional status information about connected BCEs is available Additional status information about connected BCEs is available
from the relevant line MIBs. from the relevant line MIBs.
This table contains live data from the equipment. As such, it is This table contains live data from the equipment. As such, it
NOT persistent." is NOT persistent."
::= { g9981Port 2 } ::= { g9981Port 2 }
g9981PortStatEntry OBJECT-TYPE g9981PortStatEntry OBJECT-TYPE
SYNTAX G9981PortStatEntry SYNTAX G9981PortStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond/ATM port Status table. "An entry in the G.Bond/ATM Port Status table.
Each entry represents a G.Bond/ATM port indexed by the Each entry represents a G.Bond/ATM port indexed by the
ifIndex. ifIndex.
Note that a GBS port runs on top of a single or multiple BCE Note that a GBS port runs on top of a single or multiple BCE
port(s), which are also indexed by ifIndex." port(s), which are also indexed by the ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { g9981PortStatTable 1 } ::= { g9981PortStatTable 1 }
G9981PortStatEntry ::= G9981PortStatEntry ::=
SEQUENCE { SEQUENCE {
g9981PortStatRxLostCells Counter32, g9981PortStatRxLostCells Counter32,
g9981PortStatTxLostCells Counter32, g9981PortStatTxLostCells Counter32,
g9981PortStatMaxUpDiffDelay Unsigned32, g9981PortStatMaxUpDiffDelay Unsigned32,
g9981PortStatMaxDnDiffDelay Unsigned32 g9981PortStatMaxDnDiffDelay Unsigned32
} }
g9981PortStatRxLostCells OBJECT-TYPE g9981PortStatRxLostCells OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of lost ATM cells detected by the G.Bond/ATM port "The number of lost ATM cells detected by the G.Bond/ATM port
in the receive direction, i.e. upstream direction for in the receive direction (e.g., upstream direction for
a GBS-C port. a GBS-C port).
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime as
defined in IF-MIB. defined in the IF-MIB.
This object maps to TR-159 attribute aIMARxLostCells." This object maps to the TR-159 attribute aIMARxLostCells."
REFERENCE REFERENCE
"[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" "[TR-159], Section 5.5.2.1; [G.998.1], Section 11.4.2 (4)"
::= { g9981PortStatEntry 1 } ::= { g9981PortStatEntry 1 }
g9981PortStatTxLostCells OBJECT-TYPE g9981PortStatTxLostCells OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of lost ATM cells detected by the peer G.Bond/ATM "The number of lost ATM cells detected by the peer G.Bond/ATM
port in the receive direction, e.g. downstream direction for a port in the receive direction, i.e., downstream direction for a
GBS-C port. GBS-C port.
This object is irrelevant for the GBS-R ports - an attempt to This object is irrelevant for the GBS-R ports -- an attempt to
read it MUST be rejected (in case of SNMP with the error read it MUST be rejected (in the case of SNMP, with the error
inconsistentValue). inconsistentValue).
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime as
defined in IF-MIB. defined in the IF-MIB.
This object maps to TR-159 attribute aIMAPeerRxLostCells." This object maps to the TR-159 attribute aIMAPeerRxLostCells."
REFERENCE REFERENCE
"[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" "[TR-159], Section 5.5.2.2; [G.998.1], Section 11.4.2 (4)"
::= { g9981PortStatEntry 2 } ::= { g9981PortStatEntry 2 }
g9981PortStatMaxUpDiffDelay OBJECT-TYPE g9981PortStatMaxUpDiffDelay OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current maximum upstream differential delay between all "Current maximum upstream differential delay between all
operational BCEs in the G.Bond/ATM bonding group, measured in operational BCEs in the G.Bond/ATM bonding group, measured in
units of 0.1 ms. units of 0.1 ms.
This object is read-only for the GBS-C ports. This object is read-only for the GBS-C ports.
It is irrelevant for the GBS-R ports - an attempt to read this It is irrelevant for the GBS-R ports -- an attempt to read this
object MUST be rejected (in case of SNMP with the error object MUST be rejected (in the case of SNMP, with the error
inconsistentValue). inconsistentValue).
This object maps to TR-159 attribute aIMAMaxUpDiffDelay." This object maps to the TR-159 attribute aIMAMaxUpDiffDelay."
REFERENCE REFERENCE
"[TR-159] 5.5.2.3" "[TR-159], Section 5.5.2.3"
::= { g9981PortStatEntry 3 } ::= { g9981PortStatEntry 3 }
g9981PortStatMaxDnDiffDelay OBJECT-TYPE g9981PortStatMaxDnDiffDelay OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current maximum downstream differential delay between all "Current maximum downstream differential delay between all
operational BCEs in the G.Bond/ATM bonding group, measured in operational BCEs in the G.Bond/ATM bonding group, measured in
units of 0.1 ms. units of 0.1 ms.
This object is read-only for the GBS-C ports. This object is read-only for the GBS-C ports.
It is irrelevant for the GBS-R ports - an attempt to read this It is irrelevant for the GBS-R ports -- an attempt to read this
object MUST be rejected (in case of SNMP with the error object MUST be rejected (in the case of SNMP, with the error
inconsistentValue). inconsistentValue).
This object maps to TR-159 attribute aIMAMaxDownDiffDelay." This object maps to the TR-159 attribute aIMAMaxDownDiffDelay."
REFERENCE REFERENCE
"[TR-159] 5.5.2.4" "[TR-159], Section 5.5.2.4"
::= { g9981PortStatEntry 4 } ::= { g9981PortStatEntry 4 }
------------------------------- -------------------------------
-- Performance Monitoring group -- Performance Monitoring group
------------------------------- -------------------------------
g9981PM OBJECT IDENTIFIER ::= { g9981Port 3 } g9981PM OBJECT IDENTIFIER ::= { g9981Port 3 }
g9981PortPmCurTable OBJECT-TYPE g9981PortPmCurTable OBJECT-TYPE
SYNTAX SEQUENCE OF G9981PortPmCurEntry SYNTAX SEQUENCE OF G9981PortPmCurEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains current Performance Monitoring information "This table contains current Performance Monitoring information
for a G.Bond/ATM port. This table contains live data from the for a G.Bond/ATM port. This table contains live data from the
equipment and as such is NOT persistent." equipment and as such is NOT persistent."
::= { g9981PM 1 } ::= { g9981PM 1 }
g9981PortPmCurEntry OBJECT-TYPE g9981PortPmCurEntry OBJECT-TYPE
SYNTAX G9981PortPmCurEntry SYNTAX G9981PortPmCurEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond/ATM Port PM table. "An entry in the G.Bond/ATM Port PM table.
Each entry represents a G.Bond/ATM port indexed by the Each entry represents a G.Bond/ATM port indexed by the
skipping to change at page 16, line 9 skipping to change at page 16, line 45
g9981PortPmCur1DayUpDiffDelay HCPerfCurrentCount, g9981PortPmCur1DayUpDiffDelay HCPerfCurrentCount,
g9981PortPmCur1DayDnDiffDelay HCPerfCurrentCount g9981PortPmCur1DayDnDiffDelay HCPerfCurrentCount
} }
g9981PortPmCur15MinValidIntervals OBJECT-TYPE g9981PortPmCur15MinValidIntervals OBJECT-TYPE
SYNTAX HCPerfValidIntervals SYNTAX HCPerfValidIntervals
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only number of 15-minute intervals for which the "A read-only number of 15-minute intervals for which the
performance data was collected. The value of this object will performance data was collected. The value of this object will
be 96 or the maximum number of 15-minute history intervals be 96 or the maximum number of 15-minute history intervals
collected by the implementation unless the measurement was collected by the implementation, unless the measurement was
(re-)started recently, in which case the value will be the (re)started recently, in which case the value will be the
number of complete 15 minutes intervals for which there are at number of complete 15-minute intervals for which there are at
least some data. least some data.
In certain cases it is possible that some intervals are
unavailable. In this case, this object reports the maximum In certain cases, it is possible that some intervals are
unavailable. In this case, this object reports the maximum
interval number for which data is available. interval number for which data is available.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf15MinValidIntervals." aGroupPerf15MinValidIntervals."
REFERENCE REFERENCE
"[TR-159] 5.5.1.32" "[TR-159], Section 5.5.1.32"
::= { g9981PortPmCurEntry 1 } ::= { g9981PortPmCurEntry 1 }
g9981PortPmCur15MinInvalidIntervals OBJECT-TYPE g9981PortPmCur15MinInvalidIntervals OBJECT-TYPE
SYNTAX HCPerfInvalidIntervals SYNTAX HCPerfInvalidIntervals
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only number of 15-minute intervals for which the "A read-only number of 15-minute intervals for which the
performance data was not always available. The value will performance data was not always available. The value will
typically be zero except in cases where the data for some typically be zero, except in cases where the data for some
intervals are not available. intervals are not available.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf15MinInvalidIntervals." aGroupPerf15MinInvalidIntervals."
REFERENCE REFERENCE
"[TR-159] 5.5.1.33" "[TR-159], Section 5.5.1.33"
::= { g9981PortPmCurEntry 2 } ::= { g9981PortPmCurEntry 2 }
g9981PortPmCur15MinTimeElapsed OBJECT-TYPE g9981PortPmCur15MinTimeElapsed OBJECT-TYPE
SYNTAX HCPerfTimeElapsed SYNTAX HCPerfTimeElapsed
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of seconds that have elapsed since the "A read-only count of seconds that have elapsed since the
beginning of the current 15-minute performance interval. beginning of the current 15-minute performance interval.
skipping to change at page 17, line 4 skipping to change at page 17, line 42
SYNTAX HCPerfTimeElapsed SYNTAX HCPerfTimeElapsed
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of seconds that have elapsed since the "A read-only count of seconds that have elapsed since the
beginning of the current 15-minute performance interval. beginning of the current 15-minute performance interval.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerfCurr15MinTimeElapsed." aGroupPerfCurr15MinTimeElapsed."
REFERENCE REFERENCE
"[TR-159] 5.5.1.34" "[TR-159], Section 5.5.1.34"
::= { g9981PortPmCurEntry 3 } ::= { g9981PortPmCurEntry 3 }
g9981PortPmCur15MinRxLostCells OBJECT-TYPE g9981PortPmCur15MinRxLostCells OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of lost ATM cells detected by a G.Bond/ATM "A read-only count of lost ATM cells detected by a G.Bond/ATM
port (e.g. GBS-C) in the receive direction, during the current port (e.g., the GBS-C) in the receive direction, during the
15-minute performance history interval. current 15-minute performance history interval.
Note that the total number of lost ATM cells is indicated by the Note that the total number of lost ATM cells is indicated by the
g9981PortStatRxLostCells object. g9981PortStatRxLostCells object.
This object is inhibited during Severely Errored Seconds (SES) This object is inhibited during Severely Errored Seconds (SES)
or Unavailable Seconds (UAS)." or Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.1" "[TR-159], Section 5.5.2.1"
::= { g9981PortPmCurEntry 4} ::= { g9981PortPmCurEntry 4}
g9981PortPmCur15MinTxLostCells OBJECT-TYPE g9981PortPmCur15MinTxLostCells OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of lost ATM cells detected by the peer "A read-only count of lost ATM cells detected by the peer
G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the
15-minute performance history interval. current 15-minute performance history interval.
Note that the total number of lost ATM cells is indicated by the Note that the total number of lost ATM cells is indicated by the
g9981PortStatTxLostCells object. g9981PortStatTxLostCells object.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.2" "[TR-159], Section 5.5.2.2"
::= { g9981PortPmCurEntry 5} ::= { g9981PortPmCurEntry 5}
g9981PortPmCur15MinUpDiffDelay OBJECT-TYPE g9981PortPmCur15MinUpDiffDelay OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum upstream differential "A read-only value specifying the maximum upstream differential
delay between all operational BCEs in the GBS-C, measured in delay between all operational BCEs in the GBS-C, measured in
units of 0.1 ms, during the current 15-minute performance units of 0.1 ms, during the current 15-minute performance
interval. interval.
Note that the current max upstream differential delay is Note that the current max upstream differential delay is
indicated by the g9981PortStatMaxUpDiffDelay object. indicated by the g9981PortStatMaxUpDiffDelay object.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.3" "[TR-159], Section 5.5.2.3"
::= { g9981PortPmCurEntry 6} ::= { g9981PortPmCurEntry 6}
g9981PortPmCur15MinDnDiffDelay OBJECT-TYPE g9981PortPmCur15MinDnDiffDelay OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum downstream differential "A read-only value specifying the maximum downstream
delay between all operational BCEs in the GBS-C (as perceived differential delay between all operational BCEs in the GBS-C
by GBS-R), measured in units of 0.1 ms, during the current (as perceived by the GBS-R), measured in units of 0.1 ms,
15-minute performance history interval. during the current 15-minute performance history interval.
Note that the current max downstream differential delay is Note that the current max downstream differential delay is
indicated by the g9981PortStatMaxDnDiffDelay object. indicated by the g9981PortStatMaxDnDiffDelay object.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.4" "[TR-159], Section 5.5.2.4"
::= { g9981PortPmCurEntry 7} ::= { g9981PortPmCurEntry 7}
g9981PortPmCur1DayValidIntervals OBJECT-TYPE g9981PortPmCur1DayValidIntervals OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
UNITS "days" UNITS "days"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only number of 1-day intervals for which data was "A read-only number of 1-day intervals for which data was
collected. The value of this object will be 7 or the maximum collected. The value of this object will be 7 or the maximum
number of 1-day history intervals collected by the number of 1-day history intervals collected by the
implementation unless the measurement was (re-)started recently, implementation, unless the measurement was (re)started recently,
in which case the value will be the number of complete 1-day in which case the value will be the number of complete 1-day
intervals for which there are at least some data. intervals for which there are at least some data.
In certain cases it is possible that some intervals are In certain cases, it is possible that some intervals are
unavailable. In this case, this object reports the maximum unavailable. In this case, this object reports the maximum
interval number for which data is available." interval number for which data is available."
REFERENCE REFERENCE
"[TR-159] 5.5.1.45" "[TR-159], Section 5.5.1.45"
::= { g9981PortPmCurEntry 8 } ::= { g9981PortPmCurEntry 8 }
g9981PortPmCur1DayInvalidIntervals OBJECT-TYPE g9981PortPmCur1DayInvalidIntervals OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
UNITS "days" UNITS "days"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only number of 1-day intervals for which data was "A read-only number of 1-day intervals for which data was
not always available. The value will typically be zero except in not always available. The value will typically be zero, except
cases where the data for some intervals are not available." in cases where the data for some intervals are not available."
REFERENCE REFERENCE
"[TR-159] 5.5.1.46" "[TR-159], Section 5.5.1.46"
::= { g9981PortPmCurEntry 9 } ::= { g9981PortPmCurEntry 9 }
g9981PortPmCur1DayTimeElapsed OBJECT-TYPE g9981PortPmCur1DayTimeElapsed OBJECT-TYPE
SYNTAX HCPerfTimeElapsed SYNTAX HCPerfTimeElapsed
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of seconds that have elapsed since the "A read-only count of seconds that have elapsed since the
beginning of the current 1-day performance interval." beginning of the current 1-day performance interval."
REFERENCE REFERENCE
"[TR-159] 5.5.1.47" "[TR-159], Section 5.5.1.47"
::= { g9981PortPmCurEntry 10 } ::= { g9981PortPmCurEntry 10 }
g9981PortPmCur1DayRxLostCells OBJECT-TYPE g9981PortPmCur1DayRxLostCells OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of lost ATM cells detected by the G.Bond/ATM "A read-only count of lost ATM cells detected by the G.Bond/ATM
port (e.g. GBS-C), during the current 1-day performance port (e.g., the GBS-C) during the current 1-day performance
interval. interval.
This object is inhibited during Severely Errored Seconds (SES) This object is inhibited during Severely Errored Seconds (SES)
and Unavailable Seconds (UAS)." and Unavailable Seconds (UAS)."
::= { g9981PortPmCurEntry 11 } ::= { g9981PortPmCurEntry 11 }
g9981PortPmCur1DayTxLostCells OBJECT-TYPE g9981PortPmCur1DayTxLostCells OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of lost ATM cells detected by the peer "A read-only count of lost ATM cells detected by the peer
G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the
1-day performance history interval. current 1-day performance history interval.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
::= { g9981PortPmCurEntry 12 } ::= { g9981PortPmCurEntry 12 }
g9981PortPmCur1DayUpDiffDelay OBJECT-TYPE g9981PortPmCur1DayUpDiffDelay OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum upstream differential "A read-only value specifying the maximum upstream differential
delay between all operational BCEs in the GBS-C, measured in delay between all operational BCEs in the GBS-C, measured in
units of 0.1 ms, during the current 1-day performance units of 0.1 ms, during the current 1-day performance
interval. interval.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
::= { g9981PortPmCurEntry 13 } ::= { g9981PortPmCurEntry 13 }
g9981PortPmCur1DayDnDiffDelay OBJECT-TYPE g9981PortPmCur1DayDnDiffDelay OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum downstream differential "A read-only value specifying the maximum downstream
delay between all operational BCEs in the GBS-C, measured in differential delay between all operational BCEs in the GBS-C,
units of 0.1 ms, during the current 1-day performance measured in units of 0.1 ms, during the current 1-day
interval. performance interval.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
::= { g9981PortPmCurEntry 14 } ::= { g9981PortPmCurEntry 14 }
-- Port PM history: 15-min buckets -- Port PM history: 15-min buckets
g9981PortPm15MinTable OBJECT-TYPE g9981PortPm15MinTable OBJECT-TYPE
SYNTAX SEQUENCE OF G9981PortPm15MinEntry SYNTAX SEQUENCE OF G9981PortPm15MinEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 21, line 9 skipping to change at page 21, line 52
15-minute interval, up to 96 intervals). 15-minute interval, up to 96 intervals).
Entries in this table MUST be maintained in a persistent manner." Entries in this table MUST be maintained in a persistent manner."
::= { g9981PM 2 } ::= { g9981PM 2 }
g9981PortPm15MinEntry OBJECT-TYPE g9981PortPm15MinEntry OBJECT-TYPE
SYNTAX G9981PortPm15MinEntry SYNTAX G9981PortPm15MinEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond/ATM Port historical 15-minute PM table. "An entry in the G.Bond/ATM Port historical 15-minute PM table.
Each entry represents performance monitoring data for a Each entry represents Performance Monitoring data for a
G.Bond/ATM port, indexed by ifIndex, collected during a G.Bond/ATM port, indexed by the ifIndex, collected during a
particular 15-minute interval, indexed by particular 15-minute interval, indexed by the
g9981PortPm15MinIntervalIndex." g9981PortPm15MinIntervalIndex."
INDEX { ifIndex, g9981PortPm15MinIntervalIndex } INDEX { ifIndex, g9981PortPm15MinIntervalIndex }
::= { g9981PortPm15MinTable 1 } ::= { g9981PortPm15MinTable 1 }
G9981PortPm15MinEntry ::= G9981PortPm15MinEntry ::=
SEQUENCE { SEQUENCE {
g9981PortPm15MinIntervalIndex Unsigned32, g9981PortPm15MinIntervalIndex Unsigned32,
g9981PortPm15MinIntervalMoniTime HCPerfTimeElapsed, g9981PortPm15MinIntervalMoniTime HCPerfTimeElapsed,
g9981PortPm15MinIntervalRxLostCells HCPerfIntervalCount, g9981PortPm15MinIntervalRxLostCells HCPerfIntervalCount,
g9981PortPm15MinIntervalTxLostCells HCPerfIntervalCount, g9981PortPm15MinIntervalTxLostCells HCPerfIntervalCount,
g9981PortPm15MinIntervalUpDiffDelay HCPerfIntervalCount, g9981PortPm15MinIntervalUpDiffDelay HCPerfIntervalCount,
g9981PortPm15MinIntervalDnDiffDelay HCPerfIntervalCount, g9981PortPm15MinIntervalDnDiffDelay HCPerfIntervalCount,
g9981PortPm15MinIntervalValid TruthValue g9981PortPm15MinIntervalValid TruthValue
} }
g9981PortPm15MinIntervalIndex OBJECT-TYPE g9981PortPm15MinIntervalIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..96) SYNTAX Unsigned32 (1..96)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Performance Data Interval number. 1 is the most recent previous "Performance data interval number. 1 is the most recent previous
interval; interval 96 is 24 hours ago. interval; interval 96 is 24 hours ago.
Intervals 2..96 are OPTIONAL. Intervals 2..96 are OPTIONAL.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf15MinIntervalNumber." aGroupPerf15MinIntervalNumber."
REFERENCE REFERENCE
"[TR-159] 5.5.1.57" "[TR-159], Section 5.5.1.57"
::= { g9981PortPm15MinEntry 1 } ::= { g9981PortPm15MinEntry 1 }
g9981PortPm15MinIntervalMoniTime OBJECT-TYPE g9981PortPm15MinIntervalMoniTime OBJECT-TYPE
SYNTAX HCPerfTimeElapsed SYNTAX HCPerfTimeElapsed
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of seconds over which the performance data "A read-only count of seconds over which the performance data
was actually monitored. This value will be the same as the was actually monitored. This value will be the same as the
interval duration (900 seconds), except in a situation where interval duration (900 seconds), except in a situation where
performance data could not be collected for any reason." performance data could not be collected for any reason."
::= { g9981PortPm15MinEntry 2 } ::= { g9981PortPm15MinEntry 2 }
g9981PortPm15MinIntervalRxLostCells OBJECT-TYPE g9981PortPm15MinIntervalRxLostCells OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of lost ATM cells detected by a G.Bond/ATM "A read-only count of lost ATM cells detected by a G.Bond/ATM
port (e.g. GBS-C) in the receive direction, during the port (e.g., the GBS-C) in the receive direction, during the
15-minute performance history interval. 15-minute performance history interval.
Note that the total number of lost ATM cells is indicated by the Note that the total number of lost ATM cells is indicated by the
g9981PortStatRxLostCells object. g9981PortStatRxLostCells object.
This object is inhibited during Severely Errored Seconds (SES) This object is inhibited during Severely Errored Seconds (SES)
or Unavailable Seconds (UAS)." or Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.1" "[TR-159], Section 5.5.2.1"
::= { g9981PortPm15MinEntry 3 } ::= { g9981PortPm15MinEntry 3 }
g9981PortPm15MinIntervalTxLostCells OBJECT-TYPE g9981PortPm15MinIntervalTxLostCells OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only count of lost ATM cells detected by the peer "A read-only count of lost ATM cells detected by the peer
G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 15-minute G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the
performance history interval. 15-minute performance history interval.
Note that the total number of lost ATM cells is indicated by the Note that the total number of lost ATM cells is indicated by the
g9981PortStatTxLostCells object. g9981PortStatTxLostCells object.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.2" "[TR-159], Section 5.5.2.2"
::= { g9981PortPm15MinEntry 4 } ::= { g9981PortPm15MinEntry 4 }
g9981PortPm15MinIntervalUpDiffDelay OBJECT-TYPE g9981PortPm15MinIntervalUpDiffDelay OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum upstream differential "A read-only value specifying the maximum upstream differential
delay between all operational BCEs in the GBS, measured in delay between all operational BCEs in the GBS, measured in
units of 0.1 ms, during the 15-minute performance history units of 0.1 ms, during the 15-minute performance history
interval. interval.
Note that the current max upstream differential delay is Note that the current max upstream differential delay is
indicated by the g9981PortStatMaxUpDiffDelay object. indicated by the g9981PortStatMaxUpDiffDelay object.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.3" "[TR-159], Section 5.5.2.3"
::= { g9981PortPm15MinEntry 5 } ::= { g9981PortPm15MinEntry 5 }
g9981PortPm15MinIntervalDnDiffDelay OBJECT-TYPE g9981PortPm15MinIntervalDnDiffDelay OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum downstream differential "A read-only value specifying the maximum downstream
delay between all operational BCEs in the GBS, as perceived by differential delay between all operational BCEs in the GBS,
its peer port, measured in units of 0.1 ms, during the as perceived by its peer port, measured in units of 0.1 ms,
15-minute performance history interval. during the 15-minute performance history interval.
Note that the current max upstream differential delay is Note that the current max downstream differential delay is
indicated by the g9981PortStatMaxDnDiffDelay object. indicated by the g9981PortStatMaxDnDiffDelay object.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
REFERENCE REFERENCE
"[TR-159] 5.5.2.4" "[TR-159], Section 5.5.2.4"
::= { g9981PortPm15MinEntry 6 } ::= { g9981PortPm15MinEntry 6 }
g9981PortPm15MinIntervalValid OBJECT-TYPE g9981PortPm15MinIntervalValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only object indicating whether or not this history "A read-only object indicating whether or not this history
bucket contains valid data. Valid bucket is reported as true(1) bucket contains valid data. A valid bucket is reported as
and invalid bucket as false(2). true(1) and an invalid bucket as false(2).
If this history bucket is invalid the BTU MUST NOT produce If this history bucket is invalid, the BTU MUST NOT produce
notifications based upon the value of the counters in this notifications based upon the value of the counters in this
bucket. bucket.
Note that an implementation may decide not to store invalid Note that an implementation may decide not to store invalid
history buckets in its data base. In such case this object is history buckets in its database. In such a case, this object
not required as only valid history buckets are available while is not required, as only valid history buckets are available
invalid history buckets are simply not in the data base. while invalid history buckets are simply not in the database.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf15MinIntervalValid." aGroupPerf15MinIntervalValid."
REFERENCE REFERENCE
"[TR-159] 5.5.1.58" "[TR-159], Section 5.5.1.58"
::= { g9981PortPm15MinEntry 7 } ::= { g9981PortPm15MinEntry 7 }
-- Port PM history: 1-day buckets -- Port PM history: 1-day buckets
g9981PortPm1DayTable OBJECT-TYPE g9981PortPm1DayTable OBJECT-TYPE
SYNTAX SEQUENCE OF G9981PortPm1DayEntry SYNTAX SEQUENCE OF G9981PortPm1DayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains historical 1-day buckets of Performance "This table contains historical 1-day buckets of Performance
Monitoring information for a G.Bond/ATM port (a row for each Monitoring information for a G.Bond/ATM port (a row for each
1-day interval, up to 7 intervals). 1-day interval, up to 7 intervals).
Entries in this table MUST be maintained in a persistent manner." Entries in this table MUST be maintained in a persistent manner."
::= { g9981PM 3 } ::= { g9981PM 3 }
g9981PortPm1DayEntry OBJECT-TYPE g9981PortPm1DayEntry OBJECT-TYPE
SYNTAX G9981PortPm1DayEntry SYNTAX G9981PortPm1DayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond/ATM port historical 1-day PM table. "An entry in the G.Bond/ATM Port historical 1-day PM table.
Each entry represents performance monitoring data for such port, Each entry represents Performance Monitoring data for such a
indexed by ifIndex, collected during a particular 1-day port, indexed by the ifIndex, collected during a particular
interval, indexed by g9981PortPm1DayIntervalIndex." 1-day interval, indexed by the g9981PortPm1DayIntervalIndex."
INDEX { ifIndex, g9981PortPm1DayIntervalIndex } INDEX { ifIndex, g9981PortPm1DayIntervalIndex }
::= { g9981PortPm1DayTable 1 } ::= { g9981PortPm1DayTable 1 }
G9981PortPm1DayEntry ::= G9981PortPm1DayEntry ::=
SEQUENCE { SEQUENCE {
g9981PortPm1DayIntervalIndex Unsigned32, g9981PortPm1DayIntervalIndex Unsigned32,
g9981PortPm1DayIntervalMoniTime HCPerfTimeElapsed, g9981PortPm1DayIntervalMoniTime HCPerfTimeElapsed,
g9981PortPm1DayIntervalRxLostCells HCPerfIntervalCount, g9981PortPm1DayIntervalRxLostCells HCPerfIntervalCount,
g9981PortPm1DayIntervalTxLostCells HCPerfIntervalCount, g9981PortPm1DayIntervalTxLostCells HCPerfIntervalCount,
g9981PortPm1DayIntervalUpDiffDelay HCPerfIntervalCount, g9981PortPm1DayIntervalUpDiffDelay HCPerfIntervalCount,
g9981PortPm1DayIntervalDnDiffDelay HCPerfIntervalCount, g9981PortPm1DayIntervalDnDiffDelay HCPerfIntervalCount,
g9981PortPm1DayIntervalValid TruthValue g9981PortPm1DayIntervalValid TruthValue
} }
g9981PortPm1DayIntervalIndex OBJECT-TYPE g9981PortPm1DayIntervalIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..7) SYNTAX Unsigned32 (1..7)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Performance Data Interval number. 1 is the most recent previous "Performance data interval number. 1 is the most recent previous
interval; interval 7 is 24 hours ago. interval; interval 7 is 24 hours ago.
Intervals 2..7 are OPTIONAL. Intervals 2..7 are OPTIONAL.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf1DayIntervalNumber." aGroupPerf1DayIntervalNumber."
REFERENCE REFERENCE
"[TR-159] 5.5.1.62" "[TR-159], Section 5.5.1.62"
::= { g9981PortPm1DayEntry 1 } ::= { g9981PortPm1DayEntry 1 }
g9981PortPm1DayIntervalMoniTime OBJECT-TYPE g9981PortPm1DayIntervalMoniTime OBJECT-TYPE
SYNTAX HCPerfTimeElapsed SYNTAX HCPerfTimeElapsed
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of seconds over which the performance data was actually "A count of seconds over which the performance data was actually
monitored. This value will be the same as the interval duration monitored. This value will be the same as the interval duration
(86400 seconds), except in a situation where performance data (86400 seconds), except in a situation where performance data
could not be collected for any reason. could not be collected for any reason.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf1DayIntervalMoniSecs." aGroupPerf1DayIntervalMoniSecs."
REFERENCE REFERENCE
"[TR-159] 5.5.1.64" "[TR-159], Section 5.5.1.64"
::= { g9981PortPm1DayEntry 2 } ::= { g9981PortPm1DayEntry 2 }
g9981PortPm1DayIntervalRxLostCells OBJECT-TYPE g9981PortPm1DayIntervalRxLostCells OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of lost ATM cells detected by the G.Bond/ATM port "A count of lost ATM cells detected by the G.Bond/ATM port
(e.g. GBS-C), during the 1-day performance history interval. (e.g., the GBS-C) during the 1-day performance history interval.
This object is inhibited during Severely Errored Seconds (SES) This object is inhibited during Severely Errored Seconds (SES)
and Unavailable Seconds (UAS)." and Unavailable Seconds (UAS)."
::= { g9981PortPm1DayEntry 3 } ::= { g9981PortPm1DayEntry 3 }
g9981PortPm1DayIntervalTxLostCells OBJECT-TYPE g9981PortPm1DayIntervalTxLostCells OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "cells" UNITS "cells"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of lost ATM cells detected by the peer G.Bond/ATM port "A count of lost ATM cells detected by the peer G.Bond/ATM port
(e.g. by GBS-R for GBS-C), during the 1-day performance history (e.g., by the GBS-R for the GBS-C) during the 1-day performance
interval. history interval.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
::= { g9981PortPm1DayEntry 4 } ::= { g9981PortPm1DayEntry 4 }
g9981PortPm1DayIntervalUpDiffDelay OBJECT-TYPE g9981PortPm1DayIntervalUpDiffDelay OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum upstream differential "A read-only value specifying the maximum upstream differential
delay between all operational BCEs in the GBS-C, measured in delay between all operational BCEs in the GBS-C, measured in
units of 0.1 ms, during the 1-day performance history interval. units of 0.1 ms, during the 1-day performance history interval.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
::= { g9981PortPm1DayEntry 5 } ::= { g9981PortPm1DayEntry 5 }
g9981PortPm1DayIntervalDnDiffDelay OBJECT-TYPE g9981PortPm1DayIntervalDnDiffDelay OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "0.1 ms" UNITS "0.1 ms"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only value specifying maximum downstream differential "A read-only value specifying the maximum downstream
delay between all operational BCEs in the GBS-C, measured in differential delay between all operational BCEs in the GBS-C,
units of 0.1 ms, during the 1-day performance history interval. measured in units of 0.1 ms, during the 1-day performance
history interval.
This object is inhibited during Unavailable Seconds (UAS)." This object is inhibited during Unavailable Seconds (UAS)."
::= { g9981PortPm1DayEntry 6 } ::= { g9981PortPm1DayEntry 6 }
g9981PortPm1DayIntervalValid OBJECT-TYPE g9981PortPm1DayIntervalValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-only object indicating whether or not this history "A read-only object indicating whether or not this history
bucket contains valid data. Valid bucket is reported as true(1) bucket contains valid data. A valid bucket is reported as
and invalid bucket as false(2). true(1) and an invalid bucket as false(2).
If this history bucket is invalid the BTU MUST NOT produce If this history bucket is invalid, the BTU MUST NOT produce
notifications based upon the value of the counters in this notifications based upon the value of the counters in this
bucket. bucket.
Note that an implementation may decide not to store invalid Note that an implementation may decide not to store invalid
history buckets in its data base. In such case this object is history buckets in its database. In such a case, this object
not required as only valid history buckets are available while is not required, as only valid history buckets are available
invalid history buckets are simply not in the data base. while invalid history buckets are simply not in the database.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf1DayIntervalValid." aGroupPerf1DayIntervalValid."
REFERENCE REFERENCE
"[TR-159] 5.5.1.63" "[TR-159], Section 5.5.1.63"
::= { g9981PortPm1DayEntry 7 } ::= { g9981PortPm1DayEntry 7 }
-- --
-- Conformance Statements -- Conformance Statements
-- --
g9981Groups OBJECT IDENTIFIER g9981Groups OBJECT IDENTIFIER
::= { g9981Conformance 1 } ::= { g9981Conformance 1 }
g9981Compliances OBJECT IDENTIFIER g9981Compliances OBJECT IDENTIFIER
skipping to change at page 28, line 41 skipping to change at page 29, line 41
g9981PortPm15MinIntervalRxLostCells, g9981PortPm15MinIntervalRxLostCells,
g9981PortPm15MinIntervalTxLostCells, g9981PortPm15MinIntervalTxLostCells,
g9981PortPm15MinIntervalUpDiffDelay, g9981PortPm15MinIntervalUpDiffDelay,
g9981PortPm15MinIntervalDnDiffDelay, g9981PortPm15MinIntervalDnDiffDelay,
g9981PortPm15MinIntervalValid g9981PortPm15MinIntervalValid
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects supporting OPTIONAL historical "A collection of objects supporting OPTIONAL historical
Performance Monitoring information for G.Bond/ATM ports, during Performance Monitoring information for G.Bond/ATM ports, during
previous 15-minute intervals ." previous 15-minute intervals."
::= { g9981Groups 5 } ::= { g9981Groups 5 }
g9981Perf1DayGroup OBJECT-GROUP g9981Perf1DayGroup OBJECT-GROUP
OBJECTS { OBJECTS {
g9981PortPm1DayIntervalMoniTime, g9981PortPm1DayIntervalMoniTime,
g9981PortPm1DayIntervalRxLostCells, g9981PortPm1DayIntervalRxLostCells,
g9981PortPm1DayIntervalTxLostCells, g9981PortPm1DayIntervalTxLostCells,
g9981PortPm1DayIntervalUpDiffDelay, g9981PortPm1DayIntervalUpDiffDelay,
g9981PortPm1DayIntervalDnDiffDelay, g9981PortPm1DayIntervalDnDiffDelay,
g9981PortPm1DayIntervalValid g9981PortPm1DayIntervalValid
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects supporting OPTIONAL historical "A collection of objects supporting OPTIONAL historical
Performance Monitoring information for G.Bond/ATM ports, during Performance Monitoring information for G.Bond/ATM ports, during
previous 1-day intervals ." previous 1-day intervals."
::= { g9981Groups 6 } ::= { g9981Groups 6 }
-- Compliance Statements -- Compliance Statements
g9981Compliance MODULE-COMPLIANCE g9981Compliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for G.Bond/ATM interfaces. "The compliance statement for G.Bond/ATM interfaces.
Compliance with the following external compliance statements Compliance with the following external compliance statements
is REQUIRED: is REQUIRED:
skipping to change at page 30, line 6 skipping to change at page 31, line 6
GROUP g9981Perf1DayGroup GROUP g9981Perf1DayGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting 1-day historical Performance Monitoring." supporting 1-day historical Performance Monitoring."
::= { g9981Compliances 1 } ::= { g9981Compliances 1 }
END END
7. Security Considerations 7. Security Considerations
There is a number of managed objects defined in this MIB module with There are a number of managed objects defined in this MIB module with
a MAX-ACCESS clause of read-write. Such objects may be considered a MAX-ACCESS clause of read-write. Such objects may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The 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. These protection can have a negative effect on network operations. These
are the tables and objects and their sensitivity/vulnerability: are the tables and objects and their sensitivity/vulnerability:
o Changing of g9981PortConfTable configuration parameters MAY lead o Changing of g9981PortConfTable configuration parameters MAY lead
to a potential Service Level Agreement (SLA) breach, for example to a potential Service Level Agreement (SLA) breach, for example,
if a traffic delay is increased as a result of the higher delay if a traffic delay is increased as a result of the higher delay
tolerance (increased g9981PortConfUpDiffDelayTolerance and/or tolerance (increased g9981PortConfUpDiffDelayTolerance and/or
g9981PortConfDnDiffDelayTolerance), or the differential delay g9981PortConfDnDiffDelayTolerance), or the differential delay
tolerance notifications are disabled by manipulating the tolerance notifications are disabled by manipulating the
g9981PortConfDiffDelayToleranceExceededEnable parameter. g9981PortConfDiffDelayToleranceExceededEnable parameter.
Some of the readable objects in this MIB module (i.e., those with Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments since, collectively, they vulnerable in some network environments since, collectively, they
provide information about the performance of network interfaces and provide information about the performance of network interfaces and
can reveal some aspects of their configuration. can reveal some aspects of their configuration.
It is thus important to control even GET and/or NOTIFY access to It is thus important to control even GET and/or NOTIFY access to
these objects and possibly even encrypt the values of these objects these objects and possibly to even encrypt the values of these
when sending them over the network via SNMP. objects when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
Implementations MUST provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), including full support for SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM) MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH [RFC5591] in combination with a secure transport such as SSH
[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 8. IANA Considerations
An object identifier for g9981MIB MODULE-IDENTITY SHALL be allocated IANA has assigned 208 as the object identifier for g9981MIB
by IANA [1] in the MIB-2 transmission sub-tree, before this document MODULE-IDENTITY in the MIB-2 transmission sub-tree
is published as an RFC. <http://www.iana.org/>.
9. Acknowledgments 9. 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 10. References
10.1. Normative References 10.1. Normative References
[G.998.1] ITU-T, "ATM-based multi-pair bonding", [G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T
ITU-T Recommendation G.998.3, Recommendation G.998.1, January 2005,
January 2005. <http://www.itu.int/rec/T-REC-G.998.1/en>.
[I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL
multi-pair bonding (G.Bond) MIB",
draft-ietf-adslmib-gbond-mib-10 (work
in progress), March 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
and J. Schoenwaelder, Ed., "Structure Requirement Levels", BCP 14, RFC 2119, March 1997.
of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
and J. Schoenwaelder, Ed., "Textual Schoenwaelder, Ed., "Structure of Management Information
Conventions for SMIv2", STD 58, Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, "Conformance Statements Schoenwaelder, Ed., "Textual Conventions for SMIv2",
for SMIv2", STD 58, RFC 2580, STD 58, RFC 2579, April 1999.
April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Interfaces Group MIB", RFC 2863, "Conformance Statements for SMIv2", STD 58, RFC 2580,
June 2000. April 1999.
[RFC3414] Blumenthal, U. and B. Wijnen, "User- [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
based Security Model (USM) for version MIB", RFC 2863, June 2000.
3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414,
December 2002.
[RFC3705] Ray, B. and R. Abbi, "High Capacity [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
Textual Conventions for MIB Modules (USM) for version 3 of the Simple Network Management
Using Performance History Based on 15 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
Minute Intervals", RFC 3705,
February 2004.
[RFC3826] Blumenthal, U., Maino, F., and K. [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions
McCloghrie, "The Advanced Encryption for MIB Modules Using Performance History Based on 15
Standard (AES) Cipher Algorithm in the Minute Intervals", RFC 3705, February 2004.
SNMP User-based Security Model",
RFC 3826, June 2004.
[TR-159] Beili, E. and M. Morgenstern, [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
"Management Framework for xDSL Advanced Encryption Standard (AES) Cipher Algorithm in the
Bonding", Broadband Forum technical SNMP User-based Security Model", RFC 3826, June 2004.
report TR-159, December 2008.
10.2. Informative References [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)",
RFC 5591, June 2009.
[ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", <ht [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
tp://www.ietf.org/html.charters/ Shell Transport Model for the Simple Network Management
adslmib-charter.html>. Protocol (SNMP)", RFC 5592, June 2009.
[RFC2515] Tesink, K., "Definitions of Managed [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Objects for ATM Management", RFC 2515, Model for the Simple Network Management Protocol (SNMP)",
February 1999. RFC 6353, July 2011.
[RFC3410] Case, J., Mundy, R., Partain, D., and [RFC6765] Beili, E. and M. Morgenstern, "xDSL Multi-Pair Bonding
B. Stewart, "Introduction and (G.Bond) MIB", RFC 6765, February 2013.
Applicability Statements for Internet-
Standard Management Framework",
RFC 3410, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for [TR-159] Beili, E. and M. Morgenstern, "Management Framework for
MIB Modules Using Performance History xDSL Bonding", Broadband Forum Technical Report TR-159,
Based on 15 Minute Intervals", December 2008, <http://www.broadband-forum.org/technical/
RFC 3593, September 2003. download/TR-159.pdf>.
[RFC4181] Heard, C., "Guidelines for Authors and 10.2. Informative References
Reviewers of MIB Documents", BCP 111,
RFC 4181, September 2005.
[RFC5591] Harrington, D. and W. Hardaker, [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter",
"Transport Security Model for the <http://datatracker.ietf.org/wg/adslmib/charter/>.
Simple Network Management Protocol
(SNMP)", RFC 5591, June 2009.
[RFC5592] Harrington, D., Salowey, J., and W. [AF-PHY-0086]
Hardaker, "Secure Shell Transport Model ATM Forum, "Inverse Multiplexing for ATM (IMA)
for the Simple Network Management Specification Version 1.1", ATM Forum specification af-
Protocol (SNMP)", RFC 5592, June 2009. phy-0086.001, March 1999, <http://www.broadband-forum.org/
ftp/pub/approved-specs/af-phy-0086.001.pdf>.
[RFC6353] Hardaker, W., "Transport Layer Security [RFC2515] Tesink, K., "Definitions of Managed Objects for ATM
(TLS) Transport Model for the Simple Management", RFC 2515, February 1999.
Network Management Protocol (SNMP)",
RFC 6353, July 2011.
[af-phy-0086] ATM Forum, "Inverse Multiplexing for [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
ATM (IMA) Specification Version 1.1", "Introduction and Applicability Statements for Internet-
ATM Forum specification af-pfy- Standard Management Framework", RFC 3410, December 2002.
0086.001, March 1999.
URIs [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals",
RFC 3593, September 2003.
[1] <http://www.iana.org/> [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB
Documents", BCP 111, RFC 4181, September 2005.
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
25 Bazel St. 25 Bazel St.
Petach-Tikva 49103 Petach-Tikva 49103
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
 End of changes. 190 change blocks. 
377 lines changed or deleted 363 lines changed or added

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