You are on page 1of 42

Section 61181413L2-5A Issue 1, November 2003 CLEI Code: S1C4WTXD_ _

Total Access 3000 HDSL4 Transceiver Unit for the Central Office Installation and Maintenance Practice
CONTENTS
1. General ..................................................................................... 2 2. Connections .............................................................................. 3 3. Installation ................................................................................ 4 4. Provisioning.............................................................................. 6 5. HDSL4 System Testing............................................................ 7 6. SCU Control Port Operation-HDSL4....................................... 8 7. HDSL4 Deployment Guidelines............................................. 29 8. Maintenance ........................................................................... 34 9. Specifications ......................................................................... 34 10. Warranty and Customer Service............................................. 34 Appendix A. HDSL4 Loopbacks .............................................. A-1 Appendix B. Front Panel DSX and MUX Mode Test Access .. B-1 Figure 39. Download H4TUC via TFTP...................................... 27 Figure 40. Boot Block Status and Overwrite Password............... 28 Figure 41. HDSL4 Circuit Segments ........................................... 29 Figure 42. Resistance Budget Span Powering Two Repeaters .... 31 Figure 43. Resistance Budget Span Powering (Example) ........... 32 Figure B-1. DSX MON, Tx to Customer ................................... B-1 Figure B-2. DSX Mon, Rx from Customer ................................ B-1 Figure B-3. DSX EQ, Tx to Customer and Rx from Customer . B-1 Figure B-4. MUX MON, Tx to Customer.................................. B-2 Figure B-5. MUX MON, Rx from Customer............................. B-2 Figure B-6. MUX EQ, Tx to Network and Rx from Network ... B-2 Figure B-7. MUX EQ, Tx to Customer and Rx from Customer B-2

TABLES
Table 1. ADTRAN HDSL4 Unit Compatibility .......................... 2 Table 2. Compliance Codes.......................................................... 3 Table 3. Total Access Backplane Connector Pinout .................... 4 Table 4. Front Panel LEDs ........................................................... 5 Table 5. Provisioning Options...................................................... 6 Table 6. Auto In Service Status Indications ............................... 14 Table 7. Attenuation limits......................................................... 29 Table 8. Range Limits: 26 Gauge / 70F / PIC .......................... 29 Table 9. Range Limits: 24 Gauge / 70F / PIC .......................... 29 Table 10. Single Pair DC Resistance Value ................................. 30 Table 11. HDSL4 Insertion Loss Values...................................... 33 Table 12. Single Span and First Segment of Repeatered Loop.... 33 Table 13. Second or Third Segment of Repeatered Loop ............ 33 Table 14. HDSL4 Total Access 3000 H4TU-C Specifications.... 35 Table A-1. HDSL4 Loopback Control Codes ............................ A-2 Table A-2. Loopback Control Codes.......................................... A-3

FIGURES
Figure 1. ADTRAN Total Access 3000 H4TU-C........................ 1 Figure 2. TScan Diagnostic Capabilities...................................... 3 Figure 3. H4TU-C Span Powering Diagram ................................ 3 Figure 4. H4TU-C Bantam Jack Arrangement............................. 7 Figure 5. HDSL4 Loopbacks ....................................................... 8 Figure 6. RS-232 (DB9) Pin Assignments ................................... 8 Figure 7. Total Access System Logon Screen.............................. 9 Figure 8. Total Access Main Menu .............................................. 9 Figure 9. Access Module Menu ................................................. 10 Figure 10. HDSL4 Main Menu .................................................... 10 Figure 11. Unit Information Screen ............................................. 11 Figure 12. Provisioning Menu, Page 1 ......................................... 11 Figure 13. Provisioning Menu, Page 2 ......................................... 12 Figure 14. Span Status Screen...................................................... 12 Figure 15. Detailed Status Screen ................................................ 13 Figure 16. Auto In Service Status Screen .................................... 13 Figure 17. Loopback and Test Commands Screen....................... 15 Figure 18. BERT Test Screen ...................................................... 16 Figure 19. Select Data Pattern...................................................... 16 Figure 20. BERT Timeout Screen................................................ 17 Figure 21. BERT Inject Errors Screen ......................................... 17 Figure 22. Performance Data Selection Screen (15-Minute, Line)........................................................ 18 Figure 23. Performance Data Selection Screen (24-Hour, Path) . 18 Figure 24. Performance Data Definitions .................................... 19 Figure 25. Performance Data Definitions .................................... 19 Figure 26. Scratch Pad and Circuit ID Screen ............................. 20 Figure 27. T1 Alarm History Screen ............................................ 20 Figure 28. Facility Alarm History Screen .................................... 21 Figure 29. HDSL4 Span History Screen ...................................... 21 Figure 30. Event History Screen .................................................. 22 Figure 31. System Status/PM Report Screen ............................... 23 Figure 32. Clear PM and Alarm Histories Screen........................ 23 Figure 33. Troubleshooting Screen .............................................. 24 Figure 34. Troubleshooting Guidance Screen.............................. 24 Figure 35. General Information Screen........................................ 25 Figure 36. Total Access 3000 H4TU-C Flash Image Screen ....... 25 Figure 37. Download H4TU-C via Y-Modem ............................. 26 Figure 38. Flash Upgrade, Y-Modem in Progress ....................... 26

H TUC
1181413L2

DSL 1 DSL 2 DSX/DS1 ALM

(YEL) (GRN) (YEL) (GRN)

ESF/ SF

B8ZS/ AMI LBK

EQ T X R X T X R X MON

Figure 1. ADTRAN Total Access 3000 H4TU-C

61181413L2-5A

Trademarks: Any brand names and product names included in this document are trademarks, registered trademarks, or trade names of their respective holders.

1. GENERAL This practice is an installation and maintenance guide for the ADTRAN HDSL4 Total Access 3000 HDSL4 Transceiver Unit for the Central Office (H4TU-C) (P/N 1181413L2). The H4TU-C is used to deploy an HDSL4 T1 circuit using 4-wire metallic facilities. Figure 1 illustrates the Total Access 3000 H4TU-C front panel. This unit occupies one slot in a Total Access 3000 shelf. Revision History This is the initial issue of this practice. Future changes to this documentation will be explained in this subsection. Description The DS1 or DSX-1 input signal can be supplied from the network or a Total Access 3000 Multiplexer (DS3, STS-1, or OC-3). The HDSL4 signals are provided to the local loop. The ADTRAN Total Access 3000 H4TU-C works in conjunction with the ADTRAN H4TU-R (Remote) and up to two H4Rs (Repeaters) to provide a DS1 service on the local loop. Compatible ADTRAN units for this H4TU-C are shown in Table 1. Table 1. ADTRAN HDSL4 Unit Compatibility
Part Number 122x424L2 122x426L2 122x441L1 122x445L1
x = any generic number

The Total Access 3000 H4TU-C can be deployed in circuits consisting of one H4TU-C, one H4TU-R, and up to two H4Rs. System power and alarm bus connections are made through the backplane of the Total Access 3000 chassis. DSX-1 and HDSL4 signals are connected through the 64-pin shelf connectors located on the rear of the chassis. The H4TU-C contains an onboard fuse. If the fuse opens, it supplies a 48 VDC voltage to the fuse alarm bus of the Total Access 3000 and all front panel indicators will be off. This fuse is not designed to be replaced in the field. The Total Access 3000 H4TU-C uses a DC-to-DC converter to derive its internal logic and span powering voltages from the 48 VDC office supply. The H4TU-C can span power an H4TU-R and up to two H4Rs as listed above. TScan This unit is equipped to support the TScan feature, which provides data retrieval and diagnostic capabilities for remote management of DS1 circuits. TScan allows provisioning, performance, and event history information to be retrieved by the test center via the Facility Data Link (FDL). In addition, TScan can be used to determine the nature and location of faults on DS1 trouble circuits. TScan is accessible only through the remote test center. NOTE For implementation of Tscan please contact your local ADTRAN sales representative. A patent-pending single-ended diagnostic routine residing on a host server at the central test facility, Tscan issues commands and retrieves data via FDL from the H4TU-C. Tscan performs the following functions (see Figure 2): Detection and location of an open, one or both conductors Detection and location of a short between Tip and Ring Detection and location of a ground fault from either or both conductors Detection of foreign voltage H4TU-C self diagnostics

Description T200 H4TU-R, Local Power T200 H4TU-R, Span Power T200 H4R Repeater 239 H4R Repeater

Features The basic features of the Total Access 3000 H4TU-C include the following: Auto In Service Bit Error Rate Testing (BERT) Flash Upgrade Troubleshooting Guidance TScan

These and other features will be discussed in the practice.

Issue 1, November 2003

61181413L2-5A

Remotely detects the presence or absence of a ground connection in the remote mount.

WARNING Up to 200 VDC may be present on telecommunications wiring. The DSX-1 interface is intended for connection to intra-building wiring only. Ensure chassis ground is properly connected. This product provides span powering voltage (negative only with respect to ground, 190 VDC nominal, GFI protection < 5 mA) and meets all requirements of Bellcore GR-1089-CORE (Class A2) and ANSI T1.418-2002. This product is NRTL listed to the applicable UL standards. 2. CONNECTIONS The Total Access 3000 H4TU-C occupies one card slot in a Total Access 3000 shelf. Power and alarm signals are provided to the card through the backplane of the shelf. DSX-1 and HDSL4 loop signals are connected to the mass termination (amphenol) shelf connectors. See Table 3 for the pin numbers of the Total Access 3000 backplane amphenol connectors. The Total Access 3000 H4TU-C is capable of span powering the H4TU-R and two H4Rs by applying current to the local loop. From 30 to 155 mA of loop current is coupled onto the HDSL4 span to power the H4TU-R and two H4Rs (when deployed). The span powering voltage is approximately 190 VDC with GFI protection to less than 5 mA. The differential span power output voltage (refer to Figure 3) is measured between Loop 2 and Loop 1 (reference to Loop 2) and is typically 185 VDC. Loop 1 will show a typical voltage of 191 VDC with respect to ground potential, while the Loop 2 potential is typically 6 VDC with respect to ground potential.

CO

Outside Plant Facilities

C C C C

X X X

R R R R

Open on either conductor

Open on both conductors

Short between T&R Short to ground from either or both conductors

Figure 2. TScan Diagnostic Capabilities TScan allows operators to integrate this capability across multiple computing platforms with existing operating systems. Auto In Service The Total Access 3000 H4TU-C supports the Auto InService feature that will automatically change the service state of the line card from Out-of-Service, Maintenance (OOS-MA) to In-Service and vice versa based on DSL loop synchronization and/or DSX-1/DS1 alarm presence. This and other features are discussed in more detail in the SCU Control Port Operation-HDSL4 section. Compliance Table 2 shows the compliance codes for the Total Access 3000 HDSL4 Transceiver Unit for the Central Office. The Total Access 3000 H4TU-C is NRTL listed to the applicable UL standards. The Total Access 3000 H4TU-C is to be installed in a restricted access location and in a Type B or E enclosure only. Table 2. Compliance Codes
Code Power Code (PC) Telecommunication Code (TC) Installation Code (IC) Input F A Output C X

LOOP 1 (-191 VDC)


R SPAN POWER REGULATOR

This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: 1. This device may not cause harmful interference. 2. This device must accept any interference received, including interference that may cause undesired operation.

TC PAM HDSL4

SPAN CURRENT

-185 VDC

T1

LOOP 2 (-6 VDC)


R1

Figure 3. H4TU-C Span Powering Diagram


3

61181413L2-5A

Issue 1, November 2003

Table 3. Total Access Backplane Connector Pinout


Slot HDSL4 Loop Pair 1 and Pair 2 (Customer Side) 1/33 2/34 3/35 4/36 5/37 6/38 7/39 8/40 9/41 10/42 11/43 12/44 13/45 14/46 15/47 16/48 17/49 18/50 19/51 20/52 21/53 22/54 23/55 24/56 25/57 26/58 27/59 28/60 DSX-1 Pair 7 and Pair 8 (Network Side) 1/33 2/34 3/35 4/36 5/37 6/38 7/39 8/40 9/41 10/42 11/43 12/44 13/45 14/46 15/47 16/48 17/49 18/50 19/51 20/52 21/53 22/54 23/55 24/56 25/57 26/58 27/59 28/60

3. INSTALLATION

C A U T I O N !
SUBJECT TO ELECTROSTATIC DAMAGE OR DECREASE IN RELIABILITY.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

HANDLING PRECAUTIONS REQUIRED.

After unpacking the Total Access 3000 H4TU-C, inspect it for damage. If damage has occurred, file a claim with the carrier, then contact ADTRAN Customer Service. Refer to the Warranty and Customer Service section for further information. If possible, keep the original shipping container for returning the Total Access 3000 H4TU-C for repair or for verification of shipping damage. CAUTION Electronic modules can be damaged by Electro-Static Discharge (ESD). When handling modules, wear an antistatic discharge wrist strap to prevent damage to electronic components. Place modules in antistatic packing material when transporting or storing. When working on modules, always place them on an approved antistatic mat that is electrically grounded. There are no configuration switches for the H4TU-C. Configuration is performed via software discussed in the SCU Control Port Operation-HDSL4 section of this practice. The Total Access 3000 H4TU-C plugs directly into the Total Access 3000 chassis. No installation wiring is required. Powering Options The H4TU-C is default enabled for span powering mode. The H4TU-C will power either one, two, or three elements and can be set to disable span power when the H4TU-R is being locally powered and there are no H4Rs on the circuit CAUTION Disabling the span power removes all voltage from the HDSL4 loop. This will result in an absence of sealing current which could have an adverse effect on circuit continuity over an extended period of time.

Issue 1, November 2003

61181413L2-5A

Instructions for Installing the Module To install the Total Access 3000 H4TU-C, perform the following steps: 1. If present, remove the Access Module Blank from the appropriate access module slot of the Total Access chassis. 2. Pull the ejector latch, located on the lower lefthand side of the Total Access 3000 H4TU-C front panel, from its closed position. 3. Hold the unit by the front panel while supporting the bottom edge of the module with the ejector latch opened to engage the chassis edge. 4. Align the unit edges to fit in the lower and upper guide grooves for the access module slot.

5. Slide the unit into the access module slot. Simultaneous thumb pressure at the top and at the bottom of the unit will ensure that the module is firmly positioned against the backplane of the chassis. 6. Secure the Total Access 3000 H4TU-C in place by pushing in on the ejector latch. When the unit first powers up it runs the a series of selftests. Once the power up self-test is complete, the status LEDs will reflect the true state of the hardware. Front Panel LEDs The Total Access 3000 H4TU-C provides front panel LEDs to display status information. Table 4 lists the front panel LEDs and their indications.

Table 4. Front Panel LEDs


Front Panel Label DSL 1/ DSL 2 DSX/DS1 Status Green Red Green Red Description DSL Loop 1/Loop 2 sync, no errors currently detected, and signal margin 3 dB No DSL Loop 1/Loop 2 sync, errors being detected, or signal quality < 3 dB DSX-1 signal is present and synchronized DSX-1 loss of sync is present, frame synchronization cannot be achieved, or a mismatch has occurred between the user provisioned framing and the actual received framing format No alarm condition detected Alarm condition detected either locally (H4TU-C) or locally and remotely (H4TU-C and H4TU-R) Remote alarm condition detected Unit is provisioned for DS1 unframed operation Unit is provisioned for DS1 ESF framing mode Unit is provisioned for DS1 SF framing mode Unit is provisioned for B8ZS coding Unit is provisioned for AMI coding Unit is not in loopback Local H4TU-C loopback is active toward network or customer

H TUC
1181413L2

DSL 1 DSL 2 DSX/DS1 ALM

(YEL) (GRN) (YEL) (GRN)

ESF/ SF

B8ZS/ AMI LBK

ALM
EQ T X R X T X R X MON

Off Red Yellow

ESF/SF

Off Yellow Green Yellow Green Off Yellow

B8ZS/ AMI LBK

61181413L2-5A

Issue 1, November 2003

4. PROVISIONING Through management access via the Total Access 3000 System Controller Unit (SCU), as detailed in the SCU Control Port Operation-HDSL4 section, the provisioning settings can be viewed and manipulated.

Table 5 lists the available provisioning options and the factory default settings.

Table 5. Provisioning Options


Provisioning Option 1. DSX-1 Line Build Out Option Settings 0-133 ft. 133-266 ft. 266-399 ft. 399-533 ft. 533-655 ft. B8ZS, AMI SF, ESF, Unframed, Auto Disabled, Enabled Disabled, Enabled None, 120 Min T1 (Disabled), FT1 (Enabled) 0 dB, 7.5 dB, 15 dB Enabled, Disabled AIS, Loopback, AIS/CI None, SPRM, NPRM, AUTO (both) 0 (Disabled), 1-99 dB 0 (Disabled), 1-15 dB Disabled, Enabled In-Service Out-of-Service, Unassigned Out-of-Service, Maintenance DSX, MUX A, MUX B, Auto MUX Enabled, Disabled Disabled, Enabled 1 hour, 4 hours, 8 hours, 24 hours 1 hour, 4 hours, 8 hours, 24 hours Default Settings 0 to 133 ft.

2. DSX-1/DS1 Line Code 3. DSX-1/DS1 Framing 4. Force Frame Conversion 5. Smartjack Loopback 6. Loopback Time Out 7. Latching Loopback Mode 8. DS1 Tx Level 9. Span Power 10. Customer Loss Indicator 11. Performance Reporting Messages 12. Loop Attenuation Alarm Threshold 13. SNR Margin Alarm Threshold 14. Remote Provisioning 15. Service State1

B8ZS ESF Disabled Enabled 120 Minutes T1 (Disabled) 0 dB Enabled AIS/CI AUTO 34 dB 04 dB Enabled Out-of-Service, Maintenance

16. Network Source 17. External Alarms 18. Auto In Service 19. Auto IS Startup Period 20. Auto IS Off Period
1

DSX Disabled Enabled 4 hours 8 hours

The Service State defaults to Out-of- Service, Maintenance. This setting allows active connections to the DSX or MUX interface; however, no alarms will be generated. The In-Service setting allows full functioning connections to DSX or MUX interfaces. Out of Service-Unassigned allows the loops to train up but will not connect to the DSX or MUX interface.

Issue 1, November 2003

61181413L2-5A

H4TU-C Alarm Outputs Each H4TU-C has a built-in fuse for the 48 VDC power feed. If this fuse blows, the System Controller Unit (SCU) will be notified and generate an alarm. A blown fuse indicates the card has malfunctioned and should be replaced. If there is a need to remove an H4TU-C from the Total Access 3000 shelf, the H4TU-C should be provisioned for either the Out-of-Service, Unassigned or the Out-ofService, Maintenance state. This will disable all HDSL4 level alarms from being sent to the shelf. Any HDSL4 alarm that occurred prior to changing the service state must be acknowledged at the SCU before removing the H4TU-C. In order to avoid a shelf alarm, the H4TU-C element can be provisioned to disable external alarms. This will disable all DSX and DS1 alarms. The Total Access 3000 H4TU-C is equipped with an auto provisioning feature. Upon removal of an H4TUC, all provisioning information is stored in the nonvolatile memory of the H4TU-C and is also stored at the SCU. When the original H4TU-C (or a new H4TU-C) is re-seated in that slot, all provisioning information is restored from memory of the original H4TU-C or through a download from the SCU (if the SCU is set for auto provisioning). 5. HDSL4 SYSTEM TESTING The ADTRAN HDSL4 system provides the ability to monitor the status and performance of the DSX-1 signals, DS1 signals, and HDSL4 loop signals. Detailed performance monitoring is provided via management access of the Total Access 3000 SCU. These features are valuable in troubleshooting and isolating any system level problems that may occur at installation or during operation of the HDSL4 system. The following subsections describe additional testing features. H4TU-C Bantam Jacks The front panel of the H4TU-C contains metallic splitting bantam jacks for both nonintrusive (monitoring) and intrusive (terminating) DSX-1 test access. See Appendix B, Front Panel DSX and MUX Mode Test Access for detailed information regarding the testing capabilities of the bantam jacks. Figure 4 illustrates the complete bantam jack arrangement and details for specific jacks.

T DSX-1 R DSX-1 MON Rx

H4TU-C

EQ Rx H4TU-C DATA PUMP EQ Tx

HDSL4 LOOP 1 LOOP DC POWER SOURCE HDSL4 LOOP 2

HDSL4 LOOP 1

HDSL4 LOOP 2

DSX-1 MON Tx T1 DSX-1 R1

Figure 4. H4TU-C Bantam Jack Arrangement H4TU-C Loopbacks The H4TU-C responds to two different loopback activation processes: First, loopbacks may be activated using the craft interface of the Total Access 3000 SCU. The Loopbacks and Test Screen, which provides for the H4TU-C and H4TU-R loopbacks, is described in the SCU Control Port Operation-HDSL4 of this practice. Second, the H4TU-C responds to the industry standard for HDSL4 loopbacks. A detailed description of these loopback sequences is given in Appendix A, HDSL4 Loopbacks. Even though all framing modes do not provide frame transparency, if a framed or unframed loopback control sequence is sent, then the unit will initiate the proper loopback command (refer to Appendix A, Table A-1), regardless of the framing mode. The loopback condition imposed in all cases is a logic level loopback at the point within the H4TU-C where the DSX-1 signal passes into the HDSL4 modulators. Figure 5 depicts all of the loopback locations possible with ADTRAN HDSL4 equipment.

61181413L2-5A

Issue 1, November 2003

H4TU-C Network-Side Loopback AIS DSX-1 H4TU-C LOCAL LOOP DS1 X H4TU-R

H4TU-R Network-Side Loopback and/or H4TU-R NIU Loopback AIS DSX-1 H4TU-C LOCAL LOOP X H4TU-R DS1

6. SCU CONTROL PORT OPERATION-HDSL4 H4TU-C management access is achieved via the Total Access 3000 enhanced System Controller Unit (SCU). The SCU provides VT100, Telnet, TL1, and SNMP management access through local or remote connections. The Total Access 3000 SCU provides a front panelmounted DB-9 connector that supplies an RS-232 interface for connection to a controlling terminal. The pinout of the DB-9 is illustrated in Figure 6.

H4TU-R Customer-Side Loopback X DSX-1 AIS H4TU-C LOCAL LOOP H4TU-R DS1

H4TU-C Customer-Side Loopback X DSX-1 AIS H4TU-C LOCAL LOOP H4TU-R DS1

1 6 7 8
AIS

2 3 4 5

TXD (Transmit Data) RXD (Receive Data) SGN (Signal Ground)

H4R Network-Side Loopback

DSX-1 H4TU-C H4R X H4TU-R

DS1

H4R Customer-Side Loopback X DSX-1 AIS H4TU-C H4R H4TU-R DS1

Figure 6. RS-232 (DB9) Pin Assignments The terminal interface can operate at data rates of 9.6, 19.2, 38.4, 57.6, and 115.2 kbps. The asynchronous data format is fixed at 8 data bits, no parity, and 1 stop bit. The supported terminal type is VT100 or compatible. NOTE Many portable personal computers use powersaving programs that are known to interfere with applications running on the personal computer. If using a PC with terminal emulation capability, communication between the PC and the HDSL4 unit may be periodically disrupted if power saving programs are being used on the PC. The symptoms may include misplaced characters appearing on the screen and/or the occurrence of screen time outs. These symptoms are not disruptive to the operation of the circuit and are avoidable if the power saving options are disabled or removed.

H4R1 Network-Side Loopback AIS DSX-1 X H4TU-C H4R1 H4R2 H4TU-R DS1

H4R1 Customer-Side Loopback X DSX-1 AIS H4TU-C H4R1 H4R2 H4TU-R DS1

H4R2 Network-Side Loopback AIS DSX-1 X H4TU-C H4R1 H4R2 H4TU-R DS1

H4R2 Customer-Side Loopback X DSX-1 AIS H4TU-C H4R1 H4R2 H4TU-R DS1

X = Signal Inactive

Figure 5. HDSL4 Loopbacks In addition to network-side loopbacks, the H4TU-C provides customer-side loopbacks initiated by using either the terminal control port or in-band loop codes (refer to Appendix A). In this mode, an AIS signal (all ones) is supplied to the network.

Issue 1, November 2003

61181413L2-5A

The screens illustrated in Figure 7 through Figure 40 are for a circuit deployed with the ADTRAN HDSL4 technology. The circuit includes an H4TU-C, up to two H4Rs and an H4TU-R. Other configurations are possible, and the displays will vary slightly from those shown in this section.

Accessing the HDSL4 circuit information via the Total Access SCU Control Port requires an account name and a password if a Telnet menu access is used. Figure 7 shows the logon screen. After successful logon the Total Access main menu will display, as illustrated in Figure 8.

Shelf: 1 Unacknowledged Alarms: None

Total Access System

01/25/02 10:23

Total Access System Account Name: Password:

Figure 7. Total Access System Logon Screen

Shelf: Unacknowledged Alarms: None

Total Access System

01/25/02 16:29

Total Access 1. 2. 3. 4. 5. 6. 7. System Controller Common A - [.....] common B - [.....] Access Modules System Alarms Auxiliary Shelf Access Logoff

Selection:

Figure 8. Total Access Main Menu

61181413L2-5A

Issue 1, November 2003

From the Total Access main menu, select Access Modules. The Access Module Menus screen (Figure 9) will display the access modules occupying the Total Access 3000 shelf. Select the corresponding channel slot number for the desired H4TU-C. To the right of each access module listed, the current alarm state is indicated.

After selecting the H4TU-C in the access module menu, the ADTRAN HDSL4 Main Menu (Figure 10) displays. From the ADTRAN HDSL4 Main Menu various OAM&P (Operation, Administrative, Maintenance, and Provisioning) menus may be accessed. To display a submenu, press the number key associated with the option, and press ENTER.

Shelf: 1 Unacknowledged Alarms: None

Total Access System

01/25/02 09:54

Access Module Menus 1 2 3 4 5 6 7 8 9 10 11 12 13 14 H4TUC L2.... ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ [Info] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] 15 16 17 18 19 20 21 22 23 24 25 26 27 28 ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None] [None]

Enter Channel Slot Number : Inverse = Busy Modules

Figure 9. Access Module Menu

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID: HDSL4 Main Menu 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. HDSL4 Unit Information Provisioning Status Loopbacks and Test Performance Monitoring Scratch Pad, Ckt ID Alarm History Event History System Status/PM Report Clear PM and Alarm Histories Troubleshooting Flash Upgrade

09/03/03 14:57

Selection:

Figure 10. HDSL4 Main Menu


10 Issue 1, November 2003 61181413L2-5A

The HDSL4 Unit Information Screen (Figure 11) provides detailed product information on each component in the HDSL4 circuit. The Provisioning menu (Figure 12) displays current provisioning settings for the HDSL4 circuit.

NOTE The Provisioning menu is displayed on two separate screens. Press N, and press ENTER to display the second page (Figure 13).

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None Press ESC to return to previous menu

01/25/02 09:21

ADTRAN 901 Explorer Boulevard Huntsville, Alabama 35806-2807 --------------------- For Information or Technical Support --------------------Support Hours ( Normal 7am - 7pm CST, Emergency 7 days x 24 hours ) Phone: 800.726.8663 / 888.873.HDSL Fax: 256.963.6217 Internet: www.adtran.com -------------------------------------------------------------------------------ADTN P/N: S/N: CLEI: Manf: Ver: ADTN P/N: S/N: CLEI: Manf: H4TU-C 1181413L2 123456789 SIC4WTXDAA 01/01/2000 24 1 A00000 H4R1 1223445L1 BB50A8343 T1R6TJEDAA 07/12/2003 ADTN P/N: S/N: CLEI: Manf: Ver: ADTN P/N: S/N: CLEI: Manf: H4TU-R 1223426L2 123456789 T1L7SEJAAA 01/01/2000 27 2 A00000 H4R2 1223445L1 BB50A8353 T1R6UJ3DAA 07/12/2003

Figure 11. Unit Information Screen

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID: Provisioning 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. N. DSX-1 Line Buildout DSX-1/DS1 Line Code DSX-1/DS1 Framing Forced Frame Conversion Smartjack Loopback Loopback Timeout Latching Loopback Mode DS1 TX Level Span Power Customer Loss Indicator PRM Setting Loop Atten Alarm Thres SNR Margin Alarm Thres Remote Provisioning Service State Network Source Next Page Selection: = = = = = = = = = = = = = = = =

09/03/03 14:58

0-133 Feet B8ZS ESF Disabled Enabled 120 Min T1 (Disabled) 0 dB Enabled AIS / CI AUTO 34dB 04dB Enabled OOS Maintenance DSX

Figure 12. Provisioning Menu, Page 1

61181413L2-5A

Issue 1, November 2003

11

Additional menu items are available on the second page of the Provisioning menu (Figure 13). To return to the previous menu, press P. To return to the Total Access main menu, press ESCAPE. To restore the HDSL4 factory default settings (see Table 5), press D.

The options shown in Table 5 are available with the H4TU-R (P/N 1223426L2). Some settings may differ when using different H4TU-Rs. The Span Status Screen (Figure 14) provides quick access to status information for each HDSL4 receiver in the circuit. This screen will show current loopbacks or trouble indications in a real-time mode.

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: MAJOR INFO Circuit ID:HntsvlALMn0103 Provisioning 17. 18. 19. 20. D. P. External Alarms Auto In Service Auto IS Startup Period Auto IS Off Period Restore Factory Defaults Previous Page = = = = Disabled Enabled 4 hours 8 hours

09/09/03 14:25

Selection:

Figure 13. Provisioning Menu, Page 2

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None CIRCUIT ID:ABC123 Span Status Screen

01/25/02 09:22

______ ______ ______ ______ | | | | | | | | CUST | | | | | | | | ----->| |-------| |-------| |----------------------| |-----> | | | | | | | | | | | | | | | | <-----| |-------| |-------| |----------------------| |<----| | | | | | | | Mux A |______| |______| |______| |______| DS1 H4TUC H4R 1 H4R 2 H4TUR NET

1. 2.

View Detailed Status View Auto In Service Status

Selection:

Figure 14. Span Status Screen


12 Issue 1, November 2003 61181413L2-5A

Selecting option 1, View Detailed Status, from the Span Status Screen will display the Detailed Status Screen (Figure 15). This screen displays the HDSL4 status for each receiver point.

Selecting option 2, View Auto In Service Status, from the Span Status Screen will display the The Auto In Service Status Screen (Figure 16). This screen provides the status of the Auto In Service feature.

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None CIRCUIT ID:ABC123 Detailed Status Screen LOOP 1 MARGIN ATTEN (CUR/MIN/MAX) (CUR/MAX) ------------- --------17/00/17 00/00 17/00/17 00/00 17/17/17 00/00 17/00/17 00/00 17/17/17 00/00 17/00/17 00/00

01/25/02 09:22

Interface --------H4TUC H4R1 NETW H4R1 CUST H4R2 NETW H4R2 CUST H4TUR

LOOP 2 MARGIN ATTEN (CUR/MIN/MAX) (CUR/MAX) ------------- --------17/00/17 00/00 17/13/17 00/00 17/00/17 00/00 17/13/17 00/00 17/00/17 00/00 17/00/17 00/00

1. Reset Min/Max 2. View Performance History Selection:

Figure 15. Detailed Status Screen

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: CRITICAL MAJOR INFO Circuit ID: Auto In Service Status Screen

09/02/03 17:14

Current Auto In Service State = In-Service Auto In Service Status = Currently in Exiting Period Auto In Service Criteria = DSL Loop Sync (T1 alarms ignored) NOTE: The external alarms provisioning option determines whether T1 alarms are an auto in service criterion. Enabling external alarms sets T1 alarms as a criterion. Criteria --------------DSL Loop Sync Status -----LOS

---Exit Period Timer---07 hrs 50 mins -------------------------------------------------------------------------------1. View Alarm History Selection:

Figure 16. Auto In Service Status Screen

61181413L2-5A

Issue 1, November 2003

13

The Auto In Service Status Screen will display the T1 alarm indications if the External Alarms option is enabled from the Provisioning menu (Figure 12). The Auto In Service Status Screen also displays the startup or exit period remaining as either 1, 4, 8, or 24 hours. This is the time during which the unit monitors both loop synchronization (Loop Sync) and T1 alarms (if enabled) and will only go In-Service or Out-ofService if the circuit remains synchronized and no T1

alarms are reported during the entire measured period. These times are also set from the Provisioning menu. From the Auto In Service Status Screen, select option 1 to view the Alarm History. The Alarm History Screen is also available by selecting option 7 on the Total Access main menu. System responses displayed in the status fields on the Auto In Service Status Screen are shown in Table 6.

Table 6. Auto In Service Status Indications


Status Field Name Current Auto In Service State (Line 1) Auto In Service Status (line 2) System Indications In-Service Out-of-Service, Maintenance Currently in startup period Currently in exiting period OK, Startup Period COMPLETED OK, Startup INCOMPLETE (forced in-service) DSL Loop Sync (T1 alarms ignored) DSL Loop Sync and absence of T1 alarms DSL Loop Sync = OK or LOS (LOS shown in Figure 16) T1 Alarm Status = Alarm or OK

Auto In Service Criteria (line 3) Criteria (current status)

14

Issue 1, November 2003

61181413L2-5A

The Loopback and Test Commands menu (Figure 17) is used to invoke or terminate all available HDSL4 loopbacks. Each HDSL4 circuit component can be looped toward the network or customer from this screen.

Unit self tests can also be initiated from this screen. The equipment jack can be configured for the Customer or Network direction for use in testing (MUX mode only). For more information regarding bantam jack testing capabilities, refer to Appendix B, Front Panel DSX and MUX Mode Test Access.

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None CIRCUIT ID:ABC123 Loopback and Test Commands

01/25/02 09:22

______ ______ ______ ______ | | | | | | | | CUST | | | | | | | | ----->| |-------| |-------| |----------------------| |-----> | | | | | | | | | | | | | | | | <-----| |-------| |-------| |----------------------| |<----| | | | | | | | Mux A |______| |______| |______| |______| DS1 H4TUC H4R 1 H4R 2 H4TUR NET 1. 2. 3. 4. 5. Run Self Tests H4TU-C Loopup H4TU-C Loopup H4TU-R Loopup H4TU-R Loopup 6. 7. 8. 9. 10. 11. H4R1 Loopup Net H4R1 Loopup Cust H4R2 Loopup Net H4R2 Loopup Cust Equipment Jack = Customer BERT Test Functions

Net Cust Net Cust Selection:

Figure 17. Loopback and Test Commands Screen

61181413L2-5A

Issue 1, November 2003

15

The BERT Test Screen (Figure 18) is accessed by selecting the associated number on the Loopback and Test Commands menu. The following options are available on the BERT Test Screen: (Re)start Pattern Used to start (or restart) a test.

Stop Test This option is used to manually stop a test. Select Data Pattern This option is used to select the appropriate data test pattern for the desired results. Figure 19 shows this screen with the menu of test patterns.

Shelf: 1 Slot: 18 Total Access System Unacknowledged Alarms: MAJOR INFO Circuit ID: BERT Test Screen Test Results ---------------------------------------------------Test Direction: Customer Unframed Pattern Generation: OFF Pattern: QRSS Pattern Line Coding: B8ZS Bit Errors: 0000000 Bit Error Rate: 0.0E-08 Pattern Sync: N/A Pattern Sync Losses: 000 Test Length (HH:MM:SS): 02:00:00 Time Elapsed (HH:MM:SS): 00:55:12 ---------------------------------------------------1. (Re)start Pattern 2. Stop Test 3. Select Data Pattern 4. Enter Test Timeout 5. Toggle Test Direction Selection:

07/31/03 11:00

Figure 18. BERT Test Screen

Shelf: 1 Slot: 18 Total Access System Unacknowledged Alarms: MAJOR INFO Circuit ID: CUSTOMER Pattern Screen

07/31/03 11:02

Current Pattern = QRSS Pattern -------------------------------------1. 2. 3. 4. 5. 6. 7. 8. 63 Pattern 511 Pattern 2047 Pattern REV. 2047 Pattern 2^15 Pattern 2^20 Pattern QRSS Pattern 2^23 Pattern

Selection:

Figure 19. Select Data Pattern

16

Issue 1, November 2003

61181413L2-5A

Enter Test Timeout This option displays the Timeout Screen (Figure 20). The timeout can run for a specific duration by entering the hours and/or minutes, or can run indefinitely by entering 00:00. Toggle Test Direction When no test running, this option is used to toggle the test signal in the opposite direction (from customer to network and vice versa).

The BERT only runs unframed patterns. When the BERT is running, the BERT Test Screen is redisplayed with new options (see Figure 21). This allows the tester to generate errors from this test origination point to validate the test results.

Shelf: 1 Slot: 18 Total Access System Unacknowledged Alarms: MAJOR INFO Circuit ID: CUSTOMER Timeout Screen Test Timeout(Hr:Min) = 02:00 ---------------------------1. Change Timeout 02:00 02:00 *NOTE: When timeout is set to 00:00, the test will run indefinately.

07/31/03 11:41

Selection:

Figure 20. BERT Timeout Screen

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID: BERT Test Screen

09/02/03 17:24

Test Results ---------------------------------------------------Test Direction: Customer Unframed Pattern Generation: ON Pattern: 2^23 Pattern Line Coding: B8ZS Bit Errors: 0000000 Bit Error Rate: 0.0E-05 Pattern Sync: ACQUIRED Pattern Sync Losses: 000 Test Length (HH:MM:SS): 02:00:00 Time Elapsed (HH:MM:SS): 00:02:32 ---------------------------------------------------1. Number of Errors to Inject = 001 (Maximum=255) 2. Inject Bit Error 3. (Re)start

Selection:

Figure 21. BERT Inject Errors Screen


61181413L2-5A Issue 1, November 2003 17

The Performance Data Selection screens (Figure 22 and Figure 23) are used to select and display the historical HDSL4 and T1 performance data in several different registers. At each 15-minute interval, the performance information is transferred to the 15-minute performance data register.

This H4TU-C stores performance data in 15-minute increments for the last 24-hour period. At each 24-hour interval, the performance data is transferred into the 24hour performance data registers. The H4TU-C stores up to 31 days of 24-hour interval data. Both Line and Path data are available from these screens.

Shelf: 1 Slot: 1 Total Access System 04/17/02 01:50 Unacknowledged Alarms: None Circuit ID: Menu 15 Minute H4TUC DSX-1 Performance Data 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. Definitions Reset Data 15 Min Data 60 Min Data 24 Hr Data Line Data Path Data H4TUC DSX-1 H4TUC LOOP H4TUR LOOP H4TUR DS1 H4R #1 NETW H4R #1 CUST H4R #2 NETW H4R #2 CUST ES-L 000 000 000 ------------SES-L 000 000 000 ------------LOSS-L 000 000 000 ------------PDVS-L 000 000 000 ------------B8ZS-L 000 000 000 ------------CV-L 00000 00000 00000 -------------------------

01:45 01:30 01:15 01:00 00:45 00:30 00:15 00:00

___ ___ ___ ___ | C | |#1 | |#2 | | R | -8->| |-----| |-----| |---------------| |---> | |9 12| |13 14| |15 10| | <---| |-----| |-----| |---------------| |<-11 |___| |___| |___| |___| Selection:

Figure 22. Performance Data Selection Screen (15-Minute, Line)

Shelf: 1 Slot: 1 Total Access System 04/17/02 01:51 Unacknowledged Alarms: None Circuit ID: Menu 24 Hour H4TUC DSX-1 Performance Data 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. Definitions Reset Data 15 Min Data 60 Min Data 24 Hr Data Line Data Path Data H4TUC DSX-1 H4TUC LOOP H4TUR LOOP H4TUR DS1 H4R #1 NETW H4R #1 CUST H4R #2 NETW H4R #2 CUST ES-L 00000 ----------------------------SES-L 00000 ----------------------------LOSS-L 00000 ----------------------------PDVS-L 00000 ----------------------------B8ZS-L 00000 ----------------------------CV-L 0000000 -------------------------------------------

04/16 04/15 04/14 04/13 04/12 04/11 04/10

___ ___ ___ ___ | C | |#1 | |#2 | | R | -8->| |-----| |-----| |---------------| |---> | |9 12| |13 14| |15 10| | <---| |-----| |-----| |---------------| |<-11 |___| |___| |___| |___| Selection:

Figure 23. Performance Data Selection Screen (24-Hour, Path)


18 Issue 1, November 2003 61181413L2-5A

Abbreviations used in the Performance Data Screens are defined in Performance Data Definitions screens (Figure 24 and Figure 25).

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None Circuit ID: Performance Data Definitions H4TUC, H4TUR, and H4R LOOP Related: ES-L Errored Seconds SES-L Severely Errored Seconds UAS-L Unavailable Seconds DS1 and DSX-1 Line Related: ES-L Errored Seconds SES-L Severely Errored Seconds LOSS-L Loss of Signal Seconds PDVS-L Pulse Density Violation Secs B8ZS-L B8ZS Seconds CV-L Code Violation Count HDSL4 Framing CRC>=1 or LOSW>=1 CRC>=50 or LOSW>=1 >10 cont. SES-Ls

04/17/02 05:08

Superframe and Extended Superframe (BPV+EXZ)>=1 or LOS>= 1 (BPV+EXZ)>=1544 or LOS>=1 LOS>= 1 EXZ>=1; >7 zeros if B8ZS, >15 if AMI B8ZS coded signal received (BPV+EXZ) count

NOTE: Reverse video indicates invalid data due to a terminal restart (or power cycle), a data register reset, or a system date or time change.

N. P.

Next Previous

Selection:

Figure 24. Performance Data Definitions (HDSL4 Loop Related)

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None Circuit ID: Performance Data Definitions DS1 and DSX-1 Path Related: ES-P Errored Seconds SES-P UAS-P SAS-P ES-PFE CV-P Severely Errored Seconds Unavailable Seconds SEF/AIS Seconds Far End Errored Seconds Code Violation Count Superframe FE>=1 or SEF>=1 or AIS>=1 FE>=8 or SEF>=1 or AIS>=1 >10 cont. SES-Ps SEF>=1 or AIS>=1 n/a FE count

04/17/02 05:08

Extended Superframe CRC>=1 or SEF>=1 or AIS>=1 CRC>=320 or SEF>=1 or AIS>=1 >10 cont. SES-Ps SEF>=1 or AIS>=1 PRM bits G1-G6,SE, or SL=1, or RAI CRC error count

NOTE: Under a UAS-P condition, ES-P and SES-P counts are inhibited. Under a SES-L or SES-P condition, the respective CV-L or CV-P count is inhibited.

P.

Previous

Selection:

Figure 25. Performance Data Definitions (DS1 and DSX-1 Path Related)

61181413L2-5A

Issue 1, November 2003

19

On the Scratch Pad and Circuit ID screen (Figure 26), the circuit ID can be any alphanumeric string up to 25 characters in length. A Scratch Pad is available for storage of HDSL4 circuit specific notes, and can hold 50 alphanumeric characters in any combination. The Alarm History screens are divided into three separate screens: T1 Alarm History (Figure 27)

Facility Alarm History (Figure 28) HDSL4 Span History (Figure 29)
T1 Alarm History screen (Figure 27) displays the

following: DSX-1/DS1 Red Alarm DSX-1/DS1 Yellow Alarm DSX-1/DS1 Blue Alarm

Shelf: 1 Slot: 1 Total Access System Unacknowledged Alarms: None CIRCUIT ID: ABC123

01/25/02 09:22

Current Scratch Pad: New Scratch Pad =

New Circuit ID =

Begin typing to change Circuit ID field

Press ESC to Exit.

Figure 26. Scratch Pad and Circuit ID Screen

Shelf: 1 Slot: 22 Total Access System 06/02/03 00:31 Unacknowledged Alarms: MINOR INFO Circuit ID: T1 Alarm History LOCATION ALARM FIRST LAST CURRENT COUNT -------------------------------------------------------------------------------H4TU-C RED(LOS/LOF) 01/01/00 00:00:05 01/01/00 00:00:05 Alarm 001 (DSX-1) YELLOW(RAI) OK 000 BLUE(AIS) OK 000 H4TU-R RED(LOS/LOF) 06/01/03 23:46:22 06/01/03 23:46:22 Alarm 001 (DS1) YELLOW(RAI) OK 000 BLUE(AIS) OK 000

-------------------------------------------------------------------------------1. T1 Alarm C. Clear T1 Alarms 2. Facility Alarm 3. Span H4TUC to H4TUR Selection:

Figure 27. T1 Alarm History Screen


20 Issue 1, November 2003 61181413L2-5A

The Facility Alarm History screen (Figure 28) displays the following: DC Open Over-current (short) Ground fault Power cycle

HDSL4 Span History screen (Figure 29) displays the

following: Loss of Sync for each HDSL4 receiver Margin Threshold Alarm for each HDSL4 receiver Attenuation Threshold Alarm for each HDSL4 receiver

Shelf: 1 Slot: 1 Total Access System 05/15/02 18:07 Unacknowledged Alarms: MAJOR MINOR INFO Circuit ID:1181412L4 Facility Alarm History LOCATION ALARM FIRST LAST CURRENT COUNT -------------------------------------------------------------------------------FACILITY DC OPEN 01/01/00 14:00:01 05/02/03 13:15:01 OK 002 FACILITY OVER-CURRENT OK 000 FACILITY GROUND FAULT OK 000 H4TU-C H4TU-R POWER CYCLE POWER CYCLE 01/01/00 05/02/03 14:00:01 08:33:33 05/06/03 05/02/03 09:00:01 08:33:33 OK OK 004 001

-------------------------------------------------------------------------------1. T1 Alarm 4. Span H4R1 to H4TUR 2. Facility Alarm C. Clear Facility Alarms 3. Span H4TUC to H4R1 Selection:

Figure 28. Facility Alarm History Screen

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22 Unacknowledged Alarms: None CIRCUIT ID:ABC123 HDSL4 Span History LOCATION ALARM FIRST LAST CURRENT COUNT -------------------------------------------------------------------------------SPAN C-H1 L1 LOS OK 000 L2 LOS OK 000 H4TU-C H4R1 NET L1 L2 L1 L2 MRGN MRGN MRGN MRGN OK OK OK OK 000 000 000 000

H4TU-C

L1 ATTEN OK 000 L2 ATTEN OK 000 H4R1 NET L1 ATTEN OK 000 L2 ATTEN OK 000 -------------------------------------------------------------------------------1. T1 Alarm 4. Span H4R1 to H4R2 2. System Alarm 5. Span H4R2 to H4TU-R 3. Span H4TUC to H4R1 C. Clear Span Alarms Selection:

Figure 29. HDSL4 Span History Screen

61181413L2-5A

Issue 1, November 2003

21

The Event History screen (Figure 30), option 8 on the Total Access main menu, provides history log of HDSL4 circuit events, including user-initiated events from the SCU control.

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22 Unacknowledged Alarms: None CIRCUIT ID: ABC123 Num Description of Event Date Time ----------------------------------------------------------------1. H4TU-C Powered Up 01/25/02 09:22:00

Page Number: 1/ 1 Number of Events: 1 ----------------------------------------------------------------'P' - Previous Page 'H' - Home 'R' - Reset Events 'N' - Next Page 'E' - End Selection:

Figure 30. Event History Screen

22

Issue 1, November 2003

61181413L2-5A

The System Status/PM Report screen (Figure 31), option 9 on the Total Access main menu, offers four types of reports on performance monitoring: 1. Full System/History Report 2. Current Status Report 3. System Configuration Report 4. Alarm/Event History Selecting a report type will display all the reports for that category on the screen at once.
4. 5. 6. 7. 8. 9. 10. 11. 12.

The Clear PM and Alarm Histories option (Figure 32), option 10 on the Total Access main menu, initializes data from performance monitoring and alarm histories. When this option is selected, the following prompt displays: This will clear the history data for all elements in the circuit. Are you sure (Y/N)?

Loopbacks and Test Performance Monitoring Scratch Pad, Ckt ID Alarm History Event History System Status/PM Report Clear PM and Alarm Histories Troubleshooting Flash Upgrade

Selection:

Enable data logging now. Select Report Type or Press Escape to cancel: 1) Full System/History Report 2) Current Status Report 3) System Configuration Report 4) Alarm/Event History

Figure 31. System Status/PM Report Screen


Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: MAJOR INFO Circuit ID: HDSL4 Main Menu 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. HDSL4 Unit Information Provisioning Status Loopbacks and Test Performance Monitoring Scratch Pad, Ckt ID Alarm History Event History System Status/PM Report Clear PM and Alarm Histories Troubleshooting Flash Upgrade 09/11/03 15:22

This will clear the history data for all elements in the circuit. Are you sure (Y/N)? Selection: 10

Figure 32. Clear PM and Alarm Histories Screen


61181413L2-5A Issue 1, November 2003 23

The Troubleshooting screen (Figure 33) compiles information received from all facilities and equipment in the circuit and presents them in both real-time and 7-day historical format.

The Troubleshooting Guidance screen (Figure 34), option 1 on the Troubleshooting screen, analyzes this information and makes repair recommendations.

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID: Troubleshooting

09/03/03 15:22

For HELP based on detected problems, select Troubleshooting Guidance from the list below. If further assistance is needed, contact ADTRAN Tech Support.

Hours: Normal 7am - 7pm CST Emergency 7 days x 24 hours Phone: 800.726.8663 / 888.873.HDSL Fax: 256.963.6217

1. Troubleshooting Guidance 2. General Information

Figure 33. Troubleshooting Screen

Shelf: 1 Slot: 14 Unacknowledged Alarms:

Total Access System INFO Facility DC Open

09/03/03 15:23

- A DC Open condition is often caused by a lack of current flow on the DSL loops. The condition should be resolved when an H4TUR (or H4R) is installed. - If open is not due to absence of equipment, verify wiring in the H4TUR (or H4R) housing. If still open, troubleshoot facility wiring for an open circuit. Looking toward the CO, you should see approximately 190 volts across T/T1 and R/R1 at any point. Also, if HDSL4 equipment is connected you should see a short on both pairs in both directions. If not an open circuit still exists. - If wiring and shelf OK, connect H4TUR at the frame and verify DSL sync can be achieved. If not, replace the H4TUC and H4TUR one at a time to identify the problem.

Figure 34. Troubleshooting Guidance Screen

24

Issue 1, November 2003

61181413L2-5A

The General Information screen (Figure 35) displays the Loop Deployment Guidelines for this type of circuit. Should trouble occur on the circuit, many test details are available here. Ability to download new firmware for the unit is available via the H4TU-C Flash Image screen (Figure 36). This feature allows the download and installation

of a firmware upgrade. Any existing provisioning setting will be retained, while new provisioning items will assume the factory default settings. Prior to installing, the H4TU-C will confirm that the firmware is correct. When initiated, setup instructions will be displayed on the craft access terminal.

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID:

09/03/03 15:22

HDSL4 Loop Guidelines for optimum operation ------------------------------------------Non-loaded cable pair Single bridge tap < 2Kft Total bridge taps < 2.5Kft Power influence <= 80 dBrnC Longitudinal Balance >= 60dB (If using Wideband test at 196 Khz >= 40dB) Foreign DC Voltage (t-r,t-g,r-g) < 3VDC Loop Resistance <= 1000 ohms 1st segment Loop Resistance <= 920 ohms 2nd segment The following guidelines are provided as a recommendation and may be superseded by internal deployment guidelines Margin >= 6 dB Attenuation (1st Segment) H4TUC <= 30 dB, H4TUR/H4R <= 32 dB Attenuation (2nd or 3rd Segment) H4TUR/H4R <= 28dB

Selection:

Figure 35. General Information Screen

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID:HntsvlALMn0103 SW Ver H4TU-C Flash Image: A01 Checksum DD85

09/03/03 15:25

Software Update 1. 2. 3. Download H4TU-C via Y-Modem Download H4TU-C via TFTP Boot Block Status and Overwrite Password

Selection:

Figure 36. Total Access 3000 H4TU-C Flash Image Screen


61181413L2-5A Issue 1, November 2003 25

The Download H4TU-C via Y-Modem screen (Figure 37) is used to initiate a Y-Modem file transfer from the computer connected to the SCU craft access port to the H4TU-C. This file is transferred to the SCU and downloaded to the H4TU-C at the SCU craft port baud rate. Therefore, a higher-speed connection to the SCU is recommended (typically 115200 baud) to reduce file

download times. At 115200 baud, a typical flash download to the H4TU-C will take less than 3 minutes. The file downloaded to the H4TU-C via the SCU should be of the .bin file type only and will be provided for feature enhancements/additions and bug fixes. Figure 38 shows a Flash upgrade session in progress.

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID:HntsvlALMn0103

09/03/03 15:25

Download H4TU-C via Y-Modem This utility programs the H4TUC. The VT100 terminal emulation program used must support Y-Modem file transfers and have access to the software binary file (*.bin).

1. 2.

Start Transfer Abort

Selection:

Figure 37. Download H4TU-C via Y-Modem

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: MAJOR INFO Circuit ID:

09/11/03 15:54

...Requesting SCU maintenance channel for Flash Upgrade process

Setup Instructions: [Note: Your terminal program may differ slightly] 1. Select "Send File" from Transfer options. 2. Set "Transfer Protocol" to the following: Xmodem(CRC) or Ymodem 3. Select appropriate binary file (*.BIN) to upload. 4. Upload File. [Note: =CCCC The screen will start displaying C's - this is normal.]

Figure 38. Flash Upgrade, Y-Modem in Progress

26

Issue 1, November 2003

61181413L2-5A

The Download H4TUC via TFTP screen (Figure 39) is used to perform a TFTP file transfer from a remotely located computer/server to the H4TU-C. During TFTP transfers, the SCU continues to act as an intermediary to receive the file data from the remote computer and then send it to the H4TU-C unit. Before initiating a TFTP transfer from the menu screen, first enter the TFTP remote filename that is listed on H4TU-C TFTP menu (option 1). The IP address of the remotely located computer must also be set from the network management menu on the SCU NOTE Access the SCU menu system to configure the IP address as this is not an H4TU-C menu option. In addition, the Ethernet interface of the SCU must also be provisioned properly for TFTP transfers.

The Ethernet interface settings allow the SCU to communicate properly over the Ethernet network in which it is installed. Without setting these items up properly, neither Telnet sessions nor remote TFTP file transfers will be available. Refer to the appropriate SCU Installation and Maintenance Practice for details on Ethernet settings. Once the H4TU-C and SCU have been provisioned properly for the TFTP file transfer, select option 2, Start Transfer, from the Download H4TUC via TFTP screen to initiate the TFTP file transfer from the remotely located computer to the H4TU-C. TFTP file transfers are typically faster than Y-Modem transfers. Once the SCU receives the file from the remote computer, the file is sent from the SCU to the H4TU-C to be downloaded (typically less than 2 minutes). TFTP transfers can also be initiated remotely using SNMP. This option totally eliminates the need to physically be located at the Total Access 3000 shelf to update the H4TU-C.

Figure 37.

Flash Upgrade, YModem in Progress

Shelf: 1 Slot: 14 Total Access System Unacknowledged Alarms: INFO Circuit ID:HntsvlALMn0103

09/03/03 15:25

Download H4TUC via TFTP This utility programs the H4TUC. You must set the SCU to the IP address of the TFTP server that has the firmware binary file (*.bin).

1. 2. 3.

Remote Filename = 1181413l1_a01.bin Start Transfer Abort

Figure 39. Download H4TUC via TFTP

61181413L2-5A

Issue 1, November 2003

27

The Boot Block Status and Overwrite Password screen (Figure 40) provides a method by which the bootcode can be updated on the H4TU-C. The bootcode is seldom changed with new download code.

The bootcode is the small piece of code that allows firmware upgrades on the H4TU-C unit. If it becomes corrupted, the H4TU-C will require factory service to restore it to a functional state (refer to the Warranty and Customer Service section). However, in the rare case to provide some new bootcode feature, this screen may be required to allow the bootcode to be overwritten by the newly downloaded firmware.

Shelf: 1 Slot: 14 Total Access System 09/09/03 14:58 Unacknowledged Alarms: MAJOR INFO Circuit ID:HntsvlALMn0103 Boot Block Overwrite Password Boot Block Type Current Password: NOT LOCKABLE

The current password is NOT correct To change the password, begin typing now or press ESC to exit this screen. WARNING: Overwriting the boot code involves some risk! Since the boot block is the small piece of code responsible for allowing firmware upgrades, overwriting the boot code with incorrect or incomplete code will render this linecard useless and will require factory service to restore the linecard to an operational state.

Selection:

Figure 40. Boot Block Status and Overwrite Password

28

Issue 1, November 2003

61181413L2-5A

7. HDSL4 DEPLOYMENT GUIDELINES The different segments of an HDSL4 circuit are defined in Figure 41.

to those guidelines on an as-necessary basis to ensure optimum performance. Designing a circuit with loop attenuation greater than the recommended maximum loss may result in compromised reliability of that loop. Follow the guidelines in this section to ensure that the circuit meets basic requirements: 1. 2. 3. 4. All loops are nonloaded only. Any single bridged tap is limited to 2 kft. Total bridged tap length is limited to 2.5 kft. Bridged tap within 1000 feet of units may affect performance of the circuit. 5. Loop Attenuation Limits. See Table 7. 6. DSL-Recommended Range Limits. See Table 8 and Table 9. NOTE In three segment circuits (two H4Rs), individual segment resistance values must be verified. Refer to number 7, Resistance Values, on the next page.

Figure 41. HDSL4 Circuit Segments The ADTRAN HDSL4 system provides DS1-based services over loops designed to comply with the guidelines given below. These guidelines apply to the following circuit configurations: a single segment or an HDSL4 circuit with no H4Rs, a circuit having two segments (with one H4R), or a circuit having three segments (with two H4Rs). The guidelines reflected herein are for worst-case scenarios, that is, for loops that contain a maximum amount of disturbers, noise, etc. Actual deployment guidelines may vary based on local policy. Please refer

Table 7. Attenuation limits


Recommended Maximum Upstream 1st segment 2nd and 3rd segment 30 dB 28 dB Downstream 32 dB 28 dB

Table 8. Range Limits: 26 Gauge / 70F / PIC


26 Gauge 1st segment 2nd segment 3rd segment Recommended Maximum 10,470 ft. 9,865 ft. 9,865 ft. (see note above)

Table 9. Range Limits: 24 Gauge / 70F / PIC


26 Gauge 1st segment 2nd segment 3rd segment Recommended Maximum 14,770 ft. 14,050 ft. 14,050 ft. (see note above)

61181413L2-5A

Issue 1, November 2003

29

7. Resistance Values. See Table 10. Each of the three segments associated with span powering two H4Rs and a H4TU-R must satisfy the DC resistance budgets in addition to the recommended insertion loss and loop attenuation requirements. In general, 22 and 19 AWG segments will be restricted by their loop attenuation while the DC resistance will restrict the segment reach for 26 and 24 AWG. When designing a dual H4R loop, the first segment should have lower DC resistance than the second segment. Single H4R spans do not require any restriction due to DC resistance.

NOTE A circuit that otherwise meets attenuation and insertion loss requirements for cable reach will encounter span powering problems if resistance values are excessive. The segment resistance ( segment) is determined using this equation: segment = L26 * 26 + L24 * 24 + L22 * 22 + L19 * 19 where L# is the length of # AWG cable (kft., excluding bridged taps) and 26 is the DC resistance of #AWG cable.

Table 10. Single Pair DC Resistance Value


Resistance (ohms/kft) AWG 19 22 24 26 70F 16.465 33.006 52.498 83.475 90F 17.183 34.446 54.789 87.117 120F 18.261 36.606 58.225 92.581 140F 18.979 38.046 60.516 96.223

Note: Interpolated between 70F and 120F data. Extrapolated from 70F and 120F data.

30

Issue 1, November 2003

61181413L2-5A

Once the resistance of each segment is confirmed, refer to Figure 42 to decide if the H4TU-C is capable of span powering two H4Rs and one H4TU-R. Alternatively, the DSL Assistant program will automatically calculate this and report any violations. To utilize the graph shown in Figure 42, perform the following steps: a. Find the line on the graph that represents the known third segment resistance. These are the lines running diagonally across the graph labeled 300 1100 ohms. This line represents the upper limit for two H4Rs plus H4TU-R span powering. b. Find the first segment resistance on the vertical axis.

c. Find the second segment resistance on the horizontal axis. d. Find the instance where the two points from step b and step c meet on the graph. The point found in step d must be below the upper limit line defined by the third segment measurement in step a. If the instance where these two points is above this line, the H4TU-C cannot span power two H4Rs and the H4TU-R. NOTE These measurements represent only one of the two HDSL4 pairs.

Figure 42. Resistance Budget Span Powering Two Repeaters

61181413L2-5A

Issue 1, November 2003

31

An example problem is illustrated in Figure 43. For this example, begin with three known measurements: 600 ohms first segment resistance, 700 ohms second segment resistance, and 900 ohms third segment resistance. Refer to Figure 43 and the following steps to solve the example problem: a. Find the 900 ohms third segment resistance line on the graph. This line is depicted in bold in Figure 43. This line is the upper span power limit.

b. Find the 600 ohms first segment resistance point on the vertical axis. c. Find the 700 ohms second segment resistance point on the horizontal axis. d. Find the instance on the graph where the points from step b and step c meet. e. If this point is below the bold line defined in step a, a circuit with these parameters is capable of span powering two H4Rs and one H4TU-R.

Figure 43. Resistance Budget Span Powering (Example)

32

Issue 1, November 2003

61181413L2-5A

8. Insertion Loss limits. See Table 11. The asymmetric nature of the HDSL4 TC-PAM line code necessitates that insertion loss be verified at four separate frequencies. Verifying at only 196 kHz will not insure proper circuit performance. 9. Field Technician Simplified Loop Qualification Procedure. See Table 12 and Table 13. For each of the four (or three for second and third segment) measured insertion loss values, compute the difference between the recommended

maximum loss and the measured loss (rec minus measured). If all differences are positive, then the loop meets the performance criteria. If any one of the difference values is negative (measured loss is more than rec maximum loss), then the sum of the differences must be at least +3dB for 1st segment or +1 dB for 2nd/3rd segment. If neither of these criteria is satisfied, then the loop is suspect and may not provide robust HDSL4 deployment.

Table 11. HDSL4 Insertion Loss Values (Based upon 26 AWG cable)
Frequency (KHz) 50 80 130 196 1st Segment Loss (dB) 29.8 34.2 37.0 40.8 2nd/3rd Segment Loss (dB) 28.0 32.2 34.8 N/A

Table 12. Single Span and First Segment of Repeatered Loop (Based upon 11.1 kft. of 26 AWG cable)
Frequency (kHz) 50 80 130 196 Recommended Maximum Loss (dB) 29.8 34.2 37.0 40.8
1

Measured Loss (dB)

Delta Loss (dB) (Max minus Measured)

Sum Delta Loss =

1.

If any single frequency insertion loss exceeds the maximum loss (delta loss < 0), then the sum of the three delta loss values must be > 3.0 dB.

Table 13. Second or Third Segment of Repeatered Loop (Based upon 11.1 kft. of 26 AWG cable)
Frequency (kHz) 50 80 130 50 Recommended Maximum Loss (dB) 28.0 32.2 34.8 28.0
1

Measured Loss (dB)

Delta Loss (dB) (Max minus Measured)

Sum Delta Loss =

1.

If any single frequency insertion loss exceeds the maximum loss (delta loss < 0), then the sum of the three delta loss values must be > 1.0 dB.

61181413L2-5A

Issue 1, November 2003

33

8. MAINTENANCE The Total Access 3000 HDSL4 Transceiver Unit for the Central Office requires no routine maintenance for normal operation. In case of equipment malfunction, use the front panel bantam jack connectors to help locate the source of the problem. ADTRAN does not recommend that repairs be attempted in the field. Repair services may be obtained by returning the defective unit to ADTRAN. Refer to the Warranty and Customer Service section for further information. 9. SPECIFICATIONS Specifications for the Total Access 3000 HDSL4 Transceiver Unit for the Central Office are detailed in Table 14. 10. WARRANTY AND CUSTOMER SERVICE ADTRAN will replace or repair this product within the warranty period if it does not meet its published specifications or fails while in service. Warranty information can be found at www.adtran.com/warranty. U.S. and Canada customers can also receive a copy of the warranty via ADTRANs toll-free faxback server at 877-457-5007. Request document 414 for the U.S. and Canada Carrier Networks Equipment Warranty. Request document 901 for the U.S. and Canada Enterprise Networks Equipment Warranty.

Refer to the following subsections for sales, support, CAPS requests, or further information. ADTRAN Sales Pricing/Availability: 800-827-0807 ADTRAN Technical Support Pre-Sales Applications/Post-Sales Technical Assistance: 800-726-8663 Standard hours: Monday - Friday, 7 a.m. - 7 p.m. CST Emergency hours: 7 days/week, 24 hours/day ADTRAN Repair/CAPS Return for Repair/Upgrade: (256) 963-8722 Repair and Return Address Contact Customer and Product Service (CAPS) prior to returning equipment to ADTRAN. ADTRAN, Inc. CAPS Department 901 Explorer Boulevard Huntsville, Alabama 35806-2807

34

Issue 1, November 2003

61181413L2-5A

Table 14. HDSL4 Total Access 3000 H4TU-C Specifications


Specification Loop Interface
Modulation Type Mode Number of Pairs Line Rate Baud Rate Loop Loss Bridged Taps Performance H4TU-C Transmit Power (Data) Level H4TU-C Transmit Power (Activation) Level Input Impedance Maximum Loop Resistance Return Loss 16 TC PAM Full duplex, partially overlapped echo canceling 2 1.552 Mbps 261.333 k baud Refer to the HDSL4 Deployment Guidelines section for additional measurements. Single Taps < 2000 ft., Total Taps < 2500 ft. Compliant with T1.418-2002 (HDSL4 Standard, issue 2) 14.1 0.5 dBm (0 to 400 kHz) 14.1 0.5 dBm (0 to 307 kHz) 135 ohms 1150 ohms (nonrepeatered circuit) 12 dB (50 kHz to 200 kHz)

Description

Network Interface
DS1 Transmit Level 0 dB (default), 7.5 dB, 15 dB DSX-1 Line Buildout 0-133 ft. ABAM (default) 133-266 ft. ABAM 266-399 ft. ABAM 399-533 ft. ABAM 533-655 ft. ABAM DSX-1 Line Code B8ZS (default), AMI

Power
Tested with the ADTRAN H4TU-C (P/N 1223426L2) and H4R (P/N 1223445L1) H4TU-C Total Power 48 VDC @ 197 mA with H4TU-R 48 VDC @ 348 mA with H4TU-R and one H4R H4TU-R Power Dissipation 5.5 watts with H4TU-R 6.4 watts with H4TU-R and one H4R Span Power 190 VDC (from H4TU-C) Class A2 compliant, GFI current limited at <5 mA, Loop current limited at between 150 to 160 mA Fusing 1.00 A (not field-replaceable)

Clock
Clock Sources DSX-1 derived (with HDSL4 frame bit stuffing) MUX fed Internal Clock Accuracy 25 ppm (Exceeds Stratum 4), meets T1.101 Timing Requirements

Tests
Diagnostics Self-Test, Local Loopback (H4TU-C), Remote Loopback (H4TU-R)

Physical
Total Access 3000 H4TU-C, Shelf-Mounted Dimensions 6 in. High, x 0.7 in. Wide, x 10 in. Deep Weight < 1 lb.

Environment
Operating Temperature (Standard) 40C to + 70C Storage Temperature 40C to + 85C

Compliance
UL 60950; GR-1089-CORE; GR-63-CORE; ANSI T1.418-2002, Issue 2; ANSI T1.102 (DS1 Interface)

Part Number
Total Access 3000 HDSL4 Transceiver Unit for the Central Office 1181413L2

61181413L2-5A

Issue 1, November 2003

35

This page is intentionally blank.

36

Issue 1, November 2003

61181413L2-5A

Appendix A HDSL4 Loopbacks

HDSL4 MAINTENANCE MODES This appendix describes operation of the HDSL4 system with regard to detection of inband and ESF facility data link loopback codes. Upon deactivation of a loopback, the HDSL4 system will synchronize automatically. Loopback Process Description In general, the loopback process for the HDSL4 system elements is modeled on the corresponding DS1 system process. Specifically, the H4TU-C loopback is similar to an Intelligent Office Repeater loopback, and the H4TU-R loopbacks are similar to an in-line T1 Repeater loopback. In-band control code sequences are transmitted over the DS1 link by either the insert or overwrite method. The HDSL4 elements respond to either method. The insert method produces periodic control sequences that are not overwritten by the DS1 framing bits.

The overwrite method produces periodic control sequences. However, once per frame, the framing bit overwrites one of the bits in the control sequence. The unit can detect the loopback activation or deactivation code sequence only if an error rate of 1E-03 or greater is present. Loopback Control Codes A summary of control sequences is given in Table A-1 and Table A-2. NOTE In all control code sequences presented, the inband codes are shown left-most bit transmitted first, and the esf data link codes with rightmost bit transmitted first.

61181413L2-5A

Issue 1, November 2003

A-1

Table A-1. HDSL4 Loopback Control Codes


Type Source1 Code2,3 3in7 (1110000) 4in7 (1111000) 2in6 (110000) 3in6 (111000) 6in7 (1111110) 5in7 (1111100) 4in6 (111100) 5in6 (111110) FF1E (1111 1111 0001 1110) 3F1E (0011 1111 0001 1110) FF04 (1111 1111 0000 0100) FF06 (1111 1111 0000 0110) 3F04 (0011 1111 0000 0100) 3F06 (0011 1111 0000 0110) FF02 (1111 1111 0000 0010) 3F02 (0011 1111 0000 0010) FF48 (1111 1111 0100 1000) FF48 (1111 1111 0100 1000) 1 in 3 (100) FF24 (1111 1111 0010 0100) Name Loopback data from network toward network in the HTU-R. Loopback data from network toward network in the HTU-C. Loopback data from network toward network in first HRE. Loopback data from network toward network in second HRE. Loopback data from customer toward customer in HTU-C. Loopback data from customer toward customer in HTU-R. Loopback data from customer toward customer in first HRE. Loopback data from customer toward customer in second HRE. Loopback data from network toward network at HTU-C. Loopback data from customer toward customer at HTU-C. Loopback data from network toward network at HRE1. Loopback data from network toward network at HRE2. Loopback data from customer toward customer at HRE1. Loopback data from customer toward customer at HRE2. Loopback data from network toward network at HTU-R. Loopback data from customer toward customer at HTU-R. Loopback data from customer toward customer at HTU-R.(FDL) Loopback data from network toward network at HTU-R. (FDL) Loopdown everything. Loopdown everything. (ESF-DL)

Abbreviated (N) (N) (N) (N) (C) (C) (C) (C) Wescom (N) (C) (N) (N) (C) (C) (N) (C) (C) (N) (N/C) (N/C)

1. 2. 3.

The Source column indicates which side of the interface the control codes are sent from. For example, an (N) indicates a network sourced code while a (C) indicates a customer sourced code. All codes are in-band unless labeled ESF-DL. All codes listed above must be sent for a minimum of 5 seconds to be detected and acted upon.

A-2

Issue 1, November 2003

61181413L2-5A

Table A-2. Loopback Control Codes


Function ARM (in-band) - also known as 2-in-5 pattern ARM (ESF Data Link) Code (Hex / Binary) 11000 (binary) FF48 or 1111 1111 0100 1000 sent in the Facility Data Link 11100 (binary) FF24 or 1111 1111 0010 0100 sent in the Facility Data Link D3D3 or 1101 0011 1101 0011 Response If the pattern is sent from the network, the units will arm, and the H4TU-R will loop up if NIU Loopback is enabled. If the pattern is sent from the network, the units will arm, and the H4TU-R will loop up if NIU Loopback is enabled. When sent from the customer, the units will arm. When sent from the network or customer, all units are removed from the armed state, and loopbacks will be released. When sent from the network or customer, all units are removed from the armed state, and loopbacks will be released. If armed, the H4TU-C will loop up, 2 seconds of AIS (all ones) will be transmitted, the looped data will be sent for 5 seconds, and then a burst of 231 logic errors will be injected. The burst of 231 logic errors will continue every 20 seconds as long as the D3D3 pattern is detected. When the pattern is removed, the unit will remain in loopback. If the pattern is reinstated, the injection of 231 logic errors will continue every 20 seconds. When sent from the network, all units currently in loopback will loop down. Armed units will not disarm. In order to behave like a smartjack, the H4TU-R will not loop down from a network loopback in response to the 9393 pattern if NIU Loopback is enabled. When the pattern is sent from the network, logic errors will be injected toward the network to indicate a loopback is present toward the network. The number of errors injected is determined by the nearest unit that is in loopback. As long as the pattern continues to be sent, errors are injected again every 20 seconds: H4TU-C H4R1 H4R2 H4TU-R Loopback Time Out Override1 D5D6 or 1101 0101 1101 0110 231 errors 10 errors 200 errors 20 errors

Disarm (in-band) - also known as 3-in-5 pattern Disarm (ESF Data Link)

H4TU-C Loop Up 1,2

Loop Down w/o Disarm

9393 or 1001 0011 1001 0011

Loopback Query 1

D5D5 or 1101 0101 1101 0101)

If the units are armed or a unit is currently in loopback when this pattern is sent from the network, the loopback time out will be disabled. As long as the units remain armed, the time out will remain disabled. When the units are disarmed, the loopback time out will revert to the previous loopback time out setting. If any element is in network loopback a bit error confirmation will be sent. H4TU-C H4R1 H4R2 H4TU-R 231 bps 110 bps 2200 bps 20 bps

61181413L2-5A

Issue 1, November 2003

A-3

Table A-2. Loopback Control Codes (Continued)


Function Span Power Disable1 Code (Hex / Binary) 6767 or 0110 0111 0110 0111 Response If the units are armed and 6767 is sent from the network, the H4TU-C will disable span power. If the pattern is sent from the network, the span power will be disabled as long as 6767 pattern is detected. Once the pattern is no longer received, the H4TU-C will reactivate span power. All units will then retrain and return to the disarmed and unlooped state. If one or more H4Rs are present, the H4R closest to the H4TU-C will loop up toward the network, 2 seconds of AIS (all ones) will be transmitted, the looped data will be sent for 5 seconds, and then a burst of 10 logic errors will be injected. The burst of 10 logic errors will continue every 20 seconds as long as the C741 pattern is detected. When the pattern is removed, the unit will remain in loopback. If the pattern is reinstated, the injection of 10 logic errors will continue every 20 seconds. If two H4Rs are present, the second H4R from the H4TU-C will loop up toward the network, 2 seconds of AIS (all ones) will be transmitted, the looped data will be sent for 5 seconds, and then a burst of 200 logic errors will be injected. The burst of 200 logic errors will continue every 20 seconds as long as the C754 pattern is detected. When the pattern is removed, the unit will remain in loopback. If the pattern is reinstated, the injection of 200 logic errors will continue every 20 seconds. If armed, the H4TU-R will loop up toward the network, 2 seconds of AIS (all ones) will be transmitted, the looped data will be sent for 5 seconds, and then a burst of 20 logic errors will be injected. The burst of 20 logic errors will continue every 10 seconds as long as the C742 pattern is detected. When the pattern is removed, the unit will remain in loopback. If the pattern is reinstated, the injection of 20 logic errors will continue every 20 seconds.

First H4R Loop Up 1,2

C741 1100 0111 0100 0001

Second H4R Loop Up 1,2

C754 1100 0111 0101 0100

H4TU-R Address 20 for Extended Demarc 1,2

C742 1100 0111 0100 0010

Units must be armed with 11000b or FF48h before this code will work. Loopback and error injection will only occur if the in-band code is received by the unit that is to go into loopback. In other words, if another loopback blocks the in-band code from being transmitted to the unit that is to go into loopback, loopback and error injection will not occur. Note: All codes listed above must be sent for a minimum of 5 seconds to be detected and acted upon

1. 2.

A-4

Issue 1, November 2003

61181413L2-5A

Appendix B Front Panel DSX and MUX Mode Test Access

GENERAL Figure B-1 through Figure B-3 are DSX-1 fed modes of operation, and Figure B-4 through Figure B-7 are MUX fed modes of operation. From the Provisioning menu (Figure 12), select option 16 to choose the Network Source as MUX fed or DSX fed. When performing intrusive MUX mode testing, the equipment jack (EQ) on the front panel can be configured to access the signal going to the Network or the Customer. From the Loopbacks and Test Commands screen (Figure 17), select option 10 to configure the equipment jack for network or customer. Every time the H4TU-C is powercycled, it will default to the customer direction. NOTE The H4TU-C must be provisioned for the Outof-Service, Maintenance service state when intrusive bantam jack testing is being performed. DSX MODE TEST ACCESS DSX MON, Tx to Customer The Rx of the BERT receives data from the TX MON jack (Figure B-1). This data has a monitor jack impedance of 432 ohms and comes from the backplane Network T1 DSX (the data that would go toward the customer). The BERT Tx is not used. This test is nonintrusive.

DSX MON, Rx from Customer The Rx of the BERT receives data from the RX MON jack (Figure B-2). This data has a monitor jack impedance of 432 ohms and comes from the customeroriginated data. The BERT Tx is not used. This test is nonintrusive.

To MUX From MUX TX


EQ

X
RX

T X R X T X R X MON

To DSX From DSX


432

To CUST From CUST


432

T1 BERT

Figure B-2. DSX Mon, Rx from Customer DSX EQ, Tx to Customer and Rx from Customer The Tx of the BERT goes to the TX EQ jack, and the Rx of the BERT goes to the RX EQ jack (Figure B-3). The TX EQ data from the BERT is sent to the Customer. The RX EQ data to the BERT is data from the Customer. The MON jack Tx and Rx are 432 ohm replicas of the EQ Tx and Rx direct connections. This test is intrusive, as it connects the EQ jacks directly to and from the Customer data.

To MUX From MUX To MUX From MUX TX


EQ

TX RX

EQ T X R X

To DSX From DSX


432

X
RX

T X R X

To DSX From DSX


432

T X R X

T X R X MON

To CUST From CUST


432

To CUST From CUST


432

MON

T1 BERT

T1 BERT

Figure B-1. DSX MON, Tx to Customer

Figure B-3. DSX EQ, Tx to Customer and Rx from Customer

61181413L2-5A

Issue 1, November 2003

B-1

MUX MODE TEST ACCESS MUX MON, Tx to Customer The Rx of the BERT receives data from the TX MON EQ jack (Figure B-4). This data is a copy of the data that the H4TU-C will transmit to the customer. The Tx of the BERT is not used. This test is nonintrusive.

NOTE Via the Test Screen, ensure that the equipment jack (EQ) is in the To Network mode. In the To Network mode, AIS (unframed all ones) is sent in the customer direction.

To MUX From MUX TX


EQ

To MUX From MUX

X
RX

T X R X

To DSX From DSX


432

TX RX

EQ T X R X

To DSX From DSX


432

T X R X MON

To CUST From CUST


432

T X R X MON

To CUST From CUST


432

T1 BERT T1 BERT

Figure B-4. MUX MON, Tx to Customer MUX MON, Rx from Customer The Rx of the BERT receives data from the RX MON jack Figure B-5). This data is 432 ohm copy of the data that the H4TU-C will receive from the customer and route to the Total Access 3000 shelf's MUX (Network). The Tx of the BERT is not used. This test is nonintrusive.

Figure B-6. MUX EQ, Tx to Network and Rx from Network MUX EQ, Tx to Customer and Rx from Customer The Tx of the BERT is connected to the EQ TX jack, and the Rx of the BERT is connected to the RX EQ jack (Figure B-7). The Tx of the BERT is then substituted for the data that the H4TU-C sends to the Customer. The Rx of the BERT receives data directly from the Customer. The MON Tx and Rx jacks are 432 ohm impedance copies of the EQ jack Tx and Rx. This test is intrusive. NOTE Via the Test Screen, ensure that the equipment jack (EQ) is in the To Customer mode. In the To Customer mode, AIS (unframed all ones) is sent in the Network direction.

To MUX From MUX TX


EQ

X
RX

T X R X T X R X MON

To DSX From DSX


432

To CUST From CUST


432

T1 BERT

Figure B-5. MUX MON, Rx from Customer MUX EQ, Tx to Network and Rx from Network The Tx of the BERT is connected to the EQ TX jack, and the Rx of the BERT is connected to the RX EQ jack (Figure B-6). The Tx of the BERT is then substituted for the data that the H4TU-C sends to the Total Access 3000 shelf's MUX (Network). The Rx of the BERT receives data directly from the MUX (Network). The MON TX and RX jacks are 432 ohm impedance copies of the EQ jack Tx and Rx. This test is intrusive.
To MUX From MUX TX RX
EQ T X R X

To DSX From DSX


432

T X R X MON

To CUST From CUST


432

T1 BERT

Figure B-7. MUX EQ, Tx to Customer and Rx from Customer


B-2 Issue 1, November 2003 61181413L2-5A