vdslMIB MODULE-IDENTITY
LAST-UPDATED "200402190000Z" -- February 19, 2004
ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: [email protected]
Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed
Sand Channel Systems
Postal: P.O. Box 37324
Raleigh, NC 27627-7324
USA
Email: [email protected]
Phone: +1 206 600 7022
Co-editor: Bob Ray
PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive
Huntsville, AL 35805
USA
Email: [email protected]
Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi
Alcatel USA
Postal: 2301 Sugar Bush Road
Raleigh, NC 27612-3339
USA
Email: [email protected]
Phone: +1 919 850 6194
"
DESCRIPTION
"The MIB module defining objects for the management of a pair
of VDSL transceivers at each end of the VDSL line. Each such
line has an entry in an iftable which may include multiple
transceiver lines. An agent may reside at either end of the
VDSL line. However, the MIB is designed to require no
management communication between them beyond that inherent in
the low-level VDSL line protocol. The agent may monitor and
control this protocol for its needs.
VDSL lines may support optional Fast or Interleaved channels.
If these are supported, additional entries corresponding to the
supported channels must be created in the iftable. Thus a VDSL
line that supports both channels will have three entries in the
iftable, one for each physical, fast, and interleaved, whose
iftype values are equal to vdsl(97), fast(125), and
interleaved(124), respectively. The ifStackTable is used to
represent the relationship between the entries.
Naming Conventions:
Vtuc -- (VTUC) transceiver at near (Central) end of line
Vtur -- (VTUR) transceiver at Remote end of line
Vtu -- One of either Vtuc or Vtur
Curr -- Current
Prev -- Previous
Atn -- Attenuation
ES -- Errored Second.
SES -- Severely Errored Second
UAS -- Unavailable Second
LCS -- Line Code Specific
Lof -- Loss of Frame
Lol -- Loss of Link
Los -- Loss of Signal
Lpr -- Loss of Power
xxxs -- Sum of Seconds in which xxx has occured
(e.g., xxx = Lof, Los, Lpr, Lol)
Max -- Maximum
Mgn -- Margin
Min -- Minimum
Psd -- Power Spectral Density
Snr -- Signal to Noise Ratio
Tx -- Transmit
Blks -- Blocks
Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC 3728: see the RFC
itself for full legal notices."
REVISION "200402190000Z" -- February 19, 2004
DESCRIPTION "Initial version, published as RFC 3728."
View at oid-info.com
The MIB module defining objects for the management of a pair
of VDSL transceivers at each end of the VDSL line. Each such
line has an entry in an ifTable which may include multiple
transceiver lines. An agent may reside at either end of the
VDSL line. However, the MIB is designed to require no
management communication between them beyond that inherent in
the low-level VDSL line protocol. The agent may monitor and
control this protocol for its needs.
VDSL lines may support optional Fast or Interleaved channels.
If these are supported, additional entries corresponding to the
supported channels must be created in the ifTable. Thus a VDSL
line that supports both channels will have three entries in the
ifTable, one for each physical, fast, and interleaved, whose
ifType values are equal to vdsl(97), fast(125), and
interleaved(124), respectively. The ifStackTable is used to
represent the relationship between the entries.
Naming Conventions:
Vtuc
Vtur
Vtu
Curr
Prev
Atn
ES
SES
UAS
LCS
Lof
Lol
Los
Lpr
xxxs
(e.g., xxx = Lof, Los, Lpr, Lol)
Max
Mgn
Min
Psd
Snr
Tx
Blks
Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC 3728: see the RFC
itself for full legal notices.
Parsed from file rfc3728-Very-High-Speed-Digital-Subscriber-Lines-VDSL.mib.txt
Company: None
Module: VDSL-LINE-MIB
The MIB module defining objects for the management of a pair
of VDSL transceivers at each end of the VDSL line. Each such
line has an entry in an ifTable which may include multiple
transceiver lines. An agent may reside at either end of the
VDSL line. However, the MIB is designed to require no
management communication between them beyond that inherent in
the low-level VDSL line protocol. The agent may monitor and
control this protocol for its needs.
VDSL lines may support optional Fast or Interleaved channels.
If these are supported, additional entries corresponding to the
supported channels must be created in the ifTable. Thus a VDSL
line that supports both channels will have three entries in the
ifTable, one for each physical, fast, and interleaved, whose
ifType values are equal to vdsl(97), fast(125), and
interleaved(124), respectively. The ifStackTable is used to
represent the relationship between the entries.
Naming Conventions:
Vtuc
Vtur
Vtu
Curr
Prev
Atn
ES
SES
UAS
LCS
Lof
Lol
Los
Lpr
xxxs
(e.g., xxx = Lof, Los, Lpr, Lol)
Max
Mgn
Min
Psd
Snr
Tx
Blks
Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC 3728: see the RFC
itself for full legal notices.
Parsed from file VDSL-LINE-MIB.mib
Module: VDSL-LINE-MIB
Automatically extracted from RFC3728
vdslMIB MODULE-IDENTITY LAST-UPDATED "200402190000Z" ORGANIZATION "ADSLMIB Working Group" CONTACT-INFO "WG-email: [email protected] Info: https://www1.ietf.org/mailman/listinfo/adslmib Chair: Mike Sneed Sand Channel Systems Postal: P.O. Box 37324 Raleigh, NC 27627-7324 USA Email: [email protected] Phone: +1 206 600 7022 Co-editor: Bob Ray PESA Switching Systems, Inc. Postal: 330-A Wynn Drive Huntsville, AL 35805 USA Email: [email protected] Phone: +1 256 726 9200 ext. 142 Co-editor: Rajesh Abbi Alcatel USA Postal: 2301 Sugar Bush Road Raleigh, NC 27612-3339 USA Email: [email protected] Phone: +1 919 850 6194 " DESCRIPTION "The MIB module defining objects for the management of a pair of VDSL transceivers at each end of the VDSL line. Each such line has an entry in an ifTable which may include multiple transceiver lines. An agent may reside at either end of the VDSL line. However, the MIB is designed to require no management communication between them beyond that inherent in the low-level VDSL line protocol. The agent may monitor and control this protocol for its needs. VDSL lines may support optional Fast or Interleaved channels. If these are supported, additional entries corresponding to the supported channels must be created in the ifTable. Thus a VDSL line that supports both channels will have three entries in the ifTable, one for each physical, fast, and interleaved, whose ifType values are equal to vdsl(97), fast(125), and interleaved(124), respectively. The ifStackTable is used to represent the relationship between the entries. Naming Conventions: Vtuc Vtur Vtu Curr Prev Atn ES SES UAS LCS Lof Lol Los Lpr xxxs (e.g., xxx = Lof, Los, Lpr, Lol) Max Mgn Min Psd Snr Tx Blks Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3728: see the RFC itself for full legal notices." REVISION "200402190000Z" DESCRIPTION "Initial version, published as RFC 3728." ::= { transmission 97 }
vdslMIB MODULE-IDENTITY LAST-UPDATED "200402190000Z" ORGANIZATION "ADSLMIB Working Group" CONTACT-INFO "WG-email: [email protected] Info: https://www1.ietf.org/mailman/listinfo/adslmib Chair: Mike Sneed Sand Channel Systems Postal: P.O. Box 37324 Raleigh, NC 27627-7324 USA Email: [email protected] Phone: +1 206 600 7022 Co-editor: Bob Ray PESA Switching Systems, Inc. Postal: 330-A Wynn Drive Huntsville, AL 35805 USA Email: [email protected] Phone: +1 256 726 9200 ext. 142 Co-editor: Rajesh Abbi Alcatel USA Postal: 2301 Sugar Bush Road Raleigh, NC 27612-3339 USA Email: [email protected] Phone: +1 919 850 6194 " DESCRIPTION "The MIB module defining objects for the management of a pair of VDSL transceivers at each end of the VDSL line. Each such line has an entry in an ifTable which may include multiple transceiver lines. An agent may reside at either end of the VDSL line. However, the MIB is designed to require no management communication between them beyond that inherent in the low-level VDSL line protocol. The agent may monitor and control this protocol for its needs. VDSL lines may support optional Fast or Interleaved channels. If these are supported, additional entries corresponding to the supported channels must be created in the ifTable. Thus a VDSL line that supports both channels will have three entries in the ifTable, one for each physical, fast, and interleaved, whose ifType values are equal to vdsl(97), fast(125), and interleaved(124), respectively. The ifStackTable is used to represent the relationship between the entries. Naming Conventions: Vtuc Vtur Vtu Curr Prev Atn ES SES UAS LCS Lof Lol Los Lpr xxxs (e.g., xxx = Lof, Los, Lpr, Lol) Max Mgn Min Psd Snr Tx Blks Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3728: see the RFC itself for full legal notices." REVISION "200402190000Z" DESCRIPTION "Initial version, published as RFC 3728." ::= { transmission 97 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.97.1 | vdslLineMib | 3 | 185 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.1 | optix155622H | 0 | 0 | None |
| 1.3.6.1.2.1.10.2 | optix10Gv2 | 0 | 0 | None |
| 1.3.6.1.2.1.10.5 | x25 | 10 | 169 | None |
| 1.3.6.1.2.1.10.7 | ieee8023, dot3 | 10 | 204 | CSMACD-like Objects (IEEE 802.3) |
| 1.3.6.1.2.1.10.8 | ieee8024 | 0 | 0 | IEEE 802.4 Token Bus-like Objects |
| 1.3.6.1.2.1.10.9 | dot5 | 6 | 60 | The MIB module for IEEE Token Ring entities. |
| 1.3.6.1.2.1.10.10 | dot5 | 4 | 115 | None |
| 1.3.6.1.2.1.10.15 | fddi | 7 | 236 | None |
| 1.3.6.1.2.1.10.16 | lapb | 5 | 58 | None |
| 1.3.6.1.2.1.10.18 | ds1 | 11 | 147 | The MIB module to describe DS1, E1, DS2, and E2 interfaces objects. |
| 1.3.6.1.2.1.10.19 | e1 | 0 | 0 | E1 Carrier Objects |
| 1.3.6.1.2.1.10.20 | isdnMib | 3 | 89 | The MIB module to describe the management of ISDN interfaces. |
| 1.3.6.1.2.1.10.21 | dialControlMib | 3 | 93 | The MIB module to describe peer information for demand access and possibly other kinds of interfaces. |
| 1.3.6.1.2.1.10.23 | ppp | 4 | 101 | None |
| 1.3.6.1.2.1.10.30 | ds3 | 12 | 119 | The is the MIB module that describes DS3 and E3 interfaces objects. |
| 1.3.6.1.2.1.10.31 | sip | 6 | 54 | None |
| 1.3.6.1.2.1.10.32 | frame-relay, frameRelayDTE, frameRelay, frpublic | 8 | 126 | The MIB module to describe the use of a Frame Relay interface by a DTE. |
| 1.3.6.1.2.1.10.33 | rs232 | 7 | 58 | The MIB module for RS-232-like hardware devices. |
| 1.3.6.1.2.1.10.34 | paralell, para | 5 | 25 | The MIB module for Parallel-printer-like hardware devices. |
| 1.3.6.1.2.1.10.35 | arcnet | 0 | 0 | ARC network |
| 1.3.6.1.2.1.10.36 | arcnet-plus | 0 | 0 | ARC network plus |
| 1.3.6.1.2.1.10.37 | atm | 0 | 0 | ATM |
| 1.3.6.1.2.1.10.38 | miox25, miox | 2 | 36 | MIOX25 |
| 1.3.6.1.2.1.10.39 | sonetMIB | 4 | 149 | The MIB module to describe SONET/SDH interfaces objects. |
| 1.3.6.1.2.1.10.44 | frnetservMIB | 3 | 126 | The MIB module to describe generic objects for Frame Relay Network Service. |
| 1.3.6.1.2.1.10.45 | dot12MIB | 2 | 34 | This MIB module describes objects for managing IEEE 802.12 interfaces. |
| 1.3.6.1.2.1.10.46 | ipoaMIB | 3 | 96 | This module defines a portion of the management information base (MIB) for managing Classical IP and ARP over ATM entities. |
| 1.3.6.1.2.1.10.47 | mfrMib, hippi | 5 | 94 | This is the MIB used to control and monitor the multilink frame relay (MFR) function described in FRF.16. |
| 1.3.6.1.2.1.10.48 | hdsl2ShdslMIB | 3 | 150 | This MIB module defines a collection of objects for managing HDSL2/SHDSL lines. An agent may reside at either end of the line; h… |
| 1.3.6.1.2.1.10.49 | apsMIB | 3 | 80 | This management information module supports the configuration and management of SONET linear APS groups. The definitions and desc… |
| 1.3.6.1.2.1.10.56 | fcMgmtMIB | 3 | 163 | This module defines management information specific to Fibre Channel-attached devices. Copyright (C) The Internet Society (2005).… |
| 1.3.6.1.2.1.10.81 | ds0 | 3 | 18 | The MIB module to describe DS0 interfaces objects. |
| 1.3.6.1.2.1.10.82 | ds0bundle | 4 | 19 | The MIB module to describe DS0 Bundle interfaces objects. |
| 1.3.6.1.2.1.10.94 | adslmib | 3 | 418 | The MIB module defining objects for the management of a pair of ADSL modems at each end of the ADSL line. Each such line has an … |
| 1.3.6.1.2.1.10.95 | l2tp | 9 | 186 | The MIB module that describes managed objects of general use by the Layer Two Transport Protocol. |
| 1.3.6.1.2.1.10.96 | hdslHturMIB | 1 | 23 | None |
| 1.3.6.1.2.1.10.127 | docsIfMib | 7 | 773 | This is the MIB Module for MCNS/DOCSIS compliant Radio Frequency (RF) interfaces in Cable Modems (CM) and Cable Modem Termination… |
| 1.3.6.1.2.1.10.128 | docsTrCmMIB | 0 | 0 | TELCO Return MIB for Data Over Cable Access modems and termination systems |
| 1.3.6.1.2.1.10.131 | tunnelMIB | 2 | 41 | The MIB module for management of IP Tunnels, independent of the specific encapsulation scheme in use. |
| 1.3.6.1.2.1.10.132 | coffee | 5 | 21 | The MIB Module for coffee vending devices. |
| 1.3.6.1.2.1.10.133 | optIfMibModule | 2 | 474 | The MIB module to describe pre-OTN and OTN interfaces. Copyright (C) The Internet Society (2003). This version of this MIB modul… |
| 1.3.6.1.2.1.10.134 | etherWisMIB | 3 | 32 | The objects in this MIB module are used in conjunction with objects in the SONET-MIB and the MAU-MIB to manage the Ethernet WAN I… |
| 1.3.6.1.2.1.10.146 | dvbInaIf | 2 | 300 | The MIB modules for INAs that conform to the EuroModem specification. This MIB assumes the INA implements MIB-II RFC 1213 The ori… |
| 1.3.6.1.2.1.10.166 | mplsStdMIB | 16 | 849 | None |
| 1.3.6.1.2.1.10.200 | teLinkStdMIB | 3 | 87 | Copyright (C) 2005 The Internet Society. This version of this MIB module is part of RFC 4220; see the RFC itself for full legal … |
| 1.3.6.1.2.1.10.227 | lmpMIB | 3 | 226 | Copyright (C) 2006 The Internet Society. This version of the MIB module is part of RFC 4631; see the RFC itself for full legal n… |
| 1.3.6.1.2.1.10.228 | vdslExtSCMMIB | 1 | 26 | The VDSL-LINE-MIB found in RFC 3728 defines objects for the management of a pair of VDSL transceivers at each end of the VDSL lin… |
| 1.3.6.1.2.1.10.229 | vdslExtMCMMIB | 1 | 41 | The VDSL-LINE-MIB found in RFC 3728 defines objects for the management of a pair of VDSL transceivers at each end of the VDSL lin… |
| 1.3.6.1.2.1.10.230 | ifcpMgmtMIB | 2 | 69 | This module defines management information specific to internet Fibre Channel Protocol (iFCP) gateway management. Copyright (C) Th… |
| 1.3.6.1.2.1.10.238 | adsl2MIB | 2 | 354 | This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet commun… |
| 1.3.6.1.2.1.10.239 | dvbRcsMib | 2 | 216 | dvbRcsMib MODULE-IDENTITY LAST-UPDATED "201002161200Z" ORGANIZATION "The SatLabs Group" CONTACT-INFO "The SatLabs Group Web: ht… |
| 1.3.6.1.2.1.10.246 | pwStdMIB | 3 | 137 | pwStdMIB MODULE-IDENTITY LAST-UPDATED "200906110000Z" -- 11 June 2009 00:00:00 GMT ORGANIZATION "Pseudowire Edge-to-Edge Emulat… |
| 1.3.6.1.2.1.10.251 | vdsl2MIB | 4 | 435 | This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet commun… |
| 1.3.6.1.2.1.10.274 | vplsGenericMIB | 3 | 50 | vplsGenericMIB MODULE-IDENTITY LAST-UPDATED "201405191200Z" -- 19 May 2014 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private N… |
| 1.3.6.1.2.1.10.275 | vplsLdpMIB | 3 | 13 | vplsLdpMIB MODULE-IDENTITY LAST-UPDATED "201405191200Z" -- 19 May 2014 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Netwo… |
| 1.3.6.1.2.1.10.276 | vplsBgpMIB | 2 | 21 | vplsBgpMIB MODULE-IDENTITY LAST-UPDATED "201405191200Z" -- 19 May 2014 12:00:00 GMT ORGANIZATION "Layer 2 Virtual Private Netwo… |
| 1.3.6.1.2.1.10.7777 | pwMIB | 1 | 1 | None |
| 1.3.6.1.2.1.10.9999 | mplsMIB | 1 | 1 | None |