Total Access 3000 HDSL4 Transceiver Unit for the Central Office Installation and Maintenance Practic...

Section 61181413L2-5AIssue 1, November 2003

CLEI Code: S1C4WTXD_ _

61181413L2-5A 1Trademarks: Any brand names and product names included in this document are trademarks, registered trademarks, or trade names of their respective holders.

CONTENTS1. General ..................................................................................... 22. Connections .............................................................................. 33. Installation ................................................................................ 44. Provisioning.............................................................................. 65. HDSL4 System Testing............................................................ 76. SCU Control Port Operation-HDSL4....................................... 87. HDSL4 Deployment Guidelines............................................. 298. Maintenance ........................................................................... 349. Specifications ......................................................................... 3410. Warranty and Customer Service............................................. 34Appendix A. HDSL4 Loopbacks .............................................. A-1Appendix B. Front Panel DSX and MUX Mode Test Access .. B-1

FIGURESFigure 1. ADTRAN Total Access 3000 H4TU-C........................ 1Figure 2. TScan Diagnostic Capabilities...................................... 3Figure 3. H4TU-C Span Powering Diagram................................ 3Figure 4. H4TU-C Bantam Jack Arrangement............................. 7Figure 5. HDSL4 Loopbacks ....................................................... 8Figure 6. RS-232 (DB9) Pin Assignments ................................... 8Figure 7. Total Access System Logon Screen.............................. 9Figure 8. Total Access Main Menu.............................................. 9Figure 9. Access Module Menu ................................................. 10Figure 10. HDSL4 Main Menu .................................................... 10Figure 11. Unit Information Screen ............................................. 11Figure 12. Provisioning Menu, Page 1......................................... 11Figure 13. Provisioning Menu, Page 2......................................... 12Figure 14. Span Status Screen...................................................... 12Figure 15. Detailed Status Screen ................................................ 13Figure 16. Auto In Service Status Screen .................................... 13Figure 17. Loopback and Test Commands Screen....................... 15Figure 18. BERT Test Screen ...................................................... 16Figure 19. Select Data Pattern...................................................... 16Figure 20. BERT Timeout Screen................................................ 17Figure 21. BERT Inject Errors Screen ......................................... 17Figure 22. Performance Data Selection Screen

(15-Minute, Line)........................................................ 18Figure 23. Performance Data Selection Screen (24-Hour, Path) . 18Figure 24. Performance Data Definitions .................................... 19Figure 25. Performance Data Definitions .................................... 19Figure 26. Scratch Pad and Circuit ID Screen ............................. 20Figure 27. T1 Alarm History Screen............................................ 20Figure 28. Facility Alarm History Screen .................................... 21Figure 29. HDSL4 Span History Screen ...................................... 21Figure 30. Event History Screen .................................................. 22Figure 31. System Status/PM Report Screen ............................... 23Figure 32. Clear PM and Alarm Histories Screen........................ 23Figure 33. Troubleshooting Screen .............................................. 24Figure 34. Troubleshooting Guidance Screen.............................. 24Figure 35. General Information Screen........................................ 25Figure 36. Total Access 3000 H4TU-C Flash Image Screen....... 25Figure 37. Download H4TU-C via Y-Modem ............................. 26Figure 38. Flash Upgrade, Y-Modem in Progress ....................... 26

Figure 39. Download H4TUC via TFTP...................................... 27Figure 40. Boot Block Status and Overwrite Password............... 28Figure 41. HDSL4 Circuit Segments ........................................... 29Figure 42. Resistance Budget Span Powering Two Repeaters .... 31Figure 43. Resistance Budget Span Powering (Example) ........... 32Figure B-1. DSX MON, Tx to Customer ................................... B-1Figure B-2. DSX Mon, Rx from Customer ................................ B-1Figure B-3. DSX EQ, Tx to Customer and Rx from Customer . B-1Figure B-4. MUX MON, Tx to Customer.................................. B-2Figure B-5. MUX MON, Rx from Customer............................. B-2Figure B-6. MUX EQ, Tx to Network and Rx from Network ... B-2Figure B-7. MUX EQ, Tx to Customer and Rx from Customer B-2

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

Figure 1. ADTRAN Total Access 3000 H4TU-C

1181413L2

EQ

MON

TX

RX

TX

RX

H T

UC

DSL 2

DSL 1

DSX/DS1

ALM

(GRN)(YEL)

(GRN)(YEL)

SFESF/

AMIB8ZS/

LBK

Total Access 3000 HDSL4 Transceiver Unit for the Central OfficeInstallation and Maintenance Practice

2 Issue 1, November 2003 61181413L2-5A

1. GENERALThis 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 HistoryThis is the initial issue of this practice. Future changes to this documentation will be explained in this subsection.

DescriptionThe 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.

x = any generic number

FeaturesThe 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.

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.

TScanThis unit is equipped to support the TScan feature, which provides data retrieval and diagnostic capabil-ities 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.

NOTEFor implementation of Tscan please contactyour 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

Table 1. ADTRAN HDSL4 Unit Compatibility

Part Number Description

122x424L2 T200 H4TU-R, Local Power

122x426L2 T200 H4TU-R, Span Power

122x441L1 T200 H4R Repeater

122x445L1 239 H4R Repeater

61181413L2-5A Issue 1, November 2003 3

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

Figure 2. TScan Diagnostic Capabilities

TScan allows operators to integrate this capability across multiple computing platforms with existing operating systems.

Auto In ServiceThe Total Access 3000 H4TU-C supports the Auto In-Service 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.

ComplianceTable 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.

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.

WARNINGUp to –200 VDC may be present on telecom-munications wiring. The DSX-1 interface isintended for connection to intra-buildingwiring only. Ensure chassis ground is properlyconnected.

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 appli-cable UL standards.

2. CONNECTIONSThe 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.

Figure 3. H4TU-C Span Powering Diagram

Table 2. Compliance Codes

Code Input Output

Power Code (PC) F C

Telecommunication Code (TC) – X

Installation Code (IC) A –

C

CO Outside Plant Facilities

R Open on either conductor

C R Open on both conductors

C R Short between T&R

C R Short to ground from eitheror both conductors

X

X

X

TC PAMHDSL4

SPAN POWERREGULATOR

SPAN CURRENT -185 VDC

T

R

T1

R1

LOOP 1(-191 VDC)

LOOP 2(-6 VDC)


3. INSTALLATION

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.

CAUTIONElectronic modules can be damaged byElectro-Static Discharge (ESD). Whenhandling modules, wear an antistatic dischargewrist strap to prevent damage to electroniccomponents. Place modules in antistaticpacking material when transporting or storing.When working on modules, always place themon an approved antistatic mat that is electri-cally 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 OptionsThe 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

CAUTIONDisabling the span power removes all voltagefrom the HDSL4 loop. This will result in anabsence of sealing current which could have anadverse effect on circuit continuity over anextended period of time.

Table 3. Total Access Backplane Connector Pinout

Slot HDSL4 LoopPair 1 and Pair 2(Customer Side)

DSX-1Pair 7 and Pair 8(Network Side)

1 1/33 1/33

2 2/34 2/34

3 3/35 3/35

4 4/36 4/36

5 5/37 5/37

6 6/38 6/38

7 7/39 7/39

8 8/40 8/40

9 9/41 9/41

10 10/42 10/42

11 11/43 11/43

12 12/44 12/44

13 13/45 13/45

14 14/46 14/46

15 15/47 15/47

16 16/48 16/48

17 17/49 17/49

18 18/50 18/50

19 19/51 19/51

20 20/52 20/52

21 21/53 21/53

22 22/54 22/54

23 23/55 23/55

24 24/56 24/56

25 25/57 25/57

26 26/58 26/58

27 27/59 27/59

28 28/60 28/60

C A U T I O N ! SUBJECT TO ELECTROSTATIC DAMAGE

OR DECREASE IN RELIABILITY.

HANDLING PRECAUTIONS REQUIRED.


Instructions for Installing the ModuleTo 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 left-hand 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 self-tests. Once the power up self-test is complete, the status LEDs will reflect the true state of the hardware.

Front Panel LEDsThe 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 Status Description

DSL 1/DSL 2

GreenRed

DSL Loop 1/Loop 2 sync, no errors currently detected, and signal margin ≥ 3 dBNo DSL Loop 1/Loop 2 sync, errors being detected, or signal quality < 3 dB

DSX/DS1 GreenRed

DSX-1 signal is present and synchronizedDSX-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

ALM OffRed

Yellow

No alarm condition detectedAlarm condition detected either locally (H4TU-C) or locally and remotely (H4TU-C and H4TU-R)Remote alarm condition detected

ESF/SF OffYellowGreen

Unit is provisioned for DS1 unframed operationUnit is provisioned for DS1 ESF framing modeUnit is provisioned for DS1 SF framing mode

B8ZS/AMI

YellowGreen

Unit is provisioned for B8ZS codingUnit is provisioned for AMI coding

LBK OffYellow

Unit is not in loopbackLocal H4TU-C loopback is active toward network or customer

1181413L2

EQ

MON

TX

RX

TX

RX

H T

UC

DSL 2

DSL 1

DSX/DS1

ALM

(GRN)(YEL)

(GRN)(YEL)

SFESF/

AMIB8ZS/

LBK


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

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

Table 5. Provisioning Options

Provisioning Option Option Settings Default Settings

1. DSX-1 Line Build Out 0-133 ft.133-266 ft.266-399 ft.399-533 ft.533-655 ft.

0 to 133 ft.

2. DSX-1/DS1 Line Code B8ZS, AMI B8ZS

3. DSX-1/DS1 Framing SF, ESF, Unframed, Auto ESF

4. Force Frame Conversion Disabled, Enabled Disabled

5. Smartjack Loopback Disabled, Enabled Enabled

6. Loopback Time Out None, 120 Min 120 Minutes

7. Latching Loopback Mode T1 (Disabled), FT1 (Enabled) T1 (Disabled)

8. DS1 Tx Level 0 dB, –7.5 dB, –15 dB 0 dB

9. Span Power Enabled, Disabled Enabled

10. Customer Loss Indicator AIS, Loopback, AIS/CI AIS/CI

11. Performance Reporting Messages None, SPRM, NPRM, AUTO (both) AUTO

12. Loop Attenuation Alarm Threshold 0 (Disabled), 1-99 dB 34 dB

13. SNR Margin Alarm Threshold 0 (Disabled), 1-15 dB 04 dB

14. Remote Provisioning Disabled, Enabled Enabled

15. Service State1 In-ServiceOut-of-Service, UnassignedOut-of-Service, Maintenance

Out-of-Service, Maintenance

16. Network Source DSX, MUX A, MUX B, Auto MUX DSX

17. External Alarms Enabled, Disabled Disabled

18. Auto In Service Disabled, Enabled Enabled

19. Auto IS Startup Period 1 hour, 4 hours, 8 hours, 24 hours 4 hours

20. Auto IS Off Period 1 hour, 4 hours, 8 hours, 24 hours 8 hours

1The 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.


H4TU-C Alarm OutputsEach 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-of-Service, 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 H4TU-C, all provisioning information is stored in the nonvol-atile 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 TESTINGThe 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 subsec-tions describe additional testing features.

H4TU-C Bantam JacksThe 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.

Figure 4. H4TU-C Bantam Jack Arrangement

H4TU-C LoopbacksThe 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.

DSX-1MON

Rx

H4TU-CDATAPUMP

LOOP DCPOWER SOURCE

DSX-1T

R

DSX-1T1

R1

HDSL4LOOP 1

HDSL4LOOP 2

H4TU-C

HDSL4LOOP 1

HDSL4LOOP 2

EQRx

DSX-1MON

Tx

EQTx


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.

6. SCU CONTROL PORT OPERATION-HDSL4H4TU-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 connec-tions.

The Total Access 3000 SCU provides a front panel-mounted 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.

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.

NOTEMany portable personal computers use power-saving programs that are known to interferewith applications running on the personalcomputer. If using a PC with terminalemulation capability, communication betweenthe PC and the HDSL4 unit may be periodi-cally disrupted if power saving programs arebeing used on the PC. The symptoms mayinclude misplaced characters appearing on thescreen and/or the occurrence of screen timeouts. These symptoms are not disruptive to theoperation of the circuit and are avoidable if thepower saving options are disabled or removed.

X

H4R2 Customer-Side Loopback

DSX-1

AIS H4TU-C H4R2

DS1

H4TU-RH4R1

X = Signal Inactive

H4R2 Network-Side Loopback

DSX-1

H4TU-C H4R2

DS1

AIS

AIS

H4TU-RH4R1

X

H4R1 Customer-Side Loopback

DSX-1

AIS H4TU-C H4R2

DS1

H4TU-RH4R1

H4R1 Network-Side Loopback

DSX-1

H4TU-C H4R2

DS1

H4TU-RH4R1

X

X

DSX-1

H4TU-C

LOCALLOOP

H4TU-C Network-Side Loopback

H4TU-R

H4TU-C

LOCALLOOP

H4TU-R Customer-Side Loopback

H4TU-R

H4TU-C

LOCALLOOP

H4TU-C Customer-Side Loopback

H4TU-R

X

X

DS1

DSX-1

H4TU-C

LOCALLOOP

H4TU-R Network-Side Loopback and/orH4TU-R NIU Loopback

H4TU-RX

DS1

DS1

DS1

X

AIS

X

H4R Customer-Side Loopback

DS1

H4TU-C

H4R Network-Side Loopback

H4TU-R

DS1DSX-1

H4R

DSX-1

AIS

DSX-1

AIS

DSX-1

AIS

AIS

AIS

X

H4TU-C H4TU-RH4R

6

7

8

9

1

2

3

4

5

TXD (Transmit Data)

SGN (Signal Ground)

RXD (Receive Data)


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.

Figure 7. Total Access System Logon Screen

Figure 8. Total Access Main Menu

Shelf: 1 Total Access System 01/25/02 10:23Unacknowledged Alarms: None

Total Access System

Account Name: Password:

Shelf: Total Access System 01/25/02 16:29Unacknowledged Alarms: None

Total Access

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

Selection:


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.

Figure 9. Access Module Menu

Figure 10. HDSL4 Main Menu

Shelf: 1 Total Access System 01/25/02 09:54Unacknowledged Alarms: None

Access Module Menus

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

Enter Channel Slot Number :

Inverse = Busy Modules

Shelf: 1 Slot: 14 Total Access System 09/03/03 14:57Unacknowledged Alarms: INFO Circuit ID:

HDSL4 Main Menu

1. HDSL4 Unit Information 2. Provisioning 3. Status 4. Loopbacks and Test 5. Performance Monitoring 6. Scratch Pad, Ckt ID 7. Alarm History 8. Event History 9. System Status/PM Report 10. Clear PM and Alarm Histories 11. Troubleshooting 12. Flash Upgrade

Selection:


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 twoseparate screens. Press N, and press ENTER todisplay the second page (Figure 13).

Figure 11. Unit Information Screen

Figure 12. Provisioning Menu, Page 1

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:21Unacknowledged Alarms: None Press ESC to return to previous menu

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 H4TU-C ADTN H4TU-R P/N: 1181413L2 P/N: 1223426L2 S/N: 123456789 S/N: 123456789 CLEI: SIC4WTXDAA CLEI: T1L7SEJAAA Manf: 01/01/2000 Manf: 01/01/2000 Ver: 24 1 A00000 Ver: 27 2 A00000

ADTN H4R1 ADTN H4R2 P/N: 1223445L1 P/N: 1223445L1 S/N: BB50A8343 S/N: BB50A8353 CLEI: T1R6TJEDAA CLEI: T1R6UJ3DAA Manf: 07/12/2003 Manf: 07/12/2003


Provisioning

1. DSX-1 Line Buildout = 0-133 Feet 2. DSX-1/DS1 Line Code = B8ZS 3. DSX-1/DS1 Framing = ESF 4. Forced Frame Conversion = Disabled 5. Smartjack Loopback = Enabled 6. Loopback Timeout = 120 Min 7. Latching Loopback Mode = T1 (Disabled) 8. DS1 TX Level = 0 dB 9. Span Power = Enabled 10. Customer Loss Indicator = AIS / CI 11. PRM Setting = AUTO 12. Loop Atten Alarm Thres = 34dB 13. SNR Margin Alarm Thres = 04dB 14. Remote Provisioning = Enabled 15. Service State = OOS Maintenance 16. Network Source = DSX N. Next Page Selection:


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.

Figure 13. Provisioning Menu, Page 2

Figure 14. Span Status Screen

Shelf: 1 Slot: 14 Total Access System 09/09/03 14:25Unacknowledged Alarms: MAJOR INFO Circuit ID:HntsvlALMn0103

Provisioning

17. External Alarms = Disabled 18. Auto In Service = Enabled 19. Auto IS Startup Period = 4 hours 20. Auto IS Off Period = 8 hours

D. Restore Factory Defaults P. Previous Page

Selection:

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22Unacknowledged Alarms: None CIRCUIT ID:ABC123 Span Status Screen

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

1. View Detailed Status 2. View Auto In Service Status

Selection:


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.

Figure 15. Detailed Status Screen

Figure 16. Auto In Service Status Screen

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22Unacknowledged Alarms: None CIRCUIT ID:ABC123 Detailed Status Screen

LOOP 1 LOOP 2 MARGIN ATTEN MARGIN ATTEN Interface (CUR/MIN/MAX) (CUR/MAX) (CUR/MIN/MAX) (CUR/MAX) --------- ------------- --------- ------------- --------- H4TUC 17/00/17 00/00 17/00/17 00/00 H4R1 NETW 17/00/17 00/00 17/13/17 00/00 H4R1 CUST 17/17/17 00/00 17/00/17 00/00 H4R2 NETW 17/00/17 00/00 17/13/17 00/00 H4R2 CUST 17/17/17 00/00 17/00/17 00/00 H4TUR 17/00/17 00/00 17/00/17 00/00

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

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

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 Status --------------- ------ DSL Loop Sync LOS

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

Selection:


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-of-Service 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 System Indications

Current Auto In Service State (Line 1) In-ServiceOut-of-Service, Maintenance

Auto In Service Status (line 2) Currently in startup periodCurrently in exiting periodOK, Startup Period COMPLETEDOK, Startup INCOMPLETE (forced in-service)

Auto In Service Criteria (line 3) DSL Loop Sync (T1 alarms ignored)DSL Loop Sync and absence of T1 alarms

Criteria (current status) DSL Loop Sync = OK or LOS (LOS shown in Figure 16)T1 Alarm Status = Alarm or OK


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.

Figure 17. Loopback and Test Commands Screen

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22Unacknowledged Alarms: None CIRCUIT ID:ABC123

Loopback and Test Commands

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

1. Run Self Tests 6. H4R1 Loopup Net 2. H4TU-C Loopup Net 7. H4R1 Loopup Cust 3. H4TU-C Loopup Cust 8. H4R2 Loopup Net 4. H4TU-R Loopup Net 9. H4R2 Loopup Cust 5. H4TU-R Loopup Cust 10. Equipment Jack = Customer 11. BERT Test Functions Selection:


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.

Figure 18. BERT Test Screen

Figure 19. Select Data Pattern

Shelf: 1 Slot: 18 Total Access System 07/31/03 11:00Unacknowledged 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:

Shelf: 1 Slot: 18 Total Access System 07/31/03 11:02Unacknowledged Alarms: MAJOR INFO Circuit ID: CUSTOMER Pattern Screen

Current Pattern = QRSS Pattern --------------------------------------

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

Selection:


• 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.

Figure 20. BERT Timeout Screen

Figure 21. BERT Inject Errors Screen

Shelf: 1 Slot: 18 Total Access System 07/31/03 11:41Unacknowledged 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.

Selection:

Shelf: 1 Slot: 14 Total Access System 09/02/03 17:24Unacknowledged Alarms: INFO Circuit ID: BERT Test Screen

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:


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 24-hour 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.

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

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

Shelf: 1 Slot: 1 Total Access System 04/17/02 01:50Unacknowledged Alarms: None Circuit ID: Menu 15 Minute H4TUC DSX-1 Performance Data

1. Definitions ES-L SES-L LOSS-L PDVS-L B8ZS-L CV-L 2. Reset Data 000 000 000 000 000 00000 3. 15 Min Data 01:45 000 000 000 000 000 00000 4. 60 Min Data 01:30 000 000 000 000 000 00000 5. 24 Hr Data 01:15 --- --- --- --- --- ----- 6. Line Data 01:00 --- --- --- --- --- ----- 7. Path Data 00:45 --- --- --- --- --- ----- 8. H4TUC DSX-1 00:30 --- --- --- --- --- ----- 9. H4TUC LOOP 00:15 --- --- --- --- --- ----- 10. H4TUR LOOP 00:00 --- --- --- --- --- ----- 11. H4TUR DS1 12. H4R #1 NETW 13. H4R #1 CUST ___ ___ ___ ___ 14. H4R #2 NETW | C | |#1 | |#2 | | R | 15. H4R #2 CUST -8->| |-----| |-----| |---------------| |---> | |9 12| |13 14| |15 10| | <---| |-----| |-----| |---------------| |<-11 |___| |___| |___| |___| Selection:

Shelf: 1 Slot: 1 Total Access System 04/17/02 01:51Unacknowledged Alarms: None Circuit ID: Menu 24 Hour H4TUC DSX-1 Performance Data

1. Definitions ES-L SES-L LOSS-L PDVS-L B8ZS-L CV-L 2. Reset Data 00000 00000 00000 00000 00000 0000000 3. 15 Min Data 04/16 ----- ----- ----- ----- ----- ------- 4. 60 Min Data 04/15 ----- ----- ----- ----- ----- ------- 5. 24 Hr Data 04/14 ----- ----- ----- ----- ----- ------- 6. Line Data 04/13 ----- ----- ----- ----- ----- ------- 7. Path Data 04/12 ----- ----- ----- ----- ----- ------- 8. H4TUC DSX-1 04/11 ----- ----- ----- ----- ----- ------- 9. H4TUC LOOP 04/10 ----- ----- ----- ----- ----- ------- 10. H4TUR LOOP 11. H4TUR DS1 12. H4R #1 NETW 13. H4R #1 CUST ___ ___ ___ ___ 14. H4R #2 NETW | C | |#1 | |#2 | | R | 15. H4R #2 CUST -8->| |-----| |-----| |---------------| |---> | |9 12| |13 14| |15 10| | <---| |-----| |-----| |---------------| |<-11 |___| |___| |___| |___| Selection:


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

Figure 24. Performance Data Definitions(HDSL4 Loop Related)

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

Shelf: 1 Slot: 1 Total Access System 04/17/02 05:08Unacknowledged Alarms: None Circuit ID: Performance Data Definitions

H4TUC, H4TUR, and H4R LOOP Related: HDSL4 Framing ES-L Errored Seconds CRC>=1 or LOSW>=1 SES-L Severely Errored Seconds CRC>=50 or LOSW>=1 UAS-L Unavailable Seconds >10 cont. SES-Ls

DS1 and DSX-1 Line Related: Superframe and Extended Superframe ES-L Errored Seconds (BPV+EXZ)>=1 or LOS>= 1 SES-L Severely Errored Seconds (BPV+EXZ)>=1544 or LOS>=1 LOSS-L Loss of Signal Seconds LOS>= 1 PDVS-L Pulse Density Violation Secs EXZ>=1; >7 zeros if B8ZS, >15 if AMI B8ZS-L B8ZS Seconds B8ZS coded signal received CV-L Code Violation Count (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. Next P. Previous Selection:

Shelf: 1 Slot: 1 Total Access System 04/17/02 05:08Unacknowledged Alarms: None Circuit ID: Performance Data Definitions

DS1 and DSX-1 Path Related: Superframe Extended Superframe ES-P Errored Seconds FE>=1 or CRC>=1 or SEF>=1 or AIS>=1 SEF>=1 or AIS>=1 SES-P Severely Errored Seconds FE>=8 or CRC>=320 or SEF>=1 or AIS>=1 SEF>=1 or AIS>=1 UAS-P Unavailable Seconds >10 cont. SES-Ps >10 cont. SES-Ps SAS-P SEF/AIS Seconds SEF>=1 or AIS>=1 SEF>=1 or AIS>=1 ES-PFE Far End Errored Seconds n/a PRM bits G1-G6,SE, or SL=1, or RAI CV-P Code Violation Count FE count 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:


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

Figure 26. Scratch Pad and Circuit ID Screen

Figure 27. T1 Alarm History Screen

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22Unacknowledged Alarms: None CIRCUIT ID: ABC123

Current Scratch Pad: New Scratch Pad =

New Circuit ID =

Begin typing to change Circuit ID field

Press ESC to Exit.

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:


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

Figure 28. Facility Alarm History Screen

Figure 29. HDSL4 Span History Screen

Shelf: 1 Slot: 1 Total Access System 05/15/02 18:07Unacknowledged Alarms: MAJOR MINOR INFO Circuit ID:1181412L4 Facility Alarm HistoryLOCATION ALARM FIRST LAST CURRENT COUNT-------------------------------------------------------------------------------- FACILITY DC OPEN 01/01/00 14:00:01 05/02/03 13:15:01 OK 002FACILITY OVER-CURRENT OK 000FACILITY GROUND FAULT OK 000

H4TU-C POWER CYCLE 01/01/00 14:00:01 05/06/03 09:00:01 OK 004H4TU-R POWER CYCLE 05/02/03 08:33:33 05/02/03 08:33:33 OK 001

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

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

H4TU-C L1 MRGN OK 000 L2 MRGN OK 000H4R1 NET L1 MRGN OK 000 L2 MRGN OK 000

H4TU-C L1 ATTEN OK 000 L2 ATTEN OK 000H4R1 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:


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.

Figure 30. Event History Screen

Shelf: 1 Slot: 1 Total Access System 01/25/02 09:22Unacknowledged 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:


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 Report2. Current Status Report3. System Configuration Report4. Alarm/Event History

Selecting a report type will display all the reports for that category on the screen at once.

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)?

Figure 31. System Status/PM Report Screen

Figure 32. Clear PM and Alarm Histories Screen

4. Loopbacks and Test 5. Performance Monitoring 6. Scratch Pad, Ckt ID 7. Alarm History 8. Event History 9. System Status/PM Report 10. Clear PM and Alarm Histories 11. Troubleshooting 12. 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

Shelf: 1 Slot: 14 Total Access System 09/11/03 15:22Unacknowledged Alarms: MAJOR INFO Circuit ID:

HDSL4 Main Menu

1. HDSL4 Unit Information 2. Provisioning 3. Status 4. Loopbacks and Test 5. Performance Monitoring 6. Scratch Pad, Ckt ID 7. Alarm History 8. Event History 9. System Status/PM Report 10. Clear PM and Alarm Histories 11. Troubleshooting 12. Flash Upgrade

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

Selection: 10


The Troubleshooting screen (Figure 33) compiles infor-mation 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.

Figure 33. Troubleshooting Screen

Figure 34. Troubleshooting Guidance Screen

Shelf: 1 Slot: 14 Total Access System 09/03/03 15:22Unacknowledged Alarms: INFO Circuit ID: Troubleshooting

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

Hours: Normal 7am - 7pm CST 1. Troubleshooting Guidance Emergency 7 days x 24 hours 2. General InformationPhone: 800.726.8663 / 888.873.HDSL Fax: 256.963.6217

Shelf: 1 Slot: 14 Total Access System 09/03/03 15:23Unacknowledged Alarms: INFO Facility DC Open

- A DC Open condition is often caused by a lack of current flow on the DSLloops. 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 (orH4R) housing. If still open, troubleshoot facility wiring for an open circuit.Looking toward the CO, you should see approximately 190 volts across T/T1 andR/R1 at any point. Also, if HDSL4 equipment is connected you should see a shorton 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 beachieved. If not, replace the H4TUC and H4TUR one at a time to identify theproblem.


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.

Figure 35. General Information Screen

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


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 supersededby 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:

Shelf: 1 Slot: 14 Total Access System 09/03/03 15:25Unacknowledged Alarms: INFO Circuit ID:HntsvlALMn0103

SW Ver Checksum H4TU-C Flash Image: A01 DD85

Software Update

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

Selection:


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.

Figure 37. Download H4TU-C via Y-Modem

Figure 38. Flash Upgrade, Y-Modem in Progress


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. Start Transfer 2. Abort

Selection:

Shelf: 1 Slot: 14 Total Access System 09/11/03 15:54Unacknowledged Alarms: MAJOR INFO Circuit ID:

...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 Ymodem3. Select appropriate binary file (*.BIN) to upload.4. Upload File.

[Note: The screen will start displaying C's - this is normal.]=CCCC


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

NOTEAccess the SCU menu system to configure theIP address as this is not an H4TU-C menuoption. In addition, the Ethernet interface ofthe SCU must also be provisioned properly forTFTP 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 Mainte-nance 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 physi-cally be located at the Total Access 3000 shelf to update the H4TU-C.

Figure 39. Download H4TUC via TFTP

Figure 37. Flash Upgrade, YModem in Progress


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. Remote Filename = 1181413l1_a01.bin 2. Start Transfer 3. Abort


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.

Figure 40. Boot Block Status and Overwrite Password

Shelf: 1 Slot: 14 Total Access System 09/09/03 14:58Unacknowledged 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:


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

Figure 41. HDSL4 Circuit Segments

The ADTRAN HDSL4 system provides DS1-based services over loops designed to comply with the guide-lines 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

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 compro-mised reliability of that loop. Follow the guidelines in this section to ensure that the circuit meets basic requirements:

1. All loops are nonloaded only.2. Any single bridged tap is limited to 2 kft.3. Total bridged tap length is limited to 2.5 kft.4. 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.

NOTEIn three segment circuits ( two H4Rs),individual segment resistance values must beverified. Refer to number 7, Resistance Values,on the next page.

Table 7. Attenuation limits

Recommended Maximum

Upstream Downstream

1st segment 30 dB 32 dB

2nd and 3rd segment 28 dB 28 dB

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

26 Gauge Recommended Maximum

1st segment 10,470 ft.

2nd segment 9,865 ft.

3rd segment 9,865 ft. (see note above)

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

26 Gauge Recommended Maximum

1st segment 14,770 ft.

2nd segment 14,050 ft.

3rd segment 14,050 ft. (see note above)


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.

NOTEA circuit that otherwise meets attenuation andinsertion loss requirements for cable reach willencounter span powering problems if resis-tance 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.

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

Table 10. Single Pair DC Resistance Value

Resistance (ohms/kft)

AWG 70°F 90°F 120°F 140°F

19 16.465 17.183 18.261 18.979

22 33.006 34.446 36.606 38.046

24 52.498 54.789 58.225 60.516

26 83.475 87.117 92.581 96.223


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.

NOTEThese measurements represent only one of thetwo HDSL4 pairs.

Figure 42. Resistance Budget Span Powering Two Repeaters


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)


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.

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.

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.

Table 11. HDSL4 Insertion Loss Values (Based upon 26 AWG cable)

Frequency(KHz)

1st SegmentLoss (dB)

2nd/3rd SegmentLoss (dB)

50 29.8 28.0

80 34.2 32.2

130 37.0 34.8

196 40.8 N/A

Table 12. Single Span and First Segment of Repeatered Loop (Based upon 11.1 kft. of 26 AWG cable)

Frequency (kHz) RecommendedMaximum Loss (dB)

Measured Loss (dB) Delta Loss (dB) (Max minus Measured)

50 29.8

80 34.2

130 37.0

196 40.8

1Sum Delta Loss =

Table 13. Second or Third Segment of Repeatered Loop (Based upon 11.1 kft. of 26 AWG cable)

Frequency (kHz) RecommendedMaximum Loss (dB)

Measured Loss (dB) Delta Loss (dB)(Max minus Measured)

50 28.0

80 32.2

130 34.8

50 28.0

1Sum Delta Loss =


8. MAINTENANCEThe 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. SPECIFICATIONSSpecifications for the Total Access 3000 HDSL4 Trans-ceiver Unit for the Central Office are detailed in Table 14.

10. WARRANTY AND CUSTOMER SERVICEADTRAN will replace or repair this product within the warranty period if it does not meet its published specifi-cations 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 ADTRAN’s 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 SalesPricing/Availability:800-827-0807

ADTRAN Technical SupportPre-Sales Applications/Post-Sales Technical Assistance:

800-726-8663

Standard hours: Monday - Friday, 7 a.m. - 7 p.m. CSTEmergency hours: 7 days/week, 24 hours/day

ADTRAN Repair/CAPSReturn for Repair/Upgrade:(256) 963-8722

Repair and Return AddressContact Customer and Product Service (CAPS) prior to returning equipment to ADTRAN.

ADTRAN, Inc.CAPS Department901 Explorer BoulevardHuntsville, Alabama 35806-2807

http://www.adtran.com/warranty


Table 14. HDSL4 Total Access 3000 H4TU-C SpecificationsSpecification Description

Loop InterfaceModulation Type

ModeNumber of Pairs

Line RateBaud RateLoop Loss

Bridged TapsPerformance

H4TU-C Transmit Power (Data) LevelH4TU-C Transmit Power (Activation) Level

Input ImpedanceMaximum Loop Resistance

Return Loss

16 TC PAMFull duplex, partially overlapped echo canceling 21.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)

Network InterfaceDS1 Transmit Level

DSX-1 Line Buildout

DSX-1 Line Code

0 dB (default), –7.5 dB, –15 dB0-133 ft. ABAM (default)133-266 ft. ABAM266-399 ft. ABAM399-533 ft. ABAM533-655 ft. ABAMB8ZS (default), AMI

PowerTested with the ADTRAN H4TU-C (P/N 1223426L2) and H4R (P/N 1223445L1)

H4TU-C Total Power

H4TU-R Power Dissipation

Span Power

Fusing

–48 VDC @ 197 mA with H4TU-R–48 VDC @ 348 mA with H4TU-R and one H4R5.5 watts with H4TU-R6.4 watts with H4TU-R and one H4R190 VDC (from H4TU-C) Class A2 compliant, GFI current limited at <5 mA, Loop current limited at between 150 to 160 mA1.00 A (not field-replaceable)

ClockClock Sources

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

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

PhysicalTotal Access 3000 H4TU-C, Shelf-Mounted

DimensionsWeight

6 in. High, x 0.7 in. Wide, x 10 in. Deep< 1 lb.

EnvironmentOperating Temperature (Standard)

Storage Temperature–40°C to + 70°C–40°C to + 85°C

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

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


This page is intentionally blank.

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

HDSL4 MAINTENANCE MODESThis 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 DescriptionIn 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 deacti-vation code sequence only if an error rate of 1E-03 or greater is present.

Loopback Control CodesA summary of control sequences is given in Table A-1 and Table A-2.

NOTEIn all control code sequences presented, the in-band codes are shown left-most bit transmittedfirst, and the esf data link codes with right-most bit transmitted first.

Appendix AHDSL4 Loopbacks

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

1. The Source column indicates which side of the interface the control codes are sent from. For example, an (N) indi-cates a network sourced code while a (C) indicates a customer sourced code.

2. All codes are in-band unless labeled ESF-DL.3. All codes listed above must be sent for a minimum of 5 seconds to be detected and acted upon.

Table A-1. HDSL4 Loopback Control Codes

Type Source1 Code2,3 Name

Abbreviated (N)(N)(N)(N)(C)(C)(C)(C)

3in7 (1110000)4in7 (1111000)2in6 (110000)3in6 (111000)6in7 (1111110)5in7 (1111100)4in6 (111100)5in6 (111110)

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.

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

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)

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)

61181413L2-5A Issue 1, November 2003 A-3

Table A-2. Loopback Control Codes

Function Code (Hex / Binary) Response

ARM (in-band) - also known as 2-in-5 pattern

11000 (binary) If the pattern is sent from the network, the units will arm, and the H4TU-R will loop up if NIU Loopback is enabled.

ARM (ESF Data Link) FF48 or 1111 1111 0100 1000 sent in the Facility Data Link

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.

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

11100 (binary) When sent from the network or customer, all units are removed from the armed state, and loopbacks will be released.

Disarm (ESF Data Link) FF24 or1111 1111 0010 0100 sent in the Facility Data Link

When sent from the network or customer, all units are removed from the armed state, and loopbacks will be released.

H4TU-C Loop Up 1,2 D3D3 or 1101 0011 1101 0011

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.

Loop Down w/o Disarm 9393 or 1001 0011 1001 0011

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.

Loopback Query 1 D5D5 or 1101 0101 1101 0101)

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 231 errorsH4R1 10 errorsH4R2 200 errorsH4TU-R 20 errors

Loopback Time Out Override1

D5D6 or1101 0101 1101 0110

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 231 bpsH4R1 110 bpsH4R2 2200 bpsH4TU-R 20 bps

A-4 Issue 1, November 2003 61181413L2-5A

1. Units must be armed with 11000b or FF48h before this code will work. 2. 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 loop-back, 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

Span Power Disable1 6767 or 0110 0111 0110 0111

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.

First H4R Loop Up 1,2 C741 1100 0111 0100 0001

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.

Second H4R Loop Up 1,2 C7541100 0111 0101 0100

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.

H4TU-R Address 20 for Extended Demarc 1,2

C7421100 0111 0100 0010

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.

Table A-2. Loopback Control Codes (Continued)

Function Code (Hex / Binary) Response

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

GENERALFigure 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 power-cycled, it will default to the customer direction.

NOTEThe H4TU-C must be provisioned for the Out-of-Service, Maintenance service state whenintrusive bantam jack testing is beingperformed.

DSX MODE TEST ACCESSDSX MON, Tx to CustomerThe 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.

Figure B-1. DSX MON, Tx to Customer

DSX MON, Rx from CustomerThe 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 customer-originated data. The BERT Tx is not used. This test is nonintrusive.

Figure B-2. DSX Mon, Rx from Customer

DSX EQ, Tx to Customer and Rx from CustomerThe 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.

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

EQ

MON

TX

RX

TX

RX

XFrom DSX To DSX

From CUST To CUST

From MUX To MUX

TX

RX

T1 BERT

432 ‰

432 ‰

EQ

MON

TX

RX

TX

RX

XFrom DSX To DSX

From CUST To CUST

From MUX To MUX

TX

RX

T1 BERT

432 ‰

432 ‰

EQ

MON

TX

RX

TX

RX

From CUST To CUST

From MUX To MUX

TX

RX

T1 BERT

From DSX To DSX

432 ‰

432 ‰

Appendix BFront Panel DSX and MUX Mode Test Access

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

MUX MODE TEST ACCESSMUX MON, Tx to CustomerThe 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.

Figure B-4. MUX MON, Tx to Customer

MUX MON, Rx from CustomerThe 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 nonin-trusive.

Figure B-5. MUX MON, Rx from Customer

MUX EQ, Tx to Network and Rx from NetworkThe 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.

NOTEVia the Test Screen, ensure that the equipmentjack (EQ) is in the “To Network” mode. In the“To Network” mode, AIS (unframed all ones)is sent in the customer direction.

Figure B-6. MUX EQ, Tx to Network and Rx from Network

MUX EQ, Tx to Customer and Rx from CustomerThe 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.

NOTEVia the Test Screen, ensure that the equipmentjack (EQ) is in the “To Customer” mode. In the“To Customer” mode, AIS (unframed all ones)is sent in the Network direction.

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

EQ

MON

TX

RX

TX

RX

X From DSX To DSX

From CUST To CUST

From MUX To MUX

TX

RX

T1 BERT

432 ‰

432 ‰

EQ

MON

TX

RX

TX

RX

X From DSX To DSX

From CUST To CUST

From MUX To MUX

TX

RX

T1 BERT

432 ‰

432 ‰

EQ

MON

TX

RX

TX

RX

TX

RX

T1 BERT

From DSX To DSX

From CUST To CUST

From MUX To MUX

432 ‰

432 ‰

EQ

MON

TX

RX

TX

RX

TX

RX

T1 BERT

From DSX To DSX

From CUST To CUST

From MUX To MUX

432 ‰

432 ‰

Date post:	28-Oct-2015
Category:	Documents
Upload:	cborn99
View:	44 times
Download:	0 times

Total Access 3000 HDSL4 Transceiver Unit for the Central Office Installation and Maintenance Practic...

Documents