Professional Documents
Culture Documents
1-1
1.1 Scope of Troubleshooting ...................................................................... 1-1
1.2 Knowledge and Skill ............................................................................... 1-2
1.2.1 Basic Knowledge about the Telecom Networks ............................. 1-2
1.2.2 MA5600 Service Functions and Networking .................................. 1-2
1.2.3 Operation and Maintenance Knowledge of the MA5600 ............... 1-2
1.2.4 Operating with the Troubleshooting Tools and Meters .................. 1-2
1.3 Procedure for Troubleshooting the MA5600 .......................................... 1-3
1.3.1 Flowchart ....................................................................................... 1-3
1.3.2 Collecting the Information .............................................................. 1-4
1.3.3 Analyzing the Fault ........................................................................ 1-5
1.3.4 Locating the Fault .......................................................................... 1-5
1.3.5 Eliminating the Fault ...................................................................... 1-6
1.4 Common Troubleshooting Methods ....................................................... 1-6
1.4.1 Overview ........................................................................................ 1-6
1.4.2 Alarm Analysis ............................................................................... 1-7
1.4.3 Performance Analysis .................................................................... 1-7
1.4.4 Exclusive Method ........................................................................... 1-7
1.4.5 Meter Test ...................................................................................... 1-7
1.4.6 Comparison.................................................................................... 1-8
1.4.7 Interchange .................................................................................... 1-8
1.4.8 Configuration Data Analysis ........................................................... 1-8
1.4.9 Protocol Analysis ........................................................................... 1-8
1.5 Contact of Huawei Technical Support .................................................... 1-9
Chapter 2 Common Troubleshooting Operations ........................................ 2-1
2.1 Loopback ................................................................................................ 2-1
2.1.1 Overview ........................................................................................ 2-1
2.1.2 Fiber Loopback .............................................................................. 2-2
2.1.3 IMA E1 Link Loopback ................................................................... 2-3
2.1.4 Software Loopback ........................................................................ 2-4
2.2 Replacing the Boards ............................................................................. 2-6
2.2.1 Overview ........................................................................................ 2-6
2.2.2 Precautions .................................................................................... 2-7
2.2.3 ESD-protective Measures .............................................................. 2-9
2.2.4 Replacing a Control Board ............................................................. 2-12
2.2.5 Replacing a Service Board ............................................................ 2-15
2.2.6 Replacing a Subboard ................................................................... 2-18
2.2.7 Replacing an Optical Module ......................................................... 2-20
2.3 Measuring the Optical Power ................................................................. 2-21
2.3.1 Overview ........................................................................................ 2-21
2.3.2 Measuring the Receive Optical Power ........................................... 2-22
2.3.3 Measuring the Transmit Optical Power .......................................... 2-23
2.3.4 Reference Criteria .......................................................................... 2-24
Chapter 3 Troubleshooting Physical Connections ...................................... 3-1
3.1 Troubleshooting xDSL Lines .................................................................. 3-1
3.1.1 Overview ........................................................................................ 3-1
3.1.2 Fault Locating Process .................................................................. 3-2
3.1.3 Analyzing and Troubleshooting Frequent Faults ........................... 3-4
3.1.4 Case Study .................................................................................... 3-5
3.2 Troubleshooting Ethernet Ports .............................................................. 3-7
3.2.1 Overview ........................................................................................ 3-7
3.2.2 Fault Locating Process .................................................................. 3-9
3.2.3 Analyzing and Troubleshooting Frequent Faults ........................... 3-12
3.2.4 Case Study .................................................................................... 3-12
Chapter 4 Troubleshooting ADSL Services .................................................. 4-1
4.1 Introduction to ADSL Technology ........................................................... 4-1
4.1.1 Features of ADSL/ADSL2+ ............................................................ 4-1
4.1.2 Technical Specifications ................................................................ 4-1
4.1.3 Reference Model ............................................................................ 4-2
4.1.4 ADSL/ADSL2+ Services of the MA5600 ........................................ 4-3
4.2 Fault Locating Process ........................................................................... 4-4
4.2.1 Flowchart ....................................................................................... 4-4
4.2.2 Locating an ADSL Fault Primarily .................................................. 4-4
4.2.3 Checking the Modem ..................................................................... 4-5
4.2.4 Checking Line Conditions .............................................................. 4-6
4.2.5 Checking the MA5600 .................................................................... 4-7
4.2.6 Checking the Upper Layer Device ................................................. 4-7
4.3 Analyzing and Removing Frequent Faults ............................................. 4-7
4.3.1 Failure to Make a Phone Call and Accessing the Internet ............. 4-7
4.3.2 Success in Making a Phone Call, but Failure to Access the
Internet .................................................................................................... 4-8
4.3.3 Low Internet Access rate ............................................................... 4-9
4.3.4 Frequent Offline Problems in Accessing the Internet..................... 4-10
4.4 Case Study ............................................................................................. 4-10
4.4.1 Success in Accessing the Internet Without Buzz in the
Telephone ............................................................................................... 4-10
4.4.2 Failure to Access the Internet with Buzz in the Telephone ............ 4-11
4.4.3 ATU-R Easily Deactivated in Making a Phone Call ....................... 4-12
4.4.4 Low Internet Access Rate Caused by Inconsistent Software &
Hardware Settings of Network Card ....................................................... 4-12
4.4.5 Failure to Activate the Modem Caused by Wrong Wiring of
Subscriber Lines ..................................................................................... 4-14
4.4.6 Frequent Internet Surfing Interruptions Caused by Wrong
Wiring of SPL board ................................................................................ 4-15
4.4.7 Failure to Activate ATU-R Caused by Wrong Wiring of SPL
Board ...................................................................................................... 4-15
4.4.8 Noise to Telephone Caused by High Frequency Interfering
Sources ................................................................................................... 4-16
4.4.9 Failure to Display Caller ID on the ADSL User¡fls Telephone ....... 4-16
4.4.10 Noise to the Telephone During a Phone Call Caused by
Wrong Wiring on MDF ............................................................................ 4-17
4.4.11 Faults Caused by Incorrect Settings of ADSL Port
Parameters ............................................................................................. 4-18
4.4.12 Low Internet Access Rate Caused by Virus-affected PC ............. 4-21
4.4.13 Success in PPPoE Dialup but Failure in Internet Access ............ 4-22
4.4.14 Failure to Pass Authentication with Correct PPPoE Username
and Password ......................................................................................... 4-22
4.4.15 Failure in Internet Access Caused by DNS Faults ....................... 4-23
4.4.16 Relatively Long Delays for Some Packets in Pinging the
Gateway .................................................................................................. 4-24
4.4.17 Loss of Packets and Low Internet Access Rates Caused by
Wrong Connection of Network Cable for HUB ........................................ 4-24
4.4.18 Failure to Log in to the ADSL Modem Through Internet
Explorer (IE) ............................................................................................ 4-25
4.4.19 Frequent Service Interruptions Caused to the User with a
Stationary IP Address ............................................................................. 4-26
4.4.20 Negative Downstream Channel SNR Margin ............................... 4-27
Chapter 5 Troubleshooting SHDSL Services ................................................ 5-1
5.1 Introduction to SHDSL Technology ........................................................ 5-1
5.1.1 Features of SHDSL ........................................................................ 5-1
5.1.2 Technical Specifications ................................................................ 5-1
5.1.3 Reference Model ............................................................................ 5-2
5.1.4 SHDSL Services of the MA5600 .................................................... 5-2
5.2 Fault Locating Process ........................................................................... 5-3
5.2.1 Fault Locating Flowchart ................................................................ 5-3
5.2.2 Locating a Fault Primarily .............................................................. 5-4
5.2.3 Checking the Modem ..................................................................... 5-4
5.2.4 Checking Line Conditions .............................................................. 5-5
5.2.5 Checking the MA5600 .................................................................... 5-6
5.2.6 Checking the Upper Layer Device ................................................. 5-6
5.3 Analyzing and Removing Frequent Faults ............................................. 5-6
5.3.1 Troubleshooting Based on States of the LEDs on the Modem ...... 5-6
5.3.2 Comparing with Historic Records and with the Neighboring
Line Parameters ...................................................................................... 5-6
5.3.3 Line Activation Failure Caused by Incorrect Parameter Settings... 5-6
5.3.4 Troubleshooting User Operations .................................................. 5-7
5.4 Case Study ............................................................................................. 5-8
Chapter 6 Troubleshooting Ethernet Services ............................................. 6-1
6.1 Introduction to Ethernet Technology ...................................................... 6-1
6.1.1 Features of LAN ............................................................................. 6-1
6.1.2 Technical Specifications ................................................................ 6-1
6.1.3 Reference Model ............................................................................ 6-3
6.1.4 Ethernet Services of the MA5600 .................................................. 6-4
6.2 Fault Locating Process ........................................................................... 6-6
6.2.1 Fault Locating Flowchart ................................................................ 6-6
6.2.2 Checking Port State ....................................................................... 6-6
6.2.3 Checking Port Rate and Duplex Settings....................................... 6-6
6.2.4 Checking Tag Attributes of Ports ................................................... 6-7
6.2.5 Checking Board VLAN Settings ..................................................... 6-7
6.2.6 Checking Service Port Settings ..................................................... 6-8
6.2.7 Checking Port statistics.................................................................. 6-8
6.3 Analyzing and Removing Frequent Faults ............................................. 6-9
6.4 Case Study ............................................................................................. 6-9
6.4.1 Ethernet Service Failures Caused by Wrong Network Cable
Making .................................................................................................... 6-9
6.4.2 Failure to Ping the Gateway Caused by Wrong Terminal Route
Settings ................................................................................................... 6-10
6.4.3 Low Internet Access Rate Caused by Failure in VLAN Isolation
for Upstream Port.................................................................................... 6-10
6.4.4 Internet Service Interruption Caused by Conflict of Gateway IP
Address ................................................................................................... 6-11
6.4.5 Low Internet Access Rate Caused by Unnecessary Protocols ...... 6-12
6.4.6 Internet Service Interruption Caused by a User’s Cluster MAC
Address Settings ..................................................................................... 6-12
6.4.7 Internet Access Failure Caused by Wrong VLAN settings ............. 6-13
Chapter 7 Troubleshooting Multicast Services ............................................ 7-1
7.1 Introduction to Multicast Technology ...................................................... 7-1
7.1.1 Features of Multicast ...................................................................... 7-1
7.1.2 Multicast Services of the MA5600 .................................................. 7-1
7.2 Fault Locating Process ........................................................................... 7-2
7.2.1 Failure to Access the Internet ........................................................ 7-3
7.2.2 Failure to Watch a Program Although Success in Accessing
the Internet .............................................................................................. 7-6
7.2.3 Failure to Watch a Program with Good Quality.............................. 7-10
7.3 Analyzing and Removing Frequent Faults ............................................. 7-12
7.4 Case Study ............................................................................................. 7-12
7.4.1 Poor Quality of Some Programs Ordered ...................................... 7-12
7.4.2 Triple Play User¡fls Failure to Order a Program ............................. 7-12
Chapter 8 Analyzing and Handling Alarms ................................................... 8-1
8.1 Overview ................................................................................................ 8-1
8.1.1 Composition of Alarm ID ................................................................ 8-1
8.1.2 Alarm severity ................................................................................ 8-2
8.1.3 Querying Alarm Information ........................................................... 8-3
8.2 Threshold Alarm ..................................................................................... 8-5
8.2.1 15-minute Threshold Alarm............................................................ 8-5
8.2.2 24-hour Threshold Alarm ............................................................... 8-5
8.3 Patch Alarm ............................................................................................ 8-6
8.3.1 Active/Standby Board Patch Inconsistency Alarm ......................... 8-6
8.3.2 System Patch Files Recovery Failure Alarm .................................. 8-6
8.4 Load and Backup Alarms ....................................................................... 8-6
8.4.1 Auto-load Alarm ............................................................................. 8-6
8.4.2 Auto-load Alarm ............................................................................. 8-7
8.4.3 Rollback Alarm ............................................................................... 8-8
8.4.4 Duplicate Alarm.............................................................................. 8-10
8.4.5 Backup Alarm................................................................................. 8-10
8.4.6 Erase Alarm ................................................................................... 8-11
8.5 Inverse (or Switch) Alarm ....................................................................... 8-12
8.5.1 Active/Standby Switchover Success Alarm ................................... 8-12
8.5.2 Active/Standby Switchover Failure Alarm ...................................... 8-13
8.5.3 Active/Standby Board Software Versions Inconsistency Alarm ..... 8-14
8.5.4 Active/Standby Board BIOS, CPLD Versions Inconsistency ......... 8-14
8.5.5 Alarm of System Resetting upon Abnormal Switchover ................ 8-14
8.5.6 Alarm of Communication between Active and Standby Boards ..... 8-15
8.5.7 Active/Standby Board MAC Inconsistency Alarm .......................... 8-15
8.6 CPU Alarm ............................................................................................. 8-16
8.6.1 CPU Occupation Rate Alarm ......................................................... 8-16
8.6.2 CLI Status Alarm ............................................................................ 8-16
8.6.3 SNMP Alarm .................................................................................. 8-17
8.6.4 Test Task Alarm ............................................................................. 8-17
8.7 Configuration Data Alarm ....................................................................... 8-18
8.7.1 Configuration Data Abnormality Alarm ........................................... 8-18
8.7.2 Main Control Board¡fls Configuration Data Initialization Failure
Alarm ....................................................................................................... 8-18
8.7.3 Active Data Check Failure Alarm ................................................... 8-18
8.8 Board Alarm ........................................................................................... 8-19
8.8.1 Board Fault Alarm .......................................................................... 8-19
8.8.2 TDM Resources Shortage Alarm ................................................... 8-19
8.8.3 Physical and Configured Frame Types Inconsistency Alarm......... 8-20
8.8.4 Main Control Board¡fls Subboard Change Alarm........................... 8-20
8.8.5 Invalid Subboards Combination Alarm ........................................... 8-21
8.8.6 Active/Standby Boards¡fl Subboards Inconsistency Alarm ............ 8-21
8.8.7 Board Replace ............................................................................... 8-21
8.8.8 Hardware Abnormality Alarm ......................................................... 8-22
8.9 Environment Monitoring Alarm ............................................................... 8-22
8.9.1 EMU-program Load Alarm ............................................................. 8-22
8.9.2 Fan Speed-regulating Mode or Opening Mode Changes .............. 8-23
8.9.3 Battery Charging Mode Changes................................................... 8-23
8.9.4 AC Input Changes .......................................................................... 8-23
8.9.5 ESC Power Event Information ....................................................... 8-24
8.9.6 Rectifier Mode Changes ................................................................ 8-24
8.9.7 AC Air Breaker State Changes ...................................................... 8-24
8.9.8 Lightning Protection Unit Breakdown or Damage .......................... 8-25
8.9.9 Battery Power-off Alarm ................................................................. 8-25
8.9.10 Battery Discharge Test Alarm ...................................................... 8-25
8.9.11 EMU Fault .................................................................................... 8-26
8.9.12 Analog Exceeding Threshold ....................................................... 8-26
8.9.13 Actual and Configured Digital Values Inconsistency .................... 8-28
8.9.14 Power Module Fault or Failure to Communicate with EMU ......... 8-28
8.9.15 AC Input Overvoltage/Undervoltage Alarm .................................. 8-29
8.9.16 DC Input Overvoltage/Undervoltage Alarm .................................. 8-30
8.9.17 Battery Power-off Alarm ............................................................... 8-31
8.9.18 Load Power-off ............................................................................. 8-32
8.9.19 Mains Supply Offline .................................................................... 8-32
8.9.20 Batteries Alarm ............................................................................ 8-33
8.9.21 Power-off Alarm ........................................................................... 8-34
8.9.22 Load Fuse Broken Alarm ............................................................. 8-35
8.9.23 AC Module Out of Service Alarm ................................................. 8-36
8.9.24 Battery Charging Over-current Alarm .......................................... 8-37
8.9.25 Battery Charging Under-voltage Alarm ........................................ 8-37
8.9.26 Load Power-off Alarm .................................................................. 8-38
8.9.27 Ac Input Offline Alarm .................................................................. 8-39
8.9.28 ESC Power Fault ......................................................................... 8-39
8.9.29 Rectifier Fault ............................................................................... 8-40
8.9.30 DC Module Out of Service Alarm ................................................. 8-40
8.9.31 Digital Values Abnormal Alarm .................................................... 8-41
8.9.32 Digital Parameter User-defined Alarm ......................................... 8-51
8.9.33 Analog Abnormal Alarm ............................................................... 8-65
8.9.34 Analog User-defined Alarm .......................................................... 8-67
8.10 ADSL/ADSL2+ Alarm ........................................................................... 8-75
8.10.1 ADSL/ADSL2+ Port Activation Alarm .......................................... 8-75
8.10.2 ADSL/ADSL2+ Port Performance Statistics Reaching
Threshold Alarm ...................................................................................... 8-76
8.10.3 ADSL/ADSL2+ Chipset Alarm ..................................................... 8-76
8.10.4 ADSL/ADSL2+ ATU-R Power-off Alarm ...................................... 8-77
8.10.5 ADSL/ADSL2+ Line Signal Loss Alarm ....................................... 8-77
8.10.6 ADSL/ADSL2+ Link Loss Alarm .................................................. 8-77
8.11 SHDSL Alarm ....................................................................................... 8-78
8.11.1 SHDSL Port Activation ................................................................. 8-78
8.11.2 SHDSL Port Fault ........................................................................ 8-78
8.11.3 G.SHDSL CO SNR Overflow ....................................................... 8-79
8.11.4 G.SHDSL CO Loop Attenuation Overflow ................................... 8-79
8.11.5 G.SHDSL CO Errored Seconds Overflow.................................... 8-80
8.11.6 G.SHDSL CO Severely Errored Seconds Overflow..................... 8-80
8.11.7 G.SHDSL CO CRC Errors Overflow ............................................ 8-80
8.11.8 G.SHDSL CO Loss of Synchronization Word Overflow ............... 8-81
8.11.9 G.SHDSL CO Unavailable Seconds Overflow ............................. 8-81
8.11.10 SHDSL STU-R Alarm ................................................................. 8-81
8.12 Service and Function Alarm ................................................................. 8-82
8.12.1 MAC Addresses Conflict Alarm .................................................... 8-82
8.12.2 ISU Uplink-port Failure Alarm ...................................................... 8-82
8.12.3 Device Communication Alarm...................................................... 8-83
8.12.4 VLAN L3 Interface Alarm ............................................................. 8-83
8.12.5 Bandwidth CAC Alarm ................................................................. 8-84
8.13 L2 Protocol Function Alarm .................................................................. 8-84
8.13.1 RSTP Protocol Alarm ................................................................... 8-84
8.13.2 XPoA Access Function Alarm ...................................................... 8-85
8.14 Clock Alarm .......................................................................................... 8-86
8.14.1 SDH/TDM System Clock Source Switch ...................................... 8-86
8.14.2 Clock SDH/TDM Source Locking Failure ..................................... 8-86
8.14.3 Clock SDH/TDM Resource Locking Recovered .......................... 8-87
8.14.4 Clock Source Loss ....................................................................... 8-87
8.14.5 Clock Subboard Communication Abnormality ............................. 8-88
8.14.6 Clock Subboard Communication Abnormality ............................. 8-89
8.14.7 Active/Standby Boards¡fl Clock Subboard Inconsistency ............ 8-89
Chapter 9 Guide to Routine Equipment Maintenance .................................. 9-1
9.1 Introduction to Equipment Maintenance ................................................. 9-1
9.1.1 Requirements on Equipment Maintenance .................................... 9-1
9.1.2 Equipment Maintenance Methods ................................................. 9-2
9.1.3 Equipment Maintenance Forms ..................................................... 9-3
9.2 Guide to Daily Equipment Maintenance ................................................. 9-4
9.2.1 Guide to Daily Maintenance of the Main Control System .............. 9-4
9.2.2 Guide to Daily Maintenance of the Alarm System ......................... 9-5
9.2.3 Guide to Daily Maintenance of xDSL Services .............................. 9-5
9.2.4 Guide to Daily Maintenance of Ethernet Services ......................... 9-6
9.2.5 Guide to Daily Maintenance of VLAN Services.............................. 9-7
9.2.6 Guide to Daily Maintenance of the Running Environment ............. 9-8
9.3 Guide to Monthly Equipment Maintenance ............................................ 9-8
9.3.1 Guide to Monthly Maintenance of the Main Control System .......... 9-8
9.3.2 Guide to Monthly Maintenance of the Running Environment......... 9-9
9.3.3 Guide to Monthly Maintenance of the Electromechanical
System .................................................................................................... 9-9
9.4 Guide to Quarterly Equipment Maintenance .......................................... 9-10
9.4.1 Guide to Quarterly Maintenance of the Main Control System ........ 9-10
9.4.2 Guide to Quarterly Maintenance of the Electromechanical
System .................................................................................................... 9-11
9.4.3 Guide to Quarterly Maintenance of the Grounding System ........... 9-12
9.5 Guide to Yearly Equipment Maintenance ............................................... 9-13
9.5.1 Guide to Yearly Maintenance of the Main Control System ............ 9-13
9.5.2 Guide to Yearly Maintenance of the Grounding System ................ 9-13
Appendix A List of Fault Information to Be Collected ................................. A-1
A.1 Basic Information ................................................................................... A-1
A.1.1 Information Necessary to Be Collected ......................................... A-1
A.1.2 Information Collected According to Fault Causes ......................... A-1
A.2 ADSL Related Information ..................................................................... A-2
A.3 SHDSL Related Information ................................................................... A-2
A.4 Multicast Related Information ................................................................ A-3
A.5 VLAN Related Information ..................................................................... A-3
A.6 QinQ Related Information ...................................................................... A-3
A.7 Stacking VLAN Related Information ...................................................... A-4
A.8 RSTP Related Information ..................................................................... A-4
A.9 ARP Related Information ....................................................................... A-4
A.10 QoS/ACL Related Information ............................................................. A-5
A.11 Environment Monitoring Related Information....................................... A-5
A.12 PPPoA Related Information ................................................................. A-5
A.13 IPoA Related Information ..................................................................... A-5
A.14 PITP V Mode Related Information ....................................................... A-6
A.15 PITP P Mode Related Information ....................................................... A-6
A.16 DHCP Relay Related Information ........................................................ A-6
Appendix B Frequently Used Forms for Routine Maintenance and
Troubleshooting .............................................................................................. B-1
B.1 Frequently Used Forms for Routine Maintenance ................................. B-1
B.1.1 Log ................................................................................................. B-1
B.1.2 Monthly Maintenance Record Form .............................................. B-5
B.1.3 Quarterly Maintenance Record Form ............................................ B-6
B.1.4 Yearly Maintenance Record Form ................................................. B-8
B.1.5 Board Change Record ................................................................... B-8
B.1.6 Office Data Modification Record .................................................... B-9
B.2 Frequently Used Forms for Troubleshooting ......................................... B-10
B.2.1 Routine Unexpected Fault Handling Record ................................. B-10
B.2.2 Emergency Equipment Maintenance Notification .......................... B-11
Appendix C Acronyms and Abbreviations .................................................... C-1
Index .................................................................................................................
HUAWEI
V300R001
BOM 31033991
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Website: http://www.huawei.com
Email: support@huawei.com
Trademarks
All other trademarks and trade names mentioned in this manual are the property of
their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents,
but all statements, information, and recommendations in this manual do not
constitute the warranty of any kind, express or implied.
Release Notes
Related Manuals
The following user documents are shipped together with the MA5600.
Manual Content
SmartAX MA5600 Multi-service It introduces electromagnetic compatibility
Access Module Compliance (EMC) and other safety standards and
and Safety Manual information about the MA5600. It also provides
general safety guidelines for handling, installing
and operating the MA5600.
SmartAX MA5600/MA5603
It guides you to configure the system parameters
Multi-service Access Module
and typical applications of the MA5600/MA5603.
Operation Manual
SmartAX MA5600 Multi-service It guides you to install the MA5600, including the
Access Module Installation installation of the cables, power system and
Manual various boards.
It provides all commands available in the
SmartAX MA5600/MA5603 MA5600/MA5603, as well as the usage of the
Multi-service Access Module command and examples. The Command Manual
Command Help is provided only in the documentation CD-ROM
that is shipped with the MA5600/MA5603.
SmartAX MA5600/MA5603
It guides you to analyze and handle some faults
Multi-service Access Module
that frequently occur on the MA5600/MA5603.
Troubleshooting Manual
SmartAX MA5600/MA5603
It introduces the frames, boards, and cables of
Multi-service Access Module
the MA5600/MA5603.
Hardware Description Manual
Manual Content
SmartAX MA5603 Multi-service It introduces electromagnetic compatibility
Access Module Compliance (EMC) and other safety standards and
and Safety Manual information about the MA5603. It also provides
general safety guidelines for handling, installing
and operating the MA5603.
SmartAX MA5603 Multi-service It guides you to install the MA5603, including the
Access Module Installation installation of the cables, power system and
Manual various boards.
It provides all commands available in the
SmartAX MA5600/MA5603 MA5600/MA5603, as well as the usage of the
Multi-service Access Module command and examples. The Command Manual
Command Help is provided only in the documentation CD-ROM
that is shipped with the MA5600/MA5603 device.
SmartAX MA5600/MA5603
It guides you to analyze and handle some
Multi-service Access Module
frequent faults.
Troubleshooting Manual
SmartAX MA5600/MA5603
It introduces MA5600/MA5603 frame, boards,
Multi-service Access Module
and cables.
Hardware Description Manual
The SmartAX MA5600 Multi-service Access Module (MA5600) and the SmartAX
MA5600 Multi-service Access Module (MA5603) are digital subscriber line access
multiplexer (DSLAMs) developed by HUAWEI to provide ADSL2+, SHDSL, and LAN
broadband access services.
z The MA5600 is put into a cabinet. A service frame of the MA5600 provides 16
slots. Slots 7 and 8 are for the main control boards, and slots 0–6 and 9–15 are
for the service boards. Slots 14 and 15 are also for the ISU boards.
z The MA5603 is put into a chassis, providing seven slots. Slot 7 is for the main
control board, and slots 1–6 are for the service boards.
Organization
This manual introduces the general troubleshooting process, and then details how to
locate and handle some faults that frequently occur on the MA5600/MA5603.
Chapter 8 Analyzing and Handling Alarms introduces the alarms of the MA5600
and how to handle these alarms.
Appendix introduces the list of fault information to be collected, the frequently used
forms for routine maintenance and troubleshooting, as well as acronyms and
abbreviations concerned with this manual.
Conventions
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Convention Description
Boldface The keywords of a command line are in Boldface.
Convention Description
IV. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Table of Contents
i
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
ii
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
4.4.6 Frequent Internet Surfing Interruptions Caused by Wrong Wiring of SPL board.. 4-15
4.4.7 Failure to Activate ATU-R Caused by Wrong Wiring of SPL Board...................... 4-15
4.4.8 Noise to Telephone Caused by High Frequency Interfering Sources................... 4-16
4.4.9 Failure to Display Caller ID on the ADSL User’s Telephone ................................ 4-16
4.4.10 Noise to the Telephone During a Phone Call Caused by Wrong Wiring on MDF4-17
4.4.11 Faults Caused by Incorrect Settings of ADSL Port Parameters ......................... 4-18
4.4.12 Low Internet Access Rate Caused by Virus-affected PC ................................... 4-21
4.4.13 Success in PPPoE Dialup but Failure in Internet Access ................................... 4-22
4.4.14 Failure to Pass Authentication with Correct PPPoE Username and Password.. 4-22
4.4.15 Failure in Internet Access Caused by DNS Faults.............................................. 4-23
4.4.16 Relatively Long Delays for Some Packets in Pinging the Gateway.................... 4-24
4.4.17 Loss of Packets and Low Internet Access Rates Caused by Wrong Connection of
Network Cable for HUB .................................................................................................. 4-24
4.4.18 Failure to Log in to the ADSL Modem Through Internet Explorer (IE)................ 4-25
4.4.19 Frequent Service Interruptions Caused to the User with a Stationary IP Address4-26
4.4.20 Negative Downstream Channel SNR Margin...................................................... 4-27
iii
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
iv
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
v
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
vi
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
vii
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Table of Contents
viii
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
Chapter 1 Overview
This chapter introduces the overall information about troubleshooting the MA5600.
This chapter contains the following.
Section… Describes…
1.1 Scope of The scope of faults in which the troubleshooting
Troubleshooting methods are provided
The background knowledge and operation skill to be
1.2 Knowledge and Skill
possessed by the troubleshooting personnel
1.4 Common Common methods that are used for troubleshooting the
Troubleshooting Methods MA5600
1-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
In terms of the basic knowledge about the telecom networks, you shall:
z Possess the knowledge about the computer network such as the ATM, the
Ethernet, and the TCP/IP.
z Understand the copper – wire access technologies such as the ADSL/ADSL2+,
and the SHDSL.
z Possess the knowledge about multicast service.
In terms of the knowledge about the service functions and networking of the MA5600,
you shall:
z Understand the practical networking and service configuration of the MA5600.
z Be familiar with the MA5600 hardware structure and specifications.
z Be familiar with the functions and positions of the boards on the MA5600.
z Be familiar with the devices interoperating with the MA5600 in the network.
z Be familiar with the protocols and signaling types used between the MA5600 and
the interoperating devices.
In terms of the knowledge about the operation and maintenance of the MA5600, you
shall:
z Understand explicitly which operations may completely or partially interrupt the
service.
z Understand explicitly which operations may cause damage to the MA5600.
z Understand explicitly which operations may cause customer complaint.
z Understand explicitly which emergency or backup measures are available.
In terms of the skills to use the troubleshooting tools and meters, you shall be able to
use:
z The Multimeter
1-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
The general procedure for troubleshooting the MA5600 contains the following four
steps:
z Collecting the information
z Analyzing the fault
z Locating the fault
z Eliminating the fault
Figure 1-1 shows the general procedure for troubleshooting the MA5600.
1-3
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
Start
N
The fault persists?
End
I. Source of information
1-4
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
As the MA5600 is used in more and more complicated topologies, the above
information sources are often not enough to directly indicate a fault. For this reason, it is
important that the maintenance person of the MA5600 collects the first hand
information about a fault, in order to shorten the troubleshooting time.
II. Suggestions
z Make sure you obtain enough information before handling the faults, especially
the critical faults.
z When you are dealing with fault report or claims, ask questions to obtain more
information about the fault.
z Keep good contact with related offices and sectors such as the transmission
sector and interoperating offices to exchange information and seek help.
z Keep yourself familiar with the working principle of the MA5600, as well as related
protocols.
Analyzing a fault means to determine the scope and category of the fault.
The first thing is to find out whether the fault occurs to all or some of the subscribers.
If the fault occurs to all the subscribers, find out whether the fault occurs to subscribers
of other devices that share the same upstream device with the MA5600.
If the fault occurs to part of the subscribers, find out:
z Service type of the subscribers, and whether the same fault occurs to subscribers
of other service types
z Whether the subscribers are connected to the same board as subscribers with
normal services.
z The ports/boards on the MA5600 that connect to the subscribers who claim the
fault.
Fault categories are classified according to the service categories of the MA5600.
By judging the fault category, you can determine which method to be used for analyzing
and locating the fault.
The reason that causes a fault on the MA5600 may be complex. But in most cases, a
fault is caused by a single reason. To locate a fault is to find out such a single reason
from various “possibilities”.
1-5
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
To locate a fault quickly helps you to enhance the efficiency in troubleshooting the
MA5600. Locating a fault accurately also helps you to avoid worsening of the fault.
1.4 Common Troubleshooting Methods lists some methods used for analyzing and
locating a fault.
After a fault is located, you can eliminate it following proper procedure and using proper
methods, such as checking the line, replacing the faulty parts, modifying the
configuration data, or resetting the board.
Note:
z Make detailed record of every step of operation you perform during the
troubleshooting.
z If technical support from Huawei is required, present the record to the support
personnel of Huawei to reduce the troubleshooting time.
z Contact Huawei technical support center if you find difficulty in eliminating the fault.
This section introduces some common methods used to troubleshoot the MA5600.
In troubleshooting, the first and most important thing is to judge whether the fault is on
the MA5600 device itself, so as to avoid the waste of time and resource.
To improve the efficiency of troubleshooting, you shall first check the connection of
external cables and running status of the indicators, and then check the overall running
status of the system at the console, and finally check the running status of each
module.
Table 1-2 lists the methods for locating the fault step by step.
1-6
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
The MA5600 alarm information greatly helps you to analyze and locate a fault.
If a fault occurs, the MA5600 reports alarms. The alarms are displayed on the
maintenance terminal to indicate the phenomena of the fault, possible reasons of the
fault, and suggested handling procedure. The alarm information covers all the aspects
related to the running of the MA5600, such as the hardware, the link, the fiber, the
service and the CPU occupation ratio.
The alarm information helps you to directly pinpoint the location and the reason of a
fault. You can use other analysis methods together to locate the fault.
Performance analysis is to find out the fault by querying the performance statistics
provided by the MA5600.
It is very useful to query the performance statistics when you locate various types of
faults. Before you query the statistics, make sure you know about the fault category, so
that you can query related statistics.
To use the performance analysis method well, you shall be familiar with the system
structure and operation mechanism of the MA5600. You shall also be familiar with the
type of statistics provides by the MA5600 and how to query the statistics.
Exclusive method is used when the fault may be caused by more than one reason.
Using this method, you can analyze and get rid of the false reasons, and find out the
real reason of the fault.
To use the exclusive method well, you shall be very familiar with the system structure
and the working principle of the MA5600. The loopback test and the meter test are often
used together for the exclusive method.
Instruments and meters play a key role in the troubleshooting. They can directly
indicate the fault by means of visual and quantitative data.
The following instruments and meters are usually used for troubleshooting.
1-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
z Multimeter
z Optical power meter
z Oscillometer
z Liner tester
z Signaling trace meter
By comparing the measured value with the normal parameter, you can find out the
possible causes of a fault.
1.4.6 Comparison
In case of a single-point fault, you can find it out by comparing the faulty component
with a normal one.
1.4.7 Interchange
If fault remains after you replace the doubted part with a spare one, you can
interchange the doubted part, such as a board or a fiber, with a same part that is
running normally. You may locate the position or the scope of the fault by comparing the
status before and after the interchange.
Interchange is often used when it is difficult to find out the reason of the fault, or the fault
seems to be caused by complex reasons.
Caution:
z Interchange is risky. If you interchange a normal board that is actually normal in the
shelf with a short-circuited board, you may damage the shelf. Therefore, be cautious
to use the interchange method so as to avoid another fault.
z To interchange between two boards, make sure that a good board is used to
interchange with the doubted board.
Incorrect configuration data will cause system faults. By analyzing the configuration
data, you can locate the fault easily, especially the fault that occurs in the new
deployment.
Protocol analysis is to trace the signaling and capture the packets to analyze the fault.
Protocol analysis is often used when the MA5600 is not interoperating well with the
uplink device.
1-8
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 1 Overview
To use the protocol analysis method, you must be very familiar with related protocols,
and be clear about the exchange process of signaling.
1-9
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
This chapter introduces some operations that are commonly used in troubleshooting
the MA5600. Operations in this chapter may often be referred in other chapters of this
document.
If you are familiar with the operations in this chapter, you can skip to other chapters.
This chapter contains the following.
Section… Describes…
The hardware loopback and the software loopback that
2.1 Loopback are supported by the MA5600, as well as how to locate
the faults using the loopback methods
2.2 Replacing the How to replace the various boards and optical modules of
Boards the MA5600
2.3 Measuring the
How to measure the optical power
Optical Power
2.1 Loopback
2.1.1 Overview
2-1
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
I. Description
The fiber loopback is to directly connect the Tx and Rx ports on the optical module for
the test.
The fiber loopback helps you to judge whether the status of the local optical port, the
peer optical port, or the fiber is normal. This method is used when all the services on
the optical port are interrupted, or when the optical port reports an alarm.
Figure 2-1shows the fiber loopback.
Main 1 2 3 4
control / O O
D D
interface
F F
board
Fiber loopback is carried out on the failure side segment by segment from the local end
to the peer end, as shown in the above figure. If the MA5600 optical port recovers after
the loopback on one of the segments, it indicates that the fiber and the optical
components in this segment are normal. Otherwise, it indicates that the fault occurs in
this segment. To eliminate the fault, you can check the fiber or replace the components.
Fiber loopback helps you to quickly locate the faulty segment.
II. Precautions
Services carried on the optical ports are interrupted when you implement the fiber
loopback.
z If the optical ports work in the active/standby mode, switch the services to normal
optical ports before the loopback.
z If the optical ports work in the load sharing mode, select a time when the traffic
load on the fiber is small, in order to avoid congestion.
III. Prerequisites
2-2
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
IV. Procedure
1) Use fibers to connect the MA5600 optical ports for the loopback test, as shown in
Figure 2-2.
Tx Tx
Rx Rx
I. Description
The E1 link loopback is to directly connect the Tx and Rx ports on the E1 service board
for the test.
When locating an IMA E1 fault in the physical layer, you can:
z Perform loopback for a single E1 link.
z Perform loopback for all the E1 links involved in IMA E1.
The E1 link loopback helps you in troubleshooting the following faults:
z E1 port disconnected
z E1 link cross-connected
z E1 link alarms
Figure 2-3 shows the E1 link loopback.
1 2 3 4
主控板/ D D
Interface
接口板 D D
board
F F
MA5600
UA5000 Opposite device
对端设备
E1 link loopback is carried out on the failure side segment by segment from the local
end to the peer end, as shown in parts n, o, p, and q in the above figure.
2-3
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
If the MA5600 E1 port recovers after the loopback on one of the segments, it indicates
that the line and the components in this segment are normal. Otherwise, it indicates
that the fault occurs in this segment. To eliminate the fault, you can check the line error
bit or replace the components.
E1 link loopback helps you to quickly locate the faulty segment.
II. Precaution
Services carried on the E1 ports are interrupted when you implement the E1 link
loopback.
If the E1 ports work in the active/standby mode, switch the services to normal E1 ports
before the loopback.
If the E1 ports work in the load sharing mode, select a time when the traffic load on the
link is small, in order to avoid congestion.
III. Prerequisites
IV. Procedure
1) Use the E1 loopback cable to connect the MA5600 E1 ports for the loopback test.
2) Check whether the recovery alarm of the E1 port is reported.
I. Remote loopback
The remote loopback is to directly send out from the Tx port the signals that are
received at the Rx port, without any processing on the signals by the board. This helps
you to judge whether the port processing module is normal.
Figure 2-4 shows the remote loopback.
2-4
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
Plane module
Port module
Remote Hardware
loopback loopback
The local loopback is to directly send the signals from the plane back to the plane at the
port processing module of the board. The local loopback is often used to check the
internal processing module of the board.
Figure 2-5 shows the local loopback.
Plane module
Port module
Local Hardware
loopback loopback
2-5
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
AFE Hybrid
1 2 3
Logic Chipset
ADSL board
You can run the command loopback to set software loopback for different boards in
different modes:
z In SHDSL mode, run the command loopback to enable the local loopback of the
SHDSL port:
MA5600(config-if-shl-0/4)#loopback 0 local
z In ADSL mode, run the command loopback to enable the UTOPIA loopback of the
ADSL/ADSL2+ port:
MA5600(config-if-adsl-0/4)#loopback 0 utopia
z In E3 mode, run the command loopback to enable the remote loopback of the E3
port:
MA5600(config-if-aiu-0/6.e3)#loopback 0 remote
z In optical port mode, run the command loopback to enable the remote loopback of
the ATM STM-1 port:
MA5600(config-if-aiu-0/6.optic)#loopback 0 remote
When some new functions are to be added to the board or other components, or the
capacity of an office is to be expanded, the hardware may be upgraded. In this case:
z Perform such operations as unplugging and inserting the boards or other
components, and resume their operations.
z Reposition some service boards.
2-6
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
To remove the faults and maintain the equipment, the maintenance personnel can
query the alarm information in the fault management system and the equipment
information in the maintenance system.
If a board is faulty, directly replace the board. If other components and parts are faulty,
replace these components and parts.
According to the guide described in this section, the maintenance personnel can
manage the board software, unplug and insert the board, and replace the board.
After locating the fault of a board, and replacing the board, keep a record for the board,
pack it, and then send it for repairs.
2.2.2 Precautions
I. Preparations
Before replacing a board, perform the required pre-operations to guarantee that the
device can work normally during troubleshooting and replacement, or perform some
pre-operations when the service is interrupted to guarantee the normal operation of the
device.
The pre-operations include:
z Checking and recording the board type, and ensuring that the boards before and
after the replacement are compatible.
z Saving the system configuration data and recording the board configuration.
z Switching over between the board to be replaced and the board to replace the
faulty one, so as to enable the latter to be in standby status.
z Preparing the new board and the operation tools.
At this stage, pay attention to the following points:
z Make sure that the specifications of the subboards on the boards before and after
the replacement are consistent.
z Make sure that the software versions of the boards before and after the
replacement are consistent.
z Check whether the labels for the cables from the front panels of the boards are
intact. If not, relabel the cables.
z Set the DIP switches and jumpers correctly.
2-7
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
II. Replacement
According to the guide to replacing a board, unplug and insert the hardware, check and
set the DIP switches and jumpers.
Perform all the operations in a standard manner to avoid any damages to the board.
The operations involved include:
z Wearing an Electrostatic Discharge (ESD) preventive wrist strap.
z Unplugging and inserting the board correctly.
At this stage, pay attention to the following points:
z Unplug or insert the board along the slot, neither oblique nor deviated from the
slot.
z Insert the board to the slot tight; otherwise, the interference may be caused to the
device during the operations or the board may be damaged accordingly.
z If there are cables from the front panel of the board, pull other the cable, and then
plug them into the front panel after the board is replaced.
z Check and record the settings of the jumpers and DIP switches on the board.
z Avoid short circuits caused by metal during the operations, for example, by an
operation tool that is placed improperly, or by a screw that is dropped into the
frame.
z When installing or maintaining the optical board or fiber, keep your eyes away from
and do not directly view the optical port or the fiber connector.
Check whether the new board and the service of the board are normal. Label the faulty
board, pack it, and then send it for repairs.
z The operations involved include:
z Checking the status of the LEDs on the board, and making sure the board is
working normally.
z Querying the related alarms and performance events, and making sure there is no
abnormality alarm.
z Putting the replaced board into an antistatic bag, and labeling the bag with the
board name and the fault description.
At this stage, pay attention to the following points:
z Make sure the cable connection is normal.
z When replacing the control board, synchronize the data of the active control
board.
z For the board working in active/standby mode, check whether the active/standby
switchover is normal.
z For the service board, check whether the service of the board has recovered.
2-8
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
I. General principles
To prevent ESD of the human body from damaging the ESD-sensitive parts and
components, when replacing the board, take ESD-protective measures to guarantee
no damage to the device during the replacement.
The ESD-protective measures are as follows:
z Ground the equipment correctly according to the grounding requirements.
z Always wear the ESD wrist strap to prevent the device from being damaged by
ESD.
z Keep the ESD wrist strap work in normal conditions.
Its resistance shall range from 0.75 MΩ to 10 MΩ.
Its service life is usually two years.
Replace the wrist strap when the resistance is not within the said range.
z Keep the clothes away from the board because the ESD wrist strap cannot defend
the board against the static electricity caused by the clothes' touching the board.
z Use a simple ESD-protective pad and wear the ESD wrist strap to replace the
board software or chip. Use the ESD-protective tweezers and chip extraction tools
to replace chips. Do not touch chips, circuits, or pins with your bare hands.
z Keep the boards and other ESD sensitive parts to be installed in the antistatic bags.
Place the temporarily removed boards and components on the ESD-protective
pad or other effective ESD-protective materials. Do not use non-antistatic
materials such as white foams, common plastic bags, or paper bags to pack the
boards or let them touch the boards.
z Wear the ESD wrist strap when operating the ports of the board because they are
also ESD-sensitive. Discharge the static electricity of cables and protective
sleeves before connecting them to the ports.
z Put the removed board into the ESD-protective bag or box.
z Reserve some materials for board package (such as ESD-protective boxes and
bags) in the room for future use.
Pay attention to the following points when wearing the ESD wrist strap:
2-9
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
z Keep good contact between the wrist strap and the wrist skin.
z Do not use any oil such as skin-protective oil or frostbite-preventive oil in the wrist
skin.
z Connect the grounding strap to the ESD grounding jack on the cabinet, as shown
in Figure 2-7.
z Check the ESD wrist strap before using it, and do not use any ESD wrist strap of
poor quality.
Use a multimeter to test the resistance of the inner interface of the wrist strap to the
strap buckle, as shown in Figure 2-8.
2-10
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
Multimeter(x10k Ω)
Strap buckle
Figure 2-8 Testing the resistance of the inner interface of the wrist strap to the strap
buckle
Use a multimeter to test resistance of the grounding strap, as shown in Figure 2-9.
2-11
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
I. Recommended Tools
II. Preparations
III. Procedure
2-12
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
Caution:
After the control board leaves the board track, you need still pull the control board out of
the service shelf along the previous direction, so as to avoid the control board collides
with components on other boards.
4) Hold the ejector levers with your hands and pull out the control board along the
board track, as shown in Figure 2-10p.
5) Pull outward the ejector levers on the front panel of the control board.
6) Hold the ejector levers with your hands and insert the board gently along the board
track until the ejector levers are clamped to the top and bottom beams of the board
cage, as shown in Figure 2-10 q.
7) Press the ejector levers inwards to seat the board in the connector on the plane.
Now the ejector levers shall be parallel with the front panel, as shown in
Figure 2-10 r.
8) Tighten the screws clockwise on the front panel by using a cross screwdriver, as
shown in Figure 2-10 s.
9) Connect cables to the new control board.
2-13
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
IV. Illustration
1 2 3
4 5 6
V. Test-based Examination
2-14
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
3) Run the command duplicate to synchronize the active and standby databases.
4) Run the command system switch-over to switch over between the active and
standby boards.
5) Query the alarms and performance events in the system, and confirm there are no
new alarms or performance events. Check whether the service is normal. If yes, it
indicates that the switchover succeeds.
6) Put the removed board in an ESD-protective bag and label the bag with the board
name and fault description.
I. Recommended Tools
II. Preparations
III. Procedure
Caution:
After the service board leaves the board track, you need still pull the service board out
of the service shelf along the previous direction, so as to avoid the service board
collides with components on other boards.
5) Pull outward the ejector levers on the front panel of the new service board.
2-15
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
6) Hold the ejector levers with your hands and insert the board gently along the board
track until the ejector levers are clamped to the top and bottom beams of the board
cage, as shown in Figure 2-11 q.
7) Press the ejector levers inwards to seat the board in the connector on the plane.
Now the ejector levers shall be parallel with the front panel, as shown in
Figure 2-11 r.
8) Tighten the screws clockwise on the front panel by using a cross screwdriver, as
shown in Figure 2-11 s.
9) Reconnect the cable, if any, on the front panel of the board.
2-16
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
IV. Illustration
1 2 3
4 5 6
V. Test-based Examination
2-17
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
3) Query the alarms and performance events in the system, and confirm there are no
new alarms or performance events. Check whether the service is normal. If yes, it
indicates that the switchover succeeds.
4) Put the removed board in an ESD-protective bag and label the bag with the board
name and fault description.
I. Recommended Tools
II. Preparations
Note:
To replace a subboard on the control board, make preparations as described in “2.2.4
Replacing a Control Board”.
2) Take a new subboard out of the ESD-protective box and check whether the
subboard is in good conditions. Do not touch the surface of the printed board.
3) Set the DIP switches and jumpers of the board correctly.
III. Procedure
2-18
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
7) Insert the board to the frame, and reconnect the cable on the front panel of the
board.
IV. Illustration
1 2
3 4
5 6
V. Test-based Examination
2-19
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
I. Recommended Tools
II. Procedure
Note:
When the module clicks, it means the module is seated correctly in the optical port.
III. Illustration
2-20
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
1 2
3 4
When error code occurs at the optical port or the port is disconnected, you can
measure the optical power at the port. This helps you to judge whether the fiber or the
optical transmitter is normal.
The optical power is measured on the receiving and transmitting ports.
To measure the optical power, use the optical power meter.
2-21
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
I. Description
This operation is to measure the optical power at the receive port on the MA5600 in
order to check the status of the fiber connection or the peer end.
II. Precautions
III. Prerequisite
IV. Procedure
1) Set the optical power meter to work at the wavelength of the signal to be
measured.
2) Remove the patch cord from the Rx port on the MA5600, and connect the cord to
the optical power meter, as shown in Figure 2-14.
Tx Tx
ODF ODF
Rx Rx
Interface/main
control board Optical port
3) Record the result after the reading on the optical power meter is stabilized.
2-22
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
I. Description
This operation is to measure the optical power at the transmit port of the MA5600 in
order to check the status of the local transmitting module.
II. Precautions
III. Prerequisite
IV. Procedure
1) Set the optical power meter to work at the wavelength of the signal to be
measured.
2) Remove the fiber from the Tx port on the MA5600.
3) Connect one end of the patch cord to the Tx port on the MA5600, and the other
end to the optical power meter, as shown in Figure 2-15.
Tx
Rx
Interface/ main
Optical power meter control board
MA5600
2-23
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
4) Record the result after the reading on the optical power meter is stabilized.
Table 2-2 lists the reference criteria for the STM-1 optical port.
Maximum
–3 dBm 1 dBm –4 dBm
transmitting power
Transmitter
Minimum
–11.5 dBm –4 dBm –9.5 dBm
transmitting power
Maximum receiving
–3 dBm –3 dBm 0 dBm
power
Receiver
Minimum receiving
–20 dBm –24 dBm –17 dBm
power
2-24
Troubleshooting Manual Chapter 2 Common Troubleshooting
SmartAX MA5600/MA5603 Multi-service Access Module Operations
2-25
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
To handle a fault, start from the physical layer. This chapter introduces how to
troubleshoot physical connections of the MA5600 and analyzes some related cases,
including:
z Troubleshooting xDSL Lines, on Page 3-1
z Troubleshooting Ethernet Ports, on Page 3-7
3.1.1 Overview
Digital subscriber line (DSL) a technology to transmit data, voice, and video traffic with
high bandwidth over the existing copper twisted pair cables (POTS lines) between the
equipment at the office end and the Customer Premises Equipment (CPE).
xDSL implements channels multiplexing by dividing spectrums of the twisted pair cable.
Voice and data traffic is separated by the splitters. A network topology is composed of
the Digital Subscriber Line Access Multiplexer (DSLAM) at the office end and the CPE
at the user end.
3-1
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
Start
End
--------------------------------------------------------
When the fault occurs at the xDSL port side, run the command display line operation
to query the xDSL line operation parameters. Especially, query:
z The line’s signal to noise ratio (SNR) margin to judge the quality of the current line
connection.
3-2
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
In general, the activated SNR margin free from rate restriction shall be near to the
target SNR margin.
z Whether the line attenuation is normal.
A high attenuation rate within a short distance indicates a line problem. In general,
the attenuation per kilometer is 10 dB for the downstream line, and is 6 dB for the
upstream line.
For different xDSL technologies, the line lengths are different. If the line is too long, the
xDSL transmission rate is decreased fast, causing failure to DSL services.
Generally:
z The ADSL line length is less than 5 km.
z The ADSL2+ line length is less than 6.5 km.
z The SHDSL line length is less than 6 km.
3-3
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
Bridge taps on external lines may cause strong reflection in signal transmission and
thus affect the quality of signals. In principle, do not use subscriber lines with bridge
taps to transmit xDSL signals.
According to the current troubleshooting statistics, 80% of the xDSL line faults are
caused by poor quality of service cables and loose contact of connectors.
3-4
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
xDSL Modem
Modem
Phone
Telephone line Line
Audio
Modem
[Fault description]
When a phone call comes or the user presses the telephone set, the xDSL Modem is
deactivated.
[Fault analysis]
Why the Modem is deactivated is related to Modem faults and line faults.
In this case, the ringing or pressing affects the Modem, resulting in the fault. From the
fault, it can be seen that the line at the user side is not standard, and must be checked.
[Troubleshooting]
1) Change the Modem at the user side, but the fault still exists. So the fault is
unrelated to the Modem.
2) Disconnect the subscriber line, and simulate effect on the activated Modem by the
telephone set at the MDF in the equipment room. As a result, the Modem is not
deactivated.
3) Duplicate the said simulation at the MDF at the user side. As a result, the Modem
is not deactivated.
4) Check the leading-in box in the user's house, and find that the white one of a pair
of telephone lines is misconnected. This is the cause why the VDSL line is
3-5
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
deactivated from time to time. Connect the misconnected cable again, and then
the fault is removed.
II. Slow Internet surfing and offline caused by bad line conditions
[Fault description]
After the xDSL service is provisioned for an Internet cafe user, the user reports that the
Internet surfing speed is slow and even sometimes the web pages cannot be opened.
Through observation on site, the maintenance personnel find that the rate of
downloading software from a local website by a single computer is only 13 kbit/s. The
rate of downloading software from a website out of the local province is only 6–7 kbit/s.
In addition, the offline phenomenon occurs in the Internet cafe.
[Fault analysis]
The xDSL access services require high-quality lines. So, use twisted pairs as your first
choice, do not use copper core or aluminum core. In actual applications, you can
consider using standard network cables as service cables.
[Troubleshooting]
1) Check the data configuration of the MA5600, such as upstream and downstream
rates, and SNR margin, but find no problem.
2) Check the service cables, and find that the service cables used by this user are
common copper core parallel lines, and the length is about 40 m. Replace the
parallel lines by twisted pairs, and then the Internet surfing speed is boosted
obviously.
[Fault description]
An office provisions VDSL services, but several ports are deactivated frequently.
Sometimes, these ports are deactivated automatically due to line faults once several
hours, or even once an hour. However, the distance between the users connected to
these ports and the office is less than 500 m.
[Fault analysis]
Check the line states of these ports, and find that the SNR of upstream and
downstream channels is not normal, and then deduce that the line connection is not
normal.
[Troubleshooting]
Lay out the wires on the MDF again, and reconnect the telephone lines in the
connection box of the user after replacing the old RJ-45 connector by the new one.
Then, the SNR of upstream and downstream channels returns to normal.
3-6
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
Through the related test, the line connection stability is highly boosted. In 48 hours, only
one offline phenomenon occurs.
[Conclusion]
The upstream/downstream SNR is increased when the distance between the Modem
and the MA5600 is added, but this is not a simple linear relationship.
In this case, the distance between the user and the office is less than 500 m, so the
attenuation must be small. Abnormal SNR indicates that signals are not totally
attenuated on copper wires, but mainly attenuated at connection points. Re-arrange
the line, and then the fault is removed.
[Fault description]
An office provisions xDSL services. A user can access the Internet, but fails to make a
phone call. There is neither feed current nor dialing tone in case of off hook. The xDSL
Internet surfing is not stable, and is deactivated from time to time.
[Fault analysis]
1) Replace the splitter and telephone, but the fault is not removed.
2) Take the phone back to the MDF at the office side for a test.
3) Through the test, it is found that the telephone has feed on the terminal board at
the PSTN side, but it has no feed on the terminal board at the LINE side.
4) Observe the terminal board at the LINE side carefully, and found that the clamping
interface on the terminal board is loosened, and the skin of the jumper is not
peeled.
[Troubleshooting]
Connect the jumper again, and then the phone can be used normally. The xDSL
attenuation is decreased, and the port is rarely deactivated.
3.2.1 Overview
3-7
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
Note:
When an Ethernet port is interconnected with other ports, make sure the port settings
are consistent.
I. Duplex mode
In an Ethernet network, the data link layer provides different media access control
methods for half duplex and full duplex.
z Half duplex
The half duplex transmission mode supports CSMA/CD. The traditional Local Area
Network (LAN) works in half duplex mode, which is very sensitive to the transmission
conflict over the cables.
z Full duplex
The full duplex transmission mode means that different data can be transmitted and
received at the same time without any interference. This mode is widely applied in the
PPP Ethernet and Fast Ethernet.
z Auto negotiation mode
There are many kinds of combinations of Ethernet operation modes. It will be too
complicated to configure all terminal device manually. To handle various operation
modes, the auto negotiation function comes into being.
Through the auto negotiation function, one network device can transfer the working
mode it supports to the opposite party, and can receive the relevant information from
the opposite party. Auto negotiation uses a kind of standard physical layer signal, Fast
Link Pulse (FLP) or Normal Link Pulse (NLP), to transmit the negotiation information,
and sets the devices at both sides to the highest transmission rate they both support to
guarantee highest transmission efficiency.
The auto-negotiated content includes: duplex mode, operating rate, flow control, and
so on. Once the negotiation succeeds, the devices at both sides of the link can
communicate with each other.
II. Rate
3-8
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
To change a port into Media Dependent Interface (MDI), you need to set the network
cable (straight through cable or crossover cable) used for the port. This applies to
FE/GE electrical ports.
In actual settings, the network cable type set must be the same as the actually used
network cable. You can also set the network cable type as auto.
Note:
During data configuration for a port, for auto mode, you can set this mode only when
the rate or duplex mode is auto negotiation.
Start
End
3-9
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
Check the LED of the Ethernet port. If the LED is off, check whether the network cable
or optical fiber is correctly connected.
If a fault occurs when the Ethernet port on the MA5600 is connected to the port at the
peer end, ping the peer port on the MA5600. This is a frequently used method.
You can run the command display port state to display the state of an Ethernet port,
such as duplex mode, port rate, and so on. In this way, you can check whether the port
settings at the both ends match.
You can run the command display interface to display the interface state. This
provides reference for fault diagnosis.
If the state is down, check the states of the service port and the upstream port
connected to this interface.
3-10
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
In SCU board configuration mode, you can run the command display port statistics to
collect statistics of an port.
You can judge whether an interface is normal by displaying its received and transmitted
frames.
3-11
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
Follow the above process, now you can judge whether the Ethernet port on the
MA5600 communicates normally with the port at the peer end, and judge the line
quality according to the time delay of PING packets and the packet loss ratio.
If the packet loss ratio and the time delay are large, or the ports at the both ends cannot
communicate with each other, check whether the physical links are normal. If yes,
change the current port, and then try again.
The MA5600 supports the Ethernet port mirror. That is, the MA5600 can duplicate the
service traffic of a port to another Ethernet port. This helps to locate a fault.
The frequent faults concerning Ethernet ports are related to ports interconnection. So,
generally follow the steps in “3.1.2 Fault Locating Process” to locate these faults.
[Fault description]
In a test of the MA5600, the SCU board of the MA5600 is connected with a PC directly.
Ping the interface on the upper layer router, a serious packets loss (5%) phenomenon
occurs.
[Fault description]
When the settings of the Ethernet port on the MA5600 and the ports on the network
card of the PC do not match, packets loss will occur.
[Troubleshooting]
Set the line rates and line modes of the Ethernet port on the MA5600 and the network
card of the PC the same (both in auto-negotiation, 10 Mbit/s, 100 Mbit/s, half duplex, or
full duplex), the packets loss disappears, and the services return to normal.
II. IP-DSLAM NMS channel failure caused by network ports of the upper layer
switch that are misconnected
[Fault description]
The MA5600 devices of two offices are connected to different ports on the same upper
layer switch through the photoelectric transducers. The networking mode of the
MA5600 is IP-DSLAM. The MA5600 is connected to the network management center
3-12
Troubleshooting Manual Chapter 3 Troubleshooting Physical
SmartAX MA5600/MA5603 Multi-service Acess Module Connections
(NMC) in inband NMS mode. The NMS VLANs are both 63. The two offices can be
managed at the NMC, and the NMSs are normal. The service VLANs are 58 and 59
respectively, and the MA5600 devices are connected to the upper layer equipment
through service VLANs. The two offices' Internet access services fail due to connection
timeout.
[Fault analysis]
1) Check the data configurations of the MA5600, and find no problem.
2) Check the upper layer switch and BRAS data configuration, and find no problem.
3) Ping the gateway, that is, the port of the connected upper layer switch, and then
fail.
4) Connect a PC directly to the port on the upper layer switch to which the MA5600 is
connected, and then the Internet access is normal.
5) Check the upper layer equipment room, and find when the MA5600 devices of two
offices are connected to the same upper layer switch through the photoelectric
transducers, the cable for connecting the upper layer switch and one office's
transducer is connected to another office's transducer.
[Troubleshooting]
Connect the MA5600 and the switch correctly, and then the fault is removed.
3-13
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
Various devices may cause ADSL access faults, such as the upper layer network
equipment, access equipment, subscriber lines, and ADSL Modems. In this case, the
key point for timely troubleshooting is to judge promptly where a fault is located
according to the fault phenomenon.
Asymmetric Digital Subscriber Line (ADSL) is a technology to transmit data over the
existing telephone lines. It features asymmetric upstream and downstream rates, and is
suitable for providing broadband access services. Because the frequencies for ADSL
are different from those for POTS services, ADSL services do not affect POTS
services.
4-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
Figure 4-1 shows the typical reference model of the ADSL/ADSL2+ system.
ATU-C
PDN
ATU-C Splitter Splitter ATU-R T.E
+SM T.E
ATU-C
POTS-C POTS-R T.E
PSTN PHONE
Access point
Where:
z Access point: the convergence point of broadband data and narrowband data.
z ATU-C: ADSL/ADSL2+ Transceiver Unit - Central Office end.
z ATU-R: ADSL/ADSL2+ Transceiver Unit - Remote End.
z Splitter: the filter used to separate high frequency ADSL signals from low
frequency POTS signals.
z PDN: Public Data Network used to connect the ATU-R and various application
terminals.
z SM: service module, completing terminal adaptation (such as STB-TV)
z Vc: the interface of the access point and the network side (SDH or SONET)
z B: the subsidiary data input channel to the SM (such as satellite receiver)
4-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
The MA5600 supports ADSL2+ boards to provide ADSL and ADSL2+ services.
II. Networking
I
IP
P
FE/GE
MA5600
4-3
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
4.2.1 Flowchart
Start
End
Through queries in the network management system (NMS), it can be primarily judged
where a fault is located, such as the upper layer equipment, the MA5600, or the
equipment at the user end.
4-4
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
Start
Fault may occur on the upper Fault may occur on the upper User wrongly uses
layer device, MA5600 or CPE layer device or MA5600 the PC
End
Query and record the model of the user’s Modem and the states of the LEDs on the
Modem, and judge whether the Modem is in fault.
The following takes the SmartAX MT880 series ADSL2+ Modem of Huawei for
example to introduce how to locate an ADSL2+ fault by observing the states of the
LEDs on the ATU-R.
Table 4-3 shows the states of the MT880 Modem and corresponding instructions.
4-5
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
Blinks It indicates that the LAN carries data traffic. This is normal.
1) Ensure you use the right cable from the MT880 to your
PC.
LAN 2) Ensure the connection is secured.
LINK
3) Check if the network interface card (NIC) LED lights up.
Off 4) Ensure your Network Adapter works normally by
examining whether the item of “Networking Adapters” is
labeled with “?” or “!”. If it is, you may delete it and then
click “Refresh” to reinstall. Otherwise, you may try the
NIC in another slot. As a last resort, you have to replace
the NIC.
LAN
Blinks It indicates that the LAN carries data traffic. This is normal.
ACT
Contrast current data with historic records and with the parameters of the neighboring
line parameters to find out the cause for the fault.
z Contrast the subscriber line test data with that tested in the past to see if there is
any change. Data involved mainly includes: Ca-b, Ra-gnd, Rb-gnd, Ca-gnd,
Cb-gnd, and loop resistance.
z Contrast the connection parameters of the port read on the MA5600 with the data
recorded last time. Pay attention to comparison of upstream/downstream channel
attenuation values.
4-6
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
z Contrast the connection parameters with the neighboring lines. The key point is to
see whether the difference between the channel attenuation values is more than 5
dB. If yes, it indicates that the line is in trouble.
Check:
z The MA5600 hardware, including the board states, port states, and system
running states.
z Whether the configuration data is correct, including the traffic profiles, line profiles,
and port rates.
If no fault has been found till now, maybe the upper layer device is faulty. Then, check
the running state and configuration data of the upper layer device. Especially, check
whether the upper layer interface matches the MA5600.
4-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
4.3.2 Success in Making a Phone Call, but Failure to Access the Internet
The faults of this category are complicated. They may be related to all devices in the
whole networks.
When such a fault occurs, the maintenance personnel may find the fault point through
learning the operating state of the equipment at the user end, and through querying the
related information in the NMS.
Procedure 1
Procedure 2
Procedure 3
If the user still cannot access the Internet, it can be judged that the fault may occur on
the equipment at the user end, the upstream port, or the fault is caused by the user's
improper operation. Then, locate and remove the fault according to the following steps.
1) The fault of connection between the user and the ADSL Modem
z Check whether the user's POTS services are normal.
z Check whether the ADSL Modem is started normally. If the ADSL Modem's
power-on startup is abnormal, cut off the power and then restart the Modem.
2) Method for locating the fault for a user with a stationary IP address
If a user uses a stationary IP address, and access the Internet in 1483B or IPoA mode,
Ping the gateway to judge the cause for the Internet access fault.
z If the user can ping the gateway successfully, but still cannot access the Internet, it
can be basically judged that the fault occurs on the upper layer equipment of the
MA5600, the access server, or the router.
z If the user cannot ping the gateway, the fault may occur on the MA5600, the PC
settings, or the ADSL line.
3) Method for locating the fault for a user in PPPoE dialup access mode
z Observe whether the user can reach the PPPoE authentication stage. If the user
can reach the stage, but the authentication fails, or the authentication succeeds
but the user still cannot access the Internet normally, it can be judged that the fault
occurs on the access server.
4-8
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
z If the PPPoE authentication succeeds, the user still cannot visit a website. When
visiting another website, the user still fails. In such a case, the fault occurs on the
access server or the websites.
z If the user fails to start normal PPPoE dialup, it can be judged that the user’s dialup
software is faulty. Re-install the dialup software, and make the PC settings correct.
The key points in PC settings are whether the TCP/IP attribute setting is correct,
whether the dialup account format and password are correct, and whether the
dialup software is installed correctly.
z If the user cannot log in to the access server, the fault may occur on the MA5600,
the PC settings, the ADSL line, and so on.
If the physical connection rate is relatively high, the fault is unrelated to the line
conditions. It may be because that the port capacity of the broadband access
server is not expanded.
If the line is short, but the Internet access rate still cannot reach up to 2 Mbit/s,
query through the NMS the port’s physical connection rate and line attenuation.
2) Check the interleaved depth.
If the physical connection rate reaches 2 Mbit/s or the restricted rate, it indicates
that the line is normal. Then, query the interleaved depth settings. If the
interleaved depth is 64, the FTP file transmission rate can only reach up to 1.5
Mbit/s due to restriction of TCP/IP Protocol.
3) Query the physical connection rate.
Query through the NMS the port’s physical connection rate. If the difference
between the physical connection rate and the file transmission rate is large, but
the physical connection rate is normal, it can be generally judged that the
upstream interface rate encounters bottleneck.
You can check when traffic suppression such as CAR and PVC-based traffic
control is enabled.
4) Check other causes.
4-9
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
In addition, relatively long line, large line noise, or bad quality of service cables
may also cause the fault.
The Internet access is not stable, and the user gets offline from time to time when
surfing the Internet. This fault is generally caused by bad line conditions, relatively long
line, or loose contact of line.
Then, follow the steps below to locate and handle this fault:
1) Judge whether the line is longer than 3 km. If yes, maybe relatively long line
causes the fault. Also, check whether the neighboring ADSL users encounter such
fault.
2) Check whether other devices are installed in front of the Modem. Remove these
devices, if any.
3) Check whether the splitter is installed correctly.
4) Check whether the user is making a phone call or using other household
appliances when the user gets offline.
5) Check whether the connectors of service cables and telephone lines are of good
contact. Check the quality of the service cables.
6) Check the connection restriction set on the MA5600.
7) Check the connection parameters of the port on the MA5600.
8) Test loop-line using the subscriber line test terminal to analyze the test data.
[Fault description]
The MA5600 ADSL services have been provisioned for a user, but the user reports that
the telephone has no buzz, but he/she can access the Internet.
[Fault analysis]
The user's success in accessing the Internet indicates that the channel of the LINE port
is normal. The telephone's having no buzz indicates that the channel between the
PSTN port and the LINE port is faulty. The faults of this category are mainly caused by
improper engineering.
[Troubleshooting]
4-10
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
1) Check whether the internal plate has buzz. Connect the buzz line to the jumper
terminal. It is found through the test with the telephone receiver that the cabling
terminal has buzz but the jumper terminal has no. So, it can be judged that the
terminal board is faulty. Connect the buzz line to the cabling terminal, and then the
fault is removed.
2) If the internal plate has no buzz, open the plate, and then check whether the wiring
is correct. As a result, line a and line b are not connected well. Connect them
correctly, and then the fault is removed.
3) If the internal plate has buzz, and the wiring is good, then check the port’s
corresponding connector pins on the ADSL board of the MA5600. It is found that
the pins are curved. Rectify the pins, and then the fault is removed.
4) If the connector pins of the ADSL or SPL board are normal, test with the telephone
receiver whether the cable connector at the MA5600 side has buzz. If there is no
buzz, short circuit the peer end line a and line b, and then use the multimeter to
measure the line to judge whether there exists broken circuit or crossing. If there is
any broken circuit or crossing, it may be caused by unreliable wire clamping.
5) If the cables are normal, replace the ADSL board to judge whether the ADSL
board is faulty.
[Fault description]
The MA5600 ADSL services have been provisioned for a user, but the user reports that
the telephone has buzz, but he/she fails to access the Internet.
[Fault analysis]
First, query the state of the “ADSL Link” LED on the ADSL Modem
If the “ADSL Link” LED is always on, it indicates that the Modem has been activated. In
such a case, the fault may lie in the user’s dialup software or PC settings. If the “ADSL
Link” LED blinks rapidly, it indicates that the Modem has not been activated. Then, the
fault may lie in the hardware.
[Troubleshooting]
The troubleshooting measures are different since the Modem may be in different
states.
1) If the Modem is activated, check whether the user’s dialup software is installed
correctly, and whether the settings of the user's PC are correct.
2) When the Modem is not activated, first check the state of the corresponding ADSL
port. If the port is in blocked state, unblock and activate it. If the port is in
deactivated state, activate it. If the fault is still not removed, then check the
hardware. The methods are as follows.
4-11
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
z Check connector pins of the user cables. Rectify the curved connector pins, if any.
z Pull out and then insert the ADSL board to check whether contact between the
board and the backplane of the MA5600 is firm.
z If the fault is still not removed after the ADSL board is pulled out and then inserted,
replace a normal ADSL board for the test.
[Fault description]
When a phone call comes or the user presses hookflash of the telephone set, the
ATU-R is deactivated.
[Fault analysis]
Why the ATU-R is deactivated is related to Modem faults and line faults. In this case,
the ringing or pressing affects the Modem, resulting in the fault. From the fault, it can be
seen that the line at the user side is not standard, and must be checked.
[Troubleshooting]
1) Replace the ATU-R, but the fault is not removed. So, the ATU-R is normal.
2) Disconnect the subscriber line of the user, and simulate effect on the activated
ATU-R by the telephone set at the MDF in the equipment room. As a result, the
Modem is not deactivated.
3) Duplicate the said simulation at the MDF at the user side. As a result, the ATU-R is
not deactivated.
4) It can be judged that user’s indoor wiring is wrong. Check the leading-in box in the
user's house, and find that the white one of a pair of telephone lines is
misconnected. That is to say, the grounding cable is hanging in the air. This is the
cause why the ADSL line is deactivated from time to time. Reconnect the leadin,
and then the fault is removed.
[Fault description]
An ADSL user gets access to the Internet but the Internet access rate is slow. The
download rate is just about 1 kbit/s or even slower sometimes. The user restarts the PC,
but the problem still exists. The user sends Ping packets, but found some packets are
lost.
[Fault analysis]
In general, why the ADSL user’s Internet access rate is slow is related to:
1) The user's PC settings
4-12
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Troubleshooting]
1) Use another PC for a test.
Loss of packets is not found. The user accesses the Internet normally, and the
downloading speed is about 150 kbit/s. Moreover, the user can enjoy smooth Video on
Demand (VOD) services. So, it can be deduced that the fault is related to the user’s PC.
2) Check the user’s PC.
z Check the settings of the user’s PC
The user’s PC settings: Pentium II-750MHZ/256MRAM/Legend 10M/100M triad
adaptive network card.
The settings are not substandard, so the fault is not related to PC settings.
z Check the user’s computer system
The user’s computer system was reinstalled a short period ago. So, the fault is not
caused by long-term use of the computer system.
z Check the software and hardware settings of the user’s PC
The network card rate is set to 10 Mbit/s by the user, and other settings are normal.
Restart the PC, but the fault is not removed. It is learnt from the user that this network
card is a new network card replaced after the computer system is reinstalled. Because
the new network card is of the same type as the old one, the user did not reinstall the
driver for the new one.
However, the rate of the new network card was set to 10M/100M self-adaptation by
default, and the user set the computer system's network card rate to 10 Mbit/s. In such
a case, the system’s network card rate settings are not consistent with rate settings of
the network card hardware.
4-13
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
Set the computer system’s network card rate to 10M/100M self-adaptation, and then
restart the computer. Then, the user can access the Internet normally and enjoy smooth
Video on Demand (VoD) services.
[Fault description]
Complete the data configuration at the central office end of the MA5600, as well as
connection of the ADSL port, ADSL Modem, PC, and subscriber lines, and then debug
the ADSL services of 0 kilometer at the near end.
Through debugging, it is found that the “ADSL Link” LED on the ADSL Modem blinks all
the time, which indicates that the line cannot be activated. The corresponding ADSL
port on the MA5600 is in “Activating" state.
[Fault analysis]
Since the debugging is just 0 kilometer away from the ATU-C, so the fault is not related
to the line length. So, in general, wrong connection of lines causes failure to activate
the Modem.
[Troubleshooting]
1) Check the ATU-R and the ATU-C data configurations, and confirm that these
configurations are correct.
2) Check the connections between the subscriber lines and the MDF, and confirm
that the connections are correct.
3) Check the line connections of the ADSL board and the SPL board, and found that
engineers directly connected the subscriber lines to the ADSL port on the ADSL
board. According to engineering standards, the subscriber lines must be
connected to the LINE port on the SPL board. The ADSL port on the ADSL board
is connected to the ADSL port on the SPL board with ADL-SPL cable.
4) Reconnect the lines according to engineering standards, it is found that the "ADSL
Link” on the ADSL Modem is always on. It is found through the NMS that the port is
activated.
5) Access the Internet in dialup mode through the PC for a test, and find that the
ADSL services are normal.
4-14
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Fault description]
An ADSL user gets offline frequently when surfing the Internet. The ATU-R and ATU-C
wiring is correct, and the line quality is high. Replace the ATU-R, but the fault is still not
removed.
[Fault analysis]
Through analysis, it is found that the connections between the cables and the boards
are not checked. After the cables are pulled out, it is found that the connector pins
corresponding to the LINE, PSTN, and ADSL cables are obviously deviated. This is the
cause for line instability.
[Troubleshooting]
1) Set right the pins of cables and then insert them, and find that the user does not
get offline frequently.
2) However, when the user makes or answers a phone call, he gets offline
sometimes (probability: 50%). Change an ADSL port, and the user's Internet
surfing is firmly stable.
[Fault description]
The ADSL services are provisioned for a user, but the user’s ATU-R cannot be
activated.
[Fault analysis]
If the wires from the PSTN port and the LINE port on the SPL board are misconnected
each other, the POTS services are normal, but the ATU-R cannot be activated.
[Troubleshooting]
1) Check data and find no problem.
2) Do a test on the MDF, and the ATU-R still cannot be activated, but the telephone's
dial tone is normal. Then, this indicates that the line is activated. Why the ATU-R
cannot be activated may be because the line between the MDF and the MA5600 is
in bad conditions, or is connected wrong.
3) Check the wires from the PSTN and the LINE on the SPL board, and find that
these wires are misconnected each other. Exchange the connectors, and then the
ATU-R can be activated normally.
4-15
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Fault description]
An ADSL user can access the Internet normally, but finds serious noise in the
telephone when he makes a phone call.
[Fault analysis]
[Troubleshooting]
1) Check the splitter and find no problem, but the telephone still has noise.
2) Change the telephone, but the new telephone still has noise.
3) When a phone call is answered directly at the access network side, there is no
noise. But when the ADSL board is connected with the cable, the noise is
generated. Replace the ADSL board, but there still exists noise.
4) Through investigation, it is found that there is a power cabinet near the MA5600.
Maybe the strong interference from it causes noise to the telephone.
5) Disconnect connectors to the LINE and PSTN ports on the MA5600, and do a test
on the MDF, but the noise still exists. Disconnect the PSTN wire in the interior of
the MDF, and then connect the MA5600 to the interior of the MDF using a cable.
Then, the fault is removed.
[Fault description]
The Caller ID Display (CID) service has been provisioned to ADSL users, but they
report that the caller ID cannot be displayed.
[Fault analysis]
Because the ADSL users can access the Internet normally, the problems related to high
frequency signals can be excluded. Because the frequency range set for the splitters
and the local signal frequency range do not match, the low frequency signals are in
4-16
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
fault. After the frequency range of the splitters is expanded, the caller ID can be
displayed on the telephone.
[Troubleshooting]
1) Check whether the splitters are used in these user’s houses. Through site
inspection, it is found that the splitters of the same brand are used in these users'
houses.
2) Check the indoor wiring of these users. Through site inspection, it is found that the
telephones are all correctly connected with the splitters.
3) Do a test on the MDF. It is found that the caller ID cannot be displayed when the
splitter is connected; if the splitter is disconnected, the caller ID can be displayed.
Then, maybe the splitters of this brand are faulty.
4) Through a site test, it is found that the frequency range of the splitters is not the
same as that of the corresponding office. So, the splitters of this brand cannot be
used. Expand the frequency range of splitters of this brand, and then the fault is
removed.
4.4.10 Noise to the Telephone During a Phone Call Caused by Wrong Wiring
on MDF
[Fault description]
After several months when the networking equipment works, the maintenance
personnel report: when a user makes a phone call, the telephone has noise. When the
user does not get access to the Internet, he can make a phone call normally. But when
he makes a phone call during Internet access, the telephone has noise.
[Fault analysis]
z The noise in the telephone when the user makes a phone call is caused by
interfering signals mixed into voice signals. In this case, the user can make a
phone call normally when he does not access to the Internet; but when he makes a
phone call during Internet access, he hears noise in the telephone. This indicates
that Internet access causes interfering signals to voice signals. Then, the fault can
be located after checking where the interfering signals come from.
z If at the beginning, the user can access the Internet and make a phone call
normally, but abnormalities emerge after a period of time, this indicates that some
parts are damaged, or cable connections are changed, thus causing the fault.
z First, check the splitter. Maybe the low filtering quality of the splitter causes high
frequency data signals’ intrusion into the telephone.
[Troubleshooting]
1) Replace the splitter in the user’s house, but the fault is still not removed. This
indicates that the splitter is normal, and the noise is not high frequency data signal.
4-17
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
Because for a normal splitter, its low-pass filter has high impedance against high
frequency signals, so the high frequency signals cannot pass through the low
frequency interface.
2) Check the connection of the service cables and find no problem.
3) Change the user’s telephone, but the fault is still not removed. If the characteristic
impedance of the telephone and that of the cable do not match, signals may be
reflected, causing noise.
4) Do the wiring test on the vertical MDF, but the fault still exists.
5) Do the wiring test on the horizontal ADSL terminal board, and find that Internet
access is normal but making a phone call fails. This indicates that the low
frequency voice signals do not pass, and the wiring is faulty.
6) Check the wiring of the terminal board, and find that the jumper between the
vertical MDF and the vertical MDF of the original switch is not removed. Correct
the wiring, and then the fault is removed.
[Fault description]
The subscriber lines from the ADSL board on the MA5600 are connected to the ATU-R,
providing ADSL high-speed broadband access services. But during debugging, it is
found that the Internet access rate is low.
[Fault analysis]
Ping PC1 from the PC connected to the ATU-R of the second MA5600 with default 32
bytes of data, and find that the time delay is about 41ms.
[Troubleshooting]
Check the port configuration data of the ADSL board, and change the ADSL channel
mode from interleaved mode to fast mode. Then, the time delay is 7ms and the fault is
removed now.
[Conclusion]
An ADSL port can work in interleaved mode or fast mode. The fast mode is free from
interleaving and deinterleaving process, so the time delay can be reduced. For delay
sensitive ADSL services, the fast mode is recommended.
[Fault description]
4-18
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Fault analysis]
When there are a relatively large number of users in a local area network (LAN) through
only one ADSL Modem, or these users open a number of network applications, the
number of TCP Sessions are large. In such a case, a number of TCP receivers send
“confirmation" packets at the same time, causing congestion and delay in upstream.
Then, the senders send TCP packets again. Based on these factors, the actual
downloading speed is very slow. It is recommended that you set the upstream rate to
128 kbit/s or higher.
[Troubleshooting]
Check the port parameters, and find that the upstream rate of the port on the ADSL
board of the MA5600 is 64 kbit/s, and the downstream rate is 960 kbit/s. Change the
upstream rate to 256 kbit/s, and then the downstream rate is normal.
[Fault description]
The ADSL PPPoE/oA users of the MA5600 are authenticated for access to the Internet
on the upper layer BRAS. Some users report that they often get offline, but can access
the Internet through dialup once again after they get offline.
[Fault analysis]
z Through site investigation, the said fault is confirmed. In addition, during the said
period, the Modem is not deactivated.
z Some users select the Modem + HUB + PC networking mode. Maybe the HUB is
blocked in case of large amount of data exchange. But the fault is still not removed
when the HUB is replaced.
z Maybe high occupation rate of the CPU of the BRAS causes the fault. But it is
queried that the CPU occupation rate is only 19% in trace mode. So, this
possibility is excluded.
z Check the data configuration of the MA5600, and find that the port operating mode
is interleaved and the interleaved depth is 64. During site monitoring, it is found
that the pinging packets are jittered regularly. That is to say, a pinging packet with
relatively long delay occurs after 7–8 packets.
In PPPoE/oA mode, the BRAS sends PPP ECHO packets to the client software at
intervals to check whether the PPP users exist. If there is no response after the
BRAS has sent PPP ECHO packets for certain times, the BRAS disconnects the
user. Maybe the interleaved depth is too large, so the PPP ECHO packets sent
from the BRAS to the client software are lost, and then the BRAS disconnects the
user. Change the interleaved depth to 16, and then find that the fault is abated.
4-19
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Troubleshooting]
1) Set the interleaved depth to 16. Through monitoring, it is found that the count of
service interruptions is decreased.
2) Set the interleaved depth to 8. Through a long period of monitoring, it is found that
the fault is removed.
IV. Parameter settings adjustment to boost Internet access rate or line stability
[Fault description]
A majority of ADSL users of an office can access the Internet at the rates of up to
100–200 kbit/s. But the furthest user of this office accesses the Internet at the rate of up
to 12 kbit/s. The distance between this user and the MA5600 is 3 km.
[Fault analysis]
Why the training rate is high but the actual rate is low is generally because the distance
is long, the loop resistance is large, and the SNR margin is large.
[Troubleshooting]
1) Check the line, and find no problem.
2) Check the port, and find the training rate in downstream is 6144 kbit/s, and the
actual rate is 1024 kbit/s. Change the training rate to 8000 kbit/s, and train the port
again. The actual downstream rate is changed to 1152 kbit/s, but the Internet
access rate is still about 10 kbit/s.
3) Check the ADSL port parameter settings, and find that the user selects the
interleaved mode, and set the maximum/minimum SNR margin to 14/0.
4) It is found from alarm records that other ports are deactivated occasionally, but
this port is never deactivated.
5) Change the channel mode to “fast”, and the Internet access rate is increased to
about 20 kbit/s.
6) Change the maximum SNR margin to 8, and do not change the minimum SNR
margin, and train the port again. The port works stably, and the Internet access
rate is increased fast. Change the maximum/minimum SNR margin to 4/0. The
port works stably, and the Internet access rate reaches up to 130 kbit/s. The fault
is removed.
[Conclusion]
z Change the channel mode to “fast”, and then the Internet surfing speed is always
doubled. Because in fast mode, the cell modulation and error correcting methods
are simpler than those in interleaved mode, the transmission delay in fast mode is
much shorter than that in interleaved mode.
z Increasing the SNR margin will lower the rate, but will improve the
anti-interference capabilities and boost the stability. In a similar way, decreasing
4-20
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
the SNR margin will increase the rate, but will reduce the anti-interference
capabilities, and may cause instability to the ATU-R.
z In actual applications, if the line conditions are good, lower the SNR margin to
increase the rate.
[Fault description]
An ADSL user reports that his Internet access rate in ADSL mode is very low, and even
sometimes it is lower than that in dialup mode.
[Fault analysis]
It is difficult to locate such a fault, but you can still locate in the following order: from the
upper layer device to the MA5600, to the ADSL line, to the ADSL Modem, and then to
the PC.
[Troubleshooting]
1) Use the user’s PC to download files, but the rate is just 4 kbit/s. In order to prove
that the PC is normal, connect the portable PC to a port on the upper layer switch.
The downloading rate reaches up to 8 Mbit/s.
2) Connect the portable PC to an Ethernet port on the MA5600, and then the
downloading rate approaches 8 Mbit/s.
3) Check the traffic of the ADSL port on the MA5600, and find that the cell flow in
upstream approximates that in downstream. This indicates that the
communication channel between the MA5600 and the upper layer switch is
normal. The fault may lie in subscriber lines.
4) Check the subscriber lines and the ADSL Modem, and find no problem. The fault
may occur on the user’s PC.
5) The PC configuration is standard, and the network card configuration is correct.
Then, maybe there exists virus causing the fault. Use the antivirus software, and
then find that the PC has been infected with virus seriously. In total, more than 250
viruses are killed.
6) But after all the viruses are killed, the rate is still not satisfactory. Reinstall the
driver for the network card, and the rate reaches up to 400 kbit/s. The fault is
removed.
[Conclusion]
Because the user’s PC is infected with virus, the performance of the PC and network
card is lowered. In such a case, they cannot process a large amount of data traffic, thus
causing low Internet access rate.
4-21
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Fault description]
An office provides ADSL services through the MA5600. A user succeeds in dialup with
PPPoE dialup software. Then, the addresses and DNS messages allocated can be
seen from the PPPoE window, but the user cannot access the Internet. He cannot ping
any IP address outside of the network.
[Fault analysis]
z The services fail, but the PPPoE connection succeeds. This indicates that
communication channel between the terminal and the BRAS is normal.
z First, check the BRAS port. If the same fault occurs on other points, maybe the
BRAS port is faulty.
z If this is a single-point fault, check whether there exists such software as PROXY
that affects the PPPoE software.
[Troubleshooting]
1) Through detection, it is found that other services are normal. This indicates that
Broadband Remote Access Server (BRAS) port is normal.
2) Check the terminal, and the PPPoE window indicates that the address allocation
has been performed correctly. But it is found through Winipcfg that the IP
addresses of the PC and the gateway are both 0.0.0.0. The PC is not installed with
other network software.
3) Change the PC, and perform the PPPoE dialup, and find that the services are
returned to normal.
[Fault description]
An ADSL user uses correct username and password, and performs PPPoE dialup for
Internet access authentication. The dialup software prompts an alarm “authentication
fail”. The user performs the dialup again after an hour, and passes the authentication.
Then, he can access the Internet.
[Fault analysis]
Restrict the number of persons who can use the account at the same time at the
RADIUS Server side. Also, the time for checking the account of the user who is
disconnected abnormally can be set.
In this case, the number of persons who can use the account at the RADIUS Server
side is set to 1, and the update information checking time is long. So, when the user
accesses the Internet, but gets offline abnormally in case the PC fails or due to other
4-22
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
causes, the Server still keeps the account's Internet access information. When the user
performs dialup for Internet access again, the Server deems his access as
unauthorized access (the number of persons who use the account at the same time is
more than 1) since it keeps the account’s information.
So, the dialup fails, and the alarm "authentication fail” prompts. But when the set
update time is exceeded, the Server will automatically stop the account’s Internet
access process if failing to receive any Internet access information from the user. Then,
after another dialup, the user can pass authentication.
[Troubleshooting]
1) Suspend the account’s Internet access process manually at the RADIUS Server
side.
2) Increase the number of persons who can use this account at the same time in the
attributes of the account at the RADIUS Server side.
3) Shorten the user information update time at the RADIUS Server, for example, 5
minutes.
[Fault description]
[Fault analysis]
z Observe whether the ATU-R is deactivated. It is found that the ATU-R is not
deactivated.
z Ping the gateway, and find no problem.
z Ping the DNS server, and find no problem.
z Change the PC, but the fault is still not removed.
z Directly enter the IP address of a website, and it is found that the website can be
visited. Then, it can be basically judged that the DNS server is faulty.
[Troubleshooting]
It is learnt that the DNSs and ADSL users of other points are normal. Replace the DNS
Server of this point by a new one, and then the fault is removed.
[Conclusion]
When an ADSL user does not get offline, and can ping the IP address of a website,
compare carefully this user’s PC settings with those of other computers to find out the
cause.
4-23
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
4.4.16 Relatively Long Delays for Some Packets in Pinging the Gateway
[Fault description]
An ADSL user can get access to the Internet normally. When he pings the gateway, he
finds that the time delay of one among 7 packets is relatively long. For example, the
time delay for the first six packets is 40ms, but that for the seventh is 140ms.
[Fault analysis]
The ATU-R of the ADSL user checks the line conditions from time to time. In such a
case, when checking line conditions, the ATU-R software first stores the user data in
the buffer, and then sends them out. This is the reason why the time delay for some
ping packets is relatively long. This is a normal phenomenon.
[Troubleshooting]
4.4.17 Loss of Packets and Low Internet Access Rates Caused by Wrong
Connection of Network Cable for HUB
[Fault description]
After the ADSL services are provisioned to an Internet cafe user, the user reports that
the Internet access rate is low, a number of packets are lost, and he gets offline from
time to time. At the Internet cafe, ping public network IP addresses from the PC in the
cafe, and find that a number of packets are lost. The loss rate is about 40–50%.
[Fault analysis]
In general, the UPLINK ports on the HUB are ports for subtending upper end equipment,
such as the router, the ATU-R, or the upper end HUB. They cannot be connected to a
common PC. Otherwise, faults may occur.
[Troubleshooting]
1) Check data configuration, and find no problem.
2) Remove the HUB under the ATU-R, and directly connect the PC to the ATU-R.
Then, pinging public network IP addresses is normal. Based on these facts, the
fault may occur on the HUB.
3) Check the HUB in use, and find there are two UPLINK ports on the HUB. One
UPLINK port is connected to the ATU-R, and the other one is connected to a PC
for Internet access. Pull out the common cable connected to the PC for Internet
access, and the packet loss rate is decreased to 0, and the Internet access rate is
increased rapidly.
4-24
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
4.4.18 Failure to Log in to the ADSL Modem Through Internet Explorer (IE)
I. Failure to log in to the ADSL Modem caused by the ARP Cache that is not
refreshed
[Fault description]
When the host software of the ADSL Modem is upgraded, the failure is found in logging
in to ADSL Modems through IE. The IP address of the ADSL Modem is 192.168.1.1.
[Fault analysis]
All the hosts in the network have ARP Cache. The ARP Cache stores the records of
mapping from the IP addresses visited recently to hardware MAC addresses. The time
to live for every record in the Cache is 20 minutes in general, starting from creation.
When the IP address 192.168.1.1 is entered in the address bar of IE, the system needs
to query the physical address corresponding to this IP address. If there is the
corresponding record in the Cache, the MAC address can be visited directly. If there is
no, the broadcast packets are sent to the MAC addresses corresponding the
192.168.1.1.
When logging in to the first Modem, the user succeeds since there is no mapping
record in the Cache ad the MAC address can be obtained through broadcast packets.
When logging in to another Modem, the user fails since the mapping record exists in the
Cache, and then the system will log in to the second Modem according to the MAC
address (of the first Modem) in the mapping record. After the mapping record of
192.168.1.1 is deleted from the Cache or aged, the login succeeds.
[Troubleshooting]
Go back to Windows mode, and enter 192.168.1.1 in the address bar of the IE. The
fault is removed.
[Fault description]
Enter the IP address of the Modem in the address bar of IE, a block diagram appears,
but there is no interface for inputting the password. IE has no response, so it fails to
operate the Modem.
[Fault analysis]
4-25
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
The interfaces for logging in to some ADSL Modems are programmed with JAVA
SCRIPT. To log in to the Modem, execute JAVA SCRIPT. In default install mode of IE5.5,
the JAVA option is not selected, so it fails to log in to the Modem. Reinstall IE, and select
full install.
[Troubleshooting]
Replace the Modem, but the fault is still not removed. Change the PC, the fault is
removed.
When logging in to the Modem from the original PC again, the maintenance personnel
find that the status bar of IE prompts that the system has no response after reading
JAVE SCRIPT. Uninstall IE (5.5) and reinstall it. Select default install. But it still fails to
log in to the Modem. Uninstall IE again and then reinstall it. Select full install. Then, the
fault is removed.
[Fault description]
A group of ADSL users with IP addresses get offline frequently after the ADSL services
are provisioned for them. When a user gets offline, the ADSL LINK LED of the ATU-R is
always on. When the user pings the gateway, no packet is lost. When he pings DNS,
about 80% packets are lost. The user fails to access the Internet. After about 20
minutes, he can browse web pages again.
[Fault analysis]
When using stationary IP addresses for Internet access, make sure the IP address of
the PC’s gateway is different from that of he ATU-R. Otherwise, faults frequently occur
in forwarding of IP packets.
[Troubleshooting]
1) Ping the DNS through the MA5600 and find no problem. This indicates that the
DNS is normal.
2) Then, the gateway is suspected to be the cause of the trouble. Re-set the IP
address of the gateway, and then the fault is removed. Through a test, it is found
that the fault occurs when the network segment 192.168.1.1/24–192.168.1.1 is
used as the gateway. It is found through querying the IP address of the ATU-R that
the ATU-R’s IP address is 192.168.1.1. The two IP addresses conflict.
3) Set the IP address of the gateway and then the fault is removed.
4-26
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 4 Troubleshooting ADSL Services
[Fault description]
The downstream channel SNR margin negotiated by an ADSL port of the MA5600 with
the ADSL modem is negative (–26 dB).
[Fault analysis]
The bits to be allocated are calculated according to the channel's SNR during the
training process, and the left SNR is the SNR margin. The bits allocated to each
sub-channel are not changed if the SNR of the sub-channel is changed. During the
operation, if a sub-band has a fixed interfering source, the SNR will be decreased.
Then, the SNR margin may become negative. Even if the SNR margin is negative, the
ADSL services are still normal, and the user does not get offline. But when bit errors are
increased and cannot be corrected, the user may get offline.
For example, the SNR of a sub-channel is 25 dB during the training process, and the
SNR margin is 13 dB. Then, the sub-channel carries 4 bits (3 dB for each bit) of data.
Due to the affect of noise, the SNR decreases to 0 dB, but the sub-channel still carries
4 bits of data. Then, the SNR margin decreases to -13 dB (4 bit). Bit errors are
generated, but can be corrected.
[Troubleshooting]
4-27
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
SHDSL provides a symmetrical transmission rate of 2312 kbit/s, with the transmission
distance from 3 km to 6 km. It is widely used for high-speed data service access, and
can extend the E1/T1 lines.
SHDSL features:
z High symmetric rates
z Strong anti-interference capability
z Long transmission distance
With such features, SHDSL will play an important role in the future among three DSL
technologies (SHDSL, VDSL, and SHDSL).
5-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
There are two types of SHDSL modes, TDM-based and ATM-based. In these two
modes, TDM signals and ATM signals are converted to SHDSL signals.
Figure 5-1 is the reference model of SHDSL, consisting of the STU-C and the STU-R.
The interface at the SHDSL line side is connected with the copper telephone twisted
pair. If enhanced transmission range is required, one or more SHDSL Regenerator
Units (SRU) may be inserted into the loop.
Console
I. Introduction to Boards
Table 5-2 lists the SHDSL board of the MA5600 to provide ATM-based SHDSL access
services.
II. Networking
The MA5600 supports IP-DSLAM networking, and thus the MA5600 can connect
SHDSL users to the upper layer IP network.
5-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
IP
FE/GE
MA5600
SHDSL业务
SHDSL service SHDSL
SHDSL
service SHDSL
SHDSL业务
service
Start
End
5-3
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
Through queries in the NMS, it can be primarily judged where a fault is located, such as
the upper layer equipment, the MA5600, or the equipment at the user end.
Note:
The abbreviations of the names of the LEDs on various models of SHDSL Transceiver
Units-Remote end (STU-R, SHDSL Modem) are different. But in general, “Power”,
“WAN”, “LINK/ACT” are included.
Query and record the model of the user’s Modem and the states of the LEDs on the
Modem, and judge whether the Modem is in fault.
The following takes the X3102r Modem of Huawei for example to introduce how to
locate an SHDSL fault by using the states of the LEDs on the SHDSL Modem.
Table 5-3 shows the states of the X3102r Modem and corresponding instructions.
5-4
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
5-5
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
z Contrast the connection parameters with the neighboring lines. The key point is to
see whether the difference between the channel attenuation values is more than 5
dB. If yes, it indicates that the line is faulty.
Check:
z The MA5600 hardware, including the board states, port states, and system
running states.
z Whether the configuration data is correct, including the traffic profiles, line profiles,
and port rates.
If no fault has been found till now, maybe the upper layer device is faulty. Then, check
the running state and configuration data of the upper layer device. Especially, check
whether the upper layer interface matches the MA5600.
Network access faults may result from all sets of equipment or links in the broadband
network architecture, including upstream equipment, SHDSL ports on the MA5600 at
central office end, STU-Rs, user PCs, and physical lines.
By checking the states of LEDs on the STU-R, and operation and setting of the user’s
PC, and querying the information through the NMS, you can further locate the fault.
5.3.2 Comparing with Historic Records and with the Neighboring Line
Parameters
5-6
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
If the user still cannot access the Internet, it can be judged that the fault may occur on
the equipment at the user end, the upstream port, or the fault is caused by the user's
improper operation.
Then, locate and remove the fault according to the following methods.
1) Method for locating the fault for a user with a stationary IP address
z If the user can ping the gateway successfully, but still cannot access the Internet, it
can be basically judged that the fault occurs on the upper layer equipment of the
MA5600, the access server, or the router.
z If the user cannot ping the gateway, the fault may occur on the MA5600, the PC
settings, the SHDSL line, or the DNS.
2) Method for locating the fault for a user in PPPoE dialup access mode
z Observe whether the user can reach the PPPoE authentication stage. If yes, but
the authentication fails, or the authentication succeeds but the user still cannot
access the Internet normally, it can be judged that the fault occurs on the access
server. It can be queried through the network management center (NMC) whether
other ports are involved in the similar faults.
z If the PPPoE authentication succeeds, but the user still cannot visit any website,
then the fault occurs on the access server or the websites.
z If the user fails to begin normal PPPoE dialup, it can be judged that the user’s
dialup software is faulty. Re-install the dialup software, and make the PC settings
correct. The key points in PC settings are whether the TCP/IP attribute setting is
correct, whether the IP address is obtained automatically, whether the dialup
account format and password are correct, and whether the dialup software is
installed correctly.
z If the user cannot log in to the access server, the fault may occur on the MA5600,
the PC settings, the SHDSL line, and so on.
5-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 5 Troubleshooting SHDSL Services
5-8
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
I. FE electrical port
Attribute Description
Connector RJ-45 (TPI)
Port rate (Mbit/s) 100 (full duplex)
Maximum reach (m) 100
Standards compliance IEEE 802.3u
Cable category Category-5 twisted pair cable
Attribute Description
Connector LC
6-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
Attribute Description
Center wavelength (nm) 1310
Transmit optical power (dBm) –8– –15
Extinction ratio (dB) 8.2
Receiver sensitivity (dBm) –28
Attribute Description
Connector LC
Attribute Description
Connector LC
Port rate (Gbit/s) 1.25
6-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
Attribute Description
Connector LC
Port rate (Gbit/s) 1.25
Attribute Description
Connector RJ-45
Port rate (Mbit/s) 1000 (full duplex)
Maximum reach (m) 100
Standards compliance IEEE 802.3ab
6-3
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
PC
LAN1 PC HUB
PC
Upper layer
DSLAM
network
PC
PC
In this model, several PCs are connected to form LANs based on a certain rule. The
LANs are connected to the digital subscriber line access multiplexer (DSLAM) through
the HUB or the LAN Switch. The DSLAM transparently transmits Ethernet frames from
the LANs to the upper layer network.
The FE/GE ports on the SCU board can work as upstream or subtending ports to
provide upstream or subtending services, or as service ports to provide Ethernet
access services.
Table 6-7 lists all the subboards attached on the SCU boards of the MA5600.
Subboard Description
O4GS 4-port GE optical subboard
O2GS 1-/2-port GE optical subboard
E2GA 2-port GE/FE electrical subboard
II. Networking
6-4
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
IP
MA5600 GE GE MA5600
S S
C C
U U
FE/GE
FE/GE FE/GE FE/GE FE/GE
The MA5600 transmits Ethernet service data transparently, and provides private line
based broadband access services for small to medium enterprises that are incapable of
building their private networks or fail to afford costs for the digital data network (DDN).
In this way, these enterprises can interconnect their headquarters and branches
together, and interconnect them and the Internet.
The MA5600 can also transmit service data from downstream to the upper layer
network through the FE/GE ports.
6-5
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
Start
End
Use the command display port state to query the states of all Ethernet ports on the
SCU board. Especially, check whether the ports are online or offline, and whether these
ports are activated.
MA5600(config-if-scu-0/7)#display port state all
--------------------------------------------------------------------------
Port Port Optic Native MDI Speed Duplex Flow- Active Link
Type Status VLAN (Mbps) Control State
-------------------------------------------------------------------------
0 GE - 1 auto auto_1000 auto_full off active online
1 GE - 1 auto auto_1000 auto_full off active online
--------------------------------------------------------------------------
Check whether the rate and duplex settings for the ports are correct. If one end does
not support auto-negotiation, but the peer end is set to auto-negotiation, the services
may be interrupted from time to time accordingly. Then, set the corresponding Ethernet
6-6
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
ports as non-auto-negotiation. The both ends must have the same settings. They can
be both auto-negotiation, or they can be both non-auto-negotiation.
Check whether the TAG attributes of the ports are set according to the rules below:
z When the VLAN ID of the Ethernet port is the same as the default VLAN ID (Native
VLAN ID), the packets from the port become untagged packets. That is, the
MA5600 peels the VLAN IDs off the packets.
z When the VLAN ID of the Ethernet port is different from the default VLAN ID
(Native VLAN ID), the packets from the port become tagged packets. That is, the
MA5600 transmits VLAN IDs transparently.
z Use the command display port vlan to check board VLAN settings, especially
VLAN ID and native VLAN.
MA5600(config)#display port vlan 0/7/1
---------------------------------------
1 10 50 60 61 62
100 101 1000 1001 1002 1003
1004 1005 1006 1007 1008 1009
---------------------------------------
Total: 18 Native VLAN: 1
z Use the command display vlan to check whether the upstream port and the
virtual service ports included in the VLAN configured for the board are normal.
MA5600(config)#display vlan 1000
VLAN ID: 1000
VLAN type: MUX
VLAN attribute: common
------------------------------
F/S /P Native VLAN State
------------------------------
0/7 /0 1 up
0/7 /1 1 up
------------------------------
Standard port number: 2
------------------------------
Type State F/ S/ P VPI VCI
------------------------------
adl down 0/ 2/ 0 0 35
------------------------------
Service virtual port number: 1
6-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
Use the command display service-port to check whether the settings of the service
port are correct. Especially, check the state of the service port, VLAN ID, and the virtual
service port information.
MA5600(config)#display service-port all
-------------------------------------------------------------------------
VLAN ID VLAN-ATTR PORT-TYPE F / S/ P VPI VCI RX TX STATE LABEL
-------------------------------------------------------------------------
1300 common shl 0 / 5/ 0 0 35 6 6 up -
1300 common shl 0 / 5/ 1 0 35 6 6 down -
1300 common shl 0 / 5/ 2 0 35 6 6 down -
1300 common shl 0 / 5/ 3 0 35 6 6 down -
1300 common shl 0 / 5/ 4 0 35 6 6 down -
-------------------------------------------------------------------------
Total : 5 (Up/Down : 1/4)
Note : F--Frame, S--Slot, P--Port(or Virtual Port, such as IMA GROUP,
VLAN ID etc.), the VPI is access-end VLAN ID in vdsl/eau port
or PON ID in epon port
If no problem has been found till now, use the command display port statistics to
check the ports several times.
For example, check whether the number of received and transmitted frames increases,
and whether there exist pause frames. If the received and transmitted data frames are
both added, there exists no Pause frame, but the services fail, use the command show
statistics sar to check whether CRC fault and length count error occur. If the count is
not 0, it indicates that the board may be faulty.
MA5600(config-if-scu-0/7)#display port statistics 0
Number of transmitted frames =3181505
Number of received frames =289557
Total number of frames =3471062
Number of transmitted multicast frames =17406
Number of received multicast frames =47613
Total number of multicast frames =65019
Number of transmitted broadcast frames =3163993
Number of received broadcast frames =241831
Total number of broadcast frames =3405824
Number of transmitted pause frames =0
6-8
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
[Fault description]
An office uses the SCU board of the MA5600 for LAN interconnection. But the Ethernet
services fail. Check the data configuration and physical connection and find no problem,
and the LINK LED of the network cable is green.
[Fault analysis]
1) It is suspected that the port modes at both ends do not match. Check the port
modes of the equipment at both ends, and find that they are both 10/100 Mbit/s
auto-negotiation, and the interconnection rate is also 100 Mbit/s.
6-9
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
2) Check the physical connection, and find that the network cable is not made
according to the standard linear ordering. So the network cable is just for 10 Mbit/s
line.
[Troubleshooting]
Make the network cable according to the standard linear ordering, and then the
services recover.
[Conclusion]
The ports are 100 Mbit/s auto-negotiation, but they are connected with a 10 Mbit/s
network cable. This is the reason why the Ethernet services fail.
6.4.2 Failure to Ping the Gateway Caused by Wrong Terminal Route Settings
[Fault description]
An ADSL user accesses the Internet through the MA5600 in IP-DSLAM mode. The IP
address of the user’s PC is set to 10.30.1.2, the mask is 255.255.0.0, and the gateway
is 10.30.1.1. The user can ping the IP address 10.30.1.1 of the network port of the
Layer 3 switch, but fails to ping the IP address 10.2.21.202 of the upstream network
port of the switch. The user fails to access the Internet.
[Fault analysis]
1) Check the firewall configuration and the routing forward configuration of the Layer
3 switch, and find no problem.
2) When using route print to check the routing table in DOS operating system, the
user finds two routes: 0.0.0.0. The gateways are 10.10.10.1 and 10.30.1.1
respectively. But the gateway of the preceding default route is not 10.30.1.1.
3) Check the TCP/IP settings of the PC, and find another gateway 10.10.10.14.
Because the default route 0.0.0.0 in the routing table should be one, and the one
passing through the gateway 10.10.10.1 is preceding. So, when the user pings
10.2.21.202, the IP packets are forwarded from 10.10.10.1, and then they cannot
reach the switch.
[Troubleshooting]
Delete this gateway, the user can ping the upstream network port on the switch and can
access the Internet normally.
6.4.3 Low Internet Access Rate Caused by Failure in VLAN Isolation for
Upstream Port
[Fault description]
The user's networking mode: FE port on the MA5600 ÆLAN Switch ÆRouter.
Fault phenomenon: From 7:30 PM to 9:00 PM, the ADSL user's Internet access rate is
low, and a number of ping packets are lost. A large amount of bandwidth of the user is
occupied by unnecessary broadcast packets or multicast packets.
6-10
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
[Fault analysis]
1) It is suspected that the IP addresses conflict. But when the fault reoccurs, the fault
is not removed even when there is no address conflict. So, the fault is not related
to conflict between IP addresses.
2) It is suspected that the negotiation between the SCU board of the MA5600 and the
photoelectric transducer fails. But it is found through check that the LAN board and
the transducer are both 100 M full duplex.
3) Maybe the LAN Switch does not divide VLANs. This LAN Switch is just a low-level
D-link acting as a Hub in the whole network, and cannot divide VLANs. When the
fault reoccurs, use the packet catcher software to capture packets on the ADSL
user port. A number of broadcast and multicast packets are captured which are
not related to the user. The user’s bandwidth for Internet access is occupied by
these packets, so the user's Internet access rate is low.
[Troubleshooting]
Add a VLAN to the LAN Switch connected to the upstream port, and then the fault is
removed.
[Conclusion]
In IP-DSLAM networking mode, when the LAN Switch is connected to the upstream
port, a VLAN must be added for it to isolate broadcast packets.
[Fault description]
An office adopts the MA5600 IP-DSLAM networking. The MA5600 is connected to a
layer 2 switch through its upstream port and then connected to the router. Stationary IP
addresses (public network) are allocated to users for Internet access.
Fault phenomenon: The Internet access services are disrupted, and the user can ping
the gateway, but fails to ping the DNS.
[Fault analysis]
1) Connect a user’s PC to a port on the layer 2 switch, and then the Internet access is
normal. This indicates that the port is normal.
2) Check the data configuration, and find no problem. Ping the gateway through a
port on the SCU board, and find that a number of packets are lost. Replace the
LAN board and the main control board, but the fault is still not removed.
3) Check the configuration of the router, and find IP addresses conflict alarms. The
MAC address bound to the IP address of the gateway is wrong. Based on these
facts, it can be judged that the fault is related to conflict of the gateway IP
addresses.
[Troubleshooting]
6-11
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
1) Pull out the network cable between the MA5600 and the layer 2 switch, but it still
fails to ping the IP address of the gateway.
2) Pull out the network cables connected to the layer 2 switch until it succeeds in
pinging the IP address of the gateway.
3) It is found that the IP address of a PC is the same as the IP address of the gateway.
Isolate this PC, modify the MAC address bound to the gateway, and then the
services recover.
[Fault description]
The networking mode of the MA5600 is IP-DSLAM. With the same traffic control, the
rates of the PC users who access the Internet directly through the SCU board are low,
and the maximum rate is just about 50–60 kbit/s.
[Fault analysis]
1) Check the configuration data of the MA5600, and find no problem.
2) Replace a user's PC, and then the Internet access rate is normal. Then, maybe the
user’s PC is faulty.
3) Check the network configuration of the user’s terminal, and find the ATM LAN
emulation protocol and WAN support for ATM protocol besides the TCP/IP
protocol.
[Troubleshooting]
Delete the extra protocols, and then the fault is removed.
[Conclusion]
Unnecessary network protocols are configured in the user’s terminal and thus cause
low Internet access rate. It is suggested to just configure necessary network protocols,
and do not configure extra protocols.
[Fault description]
In IP-DSLAM networking mode of the MA5600, the Internet access services are
disrupted, but Internet access directly through the SCU board is normal. After about 10
minutes, the disrupted services recover automatically. Reset the LAN board, and then
the services can recover, but the fault will occur frequently.
[Troubleshooting]
1) Check whether the SCU board is impacted by a large amount of traffic, but actually
the SCU board works normally.
2) Connect the PC to another network port (within the same VLAN) of the SCU board,
and find that Internet access is normal, but the PC fails to communicate with ADSL
6-12
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
users within the region VLAN. Then, it can be judged that the SCU is normal, and
the link between the SCU board and the ADSL is faulty.
3) Connect an ADSL Modem at the near end, and then connect a PC to it to ping the
public network IP addresses. But it fails to ping any public network IP address. Use
the packet catcher software to capture the received data packets, and find that the
user receives a large number of data packets not for him. The traffic rate reaches
up to 400–500 kbit/s. The maximum downstream rates for majority of ADSL users
are configured to 350–512 kbit/s. So, the downstream bandwidth of the user is
occupied by these useless data, thus causing failure to normal services.
4) Analyze the received useless data packets, and find that they are sent to an ADSL
user by the router, and the destination IP address and MAC address are not
broadcast IP address. In normal conditions, other ADSL users cannot receive
these data. Disable this user manually, and then the services recover. Then, it is
suspected that the user performs some special settings.
[Solution]
1) Check the user's PC and find the MAC address obtained by the SCU board is
inconsistent with the MAC address of its network card.
2) Check the settings of the PC, and find the user selects the option “Network Load
Equalization” of the Windows 2000 operating system. The cluster MAC address
generated by the operation system for the network card is different from the actual
MAC address of the network card. But the MAC address checked from the router
is the cluster MAC address.
3) Delete this option, and then the services recover.
[Conclusion]
The main function of the “Network Load Equalization" of Windows 2000 is to provide
sharing of service traffic load among multiple servers within a LAN. This option is not for
external interface of the server. If this function is enabled, a router is required to isolate
this LAN from other networks.
[Fault description]
Networking: MA5600ÆRouterÆInternet
Upon an upgrade, all users connected to an MA5600 report that they fail to access the
Internet.
[Fault analysis]
Because all users of the MA5600 fail to access the Internet, the problem may be related
to the upstream connection.
[Troubleshooting]
6-13
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 6 Troubleshooting Ethernet Services
1) Check the parameters of the Ethernet port on the SCU board: auto-negotiation,
activated, VLAN ID:1, native VLAN: 1.
2) Check the configuration data of the router, and find the default port parameters:
10/100 M, auto-negotiation, port VLAN: 2, TAGGED.
3) After the above two steps, it can be confirmed that the problem is related to the
VLAN settings at both ends.
The Ethernet packets sent from the Ethernet port at the MA5600 side do not carry
the VLAN Tag, but the router only accepts packets with the VLAN Tag.
[Solution]
Log in to the MA5600, and change the VLAN ID of the SCU board to 2, and the native
VLAN to 1000. Then, the problem is solved.
6-14
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
Multicast refers to a process of transmitting packets of data from one source to many
destinations. The key of multicast technology is to carry out packet duplication most
close to the receiver.
Multicast has the following advantages:
z Reducing load on the server, so that the server need not handle request on a per
user basis.
z Saving network bandwidth, which lowers the requirement on the network device.
z Adapting to various user quantities, so that increase of users will not impose
pressure on the network.
The MA5600 supports IGMP Proxy and plays a role of the IGMP Proxy server:
z The MA5600 works as a multicast router for a multicast user.
z The MA5600 is a multicast user for the upper layer multicast router.
Figure 7-1 shows a network topology of multicast service.
7-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
Multicast server
Internet
Multicast router
MA5600
ADSL ADSL
Modem Modem
PC PC
7-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
Start
Check VPI/VCI
End
Figure 7-2 Flow for Locating the fault of failure to access the Internet
7-3
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
7-4
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
Use the command display igmp program to check whether the programs are
correctly configured.
z Use the command display igmp program all to check whether the programs are
configured. If yes, check whether the upstream ports and VLAN IDs are correct. In
case of across-VLAN forwarding, check whether the across-VLAN forwarding is
enabled.
MA5600(config-btv)#display igmp program all
----------------------------------------------------------------------
IP | Program |Num of |Uplink|VLAN|Across |Prejoin|Prio-
Address | name |watching| port | ID | VLAN | |rity
----------------------------------------------------------------------
----
224.1.1.1 program1 0 0/7/0 100 enable disable 3
224.1.1.2 program2 0 0/7/0 100 enable disable 3
224.1.1.3 program3 0 0/7/0 100 enable disable 3
----------------------------------------------------------------------
Total: 3 program(s)
Note : # The program data is valid, but it is no license or
the uplink port ID is beyond number of board port.
z Run the command display igmp program ip ip-addr to check details of a
program, including validity of the program.
MA5600(config-btv)#display igmp program ip 224.1.1.1
---------------------------------------------
Program index : 0
Validity : valid
Program name : cctv-1
IP address : 224.1.1.1
Uplink Port : 0/7/0
VLAN ID : 10
Host attribute : enable
Log attribute : enable
Prejion attribute : disable
Across VLAN attribute : enable
Unsolicited attribute : disable
Preivew duration(s) : 120
Preivew times : 8
Preivew interval(s) : 120
Priority : 0
Numbers of watching : 0
---------------------------------------------
Watching IGMP cascade port :
0/7/1
7-5
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
0/7/2
7) Check IGMP packets.
In global mode, use the command debugging igmp all to enable igmp debugging
to check the trace of IGMP packets and query IGMP packets processing.
Start
End
Figure 7-3 Flowchart for locating the fault of failure to watch a multicast program
7-6
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
Use the command display igmp uplink-port to check whether the upstream port
configuration is correct, such as whether the configuration is complete, and
whether the VLAN ID is correct.
MA5600(config)#display igmp uplink-port all
--------------------------------------------------------------------
Program IGMP V1 Router Present
Port VLANID number version Host IP Timer(s)
--------------------------------------------------------------------
0/7/0 10 2 IGMP v2 214.1.1.1 400
0/7/2 1 3 IGMP v1 214.1.1.2 300
0/7/3 3 5 IGMP v1 214.1.1.3 350
0/7/3 4 3 IGMP v1 214.1.1.4 400
--------------------------------------------------------------------
Total: 4
2) Check the program information.
Run the command display igmp program ip ip-addr to check the details of a program,
including the VLAN ID, Host attribute and Host IP.
z VLAN ID
If the packets sent from the upper layer router do not contain the VLAN Tag, the
native VLAN of the upstream port of the MA5600 must be the same as the
program VLAN. Otherwise, the native VLAN of the upstream port of the MA5600
shall be different from the program VLAN.
z Host attribute
Normally, Host attribute is in “enable” state. Otherwise, IGMP Proxy sends no
IGMP packet to the upper layer device. If Host attribute is not in “enable” state, run
the command igmp program modify to modify it.
z Host IP
If Host attribute is in “enable” state, and the upper layer router checks the source
IP address, run the command display igmp uplink-port to check whether Host IP
is in the same network segment as the IP address of the interface on the router.
Otherwise, run the command igmp uplink-port frame/slot/port vlanid hostip to
modify Host IP and make it in the same network segment as the IP address of the
interface on the router.
MA5600(config-btv)#display igmp program ip 224.1.1.1
---------------------------------------------
Program index : 0
Validity : valid
Program name : cctv-1
IP address : 224.1.1.1
Uplink Port : 0/7/0
7-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
VLAN ID : 10
Host attribute : enable
Log attribute : enable
Prejion attribute : disable
Across VLAN attribute : enable
Unsolicited attribute : disable
Preivew duration(s) : 120
Preivew times : 8
Preivew interval(s) : 120
Priority : 0
Numbers of watching : 0
---------------------------------------------
Watching IGMP cascade port :
0/7/1
0/7/2
---------------------------------------------
3) Check RSTP root port.
If the upstream port is in RSTP mode, check whether the root port selected
according to RSTP is the expected upstream port.
4) Check port’s default video PVC.
Use the command display igmp proxy to check whether the default VPI/VCI of
the virtual service port for video service is the same as the VPI/VCI (you can use
the command display service-port to query it) of the multicast user. If not, modify
the multicast user’s VPI/VCI so that it can be the same as the default VPI/VCI.
MA5600(config-btv)#display igmp proxy
--------------------------------------------------------
Program number of license : 1024
IGMP proxy switch : enable
Authorization : enable
Default video VPI : 0
Default video VCI : 35
Robustness variable : 2
General query interval(s) : 125
General query response time(0.1s) : 100
Specific query interval(0.1s) : 10
Specific query response time(0.1s) : 8
Specific query number : 2
V1 router present timeout(s) : 400
Unsolicited report interval(s) : 10
Uplink port mode : program
Log switch : enable
7-8
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
7-9
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
Start
End
Figure 7-4 Flowchart for locating the fault of failure to watch a program with good
quality
7-10
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
In ADSL configuration mode, use the command display line operation to check
the Modem’s downstream rate.
Low downstream rate reduces the program quality. In this case, check the line
quality or the ADSL line profile.
MA5600(config)#display line operation port 0/2/34
Channel mode : Interleaved
Downstream channel bit swap : Enable
Upstream channel bit swap : Enable
Trellis mode : Enable
Standard in port training : G992.5
Downstream channel rate(Kbps) : 7996
Downstream max. attainable rate(Kbps) : 25353
Downstream channel SNR margin(dB) : 29.5
Downstream interleaved channel delay(ms) : 6
Downstream channel attenuation(dB) : 0.0
Downstream total output power(dBm) : 8.3
Upstream channel rate(Kbps) : 1021
Upstream max. attainable rate(Kbps) : 1271
Upstream channel SNR margin(dB) : 9.5
Upstream interleaved channel delay(ms) : 3
Upstream channel attenuation(dB) : 0.0
Upstream total output power(dBm) : 0.5
----------------------------------------------------------
G992.1 : G.dmt
G992.2 : G.lite
G992.3 : G.dmt.bis
G992.5 : G.dmt.bisplus
3) Check the service board type.
Because multicast data stream requires a bandwidth of 4 Mbit/s in downstream, it
is suggested that you not adopt the SHDSL board to implement multicast service
due to port rate limitation to the SHDSL board.
4) Check the upper layer device
If there exists loopback on the upper layer device, the multicast traffic will be
interfered to affect the quality of the program.
Directly connect the PC to the upper layer device (switch or router) to order a
program. If the quality of the program is poor, maybe there exists loopback on the
upper layer device, or the same multicast traffic from different sources is sent to
the upper layer device.
Check the loopback and multicast traffic configurations of the upper layer device,
and then take the corresponding measures.
7-11
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 7 Troubleshooting Multicast Services
[Fault description]
A multicast user reports when he watches the multicast programs ordered, sometimes
the quality of some programs ordered is poor.
[Fault analysis]
Upon several tests, the quality of a program is poor when the size of the program is
large, for example, exceeding 4 Mbit/s. Then, it can be primarily judged that the CAR
set is too small.
[Troubleshooting]
1) Run the command display service-port to check the traffic index of the service
port, and find that the self-defined traffic index is 10.
2) Run the command display traffic table index 10 to check traffic items, and find
that the CAR set is less than 4 Mbit/s.
3) Increase the CAR, and then the fault is removed.
[Fault description]
A Triple Play user fails to order a multicast program.
[Troubleshooting]
1) Check the upstream port state and find no problem.
2) Check the upstream port configuration, including Host IP and VLAN and find no
problem.
3) Check the state of the Triple Play user, and find no problem.
The multicast user adopts the multi-PVC solution and is online.
4) Check the default VPI/VCI of the video port and find that the user’s multicast
service VPI/VCI is 0/32 which is different from the default VPI/VCI (0/35) of the
virtual service port for video service.
5) Modify the user’s multicast service VPI/VCI so that it is the same as the default
VPI/VCI of the virtual service port for video service. Then, the fault is removed.
7-12
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
8.1 Overview
An alarm ID contains eight octets that are divided into four groups, shown as below.
0x A A B C D D D D
(4)
(3)
(2)
(1)
8-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
3 Equipment -
4 Environment -
Alarm severity labels the severity level of an alarm. In terms of decreasing order, alarm
severities are divided into critical alarm, major alarm, minor alarm and warning.
z Critical alarm refers to the alarm which endangers the normal operation of the
MA5600 and requires immediate troubleshooting, such as power circuit failure and
output clock failure.
8-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
z Major alarm refers to the alarm generated in certain board or line, which may lead
to system abnormality if not processed in time, such as fiber broken, physical line
fault, and so on. The Major alarm may not be the serious incidental event, but may
also be generated in the normal manual operation.
z Minor alarm refers to the general fault alarm or event alarm which describes
whether each board or line is normal, such as an alarm which indicates bit error in
a certain physical line.
z Warning alarm refers to the status change and event, which will not affect the
system performance and the user service, but to which the operator may pay
attention.
The MA5600 provides not only configuration and querying function of alarm information,
but also records of alarm history and statistics. The adiministrator queries the alarm
information to monitor the operating state of the MA5600.
To Use Meaning
Show basic alarm
display alarm
information by -
configuration alarm ID
alarm ID
Alarm categories include
Show basic alarm
communication, service,
information by display alarm list type
process, equipment, and
alarm categories
environment.
Show basic alarm
Alarm type includes event, fault,
information by display alarm list class
and recovery.
alarm types
To Use Meaning
Show alarm display alarm history
-
history by alarm ID alarm ID
8-3
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
To Use Meaning
Alarm categories include
Show alarm
display alarm history communication, service,
history by alarm
type process, equipment, and
categories
environment.
Show alarm type display alarm history Alarm types include event, fault,
by alarm types class and recovery.
Show alarm
display alarm history Alarm severities include critical,
history by alarm
level major, minor, warning.
severities
Use this command to query basic
Show alarm display alarm history alarm information in a range of all
history by range of from start-date start-time or a certain alarm ID without
ID to end-date end-time knowing of exact alarm ID and
find corresponding alarm ID.
Show brief
information of display alarm history list -
alarm history
Detailed information includes
Show detailed alarm ID, relevant parameters,
display alarm history
information of and detailed description of alarm,
detail
alarm history alarm cause and suggested
treatment.
Use display alarm statistics alarm ID to show alarm statistics. Now the system only
provides querying function of alarm statistics by alarm ID.
To Use Meaning
Modify alarm alarm alarmlevel alarm ID Set new alarm severities only by
severities alarm level alarm ID
Set new alarm threshold only by
alarm threshold alarmid
Modify alarm alarm ID, and the threshold
threshold15m
threshold values are 15-minute threshold
threshold24h
and 24-hour threshold
8-4
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
To Use Meaning
Enable the
alarm statistics Set by alarm ID, alarm severities,
statistics for one or
alarmid|alarmlevel|alarm alarm categories or set the
a certain kind of
type|all statistics for all alarms.
alarm
Alarm Alarm
Alarm ID 0x00200000 Event Minor
Type Severity
Alarm Alarm
Alarm ID 0x00200001 Event Minor
Type Severity
Alarm Description Alarm number in 24 hours exceeds the threshold.
8-5
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x09200000 Event Major
Type Severity
The patch files or status in active board are different form
Alarm Description
those in backup board.
Alarm Parameter -
1) Active and standby board patch files inconsistent.
Alarm Cause
2) Active and standby board patch status inconsistent.
1) For cause one, reload the patch file\r\n.
Suggested
Treatment 2) For cause two, make the patch status of standby board
be consistent with that of active board.
Alarm Alarm
Alarm ID 0x09200001 Event
Type Severity
Failed in restoring system patch files, please reload system
Alarm Description
patch files.
Alarm Alarm
Alarm ID 0x24200001 Event Major
Type Severity
Alarm Description Auto-load start.
Alarm Parameter FrameID, SlotID, Board type, File type.
Alarm Cause IO board runs.
Suggested
No need to process.
Treatment
8-6
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x24200002 Event Major
Type Severity
Alarm Description Auto-load complete.
Alarm Parameter FrameID, SlotID, Board type, File type.
Alarm Cause Auto-load succeeded.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x24200003 Event Major
Type Severity
Alarm Description Auto-load failure.
Alarm Parameter FrameID, SlotID, Board type, File type.
1) No reply from IO board.
Alarm Cause 2) The transmission of message between main control
board and IO board is not stable.
Suggested 1) Ensure the board can be loaded automatically.
Treatment 2) Make sure all the boards have been plugged in firmly.
Alarm Alarm
Alarm ID 0x0b200001 Event Major
Type Severity
Alarm Description Start to load files.
Alarm Alarm
Alarm ID 0x0b200002 Event Minor
Type Severity
Alarm Description Load files successfully.
Alarm Parameter FRAMEID, SLOTID, LOAD TYPE.
Alarm Cause Load succeeded.
Suggested
No need to process.
Treatment
8-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0b200003 Event Major
Type Severity
Alarm Description Failed in loading files.
Alarm Parameter FRAMEID, SLOTID, LOAD TYPE.
Alarm Cause Load failed.
Suggested
Check according to failure cause and reload.
Treatment
Alarm Alarm
Alarm ID 0x0b200004 Event Major
Type Severity
Alarm Description Start to roll back files.
Alarm Parameter FRAMEID, SLOTID, ROLLBACK.
Alarm Cause Rollback started.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b200005 Event Major
Type Severity
Alarm Description Roll back files successfully.
Alarm Alarm
Alarm ID 0x0b200006 Event Major
Type Severity
Alarm Description Failed in rolling back files.
Alarm Parameter FRAMEID, SLOTID, ROLLBACK.
Alarm Alarm
Alarm ID 0x0b200011 Event Major
Type Severity
8-8
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0b200012 Event Major
Type Severity
Alarm Description No rollback completed.
Alarm Parameter FRAMEID, SLOTID, NOROLLBACK.
Alarm Cause No rollback completed.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b200013 Event Major
Type Severity
Alarm Description No rollback failed.
Alarm Alarm
Alarm ID 0x0b200014 Event Major
Type Severity
Alarm Description Program or data resume failed, use save to resume.
Alarm Parameter FRAMEID, SLOTID, NOROLLBACK.
Alarm Alarm
Alarm ID 0x0b200015 Event Major
Type Severity
Alarm Description Disable rollback function in case of system timeout.
Alarm Parameter FRAMEID, SLOTID, NOROLLBACK.
Alarm Cause Disable rollback function in case of system timeout.
8-9
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b200007 Event Major
Type Severity
Alarm Description Start to duplicate files from active board to backup board.
Alarm Parameter FRAMEID, SLOTID, DUPLICATE TYPE.
Alarm Cause Duplication started.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b200008 Event Major
Type Severity
Alarm Description Duplicate files successfully to backup board.
Alarm Alarm
Alarm ID 0x0b200009 Event Major
Type Severity
Alarm Description Failed in duplicating files to backup board.
Alarm Parameter FRAMEID, SLOTID, DUPLICATE TYPE, failure reason .
Alarm Alarm
Alarm ID 0x0b20000a Event Major
Type Severity
Alarm Description Start to backup files from the host to maintenance terminal.
Alarm Parameter FRAMEID, SLOTID.BACKUP, TYPE.
Alarm Cause Backup started.
8-10
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b20000b Event Major
Type Severity
Alarm Description Backup files successfully to maintenance terminal.
Alarm Parameter FRAMEID, SLOTID, BACKUP TYPE.
Alarm Cause Backup succeeded.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b20000c Event Major
Type Severity
Alarm Description Failed in backing up files to the maintenance terminal.
Alarm Alarm
Alarm ID 0x0b20000d Event Major
Type Severity
Alarm Description The host runs backup data since active data are unavailable.
Alarm Parameter FRAMEID, SLOTID.
8-11
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0b20000f Event Minor
Type Severity
Alarm Description Erase backup files successfully.
Alarm Parameter FRAMEID, SLOTID, LOAD TYPE.
Alarm Cause Erase backup files successfully.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b200010 Event Major
Type Severity
Suggested
Check according to failure cause and re-erase.
Treatment
Alarm Alarm
Alarm ID 0x07200001 Event Major
Type Severity
Alarm Description Switch over between the active and standby boards.
Alarm Parameter FRAMEID, SLOTID, Previous active board SLOTID.
1) System manual switchover has taken place,
Alarm Cause 2) Protective switchover\r\n has occurs to the system due to
the backplane failure.
1) For cause one, there is no need to process.
Suggested
Treatment 2) For cause two, check the hardware and software of the
previous active board.
8-12
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x07200002 Event Minor
Type Severity
Automatic switchover between active and standby boards
Alarm Description
fails.
Alarm Parameter -
1) Standby board is not in position or works abnormally at
the \r\n specified automatic switchover time.
2) Clock subboard of the standby board is faulty at the
specified automatic switchover time.
3) Data synchronization is insufficient at the specified
automatic switchover time.
4) Active and standby boards have loaded the software of
Alarm Cause
different versions.
5) Database of standby board is invalid at the specified
automatic switchover time.
6) Board status has changed before the last attempt of
automatic switchover.
7) Loading/backing up/duplicating/saving is being
performed on active/standby board.
1) For cause one, check whether the standby board works
normally.
2) For cause two, check the clock subboard of standby
board. You can have it switched over manually or wait for
the next system auto switchover after the clock subboard
work normally.
3) For cause three, query to find if the data synchronization
has been completed. Try to switch over after data
synchronization is completed. You can switch over
Suggested manually or wait for the next automatic switchover.
Treatment
4) For cause four, check whether the software versions of
active and standby boards are consistent.
5) For cause five, check whether database of standby
board is valid. If not, load right database to standby
board and reboot it.
6) For cause six, you can switch over manually or wait for
the next automatic switchover.
7) For cause seven, you can switch over manually or wait
for the next automatic switchover.
8-13
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x07200003 Event Major
Type Severity
Software version of active board is different from that of
Alarm Description
standby board.
Alarm Parameter -
Active and standby boards have loaded the software of
Alarm Cause
different versions.
Check whether the software versions of active and standby
Suggested
boards are consistent. If not, load the same version software
Treatment
and reboot the system.
Alarm Alarm
Alarm ID 0x02300081 Fault Major
Type Severity
The versions of base BIOS, extend BIOS, CPLD and so on
Alarm Description
are different between active board and standby board.
Alarm Parameter -
The versions of BIOS or CPLD in active and standby boards
Alarm Cause
are different.
Alarm Alarm
Alarm ID 0x07200005 Event Major
Type Severity
Alarm Description The system reboots due to abnormal switchover.
Alarm Parameter -
1) Protective switchover occurs because of active board
fault.
Alarm Cause
2) Forced switchover occurs when data synchronization is
insufficient.
1) For cause one, check the operating status of previous
Suggested active board to locate the fault cause.
Treatment
2) For cause two, no need to process.
8-14
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x07210000 Fault Major
Type Severity
Alarm Description Active board cannot communicate with standby board.
Alarm Parameter -
1) Standby board faulty.
Alarm Cause
2) Standby board not in position.
1) For cause one, check whether standby board is working
Suggested normally.
Treatment
2) For cause two, no need to process.
Alarm Alarm
Alarm ID 0x02300044 Event Major
Type Severity
The MAC of active main control board and standby control
Alarm Description
board are different, reset standby board.
Alarm Parameter The MAC of active board, The Mac of standby board
Alarm Cause The MAC of active and standby board are different.
Suggested
Reset standby board.
Treatment
8-15
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0e210000 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x0e220000 Recovery Major
Type Severity
Alarm Description CPU occupation rate returns to normal value.
Alarm Parameter The current CPU performance
Alarm Cause CPU occupation rate returns to normal value.
Suggested
No need to process.
Treatment
8-16
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x16000000 Event Major
Type Severity
Alarm Description Important operations from NMS (Such as reboot, switchover).
Alarm Parameter Frame, slot, port, NMS IP Address
1) NMS delivers system board reset command.
2) NMS delivers disabling board command.
3) NMS delivers board reset command.
4) NMS delivers data loading command.
5) NMS delivers program loading command.
Alarm Cause 6) NMS delivers switchover command.
7) NMS delivers rollback command.
8) NMS delivers port showdown command.
9) NMS delivers flash clear command.
10) NMS delivers frame reset command.
11) NMS delivers logic loading command.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x17300002 Event Major
Type Severity
8-17
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
Load the correct configuration data file, and reset the device.
Treatment
Alarm Cause Data check of the active configuration data area fails.
Suggested Check the configuration data to see if they are complete, and
Treatment then save the data.
8-18
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x02310000 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x02300005 Event Major
Type Severity
Alarm Description Board runs short of TDM resources.
Alarm Parameter FrameID, SlotID, Board Type
Alarm Cause No more TDM resources are available.
Suggested Reconfigure boards, such as adjusting quantity, modifying
Treatment board's operating mode, to release the TDM resource.
8-19
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x02300008 Event Major
Type Severity
Alarm Description Port runs short of TDM resources.
Alarm Parameter FrameID, SlotID, Board Type
Alarm Cause No more TDM resources are available.
Suggested Reconfigure boards, such as adjusting quantity, modifying
Treatment board's operating mode, to release the TDM resource.
Alarm Alarm
Alarm ID 0x02300008 Event Major
Type Severity
Alarm Alarm
Alarm ID 0x02300042 Event Major
Type Severity
8-20
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x02300043 Event Major
Type Severity
Alarm Description Subboards type in main control board do not match.
Alarm Parameter FrameID, SlotID, sub0, sub1
The combination of subboards on main control board is not
Alarm Cause
supported.
Suggested
Check subboards of main control board.
Treatment
Alarm Alarm
Alarm ID 0x02300075 Fault Major
Type Severity
The number and types of subboards of active and standby
Alarm Description boards’ in consistency or active board's subboard fault
causes data synchronization unable to process.
Alarm Alarm
Alarm ID 0x0230003c Event Major
Type Severity
Alarm Description Board is replaced.
Alarm Parameter Frame ID, Slot ID, Old board Name, New board Name
Alarm Cause Communication with the main control board recovered.
Suggested
No need to process.
Treatment
8-21
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x023000aa Event Major
Type Severity
Exception occurs in the corresponding hardware, which may
Alarm Description
result in switchover.
Alarm Parameter Frame ID, Slot ID, Hardware type, Fault Type.
Alarm Cause Corresponding hardware failure.
Alarm Alarm
Alarm ID 0x0b20001e Event Major
Type Severity
Alarm Description Loading emu-program start.
Alarm Parameter EMU ID, loadtype
Alarm Cause Load started.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0b20001f Event Major
Type Severity
Alarm Description Loading emu-program failed.
Alarm Parameter EMU ID, loadtype, fail reason
Alarm Cause Load failure.
Suggested
Check according to failure cause and reload.
Treatment
Alarm Alarm
Alarm ID 0x0b200020 Event Major
Type Severity
8-22
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15401000 Event Major
Type Severity
Alarm Description Fan speed-regulating mode or opening mode changes.
Alarm Parameter FRAME ID, EMU ID, EMU Type, Control State, Open State
Environmental temperature or fan configuration parameter
Alarm Cause
changed.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15401002 Event Major
Type Severity
Alarm Alarm
Alarm ID 0x15401005 Event Major
Type Severity
Alarm Description AC input changes.
FRAME ID, EMU ID, Power ID, EMU Type, Power Type,
Alarm Parameter
Switch Result
8-23
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15401008 Event Major
Type Severity
Alarm Description Esc power event information.
FRAME ID, EMU ID, Power ID, EMU Type , Power Type,
Alarm Parameter
Hysics Variable Name, Physics Variable State
Alarm Cause Universal power module fault.
Suggested
Check the working status of the universal power module.
Treatment
Alarm Alarm
Alarm ID 0x1540100a Event Major
Type Severity
Alarm Description Rectifier mode changes.
Alarm Parameter FRAME ID, EMU ID, Power ID, Rectifier ID, EMU Type
Alarm Cause Rectifier working parameter changed.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1540100c Event Major
Type Severity
8-24
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1540100d Event Major
Type Severity
Alarm Description Lightning protection unit breakdown or damage.
FRAME ID, EMU ID, Power ID, EMU Type, Power Type,
Alarm Parameter
Thunder Proof Switch State
Alarm Cause Lightning protection unit broken down.
Suggested
Replace the lightning protection unit of good quality.
Treatment
Alarm Alarm
Alarm ID 0x15401010 Event Major
Type Severity
Alarm Description The configuration of power module is inconsistent with facts.
Alarm Alarm
Alarm ID 0x15401011 Event Major
Type Severity
Alarm Alarm
Alarm ID 0x15401012 Event Major
Type Severity
Alarm Description Battery discharge test stopped.
Alarm Parameter FRAME ID,EMU ID, Power ID,EMU Type, Power Type
8-25
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411000 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411001 Fault Major
Type Severity
Alarm Description Analog threshold overflow.
Alarm Parameter FRAME ID, EMU ID, Analog ID , EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
8-26
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411002 Fault Major
Type Severity
Alarm Description Analog upper limit overflow.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Alarm
Alarm ID 0x15411003 Fault Major
Type Severity
Alarm Description Analog lower limit overflow alarm.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection is lower than the preset lower limit
Alarm Cause
of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
8-27
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type , Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411005 Fault Major
Type Severity
Alarm Description Digital is inconsistent with the configured value.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411007 Fault Major
Type Severity
Alarm Description Power module is faulty or cannot communicate with EMU.
Alarm Parameter FRAME ID,EMU ID, Power ID, EMU Type, Power Type
1) Power module fault.
2) Communication between power module and monitoring
Alarm Cause
unit is abnormal.
3) Power module is reset manually.
1) For cause one, replace the power module.
Suggested 2) For cause two, check the communication line between
Treatment the power module and EMU.
3) For cause three, no need to process.
8-28
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411008 Fault Major
Type Severity
Alarm Description AC abnormal alarm.
FRAME ID, EMU ID, Power ID, AC Loop ID, EMU Type,
Alarm Parameter
Power Type
Alarm Cause AC input voltage is overvoltage or undervoltage.
Suggested 1) Check the AC input power supply.
Treatment 2) Adjust the AC input voltage threshold appropriately.
Alarm Alarm
Alarm ID 0x15411009 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x1541100a Fault Major
Type Severity
8-29
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541100b Fault Major
Type Severity
Alarm Description DC over-voltage alarm.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
8-30
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541100d Fault Major
Type Severity
Alarm Description DC under-voltage alarm.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
Alarm Cause DC output voltage is undervoltage.
Suggested 1) Check the working status of the power module.
Treatment 2) Adjust the DC output voltage threshold appropriately.
Alarm Alarm
Alarm ID 0x15411010 Fault Major
Type Severity
Alarm Description Battery off alarm.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
Alarm Cause Battery voltage is too low.
Suggested
Check the battery. Recharge or replace it if necessary.
Treatment
8-31
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411011 Fault Major
Type Severity
Alarm Description Load off alarm.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
Alarm Cause Battery voltage is too low.
Suggested
Check the battery. Recharge or replace it if necessary.
Treatment
Alarm Parameter FRAME ID, EMU ID, Power ID , EMU Type, Power Type
Alarm Cause Load power-off recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411012 Fault Major
Type Severity
Alarm Description Mains supply offline alarm.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
Alarm Cause No Mains.
Suggested
Check if the Mains are OK.
Treatment
8-32
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411013 Fault Major
Type Severity
Alarm Description Battery fuse broken alarm.
FRAME ID,EMU ID, Power ID, Battery ID ,EMU Type, Power
Alarm Parameter
Type
Alarm Cause Battery fuse is blown.
Suggested
Replace the fuse.
Treatment
Alarm Alarm
Alarm ID 0x15411014 Fault Major
Type Severity
Suggested
Check and replace the contactor when necessary.
Treatment
Alarm Alarm
Alarm ID 0x15411015 Fault Major
Type Severity
Alarm Description Battery loop broken alarm.
FRAME ID,EMU ID, Power ID, Battery ID ,EMU Type, Power
Alarm Parameter
Type
8-33
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411016 Fault Major
Type Severity
Alarm Description User module off alarm.
FRAME ID,EMU ID, Power ID, Battery ID ,EMU Type, Power
Alarm Parameter
Type
Alarm Cause Battery voltage is too low.
Suggested
Check the battery. Recharge or replace it if necessary.
Treatment
8-34
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411017 Fault Major
Type Severity
Alarm Description Transmission module off alarm.
FRAME ID, EMU ID, Power ID, Battery ID, EMU Type, Power
Alarm Parameter
Type
Alarm Cause Battery voltage is too low.
Suggested
Check the battery. Recharge or replace it if necessary.
Treatment
Alarm Alarm
Alarm ID 0x15411018 Fault Major
Type Severity
Alarm Description Load fuses broken alarm.
FRAME ID,EMU ID, Power ID, Battery ID, EMU Type, Power
Alarm Parameter
Type
Alarm Cause Load fuse is blown.
Suggested
Replace the fuse.
Treatment
8-35
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411019 Fault Major
Type Severity
Alarm Description AC module out of service alarm.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
1) AC distribution panel fault.
Alarm Cause 2) Communication between AC distribution panel and
power monitoring module is abnormal.
1) For cause one, replace the AC distribution panel.
Suggested 2) For cause two, check the communication line between
Treatment the AC distribution panel and the power monitoring
module.
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
Communication between the board and the master board
Alarm Cause
recovered.
Suggested
No need to process.
Treatment
8-36
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541101a Fault Major
Type Severity
Alarm Description Battery charging over-current alarm.
FRAME ID, EMU ID, Power ID, Battery ID, EMU Type, Power
Alarm Parameter
Type
Alarm Cause Battery charging current is too large.
Suggested
Check if the loop of the battery is normal.
Treatment
FRAME ID, EMU ID, Power ID, Battery ID , EMU Type, Power
Alarm Parameter
Type
Alarm Cause Battery charging current recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1541101b Fault Major
Type Severity
8-37
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541101c Fault Major
Type Severity
Alarm Description Second Load off alarm.
Alarm Parameter FRAME ID,EMU ID, Power ID, EMU Type, Power Type
Alarm Cause Battery voltage is too low.
Suggested
Check the battery. Recharge or replace it if necessary.
Treatment
Alarm Alarm
Alarm ID 0x1541101d Fault Major
Type Severity
Alarm Description First load off alarm.
Alarm Parameter FRAME ID,EMU ID, Power ID, EMU Type, Power Type
Alarm Cause Battery voltage is too low.
Suggested
Check the battery. Recharge or replace it if necessary.
Treatment
Alarm Parameter FRAME ID, EMU ID, Power ID, EMU Type, Power Type
Alarm Cause Load twice power-off recovered.
Suggested
No need to process.
Treatment
8-38
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541101e Fault Major
Type Severity
Alarm Description AC input offline alarm.
FRAME ID, EMU ID, Power ID, AC Loop ID, EMU Type,
Alarm Parameter
Power Type
Alarm Cause AC input stopped.
Suggested
Check if the AC input is correct.
Treatment
Alarm Alarm
Alarm ID 0x1541101f Fault Major
Type Severity
Suggested
Check the working environment of this power supply.
Treatment
8-39
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411020 Fault Major
Type Severity
Alarm Description Rectifier fault alarm.
FRAME ID,EMU ID, Power ID, Rectifier ID,EMU Type, Power
Alarm Parameter
Type
1) Rectifier module fault.
2) Communication between rectifier module with power
Alarm Cause monitoring module is abnormal.
3) Rectifier module fails.
4) Rectifier module enters protection working status.
1) For cause one, check if the rectifier module is in good
contact; Replace this rectifier if necessary.
Suggested 2) For cause two, check the communication line between
Treatment this rectifier module and power monitoring module.
3) For cause three and four, check the working status of this
rectifier module.
Alarm Alarm
Alarm ID 0x15411021 Fault Major
Type Severity
Alarm Description DC module out of service alarm.
Alarm Parameter RAME ID, EMU ID, Power ID, EMU Type, Power Type
8-40
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411100 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x15411101 Fault Major
Type Severity
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411102 Fault Major
Type Severity
Alarm Description Battery voltage abnormal.
8-41
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411103 Fault Major
Type Severity
Alarm Description Battery fuse abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411104 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x15411105 Fault Major
Type Severity
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411106 Fault Major
Type Severity
Alarm Description DC power abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
8-42
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411107 Fault Major
Type Severity
Alarm Description Cupboard door abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411108 Fault Major
Type Severity
Alarm Description Room door abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID ,EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411109 Fault Major
Type Severity
Alarm Description Window abnormal alarm.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541110a Fault Major
Type Severity
Alarm Description Thief abnormal alarm.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541110b Fault Major
Type Severity
8-43
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541110c Fault Major
Type Severity
Alarm Description Fan abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541110d Fault Major
Type Severity
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541110e Fault Major
Type Severity
Alarm Description Fog abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541110f Fault Major
Type Severity
Alarm Description Water abnormal alarm.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
8-44
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411110 Fault Major
Type Severity
Alarm Description Diesel abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411111 Fault Major
Type Severity
Alarm Description Smell abnormal alarm
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411112 Fault Major
Type Severity
Alarm Description Air-condition abnormal alarm.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411113 Fault Major
Type Severity
Alarm Description Arrester abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411114 Fault Major
Type Severity
8-45
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411115 Fault
Type Severity
Alarm Description Output control switch abnormal.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15421100 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421101 Fault Major
Type Severity
Alarm Description AC switch recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421102 Fault Major
Type Severity
Alarm Description Battery voltage recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
8-46
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421103 Fault Major
Type Severity
Alarm Description Battery fuse recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421104 Fault Major
Type Severity
Alarm Description Load fuse recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421105 Fault Major
Type Severity
Alarm Description Rectifier recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421106 Fault Major
Type Severity
Alarm Description DC power recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x154211007 Fault Major
Type Severity
8-47
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421108 Fault Major
Type Severity
Alarm Description Room door recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421109 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542110a Fault Major
Type Severity
Alarm Description Thief recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542110b Fault Major
Type Severity
Alarm Description Wiring recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
8-48
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1542110c Fault Major
Type Severity
Alarm Description Fan recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542110d Fault Major
Type Severity
Alarm Description Fire recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x154211e Fault Major
Type Severity
Alarm Description Fog recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542110f Fault Major
Type Severity
Alarm Description Water recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421110 Fault Major
Type Severity
8-49
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421111 Fault Major
Type Severity
Alarm Description Smell recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421112 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421113 Fault Major
Type Severity
Alarm Description Arrester recovery.
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421114 Fault Major
Type Severity
Alarm Description DC voltage recovery
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
8-50
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421115 Fault Major
Type Severity
Alarm Description Output control switch recovery
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411140 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-0
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411141 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-1
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411142 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-2
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
8-51
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411143 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-3
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411144 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-4
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411145 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-5
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411146 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-6
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411147 Fault Major
Type Severity
8-52
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411148 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-8
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411149 Fault Major
Type Severity
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541114a Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-10
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541114b Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-11
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
8-53
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541114c Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-12
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541114d Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-13
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541114e Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-14
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541114f Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-15
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411150 Fault Major
Type Severity
Digital abnormal private-alarm-16 , DC module out of service
Alarm Description
alarm
8-54
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411151 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-17
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411152 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x15411153 Fault Major
Type Severity
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411154 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-20
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
8-55
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411155 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-21
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411156 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-22
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411157 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-23
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411158 Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-24
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411159 Fault Major
Type Severity
Digital abnormal private-alarm-31 , DC module out of service
Alarm Description
alarm
8-56
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541115a Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-26
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541115b Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x1541115c Fault Major
Type Severity
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541115d Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-29
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
8-57
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541115e Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-30
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541115f Fault Major
Type Severity
Alarm Description Digital abnormal private-alarm-31
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value mismatches the preset effective value.
Suggested
Check the monitoring target of this switch sensor.
Treatment
Alarm Alarm
Alarm ID 0x15421140 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-0
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421141 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-1
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421142 Fault Major
Type Severity
8-58
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421143 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-3
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421144 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421145 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-5
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421146 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-6
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
8-59
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421147 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-7
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421148 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-8
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421149 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-9
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542114a Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-10
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542114b Fault Major
Type Severity
8-60
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1542114c Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-12
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542114d Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542114e Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-14
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542114f Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-15
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
8-61
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421150 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-16
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421151 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-17
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421152 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-18
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421153 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-19
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421154 Fault Major
Type Severity
8-62
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421155 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-21
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421156 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421157 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-23
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421158 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-24
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
8-63
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421159 Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-25
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542115a Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-26
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542115b Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-27
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542115c Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-28
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542115d Fault Major
Type Severity
8-64
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1542115e Fault Major
Type Severity
Alarm Description Digital recovery private-alarm-30
Alarm Parameter FRAME ID, EMU ID, Digital ID, EMU Type, Name
Alarm Cause Boolean value recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542115f Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411201 Fault Major
Type Severity
Alarm Description Temperature abnormal.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411202 Fault Major
Type Severity
Alarm Description Humidity abnormal.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
8-65
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411203 Fault Major
Type Severity
Alarm Description DC voltage abnormal.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411204 Fault Major
Type Severity
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15421201 Fault Major
Type Severity
Alarm Description Temperature recovery alarm.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421202 Fault Major
Type Severity
Alarm Description Humidity recovery alarm.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
8-66
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421203 Fault Major
Type Severity
Alarm Description Voltage recovery alarm.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421204 Fault Major
Type Severity
Alarm Description Current recovery alarm.
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name.
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15411230 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-0
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411231 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-1
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
8-67
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411232 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-2
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411233 Fault Major
Type Severity
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411234 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-4
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411235 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-5
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
8-68
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15411236 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-6
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Alarm
Alarm ID 0x15411237 Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-7
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15411238 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x15411239 Fault Major
Type Severity
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541123a Fault Major
Type Severity
8-69
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541123b Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-11
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x1541123c Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x1541123d Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-13
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
8-70
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1541123e Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-14
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Alarm
Alarm ID 0x1541123f Fault Major
Type Severity
Alarm Description Analog threshold private-alarm-15
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Analog quantity collection exceeds the preset upper limit or
Alarm Cause
lower limit of the alarm.
Suggested
Check the monitoring target of this analog sensor.
Treatment
Alarm Alarm
Alarm ID 0x15421230 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x15421231 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-1
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421232 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-2
8-71
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421233 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-3
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421234 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x15421235 Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421236 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-6
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
8-72
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x15421237 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-7
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421238 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-8
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x15421239 Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-9
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542123a Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-10
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542123b Fault Major
Type Severity
8-73
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x1542123c Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-12
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542123d Fault Major
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542123e Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-14
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x1542123f Fault Major
Type Severity
Alarm Description Analog threshold recovery private-alarm-15
Alarm Parameter FRAME ID, EMU ID, Analog ID, EMU Type, Name
Alarm Cause Analog quantity recovered.
Suggested
No need to process.
Treatment
8-74
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0a300012 Event warning
Type Severity
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0a300013 Event warning
Type Severity
Alarm Description Line-caused auto ADSL/ADSL2+ port deactivation.
Alarm Parameter Frame, Slot, Port
1) Line Fault.
2) Line deteriorated.
Alarm Cause
3) ATU-R power-off.
4) Parameter setting of port activation template is improper.
1) For cause one, check if the line is broken.
2) For cause two, check the line quality.
Suggested 3) For cause three, check if the power supply for ATU-R is
Treatment normal.
4) For cause four, adjust parameters of port activating
template.
Alarm Alarm
Alarm ID 0x0a300015 Event Warning
Type Severity
Alarm Description ADSL/ADSL2+ port reactivation after line recovery.
Alarm Alarm
Alarm ID 0x0a300016 Event Warning
Type Severity
8-75
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested The port can be reactivated only after the activating command
Treatment has been executed.
Alarm Alarm
Alarm ID 0x0a300017 Event Major
Type Severity
ADSL/ADSL2+ port performance statistics reaches the
Alarm Description
threshold.
Alarm Parameter Frame, Slot, Port, Thres ID
1) Line deteriorated.
Alarm Cause
2) Alarm threshold is too low.
1) For cause one, check line quality.
Suggested 2) For cause two, check the correlative item according to
Treatment alarm threshold ID. Modify the threshold if the value is
not appropriate.
Alarm Alarm
Alarm ID 0x0a310019 Fault Major
Type Severity
Alarm Description ADSL/ADSL2+ chipset is not available.
8-76
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0a300050 Event Minor
Type Severity
Alarm Alarm
Alarm ID 0x0a300051 Event Minor
Type Severity
Alarm Alarm
Alarm ID 0x0a300052 Event Minor
Type Severity
Alarm Description ADSL/ADSL2+ No link detected.
Alarm Parameter Frame, Slot, Port
Alarm Cause ADSL/ADSL2+ no link detected.
8-77
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0a300090 Event Warning
Type Severity
The user deactivates the port or the port deactivates
Alarm Description
automatically.
Alarm Alarm
Alarm ID 0x0a300091 Event Warning
Type Severity
Alarm Description Users activate the port or the port activates automatically.
Alarm Alarm
Alarm ID 0x0a310092 Fault Major
Type Severity
Alarm Description G.SHDSL Port fault.
Alarm Parameter Frame, Slot, Port.
8-78
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
1) Reset chipset.
Suggested
2) Reset service board.
Treatment
3) Replace service board.
Alarm Alarm
Alarm ID 0x0a300093 Event Minor
Type Severity
Alarm Description G.SHDSL CO SNR overflows.
Alarm Alarm
Alarm ID 0x0a300094 Event Minor
Type Severity
8-79
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0a300095 Event Minor
Type Severity
Alarm Description G.SHDSL CO errored second overflow.
Alarm Parameter Frame, Slot, Port
G.SHDSL errored seconds at the central office reach or
Alarm Cause
exceed the threshold.
Suggested
Check the line quality.
Treatment
Alarm Alarm
Alarm ID 0x0a300096 Event Minor
Type Severity
Alarm Description G.SHDSL CO severely errored second overflow.
Suggested
Check the line quality.
Treatment
Alarm Alarm
Alarm ID 0x0a300097 Event Minor
Type Severity
Alarm Description G.SHDSL CO CRC overflows.
Alarm Parameter Frame, Slot, Port
G.SHDSL CRC errors at the central office reach or exceed the
Alarm Cause
threshold.
Suggested
Check the line quality.
Treatment
8-80
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0a300098 Event Minor
Type Severity
Alarm Description G.SHDSL CO loss of synchronization word overflows.
Alarm Parameter Frame, Slot, Port
G.SHDSL synchronous word loss second at the central office
Alarm Cause
reaches or exceeds the threshold.
Suggested
Check the line quality.
Treatment
Alarm Alarm
Alarm ID 0x0a300099 Event Minor
Type Severity
Alarm Description G.SHDSL CO unavailable second overflow.
Suggested
Check the line quality.
Treatment
Alarm Alarm
Alarm ID 0x0a30009d Event Minor
Type Severity
Alarm Description G.SHDSL CO detects no link on the port.
Alarm Parameter Frame, Slot, Port
G.SHDSL STU-R doesn't connect with CO or has no
Alarm Cause
response.
Suggested
Check if cable connection with STU-R is correct.
Treatment
8-81
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x10300002 Event Major
Type Severity
Alarm Alarm
Alarm ID 0x3c210000 Fault Major
Type Severity
Alarm Alarm
Alarm ID 0x3c300001 Event Major
Type Severity
Alarm Description SCU uplink-port change alarm.
Alarm Parameter SCU frameid, SCU slotid, ISU frameid, ISU slotid
ISU uplink-port failed, and caused uplink-port of SCU to
Alarm Cause
change.
8-82
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
Check ISU uplink-port.
Treatment
Alarm Alarm
Alarm ID 0x28010001 Fault Major
Type Severity
Alarm Description VLAN interface link down.
8-83
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x2b100000 Event Major
Type Severity
Alarm Description Fail to pass bandwidth CAC.
The first part of IP address, The second part of IP address,
Alarm Parameter The third part of IP address, The last part of IP address,
Frame ID, Slot ID, Root port ID
Alarm Cause The root port fails to pass the bandwidth CAC.
Suggested
No need to process
Treatment
Alarm Alarm
Alarm ID 0x29100001 Event Major
Type Severity
Alarm Description Data ring created.
Alarm Parameter FrameID, PortID,SlotID
Alarm Cause Port is in a loopback topology.
Suggested Check the topology which the port participate in, eliminate the
Treatment loopback condition, and then unblock the port.
Alarm Alarm
Alarm ID 0x29000002 Event Major
Type Severity
Alarm Description Port STP status changed to forwarding.
Alarm Parameter FrameID, PortID, SlotID
Alarm Cause Port is set to forwarding state.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x29000003 Event Major
Type Severity
8-84
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x29000004 Event Major
Type Severity
Alarm Description IPoA user source IP conflict.
Origin SlotID, Origin SlotID, Origin vpi, Origin vci, New
Alarm Parameter
SlotID, New PortID, New vpi, New vci, Conflict Srcip
Alarm Alarm
Alarm ID 0x29000005 Event Major
Type Severity
Alarm Alarm
Alarm ID 0x29000006 Event Major
Type Severity
Suggested
Add srcmac pool.
Treatment
8-85
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x02300003 Event Major
Type Severity
Alarm Alarm
Alarm ID 0x02300004 Event Major
Type Severity
Alarm Description Clock TDM source switch.
Alarm Parameter Clock SourceID
1) The port locking clock source is abnormal.
Alarm Cause
2) The clock source with higher priority recovered.
1) For cause one, check if the port with previous clock
reference operates well.
Suggested
2) For cause two, check if the external cable connects this
Treatment
port well.
3) For cause 2, there is no need to process.
Alarm Alarm
Alarm ID 0x02300006 Event Major
Type Severity
Alarm Description Fail to lock clock SDH source.
Alarm Parameter FrameID, SlotID, Clock SourceID
The former clock source port is abnormal, or the clock source
Alarm Cause
with higher priority recovered.
Suggested 1) Check if lead-in cable for clock reference connects well.
Treatment 2) Measure the input signal quality of the clock reference.
8-86
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x02300007 3` Major
Type Severity
Alarm Description Fail to lock clock TDM source.
Alarm Parameter FrameID, SlotID, Clock SourceID
Alarm Alarm
Alarm ID 0x0230001e Event Major
Type Severity
Alarm Description Clock SDH source is locked again.
Alarm Parameter FrameID, SlotID, Clock SourceID
Alarm Cause Clock resource locking recovered.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0230001f Event Major
Type Severity
Alarm Description Clock TDM source is locked again.
Alarm Alarm
Alarm ID 0x02310001 Fault Critical
Type Severity
Alarm Description Loss of clock source.
Alarm Parameter FrameID, SlotID, Clock SourceID
Alarm Cause Loss of clock source.
Suggested Check if the input cable for clock reference source connects
Treatment well.
8-87
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x02310002 Fault Critical
Type Severity
8-88
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Chapter 8 Analyzing and Handling Alarms
Alarm Alarm
Alarm ID 0x0231000a Fault Critical
Type Severity
Alarm Description Loss of BITS clock source
Alarm Parameter FrameID, SlotID, Bits Index
Alarm Cause There is no input on BITS clock port.
Suggested Check if the input cable for BITS clock reference source
Treatment connects well.
Suggested
No need to process.
Treatment
Alarm Alarm
Alarm ID 0x0230001b Event Major
Type Severity
Clock subboard type of active board is different from that of
Alarm Description
standby board.
Alarm Parameter -
Clock subboard type of the active and standby boards is
Alarm Cause
inconsistent.
8-89
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
9-1
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
There are multiple methods for maintaining the MA5600 according to different
classifications.
I. By implementation
z Normal maintenance
With normal maintenance methods, such as querying the operating parameters
and port states of the MA5600, the maintenance personnel can analyze the
operation conditions of the devices.
z Abnormal maintenance
With abnormal maintenance methods, the maintenance personnel can check
whether the performance of the MA5600 has weakened or the system function
has aged.
For example, to avoid occurrence of faults in the alarm system, the maintenance
personnel can set some faults purposely to observe whether the MA5600 can
report alarms correctly.
z Daily maintenance
Daily maintenance means daily required maintenance of the MA5600. Through
routine maintenance, the maintenance personnel can learn the operation of the
MA5600 at all times, so as to find and solve problems in time.
Record in detail the problems found in routine maintenance to provide basis for
locating and solving these problems in time.
z Periodical routine maintenance
Periodical routine maintenance means periodical maintenance of the MA5600.
Through periodical maintenance, the maintenance personnel can learn the
long-term performance of the MA5600. Periodical routine maintenance consists of
monthly, quarterly, and yearly maintenance.
z Unexpected maintenance
Unexpected maintenance means maintenance resulting from device faults and
network adjustments, such as maintenance required for faults reported by
subscribers, damages to MA5600, and line faults.
9-2
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
The following introduces in brief the purposes of different maintenance forms. For the
formats of this forms, refer to "Appendix B Frequently Used Forms for Routine
Maintenance and Troubleshooting".
I. Log
This form is used to record the routing performance of the MA5600. It contains such
items as running sate and running environment of the MA5600.
Refer to “9.2 Guide to Daily Equipment Maintenance” to learn how to fill in this form.
This form lists the monthly maintenance items for the MA5600, such as check of the
main control system and running environment of the MA5600.
Refer to “9.3 Guide to Monthly Equipment Maintenance” to learn how to fill in this form.
This form lists the quarterly maintenance items for the MA5600, such as check of the
main control system, the electromechanic system, and the grounding system.
Refer to “9.4 Guide to Quarterly Equipment Maintenance to learn how to fill in this form.
This form lists the yearly maintenance items for the MA5600, such as active/standby
switchover of the main control system, and check grounding of the equipment.
Refer to “9.5 Guide to Yearly Equipment Maintenance” to learn how to fill in this form.
This form is used to record daily non-serious faults occurred suddenly, as the basis for
troubleshooting.
9-3
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
The daily maintenance of the MA5600 mainly includes maintenance of the main control
system, the alarm system, all services, as well as the running environment of the
MA5600. The following introduces how to maintain them.
Table 9-1 Guide to daily equipment maintenance of the main control system
9-4
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
9-5
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
9-6
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
9-7
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
The monthly maintenance of the MA5600 mainly includes maintenance of the main
control system, the running environment, and the electromechanical system of the
MA5600. The following introduces how to maintain them.
9-8
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
9-9
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
Maintenance
Operation guide Reference index
item
Check whether the system clock source is
Querying the Use the display clock source
the same as that in the latest record. If not,
system clock command to query the system
check the cause and the modifier, and
source clock source.
whether the change will affect the service.
Check whether the clock mode is the same
Use the display clock mode
Querying the as that in the latest record. If not, check the
command to query the system
clock mode cause and the modifier, and whether the
clock mode.
change will affect the service.
9-10
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
Maintenance
Maintenance guide Reference index
item
9-11
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
Caution:
z Before summer is coming, maintain the fan system of the equipment, especially the
fan system of transmission equipment and the power module as well as possible.
z Before lightning storm season is coming, pay attention to maintenance of the
lightning protection system and the power system. During the maintenance process,
take safety actions and avoid short circuiting accidents.
Maintenance
Operation guide Reference index
item
z The grounding system complies with the
z All connections are
Broadband Equipment Grounding
safe and reliable, and
Specifications.
the connection joint is
z When there is a lightning protection grounding free of corrosion and
cable busbar at the button of the cabinet, check oxidation.
whether the lightning protection unit’s
z The grounding cables
Grounding grounding cable busbar, the cabinet's
are not aged.
cable grounding pole (PGND, BGND, and LGND),
connection and the equipment room's grounding cable z The grounding cable
busbar connections are safe and reliable. busbar is free of
corrosion and
z When there is no lightning protection
oxidation. The
grounding cable busbar at the bottom of the
anti-corrosion
cabinet, check whether the distribution box and
processing for it is
grounding cable (BGND and PGND)
done well.
connections are safe and reliable.
Caution:
Before lightning storm season is coming, pay attention to maintenance of the grounding
system of the devices. Protect personal safety and equipment safety in maintenance
operations.
9-12
Troubleshooting Manual Chapter 9 Guide to Routine Equipment
SmartAX MA5600/MA5603 Multi-service Acess Module Maintenance
Maintenance
Operation guide Reference index
item
Observe the switchover process:
Reset the active 1) Reset the active SCU board.
Active/standby
SCU board, and 2) The standby SCU board is changed into the active
switchover of
switch the standby one, and vice versa.
the main
SCU board to the
control system 3) Except short disruption of upstream services
active one.
through the original active SCU board, other
services are normal.
Caution:
z The yearly maintenance of the active/standby SCU board switchover must be done
during the periods in which the service traffic volume is small.
z Before the active/standby SCU board switchover, ensure that the NMS terminal and
its hardware work normally, and back up the essential data.
z The interval between two switchovers must be 30 minutes or longer. Frequent
switchover is strictly prohibited.
9-13
Troubleshooting Manual Appendix A List of Fault Information
SmartAX MA5600/MA5603 Multi-service Acess Module to Be Collected
A-1
Troubleshooting Manual Appendix A List of Fault Information
SmartAX MA5600/MA5603 Multi-service Acess Module to Be Collected
A-2
Troubleshooting Manual Appendix A List of Fault Information
SmartAX MA5600/MA5603 Multi-service Acess Module to Be Collected
A-3
Troubleshooting Manual Appendix A List of Fault Information
SmartAX MA5600/MA5603 Multi-service Acess Module to Be Collected
A-4
Troubleshooting Manual Appendix A List of Fault Information
SmartAX MA5600/MA5603 Multi-service Acess Module to Be Collected
A-5
Troubleshooting Manual Appendix A List of Fault Information
SmartAX MA5600/MA5603 Multi-service Acess Module to Be Collected
A-6
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
Maintenance
Maintenance item Inspection result Abnormalities Operator
type
Is the fiber connection
Main control Querying the fiber normal?
system connection state □ Yes
□ No
B-1
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
Maintenance
Maintenance item Inspection result Abnormalities Operator
type
Has the number of
Querying whether PVCs/PVPs been
the number of PVCs changed?
has changed □ Yes
□ No
Are the queried
system prompted the
Querying the system same as the planned
prompts ones?
□ Yes
□ No
Are there any critical
Querying critical alarms?
alarms □ Yes
□ No
Alarm system
Are there any major
Querying major alarms?
alarms □ Yes
□ No
B-2
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
Maintenance
Maintenance item Inspection result Abnormalities Operator
type
Are there any traffic
overload or
Querying LAN negotiation failure
service alarms alarms?
□ Yes
□ No
Is the configuration of
Querying the IMA group
configuration of an correct?
IMA group □ Yes
IMA services □ No
Is the IMA group
Querying the running operable?
state of an IMA group □ Yes
□ No
Tools, meters,
and
documentation
B-3
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
Maintenance
Maintenance item Inspection result Abnormalities Operator
type
Verified by team
leader
B-4
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
□ Normal □
Temperature
Abnormal
□ Normal □
Running environment Humidity
Abnormal
□ Normal □
Cleanliness
Abnormal
Description of
outstanding issues
B-5
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
B-6
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
B-7
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
□ Normal
Grounding system Earth resistance test
□ Abnormal
Verified by team
leader
B-8
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
B-9
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
Occurrence
Troubleshooting time
Date
On-duty
Troubleshooter
personnel
□ Subscriber's complaint
Classification □ Daily maintenance
of fault Basic information about fault sources
sources □ Alarm information
□ Other sources
Fault description
B-10
Troubleshooting Manual Appendix B Frequently Used Forms
SmartAX MA5600/MA5603 Multi-service Acess Module for Routine Maintenance and
Troubleshooting
Is the
Complaining Required device in □ Yes
time response time warranty □ No
period?
Verifier:
Department signature and
stamp:
Troubleshooter:
Date:
Note: Department signature and stamp are signature and stamp of the department in charge of
operation and maintenance at the municipal or county level
B-11
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
A
AAL1 ATM Adaptation Layer 1
AAL5 ATM Adaptation Layer 5
ABR Available Bit Rate
ACM Self-adaptive Clock Method
ADSL Asymmetric Digital Subscriber Line
AFE Analog Front End
AOC ADSL Overhead Control Channel
ATM Asynchronous Transfer Mode
ATU ADSL Transceiver Unit
ATU-C ADSL Transceiver Unit at the Central Office end
ATU-R ADSL transceiver unit at the Remote end
B
BAS Broadband Access Server
Bc committed burst size
Be excess burst size
BECN Backward explicit congestion notification
BITS Building Integrated Timing Supply System
BRI Basic Rate Interface
BSP Board Support Packet
C
CAC Connection Admission Control
CAM Content Addressable Memory
CAP Carrierless Amplitude Phase Modulation
CAR Committed Access Rate
CAS Channel Associated Signaling
CBR Constant Bit Rate
CCS Common Control Signaling
CELL BUS Cell Bus
CES Circuit Emulation Service
C-1
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
C-2
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
C-3
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
C-4
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
C-5
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
C-6
Troubleshooting Manual Appendix C Acronyms and
SmartAX MA5600/MA5603 Multi-service Acess Module Abbreviations
VP Virtual Path
VPC Virtual Path Connection
VPCI Virtual Path Connection Identifier
VPI Virtual Path Identifier
VPL Virtual Path Link
VPDN Virtual Private Dial Network
VPN Virtual Private Network
VPRN Virtual Private Routed Network
VS Virtual Switch
VSI Virtual Switch Interface
VToA Voice Transfer over ATM
W
WAN Wide Area Network
WSA Wireless Service Access
WWW World Wide Web
X
xDSL x Digital Subscriber Line
Y
Z
C-7
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Index
Index
i-1
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Index
equipment maintenance form, 9-3 low downstream rate, low upstream rate, 4-18
erase alarm, 8-11 low Internet access rate
ESD wrist strap, 2-10 ADSL service, 4-9
exclusive method, 1-7 inconsistent software/hardware setting, 4-12
incorrect ADSL channel mode, 4-18
F virus-affected PC, 4-21
fault
analyzing, 1-5 M
eliminating, 1-6 maintenance and troubleshooting form, B-1
locating, 1-5 meter test, 1-7
fault locating process monthly maintenance
ADSL/ADSL2+ service, 4-4 electromechanical system, 9-9
Ethernet service, 6-6 main control system, 9-8
multicast service, 7-2 running environment, 9-9
SHDSL service, 5-3 monthly maintenance record form, 9-3, B-5
FE optical power, specifications, 2-24 multicast
fiber loopback, 2-2 features, 7-1
network topology, 7-2
G multicast technology, 7-1
inverse alarm
active/standby board communication, 8-15 O
active/standby switchover failure, 8-13 office data modification record, 9-4, B-9
active/standby switchover success, 8-12 offline
board software version inconsistency, 8-14 ADSL service, 4-10
system resetting upon abnormal switchover, 8-14 improper interleaved depth, 4-19
wrong wiring connection of SPL, 4-15
L optical power, measuring, 2-21
i-2
Troubleshooting Manual
SmartAX MA5600/MA5603 Multi-service Acess Module Index
i-3