zxdsl9806h - donbassmedia.net.ua technical documents... ·...

ZXDSL 9806HZTE Broadband Universal Access System

Troubleshooting Manual

Version 2.1

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

1.0 30/09/2009 First version

1.1 15/05/2010 Update boards information

Serial Number: sjzl20095518

Contents

Preface.............................................................. I

Troubleshooting Overview ................................1Safety Instruction........................................................... 1

Symbol Instructions........................................................ 1

Troubleshooting Scope .................................................... 2

Requirements for Maintenance Engineers........................... 3

Tools and Meters ............................................................ 3

Get In Touch.................................................................. 4

Troubleshooting Flow and Methods ...................5Troubleshooting Flow ...................................................... 5

Common Troubleshooting Methods.................................... 6

Fault Classification .......................................................... 7

ADSL/ADSL2+ Service Faults ............................9ADSL/ADSL2+ Basic Information ...................................... 9

Introduction............................................................... 9

Technology Implementation ......................................... 9

Information Collection ................................................10

Potential Result .............................................................10

Fault Location ...............................................................10

Fault Troubleshooting Flow..............................................11

User Modem Check ....................................................12

User-side Software and Hardware Configuration

Check ..............................................................13

External Line Check ...................................................13

Port Status Check ......................................................15

Data Configuration Check ...........................................16

Upper-layer Equipment Data Configuration Check ..........17

Fault Handling...............................................................17

Unable to Make a Call Or Access Internet......................17

Able to Make a Call, But Unable To Access Internet .........18

Internet Access at Low Speed .....................................19

Confidential and Proprietary Information of ZTE CORPORATION I

ZXDSL 9806H Troubleshooting Manual

Unstable Internet Access with Frequent Disconnec-

tions ................................................................20

Troubleshooting Cases....................................................20

Frequent Drops .........................................................20

Modem is Disabled While Calling..................................20

Low Access Rate Because of Subscriber Line

Problem ...........................................................21

Electrical Wire Interference Causes Modem

Disconnection ...................................................21

Normal Dialup, But Wrong User Name and Password

Prompt.............................................................21

Website Unaccessible After Successful Dialup ................22

Modem Link Established at Low Rate ............................22

Unsuccessful PPPoE Authentication...............................22

PPPoE Authentication Successful, But Website

Unaccessible .....................................................23

Low Speed Internet Access with Frequent

Disconnections ..................................................23

Packet Loss...............................................................23

VDSL2 Service Faults.......................................25VDSL2 Basic Information ................................................25

Introduction..............................................................25

Technology Implementation ........................................25



Fault Location ...............................................................27


User Modem Check ....................................................28

User-side Software and Hardware Configuration

Check ..............................................................29

External Line Check ...................................................29

Port Status Check ......................................................31

Data Configuration Check ...........................................32


VoIP Service Faults .........................................35VoIP Basic Information ...................................................35

Introduction..............................................................35




II Confidential and Proprietary Information of ZTE CORPORATION

Fault Location ...............................................................36


User Phone Check......................................................38

Lines Check ..............................................................39

User Port Running Status Check ..................................40

Equipment Running Status Check ................................41

RTP Resource Data Configuration Check........................42

User Service Data Configuration Check .........................42

H.248 Link Status Check ............................................43


SS Data Configuration Check.......................................43

Fault Handling...............................................................44

No Dialing Tone After Hook-Off ....................................44

Busy Tone When Hook-Off ..........................................44

Busy Tone When Dialing ............................................44

Unreliable Calling Connection ......................................45

Call Drop..................................................................45

Noise in Call..............................................................45

Unable to Hear Calling Party........................................46


Abnormal H.248 Link .................................................46

No Number Display Because of Splitter .........................47

Unsuccessful Fax Service ............................................47

Hearing SIT Tone After Dialup .....................................47

Multicast Service Faults...................................49Multicast Basic Information .............................................49

Introduction..............................................................49




Fault Location ...............................................................51


STB Check................................................................52

User Port Service Data Configuration Check ..................52

Multicast Data Configurations Check.............................52

Multicast Programme Configuration Check.....................53


User Cannot Watch Video ...........................................53

Static User and DHCP User Cannot Receive IPTV

Service ............................................................53

Confidential and Proprietary Information of ZTE CORPORATION III


System Faults..................................................55Information Collection ....................................................55



Equipment Working Environment Check........................57

Hardware Running Status Check..................................57

Fault Handling...............................................................59

Fails to View Message Through HyperTerminal ...............59

Startup Failure after Version Update.............................59


ISP Chip Works Abnormally.........................................59

Narrowband Card Offline ............................................60

Broadband Card Offline ..............................................60

NM Faults ........................................................61NM Basic Information.....................................................61

NM Installation and Configuration Requirements ............61

Operating System and Database..................................62

NM Server and Client Configuration in case of Multiple

IPs ..................................................................62

NMS and SQL Server 2005 Installation in Window

2003................................................................63

Mysql Installation ......................................................64

SUN + ORACLE Environment.......................................65

Basic NMS Installation and Configuration..............65

NMS Start-up in UNIX........................................66

Problems Related to Oracle Installation ................66

SID Configured in Oracle Inconsistent with

NMS.....................................................67

Solaris Commands ............................................68


Fault Location ...............................................................70

NMS Fault Troubleshooting Flow.......................................71

NM Environment Check ..............................................71

NM Server Operating System Configuration Check..........73

Database System Running Check.................................74

Logic Connection between NM and Database .................74

NM Basic Information Configuration Check ....................74

NM System Right Configuration Check ..........................75

NE SNMP Configuration Check .....................................75

NM Fault Handling .........................................................75

IV Confidential and Proprietary Information of ZTE CORPORATION

Unable to Ping In-band NM .........................................75

Data and Version Upload/Download Unsuccessful ...........76

NMS Fails to Receive NE Alarm Messages ......................76

Unable To Start Client ................................................77

NM Server Startup Failure...........................................77

Figures ............................................................79

Tables .............................................................81

Index ..............................................................83

Glossary ..........................................................85

Confidential and Proprietary Information of ZTE CORPORATION V


This page is intentionally blank.

VI Confidential and Proprietary Information of ZTE CORPORATION

Preface

Purpose This manual provides the methods for troubleshooting on theZXDSL 9806H (V2.1) ZTE Broadband Universal Access System.

IntendedAudience

This manual is intended for engineers and technicians who performoperation and maintenance activities on the ZXDSL 9806H (V2.1)ZTE Broadband Universal Access System.

Prerequisite Skilland Knowledge

To use this document effectively, users should have a basic conceptof xDSL technologies, telecommunications technology, and AccessNetwork.

What Is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1,TroubleshootingOverview

Introduces troubleshooting scope, safetyinstruction and symbols.

Chapter 2,TroubleshootingFlow and Methods

Describes troubleshooting flow and methods.

Chapter 3,ADSL/ADSL2+Service Faults

Describes ADSL/ADSL2+ service faultstroubleshooting and common faults handling.

Chapter 4, VDSL2Service Faults

Describes VDSL2 service faults troubleshootingand common faults handling.

Chapter 5, VoIPService Faults

Describes VoIP service faults troubleshootingand common faults handling.

Chapter 6, MulticastService Faults

Describes multicast service faultstroubleshooting and common faults handling.

Chapter 7, SystemFaults

Describes system faults troubleshooting andcommon faults handling.

Chapter 8, NMFaults

Describes NM faults troubleshooting andcommon faults handling.

RelatedDocumentation

The following documentation is related to this manual:

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemDocumentation Guide

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access ProductInformation

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemFeature Description

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemHardware Description

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemTroubleshooting Manual

Confidential and Proprietary Information of ZTE CORPORATION I


� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemRoutine Maintenance

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemVersion Update

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemNetwork Management User Manual

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemConfiguration Manual (CLI)

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemConfiguration Manual (NetNumen)

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemCommand Manual (Volume I)

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemCommand Manual (Volume II)

� ZXDSL 9806H (V2.1) ZTE Broadband Universal Access SystemCommand Manual (Volume III)

How to Get inTouch

The following sections provide information on how to obtain sup-port for the documentation and the software.

If you have problems, questions, comments, or sugges-tions regarding your product, contact us by e-mail at [email protected]. You can also call our customer support centerat (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the quality andusefulness of this document. For further questions, comments, orsuggestions on the documentation, you can contact us by e-mailat [email protected]; or you can fax your comments and sugges-tions to (86) 755 26772236. You can also browse our websiteat http://support.zte.com.cn, which contains various interestingsubjects like documentation, knowledge base, forum and servicerequest.

Declaration ofRoHS Compliance

To minimize the environmental impact and take more responsi-bility to the earth we live, this document shall serve as formaldeclaration that manufactured by ZTE CORPORATION is in com-pliance with the Directive 2002/95/EC of the European Parliament- RoHS (Restriction of Hazardous Substances) with respect to thefollowing substances:

� Lead (Pb)

� Mercury (Hg)

� Cadmium (Cd)

� Hexavalent Chromium (Cr (VI))

� PolyBrominated Biphenyls (PBB’s)

� PolyBrominated Diphenyl Ethers (PBDE’s)

This declaration is issued based on our current level of knowledge.Since conditions of use are outside our control, ZTE CORPORATIONmakes no warranties, express or implied, and assumes no liability inconnection with the use of this information.

II Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

TroubleshootingOverview

Table of ContentsSafety Instruction............................................................... 1Symbol Instructions............................................................ 1Troubleshooting Scope ........................................................ 2Requirements for Maintenance Engineers............................... 3Tools and Meters ................................................................ 3Get In Touch...................................................................... 4

Safety InstructionWhen the system is operational, observe the following safety in-structions to avoid serious damages:

� Only professional personnel who have taken proper trainingscan install, operate, and maintain the equipment.

� Follow local safety precautions and relevant procedures duringequipment installation, operation, and maintenance to avoidpersonal injury or equipment damage.

ZTE does not bear any liabilities incurred by violation of the uni-versal safety operation requirements, or violation of the safetystandards for installation and configuration of the system.

Note:

Safety precautions introduced in this manual are only supplemen-tary to local safety specifications.

Symbol InstructionsTable 1 lists the safety symbols in this manual. These symbols areused to provide safety tips during equipment installation, opera-tion and maintenance.

Confidential and Proprietary Information of ZTE CORPORATION 1


TABLE 1 SAFETY SYMBOLS

Safety Symbol Meaning

Caution!

Antistatic sign

Danger! Electric shock!

Caution, scald

Caution, laser

Caution, microwave

There are four levels of safety symbols: Danger, Warning, Caution,and Note.

Table 2 describes the safety symbol levels.

TABLE 2 SAFETY SYMBOL LEVELS

Level Description

Danger

Failure to observe the safetyinstructions will result in death orequipment damage.

Warning

Failure to observe the safetyinstructions may result in seriouspersonal injury or equipmentdamage.

Caution

Failure to observe the safetyinstructions may result in minoror moderate personal injury orequipment damage.

Note

Provides description and tips tohelp operation and maintenance.

Troubleshooting ScopeThis manual covers the troubleshooting of the following faults:

� ADSL/ADSL2+ service faults

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Troubleshooting Overview

� VDSL2 service faults

� VoIP service faults

� Multicast service faults

� System faults

� Network management faults

Requirements forMaintenance EngineersTable 3 lists the requirements for maintenance engineers.

TABLE 3 REQUIREMENTS FOR MAINTENANCE ENGINEERS

Type Requirement

Knowledge about Ethernetprotocols

Knowledge about TCP/IP protocols

Knowledge about xDSL technology

Knowledge about multicastprotocols

Technology knowledge

Knowledge about H.248 protocol

Knowledge about ZXDSL 9806Hhardware configuration

Knowledge about ZXDSL 9806Hcard functions and interfaces

Equipment knowledge

Knowledge about ZXDSL 9806Hnetworking

Knowledge about maintenance onZXDSL 9806H

System operation andmaintenance techniques

Knowledge about operation onZXDSL 9806H series products

Tools and meters Knowledge about the usage oftools and meters

Tools and MetersTable 4 describes the tools and meters used for maintenance.



TABLE 4 TOOLS AND METERS

Name Description

Snipe-nose pliers It is used to grip objects inconfined spaces.

Wire-stripping pliers It is used to cut and removeinsulation on electrical wire whileleaving the wire intact.

Diagonal pliers It is used to cut wires.

Antistatic wrist strap It is used to prevent electrostaticdischarge.

Ethernet cable tester It is used to test cable connection.

Optical power meter It is used to test optical power.

Multimeter It is used to measure voltage,current and resistance.

Ground resistance tester It is used to measure groundresistance.

Tape measure It is used to measure length.

Get In TouchThe maintenance engineer can use the following information toobtain support for troubleshooting:

� Website: [email protected]

� Hotlines:

� 800-830-1118

� 400–830–1118

� Fax: 0755–26770801

� E-mail: [email protected]


C h a p t e r 2

Troubleshooting Flowand Methods

Table of ContentsTroubleshooting Flow .......................................................... 5Common Troubleshooting Methods........................................ 6Fault Classification .............................................................. 7

Troubleshooting FlowFigure 1 shows troubleshooting flow.



FIGURE 1 TROUBLESHOOTING FLOW

Common TroubleshootingMethodsThe following are common troubleshooting methods :

� Observation

When a fault occurs, maintenance engineers need to observeit at first.

� Observe indicators on the card, such as the RUN and ALMindicators.

� Observe the alarm box indicator.

� Observe the alarm information on the NMS (maintenanceconsole).

� Plugging/unplugging

When a card does not work normally, unplug and then plug thecard. Sometimes, a card works unusually due to poor contact.


Chapter 2 Troubleshooting Flow and Methods

Caution:

While plugging/unplugging a card, make sure that the card ishot-swappable. The maintenance engineer must put on theantistatic wrist strap.

� Card replacement

Replace the card with a new one if the fault still exists afterplugging/unplugging the card.

� Alarm log analysis

Alarm logs are information displayed on the NMS terminal.Alarm logs help maintenance engineers to check the system'srunning status and locate the fault.

� Component replacement

Replace the faulty component with a spare component if it isdifficult to locate a fault.

� PING command

For network faults, execute the ping command to locate thefault.

� Isolation

When one part of the system is faulty, isolate the system fromthe equipment which is relevant to the faulty part. The faultyequipment may have an influence on the running of the rele-vant part of the system.

� Self-test

When the system or cards are powered ON, they have a self-test. The indicators on a card tell whether the card works nor-mally or not.

� Press

Pressing a chip or cable connector can remove the fault due topoor contact.

Fault ClassificationFaults can be classified into the following categories:

� ADSL/ADSL2 service faults

� VDSL2 service faults

� VoIP service faults

� Multicast service faults

� System faults

� NM faults


C h a p t e r 3

ADSL/ADSL2+ ServiceFaults

Table of ContentsADSL/ADSL2+ Basic Information .......................................... 9Potential Result .................................................................10Fault Location ...................................................................10Fault Troubleshooting Flow..................................................11Fault Handling...................................................................17Troubleshooting Cases........................................................20

ADSL/ADSL2+ BasicInformationThis topic introduces ADSL/ADSL2+ technology and its implemen-tation in ZXDSL 9806H.

Introduction

ADSL uses the FDM technology. ADSL allows more downstreambandwidth from central office to customer site than upstream. Theupstream uses the frequency band from 30 KHz to 138 KHz. Thedownstream uses the frequency band from 138 KHz to 1.104 MHz.The upstream rate can reach up to 1 Mbps and downstream ratecan reach up to 8 Mbps.

ADSL2+ is a new generation of ADSL broadband service accesstechnology. Compared with ADSL, ADSL2+ supports higher rate,wider frequency and more sub-bands (512 sub-bands). The up-stream rate can reach up to 1 Mbps and downstream rate can reachup to 24 Mbps. The longest transmission distance is 6.5 Km.

Technology Implementation

ZXDSL 9806H provides ASTDE and ASTEB cards to supportADSL/ADSL2+ service access.



� ASTDE card provides 16-route ADSL/ADSL2+ subscriber inter-faces and POTS interfaces.

� ASTEB card provides 24-route ADSL/ADSL2+ subscriber inter-faces and POTS interfaces.

Information Collection

Item Related Command Description

Show card interfacestatus.

show interfaceslot/port-list

When a card worksnormally, theLinkStatus is Up.

Show card interfaceVLAN.

show interfaceslot/port-listvlan-config

Check the interfaceVLAN configuration.

Show ADSL lineprofile.

show adsl profilefilename

Check ADSL lineparameters.

Show ADSL interfacestatus.

show interfaceslot/port-listport-status

Check ADSL inter-face status and up-stream/downstreamrate.

Show port PVCconfiguration.

show atm vcslot/port

Make sure VPI/VCIsetting on Modem isconsistent with thaton DSLAM.

Potential ResultDuring the process of removing a fault, the following operationsaffect the user service:

� Card reset

� Plugging or unplugging of the card.

Fault LocationTable 5 describes ADSL/ADSL2+ service faults and causes. Themaintenance engineer can locate the fault according to descrip-tions in this table.


Chapter 3 ADSL/ADSL2+ Service Faults

TABLE 5 ADSL/ADSL2+ SERVICE FAULT LOCATION

Fault Description Fault Cause

Some user cannot access theInternet.

� The user Modem does notwork normally.

� There is software or hardwareproblem at the user side.

� The external line is faulty.� ZXDSL 9806H user port is

faulty.� ZXDSL 9806H data is not

configured properly.

All users of one card cannotaccess the Internet.

� The card connected to theseusers is faulty.

� ZXDSL 9806H backplane isfaulty.

� ZXDSL 9806H main controlcard is faulty.

All users of a whole shelf cannotaccess the Internet.

� ZXDSL 9806H uplink port isfaulty.

� ZXDSL 9806H data is notconfigured properly.

� ZXDSL 9806H system isfaulty.

� The upper-layer network isfaulty.

Fault Troubleshooting FlowFigure 2 shows ADSL/ADSL2+ service fault troubleshooting flow.



FIGURE 2 ADSL/ADSL2+ SERVICE FAULT TROUBLESHOOTING FLOW

User Modem Check

Check the user modem. Indicators show modem's working status.Table 6 describes indicators' status. This topic takes ZXDSL 831Aas an example.

TABLE 6 MODEM FAULT LOCATION

Indicator Status Description

OFF Modem is not poweredON or modem isfaulty.

PWR

ON If PWR is ON andother indicators areall OFF, modem isfaulty.

ON Modem is activated.

OFF Modem is failedto detect signals.

DSL



Indicator Status DescriptionOr, modem is notactivated.

Flashing Modem is failedto detect signals.Or, modem is notactivated.

ON Ethernet is connected.LAN

OFF Modem is notconnected to thenetwork card. Or, thenetwork card is faulty.

ON Modem is connectedto the computer.

USB

OFF Modem is notconnected to thecomputer. Or, thecomputer's USBinterface is faulty.

DIAG ON There is modemversion problem.

User-side Software and HardwareConfiguration Check

If the user's modem works normally, check the software and hard-ware configuration, including:

� Cable connection

� Network card

� Dial-up software

� Virus scan

� Firewall

External Line Check

Check the external lines at user side and office side.

� External line check at user side

� Voltage between Line A and Line B

� Resistance between Line A and Line B

� Capacitance between Line A and Line B

� Line length

� External line check at office side



� TDR test

� PSD test

� SNR test

� Pulse noise test

ADSL subscriber line must meet the requirements described inTable 7.

TABLE 7 ADSL SUBSCRIBER LINE REQUIREMENTS

Requirement Remark

There is no extra inductor onsubscriber lines.

If a telephone is connected withthe modem, locate the splitterbefore the phone and modem.

A subscriber line must be a twistedpair copper wire.

If the service wire is a four-corewire, it is recommended to usea four-core twisted pair cableinstead of a four-core parallelwire. For four-core parallel wire,use one pair and leave the otheridle. The length must not exceed20 meters.

There is no shielding requirementfor subscriber lines.

-

Use subscriber lines withoutbridge taps.

-

The insulation resistance oftwo subscriber lines to theground must be greater than 5megaohms.

-

The direct loop resistance ofsubscriber line must be not largerthan 1.1 kiloohms.

-

The capacitance betweensubscriber lines must be less than200 nF . The capacitance betweensubscriber lines and the groundmust be less than 5%.

If the capacitance is smaller than150 nF, the Internet access speedcan be more stable and higher.

The near end crosstalk ratio mustbe greater than 50 dB and the farend crosstalk ratio is the total ofthe near end crosstalk ratio andthe line attenuation.

–

The idle channel noise must besmaller than or equal to -55dBm. The average noise powerspectrum density is smaller thanor equal to -115 dBm/Hz.

–

The nominal characteristicimpedance of the line is 100 ohm,with a maximum of 10% errorallowed.

–



Requirement Remark

Within the frequency range of 26kHz – 1104 kHz, the longitudinalconversion loss must be greaterthan or equal to 50 dB. In specialconditions, it can be greater than40 dB.

–

Table 8 lists attenuations of ADSL subscriber lines with differentline diameters. The unit for attenuation value is dB.

TABLE 8 CABLE PAIRS ATTENUATIONS PER KILOMETER

f(kHz)

40 60 80 120 150 300 1024

0.32mm

11.4 13.01 14.38 15.12 16.8 18.13 33.5

0.4mm

8.29 9.34 10.05 10.87 12.1 14.78 27.3

0.5mm

5.99 6.85 7.06 7.77 9 12.18 22.5

Table 9 lists maximum frequency attenuations.

TABLE 9 MAXIMUM FREQUENCY ATTENUATIONS

Frequency f(Hz) Maximum Attenuation

60 37

150 69

300 52

400 60

500 67

600 72

If the attenuation is greater than the maximum value, the ADSLservice is not available. Even if the service is launched, the perfor-mance and stability are not guaranteed. When the line attenuationof relevant sub-band’s carrier frequency is greater than 70 dB, theline cannot carry any information.

Port Status Check

Card Indicators Table 10 describes LED indicators on SCCB card.



TABLE 10 LED INDICATORS ON SCCB

Indicator Color Status Description

RUN Green Flashing Card is workingnormally.

Green ON Power isworkingnormally.

PWR

OFF Power isnot workingnormally.

Green ON Link isconnected.

L1, L2 (Opticalinterface linkindicators)

OFF Link is notconnected.



Yellow Flashing The interface isreceiving/trans-mitting data.

Electricalinterface/linkindicator

OFF The interfaceis not receiv-ing/transmit-ting data.

Port Status Execute the show interface slot/portlist command to check portstatus. In normal status, the LinkStatus is Up.

Execute the show interface slot/portlist port-status commandto check port status and rate.

Data Configuration Check

Check the following data configurations:

� VLAN configuration

Execute the show interface slot/portlist vlan-config com-mand to check the port's VLAN configuration.

� PVC configuration

Execute the show atm vc slot/portlist command to check theport's VPI/VCI configuration.

� ADSL line profile configuration

Execute the show adsl profile profilename command to checkADSL line profile configuration, focusing on the following pa-rameters:



� AtucConfTargetSnrMgn

� ConfProfileLineType

� AtucChanConfFastMaxTxRate

� AtucChanConfFastMinTxRate

� AtucChanConfInterleaveMaxTxRate

� AtucChanConfInterleaveMinTxRate

� AtucChanConfMaxInterleaveDelay

� AturConfTargetSnrMgn

� AturChanConfFastMaxTxRate

� AturChanConfFastMinTxRate

� AturChanConfInterleaveMaxTxRate

� AturChanConfInterleaveMinTxRate

� AturChanConfMaxInterleaveDelay

Upper-layer Equipment DataConfiguration Check

If there is no problem with the equipment hardware and dataconfiguration, check data configurations of the upper-layer equip-ment, including:

� Corresponding interface status

� Interface rate mode

� Interface security

� Interface access control

� Traffic limit

Fault HandlingThis section introduces ADSL/ADSL2+ service fault handling.

Unable to Make a Call Or AccessInternet

Symptom The user cannot make a call or access the Internet.

Troubleshooting 1. Check user-side line.

2. Check office-side line.

3. If there is no problem with lines, check the splitter.



Able to Make a Call, But Unable ToAccess Internet

Symptom Users are able to make calls, but unable to access the Internet.

Troubleshooting This fault involves all parts of the system networking. Check themodem indicators, user’s computer setting and equipment at thelocal office.

1. Check modem indicators.

This topic takes ZXDSL 831A as an example. Table 11 describesindicators' status.



OFF Modem is notpowered ON ormodem is faulty.

PWR

ON If PWR is ON andother indicators areall OFF, Modem isfaulty.

ON Modem is activated.

OFF Modem is failedto detect signals.Or, modem is notactivated.

DSL

Flashing Modem is failedto detect signals.Or, modem is notactivated.

ON Ethernet isconnected.

LAN

OFF Modem is notconnected to thenetwork card. Or,the network card isfaulty.

ON Modem is connectedto the computer.

USB

OFF Modem is notconnected to thecomputer. Or, thecomputer's USBinterface is faulty.

DIAG ON There is modemversion problem.

2. Check the dial-up software if the modem is working normally.



� If the user fails to dial up, reinstall the dial-up software.

� Set the computer's TCP/IP properties correctly. For dial-upusers, the IP addresses are obtained automatically.

� Set the format of dial-up account correctly.

� Set the password of dial-up account correctly.

3. Check the following if PPPoE dial-up is successful, while au-thentication is failed.

� If the system uses Ethernet interface for uplink and theuser uses PPPoE software, check whether upper-layer ser-vice exists at user side. If upper-layer service exists, it isupper-layer server configuration problem. If upper-layerservice does not exist, it may be system data configurationproblem.

� If the user uses the dial-up software of the system or otherdial-up software, check authentication process. If authen-tication is successful, while Internet access fails, it is up-per-layer server configuration problem. If authenticationfails, it may be system data configuration problem.

4. Both PPPoE dial-up and authentication are successful. It stillfails to access the Internet. Try different websites. If it fails toopen other websites also, it is access server problem.

5. Configurations at both the user side and office side are correct.If it still fails to access the Internet, check the lines.

Internet Access at Low Speed

Symptom Users can access the Internet, but the access speed is very low.

Troubleshooting 1. If all users access the Internet at low speed, check traffic con-trol, QoS and rate configurations at both ZXDSL 9806H andupper-layer access server.

2. If only some users access the Internet at low speed, check thefollowing:

� Open the relevant line profile. Check the maximum up-stream/downstream rate settings.

� Check the bit error ratio of the line. If the bit error ratio istoo large, decrease bandwidth or increase noise tolerance.If the fault exists, use a line tester to locate the fault.

3. If only interleaved-channel users access the Internet at lowspeed, check the following:

� Modify the line profile of interleaved-channel users to be theline profile of users who can access the Internet normally.

� Check the relevant line profile, especially maximum up-stream/downstream rate and interleaving depth.



Unstable Internet Access withFrequent Disconnections

Symptom Internet access is not stable and disconnection occurs frequently.

Troubleshooting 1. Check the length of ADSL/ADSL2+ subscriber line. ADSL sub-scriber line cannot exceed 3 km. ADSL2+ subscriber line can-not exceed 5 km.

2. Check whether there is an electrical interference near modem.

3. Check the location of splitter.

4. Check subscriber line contact.

5. Check line quality.

Troubleshooting CasesThis section introduces ADSL/ADSL2+ service troubleshootingcases.

Frequent Drops

Symptom Drops occur frequently in a cyber café.

Troubleshooting 1. Test background noise.

The incoming subscriber line is parallel line. It is about 40meters. Besides, the cyber café is near the road. The back-ground noise is too high. Many frequency points are around-100 dBm/Hz. Some frequency points are around -80 dBm/Hz.It is far beyond the requirement, which is -110 dBm/Hz.

2. Use twisted pairs cable.

Modem is Disabled While Calling

Symptom When the user makes a call, the modem is disabled.

Troubleshooting 1. Check the modem.

2. Check the user card.

3. Disconnect user-side line. Test the user line near the distribu-tion frame in the equipment room. The fault does not occur.

4. Test the user line near the distribution frame in district wherethe user lives. The fault does not occur.



5. Check the user's junction box. A pair of phone line is con-nected improperly. Connect the phone line again. The fault isremoved.

Low Access Rate Because ofSubscriber Line Problem

Symptom ADSL service is configured. The Internet access rate is very slow.Sometimes the user fails to open a website.

Troubleshooting 1. CheckZXDSL 9806H data configuration, including up-stream/downstream rate, noise margin and channel mode.

2. Check the incoming subscriber line. The subscriber line is par-allel line. Use twisted pairs cable. The access rate is enhanced.

Electrical Wire Interference CausesModem Disconnection

Symptom ADSL service is not stable. Modem is disconnected frequently.

Troubleshooting 1. Check the voltage. The voltage is normal.

2. Replace the relevant port, modem and external line trunk. Thefault exists.

3. Connect a modem at the junction box. Modem works normally.Connect a modem at the subscriber line. Modem does notwork. There is interference from the junction box to subscriberline.

4. Check the junction box to subscriber line. One part is 30 cen-timeters away from an electrical wire. Move the electrical wire100 centimeters away from the subscriber line. The fault isremoved.

Normal Dialup, But Wrong UserName and Password Prompt

Symptom The dial-up process is normal. The wrong user name and passwordprompt appears after entering user name and password.

Troubleshooting 1. Check the user name and password. Make sure both passwordand user name are right.

2. Check BAS configuration.

3. Check switch or route configuration.

4. Check authentication server configuration.



Website Unaccessible AfterSuccessful Dialup

Symptom ADSL service is provisioned. PPPoE dial-up is successful. However,the user fails to access the Internet or ping any website.

Troubleshooting 1. After successful dial-up, check IP assignment and DNS infor-mation. If both IP address assignment and DNS is shown nor-mally, it is not BAS problem.

2. Execute the winipcfg command to check the computer IP.

3. If the computer IP is '0.0.0.0', it is the computer problem. Re-place the computer.

Modem Link Established at Low Rate

Symptom Modem link is established successfully. But the rate is too slow.

Troubleshooting 1. Check subscriber line, including line attenuation and line noise.

2. Check modem. If the modem cannot work normally, replace it.

3. Check ADSL subscriber card.

4. Check ZXDSL 9806H user port rate configurations. If the linkestablishment rate is the same as the configured rate, it is nota fault.

Unsuccessful PPPoE Authentication

Symptom ADSL link is established but PPPoE authentication fails.

Troubleshooting 1. Check PPPoE user name and password.

2. Check network card.

3. Check PPPoE dial-up software.

4. Check broadband card status.

5. Check ZXDSL 9806H data configuration. Make sure user portVLAN configuration is consistent with uplink port VLAN config-uration.

6. Check broadband uplink port status.

7. Check connection between ZXDSL 9806H and BAS.

8. Check BAS data configuration and running status.



PPPoE Authentication Successful,But Website Unaccessible

Symptom PPPoE authentication is successful but the user fails to access web-site.

Troubleshooting 1. Check TCP/IP settings, especially DNS.

2. Check IE settings. Do not select 'Automatically detect settings'.

3. For Windows users, if TCP/IP and IE settings are correct, installADSL dial-up software again.

4. If the user uses LAN. Check LAN networking.

5. Check BAS data configuration and BAS running status.

Low Speed Internet Access withFrequent Disconnections

Symptom Users access the Internet at low speed and disconnection occursfrequently.

Troubleshooting 1. If the modem is not compatible, use other modem type.

2. Check the networking at the user side.

3. Check modem settings. Generally, if the built-in dial-up func-tion is already enabled, do not enable bridging function.

4. Check duplex rate mode.

5. Check card parameters and line specifications. Modify param-eters such as noise margin and delay.

6. Check upper-layer network and BAS configurations.

Packet Loss

Symptom The Internet access rate is too slow and there is packet loss.

Troubleshooting 1. Check ZXDSL 9806H optical power. Both the receiving andtransmitting optical power should be normal.

2. Check the optical power of uplink equipment. There is receivedoptical power loss. Clean the fiber pigtail. The fault still exits.

3. Check ODF in the equipment room. If there is some problemwith the flange, replace the flange. Clean fiber pigtail. Test theoptical power again. It is normal. The Internet access rate isenhanced but there is packet delay.

4. Check the line profile. The line mode is interleaved. Changethe interleaved mode to be fast channel mode. The fault isremoved.


C h a p t e r 4

VDSL2 Service Faults

Table of ContentsVDSL2 Basic Information ....................................................25Potential Result .................................................................26Fault Location ...................................................................27Fault Troubleshooting Flow..................................................27

VDSL2 Basic InformationThis topic introduces VDSL2 technology and its implementation inZXDSL 9806H.

Introduction

VDSL2, the second generation of VDSL, provides high-bandwidthaccess, with symmetric and asymmetric transmission rates.VDSL2 uses DMT technology.

VDSL2 features are as follows:

� Compatible with ADSL/ADSL2/ADSL2+

� ITU-T VDSL2 standard (G.993.2) compliant

� Supports symmetric rate up to 100 Mbps

� Supports Triple-play services, including data service, VoIP,IPTV andHDTV

� Multiple band-plan definitions


ZXDSL 9806H provides VSTDC card to support VDSL2 service ac-cess.

VSTDC provides 16-route VDSL2 subscriber interfaces and POTSinterfaces.



Its maximum transmission distance is 2.5 Km. Its downstreamtransmission rate reaches up to 85 Mbps and upstream transmis-sion rate reaches up to 50 Mbps.



Show card interfacestatus.

show interfaceslot/port-list

When a card worksnormally, theLinkStatus is Up.

Show card interfaceVLAN.

show interfaceslot/port-listvlan-config

Check the interfaceVLAN configuration.

Show VDSL2 lineprofile.

show vdsl2base-profilefilename

show vdsl2dpbo-profilefilename

show vdsl2upbo-profilefilename

show vdsl2service-profilefilename

Check VDSL2 lineparameters.

Show VDSL2 interfacestatus.

show interfaceslot/port-listport-status

Check VDSL2 inter-face status and up-stream/downstreamrate.

Show port PVCconfiguration.

show atm vcslot/port

Make sure VPI/VCIsetting on Modem isconsistent with thaton DSLAM.


� Card reset



Chapter 4 VDSL2 Service Faults

Fault LocationTable 12 describes VDSL2 service faults and causes. The main-tenance engineer can locate the fault according to descriptions inthis table.

TABLE 12 VDSL2 SERVICE FAULT LOCATION


Some user cannot access theInternet.

� The user Modem does notwork normally.

� There is software or hardwareproblem at the user side.

� The external line is faulty.� ZXDSL 9806H user port is

faulty.� ZXDSL 9806H data is not


All users of one card cannotaccess the Internet.


� ZXDSL 9806H backplane isfaulty.

� ZXDSL 9806H main controlcard is faulty.

All users of a whole shelf cannotaccess the Internet.

� ZXDSL 9806H uplink port isfaulty.

� ZXDSL 9806H data is notconfigured properly.

� ZXDSL 9806H system isfaulty.

� The upper-layer network isfaulty.

Fault Troubleshooting FlowFigure 3 shows VDSL2 service fault troubleshooting flow.



FIGURE 3 VDSL2 SERVICE FAULT TROUBLESHOOTING FLOW

User Modem Check

Check the user modem. Indicators show modem's working status.Table 13 describes indicators' status.



OFF Modem is not poweredON or modem isfaulty.

PWR

ON If PWR is ON andother indicators areall OFF, modem isfaulty.

ON Modem is workingnormally.

OFF Modem does notwork. Connect thephone line properly.

VDSL Link




Flashing VDSL line is notstable.

LAN Activity Flashing The interface isreceiving/transmittingdata.

ON (Green) Ethernet is connected.Ethernet rate is 10Mbps.

ON (Orange) Ethernet is connected.Ethernet rate is 100Mbps.

LAN Link

OFF Modem is notconnected to thenetwork card. Or, thenetwork card is faulty.

User-side Software and HardwareConfiguration Check

If the user's modem works normally, software and hardware con-figuration check includes:

� Cable connection

� Network card

� Dial-up software

� Virus scan

� Firewall

External Line Check

Check the external lines at user side and office side.

� External line check at user side

� Voltage between Line A and Line B

� Resistance between Line A and Line B

� Capacitance between Line A and Line B

� Line length

� External line check at office side

� TDR test

� PSD test

� SNR test

� Pulse noise test



VDSL subscriber line must meet the requirements described inTable 14.

TABLE 14 VDSL SUBSCRIBER LINE REQUIREMENTS

Requirement Remark

There is no extra inductor onsubscriber lines.

If a telephone is connected withthe modem, locate the splitterbefore the phone and modem.

A subscriber line must be a twistedpair copper wire.

If the service wire is a four-corewire, it is recommended to usea four-core twisted pair cableinstead of a four-core parallelwire. For four-core parallel wire,use one pair and leave the otheridle. The length must not exceed20 meters.

There is no shielding requirementfor subscriber lines.

-

VDSL subscriber line is less than1 Km.

The appropriate length for VDSLsubscriber line is not longer than1 Km.

Use subscriber lines withoutbridge taps.

-

The insulation resistance oftwo subscriber lines to theground must be greater than 5megaohms.

-

The direct loop resistance ofsubscriber line must be not largerthan 220 ohms.

-

The capacitance betweensubscriber lines must be less than40 nF . The capacitance betweensubscriber lines and the groundmust be less than 5%.

-

The near end crosstalk ratio mustbe greater than 50 dB and the farend crosstalk ratio is the total ofthe near end crosstalk ratio andthe line attenuation.

–

The idle channel noise must besmaller than or equal to -55dBm. The average noise powerspectrum density is smaller thanor equal to -115 dBm/Hz.

–



Requirement Remark

The nominal characteristicimpedance of the line is 100 ohm,with a maximum of 10% errorallowed.

–

Within the frequency range of 900kHz – 7.9 MHz, the longitudinalconversion loss must be greaterthan or equal to 50 dB. In specialconditions, it can be greater than40 dB.

–

Table 15 lists attenuations of VDSL subscriber lines with differentline diameters. The unit for attenuation value is dB.

TABLE 15 CABLE PAIRS ATTENUATIONS PER KILOMETER

f(kHz)

40 60 80 120 150 300 1024

0.32mm

11.4 13.01 14.38 15.12 16.8 18.13 33.5

0.4mm

8.29 9.34 10.05 10.87 12.1 14.78 27.3

0.5mm

5.99 6.85 7.06 7.77 9 12.18 22.5

Table 16 lists maximum frequency attenuations.

TABLE 16 MAXIMUM FREQUENCY ATTENUATIONS

Frequency f(Hz) Maximum Attenuation

60 7.47

150 9.6

300 11.8

1000 22

Port Status Check








PWR










Port Status Execute the show interface slot/portlist command to check portstatus. In normal status, the LinkStatus is Up.

Execute the show interface slot/portlist port-status commandto check port status and rate.

Data Configuration Check

Check the following data configurations:

� VLAN configuration

Execute the show interface slot/portlist vlan-config com-mand to check the port's VLAN configuration.

� VDSL2 line profile configuration

Execute the show vdsl2 service-profile profilename com-mand to check VDSL2 line profile configuration, focusing onthe following parameters:

� AtucConfTargetSnrMgn

� Ch1ProfMaxDataRateDs/Ch1ProfMaxDataRateUs

� Ch1ProfMaxDelayDs/Ch1ProfMaxDelayUs



� Ch1ProfMinProtectionDs/Ch1ProfMinProtectionUs


If there is no problem with the equipment hardware and data con-figuration, check the data configurations of the upper-layer equip-ment, including:





� Traffic limit


C h a p t e r 5

VoIP Service Faults

Table of ContentsVoIP Basic Information .......................................................35Potential Result .................................................................36Fault Location ...................................................................36Fault Troubleshooting Flow..................................................37Fault Handling...................................................................44Troubleshooting Cases........................................................46

VoIP Basic InformationThis topic introduces VoIP technology and its implementation inZXDSL 9806H.

Introduction

VoIP is a general term for a family of transmission technologiesfor delivery of voice communications over the IP network. VoIPsystems usually interface with the traditional PSTN to allow fortransparent phone communications.

VoIP architecture contains the following parts:

� Media gateway

� Media gateway controller

� Voice server

� Signalling gateway


ZXDSL 9806H supports H.248 protocol. It provides VoIP service.The VoIP sub-card, which is built in the control and switch card,implements the VoIP service. A single ZXDSL 9806H system sup-ports 128–route VoIP subscribers.





View narrowbandattributesconfiguration.

get- mgbaseattr Check the protocoltype and port number.

View narrowbandcapacityconfiguration.

get-mgcapabili -

View MGCconfiguration.

get- mgc Check MGC type, IPaddress, port whichcommunicates withMG.

View VoIPconfiguration.

get-voip-config Check MGsignaling andmedia informationconfiguration.

View narrowband userline attributes.

get-slcattrib Check user linestatus and attributesconfiguration.

View user lineTermination ID.

get-ipstermid Check user lineTermination ID.


� Card reset


Fault LocationTable 18 describes VoIP service faults and causes. The mainte-nance engineer can locate the fault according to descriptions inthis table.


Chapter 5 VoIP Service Faults

TABLE 18 VOIP SERVICE FAULT LOCATION


Some user cannot make a call. � The external line is faulty.� ZXDSL 9806H user port is

faulty.� Port TID is not added at

ZXDSL 9806H side or the portTID is not consistent with thaton SS.

� Port TID is not added at MGCside.

� The user's right is restrictedat SS.

All users of one card cannot makecalls.

� The user card cable isconnected improperly.


� Port TID is not added atZXDSL 9806H side or the portTID is not consistent with thaton SS.

� The users of the card are notadded at MGC side.

All users of a whole shelf cannotmake calls.

� ZXDSL 9806H cannotcommunicate with MGC.

� VoIP sub-card is faulty.� User TID and RTP TID at

ZXDSL 9806H side areconfigured improperly.

� User TID and RTP TID atMGC side are configuredimproperly.

Fault Troubleshooting FlowFigure 4 shows VoIP service fault troubleshooting flow.



FIGURE 4 VOIP SERVICE FAULT TROUBLESHOOTING FLOW

User Phone Check

Check the user phone, including:

� Junction box of the user phone

� Phone wire

� Battery

� Phone key



� Pulse/audio frequency dialing mode

Lines Check

Check the internal lines and external lines.

� Internal lines

� Feeding voltage

� Ringing voltage

� Circuit current

� External lines

� DC voltage

� AC voltage

� Insulation resistance

� Capacitance

Table 19 lists the line test specifications.

TABLE 19 LINE TEST SPECIFICATIONS

Item Result Specification

Normal 34 V ≤ Measuredvalue ≤ 90 V

Feeding voltage

Abnormal Measured value < 34V

Measured value > 90V

Normal 18 mA ≤ Measuredvalue ≤ 35 mA

Circuit current

Abnormal Measured value < 18mA

Measured value > 35mA

Abnormal AC voltage VACag ≥ 8 V

VACbg ≥ 8 V

VACab ≥ 8 V

Swinging cross withother lines

VDCag ≤ –30 V

VDCbg ≤ –30 V

Abnormal DC voltage VDCag ≥ 8 V

VDCbg ≥ 8 V

VDCab ≥ 8 V

External lines



Item Result Specification

Abnormal insulationresistance

100 Kohm < Rag ≤500 Kohm

100 Kohm < Rbg ≤100 Kohm

Abnormal capacitance 0.3 uF ≤ Cag < 0.7 uF

0.3 uF ≤ Cbg < 0.7 uF

Cab ≥ 3.0 uF

Poor insulation 10 Kohm < Rab ≤ 60Kohm

10 Kohm < Rag ≤ 100Kohm

10 Kohm < Rbg ≤ 100Kohm

Line disconnected Cab < 0.2 uF

Swinging cross(self-cross)

Rab ≤ 10 K

Lines grounded Rag ≤ 10 Kohm

Rbg ≤ 10 Kohm

Leakage current VACag > 100 V

VACbg > 100 V

Abnormal circuitcurrent

Measured value < 22mA

Measured value > 60mA

Circuit currentresistance

Abnormal circuitresistance

Measured value >1000 ohm

Measured value < 0ohm

– VACag: AC Voltage between Line A and ground– VACbg: AC Voltage between Line B and ground– VACab: AC Voltage between Line A and Line B– VDCag: DC Voltage between Line A and ground– VDCbg: DC Voltage between Line B and ground– VDCab: DC Voltage between Line A and Line B– Rag: Insulation resistance between Line A and ground– Rbg: Insulation resistance between Line B and ground– Rab: Insulation resistance between Line A and Line B– Cag: Capacitance between Line A and ground– Cbg: Capacitance between Line B and ground– Cab: Capacitance between Line A and Line B

User Port Running Status Check

Check the user port running status using the following commands:

� Execute the get-slcphonenum slot slotnumber command tocheck the phone number corresponding to the user port.



� Execute the get-slcstatus command to check user circuit sta-tus.

� Execute the get-ipsstatus command to check ISP circuit sta-tus.

� Execute the get-slcstatistic command to check subscriberline status such as idle, occupied and blocked.

Equipment Running Status Check






PWR










Table 21 describes LED indicators on ATLA/ATLC card.



TABLE 21 LED INDICATORS ON ATLA/ATLC


RUN Green ON Card is workingnormally.

ALM Red ON Card is faultyor software isfaulty.

HOOK - ON When a userhooks off, theHOOK indicatoris ON.

Man-machineCommands

Execute the show card command to show card status.

Execute the show temperature-check command to check tem-perature and fan running status.

Execute the show interface slot/port command to check port sta-tus. In normal status, the LinkStatus is Up.

Execute the get-bdstat-s command to check the card status indetail.

RTP Resource Data ConfigurationCheck

Check the RTP resource data configuration using the followingcommands:

� Execute the get-ipstermid command to view TID format andseries number, which must be consistent with those on SS side.

� Execute the get-ipsstatistic command to view user circuitsnumber and circuit status such as idle, occupied and blocked.

� Execute the get-ipsstatus command to view user circuit sta-tus such as idle, occupied and blocked.

User Service Data ConfigurationCheck

Check the user service data configuration using the following com-mands:

� Execute the get-mgc mgcid mgcid command to view SS pa-rameters.

� Execute the get-mgbaseattr, get-mgcapabili and get-voip-config commands to view AG parameters.

� Execute the show ip subnet command to view VoIP VLANinformation.



� Execute the get-slctermid slot slotnumber command to viewTID format and serial number, which must be consistent withthose at SS side.

� Execute the get-slcstatus command to view user status.

� Execute the get-slcstatistic command to check subscriberline status such as idle, occupied and blocked.

� Execute the get-slcattrib slot slotnumber command to viewcircuit fax mode, which must be consistent with those at SSside.

H.248 Link Status Check

If the link between ZXDSL 9806H and SS is connected, executethe h248state command to check the H.248 link status.

In normal status, H.248 link is H248-SS link status(H248Trkplink) :OK MGCid is x


If there is no problem with the equipment hardware and data con-figuration, check the data configurations of the upper-layer equip-ment, including:





� Traffic limit

SS Data Configuration Check

SS is the calling and control core of NGN. Check the data configu-ration at SS side, including:

� Phone number configuration

� H.248/MGCP configuration

� TID configuration

� Digitmap configuration



Fault HandlingThis section introduces VoIP service fault handling.

No Dialing Tone After Hook-Off

Symptom When a user hooks off, there is no dial tone.

Troubleshooting 1. Make sure it is a problem of a single user or all users.

2. Check whether hook-off status is normal.

� Check the HOOK indicator after picking up the phone. Innormal status, the HOOK indicator is ON.

� Execute the get-slcstatus command to view subscriberline status. Check whether the user line is occupied.

3. If only a single user has the problem, check whether its corre-sponding card is configured and whether the card is online.

4. If all users have the problem, check the backplane. If it isnecessary, replace the backplane.

Busy Tone When Hook-Off

Symptom The user hooks off and only hears busy tone.

Troubleshooting 1. Check H.248 link.

� Execute the get-mgc command to check MGC configura-tion. If MGC is not configured, use the add-mgc commandto create it. If MGC is not configured properly, use themod-mgc command to modify it.

� Check whether ZXDSL 9806H data is configured at SS side,including IP address, protocol port and gateway.

� Execute the show ip subnet command to check VoIP VLANconfiguration. If VoIP VLAN is not configured, use the ipsubnet command to configure it.

2. Execute the get-slctermid command to check the user's TID.

3. Check SS data configurations, especially on packet type con-figuration, number assignment and protocol type.

Busy Tone When Dialing

Symptom The user hooks off and hears the busy tone when dialling a number.

Troubleshooting 1. On SS, check the user's calling right. If the user has not acalling right, add it on SS.



2. Check the number table configured on SS. If the number tabledoes not contain the number set with the number initial, addthe number set.

Unreliable Calling Connection

Symptom Sometimes users can make a call. Sometimes, users cannot makea call. The connection is unreliable.

Troubleshooting 1. Check IPS module.

i. Execute the get-ipsstatu command to view IPS circuit sta-tus. In normal status, IPS circuit is IDLE.

ii. Execute the get-ipstermid command to view configura-tions of the terminal corresponding to the IPS circuit.

iii. Execute the get-allnat command to view NAT configura-tions of the IPS circuit.

2. Check IPS status at SS side and at ZXDSL 9806H side. IPSstatus at both sides needs to be consistent with each other.

Call Drop

Symptom Call drop occurs when a user is making a call.

Troubleshooting 1. If call drop occurs after long conversation, check whether LongConversation Restriction is set on SS. If Long Conversation Re-striction is set, it is normal.

2. If call drop occurs frequently, check whether there are frequenthook-on messages or hook-switch messages on ZXDSL 9806H.

3. Check user port signals at ZXDSL 9806H. Check whether theuser has severe interference from outside.

Noise in Call

Symptom When a user is calling, there is noise during the call.

Troubleshooting 1. Check the phone, line, signal of the opposite side.

2. Check the phone of the local side.

3. Check the phone line of the local side.

4. If a splitter is used, check the splitter and the DSL line card atthe opposite side.

5. If it is a toll call, check the network status.

6. Check the media gain of ZXDSL 9806H. If it is too large, reduceit.



7. Check the working ground and protection ground. The voltagedifference between the working ground and protection groundshould be less than 0.1 V.

Unable to Hear Calling Party

Symptom The user makes a call. The called party cannot hear the callingparty.

Troubleshooting 1. Catch packets at the uplink interface of ZXDSL 9806H aftermaking a call. Check whether there are bidirectional mediapackets.

2. Check route configuration on ZXDSL 9806H. Execute the get-voip-ipaddr command and show ip route command to checkwhether the next-hop IP address is configured.

Troubleshooting CasesThis section introduces VoIP service troubleshooting cases.

Abnormal H.248 Link

Symptom H.248 link between ZXDSL 9806H and SS is disconnected.

Troubleshooting 1. Ping the uplink interface of ZXDSL 9806H from a computer,which is in the same network segment with ZXDSL 9806H. Ifit fails, check the system data configuration, SCCB card statusand uplink subcard.

2. Execute the get-voip-ipaddr command or show ip routecommand to check whether ZXDSL 9806H is configured withthe next-hop route. If the next-hop route is not configured,create one. If the next-hop route is not configured properly,modify it.

3. Execute the get-mgc command to check MGC configuration. IfMGC is not configured, use the add-mgc command to create it.If MGC is not configured properly, use themod-mgc commandto modify it.

4. Check whether ZXDSL 9806H data is configured at SS side,including IP address, protocol port and gateway.

5. Execute the show ip subnet command to check VoIP VLANconfiguration. If VoIP VLAN is not configured, use the ipsubnet command to configure it.



No Number Display Because ofSplitter

Symptom ADSL service and VoIP service are configured. Both of them arenormal. The incoming call number display function is enabled. Butno number is displayed when a call comes in.

Troubleshooting 1. Check the user phone.

2. Check line connection.

3. Check whether a voice splitter is connected.

4. Test the distribution frame. Number is not displayed if a splitteris connected. If there is no splitter, the number is displayed.

5. Replace the splitter. The fault is removed.

Unsuccessful Fax Service

Symptom Calling between fax machines is successful but fax service is notsuccessful.

Troubleshooting 1. Check the fax machine. Make sure fax machine works properly.

2. Execute the get-rtppar command to check fax mode of userports which are used for fax service. Fax mode of both userports needs to be the same.

3. If the fax service is implemented between ZXDSL 9806H sys-tems, check the fax mode of both ZXDSL 9806H systems. Faxmodes of both ZXDSL 9806H systems need to be the same.

4. If the fax service is implemented between ZXDSL 9806H andPSTN via TG, check the fax mode of TG. Fax modes of TG andZXDSL 9806H need to be the same.

5. If T.38 mode is used, check whether SDP field is set in SS.

6. Check line quality. PSTN line quality and bearer network qual-ity.

7. Check uplink port mode. It is recommended to use 100 Mbpsfull duplex mode.

Hearing SIT Tone After Dialup

Symptom The user hears SIT after dialing.

Troubleshooting 1. Check number table and number analysis configuration of SS.If the number table contains the number cluster and the rele-vant number analysis is not configured, SIT is generated.

2. Check whether the user number in SS is consistent with thenumber cluster in ZXDSL 9806H


C h a p t e r 6

Multicast Service Faults

Table of ContentsMulticast Basic Information .................................................49Potential Result .................................................................50Fault Location ...................................................................51Fault Troubleshooting Flow..................................................51Troubleshooting Cases........................................................53

Multicast Basic InformationThis topic introduces multicast technology and its implementationin ZXDSL 9806H.

Introduction

Multicast is a network addressing method for the delivery of infor-mation to a group of destinations simultaneously using the mostefficient strategy. In this method messages are delivered overeach link of the network only once, creating copies only when thelinks to the multiple destinations split (typically network switchesand routers). Multicast is often used for streaming media and In-ternet television applications.

Multicast has the following advantages:

� Save network bandwidth

� Less load on network devices

� Server does not need to process quests for each user.

The core of multicast technology is to copy the packet at the placenear to the receiver as close as possible.

The source host just sends data packet to a specific multicastgroup. All receivers in the multicast group can receive the samedata copy. Other hosts in the network cannot receive the data ex-cept the host (destination host) in the multicast group. Hosts in amulticast group can be in the same physical network or in differentphysical networks.

The multicast group is identified with Type D IP address (224.0.0.0~ 239.255.255.255).




ZXDSL 9806H supports IGMP Snooping, IGMP Proxy and IGMPRouter

� In IGMP Snooping mode, the system does not manage statusof multicast members. It just listens to IGMP traffic and for-wards IGMP packets passively. It has a little influence on thesystem load. However, it greatly increases the load of process-ing protocols.

� In IGMP Proxy mode, the system manages status of multicastmembers actively, efficiently reducing the load of processingprotocols.

� IGMP Router mode is a simplified proxy mode. In case thatmulticast service is sent to the uplink port, the system doesnot require uplink port for multicast service dynamically.



View IGMPinformation.

show igmp Check IGMP modeand IGMP status.

View CAC information. show igmp cac Check CAC statusand CAC multicastaddress.

View channel packageinformation.

show igmpchannel-package

Check multicastchannel packagelist.

View MVLANinformation.

show igmp mvlan Check source port,destination port andmulticast groups inMVLAN.

View interface IGMPinformation.

show igmpinterface

Check multicastgroup memberconfiguration.


� Card reset



Chapter 6 Multicast Service Faults

Fault LocationTable 22 describes multicast service faults and causes. The main-tenance engineer can locate the fault according to descriptions inthis table.

TABLE 22 MULTICAST SERVICE FAULT LOCATION


Multicast service for some user isdisconnected.

� The STB is faulty.� The user port service data is

not configured properly.� Multicast program is not


Multicast service for all users of awhole shelf is disconnected.

� The user port service data isnot configured properly.

� Multicast program is notconfigured properly.

� The multicast data ofupper-layer equipment isnot configured properly.

Fault Troubleshooting FlowFigure 5 shows multicast service fault troubleshooting flow.

FIGURE 5 MULTICAST SERVICE FAULT TROUBLESHOOTING FLOW



STB Check

Check the STB, including:

� TV and STB power indicators

� CATV cable

� Connection between CATV and STB

� Video channel

� Intelligent card

� Remote controller

User Port Service Data ConfigurationCheck

Check the user port service data configuration using the followingcommands:

� Execute the show igmp interface slot/port command to viewIGMP enabled/disabled status, fast-leave status and bandwidthlimit.

� Execute the show igmp interface slot/port group commandto view multicast group registered on the port.

� Execute the show igmp mvlan mvlanid command to checkthe receive port and multicast group.

Multicast Data Configurations Check

Check the multicast data configurations, including:

� ICMP mode

Execute the show igmp command to view IGMP mode, CACand CDR status.

� Multicast programme configuration

Execute the show igmp mvlan mvlanid command to viewMVLAN configuration, source port and destination port.

� Programme preview configuration

Execute the show igmp view-profile profilename commandto view preview configurations such as preview count and pre-view interval.

� Multicast bandwidth configuration

Execute the show igmp mvlan mvlanid group groupaddresscommand to view the bandwidth of a multicast group.

� CAC configuration


Chapter 6 Multicast Service Faults

Execute the show igmp cac command to view CAC configu-ration.

Multicast Programme ConfigurationCheck

Execute the show igmp mvlan mvlanid command to view theprogrammes in multicast VLAN.

Troubleshooting CasesThis section introduces multicast service troubleshooting cases.

User Cannot Watch Video

Symptom The user is successful to establish multicast forwarding table onBRAS and ZXDSL 9806H and is able to view data traffic, but failsto view video at the client side.

Troubleshooting 1. Ping the multicast server from the client. It is successful. Thereis no problem with unicast.

2. Multicast table can be established. There is no problem withroute.

3. Use the multicast software Wlisten and Wsend to have a test.The client can receive multicast data. There is no problem withmulticast configuration and multicast forwarding.

4. Play the VLC media player. The client can watch video. Catchpackets at the client. The received multicast packets are notassembled successfully.

5. Catch packets at the multicast server. If the packets are thesame as those caught at the client, the packets sent from mul-ticast server are faulty. Replace a computer. The fault is re-moved.

Static User and DHCP User CannotReceive IPTV Service

Symptom Static users and DHCP users cannot use IPTV service.

Troubleshooting 1. If the client wants to receive multicast data from the server,unicast route must be properly established. Ping the serverfrom the client. It is successful. There is no problem withunicast route.



2. Check RP registration. If the server is registered on RP, thereis no problem with the multicast server.

3. Connect the computer to the switch. Configure relevant data.If IPTV service is normal, there may be problem with ZXDSL9806H.

4. ZXDSL 9806H is only for data transparent transmission. CheckVLAN configurations on ZXDSL 9806H. VLAN is configuredproperly.

5. Catch packets at the switch to view data sent from ZXDSL9806H. Catch packets at the computer to view IGMP packetversion. The version of IGMP packet from the multicast clientis correct. The packet caught on the switch does not containIGMP packet. It means ZXDSL 9806H has discarded IGMPpacket. The multicast forwarding table cannot be created atthe switch and BRAS. IPTV cannot be received.

6. Configure IGMP Snooping on ZXDSL 9806H. Configure trans-parent transmission on the switch. IPTV service is normal.


C h a p t e r 7

System Faults

Table of ContentsInformation Collection........................................................55Potential Result .................................................................56Fault Troubleshooting Flow..................................................56Fault Handling...................................................................59Troubleshooting Cases........................................................59

Information CollectionCard Indicators Table 23 describes LED indicators on SCCB card.





PWR


















Man-machineCommands

Execute the show card command to show card status.




� Card reset


� System reboot

Fault Troubleshooting FlowFigure 6 shows system fault troubleshooting flow.


Chapter 7 System Faults

FIGURE 6 SYSTEM FAULT TROUBLESHOOTING FLOW

Equipment Working EnvironmentCheck

Check the equipment working environment, including the followingitems:

� Power voltage

� DC voltage range: -56 V ~ -40 V

� AC voltage range: 85 V ~ 264 V

� Working temperature: -30 ℃ ~ 55 ℃� Working humidity: 5% ~ 95%

� Cleanness: Dust concentration with a diameter greater than5µm is equal to or less than 3 × 104 grains/m3, and the dustis not be electrically conductive, magnetically conductive anderosive.

� Grounding resistance: < 1 ohm

� Air pollution: Do not expose the equipment to corrosive gases(e.g., SO2, oxides of SO2 and ammonia), smog or oil solvents.No smoking in the equipment room.

Hardware Running Status Check








PWR
















Man-machineCommands

Execute the show card command to check card status.




Chapter 7 System Faults

Fault HandlingThis section introduces system fault handling.

Fails to View Message ThroughHyperTerminal

Symptom During the process of starting the main control card, the user failsto view any message through HyperTerminal interface.

Troubleshooting 1. Check the serial port cable connection.

2. Check baud rate setting on HyperTerminal. It must be '9600 –n – 8 – 1'. Serial port connection is broken if baud rate is notcorrectly configured.

Startup Failure after Version Update

Symptom Main control card fails to start after the version update.

Troubleshooting 1. Check the version. Make sure the version is correct or versionfile is not damaged.

2. If the BOOT version does not match with update version, burnBOOT version again.

Troubleshooting CasesThis section introduces system troubleshooting cases.

ISP Chip Works Abnormally

Symptom The user hooks off and hears busy tone. The NMS displays ISPrelevant unit running alarm.

Troubleshooting 1. Execute the get-ipsstatus command to view ISP circuit sta-tus. In normal status, it is IDLE. If it is FAULT, check the maincontrol card or restart the main control card.

2. Execute the get-ipstermid command to view the relevant ter-minal configuration. Check whether ISP subcard is inserted.

3. Execute the get-allnat command to view NAT configuration.



Narrowband Card Offline

Symptom The ALM indicator on the narrowband user card is always ON. Or,the HOOK indicator is always ON. The user hooks off and hearsnothing. The NMS displays that the user is offline.

Troubleshooting 1. Execute the show card slot command to check whether theoffline slot is configured with a narrowband card. The config-ured card type needs to be consistent with the real card type.

2. Perform signaling trace. Check whether ZXDSL 9806H reportsthe off-hook message after the user hooks off. If there is noreport message, the main control card does not work normally.

3. Replace the narrowband user card with a new one. Checkwhether the fault is removed.

Broadband Card Offline

Symptom Link between ZXDSL 9806H and modem is not established. TheNMS shows that the user is offline.

Troubleshooting 1. Execute the show card slot command to check the card con-figuration. The card configured on the NMS must be consistentwith the card inserted on the slot.

2. Replace the card's boot chip.

3. Download the card version.

4. Check the main control card.

5. Replace the user card.


C h a p t e r 8

NM Faults

Table of ContentsNM Basic Information.........................................................61Potential Result .................................................................70Fault Location ...................................................................70NMS Fault Troubleshooting Flow...........................................71NM Fault Handling .............................................................75

NM Basic InformationThis topic introduces the installation and configuration of networkmanagement software.

NM Installation and ConfigurationRequirements

Requirements for NM installation and configuration are as follows:

� Do not save the installation source file and destination directoryon Windows desktop.

� Installation directory name cannot be too long. The directorysuch as 'D:\9806H\netnumen' is recommended.

� For NetNumen (Version 2), it is required to create a webn-msdb database (Do not modify the name) in SQL Server en-terprise manger. Initialize the database.

� NetNumen (Version 4) has a built-in FTP server. Do not enablethe built-in FTP server. Select Use Outside FTP Server.

� After installing NetNumen, configure parameters such as data-base, NE configuration, FTP parameters, database backup andlog management.

� If the system gives a promptNetNumen (Version 4) startup error

, capture the error message.



Operating System and Database

Requirements for the operating system and database are as fol-lows:

� Use only one network card and one IP address at the server.If multiple IP addresses are required, make sure that NMS canstart when one IP is used. Then, set multiple IP addresses.

� In Windows XP/2003 operating system, open Control Panel> System Options. Close DEP. Right-click the installation fileand select Compatible with win2000

� Windows operating system must be Windows 2000Server/Windows XP Professional/Windows 2003 Server.Install SQL Server 2000 database (Standard, Enterprise orDevelopment). For Windows XP/2003 operating system, onlySQL Server 2000 Enterprise/Development is installed. SQLServer 2000 SP3 patch must be installed.

� Select local system account instead of domain account whileinstalling SQL server 2000. Select SQL Server and Windowsfor identification authentication.

� For Solaris operating system, use Solaris9. Install Oracle 9database. Install patch 9.2.0.7 or 9.2.0.8. Database SID isuep.

� Copy the installation program to the FTP directory.

NM Server and Client Configurationin case of Multiple IPs

By default, both NetNumen server and client use only one IP ad-dress. When the computer configured with NetNumen have mul-tiple IP addresses, it is necessary to configure NetNumen.

� NetNumen (Version 2)

� Set RMI server IP.

Edit the 'WebNMS\setRmiServer.bat' file. Modify the fol-lowing line:set RMI_IP=localhost

Change 'localhost' to be the communication IP for NetNu-men server/client. If the NetNumen client/server has mul-tiple IP addresses, make sure which IP is for communica-tion.

� Set the IP of FTP server.

Edit the 'WebNMS\ipms\conf\IPMS_param.conf' file. Mod-ify the following line:FTP_PARAMETERSFTPIPAddress="localhost" /

Change 'localhost' to be the IP address of FTP server.


Chapter 8 NM Faults

� NetNumen (Version 4)

Set the IP of FTP server.

Open the FTP configurations in NetNumen Config Center.Change 'localhost' to be the IP address of FTP server.

Edit the 'ums-svr\zxnm01\dsl\dsl-base.par\con\IPMS_param.xml' file. Modify the following line:FTP_PARAMETERSFTPIPAddress="localhost"

System should be able to ping the FTP server..

Note:

Restart the NetNumen server to save changes.

NMS and SQL Server 2005Installation in Window 2003

NetNumen N31 supports SQL Server 2005. This topic describesSQL Server 2005 and NetNumen N31 installation in Windows 2003.

1. Install Windows installer 3.1 before installing SQL Server 2005.

2. Perform the following steps to install SQL Server 2005. Usedefault values for the unmentioned options.

i. Run the installation program. Input the license key. TheSQL server Database Services option is mandatory. Theothers are optional.

ii. Select installation directory. It is not recommended to savethe data files on the default disk (Disk C). Select other diskswith large space.

iii. Select installation instance. Generally, use the defaultvalue.

iv. Select account. For a single system, select Use Built-inSystem Account.

v. Select ID mode. Generally, select hybrid mode. Input thepassword of the 'sa' user. The password netnumen is rec-ommended.

vi. Set the order rule. Generally, the default value is used.

3. Set communication protocol.

i. Run Programs > Microsoft SQL Server > SQL serverConfiguration Manager. Select SQL Network Config-uration > MSSQLSERVER Protocol. Enable NamedPipes and TCP/IP.

ii. Double-click TCP/IP. Select the IP address correspondingto the network card. Select Yes for the Enabled option.Make sure the port number is 1433.



4. Re-start SQL Server 2005 database.

5. Configure NetNumen N31 configuration center.

i. Run Start > Programs > NetNumen N31 > Tools >NetNumen N31 Config Center.

ii. Select Common Configuration > Database Configura-tion. Select MS SQL2005 in the Database Tpye drop-down menu. Modify database parameters such as pass-word and port number.

iii. Click Save.

Mysql Installation

It is recommended to install Oracle database in Unix system. Inspecial cases, Mysql database can be used. Perform the followingsteps to install Mysql:

1. Install different MySQL5.0 installation kit for different Solarisversions.

� Solaris 8: Use 'mysql-standard-5.0.9-beta-solaris8-sparc-64bit.tar.gz'.

� Solaris 9: Use 'mysql-standard-5.0.9-beta-solaris9-sparc-64bit.tar.gz'.

2. Execute the following commands to add MySQL user andgroup:shell> groupadd mysqlshell> useradd -g mysql mysql

3. Copy the 'mysql-standard-5.0.9-beta-solaris*-sparc-64bit.tar.gz' in the '/export/home/ myspace/ mysql'directory. Decompress the installation file.

Execute the following commands to decompress the file:shell>cd /usr/localshell>rm mysqlshell>cd /export/home/myspace/mysqlshell>gunzip mysql-standard-5.0.9-beta-solaris*-sparc-64bit.tar.gzshell>tar xvf mysql-standard-5.0.9-beta-solaris*-sparc-64bit.tarshell>cd /usr/localshell>ln -s /export/home/myspace/mysql/mysql-standard-5.0.9-beta-solaris*- sparc-64bit mysql

4. Modify file or directory right.

Execute the following commands to modify file or directoryright:shell>cd /usr/local/mysqlshell>scripts/mysql_install_db --user=mysqlshell>chown -R root .shell>chown -R mysql datashell>chgrp -R mysql .

5. Modify root user password.

Execute the following commands to modify root user password:shell>cd /usr/local/mysql/bin


Chapter 8 NM Faults

shell>./mysqld_safe --default-character-set=gb2312 --user=mysql &shell>./mysql -urootmysql>use mysql;mysql>update user set password=password(’public’) whereuser=’root’;// mysql>select user, host from user;mysql> update user set user=’%’ where host=’localhost’and user=’’;mysql>update user set host=’%’ where host=’localhost’and user=’root’;mysql>update user set user=’%’ where host=’nm9000’ anduser=’’;//mysql>update user set host=’%’ where host=’nm9000’and user=’root’;mysql>flush privileges;mysql>exit;shell>./mysqladmin -uroot -ppublic shutdown

6. Start MySql database.

Execute the following commands to start MySql server:shell>cd /usr/local/mysql/binshell>./mysqld_safe --default-character-set=gb2312--lower_case_table_ names=1 –user=mysql &

� Start NM server.

Run the 'zxnm01v4\tools\configcenter\bin\run.bat' file.Set database IP address, user name and password. Click OK.

SUN + ORACLE Environment

This section introduces NM operation and configuration in SUN +Oracle environment.

Basic NMS Installation and Configuration

It is required to use the 'oracle' user to install the NMS in Oracleenvironment. Execute the env command to check the parameters.

1. NMS installation

Open the directory where the NMS installation file resides. In-put ./install.sh or, right-click the file and change the prop-erty to be 'executable. Double-click Run.

Check the parameters in NetNumen N31 Config Center. Thedatabase IP address must be the real IP address of the networkcard. Do not use 127.0.0.1.

If FTP function is used in UNIX, the root path for the 'zte' and'webnms' users must be the same. Create these two users inUNIX manually.

2. Database initialization

Login to the database as the 'root' user. Enter the Solaris win-dow.#cd /export/home/netnumen#pwd/export/home/netnumen



#chmod -R 777 .#su – oracleSun Microsystems Inc. SunOS 5.9 Generic May 2002$cd /export/home/netnumen/ums-svr/docs/dbscript/install-db$./install-db.shObserve the initialization. The following prompts are normal.Record other prompts.chmod: WARNING: can’t change convert.batchmod: WARNING: can’t change db-installer-jdbc.sh

Or,[exec] SP2-0332: Cannot create spool file.[exec] SP2-0332: Cannot create spool file.

NMS Start-up in UNIX

� Run '/netnumen/bin/startNmsServer.sh' or '/netnu-men/ums-svr/bin/console.sh' to start up the NMS on Unixserver locally.

� For dual systems, use 'console.sh' to be start-up script.Modify the '/netnumen/umssvr/ platform/psl/ext-ser-vice/console/conf/maincontroller.xml' file. Select '0' forclient-type. In this way, when the NetNumen is started, theconsole interface is not displayed.

� Run '/netnumen/bin/remoteStartServer.sh' to start up theNMS if logon to the Unix server is through Telnet or X-managerremotely.

Problems Related to Oracle Installation

During the Oracle database installation process, following prob-lems may occur:

� The login user is not Oracle user.

The './install.sh: sqlplus: not found' message appears whenthe 'install.sh' file is run.

Perform the following steps:

i. Run sqlplus. If the '# sqlplus sqlplus: not found' messageappears, the login user is wrong. If it is successful to runsqlplus, the user name prompt appears, it means the useris right.

ii. Exit sqlplus.

iii. Run the 'install.sh' file again.

� NMS server cannot connect to the database.

When NMS client is started, many 'SQLException' messages ap-pear. It fails to start NMS client.

Perform the following steps:

i. Ping the database server. If it fails, modify network set-tings.

ii. Check IP and database name parameters.


Chapter 8 NM Faults

iii. Check Oracle database running status.

a) Log on to the database as 'oracle' user.

b) Start SQL*PLUS: $sqlplus /nolog.

c) Log on to the database as 'sysdba' user: SQL>connectsystem/manager as sysdba.

d) Start the database: SQL>startup.

If the database is already running, the 'ORA-01081:cannot start alreadyrunning ORACLE - shut it down first'message appears. If not, continue the start process.

e) Exit SQL*PLUS: SQL>exit.

iv. Check whether database monitor is started.

a) Log on to the database as 'oracle' user.

b) Run the monitoring program: $ lsnrctl.

c) Start the monitor: LSNRCTL> start.

If the monitor is already started, the 'TNS-01106:Listener using listener name LISTENER has already beenstarted' message appears. If not, continue the startprocess.

d) Exit the monitoring program: LSNRCTL> exit.

SID Configured in Oracle Inconsistent with NMS

Generally, it is recommended to configure SID in Oracle databaseto be 'uep'. If it is not, it is necessary to modify relevant NMSconfiguration files.

Perform the following steps to modify SID on NMS configurationfiles.

1. Modify NMS server start-up file: ums-svr/deploy/deploy-de-fault.properties.

Set all 'databasename' in this file to be the SID of Oracle data-base. In this instance, it is 'ipms'. The descriptions are asfollows:default.uep.ds.databasename=ipmsuep-mif-mifcore.MIBDS.ds.databasename=ipmsuep-pal-fm.fm.ds.databasename=ipmsuep-pal-pm.ueppmds.ds.databasename=ipmsjms.jms.ds.databasename=ipms

2. Modify NMS database initialization script configurationfile: ums-svr/docs/dbscript/install-db/uep/conf/in-stall-uep-conf.properties.

Set DBSID to be the SID of Oracle database. In this instance,it is 'ipms'.

Perform the modification before creating NMS database. Then,initialize database.



Solaris Commands

Table 27 lists Solaris commands.

TABLE 27 SOLARIS COMMANDS

Command Meaning Example

Cd Change directory. -

Ls Display thedirectory/fileinformation. It equalsto the dir command.

The ls-l commanddisplays the detailedinformation.

Rmdir Delete an emptydirectory.

-

mkdir Create a directory. -

pwd Display the currentdirectory.

-

rm Delete a file. Use the rm –R *command to delete allfiles in the directory.Carefully use it.

Copy a file: cpNM01.zip /netnumen

Copy a directory: cp-r /netnumen/ums-svr/tools/export/home

cp Copy a file.

Copy a directory/fileon the remoteserver: rcp –p/-rpnetnu men1:/ex-port/home/oracle.tar/export/home

mv Change a file name.Move a file ordirectory.

-

chmod 755 file

chmod u+w file

chmod g+w file

chmod o+w

chmode Change file right.

The -R parameterrecursion


Chapter 8 NM Faults


find Find the designatedfile.

Find the file in theroot directory anddisplay the result onthe terminal: find /-name filename -print

df Display disk usage. df –kh

uname Display systeminformation.

uname -a

netstat Display networkstatus.

netstat –r: Checkthe route status.

View network status:ifconfig -a

Configure interfaceaddress (formm7000): ifconfigeri0 136.1.56.170

ifconfig eri0up(down)

ifconfig eri0 add

ifconfig Configure or viewnetwork interfaceparameters.

Add a logic address:if ipaddress

admintool Create auser/directory.

-

date View or set systemtime.

-

env View systemenvironmentparameters.

-

Add the defaultgateway: route adddefault 136.1.0.1 1

route add Add a route.

If the '/etc/defaul-trouter' file exists, thesystem will set the IPaddress in this file tobe its gateway whenthe system starts up.

De-encapsulate: tar-xvf oracle.tar

tar Encapsulate/De-encapsulate.

Encapsulate: tar -cfa.tar a

Zip Compress files. -

Unzip Uncompress files. unzip a.zip




ps View the process. View all java process:ps -ef | grep java

kill -9 120kill Kill a process.

Kill a process, then,restart the process:kill -HUP 120

Pkill Kill a processaccording to theprocess name.

pkill httpd

Potential ResultDuring the process of removing a fault, restarting the NM serveror database terminates the network management at the client.

Fault LocationTable 28 describes NM faults and causes. The maintenance engi-neer can locate the fault according to descriptions in this table.

TABLE 28 NM FAULT LOCATION


The server cannot be started. � The database does not worknormally.

� The NMS installation directoryname is too long.

� The port is occupied by otherprogrammes.

� The operating system is notcompatible with the NMS.

The client cannot be started. � The firewall is installed.� The bandwidth is not enough.� The port is occupied by other

programmes.� The NMS version at the client

is not consistent with that atthe server.

Other faults Refer to NM Faults Handling.


Chapter 8 NM Faults

NMS Fault TroubleshootingFlowFigure 7 shows NMS fault troubleshooting flow.

FIGURE 7 NMS FAULT TROUBLESHOOTING FLOW

NM Environment Check

SoftwareRequirements

� Windows operating system

� Windows XP, Windows 2000, Windows 2003 with the latestpatches

� SQL Server 2000/SQL Server 2005

� Sun Solaris operating system

� Sun Solaris (above 6.5)

� Oracle 9i database



HardwareRequirements

� Hardware requirements for Windows platform

Table 29 lists hardware requirements for Windows server.

TABLE 29 HARDWARE REQUIREMENTS FOR WINDOWS SERVER

NetNumen N31 Type Hardware Platform

NETNumen N31-EXX-S-1.0 Intel XEON or Pentium IV 2.0GHz, 1 GB RAM, Two 36 GBHDDs, DVD drive, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-M-1.0 Intel XEON or Pentium IV 1.8GHz (Two on-board Processors),2 GB RAM, Two 36 GB HDDs,DVD drive, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-L-1.0 Intel XEON or Pentium IV 2.0GHz (Two on-board Processors),2 GB RAM, Two 36 GB HDDs,DVD drive, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-U-1.0 Intel XEON or Pentium IV 2.0GHz (Four on-board Processors),4 GB RAM, Two 36 GB HDDs,DVD Combo drive, 10/100 MbpsEthernet Network Adapter

Table 30 lists hardware requirements for Windows client.

TABLE 30 HARDWARE REQUIREMENTS FOR WINDOWS CLIENT


NETNumen N31-EXX-S-1.0 Pentium IV 2.0 GHz, 512 MBRAM ,20 GB HDD, CDROM,Sound Card, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-M-1.0 Pentium IV 2.0 GHz, 512 MBRAM, 20 GB HDD, CDROM,Sound Card, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-L-1.0 Pentium IV 2.0 GHz, 512 MBRAM ,20 GB HDD, CDROM,Sound Card, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-U-1.0 Pentium IV 2.0 GHz, 512 MBRAM ,20 GB HDD, CDROM,Sound Card, 10/100 MbpsEthernet Network Adapter

� Hardware requirements for Solaris platform

Table 31 lists hardware requirements for Solaris server.


Chapter 8 NM Faults

TABLE 31 HARDWARE REQUIREMENTS FOR SOLARIS SERVER


NETNumen N31-EXX-S-1.0 SUN Blade 2000 UltraSPARC IIICu 1.2 GHz, 1 GB RAM, 73 GBHDD, DVD drive, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-M-1.0 SUN Blade 2000 UltraSPARCIII Cu 1.2 G (two on-boardprocessors), 2 GB RAM, 73 GBHDD, DVD drive, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-L-1.0 V880 UltraSPARC III Cu 1.2 GHz(Four on-board processors), 4GB RAM, Two Optical Interface36 GB HDD, DVD drive, 10/100Mbps Ethernet Network Adapter

NETNumen N31-EXX-U-1.0 V880 UltraSPARC III Cu 1.2 GHz(Eight on-board processors),4 GB RAM, Two 36 GB OpticalInterface HDD, DVD Drive,10/100 Mbps Ethernet NetworkAdapter

Table 32 lists hardware requirements for Solaris client.

TABLE 32 HARDWARE REQUIREMENTS FOR SOLARIS CLIENT


NETNumen N31-EXX-S-1.0 Intel Pentium IV 2.0 GHz G, 1GB RAM ,20 GB HDD, CDROMdrive, Sound Card, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-M-1.0 Intel Pentium IV 2.0 GHz G, 1GB RAM ,20 GB HDD, CDROMdrive, Sound Card, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-L-1.0 Intel Pentium IV 2.0 GHz G, 1GB RAM ,20 GB HDD, CDROMdrive, Sound Card, 10/100 MbpsEthernet Network Adapter

NETNumen N31-EXX-U-1.0 Intel Pentium IV 2.0 GHz G, 1GB RAM ,20 GB HDD, CDROMdrive, Sound Card, 10/100 MbpsEthernet Network Adapter

NM Server Operating SystemConfiguration Check

Check the operating system which is running NM server, including:



� Software and hardware configurations

� Firewall

� Disabled ports such as Port 1433, FTP port

� Computer name: The renamed computer may cause abnormalrunning.

Database System Running Check

Select Programs > Microsoft SQL Server > Enterprise Man-ager. Check the following items:

� In the Database folder, there must be UEP, UEP_CAF_FMand UEP_FM.

� Click Security > Login. Check the password of sa user. Itmust be consistent with the password set in NetNumen system(Default: netnumen).

Logic Connection between NM andDatabase

Check the logic connection between NM and database.

1. Run the database.

2. Run NetNumen N31 config center.

Select Start > Programs > NetNumen N31 > Tools > Net-Numen N31 Config Center.

3. Test connection.

Select Common Configuration > Database Configuration.Check SQL server configurations. Click Test Connection tocheck the connection.

4. If the connection is failed, select Start > Programs > Net-Numen N31 > Tools > NetNumen N31 Init Database. Ini-tialize the database.

NM Basic Information ConfigurationCheck

Make sure that the following operations are performed in the Net-Numen N31 config center before starting NetNumen N31.

1. Config center selection

Select Start > Programs > NetNumen N31 > Tools > Net-Numen N31 Config Center.

2. NE selection


Chapter 8 NM Faults

Select DSL Product > Access Layer > DSL Product.

3. Database configuration

Select Common Configuration > Database Configuration.Check SQL server configurations.

4. FTP server configuration

Select Common Configuration > FTP Service. Check FTPserver configurations. If the outside FTP server is used, selectUse Outside FTP Server.

NM System Right ConfigurationCheck

Login to NetNumen N31 Client. Select View > Security Manage-ment. On the Security Management interface, select SecurityManagement Tree > User Management. Check the user infor-mation.

NE SNMP Configuration Check

Execute the show snmp command to check SNMP server config-uration.

Execute the snmp-server community communityname ro | rwcommand to configure the attribute 'community'.

Execute the snmp-server host ipaddress command to configureSNMP server IP address.

NM Fault HandlingThis section introduces NM fault handling.

Unable to Ping In-band NM

Symptom NMS fails to get information after ZXDSL 9806H is started.

Troubleshooting 1. Check whether NetNumen N31 Server/Client is able to ping theuplink port of ZXDSL 9806H.

i. Check the cable connection among the computer, switchand uplink port ofZXDSL 9806H.

ii. Check indicators. In normal status, L1/L2 optical interfaceor Ethernet electrical interface indicator is green. Networkinterface indicator on the computer is flashing.



iii. Execute the show ip subnet command to view VoIP VLAN.Voice and management uplink ports need to be added tothis VLAN.

iv. If the computer and the uplink port of ZXDSL 9806H are notin the same network segment, check the gateway settingsof ZXDSL 9806H and the computer.

2. Execute the get-ctrlport command to view the relevant con-trol port. The control port needs to contain the equipment portnumber, which is 161. The transmission-layer protocol is UDP.

Data and Version Upload/DownloadUnsuccessful

Symptom Downloading/uploading fails even after the directory and file nameis configured in NetNumen N31 client.

Troubleshooting 1. Check parameters on the Version Upload/Download inter-face, including the file directory and file name.

2. Make sure that it is successful to ping ZXDSL 9806H from FTPserver.

3. Make sure that FTP server is started. FTP server uses Port 21.The version file directory is specified on FTP server.

4. To upload version, make sure that the FLASH of ZXDSL 9806Hhas the version to be uploaded. To download version, makesure that the directory on FTP server has the version to bedownloaded.

NMS Fails to Receive NE AlarmMessages

Symptom ZXDSL 9806H has alarm message. Open the Realtime CurrentAlarms window in NetNumen N31 client. There is no alarm aboutNE.

Troubleshooting 1. Execute the get-ctrlport command to view whether ZXDSL9806H is configured with control port 162 (UDP type).

2. In NetNumen N31 client, check whether ZXDSL 9806H is con-figured with Trap Server. Make sure the IP address of TrapServer is correct.

3. In NetNumen N31, check whether alarm filtering is configured.

4. Use the serial port query software to view whether control port163 is used by other software. If it is used, uninstall the soft-ware.


Chapter 8 NM Faults

Unable To Start Client

Symptom The Netnumen N31 Client cannot be started after the NMS is in-stalled.

Troubleshooting 1. Make sure the server IP address is correct.

2. Make sure the database and server run normally.

3. Check firewall settings.

4. Check the use of system ports.

5. Check the bandwidth use.

NM Server Startup Failure

Symptom NM server fails to start.

Troubleshooting 1. Check whether SQL server works normally.

2. Make sure SQL server is installed with service pack SP3 orabove.

3. Select Start > Programs > NetNumen N31 > Tools > Net-Numen N31 Config Center. Select Common Configuration> Database Configuration. Make sure all parameters areconfigured properly.

4. Check NMS installation directory.


Figures

Figure 1 Troubleshooting Flow .............................................. 6

Figure 2 ADSL/ADSL2+ Service Fault Troubleshooting Flow .....12

Figure 3 VDSL2 Service Fault Troubleshooting Flow ................28

Figure 4 VoIP Service Fault Troubleshooting Flow ...................38

Figure 5 Multicast Service Fault Troubleshooting Flow .............51

Figure 6 System Fault Troubleshooting Flow ..........................57

Figure 7 NMS Fault Troubleshooting Flow ..............................71


Tables

Table 1 Safety Symbols ....................................................... 2

Table 2 Safety Symbol Levels ............................................... 2

Table 3 Requirements for Maintenance Engineers .................... 3

Table 4 Tools and Meters ..................................................... 4

Table 5 ADSL/ADSL2+ Service Fault Location ........................11

Table 6 Modem Fault Location..............................................12

Table 7 ADSL Subscriber Line Requirements ..........................14

Table 8 Cable Pairs Attenuations Per Kilometer ......................15

Table 9 Maximum Frequency Attenuations.............................15

Table 10 LED Indicators on SCCB.........................................16

Table 11 Modem Fault Location............................................18

Table 12 VDSL2 Service Fault Location..................................27

Table 13 Modem Fault Location............................................28

Table 14 VDSL Subscriber Line Requirements ........................30

Table 15 Cable Pairs Attenuations Per Kilometer.....................31

Table 16 Maximum Frequency Attenuations...........................31


Table 18 VoIP Service Fault Location ....................................37

Table 19 Line Test Specifications ..........................................39


Table 21 LED Indicators on ATLA/ATLC..................................42

Table 22 Multicast Service Fault Location ..............................51





Table 27 Solaris Commands ................................................68

Table 28 NM Fault Location .................................................70

Table 29 Hardware Requirements for Windows Server.............72

Table 30 Hardware Requirements for Windows Client..............72

Table 31 Hardware Requirements for Solaris Server................73

Table 32 Hardware Requirements for Solaris Client.................73


Index

AADSL/ADSL2 ServiceInformation Collection ......10ADSL/ADSL2 TechnologyIntroduction ......................9ADSL/ADSL2+ ServiceFault Handling .................17ADSL/ADSL2+ ServiceFault Location ..................10ADSL/ADSL2+ ServiceTroubleshooting Cases ......20

MMulticast Service FaultLocation..........................51Multicast ServiceInformation Collection ......50Multicast ServiceTroubleshooting Cases ......53Multicast TechnologyIntroduction ....................49

NNM Fault Handling .............75NM Fault Location ..............70

SSystem Fault Handling .......59System Fault InformationCollection........................55System TroubleshootingCases .............................59

Ttroubleshooting methods ......6

VVDSL2 Service FaultLocation..........................27VDSL2 ServiceInformation Collection ......26VDSL2 TechnologyIntroduction ....................25VoIP Service FaultLocation..........................36VoIP Service FaultsHandling .........................44

VoIP Service InformationCollection........................36VoIP Service Trou-bleshooting Cases ............46VoIP TechnologyIntroduction ....................35


Glossary

AC- Alternating Current

ADSL- Asymmetric Digital Subscriber Loop

AG- Access Gateway

BAS- Broadband Access Server

BRAS- Broadband Remote Access Server

CAC- Channel Access Control

CATV- CAble TeleVision

CDR- Call Detail Record

DC- Direct Current

DHCP- Dynamic Host Configuration Protocol

DMT- Discrete Multi-Tone

DNS- Domain Name Server

DSL- Digital Subscriber Line

DSLAM- Digital Subscriber Line Access Multiplexer

FDM- Frequency Division Multiplexing

FTP- File Transfer Protocol

HDTV- High Definition Television

ICMP- Internet Control Message Protocol

IGMP- Internet Group Management Protocol

IP- Internet Protocol

IPS- Intelligent Protection Switching



IPTV- Internet Protocol Television

ISP- Internet Service Provider

ITU-T- International Telecommunication Union-Telecommunication Stan-dardization Sector

LAN- Local Area Network

MG- Media Gateway

MGC- Media Gateway Controller

MGCP- Media Gateway Control Protocol

MVLAN- Multicast Virtual Local Area Network

NAT- Network Address Translation

NE- Network Element

NGN- Next Generation Network

NMS- Network Management System

ODF- Optical Distribution Frame

POTS- Plain Old Telephone Service

PPPoE- Point to Point Protocol over Ethernet

PSD- Power Spectrum Density

PSTN- Public Switched Telephone Network

PVC- Permanent Virtual Channel

QoS- Quality of Service

RP- Rendezvous Point

RTP- Real-time Transport Protocol

SDP- Session Description Protocol

SIT- Special Information Tone


Glossary

SNMP- Simple Network Management Protocol

SNR- Signal to Noise Ratio

SS- Soft Switch

STB- Set Top Box

TCP/IP- Transfer Control Protocol/Internet Protocol

TDR- Time Domain Reflectometry

TG- Trunk Gateway

TID- Terminal Identification

UDP- User Datagram Protocol

VCI- Virtual Channel Identifier

VDSL- Very High Speed Digital Subscriber Line

VDSL2- Very High Bit Rate Digital Subscriber Line 2

VLAN- Virtual Local Area Network

VPI- Virtual Path Identifier

VoIP- Voice over Internet Protocol


zxdsl9806h - donbassmedia.net.ua technical documents... ·...

Documents