Sei sulla pagina 1di 79
ZXMSG 5200 Multiplex Service Gateway Maintenance Manual (Troubleshooting) ZTE CORPORATION ZTE Plaza, Keji Road South,

ZXMSG 5200 Multiplex Service Gateway

Maintenance Manual (Troubleshooting)

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

Version 2.0.2

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

Revision No.

Serial No.

Reason for Revision

12/30/2006

R1.0

sjzl20070021

First edition

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

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

   

Document Revision

 

Product Version

V2.0.2

Number

 

R1.0

 

Equipment Installation Date

   
 

Presentation:

(Introductions,

Procedures,

Illustrations,

Completeness,

Level

of

Detail,

Organization,

Appearance)

Good

Fair

Average

Poor

Bad

N/A

Your evaluation

 

of this

documentation

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

Make it more concise/brief

 

Improve the Contents

Add more step-by-step procedures/tutorials

Improve the organization

Add more troubleshooting information

Include more figures

Make it less technical

 

Your

Add more examples

Add more/better quick reference aids

suggestions for

Add more detail

Improve the index

 

improvement of

this

Other suggestions

documentation

# 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

 

Company

 

Postcode

 

Address

 

Telephone

 

E-mail

   

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

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

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:

TABLE 1 CHAPTER SUMMARY

Chapter

Summary

Chapter 1 Troubleshooting

Introduces fault classification and fault analysis.

Chapter 2 External Interface Fault Troubleshooting

Introduces common ZXMSG 5200 external interface faults and troubleshooting.

Chapter 3 Internal Fault Troubleshooting

Introduces common ZXMSG 5200 internal faults and troubleshooting.

Chapter 4 Narrowband

Introduces common ZXMSG 5200 narrowband

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

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

Chapter

Summary

Subscriber Fault

subscriber faults and troubleshooting.

Troubleshooting

Chapter 5 Broadband Subscriber Troubleshooting

Introduces common ZXMSG 5200 broadband subscriber faults and troubleshooting.

Chapter 6 System Maintenance Fault

Introduces common ZXMSG 5200 system maintenance faults and troubleshooting.

Chapter 7 112 Testing Fault

Introduces common ZXMSG 5200 112 testing faults and troubleshooting.

Chapter 8 Subscriber Line Troubleshooting

Introduces line fault handling.

Appendix A Board Replacement

Introduces methods of replacing cards.

Appendix B Reference Values for 112 Test

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 Gateway Hardware Installation Manual (OUT30)

ZXMSG 5200 Multiplex Service Gateway Hardware Installation Manual (OUT50C/D)

ZXMSG 5200 Multiplex Service Gateway Hardware Installation Manual (19D06H20)

ZXMSG 5200 Multiplex Service Gateway Hardware Installation Manual (ONU100)

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.

¡Error! Estilo no definido.

Conventions

Typographical

ZTE documents employ the following typographical conventions.

Conventions

 

TABLE 2 TYPOGRAPHICAL CONVENTIONS

Typeface

 

Meaning

Italics

 

References to other Manuals and documents.

“Quotes”

 

Links on screens.

Bold

 

Menus, menu options, function names, input fields, radio button names, check boxes, drop- down lists, dialog box names, window names.

CAPS

 

Keys on the keyboard and buttons on screens and company name.

Constant width

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.
 

Note: Provides additional information about a certain topic.

  Checkpoint: Indicates that a particular step needs to be checked before proceeding further.
 

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
 

Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.

Mouse

TABLE 3 MOUSE OPERATION CONVENTIONS

Operation

   

Conventions

Typeface

Meaning

Click

Refers to clicking the primary mouse button (usually the left mouse button) once.

Double-click

Refers to quickly clicking the primary mouse button (usually the left mouse button) twice.

Right-click

Refers to clicking the secondary mouse button (usually the right mouse button) once.

Drag

Refers to pressing and holding a mouse button and moving the mouse.

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

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

How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software.

Customer

If you have problems, questions, comments, or suggestions

Support

regarding your product, contact us by e-mail at

Documentation

support@zte.com.cn. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830.

Support

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.

Chapter 1

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 fault causes. Sometimes, maintenance personnel just repeat his descriptions.

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

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

Therefore,

client’s

descriptions

are

reference

for

fault

solution.

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 2

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

It is failed to PING out-of-band debugging network interface after ZXMSG 5200 system is started normally.

Analysis

Possible causes are:

Troubleshooting

Improper cable connection

Abnormal system start-up

Improper PC network interface card configuration.

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.

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

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

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 doesn’t support input.

Analysis

Possible causes are:

Physical interface of serial port cable

Baud rate setting

Troubleshooting

Jumpers on ICS card

Follow the steps below to locate the fault:

1. It is normal that serial port supports output, while it doesn’t 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 in- band NM is failed.

Analysis

Possible causes are:

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.

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 ICS’s 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

It is failed to telnet through uplink port after starting ZXMSG

5200.

Analysis

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

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

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 Disconnected

Symptom

It is failed to get NE information after starting ZXMSG 5200 or during running.

Analysis

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

Signaling tracing on in-band node of ZXMSG 5200 is failed.

Analysis

Possible cause is that TCP/IP is failed between PC and ZXMSG

Troubleshooting

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.

Chapter 2 ¡Error! Estilo no definido.

Chapter 2 ¡Error! Estilo no definido.

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

It is failed to upload/download in-band NM version or data.

Analysis

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

successful for FTP SERVER to ping

it

is

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.

Analysis

Possible causes are:

SNMP is disconnected between NM and NE.

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

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

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 3

Internal Fault Troubleshooting

This chapter introduces common ZXMSG 5200 internal faults and troubleshooting.

Abnormal H.248

Symptom

H.248 link between ZXMSG 5200 and SS is disconnected.

Analysis

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.

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

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

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.

Analysis

Possible causes are:

Troubleshooting

CNIC version doesn’t exist or it is incorrect.

CNIC subcard is not inserted tightly.

BOOT chip is burnt improperly.

CNIC hardware is faulty.

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.

Analysis

Possible causes are:

Backplane data configuration error

MPR BOOT chip fault

MPR firmware version error

Chapter 3 ¡Error! Estilo no definido.

Chapter 3 ¡Error! Estilo no definido.

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 don’t 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.imgpp12fw2.imgpp12fw3.imgpp12fw4.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

It is failed to hear dialing tone after picking up the phone. NMS or alarm pool shows that IPS sub-module works abnormally.

Analysis

Possible causes are:

Troubleshooting

The subcard of IPS (GCXM) is not inserted in MPR.

ICS FLASH is lack of MPR version information.

Improper operation.

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

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

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

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.

Analysis

Possible causes are:

Troubleshooting

BOOT burning error

Version error

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

version

view whether ICS (slavecpu.bin).

FLASH

contains

8031

4. Ensure ICS card is firmly inserted in the backplane.

Replace

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

Analysis

Possible causes are:

Hardware models of active and standby cards are inconsistent.

ICS card is not inserted into the backplane.

Chapter 3 ¡Error! Estilo no definido.

Chapter 3 ¡Error! Estilo no definido.

Troubleshooting

Versions for active and standby ICS are inconsistent.

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

The ICS card on the master shelf works normally. The standby ICS card does not work.

Analysis

Possible causes are:

Standby ICS card fault

Software version doesn’t match.

Troubleshooting

Abnormal active/standby communications

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 don’t hear tone. Broadband users of the slave shelf can’t ping broadband users of the master shelf. The slave shelf is in OUT_USED state.

Analysis

Possible causes are:

Wrong cascading HW cable connection

Wrong jumpers on slave shelf backplane

Troubleshooting

Wrong slave shelf data configuration

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,

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

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

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.binicsfpga.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 get- shelfinfo 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.

Analysis

Possible causes are:

Card is faulty.

Real card type is inconsistent with configured type.

Troubleshooting

8031 slave CPU is faulty.

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

Chapter 3 ¡Error! Estilo no definido.

Chapter 3 ¡Error! Estilo no definido.

Analysis

disconnected. View on ZXMSG 5200 NMS and find subscribers on in off-line state.

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.

Analysis

Possible causes are:

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.

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

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

Chapter 4

Narrowband Subscriber Fault Troubleshooting

This chapter introduces common ZXMSG 5200 narrowband subscriber faults and troubleshooting.

Off-Hook VOIP Subscriber Hearing Nothing

Symptom

Subscribers hook off and hear nothing.

Analysis

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.

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

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

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

Subscribers hook off and hear busy tone.

Analysis

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

The subscriber hooks up and hears dialing tone. Then, he starts to dial numbers while dialing tone doesn’t eliminate.

Analysis

Possible cause is that DTMF is abnormal in receiving numbers.

Troubleshooting

Check whether DTMF-type DSP module works normally. Refer to the ‘DSP Chip of MRP Working Abnormally’ section.

Chapter 4 ¡Error! Estilo no definido.

Chapter 4 ¡Error! Estilo no definido.

Hearing Busy Tone while Dialing

Symptom

The off-hook subscriber dials the first phone number and hears busy tone.

Analysis

Possible causes are:

Troubleshooting

This subscriber hasn't the right of dialing phone numbers starting with this number.

Phone number table configured in SS is not complete.

Follow the steps below to locate the fault:

1. On SS, check whether this subscriber has this calling authority. If not, add the user’s 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

Occasionally, it is failed to make calls.

Analysis

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

Calls are frequently broken during calling.

Analysis

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:

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

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

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

The subscriber dials phone number and hears special information tone (SIT). Signaling shows that SS sends SIT.

Analysis

Possible cause is that SS is configured with improper data.

Troubleshooting

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

The subscriber hears loud noise in conversation.

Analysis

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.

Chapter 4 ¡Error! Estilo no definido.

Chapter 4 ¡Error! Estilo no definido.

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

Subscribers find the echo in conversation is too loud.

Analysis

Possible causes are:

Opposite subscriber

Local phone set

ZXMSG 5200 echo suppression is disabled.

Troubleshooting

It is configured improperly.

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

The opposite caller is failed to hear the conversation.

Analysis

Possible cause

is

the

route of ZXMSG 5200 is configured

improperly.

Troubleshooting

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.

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

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

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 problem, such as improper internal MAC address pool.

Faxes Failure

Symptom

It is successful to make calls between electrographs, while it is failed to send faxes.

Analysis

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.

Chapter 5

Broadband Subscriber Troubleshooting

This chapter introduces common ZXMSG 5200 broadband subscriber faults and troubleshooting.

ADSL MODEM Link Establishment Failure

Symptom

ADSL MODEM is failed to establish links.

Analysis

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

ADSL MODEM link establishment ratio is low.

Analysis

Possible causes are:

ADSL MODEM

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

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

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

ADSL subscriber is successfully to establish links, while PPPOE authentication is failed.

Analysis

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.

Troubleshooting

BAS data configuration is error or BAS is faulty.

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

Chapter 5 ¡Error! Estilo no definido.

Chapter 5 ¡Error! Estilo no definido.

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.

Analysis

Possible causes are:

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.

Troubleshooting

BAS setting problem or faulty.

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’. Don’t select this option.

3. For WINDOWS users, if all above check items are correct, re- install 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.

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

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

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

ADSL subscribers complain that the Internet access rate is low and disconnection occurs frequently.

Analysis

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 doesn’t match with that of upper-layer equipment.

Upper-layer network problem

Troubleshooting

BAS problem.

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.

Chapter 5 ¡Error! Estilo no definido.

Chapter 5 ¡Error! Estilo no definido.

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

When ADSL uses FTP, the rate is too low.

Analysis

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.

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

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

This page is intentionally blank.

Chapter 6

System Maintenance Fault

This chapter introduces common ZXMSG 5200 system faults and troubleshooting.

Failed to Download Version in ICS Serial Port BOOT Mode

Symptom

In ICS serial port BOOT prompt, it is failed to use the T command to download version.

Analysis

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.

Troubleshooting

PC has some problems.

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 SERVER’s user name and password are su3. Ensure that FTP file path is path of downloading version on the PC.

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

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

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.

Analysis

Possible causes are:

SQL SERVER is not installed.

SQL SERVER is not started normally.

Troubleshooting

The operating system of PC is faulty.

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.

Chapter 6 ¡Error! Estilo no definido.

Chapter 6 ¡Error! Estilo no definido.

Failed to Create MSG 5200 on NMS

Symptom

It is successful to start NMS, while it is failed to create ZXMSG 5200 NE on the NMS.

Analysis

The possible cause is that the option of ‘Support ZXMSG 5200 NE’ is not selected while installing the NMS.

Troubleshooting

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

Upgrade the system version through telnet, FTP or NMS. Then, restart the system. It is failed to restart ICS.

Analysis

Possible causes are:

Version error

Version file is damaged due to version downloading fault.

Troubleshooting

Symptom

The BOOT file doesn’t match the version.

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 doesn’t match with the upgrade version, burn the BOOT version again.

Failed to Upgrade ADSL Line Card Version

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.

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

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

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.

Chapter 7

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,

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 sub- card 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”.

two

types of

test

boards

are

often used

in

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

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

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 self- test 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. Don’t 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 don’t come from test board. Incorrect data configuration or improper connection lines are causes. These problems frequently occur to an expanded office.

Chapter 7 ¡Error! Estilo no definido.

Chapter 7 ¡Error! Estilo no definido.

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 A-

B.

Analysis

Possible causes are:

Testing version is not consistent.

The test line card is damaged.

Troubleshooting

The test interconnection line is faulty.

Follow the steps below to locate the fault:

1. If the software version of testing card doesn’t 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.

Analysis

Possible causes are:

Testing version is not matchable.

The test line card is damaged.

The test interconnection line is faulty.

Troubleshooting

The system is not in proper grounding.

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.

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

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

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

Chapter 8

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,

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

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

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 kHz–1104 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.

TABLE 4 ATTENUATIONS PER KILOMETER OF C ABLE PAIRS

F(KHz)

40

60

80

120

150

300

1,024

0.3E1m

11.4

13.01

14.38

15.12

16.8

18.13

33.5

0.4mm

8.29

9.34

10.05

10.87

12.1

14.78

27.3

0.5mm

5.99

6.85

7.06

7.77

9

12.18

22.5

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-band’s carrier frequency is greater than 70 dB, the line cannot carry any information.

TABLE 5 M AXIMUM FREQUENCY ATTENUATION