ZXA10 MSAN Trouble Shoot

Course Outline

 Fault Classification
 Source and Analysis Approach
 Fault Analysis
 Example of Trouble Shoot
Fault Classification
 1. Hardware Fault
Boards or Cable Connection

 2. Faults caused by improper operation

Wrong connection ,configuration etc

 3. Version Fault
Course Outline

 Fault Classification
 Source and Analysis Approach
 Fault Analysis
 Example of Trouble Shoot
Source and Analysis Approach
 Fault Analysis Basis
 Fault description by personnel on duty in the equipment
room
 Problem description by telephone users
 Status of equipment
 Alarm messages displayed on NM
Source and Analysis Approach
 Fault Analysis Approach
• ZXMSG 5200
Check whether the fault occurs to a whole user shelf unit or to some
users within a user shelf unit.
The fault that occurs to the whole user shelf unit and its cascading
standby shelf unit is possibly related to the ICS or MPR of the NE or
to the uplink port to the upper-level office.
For the fault that involves some users within a user shelf unit, check
the corresponding ALC and user cables.
Maintenance personnel locate both faults by replacement.

• SS
On the SS side, the fault symptoms are normally related to the
Ethernet interface between the SS and the ZXMSG 5200. The SS
faults are classified as faults with Ethernet interface interruption and
faults without Ethernet interface interruption.
Course Outline

 Fault Classification
 Source and Analysis Approach
 Fault Analysis
 Example of Trouble Shoot
Fault Analysis
 Narrowband Service Fault Analysis Approaches
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.

 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..
Course Outline

 Fault Classification
 Source and Analysis Approach
 Fault Analysis
 Example of Trouble Shoot
External Interface Fault 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:
 Improper cable connection
 Abnormal system start-up
 Improper PC network interface card configuration.
 Troubleshooting
1. Check whether PC is properly connected to ZXMSG 5200.
2. Check whether ICS card works normally.
3. Check whether PC IP is in the same network segment with the
panel IP of ICS card. Check MAC address of debugging port in
BOOT status.
4. Check whether the PC is configured with too many IP addresses.
External Interface Fault Troubleshooting
 In-band NM Disconnected
Symptom: It is failed to get NE information after starting
ZXMSG 5200 or during running.
Analysis:
TCP/IP is failed between PC and ZXMSG 5200.
ZXMSG 5200 data, such as port number, is configured
improperly.
Troubleshooting:
1. No Output from ICS Serial Port
2. Check whether it is successful to ping ZXMSG 5200 uplink
port from NM server/client.
3. Log on to port 1123 of ZXMSG 5200 in telnet mode. Use
the get-ctrlport command to check whether control ports
contain port 161. Check whether the transmission-layer
protocol UDP.
Internal Fault Troubleshooting
 Abnormal H.248
Symptom:H.248 link between ZXMSG 5200 and SS
is disconnected.
Analysis:
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
Internal Fault Troubleshooting
 Troubleshooting:
1. Use the PC which shares the same network segment with ZXMSG
5200 to ping the uplink port of ZXMSG 5200.
2. Use the get-rip-cnic command to view whether ZXMSG 5200 is
configured with next-hop route.
3. Use the get-mgc command to view MGC configuration.
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.
Internal Fault Troubleshooting
 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
Card is faulty.
Real card type is inconsistent with configured type.
8031 slave CPU is faulty.
Troubleshooting:
1. Telnet to port 1123. Use the get-boardinfo to view whether the off-line
slot is configured with narrowband card.
2. Perform signaling tracing and view whether ZXMSG 5200 reports the
off-hook message.
3. Replace the narrowband subscriber card with the same type of card.
Narrowband Subscriber Fault Troubleshooting
 Off-Hook Subscribers Hearing Busy Tone
Symptom: Subscribers hook off and hear busy tone.
Analysis:
ZXMSG 5200 data configuration problem
Relevant SS data configuration problem
H248 disconnection
Troubleshooting:
1. Check whether H248 link is properly established.
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.
Narrowband Subscriber Fault Troubleshooting
 Calls Broken
Symptom: Calls are frequently broken during calling.
Analysis
SS is set with the function of overlong conversation audit.
8031 problem on ZXMSG 5200 side.
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.
Broadband Subscriber Troubleshooting
 ADSL MODEM Link Establishment Failure
Symptom: ADSL MODEM is failed to establish links.
Analysis:
ADSL MODEM is faulty.
Subscriber line is not connected properly.
Line subscriber line card is faulty.
Troubleshootingt:
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.
Broadband Subscriber Troubleshooting
 PPPOE Authentication Failure
Symptom: ADSL subscriber is successfully to establish links,
while PPPOE authentication is failed.
Analysis:
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.
Broadband Subscriber Troubleshooting
 Troubleshooting:
 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.
 4.Check ZXMSG 5200 data configuration.
 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.
 6.Check network condition between ZXMSG 5200 and BAS.
 7.Check BAS data configuration and check whether BAS works
normally.
System Maintenance Fault
 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’.
112 Testing Fault
 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:
Testing version does not match.
The test line card is damaged.
The test interconnection line is faulty.
The system is not in proper grounding.
Troubleshootingt:
1. Check the software version of testing card. It matches with ICS version.
2. Check inter-shelf cables.
3. Replace another testing card. The fault still exists.
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