HN400 Provisioning and Troubleshooting Guide
Contents
1. Nevo 2BASE TL System Connector and LEDs Status LEDs LEDs Power Power Serial 2BASE TL Status Connector Craft Copper Plant LEDs Port Connector s Figure 3 1 HN40x CO Device Connectors and LEDs Table 3 1 HN40x CO Troubleshooting Steps Condition Solution All front panel LEDs are off 1 Verify that the device is receiving 48 VDC power 2 Verify that the power cable is wired correctly see Connecting 48 VDC Power on page 3 5 3 If only one power source is being used switch the power cables to the connection that is not in use for example to the B connection if the A connections are being used 4 Replace the device with a unit known to be in proper working condition HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Troubleshooting Using Device Indicators 3 5 Table 3 1 HN40x CO Troubleshooting Steps Continued Condition Solution The red System FAIL LED is on In normal operation the system FAIL LED will blink on and off immediately after the device is powered up while the device runs its self test diagnostics If the system FAIL LED is on after diagnostics have run it indicates that the device has detected a hardware problem 1 Remove power from the device and power it back up 2 Replace the device with a unit known to be in proper working condition One or more of the numbered 2BASE TL LEDs are off In normal operation2. Connects to These Devices at a CP HN404 CO HN408 CO HN4000 HN404 CP HN408 CP HN404 U 2E I HN408 U 2E I HN414 U 2E I e HN404 U 2E I HN418 U 2E I HN4000 I HN408 U 2E I HN414 U 2E I e HN418 U 2E I e HNA04 CP 1E I HNA08 CP 1E I HN400 Provisioning and Troubleshooting Guide HN4 TG030NN00 The Hatteras Networks Provisioning Utilities 1 5 1 2 The Hatteras Networks Provisioning Utilities 1 2 1 The Hatteras Networks Access Class Ethernet system includes the following methods to pro vision and monitor services and network connectivity O aCommand Line Interface CLI O a Web browser based Element Management System EMS O aWeb browser based GUI WebManager CLI The Command Line Interface CLI tool enables operators to perform similar provisioning and management functions by using commands that are structured in a familiar CLI format Oper ators can use the CLI commands through a telnet session or by making a direct connection to an HN400 platform through a serial port Note This HN400 Provisioning and Troubleshooting Guide provides configuration examples that use the CLI interface For examples of configuring an HN400 platform with the HN EMS refer to the HN EMS Installation and User Guide 1 2 2 EMS The Hatteras Networks Element Management System the HN EMS is a scalable carrier class EMS accessible through a Web browser The HN EMS enables network operators to provision
3. a numbered 2BASE TL LED will be off if there is no copper pair connected to the port or if a copper pair is connected at the port but is not terminated at an operational remote device If a numbered 2BASE TL LED is off when a copper pair is connected 1 Verify that the copper pairs are terminated at an operational remote device 2 Verify that the copper pairs are wired correctly in the copper pair CAT 5 cable Refer to Connecting the Copper Plant Pairs to the HN40x CO on page 3 10 for wiring information The Network LINK LED is off In normal operation the Network LINK LED is on when a link is detected between the HN40x CO and a remote device 1 Verify that the CAT 5 cable is connected properly to a 10 100 Mbps port on an operational Ethernet device The Network ACT LED is off In normal operation the Network ACT LED blinks when the device detects traffic on the Network port If the Network ACT LED is off and the Network LINK LED is on 1 Verify that there is Ethernet traffic on the network connection HN4 TGO30NNO0 HN400 Provisioning and Troubleshooting Guide 3 6 Troubleshooting Using Device Indicators 3 4 2 HN40x CP Table 3 2 summarizes the HN40x CP troubleshooting steps Figure 3 2 shows the location of the device s LEDs and connectors Power Power Status Connector LEDs Serial Craft Port CPE 2BASE TL Connector and LEDs LEDs 2BASE TL Copper Plant Connecto
4. Hatteras Networks repair and return address is Hatteras Networks Inc 523 Davis Dr Suite 500 Durham NC 27713 HN4 TGO30NNO00 HN400 Provisioning and Troubleshooting Guide C 2 Repair and Return Address HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0
5. an IP address Provisioning Descriptions There are several descriptions and data that should be input to the Hatteras Networks equip ment The most important ones that can be added using the config sys command are listed in Table 2 5 Table 2 5 Device Descriptions Keyword Argument Description hostName This field is the name of the system It is used in TL1 as Source Identifier SID and in SNMP as sysName location This field is used for the address of the location where the equipment is located contact This field is used for the name and telephone number s of the primary contact person for the equipment prompt This field changes the default CLI prompt to a new prompt It is convenient to give each piece of equipment a unique prompt clli This field is the Common Language Location Identifier CLLI code for the location where the equipment is installed description This field is used to add a description of the equipment or location that may be helpful to the network operator additionalInfo This field is used to add any additional information that is not covered under any other field The other important descriptions to add are circuit numbers or other identifiers for the copper loops The command to add these descriptions is config 2bpme n description The description may contain up to 64 characters Use quotes around the text string if it contains spaces HN4 TG030NNOO HN400 Provision
6. for SEALPIC cable The length of the cable is calculated using the following formula o L Total Resistance 88 0 for 26 AWG wire or o L Total Resistance 54 5 for 24 AWG wire At the conclusion of this test be sure to un short the tip and ring wires at the far end of the copper pair Use a VOM or other test set to determine the resistance length of the copper loop and record the results in the table below The resistance method of determining the loop length may be inaccurate if the composition of the copper loop consists of a mix of wire gauges 2 1 3 Summary of Length Measurement Method Record the three length calculations in Table 2 3 Table 2 3 Length Calculations Length Measurement Method Length feet TDR Method Capacitance Method Resistance Method HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide 2 4 Determining an Operating Point These values should be fairly close to each other If they are not then the copper pair may have bridge taps and or load coils on it or there may be a wire gauge change in the copper pair If agreement on the copper loop length is not reached manual investigation of the copper loop may be required Finally convert the copper pair length to a 26 AWG cable Equivalent Working Length EWL using the formula provided on page 2 2 2 2 Determining an Operating Point uw 2 2 x o g c The final step is to determine the ra
7. should be set at 5 dB above the highest measured loop attenuation The CRC anomalies TCA should be set at a fairly large number such as 10 000 or 50 000 Provisioning Alarms 2 5 1 After the HN40x CO and HN40x CP are placed in service there may be some standing alarms that are current Use the show alarm command to list these alarms It is good practice to clear these initial standing alarms The most common standing alarms and the procedure to clear them described in the following sections CPE Power B Alarm The HN40x CP may be dual powered with both A and B power feeds but it is fairly unusual for the B power feed to be connected by itself Most CPE installations utilize only one power feed and it is usually connected to the A power feed The standing alarm will show that the HN40x CP B power feed is not connected and therefore in alarm The cpe config env pwrAAlarm suppress command will suppress this alarm 2 5 2 2BPME Alarms The 2BPMEs that are not connected to copper loops will also produce standing alarms These alarms may be cleared by administratively disabling the unused copper ports The commands config 2bpme n admin disable and cpe config 2bpme n admin disable will clear these alarms Any other standing alarms should be cleared if possible HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide 2 8 Provisioning Event Logs 2 6 21 2 8 Provisioning Event Logs The HN40x CO and in the HN40x CP
8. the carrier network You can also ping from the HN40x CP Ethernet 1 port to a host or port on the customer s network if an IP address has been assigned to Ethernet 1 port on the HN40x CP Traffic in both directions should be verified by examining the Ethernet 1 port statistics for both the HN40x CO and the HN40x CP Provisioning 2BPME Ports Copper Pairs The copper pair ports on the Hatteras Networks products are called 2BASE TL Physical Media Entity 2BPME ports These ports automatically handshake train optimize activate and bond together based on the parameters dictated by the product s span profile After the copper pairs have completed activation and bonding the green 2BPME LEDs should be slowly blink ing green The slow blinks represent OAM packets that are periodically sent from the HN40x CO to the HN408 CP and vice versa The show 2bmpe command displays a device s line rate speed SNR margin and loop atten uation of the copper pair Compare the line rate of the copper loops with the operating point on the rate reach curve that you determined in the section Determining an Operating Point on page 2 4 If the achieved rate varies significantly from the operating point rate then HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Provisioning 2BPME Ports Copper Pairs 2 7 there may be a problem with the copper loop and the parameters of its span profile may need adjustment If the upstream and downst
9. the installation manual to determine the problem and corrective action 2 4 Provisioning Ethernet Ports 2 5 An HN40x 10 100BASE TX Ethernet ports default configuration is set for auto negotiation In most cases this setting works well and these ports are able to achieve maximum compatibility In some cases auto negotiation will not produce optimal results Throughput may seriously be affected if these Ethernet ports auto negotiate half duplex or 10 Mbps where they should nego tiate full duplex and or 100 Mbps Use the show ethernet 1 and cpe show ethernet 1 commands to display the device s Ethernet information If you determine that the Ethernet ports have not achieved optimal duplex setting or rate change the autonegotiate parameter to disable and manually set the duplex and speed to the correct values You may also have to perform this same operation on the Ethernet switch that the HN40x CO is connected to and to the device Ethernet switch IAD router etc that the HN40x CP is connected to at the customer premise The Ethernet 1 port on the HN40x CO can be assigned an IP address either manually or via DHCP with the config ip 1 command Ethernet 1 port on the HN40x CP can also be option ally assigned an IP address either manually or via DHCP from the HN40x CO with the cpe config ip 1 command To verify device connectivity ping from an HN40x CO to an Ethernet switch to which it is con nected or to some other host or port on
10. 2020082646 Bae Qe ORO LER REE RO eee AVE URS Maa ae E pan 1 5 2 Provisioning Guidelines 24 Determining Loop Length cuc tdeo ee bee ew Rex a Paha eae Fa ee ead 2 1 2 1 1 Using Circuit Records used edu xe dene eed eod Ee be Ee eee RR Qe ovde 2 1 VRISSZIShDEWEIERIITMR T mRm S 2 2 2 1 2 1 TDR Method x ue rat beh Pe heeds ERI ae OR RI eerie eae Fas Ra Pee 2 2 2 1 2 2 Capacitance Length Method 0 0 cect I fai 2 3 2 1 2 3 Resistance Length Method 0 0 0 0 ett teens 2 3 2 1 3 Summary of Length Measurement Method 0 0 cece eet 2 3 2 2 Determining an Operating Point 2 2 Rh I 2 4 2 3 Things To Do and Check After Completing The Hardware Installation 0 eee ee ee 2 5 2 4 Provisioning Ethernet Ports a 2 22 eee need ee eed a ee Ae eR iei eee ee ae Pee 2 6 2 5 Provisioning 2BPME Ports Copper Pairs o oococcooccocco RII eee 2 6 2 5 1 GPE Power BAIAT ss 2 860 op se tI bee ee ea dae eae 2d a A A a ERR EAR RR ER e cR RO ce 2 7 2 5 2 2BPME Alarms erm eL ERR pe ee bee ob eee race ted dee Pe eet wap eet ee eds 2 7 2 0 Provisioning Event LOGS avcsicice wegen werce tek danes eii e Kid psa a E qued p god 2 8 2 1 Provisioning Statistics and PM oin RR tds e he ra up EE Kus Ele ee Ra DR EROR ERR d E RS 2 8 2 8 Provisioning the Clock ocs ccc ses he eee e ese peg koe es 2 8 3 Troubleshooting Guidelines 3 1 Monitored Information 1
11. 802 3ah 2BASE TL standard for transporting Ethernet over bonded voice grade copper pairs and provide an economic robust method for extending traditionally opti cal Ethernet services over a copper infrastructure The HN400 system software supports the Hatteras Networks HN400 family of Ethernet over copper delivery systems The HN400 products utilize the IEEE 802 3ah 2BASE TL stan dard for transporting Ethernet over bonded voice grade copper pairs and provide an economic robust method for extending traditionally optical Ethernet services over a copper infrastructure 1 1 HN400 Family Product Overview The HN400 products include the following models GO HN408 CO and HN404 CO eight and four pair devices designed to be installed in the central office CO or remote terminal RT O HN408 CP HN404 CP HN408 CP 1E I and HN404 CP 1E I eight and four pair devices designed to be installed at customer premise CP locations GO HN408 U and HN404 U eight and four pair universal devices designed to support uni versal installation in any CO RT or CP location available with one or two 10 100 Mbps BASE TX network interfaces O HN418 U and HN414 U eight and four pair universal devices designed to support uni versal installation in any CO RT or CP location provided with one optical 100BASE X network interface and one 10 100 Mbps BASE TX network interface 1 1 1 HN40x CO Products The HN40x CO series of devices wh
12. HN400 Provisioning and Troubleshooting Guide HN4 TG030NNOO HATTERAS NETWORKS E Copyright 2005 2006 by Hatteras Networks Inc All Rights Reserved Printed in the United States of America Rev 00 March 1 2006 Ordering No HN4 TG030NN00 Notice Copyright 2005 2006 by Hatteras Networks Inc All rights reserved No part of this document including its interior design and icons may be reproduced stored in a retrieval system or transmitted in any form by any means electronic mechanical photocopying recording or otherwise without written permission of Hatteras Networks Inc LIMITED LIABILITY DISCLAIMER OF WARRANTY HATTERAS NETWORKS INC HAS USED ITS BEST EFFORTS IN PREPARING THIS DOCUMENT HATTERAS NETWORKS INC MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THIS DOCUMENT AND SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE THERE ARE NO WARRANTIES WHICH EXTEND BEYOND THE DESCRIPTIONS CONTAINED IN THIS PARAGRAPH NO WARRANTY MAY BE CREATED OR EXTENDED BY SALES REPRESENTATIVES OR WRITTEN SALES MATERIALS HATTERAS NETWORKS INC SHALL NOT BE LIABLE FOR ANY LOSS OF PROFIT OR ANY OTHER COMMERCIAL DAMAGES INCLUDING BUT NOT LIMITED TO SPECIAL INCIDENTAL CONSE QUENTIAL OR OTHER DAMAGES The publisher of this document is Hatteras Networks Inc PO Box 110025 Research Triangle Park NC 27709 0025 Hatteras Netwo
13. Products The HN4xx U series of universal devices are designed for installation in a CO RT or CP envi ronment Figure 2 These universal devices can be set to operate in either CO or CP mode by using the CLI s config deviceMode command Central Offlce Customer Premises HN400 U HN400 U Te aie CO Mode 2BASE TL Over CP Mode letwor t 2BASE TL Ethernet Copper Plant 40 100 BASE TX Ports Port s i HN40x U a ae 100BASE X and 10 100 BASE TX Ports HN41x U 40 100 BASE TX Ports CA To HN40x U i i XN J00BASE X and 10 100 BASE TX Ports HN41x U Customer Network 2BASE TL Ethernet Port s Figure 2 HN4xx U Device Connections Table 1 1 lists the HN4xx U device models with their 2BASE TL and network interface capabilities Table 1 1 HN4xx U Models Model Model 2BASE TL Connections Network Interfaces Abbreviation HN404 U 2E I HN404 U One to four Two 10 100 Mbps BASE TX HN408 U 2E I HN408 U One to eight Two 10 100 Mbps BASE TX HN414 U 2E I HN414 U One to four One optical 100BASE X and one 10 100 Mbps BASE TX HN418 U 2E I HN418 U One to eight One optical 100BASE X and one 10 100 Mbps BASE TX These HN4xx U models differ from the HN40x CO and HN40x CP models in the following ways GO An HN4xx U is software configurable to operate as a CO or CP device one piece of hard ware can serve both roles O The HN4xx U has two 10 100BASE T ports o
14. The Hatteras HN40x CO equipment can display detailed counters for all Ethernet ports including HN40x CO and HN40x CP Ethernet ports for unicast frames broadcast frames transmit octets received octets frames of different sizes dropped frames etc Performance Monitoring Buckets The equipment collects and stores the current 15 minute bucket and the previous15 minute buckets for errored seconds es severely errored seconds ses CRC anomalies crc loss of sync word seconds losws and unavailable seconds uas for both upstream and downstream traffic on the copper loops Performance Monitoring Statistics The equipment collects and stores cumulative counters for errored seconds es severely errored seconds ses CRC anomalies crc loss of sync word seconds losws and unavailable seconds uas for both upstream and downstream traf fic on the copper loops Port Status Statistics The equipment can display the status of all ports and entities in real time including active NIUs failed NIUs which pairs are used etc HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide 3 2 Reporting Capabilities 3 2 Logical Service Layer Statistics The equipment HN4000 or HN408 U only can display sta tistics such as octets accepted into the service octets rejected to due exceeding configured policer etc Forwarding Information The equipment can display forwarding information including an ARP table MAC learn
15. ble 3 3 HN400 software Troubleshooting Steps Condition Solution All front panel LEDs are off 1 Verify that the device is receiving 48 VDC power 2 Verify that the power cable is wired correctly see Connecting 48 VDC Power on page 3 14 4 Replace the device with a unit known to be in proper working condition The red System FAIL LED is on device is powered up while the device runs its self test diagnostics detected a hardware problem 1 Remove power from the device and power it back up 2 Replace the device with a unit known to be in proper working condition HN400 Provisioning and Troubleshooting Guide 3 If only one power source is being used switch the power cables to the connection that is not in use for example to the B connection if the A connections are being used In normal operation the system FAIL LED will blink on and off immediately after the If the system FAIL LED is on after diagnostics have run it indicates that the device has HN4 TG030NNO0O Troubleshooting Using Device Indicators 3 9 Table 3 3 HN400 software Troubleshooting Steps Continued Condition Solution One or more of the numbered 2BASE TL LEDs are off In normal operation a numbered 2BASE TL LED will be off if there is no copper pair connected to the port or if a copper pair is connected at the port but is not terminated at an operational remote device If a numbered 2BASE TL LED
16. devices maintain event logs These event logs are circu lar files that hold up to 4080 entries Only events and alarms are written to an event logs if its priority is equal to or higher than the configured priority threshold in the event log It is good practice to change the priority threshold of the port and BPM device modules from notify to info for both the HN40x CO and the HN40x CP event logs This will cause many more events to be written to the event logs regarding the Ethernet and copper ports than nor mally would be however in the event of a problem it will provide much more information to analyze and debug the problem After the first few weeks of operation the threshold settings can be changed back to their default values After the initial installation and turn up of the HN40x CO and the HN40x CP both event logs should be cleared to provide the network operator with a known starting point and an empty event log for the equipment Provisioning Statistics and PM There are three sets of statistics and one set of PM data that are supported by the HN40x CO and the HN40x CP The statistics include Ethernet port statistics for Ethernet port 1 Ethernet port 1001 CPE Ethernet port 1 and CPE Ethernet port 1001 OAM statistics for the IEEE 802 3ah OAM channel between the HN40x CO and the HN40x CP and 2BPME statistics for the copper ports both upstream and downstream The PM data consists of the same data as the 2BPME statistics except it
17. ed performance Load Coil Upwards bump Prevent communications Open Pair Upwards bump Prevent communications Shorted Pair Down spike Prevent communications Split Pair Down spike or up spike Degraded performance HN400 Provisioning and Troubleshooting Guide HN4 TG030NNO00 Determining Loop Length 2 3 Use the TDR function to determine the TDR length of the copper loop and record the results in the Table 2 3 on page 2 3 2 1 2 2 Capacitance Length Method The capacitance length method uses the fact that a cable pair has a capacitance of 83 nF per mile The test set measures the total capacitance of the copper pair and the result is divided by this value to obtain the capacitance length of the copper pair Use the AUTOTEST or manual test mode of the test set to determine the capacitance length of the copper loop and record the results in Table 2 3 on page 2 3 2 1 2 3 Resistance Length Method The resistance length method requires access to the far end of the copper pair If access is not available to the far end of the copper pair skip this test If access to the far end of the copper pair is available short the tip wire to the ring wire of the copper pair Use the AUTOTEST or manual test mode to measure the resistance in ohms from the tip wire to the ring wire The resistance of copper wire is O 88 0 ohms per 1000 feet for 26 AWG wire for SEALPIC cable O 54 5 ohms per 1000 feet for 24 AWG wire
18. eh cae ee Rx pom anm x ros A eee ee edb kde eae 3 1 3 2 Reporting Capabilities oia ci a ee ee s mE TER EE RERHER TP AR ERR RETE EE 3 2 3 3 Diagnostic Capabilities lec RI IHR Hy m hh 3 3 3 4 Troubleshooting Using Device Indicators 0 0 IRI Ih 3 4 34 1 ANOT O RI TT 3 4 3 4 2 HN4OX CP ii cad ard auer e Rer de A A eo E E E 3 6 22 3 HNZDOCU iios cen a eee A nt 3 8 HN4 TG030NN00 HN400 Provisioning and Troubleshooting Guide iv Contents A HN400 Passwords B Safety Information B 1 Definition of Qualified Personnel lille RR I uh B 1 B 2 Field Replaceable Components 2 6 002 eee bee hk km re eee B 1 B 3 Safety Information Warnings 0 0 cnet tee B 1 BA POWER d e s 08 bod eed oe 2b eae e baths See eet ae deers B 2 B 5 Handling Electrical and Optical Equipment Static Electricity 2 0 ee B 2 B 6 Common Safety Symbols 0 tent rs B 2 C Technical Assistance C 1 Hatteras Networks Technical Support 0 0 2 0 0 cnet eee C 1 C 2 Repair and Return Address si uice hcc nee uke eae x xi cA XU OUS RUD RR A CR Rd C 1 HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Introduction This document provides guidelines for provisioning and troubleshooting the Hatteras Net works HN400 family of Ethernet over copper delivery systems This chapter provides an introduction to the HN400 family of products The HN400 products utilize the IEEE
19. es the safety related symbols used in this document or on the equipment Table B 1 Safety Symbols Symbol Description Caution failure to follow documented procedures could result in damaged or inoperative equipment gt Caution Warning risk of electric shock is present gt Warning Observe precautions for handling electrostatic discharge sensitive devices Laser warning Never look at a transmit LED laser through a magnifying device while it is powered on or look directly at fiber port or fiber cable ends when they are powered on HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Common Safety Symbols B 3 Table B 1 Safety Symbols Continued Symbol Description Direct current Earth ground terminal HN4 TGO30NNO0 HN400 Provisioning and Troubleshooting Guide B 4 Common Safety Symbols HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Technical Assistance C C 1 Hatteras Networks Technical Support O The toll free Hatteras Networks Technical Assistance Center phone number is 1 866 694 2883 O E mail access to the Technical Assistance Center is available at support hatterasnetworks com C 2 Repair and Return Address Before you return a product to Hatteras Networks you must obtain a Returned Materials Authorization RMA number from the Hatteras Networks Technical Assistance Center The
20. fic may be dropped or optionally forwarded at the Hatteras HN40x CO equipment Ethernet Layer 2 Ping The equipment can generate a layer 2 ping toward the Hatteras HN40x CP equipment and the Hatteras HN40x CP equipment can reply to the layer 2 ping IP Ping The equipment both HN40x CO and HN40x CP can generate an IP ping and reply to an IP ping IP Traceroute The equipment both HN40x CO and HN40x CP can originate the IP tracer oute command and display its results MLT Test Port The HN4000 only supports two MLT test ports in and out A test set may be connected to this MLT test port and this test set may be connected to any of the copper pairs terminated on the HN4000 via an internal cross connect The test set may then be used to con duct either a TDR and or a G SHDSL test on the copper loop HN4 TGO30NNO00 HN400 Provisioning and Troubleshooting Guide 3 4 Troubleshooting Using Device Indicators 3 4 Troubleshooting Using Device Indicators The HN400 family of Ethernet over copper products provide LEDs that provided valuable information in troubleshooting situations The following sections describe the basic trouble shooting steps for the three HN400 products o HN40x CO on page 3 4 o HN40x CP on page 3 6 o HN4xx U on page 3 8 3 4 1 HN40x CO Table 3 1 summarizes the HN40x CO troubleshooting steps Figure 3 1 describes the LEDs and connectors that are located on the device s front panel
21. gured to operate in CO mode Similarly any reference to the HN40x CP also applies to an HN40X U that is configured as to operate in CP mode 2 1 Determining Loop Length 2 1 1 The copper loops are a very important part of the Ethernet over Copper solution and special consideration needs to be given to them during HN40x installation and provisioning Prior to terminating the cooper loops on an HN40x CO there are several tasks that need to be per formed The first task is to determine the length of the copper loops Using Circuit Records The circuit records may provide information about the make up and length of the copper loops If Circuit Layout Records CLR or Design Layout Records DLR records are available record the AWG and length of each segment of the copper loop in Table 2 1 Table 2 1 Circuit Record Information Loop Segment AWG of Wire Length feet Gage Factor EWL feet 1 2 3 4 5 Total HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide Determining Loop Length The following equation is used to calculate the Equivalent Working Length EWL a length of 26 AWG cable with attenuation approximately equal to that of the copper loop EWL 1 00 L26 0 75 L24 0 60 L22 0 40 L19 L26 is the total length of 26 AWG wire L24 is the total length of 24 AWG wire L22 is the total length of 22 AWG wire and L19 is the total length of 19 AWG wire The resul
22. ich are designed for installation in a Central Office Figure 1 includes the HN404 CP and the HN408 CP The HN404 CP supports 2BASE TL connections to a customer premises over one to four bonded voice grade copper pairs the HNA08 CP supports 2BASE TL over one to eight voice grade bonded copper pairs HN4 TG030NNOO HN400 Provisioning and Troubleshooting Guide 1 2 HN400 Family Product Overview Central Office Customer Premises HN40x CO 2BASE TL 2BASE TL Over Ethernet Port Port 1001 10 100 BASE TX Port 1 10 100 BASE TX To Port 1 Customer Network 2BASE TL Ethernet Port Port 1001 Figure 1 HN40x CO and HN40x CP Device Connections 1 1 2 HN40x CP Products The HN40x CP series of devices are intelligent network demarcation devices designed to be installed at customer premises The series includes the HN404 CP and HN408 CP in addition to the HN404 CP 1E I and HN408 CP 1E I The HN404 CP and HN404 CP 1E I supports 2BASE TL over one to four bonded voice grade copper pairs the HN408 CP and HN408 CP 1E I supports 2BASE TL over one to eight voice grade bonded copper pairs The HN404 CP 1E I and HN408 CP 1E I products are functionally equivalent to the HN404 CP and HN408 CP respectively but are also compatible with the HN4xx U See Table 1 2 on page 1 4 for the product compatibility matrix HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 HN400 Family Product Overview 1 3 1 1 3 HN4xx U
23. ing and Troubleshooting Guide 2 10 Provisioning the Clock HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Troubleshooting Guidelines 3 Hatteras Networks equipment supports testing diagnostic and troubleshooting capabilities which can be accessed either locally from the craft port or remotely using in band or out of band management Hatteras Networks equipment has a full range of monitoring and diagnostic capabilities at multiple network layers The diagnostic capabilities can be categorized into monitored infor mation reporting capabilities and diagnostic operations 3 1 Monitored Information Hatteras Networks equipment maintains a large amount of information specifically designed for troubleshooting and diagnostic purposes The equipment supports a variety of physical and layer two statistics to help the network operator troubleshoot problems Loop attenuation measurement The equipment can display a real time measurement of the copper loop attenuation both upstream and downstream for all loops simultaneously in dB SNR margin measurement The equipment can display a real time measurement of the SNR margin of the copper loops both upstream and downstream for all loops simultaneously in dB Temperature measurement The equipment can display a real time measurement of the HN40x CO equipment and all the attached HN40x CP equipment temperature in degrees C and degrees F Ethernet Layer Statistics
24. ing tables etc HN4000 and HN408 U only Event Logs The equipment stores an event log and a boot log that may be analyzed to diag nose and trouble shoot problems Audit Logs The equipment tracks which users change or access which management objects Boot Logs The equipment records information regarding the booting up process and stores it in the boot log Tech Support Information The equipment has the capability to display a list of technical sup port information This information can be captured via a terminal session using the show tech support command and emailed to Hatteras technical support for further analysis Reporting Capabilities The Hatteras Networks equipment supports a variety of reporting capabilities the help the net work operator troubleshoot problems Alarms The equipment reports alarms via CLI TL1 and or SNMP Current alarms may also be queried via the CLI Alarm severities are configurable SNMP Notifications The equipment reports alarms events traps notifications errors and information to one or more SNMP hosts TL1 Notifications The equipment reports alarms events traps notifications errors and information via TL 1 IEEE 802 3ah OAM Reporting The Hatteras HN40x CP equipment reports alarms events traps notifications errors and information via the IEEE 802 3ah OAM channel to the Hatteras HN40x CO equipment Threshold Crossing Alerts TCA The equipment su
25. is accumulated and presented in the current and previous 15 minute buckets After the initial installation and turn up of the HN40x CO and the HN40x CP it is a good prac tice to clear all of these statistics The PM data cannot be cleared but the initial turn up errors will roll out of the current and previous 15 minute buckets after 30 minutes have elapsed Provisioning the Clock An HN40x device s clock should be correctly set either manually or by configuring a SNTP server so that the events in the event log and alarms will be time stamped with the correct time The command config clock tod 12 10 2004 10 14 00 can be used to manually set the clock Be sure to put quotation marks at the beginning and end of the date and time to execute the com mand successfully The Coordinated Universal Time UTC offset should also be configured The command to set the clock to Eastern Standard Time EST is config clock utcoffset 4 It is better to set a SNTP server if one is available to configure the date and time of the HN40x CO To determine if a SNTP service is available execute the command net time DOMAIN HN400 Provisioning and Troubleshooting Guide HN4 TG030NNO0O Provisioning the Clock 2 9 from the command prompt of a PC on the network If a SNTP server is reachable the com mand will return the DNS resolved name of that server You may have to use the command ping www sntp com to resolve the name of the SNTP timeserver to
26. is off when a copper pair is connected 1 Verify that the copper pairs are terminated at an operational remote device 2 Verify that the copper pairs are wired correctly in the copper pair CAT 5 cable Refer to Connecting the Copper Plant Pairs to the HN400 U on page 3 23 for wiring information The Network LINK LED is off In normal operation the Network LINK LED is on when a link is detected between the HNA00 software and a remote device 1 For HN40x U devices verify that the CAT 5 cable is connected properly to a 10 100 Mbps port on an operational Ethernet device 2 For HN4xx U optical devices a verify that the fiber optic cable is connected properly to a fiber optic port on an operational Ethernet device b follow appropriate local practices to ensure that optical fiber connector ends are clean and free from contamination The Network ACT LED is off In normal operation the Network ACT LED blinks when the device detects traffic on the Ethernet port If the Network ACT LED is off and the Network LINK LED is on 1 Verify that there is Ethernet traffic on the network connection A 2BASE TL bank s CPE Mode LED is off In normal operation a 2BASE TL bank s CPE Mode LED is off when the device is operating in CO mode If the LED is off when the device is in CPE mode as confirmed by using the CLI s show deviceMode command the LED is not operating properly powered on Fiber Optic Port
27. nd removal of the equipment must be per formed by qualified service personnel only 2 Install the equipment only as described in this document 3 Never install telephone wiring during a lightning storm 4 Never install telephone jacks in wet locations unless the jack is specifically designed for wet locations 5 Use caution when installing or modifying telephone lines 6 Never touch uninsulated telephone wires or terminals unless disconnected at the network interface HN4 TGO30NNO0 HN400 Provisioning and Troubleshooting Guide B 2 Power B 4 Power AN Power Warning This equipment has two power connections When removing power from the equipment ensure that both power connections A and B are disconnected Warning 1 Do not use a power source that does not meet the device s specified requirements over the entire installed temperature range B 5 Handling Electrical and Optical Equipment Static Electricity Static electricity can damage or decrease the reliability of electrical and optical equipment While unpacking and handling electrical and optical equipment wear a grounding wrist strap to dis charge the static buildup The grounding wrist strap is designed to prevent equipment damage caused by static electricity Before unpacking and installing equipment or making system intercon nections connect the grounding wrist strap B 6 Common Safety Symbols Table B 1 describ
28. oami command For example HN408 CPH whoami username craft 25 privilege prov HN408 CP HN4 TGO30NNO00 HN400 Provisioning and Troubleshooting Guide A 2 HN400 Provisioning and Troubleshooting Guide HN4 TG030NNO0O Safety Information Jn Warning Read the following safety information thoroughly before installing this Hatteras Networks equipment Failure to follow this safety information can lead to personal injury or damage to the equipment B 1 Definition of Qualified Personnel Installation maintenance removal of parts and removal of the HN4xx U and components must be performed by qualified service personnel only Qualified service personnel are people having appropriate technical training and experience necessary to be aware of the hazards to which they are exposed when performing a task and of measures to minimize the danger to themselves or other people B 2 Field Replaceable Components The HN4xx U equipment is designed to enable qualified personnel to replace only the follow ing components 1 SFP optical transceiver in the Ethernet port of the HN414 U and HN418 U devices A Fiber Optic ports Optical Safety Never look at the transmit LED laser through a magnifying device while it is powered on Never look directly at the fiber port or fiber cable ends when they are powered on B 3 Safety Information Warnings 1 Installation maintenance removal of parts a
29. operate and diagnose Hatteras Networks devices that are in their access network 1 2 3 WebManager As part of the Total Management Solution the Hatteras Networks WebManager provides an intuitive easy to use Web accessible GUI for rapid point and click provisioning and mainte nance With WebManager craft personnel can use a Web browser to access the extensive OAMG amp P capabilities of Hatteras Networks devices The embedded WebManager Web server provides a point and click interface that can be accessed from any computer and provides a fast graphical interface to all management func tions With service wizards and graphical views even novice personnel can quickly and accurately manage and provision device services HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide 1 6 The Hatteras Networks Provisioning Utilities HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Provisioning Guidelines This chapter is designed to provide a network installer with the procedures and guidelines that are needed to turn up an HN40x U HN40x CO or HN40x CP These procedures are what the network installer should accomplish after having completed all the steps in the Hatteras Net works hardware installation guides The HN40X U is a universal device that can be configured via software to operate in either CO mode or CP mode In this document any reference to the HN40x CO also applies to an HN40x U that has been confi
30. ot terminated at an operational remote device If a numbered 2BASE TL LED is off when a copper pair is connected 1 Verify that the copper pairs are terminated at an operational remote device 2 Verify that the copper pairs are wired correctly in the copper pair CAT 5 cable Refer to Connecting the Copper Plant Pairs to the HN40x CP on page 3 13 for wiring information The CPE LINK LED is off In normal operation the CPE LINK LED is on when a link is detected between the HN40x CP and a remote device 1 Verify that the CAT 5 cable is connected properly to a 10 100 Mbps port on an operational Ethernet device The CPE ACT LED is off In normal operation the CPE ACT LED blinks when the device detects traffic on the Network port If the CPE ACT LED is off and the CPE LINK LED is on 1 Verify that there is Ethernet traffic on the network connection HN4 TGO30NNO0 HN400 Provisioning and Troubleshooting Guide 3 8 Troubleshooting Using Device Indicators 3 4 5 HN4xx U Table 3 3 summarizes the HN40x U troubleshooting steps Figure 3 3 describes the LEDs and connectors that are located on the devices front panels 2BASE TL System LEDs and CO CPE Status Mode LEDs PE Mia Power Power Serial Craft Port 2BASE TL EDO d and LEDs Copper Plant Network Connector s Connectors and LEDs Figure 3 3 Device Connectors and LEDs HN408 U Top and HN418 U Bottom Ta
31. pports configurable threshold crossing alerts for loop attenuation dB SNR margin dB errored seconds seconds severely errored seconds seconds CRC anomalies number loss of sync word seconds seconds and unavailable seconds seconds for each copper loop Minimum Rate Alarm The equipment will generate an alarm if the combined rate of the bonded group falls below a set threshold Alarm IO Port The HN4000 only supports and alarm IO port that has two outputs major alarm and critical alarm and one input user definable alarm HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Diagnostic Capabilities 3 3 Event Log FTP The equipment supports exporting the event log via FTP for off line inspection Test Alarm The equipment can send a test alarm trap to a SNMP host and a clear alarm mes sage to the SNMP host to test the alarm connectivity of the equipment 3 3 Diagnostic Capabilities The equipment supports a variety of diagnostic capabilities to help the network operator trou bleshoot problems Ethernet Loopback The equipment can send a loopback command to the HN40x CP equip ment in order to put the HN40x CP equipment s 2BASE TL Ethernet port into a loopback condition where all incoming traffic received is transmitted back in the direction it came from The Hatteras HN40x CO equipment can also send a clear command to the Hatteras HN40x CP equipment to remove the loopback The looped back traf
32. r one 100BASE X port and one 10 100BASE T ports The HN40x CO and HN40x CP each have a single 10 100BASE T port In this release port 2 of HN4xx U devices can be used only as an out of band management port HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide 1 4 HN400 Family Product Overview o The HN4xx U has a RJ 45 serial interface for local configuration and management The HN40x CO and HN40x CP have a DB serial interface o The HN4xx U operates from a 48 VDC power source regardless of operating mode but has an optional external AC DC power module for AC powered deployments The HN40x CO is 48 VDC powered only the HN40x CP is AC powered only O The HN4xx U supports the enhanced rates up to 5 7 Mbps per pair of 2BASE TL and G 991 2 bis E SHDSL with over 45 Mbps possible on eight bonded pair The HN40x CO and HN40x CP devices do not yet support the E SHDSL rates The HN4xx U extends the HN400 product family by introducing a single product that can serve either as a CO or CP depending on configuration and by offering an additional 10 100BASE T port to serve multiple customers or as an out of band management facility The entire HN400 product family provides a variety of models and capabilities to serve the needs of any customer 1 1 4 Product Compatibility Table 1 2 shows the product compatibility matrix for the HN400 and HN4000 products Table 1 2 Product Compatibility A Device Installed at CO
33. r s Figure 3 2 HNA0x CP Device Connectors and LEDs Table 3 2 HN40x CP Troubleshooting Steps Condition Solution All front panel LEDs are off 1 Verify that the device is receiving 12 VDC power 2 Verify that the power cable is wired correctly see Connecting the HN40x CP s Power Module on page 3 7 3 If only one power source is being used switch the power cables to the connection that is not in use for example to the B connection if the A connections are being used 4 Replace the device with a unit known to be in proper working condition The red System FAIL LED is on In normal operation the system FAIL LED will blink on and off immediately after the device is powered up while the device runs its self test diagnostics If the system FAIL LED is on after diagnostics have run it indicates that the device has detected a hardware problem 1 Remove power from the device and power it back up 2 Replace the device with a unit known to be in proper working condition HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Troubleshooting Using Device Indicators 3 7 Table 3 2 HN40x CP Troubleshooting Steps Continued Condition Solution One or more of the numbered 2BASE TL LEDs are off In normal operation a numbered 2BASE TL LED will be off if there is no copper pair connected to the port or if a copper pair is connected at the port but is n
34. ream target SNR margin specified by the span profile is 5 dB then the upstream and downstream SNR margins that the show 2bpme command displays should be approximately 5 dB or higher If they are less than 4 dB the span profile for that copper pair must be changed in order to set the target SNR margin higher The show 2bpme command also shows the loop attenuation which is dependent on the length of the copper loop wire gauge and many other factors This value should be checked for consistency with the other copper pairs loop attenuation assuming that all the other copper loops are somewhat identical The command show pmstats numintervals 2 will provide counters of errored seconds ES CRC anomalies CRC severely errored seconds SES loss of sync word seconds LOSWS and unavailable seconds UAS for the current 15 minutes or fraction thereof and the previous 15 minutes If the copper loop is accumulating CRC anomalies at a significant rate then the SNR margin of the copper loop will have to be increased incrementally until the CRC anoma lies drop to an acceptable level Itis a good practice to set threshold crossing alerts TCA for the SNR margin loop attenuation and CRC anomalies for each copper pair This is accomplished via the span alarm profiles using the create spanAlarmProfile and config spanAlarmProfile commands The SNR mar gin TCA should be set at 2 dB which is the default retrain SNR margin The loop attenuation TCA
35. rks Access Class Ethernet Taking Ethernet the extra mile and purpose built are trademarks or registered trademarks of Hatteras Networks Inc Cisco is a registered trademark of Cisco Systems Inc All other trademarks trade names or product names used in this document are the property of their respective owners HN400 Provisioning and Troubleshooting Guide HN4 TG030NNO00 Revision History of this Effective With Description of Changes Document Revision 00 March 1 2006 HN400 System Software Updated for software release 4 6 0 Release 4 6 0 March 1 2006 Revision 0C January 9 2006 HN400 System Software Updated to include HN41x U optical devices Release 4 5 1 December 9 2005 Revision 0B December 1 2005 HN400 System Software Original document Release 4 0 0 July 13 2005 Contents 1 Introduction 1 1 HN400 Family Product Overview l l RR e rH he 1 1 1 1 1 MNAC O Products tion e hires imer OR Rob 0e eos ete ed eos er aia tero er e Rer n 1 1 1 1 2 HN40x CP Products 2 2 eiuse dae llega eed hore doe d redu m Pide pie dd 1 2 1 1 3 HN4xx U Products oo ooocoo enn net 1 3 1 1 4 Product Compatibility seire crt ccrtc tnt eh beehive Bide kbd E Ro ERU Phebe Sak ode d 1 4 1 2 The Hatteras Networks Provisioning Utilities llle 1 5 A TTD 1 5 122A EMS p05 bee eh bP bet nb baw pene AER RE eae Reg ee We eed age nem nes Rd e dad ne 1 5 1 2 3 WebManager ia 4
36. s Optical Safety Never look at the transmit LED laser through a magnifying device while it is powered on Never look directly at the fiber port or fiber cable ends when they are Caution not being used To avoid degradation of optical fiber signals and poor system performance follow appropriate local practices to ensure that optical fiber connector ends are clean and free from contamination Always install the provided dust covers on transceiver optical ports and connector ends that are HN4 TG030NNOO HN400 Provisioning and Troubleshooting Guide 3 10 Troubleshooting Using Device Indicators HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 HN400 Passwords As shipped from the factory the HN400 CLI supports a default username and password for the administrator admin privilege level Table A 1 lists these defaults Table A 1 CLI User Account Privilege Levels Privilege Default Description Level Username Password admin admin admin Administrative superuser access The user has full read write access plus access to all of the CLI s administrative commands including the ability to create and delete CLI users CLI passwords are case sensitive Note It is strongly recommended that the you change the administrative username and password fol lowing the initial installation process Users can display their assigned CLI privilege level with the CLI wh
37. te that you should be able to achieve on the copper pair Using the EWL that you determined in the previous section and the crosstalkoffset value that you intend to use 3 dB is the default and complies most closely with the ANSI T1 417 deployment guidelines determine the rate that you should be able to achieve using the black line on the rate reach curve shown in Figure 2 1 Rate Reach Summary for 26 AWG 0 4mm 25 Pair SEALPIC Cable Expected Pair Performance for 5dB SNR Margin 7 to 24 SNEXT Interferers 2 SNEXT Interferers 12 SNEXT Interferers 24 SNEXT Interferers 417 Deployment Guidelines 1 12 13 14 15 16 17 18 9 10 1 Distance K ft Figure 2 1 Rate Reach Curves For example if you determined that the EWL is 11 000 feet then the achievable rate is approxi mately 1 28 Mbps per pair If the actual rate that you achieve when you power up the HN400 software link varies from this value you may have to make some adjustments as described in the PME section below HN400 Provisioning and Troubleshooting Guide HN4 TGO30NNO0 Things To Do and Check After Completing The Hardware Installation 2 5 The operating point may also be determined by using the Hatteras Networks Rate Reach calculator 2 3 Things To Do and Check After Completing The Hardware Installation After you complete the hardware installation of the linked HN40
38. ting EWL is the equivalent working length for 26 AWG wire The gage factor is 1 00 for 26 AWG wire 75 for 24 AWG wire 60 for 22 AWG wire and 40 for 19 AWG wire These values are used in the table above and the equation is used to calculate the EWL of the copper loops Fill in the Gage Factor and calculate the EWL of the loop using the equation shown above 2 1 2 Using a Test Set If these circuit records are not available then the circuit length must be determined by using a metallic test set such as the following 9 Manufacturer Sunrise Telecom 9 Product SunSet MTT hand held unit with one module 3 Module G SHDSL HDSL2 Module SSxDSL 14 The test set has the capability of three methods to determine the length of the copper loops as described in the following sections 2 1 2 1 TDR Method The Time Domain Reflectometer TDR function of the test set operates on the principle that impedance changes on a transmission line cause reflection of electrical energy The TDR launches an electrical pulse at one end of the copper pair and then listens for reflections especially for reflections from the far end of the copper pair The TDR may also be used to find common faults associated with the copper pair Table 2 2 lists some of these common faults and their appearance on the TDR screen Table 2 2 Common TDR Faults Fault Appearance on TDR Effect on Service Bridge Tap Down spike followed by upwards bump Degrad
39. x CO in the CO POP RT or CEV and the HN40x CP on the customer premise perform and or check the following items 1 Table 2 4 Connect the 10 100BASE TX Ethernet port on the HN40x CO at the CO to the carrier Ether net switch Connect the 10 100BASE TX Ethernet port on the HN40x CP at the customer premise to the customer premise Ethernet switch IAD etc Connect the HN40x CO at the CO copper pair cables to the carrier MDF or 66 blocks Connect the HN40x CP at the customer premise copper pair cables to the customer premise 66 blocks or other copper pairs termination connection Check to make sure all mounting screws are tight Check to make sure all cables are completely plugged in and latched securely Route dress and tie down all cables After the HN40x CO link is powered up and copper loop connectivity is completed observe the LEDs for the following conditions LED Status LED Expected Status OK Green constant Fail Off Power A Green constant Power B Green constant 10 100BASE TX Link Green constant 10 100BASE TX Activity Green blinking for traffic PME Green blinking slow CPE Mode Amber constant for CPE Off for CO HN4 TG030NNO0O HN400 Provisioning and Troubleshooting Guide 2 6 Provisioning Ethernet Ports If the LEDs are in any status other than the ones shown in the table above refer to Chapter 1 Troubleshooting Guidelines or
Download Pdf Manuals
Related Search