2 AG - TS3001 - E01 - 1 MSAN Troubleshooting Introduction-32p-201605

MSAN Troubleshooting
Introduction
Contents
 Faults Classification
 Faults Processing Method
 Faults Discussing
Requirements for Maintenance Engineers
© ZTE Corporation. All rights reserved

Fault Classification
 Hardware faults such as card or cable fault.

 Components on the card may be damaged due to dust, high temperature or
humidity.
 Aging card or cable in improper connection may cause service fault.
 Faults caused by improper operations

 To minimize this type of fault, perform every procedure during operation.
Fault location is the key point to handle this type of fault.
 Faults caused by version problem.

 Upgrade some card versions to solve the version problem. Observe the state
after version upgrade.

Fault Analysis
 Fault Analysis Principle

 Equipment status
 Alarms and notification messages displayed on NMS
 Alarms on connected equipment
 Descriptions about the fault

Contents
Narrowband Service Fault Analysis
SS
ZXA10 C300M
IP network

Narrowband Service Fault Analysis
 Important parameter
 SS type
 SS IP address and port number
 MSAG IP address and mask
 MSAG nexthop
 Vlan for signaling
 Vlan for media
 Uplink exchange port (tagged or untagged and VLANID)
 Protocol type (H.248) and port (2944)
 Terminal ID and RTP resources

Broadband Service Fault Analysis
ZXA10 C300M
IP network

Broadband Service Fault Analysis
 Important parameter
 service vlan
 subscriber port
 DSL port PVC vpi and vci
 line profile

Contents
 External Interface Fault Troubleshooting
 System Fault Troubleshooting
 Narrowband User Fault Troubleshooting
 Broadband User Fault Troubleshooting
 System Maintenance Fault Troubleshooting
Failed to Ping Uplink Port
 Symptom
 In-band maintenance interface fails to ping voice uplink port. Consequently,
the narrowband service is blocked and in-band NMS fails.
 Possible causes
 VLAN and route are not configured.
 Uplink card works abnormally.
 IP gateway is not configured properly.

Failed to Ping Uplink Port
 Troubleshooting steps
 Check Ethernet cable connecting between ZXA10 C300M uplink port and
switch. Check whether uplink card ACT indicator is blinking normally.
 Login to ZXA10 C300M through serial port mode. Use the “show vlan”
command to check whether VLAN is configured properly.
 Check whether IP gateway is configured properly. Make sure that there is no
IP collision in LAN.

In-band NMS Signal Tracing Failure
 Symptom
 Signal tracing on ZXA10 C300M in-band node fails.
 Possible causes
 the TCP/IP link fails between computer and ZXA10 C300M.
 Check whether TCP/IP connection between NMS server/client and ZXA10
C300M is successfully established. For the detailed procedures, refer to Failed
to Ping Uplink Port.
 Use “show msag ctrlport” command to check whether control ports contain
port 5001. Make sure the transmission layer protocol is TCP.
 Check whether the signal tracing is running and occupies TCP port 5001,
which leads to the signal tracing failure at client end.

Contents
Abnormal H.248
 Symptom
 H.248 link between ZXA10 C300M and SS is disconnected.
 Possible causes
 ZXA10 C300M data configuration error
 Control card software or hardware fault
 Uplink card fault
 Network between ZXA10 C300M and SS is faulty
 SS fault or SS data configuration error

Abnormal H.248
 Use “show msag mgc” command to view MGC configuration.
 Use “ping”to check the route between the uplink port of ZXA10 C300M and
SS port. If it fails, check vlan&IP configuration, uplink card status, uplink port
status and relevant switch configuration.
 Use “show msag voip-ipaddr” to view whether the configured IP address
and next-hop are correctly.
 It is required for SS to check whether relevant ZXA10 C300M data such as IP
address and protocol port is configured. Make sure the gateway node exists.

Standby SCGL/SCGM Off-line
 Symptom
 The active SCGL/SCGM card works normally. The standby one does not work.
 Possible causes
 Standby SCGL/SCGM card fault
 Software version does not match.
 Abnormal active/standby communications

Standby SCGL/SCGM Off-line
 Check whether the standby SCGL/SCGM card is properly inserted in slot 10 or
11. Use “show card” to check whether standby SCGL/SCGM card state
changes from “offline” to “hwonline”.
 Check whether the standby SCGL/SCGM card is started normally. If not,
replace the standby SCGL/SCGM card.
 Check whether active/standby communications are normal.
 Use “show version-saved master” and “show version-saved slave”
command to view whether their versions are the same. If not, synchronized
with “sync-file img” command.

Contents
VoIP Subscribers Busy Tone Problem
 Symptom
 Subscribers hook-off and hear busy tone.
 Possible causes
 ZXA10 C300M data configuration problem
 Relevant SS data configuration problem
 H.248 disconnection
 Check whether H.248 link is properly established.
 Use “show msag slc terminationid” command to check the relevant TID.
 Check SS data configuration, such as packet type, subscriber information and
DAS.

Calls Broken
 Symptom
 Calls are frequently broken during calling.
 Possible causes
 SS is configured with the function of overlong conversation audit.
 ZXA10 C300M user card fault.
 If the call is broken after long conversation, check whether SS is configured
with the function of overlong conversation audit.
 Check whether slave CPU reports hook-on messages frequently. Upgrade
slave CPU version to solve such problem.
 Check whether the subscriber has intensive interference from outside.

Contents
ADSL2+/VDSL2 Modem Link Establishment
Failure
 Symptom
 ADSL2+/VDSL2 MODEM fails to establish links.
 Possible causes
 ADSL2+/VDSL2 modem is faulty.
 Subscriber line is not connected properly.
 Line subscriber line card is faulty.
 Check ADSL2+/VDSL2 modem. If faulty, replace ADSL2+/VDSL2 modem.
 Check subscriber line condition. Check line attenuation and noise.
 Check whether ADSL2+/VDSL2 line card works normally.

PPPoE Authentication Failure
 Symptom
 ADSL2+/VDSL2 subscriber is successful to establish link, while PPPoE
authentication fails.
 Possible causes
 PPPoE authentication user name/password is wrong
 Computer or dial-up software is faulty.
 ADSL2+/VDSL2 line card is offline.
 ZXA10 C300M data configuration is improper.
 ZXA10 C300M broadband uplink port is disconnected.
 Network fault exists between ZXA10 C300M and BAS.
 BAS data configuration has error or BAS is faulty.

PPPoE Authentication Failure
 Check PPPoE user name and password.
 Check computer network interface card and PPPoE dial-up software.
 Check whether ADSL2+/VDSL2 line card is online through NMS or command
line.
 Check data configuration. Use “show vlan” command to check whether
VLAN setting of subscriber port is consistent with VLAN setting of broadband
uplink port.
 Check whether broadband uplink port works normally. Ping broadband uplink
port from normal user port and ping the normal user port from broadband
uplink port.
 Check network condition between ZXA10 C300M and BAS.
 Check BAS data configuration and check whether BAS works normally.

Low Internet Access Rate and Frequent
Disconnection
 Symptom
 ADSL2+/VDSL2 subscribers complain that the Internet access rate is low and
disconnection occurs frequently.
 Possible causes
 Card or line index configuration error
 ADSL2+/VDSL2 MODEM compatibility problem
 Networking at user end faulty
 Improper ADSL2+/VDSL2 modem settings
 Duplex working rate mode of ZXA10 C300M uplink port does not match with
that of upper-layer equipment.
 Upper-layer network problem
 BAS problem.

Low Internet Access Rate and Frequent
Disconnection
 Check whether ADSL2+/VDSL2 modem has compatibility problem. If yes,
replace modem.
 Check ADSL2+/VDSL2 modem settings. If ADSL2+/VDSL2 modem is set with
functions of built-in dialing and bridging, the network load is high and
network performance decreases. It is not permitted, if such problem exists,
replace the modem.
 Check networking at user side. Frequent networking problems can be caused
by the multiple phone sets connected. Computer is not separated from
ADSL2+/VDSL2 modem while the user end is in LAN.
 Check whether duplex working rate mode matches with transmission
equipment from uplink port to BAS.
 Check configuration of upper-layer network and BAS.

Contents
Line Card Version Upgrade Failure
 Symptom
 After the upgrade, line card version is downloaded to control card but it fails
to download the version to line card or the line card version is upgraded while
the line card is offline after restart.
 Possible causes
 The line card is in “offline status” before downloading the version to line
card.
 The version file is damaged or faulty.
 Use “show version-saved” command to check whether the line card version
file saved in control card is consistent with upgraded version file, such as size
and date. If not, re-download the version file.
 Download version file to line card again. Restart line card and check whether
upgrade is successfully.

NMS Server Startup Failure
 Symptom
 NMS server fails to startup.
 Possible causes are:

 The NMS installation path is too long. Its path length exceeds 240 characters.
 Port 1111 is occupied by other programs.
 Check whether the installation path length exceeds 240 characters. If yes,
reinstall the system.
 Check whether port 1111 is occupied. Restart the server.

2 AG - TS3001 - E01 - 1 MSAN Troubleshooting Introduction-32p-201605

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2 AG - TS3001 - E01 - 1 MSAN Troubleshooting Introduction-32p-201605

Uploaded by

Copyright:

Available Formats

MSAN Troubleshooting

© ZTE Corporation. All rights reserved

 Hardware faults such as card or cable fault.

 Faults caused by improper operations

 Faults caused by version problem.

© ZTE Corporation. All rights reserved

 Fault Analysis Principle

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 Possible causes are:

© ZTE Corporation. All rights reserved

You might also like