ZXMSG 5200 - Maintenance Manual (Troubleshooting)

ZXMSG 5200 Multiplex Service Gateway
Maintenance Manual (Troubleshooting)
Version 2.0.2
ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: doc@zte.com.cn
LEGAL INFORMATION Copyright 2006 ZTE CORPORATION. The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION 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 CORPORATION or of their respective owners. This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter 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. The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support or training are subject to change without notice.
Revision History Date 12/30/2006 Revision No. R1.0 Serial No. Reason for Revision First edition
sjzl20070021
ZTE CORPORATION Values Your Comments & Suggestions!

Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers. Please fax to: (86) 755-26772236; or mail to Documentation R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057. Thank you for your cooperation!
Document Name Product Version ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting) V2.0.2 Document Revision Number R1.0
Equipment Installation Date Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance) Good Your evaluation of this documentation Fair Average Poor Bad N/A
Accessibility: (Contents, Index, Headings, Numbering, Glossary) Good Fair Average Poor Bad N/A
Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content) Good Fair Average Poor Bad N/A Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Improve the Contents Improve the organization Include more figures Your suggestions for improvement of this documentation Add more examples Add more detail Other suggestions __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ # Please feel free to write any comments on an attached sheet. If you wish to be contacted regarding your comments, please complete the following: Name Postcode Telephone Company Address E-mail Make it more concise/brief Add more step-by-step procedures/tutorials Add more troubleshooting information Make it less technical Add more/better quick reference aids Improve the index
This page is intentionally blank.
Contents
About this Manual ........................................................... ix
Purpose ............................................................................... ix Intended Audience ................................................................ ix Prerequisite Skill and Knowledge ............................................. ix What is in This Manual ........................................................... ix Related Documentation ........................................................... x Conventions ......................................................................... xi How to Get in Touch ............................................................. xii
Chapter 1.......................................................................... 1 Troubleshooting............................................................... 1

Fault Classification ..........................................................1 Fault Analysis .................................................................1
Narrowband Service Fault Analysis Approaches ..........................2 Broadband Service Fault Analysis Approaches ............................2
Chapter 2.......................................................................... 3 External Interface Fault Troubleshooting....................... 3

Failed to PING Out-of-Band Debugging Network Interface .....3 No Output from ICS Serial Port .........................................4 Failed to PING Uplink Port ................................................4 Failed to TELNET through Uplink Port .................................5 In-band NM Disconnected.................................................6 In-band NM Signaling Tracing (112 Testing) Failed...............6 Failed to Upload/Download NM Data or Version ...................7 Failed to View NE Alarm Information on NM ........................7
Chapter 3.......................................................................... 9 Internal Fault Troubleshooting ....................................... 9

Abnormal H.248..............................................................9 Abnormal CNIC ............................................................. 10
DSP Chip of MRP Working Abnormally .............................. 10 IPS Chip of MRP Working Abnormally ............................... 11 8031 Slave CPU Working Abnormally ............................... 12 Active/Standby ICS Communications Interrupted............... 12 Standby ICS Off-line...................................................... 13 Slave Shelf Off-line ....................................................... 13 Narrowband Card Off-line............................................... 14 Broadband Card Off-line................................................. 14 Test Card Working Abnormally ........................................ 15
Chapter 4........................................................................17 Narrowband Subscriber Fault Troubleshooting............17

Off-Hook VOIP Subscriber Hearing Nothing ....................... 17 Off-Hook Subscribers Hearing Busy Tone .......................... 17 Failed to Terminate Dialing Tone ..................................... 17 Hearing Busy Tone while Dialing...................................... 17 Calling Failed Occasionally .............................................. 17 Calls Broken ................................................................. 17 Hearing SIT after Dialing................................................ 17 Loud Noise in Conversation ............................................ 17 Loud Echo in Conversation ............................................. 17 Opposite Caller Failed to Hear Conversation ...................... 17 Faxes Failure ................................................................ 17
Chapter 5........................................................................17 Broadband Subscriber Troubleshooting........................17

ADSL MODEM Link Establishment Failure .......................... 17 Low ADSL MODEM Link Establishment Ratio ...................... 17 PPPOE Authentication Failure .......................................... 17 ADSL Subscriber Successful for PPPOE Authentication, While Failed to Browse Website ............................................... 17 Low Internet Access Rate and Frequent Disconnection........ 17 Low FTP Rate ............................................................... 17
Chapter 6........................................................................17 System Maintenance Fault.............................................17

Failed to Download Version in ICS Serial Port BOOT Mode ... 17
Failed to Install NM Database.......................................... 17 Failed to Create MSG 5200 on NMS.................................. 17 Failed to Restart System after Upgrading System Version ... 17 Failed to Upgrade ADSL Line Card Version ........................ 17
Chapter 7........................................................................ 17 112 Testing Fault ........................................................... 17

Precautions for 112 Testing ............................................ 17 Analysis on 112 Testing Faults ........................................ 17 Inaccurate 112 Testing Values ........................................ 17 Big 112 Testing Value Error ............................................ 17
Chapter 8........................................................................ 17 Subscriber Line Troubleshooting................................... 17

Subscriber Line Parameters ............................................ 17
Requirements for ADSL Subscriber Line Parameters.................. 17 Definitions of Subscriber Line Parameters ................................ 17
Line Troubleshooting ..................................................... 17

Troubleshooting Procedure .................................................... 17 Troubleshooting at Office End ................................................ 17 Troubleshooting at User End .................................................. 17
Appendix A ..................................................................... 17 Board Replacement........................................................ 17

Overview ..................................................................... 17 Replacement of ICS....................................................... 17 Replacement of POWER Boards ....................................... 17 Replacement of Other Boards.......................................... 17
Appendix B ..................................................................... 17 Reference Values for 112 Test ...................................... 17

External Line Test ......................................................... 17
External Line Voltage Test ..................................................... 17 External Resistance Test ....................................................... 17 External Line Capacitance Test............................................... 17 Loop Resistance/Current Test ................................................ 17
Internal Line Test.......................................................... 17

Feeding Voltage ................................................................... 17
Ringing Current Voltage........................................................ 17 Circuit Current..................................................................... 17
Index ..............................................................................17 Figures............................................................................17 Tables .............................................................................17
About this Manual

Purpose
This Manual provides procedures and guidelines that support the maintenance of the ZXMSG 5200 Multiplex Service Gateway.
Intended Audience
This document is intended for engineers and technicians who perform maintenance activities on the ZXMSG 5200 Multiplex Service Gateway.
Prerequisite Skill and Knowledge

To use this document effectively, users should have a general understanding of network technology. Familiarity with the following is helpful:

The ZXMSG 5200 system and its various components Maintenance procedures Local operating procedures
What is in This Manual

This Manual contains the following chapters:
TAB LE 1 C HAPT ER SU MM AR Y
Chapter Chapter 1 Troubleshooting Chapter 2 External Interface Fault Troubleshooting Chapter 3 Internal Fault Troubleshooting Chapter 4 Narrowband
Summary Introduces fault classification and fault analysis. Introduces common ZXMSG 5200 external interface faults and troubleshooting. Introduces common ZXMSG 5200 internal faults and troubleshooting. Introduces common ZXMSG 5200 narrowband
Confidential and Proprietary Information of ZTE CORPORATION
ix
ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)
Chapter Subscriber Fault Troubleshooting Chapter 5 Broadband Subscriber Troubleshooting Chapter 6 System Maintenance Fault Chapter 7 112 Testing Fault Chapter 8 Subscriber Line Troubleshooting Appendix A Board Replacement Appendix B Reference Values for 112 Test
Summary subscriber faults and troubleshooting. Introduces common ZXMSG 5200 broadband subscriber faults and troubleshooting. Introduces common ZXMSG 5200 system maintenance faults and troubleshooting. Introduces common ZXMSG 5200 112 testing faults and troubleshooting. Introduces line fault handling. Introduces methods of replacing cards. Presents reference values for 112 test.
Related Documentation
The following documentation is related to this manual:
ZXMSG 5200 Multiplex Service Gateway Documentation Guide Technical Category: ZXMSG 5200 Multiplex Service Gateway Technical Manual ZXMSG 5200 Multiplex Service Gateway Hardware Manual Installation Category: ZXMSG 5200 Multiplex Service Installation Manual (OUT30) ZXMSG 5200 Multiplex Service Installation Manual (OUT50C/D) ZXMSG 5200 Multiplex Service Installation Manual (19D06H20) ZXMSG 5200 Multiplex Service Installation Manual (ONU100) Gateway Gateway Gateway Gateway Hardware Hardware Hardware Hardware
Operation Category: ZXMSG 5200 Multiplex Service Gateway Operation Manual ZXMSG 5200 Multiplex Service Gateway Command Manual Maintenance Category: ZXMSG 5200 Multiplex Service Gateway Maintenance Manual (Routine)
Error! Estilo no definido.
Conventions
Typographical Conventions ZTE documents employ the following typographical conventions.
TAB LE 2 TYPOGR APHICAL CONVENTIONS
Typeface Italics Quotes Bold
Meaning References to other Manuals and documents. Links on screens. Menus, menu options, function names, input fields, radio button names, check boxes, dropdown lists, dialog box names, window names. Keys on the keyboard and buttons on screens and company name. Text that you type, program code, files and directory names, and function names. Optional parameters. Mandatory parameters. Select one of the parameters that are delimited by it. Note: Provides additional information about a certain topic. Checkpoint: Indicates that a particular step needs to be checked before proceeding further. Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.
CAPS Constant width [] {} |
Mouse Operation Conventions
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface Click Double-click Right-click Drag
Meaning Refers to clicking the primary mouse button (usually the left mouse button) once. Refers to quickly clicking the primary mouse button (usually the left mouse button) twice. Refers to clicking the secondary mouse button (usually the right mouse button) once. Refers to pressing and holding a mouse button and moving the mouse.
xi
How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software. Customer Support If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at support@zte.com.cn. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830. ZTE welcomes your comments and suggestions on the quality and usefulness of this document. For further questions, comments, or suggestions on the documentation, you can contact us by e-mail at doc@zte.com.cn; or you can fax your comments and suggestions to (86) 755 26772236. You can also browse our website at http://support.zte.com.cn, which contains various interesting subjects like documentation, knowledge base, forum and service request.
Documentation Support
xii
Chapter
Troubleshooting
This chapter covers the following topics:

Fault Classification Fault Analysis
Fault Classification
Service faults may involve all parts related to service procedure. In terms of cause, the fault is classified into three types:
Hardware faults such as card or cable fault. Components on the card may be damaged due to dust, high temperature or humidity. Aging cable or cable in improper connection may cause service fault.
Faults caused by improper operations, such as wrong cable connection, wrong data or wrong version. Version problem.
Fault Analysis
Generally, basis for fault analysis comes from five channels:
Maintenance personnel's descriptions about the fault Usually, it is maintenance personnel who find out faults at the first time. What they describe about the fault is very important. Their descriptions may be reference for fault solution. Try to communicate with maintenance personnel for more details.
Client's descriptions about the fault Client knows well what the maintenance personnel just fault causes. Sometimes, repeat his descriptions.
Therefore, solution.
clients
descriptions
are
reference
for
fault
Equipment status Indicators on cards show equipment status. Maintenance personnel need know well about indicators. When fault occurs, they can read from indicators and solve it. Alarms and notification messages displayed on NMS NMS shows alarms and notification messages, which help maintenance personnel locate the fault
Alarms of connected equipment Sometimes the local equipment is failed to report alarms to NMS due to its own fault. Check whether the connected equipment has generated alarms. Find the fault causes based on alarms of connected equipment.
Narrowband Service Fault Analysis Approaches

Definite fault analysis approaches are helpful to solve faults effectively and quickly. For narrowband service, stream fault analysis approach is recommended. Here, stream refers to protocol stream/medium stream, which flows from the equipment where service starts to the equipment where service ends. Maintenance personnel need know which cards or devices the signalling passes through, on which part data configuration is required or which cards need software version support. If maintenance personnel have better knowledge about signalling stream, they can locate faults more easily.
Broadband Service Fault Analysis Approaches

For broadband service, stream fault analysis approach is also recommended. Here, stream refers to data stream, which flows form service source to service destination. There are some new concepts about broadband service, such as PVC, VLAN and TAG. Maintenance personnel need have some knowledge about these concepts. It is very important to locate faults.
Chapter
External Interface Fault Troubleshooting

This chapter introduces common ZXMSG 5200 external interface faults and troubleshooting.
Failed to PING Out-of-Band Debugging Network Interface

Symptom Analysis It is failed to PING out-of-band debugging network interface after ZXMSG 5200 system is started normally. Possible causes are:

Improper cable connection Abnormal system start-up Improper PC network interface card configuration.
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether PC is properly connected to ZXMSG 5200. If PC is directly connected to ZXMSG 5200, use crossover cable. If Ethernet cable is connected to PC, the network interface indicator is flashing. 2. Check whether ICS card works normally. In normal status, the RUN light is blinking slowly. Both M/S light and BACT light is constantly on. 3. Check whether PC IP is in the same network segment with the panel IP of ICS card. Ensure there is no IP collision in LAN. Check MAC address of debugging port in BOOT status. Check whether the MAC address is in collision with other MAC addresses. 4. Check whether the PC is configured with too many IP addresses. If there are many IP addresses, delete other IP addresses instead of the required one.
No Output from ICS Serial Port

Symptom During the process of starting ICS or after starting ICS, there is not any information about ICS serial port, or the information is in illegible code, or the serial port supports output, while it doesnt support input. Possible causes are:

Analysis
Physical interface of serial port cable Baud rate setting Jumpers on ICS card
Troubleshooting
Follow the steps below to locate the fault: 1. It is normal that serial port supports output, while it doesnt support input. In order to input, .it is necessary to input <Ctrl> + <Q>, then, the capital <SHELL> 2. Check whether serial port cable between PC and ZXMSG 5200 is connected properly. 3. Check whether baud rate is set to be 9600 n 8 - 1. Improper baud rate setting may cause serial port disconnected or illegible code. 4. Check the shortcut setting (X20, X21, X9, X3, X5). Set these jumpers to be 1, 2 shortcut. Viewed from the backplane, the right serial port is corresponding to the active ICS, The left serial port is corresponding to CNIC on the active ICS. 5. Check the line sequence of serial port cable. The ICS card of ZXMSG 5200 uses dual female DB9 serial port cable. Pins 2 and 3 are in crossed connection. Pin 5 is in straight connection.
Failed to PING Uplink Port

Symptom It is failed for In-band maintenance interface to ping voice uplink port. Consequently, the narrowband service is blocked and inband NM is failed. Possible causes are:

Analysis
VLAN and route are not added CNIC card works abnormally Uplink backplane subcard works abnormally PC is not configured properly.
Chapter 2 Error! Estilo no definido.
Troubleshooting
Follow the steps below to locate the fault: 1. Check Ethernet cables connecting PC, switch (or HUB), ZXMSG 5200 uplink port. Check whether ICSs ETH light is on. Check whether network interface light of PC is blinking normally. 2. Log on to port 1123 of ZXMSG 5200 in telnet mode. Use the show-vlan command to see whether VLAN of VOIP is added. If VLAN is added, check whether voice and management uplink ports are added to this VLAN. If PC is not in the VLAN where the uplink port of ZXMSG 5200 is, check the gate way settings of ZXMSG 5200 and PC. 3. Check whether MAC address of CNIC is in collision with other MAC addresses. 4. Check whether CNIC works normally. For detailed procedures, refer to the Narrowband Card Off-line section. 5. Check whether pins in uplink subcard slot are in neat arrangement. Check whether uplink subcard can be inserted in the slot properly. Check whether subcard and backplane are fixed with each other with screws.
Failed to TELNET through Uplink Port

Symptom Analysis It is failed to telnet through uplink port after starting ZXMSG 5200. Possible causes are:

TCP/IP is failed between PC and ZXMSG 5200. ZXMSG 5200 data, such as route information and control port number, is configured improperly,
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether it is successful to ping the uplink port of ZXMSG 5200. For detailed procedures, refer to the Failed to PING Uplink Port section. 2. Under the active ICS serial port mode, use the routeShow command to check route information. (Note: If the serial port is disconnected, refer to the No Output from ICS Serial Port section.) Check whether there are two pieces of route information for uplink port IP. Generally, if the debugging port IP is set in the same network segment where SS or gateway is, route information may be repeated. 3. Log on to port 1123 of ZXMSG 5200 in telnet mode. (Note: If the serial port is disconnected, refer to the Failed to PING Out-of-Band Debugging Network Interface section.) Use the get-ctrlport command to check whether control ports
contain port 1123. Check whether the transmission-layer protocol is TCP.
In-band NM Disconnected
Symptom Analysis It is failed to get NE information after starting ZXMSG 5200 or during running. Possible causes are:

TCP/IP is failed between PC and ZXMSG 5200. ZXMSG 5200 data, such as port number, is configured improperly.
Troubleshooting
Follow the steps below to locate the fault: 1. No Output from ICS Serial Port 2. Check whether it is successful to ping ZXMSG 5200 uplink port from NM server/client. For detailed procedures, refer to the Failed to PING Uplink Port section. 3. Log on to port 1123 of ZXMSG 5200 in telnet mode. (Note: If the serial port is disconnected, refer to the Failed to PING Out-of-Band Debugging Network Interface section.) Use the get-ctrlport command to check whether control ports contain port 161. Check whether the transmission-layer protocol UDP.
In-band NM Signaling Tracing (112 Testing) Failed

Symptom Analysis
Troubleshooting
Signaling tracing on in-band node of ZXMSG 5200 is failed. Possible cause is that TCP/IP is failed between PC and ZXMSG 5200. Follow the steps below to locate the fault: 1. Check whether TCP/IP connection between NM server/client and ZXMSG 5200 is successfully established. Telnet port 1123 or port 8888. For detailed procedures, refer to the Failed to TELNET through Uplink Port section. 2. Log on to port 1123 of ZXMSG 5200 in telnet mode. (Note: If the serial port is disconnected, refer to the Failed to PING Uplink Port section.) Use the get-ctrlport command to check whether control ports contain port 5001. Check whether the transmission-layer protocol is TCP. 3. Check whether signaling tracing or 112 testing is already in process, which occupies TCP port 5001. Consequently, signaling tracing may be failed.
4. If it is a 112 testing problem, check whether test line card is in position. For details on test line card troubleshooting, refer to the Test Card Working Abnormally section. 5. If it is a 112 testing problem, use the get-tlinetinfo command to check configurations on 112 test group. If it is failed to perform 112 testing on slave shelf, check 112 testing mutual-assistant cable and ringing mutual-assistant cable.
Failed to Upload/Download NM Data or Version

Symptom Analysis It is failed to upload/download in-band NM version or data. Possible causes are:

FTP SERVER is configured improperly. PC is not well connected to ZXMSG 5200.
Troubleshooting
Follow the steps below to locate the fault: 1. Check parameters of uploading/downloading version and data on NM interface, Including FTP SERVER, file path and file name. 2. Make sure that it is successful for FTP SERVER to ping ZXMSG 5200. 3. Make sure that FTP SERVER progress is started on FTP SERVER. FTP SERVER occupies the default TCP port 21. The default file path is designated on FTP SERVER. 4. For uploading version and data on NM, make sure the FLASH of ZXMSG 5200 contains the specified version or data file. For downloading version and data on NM, make sure the designated directory on FTP SERVER contains the specified version or data file. File name is case sensitive. File path is absolute path.
Failed to View NE Alarm Information on NM

Symptom The real-time monitoring window at NM client doesn't display any NM alarm while the alarm pool of ZXMSG 5200 shows alarm information. Possible causes are:
Analysis
SNMP is disconnected between NM and NE.

SNMP trap port is not added. Global/partial alarm filtering is set at NM client.
Troubleshooting
Follow the steps below to locate the fault: 1. Log on to port 1123 of ZXMSG 5200 in telnet mode. Use the get-ctrlport command to check whether control ports contain port 162. 2. View whether ZXMSG 5200 is configured with trap server. Check whether server ip is consistent with client IP. 3. Check whether any user set alarm filtering. 4. Use serial port query software to view whether port 162 is occupied by other software. If any other software occupies port 162, it is recommended to uninstall it.
Chapter
Internal Fault Troubleshooting

This chapter introduces common ZXMSG 5200 internal faults and troubleshooting.
Abnormal H.248
Symptom Analysis H.248 link between ZXMSG 5200 and SS is disconnected. Possible causes are:

ZXMSG 5200 data configuration error ICS software or hardware fault CNIC subcard fault EUX subcard fault Network between ZXMSG 5200 and SS fault SS fault and SS data configuration error
Troubleshooting
Follow the steps below to locate the fault: 1. Use the PC which shares the same network segment with ZXMSG 5200 to ping the uplink port of ZXMSG 5200. If it is failed, check data configuration, ICS status and uplink subcard. 2. Use the get-rip-cnic command to view whether ZXMSG 5200 is configured with next-hop route. If the next-hop route is not configured, configure it. If the configuration is incorrect, modify it. 3. Use the get-mgc command to view MGC configuration. If MGC is not configured, use the add-mgc command to add MGC. If MGC is configured improperly, use the mod-mgc command to modify relevant data. 4. If the port number is not 2944, use the add-ctrlport command on port 1123 to add relevant control port.
5. It is required for SS to check whether relevant ZXMSG 5200 data such as IP address and protocol port is configured. Check whether this gateway node exists. 6. Use the get-vlan command to view VOIP VLAN configuration. If VOIP VLAN is not configured, use the add-vlan command to add it. 7. Use the get-allnat command to view route setting from ICS to CNIC.
Abnormal CNIC
Symptom Narrowband subscribers are failed to make calls. Telnet port 8888. CNIC card is not started. NMS reports CNIC off-line alarm or alarm pool shows CNIC off-line alarm. Possible causes are: CNIC version doesnt exist or it is incorrect. CNIC subcard is not inserted tightly. BOOT chip is burnt improperly. CNIC hardware is faulty.
Troubleshooting
Analysis
Follow the steps below to locate the fault: 1. Check whether CNIC sub-card is inserted tightly. 2. Burn BOOT chip again. Or, replace the CNIC BOOT chip. 3. Check whether E /VERSION contains CNIC version (pp5.img). Compare the running CNIC version with that on ICS FLASH. If they are inconsistent with each other, download a new one. Then, reboot ICS card. 4. If hardware of CNIC subcard is faulty, replace a new one. Then, download CNIC version (pp5.img).
DSP Chip of MRP Working Abnormally

Symptom It is failed to hear dialing tone after picking up the phone. Two DSP indicators on MPR panel are not blinking slowly. NMS or alarm pool shows that DSP module works abnormally. Possible causes are:

Analysis
Backplane data configuration error MPR BOOT chip fault MPR firmware version error
10
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether the backplane of ZXMSG 5200 shelf is 216MICS_0404 series. 219MICS_0311 series backplanes dont support MPR. 2. Check whether MPR BOOT chip matches with main ICS version. 3. Ensure FLASH of main ICS card contains versions of MPR and all firmware. Log on to port 8888 of ZXMSG 5200 by telnet or NMS. Use the r07_ileshow command to view (pp12fw1.img pp12fw2.img pp12fw3.img pp12fw4.img pp12fw5.img). 4. Use the r07_fload command to download MPR firmware forcedly. 5. Telnet to port 1123. Use the get-dspstatus command to view whether DSP circuit is blocked. In normal status, it is IDLE. 6. Telnet port 1123. Use the mod-dspattrib command to configure properties of two DSP circuits to be tone and dtmf. Check whether it is able to start DSP normally.
IPS Chip of MRP Working Abnormally

Symptom Analysis It is failed to hear dialing tone after picking up the phone. NMS or alarm pool shows that IPS sub-module works abnormally. Possible causes are: The subcard of IPS (GCXM) is not inserted in MPR. ICS FLASH is lack of MPR version information. Improper operation.
Troubleshooting
Follow the steps below to locate the fault: 1. Telnet to port 1123. Use the get-ipsstate command to view the state of IPS circuit. Normally, it is in IDLE state. If it is in FAULT state, restart MPR. Report the operations which cause the FAULT information to R&D engineers. 2. Check the running state of MPR. Normally, the RUN light, the DSP1 light and the DSP2 light are all blinking slowly. 3. Pull out MPR card. Check whether the subcard of IPS (GCXM) is inserted in MPR properly. 4. Telnet to port 1123. Use the get-ipstermid command to view whether the IPS-related terminal is configured properly. Check whether the configured IPS subcard is in position. Ensure that the physical position with subcard is configured
11
with data. Use the get-allnat command to view whether the path from IPS subcard to CNIC is configured. 5. Telnet to port 1123. Use the get-ipsstate command to view whether IPS circuit is in blocked state. Only when IPS is in IDLE state, can it be used. 6. view versions of MPR and its firmware in ICS FLASH. They need be consistent with versions issued by R&D department.
8031 Slave CPU Working Abnormally

Symptom No dialing tone or only busy tone is heard after picking up the phone. The HOOK light or ALM light on narrowband subscriber line card is constantly on. Possible causes are:

Analysis
BOOT burning error Version error
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether BOOT chip of 8031 slave CPU is inserted properly. 2. Check whether BOOT program of 8031 CPU is successfully burnt. 3. Telnet to port 8888. Use the r07_fileshow command to view whether ICS FLASH contains 8031 version (slavecpu.bin). 4. Ensure ICS card is firmly inserted in the backplane. 5. Replace a new ICS card to check whether 8031 works normally.
Active/Standby ICS Communications Interrupted

Symptom Both the active and standby ICS cards (master or slave shelf) are in position. NMS shows the standby ICS off-line alarm and active/standby ICS communications interrupted alarm. Execute the active/standby changeover command. Execution is failed. Possible causes are: Hardware models of active and standby cards are inconsistent. ICS card is not inserted into the backplane. Analysis
12
Versions for active and standby ICS are inconsistent.

Troubleshooting
Follow the steps below to locate the fault: 1. For master shelf of ZXMSG 5200, check whether ICS hardware model is 216ICS_0311 or 216ICS_040400. Neither of them can be the ICS card of ZXMSG 5200 master shelf. 2. Check whether the standby ICS card (master or slave shelf) is properly inserted in the backplane. 3. Insert the active and standby ICS cards into slots 9 and 10. Use the r07_fileshow command to view whether their versions are the same. 4. Replace the backplane. Backplane fault may cause abnormal active/standby communications.
Standby ICS Off-line

Symptom Analysis The ICS card on the master shelf works normally. The standby ICS card does not work. Possible causes are:

Standby ICS card fault Software version doesnt match. Abnormal active/standby communications
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether the standby ICS card is properly inserted in slot 9 or 10. 2. Check whether the standby ICS card is started normally. 3. Check whether active/standby communications are normal.
Slave Shelf Off-line

Symptom Narrowband users of the slave shelf pick up the phone and dont hear tone. Broadband users of the slave shelf cant ping broadband users of the master shelf. The slave shelf is in OUT_USED state. Possible causes are:

Analysis
Wrong cascading HW cable connection Wrong jumpers on slave shelf backplane Wrong slave shelf data configuration
Troubleshooting
Follow the steps below to locate the fault: 1. Make sure cascading HW cable (master and slave shelves) is perfect. HW cable is connected properly. For master shelf,
13
legal pin numbers for HW cable are 3-6, 9-12, 15-18, 21-24. For slave shelf, legal pin numbers for HW are 3-6. 2. Check whether bit switch 4 of S1 jumper on the slave shelf backplane is on the left position, which stands for slave shelf mode. 3. Reboot the slave shelf. View versions (icsver.zslavcpu.bin icsfpga.bin) of the slave shelf in boot mode. They need be consistent with versions issued by R&D department. 4. Telnet to port 1123 or on ZXMSG 5200 NMS, use the getshelfinfo command to view whether the slave shelf is configured. Check whether the configured HW number is consistent with the actual cable. For master shelf, legal pin numbers for HW cable are 3-6, 9-12, 15-18, 21-24, corresponding to HW numbers 8, 9, 10, and 11 respectively. HW numbers 8, 9, 10 and 11 correspond to shelves 1, 2, 3 and 4.
Narrowband Card Off-line

Symptom The ALM light of narrowband subscriber card is constantly on. Or HOOK light is constantly on. Subscribers on this card picks up the phone and hear nothing. View on ZXMSG 5200 NMS and find subscribers on in off-line state. Possible causes are:

Analysis
Card is faulty. Real card type is inconsistent with configured type. 8031 slave CPU is faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Telnet to port 1123. Use the get-boardinfo to view whether the off-line slot is configured with narrowband card. Check whether real card type is consistent with configured type. 2. Perform signaling tracing and view whether ZXMSG 5200 reports the off-hook message. If the off-hook message is not reported, 8031 slave CPU works abnormally. For 8031 slave CPU troubleshooting, refer to the 8031 Slave CPU Working Abnormally section. 3. Replace the narrowband subscriber card with the same type of card.
Broadband Card Off-line

Symptom The red ALM light of broadband subscriber card is constantly on. Or green AL1-AL16 lights are constantly on. MODEM is
14
disconnected. View on ZXMSG 5200 NMS and find subscribers on in off-line state. Analysis Possible causes are:

Card is faulty. Card software version works abnormally. The boot file works abnormally. Real card type is inconsistent with configured type. 8031 slave CPU is faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Telnet to port 1123. Use the get-boardinfo to view whether the off-line slot is configured with broadband card. Check whether real card type is consistent with configured type. 2. Burn boot chip again or replace the boot chip. 3. Download card version. 4. Check whether 8031 slave CPU works abnormally. For 8031 slave CPU troubleshooting, refer to the 8031 Slave CPU Working Abnormally section 5. Replace the broadband subscriber card with the same type of card.
Test Card Working Abnormally

Symptom It is successful to log on to ZXMSG 5200 via in-band IP. However, it is failed to perform 112 testing. The light on test card shows the test card works abnormally. Possible causes are:

Analysis
Test card version error Burning error FLASH chip fault Improper testing cable connection between master and slave shelves.
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether test cards are properly inserted in relevant slots (Insert TSLCC into slot 17 of the shelf with single power. Insert TSLCD into any subscriber slot of the shelf with dual powers.) 2. Burn the version of test card again. 3. Check whether testing cables between master and slave shelves are properly connected.
15
16
Chapter
Narrowband Subscriber Fault Troubleshooting

This chapter introduces common ZXMSG 5200 narrowband subscriber faults and troubleshooting.
Off-Hook VOIP Subscriber Hearing Nothing

Symptom Analysis Subscribers hook off and hear nothing. Possible causes are:

Phone set fault, subscriber line fault Subscriber card fault Data configuration fault 8031 slave CPU is abnormal MPR DSP module is abnormal
Troubleshooting
Follow the steps below to locate the fault: 1. Determine it is global fault or partial fault. Check whether all subscribers have the problem or only special subscribers have the problem. 2. Pick up the phone and observe whether HOOK light is on. Use the get-slcstatus command to view whether the subscriber line is occupied. On NMS, view whether the subscriber line is occupied. 3. For data configuration problem of some subscribers, check whether relevant cards are configured and whether cards are on line. For narrowband card off-line troubleshooting, refer to the Narrowband Card Off-line section. 4. For 8031 slave CPU troubleshooting, refer to the 8031 Slave CPU Working Abnormally section.
17
5. If DSP is improperly configured or works abnormally, check whether DSP module in TONE type is configured. For DSP troubleshooting, refer to the DSP Chip of MRP Working Abnormally section. 6. The backplane fault may cause global fault. Global subscribers pick up phones and hear nothing. Replace a new backplane.
Off-Hook Subscribers Hearing Busy Tone

Symptom Analysis Subscribers hook off and hear busy tone. Possible causes are:

ZXMSG 5200 data configuration problem Relevant SS data configuration problem H248 disconnection
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether H248 link is properly established. Refer to the Abnormal H.248 section. 2. Telnet port 1123. Use the get-slctermid command to check the relevant TERMID. 3. Check SS data configuration, such as whether packet types are completely configured, whether this subscriber is released with number, whether protocol type is consistent.
Failed to Terminate Dialing Tone

Symptom Analysis
Troubleshooting
The subscriber hooks up and hears dialing tone. Then, he starts to dial numbers while dialing tone doesnt eliminate. Possible cause is that DTMF is abnormal in receiving numbers. Check whether DTMF-type DSP module works normally. Refer to the DSP Chip of MRP Working Abnormally section.
18
Hearing Busy Tone while Dialing

Symptom Analysis The off-hook subscriber dials the first phone number and hears busy tone. Possible causes are:
This subscriber hasn't the right of dialing phone numbers starting with this number. Phone number table configured in SS is not complete.
Troubleshooting
Follow the steps below to locate the fault: 1. On SS, check whether this subscriber has this calling authority. If not, add the users calling authority. 2. Check phone number table configured in SS. Make sure whether number string starting with this number is contained. If not, add this number string.
Calling Failed Occasionally

Symptom Analysis Occasionally, it is failed to make calls. Possible causes are:

IPS module works abnormally. ISP status on SS side is inconsistent with that on ZXMSG 5200 side.
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether IPS modules work normally. Refer to the IPS Chip of MRP Working Abnormally section. 2. Check whether ISP status on SS side is consistent with that on ZXMSG 5200 side.
Calls Broken
Symptom Analysis Calls are frequently broken during calling. Possible causes are:

SS is set with the function of overlong conversation audit. 8031 problem on ZXMSG 5200 side.
Troubleshooting
Follow the steps below to locate the fault:
19
1. If the call is broken after long conversation, check whether SS is set with the function of overlong conversation audit. If it is, it is normal. 2. If calls are frequently broken during conversation, check whether 8031 slave CPU reports on-hook messages or reed messages frequently. Upgrade 8031 slave CPU version to solve such a problem. 3. Observe whether 8031 slave CPU user port signal detection is faulty. Check whether the subscriber has intensive interference from outside.
Hearing SIT after Dialing

Symptom Analysis
Troubleshooting
The subscriber dials phone number and hears special information tone (SIT). Signaling shows that SS sends SIT. Possible cause is that SS is configured with improper data. Follow the steps below to locate the fault: 1. Check whether phone number table is consistent with phone number analysis. If the phone number table contains this number string while the relevant phone number analysis is configured with it, SS will send SIT. 2. Check whether this subscriber number in SS is consistent with the cluster of ZXMSG 5200.
Loud Noise in Conversation

Symptom Analysis The subscriber hears loud noise in conversation. Possible causes are:

Local subscriber line is in poor condition Remote subscriber line or signal is in poor condition. Phone set is faulty. DSL splitter at AUTC or AUTR is faulty. The current bearer network is in poor condition. Rack is in poor grounding condition. Medium gain of ZXMSG 5200 is too large.
Troubleshooting
Follow the steps below to locate the fault: 1. Remove causes at local side, such as phone set, line and signal. 2. Check the local phone set. 3. Check the local line.
20
4. If a splitter is connected before Modem and phone set, check the splitter and the opposite DSL line card. 5. If it is a toll call, check the current network status. 6. Check the medium gain of ZXMSG 5200. If it is too large, reduce it. 7. Check the working ground and protection ground. The voltage difference between working ground and protection ground is less than 0.1 V.
Loud Echo in Conversation

Symptom Analysis Subscribers find the echo in conversation is too loud. Possible causes are:

Opposite subscriber Local phone set ZXMSG 5200 echo suppression is disabled. It is configured improperly.
Troubleshooting
Follow the steps below to locate the fault: 1. Try another phone number. Observe whether the echo is loud. 2. Replace another phone set. Observe whether the echo is loud. 3. Check the parameter of Echo Suppression. If it disabled, enable it. 4. If Echo Suppression is configured improperly, ask the SS maintenance personnel to modify it.
Opposite Caller Failed to Hear Conversation

Symptom Analysis
Troubleshooting
The opposite caller is failed to hear the conversation. Possible cause is the route of ZXMSG 5200 is configured improperly. Follow the steps below to locate the fault: 1. Capture packets at AG uplink port while the conversion starts. Observe whether there are bi-directional medium packets. Confirm whether the fault occurs due to the equipment or upper-layer network. Check networking mode. Analyze whether medium packets is able to reach the destination.
21
2. Check the route configuration. Use the get-rip-cnic command to check whether ZXMSG 5200 is configured with the next hop and whether the next hop address is correct. 3. Other configuration may cause the improper internal MAC address pool. problem, such as
Faxes Failure
Symptom Analysis It is successful to make calls between electrographs, while it is failed to send faxes. Possible causes are:

The electrograph faulty Abnormal operations Unmatchable fax mode setting T38-related SDP fields are not set at SS side while T38 fax mode is used T38 fax mode is used for MODEM fax. Poor line quality

Troubleshooting
Follow the steps below to locate the fault: 1. Check the electrograph. Make sure operations are correct. 2. Use the get-rtppar-arp2 command at port 1123 to check whether fax modes are set in consistency, such as T30 or T38, complete control or half control, redundancy mode or transparent mode. 3. If faxing is performed across AG or through TG and PSTN, check whether fax mode setting of another AG or TG is consistent with AG. 4. If T38 faxing mode is used, check whether SS is configured with T38-related SDP fields. 5. If T38 faxing mode is used, it is recommended to use electrograph, instead of MODEM + software. 6. Check line quality, PSTN line and bearer network. 7. Check whether the uplink port is in 100 M full-duplex mode. If not, set the uplink port to be 100 M full-duplex mode.
22
Chapter
Broadband Subscriber Troubleshooting

This chapter introduces common ZXMSG 5200 broadband subscriber faults and troubleshooting.
ADSL MODEM Link Establishment Failure

Symptom Analysis ADSL MODEM is failed to establish links. Possible causes are:

ADSL MODEM is faulty. Subscriber line is not connected properly. Line subscriber line card is faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Check ADSL MODEM. Replace another ADSL MODEM. 2. Check subscriber line condition. Check line attenuation and noise. 3. Check whether ADSL line card works normally.
Low ADSL MODEM Link Establishment Ratio

Symptom Analysis ADSL MODEM link establishment ratio is low. Possible causes are:
ADSL MODEM
23

Subscriber line ADSL line card Rate configuration on the subscriber port
Troubleshooting
Follow the steps below to locate the fault: 1. Check the rate configuration on this subscriber port. If the link establishment rate is consistent with the rate limitation, it is normal. 2. Check whether ADSL MODEM. Replace another ADSL MODEM. 3. Check subscriber line condition. Check line attenuation and noise. 4. Check whether ADSL line card works normally.
PPPOE Authentication Failure

Symptom Analysis ADSL subscriber is successfully to establish links, while PPPOE authentication is failed. Possible causes are:

PPPOE authentication user name/password is wrong PC or dial-up software is faulty. ADSL line card is off line. ZXMSG 5200 data configuration is improper. ZXMSG 5200 broadband uplink port is disconnected. Network fault exists between ZXMSG 5200 and BAS. BAS data configuration is error or BAS is faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Check PPPOE user name and password. 2. Check PC network interface card and PPPOE dial-up software. 3. Check whether ZXMSG 5200 ADSL line card is on line throng NMS or command line. That is, use the unit command on port 8888 to check. 4. Check ZXMSG 5200 data configuration. Use the get-vlan command on port 1123 to check whether VLAN setting of subscriber port is consistent with VLAN setting of ZXMSG 5200 broadband uplink port. 5. Check whether ZXMSG 5200 broadband uplink port works normally. Ping broadband uplink port from normal user port and ping the normal user port from broadband uplink port. If ZXMSG 5200 broadband uplink port is faulty, check CNIC
24
card and uplink subcard. If the uplink card is faulty, replace it. 6. Check network condition between ZXMSG 5200 and BAS. 7. Check BAS data configuration and check whether BAS works normally.
ADSL Subscriber Successful for PPPOE Authentication, While Failed to Browse Website
Symptom It is successful for ADSL subscriber to perform PPPOE authentication, while it is failed for him to browse website or ping public network address. Possible causes are:

Analysis
PC network interface card is set improperly. PC IE is set improperly. Dial-up software is faulty. Networking at user side is faulty. Large packet restriction. BAS setting problem or faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Check TCP/IP setting, especially DNS setting. If IP is designated, auto get IP address is recommended. If the PC is configured with multiple network interface cards, disable others first. 2. Check IE setting. Generally browsing website failure occurs due to the selection of Auto Detection Setting. Dont select this option. 3. For WINDOWS users, if all above check items are correct, reinstall ADSL dial-up software. Three types of ADSL dial-up software are available: WinPoET, Ethernet300 and Raspppoe. Select any one. 4. If user end is in LAN networking, check the networking. Have access to the Internet on one PC. If it is successful to browse websites, the networking at user side is faulty, Frequent problems are when ADSL is in route mode, IP address on PC is inconsistent with IP on gateway. When ADSL is in agent mode, agent software or agent PC is faulty.
25
5. In DHCP mode, the Ethernet frame has 1518 bytes. It has 1522 bytes with tag. Ping the website separately with the frame of 1518 bytes and 1522 bytes. If it is failed, check whether large packet restriction is set from ZXMSG 5200 to BAS. 6. Check BAS data configuration and check whether BAS works normally.
Low Internet Access Rate and Frequent Disconnection

Symptom Analysis ADSL subscribers complain that the Internet access rate is low and disconnection occurs frequently. Possible causes are:

Card or line index configuration error ADSL MODEM compatibility problem Networking at user end faulty Improper ADSL MODEM setting Duplex working rate mode of ZXMSG 5200 uplink port doesnt match with that of upper-layer equipment. Upper-layer network problem BAS problem.

Troubleshooting
Follow the steps below to locate the fault: 1. Check whether ADSL MODEM has compatibility problem. Replace MODEM of other types. 2. Check networking at user side. Frequent networking problems are multiple phone sets are connected in front of the splitter. PC is not separated from ADSL MODEM while the user end is in LAN networking. It is recommended to adopt agent server or firewall. 3. Check ADSL MODEM setting. If ADSL MODEM is set with functions of built-in dialing and bridging, and the built-in dialing user name or password is wrong, ADSL MODEM will continuously send wrong PPPOE authentication packets when the user has access to Internet in dialing-up mode. Consequently, the network load is high and network performance is decreasing. Generally, it is not permitted to use built-in dialing-up function and bridging function at the same time. If such a problem exists, replace the MODEM. 4. Check whether duplex working rate mode matches with that of transmission equipment from ZXMSG 5200 uplink port to BAS.
26
5. Check card or user port line indexes. Try to modify noise margin and delay. 6. Check configurations of upper-layer network and BAS.
Low FTP Rate

Symptom Analysis When ADSL uses FTP, the rate is too low. Possible causes are:

Low ADSL link establishment rate FTP SERVER problem Other reasons
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether ADSL MODEM link rate is normal. Refer to the Low ADSL MODEM Link Establishment Ratio section. 2. Replace FTP SERVER. 3. Check other factors cause low rate. Refer to the Low Internet Access Rate and Frequent Disconnection section.
27
28
Chapter
System Maintenance Fault

This chapter introduces common ZXMSG 5200 system faults and troubleshooting.
Failed to Download Version in ICS Serial Port BOOT Mode

Symptom Analysis In ICS serial port BOOT prompt, it is failed to use the T command to download version. Possible causes are:
FTP SERVER is disconnected with ICS debugging network interface. FTP SERVER is not started or FTP SERVER is in improper setting. The MAC address of ICS debugging network interface is in collision with other MAC addresses in the network. The file to be downloaded has some errors. Disk C of ICS is not formatted. PC has some problems.

Troubleshooting
Follow the steps below to locate the fault: 1. Check network connection between PC and ICS debugging network interface. For ICS debugging interface problem handling, refer to the Failed to PING Out-of-Band Debugging Network Interface section. 2. Check whether FTP SERVER is enabled. If it is enabled, check FTP SERVER setting. Ensure that FTP SERVERs user name and password are su3. Ensure that FTP file path is path of downloading version on the PC.
29
3. Check whether the MAC address of ICS debugging network interface is in collision with other MAC addresses on the network. Ping ICS debugging network interface. It is failed frequently. Use the arp a command to view MAC address and find there is one more MAC address corresponding to the IP of ICS debugging network interface. Use M command in BOOT mode to modify the MAC address. 4. Execute T command. Then, check whether the file exists in the path for downloading version. The file is case sensitive. 5. Ensure disks of C, D and E of ICS have been low formatted before executing T command. 6. Check whether some applications which block FTP port exist. If it is difficult to confirm, replace the PC.
Failed to Install NM Database

Symptom During the process of database installation, the system prompts that it is failed to install NM database or the procedure of database installation is interrupted. Possible causes are:

Analysis
SQL SERVER is not installed. SQL SERVER is not started normally. The operating system of PC is faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether SQL SERVER is installed on NM server. Ensure the user name is sa and password is data. 2. Check whether SQL SERVER is started normally. 3. Ensure that the database is installed with SP3 and the latest patch. 4. PC problem may cause NM database installation procedure interrupted. Press <Ctrl> + <C> to continue. 5. If the problem still exists, re-install the operating system or replace the current PC with another one.
30
Failed to Create MSG 5200 on NMS

Symptom Analysis
Troubleshooting
It is successful to start NMS, while it is failed to create ZXMSG 5200 NE on the NMS. The possible cause is that the option of Support ZXMSG 5200 NE is not selected while installing the NMS. Follow the steps below to locate the fault: 1. Re-install ZXNMS NM server. 2. Select the option of Support ZXMSG 5200 NE.
Failed to Restart System after Upgrading System Version

Symptom Analysis Upgrade the system version through telnet, FTP or NMS. Then, restart the system. It is failed to restart ICS. Possible causes are:

Version error Version file is damaged due to version downloading fault. The BOOT file doesnt match the version.
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether the version is wrong or version file is damaged. Connect ICS serial port. Enter the BOOT mode. Check whether version size and version date of disk C are consistent with the upgrade version. If the version is wrong or version file is damaged, use the T command in serial port mode to upgrade the version. 2. If the previous BOOT version doesnt match with the upgrade version, burn the BOOT version again.
Failed to Upgrade ADSL Line Card Version

Symptom After the upgrade ADSL line card version is download to ICS, it is failed to download the version to line card. Or, the line card version is upgraded while the line card is off line after restarting.
31
Analysis
For the failure of downloading version to line card, the possible cause is that the line card is in off-line status before downloading the version to line card. The possible cause for off-line card after restarting is that the version file is damaged or faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. Check whether the line card is in normal status before downloading the version to line card. Use unit command under port 8888 or operate on the NMS to view whether the line card is in the active status. 2. Use the r07_mpfiledisply command under port 8888 to check whether the adlg.bin file saved in ICS is consistent with the Use the b command to clear the version. Then, restart ICS. Check whether it is successful to get new version automatically.
32
Chapter
112 Testing Fault

This chapter introduces common ZXMSG 5200 112 testing faults and troubleshooting.
Precautions for 112 Testing

Mind some precautions for 112 testing:
Hardware Connection Presently, two types of test boards are often used in engineering. i. TSLCC card: It resides in slot 17. It suits the shelf of single power board.
ii. TSLCD card: It resides in the subscriber card slot. It cannot reside in slot 17. It suits the shelf with dual power boards. To test ISDN subscribers, it is required to configure the subcard on TSLC board. Usually, an NE node is equipped with only one TSLC board, For NE node with multiple cascading shelves, the test interconnection line is used to implement the interconnection of test buses, for the purpose of testing multiple layers of shelves with one TSLC. At the same time, it is required to ensure that the TSLC board is inserted on the active MSG5200 shelf. Disconnection or improper connection of test interconnection line will directly result in incorrect subscriber line test result of cascading shelves. Sometimes, it will affect subscriber line test results of subscriber on the shelf holding the test board. Perform subscriber line tests on subscribers of the shelf without holding test board when test interconnection lines are not connected. For external lines, the result is definitely Broken. For internal lines, the result is definitely No tone.
33
Data configuration In the access network, the data related to the subscriber line test includes: Test board, test resource and test circuit. To configure data related to subscriber line tests, follow steps below:
1. Add test board. 2. Configure test resource.
Analysis on 112 Testing Faults

Analysis Make an analysis in three aspects.

Check whether there is any alarm in the test board. The self-test of test board is normal but the test resource configuration is incorrect. If the test proves that the sub-node subscriber of test board is normal, the test interconnection line may be faulty.
Procedure
Follow the steps below to locate the fault: 1. Check whether NMS displays alarm message of the corresponding TSLC board. If there is an alarm, the test board may be damaged. If there is no alarm, have the selftest on test board. In normal case, the Idle message returns. If the Blocked message returns, unblock the test board. Then, conduct the self-test on the board. Dont use the test board until it passes the self-test. 2. If the test goes smoothly while the test result is incorrect, the test board may be damaged or test interconnection lines may be connected improperly. Test subscribers of sub-nodes controlled by the test board. If the result is normal, the test board itself is normal and it is necessary to examine reliability of test interconnection lines. 3. If test results on subscribers under the sub-node are incorrect, unplug the test interconnection line. Eliminate possible influences from other faulty boards on the test board. If this still does not work, take out subscriber boards from this shelf and leave only the subscriber board where the test subscriber is located. Leave boards and connection lines as few as possible. NOTE: In most cases, inaccurate test results dont come from test board. Incorrect data configuration or improper connection lines are causes. These problems frequently occur to an expanded office.
34
Inaccurate 112 Testing Values

Symptom 112 testing values are different from those measured with meter. 112 testing results show that the A-B resistance is very low and A-B capacitance is very high. All 112 testing results show that very high DC voltage exists between A-G, B-G and AB. Possible causes are:

Analysis
Testing version is not consistent. The test line card is damaged. The test interconnection line is faulty.
Troubleshooting
Follow the steps below to locate the fault: 1. If the software version of testing card doesnt match with ICS version, upgrade the testing software version. 2. If components on the test line card are damaged, replace it with a new one. 3. If test cables between the master and slave shelves are not in proper connection, disconnect cables between the slave shelf and other shelves. Test the master shelf only. If 112 testing result is normal, connect cables between slave shelf and other shelves one after another. 4. Replace the test cable.
Big 112 Testing Value Error

Symptom Perform tests on the same subscriber. The value error is very large. The value error of external line voltage may reach 2 V ~ 3 V. Possible causes are:

Analysis
Testing version is not matchable. The test line card is damaged. The test interconnection line is faulty. The system is not in proper grounding.
Troubleshooting
Follow the steps below to locate the fault: 1. Check the software version of testing card. It matches with ICS version. 2. Check inter-shelf cables. They are in good connection. Disconnect the cables and the fault still exists. 3. Replace another testing card. The fault still exists.
35
4. Measure the voltage difference between working ground and protection ground. The voltage difference is 2 V. The normal value is less than 0.1 V. Connect the working ground and protection ground together. Perform the test on the same subscriber. There is little error. The fault is removed
36
Chapter
Subscriber Line Troubleshooting

This chapter covers the following topics:

Requirements for ADSL Subscriber Line Parameters Definitions of Subscriber Line Parameters Line Troubleshooting
Subscriber Line Parameters

Introduce requirements for line parameters and meanings of line parameters.
Requirements for ADSL Subscriber Line Parameters

Requirements for ADSL subscriber line parameters are:
There is no extra inductor on subscriber lines. If a telephone is connected with the modem, locate the splitter before the phone and modem. Otherwise, the transmission capability will be heavily impacted. A subscriber line must be a twisted pair copper wire. If the service wire is a four-core wire, it is recommended to use a four-core twisted pair cable instead of a four-core parallel wire. For four-core parallel wire, use one pair and leave the other idle. For an iron or aluminum parallel wire, the length must not exceed 20 meters. There is no shielding requirement for subscriber lines. It is recommended to use subscriber lines without bridge taps. If subscriber lines without bridge tap are not avoidable,

37
there can be up to two bridge taps on a subscriber line. Each bridge tap is smaller than 400 m and the distance between a bridge tap and an end is greater than 400 m.
The insulation resistance of two subscriber lines to the ground must be greater than 5 megaohms. The direct loop resistance of subscriber line conducting wire must be not larger than 1.1 kiloohms. The capacitance between subscriber lines must be less than 200 nF (if the capacitance is smaller than 150 nF, the Internet access speed can be more stable and higher). The capacitance between subscriber lines and the ground must be less than 5%. The near end crosstalk ratio must be greater than 50 dB and the far end crosstalk ratio is the total of the near end crosstalk ratio and the line attenuation. The idle channel noise must be smaller than or equal to -55 dBm. The average noise power spectrum density is smaller than or equal to -115 dBm/Hz. The nominal characteristic impedance of the line is 100 ohm, with a maximum of 10 % error allowed. Within the frequency range of 26 kHz1104 kHz, the longitudinal conversion loss must be greater than or equal to 50 dB. In special conditions, it can be greater than 40 dB. For ADSL subscriber lines with different line diameters, attenuations requirements are shown in Table 4.
T AB L E 4 AT T E N U AT I O N S PE R K I L OM ET ER OF C AB L E PAI R S
F(KHz)
40
60
80
120
150
300
1,024
0.3E1m 0.4mm 0.5mm

11.4 8.29 5.99
13.01 9.34 6.85
14.38 10.05 7.06
15.12 10.87 7.77
16.8 12.1 9
18.13 14.78 12.18
33.5 27.3 22.5
Maximum frequency attenuations are listed in Table 5. In case the attenuation is greater than the maximum value, the ADSL service is not available. Even if the service is launched, the performance and stability are not guaranteed. When the line attenuation of relevant sub-bands carrier frequency is greater than 70 dB, the line cannot carry any information.
T AB L E 5 M AX IM UM FR E QU E N C Y AT T E N U AT I O N
Frequency f(Hz) 60K 150K 300K
Maximum Attenuation 37dB 49dB 52dB
38
Frequency f(Hz) 400K 500K 600K
Maximum Attenuation 60dB 67dB 72dB
Definitions of Subscriber Line Parameters

SNR Noise Margin It is short for signal-to-noise ratio, the ratio between signal power and noise power in channels. Noise margin is the enhanced channel SNR by manually lowering the line speed to improve the anti-interference capability so that the stability of the ADSL service is guaranteed when the channel parameters are changed slightly and the line noise is changed. Attenuation includes uplink channel attenuation and downlink channel attenuation. Uplink channel attenuation is the difference (in the unit of dB) of signals sent from uplink sending end to ADSL receiving end at office end through line transmission. Downlink channel attenuation is the difference (in the unit of dB) of signals sent from downlink sending end to ADSL receiving end at office end through line transmission. It is short for frequency response. FR is the rate between input signals and the output signals through twisted pair wires transmission. It is short for near end crosstalk. NEXT occurs when the interference source and the receiving end of interfered pair wires are at the same end. It is short for far end crosstalk. FEXT occurs when the interference source is far away from the receiving end of interfered pair wires. The interference source and the receiving end of the interfered pair wires are at different ends.
Attenuation
FR
NEXT
FEXT
Line Troubleshooting
Introduce line troubleshooting.
Troubleshooting Procedure
Follow steps presented in Figure 1 to locate ADSL fault at office end.
39
FIGURE 1 TROUBLESHOOTING FLOW AT OFFICE END
Check subscriber lines
Measure basic line parameters, such as voltage, capacity and resistance
Parameters meet the requirements Y Test line through modem on MDF at office end
Troubleshoot the subscriber line fault as per actual situation
Meet connection rate and attenuation requirements Y Line fault location and troubleshooting at office end finished
Connector on the cable of the MDF and ADSL port are in poor condition
Follow steps presented in Figure 2 to locate ADSL fault at user end.
40
FIGURE 2 TROUBLESHOOTING FLOW AT USER SIDE
Troubleshooting at Office End

Introduce measurement of common line parameters and line test through Modem on MDF at office end.
Measuring Basic Line Parameters

Introduction Basic line parameters include voltage, capacitance and resistance. The ADSL subscriber line must meet requirements described in the Requirements for ADSL Subscriber Line Parameters section. Many methods are available for measuring line parameters. This manual introduces the most frequently used methods:

Measuring with a dedicated SunSet line tester Measuring with a multimeter Use a SunSet line tester to measure the voltage, resistance and capacitance:
SunSet Line Tester Measurement
41
Voltage
Follow steps below to measure the DC/AC voltage between A and B wires Va-b, DC/AC voltage between wire A and the ground Va-gnd, and DC/AC voltage between B wire and the ground Vbgnd. 1. Disconnect the line from the exchange. 2. Switch on the SunSet line tester. 3. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. 4. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. 5. Connect the green terminal of the tester to the ground.
Values
Perform as follows to obtain voltage values: 1. Open the MENU directory of the tester. Select DMMDCV to measure the DC voltage between A and B wires Va-b (the value of T_R on the tester), DC voltage between wire A and the ground Va-gnd (the value of T_G on the tester), and DC voltage between B wire and the ground Vb-gnd (the value of R_G on the tester). 2. Press ESC to exit. Select DMM ACV to measure the AC voltage between A and B wires Va-b (the value of T_R on the tester), AC voltage between wire A and the ground Vagnd (the value of T_G on the tester), and AC voltage between B wire and the ground Vb-gnd (the value of R_G on the tester).
Resistance
Follow steps below to measure the resistance between A and B wires Ra-b, resistance between wire A and the ground Ra-gnd, and resistance between B wire and the ground Rb-gnd. 1. Disconnect the line from the exchange. 2. Switch on the SunSet line tester. 3. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. 4. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. 5. Connect the green terminal of the tester to the ground.
Values
Perform as follows to obtain resistance values: Open the MENU directory of the tester. Select DMM OHM to measure the resistance between A and B wires Ra-b (the value of T_R on the tester), resistance between wire A and the ground Ra-gnd (the value of T_G on the tester), and resistance between B wire and the ground Rb-gnd (the value of R_G on the tester).
Capacitance
Follow steps below to measure the capacitance between A and B wires Ca-b, capacitance between wire A and the ground Ca-gnd, and capacitance between B wire and the ground Cb-gnd. 1. Disconnect the line from the exchange.
42
2. Switch on the SunSet line tester. 3. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. 4. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. 5. Connect the green terminal of the tester to the ground. Values Perform as follows to obtain capacitance values: Open the MENU directory of the tester. Select DMM DCV to measure the capacitance between A and B wires Ca-b (the value of T_R on the tester), capacitance between wire A and the ground Ca-gnd (the value of T_G on the tester), and capacitance between B wire and the ground Cb-gnd (the value of R_G on the tester). Result Multimeter Measurement Voltage All results need meet the requirements described Requirements for ADSL Subscriber Line Parameters section. in
Use a multimeter to measure the voltage, resistance and capacitance:

DC Va-b Disconnect the line from the exchange. Set the multimeter to the DC position. Connect the multimeter to A and B wires of the subscriber line terminal to measure the voltage between A and B wires, Va-b.
DC Va-gnd Disconnect the line from the exchange. Set the multimeter to the DC position. Connect the multimeter to wire A of the subscriber line terminal and grounding wire of MDF to measure the voltage, Va-gnd.
DC Vb-gnd Disconnect the line from the exchange. Set the multimeter to the DC position. Connect the multimeter to wire B of the subscriber line terminal and grounding wire of MDF to measure the voltage, Vb-gnd. Set the multimeter to AC position. Repeat the steps to measure AC voltages between A and B wires Va-b, between A wire and the ground Va-gnd, and between A wire and the ground Vb-gnd
Resistance
Ra-b Disconnect the line from the exchange. Set the multimeter to the resistance position. Connect the multimeter to A and B wires of the subscriber line terminal to measure the resistance between A and B wires, Ra-b.
Ra-gnd Disconnect the line from the exchange. Set the multimeter to the resistance position. Connect the multimeter to wire A of the subscriber line terminal and the grounding wire of MDF to
43
measure the resistance between A and grounding wires, Ragnd.

Rb-gnd Disconnect the line from the exchange. Set the multimeter to the resistance position. Connect the multimeter to wire B of the subscriber line terminal and the grounding wire of MDF to measure the resistance between B and grounding wires, Rbgnd.
Loop Ra-b Disconnect the line from the exchange at the office end. Set A and B wires in short circuit at DP side or subscriber side remotely. At the office end, set the multimeter to the resistance position. Connect it to A and B wires of the subscriber line terminal to measure the loop resistance between A and B wires.
Capacitance
Ca-b Disconnect the line from the exchange. Set the multimeter to the capacitance position. Connect the multimeter to A and B wires of the subscriber line terminal to measure the capacitance between A and B wires, Ca-b.
Ca-gnd Disconnect the line from the exchange. Set the multimeter to the capacitance position. Connect the multimeter to wire A of the subscriber line terminal and the grounding wire of MDF to measure the capacitance between A and grounding wires, Ca-gnd.
Cb-gnd Disconnect the line from the exchange. Set the multimeter to the capacitance position. Connect the multimeter to wire B of the subscriber line terminal and the grounding wire of MDF to measure the capacitance between B and grounding wires, Cb-gnd.
Result
All results need meet the requirements described Requirements for ADSL Subscriber Line Parameters section.
in
Testing Line Through Modem on MDF at Office End

Introduction Distribution cable at the office end refers to the cable between ZXA10 U300 and the MDF. Use cables attached to U300. Cable length ranges from 30 m to 150 m. Select appropriate cable as needed. Measuring the modem on the MDF at the office end is to check whether the MDF jumpers (internal lines) and the ADSL port are normal. Figure 3 illustrates the cable distribution for the test.
44
FIGUR E 3 CABLE DISTRIBUTION FOR TESTING MDF AT OFFICE END
Subscriberline
Voiceexchange
MDF1
MDF
Line tester
Exchangeline ZXA10 U300
Test Steps
With a SunSet line tester, follow steps below. Disconnect the subscriber line from the exchange. Switch on the SunSet line tester (with an ATU_R module). Connect the network port supplied with lines to the ADSL ATU_R port on the left of the tester. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. Connect the green terminal of the tester to the ground. Check whether internal lines are normal, channels the link bears and the maximum speed.
Test Means
Test means are as follows: Open the MODULE directory of the tester. Select SETUP. On the pop-up interface, select a line mode (ANSI, G.DMT, G.LITE or MULTI) as needed. Generally, G.DMT or G.LITE is selected. Click RETRAIN. The SunSet line tester will simulate the modem to set up a link. If the line is in good condition and the link setup succeeds, the tester will display the parameters of the link on the screen, as shown in Figure 4.
45
FIGURE 4 TESTING LINE EST ABLISHMENT INTERFACE
Values Description
Values on the line establishment interface show:

The line establishment mode is G.DMT. The line uses fast channel link setup mode. The maximum downlink channel rate is 8192 kbps. The actual downlink rate is 7616 kbps. The maximum uplink channel rate is 946 kbps. The actual uplink rate is 928 kbps. The rates show that the line is in good condition. The downlink noise margin (MARGN) is 11.5 dB and the uplink noise margin is 7.0 dB. The noise margins are smaller than 16 dB, so normal transmission can be carried out through the line. The uplink and downlink channel attenuations (ATTEN) are 1.5 dB, which is much smaller than the maximum attenuation (50 dB) for bearer lines. The downlink transmission power (POWER) is 7.5 dBm and the uplink transmission power is 12.0 dBm.
Result: The values show that the line is good in performance. It can bear ordinal ADSL service. Change the line mode on the SETUP interface to view the link setup condition in the G.LITE mode. If the line tester is not available, use ZXDSL 831A MODEM to measure line parameters. Connect the modem. If the modem can be activated normally, the ADSL subscriber can access the Internet normally, and the fastest rate can reach or approach the maximum rate set in the line configuration file, the subscriber line is in good condition. If not, the cable from ZXA10 U300 to the MDF is poor contact. Check the line and remove the fault.
46
Troubleshooting at User End

Introduce methods of testing subscriber lines at user side, testing subscriber cables through MODEM and testing subscriber LAN.
Testing Subscriber Lines at User Side

Subscriber lines at user end refer to cables from MDF at the office end to the subscriber home. Testing subscriber lines is to check whether the subscriber line is in good condition. Figure 5 shows the cable distribution for testing.
FIGUR E 5 CABLE DISTRIBUTION AT USER END FOR TESTING
Subscriberline
Voiceexchange
MDF1
MDF Line tester (at subscriber home)
Exchangeline ZXA10 U300
Figure 6 shows line troubleshooting flow at user end.
47
FIGURE 6 LINE TR OUB LESH OOTING FLOW AT USER END

Use the ATU-R simulation function of the tester to test the the line at the U-C point at the office end and find the line is in good condition. Test the line again at the U-R point at the subscriber side and check the line quality
Line transmission quality is unstable
Synchronization rate does not reach the service rate
Synchronization link setup fails
TDR/Loop resistance measurement: Check whether the line contains taps and coils and whether the impedance is too large (connector quality deteriorates)
TDR/Loop resistance measurement: Check whether the line contains taps and coils, whether the line is too long, and whether the impedance is too large (connector quality deteriorates)
TDR/Loop resistance measurement: Check whether the line contains taps and coils, whether the line is too long, and whether the impedance is too large (connector quality deteriorates)
PSD measurement: Check whether the noise power is too strong or whether there is other signal interference
DMT/BIT distributionmeasurement: Check which frequency band is heavily interfered or which signal attenuates greatly on the BIT distributiondiagram
Line attenuation measurement: Check whether the line attenuation is too large and whether there is abnormal frequency band; SNR measurement: Check whether the SNR is too small and whether there is abnormal frequency band; Line noise measurement: Check whether the noise increases greatly
Locate and troubleshoot the line fault or replace the subscriber line
SNR measurement: SNR shows whether any frequency band is heavily interfered by noises and whether signals attenuate greatly
Pulse noise measurement: Check whether any pulse interference is produced due to POS service or other interferences
Locate and troubleshoot the line fault or replace the subscriber line
Determine the frequency or spectrum of the noises to judge the noise source or the signal that produces the noise interference
Locate and troubleshoot the interference source or replace the subscriber line
Verify the QoS at the U-R point and note down the maintenance case
Use Sunset tester to test parameters below.

Time Domain Reflectometry (TDR) Noise Power Spectrum Density (PSD) SNR Pulse Noise
Testing Time Domain Reflectometry (TDR) Use TDR to evaluate the subscriber line transmission quality. At the joint between a line of 0.32 mm in diameter and a line of 0.4 mm in diameter, there is a small negative pulse reflected waveform. There is a positive pulse reflected waveform at the
48
terminal open. The size of a reflected waveform is relevant with the line distance. The longer the line is, the smaller the reflected waveform will be. Requirements TDR measurement requires a correct pulse width. Set the pulse width based on the line length which is calculated upon capacitance test. For a subscriber line shorter than 200 m, set the pulse width to be 200M_IN. For a subscriber line longer than 200 m, set the pulse width to be 200M_OT. Measurement Follow the steps below to measure TDR. 1. Disconnect the subscriber line from MODEM. Switch on the SunSet line tester. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. Connect the green terminal of the tester to the ground. 2. Open the MANU menu. Select TDR. Configure the line diameter according to the subscriber line. Accept the defaults for VP and AVG if no special requirement. Click START. A TDR curve is displayed. Result Except for the reflected point at the terminal, the TDR curve is smooth. There will be reflected points when discontinuous impedance occurs at the joint between the line with 0.32 mm in diameter and the line with 0.4 mm in diameter because the characteristic impedance of the line with 0.32 mm in diameter is greater than that of the line with 0.4 mm in diameter. Check the position of the reflected point and evaluate the length of the main cable with 0.32 mm in diameter. The performance of the ADSL service borne on a 1 km cable with 0.4 mm in diameter is equivalent to that borne on an 800m cable with 0.32 mm in diameter. From the TDR curve, you can estimate the frequency response curve. A smooth TDR curve corresponds to a smooth frequency response curve. The result indicates that the subscriber line is normal. Testing Noise Power Spectrum Density (PSD) Measurement Follow the steps below to measure PSD. 1. Disconnect the subscriber line from MODEM. Switch on the SunSet line tester. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. Connect the green terminal of the tester to the ground. 2. Open the MANU menu. Select LINE BACKGROUND NOISE. Configure the receive type (TERM or BRIDGE) as needed. Select PSD in the TYPE option. Then, click START. A background noise curve is displayed
49
3. Click TABLE to open relevant table about the spectrum and noise attenuation relationship. Click dBm/Hz to get the noise power spectrum density. Requirements If the noise power spectrum is in the range of 25140 KHz, the noise power spectrum density must be less than or equal to 120 dBm/Hz. If adjacent wire pairs include ISDN lines, the noise power spectrum must meet following requirements:
If the ISDN line is shorter than 1 km, the noise power spectrum density must be less than or equal to 95 dBm/Hz. If the ISDN line is shorter than 2 km, the noise power spectrum density must be less than or equal to 105 dBm/Hz. If the ISDN line is longer than 2 km, the noise power spectrum density must be less than or equal to 115 dBm/Hz.
Testing SNR Measurement Follow the steps below to measure TDR. 1. Disconnect the subscriber line from MODEM. Switch on the SunSet line tester. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. Connect the green terminal of the tester to the ground. 2. Open the MANU menu. Select LINE CONTROLLER SIGNAL TO NOISE. Click ENTER. An SNR curve is displayed. Result Measurement Decide the range of the SNR margin according to the SNR curve. Testing Pulse Noise Follow the steps below to measure TDR. 1. Disconnect the subscriber line from MODEM. Switch on the SunSet line tester. Connect the network port supplied with lines to the LINE TEST port on the right of the tester. Connect the red and black terminals of the tester to A and B wires of the subscriber line terminal. Connect the green terminal of the tester to the ground. 2. Open the MANU menu. Select LINE CONTROLLER IMPULSE NOISE. Click ENTER. The pop-up window shows parameters below.
THRESHOLD: It is the threshold of the pulse. When a noise is greater than the threshold, this is pulse noise. The value range is 50100 dBm DELTA: It is the range of the pulse. If the threshold is 50 dBm and the range is 4, low pulse range is 5054, middle pulse range is 5458 and high pulse is greater than 58.
3. Set MAX COUNT, DEAD TIMT and TIME as required. 4. Click START to test the pulse noise.
50
Result
The test result displays in the middle of the screen.
Testing Subscriber Line through Modem

Measurement Requirements Connect the splitter. Use Sunset tester to test connection parameters where a MODEM is connected to a phone. ADSL parameters need meet requirements below:
MaxB/R: The minimum downlink rate reaches 1472 kbps and the minimum uplink rate reaches 288 kbps. Atten: The downlink channel attenuation is up to 58 dB and the uplink channel attenuation is up to 43 dB. Connection rate: The maximum difference between the uplink connection rate measured at the DP side and the actual uplink connection rate is up to 128 kbps and the maximum difference between the downlink connection rate measured at the DP side and the actual downlink connection rate is up to 64 kbps.
Result Handling
The result may greatly differ from the measured connection rate at the DP side and the line attenuation. Check the parts below to solve the problem: 1. Connectors 2. Insulation of the line connectors 3. Splitter connection 4. Modem cable connection. It need be connected to the correct splitter port, namely the MODEM port. 5. If connectors and connecting cables are all in normal condition, the incoming line is of poor quality or is subject to serious interference. Twisted pair cables are commended.
LAN Testing at Subscriber End

If both the subscriber line and modem are in good condition while the subscriber cannot access the Internet or disconnection occurs frequently, check the line between the modem and the PC. Replace the faulty Ethernet cable or USB cable. Connect PC to the modem with a straight-though cable. If they are connected through USB ports, use a dedicated USB cable and install USB port drive correctly.
51
52
Appendix
Board Replacement
Appendix A covers the following topics:

Replacement of ICS Replacement of POWER Boards Replacement of Other Boards
Overview
Replacement of faulty boards is a commonly used and very important maintenance method during daily maintenance. We recommend that the equipment maintenance personnel, before replacing a board, should contact the related technical personnel or ZTEs local service engineers for technical support and guidance.
Replacement of ICS
Introduction The ICS cards are hot-swappable. It means that it is possible to replace the ICS card with the power on. It is not required to turn off the power supply of the sub-shelf. The ICS card works in the active/standby status. When an ICS becomes faulty, there is not any influence on the service of the unit. The maintenance personnel can replace the faulty ICS card at any time. Based on fault observation and analysis, verify that the card is faulty and needs to be replaced. Verify that the spare part is well functioning, and the model and program of the spare card are identical to those of the faulty card. Prepare an anti-static bag, an anti-moisture bag, a classified cartoon, and some adhesive labels for labeling. Follow the steps below to replace the ICS card. 1. Wear an anti-static wrist strap.
Preparation
Procedure
53
2. Pull the extractor of the fault card outward and downward with one hand using moderate force. When the card detaches with the slot and ejects, hold the lower edge of the card with the other hand, and gently pull the card out. During this process, avoid touching components or circuits on the card with the hand. 3. Put the removed faulty card into an anti-static bad lined with an anti-moisture bag, and label the bag to indicate the card model, program version and the word Faulty. Place the fault card into a cartoon as per the classification. Label the cartoon as well at the outside to facilitate consequent identification and proposal. 4. Verify the name of the spare card and insert it into the corresponding slot in the shelf by pressing the extractor on the card with a thumb and pushing the card in with moderate force until the extractor is caught, which means that the card is in position. Verification After the card is inserted, there will be a self-test process which may take some time. If the self-test succeeds, the indicators will start normal indication and the service will resume, indicating that the replacement has succeeded. If the card self-test fails, namely if the self-test does not stop, the final indication is abnormal, and the service of the related unit does not resume, the replacement has failed. Check whether the spare board is damaged or whether the fault is on another board. NOTE: Copy the above data to the ICS card.
Replacement of POWER Boards

Introduction For the ZXMSG 5200 (V2.0.2) system, the power boards of POWER H, POWER K and POWER G are available. For the three types of power boards, the replacement procedures and precautions are the same. Here, take POWER H board as an example. The POWER H board does not support hot swapping; namely, it is strictly forbidden to replace the POWER H board. Be sure to turn off the power switch before replacing the board. Preparation Based on fault observation and analysis, verify that the board is faulty and needs to be replaced. Verify that the spare board is well functioning, and the model and program of the spare board are identical to those of the faulty board. Prepare an anti-static bag, an anti-moisture bag, a classified cartoon, and some adhesive labels for labeling. Follow the steps below to replace the Power H board. 1. Wear an anti-static wrist strap.
Procedure
54
Appendix A Error! Estilo no definido.
2. Turn off the switch of the faulty POWER H. 3. Pull the extractor of the fault board outward and downward with one hand using moderate force. When the board detaches with the slot and ejects, hold the lower edge of the board with the other hand, and gently pull the board out. During this process, avoid touching components or circuits on the board with the hand. 4. Put the removed faulty card into an anti-static bad lined with an anti-moisture bag, and label the bag to indicate the card model, program version and the word Faulty. Place the fault card into a cartoon as per the classification. The cartoon should also be labeled at the outside to facilitate consequent identification and proposal. 5. Verify the name of the spare board and insert it into the corresponding slot in the shelf by pressing the extractor on the board with a thumb and pushing the board in with moderate force until the extractor is caught, which means that the board is in position. 6. After inserting the POWER H, turn on its power switch. Verification Check whether the indicators are in normal statuses and whether the service has resumed. To minimize influence on services, the board should be replace in the time section with the lowest traffic load in the night when. If the final indicators are in abnormal statuses after the replacement, the replacement has failed. Check whether the spare board is in good condition.
Replacement of Other Boards

Introduction For the ZXMSG 5200 (V2.0.2) system, the other boards refer to the service boards and subscriber cards, such as the TPU, ODT, ALC, DLCC, AUDB and DIB boards. All the other boards are hot-swappable. It means that it is possible to replace the card with the power on. It is not required to turn off the power supply of the sub-shelf. Preparation Based on fault observation and analysis, verify that the board is faulty and needs to be replaced. Verify that the spare board is well functioning, and the model and program of the spare board are identical to those of the faulty board. Prepare an anti-static bag, an anti-moisture bag, a classified cartoon, and some adhesive labels for labeling. Follow the steps below to replace the board. 1. Wear an anti-static wrist strap.
Procedure
55
2. Pull the extractor of the fault board outward and downward with one hand using moderate force. When the board detaches with the slot and ejects, hold the lower edge of the board with the other hand, and gently pull the board out. During this process, avoid touching components or circuits on the board with the hand. 3. Put the removed faulty card into an anti-static bad lined with an anti-moisture bag, and label the bag to indicate the card model, program version and the word Faulty. Place the fault card into a cartoon as per the classification. The cartoon should also be labeled at the outside to facilitate consequent identification and proposal. 4. Verify the name of the spare board and insert it into the corresponding slot in the shelf by pressing the extractor on the board with a thumb and pushing the board in with moderate force until the extractor is caught, which means that the board is in position. Verification After the board is inserted, there will be a self-test process which may take some time. If the self-test succeeds, the indicators will start normal indication and the service will resume, indicating that the replacement has succeeded. If the card self-test fails, namely if the self-test does not stop, the final indication is abnormal, and the service of the related unit does not resume, the replacement has failed. Check whether the spare board is damaged or whether the fault is on another board.
56
Appendix
Reference Values for 112 Test

Appendix B presents reference values for 112 test, including two parts:

External Line Test Internal Line Test
External Line Test

Table 6 shows external line test indices.
TABLE 6 EXTERNAL LINE TEST INDEXES
A-G DC voltage (V) AC voltage (V) Insulation resistance (k) Capacitance (F) [-8, 8] [0, 8] [10, 10000] [0, 0.3]
B-G [-8, 8] [0, 8] [10, 10000] [0, 0.3]
A-B [-8, 8] [0, 8] [20, 10000] [0.5, 2.0]
External Line Voltage Test

Test Result Take the test when the subscriber has hung up the phone and there is no power feed to the subscriber line. See Table 7.
57
TAB LE 7 EXT ERNAL LI N E VOLT AGE TES T RE SU LT
Result Analysis VACag or VACbg is greater than 100 V VACag or VACbg or VACab is greater than 8 V VDCag or VDCbg is greater than 45 V and smaller than 60 V VDCag or VDCbg or VDCab is greater than 8 V
Result Display Creepage AC abnormal Battery contact A/B wire DC abnormal
Description
The values in Table 7 are as described below:

VACag: The AC voltage between A wire and the ground VACab: The AC voltage between B wire and the ground VACbg: The AC voltage between A wire and B wire VDCag: The DC voltage between A wire and the ground VDCbg: The DC voltage between B wire and the ground VDCab: The DC voltage between A wire and B wire
NOTE: All the values here are absolute values.
External Resistance Test

Test In normal test, the subscriber has hung up the phone. There is no power feed to the subscriber line. NOTE: Unbalance between A wire to ground resistance and B wire to ground resistance may cause cross talk. Result See Table 8.
TAB LE 8 IN SU L AT ION RESIST ANCE TEST AN AL YSIS
Result Analysis Rag and Rbg are both greater than 10 k Rab is greater than 20 k and smaller than 10 M Rag or Rbg is smaller than 10 k Rab is greater than 1800 k and smaller than 20 M Rab is greater than 10 M, out of range
Result Display Normal Normal Earth contact A and B wires Loop in outward Line broken or no phone set connected; cable to be located by measuring capacitance Subscriber picked up the phone or short circuit exists
Rab is smaller than 1800
Description
58
Appendix B Error! Estilo no definido.

Rag: The insulation resistance between A wire and ground Rbg: The insulation resistance between B and ground Rab: The insulation resistance between A wire and B wire
External Line Capacitance Test

Test Carry out the test either in on-hook or off-hook status. However, it is a forced test in off-hook status. It is recommended to conduct the test in on-hook status. In addition, there is power feed to the subscriber line. Result See Table 9.
T AB L E 9 E X T ER N AL L I N E C AP AC I T AN C E TE S T AN AL Y S I S
Result Display Cag and Cbg are smaller than 0.3 F Cab is greater than 0.5 F and smaller than 2 F Cag or Cbg is greater than 0.3 F Cab is smaller than 0.5 F Cab is greater than 10 F, out of range Cab is greater than 2 F
Result Analysis Normal Normal Earthen contact, leakage or abnormal phone set capacity Broken line or phone set fault A-B short circuit or phone set fault Abnormal capacitance
Description

Cag: The capacitance between A wire and ground Cbg: The capacitance between B and ground Cab: The capacitance between A wire and B wire
Loop Resistance/Current Test

Test Conduct the test in off-hook status. The so-called loop resistance refers to the sum of the subscriber line resistance and the subscriber phone set resistance, and the measurement result is the sum of the subscriber line resistance and the equivalent impedance of the phone set. With difference wire sizes, the typical subscriber line resistance varies from 100 to 300 per km, and the typical phone set resistance varies from 200 to 600 . For common subscribers, the loop resistance should be between 300 and 1800 .
59
Result
See Table 10 and Table 11.

T AB L E 1 0 L O O P R E S I S T AN C E I N D E X AN A L Y S I S
Result Analysis The loop resistance is greater than 300 and smaller than 1800 The loop resistance is greater than 1800 The loop resistance is smaller than 300
Result Display Normal Subscriber has hung up the phone or the phones set is faulty Phone set fault or loop in outward
T AB L E 1 1 LO O P CU R R EN T I N D E X AN AL Y S I S
Result Analysis The loop current is greater than 0 mA and smaller than 100 mA The loop current is greater than 100 mA
Result Display Normal Loop current abnormal
Result: Normally the loop current is between 22 mA and 60 mA.
Internal Line Test

Internal line test involves the items below:

Feeding voltage Ringing current voltage Circuit current
Feeding Voltage
Test the feeding voltage between the subscriber line board and the phone set. For the result analysis, see Table 12.
T AB L E 1 2 F E E D I N G V O L T AG E I N D E X AN A L Y S I S
Normal feeding voltage (V) 40Vk60
Abnormal feeding voltage (V) Vk < 40 or Vk > 60
60
Appendix B Error! Estilo no definido.
Ringing Current Voltage

Test the ringing voltage, which should be between 50 V and 120 V; the average value is about 75 V. For the test result analysis, see Table 13.
T AB L E 1 3 RI N GIN G C U R R E N T V O L T AG E I N D E X AN AL Y S I S
Result Analysis The ringing current voltage is smaller than 50 V or greater than 120 V The ringing current voltage is greater than 50 V or smaller than 120 V
Result Display Abnormal The specific value is displayed
Circuit Current
For the test result analysis, see Table 14.
T AB L E 1 4 C I R C U I T C U R R E N T I N D E X AN A L Y S I S
Result Analysis The circuit current is greater than 100 mA The circuit current is greater than 0 mA and smaller than 100 mA
Result Display Abnormal The specific value is displayed
61
62
Index
112 Testing Fault, 33 Board Replacement, 53 Broadband Service Fault Analysis Approaches, 2 Broadband Subscriber Troubleshooting, 23 External Interface Fault Troubleshooting, 3 External Line Test, 57 Fault Analysis, 1 Fault Classification, 1 Internal Fault Troubleshooting, 9 Internal Line Test, 60 Narrowband Service Fault Analysis Approaches, 2 Narrowband Subscriber Fault Troubleshooting, 17 Subscriber Line Troubleshooting, 37 System Maintenance Fault, 29
63
64
Figures
Figure 1 Troubleshooting Flow at Office End ...................... 17 Figure 2 Troubleshooting Flow at User Side ....................... 17 Figure 3 Cable Distribution For Testing MDF at Office End.... 17 Figure 4 Testing Line Establishment Interface.................... 17 Figure 5 Cable Distribution at User End for Testing............. 17 Figure 6 Line Troubleshooting Flow at User End ................. 17
65
66
Tables
Table 1 Chapter Summary ............................................... ix Table 2 Typographical Conventions ................................... xi Table 3 Mouse Operation Conventions ............................... xi Table 4 Attenuations Per Kilometer of Cable Pairs .............. 17 Table 5 Maximum Frequency Attenuation.......................... 17 Table 6 External Line Test Indexes................................... 17 Table 7 External Line Voltage Test Result.......................... 17 Table 8 Insulation Resistance Test Analysis ....................... 17 Table 9 External Line Capacitance Test Analysis................. 17 Table 10 Loop Resistance Index Analysis .......................... 17 Table 11 Loop Current Index Analysis .............................. 17 Table 12 Feeding Voltage Index Analysis .......................... 17 Table 13 Ringing Current Voltage Index Analysis ............... 17 Table 14 Circuit Current Index Analysis ............................ 17
67

ZXMSG 5200 - Maintenance Manual (Troubleshooting)

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ZXMSG 5200 - Maintenance Manual (Troubleshooting)

Transféré par

Droits d'auteur :

Formats disponibles

ZXMSG 5200 Multiplex Service Gateway

Maintenance Manual (Troubleshooting)

ZTE CORPORATION Values Your Comments & Suggestions!

This page is intentionally blank.

Chapter 1.......................................................................... 1 Troubleshooting............................................................... 1

Chapter 2.......................................................................... 3 External Interface Fault Troubleshooting....................... 3

Chapter 3.......................................................................... 9 Internal Fault Troubleshooting ....................................... 9

Chapter 4........................................................................17 Narrowband Subscriber Fault Troubleshooting............17

Chapter 5........................................................................17 Broadband Subscriber Troubleshooting........................17

Chapter 6........................................................................17 System Maintenance Fault.............................................17

Chapter 7........................................................................ 17 112 Testing Fault ........................................................... 17

Chapter 8........................................................................ 17 Subscriber Line Troubleshooting................................... 17

Line Troubleshooting ..................................................... 17

Appendix A ..................................................................... 17 Board Replacement........................................................ 17

Appendix B ..................................................................... 17 Reference Values for 112 Test ...................................... 17

Internal Line Test.......................................................... 17

Ringing Current Voltage........................................................ 17 Circuit Current..................................................................... 17

Index ..............................................................................17 Figures............................................................................17 Tables .............................................................................17

About this Manual

Prerequisite Skill and Knowledge

What is in This Manual

Confidential and Proprietary Information of ZTE CORPORATION

ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)

Confidential and Proprietary Information of ZTE CORPORATION

Error! Estilo no definido.

Typeface Italics Quotes Bold

CAPS Constant width [] {} |

Mouse Operation Conventions

TABLE 3 MOUSE OPERATION CONVENTIONS

Typeface Click Double-click Right-click Drag

Confidential and Proprietary Information of ZTE CORPORATION

ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)

How to Get in Touch

Confidential and Proprietary Information of ZTE CORPORATION

Fault Classification Fault Analysis

Confidential and Proprietary Information of ZTE CORPORATION

ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)

Narrowband Service Fault Analysis Approaches

Broadband Service Fault Analysis Approaches

Confidential and Proprietary Information of ZTE CORPORATION

External Interface Fault Troubleshooting

Failed to PING Out-of-Band Debugging Network Interface

Confidential and Proprietary Information of ZTE CORPORATION

ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)

No Output from ICS Serial Port

Failed to PING Uplink Port

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Error! Estilo no definido.

Failed to TELNET through Uplink Port

Confidential and Proprietary Information of ZTE CORPORATION

ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)

contain port 1123. Check whether the transmission-layer protocol is TCP.

In-band NM Signaling Tracing (112 Testing) Failed

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Error! Estilo no definido.

Failed to Upload/Download NM Data or Version

FTP SERVER is configured improperly. PC is not well connected to ZXMSG 5200.

Failed to View NE Alarm Information on NM

SNMP is disconnected between NM and NE.

Confidential and Proprietary Information of ZTE CORPORATION

ZXMSG 5200 (V2.0.2) Multiplex Service Gateway Maintenance Manual (Troubleshooting)

Confidential and Proprietary Information of ZTE CORPORATION