1 / 8

What the slides cover

What the slides cover. They are not HDSL2 tutorials. They are not a justification/defense of HDSL (if there are those that ask "why?") They do present the differences between ADSL and HDSL2 which show why a different MIB is needed. They do not address G.SHDSL, which is similar but different.

micol
Download Presentation

What the slides cover

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. What the slides cover • They are not HDSL2 tutorials. • They are not a justification/defense of HDSL (if there are those that ask "why?") • They do present the differences between ADSL and HDSL2 which show why a different MIB is needed. • They do not address G.SHDSL, which is similar but different. • There are not many of them.

  2. Who will do the work? • Primary volunteer • Bob Ray, Verilink Corporation, • Secondary volunteers • Steve Blackwell, ADTRAN Corporation, • Mark Johnson, Redpoint Software

  3. Status of HDSL2 • HDSL2 has already gone through a balloting process with comments returned and corrections made. A default letter ballot is underway and approval seems certain. • G.SHDSL has the possibility of obsoleting HDSL2. The editor has pushed for final approval in April 2000

  4. What is different, MIB-wise, between ADSL and HDSL2 • HDSL2 has regenerators/repeaters which are capable of providing the same information as the end units (H2TU-C and H2TU-R). This information is vital during a truck roll. • HDSL2 is primarily a T1-replacement, so an SNMP agent in an HDSL2 box/card *should* support RFC 2495 (DS1 MIB).

  5. Duality Discarded • An HDSL2 line has up to 10 active elements • H2TU-C - CO side • H2TU-R - remote side • H2RU - regenerators • HDSL2 messaging is designed to support direct addressing of each of these. • Change approach used in ADSL LINE MIB where separate tables are maintained (with near identical information for central and remote equipment to an extended interpretation of ifIndex ala RFC 2495. In this case, each interface in a complete HDSL2 line has two entries in the ifTable.

  6. ifTable Example • Consider an HDSL2 line with 1 regenerator, embedded • agent in the H2TU-C, connected to routers on each end. • In this case, the ifTable will have (at least) 7 entries: • ifIndex Description • ------- --------------------- • 1 Ethernet • 2 H2TU-C, Router • 3 H2TU-C, Remote • 4 H2RU#1, Central • 5 H2RU#1, Remote • 6 H2TU-R, Central • 7 H2TU-R, Router.

  7. H2TU-R| router#2 router#1 H2TU-C H2RU ethernet

  8. ifTable Example cont’d • Obviously, the HDSL2 MIB will not address interfaces 1, 2, and 7 in this example. Note that 2 and 7 will probably be channelized DS1s with up to 24 DS0s each, giving an ifTable with 5 + 24 + 24 = 53 entries. So it goes.

More Related