BitStorm 2600 and GranDSLAM 4200 IP DSLAM SNMP Reference

BitStorm 2600 and GranDSLAM 4200 IP DSLAM SNMP Reference
BitStorm 2600 and GranDSLAM 4200IP
SNMP Reference Guide
May 2006
Document Part Number: 2600-A2-GB22-50
Zhone Technologies
@Zhone Way
7001 Oakport Street
Oakland, CA 94621
USA
510.777.7000
www.zhone.com
[email protected]
COPYRIGHT 2000–2005 Zhone Technologies, Inc. All rights reserved.
This publication is protected by copyright law. No part of this publication may be copied, distributed,
displayed, modified, transmitted, stored in a retrieval system, or translated without express written
permission from Zhone Technologies, Inc.
Acculink, ADSL/R, Bitstorm, Comsphere, DSL the Easy Way, Etherloop, FrameSaver, GigMux,
GranDSLAM, GrandVIEW, Hotwire, the Hotwire logo, iMarc, JetFusion, Jetstream, JetVision, MALC,
MVL, NextEDGE, Net to Net Technologies, Paradyne, the Paradyne logo, Quick Channel, Raptor,
ReachDSL, SLMS, StormPort, TruePut, Z-Edge, Zhone, ZMS, and the Zhone logo are trademarks owned
by Zhone Technologies, Inc., which may be registered in some jurisdictions.
Zhone Technologies makes no representation or warranties with respect to the contents hereof and
specifically disclaims any implied warranties of merchantability, noninfringement, or fitness for a
particular purpose. Further, Zhone Technologies reserves the right to revise this publication and to make
changes from time to time in the contents hereof without obligation of Zhone Technologies to notify any
person of such revision or changes.
End User License Agreement (Zhone and Affiliates)
Do not install this Software unless you agree to these provisions.
Return the Software promptly for a refund if you do not agree.
License. Zhone Technologies, Inc. and/or an affiliate ("Zhone") hereby grants you ("User")—either an
individual or a single business entity—the non-exclusive right to install, access, run, or interact with
("Use") one copy of the enclosed software (which may have been, or may be, provided on media, as part of
a hardware platform, through download, or otherwise) and associated documentation ("Software") on the
first computer system on which User installs the Software ("System") solely for internal business purposes
(including, without limitation, providing products and services to User's customers) and subject to the
restrictions below). Zhone may, in its sole discretion, make available future updates or upgrades to the
Software each of which is also Software subject hereto. Title to and all patent rights, copyrights and other
intellectual property rights in the Software are retained by Zhone and its direct and indirect suppliers and
licensors ("Licensors").
Restrictions. The Software may not be (a) Used on or from any system other than the System; (b) Used
with more than any maximum number of subscribers stated in the documentation accompanying the
Software; (c) Used so as to circumvent any technological measure included therein or provided by Zhone
from time to time to control access to or limit use of the Software; (d) sublicensed, rented, leased or lent to
third parties; (e) imported or exported into any jurisdiction except in compliance with all applicable laws of
the United States and such jurisdiction; (f) transferred to a third party unless (A) User transfers the original
and all surviving copies to a third party who has agreed in writing to be bound hereby and (B) such third
party pays to Zhone such reasonable additional fee as Zhone may impose
2
BitStorm 2600 and GranDSLAM 4200IP SNMP Reference Guide
2600-A2-GB22-50
from time to time with respect to such transfer; or (g) made available to third
parties as part of any time-sharing or service bureau arrangement. User shall
not have the right to use the Software or any portion thereof for a use other
than that contemplated by its documentation. User will not copy all or any
part of the Software or attempt, or encourage or permit any third party, to
modify, adapt, make derivative works from, reverse engineer, reverse
compile, disassemble or decompile the Software or any portion thereof except
and only to the extent that such activity is expressly permitted by law
notwithstanding this limitation. Violation of any of the foregoing shall be
deemed a material breach hereof. User may make a reasonable number of
copies solely for archival or disaster recovery and subject to the restrictions
imposed by copyright law, but may not modify or otherwise copy the
Software. User agrees to reproduce product identification, copyright and other
proprietary notices of Zhone and Licensors on all copies. User's rights are
only as expressly stated herein. Zhone may immediately terminate your rights
if you violate the provisions hereof.
Limited Warranty. Zhone warrants that the media containing the Software is free from defects in material
and workmanship for ninety (90) days following your purchase of the Software. You may provide written
notice of such defect (addressed to Zhone Technologies, Inc., Attention: Customer Service, 7001 Oakport
Street @ Zhone Way, Oakland, CA 94621) no later than ten (10) days following expiration of such period
and, as your sole and exclusive remedy, Zhone will provide replacement media. NEITHER ZHONE NOR
ITS LICENSORS MAKE ANY OTHER WARRANTY, EXPRESS, IMPLIED OR STATUTORY.
ZHONE AND ITS LICENSORS DISCLAIM ALL WARRANTIES OF FITNESS FOR PARTICULAR
PURPOSE, MERCHANTABILITY AND NON-INFRINGEMENT. Some states or other jurisdictions do
not allow the exclusion of implied warranties on limitations on how long an implied warranty lasts, so the
above limitations may not apply to you. This warranty gives you specific legal rights, and you may also
have other rights which vary from one state or jurisdiction to another.
Limit of Liability. In case of any claim hereunder or related to the Software, neither Zhone nor its
Licensors shall be liable for direct damages exceeding the price paid by User for the Software or for
special, incidental, consequential or indirect damages, even if advised in advance of the potential thereof.
U.S. Government Users. The Software is a "commercial item" as defined at 48 C.F.R. 2.101, consisting of
"commercial computer software" and "commercial computer software documentation" as such terms are
used in 48 C.F.R. 12.212. Under 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 to 227.7202-4, U.S.
Government Users acquire the Software only with the rights set forth therein.
Third Party Licensors. This Zhone End User License Agreement may be accompanied by differing or
additional provisions applicable to portions of the Software provided by one or more Licensors ("Licensor
Provisions"). User acknowledges and agrees that its Use of such portions of the Software is subject to the
Licensor Provisions.
! Important Safety Instructions
1 Read and follow all warning notices and instructions marked on the product or included in the manual.
2 This product is intended to be used with a 3-wire grounding type plug — a plug that has a grounding
pin. This is a safety feature. Equipment grounding is vital to ensure safe operation. Do not defeat the
purpose of the grounding type plug by modifying the plug or using an adapter. Prior to installation, use
an outlet tester or a voltmeter to check the AC receptacle for the presence of earth ground. If the
2600-A2-GB22-50
BitStorm 2600 and GranDSLAM 4200IP SNMP Reference Guide
3
receptacle is not properly grounded, the installation must not continue
until a qualified electrician has corrected the problem.
If a 3-wire grounding type power source is not available, consult a qualified electrician to determine
another method of grounding the equipment.
3 Slots and openings in the cabinet are provided for ventilation. To ensure reliable operation of the
product and to protect it from overheating, these slots and openings must not be blocked or covered.
4 Do not allow anything to rest on the power cord and do not locate the product where persons will walk
on the power cord.
5 Do not attempt to service this product yourself, as it will void the warranty. Opening or removing
covers may expose you to dangerous high voltage points or other risks. Refer all servicing to qualified
service personnel.
6 General purpose cables are described for use with this product. Special cables, which may be required
by the regulatory inspection authority for the installation site, are the responsibility of the customer. To
reduce the risk of fire, use a UL Listed or CSA Certified, minimum No. 26 AWG (0.128 mm2)
telecommunication cable, or comparable cables certified for use in the country of installation.
7 When installed in the final configuration, the product must comply with the applicable Safety
Standards and regulatory requirements of the country in which it is installed. If necessary, consult with
the appropriate regulatory agencies and inspection authorities to ensure compliance.
8 A rare phenomenon can create a voltage potential between the earth grounds of two or more buildings.
If products installed in separate buildings are interconnected, the voltage potential may cause a
hazardous condition. Consult a qualified electrical consultant to determine whether or not this
phenomenon exists and, if necessary, implement corrective action prior to interconnecting the
products.
9 In addition, if the equipment is to be used with telecommunications circuits, take the following
precautions:
— Never install telephone wiring during a lightning storm.
— Never install telephone jacks in wet locations unless the jack is specifically designed for wet
locations.
— Never touch uninsulated telephone wires or terminals unless the telephone line has been
disconnected at the network interface.
— Use caution when installing or modifying telephone lines.
— Avoid using a telephone (other than a cordless type) during an electrical storm. There may be a
remote risk of electric shock from lightning.
— Do not use the telephone to report a gas leak in the vicinity of the leak.
10 CLASS 1 LASER PRODUCT: This product has provisions for the customer to install a Class 1 laser
transciever, which provides optical coupling to the telecommunication network. Once a Class 1 laser
product is installed, the equipment is to be considered to be a Class 1 Laser Product (Appareil à Laser
de Classe 1). The customer is responsible for selecting and installing the laser transciever and for
insuring that the Class 1 AEL (Allowable Emission Limit) per EN/IEC 60825 is not exceeded after the
laser transponders have been installed. Do not install laser products whose class rating is greater than
1. Refer to all important safety instructions that accompanied the transciever prior to installation. Only
laser Class 1 devices, certified for use in the country of installation by the cognizant agency are to be
utilized in this product.
11 The equipment is intended for installation in a max. 50° C ambient temperature, in an environment that
is free of dust and dirt.
4
BitStorm 2600 and GranDSLAM 4200IP SNMP Reference Guide
2600-A2-GB22-50
12 The power supply cord for countries other than North America is to be a
minimum H05 V V-F type, min. 0.75 mm2, 2-conductor and earth ground terminated in an IEC 320
connector on one end, and a plug which is certified for use in the country of installation at the other
end.
13 Do not physically stack more than eight (8) 26x1 units high. Physical stability has not been evaluated
for stacking higher than eight units, and any configuration greater than eight may result in an unstable
(tip-over) condition. Ensure that the four (4) rubber feet supplied with the product have been installed
on the bottom of each unit prior to stacking any 26x1 units on top of one another.
EMI Notices
! UNITED STATES – EMI NOTICE:
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used
in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
The authority to operate this equipment is conditioned by the requirements that no
modifications will be made to the equipment unless the changes or modifications are expressly
approved by Paradyne Corporation.
If the equipment includes a ferrite choke or chokes, they must be installed per the installation
instructions.
! CANADA – EMI NOTICE:
This Class A digital apparatus meets all requirements of the Canadian interference-causing
equipment regulations.
Cet appareil numérique de la classe A respecte toutes les exigences du réglement sur le matérial
brouilleur du Canada.
2600-A2-GB22-50
BitStorm 2600 and GranDSLAM 4200IP SNMP Reference Guide
5
Notices to Users of the Canadian Telephone Network
NOTICE: This equipment meets the applicable Industry Canada Terminal Equipment Technical
Specifications. This is confirmed by the registration number. The abbreviation IC before the registration
number signifies that registration was performed based on a Declaration of Conformity indicating that
Industry Canada technical specifications were met. It does not imply that Industry Canada approved the
equipment.
NOTICE: The Ringer Equivalence Number (REN) for this terminal equipment is labeled on the
equipment. The REN assigned to each terminal equipment provides an indication of the maximum number
of terminals allowed to be connected to a telephone interface. The termination on an interface may consist
of any combination of devices subject only to the requirement that the sum of the Ringer Equivalence
Numbers of all the devices does not exceed five.
When the equipment is used in a customer premises environment, a Model 6051 POTS Splitter must be
used to ensure CS-03 compliance. Refer to the POTS splitter installation instructions for details.
CE Marking
When the product is marked with the CE mark on the equipment label, a supporting Declaration of
Conformity may be downloaded from the Zhone World Wide Web site at www.zhone.com.
Japan
Class A ITE
This is a Class A product based on the standard of the Voluntary Control Council for interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.
6
BitStorm 2600 and GranDSLAM 4200IP SNMP Reference Guide
2600-A2-GB22-50
Table of Contents
Table of Contents
1.
Document Purpose and Intended Audience ....................................................................................................
v
Document Summary ..........................................................................................................................................
v
Product-Related Documents ............................................................................................................................
vi
Introduction............................................................................................................................................................1
1.1
Internet Society Copyright Statement.......................................................................................................1
2.
Traps .......................................................................................................................................................................2
3.
Ordered MIB List ..................................................................................................................................................8
4.
Miscellaneous Textual Conventions ...................................................................................................................11
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
4.14
4.15
4.16
4.17
4.18
4.19
5.
BITS............................................................................................................................................................12
ContactState ..............................................................................................................................................12
DateAndTime ............................................................................................................................................13
IpAddress ...................................................................................................................................................13
MacAddress ...............................................................................................................................................14
PerfCurrentCount....................................................................................................................................14
PerfIntervalCount .....................................................................................................................................14
PdnPPPState..............................................................................................................................................14
PdnTestAndIncrDerivedIndexTC ...........................................................................................................15
PhysAddress ..............................................................................................................................................15
RowStatus ..................................................................................................................................................15
SwitchState ................................................................................................................................................16
TblCmd ......................................................................................................................................................16
TestAndIncr...............................................................................................................................................17
TimeInterval ..............................................................................................................................................18
TimeStamp.................................................................................................................................................18
TimeTicks ..................................................................................................................................................18
TruthValue ................................................................................................................................................19
VnidRange .................................................................................................................................................19
Management Information Base (MIBs) .............................................................................................................19
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
RFC1213-MIB — RFC 1213 ....................................................................................................................20
SNMPv2-MIB — RFC 1907.....................................................................................................................22
IF-MIB — RFC 2863 ................................................................................................................................31
IP-MIB — RFC 2011 ................................................................................................................................77
IP-FORWARD-MIB — RFC 2096..........................................................................................................86
ENTITY-MIB (Version 2) — RFC 2737.................................................................................................92
ENTITY-SENSOR-MIB — RFC 3433 .................................................................................................130
EtherLike-MIB — RFC 2665.................................................................................................................137
2600-A2-GB22-50
May 2006
i
Table of Contents
5.9
5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.17
5.18
5.19
5.20
5.21
5.22
5.23
5.24
5.25
5.26
5.27
5.28
5.29
5.30
5.31
5.32
5.33
5.34
5.35
5.36
5.37
5.38
5.39
5.40
5.41
5.42
5.43
5.44
5.45
5.46
5.47
5.48
5.49
5.50
5.51
5.52
5.53
5.54
5.55
5.56
5.57
5.58
5.59
5.60
5.61
5.62
ii
MAU-MIB — RFC2668..........................................................................................................................148
RS-232-MIB — RFC 1659......................................................................................................................175
ADSL-LINE-MIB — RFC 2662 ............................................................................................................187
ADSL-LINE-EXT-MIB — RFC 3440...................................................................................................230
HDSL2-SHDSL-LINE-MIB — RFC 3276............................................................................................247
DS1-MIB — RFC 2495 ...........................................................................................................................282
ATM-MIB — RFC 2515.........................................................................................................................313
ATM-FORUM-SNMP-M4-MIB — AF-NM-0095.001 ........................................................................343
BRIDGE-MIB — RFC 1493 ..................................................................................................................347
P-BRIDGE-MIB — RFC 2674...............................................................................................................357
Q-BRIDGE-MIB — RFC 2674 ..............................................................................................................373
IGMP-STD-MIB — RFC 2933 ..............................................................................................................400
PPP-LCP-MIB — RFC 1471 .................................................................................................................408
PPP-BRIDGE-NCP-MIB — RFC 1474 ................................................................................................419
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib ............................................................426
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib ....................................................................437
PDN-MPE-HEALTH-AND-STATUS-MIB — mpe_HealthAndStatus.mib .....................................444
PDN-ADSL-LINE-EXT-MIB ................................................................................................................446
PDN-ADSL-SELT-MIB..........................................................................................................................474
PDN-ARP-MIB........................................................................................................................................483
PDN-ATM-BRIDGE-IWF-MIB ............................................................................................................498
PDN-ATMEXT-MIB ..............................................................................................................................501
PDN-ATMM4EXT-MIB ........................................................................................................................510
PDN-ATMSTATS-MIB..........................................................................................................................522
PDN-BRIDGE-EXT-MIB ......................................................................................................................530
PDN-CONFIG-MIB................................................................................................................................539
PDN-CONTROL-MIB............................................................................................................................555
PDN-DHCP-MIB ....................................................................................................................................576
PDN-DS1CONFIG-MIB.........................................................................................................................579
PDN-DS1EXT-MIB ................................................................................................................................587
PDN-DOT1QEXT-MIB..........................................................................................................................592
PDN-DSLAM-SYSTEM-MIB................................................................................................................599
PDN-DSL-ATM-BOND-MIB ................................................................................................................613
PDN-ENTITY-SENSOR-EXT-MIB......................................................................................................641
PDN-ETHER-MIB..................................................................................................................................647
PDN-FILTER-MIB .................................................................................................................................653
PDN-HDLC-MIB ....................................................................................................................................672
PDN-IFDEV-IWF-MIB ..........................................................................................................................676
PDN-IF-EXT-CONFIG-MIB .................................................................................................................680
PDN-IGMP-STD-EXT-MIB ..................................................................................................................683
PDN-INET-MIB ......................................................................................................................................690
PDN-IP-MULTICAST-MIB ..................................................................................................................693
PDN-PPP-BRIDGE-NCP-EXT-MIB ....................................................................................................696
PDN-PPP-LCP-EXT-MIB......................................................................................................................700
PDN-PPP-ML-MIB.................................................................................................................................714
PDN-PROTO-SPEC-FILTER-MIB......................................................................................................722
PDN-REACHDSL-MIB..........................................................................................................................726
PDN-SECURITY-MIB ...........................................................................................................................738
PDN-HDSL2-SHDSL-LINE-MIB .........................................................................................................753
PDN-SPECTRUMMGMT-MIB ............................................................................................................772
PDN-STACKABLE-MIB .......................................................................................................................782
PDN-SYSLOG-MIB................................................................................................................................792
PDN-DEVICE-TIME-MIB ....................................................................................................................796
PDN-UPLINK-TAGGING-MIB............................................................................................................800
May 2006
2600-A2-GB22-50
Table of Contents
5.63 PDN-VLAN-MIB ....................................................................................................................................807
2600-A2-GB22-50
May 2006
iii
Table of Contents
iv
May 2006
2600-A2-GB22-50
About This Guide
Document Purpose and Intended Audience
This guide contains the information necessary to use Simple Network Management
Protocol (SNMP) to configure and monitor the BitStorm 2600 and GranDSLAM 4200 IP
DSLAMs. This document is based on firmware release 2.4.10
Document Summary
Section
Description
Section 1, Introduction
Describes the format and contents of this document.
Section 2, Traps
Lists traps supported by the BitStorm 2600 and GranDSLAM 4200
IP DSLAMs.
Section 3, Ordered MIB List
Lists in order MIBs that must be loaded for full support.
Section 4, Miscellaneous Textual
Conventions
Describes typographic conventions used to convey MIB constructs
and object types.
Section 5, Management Information
Base (MIBs)
Describes MIB support in the BitStorm 2600 and GranDSLAM
4200 IP DSLAMs.
Index
Lists MIBs and MIB objects for easy reference.
A master glossary of terms and acronyms used in Paradyne documents is available online
at www.paradyne.com. Select Support → Technical Manuals → Technical Glossary.
2600-A2-GB22-50
May 2006
v
Product-Related Documents
Complete documentation for this product is available online at www.paradyne.com.
Select Support → Technical Manuals.
vi
Document Number
Document Title
2600-A2-GB21
BitStorm 2600 and GranDSLAM 4200 IP DSLAM Command Line
Interface Reference
2600-A2-GN20
BitStorm 2600 IP DSLAM Installation Guide
4200-A2-GN21
GranDSLAM 4200 IP DSLAM Installation Guide
May 2006
2600-A2-GB22-50
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
1.
Introduction
This document identifies the MIBs and MIB objects supported in the BitStorm 2600 and GranDSLAM 4200 IP
DSLAM.
The document is arranged such that each MIB is a level 2 (x.y) heading under the Management Information Base
(MIBs), Section 5, Page 19. Each MIB section has a unique header where the name of the MIB is identified on all
pages applicable to that particular MIB. The MIB sections are laid out textually such that:
•
•
•
The OIDs are identified for the MIB
Any textual conventions defined in the MIB are identified
MIB objects are listed along with their:
—
object name
—
OID
—
syntax
—
status
—
support
Something is not supported when one of the following is true:
•
•
•
A whole table does not exist in the MIB tree
A particular object does not exist in the MIB tree
A particular enumeration for a particulare object is not available
When a particular table or object does not exist in the MIB tree, attempted access to it by a management entity will
result in a failure code of noSuchName.
The list of MIBs that have objects supported by the BitStorm 2600 and GranDSLAM 4200 IP DSLAM can be found
in the Table of Contents section of this document.
The goal of this document is to provide all the information required to develop, test, document, and support the
SNMP operation of the BitStorm 2600 and GranDSLAM 4200 IP DSLAM.
MIB objects that have values that are not fully supported are identified by the left justified heading as “Valid Object
Value(s).” Following this heading is a list of values supported. The absence of this heading implies that all possible
values for a MIB object are supported.
1.1
Internet Society Copyright Statement
Parts of RFCs have been directly copied into this document. In the words of the RFC Editor (a group funded by the
Internet Society), “To protect the integrity of RFC publication, all RFCs are published with an ISOC (Internet
Society) copyright statement… This copyright notice was designed to ensure that Request For Comments (RFC)
documents will have the widest possible distribution.” The copyright notice that follows should be taken to apply to
all RFCs and excerpts thereof in this document. For actual copyright date, see the individual RFCs.
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that
comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and
this paragraph are included on all such copies and derivative works. However, this document itself may not
be modified in any way, such as by removing the copyright notice or references to the Internet Society or
other Internet organizations, except as needed for the purpose of developing Internet standards in which case
1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
the procedures for copyrights defined in the Internet Standards process must be followed, or as required to
translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its
successors or assigns.
This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET
SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2.
Traps
This section describes the standards compliance and any special operational features/options for the SNMP Trap
support. Trap Support List, Table 1 on page 3, identifies all traps supported by the BitStorm 2600 and GranDSLAM
4200 IP DSLAM.
All Traps are sent in SNMPv1 PDU formats.
The SNMP agent rate-limits the transmission of traps to a Trap Manager. The object,
devSecuritySNMPTrapRateLimitPeriod, Section 5.56.4.12, Page 743, configures the rate-limiting period for traps.
2
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 1: Trap Support List (1 of 6)
Trap
Description
VarBind(s)a
MIB
Cross Reference
authenticationFailure
A SNMP message was
received that was not
properly authenticated.
devAuthenticationFailureIpAddress
SNMPv2-MIB
Section 5.2.4.3,
Page 30
warmStart
Power-on reset (software
reset)
SNMPv2-MIB
Section 5.2.4.2,
Page 30
linkDown
The link is down
ifIndex
ifAdminStatus
ifOperStatus
IF-MIB
Section 5.3.5.1,
Page 76
linkUp
The link is up
ifIndex
ifAdminStatus
ifOperStatus
IF-MIB
Section 5.3.5.2,
Page 76
adslAtucPerfLofsThreshTrap
Loss of Framing 15minute interval threshold
reached.
adslAtucPerfCurr15MinLofs
adslAtucThresh15MinLofs
ADSL-LINE-MIB
Section 5.11.3.1.1,
Page 228
adslAtucPerfLossThreshTrap
Loss of Signal 15-minute
interval threshold
reached.
adslAtucPerfCurr15MinLoss
adslAtucThresh15MinLoss
ADSL-LINE-MIB
Section 5.11.3.1.2,
Page 228
adslAtucPerfESsThreshTrap
Errored Second 15minute interval threshold
reached.
adslAtucPerfCurr15MinESs
adslAtucThresh15MinESs
ADSL-LINE-MIB
Section 5.11.3.1.4,
Page 228
adslAtucRateChangeTrap
The ATUCs transmit rate
has changed.
adslAtucChanCurrTxRate
adslAtucChanPrevTxRate
ADSL-LINE-MIB
Section 5.11.3.1.5,
Page 229
adslAtucPerfLolsThreshTrap
Loss of Link 15-minute
interval threshold
reached.
adslAtucPerfCurr15MinLols
adslAtucThresh15MinLols
ADSL-LINE-MIB
Section 5.11.3.1.6,
Page 229
adslAtucInitFailureTrap
ATUC initialization
failed.
adslAtucCurrStatus
ADSL-LINE-MIB
Section 5.11.3.1.7,
Page 229
adslAturPerfLofsThreshTrap
Loss of Framing 15minute interval threshold
reached.
adslAturPerfCurr15MinLofs
adslAturThresh15MinLofs
ADSL-LINE-MIB
Section 5.11.3.2.1,
Page 229
adslAturPerfLossThreshTrap
Loss of Signal 15-minute
interval threshold
reached.
adslAturPerfCurr15MinLoss
adslAturThresh15MinLoss
ADSL-LINE-MIB
Section 5.11.3.2.2,
Page 229
adslAturPerfLprsThreshTrap
Loss of Power 15-minute
interval threshold
reached.
adslAturPerfCurr15MinLprs
adslAturThresh15MinLprs
ADSL-LINE-MIB
Section 5.11.3.2.3,
Page 229
adslAturPerfESsThreshTrap
Errored Second 15minute interval threshold
reached.
adslAturPerfCurr15MinESs
adslAturThresh15MinESs
ADSL-LINE-MIB
Section 5.11.3.2.4,
Page 229
3
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 1: Trap Support List (2 of 6)
Trap
Description
VarBind(s)a
MIB
Cross Reference
adslAturRateChangeTrap
The ATUCs transmit rate
has changed.
adslAturChanCurrTxRate
adslAturChanPrevTxRate
ADSL-LINE-MIB
Section 5.11.3.2.5,
Page 229
adslAtucSesLThreshTrap
Severely errored seconds-line 15-minute
threshold reached.
adslAtucPerfCurr15MinSesL
adslAtucThresh15MinSesL
ADSL-LINE-EXT-MIB
Section 5.12.5.1.2,
Page 242
adslAtucUasLThreshTrap
Unavailable seconds-line
15-minute threshold
reached.
adslAtucPerfCurr15MinUasL
adslAtucThresh15MinUasL
ADSL-LINE-EXT-MIB
Section 5.12.5.1.3,
Page 242
adslAturSesLThreshTrap
Severely errored seconds-line 15-minute
threshold reached.
adslAturPerfCurr15MinSesL
adslAturThresh15MinSesL
ADSL-LINE-EXT-MIB
Section 5.12.5.2.1,
Page 243
adslAturUasLThreshTrap
Unavailable seconds-line
15-minute threshold
reached.
adslAturPerfCurr15MinUasL
adslAturThresh15MinUasL
ADSL-LINE-EXT-MIB
Section 5.12.5.2.2,
Page 243
devSecurityWebAuthenFailure
An IP address for a Web
client is not in the
“access control list.”
devSecurityFailedIpAddress
PDN-SECURITY-MIB
Section 5.56.6.1,
Page 748
devSecurityTelnetAuthenFailure
An IP address for a Telnet client is not in the
“access control list.”
devSecurityFailedIpAddress
PDN-SECURITY-MIB
Section 5.56.6.2,
Page 748
dsx1LineStatusChange
The value of a
dsx1LineStatus instance
changed.
dsx1LineStatus
dxx1LineStatusLastChange
DS1-MIB
Section 5.14.5.1,
Page 305
hdsl2ShdslLoopAttenCrossing
Loop attenuation threshold has been reached or
exceeded.
HDSL2-SHDSL-LINEMIB
Section 5.13.7.1,
Page 274
hdsl2ShdslSNRMarginCrossing
SNR margin threshold
has been reached or
exceeded.
HDSL2-SHDSL-LINEMIB
Section 5.13.7.2,
Page 274
hdsl2ShdslPerfESThresh
Errored seconds threshold has been reached or
exceeded.
HDSL2-SHDSL-LINEMIB
Section 5.13.7.3,
Page 274
hdsl2ShdslPerfSESThresh
Severely errored seconds
threshold has been
reached or exceeded.
HDSL2-SHDSL-LINEMIB
Section 5.13.7.4,
Page 274
hdsl2ShdslEndpointCurrAtn
hdsl2ShdslEndpointThreshLoopAttenuation
hdsl2ShdslEndpointCurrSnrMgn
hdsl2ShdslEndpointThreshSNRMargin
hdsl2ShdslEndpointCurr15MinES
hdsl2ShdslEndpointThreshES
hdsl2ShdslEndpointCurr15MinSES
hdsl2ShdslEndpointThreshSES
4
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 1: Trap Support List (3 of 6)
Trap
Description
hdsl2ShdslPerfCRCanomaliesThresh
CRC anomalies threshold
has been reached or
exceeded.
hdsl2ShdslPerfLOSWSThresh
SOSW seconds threshold has been reached or
exceeded.
hdsl2ShdslPerfUASThresh
Unavailable seconds
threshold has been
reached or exceeded.
hdsl2ShdslSpanInvalidNumRepeaers
A mismatch has been
detected between the
number of repeater/
regenerator units configured for the line and the
actual number of units
discovered via the EOC.
hdsl2ShdslLoopbackFailure
An endpoint maintenance
loopback command
failed for the segment.
hdsl2ShdslpowerBackoff
VarBind(s)a
MIB
Cross Reference
HDSL2-SHDSL-LINEMIB
Section 5.13.7.5,
Page 274
HDSL2-SHDSL-LINEMIB
Section 5.13.7.6,
Page 274
HDSL2-SHDSL-LINEMIB
Section 5.13.7.7,
Page 274
HDSL2-SHDSL-LINEMIB
Section 5.13.7.8,
Page 274
hdsl2ShdslMaintLoopbackConfig
HDSL2-SHDSL-LINEMIB
Section 5.13.7.9,
Page 274
The bit setting in the status for powerBackoff for
the endpoint has been
changed.
hdsl2ShdslEndpointCurrStatus
HDSL2-SHDSL-LINEMIB
Section 5.13.7.10,
Page 274
hdsl2ShdsldeviceFault
The bit setting in the status for deviceFault for the
endpoint has changed.
hdsl2ShdslEndpointCurrStatus
HDSL2-SHDSL-LINEMIB
Section 5.13.7.11,
Page 275
hdsl2ShdsldcContinuityFault
The bit setting in the status for dcContinuityFault for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
HDSL2-SHDSL-LINEMIB
Section 5.13.7.12,
Page 275
hdsl2ShdslconfigInitFailure
The bit setting in the status for configInitFailure
for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
HDSL2-SHDSL-LINEMIB
Section 5.13.7.13,
Page 275
hdsl2ShdslprotocolInitFailure
The bit setting in the status for protocolInitFailure for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
HDSL2-SHDSL-LINEMIB
Section 5.13.7.14,
Page 275
hdsl2ShdslEndpointCurr15MinCRCanomalies
hdsl2ShdslEndpointThreshCRCanomalies
hdsl2ShdslEndpointCurr15MinLOSWS
hdsl2ShdslEndpointThreshLOSWS
hdsl2ShdslEndpointCurr15MinUAS
hdsl2ShdslEndpointThreshUAS
hdsl2ShdslSpanConfNumRepeaters
hdsl2ShdslStatusNumAvailRepeaters
5
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 1: Trap Support List (4 of 6)
Trap
Description
VarBind(s)a
MIB
Cross Reference
hdsl2ShdslnoNeighborPresent
The bit setting in the status for noNeighborPresent for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
HDSL2-SHDSL-LINEMIB
Section 5.13.7.15,
Page 275
hdsl2ShdslLocalPowerLoss
Indicates an impending
unit failure due to loss of
local power.
hdsl2ShdslInvVendorID
HDSL2-SHDSL-LINEMIB
Section 5.13.7.16,
Page 275
pdnDevFileXferEvent
A File Transfer Event,
firmware or configuration
occurred
•
•
•
•
•
•
PDN-CONTROL-MIB
Section 5.35.5.5,
Page 575
mpeCcn
Configuration change
(rate limited)
entPhysicalIndex
PDN-MPE-DSLAMSYSTEM-MIB
Section 5.24.5.1,
Page 442
mpeSelfTestFailure
Sent if any portion of a
restart/self start fails
mpeDevSelfTestResults
PDN-MPE-HEALTHAND-STATUS-MIB
Section 5.25.5.1,
Page 445
mpeAlarmRelayInputStateChanged
The contacts on the
Alarm Relay input have
change from open to
closed or from closed to
open.
mpeAlarmRelayInputState
PDN-MPE-DSLAMSYSTEM-MIB
Section 5.24.5.10,
Page 443
pdnEntPhySensor
ExtThresholdExceededSet
A sensor that was previously operating within a
defined threshold is now
operating in excess of the
threshold limits.
PDN-ENTITYSENSOR-EXT-MIB
Section 5.42.5.1,
Page 644
The downstream transmit rate has changed.
• pdnDslAtmBondGroupIfIndex
• pdnDslAtmBondPerfCurrAtucNetDataRate
• pdnDslAtmBondPerfPrevAtucNetDataRate
PDN-DSL-ATM-BONDMIB
Section 5.41.7.1,
Page 635
The upstream transmit
rate has changed.
• pdnDslAtmBondGroupIfIndex
• pdnDslAtmBondPerfCurrAturNetDataRate
• pdnDslAtmBondPerfPrevAturNetDataRate
PDN-DSL-ATM-BONDMIB
Section 5.41.7.2,
Page 635
The operational status of
the group has changed.
• pdnDslAtmBondGroupIfIndex
• pdnDslAtmBondPerfGroupStatus
• pdnDslAtmBondPerfFailReason
PDN-DSL-ATM-BONDMIB
Section 5.41.7.3,
Page 635
pdnDslAtmBondAtucRateChange
pdnDslAtmBondAturRateChange
pdnDslAtmBondGroupStatusChange
pdnDevFileXferStatus
pdnDevFileXferErrorStatus
pdnDevFileXferOperation
pdnDevFileXferFileType
pdnDevFileXferFileName
pdnDevFileXferErrorStatusText
• pdnPhySensorValue
• pdnEntPhySensorExtThresholdState
6
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 1: Trap Support List (5 of 6)
Trap
Description
VarBind(s)a
pdnEntPhySensorExtThresholdExceededCleared
A sensor that was previously operating in excess
of a defined threshold is
now operating within the
threshold limits.
• pdnPhySensorValue
• pdnEntPhySensorExtThresholdState
pdnHdsl2ShdslLoopAttenCrossing
Loop attenuation threshold has been reached or
exceeded.
pdnHdsl2ShdslSNRMarginCrossing
MIB
Cross Reference
PDN-ENTITYSENSOR-EXT-MIB
Section 5.42.5.2,
Page 644
• hdsl2ShdslEndpointCurrAtn
• hdsl2ShdslEndpointThreshLoopAttenuation
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.1,
Page 766
SNR margin threshold
has been reached or
exceeded.
• hdsl2ShdslEndpointCurrSnrMgn
• hdsl2ShdslEndpointThreshSNRMargin
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.2,
Page 767
pdnHdsl2ShdslPerfESThresh
Errored seconds threshold has been reached or
exceeded.
• hdsl2ShdslEndpointCurr15MinES
• hdsl2ShdslEndpointThreshES
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.3,
Page 767
pdnHdsl2ShdslPerfSESThresh
Severely errored seconds
threshold has been
reached or exceeded.
• hdsl2ShdslEndpointCurr15MinSES
• hdsl2ShdslEndpointThreshSES
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.4,
Page 767
pdnHdsl2ShdslPerfCRCanomaliesThresh
CRC anomalies threshold
has been reached or
exceeded.
• hdsl2ShdslEndpointCurr15MinCRCanomalies
• hdsl2ShdslEndpointThreshCRCanomalies
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.5,
Page 767
pdnHdsl2ShdslPerfLOSWSThresh
SOSW seconds threshold has been reached or
exceeded.
• hdsl2ShdslEndpointCurr15MinLOSWS
• hdsl2ShdslEndpointThreshLOSWS
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.6,
Page 767
pdnHdsl2ShdslPerfUASThresh
Unavailable seconds
threshold has been
reached or exceeded.
• hdsl2ShdslEndpointCurr15MinUAS
• hdsl2ShdslEndpointThreshUAS
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.7,
Page 767
pdnHdsl2ShdslpowerBackoff
The bit setting in the status for powerBackoff for
the endpoint has been
changed.
hdsl2ShdslEndpointCurrStatus
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.8,
Page 767
pdnHdsl2ShdsldeviceFault
The bit setting in the status for deviceFault for the
endpoint has changed.
hdsl2ShdslEndpointCurrStatus
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.9,
Page 767
pdnHdsl2ShdsldcContinuityFault
The bit setting in the status for dcContinuityFault for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.10,
Page 767
7
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 1: Trap Support List (6 of 6)
Trap
Description
VarBind(s)a
MIB
Cross Reference
pdnHdsl2ShdslconfigInitFailure
The bit setting in the status for configInitFailure
for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.11,
Page 767
pdnHdsl2ShdslprotocolInitFailure
The bit setting in the status for protocolInitFailure for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.12,
Page 767
pdnHdsl2ShdslnoNeighborPresent
The bit setting in the status for noNeighborPresent for the endpoint has
changed.
hdsl2ShdslEndpointCurrStatus
PDN-HDSL2-SHDSLLINE-MIB
Section 5.57.5.13,
Page 768
a. The snmpTrapOID and snmpTrapEnterprise objects apply only to SNMPv2-Trap-PDUs and InformRequest-PDUs and will not be
supported in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM as it those PDU types are not used to generate trap/notifications.
3.
Ordered MIB List
This section contains an ordered list the MIBs and their dependencies supported in the BitStorm 2600 and
GranDSLAM 4200 IP DSLAM. In other words, MIBs that are dependent on other MIBs are listed after the MIBs
they are dependent on. The objective here is to list MIBs in the order in which they should be loaded in an NMS
application. This list is “worst case” in that it contains all possible MIBs that might be required, although not all of
them may be required. A lot of what is required is dependent on the needs of a particular NMS application. This list
was constructed by examining the “IMPORTS” clause in the MIB and making sure those items MIBs identified were
listed before the particular MIB that was importing them. MIBs in bold font are the MIBs containing objects
implemented in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. Those that are not in bold font are
dependencies.
Table 2: Ordered MIB List (1 of 4)
MIB
RFC/File
SNMPv2-SMI
RFC 2578
SNMPv2-CONF
RFC 2580
SNMPv2-TC
RFC 2579
SNMPv2- MIB
RFC 1907
RFC1213-MIB
RFC 1213
IANAifType-MIB
http://www.iana.org/assignments/ianaiftype.mib
PDN-HEADER-MIB
pdn_Header.mib
8
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
Overview
Table 2: Ordered MIB List (2 of 4)
MIB
RFC/File
PDN-TC
pdn_tc.mib
SNMP-FRAMEWORK-MIB
RFC 2571
IP-MIB
RFC 2011
ENTITY-MIB
RFC 2737
ENTITY-SENSOR-MIB
RFC 3433
IF-MIB
RFC 2863
IP-FORWARD-MIB
RFC 2096
ATM-TC-MIB
RFC 2514
ATM-MIB
RFC 2515
HOST-RESOURCES-MIB
RFC 2790
ATM-FORUM-SNMP-M4-MIB
af-nm-0095.001.mib
RS-232-MIB
RFC 1659
EtherLike-MIB
RFC 2665
MAU-MIB
RFC 2668
PerfHist-TC-MIB
RFC 3593
ADSL-TC-MIB,
ADSL-LINE-MIB
RFC 2662
ADSL-LINE-EXT-MIB
RFC 3440
BRIDGE-MIB
RFC 1493
RFC1158-MIB
RFC 1158
RFC1271-MIB
RFC 1271
RMON-MIB
RFC 2819
TOKEN-RING-RMON-MIBa
RFC 1513
RMON2-MIB
RFC 2021
P-BRIDGE-MIB
Q-BRIDGE-MIB
RFC 2674
INET-ADDRESS-MIB
RFC 2851
IGMP-STD-MIB
RFC 2933
HDSL2-SHDSL-LINE-MIB
RFC 3276
9
SNMP Reference
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
Overview
Table 2: Ordered MIB List (3 of 4)
MIB
RFC/File
DS1-MIB
RFC 2495
PPP-LCP-MIB
RFC 1471
PPP-BRIDGE-NCP-MIB
RFC 1474
PDN-HEADER-MIB
pdn_Header.mib
PDN-TC
pdn_tc.mib
PDN-MPE-DEVICE-CONTROL-MIB
mpe_Control.mib
PDN-MPE-HEALTH-AND-STATUS-MIB
mpe_HealthAndStatus.mib
PDN-MPE-MIB2-MIB
mpe_mib2.mib
PDN-MPE-DSLAM-SYSTEM-MIB
mpe_dslam.mib
PDN-ARP-MIB
pdn_Arp.mib
PDN-ATMSTATS-MIB
pdn_AtmStats.mib
PDN-CONFIG-MIB
pdn_Config.mib
PDN-CONTROL-MIB
pdn_Control.mib
PDN-IFEXT-MIB
pdn_IfExt.mib
PDN-IF-EXT-CONFIG-MIB
pdn_IfExtConfig.mib
PDN-SECURITY-MIB
pdn_Security.mib
PDN-DIAGNOSTICS-MIB
pdn_diag.mib
PDN-DSLAM-SYSTEM-MIB
pdn_dslam.mib
PDN-ETHER-MIB
pdn_ether.mib
PDN-FILTER-MIB
pdn_filter.mib
PDN-INET-MIB
pdn_inet.mib
PDN-SYSLOG-MIB
pdn_syslog.mib
PDN-UPLINK-TAGGING-MIB
PDN-UPLINK-TAGGING-MIB.mib
PDN-STACKABLE-MIB
PDN-STACKABLE-MIB.mib
PDN-DEVICE-TIME-MIB
pdn_time.mib
PDN-ATM-BRIDGE-IWF-MIB
PDN-ATM-BRIDGE-IWF-MIB.mib
PDN-REACHDSL-MIB
pdn_reachDSL.mib
PDN-SPECTRUMMGMT-MIB
pdn_spectrummgmt.mib
10
SNMP Reference
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
Table 2: Ordered MIB List (4 of 4)
MIB
RFC/File
PDN-ATMEXT-MIB
pdn_AtmExt.mib
PDN-ATMM4EXT-MIB
pdn_AtmM4Ext.mib
PDN-ENTITY-SENSOR-EXT-MIB
PDN-ENTITY-SENSOR-EXT-MIB.mib
PDN-VLAN-MIB
PDN-VLAN-MIB.mib
PDN-IGMP-STD-EXT-MIB
PDN-IGMP-STD-EXT-MIB.mib
PDN-IP-MULTICAST-MIB
PDN-IP-MULTICAST-MIB.mib
PDN-HDSL2-SHDSL-LINE-MIB
PDN-HDSL2-SHDSL-LINE-MIB.mib
PDN-ADSL-LINE-EXT-MIB
PDN-ADSL-LINE-EXT-MIB.mib
PDN-ADSL-SELT-MIB
PDN-ADSL-SELT-MIB.mib
PDN-DOT1QEXT-MIB
PDN-DOT1QEXT-MIB.mib
PDN-DS1CONFIG-MIB
pdn_Ds1Config.mib
PDN-DS1EXT-MIB
PDN-DS1EXT-MIB.mib
PDN-DHCP-MIB
PDN-DHCP-MIB.mib
PDN-HDLC-MIB
PDN-HDLC-MIB.mib
PDN-IFDEV-IWF-MIB
PDN-IFDEV-IWF-MIB.mib
PDN-PPP-LCP-EXT-MIB
PDN-PPP-LCP-EXT-MIB.mib
PDN-PPP-BRIDGE-NCP-EXT-MIB
PDN-PPP-BRIDGE-NCP-EXT-MIB.mib
PDN-PPP-ML-MIB
PDN-PPP-ML-MIB.mib
PDN-BRIDGE-EXT-MIB
PDN-BRIDGE-EXT-MIB.mib
PDN-HEALTHANDSTATUS-MIB
pdn_HealthAndStatus.mibb
PDN-DSL-ATM-BOND-MIB
PDN-DSL-ATM-BOND-MIB.mib
a. Modified the TOKEN-RING-RMON-MIB, RFC 1513, to import the RMON-MIB instead of RFC1271-MIB as there
were serious issues that would have to be worked out to get the RFC1271-MIB to compile.
b. The PDN-HEALTHANDSTATUS-MIB exists only to support the devAuthenticationFailureIpAddress
variable bind for the authenticationFailure trap/notification.
4.
Miscellaneous Textual Conventions
This sections contains Textual Conventions reference by MIBs contained in this SNMP Operational Specification,
but not defined in MIBs contained in this specification.
11
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
4.1
BITS
SMIv2 — RFC 2578
The BITS construct represents an enumeration of named bits. This collection is assigned non-negative, contiguous
(but see below) values, starting at zero. Only those named-bits so enumerated may be present in a value.
As part of updating an information module, for an object defined using the BITS construct, new enumerations can be
added or existing enumerations can have new labels assigned to them. After an enumeration is added, it might not be
possible to distinguish between an implementation of the updated object for which the new enumeration is not
asserted, and an implementation of the object prior to the addition. Depending on the circumstances, such an
ambiguity could either be desirable or could be undesirable. The means to avoid such an ambiguity is dependent on
the encoding of values on the wire; however, one possibility is to define new enumerations starting at the next
multiple of eight bits. (Of course, this can also result in the enumerations no longer being contiguous.)
Although there is no SMI-specified limitation on the number of enumerations (and therefore on the length of a value),
except as may be imposed by the limit on the length of an OCTET STRING, MIB designers should realize that there
may be implementation and interoperability limitations for sizes in excess of 128 bits.
Finally, a label for a named-number enumeration must consist of one or more letters or digits, up to a maximum of 64
characters, and the initial character must be a lower-case letter. (However, labels longer than 32 characters are not
recommended.) Note that hyphens are not allowed by this specification.
n bits are encoded
from 0…n-1 in an
OCTET STRING
0
1
2
8
9
10 11 12 13 14 15
n-3 n-2 n-1
3
4
5
6
7
First Octet
Second Octet
Last Octet
Figure 1. Encoding of BITS TC
4.2
ContactState
PDN-TC
This convention can be used to indicate the state of a switch, door, connector, etc. that can be by nature opened or
closed.
Syntax
•
•
INTEGER
open(1)
close(2)
12
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
4.3
DateAndTime
SNMPv2-TC — RFC 2579
A date-time specification.
Table 3: DateAndTime TC
Field
Octets
Contents
Range
1
1-2
yeara
0…65536
2
3
month
1…12
3
4
day
1…31
4
5
hour
0…23
5
6
minutes
0…590
6
7
seconds
0…60
7
8
deci-seconds
0…9
8
9
direction from UTC
“+” / “-”
9
10
hours from UTCb
0…13
10
11
minutes from UTC
0…59
a. The value of year is in network-byte order.
b. Daylight saving time in New Zealand is +13.
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0.
Note that if only local time is known, then time zone information (fields 8-10) is not present.
Syntax
OCTET STRING (SIZE (8 | 11))
Display Hint
The format of the display for this TC should be 2d-1d-1d,1d:1d:1d.1d,1a1d:1d, where “d” signifies a
decimal, base 10, value.
4.4
IpAddress
SNMPv2-SMI — RFC 2578
Syntax
IMPLICIT OCTET STRING (SIZE (4))
13
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
4.5
MacAddress
SNMPv2-TC — RFC 2579
Represents an 802 MAC address represented in the “canonical” order defined by IEEE 802.1a, i.e., as if it were
transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses
to be transmitted most significant bit first.
Syntax
OCTET STRING (SIZE (6))
Display Hint
1x:, where “x” signifies a hexadecimal value.
4.6
PerfCurrentCount
PerfHist-TC-MIB — RFC 3593
A counter associated with a performance measurement in a current 15 minute measurement interval. The value of this
counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that
time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero.
In the case where the agent has no valid data available for the current interval the corresponding object instance is not
available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance
does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation).
Syntax
4.7
Gauge32
PerfIntervalCount
PerfHist-TC-MIB — RFC 3593
A counter associated with a performance measurement in a previous 15 minute measurement interval. In the case
where the agent has no valid data available for a particular interval the corresponding object instance is not available
and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not
exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a
system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent
intervals respectively, the following applies at the end of a 15 minute interval:
•
•
•
•
discard the value of IntervalCount(n)
the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1
the value of IntervalCount(1) becomes that of CurrentCount
the TotalCount, if supported, is adjusted.
Syntax
4.8
Gauge32
PdnPPPState
PDN-TC — pdn_tc.mib
The state of the PPP Entity State Machine. Examples of PPP entities are Link Control Protocol (LCP), Network
Control Protocol (NCP), and Multilink PPP (ML PPP).
Reference: [RFC 1661] Simpson, W., The Point-to-Point Protocol, Section 4.2, “State Transition Table,” July 1994.
Syntax
INTEGER
14
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
•
initial(1)
•
starting(2)
•
closed(3)
•
stopped(4)
•
closing(5)
•
stopping(6)
•
reqSent(7)
•
ackRcvd(8)
•
ackSent(9)
•
opened(10)
4.9
PdnTestAndIncrDerivedIndexTC
PDN-TC — pdn_tc.mib
An index for a table entry, where a “get next index” object whose syntax is a TestAndIncr textual convention (Section
4.14, Page 17) is used to determine the value for the next unused index for a table entry. This syntax was chosen to
correspond to the TestAndIncr textual convention.
Syntax
Integer32(0…2147483647)
Display Hint
The format of the display of this TC should be d, where “d” signifies a decimal, base 10, value.
4.10 PhysAddress
SNMPv2-TC — RFC 2579
Represents media or physical-level addresses.
Syntax
OCTET STRING
Display Hint
1x:, where “x” signifies a hexadecimal value.
4.11
RowStatus
SNMPv2-TC — RFC 2579
The RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the
value of the Syntax clause for the status column of a conceptual row.
Syntax
•
INTEGER
active(1)
- Indicates that the conceptual row is available for use by the managed
device.This is a desired state that can be written and read.
15
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
•
notInService(2)
- Indicates that the conceptual row exists in the agent, but is unavailable for
use by the managed device. This is a desired state that can be written and
read.
•
notReady(3)
- Indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device
(i.e., one or more required columns in the conceptual row have not been
instantiated). This is a current state and can only be read.
•
createAndGo(4)
- Supplied by a management station wishing to create a new instance of a
conceptual row and to have its status automatically set to active, making it
available for use by the managed device. This is an action state that can be
written but not read.
•
createAndWait(5)
- Supplied by a management station wishing to create a new instance of a
conceptual row (but not make it available for use by the managed device).
This is an action state that can be written but not read. This state is generally not supported for creating rows into tables. The createAndGo(4) state
should be used to create rows in table.
•
destroy(6)
- Supplied by a management station wishing to delete all of the instances
associated with an existing conceptual row.
4.12 SwitchState
PDN-TC — pdn_tc.mib
This object indicates whether an object state is enabled or disabled.
Syntax
INTEGER
•
enabled(1)
•
disabled(2)
4.13 TblCmd
PDN-TC — pdn_tc.mib
STATUS current
DESCRIPTION
This convention can be used to command a database (e.g, mib table) to perform an action (e.g, clear).
Syntax
INTEGER
•
noCmd (1)
•
clear (2)
16
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
4.14 TestAndIncr
SNMPv2-TC — RFC 2579
Represents integer-valued information used for atomic operations. When the management protocol is used to specify
that an object instance having this syntax is to be modified, the new value supplied via the management protocol must
precisely match the value presently held by the instance. If not, the management protocol set operation fails with an
error of “inconsistentValue.” Otherwise, if the current value is the maximum value of 231-1 (2147483647 decimal),
then the value held by the instance is wrapped to zero; otherwise, the value held by the instance is incremented by
one. (Note that regardless of whether the management protocol set operation succeeds, the variable binding in the
request and response PDUs are identical.)
The value of the ACCESS clause for objects having this syntax is either “read-write”: or “read-create.” When an
instance of a columnar object having this syntax is created, any value may be supplied via the management protocol.
When the network management portion of the system is reinitialized, the value of every object instance having this
syntax must either be incremented from its value prior to the re-initialization, or (if the value prior to the reinitialization is unknown) be set to a pseudo-randomly generated value.
Syntax
4.14.1
INTEGER (0…2147483647)
TimeFilter
RMON2-MIB — RFC 2021
To be used for the index to a table. Allows an application to download only those rows changed since a particular
time. A row is considered changed if the value of any object in the row changes or if the row is created or deleted.
When sysUpTime is equal to zero, this table shall be empty.
One entry exists for each past value of sysUpTime, except that the whole table is purged should sysUpTime wrap.
As this basic row is updated new conceptual rows are created (which still share the now updated object values with all
other instances). The number of instances which are created is determined by the value of sysUpTime at which the
basic row was last updated. One instance will exist for each value of sysUpTime at the last update time for the row. A
new timeMark instance is created for each new sysUpTime value. Each new conceptual row will be associated with
the timeMark instance which was created at the value of sysUpTime with which the conceptual row is to be
associated.
By definition all conceptual rows were updated at or after time zero and so at least one conceptual row (associated
with timeMark.0) must exist for each underlying (basic) row.
Consider the following fooTable:
fooTable …
INDEX { fooTimeMark, fooIndex }
FooEntry {
fooTimeMarkTimeFilter
fooIndexINTEGER,
fooCountsCounter
}
Should there be two basic rows in this table (fooIndex == 1, fooIndex == 2) and row 1 was updated most recently at
17
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
time 6, while row 2 was updated most recently at time 8, and both rows had been updated on several earlier occasions
such that the current values were 5 and 9 respectively then the following fooCounts instances would exist.
fooCounts.0.1
5
fooCounts.0.2
9
fooCounts.1.1
5
fooCounts.1.2
9
fooCounts.2.1
5
fooCounts.2.2
9
fooCounts.3.1
5
fooCounts.3.2
9
fooCounts.4.1
5
fooCounts.4.2
9
fooCounts.5.1
5
fooCounts.5.2
9
fooCounts.6.1
5
fooCounts.6.2
9
fooCounts.7.2
9
-- note that row 1 does not exist for
fooCounts.8.2
9
-- times 7 and 8
Syntax
TimeTicks
4.15 TimeInterval
A period of time, measured in units of 0.01 seconds.
Syntax
INTEGER (0…2147483647)
4.16 TimeStamp
SNMPv2-TC — RFC 2579
The value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined
in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a reinitialization of the network management (sub)system, then the values
of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the
sysUpTime object will reach 232-1 and then increment around to zero; in this case, existing values of TimeStamp
objects do not change. This can lead to ambiguities in the value of TimeStamp objects.
Syntax
TimeTicks
4.17 TimeTicks
SMIv2 — RFC 2578
18
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Overview
The TimeTicks type represents a non-negative integer which represents the time, modulo 232 (4294967296 decimal),
in hundredths of a second between two epochs. When objects are defined which use this ASN.1 type, the description
of the object identifies both of the reference epochs.
Syntax
IMPLICIT INTEGER (0…4294967295)
4.18 TruthValue
SNMPv1-TC — RFC 2579
Represents a boolean value.
Syntax
•
•
INTEGER
true(1)
false(2)
4.19 VnidRange
PDN-TC — pdn_tc.mib
The valid range for VNID IDs.
Syntax
5.
INTEGER (2…4000)
Management Information Base (MIBs)
This section describes the SNMP MIB support implemented in the BitStorm 2600 and GranDSLAM 4200 IP
DSLAM project. MIBs supported consist of both “standard” MIBs and Paradyne Enterprise MIBs.
Unlike the “standard” MIBs, the Paradyne Enterprise MIBs change frequently. As a result, the objects listed for these
MIBs in this document may be a subset of the latest version of the particular enterprise MIB. Objects that exist in the
later versions but not in this document are not supported.
19
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RFC1213-MIB — RFC 1213
5.1
RFC1213-MIB — RFC 1213
5.1.1
Introduction
This MIB defines objects for managing devices in TCP/IP based internets. The RFC used as a reference was dated
March 1991.
5.1.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
system
interfaces
at
ip
icmp
tcp
udp
egp
cmot
transmission
snmp
5.1.3
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 1 }
{ mib-2 2 }
{ mib-2 3 }
{ mib-2 4 }
{ mib-2 5 }
{ mib-2 6 }
{ mib-2 7 }
{ mib-2 8 }
{ mib-2 9 }
{ mib-2 10 }
{ mib-2 11 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.1
1.3.6.1.2.1.2
1.3.6.1.2.1.3
1.3.6.1.2.1.4
1.3.6.1.2.1.5
1.3.6.1.2.1.6
1.3.6.1.2.1.7
1.3.6.1.2.1.8
1.3.6.1.2.1.9
1.3.6.1.2.1.10
1.3.6.1.2.1.11
The following groups supported in this MIB are as follow:
Table 4: RFC1213-MIB Objects (1 of 2)
Group
Supported
systema
Y
interfacesb
Y
at
N
ipc
Y
icmpc
N
tcpd
N
udpe
N
egp
N
cmot
N
20
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RFC1213-MIB — RFC 1213
Table 4: RFC1213-MIB Objects (2 of 2)
Group
Supported
transmission
Y
snmpf
Y
a.
b.
c.
d.
e.
f.
Per RFC 1907
Per RFC 2863
Per RFC 2011
Per RFC 2012
Per RFC 2013
Per RFC 1907
5.1.3.1
System Group
This group has been updated in SNMPv2-MIB — RFC 1907, Section 5.2, Page 22.
5.1.3.2
Interfaces Group
This group has been updated in IF-MIB — RFC 2863, Section 5.3, Page 31.
5.1.3.3
IP Group
This group has been updated in IP-MIB — RFC 2011IP-MIB, Section 5.4, Page 77.
5.1.3.4
TCP Group
Not supported.
5.1.3.5
UDP Group
Not supported.
5.1.3.6
EGP Group
Not supported.
5.1.3.6.1
Transmission Group
The Transmission Group is based on the transmission media underlying each interface on a system. The objects in the
Transmission Group are not defined within MIB-II, but rather through other internet-standard MIB definitions.
Objects that are part of this group can be derived from the OIDs documented in the relevant RFCs. The following
describes the structure to parse for in the relevant RFCs:
type OBJECT IDENTIFIER := { transmission number }
Where:
5.1.3.7
—
type
—
number
- Is the symbolic value used for the media in the ifType column of the ifTable object
See Interfaces Group for ifType values and the ifTable object
- The actual integral value corresponding to the type
SNMP Group
This group had been updated in RFC 1907. Please refer to that section of the document for support.
21
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
5.2
SNMPv2-MIB — RFC 1907
5.2.1
Introduction
This MIB defines managed object which describe the behavior of a SNMPv2 entity. The RFC used as a reference was
dated January 1996. The LAST-UPDATED for the snmp-MIB was “9511090000Z.”
5.2.2
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
system
snmp
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 1 }
{ mib-2 11 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.1
1.3.6.1.2.1.1.11
•
•
•
•
•
•
•
•
•
snmpV2
snmpModules
snmpMIB
snmpMIBObjects
snmpTrap
snmpTrapOID
snmpTrapEnterprise
snmpTraps
snmpSet
-
{ internet 6 }
{ snmpV2 3 }
{ snmpModules 1 }
{ snmpMIB 1 }
{ snmpMIBObjects 4 }
{ snmpTrap 1 }
{ snmpTrap 2 }
{ snmpMIBObjects 5 }
{ snmpMIBObjects 6 }
1.3.6.1.6
1.3.6.1.6.3
1.3.6.1.6.3.1
1.3.6.1.6.3.1.1
1.3.6.1.6.3.1.1.4
1.3.6.1.6.3.1.1.4.1
1.3.6.1.6.3.1.1.4.2
1.3.6.1.6.3.1.1.5
1.3.6.1.6.3.1.1.6
•
•
•
•
•
•
•
•
•
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-common
pdn-devStatus
devStatus
devAuthenticationFailureIpAddress
5.2.3
-
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
{ pdn-common 4 }
{ pdn-devStatus 1 }
{ devStatus 5 }
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
1.3.6.1.4.1.1795.2.24.2.4
1.3.6.1.4.1.1795.2.24.2.4.1
1.3.6.1.4.1.1795.2.24.2.4.1.5
MIB Objects
The table below identifies the objects called out in this MIB. Any table object that has elements that are supported are
indicated by a “Y” in the Supported column.
Table 5: SNMPv2-MIB Objects
Object
OID
Supported
system
{ mib-2 1 }
Y
snmp
{ mib-2 11 }
Y
22
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
5.2.3.1
System Group
A collection of objects common to all managed systems.
OIDs:
•
system - { mib-2 1 } 1.3.6.1.2.1.1
Table 6: System Group
Object
OID
Syntax
Access
Status
Supported
sysDescr
{ system 1 }
DisplayString
read-only
current
Y
sysObjectID
{ system 2 }
OBJECT IDENTIFIER
read-only
current
Y
sysUpTime
{ system 3 }
TimeTicks
read-only
current
Y
sysContact
{ system 4 }
DisplayString(SIZE(0.…32))a
read-write
current
Y
sysName
{ system 5 }
DisplayString(SIZE(0.…32))a
read-write
current
Y
sysLocation
{ system 6 }
DisplayString(SIZE(0.…32))a
read-write
current
Y
sysServices
{ system 7 }
INTEGER(0…127)
read-only
current
Y
sysORLastChange
{ system 8 }
TimeStamp
read-only
current
N
sysORTable
{ system 9 }
Sequence of sysOREntry
not-accessible
current
N
a. Product imposed limit.
5.2.3.1.1
sysDescr
A textual description of the entity. This value should include the full name and version identification of the system's
hardware type, software operating-system, and networking software.
Valid Object Value(s)
This object provides the full name and version identification for the systems hardware and software. This object is set
to display a string with the following format:
“Company Name1 Family2 Model Number3; S/W Release: yy.yy.yy;”
Where:
—
“yy.yy.yy” represents the software revision number
1. Company Name is set to “PARADYNE.”
2. The Family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
3. The Model Number is “2600” for the BitStorm family products and “4200” for the GranDSLAM family
products.
23
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
Note: Information that is unique on a “per slice” basis is reported in the Entity MIB.
5.2.3.1.2
sysObjectID
The vendor's authoritative identification of the network management subsystem contained in the entity. This value is
allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for
determining “what kind of box” is being managed. For example, if vendor “Flintstones, Inc.” was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its “Fred Router.”
Valid Object Value(s)
Below is an OID tree for sysObjectIDs for the BitStorm 2600 and GranDSLAM 4200 IP DSLAM.
•
•
•
•
Company
Company
Company
Company
Enterprise1
Enterprise1
Enterprise1
Enterprise1
.1.14.17
.1.14.17.1
.
1.14.17.1.2
.1.14.17.1.3
- ip-stackable
- ips-stack
ips-2600
ips-4200
Given that the product is part of the ip-stackable family of products, but is managed independently (that is, there is no
single management entity), this object will return:
Company Enterprise OID1.1.14.17.1.2
5.2.3.1.3
sysUpTime
The time (in hundredths of a second) since the network management portion of the system was last re-initialized.
5.2.3.1.4
sysContact
The textual identification of the contact person for this managed node, together with information on how to contact
this person. If no contact information is known, the value is the zero-length string.
5.2.3.1.5
sysName
An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain
name. If the name is unknown, the value is the zero-length string.
Valid Object Value(s)
Spaces are not allowed in the string.
5.2.3.1.6
sysLocation
The physical location of this node (for example, “telephone closet, 3rd floor”). If the location is unknown, the value is
the zero-length string.
5.2.3.1.7
sysServices
A value which indicates the set of services that this entity may potentially offers. The value is a sum. This sum
initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For example, a node which performs only routing functions would have a
value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(41) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly:
1. Company Enterprise OID is set to “1.3.6.1.4.1.1795.”
24
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
For systems including OSI protocols, layers 5 and 6 may also be counted.
Valid Object Value(s)
The table below contains the set of services and their associated values based on the standard 2(L-1) formula. The final
result for this object is 1 + 2 + 4 + 8 + 64 = 79 = 0x4F.
Table 7: sysServices
Layer (L)
Functionality
Value (2(L-1))
Sum
1
Physical
2(1-1) = 20 = 1
1
2
Data Link / Subnetwork
2(2-1) = 21 = 2
3
3
Internet
2(3-1) = 22 = 4
7
4
End-to-End
2(4-1) = 23 = 8
15
7
Application
2(7-1) = 26 = 64
79
5.2.3.1.8
Object Resource Information
A collection of objects which describe the SNMPv2 entity's (statically and dynamically configurable) support of
various MIB modules.
5.2.3.1.8.1
sysORLastChange
The value of sysUpTime at the time of the most recent change in state or value of any instance of sysORID.
5.2.3.1.8.2
sysORTable
The (conceptual) table listing the capabilities of the local SNMPv2 entity acting in an agent role with respect to
various MIB modules. SNMPv2 entities having dynamically-configurable support of MIB modules will have a
dynamically-varying number of conceptual rows.
Index(es):
•
sysORIndex
OIDs:
•
•
sysORTable
sysOREntry
- { system 9 }
- { sysORTable 1 }
1.3.6.1.2.1.1.9
1.3.6.1.2.1.1.9.1
Table 8: sysORTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
sysORIndex
{ sysOREntry 1 }
INTEGER (1…2147483647)
not-accessible
current
N
25
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
Table 8: sysORTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
sysORID
{ sysOREntry 2 }
OBJECT IDENTIFIER
read-only
current
N
sysORDescr
{ sysOREntry 3 }
DisplayString
read-only
current
N
sysORUpTime
{ system 4 }
TimeStamp
read-only
current
N
5.2.3.1.8.2.1
sysORIndex
The auxiliary variable used for identifying instances of the columnar objects in the sysORTable.
5.2.3.1.8.2.2
sysORID
An authoritative identification of a capabilities statement with respect to various MIB modules supported by the local
SNMPv2 entity acting in an agent role.
5.2.3.1.8.2.3
sysORDescr
A textual description of the capabilities identified by the corresponding instance of sysORID.
5.2.3.1.8.2.4
sysORUpTime
The value of sysUpTime at the time this conceptual row was last instantiated.
5.2.3.2
SNMP Group
This group is a collection of objects providing basic instrumentation and control of an SNMP entity.
Some objects with a Status of “obsolete” are supported. This is to comply with a request from Technical Support.
OIDs:
•
snmp
- { mib-2 11 }
1.3.6.1.2.1.1.11
Table 9: SNMP Group (1 of 2)
Object
OID
Syntax
Access
Status
Supported
snmpInPkts
{ snmp 1}
Couner32
read-only
current
Y
snmpOutPkts
{ snmp 2}
Couner32
read-only
obsolete
N
snmpInBadVersions
{ snmp 3}
Couner32
read-only
current
Y
snmpInBadCommunityNames
{ snmp 4}
Couner32
read-only
current
Y
snmpInBadCommunityUses
{ snmp 5 }
Couner32
read-only
current
Y
snmpInASNParseErrs
{ snmp 6 }
Couner32
read-only
current
Y
Counter
read-only
obsolete
N
{ snmp 7 }a
snmpInTooBigs
{ snmp 8 }
26
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
Table 9: SNMP Group (2 of 2)
Object
OID
Syntax
Access
Status
Supported
snmpInNoSuchNames
{ snmp 9 }
Counter
read-only
obsolete
N
snmpInBadValues
{ snmp 10 }
Counter
read-only
obsolete
N
snmpInReadOnlys
{ snmp 11 }
Counter
read-only
obsolete
N
snmpInGenErrs
{ snmp 12 }
Counter
read-only
obsolete
N
snmpInTotalReqVars
{ snmp 13 }
Counter
read-only
obsolete
N
snmpInTotalSetVars
{ snmp 14 }
Counter
read-only
obsolete
N
snmpInGetRequests
{ snmp 15 }
Counter
read-only
obsolete
Y
snmpInGetNexts
{ snmp 16 }
Counter
read-only
obsolete
Y
snmpInSetRequests
{ snmp 17 }
Counter
read-only
obsolete
Y
snmpInGetResponses
{ snmp 18 }
Counter
read-only
obsolete
N
snmpInTraps
{ snmp 19 }
Counter
read-only
obsolete
N
snmpOutTooBigs
{ snmp 20 }
Counter
read-only
obsolete
N
snmpOutNoSuchNames
{ snmp 21 }
Counter
read-only
obsolete
N
snmpOutBadValues
{ snmp 22 }
Counter
read-only
obsolete
N
{ snmp 23 }a
snmpOutGenErrs
{ snmp 24 }
Counter
read-only
obsolete
N
snmpOutGetRequests
{ snmp 25 }
Counter
read-only
obsolete
N
snmpOutGetNexts
{ snmp 26 }
Counter
read-only
obsolete
N
snmpOutSetRequests
{ snmp 27 }
Counter
read-only
obsolete
N
snmpOutGetResponses
{ snmp 28 }
Counter
read-only
obsolete
Y
snmpOutTraps
{ snmp 29 }
Counter
read-only
obsolete
Y
snnpEnableAuthenTraps
{ snmp 30 }
INTEGER
enabled(1)
disabled(2)
read-write
current
Y
snmpSilentDrops
{ snmp 31 }
Couner32
read-only
current
Y
snmpProxyDrops
{ snmp 31 }
Couner32
read-only
current
Y
a.
This OID is not used.
5.2.3.2.1
snmpInPkts
The total number of messages delivered to the SNMP entity from the transport service.
5.2.3.2.2
snmpInBadVersions
The total number of SNMP messages which were delivered to the SNMP entity and were for an unsupported SNMP
27
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
version.
5.2.3.2.3
snmpInBadCommunityNames
The total number of SNMP messages delivered to the SNMP entity which used a SNMP community name not known
to said entity.
5.2.3.2.4
snmpInBadCommunityUses
The total number of SNMP messages delivered to the SNMP entity which represented an SNMP operation which was
not allowed by the SNMP community named in the message.
5.2.3.2.5
snmpInASNParseErrs
The total number of ASN.1 or BER errors encountered by the SNMP entity when decoding received SNMP
messages.
5.2.3.2.6
snmpEnableAuthenTraps
Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object
overrides any configuration information; as such, it provides a means whereby all authenticationFailure traps may be
disabled.
Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant
across re-initializations of the network management system.
This object can take on the following values:
•
•
5.2.3.2.7
enabled(1)
disabled(2)
snmpSilentDrops
The total number of GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and
InformRequest-PDUs delivered to the SNMP entity which were silently dropped because the size of a reply
containing an alternate Response-PDU with an empty variable-bindings field was greater than either a local constraint
or the maximum message size associated with the originator of the request.
5.2.3.2.8
snmpProxyDrops
The total number of GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and
InformRequest-PDUs delivered to the SNMP entity which were silently dropped because the transmission of the
(possibly translated) message to a proxy target failed in a manner (other than a time-out) such that no Response-PDU
could be returned.
5.2.3.3
Set Group
This group is a collection of objects which allow several cooperating SNMPv2 entities, all acting in a manager role,
to coordinate their use of the SNMPv2 set operation.
OIDs:
•
snmpSet
- { snmpMIBObjects 6 }
1.3.6.1.6.3.1.1.6
28
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
Table 10: Set Group
Object
OID
Syntax
Access
Status
Supported
snmpSetSerialNo
{ snmpSet 1}
TestAndIncr
read-write
current
N
5.2.3.3.1
snmpSetSerialNo
An advisory lock used to allow several cooperating SNMPv2 entities, all acting in a manager role, to coordinate their
use of the SNMPv2 set operation.
This object is used for coarse-grain coordination. To achieve fine-grain coordination, one or more similar objects
might be defined within each MIB group, as appropriate.
5.2.4
Traps
This section defines a collection of objects which allow the SNMPv2 entity, when acting in an agent role, to be
configured to generate SNMPv2-Trap-PDUs. Note that the BitStorm 2600 and GranDSLAM 4200 IP DSLAM send
all traps as SNMPv1 PDUs (reference Traps, Section 2, Page 2).
The snmpTrapOID is the authoritative identification of the notification currently being sent. This variable occurs as
the second varbind in every SNMPv2-Trap-PDU and InformRequest-PDU.
The snmpTrapEnterprise is the authoritative identification of the enterprise associated with the trap currently being
sent. When a SNMPv2 proxy agent is mapping an RFC 1157 Trap-PDU into a SNMPv2-Trap-PDU, this variable
occurs as the last varbind.
OIDs:
•
snmpTraps
- { snmpMIBObjects 5 }
1.3.6.1.6.3.1.1.5
Table 11: SNMPv2-MIB Traps
Notification
OID
coldStart
Variable Bindings / Objectsa
Status
Supported
{ snmpTraps 1}
current
N
warmStart
{ snmpTraps 2}
current
Y
authenticationFailure
{ snmpTraps 5}
current
Y
devAuthenticationFailureIpAddress
a. The snmpTrapOID and snmpTrapEnterprise objects apply only to SNMPv2-Trap-PDUs and
InformRequest-PDUs and will not be supported in the BitStorm 2600 and GranDSLAM 4200 IP
DSLAM as it those PDU types are not used to generate trap/notifications.
5.2.4.1
coldStart
A coldStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself and that its
29
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
SNMPv2-MIB — RFC 1907
configuration may have been altered.
5.2.4.2
warmStart
A warmStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself such that its
configuration is unaltered.
5.2.4.3
authenticationFailure
An authenticationFailure trap signifies that the SNMPv2 entity, acting in an agent role, has received a protocol
message that is not properly authenticated. While all implementations of the SNMPv2 must be capable of generating
this trap, the snmpEnableAuthenTraps object indicates whether this trap is generated.
5.2.4.3.1
devAuthenticationFailureIpAddress
The following is an excerpt from the PDN-HEALTHANDSTATUS-MIB, pdn_HealthAndStatus.mib:
Authentication Failure Ip Address is used when a authenticationFailure trap is generated. The single varbind represents the ip address causing the error. If the ip address is not known, 0.0.0.0 is used.
OID:
—
devAuthenticationFailureIpAddress - { devStatus 5 }
Syntax:
—
IpAddress
Access:
—
read-only
Status:
—
mandatory
30
1.3.6.1.4.1.1795.2.24.2.4.1.5
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3
5.3.1
IF-MIB — RFC 2863
Introduction
This MIB describes objects for managing interfaces. The RFC used as a reference was dated June 2000. The LASTUPDATED for the IF-MIB was “200006140000Z.”
Figure 2, Interface Diagram, page 33, depicts the interfaces excluding those that exist on the Management and Uplink
Interface Module (MAUI). Figure 3, GigE MAUI, page 34, depicts the interfaces that exist on the GigE MAUI.
Figure 4, T1/E1 ML PPP MAUI, page 35 depicts the interfaces that exist on the T1/E1 ML PPP MAUI. In these
figures, there are three-digit number after the port name. These three-digit numbers represent the Port/Interface
Number for the particular port from Table 16, ifIndex, page 41. Table 12, Interface List, page 31 lists all the
interfaces.
The T1/E1 ML PPP Uplink MAUI, Figure 4, page 35, supports up to 8 multilink PPP bundles. However, typically
there will be multiple T1/E1 port assigned to a multilink PPP bundle and multiple bundles are supported.
Table 12: Interface List (1 of 2)
Interface
Quantity
Figure Label
Console Port
1 per Chassis
Console
Ethernet Port 1 (10/100 Base T)
1 per Chassis
Eth1
Ethernet Port 2 (10/100 Base T)
1 per Chassis
Eth2
Ethernet Port 3 (1000 Base T)
•
1000 Base T
•
GigE Small Form-factor Pluggable
1 per Chassisa
Eth3
T1/E1 Portsb
8 per Chassis
T1/E1
PPP HDLC Interface
8 per Chassis
HDLC
PPP LCP Interface
8 per Chassis
LCP
ML PPP Bundle Interfaces
8 per Chassis
ML PPP Bundle
PPP NCP Interface
8 per Chassis
NCP
DSL Ports
•
ADSL
•
ADSL2
•
ADSL2+
•
ReachDSL2.2
•
SHDSL.bis
24 per Chassisc
48 per Chassisd
DSL
DSL ATM Interfaces
24 per Chassisc
48 per Chassisd
DSL ATM
DSL ATM Bond Group Interfacese, f
12 per Chassisc, f
24 per Chassisd, f
DSL ATM Bond Group
31
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 12: Interface List (2 of 2)
Interface
Quantity
Figure Label
DSL Ethernet Interfaces
24 per Chassisc
48 per Chassisd
DSL Eth
Management In-Band Ethernet Interface
1 per Chassis
Mgmt IB Eth
Management Out-of-Band Ethernet Interface
1 per Chassis
Mgmt OOB Eth
a.
b.
c.
d.
Not available on units with T1/E1 ML PPP MAUI.
Not available on units with GigE MAUI.
24-Port Main DSL Card.
24-Port Main DSL Card plus 24-Port Child DSL Card.
e. DSL ATM Bonding is only supported for ADSL2+.
f. Refer to the PDN-DSL-ATM-BOND-MIB’s Implementation Restrictions, Section , Page 623, for factors that dictate the way DSL lines can be bonded along with any limitations.
32
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Eth1 (201) Eth2 (202)
Management and Uplink
Interface (MAUI) Module
Mgmt IB Eth (301)
Bridge
Mgmt OOB Eth (302)
Management Processor
Console (101)
…
DSL Eth
TCP/IP Stack
DSL Eth
DSL Eth
…
DSL Eth
DSL ATM Bond Group
(Layer 4)
(Layer 3)
DSL ATM
DSL ATM
…
DSL ATM
DSL ATM
…
DSL ATM
(Layer 2)
DSL
DSL
…
DSL
DSL
…
DSL
(Layer 1)
DSL2 (002) … DSL24 (024)
DSL1 (001)
Figure 2. Interface Diagram
33
DSL25 (025) … DSL48 (048)
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Eth3 (203)
Bridge
Figure 3. GigE MAUI
34
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
T1/E1 1 (401) T1/E1 2 (402) T1/E1 3 (403) T1/E1 4 (404) T1/E1 5 (405) T1/E1 6 (406) T1/E1 7 (407) T1/E1 8 (408)
(Layer 1)
HDLC
HDLC
HDLC
HDLC
HDLC
HDLC
HDLC
HDLC
(Layer 2)
LCP
LCP
LCP
LCP
LCP
LCP
LCP
LCP
(Layer 3)
ML PPP Bundle
ML PPP Bundle
NCP
NCP
(Layer 4)
NCP
Bridge
Figure 4. T1/E1 ML PPP MAUI
35
NCP
(Layer 5)
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.2
•
Textual Conventions
OwnerString
- This data type is used to model an administratively assigned name of the owner
of a resource. This information is taken from the NVT ASCII character set. It
is suggested that this name contain one or more of the following: ASCII form
of the manager station's transport address, management station name (for
example, domain name), network management personnel's name, location, or
phone number. In some cases the agent itself is the owner of an entry. In these
cases, this string shall be set to a string starting with “agent.”
OwnerString has the same semantics as used in RFC 1271
The syntax for this type is OCTET STRING (SIZE(0…255))
•
InterfaceIndex
- A unique value, greater than zero, for each interface or interface sub-layer in
the managed system. It is recommended that values are assigned contiguously
starting from 1. The value for each interface sub-layer must remain constant at
least from one re-initialization of the entity's network management system to
the next re-initialization.
InterfaceIndex contains the semantics of ifIndex and should be used for any
objects defined in other MIB modules that need these semantics.
The syntax for this type is integer32 (1…2147483647)
•
InterfaceIndexOrZero
- This textual convention is an extension of the InterfaceIndex convention. The
latter defines a greater than zero value used to identify an interface or interface
sub-layer in the managed system. This extension permits the additional value
of zero. the value zero is object-specific and must therefore be defined as part
of the description of any object which uses this syntax. Examples of the usage
of zero might include situations where interface was unknown, or when none
or all interfaces need to be referenced.
The syntax for this object is integer32 (0…2147483647).
36
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.3
•
•
•
•
•
•
•
•
•
•
•
•
•
•
5.3.4
OIDs
iso
org
dod
internet
mgmt
mib-2
interfaces
ifMIB
ifMIBObjects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 2 }
{ mib-2 31 }
{ ifMIB 1 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.2
1.3.6.1.2.1.31
1.3.6.1.2.1.31.1
snmpV2
snmpModules
snmpMIB
snmpMIBObjects
snmpTraps
-
{ internet 6 }
{ snmpV2 3 }
{ snmpModules 1 }
{ snmpMIB 1 }
{ snmpMIBObjects 5 }
1.3.6.1.6
1.3.6.1.6.3
1.3.6.1.6.3.1
1.3.6.1.6.3.1.1
1.3.6.1.6.3.1.1.5
MIB Objects
The table below identifies the objects called out in this MIB. Any table object that has elements that are supported are
indicated by a “Y” in the Supported column.
Table 13: IF-MIB Objects
Object
OID
Syntax
Access
Status
Supported
ifNumber
{ interfaces 1 }
Integer32
read-only
current
Y
ifTable
{ interfaces 3 }
Sequence of ifEntry
not-accessible
current
Y
ifXTable
{ ifMIBObjects 1 }
Sequence of ifXEntry
not-accessible
current
Y
ifStackTable
{ ifMIBObjects 2 }
Sequence of ifStackEntry
not-accessible
current
Y
ifTestTable
{ ifMIBObjects 3 }
Sequence of ifTestEntry
not-accessible
deprecated
N
ifRcvAddressTable
{ ifMIBObjects 4 }
Sequence of ifRcvAddressTable
not-accessible
current
Y
ifTableLastChange
{ ifMIBObjects 5 }
TimerTicks
read-only
current
Y
ifStackLastChange
{ ifMIBObjects 6 }
TimerTicks
read-only
current
Y
5.3.4.1
ifNumber
The number of network interfaces (regardless of their current state) present on this system.
Valid Object Value(s)
The ifNumber will represent the number of rows in the ifTable.
37
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.4.2
ifTableLastChange
The value of sysUpTime at the time of the last creation or deletion of an entry in the ifTable. If the number of entries
has been unchanged since the last re-initialization of the local network management subsystem, then this object
contains a zero value.
5.3.4.3
ifTable
The Interfaces table contains information on the entity's interfaces. Each sub-layer below the internetwork-layer of a
network interface is considered to be an interface. This object type is a sequence of the ifEntry where an entry
containing management information applicable to a particular interface.
Index(es):
•
ifIndex
OIDs:
•
•
ifTable - { interfaces 2 }
ifEntry - { ifTable 1 }
1.3.6.1.2.1.2.2
1.3.6.1.2.1.2.2.1
Table 14: ifTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ifIndex
{ ifEntry 1 }
Interface Index
read-only
current
Y
ifDescr
{ ifEntry 2 }
DisplayString
read-only
current
Y
ifType
{ ifEntry 3 }
IANAifType
read-only
current
Y
ifMtu
{ ifEntry 4 }
Integer32
read-only
current
Y
ifSpeed
{ ifEntry 5 }
Gauge32
read-only
current
Y
ifPhysAddress
{ ifEntry 6 }
PhysAddress
read-only
current
Y
{ ifEntry 7 }
INTEGER
up(1)
down(2)
testing(3)
read-write
current
Y
ifOperStatus
{ ifEntry 8 }
INTEGER
up(1)
down(2)
testing(3
unknown(4)
dormant(5)
notPresent(6)
lowerLayerDown(7)
read-only
current
Y
ifLastChange
{ ifEntry 9 }
TimerTicks
read-only
current
Y
ifInOctets
{ ifEntry 10 }
Counter32
read-only
current
Y
ifInUcastPkts
{ ifEntry 11 }
Counter32
read-only
current
Y
ifInNUcastPkts
{ ifEntry 12 }
Counter32
read-only
deprecated
N
ifAdminStatus
38
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 14: ifTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ifInDiscards
{ ifEntry 13 }
Counter32
read-only
current
Y
ifInErrors
{ ifEntry 14 }
Counter32
read-only
current
Y
ifInUnknownProtos
{ ifEntry 15 }
Counter32
read-only
current
Y
ifOutOctets
{ ifEntry 16 }
Counter32
read-only
current
Y
ifOutUcastPkts
{ ifEntry 17 }
Counter32
read-only
current
Y
ifOutNUcastPkts
{ ifEntry 18 }
Counter32
read-only
deprecated
N
ifOutDiscards
{ ifEntry 19 }
Counter32
read-only
current
Y
ifOutErrors
{ ifEntry 20 }
Counter32
read-only
current
Y
ifOutQLen
{ ifEntry 21 }
Counter32
read-only
deprecated
N
ifSpecific
{ ifEntry 22 }
Counter32
read-only
deprecated
N
5.3.4.3.1
ifIndex
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting
from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's
network management system to the next reinitialization.
Valid Object Value(s)
This ifIndex scheme was developed by a committee to solve a general stack hierarchy shown in Figure 5.
The ifIndex is encoded as a decimal number in the form of:
R R C C S S L P P P
Where:
•
•
R
CC
•
SS
•
•
L
PPP
- Reserved bits. Implied as 0.
- Chassis Number with the range of 1…99 and 0 is a special case to denote N/A.
The following are term used to refer to a chassis: chassis, slice, unit, or box.
- Slot Number with the range of 1…99 and 0 is a special case to denote N/A.
Slot Number is not applicable to this product and will always be 00.
- Layer Number in the range of 1…9 and 0 is a special case to denote N/A.
- Port/Interface Number in the range of 1…999 and 0 is a special case to denote N/A.
The layer number, L, can be seen as it is meant to be applied in Figure 2.
Note: Leading zeros may be omitted when using the ifIndex.
39
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Stack
Chassis1
Slot1
Port/Interface1
Slot2
Chassis2
•••
Layer1
Layer2
•••
Port/Interface2
•••
Port/Interfacen
•••
Chassisn
Slotn
Layern
Figure 5. Stack Hierarchy
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM products, although considered “stackable,” are not managed
in terms of a Single Managed Entity.
Table 15: Interface Stack
Layer
Console
T1/E1 ML PPP
DSLa
DSLb
DSL Eth
DSl Eth
5
NCP
4
ML PPP Bundle
3
LCP
2
HDLC
DSL ATM
DSL ATM
T1/E1
DSL
DSL
1
RS232
Ethn
Mgmt Ethn
Ethernet
Ethernet
DSL ATM Bond Group
a. ADSL, ADSL2, ADSL2+, ReachDSL, and SHDSL not part of a ATM-based multi-pair bonding group.
b. ADSL2+ part of a ATM-based multi-pair bonding group.
40
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 16: ifIndex
Valuea
Interface
Comment
R
R
Cb
Cb
Sc
Sc
L
P
P
P
DSL Ports
0
0
0
1
0
0
1
a
a
a
001…048
DSL ATM Interfaces
0
0
0
1
0
0
2
a
a
a
001…048
DSL ATM Bond Group Interfaces
0
0
0
1
0
0
3
a
a
a
001…048
DSL Ethernet Interfaces
0
0
0
1
0
0
4
a
a
a
001…048
Console Port
0
0
0
1
0
0
1
1
0
1
Ethernet Port 1 (10/100 Base T)
0
0
0
1
0
0
1
2
0
1
Ethernet Port 2 (10/100 Base T)
0
0
0
1
0
0
1
2
0
2
Ethernet Port 3 (1000 Base T / SFP)
0
0
0
1
0
0
1
2
0
3
Management In-Band Ethernet Interface
0
0
0
1
0
0
1
3
0
1
Management Out-of-Band Ethernet Interface
0
0
0
1
0
0
1
3
0
2
T1/E1 Ports
0
0
0
1
0
0
1
a
a
a
401…408
PPP HDLC Interface
0
0
0
1
0
0
2
a
a
a
401…408
PPP LCP Interface
0
0
0
1
0
0
3
a
a
a
401…408
ML PPP Bundle Interfaces
0
0
0
1
0
0
4
a
a
a
401…408
PPP NCP Interface
0
0
0
1
0
0
5
a
a
a
401…408
a. L PPP of 1 900 to 1 999 is reserved for internal use.
b. denotes the chassis/slice/unit/box number which is N/A in this product.
c. denotes the slot number which is N/A in this product.
Note: Leading zeros may be omitted.
5.3.4.3.2
ifDescr
A textual string containing information about the interface. This string should include the name of the manufacturer,
the product name and the version of the interface hardware/software.
41
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Valid Object Value(s)
Table 17: ifDescr (1 of 2)
Interface
Value
DSL Ports
“DSL PORT 1”
“DSL PORT 2”
•
•
•
“DSL PORT 48”
DSL ATM Interfaces
“DSL ATM Interface 1”
“DSL ATM Interface 2”
•
•
•
“DSL ATM Interface 48”
DSL ATM Bond Group Interfaces
“DSL ATM Bond Group Interface 1”
“DSL ATM Bond Group Interface 2”
•
•
•
“DSL ATM Bond Group Interface 24”
DSL Ethernet Interfaces
“DSL Ethernet Interface 1”
“DSL Ethernet Interface 2”
•
•
•
“DSL Ethernet Interface 48”
Console Port
“CONSOLE PORT”
Ethernet Port 1 (10/100 Base T)
“ETHERNET PORT 1”
Ethernet Port 2 (10/100 Base T)
“ETHERNET PORT 2”
Ethernet Port 3 (1000 Base T / SFP)
“ETHERNET PORT 3”
Management In-Band Ethernet Interface
“Management In-Band Ethernet Interface”
Management Out-of-Band Ethernet Interface
“Management Out-of-Band Ethernet Interface”
T1/E1 Ports
“T1/E1 Port 1”
“T1/E1 Port 2”
•
•
•
“T1/E1 Port 8”
42
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 17: ifDescr (2 of 2)
Interface
Value
PPP HDLC Interface
“PPP HDLC Interface 1”
“PPP HDLC Interface 2”
•
•
•
“PPP HDLC Interface 8”
PPP LCP Interface
“PPP LCP Interface 1”
“PPP LCP Interface 2”
•
•
•
“PPP LCP Interface 8”
ML PPP Bundle Interfaces
“ML PPP Bundle Interface 1”
“ML PPP Bundle Interface 2”
•
•
•
“ML PPP Bundle Interface 8”
PPP NCP Bridge Interface
“PPP NCP Interface 1”
“PPP NCP Interface 2”
•
•
•
“PPP NCP Interface 8”
5.3.4.3.3
ifType
The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA),
through updating the syntax of the IANAifType textual convention. The IANAifType is documented in the
IANAifType-MIB found at http://www.iana.org/assignments/ianaiftype-mib.
Valid Object Value(s)
Table 18: ifType (1 of 2)
Interface
Valuea,b
DSL Ports
adsl(94)
shdsl(169)
DSL ATM Interfaces
atmVirtual(149)
DSL ATM Bond Group Interfaces
linegroup(210)
43
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 18: ifType (2 of 2)
Interface
Valuea,b
DSL Ethernet Interfaces
ethernetCsmacd(6)
Console Port
rs232(33)
Ethernet Port 1(10/100 Base T)
ethernetCsmacd(6)
Ethernet Port 2 (10/100 Base T)
ethernetCsmacd(6)
Ethernet Port 3 (1000 Base T / SFP)
ethernetCsmacd(6)
Management In-Band Ethernet Interface
ethernetCsmacd(6)
Management Out-of-Band Ethernet Interface
ethernetCsmacd(6)
T1/E1 Ports
ds1(18)c
PPP HDLC Interface
hdlc(118)
PPP LCP Interface
ppp(23)
ML PPP Bundle Interfaces
pppMultilinkBundle(108)
PPP NCP Interface
ppp(23)
a. RFC 2556, “Ethernet-Like MIB,” August 1999, recommends in section 3.2.6 ifType, all Ethernet-like interfaces
use an ifType of ethernetCsmacd(6). The particular type of Ethernet that the interface is running is available from
ifSpeed and the ifMauType in the 802.3 MAU MIB (RFC 2668).
b. Both ReachDSL and ADSL Ports will report ifType adsl(94).
c. e1(19) is obsolete as noted in RFC 2495, DS1-MIB.
5.3.4.3.4
ifMtu
The size of the largest packet which can be sent/received on the interface, specified in octets. For interfaces that are
used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the
interface.
Valid Object Value(s)
Table 19: ifMtu (1 of 2)
Interface
Value
DSL Ports
53
DSL ATM Interfaces
53
DSL ATM Bond Group Interfaces
53
DSL Ethernet Interfaces
1550
44
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 19: ifMtu (2 of 2)
Interface
Value
Console Port
0
Ethernet Port 1 (10/100 Base T)
1550
Ethernet Port 2 (10/100 Base T)
1550
Ethernet Port 3 (1000 Base T / SFP)
1550
Management In-Band Ethernet Interface
1550
Management Out-of-Band Ethernet Interface
1550
T1/E1 Ports
0
PPP HDLC Interface
1532
PPP LCP Interface
1530
ML PPP Bundle Interfaces
1528
PPP NCP Interface
1528
5.3.4.3.5
ifSpeed
An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or
for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the
bandwidth of the interface is greater than the maximum value reportable by this object then this object should report
its maximum value (4,294,967,295) and ifHighSpeed must be used to report the interlaces speed. For a sub-layer
which has no concept of bandwidth, this object should be zero.
Valid Object Value(s)
Note that in the table below, spaces are added to enhance readability.
For example, 10M bps is displayed as 10000000 but documented in the table below as 10 000 000.
Table 20: ifSpeed (1 of 3)
Interface
Value
•
Port Trained
•
Port Not Trained
•
Port Trained
•
Port Not Trained
DSL Ports
DSL ATM Interfaces
- The downstream
rate of the port
- Zero
- The downstream rate
of the port
- Zero
The sum of the ifSpeed for each DSL port that is
currently part of the bonding group.
DSL ATM Bond Group Interfaces
45
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 20: ifSpeed (2 of 3)
Interface
Value
DSL Ethernet Interfaces
100 000 000
Console Port
Current configured speed
The possible values are: 9600 19200, 38400, 57600, and
115200 bps
The possible values are: 10 000 000 or
100 000 000
•
Ethernet Port 1 (10/100 Base T)
•
•
Auto-negotiation disabled
—
currently optioned speed
Auto-negotiation enabled and completed
—
auto-negotiation speed
Auto-negotiation enabled and not completed
—
100 000 000
The possible values are: 10 000 000 or
100 000 000
•
Ethernet Port 2 (10/100 Base T)
•
•
Auto-negotiation disabled
—
currently optioned speed
Auto-negotiation enabled and completed
—
auto-negotiation speed
Auto-negotiation enabled and not completed
—
100 000 000
The possible values are: 10 000 000, 100 000 000, or
1 000 000 000
•
Auto-negotiation disabled
—
currently poisoned speed
•
Auto-negotiation enabled and completed
—
auto-negotiation speed
•
Auto-negotiation enabled and not completed
—
1 000 000 000
When running on the SFP, the only valid value is
1 000 000 000
Ethernet Port 3 (1000 Base T / SFP)
Management In-Band Ethernet Interface
100 000 000
Management Out-of-Band Ethernet Interface
100 000 000
Current configured speeda
•
•
•
T1/E1 Ports
1 544 000 if configured for T1
2 048 000 if configured for E1
0 if non of the above
Current configured speed
PPP HDLC Interface
The possible values are: 64 000 bps to
2 048 000 bps in 64 000 bps increments
46
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 20: ifSpeed (3 of 3)
Interface
Value
PPP LCP Interface
0
ML PPP Bundle Interfaces
The sum of the ifSpeed for each T1/E1 port that
is currently part of the ML PPP Bundle.
PPP NCP Interface
0
a. The definition of being configured for T1 or E1 is when the appropriate dsx1LineType, Section
5.14.4.1.5, Page 285 and dsx1LineCoding, Section 5.14.4.1.6, Page 286 combination has been set.
5.3.4.3.6
ifPhysAddress
The interface's address at its protocol sub-layer. For example, for an 802.x interface, this object normally contains a
MAC address. The interface's media-specific MIB must define the bit and byte ordering and the format of the value of
this object. For interfaces which do not have such an address (for example, a serial line), this object should contain an
octet string of zero length.
Valid Object Value(s)
Table 21: ifPhysAddress (1 of 2)
Interface
Value
DSL Ports
An octet string of zero length
DSL ATM Interfaces
An octet string of zero length
DSL ATM Bond Group Interfaces
An octet string of zero length
DSL Ethernet Interfaces
An octet string of zero length
Console Port
An octet string of zero length
Ethernet Port 1 (10/100 Base T)
An octet string of zero length
Ethernet Port 2 (10/100 Base T)
An octet string of zero length
Ethernet Port 3 (1000 Base T / SFP)
An octet string of zero length
Management In-Band Ethernet Interface
MAC Address
Management Out-of-Band Ethernet Interface
MAC Address
T1/E1 Ports
An octet string of zero length
PPP HDLC Interface
An octet string of zero length
PPP LCP Interface
An octet string of zero length
47
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 21: ifPhysAddress (2 of 2)
Interface
Value
ML PPP Bundle Interfaces
An octet string of zero length
PPP NCP Interface
An octet string of zero length
5.3.4.3.7
ifAdminStatus
The desired state of the interface.
•
•
up(1)
down(2)
•
testing(3)
- The interface is operational and operational packets can be passed
- When a managed system is initialized, all interfaces start with ifAdminStatus in the down(2)
state
- The interface is in some test state and no operational packets can be passed
Valid Object Value(s)
Table 22: ifAdminStatus (1 of 2)
Interface
Value
DSL Ports
Any value supported by the syntax
DSL ATM Interfaces
The only valid value is up(1)
Setting the object to any other value will result in
badValue
DSL ATM Bond Group Interfaces
Any value supported by the syntax
DSL Ethernet Interfaces
The only valid value is up(1)
Setting the object to any other value will result in
badValue
Console Port
The only valid value is up(1)
Setting the object to any other value will result in
badValue
Ethernet Port 1 (10/100 Base T)
The only valid values are up(1) or down(2)
Setting the object to any other value will result in
badValue
Ethernet Port 2 (10/100 Base T)
The only valid values are up(1) or down(2)
Setting the object to any other value will result in
badValue
Ethernet Port 3 (1000 Base T / SFP)
The only valid values are up(1) or down(2)
Setting the object to any other value will result in
badValue
48
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 22: ifAdminStatus (2 of 2)
Interface
Value
Management In-Band Ethernet Interface
The only valid value is up(1)
Setting the object to any other value will result in
badValue
Management Out-of-Band Ethernet Interface
The only valid value is up(1)
Setting the object to any other value will result in
badValue
T1/E1 Ports
Any value supported by the syntax
PPP HDLC Interface
Any value supported by the syntax
PPP LCP Interface
The only valid values are up(1) or down(2)
Setting the object to any other value will result in
badValue
ML PPP Bundle Interfaces
Any value supported by the syntax
PPP NCP Interface
Any value supported by the syntax
5.3.4.3.8
ifOperStatus
The current operational state of the interface.
•
•
•
•
•
•
•
up(1)
down(2)
testing(3)
unknown(4)
dormant(5),
notPresent(6)
lowerLayerDown(7)
-
Ready to pass packets
The interface is in some test state and no operational packets can be passed.
status can not be determined for some reason.
some component is missing
down due to state of lower-layer interface(s)
The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then
ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the
interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for
external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and
only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the
interface has missing (typically, hardware) components.
Valid Object Value(s)
Table 23: ifOperStatus (1 of 2)
Interface
Value
DSL Ports
Any of the values supported by the syntax
49
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 23: ifOperStatus (2 of 2)
Interface
Value
DSL ATM Interfaces
Any of the values supported by the syntax except
down(2)
DSL ATM Bond Group Interfaces
Any value supported by the syntax
DSL Ethernet Interfaces
Any of the values supported by the syntax except
down(2)
Console Port
The port is always up(1)
Ethernet Port 1 (10/100 Base T)
Any value supported by the syntax
Ethernet Port 2 (10/100 Base T)
Any value supported by the syntax
Ethernet Port 3 (1000 Base T / SFP)
Any value supported by the syntax
Management In-Band Ethernet Interface
Any of the values supported by the syntax except
down(2)
Management Out-of-Band Ethernet Interface
Any of the values supported by the syntax except
down(2)
T1/E1 Ports
Any of the values supported by the syntax
PPP HDLC Interface
Any of the values supported by the syntax
PPP LCP Interface
Any of the values supported by the syntax
ML PPP Bundle Interfaces
Any value supported by the syntax
PPP NCP Interface
Any value supported by the syntax
5.3.4.3.9
ifLastChange
The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered
prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
50
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.4.3.10
Input Counters
ifInOctets
ifInUcastPkts
ifInNUcastPktsa
ifInDiscards
ifInErrors
ifInUnknownProtos
Table 24: ifIn Counter Objects
ADSL
S
U
U
U
S
U
ReachDSL
S
U
U
S
S
U
SHDSL
S
U
U
U
S
U
ADSL
S
U
U
U
S
U
ReachDSL
S
U
U
U
S
S
SHDSL
S
U
U
U
S
U
DSL ATM Bond Group Interfaces
S
U
U
U
S
U
DSL Ethernet Interfaces
U
S
U
S
S
S
Console Port
U
U
U
U
U
U
Ethernet Port 1 (10/100 Base T)
S
S
U
S
S
U
Ethernet Port 2 (10/100 Base T)
S
S
U
S
S
U
Ethernet Port 3 (1000 Base T / SFP)
S
S
U
S
S
U
Management In-Band Ethernet Interface
S
S
U
U
U
S
Management Out-of-Band Ethernet Interface
S
S
U
U
U
S
T1/E1 Ports
U
U
U
U
U
U
PPP HDLC Interface
U
U
U
U
U
U
PPP LCP Interface
U
U
U
U
U
U
ML PPP Bundle Interfaces
U
U
U
U
U
U
PPP NCP Interface
U
U
U
U
U
U
Interface
DSL Ports
DSL ATM Interfaces
Legend:
S = Supported
U = Unsupported (returns “No Such Name”)
Z = Unsupported (returns zero)
a. This MIB object is deprecated.
51
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.4.3.10.1
ifInOctets
The total number of octets received on the interface, including framing characters.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.10.2
ifInUcastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or
broadcast address at this sub-layer.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.10.3
ifInNUcastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast or
broadcast address at this sub-layer.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
This object is deprecated in favor of ifInMulticastPkts and ifInBroadcastPkts.
5.3.4.3.10.4
ifInDiscards
The number of inbound packets which were chosen to be discarded even though no errors had been detected to
prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be
to free up buffer space.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.10.5
ifInErrors
For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being
deliverable to a higher-layer protocol. For character- oriented or fixed-length interfaces, the number of inbound
transmission units that contained errors preventing them from being deliverable to a higher-layer protocol.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.10.6
ifInUnknownProtos
For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an
unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol
multiplexing the number of transmission units received via the interface which were discarded because of an
unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter will
always be 0.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
52
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.4.3.11
Output Counters
ifOutOctets
ifOutUcastPkts
ifOutNUcastPktsa
ifOutDiscards
ifOutErrors
Table 25: ifOut Counter Objects
ADSL
S
U
U
S
U
ReachDSL
S
U
U
S
U
SHDSL
S
U
U
S
U
ADSL
S
U
U
S
U
ReachDSL
S
U
U
S
U
SHDSL
S
U
U
S
U
DSL ATM Bond Group Interfaces
S
U
U
S
U
DSL Ethernet Interfaces
U
S
U
U
U
Console Port
U
U
U
U
U
Ethernet Port 1 (10/100 Base T)
S
S
U
S
S
Ethernet Port 2 (10/100 Base T)
S
S
U
S
S
Ethernet Port 3 (1000 Base T / SFP)
S
S
U
U
U
Management In-Band Ethernet Interface
S
S
U
U
U
Management Out-of-Band Ethernet Interface
S
S
U
U
U
T1/E1 Ports
U
U
U
U
U
PPP HDLC Interface
U
U
U
U
U
PPP LCP Interface
U
U
U
U
U
ML PPP Bundle Interfaces
U
U
U
U
U
PPP NCP Interface
U
U
U
U
U
Interface
DSL Ports
DSL ATM Interfaces
Legend:
S = Supported
U = Unsupported (returns “No Such Name”)
Z = Unsupported (returns zero)
a. This MIB object is deprecated.
53
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.4.3.11.1
ifOutOctets
The total number of octets transmitted out of the interface, including framing characters.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.11.2
ifOutUcastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a
multicast or broadcast address at this sub-layer, including those that were discarded or not sent.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.11.3
ifOutNUcastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a
multicast or broadcast address at this sub-layer, including those that were discarded or not sent.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
This object is deprecated in favor of ifOutMulticastPkts and ifOutBroadcastPkts.
5.3.4.3.11.4
ifOutDiscards
The number of outbound packets which were chosen to be discarded even though no errors had been detected to
prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.11.5
ifOutErrors
For packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For
character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted
because of errors.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.3.12
ifOutQLen
The length of the output packet queue (in packets).
Valid Object Value(s)
This object is deprecated and will not be supported.
Valid Object Value(s)
This object is deprecated and will not be supported.
5.3.4.3.13
ifSpecific
A reference to MIB definitions specific to the particular media being used to realize the interface. It is recommended
that this value point to an instance of a MIB object in the media-specific MIB, that is, that this object have the
semantics associated with the InstancePointer textual convention defined in RFC 2579. In fact, it is recommended that
54
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
the media-specific MIB specify what value ifSpecific should/can take for values of ifType. If no MIB definitions
specific to the particular media are available, the value should be set to the OBJECT IDENTIFIER { 0 0 }.
Valid Object Value(s)
This object is deprecated and will not be supported.
5.3.4.4
ifXTable
The Extension to the interface table provides additional objects for the interface table. The number of entries is given
by the value ifNumber. This object type is a sequence of ifXEntry and contains additional management information
applicable to a particular interface.
Augments:
•
ifTable (Section 5.3.4.3, Page 38)
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
ifXTable - { ifMIBObjects 1 }
ifXEntry - { ifXTable 1 }
1.3.6.1.2.1.31.1.1
1.3.6.1.2.1.31.1.1.1
Table 26: ifXTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ifName
{ ifXEntry 1 }
DisplayString
read-only
current
Y
ifInMulticastPkts
{ ifXEntry 2 }
Counter32
read-only
current
Y
ifInBroadcastPkts
{ ifXEntry 3 }
Counter32
read-only
current
Y
ifOutMulticastPkts
{ ifXEntry 4 }
Counter32
read-only
current
Y
ifOutBroadcastPkts
{ ifXEntry 5 }
Counter32
read-only
current
Y
ifHCInOctets
{ ifXEntry 6 }
Counter64
read-only
current
N
ifHCInUcastPkts
{ ifXEntry 7 }
Counter64
read-only
current
N
ifHCInMulticastPkts
{ ifXEntry 8 }
Counter64
read-only
current
N
ifHCInBroadcastPkts
{ ifXEntry 9 }
Counter64
read-only
current
N
ifHCOutOctets
{ ifXEntry 10 }
Counter64
read-only
current
N
ifHCOutUcastPkts
{ ifXEntry 11 }
Counter64
read-only
current
N
ifHCOutMulticastPkts
{ ifXEntry 12 }
Counter64
read-only
current
N
ifHCOutBroadcastPkts
{ ifXEntry 13 }
Counter64
read-only
current
N
55
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 26: ifXTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ifLinkUpDownTrapEnable
{ ifXEntry 14 }
INTEGER
enabled(1)
disabled(2)
read-write
current
Y
ifHighSpeed
{ ifXEntry 15 }
Gauge32
read-only
current
N
ifPromiscuousMode
{ ifXEntry 16 }
TruthValue
read-write
current
Y
IfConnectorPresent
{ ifXEntry 17 }
TruthValue
read-only
current
Y
ifAlias
{ ifXEntry 18 }
DisplayString(1…20)a
read-write
current
Y
ifCounterDiscontinuityTime
{ ifXEntry 19 }
TimeStamp
read-only
current
Y
a. Product imposed limit.
5.3.4.4.1
ifName
The textual name of the interface. The value of this object should be the name of the interface as assigned by the local
device and should be suitable for use in commands entered at the device's “console.” This might be a text name, such
as “le0” or a simple port number, such as “1,” depending on the interface naming syntax of the device. If several
entries in the ifTable together represent a single interface as named by the device, then each will have the same value
of ifName. Note that for an agent which responds to SNMP queries concerning an interface on some other (proxied)
device, then the value of ifName for such an interface is the proxied device's local name for it.
If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.
Valid Object Value(s)
Table 27: ifName (1 of 2)
Interface
Value
DSL Ports
“dsl n” where n is 1…48
DSL ATM Interfaces
“dsl atm n” where n is 1…48
DSL ATM Bond Group Interfaces
“dsl atm bond group interface n” where n is 1…24
DSL Ethernet Interfaces
“dsl eth n” where n is 1…48
Console Port
“console”
Ethernet Port 1 (10/100 Base T)
“ethernet 1”
Ethernet Port 2 (10/100 Base T)
“ethernet 2”
Ethernet Port 3 (1000 Base T / SFP)
“ethernet 3”
56
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 27: ifName (2 of 2)
Interface
Value
Management In-Band Ethernet Interface
“mgmt ib eth”
Management Out-of-Band Ethernet Interface
“mgmt oob eth”
T1/E1 Ports
“t1/e1 n” where n is 1…8
PPP HDLC Interface
“ppp hdlc interface n” where n is 1…8
PPP LCP Interface
“ppp lcp interface n” where n is 1…8
ML PPP Bundle Interfaces
“ml ppp bundle interface n” where n is 1…8
PPP NCP Interface
“ppp ncp interface n” where n is 1…8
5.3.4.4.2
Input Counters
Interface
ifInMulticastPkts
ifInBroadcastPkts
Table 28: ifXIn Counter Objects (1 of 2)
DSL Ports
U
U
DSL ATM Interfaces
U
U
DSL ATM Bond Group Interfaces
U
U
DSL Ethernet Interfaces
U
U
Console Port
U
U
Ethernet Port 1 (10/100 Base T)
S
S
Ethernet Port 2 (10/100 Base T)
S
S
Ethernet Port 3 (1000 Base T / SFP)
S
S
Management In-Band Ethernet Interface
S
S
Management Out-of-Band Ethernet Interface
S
S
T1/E1 Ports
U
U
PPP HDLC Interface
U
U
57
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Interface
ifInMulticastPkts
ifInBroadcastPkts
Table 28: ifXIn Counter Objects (2 of 2)
PPP LCP Interface
U
U
ML PPP Bundle Interfaces
U
U
PPP NCP Interface
U
U
Legend:
S = Supported
U = Unsupported (returns “No Such Name”)
Z = Unsupported (returns zero)
5.3.4.4.2.1
ifInMulticastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast
address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.2.2
ifInBroadcastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast
address at this sub-layer.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.3
Output Counters
Interface
ifOutMulticastPkts
ifOutBroadcastPkts
Table 29: ifXOut Counter Objects (1 of 2)
DSL Ports
U
U
DSL ATM Interfaces
U
U
58
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Interface
ifOutMulticastPkts
ifOutBroadcastPkts
Table 29: ifXOut Counter Objects (2 of 2)
DSL ATM Bond Group Interfaces
U
U
DSL Ethernet Interfaces
U
U
Console Port
U
U
Ethernet Port 1 (10/100 Base T)
S
S
Ethernet Port 2 (10/100 Base T)
S
S
Ethernet Port 3 (1000 Base T / SFP)
S
S
Management In-Band Ethernet Interface
S
S
Management Out-of-Band Ethernet Interface
S
S
T1/E1 Ports
U
U
PPP HDLC Interface
U
U
PPP LCP Interface
U
U
ML PPP Bundle Interfaces
U
U
PPP NCP Interface
U
U
Legend:
5.3.4.4.3.1
S = Supported
U = Unsupported (returns “No Such Name”)
Z = Unsupported (returns zero)
ifOutMulticastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a
multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this
includes both Group and Functional addresses.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.3.2
ifOutBroadcastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a
broadcast address at this sub-layer, including those that were discarded or not sent.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
59
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.4
High Capacity Input Counters
Interface
ifHCInOctets
ifHCInUcastPkts
ifHCInMulticastPkts
ifHCInBroadcastPkts
Table 30: ifHCIn Counter Objects
DSL Ports
U
U
U
U
DSL ATM Interfaces
U
U
U
U
DSL ATM Bond Group Interfaces
U
U
U
U
DSL Ethernet Interfaces
U
U
U
U
Console Port
U
U
U
U
Ethernet Port 1 (10/100 Base T)
U
U
U
U
Ethernet Port 2 (10/100 Base T)
U
U
U
U
Ethernet Port 3 (1000 Base T / SFP)
U
U
U
U
Management In-Band Ethernet Interface
U
U
U
U
Management Out-of-Band Ethernet Interface
U
U
U
U
T1/E1 Ports
U
U
U
U
PPP HDLC Interface
U
U
U
U
PPP LCP Interface
U
U
U
U
ML PPP Bundle Interfaces
U
U
U
U
PPP NCP Interface
U
U
U
U
Legend:
5.3.4.4.4.1
S = Supported
U = Unsupported (returns “No Such Name”)
Z = Unsupported (returns zero)
ifHCInOctets
The total number of octets received on the interface, including framing characters. This object is a 64-bit version of
ifInOctets.
60
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.4.2
ifHCInUcastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or
broadcast address at this sub-layer. This object is a 64-bit version of ifInUcastPkts.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other
times as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.4.3
ifHCInMulticastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast
address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. This object is
a 64-bit version of ifInMulticastPkts.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.4.4
ifHCInBroadcastPkts
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast
address at this sub-layer. This object is a 64-bit version of ifInBroadcastPkts.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.5
High Capacity Output Counters
Interface
ifHCOutOctets
ifHCOutUcastPkts
ifHCOutMulticastPkts
ifHCOutBroadcastPkts
Table 31: ifHCOut Counter Objects (1 of 2)
DSL Ports
U
U
U
U
DSL ATM Interfaces
U
U
U
U
DSL ATM Bond Group Interfaces
U
U
U
U
DSL Ethernet Interfaces
U
U
U
U
Console Port
U
U
U
U
Ethernet Port 1 (10/100 Base T)
U
U
U
U
Ethernet Port 2 (10/100 Base T)
U
U
U
U
61
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
ifHCOutOctets
ifHCOutUcastPkts
ifHCOutMulticastPkts
ifHCOutBroadcastPkts
Table 31: ifHCOut Counter Objects (2 of 2)
Ethernet Port 3 (1000 Base T / SFP)
U
U
U
U
Management In-Band Ethernet Interface
U
U
U
U
Management Out-of-Band Ethernet Interface
U
U
U
U
T1/E1 Ports
U
U
U
U
PPP HDLC Interface
U
U
U
U
PPP LCP Interface
U
U
U
U
ML PPP Bundle Interfaces
U
U
U
U
PPP NCP Interface
U
U
U
U
Interface
Legend:
5.3.4.4.5.1
S = Supported
U = Unsupported (returns “No Such Name”)
Z = Unsupported (returns zero)
ifHCOutOctets
The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit
version of ifOutOctets.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.5.2
ifHCOutUcastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a
multicast or broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit
version of ifOutUcastPkts.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.5.3
ifHCOutMulticastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a
multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this
includes both Group and Functional addresses. This object is a 64-bit version of ifOutMulticastPkts.
62
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.5.4
ifHCOutBroadcastPkts
The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a
broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of
ifOutBroadcastPkts.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.3.4.4.6
ifLinkUpDownTrapEnable
Indicates whether linkUp/linkDown traps should be generated for this interface.
•
•
enabled(1)
disabled(2)
By default, this object should have the value enabled(1) for interfaces which do not operate on “top” of any other
interface (as defined in the ifStackTable), and disabled(2) otherwise.
Valid Object Value(s)
Table 32: ifLinkUpDownTrapEnable (1 of 2)
Interface
Value
DSL Ports
enabled(1) or disabled(2)
DSL ATM Interfaces
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
DSL ATM Bond Group Interfaces
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
63
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 32: ifLinkUpDownTrapEnable (2 of 2)
Interface
Value
DSL Ethernet Interfaces
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
Console Port
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
Ethernet Port 1 (10/100 Base T)
enabled(1) or disabled(2)
Ethernet Port 2 (10/100 Base T)
enabled(1) or disabled(2)
Ethernet Port 3 (1000 Base T / SFP)
enabled(1) or disabled(2)
Management In-Band Ethernet Interface
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
Management Out-of-Band Ethernet Interface
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
T1/E1 Ports
enabled(1) or disabled(2)
PPP HDLC Interface
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
PPP LCP Interface
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
ML PPP Bundle Interfaces
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
PPP NCP Interface
The only valid value is disabled(2)
Setting the object to any other value will result in
badValue
5.3.4.4.7
ifHighSpeed
An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of
“n” then the speed of the interface is somewhere in the range of “n-500,000” to “n+499,999.” For interfaces which do
not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal
bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.
Valid Object Value(s)
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM do not have any interfaces that exceed a Gauge32 syntax. As
64
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
a result this object is not needed nor supported.
5.3.4.4.8
ifPromiscuousMode
This object has a value of false(2) if this interface only accepts packets/frames that are addressed to this station. This
object has a value of true(1) when the station accepts all packets/frames transmitted on the media. The value true(1) is
only legal on certain types of media. If legal, setting this object to a value of true(1) may require the interface to be
reset before becoming effective.
The value of ifPromiscuousMode does not affect the reception of broadcast and multicast packets/frames by the
interface.
Valid Object Value(s)
Table 33: ifPromiscuousMode
Interface
Value
DSL Ports
true(1)
DSL ATM Interfaces
true(1)
DSL ATM Bond Group Interfaces
true(1)
DSL Ethernet Interfaces
true(1)
Console Port
true(1)
Ethernet Port 1 (10/100 Base T)
false(2)
Ethernet Port 2 (10/100 Base T)
false(2)
Ethernet Port 3 (1000 Base T / SFP)
false(2)
Management In-Band Ethernet Interface
true(1)
Management Out-of-Band Ethernet Interface
true(1)
T1/E1 Ports
true(1)
PPP HDLC Interface
true(1)
PPP LCP Interface
true(1)
ML PPP Bundle Interfaces
true(1)
PPP NCP Interface
true(1)
5.3.4.4.9
ifConnectorPresent
• true(1)
- if the interface sublayer has a physical connector
• false(2) - otherwise
65
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Valid Object Value(s)
Table 34: ifConnectorPresent
Interface
Value
DSL Ports
true(1)
DSL ATM Interfaces
false(2)
DSL ATM Bond Group Interfaces
false(2)
DSL Ethernet Interfaces
false(2)
Console Port
true(1)
Ethernet Port 1 (10/100 Base T)
true(1)
Ethernet Port 2 (10/100 Base T)
true(1)
Ethernet Port 3 (1000 Base T / SFP)
true(1)
Management In-Band Ethernet Interface
false(2)
Management Out-of-Band Ethernet Interface
false(2)
T1/E1 Ports
true(1)
PPP HDLC Interface
false(2)
PPP LCP Interface
false(2)
ML PPP Bundle Interfaces
false(2)
PPP NCP Interface
false(2)
5.3.4.4.10
ifAlias
This object is an “alias” name for the interface as specified by a network manager, and provides a non-volatile 'handle'
for the interface.
On the first instantiation of an interface, the value of ifAlias associated with that interface is the zero-length string. As
and when a value is written into an instance of ifAlias through a network management set operation, then the agent
must retain the supplied value in the ifAlias instance associated with the same interface for as long as that interface
remains instantiated, including across all re- initializations/reboots of the network management system, including
those which result in a change of the interface's ifIndex value.
An example of the value which a network manager might store in this object for a WAN interface is the (Telco's)
circuit number/identifier of the interface.
Some agents may support write-access only for interfaces having particular values of ifType. An agent which
supports write access to this object is required to keep the value in non-volatile storage, but it may limit the length of
new values depending on how much storage is already occupied by the current values for other interfaces.
66
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.4.4.11
ifCounterDiscontinuityTime
The value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a
discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or
Counter64 object contained in the ifTable or ifXTable. If no such discontinuities have occurred since the last
reinitialization of the local management subsystem, then this object contains a zero value.
5.3.4.5
ifStackTable
The table containing information on the relationships between the multiple sub-layers of network interfaces. In
particular, it contains information on which sub-layers run 'on top of' which other sub-layers, where each sub-layer
corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs over the
sub-layer with ifIndex value y, then this table contains:
•
ifStackStatus.x.y=active
For each ifIndex value, I, which identifies an active interface, there are always at least two instantiated rows in this
table associated with I. For one of these rows, I is the value of ifStackHigherLayer; for the other, I is the value of
ifStackLowerLayer. (If I is not involved in multiplexing, then these are the only two rows associated with I.)
For example, two rows exist even for an interface which has no others stacked on top or below it:
•
•
ifStackStatus.0.x=active
ifStackStatus.x.0=active
This object is a sequence of ifStackEntry which contains information on a particular relationship between two sublayers, specifying that one sub-layer runs on “top” of the other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable.
Index(es):
•
•
ifStackHigherLayer
ifStackLowerLayer
OIDs:
•
•
ifStackTable
ifStackEntry
- { ifMIBObjects 2 }
- { ifStackTable 1 }
1.3.6.1.2.1.31.1.2
1.3.6.1.2.1.31.1.2.1
Table 35: ifStackTable
Object
OID
Syntax
Access
Status
Supported
ifStackHigherLayer
{ ifStackEntry 1 }
InterfaceIndexOrZero
not-accessible
current
Y
ifStackLowerLayer
{ ifStackEntry 2 }
InterfaceIndexOrZero
not-accessible
current
Y
ifStackStatus
{ ifStackEntry 3 }
RowStatus
read-create
current
Y
67
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Valid Object Value(s)
Table 36: ifStackTable Values (1 of 2)
a
Valuesb
Comments
Interface
ifStackHigherLayer
ifStackLowerLayer
0
4 aaac
Top of Stack, DSL Eth
1 aaac
0
Bottom of Stack, DSL
2 aaac
1 aaac
DSL ATM over DSL
4 aaac
2 aaac
DSL Eth over DSL ATM
0
4 aaac
Top of Stack, DSL Eth
1 aaad
0
Bottom of Stack, DSL
2 aaac
1 aaac
DSL ATM over DSL
3 aaac
2 aaac
DSL ATM Bond Group
over DSL ATM
4 aaa
3 aaa
DSL Eth over DSL ATM
Bond Group
0
1 101
1 101
0
0
1 201
1 201
0
0
1 202
1 202
0
0
1 203
1 203
0
Management In-Band Ethernet Interface
0
1 301
1 301
0
Management Out-of-Band Ethernet
Interface
0
1 302
1 302
0
DSL Ports
(not part of a bonding group)
DSL Ports
(part of a bonding group)
Console Port
Ethernet Port 1 (10/100 Base T)
Ethernet Port 2 (10/100 Base T)
Ethernet Port 3 (1000 Base T / SFP)
68
Only 1 layer
Only 1 layer
Only 1 layer
Only 1 layer
Only 1 layer
Only 1 layer
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 36: ifStackTable Values (2 of 2)
a
Valuesb
Comments
Interface
T1/E1 Ports (without ML PPP)
T1/E1 Ports (with ML PPP)
ifStackHigherLayer
ifStackLowerLayer
0
5 bbbe
Top of Stack, NCP
Bridge
5 bbb
3 ccce
NCP over LCP
3 ccc
2 ccc
LCP over HDLC
2 ccc
1 ccc
HDLC over T1/E1
1 ccc
0
Bottom of Stack, T1/E1
0
5 bbbe
Top of Stack, NCP
5 bbb
4 bbb
NCP Bridge over ML
PPP
4 bbb
3 ccce
ML PPP over LCP
3 ccc
2 ccc
LCP over HDLC
2 ccc
1 ccc
HDLC over T1/E1
1 ccc
0
Bottom of Stack, T1/E1
a. Refer to Interface List, Table 12 on page 31, to determine when the interface or port is applicable.
b. Reference Section 5.3.4.3.1, Page 39, for a description of the ifIndex encoding scheme along with
specific values of the ifIndex.
Spaces added and only the Layer and Port/Interface fields are displayed for clarification.
c. aaa refers to the associated DSL Port (001…048)
d. aaa refers to the associated DSL Port (001…048)
e. The port number bbb and ccc are independent.
5.3.4.5.1
ifStackHigherLayer
The value of ifIndex corresponding to the higher sub-layer of the relationship, that is, the sub-layer which runs on
“top” of the sub-layer identified by the corresponding instance of ifStackLowerLayer. If there is no higher sub-layer
(below the internetwork layer), then this object has the value 0.
5.3.4.5.2
ifStackLowerLayer
The value of ifIndex corresponding to the lower sub-layer of the relationship, that is, the sub-layer which runs
“below” the sub-layer identified by the corresponding instance of ifStackHigherLayer. If there is no lower sub-layer,
then this object has the value 0.
5.3.4.5.3
ifStackStatus
The status of the relationship between two sub-layers.
69
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Changing the value of this object from “active” to “notInService” or “destroy” will likely have consequences up and
down the interface stack. Thus, write access to this object is likely to be inappropriate for some types of interfaces,
and many implementations will choose not to support write-access for any type of interface.
Valid Object Value(s)
Write-access is not supported.
The createAndWait RowStatus (Section 4.11, Page 15) is not supported.
5.3.4.5.4
ifStackLastChange
The value of sysUpTime at the time of the last change of the (whole) interface stack. A change of the interface stack
is defined to be any creation, deletion, or change in value of any instance of ifStackStatus. If the interface stack has
been unchanged since the last re-initialization of the local network management subsystem, then this object contains
a zero value.
5.3.4.6
ifRcvAddressTable
The Generic Receive Address Table contains an entry for each address (broadcast, multicast, or unicast) for which the
system will receive packets/frames on a particular interface, except as follows:
•
•
for an interface operating in promiscuous mode, entries are only required for those addresses for which the
system would receive frames were it not operating in promiscuous mode
for 802.5 functional addresses, only one entry is required, for the address which has the functional address
bit ANDed with the bit mask of all functional addresses for which the interface will accept frames
A system is normally able to use any unicast address which corresponds to an entry in this table as a source address.
This table replaces the ifExtnsRcvAddr table. The main difference is that this table makes use of the RowStatus
(Section 4.11, Page 15) textual convention, while ifExtnsRcvAddr did not.
The table is a sequence of ifRcvAddressEntry which contains a list of objects identifying an address for which the
system will accept packets/frames on the particular interface identified by the index value ifIndex.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
ifRcvAddressAddress
OIDs:
•
•
ifRcvAddressTable
ifRcvAddressEntry
- { ifMIBObjects 4 }
- { ifRcvAddressTable 1 }
1.3.6.1.2.1.31.1.4
1.3.6.1.2.1.31.1.4.1
Table 37: ifRcvAddressTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ifRcvAddressAddress
{ ifRcvAddressEntry 1 }
PhysAddress
not-accessible
current
Y
ifRcvAddressStatus
{ ifRcvAddressEntry 2 }
RowStatus
read-create
current
Y
70
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 37: ifRcvAddressTable (2 of 2)
Object
ifRcvAddressType
5.3.4.6.1
OID
Syntax
Access
Status
Supported
read-create
current
Y
{ ifRcvAddressEntry 3 }
INTEGER
other(1)
volatile(2)
nonVolatile(3)
ifRcvAddressAddress
An address for which the system will accept packets/frames on this entry's interface.
5.3.4.6.2
ifRcvAddressStatus
This object is used to create and delete rows in the ifRcvAddressTable.
Valid Object Value(s)
The createAndWait RowStatus (Section 4.11, Page 15) is not supported.
5.3.4.6.3
ifRcvAddressType
• other(1)
- For those entries in the table which are valid and exist but are not classified as to
whether they will continue to exist after the next restart
• volatile(2)
- For those entries in the table which are valid and exist, but have not been saved, so that
will not exist after the next restart of the managed system
• nonVolatile(3) - For those entries in the table which are valid and will not be deleted by the next restart
of the managed system
The default value for this object is volatile(2).
5.3.4.7
ifTestTable
This table contains one entry per interface. It defines objects which allow a network manager to instruct an agent to
test an interface for various faults. Tests for an interface are defined in the media-specific MIB for that interface. After
invoking a test, the object ifTestResult can be read to determine the outcome. If an agent can not perform the test,
ifTestResult is set to so indicate. The object ifTestCode can be used to provide further test- specific or interfacespecific (or even enterprise-specific) information concerning the outcome of the test. Only one test can be in progress
on each interface at any one time. If one test is in progress when another test is invoked, the second test is rejected.
Some agents may reject a test when a prior test is active on another interface.
Before starting a test, a manager-station must first obtain “ownership” of the entry in the ifTestTable for the interface
to be tested. This is accomplished with the ifTestId and ifTestStatus objects as follows:
71
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
try_again:
get (ifTestId, ifTestStatus)
while (ifTestStatus != notInUse)
/*
* Loop while a test is running or some other
* manager is configuring a test.
*/
short delay
get (ifTestId, ifTestStatus)
}
/*
* Is not being used right now -- let's compete
* to see who gets it.
*/
lock_value = ifTestId
if ( set(ifTestId = lock_value, ifTestStatus = inUse,
ifTestOwner = 'my-IP-address') == FAILURE)
/*
* Another manager got the ifTestEntry -- go
* try again
*/
goto try_again;
/*
* I have the lock
*/
set up any test parameters.
/*
* This starts the test
*/
set(ifTestType = test_to_run);
wait for test completion by polling ifTestResult
when test completes, agent sets ifTestResult
agent also sets ifTestStatus = “notInUse”
retrieve any additional test results, and ifTestId
if (ifTestId == lock_value+1) results are valid
A manager station first retrieves the value of the appropriate ifTestId and ifTestStatus objects, periodically repeating
the retrieval if necessary, until the value of ifTestStatus is “notInUse.” The manager station then tries to set the same
ifTestId object to the value it just retrieved, the same ifTestStatus object to “inUse,” and the corresponding
ifTestOwner object to a value indicating itself. If the set operation succeeds then the manager has obtained ownership
of the ifTestEntry, and the value of the ifTestId object is incremented by the agent (per the semantics of TestAndIncr).
Failure of the set operation indicates that some other manager has obtained ownership of the ifTestEntry.
Once ownership is obtained, any test parameters can be setup, and then the test is initiated by setting ifTestType. On
completion of the test, the agent sets ifTestStatus to “notInUse.” Once this occurs, the manager can retrieve the
72
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
results. In the (rare) event that the invocation of tests by two network managers were to overlap, then there would be a
possibility that the first test's results might be overwritten by the second test's results prior to the first results being
read. This unlikely circumstance can be detected by a network manager retrieving ifTestId at the same time as
retrieving the test results, and ensuring that the results are for the desired request.
If ifTestType is not set within an abnormally long period of time after ownership is obtained, the agent should timeout the manager, and reset the value of the ifTestStatus object back to “notInUse.” It is suggested that this time-out
period be 5 minutes.
In general, a management station must not retransmit a request to invoke a test for which it does not receive a
response; instead, it properly inspects an agent's MIB to determine if the invocation was successful. Only if the
invocation was unsuccessful, is the invocation request retransmitted.
Some tests may require the interface to be taken off-line in order to execute them, or may even require the agent to
reboot after completion of the test. In these circumstances, communication with the management station invoking the
test may be lost until after completion of the test. An agent is not required to support such tests. However, if such tests
are supported, then the agent should make every effort to transmit a response to the request which invoked the test
prior to losing communication. When the agent is restored to normal service, the results of the test are properly made
available in the appropriate objects. Note that this requires that the ifIndex value assigned to an interface must be
unchanged even if the test causes a reboot. An agent must reject any test for which it cannot, perhaps due to resource
constraints, make available at least the minimum amount of information after that test completes.
This table contains one entry per interface. It defines objects which allow a network manager to instruct an agent to
test an interface for various faults.
This object is a sequence of ifTestEntry object which are objects for invoking tests on an interface.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
ifTestTable
ifTestEntry
- { ifMIBObjects 3 }
- { ifTestTable 1 }
1.3.6.1.2.1.31.1.3
1.3.6.1.2.1.31.1.3.1
Table 38: ifTestTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ifTestId
{ ifTestEntry 1 }
TestAndIncr
read-only
deprecated
N
ifTestStatus
{ ifTestEntry 2 }
INTEGER
notInUse(1)
inUse(2)
read-write
deprecated
N
ifTestType
{ ifTestEntry 3 }
AutonomousType
read-write
deprecated
N
73
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
Table 38: ifTestTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ifTestResult
{ ifTestEntry 4 }
INTEGER
none(1)
success(2)
inProgress(3)
notSupported(4)
unAbleToRun(5)
aborted(6)
failed(7)
read-only
deprecated
N
ifTestCode
{ ifTestEntry 5 }
OBJECT IDENTIFIER
read-only
deprecated
N
ifTestOwner
{ ifTestEntry 6 }
OwnerString
read-write
deprecated
N
5.3.4.7.1
ifTestId
This object identifies the current invocation of the interface's test.
Valid Object Value(s)
This object is supported for a test trap and its access is restricted to read-only.
5.3.4.7.2
ifTestStatus
This object indicates whether or not some manager currently has the necessary “ownership” required to invoke a test
on this interface. A write to this object is only successful when it changes its value from “notInUse(1)” to “inUse(2).”
After completion of a test, the agent resets the value back to “notInUse(1).
5.3.4.7.3
ifTestType
A control variable used to start and stop operator- initiated interface tests. Most OBJECT IDENTIFIER values
assigned to tests are defined elsewhere, in association with specific types of interface. However, this document
assigns a value for a full-duplex loopback test, and defines the special meanings of the subject identifier:
•
noTest OBJECT IDENTIFIER = { 0 0 }
When the value noTest is written to this object, no action is taken unless a test is in progress, in which case the test is
aborted. Writing any other value to this object is only valid when no test is currently in progress, in which case the
indicated test is initiated.
When read, this object always returns the most recent value that ifTestType was set to. If it has not been set since the
last initialization of the network management subsystem on the agent, a value of noTest is returned.
5.3.4.7.4
ifTestResult
This object contains the result of the most recently requested test, or the value none(1) if no tests have been requested
since the last reset. Note that this facility provides no provision for saving the results of one test when starting
another, as could be required if used by multiple managers concurrently. Values for this object are:
•
•
none(1)
success(2)
- no test yet requested
74
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
•
•
•
•
•
5.3.4.7.5
inProgress(3)
notSupported(4)
unAbleToRun(5)
aborted(6)
failed(7)
- due to state of system
ifTestCode
This object contains a code which contains more specific information on the test result, for example an error-code
after a failed test. Error codes and other values this object may take are specific to the type of interface and/or test.
The value may have the semantics of either the AutonomousType or InstancePointer textual conventions as defined in
RFC 2579. The identifier:
•
testCodeUnknown OBJECT IDENTIFIER = { 0 0 }
is defined for use if no additional result code is available.
5.3.4.7.6
ifTestOwner
The entity which currently has the “ownership” required to invoke a test on this interface.
75
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IF-MIB — RFC 2863
5.3.5
Traps
OIDs
•
snmpTraps
- { snmpMIBObjects 5 }
1.3.6.1.6.3.1.1.5
Table 39: Interface Group Traps
Object
OID
Trap Objects
Status
Supported
linkDown
{ snmpTraps 3 }
ifIndex
ifAdminStatus
ifOperStatus
current
Y
ifIndex
ifAdminStatus
ifOperStatus
current
Y
linkUp
{ snmpTraps 4 }
5.3.5.1
linkDown
A linkDown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for
one of its communication links is about to enter the down state from some other state (but not from the notPresent
state). This other state is indicated by the included value of ifOperStatus.
Objects:
•
•
•
5.3.5.2
ifIndex
ifAdminStatus
ifOperStatus
linkUp
A linkUp trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one
of its communication links left the down state and transitional into some other state (but not into the notPresent state).
This other state is indicated by the included value of ifOperStatus.
Objects:
•
•
•
ifIndex
ifAdminStatus
ifOperStatus
76
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
5.4
IP-MIB — RFC 2011
5.4.1
Introduction
This MIB describes objects for managing implementations of the Internet Protocol (IP) and its associated Internet
Control Message Protocol (ICMP). This MIB excludes the management of IP routes.
The RFC used as a reference was dated November 1996. The LAST-UPDATED for the IP-MIB was “9411010000z.”
5.4.2
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
ip
icmp
ipMIB
ipRouteTable
5.4.3
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 4 }
{ mib-2 5 }
{ mib-2 48 }
{ ip 21 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.4
1.3.6.1.2.1.5
1.3.6.1.2.1.48
1.3.6.1.2.1.4.21
The following groups supported in this MIB are as follow:
•
•
IP Group
ICMP Group
5.4.3.1
IP Group
OIDs:
•
ip
- { mib-2 4}
1.3.6.1.2.1.4
Table 40: IP-MIB Objects (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ipForwarding
{ ip 1 }
INTEGER
forwarding(1)
not-forwarding(2)
read-write
current
Y
ipDefaulTTL
{ ip 2 }
INTEGER(1…255)
read-write
current
Y
ipInReceives
{ ip 3 }
Counter32
read-only
current
Y
ipInHdrErrors
{ ip 4 }
Counter32
read-only
current
N
ipInAddrErrors
{ ip 5 }
Counter32
read-only
current
N
ipForwDatagrams
{ ip 6 }
Counter32
read-only
current
N
ipInUnknownProtos
{ ip 7 }
Counter32
read-only
current
N
ipInDiscards
{ ip 8 }
Counter32
read-only
current
N
77
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
Table 40: IP-MIB Objects (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ipInDelivers
{ ip 9 }
Counter32
read-only
current
N
ipOutRequests
{ ip 10 }
Counter32
read-only
current
N
ipOutDiscards
{ ip 11 }
Counter32
read-only
current
N
ipOutNoRoutes
{ ip 12 }
Counter32
read-only
current
N
ipReasmTimeout
{ ip 13 }
Integer32
read-only
current
N
ipReasmReqds
{ ip 14 }
Counter32
read-only
current
N
ipReasmOKs
{ ip 15 }
Counter32
read-only
current
N
ipReasmFails
{ ip 16 }
Counter32
read-only
current
N
ipFragOKs
{ ip 17 }
Counter32
read-only
current
N
ipFragFails
{ ip 18 }
Counter32
read-only
current
N
ipFragCreates
{ ip 19 }
Counter32
read-only
current
N
ipAddrTable
{ ip 20 }
Sequence of ipAddrEntry
not-accessible
current
Y
5.4.3.1.1
ipForwarding
The indication of whether this entity is acting as an IP router in respect to the forwarding of datagrams received by,
but not addressed to, this entity. IP routers forward datagrams. IP hosts do not (except those source-routed via the
host). Values for this object are:
•
•
forwarding(1)
notForwarding(2)
- acting as a router
- NOT acting as a router
Valid Object Value(s)
The only value supported for this object is notForwarding(2).
5.4.3.1.2
ipDefaultTTL
The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity,
whenever a TTL value is not supplied by the transport layer protocol.
The default value for this object is 255.
5.4.3.1.3
ipInReceives
The total number of input datagrams received from interfaces, including those received in error.
5.4.3.1.4
ipInHdrErrors
The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number
mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
5.4.3.1.5
ipInAddrErrors
The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid
78
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
address to be received at this entity. This count includes invalid addresses (for example, 0.0.0.0) and addresses of
unsupported Classes (for example, Class E). For entities which are not IP routers and therefore do not forward
datagrams, this counter includes datagrams discarded because the destination address was not a local address.
5.4.3.1.6
ipForwDatagrams
The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt
was made to find a route to forward them to that final destination. In entities which do not act as IP routers, this
counter will include only those packets which were Source-Routed via this entity, and the Source-Route option
processing was successful.
5.4.3.1.7
ipInUnknownProtos
The number of locally-addressed datagrams received successfully but discarded because of an unknown or
unsupported protocol.
5.4.3.1.8
ipInDiscards
The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but
which were discarded (for example, for lack of buffer space). Note that this counter does not include any datagrams
discarded while awaiting re-assembly.
5.4.3.1.9
ipInDelivers
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
5.4.3.1.10
ipOutRequests
The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for
transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
5.4.3.1.11
ipOutDiscards
The number of output IP datagrams for which no problem was encountered to prevent their transmission to their
destination, but which were discarded (for example, for lack of buffer space). Note that this counter would include
datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
5.4.3.1.12
ipOutNoRoutes
The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note
that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this
includes any datagrams which a host cannot route because all of its default routers are down.
5.4.3.1.13
ipReasmTimeout
The maximum number of seconds which received fragments are held while they are awaiting reassembly at this
entity.
This object is set to 60.
5.4.3.1.14
ipReasmReqds
The number of IP fragments received which needed to be reassembled at this entity.
5.4.3.1.15
ipReasmOKs
The number of IP datagrams successfully re-assembled.
79
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
5.4.3.1.16
ipReasmFails
The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note
that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC
815) can lose track of the number of fragments by combining them as they are received.
5.4.3.1.17
ipFragOKs
The number of IP datagrams that have been successfully fragmented at this entity.
5.4.3.1.18
ipFragFails
The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could
not be, for example, because their Don't Fragment flag was set.
5.4.3.1.19
ipFragCreates
The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
5.4.3.1.20
ipAddrTable
The table of addressing information relevant to this entity's IP addresses. This table is a sequence of ipAddrEntry
which contains the addressing information for one of this entity's IP addresses.
Index(es):
•
ipAdEntAddr
OIDs:
•
•
ipAddrTable
ipAddrEntry
- { ip 20 }
- {ipAddrTable 1 }
1.3.6.1.2.1.4.20
1.3.6.1.2.1.4.20.1
Table 41: ipAddrTable
Object
OID
Syntax
Access
Status
Supported
ipAdEntAddr
{ ipAddrEntry 1 }
IpAddress
read-only
current
Y
{ ipAddrEntry 2 }
INTEGER
(1…2147483674)
read-only
current
Y
ipAdEntNetMask
{ ipAddrEntry 3 }
IpAddress
read-only
current
Y
ipAdEntBcastAddr
{ ipAddrEntry 4 }
INTEGER(0…1)
read-only
current
Y
ipAdEntReasmMaxSize
{ ipAddrEntry 5 }
INTEGER(0…65535)
read-only
current
Y
ipAdEntIfIndex
5.4.3.1.20.1
ipAdEntAddr
The IP address to which this entry's addressing information pertains.
5.4.3.1.20.2
ipAdEntIfIndex
The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a
80
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
particular value of this index is the same interface as identified by the same value of RFC 1573's ifIndex.
5.4.3.1.20.3
ipAdEntNetMask
The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the
network bits set to 1 and all the hosts bits set to 0.
5.4.3.1.20.4
ipAdEntBcastAddr
The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface
associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is
used, the value is 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this
(logical) interface.
5.4.3.1.20.5
ipAdEntReasmMaxSize
The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams
received on this interface.
Valid Object Value(s)
1500
5.4.3.1.21
ipRouteTable
The IP Routing Table is deprecated by the Classless Inter-Domain Routing (CIDR) Table, ipCidrRouteTable,
specified in RFC 2096.
5.4.3.1.22
ipNetToMediaTable
The IP Address Translation tables contain the IpAddress to “physical” address equivalences. Some interfaces do not
use translation tables for determining address equivalences (for example, DDN-X.25 has an algorithmic method); if
all interfaces are of this type, then the Address Translation table is empty, that is, has zero entries.
The IP Address Translation table used for mapping from IP addresses to physical addresses.
The ipNetToMediaTable is a sequence of ipNetToMedialEntry which contains one ipAddress to physical address
equivalence.
Index(es):
•
•
ipNetToMediaIfIndex
ipNetToMediaNetAddress
OIDs:
•
•
ipNetToMediaTable
ipNetToMediaEntry
- { ip 22 }
- { ipNetToMediaTable 1 }
1.3.6.1.2.1.4.22
1.3.6.1.2.1.4.22.1
Table 42: ipNetToMediaTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ipNetToMediaIfIndex
{ ipNetToMediaEntry 1 }
INTEGER
(1…2147483674)
read-write
current
Y
81
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
Table 42: ipNetToMediaTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ipNetToMediaPhysAddress
{ ipNetToMediaEntry 2 }
PhysAddress
read-write
current
Y
ipNetToMediaNetAddress
{ ipNetToMediaEntry 3 }
IpAddress
read-write
current
Y
read-write
current
Y
{ ipNetToMediaEntry 4 }
INTEGER
other(1)
invalid(2)
dynamic(3)
static(4)
ipNetToMediaType
5.4.3.1.22.1
ipNetToMediaIfIndex
The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index
is the same interface as identified by the same value of RFC 1573's ifIndex.
5.4.3.1.22.2
ipNetToMediaPhysAddress
The media-dependent “physical” address.
5.4.3.1.22.3
ipNetToMediaNetAddress
The IpAddress corresponding to the media-dependent “physical” address.
5.4.3.1.22.4
ipNetToMediaType
The values for this object are:
•
•
•
•
other(1)
invalid(2)
dynamic(3)
static(4)
- None of the following
- An invalidated mapping
The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry
in the ipNetToMediaTable. That is, it effectively disassociates the interface identified with said entry from the
mapping identified with said entry. It is an implementation- specific matter as to whether the agent removes an
invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information
from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination
of the relevant ipNetToMediaType object.
5.4.3.1.23
ipRoutingDiscards
The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for
discarding such an entry could be to free-up buffer space for other routing entries.
5.4.3.2
ICMP Group
OIDs:
•
icmp - { mib-2 5 } 1.3.6.1.2.1.5
82
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
Table 43: ICMP Group
Object
OID
Syntax
Access
Status
icmpInMsgs
{ icmp 1 }
Counter32
read-only
current
N
icmpInErrors
{ icmp 2 }
Counter32
read-only
current
N
icmpInDestUnreachs
{ icmp 3 }
Counter32
read-only
current
N
icmpInTimeExcds
{ icmp 4 }
Counter32
read-only
current
N
icmpInParmProbs
{ icmp 5 }
Counter32
read-only
current
N
icmpInSrcQuenchs
{ icmp 6 }
Counter32
read-only
current
N
icmpInRedirects
{ icmp 7 }
Counter32
read-only
current
N
icmpInEchos
{ icmp 8 }
Counter32
read-only
current
N
icmpInEchoReps
{ icmp 9 }
Counter32
read-only
current
N
icmpInTimestamps
{ icmp 10 }
Counter32
read-only
current
N
icmpInTimestampReps
{ icmp 11 }
Counter32
read-only
current
N
icmpInAddrMasks
{ icmp 12 }
Counter32
read-only
current
N
icmpInAddrMaskReps
{ icmp 13 }
Counter32
read-only
current
N
icmpOutMsgs
{ icmp 14 }
Counter32
read-only
current
N
icmpOutErrors
{ icmp 15 }
Counter32
read-only
current
N
icmpOutDestUnreachs
{ icmp 16 }
Counter32
read-only
current
N
icmpOutTimeExcds
{ icmp 17 }
Counter32
read-only
current
N
icmpOutParmProbs
{ icmp 18 }
Counter32
read-only
current
N
icmpOutSrcQuenchs
{ icmp 19 }
Counter32
read-only
current
N
icmpOutRedirects
{ icmp 20 }
Counter32
read-only
current
N
icmpOutEchos
{ icmp 21 }
Counter32
read-only
current
N
icmpOutEchoReps
{ icmp 22 }
Counter32
read-only
current
N
icmpOutTimestamps
{ icmp 23 }
Counter32
read-only
current
N
icmpOutTimestampReps
{ icmp 24 }
Counter32
read-only
current
N
icmpOutAddrMasks
{ icmp 25 }
Counter32
read-only
current
N
icmpOutAddrMaskReps
{ icmp 26 }
Counter32
read-only
current
N
83
Supported
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
5.4.3.2.1
icmpInMsgs
The total number of ICMP messages which the entity received. Note that this counter includes all those counted by
icmpInErrors.
5.4.3.2.2
icmpInErrors
The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP
checksums, bad length, etc.).
5.4.3.2.3
icmpInDestUnreachs
The number of ICMP Destination Unreachable messages received.
5.4.3.2.4
icmpInTimeExcds
The number of ICMP Time Exceeded messages received.
5.4.3.2.5
icmpInParmProbs
The number of ICMP Parameter Problem messages received.
5.4.3.2.6
icmpInSrcQuenchs
The number of ICMP Source Quench messages received.
5.4.3.2.7
icmpInRedirects
The number of ICMP Redirect messages received.
5.4.3.2.8
icmpInEchos
The number of ICMP Echo (request) messages received.
5.4.3.2.9
icmpInEchoReps
The number of ICMP Echo Reply messages received.
5.4.3.2.10
icmpInTimestamps
The number of ICMP Timestamp (request) messages received.
5.4.3.2.11
icmpInTimestampReps
The number of ICMP Timestamp Reply messages received.
5.4.3.2.12
icmpInAddrMasks
The number of ICMP Address Mask Request messages received.
5.4.3.2.13
icmpInAddrMaskReps
The number of ICMP Address Mask Reply messages received.
5.4.3.2.14
icmpOutMsgs
The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those
counted by icmpOutErrors.
84
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-MIB — RFC 2011
5.4.3.2.15
icmpOutErrors
The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack
of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route
the resultant datagram. In some implementations there may be no types of error which contribute to this counter's
value.
5.4.3.2.16
icmpOutDestUnreachs
The number of ICMP Destination Unreachable messages sent.
5.4.3.2.17
icmpOutTimeExcds
The number of ICMP Time Exceeded messages sent.
5.4.3.2.18
icmpOutParmProbs
The number of ICMP Parameter Problem messages sent.
5.4.3.2.19
icmpOutSrcQuenchs
The number of ICMP Source Quench messages sent.
5.4.3.2.20
icmpOutRedirects
The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send
redirects.
5.4.3.2.21
icmpOutEchos
The number of ICMP Echo (request) messages sent.
5.4.3.2.22
icmpOutEchoReps
The number of ICMP Echo Reply messages sent.
5.4.3.2.23
icmpOutTimestamps
The number of ICMP Timestamp (request) messages sent.
5.4.3.2.24
icmpOutTimestampReps
The number of ICMP Timestamp Reply messages sent.
5.4.3.2.25
icmpOutAddrMasks
The number of ICMP Address Mask Request messages sent.
5.4.3.2.26
icmpOutAddrMaskReps
The number of ICMP Address Mask Reply messages sent.
85
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-FORWARD-MIB — RFC 2096
5.5
IP-FORWARD-MIB — RFC 2096
5.5.1
Introduction
This MIB is for displaying of Classless Inter-Domain Routing (CIDR) multipath IP Routes. The RFC used as a
reference was dated January 1997. The LAST-UPDATED for the IP_FORWARD-MIB was “9609190000Z.”
5.5.2
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
ip
ipForward
ipForwardNumber
ipForwardTable
ipCidrRouteNumber
ipCidrRouteTable
5.5.3
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 4 }
{ ip 24 }
{ ipForward 1 }
{ ipForward 2 }
{ ipForward 3 }
{ ipForward 4 }
- Obsoleted by ipCidrRouteNumber
- Obsoleted by ipCidrRouteTable
Table 44: IP-FORWARD-MIB Objects
Object
OID
Syntax
Access
Status
Supported
ipCidrRouteNumber
{ ipForward 3 }
Gauge32
read-only
current
Y
ipCidrRouteTable
{ ipForward 4 }
Sequence of ipCidrRouteEntry
not-accessible
current
Y
5.5.3.1
ipCidrRouteNumber
The number of current ipCidrRouteTable entries.
OID:
•
ipCidrRouteNumber - { ipForward 3 }
5.5.3.2
ipCidrRouteTable
The IP CIDR Route Table obsoletes and replaces the ipRoute Table current in MIB-I and MIB-II and the IP
Forwarding Table (RFC 1354). It adds knowledge of the autonomous system of the next hop, multiple next hop
support, and policy routing, and Classless Inter-Domain Routing.
Index(es):
•
•
•
•
ipCidrRouteDest
ipCidrRouteMask
ipCidrRouteTos
ipCidrRouteNextHop
86
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-FORWARD-MIB — RFC 2096
OIDs:
•
•
ipCidrRouteTable
ipCidrRouteEntry
- { ipForward 4 }
- { ipCidrRouteTable 1 }
Table 45: ipCidrRouteTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ipCidrRouteDest
{ ipCidrRouteEntry 1 }
IpAddress
read-only
current
Y
ipCidrRouteMask
{ ipCidrRouteEntry 2 }
IpAddress
read-only
current
Y
ipCidrRouteTos
{ ipCidrRouteEntry 3 }
Integer32
read-only
current
Y
ipCidrRouteNextHop
{ ipCidrRouteEntry 4 }
IpAddress
read-only
current
Y
ipCidrRouteIfIndex
{ ipCidrRouteEntry 5 }
Integer32
read-create
current
Y
ipCidrRouteType
{ ipCidrRouteEntry 6 }
INTEGER
other(1)
reject(2)
local(3)
remote(4)
read-create
current
N
ipCidrRouteProto
{ ipCidrRouteEntry 7 }
INTEGER
other(1)
local(2)
netmgmt(3)
icmp(3)
egp(5)
ggp(6)
hello(7)
rip(8)
isIs(9)
esIs(10)
ciscoIgrp(11)
bbnSpfIgp(12)
ospf(13)
bgp(14)
idpr(15)
ciscoEigrp(16)
read-only
current
Y
ipCidrRouteAge
{ ipCidrRouteEntry 8 }
Integer32
read-only
current
N
ipCidrRouteInfo
{ ipCidrRouteEntry 9 }
OBJECT IDENTIFIER
read-create
current
N
ipCidrRouteNextHopAS
{ ipCidrRouteEntry 10 }
Integer32
read-create
current
N
ipCidrRouteMetric1
{ ipCidrRouteEntry 11 }
Integer32
read-create
current
N
ipCidrRouteMetric2
{ ipCidrRouteEntry 12 }
Integer32
read-create
current
N
87
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-FORWARD-MIB — RFC 2096
Table 45: ipCidrRouteTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ipCidrRouteMetric3
{ ipCidrRouteEntry 13 }
Integer32
read-create
current
N
ipCidrRouteMetric4
{ ipCidrRouteEntry 14 }
Integer32
read-create
current
N
ipCidrRouteMetric5
{ ipCidrRouteEntry 15 }
Integer32
read-create
current
N
ipCidrRouteStatus
{ ipCidrRouteEntry 16 }
RowStatus
read-create
current
Y
5.5.3.2.1
ipCidrRouteDest
The destination IP address of this route.
This object may not take a Multicast (Class D) address value.
Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise
logical-AND of x with the value of the corresponding instance of the ipCidrRouteMask object is not equal to x.
5.5.3.2.2
ipCidrRouteMask
Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the
ipCidrRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of
the ipCidrRouteMask by reference to the IP Address Class.
Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise
logical-AND of x with the value of the corresponding instance of the ipCidrRouteDest object is not equal to
ipCidrRouteDest.
5.5.3.2.3
ipCidrRouteTos
The policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero
indicates the default path if no more specific policy applies.
The following convention is included for specification of TOS Field contents. At this time, the Host Requirements
and the Router Requirements documents disagree on the width of the TOS field. This mapping describes the Router
Requirements mapping, and leaves room to widen the TOS field without impact to fielded systems.
Table 46: ipCidrRouteTos (1 of 2)
Precedence
Type of Service
0
Policy Code
0
0
0
0
0
0
0
0
0
1
0
2
0
0
1
0
0
4
0
0
1
1
0
6
0
1
0
0
0
8
88
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-FORWARD-MIB — RFC 2096
Table 46: ipCidrRouteTos (2 of 2)
Precedence
Type of Service
0
Policy Code
0
1
0
1
0
10
0
1
1
0
0
12
0
1
1
1
0
14
1
0
0
0
0
16
1
0
0
1
0
18
1
0
1
0
0
20
1
0
1
1
0
22
1
1
0
0
24
1
1
0
1
0
26
1
1
1
0
0
28
0
1
1
1
0
30
Valid Object Value(s)
This object is not used in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. However, it is supported because it
is one of the indicies for the table. Therefore, only “0” is supported.
5.5.3.2.4
ipCidrRouteNextHop
On remote routes, the address of the next system en route; Otherwise, 0.0.0.0.
5.5.3.2.5
ipCidrRouteIfIndex
The ifIndex value which identifies the local interface through which the next hop of this route should be reached.
5.5.3.2.6
ipCidrRouteType
The type of route. Values for this object are listed below. Note that local(3) refers to a route for which the next hop is
the final destination; remote(4) refers to a route for which the next hop is not the final destination.
Routes which do not result in traffic forwarding or rejection should not be displayed even if the implementation keeps
them stored internally.
reject (2) refers to a route which, if matched, discards the message as unreachable. This is used in some protocols as a
means of correctly aggregating routes.
The values for this object are:
•
•
•
other(1)
reject(2)
local(3)
- not specified by this MIB
- route which discards traffic
- local interface
89
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-FORWARD-MIB — RFC 2096
•
remote(4)
5.5.3.2.7
- remote destination
ipCidrRouteProto
The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not
intended to imply that hosts should support those protocols.
The values for this object are:
•
•
•
•
other(1)
local(2)
netmgmt(3)
icmp(4)
-
not specified
local interface
static route
result of ICMP Redirect
Note: The following are all dynamic routing protocols
•
•
•
•
•
•
•
•
•
•
•
•
egp(5)
ggp(6)
hello(7)
rip (8)
isIs(9)
esIs(10)
ciscoIgrp(11)
bbnSpfIgp(12)
ospf(13)
bgp(14)
idpr(15)
ciscoEigrp(16)
-
Exterior Gateway Protocol
Gateway-Gateway Protocol
FuzzBall HelloSpeak
Berkeley RIP or RIP-II
Dual IS-IS
ISO 9542
Cisco IGRP
BBN SPF IGP
Open Shortest Path First
Border Gateway Protocol
InterDomain Policy Routing
Cisco EIGRP
Valid Object Value(s)
Since the BitStorm 2600 and GranDSLAM 4200 IP DSLAM use this table to defined static routes, the only value
supported is netMgmt(3).
5.5.3.2.8
ipCidrRouteAge
The number of seconds since this route was last updated or otherwise determined to be correct. Note that no
semantics of ‘too old’ can be implied except through knowledge of the routing protocol by which the route was
learned.
5.5.3.2.9
ipCidrRouteInfo
A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as date
mined by the value specified in the route’s ipCidrRouteProto value. If this information is not present, its value should
be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any implementation
conforming to ASN.1 and the Basic Encoding Rules must be able to generate and recognize this value.
5.5.3.2.10
ipCidrRouteNextHopAS
The Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing
protocol specified in the route’s ipCidrRouteProto value. When this object is unknown or not relevant its value should
be set to zero.
5.5.3.2.11
ipCidrRouteMetric1
The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol
90
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IP-FORWARD-MIB — RFC 2096
specified in the route’s ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
5.5.3.2.12
ipCidrRouteMetric2
An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol
specified in the route’s ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
5.5.3.2.13
ipCidrRouteMetric3
An alternate routing metric for this route. The semantics of this metric are determined by the routing protocol
specified in the route’s ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
5.5.3.2.14
ipCidrRouteMetric4
An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol
specified in the route’s ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
5.5.3.2.15
ipCidrRouteMetric5
An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol
specified in the route’s ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
5.5.3.2.16
ipCidrRouteStatus
The row status variable, used according to row installation and removal conventions.
91
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6
ENTITY-MIB (Version 2) — RFC 2737
5.6.1
Introduction
This MIB describes managed objects used for managing multiple logical and physical entities managed by a single
SNMP agent. The RFC used as a reference was dated December 1999. The LAST-UPDATED for this MIB in the
RFC was “9912070000Z.”
5.6.2
Terms
The following are terms used throughout this MIB:
•
Naming Scope
- A “naming scope” represents the set of information that may be potentially
accessed through a single SNMP operation. All instances within the naming
scope share the same unique identifier space. For SNMPv1, a naming scope is
identified by the value of the associated “entLogicalCommunity” instance. For
SNMPv3, the term “context” is used instead of “naming scope.” The complete
definition of an SNMP context can be found in section 3.3.1 of RFC 2571.
Each BitStorm 2600 and GranDSLAM 4200 IP DSLAM have a single naming
scope.
•
Multi-Scoped Object
- A MIB object, for which identical instance values identify different managed
information in different naming scopes, is called a “multi-scoped” MIB object.
•
Single-Scoped Object
- A MIB object, for which identical instance values identify the same managed
information in different naming scopes, is called a “single-scoped” MIB object.
Each managed object in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM is
single-scoped.
•
Logical Entity
- A managed system contains one or more logical entities, each represented by at
most one instantiation of each of a particular set of MIB objects. A set of management functions is associated with each logical entity. Examples of logical
entities include routers, bridges, print-servers, etc.
•
Physical Entity
- A “physical entity” or “physical component” represents an identifiable physical
resource within a managed system. Zero or more logical entities may utilize a
physical resource at any given time. It is an implementation-specific manner as to
which physical components are represented by an agent in the EntPhysicalTable.
Typically, physical resources (such as communications ports, backplanes, sensors, daughter-cards, power supplies, the overall chassis) which can be managed
via functions associated with one or more logical entities are included in the
MIB.
•
Containment Tree
- Each physical component may optionally be modeled as “contained” within
another physical component. A “containment-tree” is the conceptual sequence of
entPhysicalIndex values which uniquely specifies the exact physical location of a
physical component within the managed system. It is generated by “following
and recording” each “entPhysicalContainedIn” instance “up the tree towards the
root,” until a value of zero indicating no further containment is found.
5.6.3
Textual Conventions
The following textual conventions are made in this RFC:
92
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
•
PhysicalIndex
- An arbitrary value which uniquely identifies the physical entity. The value
is a small positive integer; index values for different physical entities are
not necessarily contiguous.
— Syntax
INTEGER(1…2147483647).
•
Physical Class
- An enumerated value which provides an indication of the general hardware type of a particular physical entity.There are no restrictions as to the
number of entPhysicalEntries of each entPhysicalClass, which must be
instantiated by an agent.
— Syntax
INTEGER
• other(1)
- applicable if the physical entity class is known,
but does not match any of the supported values.
• unknown(2)
- applicable if the physical entity class is
unknown to the agent.
• chassis(3)
- applicable if the physical entity class is an
overall container for networking equipment.
Any class of physical entity except a stack may
be contained within a chassis, and a chassis
may only be contained within a stack.
• backplane(4)
- applicable if the physical entity class is some
sort of device for aggregating and forwarding
networking traffic, such as a shared backplane
in a modular Ethernet switch. Note that an
agent may model a backplane as a single physical entity, which is actually implemented as
multiple discrete physical components (within
a chassis or stack).
• container(5)
- applicable if the physical entity class is capable
of containing one or more removable physical
entities, possibly of different types. For example, each (empty or full) slot in a chassis is
modeled as a container. Note that all removable
physical entities should be modeled within a
container entity, such as field-replaceable modules, fans, or power supplies. Note that all
known containers should be modeled by the
agent, including empty containers.
• powerSupply(6) - applicable if the physical entity class is a
power-supplying component.
• fan(7)
- applicable if the physical entity class is a fan or
other heat-reduction component.
• sensor(8)
- applicable if the physical entity class is some
sort of sensor, such as a temperature sensor
within a router chassis.
• module(9)
- applicable if the physical entity class is some
sort of self-contained sub-system. If it is
removable, then it should be modeled within a
container entity, otherwise it should be mod-
93
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
• port(10)
• stack(11)
5.6.4
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
entityMIB
entityMIBObjects
entityPhysical
entityLogical
entityMapping
entityGeneral
entityMIBTraps
entityMIBTrapPrefix
5.6.5
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 47 }
{ entityMIB 1 }
{ entityMIBObjects 1 }
{ entityMIBObjects 2 }
{ entityMIBObjects 3 }
{ entityMIBObjects 4 }
{ entityMIB 2 }
{ entityMIBTraps 0 }
eled directly within another physical entity (for
example, a chassis or another module).
- applicable if the physical entity class is some
sort of networking port, capable of receiving
and/or transmitting networking traffic.
- applicable if the physical entity class is some
sort of super-container (possibly virtual),
intended to group together multiple chassis
entities. A stack may be realized by a 'virtual'
cable, a real interconnect cable, attached to
multiple chassis, or may in fact be comprised
of multiple interconnect cables. A stack should
not be modeled within any other physical entities, but a stack may be contained within
another stack. Only chassis entities should be
contained within a stack.
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.47
1.3.6.1.2.1.47.1
1.3.6.1.2.1.47.1.1
1.3.6.1.2.1.47.1.2
1.3.6.1.2.1.47.1.3
1.3.6.1.2.1.47.1.4
1.3.6.1.2.1.47.1
1.3.6.1.2.1.47.1.0
The following groups are defined in this MIB:
•
•
entityPhysical group
entityLogical group
•
entityMapping group
•
entityGeneral group
- Describes the physical entities managed by a single agent.
- Describes the logical entities managed by a single agent.
This group is not implemented.
- Describes the associations between the physical entities, logical entities, interfaces, and non-interface ports managed by a single agent.
- Describes general system attributes shared by potentially all types of entities
managed by a single agent.
94
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 47: ENTITY-MIB Objects
Object
OID
Syntax
Access
Status
Supported
entPhysicalTable
{ entityPhysical 1 }
Sequence of entPhysicalEntry
not-accessible
current
Y
entLogicalTable
{ entityLogical 1 }
Sequence of entLogicalEntry
not-accessible
current
N
entLPMappingTable
{ entityMapping 1 }
Sequence of entLPMappingEntry
not-accessible
current
N
entAliasMappingTable
{ entityMapping 2 }
Sequence of entAliasMappingEntry
not-accessible
current
Y
entPhysicalContainsTable
{ entityMapping 3 }
Sequence of entPhysicalContainsEntry
not-accessible
current
Y
entLastChangeTime
{ entityGeneral 1 }
TimeStamp
read-only
current
Y
5.6.5.1
entityPhysical Group
This group contains a single table to identify physical system components, called the entPhysicalTable.
The entPhysicalTable contains one row per physical entity, and must always contain at least one row for an “overall”
physical entity, which should have an entPhysicalClass value of “stack(11),” “chassis(3)” or “module(9).”
Each row is indexed by an arbitrary, small integer, and contains a description and type of the physical entity. It also
optionally contains the index number of another entPhysicalEntry indicating a containment relationship between the
two.
Version 2 of the Entity MIB provides additional MIB objects for each physical entity. Some common read-only
attributes have been added, as well as three writable string objects.
•
entPhysicalAlias
This string can be used by an NMS as a non-volatile identifier for the physical component. Maintaining a
non-volatile string for every physical component represented in the entPhysicalTable can be costly and
unnecessary. An agent may algorithmically generate 'entPhysicalAlias' strings for particular entries (for
example, based on the entPhysicalClass value).
•
entPhysicalAssetID
This string is provided to store a user-specific asset identifier for removable physical components. In order to
reduce the non-volatile storage needed by a particular agent, a network administrator should only assign
asset identifiers to physical entities which are field-replaceable (that is, not permanently contained within
another physical entity).
•
entPhysicalSerialNum
This string is provided to store a vendor-specific serial number string for physical components. This is a
writable object in case an agent cannot identify the serial numbers of all installed physical entities, and a
network administrator wishes to configure the non-volatile serial number strings manually (via an NMS
application).
5.6.5.1.1
entPhysicalTable
This table contains one row per physical entity. There is always at least one row for an “overall” physical entity.
95
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
This table is a sequence of entPhysicalEntry which each entry provides objects (entPhysicalDescr,
entPhysicalVendorType, and entPhysicalClass) to help an NMS identify and characterize the entry, and objects
(entPhysicalContainedIn and entPhysicalParentRelPos) to help an NMS relate the particular entry to other entries in
this table.
Please refer to Interface List, Section 12, page 31, for a list of supported ports and interfaces.
Index(es):
•
entPhysicalIndex
OIDs:
•
•
entPhysicalTable
entPhysicalEntry
- {entityPhysical 1 }
- {entPhysicalTable 1 }
1.3.6.1.2.1.47.1.1.1
1.3.6.1.2.1.47.1.1.1.1
Table 48: entPhysicalTable
Object
OID
Syntax
Access
Status
Supported
entPhysicalIndex
{ entPhysicalEntry 1 }
PhysicalIndex
not-accessible
current
Y
entPhysicalDescr
{ entPhysicalEntry 2 }
SnmpAdminString
read-only
current
Y
entPhysicalVendorType
{ entPhysicalEntry 3 }
AutonomousType
read-only
current
Y
entPhysicalContainedIn
{ entPhysicalEntry 4 }
INTEGER(0…2147483647)
read-only
current
Y
entPhysicalClass
{ entPhysicalEntry 5 }
PhysicalClass
read-only
current
Y
entPhysicalParentRelPos
{ entPhysicalEntry 6 }
INTEGER(-1…2147483647)
read-only
current
Y
entPhysicalName
{ entPhysicalEntry 7 }
SnmpAdminString
read-only
current
Y
entPhysicalHardwareRev
{ entPhysicalEntry 8 }
SnmpAdminString
read-only
current
Y
entPhysicalFirmwareRev
{ entPhysicalEntry 9 }
SnmpAdminString
read-only
current
N
entPhysicalSoftwareRev
{ entPhysicalEntry 10 }
SnmpAdminString
read-only
current
Y
entPhysicalSerialNum
{ entPhysicalEntry 11 }
SnmpAdminString(SIZE(0…32))
read-onlya
current
Y
entPhysicalMfgName
{ entPhysicalEntry 12 }
SnmpAdminString
read-only
current
Y
entPhysicalModelName
{ entPhysicalEntry 13 }
SnmpAdminString
read-only
current
Y
entPhysicalAlias
{ entPhysicalEntry 14 }
SnmpAdminString(SIZE(0…32))
read-write
current
Y
entPhysicalAssetID
{ entPhysicalEntry 15 }
SnmpAdminString(SIZE(0…32))
read-write
current
Y
entPhysicalIsFRU
{ entPhysicalEntry 16 }
TruthValue
read-only
current
Y
a. Product imposed limit.
96
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6.5.1.1.1
entPhysicalIndex
The index for this entry.
Valid Object Value(s)
The value of this object is based on the ifIndex in the Interface Group, Section 5.3.4.3.1, Page 39.
The entPhysicalIndex is encoded as a decimal number in the form of:
R R C C S S L P P P
Where:
•
•
•
R
CC
SS
•
•
L
PPP
- Reserved bits. Implied as 0.
- Chassis Number with the range of 01…99 and 00 is a special case to denote N/A
- Slot Number with the range of 01…99 and 00 is a special case to denote N/A
Slot Number is not applicable to this product and will always be 00
- Layer Number in the range of 1…9 and 0 is a special case to denote N/A
- Port/Interface Number in the range of 001…999 and 000 is a special case to denote N/A
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM, although considered “stackable,” are not managed in terms
of a Single Managed Entity.
The following are values for the entPhyscialIndex object:
97
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 49: entPhysicalIndex
Value
Entity
Comment
R
R
C
C
S
S
L
P
P
P
Chassis
0
0
0
1
0
0
0
0
0
0
DSL Main Card
0
0
0
1
0
0
0
0
0
1
MAUI Card
0
0
0
1
0
0
0
0
0
2
POTS Splitter Child Card
0
0
0
1
0
0
0
0
0
3
DSL Child Card
0
0
0
1
0
0
0
0
0
4
Intake Temperature Sensor
0
0
0
1
0
0
0
0
5
1
Internal Temperature Sensor
0
0
0
1
0
0
0
0
5
2
Fan Speed Sensor n
0
0
0
1
0
0
0
0
6
n
Alarm Relay Input Contact
0
0
0
1
0
0
0
0
9
1
Alarm Relay Output Major Contact
0
0
0
1
0
0
0
0
9
2
Alarm Relay Output Minor Contact
0
0
0
1
0
0
0
0
9
3
DSL Main Card PLD
0
0
0
1
0
0
0
1
0
1
Reach DSL Main Card LED PLDa
0
0
0
1
0
0
0
1
0
2
MAUI Card PLD
0
0
0
1
0
0
0
1
1
1
DSL Child Card PLD
0
0
0
1
0
0
0
1
2
1
Reach DSL Child Card LED PLDa
0
0
0
1
0
0
0
1
2
2
Management Processor
0
0
0
1
0
0
0
2
0
1
DSL Port nb
0
0
0
1
0
0
1
0
n
n
Console Port
0
0
0
1
0
0
1
1
0
1
Ethernet Port n
0
0
0
1
0
0
1
2
0
n
T1/E1Port nd
0
0
0
1
0
0
1
4
0
n
n denotes the fan speed sensor number in
the range:
• 1…3 D/C powered chassis
• 1…4 A/C powered chassis
nn denotes the DSL port number in
the range of 1…48
n denotes the Ethernet port number
in the range of 1…3c
n denotes the T1/E1 port number in
the range of 1…8
a. ReachDSL Only
b. DSL Main Card contains 24 DSL Ports and an optional DSL Child Card contains an additional 24 DSL
Ports
c. Ethernet Port 3 is Not available on units with T1/E1 ML PPP MAUI.
d. T1/E1 Ports are not available on units with GigE MAUI.
98
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Note: Leading zeros may be omitted.
5.6.5.1.1.2
entPhysicalDescr
A textual description of physical entity. This object should contain a string which identifies the manufacturer's name
for the physical entity, and should be set to a distinct value for each version or model of the physical entity.
Valid Object Value(s)
Table 50: entPhysicalDescr (1 of 6)
Entity
Value
Company Namea Familyb Model Number; Model Description
where:
Model Number; Model Description is:
• 2600; 24 Reach DSL 2.2 Ports, No Splitters, Universal AC, GigE uplink, stacking
with 10/100 BT
• 2600; 24 Reach DSL 2.2 Ports, No Splitters, Universal AC, T1 ML PPP, stacking
with 10/100 BT
• 2600; 24 Reach DSL 2.2 Ports, No Splitters, Universal AC, E1 ML PPP, stacking
with 10/100 BT
Chassis (2600 Reach)
• 2600; 24 Reach DSL 2.2 Ports, Splitters, Universal AC, GigE uplink, stacking with
10/100 BT
• 2600; 24 Reach DSL 2.2 Ports, Splitters, Universal AC, T1 ML PPP, stacking with
10/100 BT
• 2600; 24 Reach DSL 2.2 Ports, Splitters, Universal AC, E1 ML PPP, stacking with
10/100 BT
• 2600; 48 Reach DSL 2.2 Ports, No Splitters, Universal AC, GigE uplink, stacking
with 10/100 BT
• 2600; 48 Reach DSL 2.2 Ports, No Splitters, Universal AC, T1 ML PPP, stacking
with 10/100 BT
• 2600; 48 Reach DSL 2.2 Ports, No Splitters, Universal AC, E1 ML PPP, stacking
with 10/100 BT
As determined by the Model Family Tree section in the BitStorm Product Overview document.
99
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 50: entPhysicalDescr (2 of 6)
Entity
Value
Company Namec Familyd Model Number; Model Description
where:
Model Number; Model Description is:
• 2600; 24 ADSL Annex A Ports, No Splitters, Universal AC, GigE uplink, stacking
with 10/100 BT
• 2600; 24 ADSL Annex A Ports, No Splitters, Universal AC, T1 ML PPP, stacking
with 10/100 BT
• 2600; 24 ADSL Annex A Ports, No Splitters, Universal AC, E1 ML PPP, stacking
with 10/100 BT
• 2600; 24 ADSL Annex B Ports, No Splitters, Universal AC, GigE uplink, stacking
with 10/100 BT
• 2600; 24 ADSL Annex B Ports, No Splitters, Universal AC, T1 ML PPP, stacking
with 10/100 BT
• 2600; 24 ADSL Annex B Ports, No Splitters, Universal AC, E1 ML PPP, stacking
with 10/100 BT
Chassis (2600 ADSL)
• 2600; 24 ADSL Annex A Ports, Splitters, Universal AC, GigE uplink, stacking with
10/100 BT
• 2600; 24 ADSL Annex A Ports, Splitters, Universal AC, T1 ML PPP, stacking with
10/100 BT
• 2600; 24 ADSL Annex A Ports, Splitters, Universal AC, E1 ML PPP, stacking with
10/100 BT
• 2600; 24 ADSL Annex B Ports, Splitters, Universal AC, GigE uplink, stacking with
10/100 BT
• 2600; 24 ADSL Annex B Ports, Splitters, Universal AC, T1 ML PPP, stacking with
10/100 BT
• 2600; 24 ADSL Annex B Ports, Splitters, Universal AC, E1 ML PPP, stacking with
10/100 BT
• 2600; 48 ADSL Annex A Ports, No Splitters, Universal AC, GigE uplink, stacking
with 10/100 BT
• 2600; 48 ADSL Annex A Ports, No Splitters, Universal AC, T1 ML PPP, stacking
with 10/100 BT
• 2600; 48 ADSL Annex A Ports, No Splitters, Universal AC, E1 ML PPP, stacking
with 10/100 BT
• 2600; 48 ADSL Annex B Ports, No Splitters, Universal AC, GigE uplink, stacking
with 10/100 BT
• 2600; 48 ADSL Annex B Ports, No Splitters, Universal AC, T1 ML PPP, stacking
with 10/100 BT
• 2600; 48 ADSL Annex B Ports, No Splitters, Universal AC, E1 ML PPP, stacking
with 10/100 BT
As determined by the Model Family Tree section in the BitStorm Product Overview document.
100
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 50: entPhysicalDescr (3 of 6)
Entity
Value
Chassis (2600 SHDSL)
Company Namee Familyf Model Number; Model Description
where:
Model Number; Model Description is:
• 2600; 24 SHDSL Ports, No Splitters, Universal AC, GigE uplink, stacking with 10/
100 BT
• 2600; 24 SHDSL Ports, No Splitters, Universal AC, T1 ML PPP, stacking with 10/
100 BT
• 2600; 24 SHDSL Ports, No Splitters, Universal AC, E1 ML PPP, stacking with 10/
100 BT
As determined by the Model Family Tree section in the BitStorm Product Overview document.
Company Nameg Familyh Model Number; Model Description
where:
Model Number; Model Description is:
• 4200; 24 Reach DSL 2.2 Ports, No Splitters, -48v DC, GigE uplink, stacking with
10/100 BT
• 4200; 24 Reach DSL 2.2 Ports, No Splitters, -48v DC, T1 ML PPP, stacking with
10/100 BT
• 4200; 24 Reach DSL 2.2 Ports, No Splitters, -48v DC, E1 ML PPP, stacking with
10/100 BT
Chassis (4200 Reach)
• 4200; 24 Reach DSL 2.2 Ports, Splitters, -48v DC, GigE uplink, stacking with 10/
100 BT
• 4200; 24 Reach DSL 2.2 Ports, Splitters, -48v DC, T1 ML PPP, stacking with 10/
100 BT
• 4200; 24 Reach DSL 2.2 Ports, Splitters, -48v DC, E1 ML PPP, stacking with 10/
100 BT
• 4200; 48 Reach DSL 2.2 Ports, No Splitters, -48v DC, GigE uplink, stacking with
10/100 BT
• 4200; 48 Reach DSL 2.2 Ports, No Splitters, -48v DC, T1 ML PPP, stacking with
10/100 BT
• 4200; 48 Reach DSL 2.2 Ports, No Splitters, -48v DC, E1 ML PPP, stacking with
10/100 BT
As determined by the Model Family Tree section in the BitStorm Product Overview document.
101
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 50: entPhysicalDescr (4 of 6)
Entity
Value
Company Namei Familyj Model Number; Model Description
where:
Model Number; Model Description is:
• 4200; 24 ADSL Annex A Ports, No Splitters, -48v DC, GigE uplink, stacking with
10/100 BT
• 4200; 24 ADSL Annex A Ports, No Splitters, -48v DC, T1 ML PPP, stacking with
10/100 BT
• 4200; 24 ADSL Annex A Ports, No Splitters, -48v DC, E1 ML PPP, stacking with
10/100 BT
• 4200; 24 ADSL Annex B Ports, No Splitters, -48v DC, GigE uplink, stacking with
10/100 BT
• 4200; 24 ADSL Annex B Ports, No Splitters, -48v DC, T1 ML PPP, stacking with
10/100 BT
• 4200; 24 ADSL Annex B Ports, No Splitters, -48v DC, E1 ML PPP, stacking with
10/100 BT
Chassis (4200 ADSL)
• 4200; 24 ADSL Annex A Ports, Splitters, -48v DC, GigE uplink, stacking with 10/
100 BT
• 4200; 24 ADSL Annex A Ports, Splitters, -48v DC, T1 ML PPP, stacking with 10/
100 BT
• 4200; 24 ADSL Annex A Ports, Splitters, -48v DC, E1 ML PPP, stacking with 10/
100 BT
• 4200; 24 ADSL Annex B Ports, Splitters, -48v DC, GigE uplink, stacking with 10/
100 BT
• 4200; 24 ADSL Annex B Ports, Splitters, -48v DC, T1 ML PPP, stacking with 10/
100 BT
• 4200; 24 ADSL Annex B Ports, Splitters, -48v DC, E1 ML PPP, stacking with 10/
100 BT
• 4200; 48 ADSL Annex A Ports, No Splitters, -48v DC, GigE uplink, stacking with
10/100 BT
• 4200; 48 ADSL Annex A Ports, No Splitters, -48v DC, T1 ML PPP, stacking with
10/100 BT
• 4200; 48 ADSL Annex A Ports, No Splitters, -48v DC, E1 ML PPP, stacking with
10/100 BT
• 4200; 48 ADSL Annex B Ports, No Splitters, -48v DC, GigE uplink, stacking with
10/100 BT
• 4200; 48 ADSL Annex B Ports, No Splitters, -48v DC, T1 ML PPP, stacking with
10/100 BT
• 4200; 48 ADSL Annex B Ports, No Splitters, -48v DC, E1 ML PPP, stacking with
10/100 BT
As determined by the Model Family Tree section in the BitStorm Product Overview document.
102
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 50: entPhysicalDescr (5 of 6)
Entity
Value
Chassis (4200 SHDSL)
Company Namek Familyl Model Number; Model Description
where:
Model Number; Model Description is:
• 4200; 24 SHDSL Ports, No Splitters, -48v DC, GigE uplink, stacking with 10/100
BT
• 4200; 24 SHDSL Ports, No Splitters, -48v DC, T1 ML PPP, stacking with 10/100
BT
• 4200; 24 SHDSL Ports, No Splitters, -48v DC, E1 ML PPP, stacking with 10/100
BT
As determined by the Model Family Tree section in the BitStorm Product Overview document.
DSL Main Card
Company Namea Familyb. Model Numberm; DSL Main Card
MAUI Card
Company Namea Familyb. Model Numberm ; Management Aggregation Uplink Interface
(MAUI) Card
POTS Splitter Child Card
Company Namea Familyb. Model Numberm ; POTS Splitter Child Card
DSL Child Card
Company Namea Familyb. Model Numberm ; DSL Child Card
Intake Temperature Sensor
Company Namea Familyb. Model Numberm ; Intake Temperature Sensor
Internal Temperature Sensor
Company Namea Familyb. Model Numberm ; Internal Temperature Sensor
Fan Speed Sensor n
Company Namea Familyb. Model Numberm ; Fan Speed Sensor n
Alarm Relay Input Contact
Company Namea Familyb. Model Numberm ; Alarm Relay Input Contact
Alarm Relay Output Major Contact
Company Namea Familyb. Model Numberm ; Alarm Relay Output Major Contact
Alarm Relay Output Minor Contact
Company Namea Familyb. Model Numberm ; Alarm Relay Output Minor Contact
DSL Main Card PLD
Company Namea Familyb. Model Numberm ; DSL Main Card PLD
Reach DSL Main Card LED PLD
Company Namea Familyb. Model Numberm ; DSL Main Card LED PLD
MAUI Card PLD
Company Namea Familyb. Model Numberm ; Management Aggregation Uplink Interface
(MAUI) Card PLD
DSL Child Card PLD
Company Namea Familyb. Model Numberm ; DSL Child Card PLD
Reach DSL Child Card LED PLD
Company Namea Familyb. Model Numberm ; DSL Child Card LED PLD
Management Processor
Company Namea Familyb. Model Numberm ; Management Processor
DSL Port n
Company Namea Familyb. Model Numberm ; DSL PORT n
where n is 1…48
Console Port
Company Namea Familyb. Model Numberm ; CONSOLE PORT
Ethernet Port n
Company Namea Familyb. Model Numberm ; ETHERNET PORT n
103
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 50: entPhysicalDescr (6 of 6)
Entity
Value
T1/E1Port n
Company Namea Familyb. Model Numberm ; T1/E1 PORT n
a. Reference the sysDescr object in the MIB-II’s System Group for clarification on Company Name.
b. The family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
c. Reference the sysDescr object in the MIB-II’s System Group for clarification on Company Name.
d. The family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
e. Reference the sysDescr object in the MIB-II’s System Group for clarification on Company Name.
f. The family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
g. Reference the sysDescr object in the MIB-II’s System Group for clarification on Company Name.
h. The family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
i. Reference the sysDescr object in the MIB-II’s System Group for clarification on Company Name.
j. The family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
k. Reference the sysDescr object in the MIB-II’s System Group for clarification on Company Name.
l. The family is “BitStorm” for the 26xx products and “GranDSLAM” for the 42xx products.
m. The Model Number is “2600” for the 26xx products and “4200” for the 42xx products.
5.6.5.1.1.3
entPhysicalVendorType
An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition
of MIB-II's sysObjectID.
An agent should set this object to a enterprise-specific registration identifier value indicating the specific equipment
type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device.
If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then
the value { 0 0 } is returned.
Valid Object Value(s)
Below is an OID tree for the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. The table that follows describes the
values supported for this object.
104
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 51: OID Tree (1 of 2)
OID Prefix
OID
Object
Company Enterprise.a
1.14.17.2
ips-chassis
Company Enterprise.a
1.14.17.2.2
ips-2611
1.14.17.2.3
ips-2621
1.14.17.2.4
ips-4219
1.14.17.2.5
ips-4229
1.14.17.2.6
ips-2671
1.14.17.2.7
ips-4279
1.14.17.2.9
ips-2631
1.14.17.2.10
ips-4239
1.14.17.2.11
ips-4214
1.14.17.2.12
ips-4224
1.14.17.2.13
ips-4234
1.14.17.2.14
ips-4274
1.14.17.2.15
ips-1614
1.14.17.2.16
ips-2624
1.14.17.2.17
ips-2634
1.14.17.2.18
ips-2674
1.14.17.3
ips-fixed-cards
1.14.17.3.1
ips-24port-adsl-main-card
1.14.17.3.2
ips-24port-adsl-child-card
1.14.17.3.3
ips-maui-card
1.14.17.3.4
ips-pots-splitter-child-card
1.14.17.3.5
ips-24port-reachDsl-main-card
1.14.17.3.6
ips-24port-reachDsl-child-card
1.14.17.3.7
ips-24port-shdsl-main-card
1.14.17.3.8
ips-24port-shdsl-child-card
1.14.17.3.9
ips-48port-adsl-main-card
105
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 51: OID Tree (2 of 2)
OID Prefix
OID
Object
Company Enterprise.a
1.14.17.5
ips-ports
Company Enterprise.a
1.14.17.5.2
ips-rs232-dce-port
1.14.17.5.5
ips-ethernet-port
1.14.17.5.6
ips-t1e1-port
1.14.17.5.7
ips-adsl-a-port
1.14.17.5.8
ips-reachDsl-port
1.14.17.5.9
ips-shdsl-port
1.14.17.5.10
ips-adsl-b-port
1.14.17.6
ips-components
1.14.17.6.1
ips-fan
1.14.17.6.2
ips-temperature-sensor
1.14.17.6.3
ips-processor
1.14.17.6.4
ips-pld
1.14.17.6.5
ips-speed-sensor
1.14.17.6.6
ips-alarm-relay-contact
a. Refer to sysObjectID, Section 5.2.3.1.2, page 24, for a definition of Company Enterprise.
106
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 52: entPhysicalVendorType (1 of 2)
Entity
Valuea
One of:
Chassis
•
{ Company Enterpriseb.1.14.17.2.2 }
ips-2611
•
{ Company Enterpriseb .1.14.17.2.3 }
ips-2621
•
{ Company Enterpriseb .1.14.17.2.4 }
ips-4219
•
{ Company Enterpriseb .1.14.17.2.5 }
ips-4229
b
•
{ Company Enterprise .1.14.17.2.6 }
ips-2671
•
{ Company Enterpriseb .1.14.17.2.7 }
ips-4279
•
{ Company Enterpriseb .1.14.17.2.9 }
ips-2631
•
{ Company Enterpriseb .1.14.17.2.10 }
ips-4239
•
{ Company Enterpriseb .1.14.17.2.11 }
ips-4214
•
{ Company Enterpriseb .1.14.17.2.12 }
ips-4224
•
{ Company Enterpriseb .1.14.17.2.13 }
ips-4234
•
{ Company Enterpriseb .1.14.17.2.14 }
ips-4274
•
{ Company Enterpriseb .1.14.17.2.15 }
ips-2614
•
{ Company Enterpriseb .1.14.17.2.16 }
ips-2624
•
{ Company Enterpriseb .1.14.17.2.17 }
ips-2634
One of:
DSL Main Card
•
{ Company Enterpriseb .1.14.17.3.1 }
ips-24port-adsl-main-card
•
{ Company Enterpriseb .1.14.17.3.5 }
ips-24port-reachDsl-main-card
•
{ Company Enterpriseb .1.14.17.3.7 }
ips-24port-shdsl-main-card
b
•
{ Company Enterprise .1.14.17.3.9 }
ips-48port-adsl-main-card
MAUI Card
{ Company Enterpriseb .1.14.17.3.3 }
ips-maui-card
POTS Splitter Child Card
{ Company Enterpriseb .1.14.17.3.4 }
ips-pots-splitter-child-card
One of:
DSL Child Card
•
{ Company Enterpriseb .1.14.17.3.2 }
ips-24port-adsl-child-card
•
{ Company Enterpriseb .1.14.17.3.6 }
ips-24port-reachDsl-child-card
Intake Temperature Sensor
{ Company Enterpriseb .1.14.17.6.2 }
ips-temperature-sensor
Internal Temperature Sensor
{ Company Enterpriseb .1.14.17.6.2 }
ips-temperature-sensor
Fan Speed Sensor n
{ Company Enterpriseb .1.14.17.6.5 }
ips-speed-sensor
Alarm Relay Input Contact
{ Company Enterpriseb .1.14.17.6.6 }
ips-alarm-relay-contact
Alarm Relay Output Major Contact
{ Company Enterpriseb .1.14.17.6.6 }
ips-alarm-relay-contact
Alarm Relay Output Minor Contact
{ Company Enterpriseb .1.14.17.6.6 }
ips-alarm-relay-contact
DSL Main Card PLD
{ Company Enterpriseb .1.14.17.6.4 }
ips-pld
Reach DSL Main Card LED PLD
{ Company Enterpriseb .1.14.17.6.4 }
ips-pld
107
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 52: entPhysicalVendorType (2 of 2)
Entity
Valuea
MAUI PLD
{ Company Enterpriseb .1.14.17.6.4 }
ips-pld
DSL Child Card PLD
{ Company Enterpriseb .1.14.17.6.4 }
ips-pld
Reach DSL Child Card LED PLD
{ Company Enterpriseb .1.14.17.6.4 }
ips-pld
Management Processor
{ Company Enterpriseb .1.14.17.6.3 }
ips-processor
One of:
DSL Port n
•
{ Company Enterpriseb .1.14.17.5.7 }
ips-adsl-a-port
•
{ Company Enterpriseb .1.14.17.5.8 }
ips-reachDsl-port
•
{ Company Enterpriseb .1.14.17.5.9 }
ips-shdsl-port
•
{ Company Enterpriseb .1.14.17.5.10 }
ips-adsl-b-port
Console Port
{ Company Enterpriseb .1.14.17.5.2 }
ips-rs232-dce-port
Ethernet Port n
{ Company Enterpriseb .1.14.17.5.5 }
ips-ethernet-port
T1/E1Port n
{ Company Enterpriseb .1.14.17.5.6 }
ips-t1e1-port
a. Note that some MIB browsers render the dash character ’-’ as an underscore character ’_’.
b. Reference the sysObjectID object in MIB-II’s System Group for clarification on Company Enterprise.
5.6.5.1.1.4
entPhysicalContainedIn
The value of entPhysicalIndex for the physical entity which “contains” this physical entity. A value of zero indicates
this physical entity is not contained in any other physical entity. Note that the set of “containment” relationships
define a strict hierarchy; that is, recursion is not allowed.
In the event a physical entity is contained by more than one physical entity (for example, double-wide modules), this
object should identify the containing entity with the lowest value of entPhysicalIndex.
Valid Object Value(s)
A stack is not contained in anything. A chassis is contained in a stack. A chassis or a card contains a variety of
entities. The Containment Tree, Figure 6, Page 109, illustrates the entities and their containment relationship.
108
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Containment Tree
Chassis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DSL Main Card
|
PLD
|
LED PLD1
|
Alarm Relay Input Contact
|
Alarm Relay Output Major Contact
|
Alarm Relay Output Minor Contact
|
ADSL Port 1…48
|
ReachDSL Port 1…24
|
SHDSL Port 1…24
MAUI Card
|
PLD
|
Management Processor
|
Console Port
|
Ethernet Port 1…32
|
T1/E1 Port 1…8
DSL POTS Splitter Child Card
DSL Child Card
|
PLD
|
LED PLD1
|
ADSL Port 25…48
|
ReachDSL Port 25…48
Fan Speed Sensor 1…4
Intake Temperature Sensor3
Internal Temperature Sensor3.
1. Reach DSL Only
2. Ethernet Port 3 only exists for units with a GigE Uplink.
3. This is a “logical” temperature sensor considered to be contained with in the chassis.
Figure 6. Containment Tree
109
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 53: entPhysicalContainedIn
Entity
Value
Chassis
0
DSL Main Card
entPhysicalIndex for the Chassis
MAUI Card
entPhysicalIndex for the Chassis
POTS Splitter Child Card
entPhysicalIndex for the Chassis
DSL Child Card
entPhysicalIndex for the Chassis
Intake Temperature Sensora
entPhysicalIndex for the Chassis
Internal Temperature Sensora.
entPhysicalIndex for the Chassis
Fan Speed Sensor n
entPhysicalIndex for the Chassis
Alarm Relay Input Contact
entPhysicalIndex for the DSL Main Card
Alarm Relay Output Major Contact
entPhysicalIndex for the DSL Main Card
Alarm Relay Output Minor Contact
entPhysicalIndex for the DSL Main Card
DSL Main Card PLD
entPhysicalIndex for the DSL Main Card
Reach DSL Main Card LED PLD
entPhysicalIndex for the DSL Main Card
MAUI PLD
entPhysicalIndex for the MAUI Card
DSL Child Card PLD
entPhysicalIndex for the DSL Child Card
Reach DSL Child Card LED PLD
entPhysicalIndex for the DSL Child Card
Management Processor
entPhysicalIndex for the MAUI Card
DSL Port n
One of:
•
entPhysicalIndex for the 24-port DSL Main Card, where n is
1…24
•
entPhysicalIndex for the 24-port DSL Child Card, where n is
25…48
•
entPhysicalIndex for the 48-port DSL Main Card, where n is
1…48
Console Port
entPhysicalIndex for the MAUI Card
Ethernet Port n
entPhysicalIndex for the MAUI Card
T1/E1Port n
entPhysicalIndex for the MAUI Card
a. This is a “logical” temperature sensor considered to be contained with in the chassis.
110
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6.5.1.1.5
entPhysicalClass
An indication of the general hardware type of the physical entity.
An agent should set this object to the standard enumeration value which most accurately indicates the general class of
the physical entity, or the primary class if there is more than one.
If no appropriate standard registration identifier exists for this physical entity, then the value “other(1)” is returned. If
the value is unknown by this agent, then the value “unknown(2)” is returned.
Valid Object Value(s)
Table 54: entPhysicalClass (1 of 2)
Entity
Value
Chassis
chassis(3)
DSL Main Card
module(9)
MAUI Card
module(9)
POTS Splitter Child Card
module(9)
DSL Child Card
module(9)
Intake Temperature Sensor
sensor(8)
Internal Temperature Sensor
sensor(8)
Fan Speed Sensor n
sensor(8)
Alarm Relay Input Contact
other(1)
Alarm Relay Output Major Contact
other(1)
Alarm Relay Output Minor Contact
other(1)
DSL Main Card PLD
other(1)
Reach DSL Main Card LED PLD
other(1)
MAUI PLD
other(1)
DSL Child Card PLD
other(1)
Reach DSL Child Card LED PLD
other(1)
Management Processor
other(1)
DSL Port n
port(10)
Console Port
port(10)
Ethernet Port n
port(10)
111
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 54: entPhysicalClass (2 of 2)
Entity
Value
T1/E1Port n
port(10)
5.6.5.1.1.6
entPhysicalParentRelPos
An indication of the relative position of this “child” component among all its “sibling” components. Sibling
components are defined as entPhysicalEntries —entries in the entPhysicalTable— which share the same instance
values of each of the entPhysicalContainedIn and entPhysicalClass objects.
An NMS can use this object to identify the relative ordering for all sibling components of a particular parent
(identified by the entPhysicalContainedIn instance in each sibling entry).
This value should match any external labeling of the physical component if possible. For example, for a module
labeled as “card #3,” entPhysicalParentRelPos should have the value “3.” Note that the entPhysicalEntry for the
module plugged in slot 3 should have an entPhysicalParentRelPos value of “1.”
If the physical position of this component does not match any external numbering or clearly visible ordering, then
user documentation or other external reference material should be used to determine the parent-relative position. If
this is not possible, then the agent should assign a consistent (but possibly arbitrary) ordering to a given set of
“sibling” components, perhaps based on internal representation of the components.
If the agent cannot determine the parent-relative position for some reason, or if the associated value of
entPhysicalContainedIn is “0,” then the value “-1” is returned. Otherwise a non-negative integer is returned,
indicating the parent-relative position of this physical entity.
Parent-relative ordering normally starts from “1” and continues to “N,” where “N” represents the highest positioned
child entity. However, if the physical entities (for example, slots) are labeled from a starting position of zero, then the
first sibling should be associated with a entPhysicalParentRelPos value of “0.” Note that this ordering may be sparse
or dense, depending on agent implementation.
The actual values returned are not globally meaningful, as each “parent” component may use different numbering
algorithms. The ordering is only meaningful among siblings of the same parent component.
The agent should retain parent-relative position values across reboots, either through algorithmic assignment or use of
non-volatile storage.
112
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Valid Object Value(s)
Table 55: EntPhysicalParentRelPos
Contained In
Entity
Index
Entity
Entity’s
Index
Class
Value
Chassis
1 000 000
Nothing
00 000 000
chassis(3)
-1
DSL Main Card
1 000 001
Chassis
1 000 000
module(9)
1
MAUI Card
1 000 002
Chassis
1 000 000
module(9)
2
POTS Splitter Child Card
1 000 003
Chassis
1 000 000
module(9)
3
DSL Child Card
1 000 004
Chassis
1 000 000
module(9)
3
Intake Temperature Sensor
1 000 051
Chassis
1 000 000
sensor(8)
1
Internal Temperature Sensor
1 000 052
Chassis
1 000 000
sensor(8)
2
Fan Speed Sensor n
1 000 06n
Chassis
1 000 000
sensor(8)
3…6
Alarm Relay Input Contact
1 000 091
DSL Main Card
1 000 001
other(1)
1
Alarm Relay Output Major Contact
1 000 092
DSL Main Card
1 000 001
other(1)
2
Alarm Relay Output Minor Contact
1 000 093
DSL Main Card
1 000 001
other(1)
3
DSL Main Card PLD
1 000 101
DSL Main Card
1 000 001
other(1)
4
Reach DSL Main Card LED PLD
1 000 102
DSL Main Card
1 000 001
other(1)
5
MAUI PLD
1 000 111
MAUI Card
1 000 002
other(1)
1
DSL Child Card PLD
1 000 121
DSL Child Card
1 000 004
other(1)
1
Reach DSL Child Card LED PLD
1 000 122
DSL Child Card
1 000 004
other(1)
2
Management Processor
1 000 201
MAUI Card
1 000 002
other(1)
2
DSL Main Card
1 000 001
port(10)
1…24
DSL Child Card
1 000 001
port(10)
1…24
DSL Port n = 1…24
DSL Port n = 25…48
1 001 0nn
Console Port
1 001 101
MAUI Card
1 000 002
port(10)
1
Ethernet Port n=1…3
1 001 201
MAUI Card
1 000 002
port(10)
2…4
T1/E1Port n
1 001 90n
MAUI Card
1 000 002
port(10)
4…11
113
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6.5.1.1.7
entPhysicalName
The textual name of the physical entity. The value of this object should be the name of the component as assigned by
the local device and should be suitable for use in commands entered at the device's “console.” This might be a text
name, such as “console” or a simple component number (for example, port or module number), such as “1,”
depending on the physical component naming syntax of the device.
If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.
Note that the value of entPhysicalName for two physical entities is the same in the event that the console interface
does not distinguish between them: for example, slot-1 and the card in slot-1.
Valid Object Value(s)
Table 56: entPhysicalName (1 of 2)
Entity
Value
Chassis
One of:
•
•
•
•
•
•
DSL Main Card
One of:
•
ADSL Main Card
•
ReachDSL Main Card
•
SHDSL Main Card
MAUI Card
Management Aggregation Uplink Interface (MAUI) Card
POTS Splitter Child Card
POTS Splitter Child Card
DSL Child Card
One of:
•
ADSL Child Card
•
ReachDSL Child Card
Intake Temperature Sensor
Intake Temperature Sensor
Internal Temperature Sensor
Internal Temperature Sensor
Fan Speed Sensor n
Fan Speed Sensor n
Alarm Relay Input Contact
Alarm Relay Input Contact
Alarm Relay Output Major Contact
Alarm Relay Output Major Contact
Alarm Relay Output Minor Contact
Alarm Relay Output Minor Contact
DSL Main Card PLD
DSL Main Card PLD
Reach DSL Main Card LED PLD
Reach DSL Main Card LED PLD
MAUI PLD
Management Aggregation Uplink Interface (MAUI) Card PLD
114
BitStorm 2600 ADSL Chassis
BitStorm 2600 ReachDSL Chassis
BitStorm 2600 SHDSL Chassis
GranDSLAM 4200 ADSL Chassis
GranDSLAM 4200 ReachDSL Chassis
GranDSLAM 4200 SHDSL Chassis
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 56: entPhysicalName (2 of 2)
Entity
Value
DSL Child Card PLD
DSL Child Card PLD
Reach DSL Child Card LED PLD
Reach DSL Child Card LED PLD
Management Processor
Management Processor
DSL Port n
dsl n
Console Port
console
Ethernet Port n
ethernet n
T1/E1Port n
t1/e1 n
5.6.5.1.1.8
entPhysicalHardwareRev
The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision
identifier actually printed on the component itself (if present).
Note that if revision information is stored internally in a non-printable (for example, binary) format, then the agent
must convert such information to a printable format, in an implementation-specific manner.
If no specific hardware revision string is associated with the physical component, or this information is unknown to
the agent, then this object will contain a zero-length string.
Valid Object Value(s)
Table 57: entPhysicalHardwareRev (1 of 2)
Entity
Value
Chassis
String appropriate for representing the revision of this entity
DSL Main Card
String appropriate for representing the revision of this entity
MAUI Card
String appropriate for representing the revision of this entity
POTS Splitter Child Card
String appropriate for representing the revision of this entity
DSL Child Card
String appropriate for representing the revision of this entity
Intake Temperature Sensor
zero-length string
Internal Temperature Sensor
zero-length string
Fan Speed Sensor n
zero-length string
Alarm Relay Input Contact
zero-length string
Alarm Relay Output Major Contact
zero-length string
115
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 57: entPhysicalHardwareRev (2 of 2)
Entity
Value
Alarm Relay Output Minor Contact
zero-length string
DSL Main Card PLD
String appropriate for representing the revision of this entity
Reach DSL Main Card LED PLD
String appropriate for representing the revision of this entity
MAUI PLD
String appropriate for representing the revision of this entity
DSL Child Card PLD
String appropriate for representing the revision of this entity
Reach DSL Child Card LED PLD
String appropriate for representing the revision of this entity
Management Processor
zero-length string
DSL Port n
zero-length string
Console Port
zero-length string
Ethernet Port n
zero-length string
T1/E1Port n
zero-length string
5.6.5.1.1.9
entPhysicalFirmwareRev
The vendor-specific firmware revision string for the physical entity.
Note that if revision information is stored internally in a non-printable (for example, binary) format, then the agent
must convert such information to a printable format, in an implementation-specific manner.
If no specific firmware programs are associated with the physical component, or this information is unknown to the
agent, then this object will contain a zero-length string.
Valid Object Value(s)
This object is not supported.
5.6.5.1.1.10
entPhysicalSoftwareRev
The vendor-specific software revision string for the physical entity.
Note that if revision information is stored internally in a non-printable (for example, binary) format, then the agent
must convert such information to a printable format, in an implementation-specific manner.
If no specific software programs are associated with the physical component, or this information is unknown to the
agent, then this object will contain a zero-length string.
Valid Object Value(s)
Since the operation of the BitStorm 2600 and GranDSLAM 4200 IP DSLAM is such that there is one software
revision per chassis, this object returns a zero-length string for all entities except the chassis. The chassis will return
the revision as a string in the form of yy.yy.yy.
116
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6.5.1.1.11
entPhysicalSerialNum
The vendor-specific serial number string for the physical entity. The preferred value is the serial number string
actually printed on the component itself (if present).
On the first instantiation of an physical entity, the value of entPhysicalSerialNum associated with that entity is set to
the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown
or non-existent, the entPhysicalSerialNum is set to a zero-length string instead.
Note that implementations which can correctly identify the serial numbers of all installed physical entities do not
need to provide write access to the entPhysicalSerialNum object. Agents which cannot provide non-volatile storage
for the entPhysicalSerialNum strings are not required to implement write access for this object.
Not every physical component will have a serial number, or even need one. Physical entities for which the associated
value of the entPhysicalIsFRU object is equal to “false(2)” (for example, the repeater ports within a repeater module),
do not need their own unique serial number. An agent does not have to provide write access for such entities, and may
return a zero-length string.
If write access is implemented for an instance of entPhysicalSerialNum, and a value is written into the instance, the
agent must retain the supplied value in the entPhysicalSerialNum instance associated with the same physical entity
for as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the
network management system, including those which result in a change of the physical entity's entPhysicalIndex
value.
117
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Valid Object Value(s)
Table 58: entPhysicalSerialNum
Entity
Value
Chassis
String appropriate for representing the serial number of this entity
DSL Main Card
String appropriate for representing the serial number of this entity
MAUI Card
String appropriate for representing the serial number of this entity
POTS Splitter Child Card
String appropriate for representing the serial number of this entity
DSL Child Card
String appropriate for representing the serial number of this entity
Intake Temperature Sensor
zero-length string
Internal Temperature Sensor
zero-length string
Fan Speed Sensor n
zero-length string
Alarm Relay Input Contact
zero-length string
Alarm Relay Output Major Contact
zero-length string
Alarm Relay Output Minor Contact
zero-length string
DSL Main Card PLD
zero-length string
Reach DSL Main Card LED PLD
zero-length string
MAUI PLD
zero-length string
DSL Child Card PLD
zero-length string
Reach DSL Child Card LED PLD
zero-length string
Management Processor
zero-length string
DSL Port n
zero-length string
Console Port
zero-length string
Ethernet Port n
zero-length string
T1/E1Port n
zero-length string
5.6.5.1.1.12
entPhysicalMfgName
The name of the manufacturer of this physical component. The preferred value is the manufacturer name string
actually printed on the component itself (if present).
Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev,
entPhysicalSoftwareRev, and the entPhysicalSerialNum objects, are only meaningful amongst entPhysicalEntries
with the same value of entPhysicalMfgName.
118
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
If the manufacturer name string associated with the physical component is unknown to the agent, then this object will
contain a zero-length string.
Valid Object Value(s)
The value of this object is “Paradyne.” for all entities.
5.6.5.1.1.13
entPhysicalModelName
The vendor-specific model name identifier string associated with this physical component. The preferred value is the
customer-visible part number, which may be printed on the component itself.
If the model name string associated with the physical component is unknown to the agent, then this object will
contain a zero-length string.
Valid Object Value(s)
Table 59: entPhysicalModelName (1 of 2)
Entity
Value
Chassis
String appropriate for representing the part number of this entity
DSL Main Card
String appropriate for representing the part number of this entity
MAUI Card
String appropriate for representing the part number of this entity
POTS Splitter Child Card
String appropriate for representing the part number of this entity
DSL Child Card
String appropriate for representing the part number of this entity
Intake Temperature Sensor
zero-length string
Internal Temperature Sensor
zero-length string
Fan Speed Sensor n
zero-length string
Alarm Relay Input Contact
zero-length string
Alarm Relay Output Major Contact
zero-length string
Alarm Relay Output Minor Contact
zero-length string
DSL Main Card PLD
zero-length string
Reach DSL Main Card LED PLD
zero-length string
MAUI PLD
zero-length string
DSL Child Card PLD
zero-length string
Reach DSL Child Card LED PLD
zero-length string
Management Processor
zero-length string
DSL Port n
zero-length string
Console Port
zero-length string
119
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 59: entPhysicalModelName (2 of 2)
Entity
Value
Ethernet Port n
zero-length string
T1/E1Port n
zero-length string
5.6.5.1.1.14
entPhysicalAlias
This object is an “alias” name for the physical entity as specified by a network manager, and provides a non-volatile
“handle” for the physical entity.
On the first instantiation of an physical entity, the value of entPhysicalAlias associated with that entity is set to the
zero-length string. However, agent may set the value to a locally unique default value, instead of a zero-length string.
If write access is implemented for an instance of entPhysicalAlias, and a value is written into the instance, the agent
must retain the supplied value in the entPhysicalAlias instance associated with the same physical entity for as long as
that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the network
management system, including those which result in a change of the physical entity's entPhysicalIndex value.
Valid Object Value(s)
This object will default to a zero-length string.
5.6.5.1.1.15
entPhysicalAssetID
This object is a user-assigned asset tracking identifier for the physical entity as specified by a network manager, and
provides non-volatile storage of this information.
On the first instantiation of an physical entity, the value of entPhysicalAssetID associated with that entity is set to the
zero-length string.
Not every physical component will have a asset tracking identifier, or even need one. Physical entities for which the
associated value of the entPhysicalIsFRU object is equal to “false(2)” (for example, the repeater ports within a
repeater module), do not need their own unique asset tracking identifier. An agent does not have to provide write
access for such entities, and may instead return a zero-length string.
If write access is implemented for an instance of entPhysicalAssetID, and a value is written into the instance, the
agent must retain the supplied value in the entPhysicalAssetID instance associated with the same physical entity for
as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the
network management system, including those which result in a change of the physical entity's entPhysicalIndex
value.
If no asset tracking information is associated with the physical component, then this object will contain a zero- length
string.
Valid Object Value(s)
This object will default to a zero-length string.
5.6.5.1.1.16
entPhysicalIsFRU
This object indicates whether or not this physical entity is considered a “field replaceable unit” by the vendor. If this
object contains the value “true(1)” then this entPhysicalEntry identifies a field replaceable unit. For all
120
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
entPhysicalEntries which represent components that are permanently contained within a field replaceable unit, the
value “false(2)” should be returned for this object.
Valid Object Value(s)
This object will take the value of true(1) for the following entities:
•
Chassis
The value for all other entities is false(2).
5.6.5.2
entityLogical Group
This group contains a single table to identify logical entities, called the entLogicalTable.
The entLogicalTable contains one row per logical entity. Each row is indexed by an arbitrary, small integer and
contains a name, description, and type of the logical entity.
Valid Object Value(s)
This group is not supported as there is only entity.
5.6.5.2.1
entLogicalTable
This table contains one row per logical entity. For agents which implement more than one naming scope, at least one
entry must exist. Agents which instantiate all MIB objects within a single naming scope are not required to
implement this table.
This table is a sequence of entLogicalEntry which contains information about a particular logical entity. Entities may
be managed by this agent or other SNMP agents (possibly) in the same chassis.
Index(es):
•
entLogicalIndex
OIDs:
•
•
entLogicalTable
entLogicalEntry
- {entityLogical 1 }
- {entLogicalTable 1 }
1.3.6.1.2.1.47.1.2.1
1.3.6.1.2.1.47.1.2.1.1
Table 60: entLogicalTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
entLogicalIndex
{ entLogicalEntry 1 }
INTEGER(1…2147483647)
not-accessible
current
N
entLogicalDescr
{ entLogicalEntry 2 }
DisplayString
read-only
current
N
entLogicalType
{ entLogicalEntry 3 }
AutonomousType
read-only
current
N
entLogicalCommunity
{ entLogicalEntry 4 }
OCTET STRING
(SIZE (1…255))
read-only
current
N
entLogicalTAddress
{ entLogicalEntry 5 }
TAddress
read-only
current
N
entLogicalTDomain
{ entLogicalEntry 6 }
TDomain
read-only
current
N
entLogicalContextEngineID
{ entLogicalEntry 7 }
SnmpEngineIdOrNone
read-only
current
N
121
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 60: entLogicalTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
entLoticalContextName
{ entLogicalEntry 8 }
SnmpAdminString
read-only
current
N
5.6.5.2.2
entLogicalIndex
The value of this object uniquely identifies the logical entity. The value is a small positive integer; index values for
different logical entities are not necessarily contiguous.
5.6.5.2.3
entLogicalDescr
A textual description of the logical entity. This object should contain a string which identifies the manufacturer's
name for the logical entity, and should be set to a distinct value for each version of the logical entity.
5.6.5.2.4
entLogicalType
An indication of the type of logical entity. This will typically be the OBJECT IDENTIFIER name of the node in the
SMI's naming hierarchy which represents the major MIB module, or the majority of the MIB modules, supported by
the logical entity. For example:
•
•
•
a logical entity of a regular host/router -> mib-2
a logical entity of a 802.1d bridge -> dot1dBridge
a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt
If an appropriate node in the SMI's naming hierarchy cannot be identified, the value “mib-2” should be used.
5.6.5.2.5
entLogicalCommunity
An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this
logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed
objects) and may also return a community string based on the privileges of the request used to read this object. Note
that an agent may return a community string with read-only privileges, even if this object is accessed with a readwrite community string. However, the agent must take care not to return a community string which allows more
privileges than the community string used to access this object.
A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single
“default” naming scope. This is possible when the logical entities represented by the same value of
entLogicalCommunity have no object instances in common. For example, “bridge1” and “repeater1” may be part of
the main naming scope, but at least one additional community string is needed to represent “bridge2” and “repeater2.”
Logical entities “bridge1” and “repeater1” would be represented by sysOREntries associated with the “default”
naming scope.
For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty string. This object may also
contain an empty string if a community string has not yet been assigned by the agent, or no community string with
suitable access rights can be returned for a particular SNMP request.
Note that this object is deprecated. Agents which implement SNMPv3 access should use the
entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical
entity. SNMPv3 agents may return a zero-length string for this object, or may continue to return a community string
(for example, tri-lingual agent support).
122
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6.5.2.6
entLogicalTAddress
The transport service address by which the logical entity receives network management traffic, formatted according
to the corresponding value of entLogicalTDomain.
For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 octets containing the IP-address in network-byte
order and the last 2 containing the UDP port in network-byte order. Consult “Transport Mappings for Version 2 of the
Simple Network Management Protocol” (RFC 1906) for further information on snmpUDPDomain.
5.6.5.2.7
entLogicalTDomain
Indicates the kind of transport service by which the logical entity receives network management traffic. Possible
values for this object are presently found in the Transport Mappings for SNMPv2 document (RFC 1906).
5.6.5.2.8
entLogicalContextEngineID
The authoritative contextEngineID that can be used to send an SNMP message concerning information held by this
logical entity, to the address specified by the associated “entLogicalTAddress/entLogicalTDomain” pair.
This object, together with the associated entLogicalContextName object, defines the context associated with a
particular logical entity, and allows access to SNMP engines identified by a contextEngineId and contextName pair.
If no value has been configured by the agent, a zero-length string is returned, or the agent may choose not to
instantiate this object at all.
5.6.5.2.9
entLogicalContextName
“The contextName that can be used to send an SNMP message concerning information held by this logical entity, to
the address specified by the associated “entLogicalTAddress/entLogicalTDomain” pair.
This object, together with the associated entLogicalContextEngineID object, defines the context associated with a
particular logical entity, and allows access to SNMP engines identified by a contextEngineId and contextName pair.
If no value has been configured by the agent, a zero-length string is returned, or the agent may choose not to
instantiate this object at all.
5.6.5.3
entityMapping Group
This group contains three tables to identify associations between different system components.
The entLPMappingTable contains mappings between entLogicalIndex values (logical entities) and entPhysicalIndex
values (the physical components supporting that entity). A logical entity can map to more than one physical
component, and more than one logical entity can map to (share) the same physical component. If an agent represents
a single logical entity, or multiple logical entities within a single naming scope, then implementation of this table may
be omitted by the agent.
The entAliasMappingTable contains mappings between entLogicalIndex, entPhysicalIndex pairs and “alias” object
identifier values. This allows resources managed with other MIBs (for example, repeater ports, bridge ports, physical
and logical interfaces) to be identified in the physical entity hierarchy. Note that each alias identifier is only relevant
in a particular naming scope. If an agent represents a single logical entity, or multiple logical entities within a single
naming scope, then implementation of this table may be omitted by the agent.
The entPhysicalContainsTable contains simple mappings between “entPhysicalContainedIn” values for each
container/”containee” relationship in the managed system. The indexing of this table allows an NMS to quickly
discover the “entPhysicalIndex” values for all children of a given physical entity.
123
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
5.6.5.3.1
entLPMappingTable
This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity
known by this agent, there are zero or more mappings to the physical resources which are used to realize that logical
entity.
An agent should limit the number and nature of entries in this table such that only meaningful and non-redundant
information is returned. For example, in a system which contains a single power supply, mappings between logical
entities and the power supply are not useful and should not be included.
Also, only the most appropriate physical component which is closest to the root of a particular containment tree
should be identified in an entLPMapping entry.
For example, suppose a bridge is realized on a particular module, and all ports on that module are ports on this bridge.
A mapping between the bridge and the module would be useful, but additional mappings between the bridge and each
of the ports on that module would be redundant (since the entPhysicalContainedIn hierarchy can provide the same
information). If, on the other hand, more than one bridge was utilizing ports on this module, then mappings between
each bridge and the ports it used would be appropriate.
Also, in the case of a single backplane repeater, a mapping for the backplane to the single repeater entity is not
necessary.
This table is a sequence of entLPMappingEntry which consists of information about a particular logical entity to
physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is
expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical
component information is utilized.
Index(es):
•
•
entLogicalIndex (Section 5.6.5.2.2, Page 122)
entLPPyhsicalIndex
OIDs:
•
•
entLPMappingTable - { entityMapping 1 }
entLPMappingEntry - { entLPMappingTable 1 }
1.3.6.1.2.1.47.1.3.1
1.3.6.1.2.1.47.1.3.1.1
Table 61: entLPMappingTable
Object
OID
Syntax
Access
Status
Supported
entLPPhysicalIndex
{ entLPMappingEntry 1 }
PhysicalIndex
not--accessible
current
N
5.6.5.3.2
entLPPhysicalIndex
The value of this object identifies the index value of a particular entPhysicalEntry associated with the indicated
entLogicalEntity.
5.6.5.4
entAliasMappingTable
This logical entity/component to alias table contains zero or more rows, representing mappings of logical entity and
physical component to external MIB identifiers. Each physical port in the system may be associated with a mapping
124
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
to an external identifier, which itself is associated with a particular logical entity's naming scope. A “wildcard”
mechanism is provided to indicate that an identifier is associated with more than one logical entity.
This table is a sequence of entAliasMappingEntry which consists of information about a particular physical
equipment, logical entity to external identifier binding. Each logical entity/physical component pair may be
associated with one alias mapping. The logical entity index may also be used as a “wildcard” (refer to the
entAliasLogicalIndexOrZero object DESCRIPTION clause for details.)
Note that only entPhysicalIndex values which represent physical ports (that is, associated entPhysicalClass value is
“port(10)”) are permitted to exist in this table.
Index(es):
•
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
entAliasLogicalIndexOrZero
OIDs:
•
•
entAliasMappingTable
entAliasMappingEntry
- { entityMapping 2 }
- { entAliasMappingTable 1 }
1.3.6.1.2.1.47.1.3.2
1.3.6.1.2.1.47.1.3.2.1
Table 62: entAliasMappingTable
Object
OID
Syntax
Access
Status
Supported
entAliasLogicalIndexOrZero
{ entAliasMappingEntry 1 }
INTEGER
(0…2147483647)
not--accessible
current
Y
entAliasMappingIdentifier
{ entAliasMappingEntry 2 }
RowPointer
read-only
current
Y
5.6.5.4.1
entAliasLogicalIndexOrZero
The value of this object uniquely identifies the logical entity which defines the naming scope for the associated
instance of the “entAliasMappingIdentifier” object.
If this object has a non-zero value, then it identifies the logical entity named by the same value of entLogicalIndex.
If this object has a value of zero, then the mapping between the physical component and the alias identifier for this
entAliasMapping entry is associated with all unspecified logical entities. That is, a value of zero (the default
mapping) identifies any logical entity which does not have an explicit entry in this table for a particular
entPhysicalIndex/entAliasMappingIdentifier pair.
For example, to indicate that a particular interface (for example, physical component 33) is identified by the same
value of ifIndex for all logical entities, the following instance might exist:
•
entAliasMappingIdentifier.33.0 = ifIndex.5
In the event an entPhysicalEntry is associated differently for some logical entities, additional entAliasMapping
entries may exist, for example:
•
•
•
entAliasMappingIdentifier.33.0
entAliasMappingIdentifier.33.4
entAliasMappingIdentifier.33.5
= ifIndex.6
= ifIndex.1
= ifIndex.1
125
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
•
entAliasMappingIdentifier.33.10
= ifIndex.12
Note that entries with non-zero entAliasLogicalIndexOrZero index values have precedence over any zero-indexed
entry. In this example, all logical entities except 4, 5, and 10, associate physical entity 33 with ifIndex.6.
Valid Object Value(s)
Since this object refers to a logical entity and there is only one logical entity in the BitStorm 2600 and GranDSLAM
4200 IP DSLAM product, this object will always be 0.
5.6.5.4.2
entAliasMappingIdentifier
The value of this object identifies a particular conceptual row associated with the indicated entPhysicalIndex and
entLogicalIndex pair.
Since only physical ports are modeled in this table, only entries which represent interfaces or ports are allowed. If an
ifEntry exists on behalf of a particular physical port, then this object should identify the associated “ifEntry,” For
repeater ports, the appropriate row in the “rptrPortGroupTable” should be identified instead.
For example, suppose a physical port was represented by entPhysicalEntry.3, entLogicalEntry.15 existed for a
repeater, and entLogicalEntry.22 existed for a bridge. Then there might be two related instances of
entAliasMappingIdentifier:
•
•
entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
entAliasMappingIdentifier.3.22 == ifIndex.17
It is possible that other mappings (besides interfaces and repeater ports) may be defined in the future, as required.
Bridge ports are identified by examining the Bridge MIB and appropriate ifEntries associated with each
“dot1dBasePort,” and are thus not represented in this table.
Valid Object Value(s)
This object contains the ifIndex associated with the particular port. Note that the index for this table is the
entAliasLogicalIndexOrZero object which is always 0 and the entPhysicalIndex object which is the ifIndex.
5.6.5.5
entPhysicalContainsTable
The physical mapping table exposes the container/”containee” relationships between physical entities. This table
provides equivalent information found by constructing the virtual containment tree for a given entPhysicalTable but
in a more direct format.
In the event a physical entity is contained by more than one other physical entity (for example, double-wide
modules), this table should include these additional mappings, which cannot be represented in the entPhysicalTable
virtual containment tree.
This table is a sequence of entPhysicalContainsEntry which contains a single container/”containee” relationship.
Index(es):
•
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
entPhysicalChildIndex
OIDs:
•
•
entPhysicalContainsTable
entPhysicalContainsEntry
- { entityMapping 3 }
1.3.6.1.2.1.47.1.3.3
- { entPhysicalContainsTable 1 } 1.3.6.1.2.1.47.1.3.3.1
126
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 63: entPhysicalContainsTable
Object
OID
Syntax
Access
Status
Supported
entPhysicalChildIndex
{ entPhysicalContainsEntry 1 }
PhysicalIndex
not-accessible
current
Y
5.6.5.5.1
entPhysicalChildIndex
The value of entPhysicalIndex (Section 5.6.5.1.1.1, Page 97) for the contained physical entity.
Valid Object Value(s)
The Containment Tree is diagramed in Figure 6, Page 109. This object constructs a table in the following form:
Table 64: entPhysicalChildIndexa (1 of 2)
Entity
Chassis
DSL Main Card
entPhysicalIndex
1 000 000
1 000 001
entPhysicalChildIndex
Comments
1 000 001
DSL Main Card
1 000 002
MAUI Card
1 000 003
POTS Splitter Child Card
1 000 004
DSL Child Card
1 000 051
Intake Temperature Sensor
1 000 052
Internal Temperature Sensor
1 000 06n
A chassis contains up to 4 Fan Speed Sensors, where n is
1…4
1 000 091
Alarm Relay Input Contact
1 000 092
Alarm Relay Output Major Contact
1 000 093
Alarm Relay Output Minor Contact
1 000 101
DSL Main Card PLD
1 000 102
Reach DSL Main Card LED PLD
1 001 nnn
ADSL, ReachDSL, or SHDSL Ports, where nnn is
1…24
127
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Table 64: entPhysicalChildIndexa (2 of 2)
Entity
entPhysicalIndex
MAUI Card
1 000 002
DSL Child Card
1 000 004
entPhysicalChildIndex
Comments
1 000 111
MAUI Card PLD
1 000 201
Management Processor
1 001 101
Console Port
1 001 20n
Ethernet Ports, where n is 1 …3
1 001 40n
T1/E1 Ports, where n is 1 …8
1 000 121
DSL Child Card PLD
1 000 122
Reach DSL Child Card LED PLD
1 001 0nn
ADSL or ReachDSL Ports, where nn is 25…48
a. Spaces added to increase readability. They do not actually exist as part of the value.
xx represents the chassis/slice/unit/box number.
5.6.5.6
entityGeneral Group
This group contains general information relating to the other object groups.
At this time, the entGeneral group contains a single scalar object (entLastChangeTime), which represents the value of
sysUptime when any part of the system configuration last changed.
OIDs:
•
entityGeneral
- { entityMIBObjects 4 }
1.3.6.1.2.1.47.1.4
Table 65: entLastChangeTime
Object
OID
Syntax
Access
Status
Supported
entLastChangeTime
{ entityGeneral 1 }
TimeStamp
read-only
current
Y
5.6.5.6.1
entLastChangeTime
The value of sysUpTime at the time any of these events occur:
•
a conceptual row is created, modified, or deleted in any of these tables:
—
entPhysicalTable
—
entLogicalTable
—
entLPMappingTable
—
entAliasMappingTable
—
entPhysicalContainsTable
128
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-MIB (Version 2) — RFC 2737
Valid Object Value(s)
This object will always return “time zero” as rows in the table are not dynamic in this implementation.
5.6.6
Traps
This section identifies Entity MIB Trap Definitions.
OIDs:
•
entityMIBTrapPrefix
- { entityMIBTraps 0 }
1.3.6.1.2.1.47.1.0
Table 66: ENTITY-MIB Traps
Object
OID
Trap Objects
Status
Supported
entConfigChange
{ entityMIBTrapPrefix 1 }
None
current
N
5.6.6.1
entConfigChange
An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an
NMS to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange “notification-event” in a given time interval (five
seconds is the suggested default). A “notification-event” is the transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the throttling period, then notification-events for these changes
should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one
notification-event should be generated if any configuration changes occurred since the start of the throttling period. In
such a case, another throttling period is started right away.
An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange
notification-events, for example, due to throttling or transmission loss.
129
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
5.7
ENTITY-SENSOR-MIB — RFC 3433
5.7.1
Introduction
This MIB describes managed objects for extending the Entity MIB (RFC 2737) (Section 5.6, Page 92)to provide
generalized access to information related to physical sensors, which are often found in networking equipment (such
as chassis temperature, fan RPM, power supply voltage). Physical sensors are represented in the Entity MIB with
entPhysicalEntry (Section 5.6.5.1.1, Page 95) and an entPhysicalClass (Section 5.6.5.1.1.5, Page 111) value of
“sensor(8).” The information provided in the ENTITY-SENSOR-MIB module (defined in this document) defines a
sparse augmentation of the entPhysicalTable, for entries which represent physical sensors. The RFC used as a
reference was dated December 16, 2002. The LAST-UPDATED for this MIB in the RFC was “200212160000Z.”
5.7.2
Textual Conventions
The following textual conventions are made in this RFC:
•
EntitySensorDataType
- An object using this data type represents the Entity Sensor measurement
data type associated with a physical sensor value. The actual data units are
determined by examining an object of this type together with the associated EntitySensorDataScale object.
An object of this type SHOULD be defined together with objects of type
EntitySensorDataScale and EntitySensorPrecision. Together, associated
objects of these three types are used to identify the semantics of an object
of type EntitySensorValue. Valid values are:
— Syntax
INTEGER
• other(1)
- a measure other than those listed below
• unknown(2)
- unknown measurement, or arbitrary, relative
numbers
• voltsAC(3)
- electric potential
• voltsDC(4)
- electric potential
• amperes(5)
- electric current
• watts(6)
- power
• hertz(7)
- frequency
• celsius(8)
- temperature
• percentRH(9)
- percent relative humidity
• rpm(10)
- shaft revolutions per minute
• cmm(11)
- cubic meters per minute (airflow)
• truthvalue(12) - value takes: true(1) or false(2)
•
EntitySensorDataScale
- An object using this data type represents a data scaling factor, represented
with an International System of Units (SI) prefix. The actual data units are
determined by examining an object of this type together with the associated EntitySensorDataType object.
An object of this type SHOULD be defined together with objects of type
EntitySensorDataType and EntitySensorPrecision. Together, associated
130
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
objects of these three types are used to identify the semantics of an object
of type EntitySensorValue.
— Syntax
INTEGER
• yocto(1)
- 10^-24
• zepto(2)
- 10^-21
• atto(3)
- 10^-18
• femto(4)
- 10^-15
• pico(5)
- 10^-12
• nano(6)
- 10^-9
• micro(7)
- 10^-6
• milli(8)
- 10^-3
• units(9)
- 10^0
• kilo(10)
- 10^3
• mega(11)
- 10^6
• giga(12)
- 10^9
• tera(13)
- 10^12
• exa(14)
- 10^15
• peta(15)
- 10^18
• zetta(16)
- 10^21
• yotta(17)
- 10^24
•
EntitySensorPrecision
- An object using this data type represents a sensor precision range.
An object of this type SHOULD be defined together with objects of type
EntitySensorDataType and EntitySensorDataScale. Together, associated
objects of these three types are used to identify the semantics of an object
of type EntitySensorValue.
If an object of this type contains a value in the range 1 to 9, it represents
the number of decimal places in the fractional part of an associated EntitySensorValue fixed- point number.
If an object of this type contains a value in the range -8 to -1, it represents
the number of accurate digits in the associated EntitySensorValue fixedpoint number.
The value zero indicates the associated EntitySensorValue object is not a
fixed-point number.
Agent implementors must choose a value for the associated EntitySensorPrecision object so that the precision and accuracy of the associated EntitySensorValue object is correctly indicated.
For example, a physical entity representing a temperature sensor that can
measure 0 degrees to 100 degrees C in 0.1 degree increments, +/- 0.05
degrees, would have an EntitySensorPrecision value of “1,” an EntitySensorDataScale value of units(9), and an EntitySensorValue ranging from
“0” to “1000.” The EntitySensorValue would be interpreted as
“degrees C * 10."
— Syntax
131
Integer32 (-8…9)
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
•
EntitySensorValue
- An object using this data type represents an Entity Sensor value. An object
of this type SHOULD be defined together with objects of type EntitySensorDataType, EntitySensorDataScale and EntitySensorPrecision.
Together, associated objects of those three types are used to identify the
semantics of an object of this data type.
The semantics of an object using this data type are determined by the
value of the associated EntitySensorDataType object.
If the associated EntitySensorDataType object is equal to voltsAC(3),
voltsDC(4), amperes(5), watts(6), hertz(7), celsius(8), or cmm(11), then
an object of this type MUST contain a fixed point number ranging from 999,999,999 to +999,999,999. The value -1000000000 indicates an underflow error. The value +1000000000 indicates an overflow error. The EntitySensorPrecision indicates how many fractional digits are represented in
the associated EntitySensorValue object.
If the associated EntitySensorDataType object is equal to percentRH(9),
then an object of this type MUST contain a number ranging from 0 to 100.
If the associated EntitySensorDataType object is equal to rpm(10), then an
object of this type MUST contain a number ranging from -999,999,999 to
+999,999,999.
If the associated EntitySensorDataType object is equal to truthvalue(12),
then an object of this type MUST contain either the value true(1) or the
value false(2). If the associated EntitySensorDataType object is equal to
other(1) or unknown(2), then an object of this type MUST contain a number ranging from -1000000000 to 1000000000.
— Syntax
•
5.7.3
•
•
•
•
•
EntitySensorStatus
OIDs
iso
org
dod
internet
mgmt
Integer32 (-1000000000…1000000000)
- An object using this data type represents the operational status of a physical sensor.
— Syntax
INTEGER
• ok(1)
- Indicates that the agent can obtain the sensor
value.
• unavailable(2) - Indicates that the agent presently cannot obtain
the sensor value.
• nonoperational(3)- Indicates that the agent believes the sensor is
broken. The sensor could have a hard failure
(disconnected wire), or a soft failure such as
out-of-range, jittery, or wildly fluctuating
readings.
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
132
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
•
•
•
•
5.7.4
mib-2
entitySensorMIB
entitySensorObjects
entitySensorNotifications
-
{ mgmt 1 }
{ mib-2 99 }
{ entitySensorMIB 1 }
{ entitySensorMIB 2 }
1.3.6.1.2.1
1.3.6.1.2.1.99
1.3.6.1.2.1.99.1
1.3.6.1.2.1.99.2
MIB Objects
Table 67: ENTITY-SENSOR_MIB Objects
Object
OID
Syntax
Access
Status
Supported
entPhySensorTable
{ entitySensorObjects 1 }
Sequence of entPhySensorEntry
not-accessible
current
Y
5.7.4.1
entPhySensorTable
This table contains one row per physical sensor represented by an associated row in the entPhysicalTable.
Entries are created in this table by the agent. An entry for each physical sensor SHOULD be created at the same time
as the associated entPhysicalEntry. An entry SHOULD be destroyed if the associated entPhysicalEntry is destroyed.
Valid Object Value(s)
The following sensors are supported:
•
•
•
•
•
•
Fan 1 Speed Sensor
Fan 2 Speed Sensor
Fan 3 Speed Sensor
Fan 4 Speed Sensor1
Intake Temperature Sensor
Internal Temperature Sensor
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
1. The A/C powered chassis has 4 fans; the D/C powered chassis has 3 fans.
133
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
OIDs:
•
•
entPhySensorTable
entPhySensorEntry
- {entitySensorObjects 1 }
- {entPhySensorTable 1 }
1.3.6.1.2.1.99.1.1
1.3.6.1.2.1.99.1.1.1
Table 68: entPhySensorTable
Object
OID
Syntax
Access
Status
Supported
entPhySensorType
{ entPhySensorEntry 1 }
EntitySensorDataType
read-only
current
Y
entPhySensorScale
{ entPhySensorEntry 2 }
EntitySensorDataScale
read-only
current
Y
entPhySensorPrecision
{ entPhySensorEntry 3 }
EntitySensorPrecision
read-only
current
Y
entPhySensorValue
{ entPhySensorEntry 4 }
EntitySensorValue
read-only
current
Y
entPhySensorOperStatus
{ entPhySensorEntry 5 }
EntitySensorStatus
read-only
current
Y
entPhySensorUnitsDisplay
{ entPhySensorEntry 6 }
SnmpAdminString
read-only
current
Y
entPhySensorValueTimeStamp
{ entPhySensorEntry 7 }
TimeStamp
read-only
current
Y
entPhySensorValueUpdateRate
{ entPhySensorEntry 8 }
Unsigned32
read-only
current
Y
5.7.4.1.1
entPhySensorType
The type of data returned by the associated entPhySensorValue object.
This object SHOULD be set by the agent during entry creation, and the value SHOULD NOT change during
operation.
5.7.4.1.2
entPhySensorScale
The exponent to apply to values returned by the associated entPhySensorValue object.
This object SHOULD be set by the agent during entry creation, and the value SHOULD NOT change during
operation.
5.7.4.1.3
entPhySensorPrecision
The number of decimal places of precision in fixed-point sensor values returned by the associated entPhySensorValue
object.
This object SHOULD be set to “0” when the associated entPhySensorType value is not a fixed-point type: for
example, percentRH(9), rpm(10), cmm(11), or truthvalue(12).
This object SHOULD be set by the agent during entry creation, and the value SHOULD NOT change during
operation.
5.7.4.1.4
entPhySensorValue
The most recent measurement obtained by the agent for this sensor.
To correctly interpret the value of this object, the associated entPhySensorType, entPhySensorScale, and
134
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
entPhySensorPrecision objects must also be examined.
5.7.4.1.5
entPhySensorOperStatus
The operational status of the sensor.
5.7.4.1.6
entPhySensorUnitsDisplay
A textual description of the data units that should be used in the display of entPhySensorValue.
5.7.4.1.7
entPhySensorValueTimeStamp
The value of sysUpTime at the time the status and/or value of this sensor was last obtained by the agent.
5.7.4.1.8
entPhySensorValueUpdateRate
An indication of the frequency that the agent updates the associated entPhySensorValue object, representing in
milliseconds.
The value zero indicates:
•
•
•
5.7.5
5.7.5.1
5.7.5.1.1
the sensor value is updated on demand (for example, when polled by the agent for a get-request)
the sensor value is updated when the sensor value changes (event-driven)
the agent does not know the update rate.
Conformance Information
Compliance
entitySensorCompliance
Describes the requirements for conformance to the Entity Sensor MIB module.
The following are mandatory groups:
•
•
MODULE this module
—
entitySensorValueGroup
MODULE ENTITY-MIB
—
entityPhysicalGroup
135
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ENTITY-SENSOR-MIB — RFC 3433
5.7.5.2
Conformance
Table 69: ENITITY-SENSOR-MIB Conformance
Group
Description
Objects
Supported
entitySensorValueGroup
A collection of objects representing physical
entity sensor information.
entPhySensorType
Y
entPhySensorScale
Y
entPhySensorPrecision
Y
entPhySensorValue
Y
entPhySensorOperStatus
Y
entPhySensorUnitsDisplay
Y
entPhySensorValueTimeStamp
Y
entPhySensorValueUpdateRate
Y
136
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
5.8
EtherLike-MIB — RFC 2665
5.8.1
Introduction
This MIB describes objects for managing Ethernet-like interfaces. The RFC used as a reference was dated August
1999. The LAST-UPDATED for the Ethernet-Like-MIB was “9908240400Z.”
5.8.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
etherMIB
etherMIBObjects
dot3
dot3StatsTable
dot3CollTable
dot3Tests
dot3Errors
dot3ControlTable
dot3PauseTable
5.8.3
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ mib-2 35 }
{ etherMIB 1 }
{ transmission 7 }
{ dot3 2 }
{ dot3 5 }
{ dot3 6 }
{ dot3 7 }
{ dot3 9 }
{ dot3 10 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.35
1.3.6.1.2.1.35.1
1.3.6.1.2.1.10.7
1.3.6.1.2.1.10.7.2
1.3.6.1.2.1.10.7.5
1.3.6.1.2.1.10.7.6
1.3.6.1.2.1.10.7.7
1.3.6.1.2.1.10.7.9
1.3.6.1.2.1.10.7.10
The following groups supported in this MIB are as follow:
•
•
•
•
•
•
Ethernet-like Statistics Group
Ethernet-like Collision Statistics Group
Ethernet-like Control Group
Ethernet-like Pause Group
Ethernet-like Test Group
Ethernet-like Errors Group
The table below identifies the objects called out in this MIB. Any table object that has elements that are supported are
indicated by a “Y” in the Supported column.
Table 70: EtherLike-MIB Objects (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot3StatsTable
{ dot3 2 }
Sequence of dot3StatsEntry
not-accessible
current
Y
dot3CollTable
{ dot3 5 }
Sequence of dot3CollEntry
not-accessible
current
N
dot3ControlTable
{ dot3 9 }
Sequence of dot3ControlEntry
not-accessible
current
N
dot3PauseTable
{ dot3 10 }
Sequence of dot3PauseEntry
not-accessible
current
Y
137
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
Table 70: EtherLike-MIB Objects (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot3Tests
{ dot3 6 }
N/Aa
not-accessible
current
N
dot3Errors
{ dot3 7 }
N/Aa
not-accessible
current
N
a. These are simply object grouped under the respective OID.
5.8.3.1
Ethernet-like Statistics Group
This group defines statistics for collection of Ethernet-like interfaces attached to a particular system. The statistics are
arranged in a table object known as dot3StatsTable.
5.8.3.1.1
dot3StatsTable
The dot3Stats table contains Statistics for a collection of Ethernet-like interfaces attached to a particular system.
There is one row in this table for each Ethernet-like interface in the system. This table is a sequence of dot3StatsEntry
object type.
The dot2StatsEntry object is an entry containing statistics for a particular interface to an Ethernet-like medium.
Index(es):
•
dot3StatsIndex
OIDs:
•
•
dot3StatsTable
dot3StatsEntry
- { dot3 2 }
- { dot3StatsTable 1 }
1.3.6.1.2.1.10.7.2
1.3.6.1.2.1.10.7.2.1
Table 71: dot3StatsTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot3StatsIndex
{ dot3StatsEntry 1 }
InterfaceIndex
read-only
current
Y
dot3StatsAlignmentErrors
{ dot3StatsEntry 2 }
Counter32
read-only
current
Y
dot3StatsFCSErrors
{ dot3StatsEntry 3 }
Counter32
read-only
current
Y
dot3StatsSingleCollisionFrames
{ dot3StatsEntry 4 }
Counter32
read-only
current
Y
dot3StatsMultipleCollisionsFrames
{ dot3StatsEntry 5 }
Counter32
read-only
current
Y
dot3StatsSQETestErrors
{ dot3StatsEntry 6 }
Counter32
read-only
current
N
dot3StatsDeferredTransmissions
{ dot3StatsEntry 7 }
Counter32
read-only
current
Y
dot3StatsLateCollisions
{ dot3StatsEntry 8 }
Counter32
read-only
current
Y
dot3StatsExcessiveCollisions
{ dot3StatsEntry 9 }
Counter32
read-only
current
Y
dot3StatsInternalMacTransmitErrors
{ dot3StatsEntry 10 }
Counter32
read-only
current
N
138
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
Table 71: dot3StatsTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot3StatsCarrierSenseErrors
{ dot3StatsEntry 11 }
Counter32
read-only
current
N
Counter32
read-only
current
Y
{ dot3StatsEntry 12 }a
dot3StatsFrameTooLongs
{ dot3StatsEntry 13 }
{ dot3StatsEntry 14 }a
{ dot3StatsEntry 15 }a
dot3StatsInternalMacReceiveErrors
{ dot3StatsEntry 16 }
Counter32
read-only
current
N
dot3StatsEtherChipSet
{ dot3StatsEntry 17 }
OBJECT IDENTIFIER
read-only
deprecated
N
dot3StatsSymbolErrors
{ dot3StatsEntry 18 }
Counter32
read-only
current
N
dot3StatsDuplexStatus
{ dot3StatsEntry 19 }
INTEGER
unknown(1)
halfDuplex(2)
fullDeplex(3)
read-only
current
Y
a. This OID is not used.
5.8.3.1.1.1
dot3StatsIndex
An index value that uniquely identifies an interface to an Ethernet-like medium. The interface identified by a
particular value of this index is the same interface as identified by the same value of ifIndex.
5.8.3.1.1.2
dot3StatsAlignmentErrors
A count of frames received on a particular interface that are not an integral number of octets in length and do not pass
the FCS check.
The count represented by an instance of this object is incremented when the alignmentError status is returned by the
MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are,
according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status
presented to the LLC.
This counter does not increment for 8-bit wide group encoding schemes. Discontinuities in the value of this counter
can occur at re-initialization of the management system, and at other times as indicated by the value of
ifCounterDiscontinuityTime.
5.8.3.1.1.3
dot3StatsFCSErrors
A count of frames received on a particular interface that are an integral number of octets in length but do not pass the
FCS check. This count does not include frames received with frame-too-long or frame-too-short error.
The count represented by an instance of this object is incremented when the frameCheckError status is returned by
the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are,
according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status
presented to the LLC.
139
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
Note: Coding errors detected by the physical layer for speeds above 10 Mbps will cause the frame to fail the FCS
check. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at
other times as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.4
dot3StatsSingleCollisionFrames
A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one
collision.
A frame that is counted by an instance of this object is also counted by the corresponding instance of either the
ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the
dot3StatsMultipleCollisionFrames object.
This counter does not increment when the interface is operating in full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.5
dot3StatsMultipleCollisionFrames
A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than
one collision.
A frame that is counted by an instance of this object is also counted by the corresponding instance of either the
ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the
dot3StatsSingleCollisionFrames object.
This counter does not increment when the interface is operating in full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.6
dot3StatsSQETestErrors
This object is not supported.
A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. The
SQE TEST ERROR is set in accordance with the rules for verification of the SQE detection mechanism in the PLS
Carrier Sense Function as described in IEEE Std. 802.3, 1998 Edition, section 7.2.4.6.
This counter does not increment on interfaces operating at speeds greater than 10 Mbps, or on interfaces operating in
full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.7
dot3StatsDeferredTransmissions
A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is
busy. The count represented by an instance of this object does not include frames involved in collisions.
This counter does not increment when the interface is operating in full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
140
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
5.8.3.1.1.8
dot3StatsLateCollisions
The number of times that a collision is detected on a particular interface later than one slotTime into the transmission
of a packet.
A (late) collision included in a count represented by an instance of this object is also considered as a (generic)
collision for purposes of other collision-related statistics.
This counter does not increment when the interface is operating in full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.9
dot3StatsExcessiveCollisions
A count of frames for which transmission on a particular interface fails due to excessive collisions.
This counter does not increment when the interface is operating in full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.10
dot3StatsInternalMacTransmitErrors
This object is not supported.
A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit
error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either
the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors
object.
The precise meaning of the count represented by an instance of this object is implementation- specific. In particular,
an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise
counted.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.11
dot3StatsCarrierSenseErrors
This object is not supported.
The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame
on a particular interface.
The count represented by an instance of this object is incremented at most once per transmission attempt, even if the
carrier sense condition fluctuates during a transmission attempt.
This counter does not increment when the interface is operating in full-duplex mode.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.12
dot3StatsFrameTooLongs
A count of frames received on a particular interface that exceed the maximum permitted frame size.
The count represented by an instance of this object is incremented when the frameTooLong status is returned by the
MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are,
141
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status
presented to the LLC.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.13
dot3StatsInternalMacReceiveErrors
This object is not supported.
A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A
frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the
dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors object.
The precise meaning of the count represented by an instance of this object is implementation specific. In particular, an
instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.14
dot3StatsEtherChipSet
THIS OBJECT IS DEPRECATED
This object is not supported.
This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like
interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of
which chip to identify via this object. The implementor should identify the chip which is usually called the Medium
Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually
gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the
statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip.
5.8.3.1.1.15
dot3StatsSymbolErrors
This object is not supported.
For an interface operating at 100 Mbps, the number of times there was an invalid data symbol when a valid carrier
was present.
For an interface operating in half-duplex mode at 1000 Mbps, the number of times the receiving media is non-idle (a
carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one
occurrence of an event that causes the PHY to indicate “Data reception error” or “carrier extend error” on the GMII.
For an interface operating in full-duplex mode at 1000 Mbps, the number of times the receiving media is non-idle a
carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one
occurrence of an event that causes the PHY to indicate “Data reception error” on the GMII.
The count represented by an instance of this object is incremented at most once per carrier event, even if multiple
symbol errors occur during the carrier event. This count does not increment if a collision is present.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.1.1.16
dot3StatsDuplexStatus
The current mode of operation of the MAC entity. “unknown” indicates that the current duplex mode could not be
142
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
determined.
Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support
autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType.
When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In
either case, the currently operating duplex mode is reflected both in this object and in ifMauType.
Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged.
However, in this instance, it allows a management application to determine the duplex status of an interface without
having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
5.8.3.2
Ethernet-like Collision Statistics Group
This group, which consists of the dot3CollTable, is optional and is only appropriate for all systems which have the
necessary metering.
This group is not supported. The RFC states that it is no loner in use.
OIDs:
•
•
dot3CollTable
dot3CollEntry
- { dot3 5 }
- { dot3CollTable 1 }
1.3.6.1.2.1.10.7.5
1.3.6.1.2.1.10.7.5.1
Table 72: dot3CollTable
Object
OID
Syntax
Access
Status
Supported
{ dot3CollEntry 1 }a
dot3CollCount
{ dot3CollEntry 2 }
INTEGER(1…16)
not-accessible
current
N
dot3CollFrequencies
{ dot3CollEntry 3 }
Counter32
read-only
current
N
a. This OID is no longer in use.
5.8.3.3
Ethernet-like Control Group
This group defines objects for 802.3 control functions.
5.8.3.3.1
dot3ControlTable
These functions are arranged in a table object known as dot3ControlTable. There is one row in this table for each
Ethernet-like interface in the system. This table is a sequence of dot1ControlEntry type object. The index for this
table is the dot3StatsIndex described in Section 5.8.3.1.1.1, Page 139.
The dot3ControlEntry object is an entry in the table containing information about the MAC Control sublayer on a
single Ethernet-like interface.
Index(es):
•
dot3StatsIndex (Section 5.8.3.1.1.1, Page 139)
143
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
OIDs:
•
•
dot3ControlTable
dot3ControlEntry
- { dot3 9 }
- { dot3ControlTable 1 }
1.3.6.1.2.1.10.7.9
1.3.6.1.2.1.10.7.9.1
,
Table 73: dot3ControlTable
Object
OID
Syntax
Access
Status
Supported
dot3ControlFunctionsSupported
{ dot3ControlEntry 1 }
BITS
pause(0)
read-only
current
N
dot3ControlInUnknownOpcodes
{ dot3ControlEntry 2 }
Counter32
read-only
current
N
5.8.3.3.1.1
dot3ControlFunctions
A list of the possible MAC Control functions implemented for this interface.
Pause is supported so the pause bit will be set.
5.8.3.3.1.2
dot3ControlInUnknownOpcodes
A count of MAC Control frames received on this interface that contain an opcode that is not supported by this device.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.8.3.4
Ethernet-like Pause Group
This group defines objects containing information about MAC Control PAUSE functions. The information is
arranged in a table object known as dot3PauseTable.
5.8.3.4.1
dot3PauseTable
The dot3PauseTable table of descriptive and status information about the MAC Control PAUSE function on the netlike interfaces attached to a particular system. There is one row in this table for each Ethernet-like interface in the
system which supports the MAC Control PAUSE function (that is, the “pause” bit in the corresponding instance of
dot3ControlFunctionsSupported is set). If some, but not all, of the Ethernet-like interfaces in the system implement
the MAC Control PAUSE function (for example, if some interfaces only support half-duplex), there will be fewer
rows in this table than in the dot3StatsTable. This table is a sequence of dot3PauseEntry type object.
The dot3PauseEntry object defines an entry in the table, containing information about the MAC Control PAUSE
function on a single Ethernet-like interface.
Index(es):
•
dot3StatsIndex (Section 5.8.3.1.1.1, Page 139)
OIDs:
•
•
dot3PauseTable
dot3PauseEntry
- { dot3 10 }
- { dot3PauseTable 1 }
144
1.3.6.1.2.1.10.7.10
1.3.6.1.2.1.10.7.10.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
Table 74: dot3PauseTable
Object
OID
Syntax
Access
Status
Supported
dot3PauseAdminMode
{ dot3PauseEntry 1 }
INTEGER
disabled(1)
enabledXmit(2)
enabledRcv(3)
enabledXmitAndRcv(4)
read-write
current
Y
dot3PauseOperMode
{ dot3PauseEntry 2 }
INTEGER
disabled(1)
enabledXmit(2)
enabledRcv(3)
enabledXmitAndRcv(4)
read-only
current
Y
dot3InPauseFrames
{ dot3PauseEntry 3 }
Counter32
read-only
current
N
dot3OutPauseFrames
{ dot3PauseEntry 4 }
Counter32
read-only
current
N
5.8.3.4.1.1
dot3PauseAdminMode
This object is used to configure the default administrative PAUSE mode for this interface.
This object represents the administratively-configured PAUSE mode for this interface. If auto-negotiation is not
enabled or is not implemented for the active MAU attached to this interface, the value of this object determines the
operational PAUSE mode of the interface whenever it is operating in full-duplex mode. In this case, a set to this object
will force the interface into the specified mode.
If auto-negotiation is implemented and enabled for the MAU attached to this interface, the PAUSE mode for this
interface is determined by auto-negotiation, and the value of this object denotes the mode to which the interface will
automatically revert if/when auto-negotiation is later disabled. Note that when auto-negotiation is running,
administrative control of the PAUSE mode may be accomplished using the ifMauAutoNegCapAdvertisedBits object
in the MAU-MIB.
Note that the value of this object is ignored when the interface is not operating in full-duplex mode.
Valid Object Value(s)
•
•
disabled(1)
enableXmitAndRcv(4)
An attempt to set this object to “enabledXmit(2)” or “enabledRcv(3)” will fail on interfaces that do not support
operation at greater than 100 Mbps.
5.8.3.4.1.2
dot3PauseOperMode
This object reflects the PAUSE mode currently in use on this interface, as determined by either (1) the result of the
auto-negotiation function or (2) if auto-negotiation is not enabled or is not implemented for the active MAU attached
to this interface, by the value of dot3PauseAdminMode. Interfaces operating at 100 Mbps or less will never return
145
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
“enabledXmit(2)” or “enabledRcv(3).” Interfaces operating in half-duplex mode will always return “disabled(1).”
Interfaces on which auto-negotiation is enabled but not yet completed should return the value “disabled(1).”
Valid Object Value(s)
•
•
disabled(1)
enabledXmitAndRcv(4)
5.8.3.4.1.3
dot3InPauseFrames
A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.
This counter does not increment when the interface is operating in half-duplex mode. Discontinuities in the value of
this counter can occur at re-initialization of the management system, and at other times as indicated by the value of
ifCounterDiscontinuityTime.
5.8.3.4.1.4
dot3OutPauseFrames
A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation.
This counter does not increment when the interface is operating in half-duplex mode. Discontinuities in the value of
this counter can occur at re-initialization of the management system, and at other times as indicated by the value of
ifCounterDiscontinuityTime.
5.8.3.5
Ethernet-like Test Group
This group will not be supported. No Time-Domain Reflectometry (TDR) tests or Loopback tests are supported for
Ethernet in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM.
OIDs:
•
dot3Tests
- { dot3 6 }
1.3.6.1.2.1.10.7.6
,
Table 75: dot3Tests
Object
OID
Syntax
Access
Status
Supported
dot3TestTdr
{ dot3Tests 1 }
unspecified
unspecified
current
N
dot3TestLoopBack
{ dot3Tests 2 }
unspecified
unspecified
current
N
5.8.3.6
Ethernet-like Errors Group
This group will not be supported due to lack of support for the Ethernet-like Test Group.
OIDs:
•
dot3Errors
- { dot3 7 }
1.3.6.1.2.1.10.7.7
146
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
EtherLike-MIB — RFC2665
Table 76: dot3Tests
Object
OID
Syntax
Access
Status
Supported
dot3ErrInitError
{ dot3Errors 1 }
unspecified
unspecified
current
N
dot3ErrorLoopbackError
{ dot3Errors 2 }
unspecified
unspecified
current
N
147
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
5.9
MAU-MIB — RFC2668
5.9.1
Introduction
This MIB describes objects for managing IEEE 802.3 Medium Attachment Units (MAUs). The RFC used as a
reference was dated August 1999. The LAST-UPDATED for the MAU-MIB was “9908240400Z.”
5.9.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
snmpDot3MauMgt
snmpDot3MauTraps
dot3RpMauBasicGroup
dot3IfMauBasicGroup
dot3BroadMauBasicGroup
dot3MauType
dot3IfMauAutoNegGroup
mauMod
5.9.3
Textual Conventions
•
JackType
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ mib-2 26 }
{ snmpDot3MauMgt 0 }
{ snmpDot3MauMgt 1 }
{ snmpDot3MauMgt 2 }
{ snmpDot3MauMgt 3 }
{ snmpDot3MauMgt 4 }
{ snmpDot3MauMgt 5 }
{ snmpDot3MauMgt 6 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.2.6.1.2.1.10
1.2.6.1.2.1.26
1.2.6.1.2.1.26.0
1.2.6.1.2.1.26.1
1.2.6.1.2.1.26.2
1.2.6.1.2.1.26.3
1.2.6.1.2.1.26.4
1.2.6.1.2.1.26.5
1.2.6.1.2.1.26.6
- Common enumeration values for repeater and interface MAU jack types.
— Syntax
INTEGER
• other(1)
• rj45(2),
• rj45S(3)
- rj45 shielded
• db9(4)
• bnc(5)
• fAUI(6)
- female aui
• mAUI(7)
- male aui
• fiberSC(8)
• fiberMIC(9)
• fiberST(10)
• telco(11),
• mtrj(12)
- fiber MT-RJ
• hssdc(13)
- fiber channel style-2
The following are object identities for MAU types. See rpMauType and ifMauType for usage.
•
•
•
•
•
dot3MauTypeAUI
dot3MauType10Base5
dot3MauTypeFoirl
dot3MauType10Base2
dot3MauType10BaseT
-
{ dot3MauType 1 }
{ dot3MauType 2 }
{ dot3MauType 3 }
{ dot3MauType 4 }
{ dot3MauType 5 }
148
-
no internal MAU, view from AUI
thick coax MAU (per 802.3 section 8)
FOIRL MAU (per 802.3 section 9.9)
thin coax MAU (per 802.3 section 10)
UTP MAU (per 802.3 section 14)
Note that it is strongly recommended that
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
•
•
dot3MauType10BaseFP
dot3MauType10BaseFB
dot3MauType10BaseFL
- { dot3MauType 6 }
- { dot3MauType 7 }
- { dot3MauType 8 }
-
•
dot3MauType10Broad36
- { dot3MauType 9 }
-
•
dot3MauType10BaseTHD
- { dot3MauType 10 } -
•
dot3MauType10BaseTFD
- { dot3MauType 11 } -
•
dot3MauType10BaseFLHD
- { dot3MauType 12 } -
•
dot3MauType10BaseFLFD
- { dot3MauType 13 } -
•
•
dot3MauType100BaseT4
dot3MauType100BaseTXHD
- { dot3MauType 14 } - { dot3MauType 15 } -
•
dot3MauType100BaseTXFD
- { dot3MauType 16 } -
•
dot3MauType100BaseFXHD
- { dot3MauType 17 } -
•
dot3MauType100BaseFXFD
- { dot3MauType 18 } -
•
dot3MauType100BaseT2HD
- { dot3MauType 19 } -
•
dot3MauType100BaseT2FD
- { dot3MauType 20 } -
•
dot3MauType1000BaseXHD
- { dot3MauType 21 } -
•
dot3MauType1000BaseXFD
- { dot3MauType 22 } -
•
dot3MauType1000BaseLXHD
- { dot3MauType 23 } -
•
dot3MauType1000BaseLXFD
- { dot3MauType 24 } -
149
agents return either dot3MauType10BaseTHD
or dot3MauType10BaseTFD if the duplex
mode is known. However, management applications should e prepared to receive this MAU
type value from older agent implementations.
passive fiber MAU (per 802.3 section 16)
sync fiber MAU (per 802.3 section 17)
async fiber MAU (per 802.3 section 18)
Note that it is strongly recommended that
agents return either
dot3MauType10BaseFLHD or
dot3MauType10BaseFLFD if the duplex mode
is known. However, management applications
should be prepared to receive this MAU type
value from older agent implementations.
broadband DTE MAU (per 802.3 section 11)
Note that 10BROAD36 MAUs can be attached
to interfaces but not to repeaters.
UTP MAU (per 802.3 section 14), half duplex
mode
UTP MAU (per 802.3 section 14), full duplex
mode
async fiber MAU (per 802.3 section 18), half
duplex mode
async fiber MAU (per 802.3 section 18), full
duplex mode
4 pair categ. 3 UTP (per 802.3 section 23)
2 pair categ. 5 UTP (per 802.3 section 25), half
duplex mode
2 pair categ. 5 UTP (per 802.3 section 25),full
duplex mode
X fiber over PMT (per 802.3 section 26), half
duplex mode
X fiber over PMT (per 802.3 section 26), full
duplex mode
2 pair categ. 3 UTP (per 802.3 section 32), half
duplex mode
2 pair categ. 3 UTP (per 802.3 section 32), full
duplex mode
PCS/PMA (per 802.3 section 36), unknown
PMD, half duplex mode
PCS/PMA (per 802.3 section 36), unknown
PMD, full duplex mode
Fiber over long-wavelength laser (per 802.3
section 38), half duplex mode
Fiber over long-wavelength laser (per 802.3
section 38), full duplex mode
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
dot3MauType1000BaseSXHD
•
dot3MauType1000BaseSXFD
•
dot3MauType1000BaseCXHD
•
dot3MauType1000BaseCXFD
•
dot3MauType1000BaseTHD
•
dot3MauType1000BaseTFD
5.9.4
- { dot3MauType 25 } - Fiber over short-wavelength laser (per 802.3
section 38), half duplex mode
- { dot3MauType 26 } - Fiber over short-wavelength laser (per 802.3
section 38), full duplex mode
- { dot3MauType 27 } - Copper over 150-Ohm balanced cable (per
802.3 section 39), half duplex mode
- { dot3MauType 28 } - Copper over 150-Ohm balanced cable (per
802.3 section 39), full duplex mode
- { dot3MauType 29 } - Four-pair Category 5 UTP (per 802.3 section
40), half duplex mode
- { dot3MauType 30 } - Four-pair Category 5 UTP (per 802.3 section
40), full duplex mode
MIB Objects
The table below identifies the objects called out in this MIB. Any table object that has elements that are supported are
indicated by a “Y” in the Supported column.
Table 77: MAU-MIB Objects
Object
OID
Syntax
Access
Status
Supported
rpMauTable
{ dot3RpMauBasicGroup 1 }
Sequence of rpMauEntry
not-accessible
current
N
rpJackTable
{ dot3RpMauBasicGroup 2 }
Sequence of rpJackEntry
not-accessible
current
N
ifMauTable
{ dot3IfMauBasicGrup 1 }
Sequence of ifMauEntry
not-accessible
current
Y
ifJackTable
{ dot3IfMauBasicGrup 2 }
Sequence of ifJackEntry
not-accessible
current
Y
ifMauAutoNegTable
{ dot3IfMauAutoNegGroup 1 }
Sequence of
ifMauAutoNegEntry
not-accessible
current
Y
broadMauBasicTable
{ dot3BroadMauBasicGroup 1 }
Sequence of
broadMauBasicEntry
not-accessible
deprecated
N
5.9.4.1
dot3RpMauBasicGroup
No objects in this group are supported since the BitStorm 2600 and GranDSLAM 4200 IP DSLAM do not act like a
repeater.
5.9.4.1.1
rpMauTable
Table of descriptive and status information about the MAU(s) attached to the ports of a repeater. The table is a
sequence of rpMauEntry where an entry contains information about a single MAU.
This table will not be supported since the BitStorm 2600 and GranDSLAM 4200 IP DSLAM do not act like a
repeater.
Index(es):
•
rpMauGroupIndex
150
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
•
rpMauPortIndex
rpMauIndex
OIDs:
•
•
rpMauTable
rpMauEntry
- { dot3RpMauBasicGroup 1 }
- { rpMauTable 1 }
1.2.6.1.2.1.26.1.1
1.2.6.1.2.1.26.1.1.1
Table 78: rpMauTable
Object
OID
Syntax
Access
Status
Supported
rpMauGroupIndex
{ rpMauEntry 1 }
Integer32 (1…2147483647)
read-only
current
N
rpMauPortIndex
{ rpMauEntry 2 }
Integer32 (1…2147483647)
read-only
current
N
rpMauIndex
{ rpMauEntry 3 }
Integer32(1…2147483647)
read-only
current
N
rpMauType
{ rpMauEntry 4 }
OBJECT IDENTIFIER
read-only
current
N
rpMauStatus
{ rpMauEntry 5 }
INTEGER
other(1)
unknown(2)
operational(3)
standby(4)
shutdown(5)
reset(6)
read-write
current
N
rpMauMediaAvailable
{ rpMauEntry 6 }
INTEGER
other(1)
unknown(2)
available(3)
notAvailable(4)
remoteFault(5)
invalidSignal(6)
remoteJabber(7)
remoteLinkLoss(8)
remoteTest(9)
offline(10)
autoNegError(11)
read-only
current
N
rpMauMediaAvailableStateExits
{ rpMauEntry 7 }
Counter32
read-only
current
N
rpMauJabberState
{ rpMauEntry 8 }
INTEGER
other(1)
unknown(2)
noJabber(3)
jabbering(4)
read-only
current
N
rpMauJabberingStateEnters
{ rpMauEntry 9 }
Counter32
read-only
current
N
rpMauFalseCarriers
{ rpMauEntry 10 }
Counter32
read-only
current
N
151
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
5.9.4.1.1.1
rpMauGroupIndex
This variable uniquely identifies the group containing the port to which the MAU described by this entry is
connected.
Note: In practice, a group will generally be a field-replaceable unit (such as a module, card, or board) that can fit in
the physical system enclosure, and the group number will correspond to a number marked on the physical enclosure.
The group denoted by a particular value of this object is the same as the group denoted by the same value of
rptrGroupIndex.
5.9.4.1.1.2
rpMauPortIndex
This variable uniquely identifies the repeater port within group rpMauGroupIndex to which the MAU described by
this entry is connected.
5.9.4.1.1.3
rpMauIndex
This variable uniquely identifies the MAU described by this entry from among other MAUs connected to the same
port (rpMauPortIndex).
5.9.4.1.1.4
rpMauType
This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT
IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier
unknownMauType OBJECT IDENTIFIER = { 0 0 } is returned. Note that unknownMauType is a syntactically valid
object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize
this value.
5.9.4.1.1.5
rpMauStatus
The current state of the MAU. This object MAY be implemented as a read-only object by those agents and MAUs that
do not implement software control of the MAU state. Some agents may not support setting the value of this object to
some of the enumerated values.
•
•
•
•
•
•
other(1)
- The MAU is in a state other than one of the states 2 through 6 below
unknown(2) - The MAU's true state is unknown; for example, when it is being initialized
operational(3) - The MAU is fully functional, operates, and passes signals to its attached DTE or repeater
port in accordance to its specification
standby(4)
- This state forces DI and CI to idle and the media transmitter to idle or fault, if supported.
shutdown(5) - This state assumes the same condition on DI, CI, and the media transmitter as though it
were powered down or not connected. The MAU MAY return other(1) value for the
rpMauJabberState and rpMauMediaAvailable objects when it is in this state. For an AUI,
this state will remove power from the AUI
reset(6)
- This state resets the MAU in the same manner as a power-off, power-on cycle of at least
one-half second would. The agent is not required to return the value reset (6).
Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective
state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state.
5.9.4.1.1.6
rpMauMediaAvailable
If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link test fail state/low
light function. For an AUI or a coax (including broadband) MAU this indicates whether or not loopback is detected
on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2,
152
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
10BROAD36, and 10BASE-FP.
•
•
other(1)
unknown(2)
•
•
•
available(3)
notAvailable(4)
remoteFault(5)
•
invalidSignal(6)
•
•
•
•
•
remoteJabber(7)
remoteLinkLoss(8)
remoteTest(9)
offline(10)
autoNegError(11)
- Returned if the mediaAvailable state is not one of 2 through 11
- Returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this attribute is unknown for
AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback is tested on each
transmission during which no collision is detected. If DI is receiving input when
DO returns to IDL after a transmission and there has been no collision during the
transmission, then loopback will be detected. The value of this attribute will only
change during non-collided transmissions for AUI, coax, and 10BASE-FP MAUs.
- Indicates that the link, light, or loopback is normal.
- Indicates link loss, low light, or no loopback.
- Indicates that a fault has been detected at the remote end of the link. This value
applies to 10BASE-FB, 100BASE-T4 Far End Fault Indication and non-specified
remote faults from a system running auto-negotiation.
- Indicates that an invalid signal has been received from the other end of the link.
InvalidSignal(6) applies only to MAUs of type 10BASE-FB.
- See description below.
- See description below.
- See description below.
- See description below.
- See description below.
For 100Mbps and 1000Mbps MAUs, the enumerations match the states within the respective link integrity state
diagrams, fig 32-16, 23-12 and 24-15 of sections 32, 23 and 24 of the IEEE Std 803.2, 1998 Edition specification.
Any MAU which implements management of auto-negotiation will map remote fault indication to remote fault.
Where an IEEE Std 802.3u-1995 clause 22 MII is present, a logic one in the remote fault bit (reference section
22.2.4.2.8 of that document) maps to the value remoteFault(5), and a logic zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value notAvailable(4). The value notAvailable(4) takes precedence over the
value remoteFault(5).
Any MAU that implements management of clause 37 Auto-Negotiation will map the received Remote Fault (RF1 and
RF2) bit values for Offline to offline(10), Link Failure to remoteFault(5) and Auto-Negotiation Error to
autoNegError(11).
5.9.4.1.1.7
rpMauMediaAvailableStateExits
A count of the number of times that rpMauMediaAvailable for this MAU instance leaves the state available(3).
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of rptrMonitorPortLastChange.
5.9.4.1.1.8
rpMauJabberState
• other(1)
- The value other(1) is returned if the jabber state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
• unknown(2) - The value unknown(2) is returned when the MAU's true state is unknown; for example,
when it is being initialized.
• noJabber(3) - If the MAU is not jabbering the agent returns noJabber(3). This is the “normal” state.
• jabbering(4) - If the MAU is in jabber state the agent returns the jabbering(4) value.
153
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
5.9.4.1.1.9
rpMauJabberingStateEnters
A count of the number of times that mauJabberState for this MAU instance enters the state jabbering(4). For MAUs
of type dot3MauTypeAUI, dot3MauType100BaseT4, dot3MauType100BaseTX, dot3MauType100BaseFX and all
1000Mbps types, this counter will always indicate zero.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of rptrMonitorPortLastChange.
5.9.4.1.1.10
rpMauFalseCarriers
A count of the number of false carrier events during IDLE in 100BASE-X links. This counter does not increment at
the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100 ms until the next
carrier event.
This counter increments only for MAUs of type dot3MauType100BaseT4, dot3MauType100BaseTX, and
dot3MauType100BaseFX and all 1000Mbps types. For all other MAU types, this counter will always indicate zero.
The approximate minimum time for rollover of this counter is 7.4 hours.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of rptrMonitorPortLastChange.
5.9.4.1.2
rpJackTable
The rpJackTable applies to MAUs attached to repeaters which have one or more external jacks (connectors).
Information about the external jacks attached to MAUs attached to the ports of a repeater. This table is a sequence of
rpJackEntry where an entry contains information about a particular jack.
This table will not be supported since the BitStorm 2600 and GranDSLAM 4200 IP DSLAM do not act like a
repeater.
Index(es):
•
•
•
•
rpMauGroupIndex (Section 5.9.4.1.1.1, Page 152)
rpMauPortIndex (Section 5.9.4.1.1.2, Page 152)
rpMauType (Section 5.9.4.1.1.4, Page 152)
rpJackIndex
OIDs:
•
•
rpJackTable
rpJackEntry
- { dot3RpMauBasicGroup 2 }
- { rpJackTable 1 }
1.2.6.1.2.1.26.1.2
1.2.6.1.2.1.26.1.2.1
Table 79: rpJackTable
Object
OID
Syntax
Access
Status
Supported
rpJackIndex
{ rpJackEntry 1 }
Integer32 (1…2147483647)
read-only
current
N
rpJackType
{ rpJackEntry 2 }
JackType
read-only
current
N
154
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
5.9.4.1.2.1
rpJackIndex
This variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU
(rpMauIndex).
5.9.4.1.2.2
rpJackType
The jack connector type, as it appears on the outside of the system.
5.9.4.2
dot3IfMauBasicGroup
5.9.4.2.1
ifMauTable
Table of descriptive and status information about MAU(s) attached to an interface.
This table is a sequence of IfMauEntry which consists of information about a single MAU.
Index(es):
•
•
ifMauIfIndex
ifMauIndex
OIDs:
•
•
ifMauTable
ifMauEntry
- {dot3IfMauBasicGroup 1 }
- {ifMauTable 1 }
1.2.6.1.2.1.26.2.1
1.2.6.1.2.1.26.2.1.1
Table 80: ifMauTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
ifMauIfIndex
{ ifMauEntry 1 }
Integer32 (1…2147483647)
read-only
current
Y
ifMauIndex
{ ifMauEntry 2 }
Integer32 (1…2147483647)
read-only
current
Y
ifMauType
{ ifMauEntry 3 }
OBJECT IDENTIFIER
read-only
current
Y
ifMauStatus
{ ifMauEntry 4 }
INTEGER
other (1)
unknown (2)
operational (3)
standby (4)
shutdown (5)
reset (6)
read-onlya
current
N
ifMauMediaAvailable
{ ifMauEntry 5 }
INTEGER
other (1)
unknown (2)
available (3)
notAvailable (4)
remoteFault(5)
invalidSignal(6)
remoteJabber(7)
remoteLinkLoss(8)
remoteTest(9)
offline(10)
autoNegError(11)
read-only
current
N
155
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Table 80: ifMauTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
ifMauMediaAvailableStateExits
{ ifMauEntry 6 }
Counter32
read-only
current
N
ifMauJabberState
{ ifMauEntry 7 }
INTEGER
other(1)
unknown(2)
noJabber(3)
jabbering(4)
read-only
current
N
ifMauJabberingStateEnters
{ ifMauEntry 8 }
Counter32
read-only
current
N
ifMauFalseCarriers
{ ifMauEntry 9 }
Counter32
read-only
current
N
ifMauTypeList
{ ifMauEntry 10 }
Integer32
read-only
deprecated
N
ifMauDefaultType
{ ifMauEntry 11 }
OBJECT IDENTIFIER
read-write
current
Y
ifMauAutoNegSupported
{ ifMauEntry 12 }
TruthValue
read-only
current
Y
ifMauTypeListBits
{ ifMauEntry 13 }
BITS
bOther(0)
bAUI(1)
b10base5(2)
bFoirl(3)
b10base2(4)
b10baseT(5)
b10baseFP(6)
b10baseFB(7)
b10baseFL(8)
b10broad36(9)
b10baseTHD(10)
b10baseTFD(11)
b10baseFLHD(12)
b10baseFLFD(13)
b100baseT4(14)
b100baseTXHD(15)
b100baseTXFD(16)
b100baseFXHD(17)
b100baseFXFD(18)
b100baseT2HD(19)
b100baseT2FD(20)
b1000baseXHD(21)
b1000baseXFD(22)
b1000baseLXHD(23)
b1000baseLXFD(24)
b1000baseSXHD(25)
b1000baseSXFD(26)
b1000baseCXHD(27)
b1000baseCXFD(28)
b1000baseTHD(29)
b1000baseTFD(30)
read-only
current
N
a. Software control of the MAU is not required for the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. As a result, this object is
implemented as read-only.
156
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
5.9.4.2.1.1
ifMauIfIndex
This variable uniquely identifies the interface to which the MAU described by this entry is connected.
Valid Object Value(s)
This object will return the same value as the ifIndex associated with a particular Ethernet interface.
5.9.4.2.1.2
ifMauIndex
This variable uniquely identifies the MAU described by this entry from among other MAUs connected to the same
interface (ifMauIfIndex).
Valid Object Value(s)
The concept of multiple MAUs on the same interface does not apply to the BitStorm 2600 and GranDSLAM 4200 IP
DSLAM, so this value will always be “1.”
5.9.4.2.1.3
ifMauType
This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT
IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier
unknownMauType OBJECT IDENTIFIER = { 0 0 } is returned. Note that unknownMauType is a syntactically valid
object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize
this value.
This object represents the operational type of the MAU, as determined by either (1) the result of the auto-negotiation
function or (2) if auto-negotiation is not enabled or is not implemented for this MAU, by the value of the object
ifMauDefaultType. In case (2), a set to the object ifMauDefaultType will force the MAU into the new operating
mode.
Valid Object Value(s)
The table below describes the MAU types and there associations with the interfaces applicable to the BitStorm 2600
and GranDSLAM 4200 IP DSLAM.
Table 81: ifMauType (1 of 2)
Product Interface
Interface Type
10BASE-T
Ethernet Port 1
100BASE-TX
157
Duplex Mode
MAU Type
Half
dot3MauType10BaseTHD
Full
dot3MauType10BaseTFD
Half
dot3MauType100BaseTXHD
Full
dot3MauType100BaseTXFD
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Table 81: ifMauType (2 of 2)
Product Interface
Interface Type
10BASE-T
Ethernet Port 2
100BASE-TX
10BASE-T
100BASE-TX
Ethernet Port 3
1000BASE-T
1000BASE-Xa
Duplex Mode
MAU Type
Half
dot3MauType10BaseTHD
Full
dot3MauType10BaseTFD
Half
dot3MauType100BaseTXHD
Full
dot3MauType100BaseTXFD
Half
dot3MauType10BaseTHD
Full
dot3MauType10BaseTFD
Half
dot3MauType100BaseTXHD
Full
dot3MauType100BaseTXFD
Half
dot3MauType1000BaseTHD
Full
dot3MauType1000BaseTFD
Half
dot3MauType1000BaseXHD
Full
dot3MauType1000BaseXFD
a. When a Small Form-factor Pluggable (SFP) module is installed, the MAU Type
dot3MauType1000BaseX… identifies the SFP module.
5.9.4.2.1.4
ifMauStatus
This object is not supported.
The current state of the MAU. This object MAY be implemented as a read-only object by those agents and MAUs that
do not implement software control of the MAU state. Some agents may not support setting the value of this object to
some of the enumerated values. The following are values for this object:
•
•
•
•
•
other(1)
- The value other(1) is returned if the MAU is in a state other than one of the states 2
through 6.
unknown(2) - The value unknown(2) is returned when the MAU's true state is unknown; for example,
when it is being initialized.
operational(3) - A MAU in the operational(3) state is fully functional, operates, and passes signals to its
attached DTE or repeater port in accordance to its specification.
standby(4)
- A MAU in standby(4) state forces DI and CI to idle and the media transmitter to idle or
fault, if supported. Standby(4) mode only applies to link type MAUs. The state of ifMauMediaAvailable is unaffected.
shutdown(5) - A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter as though it were powered down or not connected. The MAU MAY return other(1)
value for the ifMauJabberState and ifMauMediaAvailable objects when it is in this state.
For an AUI, this state will remove power from the AUI.
158
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
reset(6)
- Setting this variable to the value reset(6) resets the MAU in the same manner as a poweroff, power-on cycle of at least one-half second would. The agent is not required to return
the value reset (6).
Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective
state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state.
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM is not required to control the MAU. This object is considered
a status of the MAU and is implemented with an access scope of read-only.
5.9.4.2.1.5
ifMauMediaAvailable
This object is not supported.
If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link test fail state/low
light function. For an AUI or a coax (including broadband) MAU this indicates whether or not loopback is detected
on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2,
10BROAD36, and 10BASE-FP. The following are valid values for this object:
•
•
other(1)
unknown(2)
- The value other(1) is returned if the mediaAvailable state is not one of 2 through 11.
- The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this
attribute is unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback is tested on each transmission during which no collision is detected. If DI is
receiving input when DO returns to IDL after a transmission, and there has been no
collision during the transmission, then loopback will be detected. The value of this
attribute will only change during non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
•
•
•
available(3)
notAvailable(4)
remoteFault(5)
-
•
invalidSignal(6)
-
•
•
•
•
•
remoteJabber(7)
remoteLinkLoss(8)
remoteTest(9)
offline(10)
autoNegError(11)
-
For 100Mbps and 1000Mbps MAUs, the enumerations match the states within the
respective link integrity state diagrams, fig 32-16, 23-12 and 24-15 of sections 32, 23
and 24 of [16]. Any MAU which implements management of auto-negotiation will
map remote fault indication to remote fault.
The value available(3) indicates that the link, light, or loopback is normal.
The value notAvailable(4) indicates link loss, low light, or no loopback.
This value indicates that a fault has been detected at the remote end of the link. This
value applies to 10BASE-FB, 100BASE-T4 Far End Fault Indication and non-specified remote faults from a system running auto-negotiation.
This value indicates hat an invalid signal has been received from the other end of the
link. InvalidSignal(6) applies only to MAUs of type 10BASE-FB.
See explanation below.
See explanation below.
See explanation below.
See explanation below.
See explanation below.
The values remoteJabber(7), remoteLinkLoss(8), and remoteTest(9) SHOULD be used instead of remoteFault(5)
where the reason for remote fault is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an invalid signal has been received from the other end of the link.
InvalidSignal(6) applies only to MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII is present, a logic one in the remote fault bit (reference section
159
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
22.2.4.2.8 of that document) maps to the value remoteFault(5), and a logic zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value notAvailable(4). The value notAvailable(4) takes precedence over the
value remoteFault(5).
Any MAU that implements management of clause 37 Auto-Negotiation will map the received RF1 and RF2 bit values
for Offline to offline(10), Link Failure to remoteFault(5) and Auto-Negotiation Error to autoNegError(11).
5.9.4.2.1.6
ifMauMediaAvailableStateExits
This object is not supported.
A count of the number of times that ifMauMediaAvailable for this MAU instance leaves the state available(3).
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.9.4.2.1.7
ifMauJabberState
This object is not supported.
The following are valid values for this object:
•
other(1)
•
unknown(2)
•
•
noJabber(3)
jabbering(4)
5.9.4.2.1.8
- The value other(1) is returned if the jabber state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
- The value unknown(2) is returned when the MAU's true state is unknown; for example,
when it is being initialized.
- If the MAU is not jabbering the agent returns noJabber(3). This is the “normal” state.
- If the MAU is in jabber state the agent returns the jabbering(4) value.
ifMauJabberingStateEnters
This object is not supported.
A count of the number of times that mauJabberState for this MAU instance enters the state jabbering(4). This counter
will always indicate zero for MAUs of type dot1MauTypeAUI and those of speeds above 10Mbps.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.9.4.2.1.9
ifMauFalseCarriers
This object is not supported.
A count of the number of false carrier events during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will always indicate zero. This counter does not increment at the symbol rate.
It can increment after a valid carrier completion at a maximum rate of once per 100 ms for 100BASE-X and once per
10us for 1000BASE-X until the next CarrierEvent.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
5.9.4.2.1.10
ifMauTypeList
This object is not supported.
THIS OBJECT IS DEPRECATED.
A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. The value is a sum which
160
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
initially takes the value zero. Then, for each type capability of this MAU, 2 raised to the power noted below is added
to the sum. For example, a MAU which has the capability to be only 10BASE-T would have a value of 512 (2**9). In
contrast, a MAU which supports both 10Base-T (full duplex) and 100BASE-TX (full duplex) would have a value of
((2**11) + (2**16)) or 67584.
The powers of 2 assigned to the capabilities are these:
Table 82: ifMauTypeList
Power
Capability
0
other or unknown
1
reserved
2
AUI
3
10BASE-5
4
10BASE-2
5
10BASE-T duplex mode unknown
6
10BASE-FP
7
10BASE-FB
8
10BASE-FL duplex mode unknown
9
10BROAD36
10
10BASE-T half duplex mode
11
10BASE-T full duplex mode
12
10BASE-FL half duplex mode
13
10BASE-FL full duplex mode
14
100BASE-T4
15
100BASE-TX half duplex mode
16
100BASE-TX full duplex mode
17
00BASE-FX half duplex mode
18
100BASE-FX full duplex mode
19
100BASE-T2 half duplex mode
20
100BASE-T2 full duplex mode
161
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapability.
This object has been deprecated in favor of ifMauTypeListBits.
5.9.4.2.1.11
ifMauDefaultType
This object identifies the default administrative baseband MAU type, to be used in conjunction with the operational
MAU type denoted by ifMauType.
The set of possible values for this object is the same as the set defined for the ifMauType object.
This object represents the administratively-configured type of the MAU. If auto-negotiation is not enabled or is not
implemented for this MAU, the value of this object determines the operational type of the MAU. In this case, a set to
this object will force the MAU into the specified operating mode.
If auto-negotiation is implemented and enabled for this MAU, the operational type of the MAU is determined by
auto-negotiation, and the value of this object denotes the type to which the MAU will automatically revert if/when
auto-negotiation is later disabled.
NOTE TO IMPLEMENTORS: It may be necessary to provide for underlying hardware implementations which do
not follow the exact behavior specified above. In particular, when ifMauAutoNegAdminStatus transitions from
enabled to disabled, the agent implementation MUST ensure that the operational type of the MAU (as reported by
ifMauType) correctly transitions to the value specified by this object, rather than continuing to operate at the value
earlier determined by the auto-negotiation function.
Valid Object Value(s)
The table below describes the default value for each of the interfaces applicable to the BitStorm 2600 and
GranDSLAM 4200 IP DSLAM. The essence of the table is that the interfaces will default to full duplex mode at their
highest speed.
Table 83: ifMauDefaultType
Product Interface
Interface Type
Duplex Mode
MAU Type
Ethernet Port 1
10BASE-T
100BASE-TX
Full
dot3MauType100BaseTXHD
Ethernet Port 2
10BASE-T
100BASE-TX
Full
dot3MauType100BaseTXHD
10BASE-T
100BASE-TX
1000BASE-T
Full
dot3MauType1000BaseTHD
1000BASE-FXa
Full
dot3MauType1000BaseXHD
Ethernet Port 3
a. This refers to the use of a Small Form-factor Pluggable (SFP) module. If the operator plugs in a SFP that
operates at a speed that is less than 1000000 bps, it is incumbent on the operator to set the appropriate
default MAU Type.
162
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
5.9.4.2.1.12
ifMauAutoNegSupported
This object indicates whether or not auto-negotiation is supported on this MAU.
This object will return a true(1) if auto-negotiation is supported, and false(2) otherwise.
5.9.4.2.1.13
ifMauTypeListBits
This object is not supported.
A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. If auto-negotiation is
present on this MAU, this object will map to ifMauAutoNegCapability.
Note that this MAU may be capable of operating as a MAU type that is beyond the scope of this MIB. This is
indicated by returning the bit value bOther in addition to any bit values for capabilities that are listed below. The bits
below are those specified in the MIB’s RFC. Those in bold font are possible values for the BitStorm 2600 and
GranDSLAM 4200 IP DSLAM.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
bOther(0)
bAUI(1)
b10base5(2)
bFoirl(3)
b10base2(4)
b10baseT(5)
b10baseFP(6)
b10baseFB(7)
b10baseFL(8)
b10broad36(9)
b10baseTHD(10)
b10baseTFD(11)
b10baseFLHD(12)
b10baseFLFD(13)
b100baseT4(14)
b100baseTXHD(15)
b100baseTXFD(16)
b100baseFXHD(17)
b100baseFXFD(18)
b100baseT2HD(19)
b100baseT2FD(20)
b1000baseXHD(21)
b1000baseXFD(22)
b1000baseLXHD(23)
b1000baseLXFD(24)
b1000baseSXHD(25)
b1000baseSXFD(26)
b1000baseCXHD(27)
b1000baseCXFD(28)
b1000baseTHD(29)
b1000baseTFD(30)
5.9.4.2.2
ifJackTable
-
other or unknown
UI
10BASE-5
FOIRL
10BASE-2
10BASE-T duplex mode unknown
10BASE-FP
10BASE-FB
10BASE-FL duplex mode unknown
10BROAD36
10BASE-T half duplex mode
10BASE-T full duplex mode
10BASE-FL half duplex mode
10BASE-FL full duplex mode
100BASE-T4
100BASE-TX half duplex mode
100BASE-TX full duplex mode
100BASE-FX half duplex mode
100BASE-FX full duplex mode
100BASE-T2 half duplex mode
100BASE-T2 full duplex mode
1000BASE-X half duplex mode
1000BASE-X full duplex mode
1000BASE-LX half duplex mode
1000BASE-LX full duplex mode
1000BASE-SX half duplex mode
1000BASE-SX full duplex mode
1000BASE-CX half duplex mode
1000BASE-CX full duplex mode
1000BASE-T half duplex mode
1000BASE-T full duplex mode
The ifJackTable applies to MAUs attached to interfaces which have one or more external jacks (connectors).
163
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
This table contains information about the external jacks attached to MAUs attached to an interface. This table is a
sequence of ifJackEntry which contains information about a particular jack.
Index(es):
•
•
•
ifMauIfIndex (Section 5.9.4.2.1.1, Page 157)
ifMauIndex (Section 5.9.4.2.1.2, Page 157)
ifJackIndex
OIDs:
•
•
ifJackTable
ifJackEntry
- { dot3IfMauBasicGroup 2 }
- { ifJackTable 1 }
1.2.6.1.2.1.26.2.2
1.2.6.1.2.1.26.2.2.1
Table 84: ifJackTable
Object
OID
Syntax
Access
Status
Supported
ifJackIndex
{ ifJackEntry 1 }
Integer32 (1…2147483647)
not-accessible
current
Y
ifJackType
{ ifJackEntry 2 }
JackType
read-only
current
Y
5.9.4.2.2.1
ifJackIndex
This variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU.
This variable always returns a 1 since multiple jacks on a MAU does not apply to the BitStorm 2600 and
GranDSLAM 4200 IP DSLAM.
5.9.4.2.2.2
ifJackType
The jack connector type, as it appears on the outside of the system.
The following table identifies the values for the ifJackType.
Table 85: ifJackType (1 of 2)
Product Interface
Ethernet Port 1
Ethernet Port 2
Interface Type
10BASE-T
100BASE-TX
10BASE-T
100BASE-TX
Jacka
Return Value
Eight Pin Modular
rj45(2)
Eight Pin Modular
rj45(2)
164
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Table 85: ifJackType (2 of 2)
Product Interface
Interface Type
Jacka
Return Value
Eight Pin Modular
rj45(2)
Small Form-factor Pluggable
(SFP)b
other(1)
10BASE-T
100BASE-TX
Ethernet Port 3
1000BASE-T
100BASE-FX
1000BASE-SX
1000BASE-LX
a. Although an eight pin modular jack is not necessarily an RJ45-type jack, they are equated here.
b. When the SFP is installed, it takes precedence over the Eight Pin Modular.
5.9.4.3
Interface MAU Auto-Negotiation Group
The ifMauAutoNegTable applies to systems in which auto-negotiation is supported on one or more MAUs attached to
interfaces. Note that if auto-negotiation is present and enabled, the ifMauType object reflects the result of the autonegotiation function.
5.9.4.3.1
ifMauAutoNegTable
This table contains configuration and status objects for the auto-negotiation function of MAUs attached to interfaces.
The table is a sequence of ifMauAutoNegEntry which contains configuration and status information for the autonegotiation function of a particular MAU.
Index(es):
•
•
ifMauIfIndex (Section 5.9.4.2.1.1, Page 157)
ifMauIndex (Section 5.9.4.2.1.2, Page 157)
OIDs:
•
•
ifMauAutoNegTable
ifMauAutoNegEntry
- { dot3IfMauAutoNegGroup 1 }
- { ifMauAutoNegTable 1 }
1.2.6.1.2.1.26.5.1
1.2.6.1.2.1.26.5.1.1
Table 86: ifMauAutoNegTable (1 of 3)
Object
OID
Syntax
Access
Status
Supported
ifMauAutoNegAdminStatus
{ ifMauAutoNegEntry 1 }
INTEGER
enabled(1)
disabled(2)
read-write
current
Y
ifMauAutoNegRemoteSignaling
{ ifMauAutoNegEntry 2 }
INTEGER
detected(1)
notdetected(2)
read-only
current
N
165
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Table 86: ifMauAutoNegTable (2 of 3)
Object
OID
Syntax
Access
Status
Supported
ifMauAutoNegConfig
{ ifMauAutoNegEntry 4 }
INTEGER
other(1)
configuring(2)
complete(3)
disabled(4)
parallelDetectFail(5)
read-only
current
N
ifMauAutoNegCapability
{ ifMauAutoNegEntry 5 }
Integer32
read-only
deprecated
N
ifMauAutoNegCapAdvertised
{ ifMauAutoNegEntry 6 }
Integer32
read-write
deprecated
N
ifMauAutoNegCapReceived
{ ifMauAutoNegEntry 7 }
Integer32
read-only
deprecated
N
ifMauAutoNegRestart
{ ifMauAutoNegEntry 8 }
INTEGER
restert(1)
norestart(2)
read-write
current
N
ifMauAutoNegCapabilityBits
{ ifMauAutoNegEntry 9 }
BITS
bother(0)
b10baseT(1)
b10baseTFD(2)
b100baseT4(3)
b100baseTX(4)
b100baseTXFD(5)
b100baseT2(6)
b100baseT2FD(7)
bFdxPause(8)
bFdxAPause(9)
bFdxSPause(10)
bFdxBPause(11)
b1000baseX(12)
b1000baseXFD(13)
b1000baseT(14)
b1000baseTFD(15)
read-only
current
N
166
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Table 86: ifMauAutoNegTable (3 of 3)
Object
OID
Syntax
Access
Status
Supported
ifMauAutoNegCapAdvertisedBits
{ ifMauAutoNegEntry 10 }
BITS
bother(0)
b10baseT(1)
b10baseTFD(2)
b100baseT4(3)
b100baseTX(4)
b100baseTXFD(5)
b100baseT2(6)
b100baseT2FD(7)
bFdxPause(8)
bFdxAPause(9)
bFdxSPause(10)
bFdxBPause(11)
b1000baseX(12)
b1000baseXFD(13)
b1000baseT(14)
b1000baseTFD(15)
read-write
current
N
ifMauAutoNegCapReceivedBits
{ ifMauAutoNegEntry 11 }
BITS
bother(0)
b10baseT(1)
b10baseTFD(2)
b100baseT4(3)
b100baseTX(4)
b100baseTXFD(5)
b100baseT2(6)
b100baseT2FD(7)
bFdxPause(8)
bFdxAPause(9)
bFdxSPause(10)
bFdxBPause(11)
b1000baseX(12)
b1000baseXFD(13)
b1000baseT(14)
b1000baseTFD(15)
read-only
current
N
ifMauAutoNegRemoteFaultAdvertised
{ ifMauAutoNegEntry 12 }
INTEGER
noError(1)
offline(2)
linkFailure(3)
autoNegError(4)
read-write
current
N
ifMauAutoNegRemoteFaultReceived
{ ifMauAutoNegEntry 13 }
INTEGER
noError(1)
offline(2)
linkFailure(3)
autoNegError(4)
read-only
current
N
5.9.4.3.1.1
ifMauAutoNegAdminStatus
• enabled(1) - If the interface has auto-negotiation signaling ability, auto-negotiation is enabled.
167
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
disabled(2) - The interface will act as it would if it had no auto-negotiation signaling. Under these conditions, an IEEE 802.3 MAU will immediately be forced to the state indicated by the value of
the object ifMauDefaultType
NOTE TO IMPLEMENTORS: When ifMauAutoNegAdminStatus transitions from enabled to disabled, the agent
implementation MUST ensure that the operational type of the MAU (as reported by ifMauType) correctly transitions
to the value specified by the ifMauDefaultType object, rather than continuing to operate at the value earlier
determined by the auto-negotiation function.
Valid Object Value(s)
•
•
Internal Ethernet Interfaces
—
disabled(2)
External Ethernet Interfaces
—
enabled(1)
—
disabled(2)
5.9.4.3.1.2
ifMauAutoNegRemoteSignaling
This object is not supported.
A value indicating whether the remote end of the link is using auto-negotiation signaling.
•
detected(1)
•
notdetected(2)
5.9.4.3.1.3
- It takes the value detected(1) if and only if, during the previous link negotiation, FLP
Bursts were received.
ifMauAutoNegConfig
This object is not supported.
A value indicating the current status of the auto-negotiation process. The enumeration parallelDetectFail(5) maps to a
failure in parallel detection as defined in 28.2.3.1 of [IEEE 802.3 Std].
•
•
•
•
•
other(1)
configuring(2)
complete(3)
disabled(4)
parallelDetectFail(5)
5.9.4.3.1.4
ifMauAutoNegCapability
This object is not supported.
THIS OBJECT IS DEPRECATED.
A value that uniquely identifies the set of capabilities of the local auto-negotiation entity. The value is a sum which
initially takes the value zero. Then, for each capability of this interface, 2 raised to the power noted below is added to
the sum. For example, an interface which has the capability to support only 100Base-TX half duplex would have a
value of 32768 (2**15). In contrast, an interface which supports both 100Base-TX half duplex and 100Base-TX full
duplex would have a value of 98304 ((2**15) + (2**16)).
The powers of 2 assigned to the capabilities are these:
168
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Table 87: ifMauAutoNegCapability
Power
Capability
0
other or unknown
1-9
reserved
10
10BASE-T half duplex mode
11
10BASE-T full duplex mode
12
reserved
13
reserved
14
100BASE-T4
15
100BASE-TX half duplex mode
16
100BASE-TX full duplex mode
17
reserved
18
reserved
19
100BASE-T2 half duplex mode
20
100BASE-T2 full duplex mode
Note that interfaces that support this MIB may have capabilities that extend beyond the scope of this MIB. This object
has been deprecated in favor of ifMauAutoNegCapabilityBits
5.9.4.3.1.5
ifMauAutoNegCapAdvertised
This object is not supported.
THIS OBJECT IS DEPRECATED.
A value that uniquely identifies the set of capabilities advertised by the local auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the possible values of this object.
Capabilities in this object that are not available in ifMauAutoNegCapability cannot be enabled.
This object has been deprecated in favor of ifMauAutoNegCapAdvertisedBits
5.9.4.3.1.6
ifMauAutoNegCapReceived
This object is not supported.
THIS OBJECT IS DEPRECATED.
A value that uniquely identifies the set of capabilities received from the remote auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the possible values of this object.
169
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
Note that interfaces that support this MIB may be attached to remote auto-negotiation entities which have capabilities
beyond the scope of this MIB.
This object has been deprecated in favor of ifMauAutoNegCapReceivedBits
5.9.4.3.1.7
ifMauAutoNegRestart
This object is not supported.
•
restart(1)
•
norestart(2)
5.9.4.3.1.8
- Force auto-negotiation to begin link renegotiation. If auto-negotiation signaling is disabled, a write to this object has no effect.
- Setting the value of this object to norestart(2) has no effect
ifMauAutoNegCapabilityBits
This object is not supported.
A value that uniquely identifies the set of capabilities of the local auto-negotiation entity. Note that interfaces that
support this MIB may have capabilities that extend beyond the scope of this MIB.
Note that the local auto-negotiation entity may support some capabilities beyond the scope of this MIB. This is
indicated by returning the bit value bOther in addition to any bit values for capabilities that are listed below.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
bOther(0)
b10baseT(1)
b10baseTFD(2)
b100baseT4(3)
b100baseTX(4)
b100baseTXFD(5)
b100baseT2(6)
b100baseT2FD(7)
bfdxPause(8)
bfdxAPause(9)
bfdxSPause(10)
bfdxBPause(11)
b1000baseX(12)
b1000baseXFD(13)
b1000baseT(14)
b1000baseTFD(15)
5.9.4.3.1.9
-
other or unknown
10BASE-T half duplex mode
10BASE-T full duplex mode
100BASE-T4
100BASE-TX half duplex mode
100BASE-TX full duplex mode
100BASE-T2 half duplex mode
100BASE-T2 full duplex mode
PAUSE for full-duplex links
Asymmetric PAUSE for full-duplex links
Symmetric PAUSE for full-duplex links
Asymmetric and Symmetric PAUSE for full-duplex links
1000BASE-X, -LX, -SX, -CX half duplex mode
1000BASE-X, -LX, -SX, -CX full duplex mode
1000BASE-T half duplex mode
1000BASE-T full duplex mode
ifMauAutoNegCapAdvertisedBits
This object is not supported.
A value that uniquely identifies the set of capabilities advertised by the local auto-negotiation entity.
Capabilities in this object that are not available in ifMauAutoNegCapabilityBits cannot be enabled. Note that the
local auto-negotiation entity may advertise some capabilities beyond the scope of this MIB. This is indicated by
returning the bit value bOther in addition to any bit values for capabilities that are listed below.
•
•
•
bOther(0)
b10baseT(1)
b10baseTFD(2)
- other or unknown
- 10BASE-T half duplex mode
- 10BASE-T full duplex mode
170
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
•
•
•
•
•
•
•
•
•
•
•
•
b100baseT4(3)
b100baseTX(4)
b100baseTXFD(5)
b100baseT2(6)
b100baseT2FD(7)
bfdxPause(8)
bfdxAPause(9)
bfdxSPause(10)
bfdxBPause(11)
b1000baseX(12)
b1000baseXFD(13)
b1000baseT(14)
b1000baseTFD(15)
5.9.4.3.1.10
-
100BASE-T4
100BASE-TX half duplex mode
100BASE-TX full duplex mode
100BASE-T2 half duplex mode
100BASE-T2 full duplex mode
PAUSE for full-duplex links
Asymmetric PAUSE for full-duplex links
Symmetric PAUSE for full-duplex links
Asymmetric and Symmetric PAUSE for full-duplex links
1000BASE-X, -LX, -SX, -CX half duplex mode
000BASE-X, -LX, -SX, -CX full duplex mode
1000BASE-T half duplex mode
1000BASE-T full duplex mode
ifMauAutoNegCapReceivedBits
This object is not supported.
A value that uniquely identifies the set of capabilities received from the remote auto-negotiation entity.
Note that interfaces that support this MIB may be attached to remote auto-negotiation entities which have capabilities
beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for
capabilities that are listed below.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
bOther(0)
b10baseT(1)
b10baseTFD(2)
b100baseT4(3)
b100baseTX(4)
b100baseTXFD(5)
b100baseT2(6)
b100baseT2FD(7)
bfdxPause(8)
bfdxAPause(9)
bfdxSPause(10)
bfdxBPause(11)
b1000baseX(12)
b1000baseXFD(13)
b1000baseT(14)
b1000baseTFD(15)
5.9.4.3.1.11
-
other or unknown
10BASE-T half duplex mode
10BASE-T full duplex mode
100BASE-T4
100BASE-TX half duplex mode
100BASE-TX full duplex mode
100BASE-T2 half duplex mode
100BASE-T2 full duplex mode
PAUSE for full-duplex links
Asymmetric PAUSE for full-duplex links
Symmetric PAUSE for full-duplex links
Asymmetric and Symmetric PAUSE for full-duplex links
1000BASE-X, -LX, -SX, -CX half duplex mode
000BASE-X, -LX, -SX, -CX full duplex mode
1000BASE-T half duplex mode
1000BASE-T full duplex mode
ifMauAutoNegRemoteFaultAdvertised
This object is not supported.
A value that identifies any local fault indications that this MAU has detected and will advertise at the next autonegotiation interaction for 1000Mbps MAUs.
•
•
•
noError(1)
offline(2)
linkFailure(3)
171
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
•
autoNegError(4)
5.9.4.3.1.12
ifMauAutoNegRemoteFaultReceived
This object is not supported.
A value that identifies any fault indications received from the far end of a link by the local auto-negotiation entity for
1000Mbps MAUs.
•
•
•
•
noError(1)
offline(2)
linkFailure(3)
autoNegError(4)
5.9.4.4
dot3BroadMauBasicGroup
5.9.4.4.1
broadMauBasicTable
THIS OBJECT IS DEPRECATED.
Table of descriptive and status information about the broadband MAUs connected to interfaces. This table is a
sequence of broadMauBasicEntry which contains information about a single broadband MAU.
This deprecated table will not be supported in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM.
Index(es):
•
broadMauIfIndex
OIDs:
•
•
broadMauBasicTable
broadMauBasicEntry
- { dot3BroadMauBasicGroup 1 }
- { broadMauBasicTable 1 }
1.2.6.1.2.1.26.3.1
1.2.6.1.2.1.26.3.1.1
Table 88: broadMauBasicTable
Object
OID
Syntax
Access
Status
Supported
broadMauIfIndex
{ broadMauBasicEntry 1 }
Integer32 (1…2147483647)
read-only
deprecated
N
broadMauIndex
{ broadMauBasicEntry 2 }
Integer32 (1…2147483647)
read-only
deprecated
N
broadMauXmtRcvSplitType
{ broadMauBasicEntry 3 }
INTEGER
other(1)
single(2)
dual(3)
read-only
deprecated
N
broadMauXmtCarrierFreq
{ broadMauBasicEntry 4 }
Integer32
read-only
deprecated
N
broadMauTranslationFreq
{ broadMauBasicEntry 5 }
Integer32
read-only
deprecated
N
5.9.4.4.1.1
broadMauIfIndex
THIS OBJECT IS DEPRECATED.
172
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
This variable uniquely identifies the interface to which the MAU described by this entry is connected.
5.9.4.4.1.2
broadMauIndex
THIS OBJECT IS DEPRECATED.
This variable uniquely identifies the MAU connected to interface broadMauIfIndex that is described by this entry.
5.9.4.4.1.3
broadMauXmtRcvSplitType
THIS OBJECT IS DEPRECATED.
This object indicates the type of frequency multiplexing/cabling system used to separate the transmit and receive
paths for the 10BROAD36 MAU.
•
•
•
other(1) - The split type is not either single or dual.
single(2) - Indicates a single cable system
dual(3)
- Indicates a dual cable system, offset normally zero.
5.9.4.4.1.4
broadMauXmtCarrierFreq
THIS OBJECT IS DEPRECATED.
This variable indicates the transmit carrier frequency of the 10BROAD36 MAU in MHz/4; that is, in units of 250
kHz.
5.9.4.4.1.5
broadMauTranslationFreq
THIS OBJECT IS DEPRECATED.
This variable indicates the translation offset frequency of the 10BROAD36 MAU in MHz/4; that is, in units of 250
kHz.
5.9.5
Traps
No 802.3 MAU Traps are supported.
OIDs:
•
snmpDot3MauTraps
- { snmpDot3MauMgt 0 } 1.2.6.1.2.1.26.0
Table 89: 802.3 MAU Traps
Notification
OID
Variable Bindings
Supported
rpMauJabberTrap
{ snmpDot3MauTraps 1 }
rpMauJabberState
N
ifMauJabberTrap
{ snmpDot3MauTraps 2 }
ifMauIfIndex
ifMauIndex
ifMauJabberState
N
5.9.5.1
rpMauJabberTrap
This trap is sent whenever a managed repeater MAU enters the jabber state.
173
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
MAU-MIB — RFC 2668
The agent MUST throttle the generation of consecutive rpMauJabberTraps so that there is at least a five-second gap
between them.
5.9.5.2
ifMauJabberTrap
This trap is sent whenever a managed interface MAU enters the jabber state.
The agent MUST throttle the generation of consecutive ifMauJabberTraps so that there is at least a five-second gap
between them.
174
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
5.10 RS-232-MIB — RFC 1659
5.10.1
Introduction
This MIB describes objects for managing RS-232-like interfaces. The RFC used as a reference was dated July 1994.
The LAST-UPDATED for the RS-232-MIB was “9405261700Z.”
This MIB applies to the following interfaces in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM:
•
Console
5.10.2
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
rs232
5.10.3
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 33 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.33
This MIB comprises one base object and four tables, detailed in the following sections. The tables contain objects for
all ports, asynchronous ports, and input and output control signals.
Table 90: RS-232-MIB Objects
Object
OID
Syntax
Access
Status
Supported
rs232Number
{ rs232 1 }
Integer32
read-only
current
Y
rs232PortTable
{ rs232 2 }
SEQUENCE of rs232PortEntry
not-accessible
current
Y
rs232AsyncPortTable
{ rs232 3 }
SEQUENCE of rs232AyncPortEntry
not-accessible
current
Y
rs232SyncPortTable
{ rs232 4 }
SEQUENCE of rs232SyncPortEntry
not-accessible
current
N
rs232InSigTable
{ rs232 5 }
SEQUENCE of rs232InSigEntry
not-accessible
current
N
rs232OutSigTable
{ rs232 6 }
SEQUENCE of rs232OutSigEntry
not-accessible
current
N
5.10.3.1
rs232Number
The number of ports (regardless of their current state) in the RS-232-like general port table.
Valid Object Value(s)
•
5.10.3.2
1
rs232PortTable
A list of port entries. The number of entries is given by the value of rs232Number. This table is a sequence of
rs232PortEntry which contains Status and parameter values for a port.
175
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
Index(es):
•
rs232PortIndex
OIDs:
•
•
rs232PortTable
rs232PortEntry
- { rs232 2 }
- { rs232PortTable 1}
1.3.6.1.2.1.10.33.2
1.3.6.1.2.1.10.33.2.1
Table 91: rs232PortTable
Object
OID
Syntax
Access
Status
Supported
rs232PortIndex
{ rs232PortEntry 1 }
InterfaceIndex
read-only
current
Y
rs232PortType
{ rs232PortEntry 2 }
INTEGER
other(1)
rs232(2)
rs422(3)
rs423(4)
v35(5)
x21(6)
read-only
current
Y
rs232PortInSigNumber
{ rs232PortEntry 3 }
Integer32
read-only
current
Y
rs232PortOutSigNumber
{ rs232PortEntry 4 }
Integer32
read-only
current
Y
rs232PortInSpeed
{ rs232PortEntry 5 }
Integer32
read-write
current
Y
rs232PortOutSpeed
{ rs232PortEntry 6 }
Integer32
read-write
current
Y
rs232PortInFlowType
{ rs232PortEntry 7 }
INTEGER
none(1)
ctsRts(2)
dsrDtr(3)
read-write
current
Y
rs232PortOutFlowType
{ rs232PortEntry 8 }
INTEGER
none(1)
ctsRts(2)
dsrDtr(3)
read-write
current
Y
5.10.3.2.1
rs232PortIndex
The value of ifIndex for the port. By convention and if possible, hardware port numbers map directly to external
connectors. The value for each port must remain constant at least from one re-initialization of the network
management agent to the next.
Valid Object Value(s)
This object is equated to the ifIndex (Section 5.3.4.3.1, Page 39).
176
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
5.10.3.2.2
rs232PortType
The port's hardware type.
•
•
•
•
•
•
other(1)
rs232(2)
rs422(3)
rs423(4)
v35(5)
x21(6)
Valid Object Value(s)
•
Console:
5.10.3.2.3
rs232(2)
rs232PortInSigNumber
The number of input signals for the port in the input signal table (rs232InSigTable, Section 5.10.3.5, Page 183). The
table contains entries only for those signals the software can detect and that are useful to observe.
5.10.3.2.4
rs232PortOutSigNumber
The number of output signals for the port in the output signal table (rs232OutSigTable, Section 5.10.3.6, Page 185).
The table contains entries only for those signals the software can assert and that are useful to observe.
5.10.3.2.5
rs232PortInSpeed
The port's input speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on
most implementations.
Valid Object Value(s)
Note: Port speeds are symmetrical. Therefore the rs232PortInSpeed object is the same as the rs232PortOutSpeed
object. From the standpoint of the internals, when you set one, internally the other gets set to the same value as well.
•
Console:
5.10.3.2.6
9600, 19200, 38400, 57600, 115200 bps
rs232PortOutSpeed
The port's output speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on
most implementations.
Valid Object Value(s)
See rs232PortInSpeed above.
5.10.3.2.7
rs232PortInFlowType
The port's type of input flow control. “none” indicates no flow control at this level. “ctsRts” and “dsrDtr” indicate use
of the indicated hardware signals.
•
•
•
none(1)
ctsRts(2)
dsrDtr(3)
This object is interpreted from the perspective of the port. Input flow control indicates which output signal gets set to
false to signal the device attached to the other side of the communication link to stop transmitting data. This port
controls the flow of the remote device.
177
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
Valid Object Value(s)
The only valid value for this object is none(1).
5.10.3.2.8
rs232PortOutFlowType
The port's type of output flow control. “none” indicates no flow control at this level. “ctsRts” and “dsrDtr” indicate
use of the indicated hardware signals.
•
•
•
none(1)
ctsRts(2)
dsrDtr(3)
This object is interpreted from the perspective of the port. Output flow control indicates which input signal to monitor
such that when it set to false, this port should stop transmitting data to the other side of the communication link. The
remote device controls the flow of this port.
Valid Object Value(s)
•
Console:
5.10.3.3
none(1)
rs232AsyncPortTable
A list of asynchronous port entries. Entries need not exist for synchronous ports. This table is a sequence of
rs232AsyncPortEntry which contains status and parameter values for an asynchronous port.
The following interfaces on the BitStorm 2600 and GranDSLAM 4200 IP DSLAM apply to the rs232AsyncPort type:
•
Console
Index(es):
•
rs232AsyncPortIndex
OIDs:
•
•
rs232AsyncPortTable
rs232AsyncPortEntry
- { rs232 3 }
- { rs232AsyncPortTable 1}
1.3.6.1.2.1.10.33.3
1.3.6.1.2.1.10.33.3.1
Table 92: rs232AsyncPortTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
rs232AsyncPortIndex
{ rs232AsyncPortEntry 1 }
InterfaceIndex
read-only
current
Y
rs232AsyncPortBits
{ rs232AsyncPortEntry 2 }
INTEGER(5…8)
read-write
current
Y
rs232AsyncPortStopBits
{ rs232AsyncPortEntry 3 }
INTEGER
one(1)
two(2)
oneAndHalf(3)
dynamic(4)
read-write
current
Y
178
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
Table 92: rs232AsyncPortTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
rs232AsyncPortParity
{ rs232AsyncPortEntry 4 }
INTEGER
none(1)
odd(2)
even(3)
mark(4)
space(5)
read-write
current
Y
rs232AsyncPortAutobaud
{ rs232AsyncPortEntry 5 }
INTEGER
enabled(1)
disabled(2)
read-write
current
Y
rs232AsyncPortParityErrs
{ rs232AsyncPortEntry 6 }
Counter32
read-only
current
N
rs232AsyncPortFramingErrs
{ rs232AsyncPortEntry 7 }
Counter32
read-only
current
N
rs232AsyncPortOverrunErrs
{ rs232AsyncPortEntry 8 }
Counter32
read-only
current
N
5.10.3.3.1
rs232AsyncPortIndex
A unique value for each port. Its value is the same as rs232PortIndex, Section 5.10.3.2.1, Page 176, for the port.
5.10.3.3.2
rs232AsyncPortBits
The port's number of bits in a character.
Valid Object Value(s)
•
Console:
5.10.3.3.3
7 or 8
rs232AsyncPortStopBits
The port's number of stop bits.
•
•
•
•
one(1)
two(2)
oneAndHalf(3)
dynamic(4)
Valid Object Value(s)
•
Console:
5.10.3.3.4
one(1) or two(2)
rs232AsyncPortParity
The port's sense of a character parity bit.
•
•
•
•
none(1)
odd(2)
even(3)
mark(4)
179
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
•
space(5)
Valid Object Value(s)
•
Console:
5.10.3.3.5
none(1), odd(2), even(3)
rs232AsyncPortAutobaud
A control for the port's ability to automatically sense input speed. When rs232PortAutoBaud is “enabled,” a port may
autobaud to values different from the set values for speed, parity, and character size. As a result a network
management system may temporarily observe values different from what was previously set.
•
•
enabled(1)
disabled(2)
Valid Object Value(s)
•
Console:
5.10.3.3.6
disabled(2)
rs232AsyncPortParityErrs
Total number of characters with a parity error, input from the port since system re-initialization and while the port
state was “up” or “test.”
Valid Object Value(s)
This object will not be supported.
5.10.3.3.7
rs232AsyncPortFramingErrs
Total number of characters with a framing error, input from the port since system re-initialization and while the port
state was “up” or “test.”
Valid Object Value(s)
This object will not be supported.
5.10.3.3.8
rs232AsyncPortOverrunErrs
Total number of characters with an overrun error, input from the port since system re-initialization and while the port
state was “up” or “test.”
Valid Object Value(s)
This object will not be supported.
5.10.3.4
rs232SyncPortTable
A list of asynchronous port entries. Entries need not exist for synchronous ports. This table is a sequence of
rs232SyncPortEntry where each entry consists of status and parameter values for a synchronous port.
Index(es):
•
rs232SyncPortIndex
OIDs:
•
•
rs232SyncPortTable - { rs232 4 }
rs232SyncPortEntry - { rs232SyncPortTable 1}
180
1.3.6.1.2.1.10.33.4
1.3.6.1.2.1.10.33.4.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
Table 93: rs232SyncPortTable
Object
OID
Syntax
Access
Status
Supported
rs232SyncPortIndex
{ rs232SyncPortEntry 1 }
InterfaceIndex
read-only
current
N
rs232SyncPortClockSource
{ rs232SyncPortEntry 2 }
INTEGER
internal(1)
external(2)
split(3)
read-write
current
N
rs232SyncPortFrameCheckErrs
{ rs232SyncPortEntry 3 }
Counter32
read-only
current
N
rs232SyncPortTransmitUnderrunErrs
{ rs232SyncPortEntry 4 }
Counter32
read-only
current
N
rs232SyncPortReceiveOverrunErrs
{ rs232SyncPortEntry 5 }
Counter32
read-only
current
N
rs232SyncPortInterruptedFrames
{ rs232SyncPortEntry 6 }
Counter32
read-only
current
N
rs232SyncPortAbortedFrames
{ rs232SyncPortEntry 7 }
Counter32
read-only
current
N
rs232SyncPortRole
{ rs232SyncPortEntry 8 }
INTEGER
dte(1)
dce(2)
read-write
current
N
rs232SyncPortEncoding
{ rs232SyncPortEntry 9 }
INTEGER
nrz(1)
nrzi(2)
read-write
current
N
rs232SyncPortRTSControl
{ rs232SyncPortEntry 10 }
INTEGER
controlled(1)
constant(2)
read-write
current
N
rs232SyncPortRTSCTSDelay
{ rs232SyncPortEntry 11 }
Integer32
read-write
current
N
rs232SyncPortMode
{ rs232SyncPortEntry 12 }
INTEGER
fdx(1)
hdx(2)
simplexreceived(3)
simplexsend(4)
read-write
current
N
rs232SyncPortIdlePattern
{ rs232SyncPortEntry 13 }
INTEGER
mark(1)
space(2)
read-write
current
N
rs232SyncPortMinFlags
{ rs232SyncPortEntry 14 }
Integer32
read-write
current
N
181
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
5.10.3.4.1
rs232SyncPortIndex
A unique value for each port. Its value is the same as rs232PortIndex, Section 5.10.3.2.1, Page 176, for the port.
5.10.3.4.2
rs232SyncPortClockSource
Source of the port's bit rate clock. “split”' means the transmit clock is internal and the receive clock is external.
•
•
•
internal(1)
external(2)
split(3)
5.10.3.4.3
rs232SyncPortFrameCheckErrs
Total number of frames with an invalid frame check sequence, input from the port since system re-initialization and
while the port state was “up” or “test.”
5.10.3.4.4
rs232SyncPortTransmitUnderrunErrs
Total number of frames that failed to be transmitted on the port since system re-initialization and while the port state
was “up or test” because data was not available to the transmitter in time.
5.10.3.4.5
rs232SyncPortReceiveOverrunErrs
Total number of frames that failed to be received on the port since system re-initialization and while the port state was
“up or test” because the receiver did not accept the data in time.
5.10.3.4.6
rs232SyncPortInterruptedFrames
Total number of frames that failed to be received or transmitted on the port due to loss of modem signals since system
re-initialization and while the port state was “up” or “test.”
5.10.3.4.7
rs232SyncPortAbortedFrames
Number of frames aborted on the port due to receiving an abort sequence since system re-initialization and while the
port state was “up” or “test.”
5.10.3.4.8
rs232SyncPortRole
The role the device is playing that is using this port. The default value is dce(2).
•
•
dte(1)
dce(2)
5.10.3.4.9
- means the device is performing the role of data terminal equipment
- means the device is performing the role of data circuit-terminating equipment.
rs232SyncPortEncoding
The bit stream encoding technique that is in effect for this port.
•
•
nrz(1) - for Non-Return to Zero encoding
nrzi(2) - for Non-Return to Zero Inverted encoding.
5.10.3.4.10 rs232SyncPortRTSControl
The method used to control the Request To Send (RTS) signal. The default value is constant(2).
•
controlled(1)
- when the DTE is asserts RTS each time data needs to be transmitted and drops RTS at
some point after data transmission begins.
182
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
If rs232SyncPortRole is “dte,” the RTS is an output signal. The device will issue a RTS
and wait for a CTS from the DCE before starting to transmit.
If rs232SyncPortRole is “dce,” the RTS is an input signal. The device will issue a CTS
only after having received RTS and waiting the rs232SyncPortRTSCTSDelay interval.
•
constant(2)
- when the DTE constantly asserts RTS.
5.10.3.4.11 rs232SyncPortRTSCTSDelay
The interval (in milliseconds) that the DCE must wait after it sees RTS asserted before asserting CTS. This object
exists in support of older synchronous devices that cannot recognize CTS within a certain interval after it asserts RTS.
5.10.3.4.12 rs232SyncPortMode
The mode of operation of the port with respect to the direction and simultaneity of data transfer. The default value is
fdx.
•
•
•
•
fdx(1)
hdx(2)
- when frames on the data link can be transmitted and received at the same time
- when frames can either be received from the data link or transmitted onto the data link
but not at the same time.
simplex-receive(3) - when frames can only be received on this data link.
simplex-send(4)
- when frames can only be sent on this data link.
5.10.3.4.13 rs232SyncPortIdlePattern
The bit pattern used to indicate an idle line. The default is space(2).
•
•
mark(1)
space(2)
5.10.3.4.14 rs232SyncPortMinFlags
The minimum number of flag patterns this port needs in order to recognize the end of one frame and the start of the
next. Plausible values are 1 and 2. The default value is “2.”
5.10.3.5
rs232InSigTable
A list of port input control signal entries implemented and visible to the software on the port, and useful to monitor.
This table is a sequence of rs232InSigEntry and each entry consists of input control signal status for a hardware port.
Index(es):
•
•
rs232InSigPortIndex
rs232InSigName
OIDs:
•
•
rs232InSigTable
rs232InSigEntry
- { rs232 5 }
- { rs232InSigTable 1}
183
1.3.6.1.2.1.10.33.5
1.3.6.1.2.1.10.33.5.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
Table 94: rs232InSigTable
Object
OID
Syntax
Access
Status
Supported
rs232InSigPortIndex
{ rs232InSigEntry 1 }
InterfaceIndex
read-only
current
N
rs232InSigName
{ rs232InSigEntry 2 }
INTEGER
rts1)
cts(2)
dsr(3)
dtr(4)
ri(5)
dcd(6)
sq(7)
srs(8)
srts(9)
scts(10)
sdcd(11)
read-only
current
N
rs232InSigState
{ rs232InSigEntry 3 }
INTEGER
none(1)
on(2)
off(3)
read-only
current
N
rs232InSigChanges
{ rs232InSigEntry 4 }
Counter32
read-only
current
N
5.10.3.5.1
rs232InSigPortIndex
The value of rs232PortIndex, Section 5.10.3.2.1, Page 176, for the port to which this entry belongs.
5.10.3.5.2
rs232InSigName
Identification of a hardware signal, as follows:
•
•
•
•
•
•
•
•
•
•
•
rts
cts
dsr
dtr
ri
dcd
sq
srs
srts
scts
sdcd
5.10.3.5.3
-
Request to Send
Clear to Send
Data Set Ready
Data Terminal Ready
Ring Indicator
Received Line Signal Detector
Signal Quality Detector
Data Signaling Rate Selector
Secondary Request to Send
Secondary Clear to Send
Secondary Received Line Signal Detector
rs232InSigState
The current signal state.
•
none(1)
184
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
RS-232-MIB — RFC 1659
•
•
on(2)
off(3)
5.10.3.5.4
rs232InSigChanges
The number of times the signal has changed from “on” to “off” or from “off” to “on.”
5.10.3.6
rs232OutSigTable
A list of port output control signal entries implemented and visible to the software on the port, and useful to monitor.
This table is a sequence of rs232OutSigEntry where each entry consists of Output control signal status for a hardware
port.
Index(es):
•
•
rs232OutSigPortIndex
rs232OutSigName
OIDs:
•
•
rs232OutSigTable - { rs232 6 }
rs232OutSigEntry - { rs232OutSigTable 1}
1.3.6.1.2.1.10.33.6
1.3.6.1.2.1.10.33.6.1
Table 95: rs232OutSigTable
Object
OID
Syntax
Access
Status
Supported
rs232OutSigPortIndex
{ rs232OutSigEntry 1 }
InterfaceIndex
read-only
current
N
rs232OutSigName
{ rs232OutSigEntry 2 }
INTEGER
rts1)
cts(2)
dsr(3)
dtr(4)
ri(5)
dcd(6)
sq(7)
srs(8)
srts(9)
scts(10)
sdcd(11)
read-only
current
N
rs232OutSigState
{ rs232OutSigEntry 3 }
INTEGER
none(1)
on(2)
off(3)
read-only
current
N
rs232OutSigChanges
{ rs232OutSigEntry 4 }
Counter32
read-only
current
N
5.10.3.6.1
rs232OutSigPortIndex
The value of rs232PortIndex, Section 5.10.3.2.1, Page 176, for the port to which this entry belongs.
185
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
RS-232-MIB — RFC 1659
5.10.3.6.2
rs232OutSigName
Identification of a hardware signal, as follows:
•
•
•
•
•
•
•
•
•
•
•
rts
cts
dsr
dtr
ri
dcd
sq
srs
srts
scts
sdcd
5.10.3.6.3
-
Request to Send
Clear to Send
Data Set Ready
Data Terminal Ready
Ring Indicator
Received Line Signal Detector
Signal Quality Detector
Data Signaling Rate Selector
Secondary Request to Send
Secondary Clear to Send
Secondary Received Line Signal Detector
rs232OutSigState
The current signal state.
•
•
•
none(1)
on(2)
off(3)
5.10.3.6.4
rs232OutSigChanges
The number of times the signal has changed from “on” to “off” or from “off” to “on.”
186
SNMP Reference
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11
ADSL-LINE-MIB — RFC 2662
5.11.1
Introduction
This MIB defines objects for the management of ADSL lines for the BitStorm 2600 and GranDSLAM 4200 IP
DSLAM. The RFC used as a reference was dated August 1999 and the ADSL Line MIB has a LAST-UPDATED of
“9908190000Z.”
Not all objects defined in the MIB are supported by the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. What is
supported or not supported is identified.
In addition, memory required for the various MIB objects is identified.
5.11.1.1
Textual Conventions
The following textual conventions are made in the RFC:
•
AdslLineCodingType
- This data type is used as the syntax for the ADSL Line Code.
— Syntax
INTEGER
• other(1)
- none of the following
• dmt(2)
- Discrete MultiTone
• cap(3)
- Carrierless Amplitude & Phase modulation
• qam(4)
- Quadrature Amplitude Modulation
•
AdslPerfCurrDayCount
- A counter associated with interface performance measurements in a current 1-day (24 hour) measurement interval.
The value of this counter starts at zero at the beginning of an interval and
is increased when a associated events occur, until the end of the 1-day
interval. At that time the value of the counter is stored in the previous 1day history interval, if available, and the current interval counter is
restarted at zero.
In the case where the agent has no valid data available for this interval the
corresponding object instance is not available and upon a retrieval request
a corresponding error message shall be returned to indicate that this
instance does not exist (for example, a noSuchName error for SNMPv1
and a noSuchInstance for SNMPv2 GET operation).
— Syntax
•
AdslPerfPrevDayCount
Gauge32
- A counter associated with interface performance measurements during the
most previous 1-day (24 hour) measurement interval. The value of this
counter is equal to the value of the current day counter at the end of its
most recent interval.
In the case where the agent has no valid data available for this interval the
corresponding object instance is not available and upon a retrieval request
a corresponding error message shall be returned to indicate that this
instance does not exist (for example, a noSuchName error for SNMPv1
and a noSuchInstance for SNMPv2 GET operation).
— Syntax
•
AdslPerfTimeElapsed
Gauge32
- The number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the
187
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
system's time-of-day clock, the current interval exceeds the maximum
value, the agent will return the maximum value.
— Syntax
Gauge32
5.11.1.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Naming Conventions
Atuc
- (ATUC) modem at near (Central) end of line
Atur
- (ATUR) modem at Remote end of line
Curr
- Current
Prev
- Previous
Atn
- Attenuation
ES
- Errored Second.
LCS
- Line Code Specific
Lof
- Loss of Frame
Lol
- Loss of Link
Los
- Loss of Signal
Lpr
- Loss of Power
Ixxxs - interval of Seconds in which xxx occurs (for example, xxx=Lof, Los, Lpr)
Max
- Maximum
Mgn
- Margin
Min
- Minimum
Psd
- Power Spectral Density
Snr
- Signal to Noise Ratio
Tx
- Transmit
Blks
- Blocks, a data unit, see adslAtuXChanCrcBlockLength
5.11.1.3
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
adslMIB
adslLineMib
adslMibObjects
adslTraps
adsAtucTraps
adsAturTraps
-
adslLCSMib
- { adslMibObjects 16 } 1.3.6.1.2.1.10.94.1.1.16
•
5.11.2
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 94 }
{ adslMIB 1 }
{ adslLineMib 1 }
{ adslLineMib 2 }
{ adslTraps 1 }
{ adslTraps 2 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.94
1.3.6.1.2.1.10.94.1
1.3.6.1.2.1.10.94.1.1
1.3.6.1.2.1.10.94.1.2
1.3.6.1.2.1.10.94.1.2.1
1.3.6.1.2.1.10.94.1.2.2
MIB Objects
This MIB has multiple parallel tables.
•
•
•
line - common attributes
atuc and atur status
atuc and atur performance
—
Current and up to 96 buckets of 15 min performance history
188
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
•
—
Current and Previous 1-day bucket performance history
profiles
Table 96: ADSL-LINE-MIB Objects
Object
OID
Syntax
SEQUENCE of
Access
Status
Supported
adslLineTable
{ adslMibObjects 1 }
adslLineEntry
not-accessible
current
Y
adslAtucPhysTable
{ adslMibObjects 2 }
adslAtucPhysEntry
not-accessible
current
Y
adslAturPhysTable
{ adslMibObjects 3 }
adslAturPhysEntry
not-accessible
current
Y
adslAtucChanTable
{ adslMibObjects 4 }
adslAtucChanEntry
not-accessible
current
Y
adslAturChanTable
{ adslMibObjects 5 }
adslAturChanEntry
not-accessible
current
Y
adslAtucPerfDataTable
{ adslMibObjects 6 }
adslAtucPerfDataEntry
not-accessible
current
Y
adslAturPerfDataTable
{ adslMibObjects 7 }
adslAturPerfDataEntry
not-accessible
current
Y
adslAtucIntervalTable
{ adslMibObjects 8 }
adslAtucIntervalEntry
not-accessible
current
Y
adslAturIntervalTable
{ adslMibObjects 9 }
adslAturIntervalEntry
not-accessible
current
Y
adslAtucChanPerfDataTable
{ adslMibObjects 10 }
adslAtucChanPerfDataEntry
not-accessible
current
Y
adslAturChanPerfDataTable
{ adslMibObjects 11 }
adslAturChanPerfDataEntry
not-accessible
current
Y
adslAtucChanIntervalTable
{ adslMibObjects 12 }
adslAtucChanIntervalEntry
not-accessible
current
Y
adslAturChanIntervalTable
{ adslMibObjects 13 }
adslAturChanIntervalEntry
not-accessible
current
Y
adslLineConfProfileTable
{ adslMibObjects 14 }
adslLineConfProfileEntry
not-accessible
current
Y
adslLineAlarmConfProfileTable
{ adslMibObjects 15 }
adslLineAlarmConfProfileEntry
not-accessible
current
Y
5.11.2.1
adslLineTable
The ADSL Line Table includes common attributes describing both ends of the line. It is required for all ADSL
physical interfaces. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
This table is a sequence of adslLineEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslLineTable
adslLineEntry
- { adslMibObjects 1 }
- { adslLineTable 1}
1.3.6.1.2.1.10.94.1.1.1
1.3.6.1.2.1.10.94.1.1.1.2
189
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 97: adslLineTable
Object
OID
Syntax
Access
Status
Supported
adslLineCoding
{ adslLineEntry 1 }
AdslLineCodingType
read-only
current
Y
adslLineType
{ adslLineEntry 2 }
INTEGER
noChannel(1)
fastOnly(2)
interleavedOnly(3)
fastOrInterleaved(4)
fastAndInterLeaved(5)
read-only
current
Y
adslLineSpecific
{ adslLineEntry 3 }
VariablePointer
read-only
current
Y
adslLineConfProfile
{ adslLineEntry 4 }
SnmpAdminString
(SIZE (1…32))
read-write
current
Y
adslLineAlarmConfProfile
{ adslLineEntry 5 }
SnmpAdminString
(SIZE (1…32))
read-write
current
Y
5.11.2.1.1
adslLineCoding
Specifies the ADSL coding type used on this line.
Valid Object Value(s)
•
•
ADSL
—
dmt(2)
reachDSL
—
other(1)
5.11.2.1.2
adslLineType
Defines the type of ADSL physical line entity that exists, by defining whether and how the line is channelized. If the
line is channelized, the value will be other than noChannel(1). This object defines which channel type(s) are
supported.
In the case that the line is channelized, the manager can use the ifStackTable to determine the ifIndex for the
associated channel(s).
•
•
•
•
•
noChannel (1)
fastOnly (2)
interleavedOnly (3)
fastOrInterleaved (4)
fastAndInterleaved (5)
-
no channels exist
fast channel exists only
interleaved channel exists only
either fast or interleaved channels can exist, but only one at any time
both fast or interleaved channels exist
Valid Object Value(s)
•
•
ADSL
—
fastOrInterleaved (4)
reachDSL
—
fastOnly(2)
190
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.1.3
adslLineSpecific
OID instance in vendor-specific MIB. The Instance may be used to determine shelf/slot/port of the ATUC interface in
a DSLAM.
5.11.2.1.4
adslLineConfProfile
The value of this object identifies the row in the ADSL Line Configuration Profile Table, (adslLineConfProfileTable,
Section 5.11.2.14, Page 215) which applies for this ADSL Line, and channels if applicable.
For “dynamic” mode, in the case which the configuration profile has not been set, the value is set to “DEFVAL.” If the
implementator of this MIB has chosen not to implement “dynamic assignment” of profiles, this object's MINACCESS is read-only.
5.11.2.1.5
adslLineAlarmConfProfile
The value of this object identifies the row in the ADSL Line Alarm Configuration Profile Table,
adslLineAlarmConfProfileTable, Section 5.11.2.15, Page 223) which applies to this ADSL line, and channels if
applicable.
For “dynamic” mode, in the case which the alarm profile has not been set, the value is set to “DEFVAL.”
If the implementator of this MIB has chosen not to implement “dynamic assignment” of profiles, this object's MINACCESS is read-only.
5.11.2.2
adslAtucPhysTable
The ADSL ATU-C Physical Table provides one row for each ATUC. Each row contains the Physical Layer
Parameters table for that ATUC. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
This table is a sequence of adslAtucPhysEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAtucPhysTable
adslAtucPhysEntry
- { adslMibObjects 2 }
- { adslAtucPhysTable 1}
1.3.6.1.2.1.10.94.1.1.2
1.3.6.1.2.1.10.94.1.1.2.1
Table 98: adslAtucPhysTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucInvSerialNumber
{ adslAtucPhysEntry 1 }
SnmpAdminString
(SIZE (0…32))
read-only
current
Y
adslAtucInvVendorID
{ adslAtucPhysEntry 2 }
SnmpAdminString
(SIZE (0…16))
read-only
current
Y
adslAtucInvVersionNumber
{ adslAtucPhysEntry 3 }
SnmpAdminString
(SIZE (0…16))
read-only
current
Y
191
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 98: adslAtucPhysTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucCurrSnrMgn
{ adslAtucPhysEntry 4 }
INTEGER
(-640…640)
read-only
current
Y
adslAtucCurrAtn
{ adslAtucPhysEntry 5 }
Gauge32(0…630)
read-only
current
Y
adslAtucCurrStatus
{ adslAtucPhysEntry 6 }
BITS
read-only
current
Y
adslAtucCurrOutputPwr
{ adslAtucPhysEntry 7 }
INTEGER
read-only
current
Y
adslAtucCurrAttainableRate
{ adslAtucPhysEntry 8 }
Gauge32
read-only
current
Y
5.11.2.2.1
adslAtucInvSerialNumber
The vendor specific string that identifies the vendor equipment.
Valid Object Value(s)
The value of this object is the serial number of chassis the port is associated with.
5.11.2.2.2
adslAtucInvVendorID
The vendor ID code is a copy of the binary vendor identification field defined by the ANSI T1.413-1995 specification
and expressed as readable characters.
Valid Object Value(s)
This object will take on a value of 0011b as assigned to “Paradyne” in Annex D of Issue 2 of the T1.413 specification.
5.11.2.2.3
adslAtucInvVersionNumber
The vendor specific version number sent by this ATU as part of the initialization messages. It is a copy of the binary
version number field defined by the ANSI T1.413-1995 specification and expressed as readable characters.
Valid Object Value(s)
The value of this object will indicate a version number that is significant for upgrades, diagnostics, maintenance, etc.
5.11.2.2.4
adslAtucCurrSnrMgn
Noise Margin as seen by this ATU with respect to its received signal in tenths of a decibel.
5.11.2.2.5
adslAtucCurrAtn
Measured difference in the total power transmitted by the peer ATU and the total power received by this ATU in
tenths of a decibel.
5.11.2.2.6
adslAtucCurrStatus
Indicates current state of the ATUC line. This is a bit-map of possible conditions. The various bit positions are:
•
•
•
noDefect(0)
lossOfFraming(1)
lossOfSignal(2)
- There no defects on the line
- ATUC failure due to not receiving valid frame
- ATUC failure due to not receiving signal
192
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
•
•
•
•
•
•
•
lossOfPower(3)
- ATUC failure due to loss of power
lossOfSignalQuality(4) - Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds 10^-7
lossOfLink(5)
- TUC failure due to inability to link with ATUR
dataInitFailure(6)
- ATUC failure during initialization due to bit errors corrupting start-up exchange
data
configInitFailure(7)
- ATUC failure during initialization due to peer ATU not able to support
requested configuration
protocolInitFailure(8) - ATUC failure during initialization due to incompatible protocol used by the peer
ATU
noPeerAtuPresent(9)
- ATUC failure during initialization due to no activation sequence detected from
peer ATU
This is intended to supplement ifOperStatus.
5.11.2.2.7
adslAtucCurrOutputPwr
Measured total output power, in tenths of a dBm, transmitted by this ATU. This is the measurement that was reported
during the last activation sequence.
5.11.2.2.8
adslAtucCurrAttainableRate
Indicates the maximum currently attainable data rate by the ATU. This value is equal or greater than the current line
rate.
5.11.2.3
adslAturPhysTable
This table provides one row for each ATUR Each row contains the Physical Layer Parameters table for that ATUR.
ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
This table is a sequence of adslAturPhysEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAturPhysTable
adslAturPhysEntry
- { adslMibObjects 3 }
- { adslAturPhysTable 1}
1.3.6.1.2.1.10.94.1.1.3
1.3.6.1.2.1.10.94.1.1.3.1
Table 99: adslAturPhysTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturInvSerialNumber
{ adslAturPhysEntry 1 }
SnmpAdminString
(SIZE (0…32))
read-only
current
Y
adslAturInvVendorID
{ adslAturPhysEntry 2 }
SnmpAdminString
(SIZE (0…16))
read-only
current
Y
adslAturInvVersionNumber
{ adslAturPhysEntry 3 }
SnmpAdminString
(SIZE (0…16))
read-only
current
Y
193
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 99: adslAturPhysTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturCurrSnrMgn
{ adslAturPhysEntry 4 }
INTEGER
(-640…640)
read-only
current
Y
adslAturCurrAtn
{ adslAturPhysEntry 5 }
Gauge32
(0…630)
read-only
current
Y
adslAturCurrStatus
{ adslAturPhysEntry 6 }
BITS
read-only
current
Y
adslAturCurrOutputPwr
{ adslAturPhysEntry 7 }
INTEGER
read-only
current
Y
adslAturCurrAttainableRate
{ adslAturPhysEntry 8 }
Gauge32
read-only
current
Y
5.11.2.3.1
adslAturInvSerialNumber
The vendor specific string that identifies the vendor equipment.
5.11.2.3.2
adslAturInvVendorID
The vendor ID code is a copy of the binary vendor identification field defined by the ANSI T1.413-1995 specification
and expressed as readable characters.
5.11.2.3.3
adslAturInvVersionNumber
The vendor specific version number sent by this ATU as part of the initialization messages. It is a copy of the binary
version number field defined by the ANSI T1.413-1995 specification and expressed as readable characters.
5.11.2.3.4
adslAturCurrSnrMgn
Noise Margin as seen by this ATU with respect to its received signal in tenths of a decibel.
5.11.2.3.5
adslAturCurrAtn
Measured difference in the total power, in tenths of a decibel, transmitted by the peer ATU and the total power
received by this ATU.
5.11.2.3.6
adslAturCurrStatus
Indicates current state of the ATUR line. This is a bit-map of possible conditions. Due to the isolation of the ATUR
when line problems occur, many state conditions like loss of power, loss of quality signal, and initialization errors,
can not be determined. While trouble shooting ATUR, also use object, adslAtucCurrStatus. The various bit positions
are:
•
•
•
•
•
noDefect(0)
lossOfFraming(1)
lossOfSignal(2)
lossOfPower(3)
lossOfSignalQuality(4)
-
There no defects on the line
ATUR failure due to not receiving valid frame
ATUR failure due to not receiving signal
ATUR failure due to loss of power
Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds 10^-7
This is intended to supplement ifOperStatus.
194
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.3.7
adslAturCurrOutputPwr
Measured total output power transmitted by this ATU. This is the measurement that was reported during the last
activation sequence.
5.11.2.3.8
adslAturCurrAttainableRate
Indicates the maximum currently attainable data rate by the ATU. This value is equal or greater than the current line
rate.
5.11.2.4
adslAtucChanTable
This table provides one row for each ATUC channel. ADSL channel interfaces are those ifEntries where ifType is
equal to adslInterleave(124) or adslFast(125).
This table is a sequence of adslAtucChanEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAtucChanTable
adslAtucChanEntry
- { adslMibObjects 4 }
- { adslAtucChanTable 1}
1.3.6.1.2.1.10.94.1.1.4
1.3.6.1.2.1.10.94.1.1.4.1
Table 100: adslAutcChanTable
Object
OID
Syntax
Access
Status
Supported
adslAtucChanInterleaveDelay
{ adslAtucChanEntry 1 }
Gauge32
read-only
current
Y
adslAtucChanCurrTxRate
{ adslAtucChanEntry 2 }
Gauge32
read-only
current
Y
adslAtucChanPrevTxRate
{ adslAtucChanEntry 3 }
Gauge32
read-only
current
Y
adslAtucChanCrcBlockLength
{ adslAtucChanEntry 4 }
Gauge32
read-only
current
Y
5.11.2.4.1
adslAtucChanInterleaveDelay
Interleave Delay for this channel in milli-seconds.
Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent
input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers
provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse
noise immunity at the expense of payload latency.
In the case where the ifType is Fast(125), use noSuchObject.
5.11.2.4.2
adslAtucChanCurrTxRate
Actual transmit rate on this channel in bps.
195
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.4.3
adslAtucChanPrevTxRate
The rate, in bps, at the time of the last adslAtucRateChangeTrap event. It is also set at initialization to prevent a trap
being sent.
Rate changes less than adslAtucThresh (*) RateDown or less than adslAtucThresh (*) RateUp will not cause a trap or
cause this object to change.
(*) == Fast or Interleave.
See adslLineAlarmConfProfileTable, Section 5.11.2.15, Page 223.
5.11.2.4.4
adslAtucChanCrcBlockLength
Indicates the length, in bytes, of the channel data-block on which the CRC operates. Reference the following Line
Code Specific MIBs for more information:
•
•
ADSL Forum WT-014, “DMT Line Code Specific MIB,” February 1999
ADSL Forum WT-015, “CAP Line Code Specific MIB,” February 1999
5.11.2.5
adslAturChanTable
This table provides one row for each ATUR channel. ADSL channel interfaces are those ifEntries where ifType is
equal to adslInterleave(124) or adslFast(125).
This table is a sequence of adslAturChanEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAturChanTable
adslAturChanEntry
- { adslMibObjects 5 }
- { adslAturChanTable 1 }
1.3.6.1.2.1.10.94.1.1.5
1.3.6.1.2.1.10.94.1.1.5.1
Table 101: adslAturChanTable
Object
OID
Syntax
Access
Status
Supported
adslAturChanInterleaveDelay
{ adslAturChanEntry 1 }
Gauge32
read-only
current
Y
adslAturChanCurrTxRate
{ adslAturChanEntry 2 }
Gauge32
read-only
current
Y
adslAturChanPrevTxRate
{ adslAturChanEntry 3 }
Gauge32
read-only
current
Y
adslAturChanCrcBlockLength
{ adslAturChanEntry 4 }
Gauge32
read-only
current
Y
5.11.2.5.1
adslAturChanInterleaveDelay
Interleave Delay for this channel in units of milli-seconds.
Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent
196
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers
provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse
noise immunity at the expense of payload latency.
In the case where the ifType is Fast(125), use noSuchObject.
5.11.2.5.2
adslAturChanCurrTxRate
The actual transmit rate on this channel. in bps.
5.11.2.5.3
adslAturChanPrevTxRate
The rate, in bps, at the time of the last adslAturRateChangeTrap event. It is also set at initialization to prevent a trap
being sent. Rate changes less than adslAturThresh (*) RateDown or less than adslAturThresh (*) RateUp will not
cause a trap or cause this object to change.
(*) == Fast or Interleave.
See adslLineAlarmConfProfileTable, Section 5.11.2.15, Page 223.
5.11.2.5.4
adslAturChanCrcBlockLength
Indicates the length of the channel data-block on which the CRC operates. Reference the following Line Code
Specific MIBs for more information:
•
•
ADSL Forum WT-014, “DMT Line Code Specific MIB,” February 1999
ADSL Forum WT-015, “CAP Line Code Specific MIB,” February 1999
5.11.2.6
adslAtucPerfDataTable
This table provides one row for each ATUC. ADSL physical interfaces are those ifEntries where ifType is equal to
adsl(94).
This table is a sequence of adslAtucPerfDataEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAtucPerfDataTable
adslAtucPerfDataEntry
- { adslMibObjects 6 }
- { adslAtucPerfDataTable 1 }
1.3.6.1.2.1.10.94.1.1.6
1.3.6.1.2.1.10.94.1.1.6.1
Table 102: adslAtucPerfDataTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucPerfLofs
{ adslAtucPerfDataEntry 1 }
Counter32
read-only
current
Y
adslAtucPerfLoss
{ adslAtucPerfDataEntry 2 }
Counter32
read-only
current
Y
adslAtucPerfLols
{ adslAtucPerfDataEntry 3 }
Counter32
read-only
current
Y
adslAtucPerfLprs
{ adslAtucPerfDataEntry 4 }
Counter32
read-only
current
N
197
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 102: adslAtucPerfDataTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucPerfESs
{ adslAtucPerfDataEntry 5 }
Counter32
read-only
current
Y
adslAtucPerfInits
{ adslAtucPerfDataEntry 6 }
Counter32
read-only
current
Y
adslAtucPerfValidIntervals
{ adslAtucPerfDataEntry 7 }
INTEGER
(0…96)
read-only
current
Y
adslAtucPerfInvalidIntervals
{ adslAtucPerfDataEntry 8 }
INTEGER
(0…96)
read-only
current
Y
adslAtucPerfCurr15MinTimeElapsed
{ adslAtucPerfDataEntry 9 }
AdslPerfTimeElapsed
(0…899)
read-only
current
Y
adslAtucPerfCurr15MinLofs
{ adslAtucPerfDataEntry 10 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinLoss
{ adslAtucPerfDataEntry 11 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinLols
{ adslAtucPerfDataEntry 12 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinLprs
{ adslAtucPerfDataEntry 13 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinESs
{ adslAtucPerfDataEntry 14 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinInits
{ adslAtucPerfDataEntry 15 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr1DayTimeElapsed
{ adslAtucPerfDataEntry 16 }
AdslPerfTimeElapsed
read-only
current
Y
adslAtucPerfCurr1DayLofs
{ adslAtucPerfDataEntry 17 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayLoss
{ adslAtucPerfDataEntry 18 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayLols
{ adslAtucPerfDataEntry 19 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayLprs
{ adslAtucPerfDataEntry 20 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayESs
{ adslAtucPerfDataEntry 21 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayInits
{ adslAtucPerfDataEntry 22 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfPrev1DayMoniSecs
{ adslAtucPerfDataEntry 23 }
INTEGER(0…86400)
read-only
current
Y
adslAtucPerfPrev1DayLofs
{ adslAtucPerfDataEntry 24 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayLoss
{ adslAtucPerfDataEntry 25 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayLols
{ adslAtucPerfDataEntry 26 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayLprs
{ adslAtucPerfDataEntry 27 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayESs
{ adslAtucPerfDataEntry 28 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayInits
{ adslAtucPerfDataEntry 29 }
AdslPerfPrevDayCount
read-only
current
Y
Also see adslAtucIntervalTable for 15 minute interval elapsed counters.
198
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.6.1
adslAtucPerfLofs
Count of the number of Loss of Framing failures since agent reset.
5.11.2.6.2
adslAtucPerfLoss
Count of the number of Loss of Signal failures since agent reset.
5.11.2.6.3
adslAtucPerfLols
Count of the number of Loss of Link failures since agent reset.
5.11.2.6.4
adslAtucPerfLprs
Count of the number of Loss of Power failures since agent reset.
5.11.2.6.5
adslAtucPerfESs
Count of the number of Errored Seconds since agent reset. The errored second parameter is a count of one-second
intervals containing one or more crc anomalies, or one or more los or sef defects.
5.11.2.6.6
adslAtucPerfInits
Count of the line initialization attempts since agent reset. Includes both successful and failed attempts.
5.11.2.6.7
adslAtucPerfValidIntervals
The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the
maximum # of intervals supported. The value is <n> unless the measurement was (re-)started within the last
(<n>*15) minutes, in which case the value is the number of complete 15 minute intervals for which the agent has at
least some data. In certain cases (for example, in the case where the agent is a proxy) it is possible that some intervals
are unavailable. In this case, this interval is the maximum interval number for which data is available.
5.11.2.6.8
adslAtucPerfInvalidIntervals
The number of intervals in the range from 0 to the value of adslAtucPerfValidIntervals for which no data is available.
This object will typically be zero except in cases where the data for some intervals are not available (for example, in
proxy situations).
5.11.2.6.9
adslAtucPerfCurr15MinTimeElapsed
Total elapsed seconds in this interval.
5.11.2.6.10 adslAtucPerfCurr15MinLofs
Count of seconds in the current 15 minute interval when there was Loss of Framing.
5.11.2.6.11
adslAtucPerfCurr15MinLoss
Count of seconds in the current 15 minute interval when there was Loss of Signal.
5.11.2.6.12 adslAtucPerfCurr15MinLols
Count of seconds in the current 15 minute interval when there was Loss of Link.
5.11.2.6.13 adslAtucPerfCurr15MinLprs
Count of seconds in the current 15 minute interval when there was Loss of Power.
199
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.6.14 adslAtucPerfCurr15MinESs
Count of Errored Seconds in the current 15 minute interval. The errored second parameter is a count of one-second
intervals containing one or more crc anomalies, or one or more los or sef defects.
5.11.2.6.15 adslAtucPerfCurr15MinInits
Count of the line initialization attempts in the current 15 minute interval. Includes both successful and failed attempts.
5.11.2.6.16 adslAtucPerfCurr1DayTimeElapsed
Number of seconds that have elapsed since the beginning of the current 1-day interval.
5.11.2.6.17 adslAtucPerfCurr1DayLofs
Count of the number of seconds when there was Loss of Framing during the current day as measured by
adslAtucPerfCurr1DayTimeElapsed.
5.11.2.6.18 adslAtucPerfCurr1DayLoss
Count of the number of seconds when there was Loss of Signal during the current day as measured by
adslAtucPerfCurr1DayTimeElapsed.
5.11.2.6.19 adslAtucPerfCurr1DayLols
Count of the number of seconds when there was Loss of Link during the current day as measured by
adslAtucPerfCurr1DayTimeElapsed.
5.11.2.6.20 adslAtucPerfCurr1DayLprs
Count of the number of seconds when there was Loss of Power during the current day as measured by
adslAtucPerfCurr1DayTimeElapsed.
5.11.2.6.21 adslAtucPerfCurr1DayESs
Count of Errored Seconds during the current day as measured by adslAtucPerfCurr1DayTimeElapsed. The errored
second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef
defects.
5.11.2.6.22 adslAtucPerfCurr1DayInits
Count of the line initialization attempts in the day as measured by adslAtucPerfCurr1DayTimeElapsed. Includes both
successful and failed attempts.
5.11.2.6.23 adslAtucPerfPrev1DayMoniSecs
The amount of time in the previous 1-day interval over which the performance monitoring information is actually
counted. This value is the same as the interval duration except in a situation where performance monitoring data
could not be collected for any reason.
5.11.2.6.24 adslAtucPerfPrev1DayLofs
Count of seconds in the interval when there was Loss of Framing within the most recent previous 1-day period.
5.11.2.6.25 adslAtucPerfPrev1DayLoss
Count of seconds in the interval when there was Loss of Signal within the most recent previous 1-day period.
200
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.6.26 adslAtucPerfPrev1DayLols
Count of seconds in the interval when there was Loss of Link within the most recent previous 1-day period.
5.11.2.6.27 adslAtucPerfPrev1DayLprs
Count of seconds in the interval when there was Loss of Power within the most recent previous 1-day period.
5.11.2.6.28 adslAtucPerfPrev1DayESs
Count of Errored Seconds within the most recent previous 1-day period. The errored second parameter is a count of
one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
5.11.2.6.29 adslAtucPerfPrev1DayInits
Count of the line initialization attempts in the most recent previous 1-day period. Includes both successful and failed
attempts.
5.11.2.7
adslAturPerfDataTable
This table provides one row for each ATUR. ADSL physical interfaces are those ifEntries where ifType is equal to
adsl(94).
This table is a sequence of adslAturPerfDataEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAturPerfDataTable
adslAturPerfDataEntry
- { adslMibObjects 7 }
- { adslAturPerfDataTable 1 }
1.3.6.1.2.1.10.94.1.1.7
1.3.6.1.2.1.10.94.1.1.7.1
Table 103: adslAturPerfDataTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturPerfLofs
{ adslAturPerfDataEntry 1 }
Counter32
read-only
current
Y
adslAturPerfLoss
{ adslAturPerfDataEntry 2 }
Counter32
read-only
current
Y
adslAturPerfLprs
{ adslAturPerfDataEntry 3 }
Counter32
read-only
current
Y
adslAturPerfESs
{ adslAturPerfDataEntry 4 }
Counter32
read-only
current
Y
adslAturPerfValidIntervals
{ adslAturPerfDataEntry 5 }
INTEGER
(0…96)
read-only
current
Y
adslAturPerfInvalidIntervals
{ adslAturPerfDataEntry 6 }
INTEGER
(0…96)
read-only
current
Y
adslAturPerfCurr15MinTimeElapsed
{ adslAturPerfDataEntry 7 }
AdslPerfTimeElapsed
(0…899)
read-only
current
Y
adslAturPerfCurr15MinLofs
{ adslAturPerfDataEntry 8 }
PerfCurrentCount
read-only
current
Y
201
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 103: adslAturPerfDataTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturPerfCurr15MinLoss
{ adslAturPerfDataEntry 9 }
PerfCurrentCount
read-only
current
Y
adslAturPerfCurr15MinLprs
{ adslAturPerfDataEntry 10 }
PerfCurrentCount
read-only
current
Y
adslAturPerfCurr15MinESs
{ adslAturPerfDataEntry 11 }
PerfCurrentCount
read-only
current
Y
adslAturPerfCurr1DayTimeElapsed
{ adslAturPerfDataEntry 12 }
AdslPerfTimeElapsed
read-only
current
Y
adslAturPerfCurr1DayLofs
{ adslAturPerfDataEntry 13 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturPerfCurr1DayLoss
{ adslAturPerfDataEntry 14 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturPerfCurr1DayLprs
{ adslAturPerfDataEntry 15 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturPerfCurr1DayESs
{ adslAturPerfDataEntry 16 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturPerfPrev1DayMoniSecs
{ adslAturPerfDataEntry 17 }
INTEGER
(0…86400)
read-only
current
Y
adslAturPerfPrev1DayLofs
{ adslAturPerfDataEntry 18 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturPerfPrev1DayLoss
{ adslAturPerfDataEntry 19 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturPerfPrev1DayLprs
{ adslAturPerfDataEntry 20 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturPerfPrev1DayESs
{ adslAturPerfDataEntry 21 }
AdslPerfPrevDayCount
read-only
current
Y
5.11.2.7.1
adslAturPerfLofs
Count of the number of Loss of Framing failures since agent reset.
5.11.2.7.2
adslAturPerfLoss
Count of the number of Loss of Signal failures since agent reset.
5.11.2.7.3
adslAturPerfLprs
Count of the number of Loss of Power failures since agent reset.
5.11.2.7.4
adslAturPerfESs
Count of the number of Errored Seconds since agent reset. The errored second parameter is a count of one-second
intervals containing one or more crc anomalies, or one or more los or sef defects.
5.11.2.7.5
adslAturPerfValidIntervals
The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the
maximum # of intervals supported. The value is <n> unless the measurement was (re-)started within the last
(<n>*15) minutes, in which case the value is the number of complete 15 minute intervals for which the agent has at
least some data. In certain cases (for example, in the case where the agent is a proxy) it is possible that some intervals
are unavailable. In this case, this interval is the maximum interval number for which data is available.
202
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.7.6
adslAturPerfInvalidIntervals
The number of intervals in the range from 0 to the value of adslAturPerfValidIntervals for which no data is available.
This object will typically be zero except in cases where the data for some intervals are not available (for example, in
proxy situations).
5.11.2.7.7
adslAturPerfCurr15MinTimeElapsed
Total elapsed seconds in this interval.
5.11.2.7.8
adslAturPerfCurr15MinLofs
Count of seconds in the current 15 minute interval when there was Loss of Framing.
5.11.2.7.9
adslAturPerfCurr15MinLoss
Count of seconds in the current 15 minute interval when there was Loss of Signal.
5.11.2.7.10 adslAturPerfCurr15MinLprs
Count of seconds in the current 15 minute interval when there was Loss of Power.
5.11.2.7.11
adslAturPerfCurr15MinESs
Count of Errored Seconds in the current 15 minute interval. The errored second parameter is a count of one-second
intervals containing one or more crc nomalies, or one or more los or sef defects.
5.11.2.7.12 adslAturPerfCurr1DayTimeElapsed
Number of seconds that have elapsed since the beginning of the current 1-day interval.
5.11.2.7.13 adslAturPerfCurr1DayLofs
Count of the number of seconds when there was Loss of Framing during the current day as measured by
adslAturPerfCurr1DayTimeElapsed.
5.11.2.7.14 adslAturPerfCurr1DayLoss
Count of the number of seconds when there was Loss of Signal during the current day as measured by
adslAturPerfCurr1DayTimeElapsed.
5.11.2.7.15 adslAturPerfCurr1DayLprs
Count of the number of seconds when there was Loss of Power during the current day as measured by
adslAturPerfCurr1DayTimeElapsed.
5.11.2.7.16 adslAturPerfCurr1DayESs
Count of Errored Seconds during the current day as measured by adslAturPerfCurr1DayTimeElapsed. The errored
second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef
defects.
5.11.2.7.17 adslAturPerfPrev1DayMoniSecs
The amount of time in the previous 1-day interval over which the performance monitoring information is actually
counted. This value is the same as the interval duration except in a situation where performance monitoring data
could not be collected for any reason.
203
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.7.18 adslAturPerfPrev1DayLofs
Count of seconds in the interval when there was Loss of Framing within the most recent previous 1-day period.
5.11.2.7.19 adslAturPerfPrev1DayLoss
Count of seconds in the interval when there was Loss of Signal within the most recent previous 1-day period.
5.11.2.7.20 adslAturPerfPrev1DayLprs
Count of seconds in the interval when there was Loss of Power within the most recent previous 1-day period.
5.11.2.7.21 adslAturPerfPrev1DayESs
Count of Errored Seconds within the most recent previous 1-day period. The errored second parameter is a count of
one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
5.11.2.8
adslAtucIntervalTable
This table provides one row for each ATUC performance data collection interval. ADSL physical interfaces are those
ifEntries where ifType is equal to adsl(94).
This table is a sequence of adslAtucIntervalEntry.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
adslAtucIntervalNumber
OIDs:
•
•
adslAtucIntervalTable
adslAtucIntervalEntry
- { adslMibObjects 8 }
- { adslAtucIntervalTable 1 }
1.3.6.1.2.1.10.94.1.1.8
1.3.6.1.2.1.10.94.1.1.8.1
Table 104: adslAtucIntervalTable
Object
OID
Syntax
Access
Status
Supported
adslAtucIntervalNumber
{ adslAtucIntervalEntry 1 }
INTEGER(1…96)
read-only
current
Y
adslAtucIntervalLofs
{ adslAtucIntervalEntry 2 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalLoss
{ adslAtucIntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalLols
{ adslAtucIntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalLprs
{ adslAtucIntervalEntry 5 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalESs
{ adslAtucIntervalEntry 6 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalInits
{ adslAtucIntervalEntry 7 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalValidData
{ adslAtucIntervalEntry 8 }
TruthValue
read-only
current
Y
204
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.8.1
adslAtucIntervalNumber
Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2…96
are optional.
5.11.2.8.2
adslAtucIntervalLofs
Count of seconds in the interval when there was Loss of Framing.
5.11.2.8.3
adslAtucIntervalLoss
Count of seconds in the interval when there was Loss of Signal.
5.11.2.8.4
adslAtucIntervalLols
Count of seconds in the interval when there was Loss of Link.
5.11.2.8.5
adslAtucIntervalLprs
Count of seconds in the interval when there was Loss of Power.
5.11.2.8.6
adslAtucIntervalESs
Count of Errored Seconds in the interval. The errored second parameter is a count of one-second intervals containing
one or more crc anomalies, or one or more los or sef defects.
5.11.2.8.7
adslAtucIntervalInits
Count of the line initialization attempts during the interval. Includes both successful and failed attempts.
5.11.2.8.8
adslAtucIntervalValidData
This variable indicates if the data for this interval is valid.
5.11.2.9
adslAturIntervalTable
This table provides one row for each ATUR performance data collection interval. ADSL physical interfaces are those
ifEntries where ifType is equal to adsl(94).
The index for this table is the ifIndex and adslAturIntervalNumber objects. This table is a sequence of
adslAturIntervalEntry.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
adslAturIntervalNumber
OIDs:
•
•
adslAturIntervalTable
adslAturIntervalEntry
- { adslMibObjects 9 }
- { adslAturIntervalTable 1 }
205
1.3.6.1.2.1.10.94.1.1.9
1.3.6.1.2.1.10.94.1.1.9.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 105: adslAturIntervalTable
Object
OID
Syntax
Access
Status
Supported
adslAturIntervalNumber
{ adslAturIntervalEntry 1 }
INTEGER(1…96)
read-only
current
Y
adslAturIntervalLofs
{ adslAturIntervalEntry 2 }
PerfIntervalCount
read-only
current
Y
adslAturIntervalLoss
{ adslAturIntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
adslAturIntervalLprs
{ adslAturIntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
adslAturIntervalESs
{ adslAturIntervalEntry 5 }
PerfIntervalCount
read-only
current
Y
adslAturIntervalValidData
{ adslAturIntervalEntry 6 }
TruthValue
read-only
current
Y
5.11.2.9.1
adslAturIntervalNumber
Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2…96
are optional.
5.11.2.9.2
adslAturIntervalLofs
Count of seconds in the interval when there was Loss of Framing.
5.11.2.9.3
adslAturIntervalLoss
Count of seconds in the interval when there was Loss of Signal.
5.11.2.9.4
adslAturIntervalLprs
Count of seconds in the interval when there was Loss of Power.
5.11.2.9.5
adslAturIntervalESs
Count of Errored Seconds in the interval. The errored second parameter is a count of one-second intervals containing
one or more crc anomalies, or one or more los or sef defects.
5.11.2.9.6
adslAturIntervalValidData
This variable indicates if the data for this interval is valid.
5.11.2.10 adslAtucChanPerfDataTable
This table provides one row for each ATUC channel. ADSL channel interfaces are those ifEntries where ifType is
equal to adslInterleave(124) or adslFast(125).
This table is a sequence of adslAtucChanPerfDataEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
206
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
OIDs:
•
•
adslAtucChanPerfDataTable
adslAtucChanPerfDataEntry
- { adslMibObjects 10 }
- { adslAtucChanPerfDataTable 1 }
1.3.6.1.2.1.10.94.1.1.10
1.3.6.1.2.1.10.94.1.1.10.1
Table 106: adslAtucChanPerfDataTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucChanReceivedBlks
{ adslAtucChanPerfDataEntry 1 }
Counter32
read-only
current
Y
adslAtucChanTransmittedBlks
{ adslAtucChanPerfDataEntry 2 }
Counter32
read-only
current
Y
adslAtucChanCorrectedBlks
{ adslAtucChanPerfDataEntry 3 }
Counter32
read-only
current
Y
adslAtucChanUnCorrectedBlks
{ adslAtucChanPerfDataEntry 4 }
Counter32
read-only
current
Y
adslAtucChanPerfValidIntervals
{ adslAtucChanPerfDataEntry 5 }
INTEGER
(0…96)
read-only
current
Y
adslAtucChanPerfInvalidIntervals
{ adslAtucChanPerfDataEntry 6 }
INTEGER
(0…96)
read-only
current
Y
adslAtucChanPerfCurr15MinTimeElapsed
{ adslAtucChanPerfDataEntry 7 }
AdslPerfTimeElapsed
(0…899)
read-only
current
Y
adslAtucChanPerfCurr15MinReceivedBlks
{ adslAtucChanPerfDataEntry 8 }
PerfCurrentCount
read-only
current
Y
adslAtucChanPerfCurr15MinTransmitted-Blks
{ adslAtucChanPerfDataEntry 9 }
PerfCurrentCount
read-only
current
Y
adslAtucChanPerfCurr15MinCorrectedBlks
{ adslAtucChanPerfDataEntry 10 }
PerfCurrentCount
read-only
current
Y
adslAtucChanPerfCurr15MinUncorrectBlks
{ adslAtucChanPerfDataEntry 11 }
PerfCurrentCount
read-only
current
Y
adslAtucChanPerfCurr1DayTimeElapsed
{ adslAtucChanPerfDataEntry 12 }
AdslPerfTimeElapsed
(0…86399)
read-only
current
Y
adslAtucChanPerfCurr1DayReceivedBlks
{ adslAtucChanPerfDataEntry 13 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucChanPerfCurr1DayTransmitted-Blks
{ adslAtucChanPerfDataEntry 14 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucChanPerfCurr1DayCorrectedBlks
{ adslAtucChanPerfDataEntry 15 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucChanPerfCurr1DayUncorrectBlks
{ adslAtucChanPerfDataEntry 16 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucChanPerfPrev1DayMoniSecs
{ adslAtucChanPerfDataEntry 17 }
INTEGER
(0…86400)
read-only
current
Y
adslAtucChanPerfPrev1DayReceivedBlks
{ adslAtucChanPerfDataEntry 18 }
AdslPerfPrevDayCount
read-only
current
Y
207
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 106: adslAtucChanPerfDataTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucChanPerfPrev1DayTransmitted-Blks
{ adslAtucChanPerfDataEntry 19 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucChanPerfPrev1DayCorrectedBlks
{ adslAtucChanPerfDataEntry 20 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucChanPerfPrev1DayUncorrectBlks
{ adslAtucChanPerfDataEntry 21 }
AdslPerfPrevDayCount
read-only
current
Y
Note: block is intended to be the length of the channel data-block on which the CRC operates. See
adslAtucChanCrcBlockLength for more information.
5.11.2.10.1 adslAtucChanReceivedBlks
Count of all encoded blocks received on this channel since agent reset.
5.11.2.10.2 adslAtucChanTransmittedBlks
Count of all encoded blocks transmitted on this channel since agent reset.
5.11.2.10.3 adslAtucChanCorrectedBlks
Count of all blocks received with errors that were corrected since agent reset. These blocks are passed on as good
data.
5.11.2.10.4 adslAtucChanUncorrectBlks
Count of all blocks received with uncorrectable errors since agent reset.
5.11.2.10.5 adslAtucChanPerfValidIntervals
The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the
maximum # of intervals supported. The value is <n> unless the measurement was (re-)started within the last
(<n>*15) minutes, in which case the value is the number of complete 15 minute intervals for which the agent has at
least some data. In certain cases (for example, in the case where the agent is a proxy) it is possible that some intervals
are unavailable. In this case, this interval is the maximum interval number for which data is available.
5.11.2.10.6 adslAtucChanPerfInvalidIntervals
The number of intervals in the range from 0 to the value of adslAtucChanPerfValidIntervals for which no data is
available. This object will typically be zero except in cases where the data for some intervals are not available (for
example, in proxy situations).
5.11.2.10.7 adslAtucChanPerfCurr15MinTimeElapsed
Total elapsed seconds in this interval.
5.11.2.10.8 adslAtucChanPerfCurr15MinReceivedBlks
Count of all encoded blocks received on this channel within the current 15 minute interval.
208
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.10.9 adslAtucChanPerfCurr15MinTransmittedBlks
Count of all encoded blocks transmitted on this channel within the current 15 minute interval.
5.11.2.10.10 adslAtucChanPerfCurr15MinCorrectedBlks
Count of all blocks received with errors that were corrected on this channel within the current 15 minute interval.
5.11.2.10.11 adslAtucChanPerfCurr15MinUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel within the current 15 minute interval.
5.11.2.10.12 adslAtucChanPerfCurr1DayTimeElapsed
Number of seconds that have elapsed since the beginning of the current 1-day interval.
5.11.2.10.13 adslAtucChanPerfCurr1DayReceivedBlks
Count of all encoded blocks received on this channel during the current day as measured by
adslAtucChanPerfCurr1DayTimeElapsed.
5.11.2.10.14 adslAtucChanPerfCurr1DayTransmittedBlks
Count of all encoded blocks transmitted on this channel during the current day as measured by
adslAtucChanPerfCurr1DayTimeElapsed.
5.11.2.10.15 adslAtucChanPerfCurr1DayCorrectedBlks
Count of all blocks received with errors that were corrected on this channel during the current day as measured by
adslAtucChanPerfCurr1DayTimeElapsed.
5.11.2.10.16 adslAtucChanPerfCurr1DayUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel during the current day as measured by
adslAtucChanPerfCurr1DayTimeElapsed.
5.11.2.10.17 adslAtucChanPerfPrev1DayMoniSecs
The amount of time in the previous 1-day interval over which the performance monitoring information is actually
counted. This value is the same as the interval duration except in a situation where performance monitoring data
could not be collected for any reason.
5.11.2.10.18 adslAtucChanPerfPrev1DayReceivedBlks
Count of all encoded blocks received on this channel within the most recent previous 1-day period.
5.11.2.10.19 adslAtucChanPerfPrev1DayTransmittedBlks
Count of all encoded blocks transmitted on this channel within the most recent previous 1-day period.
5.11.2.10.20 adslAtucChanPerfPrev1DayCorrectedBlks
Count of all blocks received with errors that were corrected on this channel within the most recent previous 1-day
period.
5.11.2.10.21 adslAtucChanPerfPrev1DayUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel within the most recent previous 1-day period.
209
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.11 adslAturChanPerfDataTable
This table provides one row for each ATUR channel. ADSL channel interfaces are those ifEntries where ifType is
equal to adslInterleave(124) or adslFast(125).
This table is a sequence of adslAturChanPerfDataEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAturChanPerfDataTable
adslAturChanPerfDataEntry
- { adslMibObjects 11 }
- { adslAturChanPerfDataTable 1 }
1.3.6.1.2.1.10.94.1.1.11
1.3.6.1.2.1.10.94.1.1.11.1
Table 107: adslAturChanPerfDataTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturChanReceivedBlks
{ adslAturChanPerfDataEntry 1 }
Counter32
read-only
current
Y
adslAturChanTransmittedBlks
{ adslAturChanPerfDataEntry 2 }
Counter32
read-only
current
Y
adslAturChanCorrectedBlks
{ adslAturChanPerfDataEntry 3 }
Counter32
read-only
current
Y
adslAturChanUnCorrectedBlks
{ adslAturChanPerfDataEntry 4 }
Counter32
read-only
current
Y
adslAturChanPerfValidIntervals
{ adslAturChanPerfDataEntry 5 }
INTEGER
(0…96)
read-only
current
Y
adslAturChanPerfInvalidIntervals
{ adslAturChanPerfDataEntry 6 }
INTEGER
(0…96)
read-only
current
Y
adslAturChanPerfCurr15MinTimeElapsed
{ adslAturChanPerfDataEntry 7 }
AdslPerfTimeElapsed
(0…899)
read-only
current
Y
adslAturChanPerfCurr15MinReceivedBlks
{ adslAturChanPerfDataEntry 8 }
PerfCurrentCount
read-only
current
Y
adslAturChanPerfCurr15MinTransmitted-Blks
{ adslAturChanPerfDataEntry 9 }
PerfCurrentCount
read-only
current
Y
adslAturChanPerfCurr15MinCorrectedBlks
{ adslAturChanPerfDataEntry 10 }
PerfCurrentCount
read-only
current
Y
adslAturChanPerfCurr15MinUncorrectBlks
{ adslAturChanPerfDataEntry 11 }
PerfCurrentCount
read-only
current
Y
adslAturChanPerfCurr1DayTimeElapsed
{ adslAturChanPerfDataEntry 12 }
AdslPerfTimeElapsed
(0…86399)
read-only
current
Y
adslAturChanPerfCurr1DayReceivedBlks
{ adslAturChanPerfDataEntry 13 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturChanPerfCurr1DayTransmittedBlks
{ adslAturChanPerfDataEntry 14 }
AdslPerfCurrDayCount
read-only
current
Y
210
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 107: adslAturChanPerfDataTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturChanPerfCurr1DayCorrectedBlks
{ adslAturChanPerfDataEntry 15 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturChanPerfCurr1DayUncorrectBlks
{ adslAturChanPerfDataEntry 16 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturChanPerfPrev1DayMoniSecs
{ adslAturChanPerfDataEntry 17 }
INTEGER (0…86400)
read-only
current
Y
adslAturChanPerfPrev1DayReceivedBlks
{ adslAturChanPerfDataEntry 21 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturChanPerfPrev1DayTransmittedBlks
{ adslAturChanPerfDataEntry 19 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturChanPerfPrev1DayCorrectedBlks
{ adslAturChanPerfDataEntry 20 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturChanPerfPrev1DayUncorrectBlks
{ adslAturChanPerfDataEntry 21 }
AdslPerfPrevDayCount
read-only
current
Y
Note: block is intended to be the length of the channel data-block on which the CRC operates. See
adslAturChanCrcBlockLength for more information.
5.11.2.11.1
adslAturChanReceivedBlks
Count of all encoded blocks received on this channel since agent reset.
5.11.2.11.2
adslAturChanTransmittedBlks
Count of all encoded blocks transmitted on this channel since agent reset.
5.11.2.11.3
adslAturChanCorrectedBlks
Count of all blocks received with errors that were corrected since agent reset. These blocks are passed on as good
data.
5.11.2.11.4
adslAturChanUncorrectBlks
Count of all blocks received with uncorrectable errors since agent reset.
5.11.2.11.5
adslAturChanPerfValidIntervals
The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the
maximum # of intervals supported. The value is <n> unless the measurement was (re-)started within the last
(<n>*15) minutes, in which case the value is the number of complete 15 minute intervals for which the agent has at
least some data. In certain cases (for example, in the case where the agent is a proxy) it is possible that some intervals
are unavailable. In this case, this interval is the maximum interval number for which data is available.
5.11.2.11.6
adslAturChanPerfInvalidIntervals
The number of intervals in the range from 0 to the value of adslAturChanPerfValidIntervals for which no data is
211
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
available. This object will typically be zero except in cases where the data for some intervals are not available (for
example, in proxy situations).
5.11.2.11.7
adslAturChanPerfCurr15MinTimeElapsed
Total elapsed seconds in this interval. A full interval is 900 seconds.
5.11.2.11.8
adslAturChanPerfCurr15MinReceivedBlks
Count of all encoded blocks received on this channel within the current 15 minute interval.
5.11.2.11.9
adslAturChanPerfCurr15MinTransmittedBlks
Count of all encoded blocks transmitted on this channel within the current 15 minute interval.
5.11.2.11.10 adslAturChanPerfCurr15MinCorrectedBlks
Count of all blocks received with errors that were corrected on this channel within the current 15 minute interval.
5.11.2.11.11 adslAturChanPerfCurr15MinUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel within the current 15 minute interval.
5.11.2.11.12 adslAturChanPerfCurr1DayTimeElapsed
Number of seconds that have elapsed since the beginning of the current 1-day interval.
5.11.2.11.13 adslAturChanPerfCurr1DayReceivedBlks
Count of all encoded blocks received on this channel during the current day as measured by
adslAturChanPerfCurr1DayTimeElapsed.
5.11.2.11.14 adslAturChanPerfCurr1DayTransmittedBlks
Count of all encoded blocks transmitted on this channel during the current day as measured by
adslAturChanPerfCurr1DayTimeElapsed.
5.11.2.11.15 adslAturChanPerfCurr1DayCorrectedBlks
Count of all blocks received with errors that were corrected on this channel during the current day as measured by
adslAturChanPerfCurr1DayTimeElapsed.
5.11.2.11.16 adslAturChanPerfCurr1DayUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel during the current day as measured by
adslAturChanPerfCurr1DayTimeElapsed.
5.11.2.11.17 adslAturChanPerfPrev1DayMoniSecs
The amount of time in the previous 1-day interval over which the performance monitoring information is actually
counted. This value is the same as the interval duration except in a situation where performance monitoring data
could not be collected for any reason.
5.11.2.11.18 adslAturChanPerfPrev1DayReceivedBlks
Count of all encoded blocks received on this channel within the most recent previous 1-day period.
212
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.11.19 adslAturChanPerfPrev1DayTransmittedBlks
Count of all encoded blocks transmitted on this channel within the most recent previous 1-day period.
5.11.2.11.20 adslAturChanPerfPrev1DayCorrectedBlks
Count of all blocks received with errors that were corrected on this channel within the most recent previous 1-day
period.
5.11.2.11.21 adslAturChanPerfPrev1DayUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel within the most recent previous 1-day period.
5.11.2.12 adslAtucChanIntervalTable
This table provides one row for each ATUC channel's performance data collection interval. ADSL channel interfaces
are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
This table is a sequence of adslAtucChanIntervalEntry.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
adslAtucChanIntervalNumber
OIDs:
•
•
adslAtucChanIntervalTable
adslAtucChanIntervalEntry
- { adslMibObjects 12 }
- { adslAtucChanIntervalTable 1 }
1.3.6.1.2.1.10.94.1.1.12
1.3.6.1.2.1.10.94.1.1.12.1
Table 108: adslAtucChanIntervalTable
Object
OID
Syntax
Access
Status
Supported
adslAtucChanIntervalNumber
{ adslAtucChanIntervalEntry 1 }
INTEGER(1…96)
read-only
current
Y
adslAtucChanIntervalReceivedBlks
{ adslAtucChanIntervalEntry 2 }
PerfIntervalCount
read-only
current
Y
adslAtucChanIntervalTransmittedBlks
{ adslAtucChanIntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
adslAtucChanIntervalCorrectedBlks
{ adslAtucChanIntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
adslAtucChanIntervalUncorrectBlks
{ adslAtucChanIntervalEntry 5 }
PerfIntervalCount
read-only
current
Y
adslAtucChanIntervalValidData
{ adslAtucChanIntervalEntry 6 }
TruthValue
read-only
current
Y
5.11.2.12.1 adslAtucChanIntervalNumber
Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2…96
are optional.
5.11.2.12.2 adslAtucChanIntervalReceivedBlks
Count of all encoded blocks received on this channel during this interval.
213
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.12.3 adslAtucChanIntervalTransmittedBlks
Count of all encoded blocks transmitted on this channel during this interval.
5.11.2.12.4 adslAtucChanIntervalCorrectedBlks
Count of all blocks received with errors that were corrected on this channel during this interval.
5.11.2.12.5 adslAtucChanIntervalUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel during this interval.
5.11.2.12.6 adslAtucChanIntervalValidData
This variable indicates if the data for this interval is valid.
5.11.2.13 adslAturChanIntervalTable
This table provides one row for each ATUR channel's performance data collection interval. ADSL channel interfaces
are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
This table is a sequence of adslAturChanIntervalEntry.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
adslAturChanIntervalNumber
OIDs:
•
•
adslAturChanIntervalTable
adslAturChanIntervalEntry
- { adslMibObjects 13 }
- { adslAturChanIntervalTable 1 }
1.3.6.1.2.1.10.94.1.1.13
1.3.6.1.2.1.10.94.1.1.13.1
Table 109: adslAturChanIntervalTable
Object
OID
Syntax
Access
Status
Supported
adslAturChanIntervalNumber
{ adslAturChanIntervalEntry 1 }
INTEGER(1…96)
read-only
current
Y
adslAturChanIntervalReceivedBlks
{ adslAturChanIntervalEntry 2 }
PerfIntervalCount
read-only
current
Y
adslAturChanIntervalTransmittedBlks
{ adslAturChanIntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
adslAturChanIntervalCorrectedBlks
{ adslAturChanIntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
adslAturChanIntervalUncorrectBlks
{ adslAturChanIntervalEntry 5 }
PerfIntervalCount
read-only
current
Y
adslAturChanIntervalValidData
{ adslAturChanIntervalEntry 6 }
TruthValue
read-only
current
Y
5.11.2.13.1 adslAturChanIntervalNumber
Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2…96
214
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
are optional.
5.11.2.13.2 adslAturChanIntervalReceivedBlks
Count of all encoded blocks received on this channel during this interval.
5.11.2.13.3 adslAturChanIntervalTransmittedBlks
Count of all encoded blocks transmitted on this channel during this interval.
5.11.2.13.4 adslAturChanIntervalCorrectedBlks
Count of all blocks received with errors that were corrected on this channel during this interval.
5.11.2.13.5 adslAturChanIntervalUncorrectBlks
Count of all blocks received with uncorrectable errors on this channel during this interval.
5.11.2.13.6 adslAturChanIntervalValidData
This variable indicates if the data for this interval is valid.
5.11.2.14 adslLineConfProfileTable
This table contains information on the ADSL line configuration. One entry in this table reflects a profile defined by a
manager which can be used to configure the ADSL line.
This table is a sequence of adslLineConfProfileEntry. Each entry consists of a list of parameters that represents the
configuration of an ADSL modem.
When “dynamic” profiles are implemented, a default profile will always exist. This profile's name is set to
“DEFVAL” and its parameters are set to vendor specific values, unless otherwise specified in this document.
When “static” profiles are implemented, profiles are automatically created or destroyed as ADSL physical lines are
discovered and removed by the system. The name of the profile is equivalent to the decimal value of the line's
interface index.
Index(es):
•
adslLineConfProfileName (IMPLIED)
OIDs:
•
•
adslLineConfProfileTable
adslLineConfProfileEntry
- { adslMibObjects 14 }
- { adslLineConfProfileTable 1 }
1.3.6.1.2.1.10.94.1.1.14
1.3.6.1.2.1.10.94.1.1.14.1
Table 110: adslLineConfProfileTable (1 of 3)
Object
OID
Syntax
Access
Status
Supported
adslLineConfProfileName
{ adslLineConfProfileEntry 1 }
SnmpAdminString
(1…32)
not-accessible
current
Y
215
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 110: adslLineConfProfileTable (2 of 3)
Object
OID
Syntax
Access
Status
Supported
adslAtucConfRateMode
{ adslLineConfProfileEntry 2 }
INTEGER
fixed(1)
adaptAtStartup(2)
adaptAtRuntime(3)
read-create
current
Y
adslAtucConfRateChanRatio
{ adslLineConfProfileEntry 3 }
INTEGER (0…100)
read-create
current
Y
adslAtucConfTargetSnrMgn
{ adslLineConfProfileEntry 4 }
INTEGER (0…310)a
read-create
current
Y
adslAtucConfMaxSnrMgn
{ adslLineConfProfileEntry 5 }
INTEGER (0…310)a
read-create
current
Y
adslAtucConfMinSnrMgn
{ adslLineConfProfileEntry 6 }
INTEGER (0…310)a
read-create
current
Y
adslAtucConfDownshiftSnrMgn
{ adslLineConfProfileEntry 7 }
INTEGER (0…310)a
read-create
current
Y
adslAtucConfUpshiftSnrMgn
{ adslLineConfProfileEntry 8 }
INTEGER (0…310)a
read-create
current
Y
adslAtucConfMinUpshiftTime
{ adslLineConfProfileEntry 9 }
INTEGER (0…16383)
read-create
current
Y
adslAtucConfMinDownshiftTime
{ adslLineConfProfileEntry 10 }
INTEGER (0…16383)
read-create
current
Y
adslAtucChanConfFastMinTxRate
{ adslLineConfProfileEntry 11 }
Unsigned32b
read-create
current
Y
adslAtucChanConfInterleaveMinTxRate
{ adslLineConfProfileEntry 12 }
Unsigned32b
read-create
current
Y
adslAtucChanConfFastMaxTxRate
{ adslLineConfProfileEntry 13 }
Unsigned32b
read-create
current
Y
adslAtucChanConfInterleaveMaxTxRate
{ adslLineConfProfileEntry 14 }
Unsigned32b
read-create
current
Y
adslAtucChanConfMaxInterleaveDelay
{ adslLineConfProfileEntry 15 }
INTEGER (0…255)
read-create
current
Y
adslAturConfRateMode
{ adslLineConfProfileEntry 16 }
INTEGER
fixed (1)
adaptAtStartup (2)
adaptAtRuntime (3)
read-create
current
Y
adslAturConfRateChanRatio
{ adslLineConfProfileEntry 17 }
INTEGER (0…100)
read-create
current
Y
adslAturConfTargetSnrMgn
{ adslLineConfProfileEntry 18 }
INTEGER (0…310)a
read-create
current
Y
216
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 110: adslLineConfProfileTable (3 of 3)
Object
OID
Syntax
Access
Status
Supported
adslAturConfMaxSnrMgn
{ adslLineConfProfileEntry 19 }
INTEGER (0…310)a
read-create
current
Y
adslAturConfMinSnrMgn
{ adslLineConfProfileEntry 20 }
INTEGER (0…310)a
read-create
current
Y
adslAturConfDownshiftSnrMgn
{ adslLineConfProfileEntry 21 }
INTEGER (0…310)a
read-create
current
Y
adslAturConfUpshiftSnrMgn
{ adslLineConfProfileEntry 22 }
INTEGER (0…310)a
read-create
current
Y
adslAturConfMinUpshiftTime
{ adslLineConfProfileEntry 23 }
INTEGER (0…16383)
read-create
current
Y
adslAturConfMinDownshiftTime
{ adslLineConfProfileEntry 24 }
INTEGER (0…16383)
read-create
current
Y
adslAturChanConfFastMinTxRate
{ adslLineConfProfileEntry 25 }
Unsigned32b
read-create
current
Y
adslAturChanConfInterleaveMinTxRate
{ adslLineConfProfileEntry 26 }
Unsigned32b
read-create
current
Y
adslAturChanConfFastMaxTxRate
{ adslLineConfProfileEntry 27 }
Unsigned32b
read-create
current
Y
adslAturChanConfInterleaveMaxTxRate
{ adslLineConfProfileEntry 28 }
Unsigned32b
read-create
current
Y
adslAturChanConfMaxInterleaveDelay
{ adslLineConfProfileEntry 29 }
INTEGER (0…255)
read-create
current
Y
adslLineConfProfileRowStatus
{ adslLineConfProfileEntry 30 }
RowStatus
read-create
current
Y
a. Signal/Noise Margins must be entered in increments of 1dB.
b. Rates must be entered in increments of 32000 bps.
5.11.2.14.1 adslLineConfProfileName
This object is used by the line configuration table in order to identify a row of this table.
When “dynamic” profiles are implemented, the profile name is user specified. Also, the system will always provide a
default profile whose name is “DEFVAL.”
When “static” profiles are implemented, there is an one-to-one relationship between each line and its profile. In which
case, the profile name will need to algorithmically represent the Line's ifIndex. Therefore, the profile's name is a
decimalized string of the ifIndex that is fixed-length (that is, 10) with leading zero(s). For example, the profile name
for an ifIndex which equals “15” is “0000000015.”
217
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.14.2 adslAtucConfRateMode
Defines what form of transmit rate adaptation is configured on this modem. See ADSL Forum TR-005, “Network
Management Element Management,” March 1998 for more information.
•
•
•
fixed (1)
- no rate adaptation
adaptAtStartup (2)
- perform rate adaptation only at initialization
adaptAtRuntime (3) - perform rate adaptation at any time
5.11.2.14.3 adslAtucConfRateChanRatio
Configured allocation ratio of excess transmit bandwidth between fast and interleaved channels. Only applies when
two channel mode and RADSL are supported. Distribute bandwidth on each channel in excess of the corresponding
ChanConfMinTxRate so that:
adslAtucConfRateChanRatio =[Fast / (Fast + Interleaved)] * 100
In other words this value is the fast channel percentage.
5.11.2.14.4 adslAtucConfTargetSnrMgn
Configured Target Signal/Noise Margin. This is the Noise Margin the modem must achieve with a BER of 10-7 or
better to successfully complete initialization. Expressed as in tenths of a decibel.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.5 adslAtucConfMaxSnrMgn
Configured Maximum acceptable Signal/Noise Margin. If the Noise Margin is above this the modem should attempt
to reduce its power output to optimize its operation. Expressed as tenths of a decibel.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.6 adslAtucConfMinSnrMgn
Configured Minimum acceptable Signal/Noise Margin. If the noise margin falls below this level, the modem should
attempt to increase its power output. If that is not possible the modem will attempt to re-initialize or shut down.
Expressed as tenths of a decibel. Valid only for ReachDSL models.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.7 adslAtucConfDownshiftSnrMgn
Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should
attempt to decrease its transmit rate. In the case that RADSL mode is not present, the value is “0”. Expressed as tenths
of a decibel. Valid only for ADSL models.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.8 adslAtucConfUpshiftSnrMgn
Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt
218
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
to increase its transmit rate. In the case that RADSL is not present, the value is “0”. Expressed as tenths of a decibel.
Valid only for ADSL models.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.9 adslAtucConfMinUpshiftTime
Minimum time, in seconds, that the current margin is above UpshiftSnrMgn before an upshift occurs. In the case that
RADSL is not present, the value is “0.”
5.11.2.14.10 adslAtucConfMinDownshiftTime
Minimum time, in seconds, that the current margin is below DownshiftSnrMgn before a downshift occurs. In the case
that RADSL mode is not present, the value is “0.” Valid only for ADSL models.
5.11.2.14.11 adslAtucChanConfFastMinTxRate
Configured Minimum Transmit rate for “Fast” channels, in bps. See adslAtucConfRateChanRatio for information
regarding RADSL mode and ATUR transmit rate for ATUC receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
•
•
•
All values must be in increments of 32 000bps
G.dmt, ANSI, and multimode
—
64 000 to 12 000 000
G.lite
—
64 000 to 4 000 000
ReachDSL
—
32 000 to 2 176 000
5.11.2.14.12 adslAtucChanConfInterleaveMinTxRate
Configured Minimum Transmit rate for “Interleave” channels, in bps. See adslAtucConfRateChanRatio for
information regarding RADSL mode and see ATUR transmit rate for receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
•
G.dmt, ANSI, and multimode
—
64 000 to 12 000 000
G.lite
—
64 000 to 4 000 000
5.11.2.14.13 adslAtucChanConfFastMaxTxRate
Configured Maximum Transmit rate for “Fast” channels, in bps. See adslAtucConfRateChanRatio for information
regarding RADSL mode and see ATUR transmit rate for ATUC receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
G.dmt, ANSI, and multimode
219
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
•
•
—
64 000 to 12 000 000
G.lite
—
64 000 to 4 000 000
ReachDSL
—
32 000 to 2 176 000
5.11.2.14.14 adslAtucChanConfInterleaveMaxTxRate
Configured Maximum Transmit rate for “Interleave” channels, in bps. See adslAtucConfRateChanRatio for
information regarding RADSL mode and ATUR transmit rate for ATUC receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
•
G.dmt, ANSI, and multimode
—
64 000 to 12 000 000
G.lite
—
64 000 to 4 000 000
5.11.2.14.15 adslAtucChanConfMaxInterleaveDelay
Configured maximum Interleave Delay for this channel.
Interleave delay, in milli-seconds, applies only to the interleave channel and defines the mapping (relative spacing)
between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output.
Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for
improved impulse noise immunity at the expense of payload latency.
5.11.2.14.16 adslAturConfRateMode
Defines what form of transmit rate adaptation is configured on this modem. See ADSL Forum TR-005, “Network
Management Element Management,” March 1998 for more information.
•
•
•
fixed (1)
adaptAtStartup (2)
adaptAtRuntime (3)
- no rate adaptation
- perform rate adaptation only at initialization
- perform rate adaptation at any time
5.11.2.14.17 adslAturConfRateChanRatio
Configured allocation ratio of excess transmit bandwidth between fast and interleaved channels. Only applies when
two channel mode and RADSL are supported. Distribute bandwidth on each channel in excess of the corresponding
ChanConfMinTxRate so that:
adslAturConfRateChanRatio = [Fast / (Fast + Interleaved)] * 100
In other words this value is the fast channel percentage.
5.11.2.14.18 adslAturConfTargetSnrMgn
Configured Target Signal/Noise Margin. This is the Noise Margin the modem must achieve with a BER of 10-7 or
better to successfully complete initialization.
Valid Object Value(s)
Values must be in 1dB increments.
220
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.14.19 adslAturConfMaxSnrMgn
Configured Maximum acceptable Signal/Noise Margin. If the Noise Margin is above this the modem should attempt
to reduce its power output to optimize its operation. Expressed as tenths of a decibel.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.20 adslAturConfMinSnrMgn
Configured Minimum acceptable Signal/Noise Margin. If the noise margin falls below this level, the modem should
attempt to increase its power output. If that is not possible the modem will attempt to re-initialize or shut down.
Expressed as tenths of a decibel.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.21 adslAturConfDownshiftSnrMgn
Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should
attempt to decrease its transmit rate. In the case that RADSL mode is not present, the value is “0”. Expressed as tenths
of a decibel.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.22 adslAturConfUpshiftSnrMgn
Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt
to increase its transmit rate. In the case that RADSL is not present, the value is “0”. Expressed as tenths of a decibel.
Valid Object Value(s)
Values must be in 1dB increments.
5.11.2.14.23 adslAturConfMinUpshiftTime
Minimum time, in seconds, that the current margin is above UpshiftSnrMgn before an upshift occurs. In the case
that RADSL is not present, the value is “0.”
5.11.2.14.24 adslAturConfMinDownshiftTime
Minimum time, in seconds, that the current margin is below DownshiftSnrMgn before a downshift occurs. In the
case that RADSL mode is not present, the value is “0.”
5.11.2.14.25 adsladslAturChanConfFastMinTxRate
Configured Minimum Transmit rate for “Fast” channels, in bps. See adslAturConfRateChanRatio for information
regarding RADSL mode and ATUC transmit rate for ATUR receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
•
G.dmt, ANSI, G.lite, and multimode
—
64 000 to 1 024 000
ReachDSL
221
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
—
32 000 to 2 176 000
5.11.2.14.26 adslAturChanConfInterleaveMinTxRate
Configured Minimum Transmit rate for “Interleave” channels, in bps. See adslAturConfRateChanRatio for
information regarding RADSL mode and ATUC transmit rate for ATUR receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
G.dmt, ANSI, G.lite, and multimode
—
64 000 to 1 024 000
5.11.2.14.27 adslAturChanConfFastMaxTxRate
Configured Maximum Transmit rate for “Fast” channels, in bps. See adslAturConfRateChanRatio for information
regarding RADSL mode and ATUC transmit rate for ATUR receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
•
G.dmt, ANSI, G.lite, and multimode
—
64 000 to 1 024 000
ReachDSL
—
32 000 to 2 176 000
5.11.2.14.28 adslAturChanConfInterleaveMaxTxRate
Configured Maximum Transmit rate for “Interleave” channels, in bps. See adslAturConfRateChanRatio for
information regarding RADSL mode and see ATUC transmit rate for ATUR receive rates.
Valid Object Value(s)
Note: Spaces added in values to improve readability. They are not actually part of the entry.
•
G.dmt, ANSI, G.lite, and multimode
—
64 000 to 1 024 000
5.11.2.14.29 adslAturChanConfMaxInterleaveDelay
Configured maximum Interleave Delay, in milli-seconds, for this channel.
Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent
input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers
provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse
noise immunity at the expense of payload latency.
5.11.2.14.30 adslLineConfProfileRowStatus
This object is used to create a new row or modify or delete an existing row in this table.
A profile activated by setting this object to “active.” When “active” is set, the system will validate the profile.
Before a profile can be deleted or taken out of service, (by setting this object to “destroy” or “outOfService”) it must
be first unreferenced from all associated lines.
If the implementor of this MIB has chosen not to implement “dynamic assignment” of profiles, this object's MIN-
222
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
ACCESS is read-only and its value is always to be “active.”
Valid Object Value(s)
The createAndWait RowStatus (Section 4.11, Page 15) is not supported.
5.11.2.15 adslLineAlarmConfProfileTable
This table contains information on the ADSL line configuration. One entry in this table reflects a profile defined by a
manager which can be used to configure the modem for a physical line
This table is a sequence of adslLineAlarmConfProfileEntry.
Each entry consists of a list of parameters that represents the configuration of an ADSL modem.
When “dynamic” profiles are implemented, a default profile will always exist. This profile's name is set to
“DEFVAL” and its parameters are set to vendor specific values, unless otherwise specified in this document.
When “static” profiles are implemented, profiles are automatically created or destroyed as ADSL physical lines are
discovered and removed by the system. The name of the profile is equivalent to the decimal value of the line's
interface index.
Index(es):
•
adslLineAlarmConfProfileName (IMPLIED)
OIDs:
•
•
adslLineAlarmConfProfileTable
adslLineAlarmConfProfileEntry
- { adslMibObjects 15 }
- { adslLineAlarmConfProfileTable 1 }
1.3.6.1.2.1.10.94.1.1.15
1.3.6.1.2.1.10.94.1.1.15.1
Table 111: adslLineAlarmConfProfileTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslLineAlarmConfProfileName
{ adslLineAlarmConfProfileEntry 1 }
SnmpAdminString
(SIZE (1…32))
not-accessible
current
Y
adslAtucThresh15MinLofs
{ adslLineAlarmConfProfileEntry 2 }
INTEGER (0…900)
read-create
current
Y
adslAtucThresh15MinLoss
{ adslLineAlarmConfProfileEntry 3 }
INTEGER (0…900)
read-create
current
Y
adslAtucThresh15MinLols
{ adslLineAlarmConfProfileEntry 4 }
INTEGER (0…900)
read-create
current
Y
adslAtucThresh15MinLprs
{ adslLineAlarmConfProfileEntry 5 }
INTEGER (0…900)
read-create
current
Y
adslAtucThresh15MinESs
{ adslLineAlarmConfProfileEntry 6 }
INTEGER (0…900)
read-create
current
Y
adslAtucThreshFastRateUp
{ adslLineAlarmConfProfileEntry 7 }
Unsigned32
read-create
current
Y
223
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Table 111: adslLineAlarmConfProfileTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAtucThreshInterleaveRateUp
{ adslLineAlarmConfProfileEntry 8 }
Unsigned32
read-create
current
Y
adslAtucThreshFastRateDown
{ adslLineAlarmConfProfileEntry 9 }
Unsigned32
read-create
current
Y
adslAtucThreshInterleaveRateDown
{ adslLineAlarmConfProfileEntry 10 }
Unsigned32
read-create
current
Y
adslAtucInitFailureTrapEnable
{ adslLineAlarmConfProfileEntry 11 }
INTEGER
enable (1)
disable (2)
read-create
current
Y
adslAturThresh15MinLofs
{ adslLineAlarmConfProfileEntry 12 }
INTEGER (0…900)
read-create
current
Y
adslAturThresh15MinLoss
{ adslLineAlarmConfProfileEntry 13 }
INTEGER (0…900)
read-create
current
Y
adslAturThresh15MinLprs
{ adslLineAlarmConfProfileEntry 14 }
INTEGER (0…900)
read-create
current
Y
adslAturThresh15MinESs
{ adslLineAlarmConfProfileEntry 15 }
INTEGER (0…900)
read-create
current
Y
adslAturThreshFastRateUp
{ adslLineAlarmConfProfileEntry 16 }
Unsigned32
read-create
current
Y
adslAturThreshInterleaveRateUp
{ adslLineAlarmConfProfileEntry 17 }
Unsigned32
read-create
current
Y
adslAturThreshFastRateDown
{ adslLineAlarmConfProfileEntry 18 }
Unsigned32
read-create
current
Y
adslAturThreshInterleaveRateDown
{ adslLineAlarmConfProfileEntry 19 }
Unsigned32
read-create
current
Y
adslAturAlarmConfProfileRowStatus
{ adslLineAlarmConfProfileEntry 20 }
RowStatus
read-create
current
Y
5.11.2.15.1 adslLineAlarmConfProfileName
This object is used by the line alarm configuration table in order to identify a row of this table.
When “dynamic” profiles are implemented, the profile name is user specified. Also, the system will always provide a
default profile whose name is “DEFVAL.”
When “static” profiles are implemented, there is an one-to-one relationship between each line and its profile. In which
case, the profile name will need to algorithmically represent the Line's ifIndex. Therefore, the profile's name is a
decimalized string of the ifIndex that is fixed-length (that is, 10) with leading zero(s). For example, the profile name
for an ifIndex which equals '15' is '0000000015'.
224
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.2.15.2 adslAtucThresh15MinLofs
The number of Loss of Frame Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAtucPerfLofsThreshTrap. One trap is sent per
interval per interface. A value of “0” will disable the trap. This value is expressed in units of seconds.
5.11.2.15.3 adslAtucThresh15MinLoss
The number of Loss of Signal Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAtucPerfLossThreshTrap. One trap is sent per
interval per interface. A value of “0’ will disable the trap.
5.11.2.15.4 adslAtucThresh15MinLols
The number of Loss of Link Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAtucPerfLolsThreshTrap. One trap is sent per
interval per interface. A value of “0” will disable the trap.
5.11.2.15.5 adslAtucThresh15MinLprs
The number of Loss of Power Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAtucPerfLprsThreshTrap. One trap is sent per
interval per interface. A value of “0” will disable the trap.
5.11.2.15.6 adslAtucThresh15MinESs
The number of Errored Seconds encountered by an ADSL interface within any given 15 minutes performance data
collection period, which causes the SNMP agent to send an adslAtucPerfESsThreshTrap. One trap is sent per interval
per interface. A value of “0” will disable the trap.
5.11.2.15.7 adslAtucThreshFastRateUp
Applies to “Fast” channels only. Configured change in rate, in bps, causing an adslAtucRateChangeTrap. A trap is
produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of “0” will disable the
trap.
5.11.2.15.8 adslAtucThreshInterleaveRateUp
Applies to “Interleave” channels only. Configured change in rate, in bps, causing an adslAtucRateChangeTrap. A trap
is produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of “0” will disable the
trap.
5.11.2.15.9 adslAtucThreshFastRateDown
Applies to “Fast” channels only. Configured change in rate, in bps, causing an adslAtucRateChangeTrap. A trap is
produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of “0” will disable the
trap.
5.11.2.15.10 adslAtucThreshInterleaveRateDown
Applies to “Interleave” channels only. Configured change in rate, in bps, causing an adslAtucRateChangeTrap. A trap
is produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of “0” will disable
the trap.
5.11.2.15.11 adslAtucInitFailureTrapEnable
Enables and disables the InitFailureTrap. This object is defaulted disable(2)
225
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
•
•
enable (1)
disable (2)
5.11.2.15.12 adslAturThresh15MinLofs
The number of Loss of Frame Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAturPerfLofsThreshTrap. One trap is sent per
interval per interface. A value of “0” will disable the trap.
5.11.2.15.13 adslAturThresh15MinLoss
The number of Loss of Signal Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAturPerfLossThreshTrap. One trap is sent per
interval per interface. A value of “0” will disable the trap.
5.11.2.15.14 adslAturThresh15MinLprs
The number of Loss of Power Seconds encountered by an ADSL interface within any given 15 minutes performance
data collection period, which causes the SNMP agent to send an adslAturPerfLprsThreshTrap. One trap is sent per
interval per interface. A value of “0” will disable the trap.
5.11.2.15.15 adslAturThresh15MinESs
The number of Errored Seconds encountered by an ADSL interface within any given 15 minutes performance data
collection period, which causes the SNMP agent to send an adslAturPerfESsThreshTrap. One trap is sent per interval
per interface. A value of “0” will disable the trap.
5.11.2.15.16 adslAturThreshFastRateUp
Applies to “Fast” channels only. Configured change in rate, in bps, causing an adslAturRateChangeTrap. A trap is
produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of “0” will disable the
trap.
5.11.2.15.17 adslAturThreshInterleaveRateUp
Applies to “Interleave” channels only. configured change in rate, in bps, causing an adslAturRateChangeTrap. A trap
is produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of “0” will disable the
trap.
5.11.2.15.18 adslAturThreshFastRateDown
Applies to “Fast” channels only. Configured change in rate, in bps, causing an adslAturRateChangeTrap. A trap is
produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of “0” will disable the
trap.
5.11.2.15.19 adslAturThreshInterleaveRateDown
Applies to “Interleave” channels only. Configured change in rate, in bps, causing an adslAturRateChangeTrap. A trap
is produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of “0” will disable
the trap.
5.11.2.15.20 adslLineAlarmConfProfileRowStatus
This object is used to create a new row or modify or delete an existing row in this table.
A profile activated by setting this object to “active.” When “active” is set, the system will validate the profile.
226
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
Before a profile can be deleted or taken out of service, (by setting this object to “destroy” or “outOfService”) it must
be first unreferenced from all associated lines.
If the implementor of this MIB has chosen not to implement “dynamic assignment” of profiles, this object's MINACCESS is read-only and its value is always to be “active”.
5.11.2.16 adslLCSMib
This section is a place holder for the Line Code Specific MIB objects once they are defined. Line Code Specific MIB
objects may be defined in other RFCs or TR type of documents.
OIDs:
•
adslLCSMib
- { adslMibObjects 16 }
1.3.6.1.2.1.10.94.1.1.16
227
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.3
Traps
This section defines the traps generated by an ADSL line interface.
OIDs:
•
•
•
adslTraps
adslAtucTraps
adslAturTraps
5.11.3.1
- { adslLineMib 2 }
- { adslTraps 1 }
- { adslTraps 2 }
1.3.6.1.2.1.10.94.2
1.3.6.1.2.1.10.94.2.1
1.3.6.1.2.1.10.94.2.2
adslAtucTraps
Table 112: adslAtucTraps
Notification
OID
Variable Bindings
Status
Supported
adslAtucPerfLofsThreshTrap
{ adslAtucTraps 0 1 }
adslAtucPerfCurr15MinLofs
adslAtucThresh15MinLofs
current
Y
adslAtucPerfLossThreshTrap
{ adslAtucTraps 0 2 }
adslAtucPerfCurr15MinLoss
adslAtucThresh15MinLoss
current
Y
adslAtucPerfLprsThreshTrap
{ adslAtucTraps 0 3 }
adslAtucPerfCurr15MinLprs
adslAtucThresh15MinLprs
current
N
adslAtucPerfESsTreshTrap
{ adslAtucTraps 0 4 }
adslAtucPerfCurr15MinESs
adslAtucThresh15MinESs
current
Y
adslAtucRateChangeTrap
{ adslAtucTraps 0 5 }
adslAtucChanCurrTxRate
adslAtucChanPrevTxRate
current
Y
adslAtucPerfLolsThreshTrap
{ adslAtucTraps 0 6 }
adslAtucPerfCurr15MinLols
adslAtucThresh15MinLols
current
Y
adslAtucInitFailureTrap
{ adslAtucTraps 0 7 }
adslAtucCurrStatus
current
Y
5.11.3.1.1
adslAtucPerfLofsThreshTrap
Loss of Framing 15-minute interval threshold reached.
5.11.3.1.2
adslAtucPerfLossThreshTrap
Loss of Signal 15-minute interval threshold reached.
5.11.3.1.3
adslAtucPerfLprsThreshTrap
Loss of Power 15-minute interval threshold reached.
5.11.3.1.4
adslAtucPerfESsThreshTrap
Errored Second 15-minute interval threshold reached.
228
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-MIB — RFC 2662
5.11.3.1.5
adslAtucRateChangeTrap
The ATUCs transmit rate has changed (RADSL mode only)
5.11.3.1.6
adslAtucPerfLolsThreshTrap
Loss of Link 15-minute interval threshold reached.
5.11.3.1.7
adslAtucInitFailureTrap
ATUC initialization failed. See adslAtucCurrStatus for potential reasons.
5.11.3.2
adslAturTraps
Table 113: adslAturTraps
Notification
OID
Variable Bindings
Status
Supported
adslAturPerfLofsThreshTrap
{ adslAturTraps 0 1 }
adslAturPerfCurr15MinLofs
adslAturThresh15MinLofs
current
Y
adslAturPerfLossThreshTrap
{ adslAturTraps 0 2 }
adslAturPerfCurr15MinLoss
adslAturThresh15MinLoss
current
Y
adslAturPerfLprsThreshTrap
{ adslAturTraps 0 3 }
adslAtucPerfCurr15MinLprs
adslAturThresh15MinLprs
current
Y
adslAturPerfESsTreshTrap
{ adslAturTraps 0 4 }
adslAturPerfCurr15MinESs
adslAturThresh15MinESs
current
Y
adslAturRateChangeTrap
{ adslAturTraps 0 5 }
adslAturChanCurrTxRate
adslAturChanPrevTxRate
current
Y
5.11.3.2.1
adslAturPerfLofsThreshTrap
Loss of Framing 15-minute interval threshold reached.
5.11.3.2.2
adslAturPerfLossThreshTrap
Loss of Signal 15-minute interval threshold reached.
5.11.3.2.3
adslAturPerfLprsThreshTrap
Loss of Power 15-minute interval threshold reached.
5.11.3.2.4
adslAturPerfESsThreshTrap
Errored Second 15-minute interval threshold reached.
5.11.3.2.5
adslAturRateChangeTrap
The ATURs transmit rate has changed (RADSL mode only)
229
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12 ADSL-LINE-EXT-MIB — RFC 3440
5.12.1
Introduction
This MIB serves as an extension to the ADSL Line MIB (Section 5.11, Page 187) and describes additional objects for
managing ADSL interfaces not covered by the ADSL Line MIB. The document used for the ADSL-LINE-EXT-MIB
was dated December 10, 2002 and has a LAST-UPDATED of “200212100000Z.”
5.12.2
Textual Conventions
The following textual conventions are made in the reference document:
•
AdslTransmissionModeType
—
- A set of ADSL line transmission modes, with one bit per mode. The notes
(F) and (L) denote Full-Rate and G.Lite respectively.
Syntax
BITS
• ansit1413(0)
• etsi(1)
• q9921PotsNonOverlapped(2)
• q9921PotsOverlapped(3)
• q9921IsdnNonOverlapped(4)
• q9921isdnOverlapped(5)
• q9921tcmIsdnNonOverlapped(6)
• q9921tcmIsdnOverlapped(7)
• q9922potsNonOverlapped(8)
• q9922potsOverlapped(9)
• q9922tcmIsdnNonOverlapped(10)
• q9922tcmIsdnOverlapped(11)
• q9921tcmIsdnSymmetric(12)
5.12.3
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
adslMIB
adslExtMIB
adslExtMibObjects
5.12.4
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 94 }
{ adslMIB 3 }
{ adslExtMIB 1 }
: Bit 00 : Regional Std. (ANSI T1.413) (F)
: Bit 01 : Regional Std. (ETSI DTS/TM06006) (F)
: Bit 02 : G.992.1 POTS non-overlapped (F)
: Bit 03 : G.992.1 POTS overlapped (F)
: Bit 04 : G.992.1 ISDN non-overlapped (F)
: Bit 05 : G.992.1 ISDN overlapped (F)
: Bit 06 : G.992.1 TCM-ISDN non-overlapped (F)
: Bit 07 : G.992.1 TCM-ISDN overlapped (F)
: Bit 08 : G.992.2 POTS non-overlapped (L)
: Bit 09 : G.992.2 POTS overlapped (L)
: Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L)
: Bit 11 : G.992.2 with TCM-ISDN overlapped (L)
: Bit 12 : G.992.1 TCM-ISDN symmetric (F)
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.94
1.3.6.1.2.1.10.94.3
1.3.6.1.2.1.10.94.3.1
The table below identifies the objects called out in this MIB. Any table object that has elements that are supported are
indicated by a “Y” in the Supported column.
230
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
Table 114: ADSL-LINE-EXT-MIB Objects
Object
OID
Syntax
SEQUENCE of
Access
Status
Supported
adslLineExtTable
{ adslMibObjects 17 }
adslLineExtEntry
not-accessible
current
Y
adslAtucPerfDataExtTable
{ adslMibObjects 18 }
adslAtucPerfDataExtEntry
not-accessible
current
Y
adslAtucIntervalExtTable
{ adslMibObjects 19 }
adslAtucIntervalExtEntry
not-accessible
current
Y
adslAturPerfDataExtTable
{ adslMibObjects 20 }
adslAturPerfDataExtEntry
not-accessible
current
Y
adslAturIntervalExtTable
{ adslMibObjects 21 }
adslAturIntervalExtEntry
not-accessible
current
Y
adslConfProfileExtTable
{ adslMibObjects 22 }
adslConfProfileExtEntry
not-accessible
current
Y
adslAlarmConfProfileExtTable
{ adslMibObjects 23 }
adslAlarmConfProfileExtEntry
not-accessible
current
Y
5.12.4.1
adslLineExtTable
This table is an extension of the adslLineTable RFC 2662. It contains ADSL line configuration and monitoring
information. This includes the ADSL line’s capabilities and actual ADSL transmission system. Each entry
corresponds to an ADSL line.
Augments:
•
adslLineTable (Section 5.11.2.1, Page 189)
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslLineExtTable
adslLineExtEntry
- { adslExtMibObjects 17 }
- { adslLineExtTable 1 }
231
1.3.6.1.2.1.10.94.3.1.17
1.3.6.1.2.1.10.94.3.1.17.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
Table 115: adslLineExtTable
Object
OID
Syntax
Access
Status
Supported
adslLineTransAtucCap
{ adslLineExtEntry 1 }
AdslTransmissionModeType
read-only
current
Y
adslLineTransAtucConfig
{ adslLineExtEntry 2 }
AdslTransmissionModeType
read-write
current
Y
adslLineTransAtucActual
{ adslLineExtEntry 3 }
AdslTransmissionModeType
read-only
current
Y
adslLineGlitePowerState
{ adslLineExtEntry 4 }
INTEGER
none(1)
l0(2)
l1(3)
l3(4)
read-only
current
Y
adslLineConfProfileDualLite
{ adslLineExtEntry 5 }
SnmpAdminStringa
read-write
current
N
a. The SnmpAdminString syntax for this object has not been restricted in size as the adslLineConfProfile (Section 5.11.2.1.4, Page
191) object in the adslLineTable (Section 5.11.2.1, Page 189). Since the adslLineConfigProfile object is restricted to maximum of
32 bytes, this object will assume the restriction as well.
5.12.4.1.1
adslLineTransAtucCap
The transmission modes, represented by a bitmask that the ATU-C is capable of supporting. The modes available are
limited by the design of the equipment.
Valid Object Value(s)
This object is set to a bitwise OR indicating the following capabilities:
Table 116: adslLineTransAtucCap for Annex A Model
AdslTransmissionModeType
Description
Value (hex)
ansit1413(0)
ANSI T1.413
80 00
q9921PotsNonOverlapped(2)
G.992.1 POTS non-overlapped Annex A
20 00
q9922PostNonOverlapped(8)
G.992.2 POTS non-overlapped Annex A
00 80
Table 117: adslLineTransAtucCap for Annex B
AdslTransmissionModeType
Description
Value (hex)
q9921IsdnNonOverlapped(4))
G.992.1 ISDN non-overlapped Annex B
08 00
232
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.4.1.2
adslLineTransAtucConfig
The transmission modes, represented by a bitmask, currently enabled by the ATU-C. The manager can only set those
modes that are supported by the ATU-C. An ATU-C’s supported modes are provided by adslLineTransAtucCap
(Section 5.12.4.1.1, Page 232).
5.12.4.1.3
adslLineTransAtucActual
The actual transmission mode of the ATU-C. During ADSL line initialization, the ADSL Transceiver Unit - Remote
terminal end (ATU-R) will determine the mode used for the link. This value is limited to a single transmission mode
that is a subset of those modes enabled by the ATU-C and denoted by adslLineTransAtucConfig (Section 5.12.4.1.2,
Page 233). After an initialization has occurred, its mode is saved as the “Current” mode and is persistence should the
link go down. This object returns 0 (that is, BITS [Section 4.1, Page 12] with no mode bit set) if the mode is not
known.
5.12.4.1.4
adslLineGlitePowerState
The value of this object specifies the power state of this interface. The following are valid values for this object:
•
•
•
•
none(1)
l0(2)
- L0 Power on
l1(3)
- L1 Power on but reduced
l3(4)
- L3 Power off
The value of this object specifies the power state of this interface. L0 is power on, L1 is power on but reduced and L3
is power off. Power state cannot be configured by an operator but it can be viewed via the ifOperStatus (Section
5.3.4.3.8, Page 49) object for the managed ADSL interface. The value of the object ifOperStatus is set to down(2) if
the ADSL interface is in power state L3 and is set to up(1) if the ADSL line interface is in power state L0 or L1. If the
object adslLineTransAtucActual (Section 5.12.4.1.3, Page 233) is set to a G.992.2 (G.Lite)-type transmission mode,
the value of this object is one of the valid power states: L0(2), L1(3), or L3(4). Otherwise, its value is none(1).
5.12.4.1.5
adslLineConfProfileDualLite
This object extends the definition an ADSL line and associated channels (when applicable) for cases when it is
configured in dual mode, and operating in a G.Lite-type mode as denoted by adslLineTransAtucActual (Section
5.12.4.1.3, Page 233). Dual mode exists when the object, adslLineTransAtucConfig (Section 5.12.4.1.3, Page 233) is
configured with one or more full-rate modes and one or more G.Lite modes simultaneously.
When “dynamic” profiles are implemented, the value of object is equal to the index of the applicable row in the
ADSL Line Configuration Profile Table, adslLineConfProfileTable (Section 5.11.2.14, Page 215) defined in ADSLMIB [RFC 2662].
In the case when dual-mode has not been enabled, the value of the object is equal to the value of the object
adslLineConfProfile (Section 5.11.2.1.4, Page 191) [RFC 2662].
When “static” profiles are implemented, in much like the case of the object, adslLineConfProfileName (Section
5.11.2.14.1, Page 217) [RFC 2662], this object’s value will need to algorithmically represent the characteristics of the
line. In this case, the value of the line’s ifIndex plus a value indicating the line mode type (for example, G.Lite, Fullrate) is used. Therefore, the profile’s name is a string concatenating the ifIndex (Section 5.3.4.3.1, Page 39) and one
of the follow values: Full or Lite. This string is fixed-length (that is, 14) with leading zero(s). For example, the profile
name for an ifIndex that equals “15” and is a full rate line is 0000000015Full.
5.12.4.2
adslAtucPerfDataExtTable
This table extends adslAtucPerfDataTable (Section 5.11.2.6, Page 197) [RFC 2662] with additional ADSL physical
233
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
line counter information such as unavailable seconds-line and severely errored seconds-line. Each entry corresponds
to an ADSL line.
Augments:
•
adslAtucPerfDataTable (Section 5.11.2.6, Page 197)
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAtucPerfDataExtTable
adslAtucPerfDataExtEntry
- { adslExtMibObjects 18 }
- { adslAtucPerfDataExtTable 1 }
1.3.6.1.2.1.10.94.3.1.18
1.3.6.1.2.1.10.94.3.1.18.1
Table 118: adslAtucPerfDataExtTable
Object
OID
Syntax
Access
Status
Supported
adslAtucPerfStatFastR
{ adslAtucPerfDataExtEntry 1 }
Counter32
read-only
current
Y
adslAtucPerfStatFailedFastR
{ adslAtucPerfDataExtEntry 2 }
Counter32
read-only
current
Y
adslAtucPerfStatSesL
{ adslAtucPerfDataExtEntry 3 }
Counter32
read-only
current
Y
adslAtucPerfStatUasL
{ adslAtucPerfDataExtEntry 4 }
Counter32
read-only
current
Y
adslAtucPerfCurr15MinFastR
{ adslAtucPerfDataExtEntry 5 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinFailedFastR
{ adslAtucPerfDataExtEntry 6 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinSesL
{ adslAtucPerfDataExtEntry 7 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr15MinUasL
{ adslAtucPerfDataExtEntry 8 }
PerfCurrentCount
read-only
current
Y
adslAtucPerfCurr1DayFastR
{ adslAtucPerfDataExtEntry 9 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayFailedFastR
{ adslAtucPerfDataExtEntry 10 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DaySesL
{ adslAtucPerfDataExtEntry 11 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfCurr1DayUasL
{ adslAtucPerfDataExtEntry 12 }
AdslPerfCurrDayCount
read-only
current
Y
adslAtucPerfPrev1DayFastR
{ adslAtucPerfDataExtEntry 13 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayFailedFastR
{ adslAtucPerfDataExtEntry 14 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DaySesL
{ adslAtucPerfDataExtEntry 15 }
AdslPerfPrevDayCount
read-only
current
Y
adslAtucPerfPrev1DayUasL
{ adslAtucPerfDataExtEntry 16 }
AdslPerfPrevDayCount
read-only
current
Y
5.12.4.2.1
adslAtucPerfStatFastR
The value of this object reports the count of the number of fast line retrains since last agent reset.
234
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.4.2.2
adslAtucPerfStatFailedFastR
The value of this object reports the count of the number of failed fast line retrains since last agent reset.
The value of this object indicates the count of failed fast retrains.
5.12.4.2.3
adslAtucPerfStatSesL
The value of this object reports the count of the number of severely errored seconds-line since last agent reset.
The value of this object indicates the count of severely errored second-line.
5.12.4.2.4
adslAtucPerfStatUasL
The value of this object reports the count of the number of unavailable seconds-line since last agent reset.
The value of this object indicates the count of unavailable second.
5.12.4.2.5
adslAtucPerfCurr15MinFastR
For the current 15-minute interval, this object reports the current number of seconds during which there have been
fast retrains.
5.12.4.2.6
adslAtucPerfCurr15MinFailedFastR
For the current 15-minute interval, this object reports the current number of seconds during which there have been
failed fast retrains.
5.12.4.2.7
adslAtucPerfCurr15MinSesL
For the current 15-minute interval, this object reports the current number of seconds during which there have been
severely errored seconds-line.
5.12.4.2.8
adslAtucPerfCurr15MinUasL
For the current 15-minute interval, this object reports the current number of seconds during which there have been
unavailable seconds-line.
5.12.4.2.9
adslAtucPerfCurr1DayFastR
For the current day as measured by adslAtucPerfCurr1DayTimeElapsed (Section 5.11.2.6.16, Page 200) [RFC 2662],
this object reports the number of seconds during which there have been fast retrains.
5.12.4.2.10 adslAtucPerfCurr1DayFailedFastR
For the current day as measured by adslAtucPerfCurr1DayTimeElapsed (Section 5.11.2.6.16, Page 200) [RFC 2662],
this object reports the number of seconds during which there have been failed fast retrains.
5.12.4.2.11 adslAtucPerfCurr1DaySesL
For the current day as measured by adslAtucPerfCurr1DayTimeElapsed (Section 5.11.2.6.16, Page 200) [RFC 2662],
this object reports the number of seconds during which there have been severely errored seconds-line.
5.12.4.2.12 adslAtucPerfCurr1DayUasL
For the current day as measured by adslAtucPerfCurr1DayTimeElapsed (Section 5.11.2.6.16, Page 200) [RFC 2662],
this object reports the number of seconds during which there have been unavailable seconds-line.
235
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.4.2.13 adslAtucPerfPrev1DayFastR
For the previous day, this object reports the number of seconds during which there were fast retrains.
5.12.4.2.14 adslAtucPerfPrev1DayFailedFastR
For the previous day, this object reports the number of seconds during which there were failed fast retrains.
5.12.4.2.15 adslAtucPerfPrev1DaySesL
For the previous day, this object reports the number of seconds during which there were severely errored secondsline.
5.12.4.2.16 adslAtucPerfPrev1DayUasL
For the previous day, this object reports the number of seconds during which there were unavailable seconds-line.
5.12.4.3
adslAtucIntervalExtTable
This table provides one row for each ATU-C performance data collection interval for ADSL physical interfaces
whose IfEntries’ ifType (Section 5.3.4.3.3, Page 43) is equal to adsl(94).
Augments:
•
adslAtucIntervalTable (Section 5.11.2.8, Page 204)
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
adslAtucIntervalNumber (Section 5.11.2.8.1, Page 205)
OIDs:
•
•
adslAtucIntervalExtTable
adslAtucIntervalExtEntry
- { adslExtMibObjects 19 }
- { adslAtucIntervalExtTable 1 }
Table 119: adslAtucIntervalExtTable
Object
OID
Syntax
Access
Status
Supported
adslAtucIntervalFastR
{ adslAtucIntervalExtEntry 1 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalFailedFastR
{ adslAtucIntervalExtEntry 2 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalSesL
{ adslAtucIntervalExtEntry 3 }
PerfIntervalCount
read-only
current
Y
adslAtucIntervalUasL
{ adslAtucIntervalExtEntry 4 }
PerfIntervalCount
read-only
current
Y
5.12.4.3.1
adslAtucIntervalFastR
For the current interval, this object reports the current number of seconds during which there have been fast retrains.
5.12.4.3.2
adslAtucIntervalFailedFastR
For the each interval, this object reports the number of seconds during which there have been failed fast retrains.
236
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.4.3.3
adslAtucIntervalSesL
For the each interval, this object reports the number of seconds during which there have been severely errored
seconds-line.
5.12.4.3.4
adslAtucIntervalUasL
For the each interval, this object reports the number of seconds during which there have been unavailable secondsline.
5.12.4.4
adslAturPerfDataExtTable
This table contains ADSL physical line counters not defined in the adslAturPerfDataTable (Section 5.11.2.7, Page
201) from the ADSL-LINE-MIB [RFC 2662]. Each entry corresponds to an ADSL line.
Augments:
•
adslAturPerfDataTable (Section 5.11.2.7, Page 201)
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
adslAturPerfDataExtTable
adslAturPerfDataExtEntry
- { adslExtMibObjects 20 }
- { adslAturPerfDataExtTable 1 }
1.3.6.1.2.1.10.94.3.1.20
1.3.6.1.2.1.10.94.3.1.20.1
Table 120: adslAturPerfDataExtTable
Object
OID
Syntax
Access
Status
Supported
adslAturPerfStatSesL
{ adslAtucIntervalExtEntry 1 }
Counter32
read-only
current
Y
adslAturPerfStatUasL
{ adslAtucIntervalExtEntry 2 }
Counter32
read-only
current
Y
adslAturPerfCurr15MinSesL
{ adslAtucIntervalExtEntry 3 }
PerfCurrentCount
read-only
current
Y
adslAturPerfCurr15MinUasL
{ adslAtucIntervalExtEntry 4 }
PerfCurrentCount
read-only
current
Y
adslAturPerfCurr1DaySesL
{ adslAtucIntervalExtEntry 5 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturPerfCurr1DayUasL
{ adslAtucIntervalExtEntry 6 }
AdslPerfCurrDayCount
read-only
current
Y
adslAturPerfPrev1DaySesL
{ adslAtucIntervalExtEntry 7 }
AdslPerfPrevDayCount
read-only
current
Y
adslAturPerfPrev1DayUasL
{ adslAtucIntervalExtEntry 8 }
AdslPerfPrevDayCount
read-only
current
Y
5.12.4.4.1
adslAturPerfStatSesL
The value of this object reports the count of severely errored second-line since the last agent reset.
5.12.4.4.2
adslAturPerfStatUasL
The value of this object reports the count of unavailable seconds-line since the last agent reset.
237
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.4.4.3
adslAturPerfCurr15MinSesL
For the current 15-minute interval, this object reports the current number of seconds during which there have been
severely errored seconds-line.
5.12.4.4.4
adslAturPerfCurr15MinUasL
For the current 15-minute interval, this object reports the current number of seconds during which there have been
available seconds-line.
5.12.4.4.5
adslAturPerfCurr1DaySesL
For the current day as measured by adslAturPerfCurr1DayTimeElapsed (Section 5.11.2.7.12, Page 203) [RFC 2662],
adslAturPerfCurr1DaySesL reports the number of seconds during which there have been severely errored secondsline.
5.12.4.4.6
adslAturPerfCurr1DayUasL
For the current day as measured by adslAturPerfCurr1DayTimeElapsed (Section 5.11.2.7.12, Page 203) [RFC 2662],
this object reports the number of seconds during which there have been unavailable seconds-line.
5.12.4.4.7
adslAturPerfPrev1DaySesL
For the previous day, this object reports the number of seconds during which there were severely errored secondsline.
5.12.4.4.8
adslAturPerfPrev1DayUasL
For the previous day, this object reports the number of seconds during which there were severely errored secondsline.
5.12.4.5
adslAturIntervalExtTable
This table provides one row for each ATU-R performance data collection interval for ADSL physical interfaces
whose IfEntries’ ifType (Section 5.3.4.3.3, Page 43) is equal to adsl(94).
Augments:
•
adslAturIntervalTable (Section 5.11.2.9, Page 205)
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
adslAturIntervalNumber (Section 5.11.2.9.1, Page 206)
OIDs:
•
•
adslAturIntervalExtTable
adslAturIntervalExtEntry
- { adslExtMibObjects 21 }
- { adslAturIntervalExtTable 1 }
1.3.6.1.2.1.10.94.3.1.21
1.3.6.1.2.1.10.94.3.1.21.1
Table 121: adslAturIntervalExtTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturIntervalSesL
{ adslAturIntervalExtEntry 1 }
PerfIntervalCount
read-only
current
Y
238
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
Table 121: adslAturIntervalExtTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
adslAturIntervalUasL
{ adslAturIntervalExtEntry 2 }
PerfIntervalCount
read-only
current
Y
5.12.4.5.1
adslAturIntervalSesL
For the each interval, this object reports the number of seconds during which there have been severely errored
seconds-line.
5.12.4.5.2
adslAturIntervalUasL
For the each interval, this object reports the number of seconds during which there have been unavailable secondsline.
5.12.4.6
adslConfProfileExtTable
This table extends the ADSL line profile configuration information in the adslLineConfProfileTable (Section
5.11.2.14, Page 215) from the ADSL-LINE-MIB [RFC 2662] by adding the ability to configure the ADSL physical
line mode. Each entry corresponds to an ADSL line profile.
Augments:
•
adslLineConfProfileTable (Section 5.11.2.14, Page 215)
Index(es):
•
adslLineConfProfileName (Section 5.11.2.14.1, Page 217)
OIDs:
•
•
adslConfProfileExtTable - { adslExtMibObjects 22 }
adslConfProfileExtEntry - { adslConfProfileExtTable 1 }
1.3.6.1.2.1.10.94.3.1.22
1.3.6.1.2.1.10.94.3.1.22.1
Table 122: adslConfProfileExtTable
Object
OID
Syntax
Access
Status
Supported
adslConfProfileLineType
{ adslConfProfileExtEntry 1 }
INTEGER
noChannel (1)
fastOnly (2)
interleavedOnly (3)
fastOrInterleaved (4)
fastAndInterleaved (5)
read-create
current
Y
5.12.4.6.1
adslConfProfileLineType
This object is used to configure the ADSL physical line mode and can take on the following values:
•
noChannel (1)
- no channels exist
239
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
•
•
•
•
fastOnly (2)
interleavedOnly (3)
fastOrInterleaved (4)
fastAndInterleaved (5)
-
fast channel exists only
interleaved channel exists only
either fast or interleaved channels can exist, but only one at any time
both fast or interleaved channels exist
In the case when no value has been set, the MIB recommended default value is noChannel(1).
Valid Object Value(s)
•
•
fastOnly (2)
interleavedOnly (3)
5.12.4.7
adslAlarmConfProfileExtTable
This table extends the adslLineAlarmConfProfileTable (Section 5.11.2.15, Page 223) and provides threshold
parameters for all the counters defined in this MIB module. Each entry corresponds to an ADSL alarm profile.
Augments:
•
adslLineAlarmConfProfileTable (Section 5.11.2.15, Page 223)
Index(es):
•
adslLineAlarmConfProfileName (Section 5.11.2.15.1, Page 224)
OIDs:
•
•
adslAlarmConfProfileExtTable
adslAlarmConfProfileExtEntry
- { adslExtMibObjects 23 }
- { adslAlarmConfProfileExtTable 1 }
1.3.6.1.2.1.10.94.3.1.23
1.3.6.1.2.1.10.94.3.1.23.1
Table 123: adslAlarmConfProfileExtTable
Object
OID
Syntax
Access
Status
Supported
adslAtucThreshold15MinFailedFastR
{ adslAlarmConfProfileExtEntry 1 }
Integer32
(0…900)
read-create
current
Y
adslAtucThreshold15MinSesL
{ adslAlarmConfProfileExtEntry 2 }
Ineger32
(0…900)
read-create
current
Y
adslAtucThreshold15MinUasL
{ adslAlarmConfProfileExtEntry 3 }
Ineger32
(0…900)
read-create
current
Y
adslAturThreshold15MinSesL
{ adslAlarmConfProfileExtEntry 4 }
Integer32
(0…900)
read-create
current
Y
adslAturThreshold15MinUasL
{ adslAlarmConfProfileExtEntry 5 }
Integer32
(0…900)
read-create
current
Y
5.12.4.7.1
adslAtucThreshold15MinFailedFastR
The first time the value of the corresponding instance of adslAtucPerfCurr15MinFailedFastR (Section 5.12.4.2.2,
Page 235) reaches or exceeds this value within a given 15-minute performance data collection period, an
240
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
adslAtucFailedFastRThreshTrap (Section 5.12.5.1.1, Page 242) notification is generated. The value “0” will disable
the notification. The recommended MIB default value of this object is “0.”
5.12.4.7.2
adslAtucThreshold15MinSesL
The first time the value of the corresponding instance of adslAtucPerfCurr15MinSesL (Section 5.12.4.2.7, Page 235)
reaches or exceeds this value within a given 15-minute performance data collection period, an
adslAtucSesLThreshTrap (Section 5.12.5.1.2, Page 242) notification is generated. The value “0” will disable the
notification. The MIB recommended default value of this object is “0”.
Note: the RFC used adslAtucPerf15MinSesL. This seems to be a typo as that object does not exist.
5.12.4.7.3
adslAtucThreshold15MinUasL
The first time the value of the corresponding instance of adslAtucPerfCurr15MinUasL (Section 5.12.4.2.8, Page 235)
reaches or exceeds this value within a given 15-minute performance data collection period, an
adslAtucUasLThreshTrap (Section 5.12.5.1.3, Page 242) notification is generated. The value “0” will disable the
notification. The MIB recommended default value of this object is “0”.
Note: the RFC used adslAtucPerf15MinUasL. This seems to be a typo as that object does not exist.
5.12.4.7.4
adslAturThreshold15MinSesL
The first time the value of the corresponding instance of adslAturPerfCurr15MinSesL (Section 5.12.4.4.3, Page 238)
reaches or exceeds this value within a given 15-minute performance data collection period, an
adslAturSesLThreshTrap (Section 5.12.5.2.1, Page 243) notification is generated. The value “0” will disable the
notification. The MIB recommended default value of this object is “0.”
Units are in seconds.
Note: the RFC used adslAturPerfCurr15MinSesL. This seems to be a typo as that object does not exist.
5.12.4.7.5
adslAturThreshold15MinUasL
The first time the value of the corresponding instance of adslAturPerfCurr15MinUasL (Section 5.12.4.4.4, Page 238)
reaches or exceeds this value within a given 15-minute performance data collection period, an
adslAturUasLThreshTrap (Section 5.12.5.2.2, Page 243) notification is generated. The value “0” will disable the
notification. The MIB recommended default value of this object is 0."
Units are in seconds.
Note: the RFC used adslAturPerfCurr15MinUasL. This seems to be a typo as that object does not exist.
241
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.5
Traps
This section defines the traps generated.
5.12.5.1
adslExtAtucTraps
OIDs:
•
•
•
adslExtTraps
adslExtAtucTraps
adslExtAtucTapsPrefix
- { adslExtMibObjects 24 }
- { adslExtTraps 1 }
- { adslExtAtucTraps 0 }
1.3.6.1.2.1.10.94.3.1.24
1.3.6.1.2.1.10.94.3.1.24.1
1.3.6.1.2.1.10.94.3.1.24.1.0
Table 124: ADSL Line Extension MIB Atuc Traps
Notification
OID
Variable Bindings / Objects
Status
Supported
adslAtucFailedFastRThreshTrap
{ adslExtAtucTrasPrefix 1 }
adslAtucPerfCurr15MinFailedFastR
adslAtucThreshold15MinFailedFastR
current
N
adslAtucSesLThreshTrap
{ adslExtAtucTrapsPrefix 2 }
adslAtucPerfCurr15MinSesL
adslAtucThreshold15MinSesL
current
Y
adslAtucUasLThreshTrap
{ adslExtAtucTrapsPrefix 3 }
adslAtucPerfCurr15MinUasL
adslAtucThreshold15MinUasL
current
Y
5.12.5.1.1
adslAtucFailedFastRThreshTrap
Failed Fast Retrains 15-minute threshold reached.
5.12.5.1.2
adslAtucSesLThreshTrap
Severely errored seconds-line 15-minute threshold reached.
5.12.5.1.3
aslAtucUasLThreshTrap
Unavailable seconds-line 15-minute threshold reached.
5.12.5.2
adslExtAtruTraps
OIDs:
•
•
•
adslExtTraps
adslExtAturTraps
adslExtAturTrapsPrefix
- { adslExtMibObjects 24 }
- { adslExtTraps 2 }
- { adslExtAturTraps 0 }
242
1.3.6.1.2.1.10.94.3.1.24
1.3.6.1.2.1.10.94.3.1.24.2
1.3.6.1.2.1.10.94.3.1.24.2.0
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
Table 125: ADSL Line Extension MIB Atur Traps
Notification
OID
Variable Bindings / Objects
Status
Supported
adslAturSesLThreshTrap
{ adslExtAturTrapsPrefix 1 }
adslAturPerfCurr15MinSesL
adslAturThreshold15MinSesL
current
Y
adslAturUasLThreshTrap
{ adslExtAturTrapsPrefix 2 }
adslAturPerfCurr15MinUasL
adslAturThreshold15MinUasL
current
Y
5.12.5.2.1
adslAturSesLThreshTrap
Severely errored seconds-line 15-minute threshold reached.
5.12.5.2.2
adslAturUasLThreshTrap
Unavailable seconds-line 15-minute threshold reached.
243
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.6
Conformance Information
5.12.6.1
Compliance
5.12.6.1.1
adslExtLineMibAtucCompliance
The compliance statement for SNMP entities which represent ADSL ATU-C interfaces.
The following groups are mandatory groups:
•
•
•
adslExtLineGroup
adslExtLineConfProfileControlGroup
adslExtLineAlarmConfProfileGroup
The following are optional groups:
•
adslExtAtucPhysPerfCounterGroup
•
adslExtAturPhysPerfCounterGroup
•
adslExtNotificationsGroup
- This group is optional. Implementations which require continuous ATU-C physical event counters should implement this
group.
- This group is optional. Implementations which require continuous ATU-R physical event counters should implement this
group.
- This group is optional. Implementations which support TCA
(Threshold Crossing Alert) should implement this group.
The following objects have a MIN-ACCESS defined:
•
adslAtucThreshold15MinFailedFastR
•
adslAtucThreshold15MinSesL
•
adslAtucThreshold15MinUasL
•
adslAturThreshold15MinSesL
•
adslAturThreshold15MinUasL
•
adslLineConfProfileDualLite
- MIN-ACCESS read-write
Read-write access is applicable only when static profiles as
defined in ADSL Line MIB [RFC 2662] are implemented.
- MIN-ACCESS read-write
Read-write access is applicable only when static profiles as
defined in ADSL Line MIB [RFC 2662] are implemented.
- MIN-ACCESS read-write
Read-write access is applicable only when static profiles as
defined in ADSL Line MIB [RFC 2662] are implemented.
- MIN-ACCESS read-write
Read-write access is applicable only when static profiles as
defined in ADSL Line MIB [RFC 2662] are implemented.
- MIN-ACCESS read-write
Read-write access is applicable only when static profiles as
defined in ADSL Line MIB [RFC 2662] are implemented.
- MIN-ACCESS read-only
Read-only access is applicable only when static profiles as
defined in ADSL Line MIB [RFC 2662] are implemented.
244
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
5.12.6.2
Conformance
Table 126: ADSL-LINE-EXT-MIB Conformance (1 of 2)
Group
Description
Objects
Supported
adslExtLineGroup
A collection of objects providing
extended configuration information
about an ADSL Line.
adslLineConfProfileDualLite
N
adslLineTransAutcCap
Y
adslLineTransAtucConfig
Y
adslLineTransAtucActual
Y
adslLineGlitePowerState
Y
adslAtucPerfStatFastR
Y
adslAtucPerfStatFailedFastR
Y
adslAtucPerfCurr15MinFastR
Y
adslAtucPerfCurr15MinFailedFastR
Y
adslAtucPerfCurr1DayFastR
Y
adslAtucPerfCurr1DayFailedFastR
Y
adslAtucPerfPrev1DayFastR
Y
adslAtucPerfPrev1DayFailedFastR
Y
adslAtucPerfStatSesL
Y
adslAtucPerfStatUasL
Y
adslAtucPerfCurr15MinSesL
Y
adslAtucPerfCurr15MinUasL
Y
adslAtucPerfCurr1DaySesL
Y
adslAtucPerfCurr1DayUasL
Y
adslAtucPerfPrev1DaySesL
Y
adslAtucPerfPrev1DayUasL
Y
adslAtucIntervalFastR
Y
adslAtucIntervalFailedFastR
Y
adslAtucIntervalSesL
Y
adslAtucIntervalUasL
Y
adslExtAtucPhysPerfCounterGroup
A collection of objects providing raw
performance counts on an ADSL Line
(ATU-C end).
245
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ADSL-LINE-EXT- MIB — RFC 3440
Table 126: ADSL-LINE-EXT-MIB Conformance (2 of 2)
Group
Description
Objects
Supported
adslExtAturPhysPerfCounterGroup
A collection of objects providing raw
performance counts on an ADSL Line
(ATU-C end).
adslAturPerfStatSesL
Y
adslAturPerfStatUasL
Y
adslAturPerfCurr15MinSesL
Y
adslAturPerfCurr15MinUasL
Y
adslAturPerfCurr1DaySesL
Y
adslAturPerfCurr1DayUasL
Y
adslAturPerfPrev1DaySesL
Y
adslAturPerfPrev1DayUasL
Y
adslAturIntervalSesL
Y
adslAturIntervalUasL
Y
adslConfProfileLineType
Y
adslAutcThreshold15MinFailedFastR
Y
adslAtucThreshold15MinSesL
Y
adslAtucThreshold15MinUasL
Y
adslAturThreshold15MinSesL
Y
adslAturThreshold15MinUasL
Y
adslAutcFailedFastRThreshTrap
N
adslAutcSesLThreshTrap
Y
adslAutcUasLThreshTrap
Y
adslAutrSesLThreshTrap
Y
adslAutrUasLThreshTrap
Y
adslExtLineConfProfileControlGroup
A collection of objects providing profile
control for the ADSL system.
adslExtLineAlarmConfProfileGroup
A collection of objects providing alarm
profile control for the ADSL system.
adslExtNotificationsGroup
The collection of ADSL extension
notifications.
246
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13 HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.1
Introduction
This MIB defines objects for the management of SHDSL lines for the BitStorm 2600 and GranDSLAM 4200 IP
DSLAM. The RFC used as a reference was dated May 2002 and the MIB has a LAST-UPDATED of
“200205090000Z.”
Not all objects defined in the MIB are supported by the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. What is
supported or not supported is identified.
5.13.2
Standard and Enterprise MIB Interworking Relationship Note
An enterprise MIB, PDN-HDSL2-SHDSL-LINE-MIB (Section 5.57, Page 753), extends or supplements this MIB to
provide support for G.shdsl.bis. This enterprise MIB adds increased DSL line rates along with the bonding of
additional wire pairs. When operating the SHDSL ports in non-bis configurations, ether this MIB or the enterprise
MIB can be used to configure, get status, or get statistics on DSL ports. When DSL ports are configured using
SHDSL.bis parameters, the enterprise MIB must be used configure, get status, or get statistics on DSL ports as this
MIB does not support the syntax necessary for .bis operation.
Whenever an object in this MIB has a parameter that is out of range with respect to the syntax in this MIB, an attempt
to access that object will result in a failure code of noSuchName. The manager will be expected to use the
corresponding object in the enterprise MIB.
Along with MIB objects, there are traps defined in the enterprise MIB that have variable bindings or objects that are
sensitive to SHDSL.bis extended optioning. It is expected that when a trap needs to be sent, the traps defined in this
MIB will be sent as long as each variable binding or object can be represented with the syntax defined in this MIB.
When a trap needs to be sent and one of its variable bindings or objects can’t be represented with the syntax defined
in this MIB, the corresponding trap defined in the enterprise MIB must be sent. The following table identifies the
objects in this MIB that have corresponding objects in the enterprise MIB:
Table 127: HDSL2-SHDSL Standard MIB to Enterprise MIB object Mappings (1 of 2)
Standard MIB
Enterprise MIB
Object
Page
Object
Page
hdsl2ShdslStatusMaxAttainableLineRate
253
pdnHdsl2ShdslStatusMaxAttainableLineRate
755
hdsl2ShdslStatusActualLineRate
253
pdnHdsl2ShdslStatusActualLineRate
755
hdsl2ShdslEndpointConfTable
256
pdnHdsl2ShdslEndpointConfTable
755
hdsl2ShdslEndpointCurrTable
257
pdnHdsl2ShdslEndpointCurrTable
756
hdsl2Shdsl15MinIntervalTable
261
pdnHdsl2Shdsl15MinIntervalTable
760
hdsl2Shdsl1DayIntervalTable
262
pdnHdsl2Shdsl1DayIntervalTable
761
hdsl2ShdslSpanConfWireInterface
268
pdnHdsl2ShdslSpanConfWireInterface
764
247
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 127: HDSL2-SHDSL Standard MIB to Enterprise MIB object Mappings (2 of 2)
Standard MIB
Enterprise MIB
Object
Page
Object
Page
hdsl2ShdslSpanConfMinLineRate
268
pdnHdsl2ShdslSpanConfMinLineRate
764
hdsl2ShdslSpanConfMaxLineRate
268
pdnHdsl2ShdslSpanConfMaxLineRate
764
hdsl2ShdslLoopAttenCrossing
274
pdnHdsl2ShdslLoopAttenCrossing
766
hdsl2ShdslSNRMarginCrossing
274
pdnHdsl2ShdslSNRMarginCrossing
767
hdsl2ShdslPerfESThresh
274
pdnHdsl2ShdslPerfESThresh
767
hdsl2ShdslPerfSESThresh
274
pdnHdsl2ShdslPerfSESThresh
767
hdsl2ShdslPerfCRCanomaliesThresh
274
pdnHdsl2ShdslPerfCRCanomaliesThresh
767
hdsl2ShdslPerfLOSWSThresh
274
pdnHdsl2ShdslPerfLOSWSThresh
767
hdsl2ShdslPerfUASThresh
274
pdnHdsl2ShdslPerfUASThresh
767
hdsl2ShdslpowerBackoff
274
pdnHdsl2ShdslpowerBackoff
767
hdsl2ShdsldeviceFault
275
pdnHdsl2ShdsldeviceFault
767
hdsl2ShdsldcContinuityFault
275
pdnHdsl2ShdsldcContinuityFault
767
hdsl2ShdslconfigInitFailure
275
pdnHdsl2ShdslconfigInitFailure
767
hdsl2ShdslnoNeighborPresent
275
pdnHdsl2ShdslnoNeighborPresent
768
5.13.3
•
•
•
•
•
•
•
•
•
•
•
•
Naming Conventions
xtuC
- central site terminal unit; H2TU-C for HDSL2, or STU-C for SHDSL
xtuR
- remote site terminal unit; H2TU-R for HDSL2, or STU-R for SHDSL
xtu
- terminal unit; either an xtuC or xtuR
xru
- regenerator unit; H2RU for HDSL2, or SRU for SHDSL
xU
- any HDSL2/SHDSL unit; either an xtu or xru
CRC
- cyclic redundancy check
ES
- errored second
LOSW
- loss of sync word
LOSWS - LOSW seconds
SES
- severely errored second
SNR
- signal-to-noise ratio
UAS
- unavailable second
248
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.4
Textual Conventions
The following textual conventions are made in the reference document:
•
Hdsl2ShdslPerfCurrDayCount - A gauge associated with interface performance measurements in a current 1-day (24 hour) measurement interval.
The value of this gauge starts at zero at the beginning of an interval and is increased when associated events
occur, until the end of the 1-day interval. At that time the value of the gauge is stored in the previous 1-day
history interval, as defined in a companion object of type Hdsl2Shdsl1DayIntervalCount (Section 5.13.4,
Page 249), and the current interval gauge is restarted at zero.
In the case where the agent has no valid data available for this interval the corresponding object instance is
not available and upon a retrieval request a corresponding error message shall be returned to indicate that
this instance does not exist. Please note that zero is a valid value.
— Syntax
•
Gauge32
Hdsl2Shdsl1DayIntervalCount - A counter associated with interface performance measurements during
the most previous 1-day (24 hour) measurement interval. The value of this gauge is equal to the value of the
current day gauge, as defined in a companion object of type Hdsl2ShdslPerfCurrDayCount (Section 5.13.4,
Page 249), at the end of its most recent interval.
In the case where the agent has no valid data available for this interval the corresponding object instance is
not available and upon a retrieval request a corresponding error message shall be returned to indicate that
this instance does not exist.
— Syntax
Gauge32
•
Hdsl2ShdslPerfTimeElapsed - The number of seconds that have elapsed since the beginning of the current
measurement period. If, for some reason, such as an adjustment in the system’s time-of-day clock or the
addition of a leap second, the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0…899). For 24 hour intervals, the range is limited to (0…86399).
— Syntax
Unsigned32(0…86399)
•
Hdsl2ShdslPerfIntervalThreshold - This convention defines a range of values that may be set in a fault
threshold alarm control. As the number of seconds in a 15-minute interval numbers at most 900, objects of
this type may have a range of 0…900, where the value of 0 disables the alarm.
— Syntax
Unsigned32(0…900)
•
Hdsl2ShdslUnitId - This is the unique identification for all units in a HDSL2/SHDSL Span. It is based on
the EOC unit addressing scheme with reference to the xtuC.
— Syntax
INTEGER
• xtuC(1)
• xtuR(2)
• xru1(3)
• xru2(4)
• xru3(5)
• xru4(6)
• xru5(7)
• xru6(8)
• xru7(9)
• xru8(10)
249
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
•
Hdsl2ShdslUnitSide - This is the referenced side of a HDSL2/SHDSL unit - Network or Customer side.
The side facing the Network is the Network side, while the side facing the Customer is the Customer side.
— Syntax
INTEGER
• networkSide(1)
• customerSide(2)
•
Hdsl2ShdslWirePair - This is the referenced pair of wires in a HDSL2/SHDSL Segment. HDSL2 only supports a single pair (wirePair1), while SHDSL supports an optional second pair (wirePair2).
— Syntax
INTEGER
• wirePair1(1)
• wirePair2(2)
•
Hdsl2ShdslTransmissionModeType - Contains the regional setting of the HDSL2/SHDSL span, represented as a bit-map of possible settings. The various bit positions are:
— Syntax
BITS
• region1(0) - Indicates ITU-T G.991.2 Annex A.
• region2(1) - Indicates ITU-T G.991.2 Annex B.
•
Hdsl2ShdslClockReferenceType - The various STU-C symbol clock references for the HDSL2/SHDSL
span, represented as an enumeration.
— Syntax
INTEGER
• localClk(1)
- Mode-1 per G991.2
• networkClk(2)
- Mode-2 per G991.2
• dataOrNetworkClk(3)
- Mode-3a per G991.2
• dataClk(4)
- Mode-3b per G991.2
5.13.5
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
hdsl2SdslMIB
hdsl2ShdslNotifications
hdsl2ShdslMibObjects
5.13.6
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 48 }
{ hdsl2SdslMIB 0 }
{ hdsl2SdslMIB 1 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.48
1.3.6.1.2.1.10.48.0
1.3.6.1.2.1.10.48.1
The table identifies objects called out in this MIB. Any table object that has elements that are supported are indicated
by a “Y” in the Supported column.
250
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 128: HDSL2-SHDSL-LINE-MIB Objects
Object
OID
Syntax
SEQUENCE of
Access
Status
Supported
hdsl2ShdslSpanConfTable
{ hdsl2ShdslMibObjects 1 }
hdsl2ShdslSpanConfEntry
not-accessible
current
Y
hdsl2ShdslSpanStatusTable
{ hdsl2ShdslMibObjects 2 }
hdsl2ShdslSpanStatusEntry
not-accessible
current
Y
hdsl2ShdslInventoryTable
{ hdsl2ShdslMibObjects 3 }
hdsl2ShdslInventoryEntry
not-accessible
current
Y
hdsl2ShdslEndpointConfTable
{ hdsl2ShdslMibObjects 4 }
hdsl2ShdslEndpointConfEntry
not-accessible
current
Y
hdsl2ShdslEndpointCurrTable
{ hdsl2ShdslMibObjects 5 }
hdsl2ShdslEndpointCurrEntry
not-accessible
current
Y
hdsl2Shdsl15MinIntervalTable
{ hdsl2ShdslMibObjects 6 }
hdsl2Shdsl15MinIntervalEntry
not-accessible
current
Y
hdsl2Shdsl1DayIntervalTable
{ hdsl2ShdslMibObjects 7 }
hdsl2Shdsl1DayIntervalEntry
not-accessible
current
Y
hdsl2ShdslEndpointMaintTable
{ hdsl2ShdslMibObjects 8 }
hdsl2ShdslEndpointMaintEntry
not-accessible
current
Y
hdsl2ShdslUnitMaintTable
{ hdsl2ShdslMibObjects 9 }
hdsl2ShdslUnitMaintEntry
not-accessible
current
Y
hdsl2ShdslSpanConfProfileTable
{ hdsl2ShdslMibObjects 10 }
hdsl2ShdslSpanConfProfileEntry
not-accessible
current
Y
hdsl2ShdslEndpointAlarmConfProfileTable
{ hdsl2ShdslMibObjects 11 }
hdsl2ShdslEndpointAlarmConfProfileEntry
not-accessible
current
Y
5.13.6.1
Span Configuration Group
5.13.6.1.1
hdsl2ShdslSpanConfTable
This table supports overall configuration of HDSL2/SHDSL Spans. Entries in this table MUST be maintained in a
persistent manner. Each entry represents the complete Span in a single HDSL2/SHDSL line. It is indexed by the
ifIndex (Section 5.3.4.3.1, Page 39) of the associated HDSL2/SHDSL line.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
hdsl2ShdslSpanConfTable
hdsl2ShdslSpanConfEntry
- { hdsl2ShdslMibObjects 1 }
1.3.6.1.2.1.10.48.1.1
- { hdsl2ShdslSpanConfTable 1 } 1.3.6.1.2.1.10.48.1.1.1
251
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 129: hdsl2ShdslSpanConfTable
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslSpanConfNumRepeaters
{ hdsl2ShdslSpanConfEntry 1 }
Unsigned32
(0…8)
read-write
current
Y
hdsl2ShdslSpanConfProfile
{ hdsl2ShdslSpanConfEntry 2 }
SnmpAdminString
(SIZE(1…32))
read-write
current
Y
hdsl2ShdslSpanConfAlarmProfile
{ hdsl2ShdslSpanConfEntry 3 }
SnmpAdminString
(SIZE(1…32))
read-write
current
Y
5.13.6.1.1.1
hdsl2ShdslSpanConfNumRepeaters
This object provisions the number of repeaters/regenerators in this HDSL2/SHDSL Span in units of repeaters.
5.13.6.1.1.2
hdsl2ShdslSpanConfProfile
This object is a pointer to a span configuration profile in the hdsl2ShdslSpanConfProfileTable (Section 5.13.6.9.1,
Page 266), which applies to this span. The value of this object is the index of the referenced profile in the
hdsl2ShdslSpanConfProfileTable (Section 5.13.6.9.1, Page 266). Note that span configuration profiles are only
applicable to SHDSL lines.
HDSL2 lines MUST reference the default profile, “DEFVAL.” By default, this object will have the value “DEFVAL”
(the index of the default profile).
Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table,
hdsl2ShdslSpanConfProfileTable (Section 5.13.6.9.1, Page 266), MUST be rejected.
5.13.6.1.1.3
hdsl2ShdslSpanConfAlarmProfile
This object is a pointer to an Alarm configuration profile in the hdsl2ShdslEndpointAlarmConfProfileTable (Section
5.13.6.10.1, Page 270). The value of this object is the index of the referenced profile in the
hdsl2ShdslEndpointAlarmConfProfileTable (Section 5.13.6.10.1, Page 270). The alarm threshold configuration in
the referenced profile will be used by default for all segment endpoints in this span. Individual endpoints may
override this profile by explicitly specifying some other profile in the hdsl2ShdslEndpointConfTable (Section
5.13.6.4.1, Page 256). By default, this object will have the value “DEFVAL” (the index of the default profile).
Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table,
hdsl2ShdslEndpointAlarmConfProfileTable (Section 5.13.6.10.1, Page 270), MUST be rejected.
5.13.6.2
5.13.6.2.1
Span Status Group
hdsl2ShdslSpanStatusTable
This table provides overall status information of HDSL2/SHDSL spans. This table contains live data from equipment.
252
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
As such, it is NOT persistent. Each entry represents the complete span in a single HDSL2/SHDSL line. It is indexed
by the ifIndex (Section 5.3.4.3.1, Page 39) of the associated HDSL2/SHDSL line.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
hdsl2ShdslSpanStatusTable - { hdsl2ShdslMibObjects 2 }
1.3.6.1.2.1.10.48.1.2
hdsl2ShdslSpanStatusEntry - { hdsl2ShdslSpanStatusTable 1 } 1.3.6.1.2.1.10.48.1.2.1
Table 130: hdsl2ShdslSpanStatusTable
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslStatusNumAvailRepeaters
{ hdsl2ShdslSpanStatusEntry 1 }
Unsigned32(0…8)
read-only
current
Y
hdsl2ShdslStatusMaxAttainableLineRate
{ hdsl2ShdslSpanStatusEntry 2 }
Unsigned32
(0…4112000)
read-only
current
Y
hdsl2ShdslStatusActualLineRate
{ hdsl2ShdslSpanStatusEntry 3 }
Unsigned32
(0…4112000)
read-only
current
Y
hdsl2ShdslStatus
TransmissionModeCurrent
{ hdsl2ShdslSpanStatusEntry 4 }
Hdsl2ShdslTransmissionModeType
read-only
current
Y
5.13.6.2.1.1
hdsl2ShdslStatusNumAvailRepeaters
Contains the actual number of repeaters/regenerators discovered in this HDSL2/SHDSL span.
5.13.6.2.1.2
hdsl2ShdslStatusMaxAttainableLineRate
Contains the maximum attainable line rate, in bps, in this HDSL2/SHDSL span. This object provides the maximum
rate the line is capable of achieving. This is based upon measurements made during line probing.
5.13.6.2.1.3
hdsl2ShdslStatusActualLineRate
Contains the actual line rate, in bps, in this HDSL2/SHDSL span. This should equal ifSpeed (Section 5.3.4.3.5, Page
45).
5.13.6.2.1.4
hdsl2ShdslStatusTransmissionModeCurrent
Contains the current Power Spectral Density (PSD) regional setting of the HDSL2/SHDSL span.
5.13.6.3
Unit Inventory Group
253
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.3.1
hdsl2ShdslInventoryTable
This table supports retrieval of unit inventory information available via the EOC from units in a HDSL2/SHDSL line.
Entries in this table are dynamically created during the line discovery process. The life cycle for these entries is as
follows:
•
•
•
•
xtu discovers a device, either a far-end xtu or an xru
an inventory table entry is created for the device
the line goes down for whatever reason
inventory table entries for unreachable devices are destroyed.
As these entries are created/destroyed dynamically, they are NOT persistent.
Each entry represents inventory information for a single unit in a HDSL2/SHDSL line. It is indexed by the ifIndex
(Section 5.3.4.3.1, Page 39) of the HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the associated unit.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex
OIDs:
•
•
hdsl2ShdslSpanInverntoryTable - { hdsl2ShdslMibObjects 3 }
hdsl2ShdslInventoryEntry
- { hdsl2ShdslSpanInverntoryTable 1 }
1.3.6.1.2.1.10.48.1.3
1.3.6.1.2.1.10.48.1.3.1
Table 131: hdsl2ShdslInventoryTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslInvIndex
{ hdsl2ShdslInventoryEntry 1 }
Hdsl2ShdslUnitId
not-accessible
current
Y
hdsl2ShdslInvVendorID
{ hdsl2ShdslInventoryEntry 2 }
OCTET STRING
(SIZE(8))
read-only
current
Y
hdsl2ShdslInvVendorModelNumber
{ hdsl2ShdslInventoryEntry 3 }
OCTET STRING
(SIZE(12))
read-only
current
Y
hdsl2ShdslInvVendorSerialNumber
{ hdsl2ShdslInventoryEntry 4 }
OCTET STRING
(SIZE(12))
read-only
current
Y
hdsl2ShdslInvVendorEOCSoftwareVersion
{ hdsl2ShdslInventoryEntry 5 }
Integer32
read-only
current
Y
hdsl2ShdslInvStandardVersion
{ hdsl2ShdslInventoryEntry 6 }
Integer32
read-only
current
Y
hdsl2ShdslInvVendorListNumber
{ hdsl2ShdslInventoryEntry 7 }
OCTET STRING
(SIZE(3))
read-only
current
Y
hdsl2ShdslInvVendorIssueNumber
{ hdsl2ShdslInventoryEntry 8 }
OCTET STRING
(SIZE(2))
read-only
current
Y
hdsl2ShdslInvVendorSoftwareVersion
{ hdsl2ShdslInventoryEntry 9 }
OCTET STRING
(SIZE(6))
read-only
current
Y
254
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 131: hdsl2ShdslInventoryTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslInvEquipmentCode
{ hdsl2ShdslInventoryEntry 10 }
OCTET STRING
(SIZE(10))
read-only
current
Y
hdsl2ShdslInvVendorOther
{ hdsl2ShdslInventoryEntry 11 }
OCTET STRING
(SIZE(12))
read-only
current
Y
hdsl2ShdslInvTransmissionModeCapability
{ hdsl2ShdslInventoryEntry 12 }
Hdsl2ShdslTransmissionModeType
read-only
current
Y
5.13.6.3.1.1
hdsl2ShdslInvIndex
Each entry in this table corresponds to a physical element in a HDSL2/SHDSL Span. It is based on the EOC unit
addressing scheme with reference to the xtuC.
5.13.6.3.1.2
hdsl2ShdslInvVendorID
Vendor ID as reported in an Inventory Response message.
5.13.6.3.1.3
hdsl2ShdslInvVendorModelNumber
Vendor model number as reported in an Inventory Response message.
5.13.6.3.1.4
hdsl2ShdslInvVendorSerialNumber
Vendor serial number as reported in an Inventory Response message.
5.13.6.3.1.5
hdsl2ShdslInvVendorEOCSoftwareVersion
Vendor EOC version as reported in a Discovery Response message.
5.13.6.3.1.6
hdsl2ShdslInvStandardVersion
Version of the HDSL2/SHDSL standard implemented, as reported in an Inventory Response message.
5.13.6.3.1.7
hdsl2ShdslInvVendorListNumber
Vendor list number as reported in an Inventory Response message.
5.13.6.3.1.8
hdsl2ShdslInvVendorIssueNumber
Vendor issue number as reported in an Inventory Response message.
5.13.6.3.1.9
hdsl2ShdslInvVendorSoftwareVersion
Vendor software version as reported in an Inventory Response message.
5.13.6.3.1.10
hdsl2ShdslInvEquipmentCode
Equipment code conforming to ANSI T1.213, Coded Identification of Equipment Entities.
5.13.6.3.1.11
hdsl2ShdslInvVendorOther
Other vendor information as reported in an Inventory Response message.
255
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.3.1.12
hdsl2ShdslInvTransmissionModeCapability
Contains the transmission mode capability of the SHDSL unit.
5.13.6.4
Segment Endpoint Configuration Group
5.13.6.4.1
hdsl2ShdslEndpointConfTable
This table supports configuration parameters for segment endpoints in a HDSL2/SHDSL line. As this table is indexed
by ifIndex (Section 5.3.4.3.1, Page 39), it MUST be maintained in a persistent manner. Each entry represents a single
segment endpoint in a HDSL2/SHDSL line. It is indexed by the ifIndex (Section 5.3.4.3.1, Page 39) of the HDSL2/
SHDSL line, the Unit Id of the associated unit, the side of the unit, and the wire-pair of the associated modem.
Index(es):
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex (Section 5.13.6.3.1.1, Page 255)
hdsl2ShdslEndpointSide
hdsl2ShdslEndpointWirePair
OIDs:
•
•
hdsl2ShdslEndpointConfTable
hdsl2ShdslEndpointConfEntry
- { hdsl2ShdslMibObjects 4 }
- { hdsl2ShdslEndpointConfTable 1 }
1.3.6.1.2.1.10.48.1.4
1.3.6.1.2.1.10.48.1.4.1
Table 132: hdsl2ShdslEndpointConfTable
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslEndpointSide
{ hdsl2ShdslEndpointConfEntry 1 }
Hdsl2ShdslUnitSide
not-accessible
current
Y
hdsl2ShdslEndpointWirePair
{ hdsl2ShdslEndpointConfEntry 2 }
Hdsl2ShdslWirePair
not-accessible
current
Y
hdsl2ShdslEndpointAlarmConfProfile
{ hdsl2ShdslEndpointConfEntry 3 }
SnmpAdminString
(SIZE(0…32))
read-write
current
Y
5.13.6.4.1.1
hdsl2ShdslEndpointSide
The side of the unit associated with this segment endpoint - Network/Customer side - as per the Hdsl2ShdslUnitSide
textual convention.
5.13.6.4.1.2
hdsl2ShdslEndpointWirePair
The wire-pair of the modem associated with this segment endpoint as per the Hdsl2ShdslWirePair textual convention.
256
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.4.1.3
hdsl2ShdslEndpointAlarmConfProfile
This object configures the alarm threshold values to be used for this segment endpoint. The values are obtained from
the alarm configuration profile referenced by this object. The value of this object is the index of the referenced profile
in the hdsl2ShdslEndpointAlarmConfProfileTable (Section 5.13.6.10.1, Page 270), or NULL (a zero- length
SnmpAdminString). If the value is a zero-length SnmpAdminString, the endpoint uses the default Alarm
Configuration Profile for the associated span as per the hdsl2ShdslSpanConfAlarmProfile (Section 5.13.6.1.1.3, Page
252) object in the hdsl2ShdslSpanConfTable (Section 5.13.6.1.1, Page 251). The default value of this object is a zerolength SnmpAdminString.
Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table,
hdsl2ShdslEndpointAlarmConfProfileTable (Section 5.13.6.10.1, Page 270), MUST be rejected.
5.13.6.5
Segment Endpoint Current Status/Performance Group
5.13.6.5.1
hdsl2ShdslEndpointCurrTable
This table contains current status and performance information for segment endpoints in HDSL2/SHDSL Lines. As
with other tables in this MIB indexed by ifIndex (Section 5.3.4.3.1, Page 39), entries in this table MUST be
maintained in a persistent manner. Each entry contains status and performance information relating to a single
segment endpoint. It is indexed by the ifIndex (Section 5.3.4.3.1, Page 39) of the HDSL2/SHDSL line, the Unit Id of
the associated unit, the side of the unit, and the wire-pair of the associated modem.
Index(es):
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex (Section 5.13.6.3.1.1, Page 255)
hdsl2ShdslEndpointSide (Section 5.13.6.4.1.1, Page 256)
hdsl2ShdslEndpointWirePair (Section 5.13.6.4.1.2, Page 256)
OIDs:
•
•
hdsl2ShdslEndpointCurrTable
hdsl2ShdslEndpointCurrEntry
- { hdsl2ShdslMibObjects 5 }
- { hdsl2ShdslEndpointCurrTable 1 }
1.3.6.1.2.1.10.48.1.5
1.3.6.1.2.1.10.48.1.5.1
Table 133: hdsl2ShdslEndpointCurrTable (1 of 3)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslEndpointCurrAtn
{ hdsl2ShdslEndpointCurrEntry 1 }
Integer32(-127…128)
read-only
current
Y
hdsl2ShdslEndpointCurrSnrMgn
{ hdsl2ShdslEndpointCurrEntry 2 }
Integer32(-127…128)
read-only
current
Y
257
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 133: hdsl2ShdslEndpointCurrTable (2 of 3)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslEndpointCurrStatus
{ hdsl2ShdslEndpointCurrEntry 3 }
BITS
noDefect(0)
powerBackoff(1)
deviceFault(2)
dcContinuityFault(3)
snrMarginAlarm(4)
loopAttenuationAlarm(5)
loswFailureAlarm(6)
configInitFailure(7)
protocolInitFailure(8)
noNeighborPresent(9)
loopbackActive(10)
read-only
current
Y
hdsl2ShdslEndpointES
{ hdsl2ShdslEndpointCurrEntry 4 }
Counter32
read-only
current
Y
hdsl2ShdslEndpointSES
{ hdsl2ShdslEndpointCurrEntry 5 }
Counter32
read-only
current
Y
hdsl2ShdslEndpointCRCanomalies
{ hdsl2ShdslEndpointCurrEntry 6 }
Counter32
read-only
current
Y
hdsl2ShdslEndpointLOSWS
{ hdsl2ShdslEndpointCurrEntry 7 }
Counter32
read-only
current
Y
hdsl2ShdslEndpointUAS
{ hdsl2ShdslEndpointCurrEntry 8 }
Counter32
read-only
current
Y
hdsl2ShdslEndpointCurr15MinTimeElapsed
{ hdsl2ShdslEndpointCurrEntry 9 }
Hdsl2ShdslPerfTimeElapsed
read-only
current
Y
hdsl2ShdslEndpointCurr15MinES
{ hdsl2ShdslEndpointCurrEntry 10 }
PerfCurrentCount
read-only
current
Y
hdsl2ShdslEndpointCurr15MinSES
{ hdsl2ShdslEndpointCurrEntry 11 }
PerfCurrentCount
read-only
current
Y
hdsl2ShdslEndpointCurr15MinCRCanomalies
{ hdsl2ShdslEndpointCurrEntry 12 }
PerfCurrentCount
read-only
current
Y
hdsl2ShdslEndpointCurr15MinLOSWS
{ hdsl2ShdslEndpointCurrEntry 13 }
PerfCurrentCount
read-only
current
Y
hdsl2ShdslEndpointCurr15MinUAS
{ hdsl2ShdslEndpointCurrEntry 14 }
PerfCurrentCount
read-only
current
Y
hdsl2ShdslEndpointCurr1DayTimeElapsed
{ hdsl2ShdslEndpointCurrEntry 15 }
Hdsl2ShdslPerfTimeElapsed
read-only
current
Y
hdsl2ShdslEndpointCurr1DayES
{ hdsl2ShdslEndpointCurrEntry 16 }
Hdsl2ShdslPerfCurrDayCount
read-only
current
Y
hdsl2ShdslEndpointCurr1DaySES
{ hdsl2ShdslEndpointCurrEntry 17 }
Hdsl2ShdslPerfCurrDayCount
read-only
current
Y
258
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 133: hdsl2ShdslEndpointCurrTable (3 of 3)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslEndpointCurr1DayCRCanomalies
{ hdsl2ShdslEndpointCurrEntry 18 }
Hdsl2ShdslPerfCurrDayCount
read-only
current
Y
hdsl2ShdslEndpointCurr1DayLOSWS
{ hdsl2ShdslEndpointCurrEntry 19 }
Hdsl2ShdslPerfCurrDayCount
read-only
current
Y
hdsl2ShdslEndpointCurr1DayUAS
{ hdsl2ShdslEndpointCurrEntry 20 }
Hdsl2ShdslPerfCurrDayCount
read-only
current
Y
5.13.6.5.1.1
hdsl2ShdslEndpointCurrAtn
The current loop attenuation, in units of dB, for this endpoint as reported in a Network or Customer Side Performance
Status message.
5.13.6.5.1.2
hdsl2ShdslEndpointCurrSnrMgn
The current SNR margin, in units of dB, for this endpoint as reported in a Status Response/SNR message.
5.13.6.5.1.3
hdsl2ShdslEndpointCurrStatus
Contains the current state of the endpoint. This is a bitmap of possible conditions. The various bit positions are:
•
•
•
•
noDefect(0)
powerBackoff(1)
deviceFault(2)
dcContinuityFault(3)
-
•
•
•
•
snrMarginAlarm(4)
loopAttenuationAlarm(5)
loswFailureAlarm(6)
configInitFailure(7)
-
•
protocolInitFailure(8)
-
•
noNeighborPresent(9)
-
•
loopbackActive(10)
-
There no defects on the line.
Indicates enhanced Power Backoff.
Indicates a vendor-dependent diagnostic or self-test fault has been detected.
Indicates vendor-dependent conditions that interfere with span powering
such as short and open circuits.
Indicates that the SNR margin has dropped below the alarm threshold.
Indicates that the loop attenuation exceeds the alarm threshold.
Indicates a forward LOSW alarm.
Endpoint failure during initialization due to paired endpoint not able to support requested configuration.
Endpoint failure during initialization due to incompatible protocol used by
the paired endpoint.
Endpoint failure during initialization due to no activation sequence detected
from paired endpoint.
A loopback is currently active at this Segment Endpoint.
This is intended to supplement ifOperStatus (Section 5.3.4.3.8, Page 49). Note that there is a 1-1 relationship between
the status bits defined in this object and the notification thresholds defined elsewhere in this MIB (see Traps, Section
5.13.7, Page 273).
5.13.6.5.1.4
hdsl2ShdslEndpointES
Count of Errored Seconds (ES) on this endpoint since the xU was last restarted.
259
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.5.1.5
hdsl2ShdslEndpointSES
Count of Severely Errored Seconds (SES) on this endpoint since the xU was last restarted.
5.13.6.5.1.6
hdsl2ShdslEndpointCRCanomalies
Count of CRC anomalies, in units of detected CRC Anomalies, on this endpoint since the xU was last restarted.
5.13.6.5.1.7
hdsl2ShdslEndpointLOSWS
Count of Loss of Sync Word (LOSW) Seconds on this endpoint since the xU was last restarted.
5.13.6.5.1.8
hdsl2ShdslEndpointUAS
Count of Unavailable Seconds (UAS) on this endpoint since the xU was last restarted.
5.13.6.5.1.9
hdsl2ShdslEndpointCurr15MinTimeElapsed
Total elapsed seconds in the current 15-minute interval.
5.13.6.5.1.10
hdsl2ShdslEndpointCurr15MinES
Count of Errored Seconds (ES) in the current 15-minute interval.
5.13.6.5.1.11
hdsl2ShdslEndpointCurr15MinSES
Count of Severely Errored Seconds (SES) in the current 15-minute interval.
5.13.6.5.1.12
hdsl2ShdslEndpointCurr15MinCRCanomalies
Count of CRC anomalies, in units of detected CRC Anomalies, in the current 15-minute interval.
5.13.6.5.1.13
hdsl2ShdslEndpointCurr15MinLOSWS
Count of Loss of Sync Word (LOSW) Seconds in the current 15-minute interval.
5.13.6.5.1.14
hdsl2ShdslEndpointCurr15MinUAS
Count of Unavailable Seconds (UAS) in the current 15-minute interval.
5.13.6.5.1.15
hdsl2ShdslEndpointCurr1DayTimeElapsed
Number of seconds that have elapsed since the beginning of the current 1-day interval.
5.13.6.5.1.16
hdsl2ShdslEndpointCurr1DayES
Count of Errored Seconds (ES) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed
(Section 5.13.6.5.1.15, Page 260).
5.13.6.5.1.17
hdsl2ShdslEndpointCurr1DaySES
Count of Severely Errored Seconds (SES) during the current day as measured by
hdsl2ShdslEndpointCurr1DayTimeElapsed (Section 5.13.6.5.1.15, Page 260).
5.13.6.5.1.18
hdsl2ShdslEndpointCurr1DayCRCanomalies
Count of CRC anomalies during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed (Section
5.13.6.5.1.15, Page 260).
260
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.5.1.19
hdsl2ShdslEndpointCurr1DayLOSWS
Count of Loss of Sync Word (LOSW) Seconds during the current day as measured by
hdsl2ShdslEndpointCurr1DayTimeElapsed (Section 5.13.6.5.1.15, Page 260).
5.13.6.5.1.20
hdsl2ShdslEndpointCurr1DayUAS
Count of Unavailable Seconds (UAS) during the current day as measured by
hdsl2ShdslEndpointCurr1DayTimeElapsed (Section 5.13.6.5.1.15, Page 260).
5.13.6.6
Segment Endpoint 15-Minute Interval Status/Performance Group
5.13.6.6.1
hdsl2Shdsl15MinIntervalTable
This table provides one row for each HDSL2/SHDSL endpoint performance data collection interval. This table
contains live data from equipment. As such, it is NOT persistent.
Index(es):
•
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex (Section 5.13.6.3.1.1, Page 255)
hdsl2ShdslEndpointSide (Section 5.13.6.4.1.1, Page 256)
hdsl2ShdslEndpointWirePair (Section 5.13.6.4.1.2, Page 256)
hdsl2Shdsl15MinIntervalNumber
OIDs:
•
•
hdsl2Shdsl15MinIntervalTable
hdsl2Shdsl15MinIntervalEntry
- { hdsl2ShdslMibObjects 6 }
- { hdsl2Shdsl15MinIntervalTable 1 }
1.3.6.1.2.1.10.48.1.6
1.3.6.1.2.1.10.48.1.6.1
Table 134: hdsl2Shdsl15MinIntervalTable
Object
OID
Syntax
Access
Status
Supported
hdsl2Shdsl15MinIntervalNumber
{ hdsl2Shdsl15MinIntervalEntry 1 }
Unsigned32
(1…96)
not-accessible
current
Y
hdsl2Shdsl15MinIntervalES
{ hdsl2Shdsl15MinIntervalEntry 2 }
PerfIntervalCount
read-only
current
Y
hdsl2Shdsl15MinIntervalSES
{ hdsl2Shdsl15MinIntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
hdsl2Shdsl15MinIntervalCRCanomalies
{ hdsl2Shdsl15MinIntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
hdsl2Shdsl15MinIntervalLOSWS
{ hdsl2Shdsl15MinIntervalEntry 5 }
PerfIntervalCount
read-only
current
Y
hdsl2Shdsl15MinIntervalUAS
{ hdsl2Shdsl15MinIntervalEntry 6 }
PerfIntervalCount
read-only
current
Y
261
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.6.1.1
hdsl2Shdsl15MinIntervalNumber
Performance Data Interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2…96
are optional.
5.13.6.6.1.2
hdsl2Shdsl15MinIntervalES
Count of Errored Seconds (ES) during the interval.
5.13.6.6.1.3
hdsl2Shdsl15MinIntervalSES
Count of Severely Errored Seconds (SES) during the interval.
5.13.6.6.1.4
hdsl2Shdsl15MinIntervalCRCanomalies
Count of CRC anomalies, in units of detected CRC Anomalies, during the interval.
5.13.6.6.1.5
hdsl2Shdsl15MinIntervalLOSWS
Count of Loss of Sync Word (LOSW) Seconds during the interval.
5.13.6.6.1.6
hdsl2Shdsl15MinIntervalUAS
Count of Unavailable Seconds (UAS) during the interval.
5.13.6.7
Segment Endpoint 1-Day Interval Status/Performance Group
5.13.6.7.1
hdsl2Shdsl1DayIntervalTable
This table provides one row for each HDSL2/SHDSL endpoint performance data collection interval. This table
contains live data from equipment. As such, it is NOT persistent.
Index(es):
•
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex (Section 5.13.6.3.1.1, Page 255)
hdsl2ShdslEndpointSide (Section 5.13.6.4.1.1, Page 256)
hdsl2ShdslEndpointWirePair (Section 5.13.6.4.1.2, Page 256)
hdsl2Shdsl1DayIntervalNumber
OIDs:
•
•
hdsl2Shdsl1DayIntervalTable
hdsl2Shdsl1DayIntervalEntry
- { hdsl2ShdslMibObjects 7 }
- { hdsl2Shdsl1DayIntervalTable 1 }
262
1.3.6.1.2.1.10.48.1.7
1.3.6.1.2.1.10.48.1.7.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 135: hdsl2Shdsl1DayIntervalTable
Object
OID
Syntax
Access
Status
Supported
hdsl2Shdsl1DayIntervalNumber
{ hdsl2Shdsl1DayIntervalEntry 1 }
Unsigned32(1…30)
not-accessible
current
Y
hdsl2Shdsl1DayIntervalMoniSecs
{ hdsl2Shdsl1DayIntervalEntry 2 }
Hdsl2ShdslPerfTimeElapsed
read-only
current
Y
hdsl2Shdsl1DayIntervalES
{ hdsl2Shdsl1DayIntervalEntry 3 }
Hdsl2Shdsl1DayIntervalCount
read-only
current
Y
hdsl2Shdsl1DayIntervalSES
{ hdsl2Shdsl1DayIntervalEntry 4 }
Hdsl2Shdsl1DayIntervalCount
read-only
current
Y
hdsl2Shdsl1DayIntervalCRCanomalies
{ hdsl2Shdsl1DayIntervalEntry 5 }
Hdsl2Shdsl1DayIntervalCount
read-only
current
Y
hdsl2Shdsl1DayIntervalLOSWS
{ hdsl2Shdsl1DayIntervalEntry 6 }
Hdsl2Shdsl1DayIntervalCount
read-only
current
Y
hdsl2Shdsl1DayIntervalUAS
{ hdsl2Shdsl1DayIntervalEntry 7 }
Hdsl2Shdsl1DayIntervalCount
read-only
current
Y
5.13.6.7.1.1
hdsl2Shdsl1DayIntervalNumber
History Data Interval number. Interval 1 is the most recent previous day; interval 30 is 30 days ago. Intervals 2…30
are optional.
5.13.6.7.1.2
hdsl2Shdsl1DayIntervalMoniSecs
The amount of time in the 1-day interval over which the performance monitoring information is actually counted.
This value will be the same as the interval duration except in a situation where performance monitoring data could not
be collected for any reason.
5.13.6.7.1.3
hdsl2Shdsl1DayIntervalES
Count of Errored Seconds (ES) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs (Section
5.13.6.7.1.2, Page 263).
5.13.6.7.1.4
hdsl2Shdsl1DayIntervalSES
Count of Severely Errored Seconds (SES) during the 1-day interval as measured by
hdsl2Shdsl1DayIntervalMoniSecs (Section 5.13.6.7.1.2, Page 263).
5.13.6.7.1.5
hdsl2Shdsl1DayIntervalCRCanomalies
Count of CRC anomalies during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs (Section
5.13.6.7.1.2, Page 263).
5.13.6.7.1.6
hdsl2Shdsl1DayIntervalLOSWS
Count of Loss of Sync Word (LOSW) Seconds during the 1-day interval as measured by
263
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
hdsl2Shdsl1DayIntervalMoniSecs (Section 5.13.6.7.1.2, Page 263).
5.13.6.7.1.7
hdsl2Shdsl1DayIntervalUAS
Count of Unavailable Seconds (UAS) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs
(Section 5.13.6.7.1.2, Page 263).
5.13.6.8
Maintenance Group
5.13.6.8.1
hdsl2ShdslEndpointMaintTable
This table supports maintenance operations (e.g. loopbacks) to be performed on HDSL2/SHDSL segment endpoints.
This table contains live data from equipment. As such, it is NOT persistent. Each entry corresponds to a single
segment endpoint, and is indexed by the ifIndex (Section 5.3.4.3.1, Page 39) of the HDSL2/SHDSL line, the Unit Id
of the associated unit and the side of the unit.
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex (Section 5.13.6.3.1.1, Page 255)
hdsl2ShdslEndpointSide (Section 5.13.6.4.1.1, Page 256)
OIDs:
•
•
hdsl2ShdslEndpointMaintTable - { hdsl2ShdslMibObjects 8 }
hdsl2ShdslEndpointMaintEntry - { hdsl2ShdslEndpointMaintTable 1 }
1.3.6.1.2.1.10.48.1.8
1.3.6.1.2.1.10.48.1.8.1
Table 136: hdsl2ShdslEndpointMaintTable
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslMaintLoopbackConfig
{ hdsl2ShdslEndpointMaintEntry 1 }
INTEGER
noLoopback(1)
normalLoopback(2)
specialLoopback(3)
read-write
current
N
hdsl2ShdslMaintTipRingReversal
{ hdsl2ShdslEndpointMaintEntry 2 }
INTEGER
normal(1)
reversed(2)
read-only
current
Y
hdsl2ShdslMaintPowerBackOff
{ hdsl2ShdslEndpointMaintEntry 3 }
INTEGER
default(1)
enhanced(2)
read-write
current
Y
hdsl2ShdslMaintSoftRestart
{ hdsl2ShdslEndpointMaintEntry 4 }
INTEGER
ready(1)
restart(2)
read-write
current
Y
264
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.8.1.1
hdsl2ShdslMaintLoopbackConfig
This object controls configuration of loopbacks for the associated segment endpoint. The status of the loopback is
obtained via the hdsl2ShdslEndpointCurrStatus (Section 5.13.6.5.1.3, Page 259) object. The following values are
defined for this object:
•
•
•
noLoopback(1)
normalLoopback(2)
specialLoopback(3)
5.13.6.8.1.2
- This loopback only applies to the CPE endpoint and loops the data towards the
DTE attached to the endpoint.
hdsl2ShdslMaintTipRingReversal
This object indicates the state of the tip/ring pair at the associated segment endpoint. The following values are defined
for this object:
•
•
normal(1)
reversed(2)
5.13.6.8.1.3
hdsl2ShdslMaintPowerBackOff
This object configures the receiver at the associated segment endpoint to operate in default or enhanced power
backoff mode. The following values are defined for this object:
•
•
default(1)
enhanced(2)
5.13.6.8.1.4
hdsl2ShdslMaintSoftRestart
The following values are defined for this object:
•
•
ready(1)
restart(2)
This object enables the manager to trigger a soft restart of the modem at the associated segment endpoint. The
manager may only set this object to the “restart(2)” value, which initiates a restart. The agent will perform a restart
after approximately 5 seconds. Following the 5 second period, the agent will restore the object to the “ready(1)” state.
5.13.6.8.2
hdsl2ShdslUnitMaintTable
This table supports maintenance operations for units in a HDSL2/SHDSL line. Entries in this table MUST be
maintained in a persistent manner. Each entry corresponds to a single unit, and is indexed by the ifIndex (Section
5.3.4.3.1, Page 39) of the HDSL2/SHDSL line and the Unit Id of the associated unit.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
hdsl2ShdslInvIndex (Section 5.13.6.3.1.1, Page 255)
OIDs:
•
•
hdsl2ShdslUnitMaintTable
hdsl2ShdslUnitMaintEntry
- { hdsl2ShdslMibObjects 9 }
- { hdsl2ShdslUnitMaintTable 1 }
265
1.3.6.1.2.1.10.48.1.9
1.3.6.1.2.1.10.48.1.9.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 137: hdsl2ShdslUnitMaintTable
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslMaintLoopbackTimeout
{ hdsl2ShdslUnitMaintEntry 1 }
Integer32(0…4095)
read-write
current
N
hdsl2ShdslMaintUnitPowerSource
{ hdsl2ShdslUnitMaintEntry 2 }
INTEGER
local(1)
span(2)
read-only
current
Y
5.13.6.8.2.1
hdsl2ShdslMaintLoopbackTimeout
This object configures the timeout value, in minutes, for loopbacks initiated at segments endpoints contained in the
associated unit. A value of 0 disables the timeout.
5.13.6.8.2.2
hdsl2ShdslMaintUnitPowerSource
This object indicates the DC power source being used by the associated unit. The following values are defined for this
object:
•
•
local(1)
span(2)
5.13.6.9
Span Configuration Profile Group
5.13.6.9.1
hdsl2ShdslSpanConfProfileTable
This table supports definitions of span configuration profiles for SHDSL lines. HDSL2 does not support these
configuration options. This table MUST be maintained in a persistent manner.
Each entry corresponds to a single span configuration profile. Each profile contains a set of span configuration
parameters. The configuration parameters in a profile are applied to those lines referencing that profile (see the
hdsl2ShdslSpanConfProfile (Section 5.13.6.1.1.2, Page 252) object). Profiles may be created/deleted using the row
creation/deletion mechanism via hdsl2ShdslSpanConfProfileRowStatus (Section 5.13.6.9.1.16, Page 270). If an
active entry is referenced in hdsl2ShdslSpanConfProfile (Section 5.13.6.1.1.2, Page 252), the entry MUST remain
active until all references are removed.
Index(es):
•
hdsl2ShdslSpanConfProfileName IMPLIED
OIDs:
•
•
hdsl2ShdslSpanConfProfileTable - { hdsl2ShdslMibObjects 10 }
hdsl2ShdslSpanConfProfileEntry - { hdsl2ShdslSpanConfProfileTable 1 }
266
1.3.6.1.2.1.10.48.1.10
1.3.6.1.2.1.10.48.1.10.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 138: hdsl2ShdslSpanConfProfileTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslSpanConfProfileName
{ hdsl2ShdslSpanConfProfileEntry 1 }
SnmpAdminString
(SIZE(1…32))
not-accessible
current
Y
hdsl2ShdslSpanConfWireInterface
{ hdsl2ShdslSpanConfProfileEntry 2 }
INTEGER
twoWire(1)
fourWire(2)
read-create
current
Y
hdsl2ShdslSpanConfMinLineRate
{ hdsl2ShdslSpanConfProfileEntry 3 }
Unsigned32
(0…4112000)
read-create
current
Y
hdsl2ShdslSpanConfMaxLineRate
{ hdsl2ShdslSpanConfProfileEntry 4 }
Unsigned32
(0…4112000)
read-create
current
Y
hdsl2ShdslSpanConfPSD
{ hdsl2ShdslSpanConfProfileEntry 5 }
INTEGER
symmetric(1)
asymmetric(2)
read-create
current
Y
hdsl2ShdslSpanConfTransmissionMode
{ hdsl2ShdslSpanConfProfileEntry 6 }
Hdsl2ShdslTransmissionModeType
read-create
current
Y
hdsl2ShdslSpanConfRemoteEnabled
{ hdsl2ShdslSpanConfProfileEntry 7 }
INTEGER
enabled(1)
disabled(2)
read-create
current
Y
hdsl2ShdslSpanConfPowerFeeding
{ hdsl2ShdslSpanConfProfileEntry 8 }
INTEGER
noPower(1)
powerFeed(2)
wettingCurrent(3)
read-create
current
Y
hdsl2ShdslSpanConfCurrCondTargetMarginDown
{ hdsl2ShdslSpanConfProfileEntry 9 }
Integer32
(-10…21)
read-create
current
Y
hdsl2ShdslSpanConfWorstCaseTargetMarginDown
{ hdsl2ShdslSpanConfProfileEntry 10 }
Integer32
(-10…21)
read-create
current
Y
hdsl2ShdslSpanConfCurrCondTargetMarginUp
{ hdsl2ShdslSpanConfProfileEntry 11 }
Integer32
(-10…21)
read-create
current
Y
hdsl2ShdslSpanConfWorstCaseTargetMarginUp
{ hdsl2ShdslSpanConfProfileEntry 12 }
Integer32
(-10…21)
read-create
current
Y
hdsl2ShdslSpanConfUsedTargetMargins
{ hdsl2ShdslSpanConfProfileEntry 13 }
BITS
currCondDown(0)
worstCaseDown(1)
currCondUp(2)
worstCaseUp(3)
read-create
current
Y
267
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 138: hdsl2ShdslSpanConfProfileTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslSpanConfReferenceClock
{ hdsl2ShdslSpanConfProfileEntry 14 }
Hdsl2ShdslClockReferenceType
read-create
current
Y
hdsl2ShdslSpanConfLineProbeEnable
{ hdsl2ShdslSpanConfProfileEntry 15 }
INTEGER
disable(1)
enable(2)
read-create
current
Y
hdsl2ShdslSpanConfProfileRowStatus
{ hdsl2ShdslSpanConfProfileEntry 16 }
RowStatus
read-create
current
Y
5.13.6.9.1.1
hdsl2ShdslSpanConfProfileName
This object is the unique index associated with this profile. Entries in this table are referenced via the object
hdsl2ShdslSpanConfProfile (Section 5.13.6.1.1.2, Page 252) in hdsl2ShdslSpanConfTable (Section 5.13.6.1.1, Page
251).
5.13.6.9.1.2
hdsl2ShdslSpanConfWireInterface
This object configures the two-wire or optional four-wire operation for SHDSL Lines. The following values are
defined for this object:
•
•
twoWire(1) - Recommended default
fourWire(2)
5.13.6.9.1.3
hdsl2ShdslSpanConfMinLineRate
This object configures the minimum transmission rate, in bps, for the associated SHDSL Line in bits-per-second
(bps). If the minimum line rate equals the maximum line rate (hdsl2ShdslSpanMaxLineRate), the line rate is
considered “fixed.” If the minimum line rate is less than the maximum line rate, the line rate is considered “rateadaptive.
The recommended default value is 1552000.
5.13.6.9.1.4
hdsl2ShdslSpanConfMaxLineRate
This object configures the maximum transmission rate for the associated SHDSL Line in bits-per-second (bps). If the
minimum line rate equals the maximum line rate (hdsl2ShdslSpanMaxLineRate, the line rate is considered “fixed.” If
the minimum line rate is less than the maximum line rate, the line rate is considered “rate-adaptive.”
The recommended default value is 1552000.
5.13.6.9.1.5
hdsl2ShdslSpanConfPSD
This object configures use of symmetric/asymmetric PSD (Power Spectral Density) Mask for the associated SHDSL
Line. Support for symmetric PSD is mandatory for all supported data rates. Support for asymmetric PSD is optional.
The following values are defined for this object:
•
•
symmetric(1) - Recommended default
asymmetric(2)
268
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.9.1.6
hdsl2ShdslSpanConfTransmissionMode
This object specifies the regional setting for the SHDSL line.
The recommended default value is region1(0).
5.13.6.9.1.7
hdsl2ShdslSpanConfRemoteEnabled
This object enables/disables support for remote management of the units in a SHDSL line from the STU-R via the
EOC. The following values are defined for this object:
•
•
enabled(1) - Recommended default
disabled(2)
5.13.6.9.1.8
hdsl2ShdslSpanConfPowerFeeding
This object enables/disables support for optional power feeding in a SHDSL line. The following values are defined
for this object:
•
•
•
noPower(1) - Recommended default
powerFeed(2)
wettingCurrent(3)
5.13.6.9.1.9
hdsl2ShdslSpanConfCurrCondTargetMarginDown
This object specifies the downstream current condition target SNR margin, in dB, for a SHDSL line. The SNR margin
is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a
unit.
The recommended default value is 0.
5.13.6.9.1.10
hdsl2ShdslSpanConfWorstCaseTargetMarginDown
This object specifies the downstream worst case target SNR margin, in dB, for a SHDSL line. The SNR margin is the
difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
The recommended default value is 0.
5.13.6.9.1.11
hdsl2ShdslSpanConfCurrCondTargetMarginUp
This object specifies the upstream current condition target SNR margin, in dB for a SHDSL line. The SNR margin is
the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
The recommended default value is 0.
5.13.6.9.1.12
hdsl2ShdslSpanConfWorstCaseTargetmarginUp
This object specifies the upstream worst case target SNR margin, in dB, for a SHDSL line. The SNR margin is the
difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
The recommended default value is 0.
5.13.6.9.1.13
hdsl2ShdslSpanConfUsedTargetMargins
Contains indicates whether a target SNR margin is enabled or disabled. This is a bit-map of possible settings. The
various bit positions are:
•
currCondDown(0)
- current condition downstream target SNR margin enabled
Recommended default
269
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
•
•
•
worstCaseDown(1)
currCondUp(2)
worstCaseUp(3)
5.13.6.9.1.14
- worst case downstream target SNR margin enabled
- current condition upstream target SNR margin enabled
- worst case upstream target SNR margin enabled
hdsl2ShdslSpanConfReferenceClock
This object configures the clock reference for the STU-C in a SHDSL Line.
The recommended default value is localClk(1).
5.13.6.9.1.15
hdsl2ShdslSpanConfLineProbeEnable
This object enables/disables support for Line Probe of the units in a SHDSL line. When Line Probe is enabled, the
system performs Line Probing to find the best possible rate. If Line probe is disabled, the rate adaptation phase is
skipped to shorten set up time. The following values are defined for this object:
•
•
disable(1) - Recommended default
enable(2)
5.13.6.9.1.16
hdsl2ShdslSpanConfProfileRowStatus
This object controls creation/deletion of the associated entry in this table per the semantics of RowStatus (Section
4.11, Page 15). If an active entry is referenced in hdsl2ShdslSpanConfProfile (Section 5.13.6.1.1.2, Page 252), the
entry MUST remain active until all references are removed.
5.13.6.10 Segment Endpoint Alarm Configuration Profile group
5.13.6.10.1 hdsl2ShdslEndpointAlarmConfProfileTable
This table supports definitions of alarm configuration profiles for HDSL2/SHDSL segment endpoints. This table
MUST be maintained in a persistent manner.
Each entry corresponds to a single alarm configuration profile. Each profile contains a set of parameters for setting
alarm thresholds for various performance attributes monitored at HDSL2/SHDSL segment endpoints. Profiles may
be created/deleted using the row creation/deletion mechanism via hdsl2ShdslEndpointAlarmConfProfileRowStatus
(Section 5.13.6.10.1.9, Page 272). If an active entry is referenced in either hdsl2ShdslSpanConfAlarmProfile (Section
5.13.6.1.1.2, Page 252) or hdsl2ShdslEndpointAlarmConfProfile (Section 5.13.6.4.1.3, Page 257), the entry MUST
remain active until all references are removed.
The notifications defined in this table are for initialization failure and for the threshold crossings associated with the
following events: ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its own enable/threshold value.
When that value is 0, the notification is disabled.
Index(es):
•
hdsl2ShdslEndpointAlarmConfProfileName IMPLIED
OIDs:
•
hdsl2ShdslEndpointAlarmConfProfileTable
270
- { hdsl2ShdslMibObjects 11 }
1.3.6.1.2.1.10.48.1.11
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
•
hdsl2ShdslEndpointAlarmConfProfileEntry
- { hdsl2ShdslEndpointAlarmConfProfileTable 1 }
1.3.6.1.2.1.10.48.1.1.1
Table 139: hdsl2ShdslEndpointAlarmConfProfileTable
Object
OID
Syntax
Access
Status
Supported
hdsl2ShdslEndpointAlarmConfProfileName
{ hdsl2ShdslEndpointAlarmConfProfileEntry 1 }
SnmpAdminString
(SIZE(1…32))
notaccessible
current
Y
hdsl2ShdslEndpointThreshLoopAttenuation
{ hdsl2ShdslEndpointAlarmConfProfileEntry 2 }
Integer32
(-127…128)
readcreate
current
Y
hdsl2ShdslEndpointThreshSNRMargin
{ hdsl2ShdslEndpointAlarmConfProfileEntry 3 }
Integer32
(-127…128)
readcreate
current
Y
hdsl2ShdslEndpointThreshES
{ hdsl2ShdslEndpointAlarmConfProfileEntry 4 }
Hdsl2ShdslPerfIntervalThreshold
readcreate
current
Y
hdsl2ShdslEndpointThreshSES
{ hdsl2ShdslEndpointAlarmConfProfileEntry 5 }
Hdsl2ShdslPerfIntervalThreshold
readcreate
current
Y
hdsl2ShdslEndpointThreshCRCanomalies
{ hdsl2ShdslEndpointAlarmConfProfileEntry 6 }
Integer32
readcreate
current
Y
hdsl2ShdslEndpointThreshLOSWS
{ hdsl2ShdslEndpointAlarmConfProfileEntry 7 }
Hdsl2ShdslPerfIntervalThreshold
readcreate
current
Y
hdsl2ShdslEndpointThreshUAS
{ hdsl2ShdslEndpointAlarmConfProfileEntry 8 }
Hdsl2ShdslPerfIntervalThreshold
readcreate
current
Y
hdsl2ShdslEndpointAlarmConfProfileRowStatus
{ hdsl2ShdslEndpointAlarmConfProfileEntry 9 }
RowStatus
readcreate
current
Y
5.13.6.10.1.1
hdsl2ShdslEndpointAlarmConfProfileName
This object is the unique index associated with this profile.
5.13.6.10.1.2
hdsl2ShdslEndpointThreshLoopAttenuation
This object configures the loop attenuation, in dB, alarm threshold. When the current value of
hdsl2ShdslEndpointCurrAtn (Section 5.13.6.5.1.1, Page 259) reaches or exceeds this threshold, a
hdsl2ShdslLoopAttenCrossing (Section 5.13.7.1, Page 274) MAY be generated.
The recommended default is 0.
5.13.6.10.1.3
hdsl2ShdslEndpointThreshSNRMargin
This object configures the SNR margin, in dB, alarm threshold. When the current value of
hdsl2ShdslEndpointCurrSnrMgn (Section 5.13.6.5.1.2, Page 259) reaches or drops below this threshold, a
hdsl2ShdslSNRMarginCrossing (Section 5.13.7.2, Page 274) MAY be generated.
The recommended default value is 0.
271
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.6.10.1.4
hdsl2ShdslEndpointThreshES
This object configures the threshold for the number of errored seconds (ES) within any given 15-minute performance
data collection interval. If the value of errored seconds in a particular 15-minute collection interval reaches/ exceeds
this value, a hdsl2ShdslPerfESThresh (Section 5.13.7.3, Page 274) MAY be generated. At most one notification will
be sent per interval per endpoint.
The recommended default is 0.
5.13.6.10.1.5
hdsl2ShdslEndpointThreshSES
This object configures the threshold for the number of severely errored seconds (SES) within any given 15-minute
performance data collection interval. If the value of severely errored seconds in a particular 15-minute collection
interval reaches/exceeds this value, a hdsl2ShdslPerfSESThresh (Section 5.13.7.4, Page 274) MAY be generated. At
most one notification will be sent per interval per endpoint.
The recommended default is 0.
5.13.6.10.1.6
hdsl2ShdslEndpointThreshCRCanomalies
This object configures the threshold for the number of CRC anomalies, in units of detected CRC Anomalies, within
any given 15-minute performance data collection interval. If the value of CRC anomalies in a particular 15-minute
collection interval reaches/exceeds this value, a hdsl2ShdslPerfCRCanomaliesThresh (Section 5.13.7.5, Page 274)
MAY be generated. At most one notification will be sent per interval per endpoint.
The recommended default is 0.
5.13.6.10.1.7
hdsl2ShdslEndpointThreshLOSWS
This object configures the threshold for the number of Loss of Sync Word (LOSW) Seconds within any given 15minute performance data collection interval. If the value of LOSW in a particular 15-minute collection interval
reaches/exceeds this value, a hdsl2ShdslPerfLOSWSThresh (Section 5.13.7.6, Page 274) MAY be generated. At most
one notification will be sent per interval per endpoint.
The recommended default is 0.
5.13.6.10.1.8
hdsl2ShdslEndpointThreshUAS
This object configures the threshold for the number of unavailable seconds (UAS) within any given 15-minute
performance data collection interval. If the value of UAS in a particular 15-minute collection interval reaches/exceeds
this value, a hdsl2ShdslPerfUASThresh (Section 5.13.7.7, Page 274) MAY be generated. At most one notification
will be sent per interval per endpoint.
The recommended default is 0.
5.13.6.10.1.9
hdsl2ShdslEndpointAlarmConfProfileRowStatus
This object controls creation/deletion of the associated entry in this table as per the semantics of RowStatus (Section
4.11, Page 15). If an active entry is referenced in either hdsl2ShdslSpanConfAlarmProfile (Section 5.13.6.1.1.3, Page
252) or hdsl2ShdslEndpointAlarmConfProfile (Section 5.13.6.4.1.3, Page 257), the entry MUST remain active until
all references are removed.
272
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.7
Traps
This section identifies traps that are generated. Each threshold has its own enable/threshold value. When that value is
a 0, the notification is disabled. A threshold notification occurs whenever the corresponding current 15-minute
interval error counter becomes equal to, or exceeds the threshold value. One notification may be sent per interval per
interface. Since the current 15-minute counter is reset to 0 every 15 minutes, and if the condition persists, the
notification may recur as often as every 15 minutes.
OIDs:
•
hdsl2ShdslNotifications
- { hdsl2ShdslMib 0 }
1.3.6.1.2.1.10.48.0
Table 140: HDSL2-SHDSL-LINE-MIB Traps
Notification
OID
Variable Bindings / Objects
Status
Supported
hdsl2ShdslLoopAttenCrossing
{ hdsl2ShdslNotifications 1 }
hdsl2ShdslEndpointCurrAtn
hdsl2ShdslEndpointThreshLoopAttenuation
current
Y
hdsl2ShdslSNRMarginCrossing
{ hdsl2ShdslNotifications 2 }
hdsl2ShdslEndpointCurrSnrMgn
hdsl2ShdslEndpointThreshSNRMargin
current
Y
hdsl2ShdslPerfESThresh
{ hdsl2ShdslNotifications 3 }
hdsl2ShdslEndpointCurr15MinES
hdsl2ShdslEndpointThreshES
current
Y
hdsl2ShdslPerfSESThresh
{ hdsl2ShdslNotifications 4 }
hdsl2ShdslEndpointCurr15MinSES
hdsl2ShdslEndpointThreshSES
current
Y
hdsl2ShdslPerfCRCanomaliesThresh
{ hdsl2ShdslNotifications 5 }
hdsl2ShdslEndpointCurr15MinCRCanomalies
hdsl2ShdslEndpointThreshCRCanomalies
current
Y
hdsl2ShdslPerfLOSWSThresh
{ hdsl2ShdslNotifications 6 }
hdsl2ShdslEndpointCurr15MinLOSWS
hdsl2ShdslEndpointThreshLOSWS
current
Y
hdsl2ShdslPerfUASThresh
{ hdsl2ShdslNotifications 7 }
hdsl2ShdslEndpointCurr15MinUAS
hdsl2ShdslEndpointThreshUAS
current
Y
hdsl2ShdslSpanInvalidNumRepeaters
{ hdsl2ShdslNotifications 8 }
hdsl2ShdslSpanConfNumRepeaters
hdsl2ShdslStatusNumAvailRepeaters
current
Y
hdsl2ShdslLoopbackFailure
{ hdsl2ShdslNotifications 9 }
hdsl2ShdslMaintLoopbackConfig
current
Y
hdsl2ShdslpowerBackoff
{ hdsl2ShdslNotifications 10 }
hdsl2ShdslEndpointCurrStatus
current
Y
hdsl2ShdsldeviceFault
{ hdsl2ShdslNotifications 11 }
hdsl2ShdslEndpointCurrStatus
current
Y
hdsl2ShdsldcContinuityFault
{ hdsl2ShdslNotifications 12 }
hdsl2ShdslEndpointCurrStatus
current
Y
hdsl2ShdslconfigInitFailure
{ hdsl2ShdslNotifications 13 }
hdsl2ShdslEndpointCurrStatus
current
Y
hdsl2ShdslprotocolInitFailure
{ hdsl2ShdslNotifications 14 }
hdsl2ShdslEndpointCurrStatus
current
Y
hdsl2ShdslnoNeighborPresent
{ hdsl2ShdslNotifications 15 }
hdsl2ShdslEndpointCurrStatus
current
Y
hdsl2ShdslLocalPowerLoss
{ hdsl2ShdslNotifications 16 }
hdsl2ShdslInvVendorID
current
Y
273
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.7.1
hdsl2ShdslLoopAttenCrossing
This notification indicates that the loop attenuation threshold (as per the hdsl2ShdslEndpointThreshLoopAttenuation
[Section 5.13.6.10.1.2, Page 271] value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
5.13.7.2
hdsl2ShdslSNRMarginCrossing
This notification indicates that the SNR margin threshold (as per the hdsl2ShdslEndpointThreshSNRMargin [Section
5.13.6.10.1.3, Page 271] value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
5.13.7.3
hdsl2ShdslPerfESThresh
This notification indicates that the errored seconds threshold (as per the hdsl2ShdslEndpointThreshES [Section
5.13.6.10.1.4, Page 272] value) has been reached/ exceeded for the HDSL2/SHDSL segment endpoint.
5.13.7.4
hdsl2ShdslPerfSESThresh
This notification indicates that the severely errored seconds threshold (as per the hdsl2ShdslEndpointThreshSES
[Section 5.13.6.10.1.5, Page 272] value) has been reached/exceeded for the HDSL2/SHDSL Segment Endpoint.
5.13.7.5
hdsl2ShdslPerfCRCanomaliesThresh
This notification indicates that the CRC anomalies threshold (as per the hdsl2ShdslEndpointThreshCRCanomalies
[Section 5.13.6.10.1.6, Page 272] value) has been reached/exceeded for the HDSL2/SHDSL Segment Endpoint.
5.13.7.6
hdsl2ShdslPerfLOSWSThresh
This notification indicates that the LOSW seconds threshold (as per the hdsl2ShdslEndpointThreshLOSWS [Section
5.13.6.10.1.7, Page 272] value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
5.13.7.7
hdsl2ShdslPerfUASThresh
This notification indicates that the unavailable seconds threshold (as per the hdsl2ShdslEndpointThreshUAS [Section
5.13.6.10.1.8, Page 272] value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
5.13.7.8
hdsl2ShdslSpanInvalidNumRepeaters
This notification indicates that a mismatch has been detected between the number of repeater/regenerator units
configured for a HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters [Section 5.13.6.1.1.1, Page 252]
object and the actual number of repeater/regenerator units discovered via the EOC.
A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated following completion of the discovery phase if
the number of repeaters discovered on the line differs from the number of repeaters
specified in hdsl2ShdslSpanConfNumRepeaters. For those conditions where the number of provisioned repeaters is
greater than those encountered during span discovery, all table entries associated with the nonexistent repeaters are to
be discarded. For those conditions where the number of provisioned repeaters is less than those encountered during
span discovery, additional table entries are to be created using the default span configuration profile.
5.13.7.9
hdsl2ShdslLoopbackFailure
This notification indicates that an endpoint maintenance loopback command failed for an HDSL2/SHDSL segment.
5.13.7.10 hdsl2ShdslpowerBackoff
This notification indicates that the bit setting for powerBackoff in the hdsl2ShdslEndpointCurrStatus [Section
5.13.6.5.1.3, Page 259] object for this endpoint has changed.
274
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.7.11 hdsl2ShdsldeviceFault
This notification indicates that the bit setting for deviceFault in the hdsl2ShdslEndpointCurrStatus [Section
5.13.6.5.1.3, Page 259] object for this endpoint has changed.
5.13.7.12 hdsl2ShdsldcContinuityFault
This notification indicates that the bit setting for dcContinuityFault in the hdsl2ShdslEndpointCurrStatus [Section
5.13.6.5.1.3, Page 259] object for this endpoint has changed.
5.13.7.13 hdsl2ShdslconfigInitFailure
This notification indicates that the bit setting for configInitFailure in the hdsl2ShdslEndpointCurrStatus [Section
5.13.6.5.1.3, Page 259] object for this endpoint has changed.
5.13.7.14 hdsl2ShdslprotocolInitFailure
This notification indicates that the bit setting for protocolInitFailure in the hdsl2ShdslEndpointCurrStatus [Section
5.13.6.5.1.3, Page 259] object for this endpoint has changed.
5.13.7.15 hdsl2ShdslnoNeighborPresent
This notification indicates that the bit setting for noNeighborPresent in the hdsl2ShdslEndpointCurrStatus [Section
5.13.6.5.1.3, Page 259] object for this endpoint has changed.
5.13.7.16 hdsl2ShdslLocalPowerLoss
This notification indicates impending unit failure due to loss of local power (last gasp).
275
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.8
5.13.8.1
Conformance Information
Compliance
The section outlines compliance requirements for this MIB.
The following groups are mandatory:
•
•
•
•
•
•
•
•
•
•
hdsl2ShdslSpanConfGroup
hdsl2ShdslSpanStatusGroup
hdsl2ShdslInventoryGroup
hdsl2ShdslEndpointConfGroup
hdsl2ShdslEndpointCurrGroup
hdsl2Shdsl15MinIntervalGroup
hdsl2Shdsl1DayIntervalGroup
hdsl2ShdslMaintenanceGroup
hdsl2ShdslEndpointAlarmConfGroup
hdsl2ShdslNotificationGroup
The following groups are optional:
•
•
•
hdsl2ShdslInventoryShdslGroup
- Support for this group is only required for implementations supporting SHDSL lines.
hdsl2ShdslSpanShdslStatusGroup - Support for this group is only required for implementations supporting SHDSL lines.
hdsl2ShdslSpanConfProfileGroup - Support for this group is only required for implementations supporting SHDSL lines.
276
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
5.13.8.2
Conformance
Table 141: HDSL2-SDLS-LINE-MIB Conformance (1 of 5)
Group
Description
Objects
Supported
hdsl2ShdslSpanConfGroup
This group supports objects for
configuring span related parameters for HDSL2/SHDSL lines.
hdsl2ShdslSpanConfNumRepeaters
Y
hdsl2ShdslSpanConfProfile
Y
hdsl2ShdslSpanConfAlarmProfile
Y
hdsl2ShdslSpanStatusGroup
This group supports objects for
retrieving span related status
for HDSL2/SHDSL lines.
hdsl2ShdslStatusNumAvailRepeaters
Y
hdsl2ShdslInventoryShdslGroup
This group supports objects for
retrieving SHDSL-specific
inventory information.
hdsl2ShdslInvTransmissionModeCapability
Y
hdsl2ShdslSpanShdslStatusGroup
This group supports objects for
retrieving SHDSL-specific
span related status.
hdsl2ShdslStatusMaxAttainableLineRate
Y
hdsl2ShdslInventoryGroup
hdsl2ShdslEndpointConfGroup
This group supports objects
that provide unit inventory
information about the units in
HDSL2/SHDSL lines.
This group supports objects for
configuring parameters for segment endpoints in HDSL2/
SHDSL lines.
277
hdsl2ShdslStatusActualLineRate
hdsl2ShdslStatusTransmissionModeCurrent
Y
hdsl2ShdslInvVendorID
Y
hdsl2ShdslInvVendorModelNumber
Y
hdsl2ShdslInvVendorSerialNumber
Y
hdsl2ShdslInvVendorEOCSoftwareVersion
Y
hdsl2ShdslInvStandardVersion
Y
hdsl2ShdslInvVendorListNumber
Y
hdsl2ShdslInvVendorIssueNumber
Y
hdsl2ShdslInvVendorSoftwareVersion
Y
hdsl2ShdslInvEquipmentCode
Y
hdsl2ShdslInvVendorOther
Y
hdsl2ShdslEndpointCurrAtn
Y
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 141: HDSL2-SDLS-LINE-MIB Conformance (2 of 5)
Group
Description
Objects
Supported
hdsl2ShdslEndpointCurrGroup
This group supports objects
which provide current status
and performance measurements
relating to segment endpoints
in HDSL2/SHDSL lines.
hdsl2ShdslEndpointCurrAtn
Y
hdsl2ShdslEndpointCurrSnrMgn
Y
hdsl2ShdslEndpointCurrStatus
Y
hdsl2ShdslEndpointES
Y
hdsl2ShdslEndpointSES
Y
hdsl2ShdslEndpointCRCanomalies
Y
hdsl2ShdslEndpointLOSWS
Y
hdsl2ShdslEndpointUAS
Y
hdsl2ShdslEndpointCurr15MinTimeElapsed
Y
hdsl2ShdslEndpointCurr15MinES
Y
hdsl2ShdslEndpointCurr15MinSES
Y
hdsl2ShdslEndpointCurr15MinCRCanomalies
Y
hdsl2ShdslEndpointCurr15MinLOSWS
Y
hdsl2ShdslEndpointCurr15MinUAS
Y
hdsl2ShdslEndpointCurr1DayTimeElapsed
Y
hdsl2ShdslEndpointCurr1DayES
Y
hdsl2ShdslEndpointCurr1DaySES
Y
hdsl2ShdslEndpointCurr1DayCRCanomalies
Y
hdsl2ShdslEndpointCurr1DayLOSWS
Y
hdsl2ShdslEndpointCurr1DayUAS
Y
hdsl2Shdsl15MinIntervalES
Y
hdsl2Shdsl15MinIntervalSES
Y
hdsl2Shdsl15MinIntervalCRCanomalies
Y
hdsl2Shdsl15MinIntervalLOSWS
Y
hdsl2Shdsl15MinIntervalUAS
Y
hdsl2Shdsl15MinIntervalGroup
This group supports objects
which maintain historic performance measurements relating
to segment endpoints in
HDSL2/SHDSL lines in 15minute intervals.
278
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 141: HDSL2-SDLS-LINE-MIB Conformance (3 of 5)
Group
Description
Objects
Supported
hdsl2Shdsl1DayIntervalGroup
This group supports objects
which maintain historic performance measurements relating
to segment endpoints in
HDSL2/SHDSL lines in 1-day
intervals.
hdsl2Shdsl1DayIntervalMoniSecs
Y
hdsl2Shdsl1DayIntervalES
Y
hdsl2Shdsl1DayIntervalSES
Y
hdsl2Shdsl1DayIntervalCRCanomalies
Y
hdsl2Shdsl1DayIntervalLOSWS
Y
hdsl2Shdsl1DayIntervalUAS
Y
hdsl2ShdslMaintLoopbackConfig
Y
hdsl2ShdslMaintTipRingReversal
Y
hdsl2ShdslMaintPowerBackOff
Y
hdsl2ShdslMaintSoftRestart
Y
hdsl2ShdslMaintLoopbackTimeout
Y
hdsl2ShdslMaintUnitPowerSource
Y
hdsl2ShdslEndpointAlarmConfProfile
Y
hdsl2ShdslEndpointThreshLoopAttenuation
Y
hdsl2ShdslEndpointThreshSNRMargin
Y
hdsl2ShdslEndpointThreshES
Y
hdsl2ShdslEndpointThreshSES
Y
hdsl2ShdslEndpointThreshCRCanomalies
Y
hdsl2ShdslEndpointThreshLOSWS
Y
hdsl2ShdslEndpointThreshUAS
Y
hdsl2ShdslEndpointAlarmConfProfileRowStatus
Y
hdsl2ShdslMaintenanceGroup
hdsl2ShdslEndpointAlarmConfGroup
This group supports objects
that provide support for maintenance actions for HDSL2/
SHDSL lines.
This group supports objects
that allow configuration of
alarm thresholds for various
performance parameters for
HDSL2/SHDSL lines.
279
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 141: HDSL2-SDLS-LINE-MIB Conformance (4 of 5)
Group
Description
Objects
Supported
hdsl2ShdslNotificationGroup
This group supports notifications of significant conditions
associated with HDSL2/
SHDSL lines.
hdsl2ShdslLoopAttenCrossing
Y
hdsl2ShdslSNRMarginCrossing
Y
hdsl2ShdslPerfESThresh
Y
hdsl2ShdslPerfSESThresh
Y
hdsl2ShdslPerfCRCanomaliesThresh
Y
hdsl2ShdslPerfLOSWSThresh
Y
hdsl2ShdslPerfUASThresh
Y
hdsl2ShdslSpanInvalidNumRepeaters
Y
hdsl2ShdslLoopbackFailure
Y
hdsl2ShdslpowerBackoff
Y
hdsl2ShdsldeviceFault
Y
hdsl2ShdsldcContinuityFault
Y
hdsl2ShdslconfigInitFailure
Y
hdsl2ShdslprotocolInitFailure
Y
hdsl2ShdslnoNeighborPresent
Y
hdsl2ShdslLocalPowerLoss
Y
280
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
HDSL2-SHDSL-LINE-MIB — RFC 3276
Table 141: HDSL2-SDLS-LINE-MIB Conformance (5 of 5)
Group
Description
Objects
Supported
hdsl2ShdslSpanConfProfileGroup
This group supports objects
that constitute configuration
profiles for configuring span
related parameters in SHDSL
lines.
hdsl2ShdslSpanConfWireInterface
Y
hdsl2ShdslSpanConfMinLineRate
Y
hdsl2ShdslSpanConfMaxLineRate
Y
hdsl2ShdslSpanConfPSD
Y
hdsl2ShdslSpanConfTransmissionMode
Y
hdsl2ShdslSpanConfRemoteEnabled
Y
hdsl2ShdslSpanConfPowerFeeding
Y
hdsl2ShdslSpanConfCurrCondTargetMarginDown
Y
hdsl2ShdslSpanConfWorstCaseTargetMarginDown
Y
hdsl2ShdslSpanConfCurrCondTargetMarginUp
Y
hdsl2ShdslSpanConfWorstCaseTargetMarginUp
Y
hdsl2ShdslSpanConfUsedTargetMargins
Y
hdsl2ShdslSpanConfReferenceClock
Y
hdsl2ShdslSpanConfLineProbeEnable
Y
hdsl2ShdslSpanConfProfileRowStatus
Y
281
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14 DS1-MIB — RFC 2495
5.14.1
Introduction
The MIB module to describe DS1, E1, DS2, and E2 interfaces objects. The RFC used as a reference was dated January 1999.
5.14.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.14.3
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
ds1
ds1Traps
5.14.4
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 18 }
{ ds1 15 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.18
1.3.6.1.2.1.10.18.15
Table 142: DS1-MIB Objects (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dsx1ConfigTable
{ ds1 6 }
SEQUENCE of
dsx1ConfigEntry
not-accessible
current
Y
dsx1CurrentTable
{ ds1 7 }
SEQUENCE of
dsx1CurrentEntry
not-accessible
current
Y
dsx1IntervalTable
{ ds1 8 }
SEQUENCE of
dsx1IntervalEntry
not-accessible
current
Y
dsx1TotalTable
{ ds1 9 }
SEQUENCE of
dsx1TotalEntry
not-accessible
current
Y
dsx1FarEndCurrentTable
{ ds1 10 }
SEQUENCE of
dsx1FarEndCurrentEntry
not-accessible
current
Ya
dsx1FarEndIntervalTable
{ ds1 11 }
SEQUENCE of
dsx1FarEndIntervalEntry
not-accessible
current
Ya
dsx1FarEndTotalTable
{ ds1 12 }
SEQUENCE of
dsx1FarEndTotalEntry
not-accessible
current
Ya
dsx1FracTable
{ ds1 13 }
SEQUENCE of
dsx1FracEntry
not-accessible
current
N
ds1Traps
{ ds1 15 }
OID
N/A
N/A
Y
282
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 142: DS1-MIB Objects (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dsx1ChanMappingTable
{ ds1 16 }
SEQUENCE of
dsx1ChanMappingEntry
not-accessible
current
Y
a. Supported only in T1 Models. A noSuchName will be returned when any of the table’s objects are
accessed in E1 models.
5.14.4.1
dsx1ConfigTable
The DS1 Configuration table.
Index(es):
•
dsx1LineIndex
OIDs:
•
•
dsx1ConfigTable
dsx1ConfigEntry
- { ds1 6 }
- { dsx1ConfigTable 1 }
1.3.6.1.2.1.10.18.6
1.3.6.1.2.1.10.18.6.1
Table 143: dsx1ConfigTable (1 of 3)
Object
OID
Syntax
Access
Status
Supported
dsx1LineIndex
{ dsx1ConfigEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1IfIndex
{ dsx1ConfigEntry 2 }
InterfaceIndex
read-only
deprecated
N
dsx1TimeElapsed
{ dsx1ConfigEntry 3 }
INTEGER(0…899)
read-only
current
Y
dsx1ValidIntervals
{ dsx1ConfigEntry 4 }
INTEGER(0…96)
read-only
current
Y
dsx1LineType
{ dsx1ConfigEntry 5 }
INTEGER
other(1)
dsx1ESF(2)
dsx1D4(3)
dsx1E1(4)
dsx1E1CRC(5)
dsx1E1MF(6)
dsx1E1CRCMF(7)
dsx1Unframed(8)
dsx1E1Unframed(9)
dsx1DS2M12(10)
dsx2E2(11)
read-write
current
Y
283
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 143: dsx1ConfigTable (2 of 3)
Object
OID
Syntax
Access
Status
Supported
dsx1LineCoding
{ dsx1ConfigEntry 6 }
INTEGER
dsx1JBZS(1)
dsx1B8ZS(2)
dsx1HDB3(3)
dsx1ZBTSI(4)
dsx1AMI(5)
other(6)
dsx1B6ZS(7)
read-write
current
Y
dsx1SendCode
{ dsx1ConfigEntry 7 }
INTEGER
dsx1SendNoCode(1)
dsx1SendLineCode(2)
dsx1SendPayloadCode(3)
dsx1SendResetCode(4)
dsx1SendQRS(5)
dsx1Send511Pattern(6)
dsx1Send3in24Pattern(7)
dsx1SendOtherTestPattern(8)
read-write
current
Y
dsx1CircuitIdentifier
{ dsx1ConfigEntry 8 }
DisplayString
(SIZE(0…255))
read-write
current
Y
dsx1LoopbackConfig
{ dsx1ConfigEntry 9 }
INTEGER
dsx1NoLoop(1)
dsx1PayloadLoop(2)
dsx1LineLoop(3)
dsx1OtherLoop(4)
dsx1InwardLoop(5)
dsx1DualLoop(6)
read-write
current
Y
dsx1LineStatus
{ dsx1ConfigEntry 10 }
INTEGER(1…131071)
read-only
current
Y
dsx1SignalMode
{ dsx1ConfigEntry 11 }
INTEGER
none(1)
robbedBit(2)
bitOriented(3)
messageOriented(4)
other(5)
read-write
current
Y
dsx1TransmitClockSource
{ dsx1ConfigEntry 12 }
INTEGER
loopTiming(1)
localTiming(2)
throughTiming(3)
read-write
current
Y
dsx1Fdl
{ dsx1ConfigEntry 13 }
INTEGER(1…15)
read-write
current
Y
dsx1InvalidIntervals
{ dsx1ConfigEntry 14 }
INTEGER (0…96)
read-only
current
Y
dsx1LineLengtha
{ dsx1ConfigEntry 15 }
INTEGER(0…64000)
read-onlyb
current
Y
dsx1LineStatusLastChange
{ dsx1ConfigEntry 16 }
TimeStamp
read-only
current
Y
dsx1LineStatusChangeTrapEnable
{ dsx1ConfigEntry 17 }
INTEGER
enabled(1)
disabled(2)
read-write
current
Y
284
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 143: dsx1ConfigTable (3 of 3)
Object
OID
Syntax
Access
Status
Supported
dsx1LoopbackStatus
{ dsx1ConfigEntry 18 }
INTEGER(1…127)
read-only
current
Y
dsx1Ds1ChannelNumber
{ dsx1ConfigEntry 19 }
INTEGER(0…28)
read-only
current
N
dsx1Channelization
{ dsx1ConfigEntry 20 }
INTEGER
disabled(1)
enabledDs0(2)
enabledDs1(3)
read-onlyb
current
Y
a. See pdnDs1ExtConfTable (Section 5.38.4.1, Page 587).
b. Product imposed restriction.
5.14.4.1.1
dsx1LineIndex
This object should be made equal to ifIndex. The next paragraph describes its previous usage. Making the object
equal to ifIndex allows proper use of ifStackTable and ds0/ds0bundle mibs.
Previously, this object is the identifier of a DS1 Interface on a managed device. If there is an ifEntry that is directly
associated with this and only this DS1 interface, it should have the same value as ifIndex. Otherwise, number the
dsx1LineIndices with an unique identifier following the rules of choosing a number that is greater than ifNumber and
numbering the inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g, network side)
with odd numbers.
5.14.4.1.2
dsx1IfIndex
This value for this object is equal to the value of ifIndex from the Interfaces table of MIB II (RFC 1213).
5.14.4.1.3
dsx1TimeElapsed
The number of seconds that have elapsed since the beginning of the near end current error-measurement period. If, for
some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum
value, the agent will return the maximum value.
5.14.4.1.4
dsx1ValidIntervals
The number of previous near end intervals for which data was collected. The value will be 96 unless the interface was
brought online within the last 24 hours, in which case the value will be the number of complete 15 minute near end
intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals
are unavailable. In this case, this interval is the maximum interval number for which data is available.
5.14.4.1.5
dsx1LineType
This variable indicates the variety of DS1 Line implementing this circuit. The type of circuit affects the number of
bits per second that the circuit can reasonably carry, as well as the interpretation of the usage and error statistics. The
following values are defined for this object:
285
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 144: dsx1LineType
Supported
other(1)
N
dsx1ESF(2)
Extended SuperFrame DS1 (T1.107)
Y
dsx1D4(3)
AT&T D4 format DS1 (T1.107)
N
dsx1E1(4)
ITU-T Recommendation G.704 (Table 4a)
Y
dsx1E1CRC(5)
ITU-T Recommendation G.704 (Table 4b)
Y
dsx1E1MF(6)
G.704 (Table 4a) with TS16 multiframing enabled
N
dsx1E1CRCMF(7)
G.704 (Table 4b) with TS16 multiframing enabled
N
dsx1Unframed(8)
DS1 with No Framing
N
dsx1E1Unframed(9)
E1 with No Framing (G.703)
N
dsx1DS2M12(10)
DS2 frame format (T1.107)
N
dsx2E2(11)
E2 frame format (G.704)
N
For clarification, the capacity for each E1 type is as listed below:
•
•
•
dsx1E1Unframed
dsx1E1 or dsx1E1CRC
dsx1E1MF or dsx1E1CRCMF
- E1, no framing = 32 x 64k = 2048k
- E1, with framing, no signalling = 31 x 64k = 1984k
- E1, with framing, signalling = 30 x 64k = 1920k
Valid Object Value(s)
•
•
•
dsx1ESF(2)
dsx1E1(3)
dsx1E1CRC(5)
5.14.4.1.6
- T1 models only
- E1 models only
- E1 models only
dsx1LineCoding
This variable describes the variety of Zero Code Suppression used on this interface, which in turn affects a number of
its characteristics. The following values are defined for this object:
286
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 145: dsx1LineCoding
Supported
dsx1JBZS(1)
dsx1JBZS refers the Jammed Bit Zero Suppression, in which the AT&T
specification of at least one pulse every 8 bit periods is literally implemented by forcing a pulse in bit 8 of each channel. Thus, only seven
bits per channel, or 1.344 Mbps, is available for data.
N
dsx1B8ZS(2)
dsx1B8ZS refers to the use of a specified pattern of normal bits and
bipolar violations which are used to replace a sequence of eight zero
bits.
Y
dsx1HDB3(3)
E1 links, with or without CRC may use this line code.
Y
dsx1ZBTSI(4)
ANSI Clear Channels may use dsx1ZBTSI, or Zero Byte Time Slot
Interchange.
N
dsx1AMI(5)
dsx1AMI refers to a mode wherein no zero code suppression is present
and the line encoding does not solve the problem directly. In this application, the higher layer must provide data which meets or exceeds the
pulse density requirements, such as inverting HDLC data. E1 links,
with or without CRC may use this line code.
N
other(6)
N
dsx1B6ZS(7)
dsx1B6ZS refers to the user of a specified pattern of normal bits and
bipolar violations which are used to replace a sequence of six zero bits.
Used for DS2.
N
Valid Object Value(s)
•
•
dsx1B8ZS(2)
dsx2HDB3(2)
5.14.4.1.7
- T1 models only
- E1 models only
dsx1SendCode
This variable indicates what type of code is being sent across the DS1 interface by the device. Setting this variable
causes the interface to send the code requested. The following values are defined for this object:
Table 146: dsx1SendCode (1 of 2)
Supported
dsx1SendNoCode(1)
sending looped or normal data
Y
dsx1SendLineCode(2)
sending a request for a line loopback
Y (T1 models only)
dsx1SendPayloadCode(3)
sending a request for a payload loopback
Y (T1 models only)
287
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 146: dsx1SendCode (2 of 2)
Supported
dsx1SendResetCode(4)
sending a loopback termination request
Y (T1 models only)
dsx1SendQRS(5)
sending a Quasi-Random Signal (QRS) test pattern
Y
dsx1Send511Pattern(6)
sending a 511 bit fixed test pattern
N
dsx1Send3in24Pattern(7)
sending a fixed test pattern of 3 bits set in 24
N
sending a test pattern other than those described by
this object
dsx1SendOtherTestPattern(8)
5.14.4.1.8
This value is not supported on a write operation. On
a read operation, this value indicates that a test pattern described by devDS1TestType, Section
5.37.4.1.2, Page 581.
Y
dsx1CircuitIdentifier
This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting.
5.14.4.1.9
dsx1LoopbackConfig
This variable represents the desired loopback configuration of the DS1 interface. Agents supporting read/write access
should return inconsistentValue in response to a requested loopback state that the interface does not support. The following values are defined for this object:
Table 147: dsx1LoopbackConfig
Supported
dsx1NoLoop(1)
Not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as
its value.
Y
dsx1PayloadLoop(2)
The received signal at this interface is looped through the
device. Typically the received signal is looped back for retransmission after it has passed through the device's framing function.
Y
dsx1LineLoop(3)
The received signal at this interface does not go through the
device (minimum penetration) but is looped back out.
Y
dsx1OtherLoop(4)
Loopbacks that are not defined here.
N
dsx1InwardLoop(5)
The transmitted signal at this interface is looped back and
received by the same interface. What is transmitted onto the line
is product dependent.
N
dsx1DualLoop(6)
Both dsx1LineLoop and dsx1InwardLoop will be active simultaneously.
N
288
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.1.10 dsx1LineStatus
This variable indicates the Line Status of the interface. It contains loopback, failure, received “alarm” and transmitted
“alarms” information.
The dsx1LineStatus is a bit map represented as a sum, therefore, it can represent multiple failures (alarms) and a
LoopbackState simultaneously.
dsx1NoAlarm must be set if and only if no other flag is set.
If the dsx1loopbackState bit is set, the loopback in effect can be determined from the dsx1loopbackConfig object.
The various bit positions are:
Table 148: dsx1LineStatus
Supported
1
dsx1NoAlarm
No Alarm Present
Y
2
dsx1RcvFarEndLOF
Far end LOF (a.k.a., Yellow Alarm)
Y
4
dsx1XmtFarEndLOF
Near end sending LOF Indication
Y
8
dsx1RcvAIS
Far end sending AIS
Y
16
dsx1XmtAIS
Near end sending AIS
Y
32
dsx1LossOfFrame
Near end LOF (a.k.a., Red Alarm)
Y
64
dsx1LossOfSignal
Near end Loss Of Signal
Y
128
dsx1LoopbackState
Near end is looped
Y
256
dsx1T16AIS
E1 TS16 AIS
Y
512
dsx1RcvFarEndLOMF
Far End Sending TS16 LOMF
Y
1024
dsx1XmtFarEndLOMF
Near End Sending TS16 LOMF
Y
2048
dsx1RcvTestCode
Near End detects a test code
Y
4096
dsx1OtherFailure
any line status not defined here
Y
8192
dsx1UnavailSigState
Near End in Unavailable Signal State
Y
16384
dsx1NetEquipOOS
Carrier Equipment Out of Service
Y
32768
dsx1RcvPayloadAIS
DS2 Payload AIS
N
65536
dsx1Ds2PerfThreshold
DS2 Performance Threshold Exceeded
N
289
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.1.11 dsx1SignalMode
The following values are defined for this object:
Table 149: dsx1SignalMode
Supported
none(1)
indicates that no bits are reserved for signaling on this channel
Y
robbedBit(2)
indicates that DS1 Robbed Bit Signaling is in use
N
bitOriented(3)
indicates that E1 Channel Associated Signaling is in use
N
messageOriented(4)
indicates that Common Channel Signaling is in use either on
channel 16 of an E1 link or channel 24 of a DS1
N
other (5)
N
Valid Object Value(s)
A write operation to this object is not supported. Upon a read, this value returned by this object is indicated by the
Supported column in the table above.
5.14.4.1.12 dsx1TransmitClockSource
The source of Transmit Clock. The following values are defined for this object:
Table 150: dsx1TransmitClockSource
Supported
loopTiming(1)
indicates that the recovered receive clock is used as the transmit
clock
Y
localTiming(2)
indicates that a local clock source is used or when an external
clock is attached to the box containing the interface
Y
throughTiming(3)
indicates that recovered receive clock from another interface is
used as the transmit clock
N
5.14.4.1.13 dsx1Fdl
This bitmap describes the use of the facilities data link, and is the sum of the capabilities. Set any bits that are appropriate:
290
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 151: dsx1Fdl
Supported
other(1)
indicates that a protocol other than one following is used
N
dsx1AnsiT1403(2)
refers to the FDL exchange recommended by ANSI
Y (T1 models only)
dsx1Att54016(4)
refers to ESF FDL exchanges
Y
dsx1FdlNone(8)
indicates that the device does not use the FDL
Y (E1 models only)
Valid Object Value(s)
A write operation to this object is not supported. Upon a read, this value returned by this object is indicated by the
Supported column in the table above.
5.14.4.1.14 dsx1InvalidIntervals
The number of intervals in the range from 0 to dsx1ValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
5.14.4.1.15 dsx1LineLength
The length of the ds1 line in meters. This objects provides information for line build out circuitry. This object is only
useful if the interface has configurable line build out circuitry.
Valid Object Value(s)
•
0
This object is not used to configure the length of a line. A 0 is always returned. Please refer to the
pdnDs1ExtConfTable (Section 5.38.4.1, Page 587) to configure the length of the link.
5.14.4.1.16 dsx1LineStatusLastChange
The value of MIB II's sysUpTime object at the time this DS1 entered its current line status state. If the current state
was entered prior to the last re-initialization of the proxy-agent, then this object contains a zero value.
5.14.4.1.17 dsx1LineStatusChangeTrapEnable
Indicates whether dsx1LineStatusChange traps should be generated for this interface. The following values are
defined for this object:
•
•
enabled(1)
disabled(2)
The MIB recommended default value is disabled(2).
5.14.4.1.18 dsx1LoopbackStatus
This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks established by a manager and remotely from the far end.
The dsx1LoopbackStatus is a bit map represented as a sum, therefore is can represent multiple loopbacks simultaneously.
291
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
The various bit positions are:
Table 152: dsx1LoopbackStatus
Supported
1
dsx1NoLoopback
Y
2
dsx1NearEndPayloadLoopback
Y
4
dsx1NearEndLineLoopback
Y
8
dsx1NearEndOtherLoopback
N
16
dsx1NearEndInwardLoopback
N
32
dsx1FarEndPayloadLoopback
Y
64
dsx1FarEndLineLoopback
Y
5.14.4.1.19 dsx1Ds1ChannelNumber
This variable represents the channel number of the DS1/E1 on its parent Ds2/E2 or DS3/E3. A value of 0 indicated
this DS1/E1 does not have a parent DS3/E3.
Valid Object Value(s)
•
0
5.14.4.1.20 dsx1Channelization
Indicates whether this ds1/e1 is channelized or unchannelized. The following values are defined for this object:
•
•
•
disabled(1)
enabledDs0(2)
enabledDs1(3)
- indicates that this is a DS1 channelized into DS0s
- indicated that this is a DS2 channelized into DS1s
Setting this value will cause the creation or deletion of entries in the ifTable for the DS0s that are within the DS1.
Valid Object Value(s)
This object has its access restricted to read-only and returns disabled(1).
5.14.4.2
dsx1CurrentTable
The DS1 current table contains various statistics being collected for the current 15 minute interval.
Index(es):
•
dsx1CurrentIndex
OIDs:
•
•
dsx1CurrentTable - { ds1 7 }
dsx1CurrentEntry - { dsx1CurrentTable 1 }
292
1.3.6.1.2.1.10.18.7
1.3.6.1.2.1.10.18.7.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 153: dsx1CurrentTable
Object
OID
Syntax
Access
Status
Supported
dsx1CurrentIndex
{ dsx1CurrentEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1CurrentESs
{ dsx1CurrentEntry 2 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentSESs
{ dsx1CurrentEntry 3 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentSEFSs
{ dsx1CurrentEntry 4 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentUASs
{ dsx1CurrentEntry 5 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentCSSs
{ dsx1CurrentEntry 6 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentPCVs
{ dsx1CurrentEntry 7 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentLESs
{ dsx1CurrentEntry 8 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentBESs
{ dsx1CurrentEntry 9 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentDMs
{ dsx1CurrentEntry 10 }
PerfCurrentCount
read-only
current
Y
dsx1CurrentLCVs
{ dsx1CurrentEntry 11 }
PerfCurrentCount
read-only
current
Y
5.14.4.2.1
dsx1CurrentIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable. The interface identified
by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object
instance.
5.14.4.2.2
dsx1CurrentESs
The number of Errored Seconds.
5.14.4.2.3
dsx1CurrentSESs
The number of Severely Errored Seconds.
5.14.4.2.4
dsx1CurrentSEFSs
The number of Severely Errored Framing Seconds.
5.14.4.2.5
dsx1CurrentUASs
The number of Unavailable Seconds.
5.14.4.2.6
dsx1CurrentCSSs
The number of Controlled Slip Seconds.
5.14.4.2.7
dsx1CurrentPCVs
The number of Path Coding Violations.
293
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.2.8
dsx1CurrentLESs
The number of Line Errored Seconds.
5.14.4.2.9
dsx1CurrentBESs
The number of Bursty Errored Seconds.
5.14.4.2.10 dsx1CurrentDMs
The number of Degraded Minutes.
5.14.4.2.11 dsx1CurrentLCVs
The number of Line Code Violations (LCVs).
5.14.4.3
dsx1IntervalTable
The DS1 Interval Table contains various statistics collected by each DS1 Interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15 minute intervals. Each row in this table represents one such
interval (identified by dsx1IntervalNumber) for one specific instance (identified by dsx1IntervalIndex).
Index(es):
•
•
dsx1IntervalIndex
dsx1IntervalNumber
OIDs:
•
•
dsx1IntervalTable - { ds1 8 }
dsx1IntervalEntry - { dsx1IntervalTable 1 }
1.3.6.1.2.1.10.18.8
1.3.6.1.2.1.10.18.8.1
Table 154: dsx1IntervalTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dsx1IntervalIndex
{ dsx1IntervalEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1IntervalNumber
{ dsx1IntervalEntry 2 }
INTEGER(1…96)
read-only
current
Y
dsx1IntervalESs
{ dsx1IntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalSESs
{ dsx1IntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalSEFSs
{ dsx1IntervalEntry 5 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalUASs
{ dsx1IntervalEntry 6 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalCSSs
{ dsx1IntervalEntry 7 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalPCVs
{ dsx1IntervalEntry 8 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalLESs
{ dsx1IntervalEntry 9 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalBESs
{ dsx1IntervalEntry 10 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalDMs
{ dsx1IntervalEntry 11 }
PerfIntervalCount
read-only
current
Y
dsx1IntervalLCVs
{ dsx1IntervalEntry 12 }
PerfIntervalCount
read-only
current
Y
294
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 154: dsx1IntervalTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dsx1IntervalValidData
{ dsx1IntervalEntry 13 }
TruthValue
read-only
current
Y
5.14.4.3.1
dsx1IntervalIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable. The interface identified
by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object
instance.
5.14.4.3.2
dsx1IntervalNumber
A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes
interval completed 23 hours and 45 minutes prior to interval 1.
5.14.4.3.3
dsx1IntervalESs
The number of Errored Seconds.
5.14.4.3.4
dsx1IntervalSESs
The number of Severely Errored Seconds.
5.14.4.3.5
dsx1IntervalSEFSs
The number of Severely Errored Framing Seconds.
5.14.4.3.6
dsx1IntervalUASs
The number of Unavailable Seconds. This object may decrease if the occurrence of unavailable seconds occurs across
an interval boundary.
5.14.4.3.7
dsx1IntervalCSSs
The number of Controlled Slip Seconds.
5.14.4.3.8
dsx1IntervalPCVs
The number of Path Coding Violations.
5.14.4.3.9
dsx1IntervalLESs
The number of Line Errored Seconds.
5.14.4.3.10 dsx1IntervalBESs
The number of Bursty Errored Seconds.
5.14.4.3.11 dsx1IntervalDMs
The number of Degraded Minutes.
5.14.4.3.12 dsx1IntervalLCVs
The number of Line Code Violations.
295
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.3.13 dsx1IntervalValidData
This variable indicates if the data for this interval is valid.
5.14.4.4
dsx1TotalTable
The DS1 Total Table contains the cumulative sum of the various statistics for the 24 hour period preceding the current
interval.
Index(es):
•
dsx1TotalIndex
OIDs:
•
•
dsx1TotalTable
dsx1TotalEntry
- { ds1 9 }
- { dsx1TotalTable 1 }
1.3.6.1.2.1.10.18.9
1.3.6.1.2.1.10.18.9.1
Table 155: dsx1TotalTable
Object
OID
Syntax
Access
Status
Supported
dsx1TotalIndex
{ dsx1TotalEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1TotalESs
{ dsx1TotalEntry 2 }
PerfTotalCount
read-only
current
Y
dsx1TotalSESs
{ dsx1TotalEntry 3 }
PerfTotalCount
read-only
current
Y
dsx1TotalSEFSs
{ dsx1TotalEntry 4 }
PerfTotalCount
read-only
current
Y
dsx1TotalUASs
{ dsx1TotalEntry 5 }
PerfTotalCount
read-only
current
Y
dsx1TotalCSSs
{ dsx1TotalEntry 6 }
PerfTotalCount
read-only
current
Y
dsx1TotalPCVs
{ dsx1TotalEntry 7 }
PerfTotalCount
read-only
current
Y
dsx1TotalLESs
{ dsx1TotalEntry 8 }
PerfTotalCount
read-only
current
Y
dsx1TotalBESs
{ dsx1TotalEntry 9 }
PerfTotalCount
read-only
current
Y
dsx1TotalDMs
{ dsx1TotalEntry 10 }
PerfTotalCount
read-only
current
Y
dsx1TotalLCVs
{ dsx1TotalEntry 11 }
PerfTotalCount
read-only
current
Y
5.14.4.4.1
dsx1TotalIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable. The interface identified
by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object
instance.
5.14.4.4.2
dsx1TotalESs
The sum of Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
296
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.4.3
dsx1TotalSESs
The number of Severely Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.4.4
dsx1TotalSEFSs
The number of Severely Errored Framing Seconds encountered by a DS1 interface in the previous 24 hour interval.
Invalid 15 minute intervals count as 0.
5.14.4.4.5
dsx1TotalUASs
The number of Unavailable Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.4.6
dsx1TotalCSSs
The number of Controlled Slip Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.4.7
dsx1TotalPCVs
The number of Path Coding Violations encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.4.8
dsx1TotalLESs
The number of Line Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.4.9
dsx1TotalBESs
The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the previous 24 hour interval.
Invalid 15 minute intervals count as 0.
5.14.4.4.10 dsx1TotalDMs
The number of Degraded Minutes (DMs) encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.4.11 dsx1TotalLCVs
The number of Line Code Violations (LCVs) encountered by a DS1 interface in the current 15 minute interval.
Invalid 15 minute intervals count as 0.
5.14.4.5
dsx1FarEndCurrentTable
The DS1 Far End Current table contains various statistics being collected for the current 15 minute interval. The statistics are collected from the far end messages on the Facilities Data Link. The definitions are the same as described
for the near-end information.
Note: This table only applies for T1 models.
Index(es):
•
dsx1FarEndCurrentIndex
297
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
OIDs:
•
•
dsx1FarEndCurrentTable
dsx1FarEndCurrentEntry
- { ds1 10 }
- { dsx1FarEndCurrentTable 1 }
1.3.6.1.2.1.10.18.10
1.3.6.1.2.1.10.18.10.1
Table 156: dsx1FarEndCurrentTable
Object
OID
Syntax
Access
Status
Supported
dsx1FarEndCurrentIndex
{ dsx1FarEndCurrentEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1FarEndTimeElapsed
{ dsx1FarEndCurrentEntry 2 }
INTEGER(0…899)
read-only
current
Y
dsx1FarEndValidIntervals
{ dsx1FarEndCurrentEntry 3 }
INTEGER(0…96)
read-only
current
Y
dsx1FarEndCurrentESs
{ dsx1FarEndCurrentEntry 4 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentSESs
{ dsx1FarEndCurrentEntry 5 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentSEFSs
{ dsx1FarEndCurrentEntry 6 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentUASs
{ dsx1FarEndCurrentEntry 7 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentCSSs
{ dsx1FarEndCurrentEntry 8 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentLESs
{ dsx1FarEndCurrentEntry 9 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentPCVs
{ dsx1FarEndCurrentEntry 10 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentBESs
{ dsx1FarEndCurrentEntry 11 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndCurrentDMs
{ dsx1FarEndCurrentEntry 12 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndInvalidIntervals
{ dsx1FarEndCurrentEntry 13 }
INTEGER(0…96)
read-only
current
Y
5.14.4.5.1
dsx1FarEndCurrentIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable. The interface identified
by a particular value of this index is identical to the interface identified by the same value of dsx1LineIndex.
5.14.4.5.2
dsx1FarEndTimeElapsed
The number of seconds that have elapsed since the beginning of the far end current error-measurement period. If, for
some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum
value, the agent will return the maximum value.
5.14.4.5.3
dsx1FarEndValidIntervals
The number of previous far end intervals for which data was collected. The value will be 96 unless the interface was
brought online within the last 24 hours, in which case the value will be the number of complete 15 minute far end
intervals since the interface has been online.
5.14.4.5.4
dsx1FarEndCurrentESs
The number of Far End Errored Seconds.
298
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.5.5
dsx1FarEndCurrentSESs
The number of Far End Severely Errored Seconds.
5.14.4.5.6
dsx1FarEndCurrentSEFSs
The number of Far End Severely Errored Framing Seconds.
5.14.4.5.7
dsx1FarEndCurrentUASs
The number of Unavailable Seconds.
5.14.4.5.8
dsx1FarEndCurrentCSSs
The number of Far End Controlled Slip Seconds.
5.14.4.5.9
dsx1FarEndCurrentLESs
The number of Far End Line Errored Seconds.
5.14.4.5.10 dsx1FarEndCurrentPCVs
The number of Far End Path Coding Violations.
5.14.4.5.11 dsx1FarEndCurrentBESs
The number of Far End Bursty Errored Seconds.
5.14.4.5.12 dsx1FarEndCurrentDMs
The number of Far End Degraded Minutes.
5.14.4.5.13 dsx1FarEndInvalidIntervals
The number of intervals in the range from 0 to dsx1FarEndValidIntervals for which no data is available. This object
will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
5.14.4.6
dsx1FarEndIntervalTable
The DS1 Far End Interval Table contains various statistics collected by each DS1 interface over the previous 24 hours
of operation. The past 24 hours are broken into 96 completed 15 minute intervals. Each row in this table represents
one such interval (identified by dsx1FarEndIntervalNumber) for one specific instance (identified by
dsx1FarEndIntervalIndex).
Note: This table only applies for T1 models.
Index(es):
•
•
dsx1FarEndIntervalIndex
dsx1FarEndIntervalNumber
OIDs:
•
•
dsx1FarEndIntervalTable
dsx1FarEndIntervalEntry
- { ds1 11 }
- { dsx1FarEndIntervalTable 1 }
299
1.3.6.1.2.1.10.18.11
1.3.6.1.2.1.10.18.11.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 157: dsx1FarEndIntervalTable
Object
OID
Syntax
Access
Status
Supported
dsx1FarEndIntervalIndex
{ dsx1FarEndIntervalEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1FarEndIntervalNumber
{ dsx1FarEndIntervalEntry 2 }
INTEGER(1…96)
read-only
current
Y
dsx1FarEndIntervalESs
{ dsx1FarEndIntervalEntry 3 }
PerfIntervalCount
read-only
current
Y
dsx1FarEndIntervalSESs
{ dsx1FarEndIntervalEntry 4 }
PerfIntervalCount
read-only
current
Y
dsx1FarEndIntervalSEFSs
{ dsx1FarEndIntervalEntry 5 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalUASs
{ dsx1FarEndIntervalEntry 6 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalCSSs
{ dsx1FarEndIntervalEntry 7 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalLESs
{ dsx1FarEndIntervalEntry 8 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalPCVs
{ dsx1FarEndIntervalEntry 9 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalBESs
{ dsx1FarEndIntervalEntry 10 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalDMs
{ dsx1FarEndIntervalEntry 11 }
PerfCurrentCount
read-only
current
Y
dsx1FarEndIntervalValidData
{ dsx1FarEndIntervalEntry 12 }
TruthValue
read-only
current
Y
5.14.4.6.1
dsx1FarEndIntervalIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable. The interface identified
by a particular value of this index is identical to the interface identified by the same value of dsx1LineIndex.
5.14.4.6.2
dsx1FarEndIntervalNumber
A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes
interval completed 23 hours and 45 minutes prior to interval 1.
5.14.4.6.3
dsx1FarEndIntervalESs
The number of Far End Errored Seconds.
5.14.4.6.4
dsx1FarEndIntervalSESs
The number of Far End Severely Errored Seconds.
5.14.4.6.5
dsx1FarEndIntervalSEFSs
The number of Far End Severely Errored Framing Seconds.
5.14.4.6.6
dsx1FarEndIntervalUASs
The number of Unavailable Seconds.
300
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.6.7
dsx1FarEndIntervalCSSs
The number of Far End Controlled Slip Seconds.
5.14.4.6.8
dsx1FarEndIntervalLESs
The number of Far End Line Errored Seconds.
5.14.4.6.9
dsx1FarEndIntervalPCVs
The number of Far End Path Coding Violations.
5.14.4.6.10 dsx1FarEndIntervalBESs
The number of Far End Bursty Errored Seconds.
5.14.4.6.11 dsx1FarEndIntervalDMs
The number of Far End Degraded Minutes.
5.14.4.6.12 dsx1FarEndIntervalValidData
This variable indicates if the data for this interval is valid.
5.14.4.7
dsx1FarEndTotalTable
The DS1 Far End Total Table contains the cumulative sum of the various statistics for the 24 hour period preceding
the current interval.
Index(es):
•
dsx1FarEndTotalIndex
OIDs:
•
•
dsx1FarEndTotalTable
dsx1FarEndTotalEntry
- { ds1 12 }
- { dsx1FarEndTotalTable 1 }
1.3.6.1.2.1.10.18.12
1.3.6.1.2.1.10.18.12.1
Table 158: dsx1FarEndTotalTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dsx1FarEndTotalIndex
{ dsx1FarEndTotalEntry 1 }
InterfaceIndex
read-only
current
Y
dsx1FarEndTotalESs
{ dsx1FarEndTotalEntry 2 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalSESs
{ dsx1FarEndTotalEntry 3 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalSEFSs
{ dsx1FarEndTotalEntry 4 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalUASs
{ dsx1FarEndTotalEntry 5 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalCSSs
{ dsx1FarEndTotalEntry 6 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalLESs
{ dsx1FarEndTotalEntry 7 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalPCVs
{ dsx1FarEndTotalEntry 8 }
PerfTotalCount
read-only
current
Y
dsx1FarEndTotalBESs
{ dsx1FarEndTotalEntry 9 }
PerfTotalCount
read-only
current
Y
301
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 158: dsx1FarEndTotalTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dsx1FarEndTotalDMs
{ dsx1FarEndTotalEntry 10 }
PerfTotalCount
read-only
current
Y
5.14.4.7.1
dsx1FarEndTotalIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable. The interface identified
by a particular value of this index is identical to the interface identified by the same value of dsx1LineIndex.
5.14.4.7.2
dsx1FarEndTotalESs
The number of Far End Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.7.3
dsx1FarEndTotalSESs
The number of Far End Severely Errored Seconds encountered by a DS1 interface in the previous 24 hour interval.
Invalid 15 minute intervals count as 0.
5.14.4.7.4
dsx1FarEndTotalSEFSs
The number of Far End Severely Errored Framing Seconds encountered by a DS1 interface in the previous 24 hour
interval. Invalid 15 minute intervals count as 0.
5.14.4.7.5
dsx1FarEndTotalUASs
The number of Unavailable Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
5.14.4.7.6
dsx1FarEndTotalCSSs
The number of Far End Controlled Slip Seconds encountered by a DS1 interface in the previous 24 hour interval.
Invalid 15 minute intervals count as 0.
5.14.4.7.7
dsx1FarEndTotalLESs
The number of Far End Line Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid
15 minute intervals count as 0.
5.14.4.7.8
dsx1FarEndTotalPCVs
The number of Far End Path Coding Violations reported via the far end block error count encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
5.14.4.7.9
dsx1FarEndTotalBESs
The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the previous 24 hour interval.
Invalid 15 minute intervals count as 0.
5.14.4.7.10 dsx1FarEndTotalDMs
The number of Degraded Minutes (DMs) encountered by a DS1 interface in the previous 24 hour interval. Invalid 15
minute intervals count as 0.
302
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.4.8
dsx1FracTable
This table is deprecated in favour of using ifStackTable. The table was mandatory for systems dividing a DS1 into
channels containing different data streams that are of local interest. Systems which are indifferent to data content,
such as CSUs, need not implement it.
The DS1 fractional table identifies which DS1 channels associated with a CSU are being used to support a logical
interface, i.e., an entry in the interfaces table from the Internet-standard MIB.
For example, consider an application managing a North American ISDN Primary Rate link whose division is a 384
kbit/s H1 _B_ Channel for Video, a second H1 for data to a primary routing peer, and 12 64 kbit/s H0 _B_ Channels.
Consider that some subset of the H0 channels are used for voice and the remainder are available for dynamic data
calls.
We count a total of 14 interfaces multiplexed onto the DS1 interface. Six DS1 channels (for the sake of the example,
channels 1…6) are used for Video, six more (7…11 and 13) are used for data, and the remaining 12 are in channels
12 and 14…24.
Let us further imagine that ifIndex 2 is of type DS1 and refers to the DS1 interface, and that the interfaces layered
onto it are numbered 3…16.
We might describe the allocation of channels, in the dsx1FracTable, as follows:
•
dsx1FracIfIndex.2. 1 = 3
•
dsx1FracIfIndex.2.13 = 4
•
dsx1FracIfIndex.2. 2 = 3
•
dsx1FracIfIndex.2.14 = 6
•
dsx1FracIfIndex.2. 3 = 3
•
dsx1FracIfIndex.2.15 = 7
•
dsx1FracIfIndex.2. 4 = 3
•
dsx1FracIfIndex.2.16 = 8
•
dsx1FracIfIndex.2. 5 = 3
•
dsx1FracIfIndex.2.17 = 9
•
dsx1FracIfIndex.2. 6 = 3
•
dsx1FracIfIndex.2.18 = 10
•
dsx1FracIfIndex.2. 7 = 4
•
dsx1FracIfIndex.2.19 = 11
•
dsx1FracIfIndex.2. 8 = 4
•
dsx1FracIfIndex.2.20 = 12
•
dsx1FracIfIndex.2. 9 = 4
•
dsx1FracIfIndex.2.21 = 13
•
dsx1FracIfIndex.2. 10 = 4
•
dsx1FracIfIndex.2.22 = 14
•
dsx1FracIfIndex.2. 11 = 4
•
dsx1FracIfIndex.2.23 = 615
•
dsx1FracIfIndex.2. 12 = 5
•
dsx1FracIfIndex.2.24 = 16
For North American (DS1) interfaces, there are 24 legal channels, numbered 1 through 24.
For G.704 interfaces, there are 31 legal channels, numbered 1 through 31. The channels (1…31) correspond directly
to the equivalently numbered time-slots.
303
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Index(es):
•
•
dsx1FracIndex
dsx1FracNumber
OIDs:
•
•
dsx1FracTable
dsx1FracEntry
- { ds1 13 }
- { dsx1FracTable 1 }
1.3.6.1.2.1.10.18.13
1.3.6.1.2.1.10.18.13.1
Table 159: dsx1FracTableTable
Object
OID
Syntax
Access
Status
Supported
dsx1FracIndex
{ dsx1FracEntry 1 }
INTEGER(1…0x7FFFFFFF)
read-only
depreciated
N
dsx1FracNumber
{ dsx1FracEntry 2 }
INTEGER(1…31)
read-only
depreciated
N
dsx1FracIfIndex
{ dsx1FracEntry 3 }
INTEGER(1…0x7FFFFFFF)
read-write
depreciated
N
5.14.4.8.1
dsx1FracIndex
The index value which uniquely identifies the DS1 interface to which this entry is applicable The interface identified
by a particular value of this index is the same interface as identified by the same value an dsx1LineIndex object
instance.
5.14.4.8.2
dsx1FracNumber
The channel number for this entry.
5.14.4.8.3
dsx1FracIfIndex
An index value that uniquely identifies an interface. The interface identified by a particular value of this index is the
same interface as identified by the same value an ifIndex object instance. If no interface is currently using a channel,
the value should be zero. If a single interface occupies more than one time slot, that ifIndex value will be found in
multiple time slots.
5.14.4.9
dsx1ChanMappingTable
The DS1 Channel Mapping table. This table maps a DS1 channel number on a particular DS3 into an ifIndex. In the
presence of DS2s, this table can be used to map a DS2 channel number on a DS3 into an ifIndex, or used to map a
DS1 channel number on a DS2 onto an ifIndex.
There is an entry in this table corresponding to each ds1 ifEntry within any interface that is channelized to the individual ds1 ifEntry level.
This table is intended to facilitate mapping from channelized interface / channel number to DS1 ifEntry. (e.g. mapping (DS3 ifIndex, DS1 Channel Number) -> ifIndex)
While this table provides information that can also be found in the ifStackTable and dsx1ConfigTable, it provides this
same information with a single table lookup, rather than by walking the ifStackTable to find the various constituent
ds1 ifTable entries, and testing various dsx1ConfigTable entries to check for the entry with the applicable DS1 channel number.
304
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
dsx1Ds1ChannelNumber
OIDs:
•
•
dsx1ChanMappingTable - { ds1 16 }
dsx1ChanMappingEntry - { dsx1ChanMappingTable 1 }
1.3.6.1.2.1.10.18.16
1.3.6.1.2.1.10.18.16.1
Table 160: dsx1ChanMappingTable
Object
OID
Syntax
Access
Status
Supported
dsx1ChanMappedIfIndex
{ dsx1ChanMappingEntry 1 }
InterfaceIndex
read-only
current
Y
5.14.4.9.1
dsx1ChanMappedIfIndex
This object indicates the ifIndex value assigned by the agent for the individual ds1 ifEntry that corresponds to the
given DS1 channel number (specified by the INDEX element dsx1Ds1ChannelNumber) of the given channelized
interface (specified by INDEX element ifIndex).
5.14.5
Traps
OIDs
•
ds1Traps
- { ds1 15 }
1.3.6.1.2.1.10.18.15
Table 161: DS1-MIB Traps
Object
OID
Trap Objects
Status
Supported
dsx1LineStatusChange
{ dslTraps 1 }
dsx1LineStatus
dsx1LineStatusLastChange
current
Y
5.14.5.1
dsx1LineStatusChange
A dsx1LineStatusChange trap is sent when the value of an instance dsx1LineStatus changes. It can be utilized by an
NMS to trigger polls. When the line status change results from a higher level line status change (i.e. ds3), then no
traps for the ds1 are sent.
305
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.6
Conformance Information
5.14.6.1
Compliance
The section outlines compliance requirements for this MIB.
5.14.6.1.1
ds1Compliance
Compliance statement for T1 and E1 interfaces.
The following groups are mandatory:
•
ds1NearEndConfigGroup
•
ds1NearEndStatisticsGroup
- A collection of objects providing configuration information applicable to all DS1 interfaces.
- A collection of objects providing statistics information applicable to
all DS1 interfaces.
The following groups are optional:
•
•
•
•
•
ds1FarEndGroup
- Implementation of this group is optional for all systems that attach to
a DS1 Interface.
ds1NearEndOptionalConfigGroup - Implementation of this group is optional for all systems that attach to
a DS1 Interface.
ds1DS2Group
- Implementation of this group is optional for all systems that attach to
a DS2 Interface.
ds1TransStatsGroup
- This group is the set of statistics appropriate for all systems which
attach to a DS1 Interface running transparent or unFramed lineType.
ds1ChanMappingGroup
- This group is the set of objects for mapping a DS3 Channel
(ds1ChannelNumber) to ifIndex. Implementation of this group is
mandatory for systems which support the channelization of DS3s into
DS1s.
5.14.6.1.2
ds1MibT1PriCompliance
Compliance statements for using this MIB for IDSN Primary Rate interfaces on T1 lines.
The MIB is not supported in this fashion so there is not compliance statement.
5.14.6.1.3
ds1MibE1PriCompliance
Compliance statements for using this MIB for IDSN Primary Rate interfaces on E1 lines.
The MIB is not supported in this fashion so there is not compliance statement.
5.14.6.1.4
ds1Ds2Compliance
Compliance statement for using this MIB for DS2 interfaces.
The MIB is not supported in this fashion so there is not compliance statement.
306
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
5.14.6.2
Conformance
Table 162: DS1-MIB Conformance (1 of 6)
Group
Description
Objects
Supported
ds1NearEndConfigGroup
A collection of objects providing configuration information
applicable to all DS1 interfaces.
dsx1LineIndex
Y
dsx1TimeElapsed
Y
dsx1ValidIntervals
Y
dsx1LineType
Y
dsx1LineCoding
Y
dsx1SendCode
Y
dsx1CircuitIdentifier
Y
dsx1LoopbackConfig
Y
dsx1LineStatus
Y
dsx1SignalMode
Y
dsx1TransmitClockSource
Y
dsx1Fdl
Y
dsx1InvalidIntervals
Y
dsx1LineLength
Y
dsx1LoopbackStatus
Y
dsx1Ds1ChannelNumber
Y
dsx1Channelization
Y
307
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 162: DS1-MIB Conformance (2 of 6)
Group
Description
Objects
Supported
ds1NearEndStatisticsGroup
A collection of objects providing statistics information applicable to all DS1 interfaces.
dsx1CurrentIndex
Y
dsx1CurrentESs
Y
dsx1CurrentSESs
Y
dsx1CurrentSEFSs
Y
dsx1CurrentUASs
Y
dsx1CurrentCSSs
Y
dsx1CurrentPCVs
Y
dsx1CurrentLESs
Y
dsx1CurrentBESs
Y
dsx1CurrentDMs
Y
dsx1CurrentLCVs
Y
dsx1IntervalIndex
Y
dsx1IntervalNumber
Y
dsx1IntervalESs
Y
dsx1IntervalSESs
Y
dsx1IntervalSEFSs
Y
dsx1IntervalUASs
Y
dsx1IntervalCSSs
Y
dsx1IntervalPCVs
Y
dsx1IntervalLESs
Y
dsx1IntervalBESs
Y
dsx1IntervalDMs
Y
dsx1IntervalLCVs
Y
dsx1IntervalValidData
Y
dsx1TotalIndex
Y
dsx1TotalESs
Y
dsx1TotalSESs
Y
dsx1TotalSEFSs
Y
308
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 162: DS1-MIB Conformance (3 of 6)
Group
Description
Objects
Supported
(ds1NearEndStatisticsGroup—Continued)
(Group continued)
dsx1TotalUASs
Y
dsx1TotalCSSs
Y
dsx1TotalPCVs
Y
dsx1TotalLESs
Y
dsx1TotalBESs
Y
dsx1TotalDMs
Y
dsx1TotalLCVs
Y
309
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 162: DS1-MIB Conformance (4 of 6)
Group
Description
Objects
Supported
ds1FarEndGroup
A collection of objects providing remote configuration and
statistics information.
dsx1FarEndCurrentIndex
Y
dsx1FarEndTimeElapsed
Y
dsx1FarEndValidIntervals
Y
dsx1FarEndCurrentESs
Y
dsx1FarEndCurrentSESs
Y
dsx1FarEndCurrentSEFSs
Y
dsx1FarEndCurrentUASs
Y
dsx1FarEndCurrentCSSs
Y
dsx1FarEndCurrentLESs
Y
dsx1FarEndCurrentPCVs
Y
dsx1FarEndCurrentBESs
Y
dsx1FarEndCurrentDMs
Y
dsx1FarEndInvalidIntervals
Y
dsx1FarEndIntervalIndex
Y
dsx1FarEndIntervalNumber
Y
dsx1FarEndIntervalESs
Y
dsx1FarEndIntervalSESs
Y
dsx1FarEndIntervalSEFSs
Y
dsx1FarEndIntervalUASs
Y
dsx1FarEndIntervalCSSs
Y
dsx1FarEndIntervalLESs
Y
dsx1FarEndIntervalPCVs
Y
dsx1FarEndIntervalBESs
Y
dsx1FarEndIntervalDMs
Y
dsx1FarEndIntervalValidData
Y
dsx1FarEndTotalIndex
Y
310
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 162: DS1-MIB Conformance (5 of 6)
Group
Description
Objects
Supported
(ds1FarEndGroup—Continued)
(Group continued)
dsx1FarEndTotalESs
Y
dsx1FarEndTotalSESs
Y
dsx1FarEndTotalSEFSs
Y
dsx1FarEndTotalUASs
Y
dsx1FarEndTotalCSSs
Y
dsx1FarEndTotalLESs
Y
dsx1FarEndTotalPCVs
Y
dsx1FarEndTotalBESs
Y
dsx1FarEndTotalDMs
Y
A collection of objects that
may be implemented on DS1
and DS2 interfaces.
dsx1LineStatusLastChange
Y
dsx1LineStatusChangeTrapEnable
Y
A collection of objects providing information about DS2
(6,312 kbps) and E2 (8,448
kbps)
dsx1LineIndex
Y
dsx1LineType
Y
dsx1LineCoding
Y
ds1NearEndOptionalConfigGroup
ds1DS2Group
dsx1SendCode
ds1TransStatsGroup
ds1NearEndOptionalTrapGroup
A collection of objects which
are the statistics which can be
collected from a ds1 interface
that is running transparent or
unframed lineType. Statistics
not in this list should return
noSuchInstance”
A collection of notifications
that may be implemented on
DS1 and DS2 interfaces.
311
dsx1LineStatus
Y
dsx1SignalMode
Y
dsx1TransmitClockSource
Y
dsx1Channelization
Y
dsx1CurrentESs
Y
dsx1CurrentSESs
Y
dsx1CurrentUASs
Y
dsx1IntervalESs
Y
dsx1IntervalSESs
Y
dsx1IntervalUASs
Y
dsx1TotalESs
Y
dsx1TotalSESs
Y
dsx1TotalUASs
Y
dsx1LineStatusChange
Y
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
DS1-MIB — RFC 2495
Table 162: DS1-MIB Conformance (6 of 6)
Group
Description
Objects
Supported
ds1ChanMappingGroup
A collection of objects that give
an mapping of DS3 Channel
(ds1ChannelNumber) to ifIndex.
dsx1ChanMappedIfIndex
Y
312
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15 ATM-MIB — RFC 2515
5.15.1
Introduction
This MIB describes objects for managing ATM-based interfaces. The RFC used as a reference was dated February
1999. The LAST-UPDATED for the atmMIB was “9810191200Z.”
5.15.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
atmMIB
atmMIBObjects
atmTrafficDescriptorTypes
atmInterfaceConfTable
atmInterfaceDs3PlcpTable
atmInterfaceTCTable
atmTrafficDescrParamTable
atmVplTable
atmVclTable
atmVpCrossConnectIndexNext
atmVpCrossConnectTable
atmVcCrossconnectIndexNext
atmVcCrossConnectTable
aal5VccTable
atmTrafficDescrParamIndexNext
5.15.3
Textual Conventions
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ mib-2 37 }
{ atmMIB 1 }
{ atmMIBObjects 1 }1
{ atmMIBObjects 2 }
{ atmMIBObjects 3 }
{ atmMIBObjects 4 }
{ atmMIBObjects 5 }
{ atmMIBObjects 6 }
{ atmMIBObjects 7 }
{ atmMIBObjects 8 }
{ atmMIBObjects 9 }
{ atmMIBObjects 10 }
{ atmMIBObjects 11 }
{ atmMIBObjects 12 }
{ atmMIBObjects 13 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.37
1.3.6.1.2.1.10.37.1
1.3.6.1.2.1.10.37.1.1
1.3.6.1.2.1.10.37.1.2
1.3.6.1.2.1.10.37.1.3
1.3.6.1.2.1.10.37.1.4
1.3.6.1.2.1.10.37.1.5
1.3.6.1.2.1.10.37.1.6
1.3.6.1.2.1.10.37.1.7
1.3.6.1.2.1.10.37.1.8
1.3.6.1.2.1.10.37.1.9
1.3.6.1.2.1.10.37.1.10
1.3.6.1.2.1.10.37.1.11
1.3.6.1.2.1.10.37.1.12
1.3.6.1.2.1.10.37.1.13
The following textual conventions were cited in RFC 2514, ATM TCs and OBJECT-IDENTITIES, February 1999:
•
AtmAddr
- An ATM address. The semantics are implied by the length.
— Syntax
OCTET STRING (SIZE(0…40)
• no address (0 octets)
• E.164 (8 octets)
• NSAP (20 octets)
In addition, when subaddresses are used the AtmAddr may represent the
concatenation of address and subaddress. The associated address types
are:
• E.164, E.164 (16 octets)
• E.164, NSAP (28 octets)
• NSAP, NSAP (40 octets)
1. From RFC 2514, ATM TCs and OBJECT-IDENTITIES, February, 1999.
313
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Address lengths other than defined in this definition imply address types
defined elsewhere. Note: The E.164 address is encoded in BCD format.
•
AtmConnCastType
- The type of topology of a connection (point- to-point, point-to-multipoint). In the case of point-to-multipoint, the orientation of this VPL or
VCL in the connection. On a host:
• p2mpRoot indicates that the host is the root of the p2mp connection.
• p2mpLeaf indicates that the host is a leaf of the p2mp connection.
On a switch interface:
• p2mpRoot indicates that cells received by the switching fabric from
the interface are from the root of the p2mp connection.
• p2mpLeaf indicates that cells transmitted to the interface from the
switching fabric are to the leaf of the p2mp connection.
— Syntax
INTEGER
• p2p(1)
• p2mpRoot(2)
• p2mpLeav(3)
•
AtmConnKind
- The type of call control used for an ATM connection at a particular interface. The use is as follows:
• pvc(1)
- Virtual link of a PVC. Should not be used for
an PVC/SVC (that is, Soft PVC) crossconnect.
• svcIncoming(2) - Virtual link established after a received signaling request to setup an SVC.
• svcOutgoing(3) - Virtual link established after a transmitted or
forwarded signaling request to setup an SVC.
• spvcInitiator(4) - Virtual link at the PVC side of an SVC/PVC
crossconnect, where the switch is the initiator
of the Soft PVC setup.
• spvcTarget(5)
- Virtual link at the PVC side of an SVC/PVC
crossconnect, where the switch is the target of
the Soft PVC setup.
For PVCs, a pvc virtual link is always cross-connected to a pvc virtual
link.
For SVCs, an svcIncoming virtual link is always cross-connected to an
svcOutgoing virtual link.
For Soft PVCs, an spvcInitiator is either cross-connected to an svcOutgoing or an spvcTarget, and an spvcTarget is either cross-connected to an
svcIncoming or an spvcInitiator.
Syntax
•
•
•
•
•
INTEGER
pvc(1)
svcIncoming(2)
svcOutgoing(3)
spvcInitiator(4)
spvcTarget(5)
314
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
•
AtmIlmiNetworkPrefix
- A network prefix used for ILMI address registration. In the case of ATM
endsystem addresses (AESAs), the network prefix is the first 13 octets of
the address which includes the AFI, IDI, and HO-DSP fields. In the case
of native E.164 addresses, the network prefix is the entire E.164 address
encoded in 8 octets, as if it were an E.164 IDP in an ATM endsystem
address structure.
Syntax: OCTET STRING (SIZE(8|13))
•
AtmInterfaceType
- The connection setup procedures used for the identified interface.
• Other
• Connection setup procedures other than hose listed below.
• Auto-configuration
• Indicates that the connection setup procedures are to be determined
dynamically, or that determination has not yet been completed. One
such mechanism is via ATM Forum ILMI auto-configuration procedures.
• ITU-T DSS2:
— ITU-T Recommendation Q.2931, Broadband Integrated Service
Digital Network (B-ISDN) Digital Subscriber Signalling System
No.2 (DSS2) User-Network Interface (UNI) Layer 3 Specification
for Basic Call/Connection Control (September 1994)
— ITU-T Draft Recommendation Q.2961, B-ISDN DSS 2 Support of
Additional Traffic Parameters (May 1995)
— ITU-T Draft Recommendation Q.2971, B-ISDN DSS 2 User Network Interface Layer 3 Specification for Point-to-multipoint Call/
connection Control (May 1995)
• ATM Forum UNI 3.0
ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0)
Specification, (1994).
• ATM Forum UNI 3.1
ATM Forum, ATM User-Network Interface, Version 3.1 (UNI 3.1)
Specification, (November 1994).
• ATM Forum UNI Signalling 4.0
ATM Forum, ATM User-Network Interface (UNI) Signalling Specification Version 4.0, af-sig-0061.000 (June 1996).
• ATM Forum IISP (based on UNI 3.0 or UNI 3.1)
Interim Inter-switch Signaling Protocol (IISP) Specification, Version
1.0, af-pnni-0026.000, (December 1994).
• ATM Forum PNNI 1.0
ATM Forum, Private Network-Network Interface Specification, Version
1.0, af-pnni-0055.000, (March 1996).
• ATM Forum B-ICI
ATM Forum, B-ICI Specification, Version 2.0, af-bici-0013.002,
(November 1995).
• ATM Forum UNI PVC Only
An ATM Forum compliant UNI with the signalling disabled.
• ATM Forum NNI PVC Only
An ATM Forum compliant NNI with the signalling disabled.
315
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
— Syntax
INTEGER
• other(1)
• autoConfig(2)
• ituDss2(3)
• atmfUni3Dot0(4)
• atmfUni3Dot1(5)
• atmfUni4Dot0(6)
• atmfIispUni3Dot0(7)
• atmfIispUni3Dot1(8)
• atmfIispUni4Dot0(9)
• atmfPnni1Dot0(10)
• atmfBici2Dot0(11)
• atmfUniPvcOnly(12)
• atmfNniPvcOnly(13)
•
AtmServiceCategory
- The service category for a connection.
— Syntax
INTEGER
• other(1)
- none of the following
• cbr(2)
- constant bit rate
• rtVbr(3)
- real-time variable bit rate
• nrtVbr(4)
- non real-time variable bit rate
• abr(5)
- available bit rate
• ubr(6)
- unspecified bit rate
•
AtmSigDescrParamIndex
- The value of this object identifies a row in the atmSigDescrParamTable.
The value 0 signifies that none of the signalling parameters defined in the
atmSigDescrParamTable are applicable.
— Syntax
INTEGER (0…2147483647)
•
AtmTrafficDescrParamIndex - The value of this object identifies a row in the atmTrafficDescrParamTable. The value 0 signifies that no row has been identified.
— Syntax
INTEGER (0…2147483647)
•
AtmVcIdentifier
- The VCI value for a VCL. The maximum VCI value cannot exceed the
value allowable by atmInterfaceMaxVciBits defined in ATM-MIB.
Syntax
•
AtmVpIdentifier
INTEGER (0…65535)
- The VPI value for a VPL or VCL. The value VPI=0 is only allowed for a
VCL. For ATM UNIs supporting VPCs the VPI value ranges from 0 to
255. The VPI value 0 is supported for ATM UNIs conforming to the ATM
Forum UNI 4.0 Annex 8 (Virtual UNIs) specification. For ATM UNIs supporting VCCs the VPI value ranges from 0 to 255. For ATM NNIs the VPI
value ranges from 0 to 4095. The maximum VPI value cannot exceed the
value allowable by atmInterfaceMaxVpiBits defined in ATM-MIB.
Syntax
•
AtmVorXAdminStatus
INTEGER (0…4095)
- The value determines the desired administrative status of a virtual link or
cross-connect. The up and down states indicate that the traffic flow is
enabled or disabled respectively on the virtual link or cross-connect.
Syntax
INTEGER
316
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
• up(1)
• down(2)
•
AtmVorXLastChange
- The value of MIB II’s sysUpTime at the time a virtual link or cross-connect entered its current operational state. If the current state was entered
prior to the last re-initialization of the agent then this object contains a
zero value.
—
Syntax TimeTicks (Section 4.17, Page 18)
•
AtmVorXOperStatus
- The value determines the operational status of a virtual link or cross-connect. The up and down states indicate that the traffic flow is enabled or disabled respectively on the virtual link or cross-connect. The unknown state
indicates that the state of it cannot be determined. The state is down or
unknown if the supporting ATM interface(s) is down or unknown respectively.
Syntax
INTEGER
• up(1)
• down(2)
• unknown(3)
5.15.4
MIB Objects
The following tables are supported in this MIB:
•
•
•
•
•
•
•
•
•
ATM Interface configuration table
ATM Interface DS3 PLCP table
ATM Interface TC Sublayer table
ATM Traffic Descriptor table
ATM Interface VPL configuration table
ATM Interface VCL configuration table
ATM VP Cross connect table (for PVCs)
ATM VC Cross connect table (for PVCs)
ATM Interface AAL5 VCC performance statistics table
Table 163: ATM-MIB Objects (1 of 2)
Object
OID
Syntax
Access
Status
Supported
atmInterfaceConfTable
{ atmMIBObjects 2 }
Sequence of atmInterfaceConfEntry
not-accessible
current
N
atmInterfaceDs3PlcpTable
{ atmMIBObjects 3 }
Sequence of
atmInterfaceDs3PlcpEntry
not-accessible
current
N
atmInterfaceTCTable
{ atmMIBObjects 4 }
Sequence of atmInterfaceTCEntry
not-accessible
current
Y
atmTrafficDescrParamTable
{ atmMIBObjects 5 }
Sequence of
atmTrafficDescrParamEntry
not-accessible
current
N
atmVplTable
{ atmMIBObjects 6 }
Sequence of atmVplEntry
not-accessible
current
N
atmVclTable
{ atmMIBObjects 7 }
Sequence of atmVclEntry
not-accessible
current
Y
317
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Table 163: ATM-MIB Objects (2 of 2)
Object
OID
Syntax
Access
Status
Supported
atmVpCrossConnectIndexNext
{ atmMIBObjects 8 }
INTEGER(0…2147483647)
read-only
current
N
atmVpCrossConnectTable
{ atmMIBObjects 9 }
Sequence of
atmVpCrossConnectEntry
not-accessible
current
N
atmVcCrossConnectIndexNext
{ atmMIBObjects 10 }
INTEGER(0…2147483647)
read-only
current
N
atmVcCrossConnectTable
{ atmMIBObjects 11 }
Sequence of
atmVcCrossConnectEntry
not-accessible
current
N
aal5VccTable
{ atmMIBObjects 12 }
Sequence of aal5VccTable
not-accessible
current
Y
atmTrafficDescrParamIndexNext
{ atmMIBObjects 13 }
INTEGER(0…2147483647)
not-accessible
current
N
5.15.4.1
atmInterfaceConfTable
The ATM Interface Configuration Parameters Table contains ATM specific configuration information associated with
an ATM interface beyond those supported using the ifTable. There is one entry per ATM interface port. This table is a
sequence of atmInterfaceConfEntry.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
atmInterfaceConfTable
atmInterfaceConfEntry
- { atmMIBObjects 2 }
- { atmInterfaceConfTable 1}
1.3.6.1.2.1.10.37.1.2
1.3.6.1.2.1.10.37.1.2.1
Table 164: atmInterfaceConfTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
atmInterfaceMaxVpcs
{ atmInterfaceConfEntry 1 }
INTEGER (0…4096)
read-write
current
N
atmInterfaceMaxVccs
{ atmInterfaceConfEntry 2 }
INTEGER (0…65536)
read-write
current
N
atmInterfaceConfVpcs
{ atmInterfaceConfEntry 3 }
INTEGER (0…4096)
read-only
current
N
atmInterfaceConfVccs
{ atmInterfaceConfEntry 4 }
INTEGER (0…65536)
read-only
current
N
atmInterfaceMaxActiveVpiBits
{ atmInterfaceConfEntry 5 }
INTEGER (0…12)
read-write
current
N
atmInterfaceMaxActiveVciBits
{ atmInterfaceConfEntry 6 }
INTEGER (0…16)
read-write
current
N
atmInterfaceIlmiVpi
{ atmInterfaceConfEntry 7 }
AtmVpIdentifier
read-write
current
N
318
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Table 164: atmInterfaceConfTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
atmInterfaceIlmiVci
{ atmInterfaceConfEntry 8 }
AtmVpIdentifier
read-write
current
N
atmInterfaceAddressType
{ atmInterfaceConfEntry 9 }
INTEGER
private(1)
nsapE164(2)
nativeE164(3)
other(4)
read-only
deprecated
N
atmInterfaceAdminAddress
{ atmInterfaceConfEntry 10 }
AtmAddr
read-only
deprecated
N
atmInterfaceMyNeighborIpAddress
{ atmInterfaceConfEntry 11 }
IpAddress
read-write
current
N
atmInterfaceMyNeighborIfName
{ atmInterfaceConfEntry 12 }
DisplayString
read-write
current
N
atmInterfaceCurrentMaxVpiBits
{ atmInterfaceConfEntry 13 }
INTEGER (0…12)
read-only
current
N
atmInterfaceCurrentMaxVciBits
{ atmInterfaceConfEntry 14 }
INTEGER (0…16)
read-only
current
N
atmInterfaceSubscrAddress
{ atmInterfaceConfEntry 15 }
AtmAddr
read-write
current
N
5.15.4.1.1
atmInterfaceMaxVpcs
The maximum number of VPCs (PVPCs and SVPCs) supported at this ATM interface. At the ATM UNI, the
maximum number of VPCs (PVPCs and SVPCs) ranges from 0 to 256 only.
5.15.4.1.2
atmInterfaceMaxVccs
The maximum number of VCCs (PVCCs and SVCCs) supported at this ATM interface.
5.15.4.1.3
atmInterfaceConfVpcs
The number of VPCs (PVPC, Soft PVPC and SVPC) currently in use at this ATM interface. It includes the number of
PVPCs and Soft PVPCs that are configured at the interface, plus the number of SVPCs that are currently established
at the interface.
At the ATM UNI, the configured number of VPCs (PVPCs and SVPCs) can range from 0 to 256 only.
5.15.4.1.4
atmInterfaceConfVccs
The number of VCCs (PVCC, Soft PVCC and SVCC) currently in use at this ATM interface. It includes the number
of PVCCs and Soft PVCCs that are configured at the interface, plus the number of SVCCs that are currently
established at the interface.
5.15.4.1.5
atmInterfaceMaxActiveVpiBits
The maximum number of active VPI bits configured for use at the ATM interface. At the ATM UNI, the maximum
number of active VPI bits configured for use ranges from 0 to 8 only.
5.15.4.1.6
atmInterfaceMaxActiveVciBits
The maximum number of active VCI bits configured for use at this ATM interface.
319
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15.4.1.7
atmInterfaceIlmiVpi
The VPI value of the VCC supporting the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and
atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.
The MIB recommended default value for this object is { 0 }.
5.15.4.1.8
atmInterfaceIlmiVci
The VCI value of the VCC supporting the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and
atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.
The MIB recommended default value for this object is { 16 }.
5.15.4.1.9
atmInterfaceAddressType
The type of primary ATM address configured for use at this ATM interface.
•
•
•
•
private(1),
nsapE164(2),
nativeE164(3),
other(4)
5.15.4.1.10 atmInterfaceAdminAddress
The primary address assigned for administrative purposes, for example, an address associated with the service
provider side of a public network UNI (thus, the value of this address corresponds with the value of ifPhysAddress at
the host side). If this interface has no assigned administrative address, or when the address used for administrative
purposes is the same as that used for ifPhysAddress, then this is an octet string of zero length.
Note: The atmInterfaceAdminAddress object has been replaced by atmInterfaceSubscrAddress.
5.15.4.1.11 atmInterfaceMyNeighborIpAddress
The IP address of the neighbor system connected to the far end of this interface, to which a Network Management
Station can send SNMP messages, as IP datagrams sent to UDP port 161, in order to access network management
information concerning the operation of that system. Note that the value of this object may be obtained in different
ways, for example, by manual configuration, or through ILMI interaction with the neighbor system.
5.15.4.1.12 atmInterfaceMyNeighborIfName
The textual name of the interface on the neighbor system on the far end of this interface, and to which this interface
connects. If the neighbor system is manageable through SNMP and supports the object ifName, the value of this
object must be identical with that of ifName for the ifEntry of the lowest level physical interface for this port. If this
interface does not have a textual name, the value of this object is a zero length string. Note that the value of this object
may be obtained in different ways, for example, by manual configuration, or through ILMI interaction with the
neighbor system.
5.15.4.1.13 atmInterfaceCurrentMaxVpiBits
The maximum number of VPI Bits that may currently be used at this ATM interface. The value is the minimum of
atmInterfaceMaxActiveVpiBits, and the atmInterfaceMaxActiveVpiBits of the interface's UNI/NNI peer.
If the interface does not negotiate with its peer to determine the number of VPI Bits that can be used on the interface,
then the value of this object must equal atmInterfaceMaxActiveVpiBits.
320
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15.4.1.14 atmInterfaceCurrentMaxVciBits
The maximum number of VCI Bits that may currently be used at this ATM interface. The value is the minimum of
atmInterfaceMaxActiveVciBits, and the atmInterfaceMaxActiveVciBits of the interface's UNI/NNI peer.
If the interface does not negotiate with its peer to determine the number of VCI Bits that can be used on the interface,
then the value of this object must equal atmInterfaceMaxActiveVciBits.
5.15.4.1.15 atmInterfaceSubscrAddress
The identifier assigned by a service provider to the network side of a public network UNI. If this interface has no
assigned service provider address, or for other interfaces this is an octet string of zero length.
5.15.4.2
atmInterfaceDs3PlcpTable
The ATM Interface DS3 PLCP Table contains ATM interface DS3 PLCP parameters and state variables, one entry per
ATM interface port. This table is a sequence of atmInterfaceDs3PlcpEntry which contains DS3 PLCP parameters and
state variables at the ATM interface.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
atmInterfaceDs3PlcpTable - { atmMIBObjects 3 }
atmInterfaceDs3PlcpEntry - { atmInterfaceDs3PlcpTable 1}
1.3.6.1.2.1.10.37.1.3
1.3.6.1.2.1.10.37.1.3.1
Table 165: atmInterfaceDs3PlcpTable
Object
OID
Syntax
Access
Status
Supported
atmInterfaceDs3PlcpSEFSs
{ atmInterfaceDs3PlcpEntry 1 }
Counter32
read-only
current
N
atmInterfaceDs3PlcpAlarmState
{ atmInterfaceDs3PlcpEntry 2 }
INTEGER
noAlarm(1)
receivedFarEndAlarm(2)
incomingLOF(3)
read-only
current
N
atmInterfaceDs3PlcpUASs
{ atmInterfaceDs3PlcpEntry 3 }
Counter32
read-only
current
N
5.15.4.2.1
atmInterfaceDs3PlcpSEFSs
The number of DS3 PLCP Severely Errored Framing Seconds (SEFS). Each SEFS represents a one-second interval
which contains one or more SEF events.
5.15.4.2.2
atmInterfaceDs3PlcpAlarmState
This variable indicates if there is an alarm present for the DS3 PLCP. The value receivedFarEndAlarm means that the
DS3 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS3 PLCP has declared
a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. Transition
from the failure to the no alarm state occurs when no defects (for example, LOF) are received for more than 10
321
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
seconds.
•
•
•
noAlarm(1)
receivedFarEndAlarm(2)
incomingLOF(3)
5.15.4.2.3
atmInterfaceDs3PlcpUASs
The counter associated with the number of Unavailable Seconds encountered by the PLCP.
5.15.4.3
atmInterfaceTCTable
The ATM Interface TC Sublayer Table contains TC sublayer configuration and state parameters of those ATM
interfaces which use TC sublayer for carrying ATM cells over SONET/SDH or DS3. This table has one entry per
ATM interface port. This table is a sequence of atmInterfaceTCEntry which is a list that contains TC Sublayer
parameters and state variables at the ATM interface.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
atmInterfaceTCTable
atmInterfaceTCEntry
- { atmMIBObjects 4 }
- { atmInterfaceTCTable 1}
1.3.6.1.2.1.10.37.1.4
1.3.6.1.2.1.10.37.1.4.1
Table 166: atmInterfaceTCTable
Object
OID
Syntax
Access
Status
Supported
atmInterfaceOCDEvents
{ atmInterfaceTCEntry 1 }
Counter32
read-only
current
Y
atmInterfaceTCAlarmState
{ atmInterfaceTCEntry 2 }
INTEGER
noAlarm(1)
lcdFailure(2)
read-only
current
Y
5.15.4.3.1
atmInterfaceOCDEvents
The number of times the Out of Cell Delineation (OCD) events occur. If seven consecutive ATM cells have Header
Error Control (HEC) violations, an OCD event occurs. A high number of OCD events may indicate a problem with
the TC Sublayer.
5.15.4.3.2
atmInterfaceTCAlarmState
This variable indicates if there is an alarm present for the TC Sublayer. The value lcdFailure(2) indicates that the TC
Sublayer is currently in the Loss of Cell Delineation (LCD) defect maintenance state. The value noAlarm(1) indicates
that the TC Sublayer is currently not in the LCD defect maintenance state.
•
•
noAlarm(1)
lcdFailure(2)
322
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15.4.4
atmTrafficDescrParamTable
ATM Traffic Descriptor Parameter Table contains a set of self-consistent ATM traffic parameters including the ATM
traffic service category.
The ATM virtual link tables (that is, VPL and VCL tables) will use this ATM Traffic Descriptor table to assign traffic
parameters and service category to the receive and transmit directions of the ATM virtual links (that is, VPLs and
VCLs). The ATM VPL or VCL table will indicate a row in the atmTrafficDescrParamTable using its
atmTrafficDescrParamIndex value. The management application can then compare a set of ATM traffic parameters
with a single value.
If no suitable row(s) in the atmTrafficDescrParamTable exists, the manager must create a new row(s) in this table. If
such a row is created, agent checks the sanity of that set of ATM traffic parameter values.
The manager may use atmTrafficDescrParamIndexNext in order to obtain a free atmTrafficDescrParamIndex value.
When creating a new row, the parameter values are checked for self-consistency. Predefined/template rows may be
supported.
A row in the atmTrafficDescrParamTable is deleted by setting the atmTrafficDescrRowStatus to destroy(6). The agent
will check whether this row is still in use by any entry of the atmVplTable or atmVclTable. The agent denies the
request if the row is still in use.
This table is a sequence of atmTrafficDescrParamEntry which contains ATM traffic descriptor type and the associated
parameters.
Index(es):
•
atmTrafficDescrParamIndex
OIDs:
•
•
atmTrafficDescrParamTable
atmTrafficDescrParamEntry
- { atmMIBObjects 5 }
- { atmTrafficDescrParamTable 1}
1.3.6.1.2.1.10.37.1.5
1.3.6.1.2.1.10.37.1.5.1
Table 167: atmTrafficDescrParamTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
atmTrafficDescrParamIndex
{ atmTrafficDescrParamEntry 1 }
AtmTrafficDescrParamIndex
(1…2147483647)
not-accessible
current
N
atmTrafficDescrType
{ atmTrafficDescrParamEntry 2 }
OBJECT IDENTIFIER
read-create
current
N
atmTrafficDescrParam1
{ atmTrafficDescrParamEntry 3 }
Integer32
read-create
current
N
atmTrafficDescrParam2
{ atmTrafficDescrParamEntry 4 }
Integer32
read-create
current
N
atmTrafficDescrParam3
{ atmTrafficDescrParamEntry 5 }
Integer32
read-create
current
N
atmTrafficDescrParam4
{ atmTrafficDescrParamEntry 6 }
Integer32
read-create
current
N
atmTrafficDescrParam5
{ atmTrafficDescrParamEntry 7 }
Integer32
read-create
current
N
atmTrafficQoSClass
{ atmTrafficDescrParamEntry 8 }
INTEGER(0…255)
read-create
deprecated
N
323
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Table 167: atmTrafficDescrParamTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
atmTrafficDescrRowStatus
{ atmTrafficDescrParamEntry 9 }
RowStatus
read-create
current
N
atmServiceCategory
{ atmTrafficDescrParamEntry 10 }
AtmServiceCategory
read-create
current
N
atmTrafficFrameDiscard
{ atmTrafficDescrParamEntry 11 }
TruthValue
read-create
current
N
5.15.4.4.1
atmTrafficDescrParamIndex
This object is used by the virtual link table (that is, VPL or VCL table) to identify the row of this table. When creating
a new row in the table the value of this index may be obtained by retrieving the value of
atmTrafficDescrParamIndexNext.
5.15.4.4.2
atmTrafficDescrType
The value of this object identifies the type of ATM traffic descriptor. The type may indicate no traffic descriptor or
traffic descriptor with one or more parameters. These parameters are specified as a parameter vector, in the
corresponding instances of the objects:
•
•
•
•
•
atmTrafficDescrParam1
atmTrafficDescrParam2
atmTrafficDescrParam3
atmTrafficDescrParam4
atmTrafficDescrParam5
The MIB recommended default value for this object is atmNoClpNoScr.
5.15.4.4.3
atmTrafficDescrParam1
The first parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
The MIB recommended default value for this object is { 0 }.
5.15.4.4.4
atmTrafficDescrParam2
The second parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
The MIB recommended default value for this object is { 0 }.
5.15.4.4.5
atmTrafficDescrParam3
The third parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
The MIB recommended default value for this object is { 0 }.
5.15.4.4.6
atmTrafficDescrParam4
The fourth parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
The MIB recommended default value for this object is { 0 }.
324
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15.4.4.7
atmTrafficDescrParam5
The fifth parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
5.15.4.4.8
atmTrafficQoSClass
The value of this object identifies the QoS Class. Four Service classes have been specified in the ATM Forum UNI
Specification:
1.
2.
3.
4.
Service Class A: Constant bit rate video and Circuit emulation
Service Class B: Variable bit rate video/audio
Service Class C: Connection-oriented data
Service Class D: Connectionless data
Four QoS classes numbered 1, 2, 3, and 4 have been specified with the aim to support service classes A, B, C, and D
respectively.
An unspecified QoS Class numbered “0” is used for best effort traffic.
The MIB recommended default value for this object is { 0 }.
5.15.4.4.9
atmTrafficDescrRowStatus
This object is used to create a new row or modify or delete an existing row in this table.
The MIB recommended default value for this object is { active }.
5.15.4.4.10 atmServiceCategory
The ATM service category.
The MIB recommended default value for this object is { ubr }.
5.15.4.4.11 atmTrafficFrameDiscard
If set to “true,” this object indicates that the network is requested to treat data for this connection, in the given
direction, as frames (for example, AAL5 CPCS_PDUs) rather than as individual cells. While the precise
implementation is network-specific, this treatment may for example involve discarding entire frames during
congestion, rather than a few cells from many frames.
The MIB recommended default value for this object is { true }.
5.15.4.5
atmVplTable
ATM Interface Virtual Path Link (VPL) Table contains configuration and state information of a bi-directional Virtual
Path Link (VPL). A bi-directional VPL is modeled as one entry in this table. This table can be used for PVCs, SVCs
and Soft PVCs. Entries are not present in this table for the VPIs used by entries in the atmVclTable.
This table can be used to create, delete or modify a VPL that is terminated in an ATM host or switch. This table can
also be used to create, delete or modify a VPL which is cross-connected to another VPL.
In the example below, the traffic flows on the receive and transmit directions of the VPLs are characterized by
atmVplReceiveTrafficDescrIndex and atmVplTransmitTrafficDescrIndex respectively. The cross-connected VPLs are
identified by atmVplCrossConnectIdentifier.
In the example below, the traffic flows on the receive and transmit directions of the VPLs are characterized by
atmVplReceiveTrafficDescrIndex and,atmVplTransmitTrafficDescrIndex respectively.mThe cross-connected VPLs
are identified by atmVplCrossConnectIdentifier.
325
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
VPL
VPL
receive
ATM Host, Switch or Network
receive
transmit
transmit
This table is a sequence of atmVplEntry. The index for this table is the ifIndex and atmVplVpi objects.
To create a VPL at an ATM interface, either of the following procedures are used:
•
1.
Negotiated VPL establishment
The management application creates a VPL entry in the atmVplTable by setting atmVplRowStatus to createAndWait(5). This may fail for the following reasons:
• The selected VPI value is unavailable
•The selected VPI value is in use.
Otherwise, the agent creates a row and reserves the VPI value on that port.
2.
3.
4.
•
The manager selects an existing row(s) in the atmTrafficDescrParamTable, thereby, selecting a set of selfconsistent ATM traffic parameters and the service category for receive and transmit directions of the VPL.
2a.
If no suitable row(s) in the atmTrafficDescrParamTable exists, the manager must create a new
row(s) in that table.
2b.
The manager characterizes the VPL's traffic parameters through setting the
atmVplReceiveTrafficDescrIndex and the atmVplTransmitTrafficDescrIndex values in the VPL
table, which point to the rows containing desired ATM traffic parameter values in the
atmTrafficDescrParamTable. The agent will check the availability of resources and may refuse
the request. If the transmit and receive service categories are inconsistent, the agent should refuse
the request.
The manager activates the VPL by setting the atmVplRowStatus to active(1). If this set is successful, the
agent has reserved the resources to satisfy the requested traffic parameter values and the service category for
that VPL.
If the VPL terminates a VPC in the ATM host or switch, the manager turns on the atmVplAdminStatus to
up(1) to turn the VPL traffic flow on. Otherwise, the atmVpCrossConnectTable must be used to cross-connect the VPL to another VPL(s) in an ATM switch or network.
One-Shot VPL Establishment
A VPL may also be established in one step by a set-request with all necessary VPL parameter values and
atmVplRowStatus set to createAndGo(4). In contrast to the negotiated VPL establishment which allows for
detailed error checking (that is, set errors are explicitly linked to particular resource acquisition failures), the
326
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
one-shot VPL establishment performs the setup on one operation but does not have the advantage of stepwise error checking.
•
VPL Retirement
A VPL is released by setting atmVplRowStatus to destroy(6), and the agent may release all associated
resources.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVplVpi
OIDs:
•
•
atmVplTable
atmVplEntry
- { atmMIBObjects 6 }
- { atmVplTable 1}
1.3.6.1.2.1.10.37.1.6
1.3.6.1.2.1.10.37.1.6.1
Table 168: atmVplTable
Object
OID
Syntax
Access
Status
Supported
atmVplVpi
{ atmVplEntry 1 }
AtmVpIdentifier
not-accessible
current
N
atmVplAdminStatus
{ atmVplEntry 2 }
AtmVorXAdminStatus
read-create
current
N
atmVplOperStatus
{ atmVplEntry 3 }
AtmVorXOperStatus
read-only
current
N
atmVplLastChange
{ atmVplEntry 4 }
AtmVorXLastChange
read-only
current
N
atmVplReceiveTrafficDescrIndex
{ atmVplEntry 5 }
AtmTrafficDescrParamIndex
read-create
current
N
atmVplTransmitTrafficDescrIndex
{ atmVplEntry 6 }
AtmTrafficDescrParamIndex
read-create
current
N
atmVplCrossConnectIdentifier
{ atmVplEntry 7 }
INTEGER(1…2147483647)
read-create
current
N
atmVplRowStatus
{ atmVplEntry 8 }
RowStatus
read-create
current
N
atmVplCastType
{ atmVplEntry 9 }
AtmConnCastType
read-create
current
N
atmVplConnKind
{ atmVplEntry 10 }
AtmConnKind
read-create
current
N
5.15.4.5.1
atmVplVpi
The VPI value of the VPL.
5.15.4.5.2
atmVplAdminStatus
This object is instantiated only for a VPL which terminates a VPC (that is, one which is NOT cross-connected to
other VPLs). Its value specifies the desired administrative state of the VPL.
The MIB recommended default value for this object is { down }.
327
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15.4.5.3
atmVplOperStatus
The current operational status of the VPL.
5.15.4.5.4
atmVplLastChange
The value of sysUpTime at the time this VPL entered its current operational state.
5.15.4.5.5
atmVplReceiveTrafficDescrIndex
The value of this object identifies the row in the atmTrafficDescrParamTable which applies to the receive direction of
the VPL.
The MIB recommended default value for this object is { 0 }.
5.15.4.5.6
atmVplTransmitTrafficDescrIndex
The value of this object identifies the row in the atmTrafficDescrParamTable which applies to the transmit direction
of the VPL.
The MIB recommended default value for this object is { 0 }.
5.15.4.5.7
atmVplCrossConnectIdentifier
This object is instantiated only for a VPL which is cross-connected to other VPLs that belong to the same VPC. All
such associated VPLs have the same value of this object, and all their cross-connections are identified either by
entries that are indexed by the same value of atmVpCrossConnectIndex in the atmVpCrossConnectTable of this MIB
module or by the same value of the cross-connect index in the cross-connect table for SVCs and Soft PVCs (defined
in a separate MIB module). At no time should entries in these respective cross-connect tables exist simultaneously
with the same cross-connect index value. The value of this object is initialized by the agent after the associated entries
in the atmVpCrossConnectTable have been created.
5.15.4.5.8
atmVplRowStatus
This object is used to create, delete or modify a row in this table. To create a new VCL, this object is initially set to
“createAndWait” or “createAndGo”. This object should not be set to “active” unless the following columnar objects
have been set to their desired value in this row: atmVplReceiveTrafficDescrIndex and
atmVplTransmitTrafficDescrIndex. The DESCRIPTION of atmVplEntry provides further guidance to row treatment
in this table.
The MIB recommended default value for this object is { createAndWait }.
5.15.4.5.9
atmVplCastType
The connection topology type.
The MIB recommended default value for this object is { p2p }.
5.15.4.5.10 atmVplConnKind
The use of call control.
The MIB recommended default value for this object is { pvc }.
5.15.4.6
atmVclTable
The ATM Interface Virtual Channel Link (VCL) Table contains configuration and state information of a bi-directional
Virtual Channel Link (VCL) at an ATM interface. A bi-directional VCL is modeled as one entry in this table. This
328
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
table can be used for PVCs, SVCs and Soft PVCs. This table can be used to create, delete or modify a VCL that is
terminated in an ATM host or switch. This table can also be used to create, delete or modify a VCL that is crossconnected to another VCL.
This table is a sequence of atmVclEntry and indexed by ifIndex, atmVclVpi, and atmVclVci objects.
To create a VCL at an ATM interface, either of the following procedures are used:
•
1.
Negotiated VCL establishment
The management application creates a VCL entry in the atmVclTable by setting atmVclRowStatus to createAndWait(5). This may fail for the following reasons:
•The selected VPI/VCI values are unavailable
•The selected VPI/VCI values are in use
Otherwise, the agent creates a row and reserves the VPI/VCI values on that port.
2.
The manager selects an existing row(s) in the atmTrafficDescrParamTable, thereby, selecting a set of selfconsistent ATM traffic parameters and the service category for receive and transmit directions of the VCL.
2a. If no suitable row(s) in the atmTrafficDescrParamTable exists, the manager must create a new
row(s) in that table.
2b. The manager characterizes the VCL's traffic parameters through setting the
atmVclReceiveTrafficDescrIndex and the atmVclTransmitTrafficDescrIndex values in the VCL
table, which point to the rows containing desired ATM traffic parameter values in the
atmTrafficDescrParamTable. The agent will check the availability of resources and may refuse the
request. If the transmit and receive service categories are inconsistent, the agent should refuse the
request.
3.
4.
•
The manager activates the VCL by setting the atmVclRowStatus to active(1) (for requirements on this activation see the description of atmVclRowStatus). If this set is successful, the agent has reserved the resources
to satisfy the requested traffic parameter values and the service category for that VCL.
If the VCL terminates a VCC in the ATM host or switch, the manager turns on the atmVclAdminStatus to
up(1) to turn the VCL traffic flow on. Otherwise, the atmVcCrossConnectTable must be used to cross-connect the VCL to another VCL(s) in an ATM switch or network.
One-Shot VCL Establishment
A VCL may also be established in one step by a set-request with all necessary VCL parameter values and
atmVclRowStatus set to createAndGo(4).
In contrast to the negotiated VCL establishment which allows for detailed error checking (that is, set errors
are explicitly linked to particular resource acquisition failures), the one-shot VCL establishment performs
the setup on one operation but does not have the advantage of step-wise error checking.
•
VCL Retirement
A VCL is released by setting atmVclRowStatus to destroy(6), and the agent may release all associated
resources.
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVclVpi
atmVclVci
329
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
OIDs:
•
•
atmVclTable
atmVclEntry
- { atmMIBObjects 7 }
- { atmVclTable 1}
1.3.6.1.2.1.10.37.1.7
1.3.6.1.2.1.10.37.1.7.1
Table 169: atmVclTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
atmVclVpi
{ atmVclEntry 1 }
AtmVpIdentifier
not-accessible
current
Y
atmVclVci
{ atmVclEntry 2 }
AtmVcIdentifier
not-accessible
current
Y
atmVclAdminStatus
{ atmVclEntry 3 }
AtmVorXAdminStatus
read-create
current
Y
atmVclOperStatus
{ atmVclEntry 4 }
AtmVorXOperStatus
read-only
current
Y
atmVclLastChange
{ atmVclEntry 5 }
AtmVorXLastChange
read-only
current
Y
atmVclReceiveTrafficDescrIndex
{ atmVclEntry 6 }
AtmTrafficDescrParamIndex
read-create
current
N
atmVclTransmitTrafficDescrIndex
{ atmVclEntry 7 }
AtmTrafficDescrParamIndex
read-create
current
N
atmVccAalType
{ atmVclEntry 8 }
INTEGER
aal1(1)
aal34(2)
aal5(3)
other(4)
unknown(5)
aal2(6)
read-create
current
Y
atmVccAal5CpcsTransmitSduSize
{ atmVclEntry 9 }
INTEGER(1…65535)
read-create
current
Y
atmVccAal5CpcsReceiveSduSize
{ atmVclEntry 10 }
INTEGER(1…65535)
read-create
current
Y
atmVccAal5EncapsType
{ atmVclEntry 11 }
INTEGER
vcMultiplexRoutedProtocol(1)
vcMultiplexBridgedProtocol8023(2)
vcMultiplexBridgedProtocol8025(3)
vcMultiplexBridgedProtocol(4)
vcMultiplexLANemulation8023(5)
vcMultiplexLANemulation8025(6)
llcEncapsulation(7)
multiprotocolFrameRelaySscs(8)
other(9)
unknown(10)
read-create
current
Y
atmVclCrossConnectIdentifier
{ atmVclEntry 12 }
INTEGER(1…2147483674)
read-only
current
N
atmVclRowStatus
{ atmVclEntry 13 }
RowStatus
read-create
current
Y
atmVclCastType
{ atmVclEntry 14 }
AtmConnCastType
read-create
current
N
330
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Table 169: atmVclTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
atmVclConnKind
{ atmVclEntry 15 }
AtmConnKind
read-create
current
N
5.15.4.6.1
atmVclVpi
The VPI value of the VPL.
5.15.4.6.2
atmVclVci
The VCI value of the VCL.
5.15.4.6.3
atmVclAdminStatus
This object is instantiated only for a VCL which terminates a VCC (that is, one which is NOT cross-connected to
other VCLs). Its value specifies the desired administrative state of the VCL.
The MIB recommended default value for this object is { down }.
5.15.4.6.4
atmVclOperStatus
The current operational status of the VCL.
5.15.4.6.5
atmVclLastChange
The value of sysUpTime at the time this VCL entered its current operational state.
5.15.4.6.6
atmVclReceiveTrafficDescrIndex
The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction
of this VCL.
The MIB recommended default value for this object is { 0 }.
5.15.4.6.7
atmVclTransmitTrafficDescrIndex
The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction
of this VCL.
The MIB recommended default value for this object is { 0 }.
5.15.4.6.8
atmVccAalType
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL is in use.
The type of AAL used on this VCC. The AAL type includes AAL1, AAL2, AAL3/4, and AAL5. The other(4) may be
user-defined AAL type. The unknown type indicates that the AAL type cannot be determined.
•
•
•
•
•
•
aal1(1)
aal34(2)
aal5(3)
other(4)
unknown(5)
aal2(6)
331
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
The MIB recommended default value for this object is { aal5 }.
Valid Object Value(s)
This object will always return aal5(3) and attempts to write a different value will return notWritable(17) in the errorstatus filed of the SNMP PDU.
5.15.4.6.9
atmVccAal5CpcsTransmitSduSize
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use.
The maximum AAL5 CPCS SDU size in octets that is supported on the transmit direction of this VCC.
The MIB recommended default value for this object is { 9188 }.
Valid Object Value(s)
This object will always return 1536 and attempts to write a different value will return notWritable(17) in the errorstatus filed of the SNMP PDU.
5.15.4.6.10 atmVccAal5CpcsReceiveSduSize
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use.
The maximum AAL5 CPCS SDU size in octets that is supported on the receive direction of this VCC.
The MIB recommended default value for this object is { 9188 }.
Valid Object Value(s)
This object will always return 1536 and attempts to write a different value will return notWritable(17) in the errorstatus filed of the SNMP PDU.
5.15.4.6.11 atmVccAal5EncapsType
An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use.
The type of data encapsulation used over the AAL5 SSCS layer. The definitions reference RFC 1483 Multiprotocol
Encapsulation over ATM AAL5 and to the ATM Forum LAN Emulation specification.
•
•
•
•
•
•
•
•
•
•
vcMultiplexRoutedProtocol(1)
vcMultiplexBridgedProtocol8023(2)
vcMultiplexBridgedProtocol8025(3)
vcMultiplexBridgedProtocol8026(4)
vcMultiplexLANemulation8023(5)
vcMultiplexLANemulation8025(6)
llcEncapsulation(7)
multiprotocolFrameRelaySscs(8)
other(9)
unknown(10)
The MIB recommended default value for this object is { llcEncapsulation }.
Valid Object Values
•
•
vcMultiplexBridgedProtocol8023(2)
llcEncapsulation(7)
5.15.4.6.12 atmVclCrossConnectIdentifier
This object is instantiated only for a VCL which is cross-connected to other VCLs that belong to the same VCC. All
332
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
such associated VCLs have the same value of this object, and all their cross-connections are identified either by
entries that are indexed by the same value of atmVcCrossConnectIndex in the atmVcCrossConnectTable of this MIB
module or by the same value of the cross-connect index in the cross-connect table for SVCs and Soft PVCs (defined
in a separate MIB module).
At no time should entries in these respective cross-connect tables exist simultaneously with the same cross-connect
index value. The value of this object is initialized by the agent after the associated entries in the
atmVcCrossConnectTable have been created.
5.15.4.6.13 atmVclRowStatus
This object is used to create, delete or modify a row in this table. To create a new VCL, this object is initially set to
“createAndWait” or “createAndGo.” This object should not be set to “active” unless the following columnar objects
have been set to their desired value in this row: atmVclReceiveTrafficDescrIndex, atmVclTransmitTrafficDescrIndex.
In addition, if the local VCL end-point is also the VCC end-point: atmVccAalType. In addition, for AAL5
connections only: atmVccAal5CpcsTransmitSduSize, atmVccAal5CpcsReceiveSduSize, and
atmVccAal5EncapsType. (The existence of these objects imply the AAL connection type.). The DESCRIPTION of
atmVclEntry provides further guidance to row treatment in this table.
Valid Object Value(s)
The MIB recommended default value for this object is { createAndGo }.
The { createAndWait } RowStatus (Section 4.11, Page 15) is not supported.
5.15.4.6.14 atmVclCastType
The connection topology type.
The MIB recommended default value for this object is { p2p }.
5.15.4.6.15 atmVclConnKind
The use of call control.
The MIB recommended default value for this object is { pvc }.
5.15.4.7
atmVpCrossConnectIndexNext
This object contains an appropriate value to be used for atmVpCrossConnectIndex when creating entries in the
atmVpCrossConnectTable. The value 0 indicates that no unassigned entries are available. To obtain the
atmVpCrossConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to
obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned
index. After a manager retrieves a value the agent will determine through its local policy when this index value is
made available for reuse.
OID:
•
5.15.4.8
atmVpCrossConnectIndexNext
- { atmMIBObjects 8 }
atmVpCrossConnectTable
The ATM Virtual Path (VP) Cross Connect Table contains configuration and state information of point-to-point,
point-to-multipoint, or multipoint-to-multipoint VP cross-connects for PVCs. An entry in this table models two
cross-connected VPLs. Each VPL must have its atmConnKind set to pvc(1).
This table has read-create access and can be used to cross-connect the VPLs together in an ATM switch or network.
333
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
The atmVpCrossConnectIndex is used to associate the related VPLs that are cross-connected together.
The ATM VP Cross Connect Table models each bi-directional VPC cross-connect as a set of entries in the
atmVpCrossConnectTable. A point-to-point VPC cross-connect is modeled as one entry; a point-to-multipoint (N
leafs) VPC cross-connect as N entries in this table; and a multipoint-to-multipoint (N parties) VPC cross- connect as
N(N-1)/2 entries in this table. In the latter cases, all the N (or N(N-1)/2) entries are associated with a single VPC
cross-connect by having the same value of atmVpCrossConnectIndex.
Low
port
ATM Switch or Network
>> from low to high VPC traffic flow >>
<< from high to low VPC traffic flow <<
High
port
The terms low and high are chosen to represent numerical ordering of the two interfaces associated with a VPC crossconnect. That is, the ATM interface with the lower value of ifIndex is termed “low” while the other ATM interface
associated with the, VPC cross-connect is termed “high.” This terminology is used to provide directional information;
for example, the atmVpCrossConnectL2HOperStatus applies to the low->high direction, and
atmVpCrossConnectH2LOperStatus applies to the high->low direction, as illustrated above.
The atmVpCrossConnectTable is a sequence of atmVpCrossConnectEntry and is index by
atmVpCrossConnectIndex, atmVpCrossConnectLowIfIndex, atmVpCrossConnectLowVpi,
atmVpCrossConnectHighIfIndex, and atmVpCrossConnectHighVpi objects.
•
Step-wise Procedures to set up a VP Cross-connect
Once the entries in the atmVplTable are created, the following procedures are used to cross-connect the
VPLs together.
1.
2.
•
The manager obtains a unique atmVpCrossConnectIndex by reading the atmVpCrossConnectIndexNext
object.
Next, the manager creates a set of one or more rows in the ATM VP Cross Connect Table, one for each
cross-connection between two VPLs. Each row is indexed by the ATM interface port numbers and VPI values of the two ends of that cross-connection. This set of rows specifies the topology of the VPC cross-connect and is identified by a single value of atmVpCrossConnectIndex.
Negotiated VP Cross-Connect Establishment
2a. The manager creates a row in this table by setting atmVpCrossConnectRowStatus to createAndWait(5).
The agent checks the requested topology and the mutual sanity of the ATM traffic parameters and
service categories, that is, the row creation fails if:
•the requested topology is incompatible with associated values of atmVplCastType,
334
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
•the requested topology is not supported by the agent,
•the traffic/service category parameter values associated with the requested row are incompatible with
those of already existing rows for this VP cross-connect. [For example, for setting up a point-topoint VP cross-connect, the ATM traffic parameters in the receive direction of a VPL at the low end
of the cross-connect must equal to the traffic parameters in the transmit direction of the other VPL
at the high end of the cross-connect, otherwise, the row creation fails.] The agent also checks for
internal errors in building the cross-connect.
The atmVpCrossConnectIndex values in the corresponding atmVplTable rows are filled in by the
agent at this point.
2b. The manager promotes the row in the atmVpCrossConnectTable by setting
atmVpCrossConnectRowStatus to active(1). If this set is successful, the agent has reserved the
resources specified by the ATM traffic parameter and Service category values for each direction of the
VP cross-connect in an ATM switch or network.
3.
•
The manager sets the atmVpCrossConnectAdminStatus to up(1) in all rows of this VP cross-connect to turn
the traffic flow on.
One-Shot VP Cross-Connect Establishment
A VP cross-connect may also be established in one step by a set-request with all necessary parameter values
and atmVpCrossConnectRowStatus set to createAndGo(4).
In contrast to the negotiated VP cross-connect establishment which allows for detailed error checking (that
is, set errors are explicitly linked to particular resource acquisition failures), the one-shot VP cross-connect
establishment performs the setup on one operation but does not have the advantage of step-wise error
checking.
•
VP Cross-Connect Retirement
A VP cross-connect identified by a particular value of atmVpCrossConnectIndex is released by:
1.
2.
•
Setting atmVpCrossConnectRowStatus of all rows identified by this value of atmVpCrossConnectIndex to
destroy(6). The agent may release all associated resources, and the atmVpCrossConnectIndex values in the
corresponding atmVplTable row are removed. Note that a situation when only a subset of the associated
rows are deleted corresponds to a VP topology change.
After deletion of the appropriate atmVpCrossConnectEntries, the manager may set atmVplRowStatus to
destroy(6) the associated VPLs. The agent releases the resources and removes the associated rows in the
atmVplTable.
VP Cross-connect Reconfiguration
At the discretion of the agent, a VP cross-connect may be reconfigured by adding and/or deleting leafs to/
from the VP topology as per the VP cross-connect establishment/retirement procedures. Reconfiguration of
traffic/service category parameter values requires release of the VP cross-connect before those parameter
values may by changed for individual VPLs.
Index(es):
•
•
•
•
•
atmVpCrossConnectIndex
atmVpCrossConnectLowIfIndex
atmVpCrossConnectLowVpi
atmVpCrossConnectHighIfIndex
atmVpCrossConnectHighVpi
335
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
OIDs:
•
•
atmVpCrossConnectTable - { atmMIBObjects 9 }
atmVpCrossConnectEntry - { atmVpCrossConnectTable 1}
1.3.6.1.2.1.10.37.1.9
1.3.6.1.2.1.10.37.1.9.1
Table 170: atmVpCrossConnectTable
Object
OID
Syntax
Access
Status
Supported
atmVpCrossConnectIndex
{ atmVpCrossConnectEntry 1 }
INTEGER
(1…2147483647)
not-accessible
current
N
atmVpCrossConnectLowIfIndex
{ atmVpCrossConnectEntry 2 }
InterfaceIndex
not-accessible
current
N
atmVpCrossConnectLowVpi
{ atmVpCrossConnectEntry 3 }
AtmVpIdentifier
not-accessible
current
N
atmVpCrossConnectHighIfIndex
{ atmVpCrossConnectEntry 4 }
InterfaceIndex
not-accessible
current
N
atmVpCrossConnectHighVpi
{ atmVpCrossConnectEntry 5 }
AtmVpIdentifier
not-accessible
current
N
atmVpCrossConnectAdminStatus
{ atmVpCrossConnectEntry 6 }
AtmVorXAdminStatus
read-create
current
N
atmVpCrossConnectL2HOperStatus
{ atmVpCrossConnectEntry 7 }
AtmVorXOperStatus
read-only
current
N
atmVpCrossConnectH2LOperStatus
{ atmVpCrossConnectEntry 8 }
AtmVorXOperStatus
read-only
current
N
atmVpCrossConnectL2HLastChange
{ atmVpCrossConnectEntry 9 }
AtmVorXLastChange
read-only
current
N
atmVpCrossConnectH2LLastChange
{ atmVpCrossConnectEntry 10 }
AtmVorXLastChange
read-only
current
N
atmVpCrossConnectRowStatus
{ atmVpCrossConnectEntry 11 }
RowStatus
read-create
current
N
5.15.4.8.1
atmVpCrossConnectIndex
A unique value to identify this VP cross-connect. For each VPL associated with this cross-connect, the agent reports
this cross-connect index value in the atmVplCrossConnectIdentifier attribute of the corresponding atmVplTable
entries.
5.15.4.8.2
atmVpCrossConnectLowIfIndex
The ifIndex value of the ATM interface for this VP cross-connect. The term low implies that this ATM interface has
the numerically lower ifIndex value than the other ATM interface identified in the same atmVpCrossConnectEntry.
5.15.4.8.3
atmVpCrossConnectLowVpi
The VPI value at the ATM interface associated with the VP cross-connect that is identified by
atmVpCrossConnectLowIfIndex.
5.15.4.8.4
atmVpCrossConnectHighIfIndex
The ifIndex value of the ATM interface for this VP cross-connect. The term high implies that this ATM interface has
the numerically higher ifIndex value than the other ATM interface identified in the same atmVpCrossConnectEntry.
336
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
5.15.4.8.5
atmVpCrossConnectHighVpi
The VPI value at the ATM interface associated with the VP cross-connect that is identified by
atmVpCrossConnectHighIfIndex.
5.15.4.8.6
atmVpCrossConnectAdminStatus
The desired administrative status of this bi-directional VP cross-connect.
The MIB recommended default value for this object is { down }.
5.15.4.8.7
atmVpCrossConnectL2HOperStatus
The operational status of the VP cross-connect in one direction; (that is, from the low to high direction).
5.15.4.8.8
atmVpCrossConnectH2LOperStatus
The operational status of the VP cross-connect in one direction; (that is, from the high to low direction).
5.15.4.8.9
atmVpCrossConnectL2HLastChange
The value of sysUpTime at the time this VP cross-connect entered its current operational state in the low to high
direction.
5.15.4.8.10 atmVpCrossConnectH2LLastChange
The value of sysUpTime at the time this VP cross-connect entered its current operational in the high to low direction.
5.15.4.8.11 atmVpCrossConnectRowStatus
The status of this entry in the atmVpCrossConnectTable. This object is used to create a cross-connect for crossconnecting VPLs which are created using the atmVplTable or to change or delete an existing cross-connect. This
object must be initially set to “createAndWait” or “createAndGo.” To turn on a VP cross-connect, the
atmVpCrossConnectAdminStatus is set to “up.”
The MIB recommended default value for this object is { createAndWait }.
5.15.4.9
atmVcCrossConnectIndexNext
This object contains an appropriate value to be used for atmVcCrossConnectIndex when creating entries in the
atmVcCrossConnectTable. The value 0 indicates that no unassigned entries are available. To obtain the
atmVcCrossConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to
obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned
index. After a manager retrieves a value the agent will determine through its local policy when this index value is
made available for reuse.
OID:
•
atmVcCrossConnectIndexNext
- { atmMIBObjects 10 }
1.3.6.1.2.1.10.37.1.10
5.15.4.10 atmVcCrossConnectTable
The ATM Virtual Channel (VC) Cross Connect Table contains configuration and state information of point-to-point,
point-to-multipoint or multipoint-to-multipoint VC cross-connects for PVCs. An entry in the ATM VC Cross
Connect table is used to model a bi-directional ATM VC cross-connect cross-connecting two end points
This table has read-create access and is used to cross-connect the VCLs together in an ATM switch or network that
belong to a VC connection. The atmVcCrossConnectIndex is used to associate the related VCLs that are cross-
337
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
connected together.
The model using step-wise procedures described for setting up a VP cross-connect is also used for setting up a VC
cross-connect.
This table is a sequence of atmVcCrossConnectEntry and is indexed by atmVcCrossConnectIndex,
atmVcCrossConnectLowIfIndex, atmVcCrossConnectLowVpi, atmVcCrossConnectLowVci,
atmVcCrossConnectHighIfIndex, atmVcCrossConnectHighVpi, and atmVcCrossConnectHighVci objects.
An entry in this table models two cross-connected VCLs. Each VCL must have its atmConnKind set to pvc(1).
•
Step-wise Procedures to set up a VC Cross-connect
Once the entries in the atmVclTable are created, the following procedures are used to cross-connect the
VCLs together to form a VCC segment.
1.
2.
•
The manager obtains a unique atmVcCrossConnectIndex by reading the atmVcCrossConnectIndexNext
object.
Next, the manager creates a set of one or more rows in the ATM VC Cross Connect Table, one for each
cross-connection between two VCLs. Each row is indexed by the ATM interface port numbers and VPI/VCI
values of the two ends of that cross-connection. This set of rows specifies the topology of the VCC crossconnect and is identified by a single value of atmVcCrossConnectIndex.
Negotiated VC Cross-Connect Establishment
2a. The manager creates a row in this table by setting atmVcCrossConnectRowStatus to createAndWait(5).
The agent checks the requested topology and the mutual sanity of the ATM traffic parameters and
service categories, that is, the row creation fails if:
•the requested topology is incompatible with associated values of atmVclCastType,
•the requested topology is not supported by the agent,
•the traffic/service category parameter values associated with the requested row are incompatible with
those of already existing rows for this VC cross-connect.
[For example, for setting up a point-to-point VC cross-connect, the ATM traffic parameters in the
receive direction of a VCL at the low end of the cross-connect must equal to the traffic parameters in the
transmit direction of the other VCL at the high end of the cross-connect, otherwise, the row creation
fails.] The agent also checks for internal errors in building the cross-connect.
The atmVcCrossConnectIndex values in the corresponding atmVclTable rows are filled in by the agent
at this point.
2b. The manager promotes the row in the atmVcCrossConnectTable by setting
atmVcCrossConnectRowStatus to active(1). If this set is successful, the agent has reserved the resources
specified by the ATM traffic parameter and Service category values for each direction of the VC crossconnect in an ATM switch or network.
3.
•
The manager sets the atmVcCrossConnectAdminStatus to up(1) in all rows of this VC cross-connect to turn
the traffic flow on.
One-Shot VC Cross-Connect Establishment
A VC cross-connect may also be established in one step by a set-request with all necessary parameter values
and atmVcCrossConnectRowStatus set to createAndGo(4).
In contrast to the negotiated VC cross-connect establishment which allows for detailed error checking that
is, set errors are explicitly linked to particular resource acquisition failures), the one-shot VC cross-connect
338
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
establishment performs the setup on one operation but does not have the advantage of step-wise error
checking.
•
VC Cross-Connect Retirement
A VC cross-connect identified by a particular value of atmVcCrossConnectIndex is released by:
1.
2.
•
Setting atmVcCrossConnectRowStatus of all rows identified by this value of atmVcCrossConnectIndex to
destroy(6). The agent may release all associated resources, and the atmVcCrossConnectIndex values in the
corresponding atmVclTable row are removed. Note that a situation when only a subset of the associated
rows are deleted corresponds to a VC topology change.
After deletion of the appropriate atmVcCrossConnectEntries, the manager may set atmVclRowStatus to
destroy(6) the associated VCLs. The agent releases the resources and removes the associated rows in the
atmVclTable.
VC Cross-Connect Reconfiguration
At the discretion of the agent, a VC cross-connect may be reconfigured by adding and/or deleting leafs to/
from the VC topology as per the VC cross-connect establishment/retirement procedures. Reconfiguration of
traffic/service category parameter values requires release of the VC cross-connect before those parameter
values may by changed for individual VCLs.
Index(es):
•
•
•
•
•
•
•
atmVcCrossConnectIndex
atmVcCrossConnectLowIfIndex
atmVcCrossConnectLowVpi
atmVcCrossConnectLowVci
atmVcCrossConnectHighIfIndex
atmVcCrossConnectHighVpi
atmVcCrossConnectHighVci
OIDs:
•
•
atmVcCrossConnectTable - { atmMIBObjects 11 }
atmVcCrossConnectEntry - { atmVcCrossConnectTable 1}
1.3.6.1.2.1.10.37.1.11
1.3.6.1.2.1.10.37.1.11.1
Table 171: atmVcCrossConnectTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
atmVcCrossConnectIndex
{ atmVcCrossConnectEntry 1 }
INTEGER
(1…2147483647)
not-accessible
current
N
atmVcCrossConnectLowIfIndex
{ atmVcCrossConnectEntry 2 }
InterfaceIndex
not-accessible
current
N
atmVcCrossConnectLowVpi
{ atmVcCrossConnectEntry 3 }
AtmVpIdentifier
not-accessible
current
N
atmVcCrossConnectLowVci
{ atmVcCrossConnectEntry 4 }
AtmVcIdentifier
not-accessible
current
N
atmVcCrossConnectHighIfIndex
{ atmVcCrossConnectEntry 5 }
InterfaceIndex
not-accessible
current
N
atmVcCrossConnectHighVpi
{ atmVcCrossConnectEntry 6 }
AtmVpIdentifier
not-accessible
current
N
atmVcCrossConnectHighVci
{ atmVcCrossConnectEntry 7 }
AtmVcIdentifier
not-accessible
current
N
339
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Table 171: atmVcCrossConnectTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
atmVcCrossConnectAdminStatus
{ atmVcCrossConnectEntry 8 }
AtmVorXAdminStatus
read-create
current
N
atmVcCrossConnectL2HOperStatus
{ atmVcCrossConnectEntry 9 }
AtmVorXOperStatus
read-only
current
N
atmVcCrossConnectH2LOperStatus
{ atmVcCrossConnectEntry 10 }
AtmVorXOperStatus
read-only
current
N
atmVcCrossConnectL2HLastChange
atmVcCrossConnectEntry 11 }
AtmVorXLastChange
read-only
current
N
atmVcCrossConnectH2LLastChange
atmVcCrossConnectEntry 12 }
AtmVorXLastChange
read-only
current
N
atmVcCrossConnectRowStatus
atmVcCrossConnectEntry 13 }
RowStatus
read-create
current
N
5.15.4.10.1 atmVcCrossConnectIndex
A unique value to identify this VC cross-connect. For each VCL associated with this cross-connect, the agent reports
this cross-connect index value in the atmVclCrossConnectIdentifier attribute of the corresponding atmVclTable
entries.
5.15.4.10.2 atmVcCrossConnectLowIfIndex
The ifIndex value of the ATM interface for this VC cross-connect. The term low implies that this ATM interface has
the numerically lower ifIndex value than the other ATM interface identified in the same atmVcCrossConnectEntry.
5.15.4.10.3 atmVcCrossConnectLowVpi
The VPI value at the ATM interface associated with the VC cross-connect that is identified by
atmVcCrossConnectLowIfIndex.
5.15.4.10.4 atmVcCrossConnectLowVci
The VCI value at the ATM interface associated with this VC cross-connect that is identified by
atmVcCrossConnectLowIfIndex.
5.15.4.10.5 atmVcCrossConnectHighIfIndex
The ifIndex value for the ATM interface for this VC cross-connect. The term high implies that this ATM interface has
the numerically higher ifIndex value than the other ATM interface identified in the same atmVcCrossConnectEntry.
5.15.4.10.6 atmVcCrossConnectHighVpi
The VPI value at the ATM interface associated with the VC cross-connect that is identified by
atmVcCrossConnectHighIfIndex.
5.15.4.10.7 atmVcCrossConnectHighVci
The VCI value at the ATM interface associated with the VC cross-connect that is identified by
atmVcCrossConnectHighIfIndex.
5.15.4.10.8 atmVcCrossConnectAdminStatus
The desired administrative status of this bi-directional VC cross-connect.
340
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
The MIB recommended default value for this object is { down }.
5.15.4.10.9 atmVcCrossConnectL2HOperStatus
The current operational status of the VC cross-connect in one direction; (that is, from the low to high direction).
5.15.4.10.10 atmVcCrossConnectH2LOperStatus
The current operational status of the VC cross-connect in one direction; (that is, from the high to low direction).
5.15.4.10.11 atmVcCrossConnectL2HLastChange
The value of sysUpTime at the time this VC cross-connect entered its current operational state in low to high
direction.
5.15.4.10.12 atmVcCrossConnectH2LLastChange
The value of sysUpTime at the time this VC cross-connect entered its current operational state in high to low
direction.
5.15.4.10.13 atmVcCrossConnectRowStatus
The status of this entry in the atmVcCrossConnectTable. This object is used to create a new cross-connect for crossconnecting VCLs which are created using the atmVclTable or to change or delete existing cross-connect. This object
must be initially set to “createAndWait” or “createAndGo.” To turn on a VC cross-connect, the
atmVcCrossConnectAdminStatus is set to “up.”
The MIB recommended default value for this object is { createAndWait }.
5.15.4.11 aal5VccTable
The AAL5 Virtual Channel Connection Performance Statistics Table contains the AAL5 performance statistics of a
VCC at the interface associated with an AAL5 entity in an ATM host or ATM switch.
This table is a sequence of aal5VccEntry which contains the AAL5 VCC performance parameters.
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
aal5VccVpi
aal5VccVci
OIDs:
•
•
aal5VccTable - { atmMIBObjects 12 }
aal5VccEntry - { aal5VccTable 1}
1.3.6.1.2.1.10.37.1.12
1.3.6.1.2.1.10.37.1.12.1
Table 172: aal5VccTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
aal5VccVpi
{ aal5VccEntry 1 }
AtmVpIdentifier
not-accessible
current
Y
aal5VccVci
{ aal5VccEntry 2 }
AtmVcIdentifier
not-accessible
current
Y
341
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-MIB — RFC 2515
Table 172: aal5VccTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
aal5VccCrcErrors
{ aal5VccEntry 3 }
Counter32
read-only
current
Y
aal5VccSarTimeOuts
{ aal5VccEntry 4 }
Counter32
read-only
current
Y
aal5VccOverSizedSDUs
{ aal5VccEntry 5 }
Counter32
read-only
current
Y
5.15.4.11.1 aal5VccVpi
The VPI value of the AAL5 VCC at the interface identified by the ifIndex.
5.15.4.11.2 aal5VccVci
The VCI value of the AAL5 VCC at the interface identified by the ifIndex.
5.15.4.11.3 aal5VccCrcErrors
The number of AAL5 CPCS PDUs received with CRC-32 errors on this AAL5 VCC at the interface associated with
an AAL5 entity.
5.15.4.11.4 aal5VccSarTimeOuts
The number of partially re-assembled AAL5 CPCS PDUs which were discarded on this AAL5 VCC at the interface
associated with an AAL5 entity because they were not fully re-assembled within the required time period. If the reassembly timer is not supported, then this object contains a zero value.
5.15.4.11.5 aal5VccOverSizedSDUs
The number of AAL5 CPCS PDUs discarded on this AAL5 VCC at the interface associated with an AAL5 entity
because the AAL5 SDUs were too large.
5.15.4.12 atmTrafficDescrParamIndexNext
OID:
•
atmTrafficDescrParamIndexNext
- { atmMIBObjects 13 }
1.3.6.1.2.1.10.37.1.13
This object contains an appropriate value to be used for atmTrafficDescrParamIndex when creating entries in the
atmTrafficDescrParamTable. The value 0 indicates that no unassigned entries are available. To obtain the
atmTrafficDescrParamIndex value for a new entry, the manager issues a management protocol retrieval operation to
obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned
index. After a manager retrieves a value the agent will determine through its local policy when this index value is
made available for reuse.
This object may be used in conjunction with the atmTrafficDescrParamTable for the creation of new table entries.
342
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-FORUM-SNMP-M4-MIB — AF-NM-0095.001
5.16 ATM-FORUM-SNMP-M4-MIB — AF-NM-0095.001
5.16.1
Introduction
This MIB describes objects for managing the ATM Forum’s M4 interface. The AF-NM-0095.001 document used as a
reference was dated July 1998. The LAST-UPDATED for the atmfM4MIB was “9805140000Z.”
5.16.2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
5.16.3
OIDs
iso
org
dod
internet
private
enterprise
atmForum
atmForumNetworkManagement
atmfM4
atmfM4SnmpNEView
atmfM4MIB
atmfM4MIBObjects
atmfM4TcAdapterTable
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 4 }
{ private 4 }
{ enterprises 353 }
{ atmForum 5 }
{ atmForumNetworkManagement 1 }
{ atmfM4 3 }
{ atmfM4SnmpNEView 1 }
{ atmfM4MIB 1 }
{ atmfM4MIBObjects 7 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.4
1.3.6.1.4.4
1.3.6.1.4.4.353
1.3.6.1.4.4.353.5
1.3.6.1.4.4.353.5.1
1.3.6.1.4.4.353.5.1.3
1.3.6.1.4.4.353.5.1.3.1
1.3.6.1.4.4.353.5.1.3.1.1
1.3.6.1.4.4.353.5.1.3.1.1.7
mgmt
mib-2
transmission
atmMIB
atmMIBObjects
-
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ mib-2 37 }
{ atmMIB 1 }
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.37
1.3.6.1.2.1.10.37.1
MIB Objects
Only the atmfM4TcACellScrambling object which is part of the atmfM4TcAdapterTable is supported in this MIB.
The table below lists objects supported in this MIB. Objects that are not listed are not supported.
Table 173: ATM-FORUM-SNMP-M4-MIB Objects
Object
OID
Syntax
Access
Status
atmfM4TcAdaptorTable
{ atmfM4MIBObjects 7 }
SEQUENCE OF
atmfM4TcAdaptorEntry
not-accessible
current
atmfMCellProtoCurrTable
{ pdnAtmM4ExtMIBObjects 15 }
SEQUENCE OF
pdnAtmfM4CellProtoCurrEntry
not-accessible
current
atmfM4CellProtoHistTable
{ pdnAtmM4ExtMIBObjects 16 }
SEQUENCE OF
pdnAtmfM4CellProtoHistEntry
not-accessible
current
5.16.3.1
atmfM4TcAdapterTable
Table to configure extensions for the TC Adapter. This table consists of a sequence of atmfM4AdapterEntry which
343
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-FORUM-SNMP-M4-MIB — AF-NM-0095.001
contains the TC Adapter fields.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
atmfM4TcAdapterTable
atmfM4TcAdapterEntry
- { atmfM4MIBObjects 7 }
- { atmfM4TcAdapterTable 1}
1.3.6.1.4.4.353.5.1.3.1.1.7
1.3.6.1.4.4.353.5.1.3.1.1.7.1
Table 174: atmfM4PhysPathTpTable
Object
OID
Syntax
Access
Status
atmfM4TcACellScrambling
{ atmfM4TcAdapterEntry 1 }
TruthValue
read-write
current
5.16.3.1.1
atmfM4TcACellScrambling
This object allows the ATM cell scrambling function to be enabled or disabled.
•
•
true(1)
false(2)
- Cell scrambling is activated
- Cell scrambling is not activated
This object defaults to true(1).
5.16.3.2
atmfM4CellProtoCurrTable
The ATM Forum M4 Cell Protocol Monitoring Current Data table. This table maintains per-interface statistics for the
fifteen-minute interval currently being collected. Each ATM interface (UNI, BICI, BISSI) automatically has an entry
in this table associated with it.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
atmfM4CellProtoCurrTable - { atmfM4MIBObjects 15 }
atmfM4CellProtoCurrEntry - { atmfM4CellProtoCurrTable 1}
1.3.6.1.4.4.353.5.1.3.1.1.15
1.3.6.1.4.4.353.5.1.3.1.1.15.1
Table 175: atmfM4CellProtoCurrTable (1 of 2)
Object
OID
Syntax
Access
Status
atmfM4CellProtoCurrSuspect
{ atmfM4CellProtoCurrEntry 1 }
TruthValue
read-only
current
atmfM4CellProtoCurrElapsedTime
{ atmfM4CellProtoCurrEntry 2 }
TimeInterval
read-only
current
atmfM4CellProtoCurrSupprIntvls
{ atmfM4CellProtoCurrEntry 3 }
Gauge32
read-only
current
344
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-FORUM-SNMP-M4-MIB — AF-NM-0095.001
Table 175: atmfM4CellProtoCurrTable (2 of 2)
Object
OID
Syntax
Access
Status
atmfM4CellProtoCurrProtoErrors
{ atmfM4CellProtoCurrEntry 4 }
Gauge32
read-only
current
atmfM4CellProtoCurrInOAMCells
{ atmfM4CellProtoCurrEntry 5 }
Gauge32
read-only
current
5.16.3.2.1
atmfM4CellProtoCurrSuspect
If true, the statistics in this entry may be unreliable.
5.16.3.3
atmfM4CellProtoCurrElapsedTime
Amount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been
counted.
5.16.3.3.1
atmfM4CellProtoCurrSupprIntvls
This attribute is non-zero only if the ATM NE is suppressing ATM Cell Protocol Monitoring History Data entry
creation when the current interval terminates with “all-zeroes” performance measurements.
When non-zero, this attribute represents the number of “all-zeroes” intervals that were suppressed immediately prior
to the current interval.
Note that the suppression of “all-zeroes” intervals is controlled by the atmfM4NeSuppressZeroStats object.
5.16.3.3.2
atmfM4CellProtoCurrProtoErrors
The number of ATM cells dropped on this interface, due to an unrecognized field or set of fields in the ATM cell
header, since the start of this interval.
5.16.3.3.3
atmfM4CellProtoCurrInOAMCells
The number of OAM cells received at this interface since the start of this interval.
5.16.3.4
atmfM4CellProtoHistTable
The ATM Forum M4 Cell Protocol Monitoring History Datatable.This table maintains per-interface statistics for
previous fifteen-minute intervals. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table
associated with it for each fifteen-minute interval in which statistics are collected for it.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmfM4CellProtoHistIndex
OIDs:
•
•
atmfM4CellProtoHistTable - { atmfM4MIBObjects 16 }
atmfM4CellProtoHistEntry - { atmfM4CellProtoHistTable 1}
345
1.3.6.1.4.4.353.5.1.3.1.1.16
1.3.6.1.4.4.353.5.1.3.1.1.16.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
ATM-FORUM-SNMP-M4-MIB — AF-NM-0095.001
Table 176: atmfM4CellProtoHistTable
Object
OID
Syntax
Access
Status
atmfM4CellProtoHistIndex
{ atmfM4CellProtoHistEntry 1 }
INTEGER(1…96)
not-accessible
current
atmfM4CellProtoHistSuspect
{ atmfM4CellProtoHistEntry 2 }
TruthValue
read-only
current
atmfM4CellProtoHistElapsedTime
{ atmfM4CellProtoHistEntry 3 }
TimeInterval
read-only
current
atmfM4CellProtoHistSupprIntvls
{ atmfM4CellProtoHistEntry 4 }
Gauge32
read-only
current
atmfM4CellProtoHistProtoErrors
{ atmfM4CellProtoHistEntry 5 }
Gauge32
read-only
current
atmfM4CellProtoHistInOAMCells
{ atmfM4CellProtoHistEntry 6 }
Gauge32
read-only
current
5.16.3.4.1
atmfM4CellProtoHistIndex
A number between 1 and 96, which identifies the interval for which the set of statistics in this entry was collected.
The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the
interval immediately preceding the one identified by N-1.
5.16.3.4.2
atmfM4CellProtoHistSuspect
If true, the statistics in this entry may be unreliable.
5.16.3.4.3
atmfM4CellProtoHistElapsedTime
Amount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been
counted.
5.16.3.4.4
atmfM4CellProtoHistSupprIntvls
This attribute is non-zero only if the ATM NE is suppressing ATM Cell Protocol Monitoring History Data entry
creation when the current interval terminates with “all-zeroes” performance measurements.
When non-zero, this attribute represents the number of “all-zeroes” intervals that were suppressed immediately prior
to this “non-all-zeroes” history interval.
Note that the suppression of “all-zeroes” intervals is controlled by the atmfM4NeSuppressZeroStats object.
5.16.3.4.5
atmfM4CellProtoHistProtoErrors
The number of ATM cells dropped on this interface, due to an unrecognized field or set of fields in the ATM cell
header, during this interval.
5.16.3.4.6
atmfM4CellProtoHistInOAMCells
The number of OAM cells received at this interface during this interval.
346
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
5.17 BRIDGE-MIB — RFC 1493
5.17.1
Introduction
This MIB defines objects for managing MAC bridges based on the IEEE 802.1D standard between Local Area
Network (LAN) segments. The RFC used as a reference was dated July 1993.
5.17.2
Textual Conventions
The following definitions are made in this RFC:
•
MacAddress
- A 6 octet address in the “canonical” order defined by IEEE 802.1a,
that is, as it were transmitted least significant bit first
— Syntax
OCTET STRING ( SIZE (6) )
•
BridgeId
- The Bridge-Identifier as used in the Spanning Tree Protocol to uniquely
identify a bridge.
— Syntax
OCTET STRING ( SIZE (8) )
•
Timeout
- A Spanning Tree Protocol timer in units of 1/100 seconds.
— Syntax
INTEGER
5.17.3
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
dot1dBridge
dot1dBase
dot1dStp
dot1dSr
dot1dTp
dot1dStatic
5.17.4
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 17 }
{ dot1dBridge 1 }
{ dot1dBridge 2 }
{ dot1dBridge 3 }
{ dot1dBridge 4 }
{ dot1dBridge 5 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.17
1.3.6.1.2.1.17.1
1.3.6.1.2.1.17.2
1.3.6.1.2.1.17.3
1.3.6.1.2.1.17.4
1.3.6.1.2.1.17.5
The following groups are defined in this MIB:
Table 177: BRIDGE-MIB Objects (1 of 2)
Groups
OID
Description
Supported
dot1dBase
{ dot1dBridge 1 }
This group contains objects which are applicable to all types of
bridges.
Y
dot1dStp
{ dot1dBridge 2 }
This group contains the objects that denote the bridge’s state with
respect to the Spanning Tree Protocol.
N
dot1dSr
{ dot1dBridge 3 }
This group contains the objects that describe the entity’s state with
respect to source route bridging.
N
347
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
Table 177: BRIDGE-MIB Objects (2 of 2)
Groups
OID
Description
Supported
dot1dTp
{ dot1dBridge 4 }
This group contains objects that describe the entity’s state with
respect to transparent bridging.
Y
dot1dStatic
{ dot1dBridge 5 }
This group contains objects that describe the entity’s state with
respect to destination-address filtering.
Y
5.17.4.1
dot1dBase Group
OID:
•
dot1dBase
- { dot1dBridge 1 } 1.3.6.1.2.1.17.1
Table 178: dot1dBase Group
Object
OID
Syntax
Access
Status
Supported
dot1dBaseBridgeAddress
{ dot1dBase 1 }
MacAddress
read-only
mandatory
N
dot1dBaseNumPorts
{ dot1dBase 2 }
INTEGER
read-only
mandatory
Y
dot1dBaseType
{ dot1dBase 3 }
INTEGER
unknown (1)
transparent-only (2)
sourceroute-only (3)
srt (4)
read-only
mandatory
Y
dot1dBasePortTable
{ dot1dBase 4 }
SEQUENCE of
dot1dBasePortEntry
not-accessible
mandatory
Y
5.17.4.1.1
dot1dBaseBridgeAddress
The MAC address used by this bridge when it must be referred to in a unique fashion. It is recommended that this be
the numerically smallest MAC address of all ports that belong to this bridge. However it is only required to be unique.
When concatenated with dot1dStpPriority a unique BridgeIdentifier is formed which is used in the Spanning tree
protocol.
Valid Object Value(s)
This object will not be supported as there is no MAC address for a bridge in the BitStorm 2600 and GranDSLAM
4200 IP DSLAM.
348
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
5.17.4.1.2
dot1dBaseNumPorts
The number of ports controlled by this bridging entity.
Valid Object Value(s)
Each chassis has the following bridge ports:
•
•
Ethernet Port(s)
ADSL Ports
•
Management Ports
- 3
- 384
Each DSL Port has 8 connections to the Bridge.
(48 DSL Ports * 8 Connections to the Bridge = 384 Bridge Ports)
- 2
Which gives a total of 389 bridge ports.
5.17.4.1.3
dot1dBaseType
Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging
this is indicated by entries in the port table for the given type.
•
•
•
•
unknown(1)
transparent-only(2)
soureceroute-only(3)
srt(4)
Valid Object Value(s)
This object will always return the transparent-only(2) value.
5.17.4.1.4
dot1dBasePortTable
This is a generic bridge port table that contains generic information about every port that is associated with this
bridge. Transparent, source-route, and srt ports are included.
Index(es):
•
dot1dBasePort
OIDs:
•
•
dot1dBasePortTable
dot1dBasePortEntry
- { dot1dBase 4 }
- { dot1dBasePortTable 1 }
1.3.6.1.2.1.17.1.4
1.3.6.1.2.1.17.1.4.1
Table 179: dot1dBasePortTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1dBasePort
{ dot1dBasePortEntry 1 }
INTEGER (1…65535)
read-only
mandatory
Y
dot1dBasePortIfIndex
{ dot1dBasePortEntry 2 }
INTEGER
read-only
mandatory
Y
dot1dBasePortCircuit
{ dot1dBasePortEntry 3 }
OBJECT IDENTIFIER
read-only
mandatory
Y
dot1dBasePortDelayExceededDiscards
{ dot1dBasePortEntry 4 }
Counter
read-only
mandatory
N
349
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
Table 179: dot1dBasePortTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1dBaseMtuExceededDiscards
{ dot1dBasePortEntry 5 }
Counter
read-only
mandatory
N
5.17.4.1.4.1
dot1dBasePort
The port number of the port for which this entry contains bridge management information.
5.17.4.1.4.2
dot1dBasePortIfIndex
The value of this instance of the ifIndex (Section 5.3.4.3.1, Page 39) object, defined in MIB-II, for the interface
corresponding to this port.
5.17.4.1.4.3
dot1dBasePortCircuit
For a port which (potentially) has the same value of dot1dBasePortIfIndex as another port on the same bridge, this
object contains the name of an object instance unique to this port. For example, in the case where multiple ports co
respond one- to-one with multiple X.25 virtual circuits, this value might identify an (for example, the first) object
instance associated with the X.25 virtual circuit corresponding to this port.
For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value { 0 0 }.
Valid Object Value(s)
Bridge ports do not necessarily have the same ifIndex. For example, for each DSL Port, there a 8 Bridge Ports (1 per
Priority Inter-Working Group). As a result, the following are defined for this object:
Company Enterprise.a
1.14.17.7
ips-dot1dBasePortCircuit
1.14.17.7.1
ips-piwg-1
1.14.17.7.2
ips-piwg-2
1.14.17.7.3
ips-piwg-3
1.14.17.7.4
ips-piwg-4
1.14.17.7.5
ips-piwg-5
1.14.17.7.6
ips-piwg-6
1.14.17.7.7
ips-piwg-7
1.14.17.7.8
ips-piwg-8
a. Refer to Section 5.2.3.1.2, Page 24, for a definition of Company Enterprise.
Figure 7. dot1dBasePortCircuit Values
5.17.4.1.4.4
dot1dBasePortDelayExceededDiscards
The number of frames discarded by this port due to excessive transit delay through the bridge. It is incremented by
both transparent and source route bridges.
350
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
5.17.4.1.4.5
dot1dBasePortMtuExceededDiscards
The number of frames discarded by this port due to an excessive size. It is incremented by both transparent and source
route bridges.
5.17.4.2
dot1dStp Group
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM do not support the Spanning Tree Protocol so this group is
not supported.
5.17.4.3
dot1dSr Group
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM do not support source route bridging so this group is not
supported.
5.17.4.4
dot1dTp Group
OID:
•
dot1dTp
- { dot1dBridge 4 }
1.3.6.1.2.1.17.4
Table 180: dot1dTp Group
Object
OID
Syntax
Access
Status
Supported
dot1dTpLearnedEntityDiscards
{ dot1dTp 1 }
Counter
read-only
mandatory
N
dot1dTpAgingTime
{ dot1dTp 2 }
INTEGER (10…1000000)
read-write
mandatory
Y
dot1dTpFdbTable
{ dot1dTp 3 }
SEQUENCE of dot1dTpFdbEntry
not-accessible
mandatory
Y
dot1dTpPortTable
{ dot1dTp 4 }
SEQUENCE of dot1dTpPortEntry
not-accessible
mandatory
Y
5.17.4.4.1
dot1dTpLearnedEntryDiscards
The total number of Forwarding Database entries, which have been or would have been learnt, but have been
discarded due to a lack of space to store them in the Forwarding Database. If this counter is increasing, it indicates
that the Forwarding Database is regularly becoming full (a condition which has unpleasant performance effects on the
subnetwork). If this counter has a significant value but is not presently increasing, it indicates that the problem has
been occurring but is not persistent.
5.17.4.4.2
dot1dTpAgingTime
The timeout period in seconds for aging out dynamically learned forwarding information. 802.1D-1990 recommends
a default of 300 seconds.
This object will default to 300 seconds.
5.17.4.4.3
dot1dTpFdbTable
The Forwarding Database for Transparent Bridges is a table that contains information about unicast entries for which
the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function
in determining how to propagate a received frame.
351
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
Each entry contains information about a specific unicast MAC address for which the bridge has some forwarding
and/or filtering information.
This table reports MAC addresses learned on each port, regardless of which Filtering Database they have been learnt
in. If an address has been learnt in multiple databases on a single port, report it only once. If an address has been
learnt in multiple databases on more than one port, report the entry on any one of the valid ports.
Index(es):
•
dot1dTpFdbAddress
OIDs:
•
•
dot1dTpFdbTable
dot1dTpFdbEntry
- { dot1dTp 3 }
- { dot1dTpFdbTable 1 }
1.3.6.1.2.1.17.4.3
1.3.6.1.2.1.17.4.3.1
Table 181: dot1dTpFdbTable
Object
OID
Syntax
Access
Status
Supported
dot1dTpFdbAddress
{ dot1dTpFdbEntry 1 }
MacAddress
read-only
mandatory
Y
dot1dTpFdbPort
{ dot1dTpFdbEntry 2 }
INTEGER
read-only
mandatory
Y
dot1dTpFdbStatus
{ dot1dTpFdbEntry 3 }
INTEGER
other (1)
invalid (2)
learned (3)
self (4)
mgmt (5)
read-only
mandatory
Y
5.17.4.4.3.1
dot1dTpFdbAddress
A unicast MAC address for which the bridge has forwarding and/or filtering information.
5.17.4.4.3.2
dot1dTpFdbPort
Either the value “0,” or the port number of the port on which a frame having a source address equal to the value of the
corresponding instance of dot1dTpFdbAddress has been seen. A value of “0” indicates that the port number has not
been learned but that the bridge does have some forwarding/filtering information about this address (for example, in
the dot1dStaticTable). Implementors are encouraged to assign the port value to this object whenever it is learned even
for addresses for which the corresponding value of dot1dTpFdbStatus is not learned(3).
5.17.4.4.3.3
dot1dTpFdbStatus
The status of this entry in the table. The meanings of the values are:
•
other(1)
- none of the following. This would include the case where some other MIB object (not the
corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticTable) is being
used to determine if and how frames addressed to the value of the corresponding instance of
dot1dTpFdbAddress are being forwarded.
352
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
•
invalid(2)
•
•
learned(3)
self(4)
•
mgmt(5)
5.17.4.4.4
- this entry is not longer valid (for example, it was learned but has since aged-out), but has not
yet been flushed from the table.
- the value of the corresponding instance of dot1dTpFdbPort was learned, and is being used.
- the value of the corresponding instance of dot1dTpFdbAddress represents one of the
bridge’s addresses. The corresponding instance of dot1dTpFdbPort indicates which of the
bridge’s ports has this address.
- the value of the corresponding instance of dot1dTpFdbAddress is also the value of an existing instance of dot1dStaticAddress.
dot1dTpPortTable
The Port Table for Transparent Bridges is table that contains information about every port that is associated with this
transparent bridge.
Each entry is list of information for each port of a transparent bridge. Also, this table is port-based and is not affected
by multiple Filtering Databases or multiple VLANs. The counters should include frames received or transmitted for
all VLANs. Note that equivalent 64-bit port statistics counters, as well as other objects to represent the upper 32 bits
of these counters, are defined in this document for high capacity network interfaces.
Index(es):
•
dot1dTpPort
OIDs:
•
•
dot1dTpPortTable
dot1dTpPortEntry
- { dot1dTp 4 }
- { dot1dTpPortTable 1 }
1.3.6.1.2.1.17.4.4
1.3.6.1.2.1.17.4.4.1
Object
OID
Syntax
Access
Status
Supported
dot1dTpPort
{ dot1dTpPortEntry 1 }
INTEGER
read-only
mandatory
Y
dot1dTpPortMaxInfo
{ dot1dTpPortEntry 2 }
INTEGER
read-only
mandatory
Y
dot1dTpPortInFrames
{ dot1dTpPortEntry 3 }
Counter
read-only
mandatory
Y
dot1dTpPortOutFrames
{ dot1dTpPortEntry 4 }
Counter
read-only
mandatory
Y
dot1dTpPortInDiscards
{ dot1dTpPortEntry 5 }
Counter
read-only
mandatory
Y
Table 182: dot1dTpPortTable
5.17.4.4.4.1
dot1dTpPort
The port number of the port for which this entry information.
5.17.4.4.4.2
dot1dTpPortMaxInfo
The maximum size of the INFO (non-MAC) field that this port will receive or transmit.
Valid Object Value(s)
353
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
This object will return a 1500.
5.17.4.4.4.3
dot1dTpPortInFrames
The number of frames that have been received by this port from its segment. Note that a frame received on the
interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by
the local bridging function, including bridge management frames.
5.17.4.4.4.4
dot1dTpPortOutFrames
The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the
interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by
the local bridging function, including bridge management frames.
5.17.4.4.4.5
dot1dTpPortInDiscards
Count of valid frames received which were discarded (that is, filtered) by the Forwarding Process.
5.17.4.5
dot1dStatic Group
The Static (Destination-Address Filtering) Database Group if fully supported. The following sections provide
clarification for objects contained in this group.
OID:
•
dot1dStatic - { dot1dBridge 5 } 1.3.6.1.2.1.17.5
Table 183: dot1dStatic Group
Object
OID
Syntax
Access
Status
Supported
dot1dStaticTable
{ dot1dStatic 1 }
SEQUENCE of dot1dStaticEntry
not-accessible
mandatory
Y
5.17.4.5.1
dot1dStaticTable
A table containing filtering information configured into the bridge by (local or network) management specifying the
set of ports to which frames received from specific ports and containing specific destination addresses are allowed to
be forwarded. The value of zero in this table as the port number from which frames with a specific destination address
are received, is used to specify all ports for which there is no specific entry in this table for that particular destination
address. Entries are valid for unicast and for group/broadcast addresses.
Each entry consists of filtering information configured into the bridge by (local or network) management specifying
the set of ports to which frames received from a specific port and containing a specific destination address are allowed
to be forwarded. Entries read from this table include all static entries from all of the Filtering Databases. Entries for
the same MAC address and receive port in more than one Filtering Database must appear only once since these are
the indices of this table. This table should be implemented as read-only in devices that support multiple Forwarding
Databases - instead, write access should be provided through dot1qStaticUnicastTable and
dot1qStaticMulticastTable, as defined in this document.
Index(es):
•
•
dot1dStaticAddress
dot1dStaticReceivePort
354
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
OIDs:
•
•
dot1dStaticTable
dot1dStaticEntry
- { dot1dStatic 1 }
- { dot1dStaticTable 1 }
1.3.6.1.2.1.17.5.1
1.3.6.1.2.1.17.5.1.1
Table 184: dot1dStaticTable
Object
OID
Syntax
Accessa
Status
Supported
dot1dStaticAddress
{ dot1dStaticEntry 1 }
MacAddress
read-only
mandatory
Y
dot1dStaticReceivePort
{ dot1dStaticEntry 2 }
INTEGER
read-only
mandatory
Y
dot1dStaticAllowedToGoTo
{ dot1dStaticEntry 3 }
OCTET STRING
read-only
mandatory
Y
dot1dStaticStatus
{ dot1dStaticEntry 4 }
INTEGER
other (1)
invalid (2)
permanent (3)
deleteOnReset (4)
deleteOnTimeout (5)
read-only
mandatory
Y
a. Access restricted to read-only per RFC 2674, dot1dStaticTable section, as captured in paragraph above.
5.17.4.5.1.1
dot1dStaticAddress
The destination MAC address in a frame to which this entry's filtering information applies. This object can take the
value of a unicast address, a group address or the broadcast address.
5.17.4.5.1.2
dot1dStaticReceivePort
Either the value “0,” or the port number of the port from which a frame must be received in order for this entry's
filtering information to apply. A value of zero indicates that this entry applies on all ports of the bridge for which
there is no other applicable entry.
5.17.4.5.1.3
dot1dStaticAllowedToGoTo
The set of ports to which frames received from a specific port and destined for a specific MAC address, are allowed to
be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying
ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit
represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each
port of the bridge is represented by a single bit within the value of this object. If that bit has a value of “1” then that
port is included in the set of ports; the port is not included if its bit has a value of “0.” (Note that the setting of the bit
corresponding to the port from which a frame is received is irrelevant.) The default value of this object is a string of
ones of appropriate received is irrelevant.) The default value of this object is a string of ones of appropriate length.
5.17.4.5.1.4
dot1dStaticStatus
This object indicates the status of this entry. The default value is permanent(3).
•
other(1)
- this entry is currently in use but the conditions under which it will remain so are different from each of the following values.
355
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
BRIDGE-MIB — RFC 1493
•
•
•
•
invalid(2)
permanent(3)
deleteOnReset(4)
deleteOnTimeout(5)
-
writing this value to the object removes the corresponding entry.
this entry is currently in use and will remain so after the next reset of the bridge.
this entry is currently in use and will remain so until the next reset of the bridge.
this entry is currently in use and will remain so until it is aged out.
356
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18 P-BRIDGE-MIB — RFC 2674
5.18.1
Introduction
The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998.
The LAST-UPDATED for this MIB in the RFC was “9908250000Z.”
5.18.2
Textual Conventions
The following textual conventions are made in this RFC:
•
EnabledStatus
5.18.3
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
dot1dBridge
pBridgeMIB
pBridgeMIBObjects
dot1dExtBase
dot1dPriority
dot1dGarp
dot1dGmrp
5.18.4
MIB Objects
- A simple status value for an object.
— INTEGER
• enabled(1)
• disabled(2)
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 17 }
{ dot1dBridge 6 }
{ pBridgeMIB 1 }
{ pBridgeMIBObjects 1 }
{ pBridgeMIBObjects 2 }
{ pBridgeMIBObjects 3 }
{ pBridgeMIBObjects 4 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.17
1.3.6.1.2.1.17.6
1.3.6.1.2.1.17.6.1
1.3.6.1.2.1.17.6.1.1
1.3.6.1.2.1.17.6.1.2
1.3.6.1.2.1.17.6.1.3
1.3.6.1.2.1.17.6.1.4
Table 185: P-BRIDGE-MIB Objects (1 of 2)
Object
OID
Description
Supported
dot1dExtBase
{ pBridgeMIBObjects 1 }
Bridge MIB Extensions Base Group
This group contains the objects which are applicable to all
bridges implementing the traffic class and multicast filtering features of IEEE 802.1D-1998 [802.1D]. It includes per
device configuration of GARP and GMRP protocols
Y
dot1dPriority
{ pBridgeMIBObjects 2 }
Bridge Priority Group
Y
This group contains the objects for configuring and
reporting status of priority-based queuing mechanisms in a
bridge. This includes per-port user_priority treatment,
mapping of user_priority in frames into internal traffic
classes and outbound user_priority and access priority.
357
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
Table 185: P-BRIDGE-MIB Objects (2 of 2)
Object
OID
Description
Supported
dot1dGarp
{ pBridgeMIBObjects 3 }
Generic Attribute Registration Protocol (GARP) Group
This group contains the objects for configuring and reporting on operations of the Generic Attribute Registration Protocol (GARP).
N
dot1dGmrp
{ pBridgeMIBObjects 4 }
GARP Multicast Registration Protocol (GMRP)
This group contains the objects for configuring and reporting on operation of the GARP Multicast Registration Protocol (GMRP).
N
dot1dTp
{ dot1dBridge 4 }
Extension of the Transparent Bridges
This group contains objects that describe the entity’s state
with respect to high capacity transparent bridging. This
group consists primarily the High Capacity Port Table for
Transparent Bridges.
N
5.18.4.1
dot1dExtBase Group
This group contains the objects which are applicable to all bridges implementing the traffic class and multicast
filtering features of IEEE 802.1D-1998 [802.1D]. It includes per device configuration of GARP and GMRP protocols.
OID:
•
dot1dExtBase
- { pBridgeMIBObjects 1 }
1.3.6.1.2.1.17.6.1.1
Table 186: dot1dExtBase Group
Object
OID
Syntax
Access
Status
Supported
dot1dDeviceCapabilities
{ dot1dExtBase 1 }
Bits
dot1dExtendedFilteringServices(0)
dot1dTrafficClasses(1)
dot1qStaticEntryIndividualPort(2)
dot1qIVLCapable(3)
dot1qSVLCapable(4)
dot1qHybridCapable(5)
dot1qConfigurablePvidTagging(6)
dot1dLocalVlanCapable(7)
read-only
current
Y
dot1dTrafficClassesEnabled
{ dot1dExtBase 2 }
TruthValue
read-write
current
Y
dot1dGmrpStatus
{ dot1dExtBase 3 }
EnabledStatus
read-onlya
current
Y
dot1dPortCapabilitiesTable
{ dot1dExtBase 4 }
SEQUENCE of
dot1dPortCapabilitiesEntry
not-accessible
current
Y
a. Product imposed limit.
358
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.4.1.1
dot1dDeviceCapabilities
Indicates the optional parts of IEEE 802.1D and 802.1Q that are implemented by this device and are manageable
through this MIB. Capabilities that are allowed on a per-port basis are indicated in dot1dPortCapabilities.
The following are definitions for this objects’ syntax:
•
dot1dExtendedFilteringServices(0)
•
•
dot1dTrafficClasses(1)
dot1qStaticEntryIndividualPort(2)
•
•
•
•
dot1qIVLCapable(3)
dot1qSVLCapable(4)
dot1qHybridCapable(5)
dot1qConfigurablePvidTagging(6)
•
dot1dLocalVlanCapable(7)
- can perform filtering of individual multicast addresses controlled by
GMRP.
- can map user priority to multiple traffic classes.
- dot1qStaticUnicastReceivePort (Section 5.19.4.3.1.2, Page 384) &
dot1qStaticMulticastReceivePort (Section 5.19.4.3.2.2, Page 385)
can represent non-zero entries.
- Independent VLAN Learning.
- Shared VLAN Learning.
- both IVL & SVL simultaneously.
- whether the implementation supports the ability to override the
default PVID setting and its egress status (VLAN-Tagged or
Untagged) on each port.
- can support multiple local bridges, outside of the scope of 802.1Q
defined VLANs.
Valid Object Value(s)
The following bits should be set:
•
•
•
dot1dTrafficClasses(1)
dot1qIVLCapable(3)
dot1qConfigurablePvidTAgging(6)
5.18.4.1.2
dot1dTrafficClassesEnabled
The value true(1) indicates that Traffic Classes are enabled on this bridge. When false(2), the bridge operates with a
single priority level for all traffic. The default value is true.
Valid Object Value(s)
•
true(1)
5.18.4.1.3
dot1dGmrpStatus
The administrative status requested by management for GMRP. The value enabled(1) indicates that GMRP should be
enabled on this device, in all VLANs, on all ports for which it has not been specifically disabled. When disabled(2),
GMRP is disabled, in all VLANs, on all ports and all GMRP packets are forwarded transparently. This object affects
both Applicant and Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all
GMRP state machines on all ports. The default value is enabled.
Valid Object Value(s)
•
disabled(2)
359
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.4.1.4
dot1dPortCapabilitiesTable
This object is a table that contains capabilities information about every port that is associated with this bridge.
Augments:
•
dot1dBasePortTable (Section 5.17.4.1.4, Page 349)
Index(es):
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1dPortCapabilitiesTable
dot1dPortCapabilitiesEntry
- { dot1dExtBase 4 }
- { dot1dPortCapabilitiesTable 1 }
1.3.6.1.2.1.17.6.1.1.4
1.3.6.1.2.1.17.6.1.1.4.1
Table 187: dot1dPortCapabilitiesTable
Object
OID
Syntax
Access
Status
Supported
dot1dPortCapabilities
{ dot1dPortCapabilitiesEntry 1 }
Bits
dot1qDot1qTagging(0)
dot1qConfigurableAcceptableFrameTypes(1)
dot1qIngressFiltering(2)
dot1qIngressFiltering(2)
read-only
current
Y
5.18.4.1.4.1
dot1dPortCapabilities
Indicates the parts of IEEE 802.1D and 802.1Q that are optional on a per-port basis that are implemented by this
device and are manageable through this MIB.
The following are definitions for this objects’ syntax:
•
•
dot1qDot1qTagging(0)
dot1qConfigurableAcceptableFrameTypes(1)
•
dot1qIngressFiltering(2)
Valid Object Value(s)
The following bits should be set:
•
•
dot1qConfigurableAcceptableFrameTypes(1)
dot1qIngressFiltering(2)
360
- supports 802.1Q VLAN tagging of frames and GVRP.
- allows modified values of
dot1qPortAcceptableFrameTypes (Section 5.19.4.4.5.2,
Page 391).
- supports the discarding of any frame received on a Port
whose VLAN classification does not include that Port in
its Member set.
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.4.2
dot1dPriority Group
This group contains the objects for configuring and reporting status of priority-based queuing mechanisms in a
bridge. This includes per-port user_priority treatment, mapping of user_priority in frames into internal traffic classes
and outbound user_priority and access priority.
OID:
•
dot1dPriority - { pBridgeMIBObjects 2 }
1.3.6.1.2.1.17.6.1.2
Table 188: dot1dPriority Group
Object
OID
Syntax
Access
Status
Supported
dot1dPortPriorityTable
{ dot1dPriority 1 }
SEQUENCE of
dot1dPortPriorityEntry
not-accessible
current
Y
dot1dUserPriorityRegenTable
{ dot1dPriority 2 }
SEQUENCE of
dot1dUserPriorityRegenEntry
not-accessible
current
N
dot1dTrafficClassTable
{ dot1dPriority 3 }
SEQUENCE of
dot1dTrafficClassEntry
not-accessible
current
Y
dot1dPortOutboundAccessPriorityTable
{ dot1dPriority 4 }
SEQUENCE of
dot1dPortOutboundAccessPriorityEntry
not-accessible
current
N
5.18.4.2.1
dot1dPortPriorityTable
The Port Priority Table contains information about every port that is associated with this transparent bridge. Each
entry consists of a list of Default User Priorities for each port of a transparent bridge.
Augments:
•
dot1dBasePortTable (Section 5.17.4.1.4, Page 349)
Index(es):
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1dPortPriorityTable - { dot1dPriority 1 }
dot1dPortPriorityEntry - { dot1dPortPriorityTable 1 }
1.3.6.1.2.1.17.6.1.2.1
1.3.6.1.2.1.17.6.1.2.1.1
Table 189: dot1dPortPriorityTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1dPortDefaultUserPriority
{ dot1dPortPriorityEntry 1 }
INTEGER (0…7)
read-write
current
Y
361
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
Table 189: dot1dPortPriorityTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1dPortNumTrafficClasses
{ dot1dPortPriorityEntry 2 }
INTEGER (1…8)
read-onlya
current
Y
a. Product imposed restriction.
5.18.4.2.1.1
dot1dPortDefaultUserPriority
The default ingress User Priority for this port. This only has effect on media, such as Ethernet, that do not support
native User Priority.
5.18.4.2.1.2
dot1dPortNumTrafficClasses
The number of egress traffic classes supported on this port. This object may optionally be read-only.
Valid Object Value(s)
The BitStorm 2600 and GranDSLAM 4200 IP DSLAM support four egress traffic classes.
5.18.4.2.2
dot1dUserPriorityRegenTable
The User Priority Regeneration Table is a list of Regenerated User Priorities for each received User Priority on each
port of a bridge. The Regenerated User Priority value may be used to index the Traffic Class Table for each input port.
This only has effect on media that support native User Priority. The default values for Regenerated User Priorities are
the same as the User Priorities. Each entry consists of a mapping of incoming User Priority to a Regenerated User
Priority.
Index(es):
•
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
dot1dUserPriority
OIDs:
•
•
dot1dUserPriorityRegenTable - { dot1dPriority 2 }
dot1dUserPriorityRegenEntry - { dot1dUserPriorityRegenTable 1 }
1.3.6.1.2.1.17.6.1.2.2
1.3.6.1.2.1.17.6.1.2.2.1
Table 190: dot1dUserPriorityRegenTable
Object
OID
Syntax
Access
Status
Supported
dot1dUserPriority
{ dot1dUserPriorityRegenEntry 1 }
INTEGER (0…7)
not-accessible
current
N
dot1dRegenUserPriority
{ dot1dUserPriorityRegenEntry 2 }
INTEGER (0…7)
read-write
current
N
362
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.4.2.2.1
dot1dUserPriority
The User Priority for a frame received on this port.
5.18.4.2.2.2
dot1dRegenUserPriority
The Regenerated User Priority the incoming User Priority is mapped to for this port.
5.18.4.2.3
dot1dTrafficClassTable
The Traffic Class Table is a table mapping evaluated User Priority to Traffic Class, for forwarding by the bridge.
Traffic class is a number in the range (0…(dot1dPortNumTrafficClasses [Section 5.18.4.2.1.2, Page 362]-1)).
Index(es):
•
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
dot1dTrafficClassPriority
OIDs:
•
•
dot1dTrafficClassTable
dot1dTrafficClassEntry
- { dot1dPriority 3 }
- { dot1dTrafficClassTable 1 }
1.3.6.1.2.1.17.6.1.2.3
1.3.6.1.2.1.17.6.1.2.3.1
Table 191: dot1dTrafficClassTable
Object
OID
Syntax
Access
Status
Supported
dot1dTrafficClassPriority
{ dot1dTrafficClassEntry 1 }
INTEGER (0…7)
not-accessible
current
Y
dot1dTrafficClass
{ dot1dTrafficClassEntry 2 }
INTEGER (0…7)
read-write
current
Y
5.18.4.2.3.1
dot1dTrafficClassPriority
The Priority value determined for the received frame. This value is equivalent to the priority indicated in
the tagged frame received, or one of the evaluated priorities, determined according to the media-type.
For untagged frames received from Ethernet media, this value is equal to the dot1dPortDefaultUserPriority (Section
5.18.4.2.1.1, Page 362) value for the ingress port.
For untagged frames received from non-Ethernet media, this value is equal to the dot1dRegenUserPriority (Section
5.18.4.2.2.2, Page 363) value for the ingress port and media-specific user priority.
5.18.4.2.3.2
dot1dTrafficClass
The Traffic Class the received frame is mapped to.
Valid Object Value(s)
The table below maps User Priority (dot1dTrafficClassPriority) to Traffic Class (dot1dTrafficClass) default. This
table is extracted from the IEEE 802.1D Standard’s Recommended user priority to traffic class mappings table. The
default mapping is determined based on the product’s support of 4 output classes (queues).
363
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
Table 192: Default dot1dTrafficClass Mapping
User Priority
Number of Available Traffic Classes
5.18.4.2.4
1
2
3
4
5
6
7
8
0 (Default)
0
0
0
1
1
1
1
2
1
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
1
3
0
0
0
1
1
2
2
3
4
0
1
1
2
2
3
3
4
5
0
1
1
2
3
4
4
5
6
0
1
2
3
4
5
5
6
7
0
1
2
3
4
5
6
7
dot1dPortOutboundAccessPriorityTable
The Outbound Access Priority Table is a mapping Regenerated User Priority to Outbound Access Priority. This is a
fixed mapping for all port types, with two options for 802.5 Token Ring. Each entry consists of regenerated User
Priority to Outbound Access Priority mapping.
Index(es):
•
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
dot1dRegenUserPriority
OIDs:
•
•
dot1dPortOutboundAccessPriorityTable
dot1dPortOutboundAccessPriorityEntry
1.3.6.1.2.1.17.6.1.2.4.1
- { dot1dPriority 4 }
1.3.6.1.2.1.17.6.1.2.4
- { dot1dPortOutboundAccessPriorityTable 1 }
Table 193: dot1dPortOutboundAccessPriorityTable
Object
OID
Syntax
Access
Status
Supported
dot1dPortOutboundAccessPriority
{ dot1dPortOutboundAccessPriorityEntry 1 }
INTEGER (0…7)
read-only
current
N
364
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.4.2.4.1
dot1dPortOutboundAccessPriority
The Outbound Access Priority the received frame is mapped to.
5.18.4.3
dot1dGarp Group
This group contains the objects for configuring and reporting on operations of the Generic Attribute Registration
Protocol (GARP).
OID:
•
dot1dGarp
- { pBridgeMIBObjects 3 }
1.3.6.1.2.1.17.6.1.3
Table 194: dot1dGarp Group
Object
OID
Syntax
Access
Status
Supported
dot1dPortGarpTable
{ dot1dGarp 1 }
SEQUENCE of
dot1dPortGarpEntry
not-accessible
current
N
5.18.4.3.1
dot1dPortGarpTable
A table of GARP control information about every bridge port.
Augments:
•
dot1dBasePortTable (Section 5.17.4.1.4, Page 349)
Index(es):
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1dPortGarpTable - { dot1dGarp 1 }
dot1dPortGarpEntry - { dot1dPortGarpTable 1 }
1.3.6.1.2.1.17.6.1.3.1
1.3.6.1.2.1.17.6.1.3.1.1
Table 195: dot1dPortGarpTable
Object
OID
Syntax
Access
Status
Supported
dot1dPortGarpJoinTime
{ dot1dPortGarpEntry 1 }
TimeInterval
read-write
current
N
dot1dPortGarpLeaveTime
{ dot1dPortGarpEntry 2 }
TimeInterval
read-write
current
N
dot1dPortGarpLeaveAllTime
{ dot1dPortGarpEntry 3 }
TimeInterval
read-write
current
N
365
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.4.3.1.1
dot1dPortGarpJoinTime
The GARP Join time, in centiseconds.
DEFVAL
- 20
5.18.4.3.1.2
dot1dPortGarpLeaveTime
The GARP Leave time, in centiseconds.
DEFVAL
- 60
5.18.4.3.1.3
dot1dPortGarpLeaveAllTime
The GARP LeaveAll time, in centiseconds.
DEFVAL
5.18.4.4
- 1000
dot1dGmrp Group
This group contains the objects for configuring and reporting on operations of the Generic Attribute Registration
Protocol (GARP).
OID:
•
dot1dGmrp
- { pBridgeMIBObjects 4 }
1.3.6.1.2.1.17.6.1.4
Table 196: dot1dGmrp Group
Object
OID
Syntax
Access
Status
Supported
dot1dPortGmrpTable
{ dot1dGmrp 1 }
SEQUENCE of
dot1dPortGmrpEntry
not-accessible
current
N
5.18.4.4.1
dot1dPortGmrpTable
A table of GMRP control and status information about every bridge port. Augments the dot1dBasePortTable.
Augments:
•
dot1dBasePortTable (Section 5.17.4.1.4, Page 349)
Index(es):
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1dPortGmrpTable - { dot1dGmrp 1 }
dot1dPortGmrpEntry - { dot1dPortGmrpTable 1 }
366
1.3.6.1.2.1.17.6.1.4.1
1.3.6.1.2.1.17.6.1.4.1.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
Table 197: dot1dPortGmrpTable
Object
OID
Syntax
Access
Status
Supported
dot1dPortGmrpStatus
{ dot1dPortGmrpEntry 1 }
EnabledStatus
read-write
current
N
dot1dPortGmrpFailedRegistrations
{ dot1dPortGmrpEntry 2 }
Counter32
read-only
current
N
dot1dPortGmrpLastPduOrigin
{ dot1dPortGmrpEntry 3 }
MacAddress
read-only
current
N
5.18.4.4.1.1
dot1dPortGmrpStatus
The administrative state of GMRP operation on this port. The value enabled(1) indicates that GMRP is enabled on
this port in all VLANs as long as dot1dGmrpStatus is also enabled(1). A value of disabled(2) indicates that GMRP is
disabled on this port in all VLANs: any GMRP packets received are silently discarded and no GMRP registrations are
propagated from other ports. Setting this to a value of enabled(1) will be stored by the agent but will only take effect
on the GMRP protocol operation if dot1dGmrpStatus also indicates the value enabled(1). This object affects all
GMRP Applicant and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a
reset of all GMRP state machines on this port.
DEFVAL
- enabled
5.18.4.4.1.2
dot1dPortGmrpFailedRegistrations
The total number of failed GMRP registrations, for any reason, in all VLANs, on this port.
5.18.4.4.1.3
dot1dPortGmrpLastPduOrigin
The Source MAC Address of the last GMRP message received on this port.
5.18.4.5
dot1dGmrp Group
This group contains the objects for configuring and reporting on operation of the GARP Multicast Registration
Protocol (GMRP).
Valid Object Value(s)
This group is not supported in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM.
5.18.4.6
dot1dTp Group
This group contains objects that describe the entity’s state with respect to transparent bridging.
OID:
•
dot1dTp
5.18.4.6.1
- { dot1dBridge 4 } 1.3.6.1.2.1.17.4
dot1dTpHCPortTable
The High Capacity Port Table extends the dot1dTp group form the original bridge MIB and contains the objects for
reporting port bridging statistics for high capacity network interfaces. This table contains information about every
367
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
high capacity port that is associated with this transparent bridge.
Index(es):
•
dot1dTpPort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1dTpHCPortTable
dot1dTpHCPortEntry
- { dot1dTp 5 }
- { dot1dTpHCPortTable 1 }
1.3.6.1.2.1.17.4.5
1.3.6.1.2.1.17.4.5.1
Table 198: dot1dTpHCPortTable
Object
OID
Syntax
Access
Status
Supported
dot1dTpHCPortInFrames
{ dot1dTpHCPortEntry 1 }
Counter64
read-only
current
N
dot1dTpHCPortOutFrames
{ dot1dTpHCPortEntry 2 }
Counter64
read-only
current
N
dot1dTpHCPortInDiscards
{ dot1dTpHCPortEntry 3 }
Counter64
read-only
current
N
5.18.4.6.1.1
dot1dTpHCPortInFrames
The number of frames that have been received by this port from its segment. Note that a frame received on the
interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by
the local bridging function, including bridge management frames.
5.18.4.6.1.2
dot1dTpHCPortOutFrames
The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the
interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by
the local bridging function, including bridge management frames.
5.18.4.6.1.3
dot1dTpHCPortInDiscards
Count of valid frames that have been received by this port from its segment which were discarded (that is, filtered) by
the Forwarding Process.
5.18.4.6.2
dot1dTpPortOverflowTable
The Upper part of High Capacity Port Table for Transparent Bridges. This is a table that contains the most-significant
bits of statistics counters for ports that are associated with this transparent bridge that are on high capacity interfaces,
as defined in the conformance clauses for this table. This table is provided as a way to read 64-bit counters for agents
which support only SNMPv1.
Note that the reporting of most-significant and least-significant counter bits separately runs the risk of missing an
overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even
within the same varbindlist, when interpreting the results of a request or asynchronous notification.
This table is a sequence of dot1dTpPortOverflowEntry which consists of the most significant bits of statistics
counters for a high capacity interface of a transparent bridge. Each object is associated with a corresponding object in
dot1dTpPortTable which indicates the least significant bits of the counter.
368
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
Index:
•
dot1dTpPort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1dTpPortOverflowTable - { dot1dTp 6 }
dot1dTpPortOverflowEntry - { dot1dTpPortOverflowTable 1 }
1.3.6.1.2.1.17.4.6
1.3.6.1.2.1.17.4.6.1
Table 199: dot1dTpPortOverflowTable
Object
OID
Syntax
Access
Status
Supported
dot1dTpTpPortInOverflowFrames
{ dot1dTpPortOverflowEntry 1 }
Counter32
read-only
current
N
dot1dTpTpPortOutOverflowFrames
{ dot1dTpPortOverflowEntry 2 }
Counter32
read-only
current
N
dot1dTpTpPortInOverflowDiscards
{ dot1dTpPortOverflowEntry 3 }
Counter32
read-only
current
N
5.18.4.6.2.1
dot1dTpPortInOverflowFrames
The number of times the associated dot1dTpPortInFrames (Section 5.17.4.4.4.3, Page 354) counter has overflowed.
5.18.4.6.2.2
dot1dTpPortOutOverflowFrames
The number of times the associated dot1dTpPortOutFrames (Section 5.17.4.4.4.4, Page 354) counter has overflowed.
5.18.4.6.2.3
dot1dTpPortInOverflowDiscards
The number of times the associated dot1dTpPortInDiscards (Section 5.17.4.4.4.5, Page 354) counter has overflowed.
369
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
5.18.5
Conformance Information
5.18.5.1
Compliance
5.18.5.1.1
pBridgeCompliance
The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
Mandatory Groups:
•
pBridgeExtCapGroup
Optional Groups:
•
pBridgeDeviceGmrpGroup
•
pBridgeDevicePriorityGroup
•
pBridgeDefaultPriorityGroup
•
pBridgeRegenPriorityGroup
•
pBridgePriorityGroup
•
pBridgeAccessPriorityGroup
•
pBridgePortGarpGroup
•
pBridgePortGmrpGroup
•
pBridgeHCPortGroup
•
pBridgePortOverflowGroup
- This group is mandatory for devices supporting the GMRP
application, defined by IEEE 802.1D Extended Filtering Services.
- This group is mandatory only for devices supporting the priority forwarding operations defined by IEEE 802.1D.
- This group is mandatory only for devices supporting the priority forwarding operations defined by the extended bridge services with media types, such as Ethernet, that do not support
native User Priority.
- This group is mandatory only for devices supporting the priority forwarding operations defined by IEEE 802.1D and which
have interface media types that support native User Priority,
such as IEEE 802.5.
- This group is mandatory only for devices supporting the priority forwarding operations defined by IEEE 802.1D.
- This group is optional and is relevant only for devices supporting the priority forwarding operations defined by IEEE 802.1D
and which have interface media types that support native
Access Priority, such as IEEE 802.5.
- This group is mandatory for devices supporting any of the
GARP applications, including GMRP, defined by the extended
filtering services of 802.1D, and GVRP, defined by 802.1Q
(refer to the Q-BRIDGE-MIB for conformance statements for
GVRP).
- This group is mandatory for devices supporting the GMRP
application, as defined by IEEE 802.1D Extended Filtering
Services.
- Support for this group in a device is mandatory for those bridge
ports which map to network interfaces that have the value of
the corresponding instance of ifSpeed greater than 650,000,000
bits/second.
- Support for this group in a device is mandatory for those bridge
ports which map to network interfaces that have the value of
370
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
the corresponding instance of ifSpeed greater than 650,000,000
bits/second.
Objects that have a MIN-ACCESS defined:
•
dot1dPortNumTrafficClasses
•
dot1dTrafficClass
•
dot1dRegenUserPriority
5.18.5.2
- MIN-ACCESS read-only
Write access is not required.
- MIN-ACCESS read-only
Write access is not required.
- MIN-ACCESS read-only
Write access is not required.
Conformance
Table 200: P-BRIDGE-MIB Conformance (1 of 2)
Group
Description
Objects
Supported
pBridgeExtCapGroup
A collection of objects indicating the
optional capabilities of the device.
dot1dDeviceCapabilities
Y
dot1dPortCapabilities
Y
pBridgeDeviceGmrpGroup
A collection of objects providing
device-level control for the Multicast
Filtering extended bridge services.
dot1dGmrpStatus
Y
pBridgeDevicePriorityGroup
A collection of objects providing
device-level control for the Priority
services.
dot1dTrafficClassesEnabled
Y
pBridgeDefaultPriorityGroup
A collection of objects defining the
UserPriority applicable to each port
for media which do not support native
user priority.
dot1dPortDefaultUserPriority
Y
pBridgeRegenPriorityGroup
A collection of objects defining User
Priorities applicable to each port for
media which support native User
Priority.
dot1dRegenUserPriority
N
pBridgePriorityGroup
A collection of objects defining the
traffic classes within a bridge for each
evaluated User Priority.
dot1dPortNumTrafficClasses
Y
dot1dTrafficClass
Y
dot1dPortOutboundAccessPriority
N
pBridgeAccessPriorityGroup
A collection of objects defining the
media dependent outbound access
level for each priority.
371
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
P-BRIDGE-MIB — RFC 2674
Table 200: P-BRIDGE-MIB Conformance (2 of 2)
Group
Description
Objects
Supported
pBridgePortGarpGroup
A collection of objects providing port
level control and status information
for GARP operation.
dot1dPortGarpJoinTime
N
dot1dPortGarpLeaveTime
N
dot1dPortGarpLeaveAllTime
N
dot1dPortGmrpStatus
N
dot1dPortGmrpFailedRegistrations
N
dot1dPortGmrpLastPduOrigin
N
dot1dTpHCPortInFrames
N
dot1dTpHCPortOutFrames
N
dot1dTpHCPortInDiscards
N
dot1dTpPortInOverflowFrames
N
dot1dTpPortOutOverflowFrames
N
dot1dTpPortInOverflowDiscards
N
pBridgePortGmrpGroup
pBridgeHCPortGroup
pBridgePortOverflowGroup
A collection of objects providing port
level control and status information
for GMRP operation.
A collection of objects providing 64bit statistics counters for high
capacity bridge ports.
A collection of objects providing
overflow statistics counters for high
capacity bridge ports.
372
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19 Q-BRIDGE-MIB — RFC 2674
5.19.1
Introduction
The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE 802.1Q1998. The LAST-UPDATED for this MIB in the RFC was “9908250000Z.”
5.19.2
•
Textual Conventions
PortList
- Each octet within this value specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within
each octet, the most significant bit represents the lowest numbered port, and the
least significant bit represents the highest numbered port. Thus, each port of the
bridge is represented by a single bit within the value of this object. If that bit has a
value of “1” then that port is included in the set of ports; the port is not included if
its bit has a value of “0.” Its syntax is an OCTET STRING.
See Implementation Notes on PortList (Section 5.19.2.1.1, Page 373)
•
VlanIndex
- A value used to index per-VLAN tables: values of 0 and 4095 are not permitted; if
the value is between 1 and 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID
with global scope within a given bridged domain (see VlanId textual convention). If
the value is greater than 4095 then it represents a VLAN with scope local to the particular agent, that is one without a global VLAN-ID assigned to it. Such VLANs
are outside the scope of IEEE 802.1Q but it is convenient to be able to manage them
in the same way using this MIB. Its syntax is an Unsigned32.
•
VlanId
- A 12-bit VLAN ID used in the VLAN Tag header. Its syntax is an INTEGER
(1…4094).
5.19.2.1
Implementation Notes
5.19.2.1.1
PortList
Table 201: Implementation for PortList (1 of 2)
373
3
4
5
6
7
8 (LSB)
PIWG 3
PIWG 4
PIWG 5
PIWG 6
PIWG 7
PIWG 8
DSL Port 1
2
1
PIWG 2
Port
1 (MSB)
Octet Nbr.
PIWG 1
Bit Position
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 201: Implementation for PortList (2 of 2)
5.19.3
•
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
dot1dBridge
qBridgeMIB
qBridgeMIBObjects
dot1qBase
dot1qTp
dot1qStatic
dot1qVlan
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 17 }
{ dot1dBridge 7 }
{ qBridgeMIB 1 }
{ qBridgeMIBObjects 1 }
{ qBridgeMIBObjects 2 }
{ qBridgeMIBObjects 3 }
{ qBridgeMIBObjects 4 }
374
8 (LSB)
…
PIWG 8
PIWG 8
7
…
PIWG 7
PIWG 7
6
…
PIWG 6
PIWG 6
5
…
PIWG 5
PIWG 5
4
…
PIWG 4
PIWG 4
3
…
PIWG 3
2
PIWG 2
PIWG 3
Ethernet Port 1…3
0
0
0
0
0
0
0
0
Eth 3
50
…
Management Ethernet Interfaces
PIWG 2
49
Eth 2
PIWG 1
DSL Port 48
…
48
PIWG 1
DSL Port 2
Mgmt IB Eth
2
…
Port
…
Octet Nbr.
1 (MSB)
Bit Position
0
0
0
0
0
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.17
1.3.6.1.2.1.17.7
1.3.6.1.2.1.17.7.1
1.3.6.1.2.1.17.7.1.1
1.3.6.1.2.1.17.7.1.2
1.3.6.1.2.1.17.7.1.3
1.3.6.1.2.1.17.7.1.4
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19.4
MIB Objects
Table 202: Q-BRIDGE-MIB Objects
Object
OID
Description
Supported
dot1qBase
{ qBridgeMIBObjects 1 }
This group contains objects which are applicable to all
bridges implementing IEEE 802.1Q virtual LANs.
Y
dot1qTp
{ qBridgeMIBObjects 2 }
This group contains objects that control the operation and
report the status of transparent bridging. This includes
management of the Dynamic-Filtering Databases for both
unicast and multicast forwarding.
Y
This group also defines a dot1dTpFdbTable (Section
5.17.4.4.3, Page 351) that allowed multiple forwarding
databases for 802.1Q transparent devices. This version of
the table is an alternative to the one defined for 802.1D
devices which only supports a single forwarding database.
Refer to the Bridge MIB for the single forwarding database
version of the table.
dot1qStatic
{ qBridgeMIBObjects 3 }
This group defines the Static Destination-Address Filtering
Database and contains objects that control static configuration information for transparent bridging. This includes
management of the static entries in the Filtering Databases
for both unicast and multicast forwarding.
Y
dot1qVlan
{ qBridgeMIBObjects 4 }
This group contains objects that control configuration and
report status of the Virtual LANs known to a bridge. This
includes management of the statically configured VLANs
as well as reporting VLANs discovered by other means,
such as GVRP. It also controls configuration and reports
status of per-port objects relating to VLANs and reports
traffic statistics. It also provides for management of the
VLAN Learning Constraints.
Y
5.19.4.1
dot1qBase Group
This group contains objects which are applicable to all bridges implementing IEEE 802.1Q virtual LANs.
OIDs:
•
dot1qBase
- { qBridgeMIBObjects 1 }
1.3.6.1.2.1.17.7.1.1
375
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 203: dot1qBase
Object
OID
Syntax
Access
Status
Supported
dot1qVlanVersionNumber
{ dot1qBase 1 }
INTEGER
version1(1)
read-only
current
Y
dot1qMaxVlanId
{ dot1qBase 2 }
VlanId
read-only
current
Y
dot1qMaxSupportedVlans
{ dot1qBase 3 }
Unsigned32
read-only
current
Y
dot1qNumVlans
{ dot1qBase 4 }
Unsigned32
read-only
current
Y
dot1qGvrpStatus
{ dot1qBase 5 }
EnabledStatus
read-onlya
current
Y
a. Product Imposed Limit
5.19.4.1.1
dot1qVlanVersionNumber
The version number of IEEE 802.1Q that this device supports.
Valid Object Value(s)
•
version1(1)
5.19.4.1.2
dot1qMaxVlanId
The maximum IEEE 802.1Q VLAN ID that this device supports.
Valid Object Value(s)
•
4095
5.19.4.1.3
dot1qMaxSupportedVlans
The maximum number of IEEE 802.1Q VLANs that this device supports.
•
The following formula determines the value returned
( NbrDslPortsPerChassis × NbrPiwgsPerDslPort × NbrVlansPerPiwg ) + InBandMgmtVlan
Where:
NbrDslPortsPerChassis
=
24 or 48
NbrPiwgsPerDslPort
=
8
NbrVlansPerPiwg
=
8
=
=
( 24 x 8 x 8 ) + 1 = 1537
( 48 x 8 x 8 ) + 1 = 3073
Final Result:
5.19.4.1.4
24 port chassis
48 port chassis
dot1qNumVlans
The current number of IEEE 802.1Q VLANs that are configured in this device.
376
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19.4.1.5
dot1qGvrpStatus
The administrative status requested by management for GVRP. The value enabled(1) indicates that GVRP should be
enabled on this device, on all ports for which it has not been specifically disabled. When disabled(2), GVRP is
disabled on all ports and all GVRP packets are forwarded transparently. This object affects all GVRP Applicant and
Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all GVRP state machines on
all ports.
Valid Object Value(s)
•
disabled(2)
5.19.4.2
dot1qTp Group
This group contains objects that control the operation and report the status of transparent bridging. This includes
management of the dynamic Filtering Databases for both unicast and multicast forwarding.
OIDs:
•
dot1qTp
- { qBridgeMIBObjects 2 }
1.3.6.1.2.1.17.7.1.2
Table 204: dot1qTp
Object
OID
Syntax
Access
Status
Supported
dot1qFdbTable
{ dot1qTp 1 }
SEQUENCE of dot1qFdbEntry
not-accessible
current
N
dot1qTpFdbTable
{ dot1qTp 2 }
SEQUENCE of dot1qTpFdbEntry
not-accessible
current
N
dot1qTpGroupTable
{ dot1qTp 3 }
SEQUENCE of dot1qTpGroupEntry
not-accessible
current
N
dot1qForwardAllTable
{ dot1qTp 4 }
SEQUENCE of dot1qForwardAllEntry
not-accessible
current
N
dot1qForwardUnregisteredTable
{ dot1qTp 5 }
SEQUENCE of dot1qForwardUnregisteredEntry
not-accessible
current
N
5.19.4.2.1
dot1qFdbTable
The Filtering Database Table contains configuration and control information for each Filtering Database currently
operating on this device. Entries in this table appear automatically when VLANs are assigned FDB IDs in the
dot1qVlanCurrentTable (Section 5.19.4.4.2, Page 387).
Index(es):
•
dot1qFdbId
377
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
OIDs:
•
•
dot1qFdbTable
dot1qFdbEntry
- { dot1qTp 1 }
- { dot1qFdbTable 1 }
1.3.6.1.2.1.17.7.1.2.1
1.3.6.1.2.1.17.7.1.2.1.1
Table 205: dot1qFdbTable
Object
OID
Syntax
Access
Status
Supported
dot1dFdbId
{ dot1qFdbEntry 1 }
Unsigned32
not-accessible
current
N
dot1dTpFdbDynamicCount
{ dot1qFdbEntry 2 }
Counter32
read-only
current
N
5.19.4.2.1.1
dot1qFdbId
The identity of this Filtering Database.
5.19.4.2.1.2
dot1qFdbDynamicCount
The current number of dynamic entries in this Filtering Database.
5.19.4.2.2
dot1qTpFdbTable
Transparent Bridge Filtering Database Table contains information about unicast entries for which the device has
forwarding and/or filtering information. This information is used by the transparent bridging function in determining
how to propagate a received frame.
Each entry consists of information about a specific unicast MAC address for which the device has some forwarding
and/or filtering information.
Note in RFC:
Multiple Forwarding Databases for 802.1Q Transparent devices
This table is an alternative to the dot1dTpFdbTable (Section 5.17.4.4.3, Page 351) previously defined for
802.1D devices which only support a single Forwarding Database.
Index(es):
•
•
dot1qFdbId (Section 5.19.4.2.1.1, Page 378)
dot1qTpFdbAddress
OIDs:
•
•
dot1dTpFdbTable - { dot1qTp 2 }
dot1qTpFdbEntry - { dot1dTpFdbTable 1 }
378
1.3.6.1.2.1.17.7.1.2.2
1.3.6.1.2.1.17.7.1.2.2.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 206: dot1qTpFdbTable
Object
OID
Syntax
Access
Status
Supported
dot1qTpFdbAddress
{ dot1qTpFdbEntry 1 }
MacAddress
not-accessible
current
Y
dot1qTpFdbPort
{ dot1qTpFdbEntry 2 }
INTEGER (0…65535)
read-only
current
Y
dot1qTpFdbStatus
{ dot1qTpFdbEntry 3 }
INTEGER
other (1)
invalid (2)
learned (3)
self (4)
mgmt (5)
read-only
current
Y
5.19.4.2.2.1
dot1qTpFdbAddress
A unicast MAC address for which the device has forwarding and/or filtering information.
5.19.4.2.2.2
dot1qTpFdbPort
Either the value “0,” or the port number of the port on which a frame having a source address equal to the value of the
corresponding instance of dot1qTpFdbAddress has been seen. A value of “0” indicates that the port number has not
been learned but that the device does have some forwarding/filtering information about this address (for example, in
the dot1qStaticUnicastTable [dot1qStaticUnicastTable, Section 5.19.4.3.1, Page 383].
Implementors are encouraged to assign the port value to this object whenever it is learned even for addresses for
which the corresponding value of dot1qTpFdbStatus is not learned(3).
5.19.4.2.2.3
dot1qTpFdbStatus
The status of this entry. The meanings of the values are:
•
other(1)
•
invalid(2)
•
learned(3)
•
self(4)
•
mgmt(5)
- none of the following. This may include the case where some other MIB object (not the
corresponding instance of dot1qTpFdbPort, nor an entry in the
dot1qStaticUnicastTable) is being used to determine if and how frames addressed to the
value of the corresponding instance of dot1qTpFdbAddress are being forwarded.
- this entry is no longer valid (for example, it was learned but has since aged out), but has
not yet been flushed from the table.
- the value of the corresponding instance of dot1qTpFdbPort was learned and is being
used.
- the value of the corresponding instance of dot1qTpFdbAddress represents one of the
device's addresses. The corresponding instance of dot1qTpFdbPort indicates which of
the device's ports has this address.
- the value of the corresponding instance of dot1qTpFdbAddress is also the value of an
existing instance of dot1qStaticAddress (Author comment: I think that this is a typo in
the RFC. I seems like this should be dot1qStaticUnicastAddress [Section 5.19.4.3.1.1,
Page 384] as there is currently no object called dot1qStaticAddress.)
379
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19.4.2.3
dot1qTpGroupTable
This is the Dynamic Group Registration Table which contains filtering information for VLANs configured into the
bridge by (local or network) management, or learnt dynamically, specifying the set of ports to which frames received
on a VLAN for this FDB and containing a specific Group destination address are allowed to be forwarded.
Each entry consists of filtering information configured into the bridge by management, or learnt dynamically,
specifying the set of ports to which frames received on a VLAN and containing a specific Group destination address,
are allowed to be forwarded. The subset of these ports learnt dynamically is also provided.
Index(es):
•
•
dot1qVlanIndex (Reference Section 5.19.4.4.2.2, Page 388)
dot1qTpGroupAddress
OIDs:
•
•
dot1dTpGroupTable - { dot1qTp 3 }
dot1qTpGroupEntry - { dot1dTpGroupTable 1 }
1.3.6.1.2.1.17.7.1.2.3
1.3.6.1.2.1.17.7.1.2.3.1
Table 207: dot1qTpGroupTable
Object
OID
Syntax
Access
Status
Supported
dot1qTpGroupAddress
{ dot1qTpGroupEntry 1 }
MacAddress
not-accessible
current
N
dot1qTpGroupEgressPorts
{ dot1qTpGroupEntry 2 }
PortList
read-only
current
N
dot1qTpGroupLearnt
{ dot1qTpGroupEntry 3 }
PortList
read-only
current
N
5.19.4.2.3.1
dot1qTpGroupAddress
The destination Group MAC address in a frame to which this entry's filtering information applies.
5.19.4.2.3.2
dot1qTpGroupEgressPorts
The complete set of ports, in this VLAN, to which frames destined for this Group MAC address are currently being
explicitly forwarded. This does not include ports for which this address is only implicitly forwarded, in the
dot1qForwardAllPorts list.
5.19.4.2.3.3
dot1qTpGroupLearnt
The subset of ports in dot1qTpGroupEgressPorts which were learnt by GMRP or some other dynamic mechanism,
in this Filtering database.
5.19.4.2.4
dot1qForwardAllTable
This is a table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of
all multicasts applies, configured statically by management or dynamically by GMRP. An entry appears in this table
for all VLANs that are currently instantiated.
Each entry consists of forwarding information for a VLAN, specifying the set of ports to which all multicasts should
380
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
be forwarded, configured statically by management or dynamically by GMRP.
Index(es):
•
dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388)
OIDs:
•
•
dot1qForwardAllTable
dot1qForwardAllEntry
- { dot1qTp 4 }
- { dot1qForwardAllTable 1 }
1.3.6.1.2.1.17.7.1.2.4
1.3.6.1.2.1.17.7.1.2.4.1
Table 208: dot1qForwardAllTable
Object
OID
Syntax
Access
Status
Supported
dot1qForwardAllPorts
{ dot1qForwardAllEntry 1 }
PortList
not-accessible
current
N
dot1qForwardAllStaticPorts
{ dot1qForwardAllEntry 2 }
PortList
read-write
current
N
dot1qForwardAllForbiddenPorts
{ dot1qForwardAllEntry 3 }
PortList
read-write
current
N
5.19.4.2.4.1
dot1qForwardAllPorts
The complete set of ports in this VLAN to which all multicast group-addressed frames are to be forwarded. This
includes ports for which this need has been determined dynamically by GMRP, or configured statically by
management.
5.19.4.2.4.2
dot1qForwardAllStaticPorts
The set of ports configured by management in this VLAN to which all multicast group-addressed frames are to be
forwarded. Ports entered in this list will also appear in the complete set shown by dot1qForwardAllPorts. This value
is restored after the device is reset. This only applies to ports that are members of the VLAN, defined by
dot1qVlanCurrentEgressPorts. A port may not be added in this set if it is already a member of the set of ports in
dot1qForwardAllForbiddenPorts. The default value is a string of ones of appropriate length, to indicate standard nonEFS behavior, that is, forward all multicasts to all ports.
5.19.4.2.4.3
dot1qForwardAllForbiddenPorts
The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward All
Multicast Groups may not be dynamically registered by GMRP. This value is restored after the device is reset. A port
may not be added in this set if it is already a member of the set of ports in dot1qForwardAllStaticPorts. The default
value is a string of zeros of appropriate length.
5.19.4.2.5
dot1qForwardUnregisteredTable
This is a table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of
multicast group-addressed frames for which there is no more specific forwarding information applies. This is
configured statically by management and determined dynamically by GMRP. An entry appears in this table for all
VLANs that are currently instantiated.
Each entry consists of forwarding information for a VLAN, specifying the set of ports to which all multicasts for
381
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
which there is no more specific forwarding information shall be forwarded. This is configured statically by
management or dynamically by GMRP.
Index(es):
•
dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388)
OIDs:
•
•
dot1qForwardUnregisteredTable
dot1qForwardUnregisteredEntry
- { dot1qTp 5 }
- { dot1qForwardUnregisteredTable 1 }
1.3.6.1.2.1.17.7.1.2.5
1.3.6.1.2.1.17.7.1.2.5.1
Table 209: dot1qForwardUnregisteredTable
Object
OID
Syntax
Access
Status
Supported
dot1qForwardUnregisteredPorts
{ dot1qForwardUnregisteredEntry 1 }
PortList
read-only
current
N
dot1qForwardUnregisteredStaticPorts
{ dot1qForwardUnregisteredEntry 2 }
PortList
read-write
current
N
dot1qForwardUnregisteredForbiddenPorts
{ dot1qForwardUnregisteredEntry 3 }
PortList
read-write
current
N
5.19.4.2.5.1
dot1qForwardUnregisteredPorts
The complete set of ports in this VLAN to which multicast group-addressed frames for which there is no more
specific forwarding information is forwarded. This includes ports for which this need has been determined
dynamically by GMRP, or configured statically by management.
5.19.4.2.5.2
dot1qForwardUnregisteredStaticPorts
The set of ports configured by management, in this VLAN, to which multicast group-addressed frames for which
there is no more specific forwarding information are to be forwarded. Ports entered in this list will also appear in the
complete set shown by dot1qForwardUnregisteredPorts. This value is restored after the device is reset. A port may
not be added in this set if it is already a member of the set of ports in dot1qForwardUnregisteredForbiddenPorts. The
default value is a string of zeros of appropriate length, although this has no effect with the default value of
dot1qForwardAllStaticPorts (Section 5.19.4.2.4.2, Page 381).
5.19.4.2.5.3
dot1qForwardUnregisteredForbiddenPorts
The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward
Unregistered Multicast Groups may not be dynamically registered by GMRP. This value is restored after the device is
reset. A port may not be added in this set if it is already a member of the set of ports in
dot1qForwardUnregisteredStaticPorts. The default value is a string of zeros of appropriate length.
5.19.4.3
dot1qStatic Group
This group contains objects that control static configuration information for transparent bridging. This includes
management of the static entries in the Filtering Databases for both unicast and multicast forwarding.
382
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
OIDs:
•
dot1qStatic - { qBridgeMIBObjects 3 }
1.3.6.1.2.1.17.7.1.3
Table 210: dot1qStatic
Object
OID
Syntax
Access
Status
Supported
dot1qStaticUnicastTable
{ dot1qStatic 1 }
SEQUENCE of dot1qStaticUnicastEntry
not-accessible
current
Y
dot1qStaticMulticastTable
{ dot1qStatic 2 }
SEQUENCE of dot1qStaticMulticastEntry
not-accessible
current
N
5.19.4.3.1
dot1qStaticUnicastTable
The Static (Destination-Address Filtering) Database table containing filtering information for Unicast MAC
addresses for each Filtering Database, configured into the device by (local or network) management specifying the set
of ports to which frames received from specific ports and containing specific unicast destination addresses are
allowed to be forwarded. A value of zero in this table as the port number from which frames with a specific
destination address are received, is used to specify all ports for which there is no specific entry in this table for that
particular destination address. Entries are valid for unicast addresses only.
Each entry consists of filtering information configured into the device by (local or network) management specifying
the set of ports to which frames received from a specific port and containing a specific unicast destination address are
allowed to be forwarded.
Index(es):
•
•
•
dot1qFdbId (Section 5.19.4.2.1.1, Page 378)
dot1qStaticUnicastAddress
dot1qStaticUnicastReceivePort
OIDs:
•
•
dot1qStaticUnicastTable - { dot1qStatic 1 }
dot1qStaticUnicastEntry - { dot1qStaticUnicastTable 1 }
1.3.6.1.2.1.17.7.1.3.1
1.3.6.1.2.1.17.7.1.3.1.1
Table 211: dot1qStaticUnicastTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qStaticUnicastAddress
{ dot1qStaticUnicastEntry 1 }
MacAddress
not-accessible
current
Y
dot1qStaticUnicastReceivePort
{ dot1qStaticUnicastEntry 2 }
INTEGER (0…65535)
not-accessible
current
Y
dot1qStaticUnicastAllowedToGoTo
{ dot1qStaticUnicastEntry 3 }
PortList
read-write
current
Y
383
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 211: dot1qStaticUnicastTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qStaticUnicastStatus
{ dot1qStaticUnicastEntry 4 }
INTEGER
other (1)
invalid (2)
permanent (3)
deleteOnReset (4)
deleteOnTimeout (5)
read-write
current
Y
5.19.4.3.1.1
dot1qStaticUnicastAddress
The destination MAC address in a frame to which this entry's filtering information applies. This object must take the
value of a unicast address.
5.19.4.3.1.2
dot1qStaticUnicastReceivePort
Either the value “0,” or the port number of the port from which a frame must be received in order for this entry's
filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which
there is no other applicable entry.
5.19.4.3.1.3
dot1qStaticUnicastAllowedToGoTo
The set of ports for which a frame with a specific unicast address will be flooded in the event that it has not been
learned. It also specifies the set of ports a specific unicast address may be dynamically learnt on. The dot1qFdbTable
(Section 5.19.4.2.1, Page 377) will have an equivalent entry with a dot1qTpFdbPort (Section 5.19.4.2.2.2, Page 379)
value of “0” until this address has been learned, when it will be updated with the port the address has been seen on.
This only applies to ports that are members of the VLAN, defined by dot1qVlanCurrentEgressPorts (Section
5.19.4.4.2.4, Page 388). The default value of this object is a string of ones of appropriate length.
5.19.4.3.1.4
dot1qStaticUnicastStatus
This object indicates the status of this entry. The default value is permanent.
•
other(1)
•
•
•
•
invalid(2)
permanent(3)
deleteOnReset(4)
deleteOnTimeout(5)
5.19.4.3.2
- this entry is currently in use but the conditions under which it will remain so differ from the following values.
- writing this value to the object removes the corresponding entry.
- this entry is currently in use and will remain so after the next reset of the bridge.
- this entry is currently in use and will remain so until the next reset of the bridge.
- this entry is currently in use and will remain so until it is aged out.
dot1qStaticMulticastTable
This is a table containing filtering information for Multicast and Broadcast MAC addresses for each VLAN,
configured into the device by (local or network) management specifying the set of ports to which frames received
from specific ports and containing specific Multicast and Broadcast destination addresses are allowed to be
forwarded. A value of zero in this table as the port number from which frames with a specific destination address are
received, is used to specify all ports for which there is no specific entry in this table for that particular destination
address. Entries are valid for Multicast and Broadcast addresses only.
384
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Each entry consists of filtering information configured into the device by (local or network) management specifying
the set of ports to which frames received from this specific port for this VLAN and containing this Multicast or
Broadcast destination address are allowed to be forwarded.
Index(es):
•
•
•
dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388)
dot1qStaticMulticastAddress
dot1qStaticMulticastReceivePort
OIDs:
•
•
dot1qStaticMulticastTable
dot1qStaticMulticastEntry
- { dot1qStatic 2 }
- { dot1qStaticMulticastTable 1 }
1.3.6.1.2.1.17.7.1.3.2
1.3.6.1.2.1.17.7.1.3.2.1
Table 212: dot1qStaticMulticastTable
Object
OID
Syntax
Access
Status
Supported
dot1qStaticMulticastAddress
{ dot1qStaticMulticastEntry 1 }
MacAddress
not-accessible
current
N
dot1qStaticMulticastReceivePort
{ dot1qStaticMulticastEntry 2 }
INTEGER
(0…65535)
not-accessible
current
N
dot1qStaticMulticastStaticEgressPorts
{ dot1qStaticMulticastEntry 3 }
PortList
read-write
current
N
dot1qStaticMulticastForbiddenEgressPorts
{ dot1qStaticMulticastEntry 4 }
PortList
read-write
current
N
dot1qStaticMulticastStatus
{ dot1qStaticMulticastEntry 5 }
INTEGER
other (1)
invalid (2)
permanent (3)
deleteOnReset (4)
deleteOnTimeout (5)
read-write
current
N
5.19.4.3.2.1
dot1qStaticMulticastAddress
The destination MAC address in a frame to which this entry's filtering information applies. This object must take the
value of a Multicast or Broadcast address.
5.19.4.3.2.2
dot1qStaticMulticastReceivePort
Either the value “0,” or the port number of the port from which a frame must be received in order for this entry's
filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which
there is no other applicable entry.
5.19.4.3.2.3
dot1qStaticMulticastStaticEgressPorts
The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC
address must be forwarded, regardless of any dynamic information such as that from GMRP. A port may not be added
385
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
in this set if it is already a member of the set of ports in dot1qStaticMulticastForbiddenEgressPorts. The default value
of this object is a string of ones of appropriate length.
5.19.4.3.2.4
dot1qStaticMulticastForbiddenEgressPorts
The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC
address must not be forwarded, regardless of any dynamic information such as that from GMRP. A port may not be
added in this set if it is already a member of the set of ports in dot1qStaticMulticastStaticEgressPorts.
The default value of this object is a string of zeros of appropriate length.
5.19.4.3.2.5
dot1qStaticMulticastStatus
This object indicates the status of this entry. Its default value is permanent.
•
•
•
•
•
5.19.4.4
other(1)
- this entry is currently in use but the conditions under which it will remain so differ
from the following values.
invalid(2)
- writing this value to the object removes the corresponding entry.
permanent(3)
- this entry is currently in use and will remain so after the next reset of the bridge.
deleteOnReset(4)
- this entry is currently in use and will remain so until the next reset of the bridge.
deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out.
dot1qVlan Group
This group contains objects that control configuration and report status of the Virtual LANs known to a bridge. This
includes management of the statically configured VLANs as well as reporting VLANs discovered by other means,
such as GVRP. It also controls configuration and reports status of per-port objects relating to VLANs and reports
traffic statistics. It also provides for management of the VLAN Learning Constraints.
OIDs:
•
dot1qVlan
- { qBridgeMIBObjects 4 }
1.3.6.1.2.1.17.7.1.4
Table 213: dot1qVlan (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qVlanNumDeletes
{ dot1qVlan 1 }
Counter32
Read-only
current
N
dot1qVlanCurrentTable
{ dot1qVlan 2 }
SEQUENCE of
dot1qVlanCurrentEntry
not-accessible
current
Y
dot1qVlanStaticTable
{ dot1qVlan 3 }
SEQUENCE of
dot1qVlanStaticEntry
not-accessible
current
Y
dot1qNextFreeLocalVlanIndex
{ dot1qVlan 4 }
INTEGER(0 | 4096…2147483647)
read-only
current
Y
dot1qPortVlanTable
{ dot1qVlan 5 }
SEQUENCE of
dot1qPortVlanEntry
not-accessible
current
N
dot1qPortVlanStatisticsTable
{ dot1qVlan 6 }
SEQUENCE of
dot1qPortVlanStatisticsEntry
not-accessible
current
N
386
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 213: dot1qVlan (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qPortVlanHCStatisticsTable
{ dot1qVlan 7 }
SEQUENCE of
dot1qPortVlanHCStatisticsEntry
not-accessible
current
N
dot1qLearningConstraintsTable
{ dot1qVlan 8 }
SEQUENCE of
dot1qLearningConstraintsEntry
not-accessible
current
N
dot1qConstraintSetDefault
{ dot1qVlan 9 }
INTEGER (0…65535)
read-write
current
N
dot1qConstraintTypeDefault
{ dot1qVlan 10 }
INTEGER
independent (1)
shared (2)
read-write
current
N
5.19.4.4.1
dot1qVlanNumDeletes
The number of times a VLAN entry has been deleted from the dot1qVlanCurrentTable (Section 5.19.4.4.2, Page 387)
(for any reason). If an entry is deleted, then inserted, and then deleted, this counter is incremented by 2.
5.19.4.4.2
dot1qVlanCurrentTable
The Current VLAN Database table contains current configuration information for each VLAN currently configured
into the device by (local or network) management, or dynamically created as a result of GVRP requests received.
Each entry consists of information for a VLAN configured into the device by (local or network) management, or
dynamically created as a result of GVRP requests received.
Index(es):
•
•
dot1qVlanTimeMark
dot1qVlanIndex
OIDs:
•
•
dot1qVlanCurrentTable
dot1qVlanCurrentEntry
- { dot1qVlan 2 }
- { dot1qVlanCurrentTable 1 }
1.3.6.1.2.1.17.7.1.4.2
1.3.6.1.2.1.17.7.1.4.2.1
Table 214: dot1qVlanCurrentTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qVlanTimeMark
{ dot1qVlanCurrentEntry 1 }
TimeFilter
not-accessible
current
Y
dot1qVlanIndex
{ dot1qVlanCurrentEntry 2 }
VlanIndex
not-accessible
current
Y
dot1qVlanFdbId
{ dot1qVlanCurrentEntry 3 }
Unsigned32
read-only
current
Y
dot1qVlanCurrentEgresPorts
{ dot1qVlanCurrentEntry 4 }
PortList
read-only
current
Y
387
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 214: dot1qVlanCurrentTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qVlanCurrentUngaggedPorts
{ dot1qVlanCurrentEntry 5 }
PortList
read-only
current
Y
dot1qVlanStatus
{ dot1qVlanCurrentEntry 6 }
INTEGER
other (1)
permanent (2)
dynamicGvrp (3)
read-only
current
Y
dot1qVlanCreationTime
{ dot1qVlanCurrentEntry 7 }
TimeTicks
read-only
current
Y
5.19.4.4.2.1
dot1qVlanTimeMark
A TimeFilter [Section 4.14.1, Page 17] for this entry. See the TimeFilter textual convention to see how this works.
Valid Object Value(s)
This object must be zero when indexing into this table.
5.19.4.4.2.2
dot1qVlanIndex
The VLAN-ID or other identifier referring to this VLAN.
5.19.4.4.2.3
dot1qVlanFdbId
The Filtering Database used by this VLAN. This is one of the dot1qFdbId values in the dot1qFdbTable. This value is
allocated automatically by the device whenever the VLAN is created: either dynamically by GVRP, or by
management, in dot1qVlanStaticTable (Section 5.19.4.4.3, Page 389). Allocation of this value follows the learning
constraints defined for this VLAN in dot1qLearningConstraintsTable (Section 5.19.4.4.8, Page 394).
5.19.4.4.2.4
dot1qVlanCurrentEgressPorts
The set of ports which are transmitting traffic for this VLAN as either tagged or untagged frames.
5.19.4.4.2.5
dot1qVlanCurrentUntaggedPorts
The set of ports which are transmitting traffic for this VLAN as untagged frames.
5.19.4.4.2.6
dot1qVlanStatus
This object indicates the status of this entry.
•
•
•
other(1)
- this entry is currently in use but the conditions under which it will remain so differ from
the following values.
permanent(2)
- this entry, corresponding to an entry in dot1qVlanStaticTable (Section 5.19.4.4.3, Page
389), is currently in use and will remain so after the next reset of the device. The port
lists for this entry include ports from the equivalent dot1qVlanStaticTable entry and
ports learnt dynamically.
dynamicGvrp(3) - this entry is currently in use and will remain so until removed by GVRP. There is no
static entry for this VLAN and it is removed when the last port leaves the VLAN.
388
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19.4.4.2.7
dot1qVlanCreationTime
The value of sysUpTime when this VLAN was created.
5.19.4.4.3
dot1qVlanStaticTable
The Static VLAN Database is a table containing static configuration information for each VLAN configured into the
device by (local or network) management. All entries are permanent and are restored after the device is reset.
Each entry consists of static information for a VLAN configured into the device by (local or network) management.
Index(es):
•
dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388)
OIDs:
•
•
dot1qVlanStaticTable
dot1qVlanStaticEntry
- { dot1qVlan 3 }
1.3.6.1.2.1.17.7.1.4.3
- { dot1qVlanStaticTable 1 } 1.3.6.1.2.1.17.7.1.4.3.1
Table 215: dot1qVlanStaticTable
Object
OID
Syntax
Access
Status
Supported
dot1qVlanStaticName
{ dot1qVlanStaticEntry 1 }
SnmpAdminString
(SIZE (0…32))
read-create
current
Y
dot1qVlanStaticEgressPorts
{ dot1qVlanStaticEntry 2 }
PortList
read-create
current
Y
dot1qVlanForbiddenEgressPorts
{ dot1qVlanStaticEntry 3 }
PortList
read-create
current
Y
dot1qVlanStaticUntaggedPorts
{ dot1qVlanStaticEntry 4 }
PortList
read-create
current
Y
dot1qVlanStaticRowStatus
{ dot1qVlanStaticEntry 5 }
RowStatus
read-create
current
Y
5.19.4.4.3.1
dot1qVlanStaticName
An administratively assigned string, which may be used to identify the VLAN.
5.19.4.4.3.2
dot1qVlanStaticEgressPorts
The set of ports which are permanently assigned to the egress list for this VLAN by management. Changes to a bit in
this object affect the per-port per-VLAN Registrar control for Registration Fixed for the relevant GVRP state machine
on each port. A port may not be added in this set if it is already a member of the set of ports in
dot1qVlanForbiddenEgressPorts. The default value of this object is a string of zeros of appropriate length, indicating
not fixed.
5.19.4.4.3.3
dot1qVlanForbiddenEgressPorts
The set of ports which are prohibited by management from being included in the egress list for this VLAN. Changes
to this object that cause a port to be included or excluded affect the per-port per-VLAN Registrar control for
Registration Forbidden for the relevant GVRP state machine on each port. A port may not be added in this set if it is
389
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
already a member of the set of ports in dot1qVlanStaticEgressPorts. The default value of this object is a string of
zeros of appropriate length, excluding all ports from the forbidden set.
5.19.4.4.3.4
dot1qVlanStaticUntaggedPorts
The set of ports which should transmit egress packets for this VLAN as untagged. The default value of this object for
the default VLAN (dot1qVlanIndex = 1) is a string of appropriate length including all ports. There is no specified
default for other VLANs. If a device agent cannot support the set of ports being set then it will reject the set operation
with an error. An example might be if a manager attempts to set more than one VLAN to be untagged on egress where
the device does not support this IEEE 802.1Q option.
5.19.4.4.3.5
dot1qVlanStaticRowStatus
This object indicates the status of this entry.
5.19.4.4.4
dot1qNextFreeLocalVlanIndex
The next available value for dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388) of a local VLAN entry in
dot1qVlanStaticTable (Section 5.19.4.4.3, Page 389). This will report values >= 4096 if a new Local VLAN may be
created or else the value 0 if this is not possible. A row creation operation in this table for an entry with a local
VlanIndex value may fail if the current value of this object is not used as the index. Even if the value read is used,
there is no guarantee that it will still be the valid index when the create operation is attempted - another manager may
have already got in during the intervening time interval. In this case, dot1qNextFreeLocalVlanIndex (Section
5.19.4.4.4, Page 390) should be re-read and the creation re-tried with the new value.
This value will automatically change when the current value is used to create a new row.
5.19.4.4.5
dot1qPortVlanTable
The VLAN Port Configuration table contains per port control and status information for VLAN configuration in the
device.
Each entry consists of information controlling VLAN configuration for a port on the device.
Augments:
•
dot1dBasePortTable(Section 5.17.4.1.4, Page 349)
Index(es):
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
OIDs:
•
•
dot1qPortVlanTable - { dot1qVlan 5 }
dot1qPortVlanEntry - { dot1qPortVlanTable 1 }
1.3.6.1.2.1.17.7.1.4.5
1.3.6.1.2.1.17.7.1.4.5.1
Table 216: dot1qPortVlanTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qPvid
{ dot1qPortVlanEntry 1 }
VlanIndex
read-write
current
Y
390
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 216: dot1qPortVlanTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qPortAcceptableFrameTypes
{ dot1qPortVlanEntry 2 }
INTEGER
AdmitAll (1)
AdmitOnlyVlanTagged (2)
read-write
current
Y
dot1qPortIngressFiltering
{ dot1qPortVlanEntry 3 }
TruthValue
read-write
current
Y
dot1qPortGvrpStatus
{ dot1qPortVlanEntry 4 }
EnabledStatus
read-write
current
N
dot1qPortGvrpFailedRegistrations
{ dot1qPortVlanEntry 5 }
EnableStatus
read-write
current
N
dot1qPortGvrpLastPduOrigin
{ dot1qPortVlanEntry 6 }
MacAddress
read-only
current
N
5.19.4.4.5.1
dot1qPvid
The PVID, the VLAN ID assigned to untagged frames or Priority-Tagged frames received on this port. The default
value for this object is 1.
5.19.4.4.5.2
dot1qPortAcceptableFrameTypes
• admitAll(1)
- untagged frames or Priority-Tagged frames received on this port are
accepted and assigned to the PVID for this port.
•
admitOnlyVlanTagged(2) - the device will discard untagged frames or Priority-Tagged frames received
on this port.
This control does not affect VLAN independent BPDU frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP.
The default value for this object is admitAll (1).
5.19.4.4.5.3
dot1qPortIngressFiltering
• true(1) - the device will discard incoming frames for VLANs which do not include this Port in its Member
set.
• false(2) - the port will accept all incoming frames.
This control does not affect VLAN independent BPDU frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP.
The default value is false.
5.19.4.4.5.4
dot1qPortGvrpStatus
The state of GVRP operation on this port. The value enabled(1) indicates that GVRP is enabled on this port, as long
as dot1qGvrpStatus (Section 5.19.4.1.5, Page 377) is also enabled for this device. When disabled(2) but
dot1qGvrpStatus is still enabled for the device, GVRP is disabled on this port: any GVRP packets received are
silently discarded and no GVRP registrations are propagated from other ports. This object affects all GVRP Applicant
and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a reset of all GVRP
state machines on this port.
The default value is enabled.
391
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19.4.4.5.5
dot1qPortGvrpFailedRegistrations
The total number of failed GVRP registrations, for any reason, on this port.
5.19.4.4.5.6
dot1qPortGvrpLastPduOrigin
The Source MAC Address of the last GVRP message received on this port.
5.19.4.4.6
dot1qPortVlanStatisticsTable
The Per-port VLAN Statistics Table containing per-port, per-VLAN statistics for traffic received. Separate objects are
provided for both the most significant and least-significant bits of statistics counters for ports that are associated with
this transparent bridge. The most-significant bit objects are only required on high capacity interfaces, as defined in the
conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents which
support only SNMPv1.
Note that the reporting of most-significant and least-significant counter bits separately runs the risk of missing an
overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even
within the same varbindlist, when interpreting the results of a request or asynchronous notification.
Each entry consists of Traffic statistics for a VLAN on an interface.
Index(es):
•
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388)
OIDs:
•
•
dot1qPortVlanStatisitcsTable - { dot1qVlan 6 }
dot1qPortVlanStatisticsEntry - { dot1qPortVlanStatisitcsTable 1 }
1.3.6.1.2.1.17.7.1.4.6
1.3.6.1.2.1.17.7.1.4.6.1
Table 217: dot1qPortVlanStatisticsTable
Object
OID
Syntax
Access
Status
Supported
dot1qTpVlanPortInFrames
{ dot1qPortVlanStatisticsEntry 1 }
Counter32
read-write
current
Y
dot1qTpVlanPortOutFrames
{ dot1qPortVlanStatisticsEntry 2 }
Counter32
read-only
current
Y
dot1qTpVlanPortInDiscards
{ dot1qPortVlanStatisticsEntry 3 }
Counter32
read-only
current
Y
dot1qTpVlanPortInOverflowFrames
{ dot1qPortVlanStatisticsEntry 4 }
Counter32
read-only
current
Y
dot1qTpVlanPortOutOverflowFrames
{ dot1qPortVlanStatisticsEntry 5 }
Counter32
read-only
current
Y
dot1qTpVlanPortInOverflowDiscards
{ dot1qPortVlanStatisticsEntry 6 }
Counter32
read-only
current
Y
5.19.4.4.6.1
dot1qTpVlanPortInFrames
The number of valid frames received by this port from its segment which were classified as belonging to this VLAN.
Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by
392
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
the local forwarding process for this VLAN. This object includes received bridge management frames classified as
belonging to this VLAN (such as GMRP, but not GVRP or STP).
5.19.4.4.6.2
dot1qTpVlanPortOutFrames
The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN.
This includes bridge management frames originated by this device which are classified as belonging to this VLAN
(such as GMRP, but not GVRP or STP).
5.19.4.4.6.3
dot1qTpVlanPortInDiscards
The number of valid frames received by this port from its segment which were classified as belonging to this VLAN
which were discarded due to VLAN related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and
Discard on Ingress Filtering.
5.19.4.4.6.4
dot1qTpVlanPortInOverflowFrames
The number of times the associated dot1qTpVlanPortInFrames (Section 5.19.4.4.6.1, Page 392) counter has
overflowed.
5.19.4.4.6.5
dot1qTpVlanPortOutOverflowFrames
The number of times the associated dot1qTpVlanPortOutFrames (Section 5.19.4.4.6.2, Page 393) counter has
overflowed.
5.19.4.4.6.6
dot1qTpVlanPortInOverflowDiscards
The number of times the associated dot1qTpVlanPortInDiscards (Section 5.19.4.4.6.3, Page 393) counter has
overflowed.
5.19.4.4.7
dot1qPortVlanHCStatisticsTable
Port VLAN High Capacity Statistics Table contains per port, per VLAN statistics for traffic on high capacity
interfaces.
Each entry consists of traffic statistics for a VLAN on a high capacity interface.
Index(es):
•
•
dot1dBasePort (Section 5.17.4.1.4.1, Page 350)
dot1qVlanIndex (Section 5.19.4.4.2.2, Page 388)
OIDs:
•
•
dot1qPortVlanHCStatistics
dot1qPortVlanHCStatisticsEntry
- { dot1qVlan 7 }
- { dot1qPortVlanHCStatistics 1 }
1.3.6.1.2.1.17.7.1.4.7
1.3.6.1.2.1.17.7.1.4.7.1
Table 218: dot1qPortVlanHCStatisticsTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qTpVlanPortHCInFrames
{ dot1qPortVlanHCStatisticsEntry 1 }
Counter64
read-only
current
N
393
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 218: dot1qPortVlanHCStatisticsTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qTpVlanPortHCOutFrames
{ dot1qPortVlanHCStatisticsEntry 2 }
Counter64
read-only
current
N
dot1qTpVlanPortHCInDiscards
{ dot1qPortVlanHCStatisticsEntry 3 }
Counter64
read-only
current
N
5.19.4.4.7.1
dot1qTpVlanPortHCInFrames
The number of valid frames received by this port from its segment which were classified as belonging to this VLAN.
Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by
the local forwarding process for this VLAN. This object includes received bridge management frames classified as
belonging to this VLAN (such as GMRP, but not GVRP or STP).
5.19.4.4.7.2
dot1qTpVlanPortHCOutFrames
The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN.
This includes bridge management frames originated by this device which are classified as belonging to this VLAN
(such as GMRP, but not GVRP or STP).
5.19.4.4.7.3
dot1qTpVlanPortHCInDiscards
The number of valid frames received by this port from its segment which were classified as belonging to this VLAN
which were discarded due to VLAN related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and
Discard on Ingress Filtering.
5.19.4.4.8
dot1qLearningConstraintsTable
The VLAN Learning Constraints Table containing learning constraints for sets of Shared and Independent VLANs.
Each entry consists of a learning constraint defined for a VLAN.
Index(es):
•
•
dot1qConstraintVlan
dot1qConstraintSet
OIDs:
•
•
dot1qLearningConstraintsTable
dot1qLearningConstraintsEntry
- { dot1qVlan 8 }
- { dot1qLearningConstraintsTable 1 }
1.3.6.1.2.1.17.7.1.4.8
1.3.6.1.2.1.17.7.1.4.8.1
Table 219: dot1qLearningConstraintsTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qConstraintVlan
{ dot1qLearningConstraintsEntry 1 }
VlanIndex
not-accessible
current
N
394
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 219: dot1qLearningConstraintsTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
dot1qConstraintSet
{ dot1qLearningConstraintsEntry 2 }
INTEGER (0…65535)
not-accessible
current
N
dot1qConstraintType
{ dot1qLearningConstraintsEntry 3 }
INTEGER
independent (1)
shared (2)
read-only
current
N
dot1qConstraintStatus
{ dot1qLearningConstraintsEntry 4 }
RowStatus
read-only
current
N
5.19.4.4.8.1
dot1qConstraintVlan
The index of the row in dot1qVlanCurrentTable for the VLAN constrained by this entry.
5.19.4.4.8.2
dot1qConstraintSet
The identity of the constraint set to which dot1qConstraintVlan belongs. These values may be chosen by the
management station.
5.19.4.4.8.3
dot1qConstraintType
The type of constraint this entry defines.
•
independent(1)
•
shared(2)
5.19.4.4.8.4
- the VLAN, dot1qConstraintVlan, uses an independent filtering database from all other
VLANs in the same set, defined by dot1qConstraintSet.
- the VLAN, dot1qConstraintVlan, shares the same filtering database as all other VLANs
in the same set, defined by dot1qConstraintSet.
dot1qConstraintStatus
The status of this entry.
5.19.4.4.9
dot1qConstraintSetDefault
The identity of the constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in
dot1qLearningConstraintsTable.
5.19.4.4.10 dot1qConstraintTypeDefault
The type of constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in
dot1qLearningConstraintsTable (Section 5.19.4.4.8, Page 394). The types are as defined for dot1qConstraintType.
395
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
5.19.5
Conformance Information
5.19.5.1
Compliance
5.19.5.1.1
qBridgeCompliance
The compliance statement for device support of Virtual LAN Bridge services.
Mandatory Groups:
•
•
•
•
qBridgeBaseGroup
qBridgeVlanGroup
qBridgeVlanStaticGroup
qBridgePortGroup
Optional Groups:
•
•
•
•
•
•
•
•
•
qBridgeFdbUnicastGroup
- This group is mandatory for bridges that implement 802.1Q
transparent bridging.
qBridgeFdbMulticastGroup
- This group is mandatory for bridges that implement 802.1Q
transparent bridging.
qBridgeServiceRequirementsGroup
- This group is mandatory for bridges that implement extended
filtering services. All objects must be read-write if extendedfiltering services are enabled.
qBridgeFdbStaticGroup
- This group is optional.
qBridgeVlanStatisticsGroup
- This group is optional as there may be significant implementation cost associated with its support.
qBridgeVlanStatisticsOverflowGroup
- This group is optional as there may be significant implementation cost associated with its support. It is most relevant for high
capacity interfaces where the SNMP agent supports only
SNMPv1.
qBridgeVlanHCStatisticsGroup
- This group is optional as there may be significant implementation cost associated with its support. It is most relevant for high
capacity interfaces.
qBridgeLearningConstraintsGroup
- This group is mandatory for devices implementing both Independent VLAN Learning (IVL) and Shared VLAN Learning
(SVL) modes of operation of the filtering database, as defined
by IEEE 802.1Q.
qBridgeLearningConstraintDefaultGroup - This group is mandatory for devices implementing both Independent VLAN Learning (IVL) and Shared VLAN Learning
(SVL) modes of operation of the filtering database, as defined
by IEEE 802.1Q.
Objects that have a MIN-ACCESS defined:
396
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
•
dot1qPortAcceptableFrameTypes
•
dot1qPortIngressFiltering
•
dot1qConstraintSetDefault
•
dot1qConstraintTypeDefault
5.19.5.2
- MIN-ACCESS read-only
Write access is not required as this is an optional capability in
IEEE 802.1Q.
- MIN-ACCESS read-only
Write access is not required as this is an optional capability in
IEEE 802.1Q.
- MIN-ACCESS read-only
Write access is not required as this is an optional capability in
IEEE 802.1Q.
- MIN-ACCESS read-only
Write access is not required as this is an optional capability in
IEEE 802.1Q.
Conformance
Table 220: Q-BRIDGE-MIB Conformance (1 of 3)
Group
Description
Objects
Supported
qBridgeBaseGroup
A collection of objects
providing device level control
and status information for the
Virtual LAN bridge services.
dot1qVlanVersionNumber
Y
dot1qMaxVlanId
Y
dot1qMaxSupportedVlans
Y
dot1qNumVlans
Y
dot1qGvrpStatus
N
A collection of objects
providing information about
all unicast addresses, learnt
dynamically or statically
configured by management,
in each Filtering Database.
dot1qFdbDynamicCount
N
dot1qTpFdbPort
Y
dot1qTpFdbStatus
Y
A collection of objects
providing information about
all multicast addresses, learnt
dynamically or statically
configured by management,
in each Filtering Database.
dot1qTpGroupEgressPorts
N
dot1qTpGroupLearnt
N
qBridgeFdbUnicastGroup
qBridgeFdbMulticastGroup
397
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 220: Q-BRIDGE-MIB Conformance (2 of 3)
Group
Description
Objects
Supported
qBridgeServiceRequirementsGroup
A collection of objects
providing information about
service requirements, learnt
dynamically or statically
configured by management,
in each Filtering Database.
dot1qForwardAllPorts
N
dot1qForwardAllStaticPorts
N
dot1qForwardAllForbidden
N
dot1qForwardUnregisteredPorts
N
dot1qForwardUnregisteredStaticPorts
N
dot1qForwardUnregisteredForbidden
Ports
N
dot1qStaticUnicastAllowedToGoTo
Y
dot1qStaticUnicastStatus
Y
dot1qStaticMulticastStaticEgressPort
s
N
dot1qStaticMulticastForbiddenEgress
Ports
N
dot1qStaticMulticastStatus
N
dot1qVlanNumDeletes
N
dot1qVlanFdbId
Y
dot1qVlanCurrentEgressPorts
Y
dot1qVlanCurrentUntaggedPorts
Y
dot1qVlanStatus
Y
dot1qVlanCreationTime
Y
dot1qVlanStaticName
Y
dot1qVlanStaticEgressPorts
Y
dot1qVlanForbiddenEgressPorts
Y
dot1qVlanStaticUntaggedPorts
Y
dot1qVlanStaticRowStatus
Y
dot1qNextFreeLocalVlanIndex
Y
qBridgeFdbStaticGroup
qBridgeVlanGroup
qBridgeVlanStaticGroup
A collection of objects
providing information about
unicast and multicast
addresses statically
configured by management,
in each Filtering Database or
VLAN.
A collection of objects
providing information about
unicast and multicast
addresses statically
configured by management,
in each Filtering Database or
VLAN.
A collection of objects
providing information about
VLANs statically configured
by management.
398
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
Q-BRIDGE-MIB — RFC 2674
Table 220: Q-BRIDGE-MIB Conformance (3 of 3)
Group
Description
Objects
Supported
qBridgePortGroup
A collection of objects
providing port level VLAN
control and status information
for all ports.
dot1qPvid
Y
dot1qPortAcceptableFrameTypes
Y
dot1qPortIngressFiltering
Y
dot1qPortGvrpStatus
N
dot1qPortGvrpFailedRegistrations
N
dot1qPortGvrpLastPduOrigin
N
A collection of objects
providing per-port packet
statistics for all VLANs
currently configured on this
device.
dot1qTpVlanPortInFrames
N
dot1qTpVlanPortOutFrames
N
dot1qTpVlanPortInDiscards
N
A collection of objects
providing overflow counters
for per-port packet statistics
for all VLANs currently
configured on this device for
high capacity interfaces,
defined as those that have the
value of the corresponding
instance of ifSpeed greater
than 650,000,000 bits/second.
dot1qTpVlanPortInOverflowFrames
N
dot1qTpVlanPortOutOverflowFrames
N
dot1qTpVlanPortInOverflowDiscards
N
A collection of objects
providing per-port packet
statistics for all VLANs
currently configured on this
device for high capacity
interfaces, defined as those
that have the value of the
corresponding instance of
ifSpeed greater than
650,000,000 bits/second.
dot1qTpVlanPortHCInFrames
N
dot1qTpVlanPortHCOutFrames
N
dot1qTpVlanPortHCInDiscards
N
A collection of objects
defining the Filtering
Database constraints all
VLANs have with each other.
dot1qConstraintType
N
dot1qConstraintTypeDefault
N
A collection of objects
defining the default Filtering
Database constraints for
VLANs which have no
specific constraints defined.
dot1qConstraintSetDefault
N
qBridgeVlanStatisticsGroup
qBridgeVlanStatisticsOverflowGroup
qBridgeVlanHCStatisticsGroup
qbridgeLearningConstraintsGroup
qBridgeLearningConstraintDefaultGroup
399
dot1qConstraintTypeDefault
N
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
5.20 IGMP-STD-MIB — RFC 2933
5.20.1
Introduction
The MIB module for IGMP Management.
The revision of the MIB that this SNMP Operational Specification aligns with is that which has a LAST-UPDATED
of “200009280000Z,” or September 28, 2000.
5.20.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.20.3
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
igmpStdMIB
igmpMIBObjects
5.20.4
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 85 }
{ igmpStdMIB 1 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.85
1.3.6.1.2.1.85.1
Table 221: IGMP-STD-MIB Objects
Object
OID
Syntax
Access
Status
Supported
igmpInterfaceTable
{ igmpMIBObjects 1 }
SEQUENCE of
igmpInterfaceEntry
not-accessible
current
Y
igmpCacheTable
{ igmpMIBObjects 2 }
SEQUENCE of
igmpCacheEntry
not-accessible
current
Y
5.20.4.1
igmpInterfaceTable
The (conceptual) table listing the interfaces on which IGMP is enabled.
Note:
This table is not implemented as a dynamic table; rows can’t be created or destroyed. A row in this table will
exist for each and every DSL interface and potential Ethernet interface that can carry multicast data.
Index(es):
•
igmpInterfaceIfIndex
400
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
OIDs:
•
•
igmpInterfaceTable
igmpInterfaceEntry
- { igmpMIBObjects 1 }
- { igmpInterfaceTable 1 }
1.3.6.1.2.1.85.1.1
1.3.6.1.2.1.85.1.1.1
Table 222: igmpInterfaceTable
Object
OID
Syntax
Access
Status
Supported
igmpInterfaceIfIndex
{ igmpInterfaceEntry 1 }
InterfaceIndex
not-accessible
current
Y
igmpInterfaceQueryInterval
{ igmpInterfaceEntry 2 }
Unsigned32
read-writea
current
Y
igmpInterfaceStatus
{ igmpInterfaceEntry 3 }
RowStatus
read-writea
current
Y
igmpInterfaceVersion
{ igmpInterfaceEntry 4 }
Unsigned32
read-writea
current
Y
igmpInterfaceQuerier
{ igmpInterfaceEntry 5 }
IpAddress
read-only
current
Y
igmpInterfaceQueryMaxResponseTime
{ igmpInterfaceEntry 6 }
Unsigned32(0…255)
read-writea
current
Y
igmpInterfaceQuerierUpTime
{ igmpInterfaceEntry 7 }
TimeTicks
read-only
current
N
igmpInterfaceQuerierExpiryTime
{ igmpInterfaceEntry 8 }
TimeTicks
read-only
current
N
igmpInterfaceVersion1QuerierTimer
{ igmpInterfaceEntry 9 }
TimeTicks
read-only
current
Y
igmpInterfaceWrongVersionQueries
{ igmpInterfaceEntry 10 }
Counter32
read-only
current
Y
igmpInterfaceJoins
{ igmpInterfaceEntry 11 }
Counter32
read-only
current
Y
igmpInterfaceProxyIfIndex
{ igmpInterfaceEntry 12 }
InterfaceIndexOrZero
read-writea
current
Y
igmpInterfaceGroups
{ igmpInterfaceEntry 13 }
Gauge32
read-only
current
Y
igmpInterfaceRobustness
{ igmpInterfaceEntry 14 }
Unsigned32(1…10)b
read-writea
current
Y
igmpInterfaceLastMembQueryIntvl
{ igmpInterfaceEntry 15 }
Unsigned32(0…255)
read-writea
current
Y
a. Product imposed restriction. This table is not dynamic, therefore rows can’t be created.
b. Product imposed restriction.
5.20.4.1.1
igmpInterfaceIfIndex
The ifIndex (Section 5.3.4.3.1, Page 39) value of the interface for which IGMP is enabled.
5.20.4.1.2
igmpInterfaceQueryInterval
The frequency at which IGMP Host-Query packets are transmitted on this interface in units of seconds.
DEFVAL - 125 (Packet transmitted every 125 seconds)
401
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
5.20.4.1.3
igmpInterfaceStatus
The activation of a row enables IGMP on the interface. The destruction of a row disables IGMP on the interface.
Valid Object Value(s)
The following values are supported to allow entries to be modified:
•
active(1)
5.20.4.1.4
igmpInterfaceVersion
The version of IGMP which is running on this interface. This object can be used to configure a router capable of
running either value. For IGMP to function correctly, all routers on a LAN must be configured to run the same version
of IGMP on that LAN.
DEFVAL - 2
5.20.4.1.5
igmpInterfaceQuerier
The address of the IGMP Querier on the IP subnet to which this interface is attached.
5.20.4.1.6
igmpInterfaceQueryMaxResponseTime
The maximum query response time advertised in IGMPv2 queries on this interface.
The units are in tenths of a second. The valid range of this object is 0 to 25.5 seconds.
DEFVAL - 100 (10.0 seconds)
5.20.4.1.7
igmpInterfaceQuerierUpTime
The time since igmpInterfaceQuerier was last changed.
5.20.4.1.8
igmpInterfaceQuerierExpiryTime
The amount of time remaining before the Other Querier Present Timer expires. If the local system is the querier, the
value of this object is zero.
5.20.4.1.9
igmpInterfaceVersion1QuerierTimer
The time remaining until the host assumes that there are no IGMPv1 routers present on the interface. While this is
non-zero, the host will reply to all queries with version 1 membership reports.
5.20.4.1.10 igmpInterfaceWrongVersionQueries
The number of queries received whose IGMP version does not match igmpInterfaceVersion (Section 5.20.4.1.4, Page
402), over the lifetime of the row entry. IGMP requires that all routers on a LAN be configured to run the same
version of IGMP. Thus, if any queries are received with the wrong version, this indicates a configuration error.
5.20.4.1.11 igmpInterfaceJoins
The number of times a group membership has been added on this interface; that is, the number of times an entry for
this interface has been added to the Cache Table. This object gives an indication of the amount of IGMP activity over
the lifetime of the row entry.
5.20.4.1.12 igmpInterfaceProxyIfIndex
Some devices implement a form of IGMP proxying whereby memberships learned on the interface represented by
this row, cause IGMP Host Membership Reports to be sent on the interface whose ifIndex value is given by this
402
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
object. Such a device would implement the igmpV2RouterMIBGroup only on its router interfaces (those interfaces
with non-zero igmpInterfaceProxyIfIndex). Typically, the value of this object is 0, indicating that no proxying is
being done.
DEFVAL - 0 (No proxying is being done)
5.20.4.1.13 igmpInterfaceGroups
The current number of entries for this interface in the Cache Table (Section 5.20.4.2, Page 403).
5.20.4.1.14 igmpInterfaceRobustness
The Robustness Variable allows tuning for the expected packet loss on a subnet. If a subnet is expected to be lossy, the
Robustness Variable may be increased. IGMP is robust to (Robustness Variable-1) packet losses.
The valid range for this object is 1 to 10 per product imposed restriction
DEFVAL - 2
5.20.4.1.15 igmpInterfaceLastMembQueryIntvl
The Last Member Query Interval is the Max Response Time inserted into Group-Specific Queries sent in response to
Leave Group messages, and is also the amount of time between Group-Specific Query messages. This value may be
tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last
member of a group. The value of this object is irrelevant if igmpInterfaceVersion is 1.
The units are in tenths of a second. The valid range for this object is 0 to 25.5 seconds.
DEFVAL - 1 (0.1 second)
5.20.4.2
igmpCacheTable
The (conceptual) table listing the IP multicast groups for which there are members on a particular interface.
Note:
This table is not implemented as a dynamic table; rows can’t be created or destroyed. A row in this table will
exist for each and every multicast stream on every interface that is carrying multicast data where the “join”
has been snooped.
Index(es):
•
•
igmpCacheAddress
igmpCacheIfIndex
OIDs:
•
•
igmpCacheTable
igmpCacheEntry
- { igmpMIBObjects 2 }
- { igmpCacheTable 1 }
1.3.6.1.2.1.85.1.2
1.3.6.1.2.1.85.1.2.1
Table 223: igmpCacheTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
igmpCacheAddress
{ igmpCacheEntry 1 }
IpAddress
not-accessible
current
Y
403
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
Table 223: igmpCacheTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
igmpCacheIfIndex
{ igmpCacheEntry 2 }
InterfaceIndex
not-accessible
current
Y
igmpCacheSelf
{ igmpCacheEntry 3 }
TruthValue
read-onlya
current
N
igmpCacheLastReporter
{ igmpCacheEntry 4 }
IpAddress
read-only
current
N
igmpCacheUpTime
{ igmpCacheEntry 5 }
TimeTicks
read-only
current
N
igmpCacheExpiryTime
{ igmpCacheEntry 6 }
TimeTicks
read-only
current
N
igmpCacheStatus
{ igmpCacheEntry 7 }
RowStatus
read-onlya
current
Y
igmpCacheVersion1HostTimer
{ igmpCacheEntry 8 }
TimeTicks
read-only
current
N
a. Product imposed restriction.
5.20.4.2.1
igmpCacheAddress
The IP multicast group address for which this entry contains information.
5.20.4.2.2
igmpCacheIfIndex
The interface for which this entry contains information for an IP multicast group address.
5.20.4.2.3
igmpCacheSelf
An indication of whether the local system is a member of this group address on this interface.
DEFVAL - true
5.20.4.2.4
igmpCacheLastReporter
The IP address of the source of the last membership report received for this IP Multicast group address on this
interface. If no membership report has been received, this object has the value 0.0.0.0.
5.20.4.2.5
igmpCacheUpTime
The time elapsed since this entry was created.
5.20.4.2.6
igmpCacheExpiryTime
The minimum amount of time remaining before this entry is aged out. A value of 0 indicates that the entry is only
present because igmpCacheSelf is true and that if the router left the group, this entry would be aged out immediately.
Note that some implementations may process membership reports from the local system in the same way as reports
from other hosts, so a value of 0 is not required.
5.20.4.2.7
igmpCacheStatus
The status of this entry.
Valid Object Value(s)
•
active(1)
404
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
5.20.4.2.8
igmpCacheVersion1HostTimer
The time remaining until the local router will assume that there are no longer any IGMP version 1 members on the IP
subnet attached to this interface. Upon hearing any IGMPv1 Membership Report, this value is reset to the group
membership timer. While this time remaining is non-zero, the local router ignores any IGMPv2 Leave messages for
this group that it receives on this interface.
5.20.5
Conformance Information
5.20.5.1
Compliance
5.20.5.1.1
igmpV1HostMIBCompliance
The compliance statement for hosts running IGMPv1 and implementing the IGMP MIB.
Mandatory Groups:
•
igmpBaseMIBGroup
Objects that have a MIN-ACCESS defined:
•
igmpInterfaceStatus
•
igmpCacheStatus
5.20.5.1.2
- MIN-ACCESS read-only
Write access is not required.
- MIN-ACCESS read-only
Write access is not required.
igmpV1RouterMIBCompliance
The compliance statement for routers running IGMPv1 and implementing the IGMP MIB.
Mandatory Groups:
•
•
igmpBaseMIBGroup
igmpRouterMIBGroup
Objects that have a MIN-ACCESS defined:
•
igmpInterfaceStatus
•
igmpCacheStatus
5.20.5.1.3
- MIN-ACCESS read-only
Write access is not required.
- MIN-ACCESS read-only
Write access is not required.
igmpV2HostMIBCompliance
The compliance statement for hosts running IGMPv2 and implementing the IGMP MIB.
Mandatory Groups:
405
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
IGMP-STD-MIB — RFC 2933
•
•
igmpBaseMIBGroup
igmpV2HostMIBGroup
Objects that have a MIN-ACCESS defined:
•
igmpInterfaceStatus
•
igmpCacheStatus
5.20.5.1.4
- MIN-ACCESS read-only
Write access is not required.
- MIN-ACCESS read-only
Write access is not required.
igmpV2RouterMIBCompliance
The compliance statement for routers running IGMPv2 and implementing the IGMP MIB.
Mandatory Groups:
•
•
•
igmpBaseMIBGroup
igmpRouterMIBGroup
igmpV2RouterMIBGroup
Objects that have a MIN-ACCESS defined:
•
igmpInterfaceStatus
•
igmpCacheStatus
- MIN-ACCESS read-only
Write access is not required.
- MIN-ACCESS read-only
Write access is not required.
406
SNMP Reference
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
IGMP-STD-MIB — RFC 2933
5.20.6
Conformance
Table 224: IGMP-STD-MIB Conformance
Group
Description
Objects
Supported
igmpCacheSelf
N
igmpBaseMIBGroup
The basic collection of objects providing management of IGMP version 1 or
2.
igmpCacheStatus
Y
igmpInterfaceStatus
Y
igmpCacheUpTime
N
igmpCacheExpiryTime
Y
igmpInterfaceJoins
Y
igmpInterfaceGroups
Y
igmpCacheLastReporter
Y
igmpInterfaceQuerierUpTime
N
igmpInterfaceQuerierExpiryTime
N
igmpInterfaceQueryInterval
Y
igmpInterfaceVersion1QuerierTimer
Y
A collection of additional objects for
management of IGMP version 1 or version 2 routers.
igmpRouterMIBGroup
igmpV2HostMIBGroup
A collection of additional objects for
management of IGMP version 2 in
hosts.
igmpCacheLastReporter
Y
igmpHostOptMIBGroup
A collection of optional objects for
IGMP hosts. Supporting this group can
be especially useful in an environment
with a router which does not support
the IGMP MIB.
igmpInterfaceQuerier
Y
A collection of additional objects for
management of IGMP version 2 in
routers.
igmpInterfaceVersion
Y
igmpInterfaceQuerier
Y
igmpInterfaceQueryMaxResponseTime
Y
igmpInterfaceRobustness
Y
igmpInterfaceWrongVersionQueries
Y
igmpInterfaceLastMembQueryIntvl
Y
igmpCacheVersion1HostTimer
Y
igmpInterfaceProxyIfIndex
Y
igmpV2RouterMIBGroup
igmpV2ProxyMIBGroup
A collection of additional objects for
management of IGMP proxy devices.
407
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
5.21 PPP-LCP-MIB — RFC 1471
5.21.1
Introduction
This MIB describes objects for managing the Link Control Protocol and Link Quality Monitoring on subnetwork
interfaces that use the family of Point-to-Point protocols defined in:
•
•
•
•
•
The Point-to-Point Protocol for the Transmission of Multi-protocol Datagrams over Point-to-Point Links,
RFC 1331
The PPP Internet Protocol Control Protocol, RFC 1332
Point-to-Point Protocol Extensions for Bridging, RFC 1220
PPP Authentication Protocols, RFC 1334
PPP Link Quality Monitoring, RFC 1333
5.21.2 Terms
ACC
- Asynchronous-Control-Character-Map
FCS
- Frame Check Sequence
HDLC
- High-level Data Link Control
LAP-B
- Link Access Procedure for Balanced Mode.
LCP
- Link Control Protocol
LQR
- Line Quality Report
MRU
- Maximum Receive Unit
PPP
- Point-to-Point Protocol
5.21.3
•
•
•
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
ppp
pppLcp
pppLink
pppLqr
pppTests
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 23 }
{ ppp 1 }
{ pppLcp 1 }
{ pppLcp 2 }
{ pppLcp 3 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.23
1.3.6.1.2.1.10.23.1
1.3.6.1.2.1.10.23.1.1
1.3.6.1.2.1.10.23.1.2
1.3.6.1.2.1.10.23.1.3
408
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
5.21.4
MIB Objects
Table 225: PPP-LCP-MIB Objects
Object
OID
Description
Supported
pppLink
{ pppLcp 1 }
The PPP Link Group
Y
This group represents the lowest level of the PPP protocol.
This group contains two tables, one containing status information
and the other configuration information. The configuration table is
split off of the status so that it may be placed in a separate MIB
View for security purposes.
The PPP LQR Group
N
This group provides the basic MIB variables that apply to the PPP
LQR Protocol. This group provides MIB access to the information
required for LQR processing. This group contains two tables, one
containing status information and the other configuration information. The configuration table is split off of the status so that it may
be placed in a separate MIB View for security purposes.
The PPP LQR Extensions Group
pppLqr
{ pppLcp 2 }
N
The PPP LQR Extensions group contains the most recently
received LQR packet, as well as the save fields that are logically
appended PPP Link Quality Monitoring, RFC 1333 to received
LQR packets. This is done in order to facilitate external implementations of the Link Quality Monitoring policies.
It is not practical to examine the relevant MIB objects which are
used to generate LQR packets since LQR policies may require
synchronization of the values of all data used to determine Link
Quality; i.e., the values of the relevant counters must all be taken at
the same instant in time. Thus, by recording the last received LQR
packet, a synchronized record of the relevant data is available.
pppTests
{ pppLcp 3 }
PPP Test Group
N
The extensions to the interface table define a table through which
the network manager can instruct the managed object to perform
various tests of the interface. This is the ifExtnsTestTable.
5.21.4.1
PPP Link Group
This group represents the lowest level of the PPP protocol.
This group contains two tables, one containing status information and the other configuration information. The configuration table is split off of the status so that it may be placed in a separate MIB View for security purposes.
OID:
•
pppLink
- { pppLcp 1 }
1.3.6.1.2.1.10.23.1.1
409
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
5.21.4.1.1
pppLinkStatusTable
A table containing PPP-link specific variables for this PPP implementation.
This table is a sequence of pppLinkStatusEntry which contains management information about a particular PPP Link.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pppLinkStatusTable - { pppLink 1 }
pppLinkStatusEntry - { pppLinkStatusTable 1 }
1.3.6.1.2.1.10.23.1.1.1
1.3.6.1.2.1.10.23.1.1.1.1
Table 226: pppLinkStatusTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pppLinkStatusPhysicalIndex
{ pppLinkStatusEntry 1 }
INTEGER
(0…2147483647)
read-only
mandatory
Y
pppLinkStatusBadAddresses
{ pppLinkStatusEntry 2 }
Counter
read-only
mandatory
Y
pppLinkStatusBadControls
{ pppLinkStatusEntry 3 }
Counter
read-only
mandatory
Y
pppLinkStatusPacketTooLongs
{ pppLinkStatusEntry 4 }
Counter
read-only
mandatory
Y
pppLinkStatusBadFCSs
{ pppLinkStatusEntry 5 }
Counter
read-only
mandatory
Y
pppLinkStatusLocalMRU
{ pppLinkStatusEntry 6 }
INTEGER
(1…2147483648)
read-only
mandatory
Y
pppLinkStatusRemoteMRU
{ pppLinkStatusEntry 7 }
INTEGER
(1…2147483648)
read-only
mandatory
Y
pppLinkStatusLocalToPeerACCMap
{ pppLinkStatusEntry 8 }
OCTET STRING
(SIZE (4))
read-only
mandatory
Y
pppLinkStatusPeerToLocalACCMap
{ pppLinkStatusEntry 9 }
OCTET STRING
(SIZE (4))
read-only
mandatory
Y
pppLinkStatusLocalToRemoteProtocolCompression
{ pppLinkStatusEntry 10 }
INTEGER
enabled(1)
disabled(2)
read-only
mandatory
Y
pppLinkStatusRemoteToLocalProtocolCompression
{ pppLinkStatusEntry 11 }
INTEGER
enabled(1)
disabled(2)
read-only
mandatory
Y
pppLinkStatusLocalToRemoteACCompression
{ pppLinkStatusEntry 12 }
INTEGER
enabled(1)
disabled(2)
read-only
mandatory
Y
410
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
Table 226: pppLinkStatusTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pppLinkStatusRemoteToLocalACCompression
{ pppLinkStatusEntry 13 }
INTEGER
enabled(1)
disabled(2)
read-only
mandatory
Y
pppLinkStatusTransmitFcsSize
{ pppLinkStatusEntry 14 }
INTEGER
(0…128)
read-only
mandatory
Y
pppLinkStatusReceiveFcsSize
{ pppLinkStatusEntry 15 }
INTEGER
(0…128)
read-only
mandatory
Y
5.21.4.1.1.1
pppLinkStatusPhysicalIndex
The value of ifIndex that identifies the lower-level interface over which this PPP Link is operating. This interface
would usually be an HDLC or RS-232 type of interface. If there is no lower-layer interface element, or there is no
ifEntry for the element, or the element can not be identified, then the value of this object is 0. For example, suppose
that PPP is operating over a serial port. This would use two entries in the ifTable. The PPP could be running over
“interface” number 123 and the serial port could be running over “interface” number 987. Therefore, ifSpecific.123
would contain the OBJECT IDENTIFIER ppp pppLinkStatusPhysicalIndex.123 would contain 987, and ifSpecific.987 would contain the OBJECT IDENTIFIER for the serial-port's media- specific MIB.
5.21.4.1.1.2
pppLinkStatusBadAddresses
The number of packets received with an incorrect Address Field. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.
5.21.4.1.1.3
pppLinkStatusBadControls
The number of packets received on this link with an incorrect Control Field. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.
5.21.4.1.1.4
pppLinkStatusPacketTooLongs
The number of received packets that have been discarded because their length exceeded the MRU. This counter is a
component of the ifInErrors variable that is associated with the interface that represents this PPP Link. NOTE, packets which are longer than the MRU but which are successfully received and processed are NOT included in this count.
5.21.4.1.1.5
pppLinkStatusBadFCSs
The number of received packets that have been discarded due to having an incorrect FCS. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.
5.21.4.1.1.6
pppLinkStatusLocalMRU
The current value of the MRU for the local PPP Entity. This value is the MRU that the remote entity is using when
sending packets to the local PPP entity. The value of this object is meaningful only when the link has reached the
open state (ifOperStatus is up).
5.21.4.1.1.7
pppLinkStatusRemoteMRU
The current value of the MRU for the remote PPP Entity. This value is the MRU that the local entity is using when
411
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
sending packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the
open state (ifOperStatus is up).
5.21.4.1.1.8
pppLinkStatusLocalToPeerACCMap
The current value of the ACC Map used for sending packets from the local PPP entity to the remote PPP entity. The
value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
5.21.4.1.1.9
pppLinkStatusPeerToLocalACCMap
The ACC Map used by the remote PPP entity when transmitting packets to the local PPP entity. The value of this
object is meaningful only when the link has reached the open state (ifOperStatus is up).
5.21.4.1.1.10
pppLinkStatusLocalToRemoteProtocolCompression
Indicates whether the local PPP entity will use Protocol Compression when transmitting packets to the remote PPP
entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
5.21.4.1.1.11
pppLinkStatusRemoteToLocalProtocolCompression
Indicates whether the remote PPP entity will use Protocol Compression when transmitting packets to the local PPP
entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
5.21.4.1.1.12
pppLinkStatusLocalToRemoteACCompression
Indicates whether the local PPP entity will use Address and Control Compression when transmitting packets to the
remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus
is up).
5.21.4.1.1.13
pppLinkStatusRemoteToLocalACCompression
Indicates whether the remote PPP entity will use Address and Control Compression when transmitting packets to the
local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is
up).
5.21.4.1.1.14
pppLinkStatusTransmitFcsSize
The size of the Frame Check Sequence (FCS) in bits that the local node will generate when sending packets to the
remote node. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is
up).
Valid Object Value(s)
•
•
16
32
5.21.4.1.1.15
pppLinkStatusReceiveFcsSize
The size of the Frame Check Sequence (FCS) in bits that the remote node will generate when sending packets to the
local node. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
Valid Object Value(s)
•
•
16
32
412
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
5.21.4.1.2
pppLinkConfigTable
A table containing the LCP configuration parameters for this PPP Link. These variables represent the initial configuration of the PPP Link. The actual values of the parameters may be changed when the link is brought up via the LCP
options negotiation mechanism.
This table is a sequence of pppLinkConfigEntry which contains configuration information about a particular PPP
Link.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pppLinkConfigTable - { pppLink 2 }
pppLinkConfigEntry - { pppLinkConfigTable 1 }
1.3.6.1.2.1.10.23.1.1.2
1.3.6.1.2.1.10.23.1.1.2.1
Table 227: pppLinkConfigTable
Object
OID
Syntax
Access
Status
Supported
pppLinkConfigInitialMRU
{ pppLinkConfigEntry 1 }
INTEGER
(0…2147483647)
read-write
mandatory
Y
pppLinkConfigReceiveACCMap
{ pppLinkConfigEntry 2 }
OCTET STRING(SIZE (4))
read-write
mandatory
Y
pppLinkConfigTransmitACCMap
{ pppLinkConfigEntry 3 }
OCTET STRING(SIZE (4))
read-write
mandatory
Y
pppLinkConfigMagicNumber
{ pppLinkConfigEntry 4 }
INTEGER
false(1)
true(2)
read-write
mandatory
Y
pppLinkConfigFcsSize
{ pppLinkConfigEntry 5 }
INTEGER(0…128)
read-write
mandatory
Y
5.21.4.1.2.1
pppLinkConfigInitialMRU
The initial Maximum Receive Unit (MRU) that the local PPP entity will advertise to the remote entity. If the value of
this variable is 0 then the local PPP entity will not advertise any MRU to the remote entity and the default MRU will
be assumed. Changing this object will have effect when the link is next restarted.
The MIB recommended default value for this object is { 1500 }.
5.21.4.1.2.2
pppLinkConfigReceiveACCMap
The Asynchronous-Control-Character-Map (ACC) that the local PPP entity requires for use on its receive side. In
effect, this is the ACC Map that is required in order to ensure that the local modem will successfully receive all characters. The actual ACC map used on the receive side of the link will be a combination of the local node's pppLinkConfigReceiveACCMap and the remote node's pppLinkConfigTransmitACCMap. Changing this object will have
effect when the link is next restarted.
413
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
The MIB recommended default value for this object is { ffffffffh }.
5.21.4.1.2.3
pppLinkConfigTransmitACCMap
The Asynchronous-Control-Character-Map (ACC) that the local PPP entity requires for use on its transmit side. In
effect, this is the ACC Map that is required in order to ensure that all characters can be successfully transmitted
through the local modem. The actual ACC map used on the transmit side of the link will be a combination of the local
node's pppLinkConfigTransmitACCMap and the remote node's pppLinkConfigReceiveACCMap. Changing this
object will have effect when the link is next restarted.
The MIB recommended default value for this object is { ffffffffh }.
5.21.4.1.2.4
pppLinkConfigMagicNumber
• false(1)
• true(2)
If true(2) then the local node will attempt to perform Magic Number negotiation with the remote node. If false(1) then
this negotiation is not performed. In any event, the local node will comply with any magic number negotiations
attempted by the remote node, per the PPP specification. Changing this object will have effect when the link is next
restarted.
The MIB recommended default value for this object is { false }.
5.21.4.1.2.5
pppLinkConfigFcsSize
The size of the FCS, in bits, the local node will attempt to negotiate for use with the remote node. Regardless of the
value of this object, the local node will comply with any FCS size negotiations initiated by the remote node, per the
PPP specification. Changing this object will have effect when the link is next restarted.
The MIB recommended default value for this object is { 16 }.
5.21.4.2
PPP LQR Group
This group provides the basic MIB variables that apply to the PPP LQR Protocol. This group provides MIB access to
the information required for LQR processing. This group contains two tables, one containing status information and
the other configuration information. The configuration table is split off of the status so that it may be placed in a separate MIB View for security purposes.
OID:
•
pppLqr
5.21.4.2.1
- { pppLcp 2 }
1.3.6.1.2.1.10.23.1.2
pppLqrTable
Table containing the LQR parameters and statistics for the local PPP entity.
This table is a sequence of pppLqrEntry which contains LQR information for a particular PPP link. A PPP link will
have an entry in this table if and only if LQR Quality Monitoring has been successfully negotiated for said link.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pppLqrTable
pppLqrEntry
- { pppLqr 1 }
- { pppLqrTable 1 }
1.3.6.1.2.1.10.23.1.2.1
1.3.6.1.2.1.10.23.1.2.1.1
414
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
Table 228: pppLqrTable
Object
OID
Syntax
Access
Status
Supported
pppLqrQuality
{ pppLqrEntry 1 }
INTEGER
good(1)
bad(2)
not-determined(3)
read-only
mandatory
N
pppLqrInGoodOctets
{ pppLqrEntry 2 }
Counter
read-only
mandatory
N
pppLqrLocalPeriod
{ pppLqrEntry 3 }
INTEGER
(1…2147483648)
read-only
mandatory
N
pppLqrRemotePeriod
{ pppLqrEntry 4 }
INTEGER
(1…2147483648)
read-only
mandatory
N
pppLqrOutLQRs
{ pppLqrEntry 5 }
Counter
read-only
mandatory
N
pppLqrInLQRs
{ pppLqrEntry 6 }
Counter
read-only
mandatory
N
5.21.4.2.1.1
pppLqrQuality
The current quality of the link as declared by the local PPP entity's Link-Quality Management modules. No effort is
made to define good or bad, nor the policy used to determine it. The not-determined value indicates that the entity
does not actually evaluate the link's quality. This value is used to disambiguate the “determined to be good” case from
the “no determination made and presumed to be good” case.
5.21.4.2.1.2
pppLqrInGoodOctets
The LQR InGoodOctets counter for this link.
5.21.4.2.1.3
pppLqrLocalPeriod
The LQR reporting period, in hundredths of a second that is in effect for the local PPP entity.
5.21.4.2.1.4
pppLqrRemotePeriod
The LQR reporting period, in hundredths of a second, that is in effect for the remote PPP entity.
5.21.4.2.1.5
pppLqrOutLQRs
The value of the OutLQRs counter on the local node for the link identified by ifIndex.
5.21.4.2.1.6
pppLqrInLQRs
The value of the InLQRs counter on the local node for the link identified by the ifIndex.
5.21.4.2.2
pppLqrConfigTable
Table containing the LQR Configuration parameters for the local PPP entity.
This table is a sequence of pppLqrConfigEntry which contains LQR configuration information for a particular PPP
link.
415
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pppLqrConfigTable
pppLqrConfigEntry
- { pppLqr 2 }
- { pppLqrConfigTable 1 }
1.3.6.1.2.1.10.23.1.2.2
1.3.6.1.2.1.10.23.1.2.2.1
Table 229: pppLqrConfigTable
Object
OID
Syntax
Access
Status
Supported
pppLqrConfigPeriod
{ pppLqrConfigEntry 1 }
INTEGER
(0…2147483647)
read-write
mandatory
N
pppLqrConfigStatus
{ pppLqrConfigEntry 2 }
INTEGER
disabled(1)
enabled(2)
read-write
mandatory
N
5.21.4.2.2.1
pppLqrConfigPeriod
The LQR Reporting Period that the local PPP entity will attempt to negotiate with the remote entity, in units of hundredths of a second. Changing this object will have effect when the link is next restarted.
The MIB recommended default value for this object is { 0 }.
5.21.4.2.2.2
pppLqrConfigStatus
If enabled(2) then the local node will attempt to perform LQR negotiation with the remote node. If disabled(1) then
this negotiation is not performed. In any event, the local node will comply with any magic number negotiations
attempted by the remote node, per the PPP specification. Changing this object will have effect when the link is next
restarted. Setting this object to the value disabled(1) has the effect of invalidating the corresponding entry in the
pppLqrConfigTable object. It is an implementation-specific matter as to whether the agent removes an invalidated
entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents
that corresponds to entries not currently in use.
The MIB recommended default value for this object is { enabled }.
5.21.4.3
PPP LQR Extensions Group
The intent of this group is to allow external implementation of the policy mechanisms that are used to declare a link to
be bad or not.
It is not practical to examine the MIB objects which are used to generate LQR packets since LQR policies tend to
require synchronization of the values of all data used to determine Link Quality; i.e. the values of the relevant
counters must all be taken at the same instant in time.
5.21.4.3.1
pppLqrExtnsTable
Table containing additional LQR information for the local PPP entity.
This table is a sequence of pppLqrExtnsEntry which contains extended LQR information for a particular PPP link.
416
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
Assuming that this group has been implemented, a PPP link will have an entry in this table if and only if LQR Quality
Monitoring has been successfully negotiated for said link.
Extended LQR information for a particular PPP link. Assuming that this group has been implemented, a PPP link will
have an entry in this table if and only if LQR Quality Monitoring has been successfully negotiated for said link.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pppLqrExtnsTable
pppLqrExtnsEntry
- { pppLqr 3 }
- { pppLqrExtnsTable 1 }
1.3.6.1.2.1.10.23.1.2.3
1.3.6.1.2.1.10.23.1.2.3.1
Table 230: pppLqrExtnsTable
Object
OID
Syntax
Access
Status
Supported
pppLqrExtnsLastReceivedLqrPacket
{ pppLqrExtnsEntry 1 }
OCTET STRING
(SIZE(68))
read-only
mandatory
N
5.21.4.3.1.1
pppLqrExtnsLastReceivedLqrPacket
This object contains the most recently received LQR packet. The format of the packet is as described in the LQM Protocol specification. All fields of the packet, including the “save” fields, are stored in this object.
The LQR packet is stored in network byte order. The LAP-B and PPP headers are not stored in this object; the first
four octets of this variable contain the Magic-Number field, the second four octets contain the LastOutLQRs field and
so on. The last four octets of this object contain the SaveInOctets field of the LQR packet.
5.21.4.4
PPP Tests
The extensions to the interface table define a table through which the network manager can instruct the managed
object to perform various tests of the interface. This is the ifTestTable.
The PPP MIB defines two such tests.
•
•
PPP Echo Test
PPP Discard Test
OIDs:
•
pppTests - { pppLcp 3 }
1.3.6.1.2.1.10.23.1.3
Table 231: PPP Tests (1 of 2)
Object
OID
Supported
pppEchoTest
{ pppTests 1 }
N
417
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-LCP-MIB — RFC 1471
Table 231: PPP Tests (2 of 2)
Object
OID
Supported
pppDiscardTest
{ pppTests 2 }
N
5.21.4.4.1
pppEchoTest
Invoking this test causes a PPP Echo Packet to be sent on the line. ifTestResult returns success(2) if the echo response
came back properly. It returns failed(7) if the response did not properly return. The definition of proper in this context
is left to the discretion of the implementor.
5.21.4.4.2
pppDiscardTest
Invoking this test causes a PPP Discard Packet to be sent on the line. ifTestResult returns success(2) if the discard
packet was successfully transmitted and failed(7) if an error was detected on transmission. The definition of transmission error in this context is left to the discretion of the implementor.
418
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
5.22 PPP-BRIDGE-NCP-MIB — RFC 1474
5.22.1
Introduction
The PPP Bridge NCP Group. Implementation of this group is mandatory for all PPP implementations that support
MAC Bridging over PPP (RFC1220).
5.22.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.22.3
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
mgmt
mib-2
transmission
ppp
pppBridge
5.22.4
MIB Objects
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ mgmt 1 }
{ mib-2 10 }
{ transmission 23 }
{ ppp 4 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.10
1.3.6.1.2.1.10.23
1.3.6.1.2.1.10.23.4
Table 232: PPP-BRIDGE-NCP-MIB Objects
Object
OID
Syntax
Access
Status
Supported
pppBridgeTable
{ pppBridge 1 }
SEQUENCE OF
pppBridgeEntry
not-accessible
mandatory
Y
pppBridgeConfigTable
{ pppBridge 2 }
SEQUENCE OF
pppBridgeConfigEntry
not-accessible
mandatory
Y
pppBridgeMediaTable
{ pppBridge 3 }
SEQUENCE OF
pppBridgeMediaEntry
not-accessible
mandatory
Y
pppBridgeMediaConfigTable
{ pppBridge 4 }
SEQUENCE OF
pppBridgeMediaConfigEntry
not-accessible
mandatory
Y
5.22.4.1
pppBridgeTable
Table containing the parameters and statistics for the local PPP entity that are related to the operation of Bridging
over the PPP.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
pppBridgeTable
- { pppBridge 1 }
1.3.6.1.2.1.10.23.4.1
419
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
•
pppBridgeEntry
- { pppBridgeTable 1 }
1.3.6.1.2.1.10.23.4.1.1
Table 233: pppBridgeTable
Object
OID
Syntax
Access
Status
Supported
pppBridgeOperStatus
{ pppBridgeEntry 1 }
INTEGER
opened(1)
not-opened(2)
read-only
mandatory
Y
pppBridgeLocalToRemoteTinygramCompression
{ pppBridgeEntry 2 }
INTEGER
false(1)
true(2)
read-only
mandatory
Y
pppBridgeRemoteToLocalTinygramCompression
{ pppBridgeEntry 3 }
INTEGER
false(1)
true(2)
read-only
mandatory
Y
pppBridgeLocalToRemoteLanId
{ pppBridgeEntry 4 }
INTEGER
false(1)
true(2)
read-only
mandatory
Y
pppBridgeRemoteToLocalLanId
{ pppBridgeEntry 5 }
INTEGER
false(1)
true(2)
read-only
mandatory
Y
5.22.4.1.1
pppBridgeOperStatus
The following values are defined for this object:
•
•
opened(1)
not-opened(2)
The operational status of the Bridge network protocol. If the value of this object is up then the finite state machine for
the Bridge network protocol has reached the Opened state.
5.22.4.1.2
pppBridgeLocalToRemoteTinygramCompression
The following values are defined for this object:
•
•
false(1)
true(2)
Indicates whether the local node will perform Tinygram Compression when sending packets to the remote entity. If
false then the local entity will not perform Tinygram Compression. If true then the local entity will perform Tinygram
Compression. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
5.22.4.1.3
pppBridgeRemoteToLocalTinygramCompression
The following values are defined for this object:
•
•
false(1)
true(2)
420
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
If false(1) then the remote entity is not expected to perform Tinygram Compression. If true then the remote entity is
expected to perform Tinygram Compression. The value of this object is meaningful only when the link has reached
the open state (pppBridgeOperStatus is opened). The following values are defined for this object:
5.22.4.1.4
pppBridgeLocalToRemoteLanId
The following values are defined for this object:
•
•
false(1)
true(2)
Indicates whether the local node will include the LAN Identification field in transmitted packets or not. If false(1)
then the local node will not transmit this field, true(2) means that the field will be transmitted. The value of this object
is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
5.22.4.1.5
pppBridgeRemoteToLocalLanId
The following values are defined for this object:
•
•
false(1)
true(2)
Indicates whether the remote node has indicated that it will include the LAN Identification field in transmitted packets or not. If false(1) then the field will not be transmitted, if true(2) then the field will be transmitted. The value of
this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
5.22.4.2
pppBridgeConfigTable
Table containing the parameters and statistics for the local PPP entity that are related to the operation of Bridging
over the PPP. Each entry contains bridging configuration information for a particular PPP link.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pppBridgeConfigTable - { pppBridge 2 }
pppBridgeConfigEntry - { pppBridgeConfigTable 1 }
1.3.6.1.2.1.10.23.4.2
1.3.6.1.2.1.10.23.4.2.1
Table 234: pppBridgeConfigTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pppBridgeConfigAdminStatus
{ pppBridgeConfigEntry 1 }
INTEGER
open(1)
close(2)
read-write
mandatory
Y
pppBridgeConfigTinygram
{ pppBridgeConfigEntry 2 }
INTEGER
false(1)
true(2)
read-onlya
mandatory
Y
421
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
Table 234: pppBridgeConfigTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pppBridgeConfigRingId
{ pppBridgeConfigEntry 3 }
INTEGER
false(1)
true(2)
read-write
mandatory
N
pppBridgeConfigLineId
{ pppBridgeConfigEntry 4 }
INTEGER
false(1)
true(2)
read-write
mandatory
N
pppBridgeConfigLanId
{ pppBridgeConfigEntry 5 }
INTEGER
false(1)
true(2)
read-write
mandatory
N
a. The access is restricted to read-only in the BitStorm 2600 and GranDSLAM 4200 IP DSLAM product.
5.22.4.2.1
pppBridgeConfigAdminStatus
The following values are defined for this object:
•
•
open(1)
close(2)
The immediate desired status of the Bridging network protocol. Setting this object to open will inject an administrative open event into the Bridging network protocol’s finite state machine. Setting this object to close will inject an
administrative close event into the Bridging network protocol’s finite state machine.
5.22.4.2.2
pppBridgeConfigTinygram
The following values are defined for this object:
•
•
false(1)
true(2)
- MIB recommended default
If false then the local BNCP entity will not initiate the Tinygram Compression Option Negotiation. If true then the
local BNCP entity will initiate negotiation of this option.
Valid Object Value(s)
This object is restricted to read-only and will only return false(1).
5.22.4.2.3
pppBridgeConfigRingId
The following values are defined for this object:
•
•
false(1)
true(2)
- MIB recommended default
If false then the local PPP Entity will not initiate a Remote Ring Identification Option negotiation. If true then the
local PPP entity will initiate this negotiation. This MIB object is relevant only if the interface is for 802.5 Token Ring
bridging.
5.22.4.2.4
pppBridgeConfigLineId
The following values are defined for this object:
422
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
•
•
false(1)
true(2)
- MIB recommended default
If false then the local PPP Entity is not to initiate a Line Identification Option negotiation. If true then the local PPP
entity will initiate this negotiation. This MIB object is relevant only if the interface is for 802.5 Token Ring bridging.
5.22.4.2.5
pppBridgeConfigLanId
The following values are defined for this object:
•
•
false(1)
true(2)
- MIB recommended default
If false then the local BNCP entity will not initiate the LAN Identification Option Negotiation. If true then the local
BNCP entity will initiate negotiation of this option.
5.22.4.3
pppBridgeMediaTable
Table identifying which MAC media types are enabled for the Bridging NCPs. Each entry is the status of a specific
MAC Type for a specific PPP Link.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pppBridgeMediaMacType
OIDs:
•
•
pppBridgeMediaTable - { pppBridge 3 }
pppBridgeMediaEntry - { pppBridgeMediaTable 1 }
1.3.6.1.2.1.10.23.4.3
1.3.6.1.2.1.10.23.4.3.1
Table 235: pppBridgeMediaTable
Object
OID
Syntax
Access
Status
Supported
pppBridgeMediaMacType
{ pppBridgeMediaEntry 1 }
INTEGER
(0…2147483647)
read-only
mandatory
Y
pppBridgeMediaLocalStatus
{ pppBridgeMediaEntry 2 }
INTEGER
accept(1)
dont-acceip(2)
read-only
mandatory
Y
pppBridgeMediaRemoteStatus
{ pppBridgeMediaEntry 3 }
INTEGER
accept(1)
dont-acceip(2)
read-only
mandatory
Y
5.22.4.3.1
pppBridgeMediaMacType
The MAC type for which this entry in the pppBridgeMediaTable is providing status information. Valid values for this
object are defined in Section 6.6 MAC Type Support Selection of RFC1220 (Bridging Point-to-Point Protocol).
423
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
5.22.4.3.2
pppBridgeMediaLocalStatus
The following values are defined for this object:
•
•
accept(1)
dont-accept(2)
Indicates whether the local PPP Bridging Entity will accept packets of the protocol type identified in pppBridgeMediaMacType on the PPP link identified by ifIndex or not. If this object is accept then any packets of the indicated MAC
type will be received and properly processed. If this object is dont- accept then received packets of the indicated MAC
type will not be properly processed.
5.22.4.3.3
pppBridgeMediaRemoteStatus
The following values are defined for this object:
•
•
accept(1)
dont-accept(2)
Indicates whether the local PPP Bridging Entity believes that the remote PPP Bridging Entity will accept packets of
the protocol type identified in pppBridgeMediaMacType on the PPP link identified by ifIndex or not.
5.22.4.4
pppBridgeMediaConfigTable
Table identifying which MAC media types are enabled for the Bridging NCPs. Each entry contains the status of a specific MAC Type for a specific PPP Link.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pppBridgeMediaConfigMacType
OIDs:
•
•
pppBridgeMediaConfigTable - { pppBridge 4 }
pppBridgeMediaConfigEntry - { pppBridgeMediaTable 1 }
1.3.6.1.2.1.10.23.4.4
1.3.6.1.2.1.10.23.4.4.1
Table 236: pppBridgeMediaConfigTable
Object
OID
Syntax
Access
Status
Supported
pppBridgeMediaConfigMacType
{ pppBridgeMediaConfigEntry 1 }
INTEGER
(0…2147483647)
read-write
mandatory
Y
pppBridgeMediaConfigLocalStatus
{ pppBridgeMediaConfigEntry 2 }
INTEGER
accept(1)
dont-accept(2)
read-write
mandatory
Y
5.22.4.4.1
pppBridgeMediaConfigMacType
The MAC type for which this entry in the pppBridgeMediaConfigTable is providing status information. Valid values
for this object are defined in Section 6.6 MAC Type Support Selection of RFC1220 (Bridging Point-to-Point Protocol).
424
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PPP-BRIDGE-NCP-MIB — RFC 1474
5.22.4.4.2
pppBridgeMediaConfigLocalStatus
The following values are defined for this object:
•
•
accept(1)
dont-accept(2)
Indicates whether the local PPP Bridging Entity should accept packets of the protocol type identified in pppBridgeMediaConfigMacType on the PPP link identified by ifIndex or not. Setting this object to the value dont-accept has the
affect of invalidating the corresponding entry in the pppBridgeMediaConfigTable object. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations
must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Changing
this object will have effect when the link is next restarted.
425
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23 PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23.1
Introduction
This MIB Module allows a user to reset a device in the DSLAM, as well as perform various operations related to the
storage and retrieval of firmware and configuration files on devices.
The version of the MIB used for this document had a LAST-UPDATED of 0011211800Z which decodes to
November 21, 2002.
5.23.2
Textual Conventions
The following “special” textual conventions are made or referenced in this MIB:
•
5.23.3
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ResetStates
OIDs
iso
org
dod
internet
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-mpe
- This object defines the enumerations of values that can be applied to the reset object.
— Syntax
INTEGER
• noOp(1)
• reset(2)
• resetToFactoryDefaults(3)
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 12 }
mpeDevControl
mpeDevControlMIBObjects
mpeDevControlMIBTraps
mpeDevControlMIBTrapsV2
mpeDevHwControl
mpeDevFileXferConfig
mpeDevFirmwareControl
mpeDevTestControl
-
1
1.3
1.3.6
1.3.6.1
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.12
{ pdn-mpe 10 }
{ mpeDevControl 1 }
{ mpeDevControl 2 }
{ mpeDevControlMIBObjects 0 }
{ mpeDevControlMIBObjects 1 }
{ mpeDevControlMIBObjects 2 }
{ mpeDevControlMIBObjects 3 }
{ mpeDevControlMIBObjects 4 }
426
1.3.6.1.4.1.1795.2.24.12.10
1.3.6.1.4.1.1795.2.24.12.10.1
1.3.6.1.4.1.1795.2.24.12.10.2
1.3.6.1.4.1.1795.2.24.12.10.1.0
1.3.6.1.4.1.1795.2.24.12.10.1.1
1.3.6.1.4.1.1795.2.24.12.10.1.2
1.3.6.1.4.1.1795.2.24.12.10.1.3
1.3.6.1.4.1.1795.2.24.12.10.1.4
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23.4
MIB Objects
Table 237: PDN-MPE-DEVICE-CONTROL-MIB Objects
Object
OID
Description
Supported
mpeDevHwControl
{ mpeDevControlMIBObjects 1 }
Hardware Control Group
Y
mpeDevFileXferConfig
{ mpeDevControlMIBObjects 2 }
File Transfer Group
N
mpeDevFirmwareControl
{ mpeDevControlMIBObjects 3 }
Firmware Control Group
N
mpeDevTestControl
{ mpeDevControlMIBObjects 4 }
Device Specific Test Group
N
5.23.4.1
mpeDevHwControl
The Hardware Control Group.
Table 238: mpeDevHwControl
Object
OID
Syntax
Access
Status
Supported
mpeDevControlTable
{ mpeDevHwControl 1 }
SEQUENCE OF
mpeDevControlEntry
not-accessible
current
Y
mpeDevControlSelfTestTable
{ mpeDevHwControl 2 }
SEQUENCE OF
devControlSelfTestEntry
not-accessible
current
N
5.23.4.1.1
mpeDevControlTable
A table that contains generic information about Card Control.
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
OIDs:
•
•
mpeDevControlTable
mpeDevControlEntry
- { mpeDevHwControl 1 }
- { mpeDevControlTable 1 }
427
1.3.6.1.4.1.1795.2.24.12.10.1.1.1
1.3.6.1.4.1.1795.2.24.12.10.1.1.1.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
Table 239: mpeDevControlTable
Object
OID
Syntax
Access
Status
Supported
mpeDevControlReset
{ mpeDevControlEntry 1 }
ResetStates
read-create
current
Y
5.23.4.1.1.1
mpeDevControlReset
Writing the value reset (2) to this object initiates a Hardware power-on reset of the device. Writing the value
resetToFactoryDefaults (3) causes the device to re-configure itself with factory defaults. The value read from this
object is noOp(1).
Valid Object Value(s)
There are two types of reset: hardware reset and software reset. A hardware reset will cause the coldStart trap to be
sent while a software reset will cause a warmStart trap to be sent.
Table 240: mpeDevControlReset
Locator String
entPhysicalIndex
reset(2)
System
System
Hardware Reset
Unit
Unit
Hardware Reset
5.23.4.1.2
mpeDevControlSelfTestTable
A table containing information to control device specific Self-Test operations.
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
OIDs:
•
•
mpeDevControlSelfTestTable
devControlSelfTestEntry
- { mpeDevHwControl 2 }1.3.6.1.4.1.1795.2.24.12.10.1.1.2
- { mpeDevControlSelfTestTable 1 }1.3.6.1.4.1.1795.2.24.12.10.1.1.2.1
428
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
Table 241: mpeDevControlSelfTestTable
Object
OID
Syntax
Access
Status
Supported
mpeDevControlExtendedSelfTest
{ devControlSelfTestEntry 1 }
INTEGER
noOp(1)
enableExtendSelfTestAndReset(2)
read-write
current
N
5.23.4.1.2.1
mpeDevControlExtendedSelfTest
The following values are defined for this object:
•
•
noOp(1)
enableExtendSelfTestAndReset(2)
This object is used to start the extended Power-On Self-Test test. Writing the value enableExtendSelfTestAndReset(2)
to this object resets the device and puts it into extended Power-On Self-Test mode. During device initialization, the
extended Self-Test would be carried out first and then the device would carry out its normal boot operation. The value
read from this object is noOp(1). Writing back the same value, noOp(1) will not start the test. Note that if extended
Self-Test fails for some reason, after re-initialization, the value of this object will default to
enableExtendSelfTestAndReset(2) again unless the manager explicitly chooses not to do so.
5.23.4.2
mpeDevFileXferConfig
The File Transfer Config Group.
Table 242: mpeDevFileXferConfig
Object
OID
Syntax
Access
Status
Supported
mpeDevFileXferConfigTable
{ mpeDevFileXferConfig 1 }
SEQUENCE OF
mpeDevFileXferConfigEntry
not-accessible
current
N
5.23.4.2.1
mpeDevFileXferConfigTable
The Paradyne FileXfer Client Config Table.
Use of the File Tranfer MIB could be used with other MIBS in the following manner:
•
•
•
•
Use another MIB/means to verify available space /make room for a file to be transferred to this device
Use this MIB to download the file
Use another MIB/means to select the file you want to make active if your selecting firmware for example.
Use another MIB/means to reset the device.
A management station wishing to initiate a file transfer needs to create an entry in this table. To do so, you must first
identify the entPhysicalIndex of the device you intend to do the transfer with. You should then create the associated
instance of the row status It must also, either in the same or in successive PDUs, create an instance of
429
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
mpeDevFileXferFileName, mpeDevFileXferFileType, mpeDevFileXferServerIpAddress,
mpeDevFileXferOperation.
It should also modify the default values for the other configuration objects if the defaults are not appropriate.
Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set
request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may
be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for
the non-defaulted configuration objects.
Once the MpeDevFileXferConfigEntry request has been created (that is, the mpeDevFileXferRowStatus has been
made active), the entry cannot be modified - the only operation possible after this is to delete the row.
Once the request completes, the management station should retrieve the values of the status objects of interest, and
should then delete the entry. In order to prevent old entries from clogging the table, entries could be aged out, but an
entry will never be deleted within 5 minutes of completing.
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
OIDs:
•
•
mpeDevFileXferConfigTable - { mpeDevFileXferConfig 1 }
mpeDevFileXferConfigEntry - { mpeDevFileXferConfigTable 1 }
1.3.6.1.4.1.1795.2.24.12.10.1.2.1
1.3.6.1.4.1.1795.2.24.12.10.1.2.1.1
Table 243: mpeDevFileXferConfigTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
mpeDevFileXferFileName
{ mpeDevFileXferConfigEntry 1 }
DisplayString
read-create
current
N
mpeDevFileXferCopyProtocol
{ mpeDevFileXferConfigEntry 2 }
INTEGER
tftp(1)
ftp(2)
read-create
current
N
mpeDevFileXferFileType
{ mpeDevFileXferConfigEntry 3 }
INTEGER
firmware(1)
config(2)
read-create
current
N
mpeDevFileXferServerIpAddress
{ mpeDevFileXferConfigEntry 4 }
IpAddress
read-create
current
N
mpeDevFileXferUserName
{ mpeDevFileXferConfigEntry 5 }
DisplayString
read-create
current
N
mpeDevFileXferUserPassword
{ mpeDevFileXferConfigEntry 6 }
DisplayString
read-create
current
N
mpeDevFileXferOperation
{ mpeDevFileXferConfigEntry 7 }
INTEGER
get(1)
put(2)
read-create
current
N
mpeDevFileXferPktsSent
{ mpeDevFileXferConfigEntry 8 }
Counter32
read-only
current
N
mpeDevFileXferPktsRecv
{ mpeDevFileXferConfigEntry 9 }
Counter32
read-only
current
N
mpeDevFileXferOctetsSent
{ mpeDevFileXferConfigEntry 10 }
Counter32
read-only
current
N
430
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
Table 243: mpeDevFileXferConfigTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
mpeDevFileXferOctetsRecv
{ mpeDevFileXferConfigEntry 11 }
Counter32
read-only
current
N
mpeDevFileXferOwnerString
{ mpeDevFileXferConfigEntry 12 }
OCTET STRING
(SIZE(0…255))
read-create
current
N
mpeDevFileXferStatus
{ mpeDevFileXferConfigEntry 13 }
INTEGER
none(1)
success(2)
failure(3)
inprogress(4)
read-only
current
N
mpeDevFileXferErrorStatus
{ mpeDevFileXferConfigEntry 14 }
Integer32
read-only
current
N
mpeDevFileXferSendEvent
{ mpeDevFileXferConfigEntry 15 }
INTEGER
active(1)
inactive(2)
read-create
current
N
mpeDevFileXferRowStatus
{ mpeDevFileXferConfigEntry 16 }
RowStatus
read-create
current
N
mpeDevFileXferXferTime
{ mpeDevFileXferConfigEntry 17 }
TimeTicks
read-only
current
N
mpeDevFileXferFileFormat
{ mpeDevFileXferConfigEntry 18 }
INTEGER
ascii(1)
binary(2)
read-create
current
N
5.23.4.2.1.1
mpeDevFileXferFileName
This object contains the name of the file that is to be transferred.
5.23.4.2.1.2
mpeDevFileXferCopyProtocol
The transfer protocol that should be used to copy the file across the network. If the file transfer is to occur locally on
the SNMP agent, the method of transfer is left up to the implementation, and is not restricted to the protocols below.
•
•
tftp(1)
ftp(2)
The default value is tftp(1).
5.23.4.2.1.3
mpeDevFileXferFileType
Specifies the type of file your want to transfer. The following values are defined for this object:
•
•
firmware(1)
config(2)
5.23.4.2.1.4
mpeDevFileXferServerIpAddress
This object contains the file transfer server’s IP address.
5.23.4.2.1.5
mpeDevFileXferUserName
This object contains the username if a username is needed to login to the server.
431
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23.4.2.1.6
mpeDevFileXferUserPassword
This object contains the password if a password is needed to login to the server. This object will return null on a read
operation.
5.23.4.2.1.7
mpeDevFileXferOperation
This object contains the operation the file transfer wants to perform. The following values are defined for this object:
•
•
get(1)
put(2)
5.23.4.2.1.8
mpeDevFileXferPktsSent
This object contains the number of packets sent to the server at the time of interrogation.
5.23.4.2.1.9
mpeDevFileXferPktsRecv
This object contains the number of packets received from the server at the time of interrogation.
5.23.4.2.1.10
mpeDevFileXferOctetsSent
This object contains the number of octets sent to the server at the time of interrogation.
5.23.4.2.1.11
mpeDevFileXferOctetsRecv
This object contains the number of octets received from the server at the time of interrogation.
5.23.4.2.1.12
mpeDevFileXferOwnerString
The entity which currently has the “ownership” required to invoke the operation on this index.
5.23.4.2.1.13
mpeDevFileXferStatus
This object contains the status of the file transfer. The following values are defined for this object:
•
•
•
•
none(1)
success(2)
failure(3)
inprogress(4)
5.23.4.2.1.14
mpeDevFileXferErrorStatus
This object contains the reason code of the failure determined in mpeDevFileXferStatus. The reason code are specific
to the file transfer protocol.
Please refer to the file transfer protocols respective RFC for clarification of the error code value meanings.
•
•
RFC 1350 - TFTP Error Codes
RFC 959 - FTP Error Codes
5.23.4.2.1.15
mpeDevFileXferSendEvent
This object indicates whether or not to send the mpeDevFileXferEvent event trap. The following values are defined
for this object:
•
•
active(1)
inactive(2)
432
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23.4.2.1.16
mpeDevFileXferRowStatus
This object is used to create a new row or delete an existing row in this table.
5.23.4.2.1.17
mpeDevFileXferXferTime
This object indicates the elapsed time (in hundredths of a second) of the file transfer.
5.23.4.2.1.18
mpeDevFileXferFileFormat
The following values are defined for this object:
•
•
ascii(1)
binary(2)
This object contains the file representation type. A file representation type of ascii implies an ASCII, non-print text
file. A file representation type of binary implies an binary image file.
The default file representation type is binary(2).
5.23.4.3
mpeDevFirmwareControl
The Firmware Control Group.
Table 244: mpeDevFirmwareControl
Object
OID
Syntax
Access
Status
Supported
mpeDevFirmwareControlTable
{ mpeDevFirmwareControl 1 }
SEQUENCE OF
mpeDevFirmwareControlEntry
not-accessible
current
N
5.23.4.3.1
mpeDevFirmwareControlTable
A list of the current Firmware Releases and their associated status. Each Firmware Release is indexed by a number
from 1 to N. The user is able to view the Firmware Release String and Operational Status of the release (valid or
invalid) and activate a valid Firmware Release by changing the Administration Status to active.
Index(es):
•
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
mpeDevFirmwareControlIndex
OIDs:
•
•
mpeDevFirmwareControlTable - { mpeDevFirmwareControl 1 }
1.3.6.1.4.1.1795.2.24.12.10.1.3.1
mpeDevFirmwareControlEntry - { mpeDevFirmwareControlTable 1 }1.3.6.1.4.1.1795.2.24.12.10.1.3.1.1
433
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
Table 245: mpeDevFirmwareControlTable
Object
OID
Syntax
Access
Status
Supported
mpeDevFirmwareControlIndex
{ mpeDevFirmwareControlEntry 1 }
Integer32
read-only
current
N
mpeDevFirmwareControlRelease
{ mpeDevFirmwareControlEntry 2 }
DisplayString
(SIZE (1…16))
read-only
current
N
mpeDevFirmwareControlOperStatus
{ mpeDevFirmwareControlEntry 3 }
INTEGER
valid(1)
invalid(2)
unknown(3)
read-only
current
N
mpeDevFirmwareControlAdminStatus
{ mpeDevFirmwareControlEntry 4 }
INTEGER
active(1)
inactive(2)
read-create
current
N
5.23.4.3.1.1
mpeDevFirmwareControlIndex
This object is used to index the Firmware table (range 1 to N).
5.23.4.3.1.2
mpeDevFirmwareControlRelease
This object indicates the Software Release for this Firmware. If the Software Firmware is Operational Status is
invalid, the Software Revision Number is blank.
5.23.4.3.1.3
mpeDevFirmwareControlOperStatus
This object indicates whether or not the indexed Firmware entry contains a valid.or invalid Firmware. The following
values are defined for this object:
•
•
•
valid(1)
invalid(2)
unknown(3)
5.23.4.3.1.4
mpeDevFirmwareControlAdminStatus
This object indicates whether or not the indexed Firmware entry is active or inactive. The following values are defined
for this object:
•
•
active(1)
inactive(2)
Writing active(1) will activate that software release and cause the unit to reset (response may timeout). Writing
active(1) to a Firmware entry whose mpeDevFirmwareControlOperStatus is invalid will return BAD VALUE.
Writing inactive(2) will always return BAD VALUE.
434
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23.4.4
mpeDevTestControl
The device specific test group.
Table 246: mpeDevTestControl
Object
OID
Syntax
Access
Status
Supported
mpeDevControlTestTable
{ mpeDevTestControl 3 }a
SEQUENCE OF
mpeDevControlTestEntry
not-accessible
current
Y
a. No { mpeDevTestControl 1 } or { mpeDevTestControl 2 } objects specified in the MIB.
5.23.4.4.1
mpeDevControlTestTable
A table that contains configuration information to perform device specific tests.
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
OIDs:
•
•
mpeDevControlTestTable
mpeDevControlTestEntry
- { mpeDevTestControl 3 }
- { mpeDevControlTestTable 1 }
1.3.6.1.4.1.1795.2.24.12.10.1.4.3
1.3.6.1.4.1.1795.2.24.12.10.1.4.3.1
Table 247: mpeDevControlTestTable
Object
OID
Syntax
Access
Status
Supported
mpeDevControlTestType
{ mpeDevControlTestEntry 1 }
INTEGER
lampTest(1)
read-write
current
Y
mpeDevControlTestStatus
{ mpeDevControlTestEntry 2 }
INTEGER
active(1)
inactive(2)
read-only
current
Y
mpeDevControlTestCmd
{ mpeDevControlTestEntry 3 }
INTEGER
start(1)
stop(2)
read-write
current
Y
5.23.4.4.1.1
mpeDevControlTestType
This object is used to specify the type of the test to start. The following values are defined for this object:
•
lampTest(1)
435
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DEVICE-CONTROL-MIB — mpe_Control.mib
5.23.4.4.1.2
mpeDevControlTestStatus
The following values are defined for this object:
•
•
active(1)
inactive(2)
The test status on the device. This object indicates whether the indexed test is currently active(1) or inactive(2).
5.23.4.4.1.3
mpeDevControlTestCmd
Used to start or stop the indexed test. When read, the value returned is the next logical command. The following
values are defined for this object:
•
•
5.23.5
start (1)
stop (2)
Traps
OIDs:
•
mpeDevControlMIBTrapsV2 - { mpeDevControlMIBTraps 0 }
1.3.6.1.4.1.1795.2.24.12.10.2.0
Table 248: PDN-MPE-DEVICE-CONTROL-MIB Traps
Notification
OID
Variable Bindings / Objects
Status
Supported
mpeDevFileXferEvent
{ mpeDevControlMIBTrapsV2 1 }
mpeDevFileXferStatus
mpeDevFileXferErrorStatus
mpeDevFileXferOperation
mpeDevFileXferFileType
mpeDevFileXferFileName
current
N
5.23.5.1
mpeDevFileXferEvent
This trap is to communicate a couple of things about the completion of a file transfer.
•
•
•
•
•
mpeDevFileXferStatus
mpeDevFileXferErrorStatus
mpeDevFileXferOperation
mpeDevFileXferFileType
mpeDevFileXferFileName
-
Did it complete successfully or not
If not, what was the error code
What operation was performed
Was it a firmware xfer or config
The name of the file transferred
436
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
5.24 PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
5.24.1
Introduction
The mpe dslam MIB. This MIB is written specifically to extend entPhysicalTable.
The version of the MIB used for this document had a LAST-UPDATED of 200306060000Z which decodes to
June 6, 2003.
5.24.2
Textual Conventions
The following textual conventions are made in this RFC:
•
MpeEntExtAdminStatus
- Values to support the desired state of the entity. These values were selected
to correspond to the syntax of the ifAdminStatus in the IF-MIB.
— INTEGER
• up(1)
- The Administrator considers the entity to be in
the “up” or “operational” state.
• down(2)
- The Administrator considers the entity to be in
the “down” or “non-operational” state. Generally in this state, alarms or traps should not be
reported.
• testing(3)
- The Administrator considers the entity to be in
a state where the entity is under going some
sort of tests.
•
MpeEntExtOperStatus
- Values to support the current operational state of the entity. These values
were selected to correspond to the syntax of the ifOperStatus in the IFMIB.
— INTEGER
• up(1)
- The entity is operational.
• down(2)
- The entity is non-operational.
• testing(3)
- The entity is in some test mode.
• unknown(4)
- The entity is in an “unknown” state.
• dormant(5)
- The entity is in a “dormant” state.
• notPresent(6)
- The entity was present, but is currently not
present.
• reserved1(7)
- Not used, but reserved.
5.24.3
•
•
•
•
•
•
•
•
•
OIDs
iso
org
dod
internet
private
enterprises
pdyn
pdn-mgmt
paradyne
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
437
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
•
pdn-mpe
•
•
•
•
•
•
•
mpe-dslam
mpeSysDevDslamMIBObjects
mpeSysDevDslamMIBTraps
mpeEntExtAlarms
mpeAlarmRelay
mpeEntExtMibObjects
mpeSysDevDslamMIBNotifications
5.24.4
- { paradyne 12 }
1.3.6.1.4.1.1795.2.24.12
-
{ pdn-mpe 24 }
{ mpe-dslam 1 }
{ mpe-dslam 2 }
{ mpeSysDevDslamMIBObjects 0 }
{ mpeSysDevDslamMIBObjects 2 }
{ mpeSysDevDslamMIBObjects 3 }
{ mpeSysDevDslamMIBTraps 1 }
1.3.6.1.4.1.1795.2.24.12.24
1.3.6.1.4.1.1795.2.24.12.24.1
1.3.6.1.4.1.1795.2.24.12.24.2
1.3.6.1.4.1.1795.2.24.12.24.1.1
1.3.6.1.4.1.1795.2.24.12.24.1.2
1.3.6.1.4.1.1795.2.24.12.24.1.3
1.3.6.1.4.1.1795.2.24.12.24.2.0
MIB Objects
Table 249: PDN-MPE-DSLAM-SYSTEM-MIB Objects
Object
OID
Description
Supported
mpeEntExtAlarms
{ mpeSysDevDslamMIBObjects 1 }
ALARM Objects
Y
mpeAlarmRelay
{ mpeSysDevDslamMIBObjects 2 }
ALARM Relay Objects
Y
mpeEntExtMibObjects
{ mpeSysDevDslamMIBObjects 3 }
Objects that extend the entPhysicalTable.
N
5.24.4.1
mpeEntExtAlarms
The Alarm Objects Group.
Table 250: mpeEntExtAlarms
Object
OID
Syntax
Access
Status
Supported
mpeEntExtAlarmTable
{ mpeEntExtAlarms 1 }
SEQUENCE OF
mpeEntExtAlarmEntry
not-accessible
current
Y
5.24.4.1.1
mpeEntExtAlarmTable
This table lists the alarm states of the objects listed in the entity-MIB entPhysicalTable.
Augments:
•
entPhysicalEntry
438
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
Index(es):
•
entPhysicalIndex
OIDs:
•
•
mpeEntExtAlarmTable
mpeEntExtAlarmEntry
- { mpeEntExtAlarms 1 }
- { mpeEntExtAlarmTable 1 }
1.3.6.1.4.1.1795.2.24.12.24.1.1.1
1.3.6.1.4.1.1795.2.24.12.24.1.1.1.1
Table 251: mpeEntExtAlarmTable
Object
OID
Syntax
Access
Status
Supported
mpeEntExtAlarm
{ mpeEntExtAlarmEntry 1 }
TruthValue
read-only
current
Y
5.24.4.1.1.1
mpeEntExtAlarm
This variable indicates the alarm state of the physical entity.
5.24.4.2
mpeAlarmRelay
Alarm Relay objects. For the purpose of being used as VarBinds for the AlarmRelayInputContact trap.
Table 252: mpeAlarmRelay
Object
OID
Syntax
Access
Status
Supported
mpeAlarmRelayEquipIndex
{ mpeAlarmRelay 1 }
Integer32
accessible-for-notify
deprecated
N
mpeAlarmRelayInputContactState
{ mpeAlarmRelay 2 }
ContactState
accessible-for-notify
deprecated
N
mpeAlarmRelayTable
{ mpeAlarmRelay 3 }
SEQUENCE OF
mpeAlarmRelayEntry
not-accessible
current
Y
5.24.4.2.1
mpeAlarmRelayEquipIndex
This variable is the index of the equipment whose alarms are being relayed. It is a integer number starting from 1 until
the max number of physical connectors the DSLAM device has to support relay.
5.24.4.2.2
mpeAlarmRelayInputContactState
This variable indicates the alarm state of the Input Contact (open/closed).
5.24.4.2.3
mpeAlarmRelayTable
This table holds objects that relate to Alarm Relay input or output. It is a sparse augments for the entPhysicalTable.
439
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
OIDs:
•
•
mpeAlarmRelayTable
mpeAlarmRelayEntry
- { mpeAlarmRelay 3 }
- { mpeAlarmRelayTable 1 }
1.3.6.1.4.1.1795.2.24.12.24.1.2.3
1.3.6.1.4.1.1795.2.24.12.24.1.2.3.1
Table 253: mpeAlarmRelayTable
Object
OID
Syntax
Access
Status
Supported
mpeAlarmRelayState
{ mpeAlarmRelayEntry 1 }
ContactState
read-write
current
Y
5.24.4.2.3.1
mpeAlarmRelayState
This object is used to read or write the state of an Alarm Relay input or output.
5.24.4.3
mpeEntExtMibObjects
Objects that extend the entPhysicalTable.
Table 254: mpeEntExtMibObjects
Object
OID
Syntax
Access
Status
Supported
mpeEntPhhsicalExtTable
{ mpeEntExtMibObjects 1 }
SEQUENCE OF
mpeEntPhhsicalExtEntry
not-accessible
current
N
5.24.4.3.1
mpeEntPhysicalExtTable
This table contains entity information that is not defined in the standard ENTITY-MIB.
Augments:
•
entPhysicalEntry
Index(es):
•
entPhysicalIndex
OIDs:
•
•
mpeEntPhysicalExtTable
mpeEntPhysicalExtEntry
- { mpeEntExtMibObjects 1 }
- { mpeEntPhysicalExtTable 1 }
440
1.3.6.1.4.1.1795.2.24.12.24.1.3
1.3.6.1.4.1.1795.2.24.12.24.1.3.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
Table 255: mpeEntPhysicalExtTable
Object
OID
Syntax
Access
Status
Supported
mpeEntPhysicalExtUpTime
{ mpeEntPhysicalExtEntry 1 }
TimeTicks
read-only
current
N
mpeEntPhysicalExtLocation
{ mpeEntPhysicalExtEntry 1 }
SnmpAdminString
read-write
current
N
mpeEntPhysicalExtAdminStatus
{ mpeEntPhysicalExtEntry 1 }
MpeEntExtAdminStatus
read-write
current
N
mpeEntPhysicalExtOperStatus
{ mpeEntPhysicalExtEntry 1 }
MpeEntExtOperStatus
read-only
current
N
5.24.4.3.1.1
mpeEntPhysicalExtUpTime
The time (in hundredths of a second --just like the sysUpTime) since the entity was last re-initialized.
5.24.4.3.1.2
mpeEntPhysicalExtLocation
This object allows the manager to enter the location of the physical entity where applicable. For example, in a stack,
chassis or units may be in different locations. In this case, it would be logical for the manager to set this object to the
location of the associated chassis.
Where the location does not make sense, it is recommended that the object return a zero-length string.
5.24.4.3.1.3
mpeEntPhysicalExtAdminStatus
The desired state of the entity.
5.24.4.3.1.4
mpeEntPhysicalExtOperStatus
The current operational state of the entity.
5.24.5
Traps
Table 256: PDN-MPE-DSLAM-SYSTEM-MIB Traps (1 of 2)
Notification
OID
Variable Bindings / Objects
Status
Supported
mpeCcn
{ mpeSysDevDslamMIBTraps 7 }
entPhysicalIndex
current
Y
mpeDeviceFailure
{ mpeSysDevDslamMIBTraps 15 }
entPhysicalIndex
current
N
mpeDeviceFailureCleared
{ mpeSysDevDslamMIBTraps 16 }
entPhysicalIndex
current
N
mpeNonSupportedMCC
{ mpeSysDevDslamMIBTraps 20 }
mpeSysObjectID
current
N
441
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
Table 256: PDN-MPE-DSLAM-SYSTEM-MIB Traps (2 of 2)
Notification
OID
Variable Bindings / Objects
Status
Supported
mpeNonSupportedChassis
{ mpeSysDevDslamMIBTraps 21 }
mpeSysObjectID
current
N
mpeAlarmRelayInputContactStateChanged
{ mpeSysDevDslamMIBTraps 22 }
mpeAlarmRelayEquipIndex
mpeAlarmRelayInputContactState
deprecated
N
mpeEntPhysicalExtEntityCreated
{ mpeSysDevDslamMIBTraps 23 }
entPhysicalIndex
current
N
mpeEntPhysicalExtEntityDeleted
{ mpeSysDevDslamMIBTraps 24 }
entPhysicalIndex
current
N
mpeEntPhysicalExtEntityChanged
{ mpeSysDevDslamMIBTraps 25 }
entPhysicalIndex
current
N
mpeAlarmRelayInputStateChanged
{ mpeSysDevDslamMIBTraps 26 }
mpeAlarmRelayState
current
Y
5.24.5.1
mpeCcn
This trap signifies a Configuration change or software upgrade in the xDSL card. This trap is of “warning” class.
5.24.5.2
mpeDeviceFailure
This trap signifies that the sending protocol’s device has failed and the failure was not a result of a device test. In other
words, an internal device failure has been detected by the operating software for the unit.
In the BitStorm 2600 and GranDSLAM 4200 IP DSLAM, this trap indicates that an internal communication
subsystem failure has occurred.
5.24.5.3
mpeDeviceFailureCleared
This trap signifies that the sending protocol’s device has failed but now it is operational. Failure was not a result of a
device test. In other words, an internal device failure has been previously detected by the operating software for the
unit and the failure cleared.
In the BitStorm 2600 and GranDSLAM 4200 IP DSLAM, this trap indicates that an internal communication
subsystem failure cleared. The subsystem communication has been established.
5.24.5.4
mpeNonSupportedMCC
AN has detected MCC firmware release too low to support this device.
5.24.5.4.1
mpeSysObjectID
OID:
•
mpeSysObjectID
- { mpeSystemsEntry 2 }
1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.2
The following is an excerpt from PDN-MPE-MIB2-MIB, mpe_mib2.mib:
The vendor’s authoritative identification of the network management subsystem contained in the entity. This
value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means
442
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-DSLAM-SYSTEM-MIB — mpe_dslam.mib
for determining “what kind of box” is being managed. For example, if vendor “Flinstones, Inc.” was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its “Fred Router.”
•
•
•
5.24.5.5
Syntax
Access
Status
- OBJECT IDENTIFIER
- read-only
- mandatory
mpeNonSupportedChassis
AN in slot xx has been installed in a chassis that cannot support one or more of its features.
Reference Section 5.24.5.4.1, Page 442 for detail on mpeSysObjectID.
5.24.5.6
mpeAlarmRelayInputContactStateChanged
This trap signifies that the state of the InputContact Alarm has changed since last time.
NOTE: This object has been deprecated. Please consider using the mpeAlarmRelayInputStateChanged notification.
5.24.5.7
mpeEntPhysicalExtEntityCreated
This trap signifies that an instance of this entity has been created in the entPhysicalTable.
This trap is generated in addition to the entConfigChange notification defined in RFC 2737.
5.24.5.8
mpeEntPhysicalExtEntityDeleted
This trap signifies that an instance of this entity has been deleted from the entPhysicalTable.
This trap is generated in addition to the entConfigChange notification defined in RFC 2737.
5.24.5.9
mpeEntPhysicalExtEntityChanged
This trap signifies that an instance of this entity has been modified in the entPhysicalTable as a result of a change in
any of the objects in that table.
This trap is generated in addition to the entConfigChange notification defined in RFC 2737.
5.24.5.10 mpeAlarmRelayInputStateChanged
This trap signifies that the state of the Alarm Relay Input has changed.
443
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-HEALTH-AND-STATUS-MIB — mpe_HealthAndStatus.mib
5.25 PDN-MPE-HEALTH-AND-STATUS-MIB — mpe_HealthAndStatus.mib
5.25.1
Introduction
Enterprise Health and Status MIB (mpe support).
5.25.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.25.3
•
•
•
•
•
•
•
•
•
•
•
•
•
5.25.4
OIDs
iso
org
dod
internet
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-mpe
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 12 }
mpe-devHealth
mpeDevHealthAndStatusMIBObjects
mpeDevHealthAndStatusMIBTraps
1
1.3
1.3.6
1.3.6.1
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.12
- { pdn-mpe 10 }
- { mpe-devHealth 1 }
- { mpe-devHealth 2 }
1.3.6.1.4.1.1795.2.24.12.10
1.3.6.1.4.1.1795.2.24.12.10.1
1.3.6.1.4.1.1795.2.24.12.10.2
MIB Objects
Table 257: PDN-MPE-HEALTH-AND-STATUS-MIB Objects
Object
OID
Syntax
Access
Status
Supported
mpeDevHealthAndStatusTable
{ mpeDevHealthAndStatusMIBObjects 1 }
SEQUENCE OF
mpeDevHealthAndStatusEntry
not-accessible
mandatory
Y
5.25.4.1
mpeDevHealthAndStatusTable
A table that contains information about an Entity’s health.
Index(es):
•
entPhysicalIndex (Section 5.6.5.1.1.1, Page 97)
OIDs:
•
•
mpeDevHealthAndStatusTable - { mpeDevHealthAndStatusMIBObjects 1 }
1.3.6.1.4.1.1795.2.24.12.10.1.1
mpeDevHealthAndStatusEntry - { mpeDevHealthAndStatusTable 1 }
1.3.6.1.4.1.1795.2.24.12.10.1.1.1
444
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-MPE-HEALTH-AND-STATUS-MIB — mpe_HealthAndStatus.mib
Table 258: mpeDevHealthAndStatusTable
Object
OID
Syntax
Access
Status
Supported
mpeDevSelfTestResults
{ mpeDevHealthAndStatusEntry 1 }
DisplayString(SIZE(0…255))
read-only
mandatory
Y
5.25.4.1.1
mpeDevSelfTestResults
Self-test results. Self-test (or power-up test) results summarizes the test results of each CCA, where each CCA test
result is separated by a semi-colon. Refer to device-specific user documentation for a complete description of the self
test codes and messages.
Valid Object Value(s)
This object contains the self-test results of the device. Self-test (or power-up test) results summarizes the test results
of each CCA (such as memory and CPU) where each CCA test result is separated by a semi-colon. The following are
values supported for this object where %c: P = pass, F = fail, U = unknown status:
•
•
•
•
•
•
Chassis
Management Processor
DSL Ports
Ethernet Port 1
Ethernet Port 2
Ethernet Port 3
-
“Chassis=%c”
“CPUReg=%c;CPUTimer=%c;SDRAM=%c;File System=%c”
“Memory=%c;DataPump=%c;PHY=%c”
“MAC=%c;PHY=%c;Device Reg=%c”
“MAC=%c;PHY=%c;Device Reg=%c”
“MAC=%c;PHY=%c;Device Reg=%c”
The corresponding UI elements are on the Selftest Results (Diagnostics - Selftest) Screen.
5.25.5
Traps
OIDs:
•
mpeDevHealthAndStatusMIBTraps
- { mpe-devHealth 2 }
1.3.6.1.4.1.1795.2.24.12.10.2
Table 259: PDN-MPE-HEALTH-AND-STATUS-MIB Traps
Trap
ENTERPRISE
:=
Variable Bindings / Objects
Supported
mpeSelfTestFailure
mpeDevHealthAndStatusMIBTraps
1
mpeDevSelfTestResults
Y
5.25.5.1
mpeSelfTestFailure
This trap signifies that the sending protocol’s device has failed self test. The variable binding for this trap would be
the selfTest devSelfTestResults object of the Health and Status MIB.
445
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26 PDN-ADSL-LINE-EXT-MIB
5.26.1
Introduction
This MIB module is a supplement to the ADSL-LINE-MIB and to the ADSL-LINE-EXT-MIB, the “standard” MIBs,
where additional objects are needed to support ADSL modes or flavors not covered in the “standard” MIBs. The MIB
used as a reference was dated January 27, 2006 and has a LAST-UPDATED of “200601270000Z.”
At the time this MIB was defined, the IETF ADSL MIB Working does not have any work on the “standard” MIBs
planned and/or has not produced a schedule to address ADSL2/ADSL2plus needs. As a result, these objects may be a
“temporary” solution until MIBs/Objects are defined or extended to meet the needs of ADSL2/ADSL2plus.
The following documents that should be referenced with respect to this MIB:
[G.997.1]
ITU-T G.997.1 “Physical layer management for Digital Subscriber Line (DSL) transceivers,” May 2003.
[G.997.1 Am 1]
ITU-T G.997.1 Amendment 1 “Physical layer management for Digital Subscriber Line
(DSL) transceivers Amendment 1,” December 2003.
[OA 305]
Telenor Networks Specification, Specification Number OA 305, “Requirements for equipment to be connected to the local sub-loop in the access network of Telenor. Equipment providing ADSL and PSTN or ISDN Basic Access Services, full unbundled access (service type
EDF,”
TN-NL-U-T/0A305/1010 2005, Edition 4.1, January 1, 2005.
[WT-090]
DSL Forum Working Text WT-090 “Protocol Independent Object Model for Managing Next
Generation ADSL Technologies,” Revision-1, September 2003.
[WT-090-4]
DSL Forum Working Text WT-090 “Protocol Independent Object Model for Managing Next
Generation ADSL Technologies,” Revision-4, June 2004.
[RFC 2662]
Bathrick, G., Ly, F. “ADSL-LINE-MIB,” August 1999.
[RFC 3440]
Ly, F., Bathrick, G. “ADSL-LINE-EXT-MIB,” December 2002.
Generally the MIB objects are defined using G.997.1 and the MIB objects are arranged using WT-090.
Not all objects defined in the MIB are supported by the BitStorm 2600 and GranDSLAM 4200 IP DSLAM. What is
supported or not supported is identified.
5.26.2
Textual Conventions
The following “special” textual conventions are made or referenced in this MIB:
•
PdnAdslTransmissionModeType
- A set of ADSL line transmission modes, with one bit per mode.
Reference: G.997.1, Section 7.3.1.1.1, ATU Transmission System Enabling (ATSE).
—
Syntax
BITS
Octet 1
• ansit1413(0)
• etsi(1)
• q9921PotsNonOverlapped(2)
•
Bit 00 : Regional Std. (ANSI T1.413)
Bit 01 : Regional Std. (ETSI DTS/TM06006)
Bit 02 : G.992.1 POTS non-overlapped spectrum
Annex A
Bit 03 : G.992.1 POTS overlapped spectrum
Annex A
q9921PotsOverlapped(3)
446
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
•
q9921IsdnNonOverlapped(4)
•
q9921isdnOverlapped(5)
•
q9921tcmIsdnNonOverlapped(6)
•
q9921tcmIsdnOverlapped(7)
Octet 2
• q9922potsNonOverlapeed(8)
•
q9922potsOverlapped(9)
•
q9922tcmIsdnNonOverlapped(10)
•
q9922tcmIsdnOverlapped(11)
•
•
•
•
q9921tcmIsdnSymmetric(12)
reservedBit13(13)
reservedBit14(14)
reservedBit15(15)
Octet 3
• reservedBit16(16)
• reservedBit17(17)
• q9923potsNonOverlapped(18)
•
q9923potsOverlapped(19)
•
q9923isdnNonOverlapped(20)
•
q9923isdnOverlapped(21)
•
•
reservedBit22(22)
reservedBit23(23)
Octet 4
• q9924potsNonOverlapped(24)
•
q9924potsOverlapped(25)
•
•
•
reservedBit26(26)
reservedBit27(27)
q9923DigitalNonOverlappedI(28)
447
Bit 04 : G.992.1 ISDN non-overlapped spectrum
Annex B
Bit 05 : G.992.1 ISDN overlapped spectrum
Annex B
Bit 06 : G.992.1 TCM-ISDN non-overlapped spectrum
Annex C
Bit 07 : G.992.1 TCM-ISDN overlapped spectrum
Annex C
Bit 08 : G.992.2 POTS non-overlapped spectrum
Annex A
Bit 09 : G.992.2 POTS overlapped spectrum
Annex B
Bit 10 : G.992.2 TCM-ISDN non-overlapped spectrum
Annex C
Bit 11 : G.992.2 TCM-ISDN overlapped spectrum
Annex C
Bit 12 : G.992.1 TCM-ISDN symmetric
Bit 13 : Reserved
Bit 14 : Reserved
Bit 15 : Reserved
Bit 16 : Reserved
Bit 17 : Reserved
Bit 18 : G.992.3 POTS non-overlapped spectrum
Annex A
Bit 19 : G.992.3 POTS overlapped spectrum Annex
A
Bit 20 : G.992.3 ISDN non-overlapped spectrum
Annex B
Bit 21 : G.992.3 ISDN overlapped spectrum Annex
B
Bit 22 : Reserved
Bit 23 : Reserved
Bit 24 : G.992.4 POTS non-overlapped spectrum
Annex A
Bit 25 : G.992.4 POTS overlapped spectrum
Annex A
Bit 26 : Reserved
Bit 27 : Reserved
Bit 28 : G.992.3 All Digital Mode non-overlapped
spectrum
Annex I
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
•
q9923DigitalOverlappedI(29)
•
q9923DigitalNonOverlappedJ(30)
•
q9923DigitalOverlappedJ(31)
Bit 29 : G.992.3 All Digital Mode overlapped spectrum
Annex I
Bit 30 : G.992.3 All Digital Mode non-overlapped
spectrum
Annex J
Bit 31 : G.992.3 All Digital Mode overlapped spectrum
Annex J
Octet 5
• q9924DigitalNonOverlappedI(32)
•
•
•
•
•
•
Bit 32 : G.992.4 All Digital Mode non-overlapped
spectrum
Annex I
q9924DigitalOverlappedI(33)
Bit 33 : G.992.4 All Digital Mode overlapped spectrum
Annex I
q9923ReachExtOverPotsMode1L(34) Bit 34 : G.992.3 Reach Extended operation over
POTS Mode 1 (non-overlapped, wide
upstream)
Annex L
q9923ReachExtOverPotsMode2L(35) Bit 35 : G.992.3 Reach Extended operation over
POTS Mode 2 (non-overlapped, narrow
upstream)
Annex L
q9923ReachExtOverPotsMode3L(36) Bit 36 : G.992.3 Reach Extended operation over
POTS Mode 3 (overlapped, wide upstream)
Annex L
q9923ReachExtOverPotsMode4L(37) Bit 37 : G.992.3 Reach Extended operation over
POTS Mode 4 (overlapped, narrow
upstream)
Annex L
q9923ExtUpOverPotsNonOverlappedM(38)
Bit 38 : G.992.3 Extended upstream operation over
POTS non-overlapped spectrum
Annex M
•
q9923ExtUpOverPotsOverlappedM(39),
Bit 39 : G.992.3 Extended upstream operation over
POTS overlapped spectrum
Annex M
Octet 6
• q9925potsNonOverlapped(40)
•
q9925potsOverlapped(41)
•
q9925isdnNonOverlapped(42)
448
Bit 40 : G.992.5 POTS non-overlapped spectrum
Annex A
Bit 41 : G.992.5 POTS overlapped spectrum
Annex A
Bit 42 : G.992.5 ISDN non-overlapped spectrum
Annex B
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
•
q9925isdnOverlapped(43)
•
•
•
reserved44(44)
reserved45(45)
q9925DigitalNonOverlappedI(46)
•
q9925DigitalOverlappedI(47)
Bit 43 : G.992.5 ISDN overlapped spectrum
Annex B
Bit 44 : Reserved
Bit 45 : Reserved
Bit 46 : G.992.5 All Digital Mode non-overlapped
spectrum
Annex I
Bit 47 : G.992.5 All Digital Mode overlapped spectrum
Annex I
Octet 7
• q9925DigitalNonOverlappedJ(48)
•
•
Bit 48 : G.992.5 All Digital Mode non-overlapped
spectrum
Annex J
q9925OverlappedJ(49)
Bit 49 : G.992.5 All Digital Mode overlapped spectrum
Annex J
q9925ExtUpOverPotsNonOverlappedM(50)
Bit 50 : G.992.5 Extended upstream over POTS nonoverlapped spectrum
Annex M
•
q9925ExtUpOverPotsOverlappedM(51)
Bit 51 : G.992.5 Extended upstream over POTS
overlapped spectrum
Annex M
•
•
•
•
5.26.3
•
•
•
•
•
•
•
•
•
•
•
reservedBit52(52)
reservedBit53(53)
reservedBit54(54)
reservedBit55(55)
Bit 52 :
Bit 53 :
Bit 54 :
Bit 55 :
Reserved
Reserved
Reserved
Reserved
OIDs
iso
org
dod
internet
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
1
1.3
1.3.6
1.3.6.1
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-common
pdn-interfaces
-
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
{ pdn-common 6 }
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
1.3.6.1.4.1.1795.2.24.2.6
449
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
•
•
•
5.26.4
pdnAdslLineExtMIB
pdnAdslLineExtNotifications
pdnAdslLineExtObjects
- { pdn-interfaces 24 }
- { pdnAdslLineExtMIB 0 }
- { pdnAdslLineExtMIB 1 }
1.3.6.1.4.1.1795.2.24.2.6.24
1.3.6.1.4.1.1795.2.24.2.6.24.0
1.3.6.1.4.1.1795.2.24.2.6.24.1
MIB Objects
The table identifies objects called out in this MIB. Any table object that has elements that are supported are indicated
by a “Y” in the Supported column.
Table 260: PDN-ADSL-LINE-EXT-MIB Objects
Syntax
SEQUENCE of
Access
Status
Supported
{ pdnAdslLineExtObjects 1 }
pdnAdslLineExtEntry
notaccessible
current
Y
pdnAdslLineSpectrumProfileTable
{ pdnAdslLineExtObjects 2 }
pdnAdslLineSpectrumProfileEntry
notaccessible
current
Y
pdnAdslModeSpecificPsdConfTable
{ pdnAdslLineExtObjects 3 }
pdnAdslModeSpecificPsdConfEntry
notaccessible
current
Y
pdnAdslPsdConfTable
{ pdnAdslLineExtObjects 4 }
pdnAdslPsdConfEntry
notaccessible
current
Y
pdnAdslCarMaskTable
{ pdnAdslLineExtObjects 5 }
pdnAdslCarMaskEntry
notaccessible
current
Y
pdnAdslLineStatusTable
{ pdnAdslLineExtObjects 6 }
pdnAdslLineStatusEntry
notaccessible
current
Y
pdnAdslLineSubCarStatusTable
{ pdnAdslLineExtObjects 7 }
pdnAdslLineSubCarStatusEntry
notaccessible
current
Y
Object
OID
pdnAdslLineExtTable
5.26.4.1
pdnAdslLineExtTable
This table extends the adslLineTable (Section 5.11.2.1, Page 189) in support of an ADSL Line object.
The objects pdnAdslLineTransAtucCap (Section 5.26.4.1.1, Page 452), pdnAdslLineTransAtucConfig (Section
5.26.4.1.2, Page 453), and pdnAdslLineTransAtucActual (Section 5.26.4.1.3, Page 453) exist along with their
PdnAdslTransmissionModeType (Section •, Page 446) TC because the AdslTransmissionModeType (Section •, Page
230) defined in the ADSL-LINE-EXT-MIB, Section 5.12, Page 230, does not include the ADSL2/ADSL2plus bits
defined in the ITU G.997.1 (05/2003) ATU Transmission System Enabling (ATSE) section.
When using the objects defined in this MIB with a syntax of type PdnAdslTransmissionModeType (Section •, Page
446), the interworking relationship between these objects and the objects defined in the ADSL-LINE-EXT-MIB,
Section 5.12, Page 230, defined with a syntax of type AdslTransmissionModeType (Section •, Page 230) must be
considered and explained in an implementation-specific document such as an Operational Specification. Note that the
PdnAdslTransmissionModeType (Section •, Page 446) is a super set of the AdslTransmissionModeType (Section •,
Page 230). One possible implementation could be as follows:
450
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
1.
2.
3.
Both objects of syntax AdslTransmissionModeType (Section •, Page 230) defined in the ADSL-LINE-EXTMIB, Section 5.12, Page 230, and objects of syntax PdnAdslTransmissionModeType (Section •, Page 446)
defined in this MIB are supported. By supporting both, a manager with the ADSL-LINE-EXT-MIB loaded
could manage the device with the restriction of not being able to utilize ADSL2/ADSL2plus modes.
When the ADSL2/ADSL2plus capabilities are desired, a manager would have to use the objects defined in
this MIB to configure the transmission modes, read capability, or read the actual transmission mode of the
ATU-C.
The transmission mode that the ATU-C is currently configured for is based on the last object, adslLineTransAtucConfig (Section 5.12.4.1.2, Page 233) or pdnAdslLineTransAtucConfig (Section 5.26.4.1.2, Page
453), that was written.
Reference(s):
•
WT-090, Section 5.1.1, ADSL Line
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pdnAdslLineExtTable
pdnAdslLineExtEntry
- { pdnAdslLineExtObjects 1 }
- { pdnAdslLineExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.1
1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1
Table 261: pdnAdslLineExtTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAdslLine
TransAtucCap
{ pdnAdslLineExtEntry 1 }
PdnAdslTransmissionModeType
read-only
current
Y
pdnAdslLine
TransAtucConfig
{ pdnAdslLineExtEntry 2 }
PdnAdslTransmissionModeType
read-write
current
Y
pdnAdslLine
TransAtucActual
{ pdnAdslLineExtEntry 3 }
PdnAdslTransmissionModeType
read-only
current
Y
pdnAdslLine
PowerManagementConfig
{ pdnAdslLineExtEntry 4 }
INTEGER
enabled(1)
disabled(2)
read-write
current
Y
pdnAdslLine
SpectrumProfile
{ pdnAdslLineExtEntry 5 }
SnmpAdminString(SIZE(0 | 1…32))
read-write
current
Y
pdnAdslLinePmMode
{ pdnAdslLineExtEntry 6 }
BITS
idleStateL3(0)
lowPwrStateL1L2(1)
read-write
current
Y
pdnAdslLineL0Time
{ pdnAdslLineExtEntry 7 }
Unsigned32(0…255)
read-write
current
Y
pdnAdslLineL2Time
{ pdnAdslLineExtEntry 8 }
Unsigned32(0…255)
read-write
current
Y
pdnAdslLineL2Atpr
{ pdnAdslLineExtEntry 9 }
Unsigned32
read-write
current
Y
451
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Table 261: pdnAdslLineExtTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAdslLineLdsf
{ pdnAdslLineExtEntry 10 }
INTEGER
ldsfMode0(1)
ldsfMode1(2)
read-write
current
Y
pdnAdslLineL2Atprt
{ pdnAdslLineExtEntry 11 }
Unsigned32(0…32)
read-write
current
Y
pdnAdslLineLdDateAndTimeCompleted
{ pdnAdslLineExtEntry 12 }
DateAndTime
read-only
current
Y
5.26.4.1.1
pdnAdslLineTransAtucCap
The transmission modes, represented by a bitmask that the ATU-C is capable of supporting. The modes available are
limited by the design of the equipment.
Valid Object Value(s)
This object is set to a bitwise OR indicating the following capabilities:
Table 262: pdnAdslLineTransAtucCap for Annex A, L, and M Models
AdslTransmissionModeType
Description
Value (hex)
ansit1413(0)
ANSI T1.413
80 00 00 00 00 00 00
q9921PotsNonOverlapped(2)
G.992.1 POTS, non-overlapped spectrum, Annex A
20 00 00 00 00 00 00
q9922PostNonOverlapped(8)
G.992.2 POTS, non-overlapped spectrum, Annex A
00 80 00 00 00 00 00
q9923potsNonOverlapped(18)
G.992.3 POTS, non-overlapped spectrum, Annex A
00 00 20 00 00 00 00
q9924potsNonOverlapped(24)
G.992.4 POTS, non-overlapped spectrum, Annex A
00 00 00 80 00 00 00
q9923ReachExtOverPotsMode1L(34)
G.992.3 Reach Extended POTS, non-overlapped wide upstream
spectrum, Annex L
00 00 00 00 20 00 00
q9923ReachExtOverPotsMode2L(35)
G.992.3 Reach Extended POTS, non-overlapped narrow upstream
spectrum, Annex L
00 00 00 00 10 00 00
q9923ExtUpOverPotsNonOverlappedM(38)
G.992.3 Extended upstream operation over POTS, non-overlapped
spectrum, Annex M
00 00 00 00 02 00 00
q992.5ExtUpOverPotsNonOverlappedM(50)
G.992.5 Extended upstream operation over POTS, non-overlapped
spectrum, Annex M
00 00 00 00 00 00 20
452
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Table 263: pdnAdslLineTransAtucCap for Annex B Model
AdslTransmissionModeType
Description
Value (hex)
q9921IsdnNonOverlapped(4)
G.992.1 ISDN non-overlapped spectrum Annex B
08 00 00 00 00 00 00
q9923isdnNonOverlapped(20)
G.992.3 ISDN non-overlapped spectrum Annex B
00 00 08 00 00 00 00
q9925isdnNonOverlapped(42)
G.992.5 ISDN non-overlapped spectrum Annex B
00 00 00 00 00 20 00
Reference(s):
•
•
G.997.1, Section 7.3.1.1.1, ATU Transmission System Enabling
(ATSE)
RFC 3440, adslLineTransAtucCap (Section 5.12.4.1.1, Page 232)
5.26.4.1.2
pdnAdslLineTransAtucConfig
The transmission modes, represented by a bitmask, currently enabled by the ATU-C. The manager can only set those
modes that are supported by the ATU-C. An ATU-C’s supported modes are provided by pdnAdslLineTransAtucCap
(Section 5.26.4.1.1, Page 452).
Reference(s)
•
•
G.997.1, Section 7.3.1.1.1, ATU Transmission System Enabling (ATSE)
RFC 3440, adslLineTransAtucConfig (Section 5.12.4.1.2, Page 233)
5.26.4.1.3
pdnAdslLineTransAtucActual
The actual transmission mode of the ATU-C. During ADSL line initialization, the ADSL Transceiver Unit Remote
terminal end (ATU-R) will determine the mode used for the link. This value will be limited a single transmission
mode that is a subset of those modes enabled by the ATU-C and denoted by pdnAdslLineTransAtucConfig (Section
5.26.4.1.2, Page 453). After an initialization has occurred, its mode is saved as the “Current” mode and is persistent
should the link go down. This object returns 0 (i.e. BITS (Section 4.1, Page 12) with no mode bit set) if the mode is
not known.
Reference(s):
•
•
G.997.1, Section 7.3.1.1.1, ATU Transmission System Enabling
(ATSE)
RFC 3440 adslLineTransAtucActual (Section 5.12.4.1.3, Page 233)
5.26.4.1.4
pdnAdslLinePowerManagementConfig
This object enables or disables power management functionality. The following are valid values for this object:
•
•
enabled(1)
disabled(2)
The MIB recommended default value is disabled(2).
5.26.4.1.5
pdnAdslLineSpectrumProfile
The value of this object identifies the row in the ADSL Line Spectrum Profile Table,
pdnAdslLineSpectrumProfileTable (Section 5.26.4.2, Page 455), which applies for this ADSL line. If this object is
453
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
not a zero-length string, it should default to the default profile whose name is “DEFVAL.”
The system will always provide a default profile whose name is “DEFVAL.”
Reference(s):
•
WT-090, Section 5.1.1, ADSL Line
5.26.4.1.6
pdnAdslLinePmMode
The line states the ATU-C or ATU-R may autonomously transition to on this line. It is coded in a bit-map
representation (0 if not allowed, 1 if allowed) as follows:
•
•
idleStateL3(0)
lowPwrStateL1L2(1)
- Bit 0
- Bit 1
L3 state (Idle state)
L1/L2 state (Low power state)
Reference(s):
•
G.997.1, Section 7.3.1.1.4, Power Management State Enabling
(PMMode)
5.26.4.1.7
pdnAdslLineL0Time
The minimum time, in seconds, between and Exit from the L2 state and the next Entry into the L2 state.
Reference(s):
•
G.997.1, Section 7.3.1.1.5, Minimum L0 Time interval, between L2 exit and next L2 entry
(L0-TIME)
5.26.4.1.8
pdnAdslLineL2Time
The minimum time, in seconds, between an Entry into the L2 state and the first Power Trim in the L2 state and
between two consecutive Power Trims in the L2 State.
Reference(s):
•
G.997.1, Section 7.3.1.1.6, Minimum L2 Time interval between L2 entry and first L2 trim
(L2-TIME)
5.26.4.1.9
pdnAdslLineL2Atpr
The maximum aggregate transmit power reduction, in dB, that can be performed through a single Power Trim in the
L2 state.
At the time this MIB was produced, the upper limit for this object was not updated in the G.997.1 with respect to
ADSL2plus. As such, the upper limit of this object should be defined in an implementation-specific document such as
an Operational Specification.
Reference(s):
•
G.997.1, Section 7.3.1.1.7, Maximum Aggregate Transmit Power reduction per L2 trim
(L2-ATPR)
5.26.4.1.10 pdnAdslLineLdsf
Defines whether the line should be forced into the loop diagnostics mode by the near-end ATU on this line. The
454
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
following are valid values:
•
ldsfMode0(1) - 0:
•
ldsModef1(2) - 1:
Inhibits the near-end ATU from performing loop diagnostics mode procedures on the
line. Loop diagnostic mode procedures may still be initiated by the far-end ATU.
Forces the near-end ATU to perform the loop diagnostics procedures.
The line needs to be forced to the L3 state (idle state) before it can be forced to the loop diagnostics mode. Only while
the line power management state is the L3 state, the line can be forced into the loop diagnostics mode procedures.
The following are ways to force the line to the L3 state:
1.
Set the ifAdminStatus (Section 5.3.4.3.7, Page 48) to down
When the loop diagnostics mode procedures are completed successfully, this object shall reset to ldsf0 and the line
shall return to and remain in the L3 idle state. The loop diagnostics data shall be available at least until the line is
forced to the L0 state. If the loop diagnostics procedures can’t be completed successfully, then an Initialization
Failure occurs. As long as loop diagnostics procedures are not completed successfully, attempts shall be made to do
so, until the loop diagnostics mode is no longer forced on the line through this configuration parameter.
Reference(s):
•
G.997.1, Section 7.3.1.1.8, Loop Diagnostics Mode forced
(LDSF).
5.26.4.1.11 pdnAdslLineL2Atprt
This parameter represents the total maximum aggregate transmit power reduction (in dB) that can be performed in an
L2 state. This is the sum of all reductions of L2 Request (i.e., at transition of L0 to L2 state) and Power Trims.
Reference(s):
•
G.997.1 Am 1, Section 7.3.1.1.9, Total maximum aggregate transmit power reduction in L2
(L2-ATPRT).
5.26.4.1.12 pdnAdslLineLdDateAndTimeCompleted
This object provides a date and time stamp corresponding to the last completion of loop diagnostics where valid
results were obtained. If no test results are available, perhaps in the situation where no test has ever been started, this
object shall return a value that has all the fields set to zero.
5.26.4.2
pdnAdslLineSpectrumProfileTable
This table contains specific configuration of transmission spectrum and power spectral density related parameters that
can be mapped to one of the ADSL lines.
Each entry contains a specific profile for transmission spectrum and power spectral density related parameters. A
default profile with an index of “DEFVAL,” will always exist and its parameters will be set to vendor or product
specific values, unless otherwise specified in this document.
Reference(s):
•
WT-090, Section 5.1.6, ADSL Line Spectrum Profile.
Index(es):
•
pdnAdslLineSpectrumProfileName (Section 5.26.4.2.1, Page 456) IMPLIED
455
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
OIDs:
•
•
pdnAdslLineSpectrumProfileTable - { pdnAdslLineExtObjects 2 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.2
pdnAdslLineSpectrumProfileEntry - { pdnAdslLineSpectrumProfileTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.2.1
Table 264: pdnAdslLineSpectrumProfileTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslLineSpectrumProfileName
{ pdnAdslLineSpectrumProfileEntry 1 }
SnmpAdminString
(SIZE(1…32))
notaccessible
current
Y
pdnAdslLineSpectrumProfileRowStatus
{ pdnAdslLineSpectrumProfileEntry 2 }
RowStatus
read-create
current
Y
pdnAdslLineSpectrumModeSpecificPsdProfile
{ pdnAdslLineSpectrumProfileEntry 3 }
SnmpAdminString
(SIZE(1…32))
read-create
current
Y
pdnAdslLineSpectrumModeAtucCarMaskProfile
{ pdnAdslLineSpectrumProfileEntry 4 }
SnmpAdminString
(SIZE(0…32))
read-create
current
Y
pdnAdslLineSpectrumModeAturCarMaskProfile
{ pdnAdslLineSpectrumProfileEntry 4 }
SnmpAdminString
(SIZE(0…32))
read-create
current
Y
5.26.4.2.1
pdnAdslLineSpectrumProfileName
This object identifies a row in the pdnAdslLineSpectrumProfileTable (Section 5.26.4.2, Page 455). The system will
always provide a default profile whose name is “DEFVAL.”
Reference(s):
•
G.997.1, Section 7.3.1.1.1 ATU Transmission System Enabling
(ATSE)
5.26.4.2.2
pdnAdslLineSpectrumProfileRowStatus
This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by
setting this object to “valid.”
Before a profile can be deleted or taken out of service, by setting this object to “destroy” or “outOfService,” the
profile must be first unreferenced from all entries that referred to it—entries in the pdnAdslLineExtTable (Section
5.26.4.1, Page 450).
5.26.4.2.3
pdnAdslLineSpectrumModeSpecificPsdProfile
The value of this object identifies the row(s) in the ADSL Mode-Specific PDS Configuration Table,
pdnAdslModeSpecificPsdConfTable (Section 5.26.4.3, Page 457), which applies for this Line Spectrum Profile.
A particular ADSL line may need to support multiple mode-specific power spectral density related settings. For
example, a ADSL line may need to support one set of settings for ADSL2 and another set of settings for ADSL2plus.
See the pdnAdslModeSpecificPsdConfTable (Section 5.26.4.3, Page 457) for additional detail. The system will
456
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
always provide a default profile whose name is “DEFVAL”
Reference(s):
•
WT-090, Section 5.1.6 ADSL Line Spectrum Profile and Section 5.1.7 ADSL Mode-Specific PSD Configuration.
5.26.4.2.4
pdnAdslLineSpectrumAtucCarMaskProfile
This object identifies one or more rows in the pdnAdslCarMaskTable, Section 5.26.4.5, Page 461. The
pdnAdslCarMaskTable is a table containing a list of subcarriers to be masked in the downstream or upstream
direction; the profile in the pdnAdslCarMaskTable that this object identifies will apply the masks in the downstream
direction.
This object defaults to an empty string meaning that no subcarriers are masked by an administrator.
Reference(s):
•
•
WT-090, Section 5.1.6, ADSL Line Spectrum Profile.
G.997.1, Section 7.3.1.2.6, Downstream subcarrier masking (CARMASKds).
5.26.4.2.5
pdnAdslLineSpectrumAturCarMaskProfile
This object identifies one or more rows in the pdnAdslCarMaskTable., Section 5.26.4.5, Page 461. The
pdnAdslCarMaskTable is a table containing a list of subcarriers to be masked in the downstream or upstream
direction; the profile in the pdnAdslCarMaskTable that this object identifies will apply the masks in the upstream
direction.
This object defaults to an empty string meaning that no subcarriers are masked by an administrator.
Reference(s):
•
•
WT-090, Section 5.1.6, ADSL Line Spectrum Profile.
G.997.1, Section 7.3.1.2.7, Upstream subcarrier masking (CARMASKus).
5.26.4.3
pdnAdslModeSpecificPsdConfTable
For each particular ADSL mode or flavor supported (pdnAdslModeSpecificPsdConfAdslMode, Section 5.26.4.3.2,
Page 458), there will be an entry that points to an entry in the ADSL PSD Configuration Table
(pdnAdslPsdConfTable, Section 5.26.4.4, Page 459). For example, if ADSL2 and ADSL2plus ADSL modes are
supported, this table will have the following two default entries:
1.
2.
An entry indexed by pdnAdslModeSpecificPsdConfProfileName, Section 5.26.4.3.1, Page 458, = DEFVAL
and pdnAdslModeSpecificPsdConfAdslMode = adsl2(1) and has pdnAdslModeSpecificPsdConfAdslPsdConfProfile, Section 5.26.4.3.4, Page 459 = DEFVAL_ADSL2
2. An entry indexed by pdnAdslModeSpecificPsdConfProfileName, Section 5.26.4.3.1, Page 458,=
DEFVAL and pdnAdslModeSpecificPsdConfAdslMode = adsl2plus(3) and has pdnAdslModeSpecificPsdConfAdslPsdConfProfile = DEFVAL_ADSL2PLUS
Reference(s):
•
WT-090, Section 5.1, Configuration Management, and Section 5.1.6, ADSL Line Spectrum Profile
Index(es):
•
pdnAdslModeSpecificPsdConfProfileName (Section 5.26.4.3.1, Page 458)
457
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
•
pdnAdslModeSpecificPsdConfAdslMode (Section 5.26.4.3.2, Page 458)
OIDs:
•
•
pdnAdslModeSpecificPsdConfTable - { pdnAdslLineExtObjects 3 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.3
pdnAdslModeSpecificPsdConfEntry - { pdnAdslModeSpecificPsdConfTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.3.1
Table 265: pdnAdslModeSpecificPsdConfTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslModeSpecificPsdConfProfileName
{ pdnAdslModeSpecificPsdConfEntry 1 }
SnmpAdminString
(SIZE(1…32))
notaccessible
current
Y
pdnAdslModeSpecificPsdConfAdslMode
{ pdnAdslModeSpecificPsdConfEntry 2 }
INTEGER
adsl2(1)
adsl2NoSplitter(2)
adsl2plus(3)
notaccessible
current
Y
pdnAdslModeSpecificPsdConfRowStatus
{ pdnAdslModeSpecificPsdConfEntry 3 }
RowStatus
read-create
current
Y
pdnAdslModeSpecificPsdConfAdslPsdConfProfile
{ pdnAdslModeSpecificPsdConfEntry 4 }
SnmpAdminString
(SIZE(1…32))
read-create
current
Y
5.26.4.3.1
pdnAdslModeSpecificPsdConfProfileName
This object identifies a row in the pdnAdslModeSpecificPsdConfTable (Section 5.26.4.3, Page 457). The system will
always provide a default profile whose name is “DEFVAL.”
Reference:
•
WT-090, Section 5.1.7, ADSL Mode-Specific PDS Configuration
5.26.4.3.2
pdnAdslModeSpecificPsdConfAdslMode
This object identifies a row in the pdnAdslModeSpecificPsdConfTable (Section 5.26.4.3, Page 457) containing
parameters specific to a particular ADSL mode or flavor identified by this object.
Valid Object Value(s)
•
•
adsl2(1)
adsl2plus(3)
- G.992.3 ADSL transceivers - 2 (ADSL2)
- G.992.5 Extended Bandwidth ADSL2 (ADSL2plus)
Reference:
•
WT-090, Section 5.1.7, ADSL Mode-Specific PDS Configuration
5.26.4.3.3
pdnAdslModeSpecificPsdConfRowStatus
This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by
458
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
setting this object to “valid.”
Before a profile can be deleted or taken out of service, by setting this object to “destroy” or “outOfService,” the
profile must be first unreferenced from all entries that referred to it—entries in the pdnAdslLineSpectrumProfileTable
(Section 5.26.4.2, Page 455).
5.26.4.3.4
pdnAdslModeSpecificPsdConfAdslPsdConfProfile
This object identifies a row in the ADSL PSD Configuration Table, pdnAdslPsdConfTable (Section 5.26.4.4, Page
459).
Reference(s):
•
•
WT-090, Section 5.1, Configuration Management, and Section 5.1.7, ADSL Mode-Specific PSD Configuration.
G.997.1, Section 7.3.1.2, Power/PSD configuration parameters.
5.26.4.4
pdnAdslPsdConfTable
Each entry contains specific power spectral density settings for a particular profile. A default profile for each
particular ADSL mode or flavor supporting PSD configuration will exist (See the
pdnAdslModeSpecificPsdConfAdslMode, Section 5.26.4.3.2, Page 458, object the range of possible ADSL modes or
flavors that are possible). For example, if only ADSL2 and ADSL2plus modes are supported, the indices would be
“DEFVAL_ADSL2” and “DEFVAL_ADSL2PLUS.” The DEFVAL rows may be modified but not deleted. The
DEFVAL rows will always exist and its parameters will be set to vendor or product specific values, unless otherwise
specified in this document.
Reference(s):
•
•
WT-090, Section 5.1.7, ADSL Mode-Specific PSD Configuration
G.997.1, Section 7.3.1.2, Power/PSD configuration parameters
Index(es):
•
pdnAdslPsdConfProfileName (Section 5.26.4.4.1, Page 460) IMPLIED
OIDs:
•
•
pdnAdslPsdConfTable
pdnAdslPsdConfEntry
- { pdnAdslLineExtObjects 4 }
- { pdnAdslPsdConfTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.4
1.3.6.1.4.1.1795.2.24.2.6.24.1.4.1
Table 266: pdnAdslPsdConfTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAdslPsdConfProfileName
{ pdnAdslPsdConfEntry 1 }
SnmpAdminString
(SIZE(1…32))
notaccessible
current
Y
pdnAdslPsdConfRowStatus
{ pdnAdslPsdConfEntry 2 }
RowStatus
notaccessible
current
Y
pdnAdslPsdConfAtucMaxNomPsd
{ pdnAdslPsdConfEntry 3 }
Integer32
(-800…-400)
read-create
current
Y
459
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Table 266: pdnAdslPsdConfTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAdslPsdConfAturMaxNomPsd
{ pdnAdslPsdConfEntry 4 }
Integer32
(-650…-380)
read-create
current
Y
pdnAdslPsdConfAtucMaxNomAtp
{ pdnAdslPsdConfEntry 5 }
Unsigned32
(0…255)
read-create
current
Y
pdnAdslPsdConfAturMaxNomAtp
{ pdnAdslPsdConfEntry 6 }
Unsigned32
(0…255)
read-create
current
Y
pdnAdslPsdConfAtucMaxRxPwr
{ pdnAdslPsdConfEntry 7 }
Unsigned32
(-255…255 | 2048)
read-create
current
Y
5.26.4.4.1
pdnAdslPsdConfProfileName
This object identifies a row in the pdnAdslPsdConfTable (Section 5.26.4.4, Page 459). The system will always
provide a default profile whose name is “DEFVAL.”
Reference(s):
•
WT-090, Section 5.1.7, ADSL Mode-Specific PDS Configuration
5.26.4.4.2
pdnAdslPsdConfRowStatus
This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by
setting this object to “valid.”
Before a profile can be deleted or taken out of service, by setting this object to “destroy” or “outOfService,” the
profile must be first unreferenced from all entries that referred to it such as
pdnAdslModeSpecificPsdConfAdslPsdConfProfile (Section 5.26.4.3.4, Page 459).
5.26.4.4.3
pdnAdslPsdConfAtucMaxNomPsd
Represents the Maximum nominal transmit PSD for the ATU-C. The values range from -80 to -40 dBm/Hz in 0.1 dB
steps.
Reference(s):
•
•
•
G.997.1, Section 7.3.1.2.1, Downstream Maximum Nominal Power Spectral Density
(MAXNOMPSDds)
G.997.1, Section 7.3.1.2.2, Upstream Maximum Nominal Power Spectral Density
(MAXNOMPSDus)
OA 305, Section 7.2.2, Downstream transmit spectral mask.
5.26.4.4.4
pdnAdslPsdConfAturMaxNomPsd
Represents the Maximum nominal transmit PSD for the ATU-R. The values range from -65 to -38 dBm/Hz in 0.1 dB
steps.
460
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Reference(s):
•
•
G.997.1, Section 7.3.1.2.1, Downstream Maximum Nominal Power Spectral Density
(MAXNOMPSDds)
G.997.1, Section 7.3.1.2.2, Upstream Maximum Nominal Power Spectral Density
(MAXNOMPSDus)
5.26.4.4.5
pdnAdslPsdConfAtucMaxNomAtp
Represents the Maximum nominal aggregate transmit power for the ATU-C. The values range from 0 to 25.5 dBm in
0.1 dB steps.
Reference(s):
•
•
G.997.1, Section 7.3.1.2.3, Downstream Maximum Nominal Aggregate Transmit Power
(MAXNOMATPds)
G.997.1, Section 7.3.1.2.4, Upstream Maximum Nominal Aggregate Transmit Power
(MAXNOMATPus).
5.26.4.4.6
pdnAdslPsdConfAturMaxNomAtp
Represents the Maximum nominal aggregate transmit power for the ATU-R. The values range from 0 to 25.5 dBm in
0.1 dB steps.
Reference(s):
•
•
G.997.1, Section 7.3.1.2.3, Downstream Maximum Nominal Aggregate Transmit Power
(MAXNOMATPds)
G.997.1, Section 7.3.1.2.4, Upstream Maximum Nominal Aggregate Transmit Power
(MAXNOMATPus)
5.26.4.4.7
pdnAdslPsdConfAtucMaxRxPwr
Represents the maximum upstream aggregate receive power over a set of subcarriers (in dBm). The ATU-C shall
request an upstream power cutback such that the upstream aggregate receive power over that set of subcarriers is at or
below the configured maximum value. It ranges from -25.5 to 25.5 dBm, with 0.1 dB steps. The value 2048 is a
special value and indicates that no Upstream Maximum Aggregate Receive Power limit is to be applied (i.e., the
maximum value is infinite).
Reference(s):
•
5.26.4.5
G.997.1, Section 7.3.1.2.5, Upstream Maximum Aggregate Receive Power (MAXRXPWRus).
pdnAdslCarMaskTable
This table contains a list of subcarriers that are to be masked (i.e. not transmitted). Subcarriers that are not entries in
this table are not masked. Each entry represents a specific subcarrier that is masked for a particular profile.
Reference(s):
•
•
•
WT-090, Section 5.1.6, ADSL Line Spectrum Profile.
G.997.1, Section 7.3.1.2.6, Downstream subcarrier masking (CARMASKds).
G.997.1, Section 7.3.1.2.7, Upstream subcarrier masking (CARMASKus).
461
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Index(es):
•
•
pdnAdslCarMaskProfileName, Section 5.26.4.5.1, Page 462
pdnAdslCarMaskSubCarrierIndex, Section 5.26.4.5.2, Page 462
OIDs:
•
•
pdnAdslCarMaskTable
pdnAdslCarMaskEntry
- { pdnAdslLineExtObjects 5 }
- { pdnAdslCarMaskTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.5
1.3.6.1.4.1.1795.2.24.2.6.24.1.5.1
Table 267: pdnAdslCarMaskTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslCarMaskProfileName
{ pdnAdslCarMaskEntry 1 }
SnmpAdminString
(SIZE(1…32))
notaccessible
current
Y
pdnAdslCarMaskSubCarrierIndex
{ pdnAdslPsdConfEntry 2 }
Unsigned32
notaccessible
current
Y
pdnAdslCarMaskRowStatus
{ pdnAdslPsdConfEntry 3 }
RowStatus
read-create
current
Y
pdnAdslCarMaskSubCarrierStatus
{ pdnAdslPsdConfEntry 4 }
INTEGER
masked(1)
read-only
current
Y
5.26.4.5.1
pdnAdslCarMaskProfileName
This object identifies a row in the pdnAdslCarMaskTable based on a profile name.
5.26.4.5.2
pdnAdslCarMaskSubCarrierIndex
This object identifies a row in the pdnAdslCarMaskTable, Section 5.26.4.5, Page 461, based on subcarrier that is
being masked. The subcarrier index ranges from 0 to (NSCds-1 or NSCus-1 (NSC is Number of Subcarriers) as
specified in G.997.1 where NSCds is the higher subcarrier that can be transmitted in the downstream direction and
NSCus is the higher subcarrier that can be transmitted in the upstream direction. Please refer to the corresponding
ITU recommendation for specific values of NSCds and NSCus.
The following ITU recommendations should be reference for specific values for NSCds and NSCus:
•
•
•
•
•
•
G.997.1
G.992.1
G.992.2
G.992.3
G.992.4
G.992.5
5.26.4.5.3
-
Physical layer management for DSL transceivers
ADSL, G.dmt
Splitterless ADSL, G.lite
ADSL2, G.dmt.bis
Splitterless ADSL2
Extended Bandwidth ADSL2, ADSL2plus
pdnAdslCarMaskRowStatus
This object is used to create a new row or delete an existing row in this table. A row is activated by setting this object
to active(1).
462
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26.4.5.4
pdnAdslCarMaskSubCarrierStatus
This object provides a clear indication that the subcarrier is masked. The following are valid values for the object:
•
masked(1)
5.26.4.6
pdnAdslLineStatusTable
This table contains current line status measurements. Each entry represents an interface. i.e. a row in the ifTable.
Reference(s):
•
•
WT-090-4, Section 5.2.1, ADSL Line Status.
G.997.1, Section 7.5.1, Line test, diagnostics and status.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pdnAdslLineStatusTable
pdnAdslLineStatusEntry
- { pdnAdslLineExtObjects 6 }
- { pdnAdslLineStatusTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.6
1.3.6.1.4.1.1795.2.24.2.6.24.1.6.1
Table 268: pdnAdlsLineStatusTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslLineStatusAtucLineAtn
{ pdnAdslLineStatusEntry 1 }
Unsigned32
(0…1270 | 2048)
read-only
current
Y
pdnAdslLineStatusAturLineAtn
{ pdnAdslLineStatusEntry 2 }
Unsigned32
(0…1270 | 2048)
read-only
current
Y
pdnAdslLineStatusAtucSignalAtn
{ pdnAdslLineStatusEntry 3 }
Unsigned32
(0…1270 | 2048)
read-only
current
Y
pdnAdslLineStatusAturSignalAtn
{ pdnAdslLineStatusEntry 4 }
Unsigned32
(0…1270 | 2048)
read-only
current
Y
pdnAdslLineStatusAtucSnrMgn
{ pdnAdslLineStatusEntry 5 }
Integer32
(-640…630 | 2048)
read-only
current
Y
pdnAdslLineStatusAturSnrMgn
{ pdnAdslLineStatusEntry 6 }
Integer32
(-640…630 | 2048
read-only
current
Y
pdnAdslLineStatusAtucMaxAttainableLineRate
{ pdnAdslLineStatusEntry 7 }
Gauge32
read-only
current
Y
pdnAdslLineStatusAturMaxAttainableLineRate
{ pdnAdslLineStatusEntry 8 }
Gauge32
read-only
current
Y
pdnAdslLineStatusAtucActAtp
{ pdnAdslLineStatusEntry 9 }
Integer32
(-310…310 | 2048)
read-only
current
Y
pdnAdslLineStatusAturActAtp
{ pdnAdslLineStatusEntry 10 }
Integer32
(-310…310 | 2048)
read-only
current
Y
463
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26.4.6.1
pdnAdslLineStatusAtucLineAtn
The measured difference in the total power transmitted by the ATU-C and the total power received by the ATU-R over
all subcarriers during diagnostics mode and initialization in units of tenth dB. The value 2048 is a special value and
indicates the line attenuation is out of the range to be represented.
Reference(s):
•
.997.1, Section 7.5.1.6, Downstream Line Attenuation (LATNds).
5.26.4.6.2
pdnAdslLineStatusAturLineAtn
The measured difference in the total power transmitted by the ATU-R and the total power received by the ATU-C over
all subcarriers during diagnostics mode and initialization in units of tenth dB. The value 2048 is a special value and
indicates the line attenuation is out of the range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.7, Upstream Line Attenuation (LATNus).
5.26.4.6.3
pdnAdslLineStatusAtucSignalAtn
The measured difference in the total power transmitted by the ATU-C and the total power received by the ATU-R, in
units of tenth dB, over all subcarriers during showtime. The value 2048 is a special value and indicates the line
attenuation is out of the range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.8, Downstream Signal Attenuation (SATNds).
5.26.4.6.4
pdnAdslLineStatusAturSignalAtn
The measured difference in the total power transmitted by the ATU-R and the total power received by the ATU-C, in
units of tenth dB, over all subcarriers during showtime. The value 2048 is a special value and indicates the line
attenuation is out of the range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.9, Upstream Signal Attenuation (SATNus).
5.26.4.6.5
pdnAdslLineStatusAtucSnrMgn
The upstream signal-to-noise ratio margin, in units of tenth dB, is the increase in dB of the noise power received at
the ATU-R, such that the BER requirements are met for all upstream bearer channels. The value 2048 is a special
value and indicates the parameter is out of range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.10, Downstream Signal-to-Noise Ratio Margin (SNRMds).
5.26.4.6.6
pdnAdslLineStatusAturSnrMgn
The downstream signal-to-noise ratio margin, in units of tenth dB, is the increase in dB of the noise power received at
the ATU-C, such that the BER requirements are met for all upstream bearer channels. The value 2048 is a special
value and indicates the parameter is out of range to be represented.
464
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Reference(s):
•
G.997.1, Section 7.5.1.11, Upstream Signal-to-Noise Ratio Margin (SNRMus).
5.26.4.6.7
pdnAdslLineStatusAtucMaxAttainableLineRate
The maximum downstream net data rate, in bps, currently attainable by the ATU-C transmitter and the ATU-R
receiver.
Reference(s):
•
G.997.1, Section 7.5.1.12, Downstream Maximum Attainable Data Rate (ATTNDRds).
5.26.4.6.8
pdnAdslLineStatusAturMaxAttainableLineRate
The maximum upstream net data rate, in bps, currently attainable by the ATU-R transmitter and the ATU-C receiver.
Reference(s):
•
G.997.1, Section 7.5.1.13, Upstream Maximum Attainable Data Rate (ATTNDRus).
5.26.4.6.9
pdnAdslLineStatusAtucActAtp
The total amount of transmit power, in tenth dBm, delivered by the ATU-C at the U-R reference point, at the instant
of the measurement. The value 2048 is a special value and indicates the parameter is out of range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.16, Downstream Actual Aggregate Transmit Power (ACTATPus).
5.26.4.6.10 pdnAdslLineStatusAturActAtp
The total amount of transmit power, in tenth dBm, delivered by the ATU-R at the U-R reference point, at the instant
of the measurement. The value 2048 is a special value and indicates the parameter is out of range to be represented.
Reference(s):
•
5.26.4.7
G.997.1, Section 7.5.1.17, Upstream Actual Aggregate Transmit Power (ACTATPds)
pdnAdslLineSubCarStatusTable
This table contains current line status measurements. Each entry represents an interface. i.e. a row in the ifTable for a
particular carrier.
Some objects in this table are only valid if a loop diagnostic has successfully completed. Those objects will return a
noSuchName for a Get or Get Next operation if no loop diagnostic has completed. The following objects will return a
value in a Get or Get Next operation without a successful completion of a loop diagnostic provided the ifOperStatus
(Section 5.3.4.3.8, Page 49) is up(1):
•
•
•
pdnAdslLineSubCarAturSnrPs
pdnAdslLineSubCarAtucBitsPs
pdnAdslLineSubCarAturBitsPs
Reference(s):
•
•
WT-090-4, Section 5.2.1, ADSL Line Status.
G.997.1, Section 7.5.1, Line test, diagnostics and status parameters.
465
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnAdslLineCarrierIndex (Section 5.26.4.7.1, Page 467)
OIDs:
•
pdnAdslLineSubCarStatusTable
•
pdnAdslLineSubCarStatusEntry
- { pdnAdslLineExtObjects 6 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.7
- { pdnAdslLineSubCarStatusTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.24.1.7.1
Table 269: pdnAdlsLineSubCarStatusTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslLineCarrierIndex
{ pdnAdslLineSubCarStatusEntry 1 }
Unsigned32
read-only
current
Y
pdnAdslLineSubCarAtucHlinPs
{ pdnAdslLineSubCarStatusEntry 2 }
Integer32
(-32768 | -32767…32767)
read-only
current
N
pdnAdslLineSubCarAturHlinPs
{ pdnAdslLineSubCarStatusEntry 3 }
Integer32
(-32768 | -32767…32767)
read-only
current
N
pdnAdslLineSubCarAtucHlogMt
{ pdnAdslLineSubCarStatusEntry 4 }
Unsigned32
(0…65535)
read-only
current
N
pdnAdslLineSubCarAturHlogMt
{ pdnAdslLineSubCarStatusEntry 5 }
Unsigned32
(0…65535)
read-only
current
N
pdnAdslLineSubCarAtucQlnPs
{ pdnAdslLineSubCarStatusEntry 6 }
Unsigned32
(0…254 | 255)
read-only
current
Y
pdnAdslLineSubCarAturQlnPs
{ pdnAdslLineSubCarStatusEntry 7 }
Unsigned32
(0…254 | 255)
read-only
current
Y
pdnAdslLineSubCarAtucSnrPs
{ pdnAdslLineSubCarStatusEntry 8 }
Unsigned32
(0…254 | 255)
read-only
current
Y
pdnAdslLineSubCarAturSnrPs
{ pdnAdslLineSubCarStatusEntry 9 }
Unsigned32
(0…254 | 255)
read-only
current
Y
pdnAdslLineSubCarAtucBitsPs
{ pdnAdslLineSubCarStatusEntry 10 }
Unsigned32
(0…15)
read-only
current
Y
pdnAdslLineSubCarAturBitsPs
{ pdnAdslLineSubCarStatusEntry 11 }
Unsigned32
(0…15)
read-only
current
Y
pdnAdslLineSubCarAtucHlogPs
{ pdnAdslLineSubCarStatusEntry 12 }
Unsigned32
(0…1022 | 1023)
read-only
current
Y
pdnAdslLineSubCarAturHlogPs
{ pdnAdslLineSubCarStatusEntry 13 }
Unsigned32
(0…1022 | 1023)
read-only
current
Y
466
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26.4.7.1
pdnAdslLineCarrierIndex
Identifies a row in the table based on a subcarrier. The subcarrier index ranges from 0 to (NSCds-1 or NSCus-1 (NSC
is Number of Subcarriers) as specified in G.997.1 where NSCds is the higher subcarrier that can be transmitted in the
downstream direction and NSCus is the higher subcarrier that can be transmitted in the upstream direction. Please
refer to the corresponding ITU recommendation for specific values of NSCds and NSCus.
The following ITU recommendations should be reference for specific values for NSCds and NSCus:
•
•
•
•
•
•
G.997.1
G.992.1
G.992.2
G.992.3
G.992.4
G.992.5
5.26.4.7.2
-
Physical layer management for DSL transceivers
ADSL, G.dmt
Splitterless ADSL, G.lite
ADSL2, G.dmt.bis
Splitterless ADSL2
Extended Bandwidth ADSL2, ADSL2plus
pdnAdslLineSubCarAtucHlinPs
The downstream linear representation, Hlin(f), of the Channel Characteristics Function, H(f). This value is only
available after a loop diagnostic procedure. The special value -32768 indicates that no measurement could be done for
the subcarrier because it is out of the passband or that the attenuation is out of the range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.18.2, Downstream H(f) Linear Representation (HLINpsds).
5.26.4.7.3
pdnAdslLineSubCarAturHlinPs
The upstream linear representation, Hlin(f), of the Channel Characteristics Function, H(f). This value is only
available after a loop diagnostic procedure. The special value -32768 indicates that no measurement could be done for
the subcarrier because it is out of the passband or that the attenuation is out of the range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.18.6, Upstream H(f) Linear Representation (HLINpsus).
5.26.4.7.4
pdnAdslLineSubCarAtucHlogMt
The number of symbols used to measure downstream H(f) logarithmic measurement values. After a loop diagnostic
procedure, this parameter shall contain the number of symbols used to generate the associate parameter. It should
correspond to the value specified in the recommendation (e.g. the number of symbols in 1 s. time interval for
G.992.3).
Reference(s):
•
G.997.1, Section 7.5.1.18.3, Downstream H(f) Logarithmic Measurement Time (HLOGMTds).
5.26.4.7.5
pdnAdslLineSubCarAturHlogMt
The number of symbols used to measure downstream H(f) logarithmic measurement values. After a loop diagnostic
procedure, this parameter shall contain the number of symbols used to generate the associate parameter. It should
correspond to the value specified in the recommendation (e.g. the number of symbols in 1 s. time interval for
G.992.3).
467
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Reference(s):
•
G.997.1, Section 7.5.1.18.7, Upstream H(f) Logarithmic Measurement Time (HLOGMTus).
5.26.4.7.6
pdnAdslLineSubCarAtucQlnPs
Downstream Quiet Line Noise in dB units. The special value 255 indicates that no measurement could be done for the
subcarrier because it is out of the passband or that the noise power Spectral Density (PSD) is out of the range to be
represented.
Reference(s):
•
G.997.1, Section 7.5.1.19.2, Downstream QLN(f) (QLNpsds).
5.26.4.7.7
pdnAdslLineSubCarAturQlnPs
Upstream Quiet Line Noise in dB units. The special value 255 indicates that no measurement could be done for the
subcarrier because it is out of the passband or that the noise power spectral density (PSD) is out of the range to be
represented.
Reference(s):
•
G.997.1, Section 7.5.1.19.4, Upstream QLN(f) (QLNpsus).
5.26.4.7.8
pdnAdslLineSubCarAtucSnrPs
Downstream Signal-to-Noise Ratio in dB units. The special value 255 indicates that no measurement could be done
for the subcarrier because it is out of the passband or that the noise power spectral density (PSD) is out of the range to
be represented.
Reference(s):
•
G.997.1, Section 7.5.1.20.2, Downstream SNR(f) (SNRpsds).
5.26.4.7.9
pdnAdslLineSubCarAturSnrPs
Upstream Signal-to-Noise Ratio in dB units. The special value 255 indicates that no measurement could be done for
the subcarrier because it is out of the passband or that the noise power spectral density (PSD) is out of the range to be
represented.
Reference(s):
•
G.997.1, Section 7.5.1.20.4, Upstream SNR(f) (SNRpsus).
5.26.4.7.10 pdnAdslLineSubCarAtucBitsPs
Downstream bits allocation in “bits” units.
Reference(s):
•
G.997.1, Section 7.5.1.21.1, Downstream Bits Allocation (BITSpsds).
5.26.4.7.11 pdnAdslLineSubCarAturBitsPs
Upstream bits allocation in “bits” units.
Reference(s):
•
G.997.1, Section 7.5.1.21.2, Upstream Bits Allocation (BITSpsus).
468
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26.4.7.12 pdnAdslLineSubCarAtucHlogPs
The downstream logarithmic representation, Hlog(f), in dB units, of the Channel Characteristics function, H(f),
providing magnitude values. The special value 1023 indicates that no measurement could be done for the subcarrier
because it is out of the passband or that the attenuation is out of the range to be represented.
Reference(s):
•
G.997.1, Section 7.5.1.18.4, Downstream H(f) Logarithmic Representation (HLOGpsds).
5.26.4.7.13 pdnAdslLineSubCarAturHlogPs
The upstream logarithmic representation, Hlog(f), in dB units, of the Channel Characteristics function, H(f),
providing magnitude values. The special value 1023 indicates that no measurement could be done for the subcarrier
because it is out of the passband or that the attenuation is out of the range to be represented.
G.997.1, Section 7.5.1.18.8, Upstream H(f) Logarithmic Representation (HLOGpsus).
469
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26.5
5.26.5.1
Conformance Information
Compliance
This section outlines the compliance requirements for this MIB.
Mandatory Groups:
None specified.
Optional Groups:
•
•
•
•
•
•
•
•
•
•
•
•
•
pdnAdslLineExtGroup
This group is mandatory only for those entities which implement ADSL2 or ADSL2plus capabilities and
providing that no IETF standard MIB exists that has objects allowing ADSL2 or ADSL2plus capabilities to
be identified and controlled.
pdnAdslLineSpectrumGroup
This group associates objects related to spectrum and power spectral configurations and is mandatory only
for those entities which implement ADSL2 or ADSL2plus capabilities and providing that no IETF standard
MIB exists that has objects allowing ADSL2 or ADSL2plus capabilities to be identified and controlled.
pdnAdslModeSpecificPsdGroup
This group associates objects related to spectrum and power spectral configurations that are specific to a particular type of ADSL mode is mandatory only for those entities which implement ADSL2 or ADSL2plus
capabilities and providing that no IETF standard MIB exists that has objects allowing ADSL2 or
ADSL2plus capabilities to be identified and controlled.
pdnAdslPsdGroup
This group associates objects related to configuring profiles for power spectral density setting and is mandatory only for those entities which implement ADSL2 or ADSL2plus capabilities and providing that no IETF
standard MIB exists that has objects allowing ADSL2 or ADSL2plus capabilities to be identified and controlled.
pdnAdslCarMaskGroup
This group associates objects related to defining subcarriers to be masked in the downstream direction.
pdnAdslLineL2AtprtGroup
This group adds an object for total maximum aggregate transmit power reduction in L2.
pdnAdslLineStatusLineAtnGroup
This group associates status objects related to line attenuation during diagnostic mode and initialization.
pdnAdslLineStatusSignalAtnGroup
This group associates status objects related to line attenuation during showtime.
pdnAdslLineStatusSnrMgnGroup
This group associates status objects related to SNR margin ratio.
pdnAdslLineStatusMaxattainableLineRateGroup
This group associates status objects related to the current maximum attainable net data rate.
pdnAdslLineStatusActAtpGroup
This group associates status objects related to the actual aggregate transmit power.
pdnAdslLineSubCarStatusHlinGroup
This group associates the status objects related to the linear representation of the Channel Characteristics
Function on a per-subcarrier basis for a line.
pdnAdslLineSubCarStatusHlogMtGroup
This group associates the status objects related to the logarithmic measurement time on a per-subcarrier
basis for the line.
470
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
•
•
•
•
•
pdnAdslLineSubCarStatusQlnGroup
This group associates the status objects related to the Quiet Line Noise on a per-subcarrier basis for the line.
pdnAdslLineSubCarStatusSnrGroup
This group associates the status objects related to the Signal-to-Noise Ratio on a per-subcarrier basis for the
line.
pdnAdslLineSubCarStatusBitsGroup
The group associates the status objects related to the bits allocation on a per-subcarrier basis for the line.
pdnAdslLineSubCarStatusHlogGroup
The group associates the status objects related to the logarithmic representation of the Channel Characteristics function on a per-subcarrier basis for the line.
pdnAdslLineLdDateAndTimeCompletedGroup
This group is only required for implementations that require a timestamp corresponding to the last completion of loop diagnostics where valid results were obtained.
471
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
5.26.5.2
Conformance
Table 270: PDN-ADSL-LINE-EXT-MIB Conformance (1 of 2)
Group
Description
Objects
Supported
pdnAdslLineExtGroup
A collection of objects
providing extended
configuration information
about an ADSL Line.
pdnAdslLineTransAtucCap
Y
pdnAdslLineTransAtucConfig
Y
pdnAdslLineTransAtucActual
Y
pdnAdslLinePowerManagementConfig
Y
pdnAdslLineSpectrumProfile
Y
pdnAdslLinePmMode
Y
pdnAdslLineL0Time
Y
pdnAdslLineL2Time
Y
pdnAdslLineL2Atpr
Y
pdnAdslLineLdsf
Y
pdnAdslLineSpectrumProfileRowStatus
Y
pdnAdslLineSpectrumModeSpecificPsdProfile
Y
pdnAdslLineSpectrumAtucCarMaskProfile
Y
pdnAdslLineSpectrumAturCarMaskProfile
Y
A collection of objects
providing a mapping from an
entry into the ADSL Line
Spectrum Table to a profile
defining a specific set of power
spectral density settings.
pdnAdslModeSpecificPsdConfRowStatus
Y
pdnAdslModeSpecificPsdConfAdslPsdConfProfile
Y
A collection of objects
providing specific power
spectral density settings based
on a named profile.
pdnAdslPsdConfRowStatus
Y
pdnAdslPsdConfAtucMaxNomPsd
Y
pdnAdslPsdConfAturMaxNomPsd
Y
pdnAdslPsdConfAtucMaxNomAtp
Y
pdnAdslPsdConfAturMaxNomAtp
Y
pdnAdslPsdConfAtucMaxRxPwr
Y
pdnAdslCarMaskRowStatus
Y
pdnAdslCarMaskSubCarrierStatus
Y
pdnAdslLineSpectrumGroup
pdnAdslModeSpecificPsdGroup
pdnAdslPsdGroup
pdnAdslCarMaskGroup
A collection of objects
providing transmission
spectrum and power spectral
density related profiles.
A collection of objects providing the ability for an administrator to mask out specific
subcarriers in the downstream
or upstream direction.
472
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-LINE-EXT-MIB — PDN-ADSL-LINE-EXT-MIB.mib
Table 270: PDN-ADSL-LINE-EXT-MIB Conformance (2 of 2)
Group
Description
Objects
Supported
pdnAdslLineL2AtprtGroup
Total maximum aggregate
transmit power reduction in L2.
pdnAdslLineL2Atprt
Y
pdnAdslLineStatusLineAtnGroup
Line attenuation during diagnostic mode and initialization.
pdnAdslLineStatusAtucLineAtn
Y
pdnAdslLineStatusAturLineAtn
Y
Line attenuation during showtime.
pdnAdslLineStatusAtucSignalAtn
Y
pdnAdslLineStatusAturSignalAtn
Y
SNR margin ratio.
pdnAdslLineStatusAtucSnrMgn
Y
pdnAdslLineStatusAturSnrMgn
Y
pdnAdslLineStatusSignalAtnGroup
pdnAdslLineStatusSnrMgnGroup
pdnAdslLineStatusMaxattainableLineRateGroup
Current maximum attainable
net data rate.
pdnAdslLineStatusAtucMaxAttainableLineRate
Y
pdnAdslLineStatusAturMaxAttainableLineRate
Y
pdnAdslLineStatusActAtpGroup
Actual aggregate transmit
power.
pdnAdslLineStatusAtucActAtp
Y
pdnAdslLineStatusAturActAtp
Y
Linear representation of the
Channel Characteristics function for a subcarrier on a line.
pdnAdslLineSubCarAtucHlinPs
N
pdnAdslLineSubCarAturHlinPs
N
pdnAdslLineSubCarStatusHlogMtGroup
Logarithmic measurement time
of the Channel Characteristic
function for a subcarrier on a
line.
pdnAdslLineSubCarAtucHlogMt
N
pdnAdslLineSubCarAturHlogMt
N
pdnAdslLineSubCarStatusQlnGroup
Quiet Line Noise for a subcarrier on a line.
pdnAdslLineSubCarAtucQlnPs
Y
pdnAdslLineSubCarAturQlnPs
Y
Signal-to-Noise Ratio for a
subcarrier on a line.
pdnAdslLineSubCarAtucSnrPs
Y
pdnAdslLineSubCarAturSnrPs
Y
Bits allocation for a subcarrier
on a line.
pdnAdslLineSubCarAtucBitsPs
Y
pdnAdslLineSubCarAturBitsPs
Y
Logarithmic representation of
the Channel Characteristics
function for a subcarrier on a
line.
pdnAdslLineSubCarAtucHlogPs
Y
pdnAdslLineSubCarAturHlogPs
Y
The timestamp corresponding
to the last completion of loop
diagnostics where valid results
were obtained.
pdnAdslLineLdDateAndTimeCompleted
Y
pdnAdslLineSubCarStatusHlinGroup
pdnAdslLineSubCarStatusSnrGroup
pdnAdslLineSubCarStatusBitsGroup
pdnAdslLineSubCarStatusHlogGroup
pdnAdslLineLdDateAndTimeCompletedGroup
473
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
5.27 PDN-ADSL-SELT-MIB
5.27.1
Introduction
This MIB module defines a portion of the management information base (MIB) for managing configuration and
monitoring results of SELT (Single Ended Line Test) tests over ADSL interfaces. The MIB module used as a
reference was dated January 27, 2006 and has a LAST-UPDATED of “200601270000Z.”
At the time this MIB was defined, the IETF ADSL MIB Working does not have any work on the “standard” MIBs
planned and/or has not produced a schedule to address G.SELT needs. As a result, these objects may be a
“temporary” solution until MIBs/Objects are defined meet the needs of ADSL SELT testing.
5.27.2
Textual Conventions
The following “special” textual conventions are made or referenced in this MIB module:
•
5.27.3
•
•
•
•
PdnSeltTypes
- This textual convention defines the SELT test types available for configuration.
—
Syntax
INTEGER
• loopCharacterization(1)
- Loop Characterization Test
• loopNoiseFloor(2)
- Loop noise Floor Test
OIDs
iso
org
dod
internet
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
1
1.3
1.3.6
1.3.6.1
•
•
•
•
•
•
•
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-common
pdn-interfaces
-
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
{ pdn-common 6 }
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
1.3.6.1.4.1.1795.2.24.2.6
•
•
•
pdnAdslSeltMIB
pdnAdslSeltNotifications
pdnAdslSeltObjects
5.27.4
- { pdn-interfaces 31 }
- { pdnAdslSeltMIB 0 }
- { pdnAdslSeltMIB 1 }
1.3.6.1.4.1.1795.2.24.2.6.31
1.3.6.1.4.1.1795.2.24.2.6.31.0
1.3.6.1.4.1.1795.2.24.2.6.31.1
MIB Objects
The table identifies objects called out in this MIB. Any table object that has elements that are supported are indicated
by a “Y” in the Supported column.
474
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
Table 271: PDN-ADSL-SELT-MIB Objects
Syntax/
SEQUENCE of
Access
Status
Supported
INTEGER
awg(1)
metric(2)
metricJapan(3)
read-write
current
Y
{ pdnAdslSeltObjects 2 }
pdnAdslSeltEntry
notaccessible
current
Y
pdnAdslSeltLcTable
{ pdnAdslSeltObjects 3 }
pdnAdslSeltLcEntry
notaccessible
current
Y
pdnAdslSeltLnfTable
{ pdnAdslSeltObjects 4 }
pdnAdslSeltLnfEntry
notaccessible
current
Y
Object
OID
pdnAdslSeltWireSize
{ pdnAdslSeltObjects 1 }
pdnAdslSeltTable
5.27.4.1
pdnAdslSeltWireSize
OID:
•
pdnAdslSeltTable - { pdnAdslSeltMIB 2 }
1.3.6.1.4.1.1795.2.24.2.6.31.1
This object permits the selection of units to be used when reporting SELT results and applies to all the types of SELT
run in the device. The following are valid values:
•
•
•
awg
metric
metricJapan
5.27.4.2
- results are in feet
- results are in meters
- results are in meters
pdnAdslSeltTable
This table allows initiation/termination of SELT Tests. Each entry represents an instance of a SELT test currently
running or ever run (since last system reset) on an ADSL interface.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnAdslSeltType
475
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
OIDs:
•
•
pdnAdslSeltTable
pdnAdslSeltEntry
- { pdnAdslSeltMIB 2 }
- { pdnAdslSeltTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.31.2
1.3.6.1.4.1.1795.2.24.2.6.31.2.1
Table 272: pdnAdslSeltTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslSeltType
{ pdnAdslSeltEntry 1 }
PdnSeltTypes
not-accessible
current
Y
pdnAdslSeltCmd
{ pdnAdslSeltEntry 2 }
INTEGER
noOp(1)
start(2)
stop(3)
clearResults(4)
read-write
current
Y
pdnAdslSeltStatus
{ pdnAdslSeltEntry 3 }
INTEGER
inProgress(1)
stoppedInProgress(2)
complete(3)
notStarted(4)
resultsCleared(5)
read-only
current
Y
pdnAdslSeltDuration
{ pdnAdslSeltEntry 4 }
Unsigned32
read-write
current
Y
pdnAdslSeltTimeLeft
{ pdnAdslSeltEntry 5 }
Unsigned32
read-only
current
Y
pdnAdslSeltDateAndTimeCompleted
{ pdnAdslSeltEntry 6 }
DateAndTime
read-only
current
Y
5.27.4.2.1
pdnAdslSeltType
This object is used to specify the SELT test type that will be operated on.
5.27.4.2.2
pdnAdslSeltCmd
This object corresponds to the list of test operations that can be performed for a particular test. The following are
valid values:
•
•
•
•
noOp(1)
start(2)
stop(3)
clearResults(4)
-
Returned when reading the object
Start a test.
Stop an initiated test.
Clears the results for the pdnAdslSeltType by removing and entry in the pdnAdslSeltLcTable or the pdnAdslSeltLnfTable. After the execution of this command, the
appropriate value for pdnAdslSeltStatus would be resultsCleared(5).
If SELT test is already running on an ADSL interface, the only possible test command is stop(1).
5.27.4.2.3
pdnAdslSeltStatus
This object provides status about any SELT test running or ever run (since last reset) on an ADSL interface. This
object can be read by NMS managers to determine the status of a test; that is:
476
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
•
•
•
•
•
inProgress(1)
stoppedInProgress(2)
complete(3)
notStarted(4)
resultsCleared(5)
5.27.4.2.4
-
The test is currently running.
A test was stopped prior to completion.
The test completed are results are available.
The test has not been run on this interface since last system reset.
The entry in the test results table, Lc or Lnf, was removed as the result of the execution of the clearResults(4) pdnAdslSeltCmd.
pdnAdslSeltDuration
This object provides the approximate time, in seconds, that the SELT test measurement will take. This object should
return 0 if no test is actively running on the ADSL interface specified.
5.27.4.2.5
pdnAdslSeltTimeLeft
This object provides the approximate time left, in seconds, for the test running on this ADSL interface. This object
should return 0 if no test is actively running on the ADSL interface specified.
5.27.4.2.6
pdnAdslSeltDateAndTimeCompleted
This object provides a date and time stamp corresponding to the last completion of a test where valid results were
obtained. If no test results are available, perhaps in the situation where no test has ever been started, this object shall
return a value that has all the fields set to zero.
5.27.4.3
pdnAdslSeltLcTable
This table post results for Loop Characterization (Lc) Tests that have completed. Each entry represents the results of a
loop characterization test performed over an ADSL interface
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnAdslSeltLcSegmentIndex
OIDs:
•
•
pdnAdslSeltLcTable
pdnAdslSeltLcEntry
- { pdnAdslSeltMIB 3 }
- { pdnAdslSeltLcTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.31.3
1.3.6.1.4.1.1795.2.24.2.6.31.3.1
Table 273: pdnAdslSeltLcTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAdslSeltLcSegmentIndex
{ pdnAdslSeltLcEntry 1 }
Integer32(0…9)
not-accessible
current
Y
pdnAdslSeltLcSegmentLength
{ pdnAdslSeltLcEntry 2 }
Integer32(0…65534)
read-only
current
Y
477
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
Table 273: pdnAdslSeltLcTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAdslSeltLcSegmentGauge
{ pdnAdslSeltLcEntry 3 }
INTEGER
unknown(1)
awg26(2)
awg24(3)
awg22(4)
awg19(5)
metric32(10)
metric40(11)
metric50(12)
metric63(13)
metric90(14)
metricJapan32(20)
metricJapan40(21)
metricJapan50(22)
metricJapan65(23)
metricJapan90(24)
read-only
current
Y
pdnAdslSeltLcSegmentType
{ pdnAdslSeltLcEntry 4 }
INTEGER
notPresent(1)
inline(2)
bridgeTap(3)
read-only
current
Y
5.27.4.3.1
pdnAdslSeltLcSegmentIndex
This object indicates the index of the segment being reported. From no segments to a possible of 10 segments could
be identified in the loop topology.
5.27.4.3.2
pdnAdslSeltLcSegmentLength
This object indicates an estimate of the segment Length being reported
5.27.4.3.3
pdnAdslSeltLcSegmentGauge
This object indicates the estimated Gauge of the segment being reported. The gauge reported back is based on the
pdnAdslSeltWireSizeWireSize configuration parameter passed when the test is started. The following are valid
values:
•
•
•
•
•
•
•
•
•
•
•
•
unknow(1),
awg26(2)
awg24(3)
awg22(4)
awg19(5)
metric32(10)
metric40(11)
metric50(12)
metric63(13)
metric90(14)
metricJapan32(20)
metricJapan40(21)
-
0.32mm
0.40mm
0.50mm
0.63mm
0.90mm
0.32mm
0.40mm
478
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
•
•
•
metricJapan50(22)
metricJapan65(23)
metricJapan90(24)
5.27.4.3.4
- 0.50mm
- 0.65mm
- 0.90mm
pdnAdslSeltLcSegmentType
This object indicates the segment type being reported. The following are valid values:
•
•
•
notPresent(1)
inline(2)
bridgeTap(3)
5.27.4.4
pdnAdslSeltLnfTable
This table post results for Loop Noise Floor (Lnf) Tests that have completed. Each entry represents the results of a
Loop Noise Floor test performed over an ADSL interface.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnAdslSeltLnfSubCarrierIndex
OIDs:
•
•
pdnAdslSeltLnfTable
pdnAdslSeltLnfEntry
- { pdnAdslSeltMIB 4 }
- { pdnAdslSeltLnfTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.31.4
1.3.6.1.4.1.1795.2.24.2.6.31.4.1
Table 274: pdnAdslSeltLnfTable
Object
OID
Syntax
Access
Status
Supported
pdnAdslSeltLnfSubCarrierIndex
{ pdnAdslSeltLnfEntry 1 }
Integer32(0…63)
not-accessible
current
Y
pdnAdslSeltLnfPeakPsd
{ pdnAdslSeltLnfEntry 2 }
Integer32(0…65534)
read-only
current
Y
pdnAdslSeltLnfTotalPsd
{ pdnAdslSeltLnfEntry 3 }
Integer32(0…65534)
read-only
current
Y
pdnAdslSeltLnfSignalPsd
{ pdnAdslSeltLnfEntry 4 }
Integer32(0…65534)
read-only
current
Y
5.27.4.4.1
pdnAdslSeltLnfSubCarrierIndex
Identifies a row in the table based on a subcarrier.
The subcarrier index ranges from 0 to NSCus-1 (NSC is Number of Subcarriers) as specified in G.997.1 in the
upstream direction. Please refer to the corresponding ITU recommendation for specific values of NSCus. The “ADSL
Values for NSC” comment above lists those recommendations.
479
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
5.27.4.4.2
pdnAdslSeltLnfPeakPsd
This object indicates the peak Psd of the tone indicated by the sub-carrier index. The value returned by the agent for
this object is expressed in units of 1/256 dBm.
5.27.4.4.3
pdnAdslSeltLnfTotalPsd
This object indicates the total Psd of the tone indicated by the sub-carrier index. The value returned by the agent for
this object is expressed in units of 1/256 dBm.
5.27.4.4.4
pdnAdslSeltLnfSignalPsd
This object indicates the signal Psd of the tone indicated by the sub-carrier index. The value returned by the agent for
this object is expressed in units of 1/256 dBm.
480
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
5.27.5
5.27.5.1
Conformance Information
Compliance
This section outlines the compliance requirements for this MIB.
Mandatory Groups:
None specified.
Optional Groups:
•
•
•
•
pdnAdslSeltGroup
The group associates the objects related to the configuration of SELT tests in General.
pdnAdslSeltLcGroup
The group associates the objects related to the results of a Loop characterization SELT test.
pdnAdslSeltLnfGroup
The group associates the objects related to the results of a Loop Noise Floor SELT test.
pdnAdslSeltDateAndTimeCompletedGroup
This group is only required for implementations that require a timestamp corresponding to the last completion of a test where valid results were obtained.
481
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ADSL-SELT-MIB — PDN-ADSL-SELT-MIB.mib
5.27.5.2
Conformance
Table 275: PDN-ADSL-SELT-MIB Conformance
Group
Description
Objects
Supported
pdnAdslSeltGroup
General configuration of SELT
tests.
pdnAdslSeltCmd
Y
pdnAdslSeltStatus
Y
pdnAdslSeltWireSize
Y
pdnAdslSeltDuration
Y
pdnAdslSeltTimeLeft
Y
pdnAdslSeltLcSegmentLength
Y
pdnAdslSeltLcSegmentGauge
Y
pdnAdslSeltLcSegmentType
Y
pdnAdslSeltLnfPeakPsd
Y
pdnAdslSeltLnfTotalPsd
Y
pdnAdslSeltLnfSignalPsd
Y
pdnAdslSeltDateAndTimeCompleted
Y
pdnAdslSeltLcGroup
pdnAdslSeltLnfGroup
pdnAdslSeltDateAndTimeCompletedGroup
Objects related to results
posted for Loop
Characterization Test.
Objects related to results
posted for Loop Signal Floor
Test.
The timestamp corresponding
to the last completion of a test
where valid results were
obtained
482
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28 PDN-ARP-MIB
5.28.1
Introduction
This MIB contains objects that is used configure ARP Entries and display ARP information on a Device. The version
of the MIB used for this document had a LAST-UPDATED of 200602010000Z which decodes to February 1, 2006.
5.28.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.28.3
OIDs
•
•
•
•
iso
org
dod
internet
-
•
•
•
mgmt
mib-2
ip
- { internet 2 }
- { mgmt 1 }
- { mib-2 4 }
•
•
•
•
•
•
private
enterprises pdyn
pdn-mgmt paradyne pdn-common-
•
•
•
•
•
•
•
pdn-arp
pdnNetToMediaGenericMIBObjects
pdnNetToMediaMIBTraps
pdnNetToMediaMIBNotifications
pdnNetToMediaParams
pdnNetToMediaConfig
pdnNetTo8023MediaConfig
-
{ pdn-common 27 }
{ pdn-arp 1 }
{ pdn-arp 2 }
{ pdnNetToMediaMIBTraps 0 }
{ pdnNetToMediaGenericMIBObjects 1 }
{ pdnNetToMediaGenericMIBObjects 2 }
{ pdnNetToMediaGenericMIBObjects 3 }
1.3.6.1.4.1.1795.2.24.2.27
1.3.6.1.4.1.1795.2.24.2.27.1
1.3.6.1.4.1.1795.2.24.2.27.2
1.3.6.1.4.1.1795.2.24.2.27.2.0
1.3.6.1.4.1.1795.2.24.2.27.1.1
1.3.6.1.4.1.1795.2.24.2.27.1.2
1.3.6.1.4.1.1795.2.24.2.27.1.3
•
•
•
•
ipNetToMediaTable
ipNetToMediaEntry
ipNetToMediaIfIndex
ipNetToMediaPhysAddress
-
{ ip 2 }
{ ipNetToMediaTable 1 }
{ ipNetToMediaEntry 1 }
{ pdnNetToMediaMIBTraps 1 }
1.3.6.1.2.1.4.2
1.3.6.1.2.1.4.2.1
1.3.6.1.2.1.4.2.1.1
1.3.6.1.4.1.1795.2.24.2.27.1.1
5.28.4
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.4
{ internet 4 }
1.3.6.1.4
{ private 1 }
1.3.6.1.4.1
{ enterprises 1795 }1.3.6.1.4.1.1795
{ pdyn 2 }
1.3.6.1.4.1.1795.2
{ pdn-mgmt 24 } 1.3.6.1.4.1.1795.2.24
{ paradyne 2 }
1.3.6.1.4.1.1795.2.24.2
MIB Objects
Table 276: PDN-ARP- MIB Objects (1 of 2)
Object
OID
Description
Supported
pdnNetToMediaParams
{ pdnNetToMediaGenericMIBObjects 1 }
ARP Parameters Configuration group
N
pdnNetToMediaConfig
{ pdnNetToMediaGenericMIBObjects 2 }
ARP Entry Configuration group
Y
pdnNetTo8023MediaConfig
{ pdnNetToMediaGenericMIBObjects 3 }
ARP Entry Configuration for 802.3 Media Cards
N
483
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Table 276: PDN-ARP- MIB Objects (2 of 2)
Object
OID
Description
Supported
ipNetToMediaConfig
{ pdnNetToMediaConfig 4 }
Proxy ARP Configuration Group
Y
5.28.4.1
pdnNetToMediaParams
This group consists of configurable ARP parameters.
OIDs:
•
pdnNetToMediaParams
- { pdnNetToMediaGenericMIBObjects 1 }
1.3.6.1.4.1.1795.2.24.2.27.1.1
Table 277: pdnNetToMediaParams
Object
OID
Syntax
Access
Status
Supported
pdnNetToMediaParamsCompEntryTimout
{ pdnNetToMediaParams 1 }
Integer32
(0…99999)
read-write
current
N
pdnNetToMediaParamsIncompEntryTimeout
{ pdnNetToMediaParams 2 }
Integer32
(0…99999)
read-write
current
N
pdnNetToMediaParamsDefRoutEntryTimeout
{ pdnNetToMediaParams 3 }
Integer32
(0…99999)
read-write
current
N
pdnNetToMediaParamsAprTable
{ pdnNetToMediaParams 4 }
SEQUENCE of
pdnNetToMediaParamsAprEntry
not-accessible
current
Y
5.28.4.1.1
pdnNetToMediaParamsCompEntryTimeout
Complete Entry Timeout is the length of time that a complete entry remains in the ARP table before removal. A
complete entry is one for which there is a MAC address (that is, a node has responded to the ARP request). If an entry
gets this old without being referenced, it is removed from the table. The range for this parameter is 1 to 200000
minutes.
The default value for this object is 20.
5.28.4.1.2
pdnNetToMediaParamsIncompEntryTimeout
Incomplete Entry Timeout is the length of time that an incomplete entry remains in the ARP table before removal. An
incomplete entry is one for which there is no MAC address (that is, an ARP request has been made, but no response
has been received.) This is also the amount of time that a packet will remain in the system while waiting for address
resolution. The range for this parameter is 1 to 255 minutes.
The default value for this object is 3.
484
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28.4.1.3
pdnNetToMediaParamsDefRouteEntryTimeout
Default Route Entry Timeout is the length of time a default route entry will remain in the ARP table. If default route
gets this old without being referenced, an ARP request is sent to the next hop router. If no response is received, it is
removed from the ARP table and the card will switch to the next reachable default route with the highest preference.
The range for this parameter is 1 to 20 minutes.
The default value for this object is 1.
5.28.4.1.4
pdnNetToMediaParamsAprTable
The ARP Periodic Request (APR) Table. This table allows timers which control the rate in which ARP requests are
periodically sent to IP addresses to be configured and displayed. Each entry represents an IP address to send an ARP
request to.
Index(es):
•
pdnNetToMediaParamsAprIpAddr
OIDs:
•
pdnNetToMediaParamsAprTable
- { pdnNetToMediaParams 4 }
1.3.6.1.4.1.1795.2.24.2.27.1.1.4
•
pdnNetToMediaParamsAprEntry
- { pdnNetToMediaParamsAprTable 1 }
1.3.6.1.4.1.1795.2.24.2.27.1.1.4.1
Table 278: pdnNetToMediaParamsAprTable
Object
OID
Syntax
Access
Status
Supported
pdnNetToMediaParamsAprIpAddr
{ pdnNetToMediaParamsAprEntry 1 }
IpAddress
not-accessible
current
Y
pdnNetToMediaParamsAprRowStatus
{ pdnNetToMediaParamsAprEntry 2 }
RowStatus
read-create
current
Y
pdnNetToMediaParamsAprReqPeriod
{ pdnNetToMediaParamsAprEntry 3 }
Unsigned32(1…1440)
read-create
current
Y
pdnNetToMediaParamsAprTimeToNext
{ pdnNetToMediaParamsAprEntry 4 }
Unsigned32
read-only
current
Y
5.28.4.1.4.1
pdnNetToMediaParamsAprIpAddr
Identifies the IP address to periodically send an ARP request to and is used to identify corresponding rows in the
table.
5.28.4.1.4.2
pdnNetToMediaParamsAprRowStatus
This object allows create, change, and delete operations on the table.
485
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28.4.1.4.3
pdnNetToMediaParamsAprReqPeriod
Configures the period, in minutes, that ARP requests are periodically sent. The range is from one request every
minute to one request every day (1440 minutes).
5.28.4.1.4.4
pdnNetToMediaParamsAprTimeToNext
Indicates the time, in minutes, remaining before the next ARP request will be sent.
5.28.4.2
pdnNetToMediaConfig
This group contains objects for configuring ARP entries.
OIDs:
•
pdnNetToMediaConfig
- { pdnNetToMediaGenericMIBObjects 2 }
1.3.6.1.4.1.1795.2.24.2.27.1.2
Table 279: pdnNetToMediaConfig
Object
OID
Syntax
Access
Status
Supported
pdnNetToMediaConfigTable
{ pdnNetToMediaConfig 1 }
SEQUENCE of
pdnNetToMediaConfigEntry
not-accessible
current
N
pdnNetToMediaClearAllArp
{ pdnNetToMediaConfig 2 }
INTEGER
noop(1)
clear(2)
read-write
current
Y
pdnNetToMediaProxyArpTable
{ pdnNetToMediaConfig 3 }
SEQUENCE of
pdnNetToMediaProxyArpEntry
not-accessible
current
N
5.28.4.2.1
pdnNetToMediaConfigTable
This table supports the ARP Entry Configuration Table for 802.3 Media Cards and is a sequence of
pdnNetToMediaConfigEntry where each entry is a list of information for each ARP Entry in the ARP Table to be
displayed.
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnNetToMediaConfigIpAddr
OIDs:
•
•
pdnNetToMediaConfigTable
pdnNetToMediaConfigEntry
- { pdnNetToMediaConfig 1 }
- { pdnNetToMediaConfigTable 1 }
486
1.3.6.1.4.1.1795.2.24.2.27.1.2.1
1.3.6.1.4.1.1795.2.24.2.27.1.2.1.1
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Table 280: pdnNetToMediaConfigTable
Object
OID
Syntax
Access
Status
Supported
pdnNetToMediaConfigIpAddr
{ pdnNetToMediaConfigEntry 1 }
IpAddress
not-accessible
current
N
pdnNetToMediaConfigMacAddr
{ pdnNetToMediaConfigEntry 2 }
MacAddress
read-create
current
N
pdnNetToMediaConfigMin
{ pdnNetToMediaConfigEntry 3 }
Integer32
(0…99999)
read-only
current
N
pdnNetToMediaConfigFlags
{ pdnNetToMediaConfigEntry 4 }
Integer32
read-only
current
N
pdnNetToMediaConfigTrailer
{ pdnNetToMediaConfigEntry 5 }
SwitchState
read-create
current
N
pdnNetToMediaConfigPerm
{ pdnNetToMediaConfigEntry 6 }
TruthValue
read-create
current
N
pdnNetToMediaConfigRowStatus
{ pdnNetToMediaConfigEntry 7 }
RowStatus
read-create
current
N
5.28.4.2.1.1
pdnNetToMediaConfigIpAddr
This objects corresponds to an IP Address of a Host or Client
5.28.4.2.1.2
pdnNetToMediaConfigMacAddr
This object corresponds to a MAC Address of a Host or Client
5.28.4.2.1.3
pdnNetToMediaConfigMin
This objects displays the number of minutes since an Arp entry was last used.
5.28.4.2.1.4
pdnNetToMediaConfigFlags
This object contains multiple information for an entry. The information can be interpreted as follows:
•
•
•
•
•
•
0x0004 - permanent entry
0x0008 - publish entry (respond for other host)
0x0010 - has requested trailers
0x0020 - Proxy Arp Entry
0x0040 - Subnetted Proxy ARP entry
0x0100 - Arp For Default Gateway
5.28.4.2.1.5
pdnNetToMediaConfigTrailer
This object is used to specify whether or not trailer encapsulation should be enabled or disabled.
5.28.4.2.1.6
pdnNetToMediaConfigPerm
This object is used to specify whether or not an entry should be stored permanently in Non-volatile storage. If the
value is “true(1)” a permanent entry is added to non-volatile storage.
487
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28.4.2.1.7
pdnNetToMediaConfigRowStatus
This object is used to create or delete a row in this table
5.28.4.2.2
pdnNetToMediaClearAllArp
Setting this object to a value of “clear(2)” will remove all entries from the ARP table.
5.28.4.2.3
pdnNetToMediaProxyArpTable
This table is used to enable or disable proxy ARP for the specified interface. This table is a sequence of
pdnNetToMediaProxyArpEntry that allows a user to enable or disable proxy ARP for the specified interface.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pdnNetToMediaProxyArpTable - { pdnNetToMediaConfig 3 }
pdnNetToMediaProxyArpEntry - { pdnNetToMediaProxyArpTable 1 }
1.3.6.1.4.1.1795.2.24.2.27.1.2.3
1.3.6.1.4.1.1795.2.24.2.27.1.2.3.1
Table 281: pdnNetToMediaProxyArpTable
Object
OID
Syntax
Access
Status
Supported
pdnNetToMediaProxyArpStatus
{ pdnNetToMediaProxyArpEntry 1 }
INTEGER
disable(1)
enable(2)
read-create
current
N
5.28.4.2.4
pdnNetToMediaProxyArpStatus
Setting this object to a value “enable(2)” will enable proxy ARP for the interface identified by IfIndex. The value
“disable(1)” will disable proxy ARP for the interface.
5.28.4.3
pdnNetTo8023MediaConfig
This group contains an ARP Entry Table for configuring 802.3 Media Cards
OIDs:
•
pdnNetTo8023MediaConfig
- { pdnNetToMediaGenericMIBObjects 3 } 1.3.6.1.4.1.1795.2.24.2.27.1.3
488
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Table 282: pdnNetTo8023MediaConfig
Object
OID
Syntax
Access
Status
Supported
pdnNetTo8023MediaConfigTable
{ pdnNetTo8023MediaConfig 1 }
SEQUENCE of
pdnNetTo8023MediaConfigEntry
not-accessible
current
N
5.28.4.3.1
pdnNetTo8023MediaConfigTable
A table displaying information about ARP Entries. This table is a sequence of pdnNetTo8032MediaConfigEntry
where each entry is a list of information for each ARP Entry in the ARP Table to be displayed.
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnNetTo8023MediaConfigIpAddr
pdnNetTo8023MediaConfigVnidId
OIDs:
•
pdnNetTo8023MediaConfigTable
•
pdnNetTo8023MediaConfigEntry
- { pdnNetTo8023MediaConfig 1 }
- { pdnNetTo8023MediaConfigTable 1 }
1.3.6.1.4.1.1795.2.24.2.27.1.3.1
1.3.6.1.4.1.1795.2.24.2.27.1.3.1.1
Table 283: pdnNetTo8023MediaConfigTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnNetTo8023MediaConfigIpAddr
{ pdnNetTo8023MediaConfigEntry 1 }
IpAddress
not-accessible
current
N
pdnNetTo8023MediaConfigVnidId
{ pdnNetTo8023MediaConfigEntry 2 }
VnidRange
read-only
current
N
pdnNetTo8023MediaConfigMacAddr
{ pdnNetTo8023MediaConfigEntry 3 }
MacAddress
read-create
current
N
pdnNetTo8023MediaConfigMin
{ pdnNetTo8023MediaConfigEntry 4 }
Integer32
(1…99999)
read-only
current
N
pdnNetTo8023MediaConfigFlags
{ pdnNetTo8023MediaConfigEntry 5 }
Integer32
read-only
current
N
pdnNetTo8023MediaConfigTrailer
{ pdnNetTo8023MediaConfigEntry 6 }
SwitchState
read-create
current
N
pdnNetTo8023MediaConfigPerm
{ pdnNetTo8023MediaConfigEntry 7 }
TruthValue
read-create
current
N
489
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Table 283: pdnNetTo8023MediaConfigTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnNetTo8023MediaConfigRowStatus
{ pdnNetTo8023MediaConfigEntry 8 }
RowStatus
read-create
current
N
5.28.4.3.1.1
pdnNetTo8023MediaConfigIpAddr
This objects corresponds to an IP Address of a Host or Client.
5.28.4.3.1.2
pdnNetTo8023MediaConfigVnidId
The VNID Id number of the virtual network for which this entry contains management information.
5.28.4.3.1.3
pdnNetTo8023MediaConfigMacAddr
This object corresponds to a MAC Address of a Host or Client.
5.28.4.3.1.4
pdnNetTo8023MediaConfigMin
This objects displays the number of minutes since an Arp entry was last used.
5.28.4.3.1.5
pdnNetTo8023MediaConfigFlags
This object contains multiple information for an entry. The information can be interpreted as follows:
•
•
•
•
•
•
0x0004 - permanent entry
0x0008 - publish entry (respond for other host)
0x0010 - has requested trailers
0x0020 - Proxy Arp Entry
0x0040 - Subnetted Proxy ARP entry
0x0100 - Arp For Default Gateway
5.28.4.3.1.6
pdnNetTo8023MediaConfigTrailer
This object is used to specify whether or not trailer encapsulation should be enabled or disabled.
5.28.4.3.1.7
pdnNetTo8023MediaConfigPerm
This object is used to specify whether or not an entry should be stored permanently in Non-volatile storage. If the
value is “true(1)” a permanent entry is added to non-volatile storage.
5.28.4.3.1.8
pdnNetTo8023MediaConfigRowStatus
This object is used to create or delete a row in this table.
5.28.4.4
ipNetToMediaConfig
OIDs:
•
ipNetToMediaConfig
- { pdnNetToMediaConfig 4 }
490
1.3.6.1.4.1.1795.2.24.2.27.1.2.4
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Table 284: ipNetToMediaConfig
Object
OID
Syntax
Access
Status
Supported
ipNetToMediaForwardingMode
{ ipNetToMediaConfig 1 }
INTEGER
basic(1)
mxu(2)
sms(3)
ult(4)
read-write
current
Y
ipNetToMediaDefaultNHR
{ ipNetToMediaConfig 2 }
IpAddress
read-write
current
Y
ipNetToMediaExtTable
{ ipNetToMediaConfig 3 }
SEQUENCE OF
ipNetToMediaExtEntry
not-accessible
current
Y
ipNetToMediaLimitTable
{ ipNetToMediaConfig 4 }
SEQUENCE OF
ipNetToMediaLimitEntry
not-accessible
current
Y
5.28.4.4.1
ipNetToMediaForwardingMode
The following are values are defined for this object:
•
•
basic(1)
mxu(2)
•
sms(3)
•
ult(4)
- basic or (transparent) Mode
- Mux Forwarding Mode
All traffic is routed to the upstream router. Port-to-port switching is not allowed.
For more information about transparent vs. forwarding mode refer to RFC 1483 that defines
bridge functionality and the mib RFC 1493 that defines mib needed to support different bridge
functionality.
- Subscriber Management Mode
In this mode all traffic is routed to the uplink port. Port-to-port switching is not allowed. This
also enables other internal software functions that are needed to the SMS support. When this
mode is selected, an external management VLAN is established to the Subscriber Management
System.
- Uplink Tagging Mode
Setting the value to ult(4) will enable Uplink Tagging. The Uplink Tagging Feature implements a portion of the IEEE 802.3Q VLAN standard to provide tagged Ethernet frames on the
uplink port with a one-to-one mapping of ingress ADSL (subscriber) link to the VLAN identifier carried in the Ethernet tag header.
In this mode, VLANs are assigned using the ultBaseVlanTag (Section 5.62.4.5, Page 806) and
the ultIndex (Section 5.62.4.6, Page 806) MIB objects.
5.28.4.4.2
ipNetToMediaDefaultNHR
Setting this address will configure a default NHR for the system.
5.28.4.4.3
ipNetToMediaExtTable
This table is designed to augment ipNetToMediaTable from RFC 1213. This table is the IP Address Translation table
used for mapping from IP addresses to physical addresses where each entry contains one IpAddress to ‘physical’
491
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
address equivalence.
Augments:
•
ipNetToMediaTable (Section 5.4.3.1.22, Page 81)
Index(es):
•
•
ipNetToMediaIfIndex (Section 5.4.3.1.22.1, Page 82)
ipNetToMediaNetAddress (Section 5.4.3.1.22.3, Page 82)
OIDs:
•
•
ipNetToMediaExtTable
ipNetToMediaExtEntry
- { ipNetToMediaConfig 3 }
- { ipNetToMediaExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.27.1.2.4.3
1.3.6.1.4.1.1795.2.24.2.27.1.2.4.3.1
Table 285: ipNetToMediaExtTable
Object
OID
Syntax
Access
Status
Supported
ipNetToMediaNHR
{ ipNetToMediaExtEntry 1 }
IpAddress
read-create
current
Y
ipNetToMediaSubPort
{ ipNetToMediaExtEntry 2 }
Integer32(1…8)
read-create
current
Y
ipNetToMediaVlanID
{ ipNetToMediaExtEntry 3 }
VlanIndex
read-create
current
Y
ipNetToMediaAgeOutTime
{ ipNetToMediaExtEntry 4 }
Integer32
(0…86400)
read-create
current
Y
ipNetToMediaTimeRemaining
{ ipNetToMediaExtEntry 5 }
Integer32
(0…86400)
read-create
current
Y
5.28.4.4.3.1
ipNetToMediaNHR
This object is used to configure next hop router for the interface using proxy ARP.
5.28.4.4.3.2
ipNetToMediaSubPort
The subport associated with the entry. Some implementations can select one of multiple priority-ordered MAC bridge
ports. The term “subport” refers to one of the priority-ordered MAC bridge ports that can be mapped to an interface.
This object is used to select which “subport” corresponds to an entry in implementations that support “subports.”
Implementations that do not support ‘subports’ and yet support this object, must set this object to “1.”
Reference(s):
•
Section 3.4, Proxy ARP Table,
Franzek, P. and Tran, T., “Proxy ARP and DHCP Snooping Enhancements,” Issue 0.2, January 19, 2006.
5.28.4.4.3.3
ipNetToMediaVlanID
The VLAN the entry corresponds to.
492
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Reference(s):
•
Section 3.4, Proxy ARP Table,
Franzek, P. and Tran, T., “Proxy ARP and DHCP Snooping Enhancements,” Issue 0.2, January 19, 2006.
5.28.4.4.3.4
ipNetToMediaAgeOutTime
The length of time, in seconds, unreferenced-dynamic entries are to remain in the ARP Table. When this object is set
to “0,” unreferenced-dynamic entries will not be removed from the ARP Table.
Reference(s):
•
Section 3.4, Proxy ARP Table,
Franzek, P. and Tran, T., “Proxy ARP and DHCP Snooping Enhancements,” Issue 0.2, January 19, 2006.
5.28.4.4.3.5
ipNetToMediaTimeRemaining
The length of time, in seconds, until an unreferenced entry is removed from the ARP Table.
5.28.4.4.4
ipNetToMediaLimitTable
This table is used for to configure max number of IP addresses allowed on that interface. This table is a sequence of
ipNetToMediaLimitEntry where each entry contains number of IP Addresses allowed on that interface.
Index(es):
•
ipNetToMediaIfIndex (Section 5.4.3.1.22.1, Page 82)
OIDs:
•
•
ipNetToMediaLimitTable
ipNetToMediaLimitEntry
- { ipNetToMediaConfig 4 }
- { ipNetToMediaLimitTable 1 }
1.3.6.1.4.1.1795.2.24.2.27.1.2.4.4
1.3.6.1.4.1.1795.2.24.2.27.1.2.4.4.1
Table 286: ipNetToMediaLimitTable
Object
OID
Syntax
Access
Status
Supported
ipNetToMediaLimitEnabled
{ ipNetToMediaLimitEntry 1 }
TruthValue
read-create
current
Y
ipNetToMediaMaxIPAddresses
{ ipNetToMediaLimitEntry 2 }
Integer32(0…99999)
read-create
current
Y
5.28.4.4.4.1
ipNetToMediaLimitEnabled
This object is used to enable/disable limiting number of ip addresses on interfaces using proxy ARP.
5.28.4.4.4.2
ipNetToMediaMaxIPAddresses
This object is used to configure number of ip addresses allowed on interfaces using proxy ARP.
493
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28.5
Traps
OIDs:
•
pdnNetToMediaMIBNotifications
- { pdnNetToMediaMIBTraps 1 }
1.3.6.1.4.1.1795.2.24.2.27.2.0
Table 287: PDN-ARP- MIB Traps
Notification
OID
Variable Bindings / Objects
Status
Supported
unauthorizedUserEvent
{ pdnNetToMediaMIBNotifications1 }
ipNetToMediaIfIndex
ipNetToMediaPhysAddress
current
N
5.28.5.1
unauthorizedUserEvent
This trap is to communicate that on the interface where security authorization (MAC or IP to port) is enabled, frame
arrived that is not authorized for that interface.
494
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28.6
5.28.6.1
Conformance Information
Compliance
This section outlines the compliance requirements for this MIB.
Mandatory Groups:
None specified.
Optional Groups:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
pdnNetToMediaParamsGroup
This group is only required for implementations that need to configure the ARP table.
pdnNetToMediaConfigGroup
This group is only required for implementations that need to be able to add ARP table entries.
pdnNetToMedia8023ConfigGroup
This group is only required for implementations that need to be able to add 802.3 ARP table entries.
pdnNetToMediaClearGroup
This group is only required for implementations that need to be able to clear all ARP entries from a table.
pdnNetToMediaProxyArpGroup
This group is only required for implementations that need to be able to set all proxy ARP entries.
pdnNetToMediaConfigProxyArpGroup
This group is only required for implementations that need to allow the setting of some proxy ARP entries.
pdnNetToMediaExtGroup
This group is only required for implementations that need to allow the configuration of a next-hop router.
pdnNetToMediaLimitGroup
This group is only required for implementations that need to allow the configuration of limits for proxy ARP.
pdnNetToMediaUnauthorizedUserEventGroup
This group is only required for implementations that need generate notifications of unauthorized user events.
pdnNetToMediaParamsAprConfigGroup
This group is only required for implementations that need to configure a timer to send ARP requests to IP
addresses periodically.
pdnNetToMediaParamsAprTimeToNextGroup
This group is only required for implementations that need to configure a timer to send ARP requests to IP
addresses periodically and that need to display the amount of time remaining until the next ARP request gets
sent to a particular IP address.
ipNetToMediaSubPortGroup
This group is only required for implementations that need to support “subports.”
ipNetToMediaVlanIDGroup
This group is only required for implementations that need to configure a VLAN ID with a static entry in the
ARP Table.
ipNetToMediaAgeOutGroup
This group is only required for implementations that need to be able to configure the length of time that
unreferenced-entries are to remain in the ARP Table.
495
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
5.28.6.2
Conformance
Table 288: PDN-ARP-MIB Conformance (1 of 2)
Group
Description
Objects
Supported
pdnNetToMediaParamsGroup
A collection of objects
providing way to configure
ARP table entries.
pdnNetToMediaParamsCompEntryTimeout
N
pdnNetToMediaParamsIncompEntryTimeout
N
pdnNetToMediaParamsDefRouteEntryTimeout
N
A collection of objects
providing way to add ARP
table
pdnNetToMediaConfigMacAddr
N
pdnNetToMediaConfigMin
N
entries.
pdnNetToMediaConfigFlags
N
pdnNetToMediaConfigTrailer
N
pdnNetToMediaConfigPerm
N
pdnNetToMediaConfigRowStatus
N
pdnNetTo8023MediaConfigVnidId
N
pdnNetTo8023MediaConfigMacAddr
N
pdnNetTo8023MediaConfigMin
N
pdnNetTo8023MediaConfigFlags
N
pdnNetTo8023MediaConfigTrailer
N
pdnNetTo8023MediaConfigPerm
N
pdnNetTo8023MediaConfigRowStatus
N
pdnNetToMediaConfigGroup
pdnNetToMedia8023ConfigGroup
A collection of objects
providing way to add 802.3
ARP table entries.
pdnNetToMediaClearGroup
A collection of objects that
allows to clear all arp entries
from a table.
pdnNetToMediaClearAllArp
Y
pdnNetToMediaProxyArpGroup
A collection of objects that
allows to set all proxy ARP
entries
pdnNetToMediaProxyArpStatus
N
pdnNetToMediaConfigProxyArpGroup
A collection of objects that
allows to set some proxy ARP
entries.
ipNetToMediaForwardingMode
Y
ipNetToMediaDefaultNHR
Y
pdnNetToMediaExtGroup
A collection of objects that
allows to set some proxy ARP
entries.
ipNetToMediaNHR
Y
pdnNetToMediaLimitGroup
A collection of objects that
allows to set some proxy ARP
entries.
ipNetToMediaLimitEnabled
Y
ipNetToMediaMaxIPAddresses
Y
496
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ARP-MIB — pdn_Arp.mib
Table 288: PDN-ARP-MIB Conformance (2 of 2)
Group
Description
Objects
Supported
pdnNetToMediaParamsAprConfigGroup
A collection of objects to
configure a timer to send ARP
request to IP addresses
periodically.
pdnNetToMediaParamsAprRowStatus
Y
pdnNetToMediaParamsAprReqPeriod
Y
pdnNetToMediaParamsAprTimeToNextGroup
Object to display the amount of
time remaining until the next
ARP request gets sent for a
particular IP address.
pdnNetToMediaParamsAprTimeToNext
Y
pdnNetToMediaUnauthorizedUserEventGroup
Unauthorized user event group.
unauthorizedUserEvent
N
ipNetToMediaSubPortGroup
Object representing a “subport”
corresponding to an entry in the
ARP Table.
ipNetToMediaSubPort
Y
ipNetToMediaVlanIDGroup
Object representing a VLAN
corresponding to an entry in the
ARP Table.
ipNetToMediaVlanID
Y
ipNetToMediaAgeOutGroup
Objects supporting the aging
and removal of entries in the
ARP TAble.
ipNetToMediaAgeOutTime
Y
ipNetToMediaTimeRemaining
Y
497
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATM-BRIDGE-IWF-MIB — PDN-ATM-BRIDGE-IWF-MIB.mib
5.29 PDN-ATM-BRIDGE-IWF-MIB
5.29.1
Introduction
This MIB contains objects that are used for monitoring and controlling the ATM/Bridge Interworking Function.
The revision of the MIB that this SNMP Operational Specification aligns with is that which has a LAST-UPDATED
of “200304240000Z,” or April 24, 2003.
5.29.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.29.3
•
•
•
•
OIDs
iso
org
dod
internet
-
•
•
•
mgmt
mib-2
ip
- { internet 2 }
- { mgmt 1 }
- { mib-2 4 }
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.4
•
•
•
•
•
•
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-common
-
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
•
•
•
pdnAtmBridgeIwfMIB
pdnAtmBridgeIwfNotifications
pdnAtmBridgeIwfObjects
5.29.4
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
1
1.3
1.3.6
1.3.6.1
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
- { pdn-common 43 }
- { pdnAtmBridgeIwfMIB 0 }
- { pdnAtmBridgeIwfMIB 1 }
1.3.6.1.4.1.1795.2.24.2.43
1.3.6.1.4.1.1795.2.24.2.43.0
1.3.6.1.4.1.1795.2.24.2.43
MIB Objects
Table 289: PDN-ATM-BRIDGE-IWF-MIB Objects
Object
OID
Syntax
Access
Status
Supported
pdnAtmBridgeIwfTable
{ pdnAtmBridgeIwfObjects 1 }
SEQUENCE OF
pdnAtmBridgeIwfEntry
not-accessible
current
Y
5.29.4.1
pdnAtmBridgeIwfTable
This table allows mapping of ATM VCs to Bridge Ports.
498
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATM-BRIDGE-IWF-MIB — PDN-ATM-BRIDGE-IWF-MIB.mib
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
pdnAtmBridgeIwfVclVpi
pdnAtmBridgeIwfVclVci
OIDs:
•
•
pdnAtmBridgeIwfTable
pdnAtmBridgeIwfEntry
- { pdnAtmBridgeIwfObjects 1 } 1.3.6.1.4.1.1795.2.24.2.43.1.1
- { pdnAtmBridgeIwfTable 1 }
1.3.6.1.4.1.1795.2.24.2.43.1.1.1
Table 290: pdnAtmBridgeIwfTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmBridgeIwfVclVpi
{ pdnAtmBridgeIwfEntry 1 }
Unsigned32(0…4095)
not-accessible
current
Y
pdnAtmBridgeIwfVclVci
{ pdnAtmBridgeIwfEntry 2 }
Unsigned32(0…65535)
not-accessible
current
Y
pdnAtmBridgeIwfRowStatus
{ pdnAtmBridgeIwfEntry 3 }
RowStatus
read-create
current
Y
pdnAtmBridgeIwfDot1dBasePort
{ pdnAtmBridgeIwfEntry 4 }
Unsigned32(1…65535)
read-create
current
Y
5.29.4.1.1
pdnAtmBridgeIwfVclVpi
The VPI value of the VCL.
5.29.4.1.2
pdnAtmBridgeIwfVclVci
The VCI value of the VCL.
5.29.4.1.3
pdnAtmBridgeIwfRowStatus
The SNMP RowStatus (Section 4.11, Page 15) of the current row.
5.29.4.1.4
pdnAtmBridgeIwfDot1dBasePort
This object specifies the bridge port the VPI/VCI maps to.
499
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATM-BRIDGE-IWF-MIB — PDN-ATM-BRIDGE-IWF-MIB.mib
5.29.5
Conformance Information
5.29.5.1
Compliance
No compliance statements were defined nor were any mandatory objects specified.
5.29.5.1.1
pdnAtmBridgeIwfMIBCompliance
The compliance statement for pdnAtmIwfBridge entities which implement the pdnAtmBridgeIwfMIB.
Mandatory Groups:
•
5.29.5.2
pdnAtmBridgeIwfGroup
Conformance
Table 291: PDN-ATM-BRIDGE-IWF-MIB Conformance
Group
Description
pdnAtmBridgeIwfGroup
Objects grouped for ATM to Bridge Port Mapping
500
Objects
Supported
pdnAtmBridgeIwfRowStatus
Y
pdnAtmBridgeIwfDot1dBasePort
Y
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
5.30 PDN-ATMEXT-MIB
5.30.1
Introduction
This MIB Module extends the ATM-MIB defined in RFC 2515.
The revision of the MIB that this SNMP Operational Specification aligns with is that which has a LAST-UPDATED
of “200303310000Z,” or March 31, 2003.
5.30.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.30.3
•
•
•
•
OIDs
iso
org
dod
internet
-
•
•
•
mgmt
mib-2
ip
- { internet 2 }
- { mgmt 1 }
- { mib-2 4 }
1.3.6.1.2
1.3.6.1.2.1
1.3.6.1.2.1.4
•
•
•
•
•
•
•
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-common
pdn-interfaces
-
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
1.3.6.1.4.1.1795.2.24.2.6
•
•
•
•
•
•
pdnAtm
pdnAtmExtMIB
pdnAtmExtMIBObjects
pdnAtmExtMIBTraps
pdnAtmExtMIBTrapPrefix
pdnAtmExtMIBConformance
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
1
1.3
1.3.6
1.3.6.1
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
{ pdn-common 6 }
-
{ pdn-interfaces 11 }
{ pdnAtm 5 }
{ pdnAtmExtMIB 1 }
{ pdnAtmExtMIB 2 }
{ pdnAtmExtMIBTraps 0 }
{ pdnAtmExtMIB 3 }
501
1.3.6.1.4.1.1795.2.24.2.6.11
1.3.6.1.4.1.1795.2.24.2.6.11.5
1.3.6.1.4.1.1795.2.24.2.6.11.5.1
1.3.6.1.4.1.1795.2.24.2.6.11.5.2
1.3.6.1.4.1.1795.2.24.2.6.11.5.2.0
1.3.6.1.4.1.1795.2.24.2.6.11.5.3
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
5.30.4
MIB Objects
Table 292: PDN-ATMEXT-MIB Objects
Object
OID
Syntax
Access
Status
Supported
pdnAtmIfConfExtTable
{ pdnAtmExtMIBObjects 1 }
SEQUENCE OF
pdnAtmIfConfExtEntry
not-accessible
current
N
pdnAtmTrafficDescrParam
ExtTable
{ pdnAtmExtMIBObjects 2 }
SEQUENCE OF
pdnAtmTrafficDescrParamExtEntry
not-accessible
current
N
pdnAal5VccExtTable
{ pdnAtmExtMIBObjects 3 }
SEQUENCE OF
pdnAal5VccExtEntry
not-accessible
current
Y
5.30.4.1
pdnAtmIfConfExtTable
The Paradyne Extension to the atmInterfaceConfTable of the ATM-MIB.
Augments:
•
atmInterfaceConfTable (Section 5.15.4.1, Page 318)
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pdnAtmIfConfExtTable
pdnAtmIfConfExtEntry
- { pdnAtmExtMIB 1 }
- { pdnAtmIfConfExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.5.1
1.3.6.1.4.1.1795.2.24.2.6.11.5.1.1
Table 293: pdnAtmIfConfExtTable (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAtmIfConfExt
VbrRtBandwidthUtil
{ pdnAtmIfConfExtEntry 1 }
Integer32(0…9999)
read-write
current
N
pdnAtmIfConfExt
VbrNrtBandwidthUtil
{ pdnAtmIfConfExtEntry 2 }
Integer32(0…9999)
read-write
current
N
pdnAtmIfConfExt
HecErrorThreshold
{ pdnAtmIfConfExtEntry 3 }
Integer32
read-write
current
N
pdnAtmIfConfExt
UnknownCellThreshold
{ pdnAtmIfConfExtEntry 4 }
Integer32
read-write
current
N
502
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
Table 293: pdnAtmIfConfExtTable (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAtmIfConfExt
OcdEventThreshold
{ pdnAtmIfConfExtEntry 5 }
Integer32
read-write
current
N
pdnAtmIfConfExt
BandwidthUtilCbrReserved
{ pdnAtmIfConfExtEntry 6 }
Integer32
read-write
current
N
pdnAtmIfConfExt
BandwidthUtilCbrAssigned
{ pdnAtmIfConfExtEntry 7 }
Integer32
read-only
current
N
pdnAtmIfConfExt
BandwidthUtilVbrRtReserved
{ pdnAtmIfConfExtEntry 8 }
Integer32
read-write
current
N
pdnAtmIfConfExt
BandwidthUtilVbrRtAssigned
{ pdnAtmIfConfExtEntry 9 }
Integer32
read-only
current
N
pdnAtmIfConfExt
BandwidthUtilVbrNrtReserved
{ pdnAtmIfConfExtEntry 10 }
Integer32
read-write
current
N
pdnAtmIfConfExt
BandwidthUtilVbrNrtAssigned
{ pdnAtmIfConfExtEntry 11 }
Integer32
read-only
current
N
pdnAtmIfConfExt
BandwidthUtilUbrReserved
{ pdnAtmIfConfExtEntry 12 }
Integer32
read-write
current
N
pdnAtmIfConfExt
BandwidthUtilUbrAssigned
{ pdnAtmIfConfExtEntry 13 }
Integer32
read-only
current
N
pdnAtmIfConfExt
RateShape
{ pdnAtmIfConfExtEntry 14 }
Integer32(512…46080)
read-write
current
N
5.30.4.1.1
pdnAtmIfConfExtVbrRtBandwidthUtil
The bandwidth utilization for real-time vbr type traffic expressed as a percentage.
5.30.4.1.2
pdnAtmIfConfExtVbrNrtBandwidthUtil
The bandwidth utilization for non-real-time VBR type traffic expressed as a percentage.
5.30.4.1.3
pdnAtmIfConfExtHecErrorThreshold
The value of this object represents the threshold value for the number of uncorrectable HEC errors in a 15 minutes
interval. An SNMP link Up/Down trap would be generated if the number of uncorrectable HEC errors in a 15 minutes
interval exceeds this threshold. The valid range of this object is 0 to 1000. A value of 0 will cause a trap to be sent on
each occurrence of a HEC error. A value of -9999 disables the threshold check.
The MIB recommended default value for this object is 100.
503
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
5.30.4.1.4
pdnAtmIfConfExtUnknownCellThreshold
The value of this object represents the threshold value for the number of unknown cells in a 15 minutes interval. An
SNMP trap would be generated if the number of unknown cell in a 15 minutes interval exceeds this threshold. The
valid range of this object is 0 to 1000. A value of 0 will cause a trap to be sent on each occurrence of an unknown cell.
A value of -9999 disables the threshold check.
The MIB recommended default value for this object is 10.
5.30.4.1.5
pdnAtmIfConfExtOcdEventThreshold
The value of this object represents the threshold value for the number of Out of Cell Delineation(OCD) events in a 15
minutes interval. An SNMP trap would be generated if the number of OCD events in a 15 minutes interval exceeds
this threshold. The valid range of this object is 0 to 1000. A value of 0 will cause a trap to be sent on each occurrence
of a HEC error. A value of -9999 disables the threshold check.
The MIB recommended default value for this object is 0.
5.30.4.1.6
pdnAtmIfConfExtBandwidthUtilCbrReserved
This object specifies the percent of the interface bandwidth to be allocated to the CBR traffic class.
5.30.4.1.7
pdnAtmIfConfExtBandwidthUtilCbrAssigned
This object specifies the percent of bandwidth utilization (sometimes referred to as over subscription) the connection
Admission Control algorithm has already allowed for the CBR class of service.
5.30.4.1.8
pdnAtmIfConfExtBandwidthUtilVbrRtReserved
This object specifies the percent of the interface bandwidth to be allocated to the VBR-rt traffic class.
5.30.4.1.9
pdnAtmIfConfExtBandwidthUtilVbrRtAssigned
This object specifies the percent of bandwidth utilization (sometimes referred to as over subscription) the connection
Admission Control algorithm has already allowed for the VBR-rt class of service.
5.30.4.1.10 pdnAtmIfConfExtBandwidthUtilVbrNrtReserved
This object specifies the percent of the interface bandwidth to be allocated to the VBR-nrt traffic class.
5.30.4.1.11 pdnAtmIfConfExtBandwidthUtilVbrNrtAssigned
This object specifies the percent of bandwidth utilization (sometimes referred to as over subscription) the connection
Admission Control algorithm has already allowed for the VBR-nrt class of service.
5.30.4.1.12 pdnAtmIfConfExtBandwidthUtilUbrReserved
This object specifies the percent of the interface bandwidth to be allocated to the UBR traffic class.
5.30.4.1.13 pdnAtmIfConfExtBandwidthUtilUbrAssigned
This object specifies the percent of bandwidth utilization (sometimes referred to as over subscription) the connection
Admission Control algorithm has already allowed for the UBR class of service.
5.30.4.1.14 pdnAtmIfConfExtRateShape
This object is used to specify rate shaping on this interface in units of kbps. The valid range of this object is 512 to
46080 [512K…46Mbps] with increments of 64K. The default value is set depending on the interface.
504
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
5.30.4.2
pdnAtmTrafficDescrParamExtTable
The Paradyne Extension to the atmTrafficDescrParamTable of the ATM-MIB.
Augments:
•
atmTrafficDescrParamTable (Section 5.15.4.4, Page 323)
Index(es):
•
atmTrafficDescrParamIndex (Section 5.15.4.4.1, Page 324)
OIDs:
•
•
pdnAtmTrafficDescrParamExtTable - { pdnAtmExtMIB 2 }
pdnAtmTrafficDescrParamExtEntry - { pdnAtmTrafficDescrParamExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.5.2
1.3.6.1.4.1.1795.2.24.2.6.11.5.2.1
Table 294: pdnAtmTrafficDescrParamExtTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmTrafficDescrParamName
{ pdnAtmTrafficDescrParamExtEntry 1 }
DisplayString
(SIZE(1…12))
read-create
current
N
pdnAtmTrafficPolicing
{ pdnAtmTrafficDescrParamExtEntry 2 }
TruthValue
read-create
current
N
5.30.4.2.1
pdnAtmTrafficDescrParamName
The value of this Object identifies the traffic descriptor by a by a name.
5.30.4.2.2
pdnAtmTrafficPolicing
The value of this Object determines whether or not the vcl/vpl to which this traffic descriptor is bound will be policed.
5.30.4.3
pdnAal5VccExtTable
The Paradyne Extension to the aal5VccTable in the ATM-MIB.
Augments:
•
aal5VccTable (Section 5.15.4.11, Page 341)
Index(es):
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
aal5VccVpi
aal5VccVci
505
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
OIDs:
•
•
pdnAal5VccExtTable
pdnAal5VccExtEntry
- { pdnAtmExtMIB 3 }
- { pdnAal5VccExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.5.3
1.3.6.1.4.1.1795.2.24.2.6.11.5.3.1
Table 295: pdnAal5VccExtTable
Object
OID
Syntax
Access
Status
Supported
pdnAal5VccExtOutPDUs
{ pdnAal5VccExtEntry 1 }
Unsigned32
read-only
current
Y
pdnAal5VccExtInPDUs
{ pdnAal5VccExtEntry 2 }
Unsigned32
read-only
current
Y
5.30.4.3.1
pdnAal5VccExtOutPDUs
The total number of AAL5 CPCS PDUs transmitted on the interface associated with an AAL5 entry.
5.30.4.3.2
pdnAal5VccExtInPDUs
This total number of AAL5 CPCS PDUs transmitted on the interface associated with an AAL5 entry.
5.30.5
Traps
This section defines the traps generated.
OIDs:
•
pdnAtmExtMIBTraps
- { pdnAtmExtMIB 2 }
1.3.6.1.4.1.1795.2.24.2.6.11.5.2
Table 296: ADSL-ATMEXT-MIB Traps (1 of 2)
Notification
OID
Variable Bindings / Objects
Status
Supported
pdnAtmIfConfExt
ExcessInvalidCellsAlarm
{ pdnAtmExtMIBTrapPrefix 1 }
ifOperStatus
pdnAtmIfConfExtUnknownCellThreshold
current
N
pdnAtmIfConfExt
EgressLineRateAlarmSet
{ pdnAtmExtMIBTrapPrefix 2 }
ifIndex
current
N
pdnAtmIfConfExt
EgressLineRateAlarmClear
{ pdnAtmExtMIBTrapPrefix 102 }
ifIndex
current
N
pdnAtmIfConfExt
VplNoBandwidthAvail
{ pdnAtmExtMIBTrapPrefix 3 }
atmVpCrossConnectAdminStatus
current
N
pdnAtmIfConfExt
VclNoBandwidthAvail
{ pdnAtmExtMIBTrapPrefix 4 }
atmVcCrossConnectAdminStatus
current
N
506
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
Table 296: ADSL-ATMEXT-MIB Traps (2 of 2)
Notification
OID
Variable Bindings / Objects
Status
Supported
pdnAtmIfConfExt
IngressLineRateAlarmSet
{ pdnAtmExtMIBTrapPrefix 5 }
ifIndex
current
N
pdnAtmIfConfExt
IngressLineRateAlarmClear
{ pdnAtmExtMIBTrapPrefix 105 }
ifIndex
current
N
5.30.5.1
pdnAtmIfConfExtExcessInvalidCellsAlarm
This alarm indicates that the number of cells with uncorrectable HEC errors has exceeded the used defined the
threshold.
5.30.5.2
pdnAtmIfConfExtEgressLineRateAlarmSet
This alarm indicates that the line rate of the specified interface has dropped below a value which violates the traffic
contracts of the admitted connections in the egress (transmit) direction.
5.30.5.3
pdnAtmIfConfExtEgressLineRateAlarmClear
This alarm indicates that the line rate of the specified interface has risen above a value which would no longer violate
the traffic contracts of the admitted connections in the egress (transmit) direction.
5.30.5.4
pdnAtmIfConfExtVplNoBandwidthAvail
This alarm indicates that the traffic contract(s) associated with the Virtual Path (VP) Cross Connect cannot be
satisfied by the ATM switch. It is left up to the implementation to decide whether or not the VP cross connect will be
admitted.
5.30.5.5
pdnAtmIfConfExtVclNoBandwidthAvail
This alarm indicates that the traffic contract(s) associated with the Virtual Channel (VC) Cross Connect cannot be
satisfied by the ATM switch. It is left up to the implementation to decide whether or not the VC cross connect will be
admitted.
5.30.5.6
pdnAtmIfConfExtIngressLineRateAlarmSet
This alarm indicates that the line rate of the specified interface has dropped below a value which violates the traffic
contracts of the admitted connections in the ingress (receive) direction.
5.30.5.7
pdnAtmIfConfExtIngressLineRateAlarmClear
This alarm indicates that the line rate of the specified interface has risen above a value which would no longer violate
the traffic contracts of the admitted connections in the ingress (receive) direction.
507
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
5.30.6
Conformance Information
5.30.7
Compliance
No compliance statements were defined nor were any mandatory objects specified.
5.30.8
Conformance
Table 297: ADSL-ATMEXT-MIB Conformance (1 of 2)
Group
Description
Objects
Supported
pdnAtmIfConfExtGroup
Objects grouped for the pdnAtmIfConfExtTable.
pdnAtmIfConfExtVbrRtBandwidthUtil
N
pdnAtmIfConfExtVbrNrtBandwidthUtil
N
pdnAtmIfConfExtHecErrorThreshold
N
pdnAtmIfConfExtUnknownCellThreshold
N
pdnAtmIfConfExtOcdEventThreshold
N
pdnAtmIfConfExtBandwidthUtilCbrReserved
N
pdnAtmIfConfExtBandwidthUtilCbrAssigned
N
pdnAtmIfConfExtBandwidthUtilVbrRtReserved
N
pdnAtmIfConfExtBandwidthUtilVbrRtAssigned
N
pdnAtmIfConfExtBandwidthUtilVbrNrtReserved
N
pdnAtmIfConfExtBandwidthUtilVbrNrtAssigned
N
pdnAtmIfConfExtBandwidthUtilUbrReserved
N
pdnAtmIfConfExtBandwidthUtilUbrAssigned
N
pdnAtmIfConfExtRateShape
N
pdnAtmTrafficDescrParamsExtGroup
Objects grouped for the pdnAtmTrafficDescrParamExtTable
pdnAtmTrafficDescrParamName
N
pdnAtmTrafficPolicing
Y
pdnAal5VccExtGroup
Objects grouped for the
pdnAal5VccExtTable.
pdnAal5VccExtInPDUs
Y
pdnAal5VccExtOutPDUs
N
508
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMEXT-MIB — pdn_AtmExt.mib
Table 297: ADSL-ATMEXT-MIB Conformance (2 of 2)
Group
Description
Objects
Supported
pdnAtmExtNotificationGroup
Objects grouped for Notification
defined in this MIB.
pdnAtmIfConfExtExcessInvalidCellsAlarm
N
pdnAtmIfConfExtEgressLineRateAlarmSet
N
pdnAtmIfConfExtEgressLineRateAlarmClear
N
pdnAtmIfConfExtVplNoBandwidthAvail
N
pdnAtmIfConfExtVclNoBandwidthAvail
N
pdnAtmIfConfExtIngressLineRateAlarmSet
N
pdnAtmIfConfExtIngressLineRateAlarmClear
N
509
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31 PDN-ATMM4EXT-MIB
5.31.1
Introduction
This MIB Module extends the ATM-FORUM-SNMP-M4-MI defined in af-nm-0095.001.
The revision of the MIB that this SNMP Operational Specification aligns with is that which has a LAST-UPDATED
of “200103080000Z,” or March 8, 2001.
5.31.2
Textual Conventions
The following textual conventions are made in the reference document:
•
5.31.3
•
•
•
•
•
•
•
PdnAtmfM4TestErrorCode
- The specific error codes related to attempting to run a test.
—
Syntax
INTEGER
• noError(0)
- No Error Occurred
• badIfIndex(1)
- Specified interface does not exist
• noVccFound(2)
- The Vcc does not exist on the interface
• notOwner(3)
- Not the current owner of the test
• noResourceAvailable(4)
- Device memory allocation failure
• noLoopbackAllocated(5)
- Could not start the test
• testCompleted(6)
- Test completed or stopped normally
• testTimeOut(7)
- Test unsuccessfully due to timeout
• adminStatusDisabled(8)
- ifAdminStatus is Disabled
• noVpFound(9)
- The Vp does not exist on the interface
OIDs
iso
org
dod
internet
mgmt
private
enterprises
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 2 }
{ internet 4 }
{ private 1 }
1
1.3
1.3.6
1.3.6.1
1.3.6.1.2
1.3.6.1.4
1.3.6.1.4.1
•
•
•
•
•
pdyn
pdn-mgmt
paradyne
pdn-common
pdn-interfaces
-
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
{ pdn-common 6 }
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
1.3.6.1.4.1.1795.2.24.2.6
•
•
•
•
•
•
pdnAtm
pdnAtmfM4ExtMIB
pdnAtmfM4ExtObjects
pdnAtmfM4ExtTraps
pdnAtmfM4ExtTrapPrefix
pdnAtmfM4ExtConformance
-
{ pdn-interfaces 11 }
{ pdnAtm 6 }
{ pdnAtmExtMIB 1 }
{ pdnAtmExtMIB 2 }
{ pdnAtmExtMIBTraps 0 }
{ pdnAtmExtMIB 3 }
510
1.3.6.1.4.1.1795.2.24.2.6.11
1.3.6.1.4.1.1795.2.24.2.6.11.6
1.3.6.1.4.1.1795.2.24.2.6.11.6.1
1.3.6.1.4.1.1795.2.24.2.6.11.6.2
1.3.6.1.4.1.1795.2.24.2.6.11.6.2.0
1.3.6.1.4.1.1795.2.24.2.6.11.6.3
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31.4
MIB Objects
Table 298: PDN-ATMM4EXT-MIB Objects
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4TcProtoCurrExtTable
{ pdnAtmM4ExtMIBObjects 1 }
SEQUENCE OF
pdnAtmfM4TcProtoCurrExtEntry
not-accessible
current
Y
pdnAtmfM4TcProtoHistExtTable
{ pdnAtmM4ExtMIBObjects 2 }
SEQUENCE OF
pdnAtmfM4TcProtoHistExtEntry
not-accessible
current
Y
pdnAtmfM4TestTypes
{ pdnAtmM4ExtMIBObjects 3 }
OID
not-accessible
current
N
pdnAtmfM4VcLoopbackTestTable
{ pdnAtmM4ExtMIBObjects 4 }
SEQUENCE OF
pdnAtmM4VcLoopbackTestEntry
not-accessible
current
N
pdnAtmfM4VclCellLoopbackTable
{ pdnAtmM4ExtMIBObjects 5 }
SEQUENCE OF
pdnAtmfM4VclCellLoopbackEntry
not-accessible
current
N
pdnAtmfM4LoopbackLocationTable
{ pdnAtmM4ExtMIBObjects 6 }
SEQUENCE OF
pdnAtmfM4LoopbackLocationEntry
not-accessible
current
N
pdnAtmfM4VpLoopbackTestTable
{ pdnAtmM4ExtMIBObjects 7 }
SEQUENCE OF
pdnAtmfM4VpLoopbackTestEntry
not-accessible
current
N
5.31.4.1
pdnAtmfM4TcProtoCurrExtTable
The Paradyne Extension to the atmfM4TcProtoCurrTable of the ATM-FORUM-SNMP-M4-MIB containing ATM
TC layer current fifteen-minute interval data statistics.
Augments:
•
atmfM4TcProtoCurrTable
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pdnAtmfM4TcProtoCurrExtTable - { pdnAtmfM4ExtObjects 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.1
pdnAtmfM4TcProtoCurrExtEntry - { pdnAtmfM4TcProtoCurrExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.1.1
511
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
Table 299: pdnAtmfM4TcProtoCurrExtTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4TcProtoCurrCellIns
{ pdnAtmfM4TcProtoCurrExtEntry 1 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoCurrCellOuts
{ pdnAtmfM4TcProtoCurrExtEntry 2 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoCurrInDiscards
{ pdnAtmfM4TcProtoCurrExtEntry 3 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoCurrOutDiscards
{ pdnAtmfM4TcProtoCurrExtEntry 4 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoCurrLCDEvents
{ pdnAtmfM4TcProtoCurrExtEntry 5 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoCurrUnknownCells
{ pdnAtmfM4TcProtoCurrExtEntry 6 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoCurrCorrectedHEC
{ pdnAtmfM4TcProtoCurrExtEntry 7 }
Gauge32
read-only
current
Y
5.31.4.1.1
pdnAtmfM4TcProtoCurrCellIns
The number of ATM cells received on this interface since the start of this interval.
5.31.4.1.2
pdnAtmfM4TcProtoCurrCellOuts
The number of ATM cells sent on this interface since the start of this interval.
5.31.4.1.3
pdnAtmfM4TcProtoCurrInDiscards
The number of RX ATM cells dropped on this interface since the start of this interval.
5.31.4.1.4
pdnAtmfM4TcProtoCurrOutDiscards
The number of TX ATM cells dropped on this interface since the start of this interval.
5.31.4.1.5
pdnAtmfM4TcProtoCurrLCDEvents
The number of Loss of Cell Delineation (LCD) event occurred on this interface since the start of this interval.
5.31.4.1.6
pdnAtmfM4TcProtoCurrUnknownCells
The number of unknown Cells received on this interface since the start of this interval.
5.31.4.1.7
pdnAtmfM4TcProtoCurrCorrectedHEC
The number of Cell with corrected HEC received on this interface since the start of this interval.
5.31.4.2
pdnAtmfM4TcProtoHistExtTable
The Paradyne Extension to the atmfM4TcProtoHistTable of the ATM-FORUM-SNMP-M4-MIB contining ATM TC
layer historical fifteen-minute interval statistics.
512
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
Augments:
•
atmfM4TcProtoHistTable
Index(es):
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmfM4CellProtoHistIndex
OIDs:
•
•
pdnAtmfM4TcProtoHistExtTable - { pdnAtmfM4ExtObjects 2 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.2
pdnAtmfM4TcProtoHistExtEntry - { pdnAtmfM4TcProtoHistExtTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.2.1
Table 300: pdnAtmfM4TcProtoHistExtTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4TcProtoHistCellIns
{ pdnAtmfM4TcProtoHistExtEntry 1 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoHistCellOuts
{ pdnAtmfM4TcProtoHistExtEntry 2 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoHistInDiscards
{ pdnAtmfM4TcProtoHistExtEntry 3 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoHistOutDiscards
{ pdnAtmfM4TcProtoHistExtEntry 4 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoHistLCDEvents
{ pdnAtmfM4TcProtoHistExtEntry 5 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoHistUnknownCells
{ pdnAtmfM4TcProtoHistExtEntry 6 }
Gauge32
read-only
current
Y
pdnAtmfM4TcProtoHistCorrectedHEC
{ pdnAtmfM4TcProtoHistExtEntry 7 }
Gauge32
read-only
current
Y
5.31.4.2.1
pdnAtmfM4TcProtoHistCellIns
The number of ATM cells received on this interface during this interval.
5.31.4.2.2
pdnAtmfM4TcProtoHistCellOuts
The number of ATM cells sent on this interface during this interval.
5.31.4.2.3
pdnAtmfM4TcProtoHistInDiscards
The number of RX ATM cells dropped on this interface during this interval.
5.31.4.2.4
pdnAtmfM4TcProtoHistOutDiscards
The number of TX ATM cells dropped on this interface during this interval.
5.31.4.2.5
pdnAtmfM4TcProtoHistLCDEvents
The number of Loss of Cell Delineation (LCD) event occurred on this interface during this interval.
513
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31.4.2.6
pdnAtmfM4TcProtoHistUnknownCells
The number of unknown Cells received on this interface since the start of this interval.
5.31.4.2.7
pdnAtmfM4TcProtoHistCorrectedHEC
The number of Cell with corrected HEC received on this interface during this interval.
5.31.4.3 pdnAtmfM4TestTypes
• pdnAtmfM4TestTypes
1.3.6.1.4.1.1795.2.24.2.6.11.6.1.3
• pdnAtmfM4TestOAMLoopbackSegMultiCell
1.3.6.1.4.1.1795.2.24.2.6.11.6.1.3.1
• pdnAtmfM4TestOAMLoopbackE2EMultiCell
1.3.6.1.4.1.1795.2.24.2.6.11.6.1.3.2
- { pdnAtmfM4ExtObjects 3 }
- { pdnAtmfM4TestTypes 1 }
- { pdnAtmfM4TestTypes 2 }
Table 301: pdnAtmM4 Test Code to Test Results Matrix
atmfM4VcTestType
atmfM4VcTestCode Results
atmfM4TestOAMLoopbackSeg (standard is a single cell test)
pdnAtmfM4VclCellLoopTable
atmfM4TestOAMLoopbackE2E (standard is a single cell test)
pdnAtmfM4VclCellLoopTable
pdnAtmfM4TestOAMLoopbackSegMultiCell
pdnAtmfM4VcLoopbackTestTable
pdnAtmfM4TestOAMLoopbackE2EMultiCell
pdnAtmfM4VcLoopbackTestTable
5.31.4.3.1
pdnAtmfM4TestOAMLoopbackSegMultiCell
This identifies an OID for OAM Loopback Test on a VPL, VPC, VCL, or VCC termination point, using a segment
OAM cell.
The test type must have appended to it a code that uniquely identifies an intermediate point responsible for looping
back the cell. If this is absent, the loopback is performed at the end of the segment or connection.
E.g., the OID { pdnAtmfM4TestOAMLoopbackSegMultiCell 5 } identifies that the loopback should be performed at
the intermediate point labeled 5.
5.31.4.3.2
pdnAtmfM4TestOAMLoopbackE2EMultiCell
This identifies an OAM Loopback Test on a VPL, VPC, VCL, or VCC termination point, using an end-to-end OAM
cell.
5.31.4.4
pdnAtmfM4VcLoopbackTestTable
This table contains input and results for OAM loopback tests. There can be only one test running per ATM VCC This
table should be used in conjunction with atmfM4VcTestTablewith all the semantics of atmfM4VcTestTable.
514
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
Augments:
•
atmfM4VcTestTable
Index(es):
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVclVpi
atmVclVci
atmfM4VcTestObject
OIDs:
•
•
pdnAtmfM4VcLoopbackTestTable - { pdnAtmfM4ExtObjects 4 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.4
pdnAtmfM4VcLoopbackTestEntry - { pdnAtmfM4VcLoopbackTestTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.4.1
Table 302: pdnAtmfM4VcLoopbackTestTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4VcLoopbackTestElpsTime
{ pdnAtmfM4VcLoopbackTestEntry 1 }
TimeTicks
read-only
current
N
pdnAtmfM4VcLoopbackTestCellsSent
{ pdnAtmfM4VcLoopbackTestEntry 2 }
Gauge32
read-only
current
N
pdnAtmfM4VcLoopbackTestCellsRcvd
{ pdnAtmfM4VcLoopbackTestEntry 3 }
Gauge32
read-only
current
N
pdnAtmfM4VcLoopbackTestMinRTDelay
{ pdnAtmfM4VcLoopbackTestEntry 4 }
Gauge32
read-only
current
N
pdnAtmfM4VcLoopbackTestMaxRTDelay
{ pdnAtmfM4VcLoopbackTestEntry 5 }
Gauge32
read-only
current
N
pdnAtmfM4VcLoopbackTestAvgRTDelay
{ pdnAtmfM4VcLoopbackTestEntry 6 }
Gauge32
read-only
current
N
pdnAtmfM4VcLoopbackTestErrorCode
{ pdnAtmfM4VcLoopbackTestEntry 7 }
PdnAtmfM4TestErrorCode
read-only
current
N
5.31.4.4.1
pdnAtmfM4VcLoopbackTestElpsTime
This object contains the time that has elapsed since the test started.
5.31.4.4.2
pdnAtmfM4VcLoopbackTestCellsSent
This object specifies a count of the number of test cells that have been sent. The value of this object stops increasing
when it reaches its maximum value.
515
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31.4.4.3
pdnAtmfM4VcLoopbackTestCellsRcvd
This object specifies a count of the number of test cells that have been received. The value of this object stops
increasing when it reaches its maximum value.
5.31.4.4.4
pdnAtmfM4VcLoopbackTestMinRTDelay
This object contains the value of the shortest round trip delay, in milliseconds, since the test has been started. It is
calculated only on the cells that have been received. Cells that were dropped are not counted.
5.31.4.4.5
pdnAtmfM4VcLoopbackTestMaxRTDelay
This object contains the value of the longest round trip delay, in milliseconds, since the test has been started. It is
calculated only on the cells that have been received. Cells that were dropped are not counted.
5.31.4.4.6
pdnAtmfM4VcLoopbackTestAvgRTDelay
This object contains the value of the average round trip delay, milliseconds, since the test has been started. It is
calculated only on the cells that have been received. Cells that were dropped are not counted.
5.31.4.4.7
pdnAtmfM4VcLoopbackTestErrorCode
This object contains the specific error code on the test result.
5.31.4.5
pdnAtmfM4Vc1CellLoopTable
This table contains input and results for single cell OAMloopback tests. There can be only one test running per ATM
VCC This table should be used in conjunction with atmfM4VcTestTablewith all the semantics of
atmfM4VcTestTable. Each entry contains objects for test results for a single cell ATM OAM loopback test.
This table contains results for single cell OAM tests that are not of a broadcast variety. Recommended Use:
1.
2.
3.
The NMS will start a test using the M4 MIB's atmfM4VcTestTable.
Upon starting the test, the agent will put the corresponding OID of a row in this table into the
atmfM4VcTestCode object.
When the value of atmfM4VcTestResult is not equal to inProgress(3), the values contained in this table
should be read.
Augments:
•
atmfM4VcTestEntry
Index(es):
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVclVpi
atmVclVci
atmfM4VcTestObject
OIDs:
•
•
pdnAtmfM4Vc1CellLoopTable
- { pdnAtmfM4ExtObjects 5 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.5
pdnAtmfM4Vc1CellLoopEntry
- { pdnAtmfM4Vc1CellLoopTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.6.5.1
516
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
Table 303: pdnAtmfM4Vc1CellLoopTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4Vc1CellLoopRTDelay
{ pdnAtmfM4Vc1CellLoopEntry 1 }
Gauge32
read-only
current
N
pdnAtmfM4Vc1CellLoopReportedLocation
{ pdnAtmfM4Vc1CellLoopEntry 2 }
OCTET STRING(SIZE(16))
read-only
current
N
pdnAtmfM4Vc1CellLoopErrorCode
{ pdnAtmfM4Vc1CellLoopEntry 3 }
PdnAtmfM4TestErrorCode
read-only
current
N
5.31.4.5.1
pdnAtmfM4Vc1CellLoopRTDelay
This object contains the value of the round trip delay, in milliseconds, of the test cell. A value of zero indicates that no
cell has been received.
5.31.4.5.2
pdnAtmfM4Vc1CellLoopReportedLocation
This object contains the value of the location identifier reported by the received cell.
5.31.4.5.3
pdnAtmfM4Vc1CellLoopErrorCode
This object contains the specific error code on the test result.
5.31.4.6
pdnAtmfM4LoopbackLocationTable
This table contains the ATM OAM loopback location codes for ATM cell layer interfaces.
Index(es):
•
ifIndex (Section 5.3.4.3.1, Page 39)
OIDs:
•
•
pdnAtmfM4LoopbackLocationTable
1.3.6.1.4.1.1795.2.24.2.6.11.6.6
pdnAtmfM4LoopbackLocationEntry
1.3.6.1.4.1.1795.2.24.2.6.11.6.6.1
- { pdnAtmfM4ExtObjects 6 }
- { pdnAtmfM4LoopbackLocationTable 1 }
Table 304: pdnAtmfM4LoopbackLocationTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4LoopbackLocationCode
{ pdnAtmfM4LoopbackLocationEntry 1 }
OCTET STRING(SIZE(16))
read-write
current
N
517
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31.4.7
pdnAtmfM4LoopbackLocationCode
This object contains the value of ATM OAM Loopback Location Code.
5.31.4.8
pdnAtmfM4VpLoopbackTestTable
This table contains input and results for OAM loopback tests. There can be only one test running per ATM VPC. This
table should be used in conjunction with atmfM4VpTestTablewith all the semantics of atmfM4VpTestTable. Each
entry contains objects for test results for ATM OAM loopback test.
Augments:
•
atmfM4VpTestTable
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVplVpi
atmfM4VpTestObject
OIDs:
•
•
pdnAtmfM4VpLoopbackTestTable
1.3.6.1.4.1.1795.2.24.2.6.11.6.7
pdnAtmfM4VpLoopbackTestEntry
1.3.6.1.4.1.1795.2.24.2.6.11.6.7.1
- { pdnAtmfM4ExtObjects 7 }
- { pdnAtmfM4VpLoopbackTestTable 1 }
Table 305: pdnAtmfM4VpLoopbackTestTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmfM4VpLoopbackTestElpsTime
{ pdnAtmfM4VpLoopbackTestEntry 1 }
TimeTicks
read-only
current
N
pdnAtmfM4VpLoopbackTestCellsSent
{ pdnAtmfM4VpLoopbackTestEntry 2 }
Gauge32
read-only
current
N
pdnAtmfM4VpLoopbackTestCellsRcvd
{ pdnAtmfM4VpLoopbackTestEntry 3 }
Gauge32
read-only
current
N
pdnAtmfM4VpLoopbackTestMinRTDelay
{ pdnAtmfM4VpLoopbackTestEntry 4 }
Gauge32
read-only
current
N
pdnAtmfM4VpLoopbackTestMaxRTDelay
{ pdnAtmfM4VpLoopbackTestEntry 5 }
Gauge32
read-only
current
N
pdnAtmfM4VpLoopbackTestAvgRTDelay
{ pdnAtmfM4VpLoopbackTestEntry 6 }
Gauge32
read-only
current
N
pdnAtmfM4VpLoopbackTestErrorCode
{ pdnAtmfM4VpLoopbackTestEntry 7 }
PdnAtmfM4TestErrorCode
read-only
current
N
518
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31.4.8.1
pdnAtmfM4VpLoopbackTestElpsTime
This object contains the time that has elapsed since the test started.
5.31.4.8.2
pdnAtmfM4VpLoopbackTestCellsSent
This object specifies a count of the number of test cells that have been sent. The value of this object stops increasing
when it reaches its maximum value.
5.31.4.8.3
pdnAtmfM4VpLoopbackTestCellsRcvd
This object specifies a count of the number of test cells that have been received. The value of this object stops
increasing when it reaches its maximum value.
5.31.4.8.4
pdnAtmfM4VpLoopbackTestMinRTDelay
This object contains the value of the shortest round trip delay, in milliseconds, since the test has been started. It is
calculated only on the cells that have been received. Cells that were dropped are not counted.
5.31.4.8.5
pdnAtmfM4VpLoopbackTestMaxRTDelay
This object contains the value of the longest round trip delay, in milliseconds, since the test has been started. It is
calculated only on the cells that have been received. Cells that were dropped are not counted.
5.31.4.8.6
pdnAtmfM4VpLoopbackTestAvgRTDelay
This object contains the value of the average round trip delay, in milliseconds, since the test has been started. It is
calculated only on the cells that have been received. Cells that were dropped are not counted.
5.31.4.8.7
pdnAtmfM4VpLoopbackTestErrorCode
This object contains the specific error code on the test result.
519
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
5.31.5
Conformance Information
5.31.5.1
5.31.5.1.1
Compliance
pdnAtmfM4Complaince
The compliance statement for SNMP entities which support the ATM M4 extensions.
No mandatory groups are specified.
5.31.5.2
Conformance
Table 306: PDN-ATMM4EXT-MIB Conformance (1 of 2)
Group
Description
Objects
Supported
pdnAtmfM4TcCurrGroup
The objects in the ATM TC layer
current table.
pdnAtmfM4TcProtoCurrCellIns
Y
pdnAtmfM4TcProtoCurrCellOuts
Y
pdnAtmfM4TcProtoCurrInDiscards
Y
pdnAtmfM4TcProtoCurrOutDiscards
Y
pdnAtmfM4TcProtoCurrLCDEvents
Y
pdnAtmfM4TcProtoCurrUnknownCells
Y
pdnAtmfM4TcProtoCurrCorrectedHEC
Y
pdnAtmfM4TcProtoHistCellIns
Y
pdnAtmfM4TcProtoHistCellOuts
Y
pdnAtmfM4TcProtoHistInDiscards
Y
pdnAtmfM4TcProtoHistOutDiscards
Y
pdnAtmfM4TcProtoHistLCDEvents
Y
pdnAtmfM4TcProtoHistUnknownCells
Y
pdnAtmfM4TcProtoHistCorrectedHEC
Y
pdnAtmfM4TcHistGroup
The objects in the ATM TC layer
history table.
520
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMM4EXT-MIB — pdn_AtmM4Ext.mib
Table 306: PDN-ATMM4EXT-MIB Conformance (2 of 2)
Group
Description
Objects
Supported
pdnAtmfM4VcLoopbackTestGroup
The objects in the ATM OAM
Loopback Test (multiple cell) table
for ATM VCC.
pdnAtmfM4VcLoopbackTestElpsTime
N
pdnAtmfM4VcLoopbackTestCellsSent
N
pdnAtmfM4VcLoopbackTestCellsRcvd
N
pdnAtmfM4VcLoopbackTestMinRTDelay
N
pdnAtmfM4VcLoopbackTestMaxRTDelay
N
pdnAtmfM4VcLoopbackTestAvgRTDelay
N
pdnAtmfM4VcLoopbackTestErrorCode
N
pdnAtmfM4Vc1CellLoopRTDelay
N
pdnAtmfM4Vc1CellLoopReportedLocation
N
pdnAtmfM4Vc1CellLoopErrorCode
N
pdnAtmfM4LoopbackLocationCode
N
pdnAtmfM4VpLoopbackTestElpsTime
N
pdnAtmfM4VpLoopbackTestCellsSent
N
pdnAtmfM4VpLoopbackTestCellsRcvd
N
pdnAtmfM4VpLoopbackTestMinRTDelay
N
pdnAtmfM4VpLoopbackTestMaxRTDelay
N
pdnAtmfM4VpLoopbackTestAvgRTDelay
N
pdnAtmfM4VpLoopbackTestErrorCode
N
pdnAtmfM4VclLoopGroup
The objects in the ATM Single Cell
OAM Loopback Test table.
pdnAtmfM4LoopbackLocationGroup
The objects in the ATM Loopback
Location table.
pdnAtmfM4VpLoopbackTestGroup
The objects in the ATM OAM
Loopback Test (multiple cell) table
for ATM VPC.
521
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
5.32 PDN-ATMSTATS-MIB
5.32.1
Introduction
This MIB Module supports ATM Statistics.
The version of the MIB used for this document had a LAST-UPDATED of 0004130000Z which decodes to April 13,
2000.
5.32.2
Textual Conventions
No “special” textual conventions are made or referenced in this MIB.
5.32.3
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
5.32.4
OIDs
iso
org
dod
internet
private
enterprises
pdyn
pdn-mgmt
paradyne
pdn-common
-
{1}
{ iso 3 }
{ org 6 }
{ dod 1 }
{ internet 4 }
{ private 1 }
{ enterprises 1795 }
{ pdyn 2 }
{ pdn-mgmt 24 }
{ paradyne 2 }
pdn-interfaces
pdnAtm
pdnAtmStatsMIB
pdnAtmVplStat
pdnAtmVclStat
pdnAtmStat
-
1
1.3
1.3.6
1.3.6.1
1.3.6.1.4
1.3.6.1.4.1
1.3.6.1.4.1.1795
1.3.6.1.4.1.1795.2
1.3.6.1.4.1.1795.2.24
1.3.6.1.4.1.1795.2.24.2
{ pdn-common 6 }
{ pdn-interfaces 11 }
{ pdnAtm 3 }
{ pdnAtmStatsMIB 1 }
{ pdnAtmStatsMIB 2 }
{ pdnAtmStatsMIB 3 }
1.3.6.1.4.1.1795.2.24.2.6
1.3.6.1.4.1.1795.2.24.2.6.11
1.3.6.1.4.1.1795.2.24.2.6.11.3
1.3.6.1.4.1.1795.2.24.2.6.11.3.1
1.3.6.1.4.1.1795.2.24.2.6.11.3.2
1.3.6.1.4.1.1795.2.24.2.6.11.3.3
MIB Objects
Table 307: PDN-ATMSTATS-MIB Objects
Object
OID
Description
Supported
pdnAtmVplStat
{ pdnAtmStatsMIB 1 }
ATM VPL Statistics
N
pdnAtmVclStat
{ pdnAtmStatsMIB 2 }
ATM VCL Statistics
Y
pdnAtmStat
{ pdnAtmStatsMIB 3 }
ATM Statistics
Y
5.32.4.1
pdnAtmVplStat
This group consists of VPL statistics.
522
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
OIDs:
•
pdnAtmVplStat
- { pdnAtmStatsMIB 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.3.1
Table 308: pdnAtmVplStat
Object
OID
Syntax
Access
Status
Supported
pdnAtmVplStatTable
{ pdnAtmVplStat 1 }
SEQUENCE OF
pdnAtmVplStatEntry
not-accessible
current
N
5.32.4.1.1
pdnAtmVplStatTable
This table contains all statistic counters per VPL. It is used to monitor the usage of the VPL in terms of incoming
cells and outgoing cells. This table is a sequence of pdnAtmVlpStatEntry where each entry in this table represents a
VPL.
Index(es):
•
•
pdnAtmVplStatIfIndex
pdnAtmVplStatVpi
OIDs:
•
•
pdnAtmVplStatTable - { pdnAtmVplStat 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.3.1.1
pdnAtmVplStatEntry - { pdnAtmVplStatTable 1 } 1.3.6.1.4.1.1795.2.24.2.6.11.3.1.1.1
Table 309: pdnAtmVplStatTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmVplStatIfIndex
{ pdnAtmVplStatEntry 1 }
Integer32
read-only
current
N
pdnAtmVplStatVpi
{ pdnAtmVplStatEntry 2 }
Integer32
read-only
current
N
pdnAtmVplStatTotalCellIns
{ pdnAtmVplStatEntry 3 }
Counter32
read-only
current
N
pdnAtmVplStatClp0CellIns
{ pdnAtmVplStatEntry 4 }
Counter32
read-only
current
N
pdnAtmVplStatTotalDiscards
{ pdnAtmVplStatEntry 5 }
Counter32
read-only
current
N
pdnAtmVplStatClp0Discards
{ pdnAtmVplStatEntry 6 }
Counter32
read-only
current
N
pdnAtmVplStatTotalCellOuts
{ pdnAtmVplStatEntry 7 }
Counter32
read-only
current
N
pdnAtmVplStatClp0CellOuts
{ pdnAtmVplStatEntry 8 }
Counter32
read-only
current
N
pdnAtmVplStatTaggedOuts
{ pdnAtmVplStatEntry 9 }
Counter32
read-only
current
N
523
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
5.32.4.1.1.1
pdnAtmVplStatIfIndex
A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface
must remain constant at least from one re-initialization of the entity's network management system to the next
reinitialization.
5.32.4.1.1.2
pdnAtmVplStatVpi
The VPI value of the VPL.
5.32.4.1.1.3
pdnAtmVplStatTotalCellIns
The total number of valid ATM cells received by this VPL including both CLP=0 and CLP=1 cells. The cells are
counted prior to the application of the traffic policing.
5.32.4.1.1.4
pdnAtmVplStatClp0CellIns
The number of valid ATM cells received by this VPL with CLP=0. The cells are counted prior to the application of
the traffic policing.
5.32.4.1.1.5
pdnAtmVplStatTotalDiscards
The total number of valid ATM cells discarded by the traffic policing entity. This includes cells originally received
with CLP=0 and CLP=1.
5.32.4.1.1.6
pdnAtmVplStatClp0Discards
The total number of valid ATM cells received with CLP=0 an discarded by the traffic policing entity.
5.32.4.1.1.7
pdnAtmVplStatTotalCellOuts
The total number of valid ATM cells transmitted by this VPL. This includes both CLP=0 and CLP=1 cells.
5.32.4.1.1.8
pdnAtmVplStatClp0CellOuts
The total number of valid ATM cells transmitted with CLP=0 by this VPL.
5.32.4.1.1.9
pdnAtmVplStatTaggedOuts
The total number of valid ATM cells tagged by the traffic policing entity from CLP=0 to CLP=1 and transmitted by
this VPL.
5.32.4.2
pdnAtmVclStat
This group consists of Vcl statistics.
OIDs:
•
pdnAtmVclStat - { pdnAtmStatsMIB 2 }
1.3.6.1.4.1.1795.2.24.2.6.11.3.2
Table 310: pdnAtmVclStat (1 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAtmVclStatTable
{ pdnAtmVclStat 2 }
SEQUENCE OF
pdnAtmVclStatEntry
not-accessible
current
N
524
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
Table 310: pdnAtmVclStat (2 of 2)
Object
OID
Syntax
Access
Status
Supported
pdnAtmVclCurrTable
{ pdnAtmVclStat 3 }
SEQUENCE OF
pdnAtmVclCurrEntry
not-accessible
current
N
pdnAtmVclHistTable
{ pdnAtmVclStat 4 }
SEQUENCE OF
pdnAtmVclHistEntry
not-accessible
current
N
5.32.4.2.1
pdnAtmVclStatTable
This table contains all statistic counters per VCL. It is used to monitor the usage of the VCL in terms of incoming
cells and outgoing cells. The table is a sequence of pdnAtmVclStatEntry where each entry in this table represents a
VCL.
Index(es):
•
•
•
pdnAtmVclStatIfIndex
pdnAtmVclStatVpi
pdnAtmVclStatVci
OIDs:
•
•
pdnAtmVclStatTable - { pdnAtmVclStat 2 }
pdnAtmVclStatEntry - { pdnAtmVclStatTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.3.2.2
1.3.6.1.4.1.1795.2.24.2.6.11.3.2.2.1
Table 311: pdnAtmVclStatTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmVclStatIfIndex
{ pdnAtmVclStatEntry 1 }
Integer32
read-only
current
N
pdnAtmVclStatVpi
{ pdnAtmVclStatEntry 2 }
Integer32
read-only
current
N
pdnAtmVclStatVci
{ pdnAtmVclStatEntry 3 }
Integer32
read-only
current
N
pdnAtmVclStatTotalCellIns
{ pdnAtmVclStatEntry 4 }
Counter32
read-only
current
N
pdnAtmVclStatClp0CellIns
{ pdnAtmVclStatEntry 5 }
Counter32
read-only
current
N
pdnAtmVclStatTotalDiscards
{ pdnAtmVplStatEntry 6 }
Counter32
read-only
current
N
pdnAtmVclStatClp0Discards
{ pdnAtmVclStatEntry 7 }
Counter32
read-only
current
N
pdnAtmVclStatTotalCellOuts
{ pdnAtmVclStatEntry 8 }
Counter32
read-only
current
N
pdnAtmVclStatClp0CellOuts
{ pdnAtmVclStatEntry 9 }
Counter32
read-only
current
N
pdnAtmVclStatTaggedOuts
{ pdnAtmVclStatEntry 10 }
Counter32
read-only
current
N
pdnAtmVclStatRowStatus
{ pdnAtmVclStatEntry 11 }
RowStatus
read-write
current
N
525
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
5.32.4.2.1.1
pdnAtmVclStatIfIndex
A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface
must remain constant at least from one re-initialization of the entity's network management system to the next reinitialization.
5.32.4.2.1.2
pdnAtmVclStatVpi
The VPI value of the VCL.
5.32.4.2.1.3
pdnAtmVclStatVci
The VCI value of the VCL.
5.32.4.2.1.4
pdnAtmVclStatTotalCellIns
The total number of valid ATM cells received by this VCL including both CLP=0 and CLP=1 cells. The cells are
counted prior to the application of the traffic policing.
5.32.4.2.1.5
pdnAtmVclStatClp0CellIns
The number of valid ATM cells received by this VCL with CLP=0. The cells are counted prior to the application of
the traffic policing.
5.32.4.2.1.6
pdnAtmVclStatTotalDiscards
The total number of valid ATM cells discarded by the traffic policing entity. This includes cells originally received
with CLP=0 and CLP=1.
5.32.4.2.1.7
pdnAtmVclStatClp0Discards
The total number of valid ATM cells received with CLP=0 an discarded by the traffic policing entity.
5.32.4.2.1.8
pdnAtmVclStatTotalCellOuts
The total number of valid ATM cells transmitted by this VCL. This includes both CLP=0 and CLP=1 cells.
5.32.4.2.1.9
pdnAtmVclStatClp0CellOuts
The total number of valid ATM cells transmitted with CLP=0 by this VCL.
5.32.4.2.1.10
pdnAtmVclStatTaggedOuts
The total number of valid ATM cells tagged by the traffic policing entity from CLP=0 to CLP=1 and transmitted by
this VCL.
5.32.4.2.1.11
pdnAtmVclStatRowStatus
This object is used to create a new row or delete an existing row in this table. When a new row is added, statistics are
collected for the VCL. Statistics collection is terminated by deletion of the row.
5.32.4.2.2
pdnAtmVclCurrTable
This table maintains per-TP statistics for the fifteen-minute interval currently being collected. This table is a sequence
of pdnAtmVclCurrEntry where an entry in this table for VCL termination points. Each VCL Termination Point
automatically has an entry in this table associated with it.
526
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
Index(es):
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVclVpi (Section 5.15.4.6.1, Page 331)
atmVclVci (Section 5.15.4.6.2, Page 331)
OIDs:
•
•
pdnAtmVclCurrTable
pdnAtmVclCurrEntry
- { pdnAtmVclStat 3 }
- { pdnAtmVclCurrTable 1 }
1.3.6.1.4.1.1795.2.24.2.6.11.3.2.3
1.3.6.1.4.1.1795.2.24.2.6.11.3.2.3.1
Table 312: pdnAtmVclCurrTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmVclCurrElapsedTime
{ pdnAtmVclCurrEntry 1 }
TimeInterval
read-only
current
N
pdnAtmVclCurrTotalCellIns
{ pdnAtmVclCurrEntry 2 }
Gauge32
read-only
current
N
pdnAtmVclCurrTotalInDiscards
{ pdnAtmVclCurrEntry 3 }
Gauge32
read-only
current
N
pdnAtmVclCurrTotalCellOuts
{ pdnAtmVclCurrEntry 4 }
Gauge32
read-only
current
N
pdnAtmVclCurrTotalOutDiscards
{ pdnAtmVclCurrEntry 5 }
Gauge32
read-only
current
N
5.32.4.2.2.1
pdnAtmVclCurrElapsedTime
Amount of time, measured in seconds, that statistics for this entry (the current interval) have been counted.
5.32.4.2.2.2
pdnAtmVclCurrTotalCellIns
The total number of valid ATM cells received by this VCL. This number corresponds to that of total cells received
from CPE if this interface is a DSL ATM interface.
5.32.4.2.2.3
pdnAtmVclCurrTotalInDiscards
The number of discarded received cells.
5.32.4.2.2.4
pdnAtmVclCurrTotalCellOuts
The number of cells that have been successfully sent. This number corresponds to that of total cells transmitted to
CPE if this interface is a DSL ATM interface.
5.32.4.2.2.5
pdnAtmVclCurrTotalOutDiscards
The number of discarded transmitted cells since this interval.
5.32.4.2.3
pdnAtmVclHistTable
This table maintains per-interface statistics for previous fifteen-minute intervals. The table is a sequence of
pdnAtmVclHistory where an entry in History Data table for VCL termination points. Each VCL Termination Point
automatically has an entry in this table associated with it. This data are only recorded fro permanent connections.
527
BitStorm 2600 and GranDSLAM 4200 IP DSLAM
SNMP Reference
PDN-ATMSTATS-MIB — pdn_AtmStats.mib
Index(es):
•
•
•
•
ifIndex (Section 5.3.4.3.1, Page 39)
atmVclVpi (Section 5.15.4.6.1, Page 331)
atmVclVci (Section 5.15.4.6.2, Page 331)
pdnAtmVclHistIndex
OIDs:
•
•
pdnAtmVclHistTable
pdnAtmVclHistEntry
- { pdnAtmVclStat 4 }
1.3.6.1.4.1.1795.2.24.2.6.11.3.2.4
- { pdnAtmVclHistTable 1 } 1.3.6.1.4.1.1795.2.24.2.6.11.3.2.4.1
Table 313: pdnAtmVclHistTable
Object
OID
Syntax
Access
Status
Supported
pdnAtmVclHistIndex
{ pdnAtmVclHistEntry 1 }
Integer32(1…96)
not-accessible
current
N
pdnAtmVclHistElapsedTime
{ pdnAtmVclHistEntry 2 }
TimeInterval
read-only
current
N
pdnAtmVclHistTotalCellIns
{ pdnAtmVclHistEntry 3 }
Gauge32
read-only
current
N
pdnAtmVclHistTotalInDiscards
{ pdnAtmVclHistEntry 4 }
Gauge32
read-only
current
N
pdnAtmVclHistTotalCellOuts
{ pdnAtmVclHistEntry 5 }
Gauge32