Professional Documents
Culture Documents
1.fault Analysis
1.fault Analysis
FAULT ANALYSIS
wholly to the PC. Then, connect the abnormal MP to the PC and copy the real-
time OS from the PC. Modify the related configuration file.
(4) If the real-time OS starts up normally but the MP cannot start up normally,
it is possibly because the batch processing file or system parameter
configuration is incorrect. Check as follows: Whether the version file name is
correct in the batch processing file, whether parameter configuration of the
network card is correct, whether a repeated IP address is used, and whether the
old data are not emptied.
2. Fault 2:
Symptom: The communications between the active and standby MPs are
interrupted.
Locating: In normal operation, the active and standby MPs run at the same time.
The running indicators of both are flashing synchronously. When the
communications between the active and standby MPs are blocked, they cannot
communicate with each other normally. This will cause error in the
active/standby changeover and affect the normal operation of the system. The
fault cause may standby MP faulty, network cable or network faulty.
(1) Check whether the MP is powered on, that is, if the power indicator is on.
(2) Check whether the standby MP communication is normal on the O&M
console.
(3) Check the network through the O&M console whether the communication is
normal between the server and the active/standby MP.
(4) If you are not sure, please contact the local ZTE office for help.
3. Fault 3:
Symptom: The COMM board (MPMP, MPPP and STB) cannot run normally.
Locating: The power failure of the COMM board usually causes this alarm.
(1) Check whether the COMM board is inserted securely or in good contact.
Unplug and plug it again to verify that.
(2) Check whether the background configuration data are correct.
(3) Check whether the BE cable is correctly connected and whether the
connectors are secure. (The BE cable is the connection wire between the
COMM board and the DSNI board at the MP level).
(4) Check whether the cable itself has any problem. Try to replace it with a new
cable.
(5) If all the COMM boards cannot run normally, check whether the first pair of
DSNI boards in the third shelf is inserted securely or in good contact, and
Locating:
(1) If the SYCK is in a free running state, first view whether there is a clock
reference on the background alarming diagram. If no, check whether the
connection wire of the clock input reference is incorrect.
(2) If there is a clock reference, check whether the SYCK is in the self-selected
running status. If not, set the SYCK as the self-selected running status.
(3) In addition, choose different input references for observation to exclude the
input of some poor quality reference.
(4) If the SYCK board is always in the fast capture status, check whether the
upper-level clock signal quality is relatively poor or there is any level-2 clock
tracing the level-3 clock.
7. Fault 7:
Symptom: Error code alarm frequently occurs on the FBI board.
Locating:
(1) Change over the FBI boards. If the status resumes normal, it means that the
original FBI board has problems and should be replaced.
(2) Check whether the hardware jumper “Balance out/in” switch on the FBI
board is set correctly.
(3) Check whether the slot that of the FBI board located and the connector,
including optical fiber, have any damage or are loose.
(4) Check whether the active SYCK board on the module is in the tracing
status. If the active SYCK board is in the fast capture status but the standby
board is in the tracing status, the fault will disappear after the changeover of the
SYCK board. The normal operation of the FBI board requires excellent
synchronous clock. If the SYCK board is not in the tracing status, its clock
output might be in an unstable status, resulting in the FBI board clock unstable
and error codes. If the FBI board is connected with two modules with clocks
asynchronous, this alarm may also occur.
8. Fault 8:
Symptom: All alarm indicators in the alarm box are on, while there is no alarm
displayed in the fault management.
Locating:
(1) Check whether the ALARM.EXE process is running on the 129 server.
(2) If the alarm box is directly connected to the 129 server through a network
card, check if the net network works properly, and observe whether the
indicators on the network card are on, and whether they are flashing when there
are data transmitting (the network wire should be a crossover cable.)
(3) If the alarm box is connected to LAN through a HUB, check if there are
multiple 129 servers working simultaneously in the whole ZXG10 LAN, or
node 254 is occupied by another device (because node 254 is assigned to the
alarm box by default.)
Troubleshooting:
1. Check at the local office whether the signaling point codes, signaling link
codes, and trunk time slots of both parties are matched. If correct, proceed to
the next step.
2. Observe whether the indicator of the trunk with the link is flashing rapidly. If
it is always on, check if the trunk line is reversely connected. If it is flashing
rapidly, proceed to the next step.
3. Self-loop the trunk circuits of this link, and self-loop the link in the dynamic
management. Then, transfer the data. Observe the link status. If it is in the
service status, it means that the local office has no problem.
4. Self-loop this trunk at the opposite office. If it is still in the service status, it
means that there is no problem with the transmission. If the problem is not
solved yet, contact the opposite office to check whether the data are configured
correctly.
10. Fault 2:
Symptom: The signaling links of some or all office directions are interrupted
suddenly.
Locating:
1. Find out the physical location of the disconnected links, and check if the
boards at the location (DTI, DTEC) have any transmission alarm. If such alarms
as “Loss of Frame”, “TS0 all 1” or “Loss of frame at opposite end” arises,
check the transmission system immediately. Check whether the 2M line of DDF
rack has been improperly modified. If there is no transmission alarm, no DTI
board power failure indication is seen in the fault management system and the
diagnosis test of the board is normal, please proceed to the next step.
2. Check whether the No. 7 MTP data of local office are correct at the O&M
console. Check the O&M log whether the No. 7 data have been modified. If the
modification has an error, please correct it at once; otherwise, please proceed to
the next step.
3. Check whether No. 7 MTP data of each foreground module are normal. Try
to check the related MTP data table through probe. If an abnormality is
detected, rename the abnormal data and save them in the foreground. Then,
synchronize the data between the foreground and the background on the basis
of the correctness of background data. If it cannot be recovered after the
synchronization, please proceed to the next step.
4. Contact the opposite office at once for assistant checks. If no problem is