You are on page 1of 137

Chapter 1 General Procedures for Troubleshooting .................................... 1.1 Overview ................................................................................................ 1.2 Finding out a Fault .................................................................................. 1.2.

1 Finding out Phenomena of a Fault ................................................. 1.2.2 Finding out Human Factors............................................................ 1.2.3 Working out Subsequent Processing Procedures ......................... 1.3 Collecting Detailed Information about a Fault ........................................ 1.3.1 Collecting Detailed Fault-related Equipment Information............... 1.3.2 Collecting Detailed Networking Information ................................... 1.3.3 Collecting Upstream and Downstream Equipment Information ..... 1.4 Troubleshooting ...................................................................................... 1.4.1 Overview ........................................................................................ 1.4.2 Determining Fault Type.................................................................. 1.4.3 Frequently-used Troubleshooting Methods ................................... Chapter 2 Physical Connection Troubleshooting ........................................ 2.1 Transmission Interconnection Fault ....................................................... 2.1.1 Introduction to Principles ................................................................ 2.1.2 Frequently-used Troubleshooting Methods ................................... 2.1.3 Fault Case Study ........................................................................... 2.2 E1 Line Connection Fault ....................................................................... 2.2.1 Introduction to Principles ................................................................ 2.2.2 Frequently-used Troubleshooting Methods ................................... 2.2.3 Fault Case Study ........................................................................... 2.3 ATM Optical Interface Interconnection Fault .......................................... 2.3.1 Introduction to Principles ................................................................ 2.3.2 Frequently-used Troubleshooting Methods ................................... 2.4 Ethernet Port Interconnection Fault ........................................................ 2.4.1 Introduction to Principles ................................................................ 2.4.2 Frequently-used Troubleshooting Methods ................................... Chapter 3 Narrowband Service Troubleshooting ......................................... 3.1 Overview ................................................................................................ 3.2 Narrowband Voice Service ..................................................................... 3.2.1 Frequently-used Troubleshooting Methods ................................... 3.2.2 Fault Case Study ........................................................................... 3.3 MTA Service ........................................................................................... 3.3.1 Introduction to Principles ................................................................ 3.3.2 Frequently-used Troubleshooting Methods ................................... 3.3.3 Fault Case Study ........................................................................... 3.4 HSL Service ...........................................................................................

1-1 1-1 1-2 1-2 1-4 1-5 1-5 1-6 1-7 1-9 1-10 1-10 1-10 1-11 2-1 2-1 2-1 2-1 2-3 2-4 2-4 2-5 2-8 2-15 2-15 2-16 2-18 2-18 2-21 3-1 3-1 3-1 3-1 3-7 3-11 3-11 3-12 3-13 3-14

3.4.1 Introduction to Principles ................................................................ 3.4.2 Frequently-used Troubleshooting Methods ................................... 3.4.3 Fault Case Study ........................................................................... Chapter 4 Broadband Service Troubleshooting ........................................... 4.1 Overview ................................................................................................ 4.1.1 Broadband Service Classification .................................................. 4.1.2 Application of Cell Statistics in Fault Location ............................... 4.2 BAS Service ........................................................................................... 4.2.1 Introduction to Principles ................................................................ 4.2.2 Frequently-used Troubleshooting Methods ................................... 4.2.3 Fault Case Study ........................................................................... 4.3 L2 Transparent Transmission Service .................................................... 4.3.1 Introduction to Principles ................................................................ 4.3.2 Frequently-used Troubleshooting Methods ................................... 4.4 ADSL Service ......................................................................................... 4.4.1 Introduction to Principles ................................................................ 4.4.2 Frequently-used Troubleshooting Methods ................................... 4.4.3 Fault Case Study ........................................................................... 4.5 Flow Control ........................................................................................... 4.5.1 Introduction to Principles ................................................................ 4.5.2 Frequently-used Troubleshooting Methods ................................... 4.6 Circuit Emulation Service ....................................................................... 4.6.1 Introduction to Principles ................................................................ 4.6.2 Frequently-used Troubleshooting Methods ................................... 4.6.3 Fault Case Study ........................................................................... Chapter 5 Other Troubleshooting .................................................................. 5.1 PV8/PV4 Board Loading ........................................................................ 5.1.1 Introduction to Principles ................................................................ 5.1.2 Frequently-used Troubleshooting Methods ................................... 5.1.3 Fault Case Study ........................................................................... 5.2 Board Registration .................................................................................. 5.2.1 Introduction to Principles ................................................................ 5.2.2 Frequently-used Troubleshooting Methods ................................... 5.2.3 Fault Case Study ........................................................................... 5.3 Environment Monitoring ......................................................................... 5.3.1 Introduction to Principles ................................................................ 5.3.2 Frequently-used Troubleshooting Methods ................................... 5.3.3 Fault Case Study ........................................................................... Chapter 6 Alarm Analysis and Processing ...................................................

3-14 3-16 3-20 4-1 4-1 4-1 4-1 4-3 4-3 4-6 4-9 4-12 4-12 4-12 4-14 4-14 4-15 4-21 4-24 4-24 4-24 4-25 4-25 4-25 4-27 5-1 5-1 5-1 5-4 5-6 5-9 5-9 5-10 5-11 5-13 5-13 5-14 5-15 6-1

6.1 Analysis and Processing of System Alarms ........................................... 6.1.1 Can Not Lock SDH Clock Source .................................................. 6.1.2 Can Not Lock TDM Clock Source .................................................. 6.1.3 Board Fault .................................................................................... 6.1.4 Loss of Clock Source ..................................................................... 6.1.5 Abnormal Clock Subboard Communication ................................... 6.1.6 Loss of BITS Clock Source ............................................................ 6.1.7 Inconsistent Active and Standby Board Software Version ............. 6.1.8 Abnormal Communication of Active Board with Standby Board .... 6.2 Analysis and Processing of E1 Link Alarms ........................................... 6.2.1 CRC4 Error of PCM ....................................................................... 6.2.2 PCM Slip Code .............................................................................. 6.2.3 PCM Line Disconnection ................................................................ 6.2.4 Remote Frame Alarm of PCM ........................................................ 6.2.5 Loss of Multiframe Alignment of PCM ............................................ 6.2.6 Loss of Frame Alignment of PCM .................................................. 6.2.7 E-Bit Remote Alarm Indication of PCM .......................................... 6.2.8 Abnormal PCM Line ....................................................................... 6.3 Analysis and Processing of Optical Port Alarms .................................... 6.3.1 Abnormal Optical Port .................................................................... 6.3.2 Receiving Signal Deterioration Alarm ............................................ 6.3.3 No Optical Signal at Port ................................................................ 6.3.4 Optical Port Fault ........................................................................... 6.4 Analysis and Processing of LAN Alarms ................................................ 6.4.1 Peer End Not Supporting Auto-Negotiation ................................... 6.5 Analysis and Processing of Narrowband Voice Alarms ......................... 6.5.1 Abnormal Frame ............................................................................ 6.5.2 Insufficient TS Resources .............................................................. 6.5.3 Local Port Blocking Indication ........................................................ 6.5.4 Peer End Port Blocking Indication ................................................. 6.5.5 Port Locking Indication ................................................................... 6.5.6 V5 Interface Interruption ................................................................ 6.5.7 Receiving V5 Protection Switching Command ............................... 6.5.8 Originating Protection Switching Request ...................................... 6.5.9 Link Blocking .................................................................................. 6.5.10 V5 Interface Restart Failure ......................................................... 6.5.11 V5 Link ID Failure ........................................................................ 6.6 Analysis and Processing of SPC Alarms................................................ 6.6.1 Semi-permanent Connection Interruption ...................................... 6.7 Analysis and Processing of MTA Alarms ............................................... 6.7.1 Abnormal MTA Communication .....................................................

6-1 6-1 6-2 6-2 6-2 6-3 6-3 6-3 6-3 6-4 6-4 6-4 6-4 6-5 6-5 6-5 6-6 6-6 6-6 6-6 6-7 6-7 6-7 6-8 6-8 6-8 6-8 6-8 6-9 6-9 6-9 6-10 6-10 6-10 6-11 6-11 6-11 6-12 6-12 6-13 6-13

6.7.2 MTA B1/B2 Channel Local End LFA .............................................. 6.7.3 MTA B1/B2 Channel Peer End LFA ............................................... 6.7.4 Equipment Connected with MTA Data Port Not Ready ................. 6.8 Analysis and Processing of HSL Alarms ................................................ 6.8.1 LFA of FE1 Port of HSL Board ....................................................... 6.8.2 Loss of Signal of FE1 Port of HSL Board....................................... 6.9 Analysis and Processing of BAS Alarms ................................................ 6.9.1 Accounting Server Communication Interruption ............................ 6.9.2 Authentication Server Communication Interruption ....................... 6.9.3 Bill Pool Overflow ........................................................................... 6.9.4 Bill Pool Full ................................................................................... 6.9.5 Flash Bill Pool Full ......................................................................... 6.9.6 Flash Card Damaged or Not in Position ........................................ 6.9.7 TFTP Server Having No Route or Unreachable ............................ 6.9.8 IPoA User Creation Failure ............................................................ 6.10 Analysis and Processing of CES Alarms .............................................. 6.10.1 LOS of CES E1 Line .................................................................... 6.10.2 LFA of CES E1 Line ..................................................................... 6.10.3 CES E1 Line Remote Alarm ........................................................ 6.10.4 E1 Line CRC4 Alarm .................................................................... Appendix Abbreviations and Acronyms .......................................................

6-13 6-13 6-14 6-14 6-14 6-14 6-15 6-15 6-15 6-15 6-16 6-16 6-16 6-16 6-17 6-17 6-17 6-17 6-18 6-18 1

HUAWEI

HONET Integrated Services Access Network Troubleshooting Manual V600R003

HONET Integrated Services Access Network Troubleshooting Manual


Manual Version Product Version BOM T2-050396-20031114-C-6.30 V600R003 31033296

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office, customer care center or company headquarters.

Huawei Technologies Co., Ltd.


Address: Administration Building, Huawei Technologies Co., Ltd., Bantian, Longgang District, Shenzhen, P. R. China Postal Code: 518129 Website: http://www.huawei.com Email: support@huawei.com

Copyright 2003 Huawei Technologies Co., Ltd.

All Rights Reserved


No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, SoftX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX are trademarks of Huawei Technologies Co., Ltd. All other trademarks 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.

About This Manual


Version
The manual applies to the HONET Integrated Services Access Network V600R003.

Related Manuals
The following manuals provide more information about the MD5500.
Manual HONET Integrated Services Access Network Technical Manual HONET MD5500B Multi-service Distribution Module Operation Manual HONET MD5500B Multi-service Distribution Module Command Reference HONET MD5500B Multi-service Distribution Module Installation Manual HONET MD5500 Multi-service Distribution Module Safety Manual HONET Integrated Services Access Network Troubleshooting Manual Documentation CD Description It presents a comprehensive introduction to the HONET Integrated Services Access Network. It discusses the maintenance and data configuration for the MD5500. It elaborates on all commands supported by the system. The manual is contained in the documentation CD only. It is a guide to install the MD5500B. It lists the safety information needed to install and maintain the equipment. It describes commonly used troubleshooting methods. The CD contains the set of manuals.

Organization of the Manual


The manual introduces the general procedure for handling a problem and detailed troubleshooting methods for common failures. There are six chapters and one appendix in the manual. Chapter 1 General Procedures for Troubleshooting introduces the overall procedure for handling a problem. Chapter 2 Physical Connection Troubleshooting details the troubleshooting practices for transmission interconnection fault, E1 connection fault and ATM optical interface connection fault.

Chapter 3 Narrowband Service Troubleshooting elaborates on troubleshooting practices for fault of narrowband services, including voice service, HSL service and MTA service. Chapter 4 Broadband Service Troubleshooting discusses the troubleshooting practices for fault of broadband services, including BAS service, BSL service and CES service. Chapter 5 Other Troubleshooting focuses on the troubleshooting practices for PV8 software loading, board registration and environment monitoring. Chapter 6 Alarm Analysis and Processing describes various alarms of the MD5500. Appendix lists the abbreviations and acronyms used in this publication.

Intended Readers
The manual is intended for the following readers:
z z z

Access network system engineers HONET maintenance engineers HONET technical support engineers

Conventions
This manual uses the following conventions:

I. General conventions
Convention Arial Arial Narrow Boldface Courier New Normal paragraphs are in Arial. Warnings, Cautions, Notes and Tips are in Arial Narrow. Headings are in Boldface. Terminal Display is in Courier New. Description

II. Command conventions


Convention Boldface italic [] { x | y | ... } Description The keywords of a command line are in Boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected.

Convention Boldface [ x | y | ... ] { x | y | ... } * [ x | y | ... ] *

Description The keywords of a command line are in Boldface. Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected. Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected. Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected.

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

Caution, Warning, Danger: Means reader be extremely careful during the operation. Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Troubleshooting Manual HONET Integrated Services Access Network

Table of Contents

Table of Contents
Chapter 1 General Procedures for Troubleshooting ................................................................. 1-1 1.1 Overview ............................................................................................................................ 1-1 1.2 Finding out a Fault ............................................................................................................. 1-2 1.2.1 Finding out Phenomena of a Fault .......................................................................... 1-2 1.2.2 Finding out Human Factors..................................................................................... 1-4 1.2.3 Working out Subsequent Processing Procedures .................................................. 1-5 1.3 Collecting Detailed Information about a Fault.................................................................... 1-5 1.3.1 Collecting Detailed Fault-related Equipment Information ....................................... 1-6 1.3.2 Collecting Detailed Networking Information ............................................................ 1-7 1.3.3 Collecting Upstream and Downstream Equipment Information .............................. 1-9 1.4 Troubleshooting ............................................................................................................... 1-10 1.4.1 Overview ............................................................................................................... 1-10 1.4.2 Determining Fault Type......................................................................................... 1-10 1.4.3 Frequently-used Troubleshooting Methods .......................................................... 1-11 Chapter 2 Physical Connection Troubleshooting...................................................................... 2-1 2.1 Transmission Interconnection Fault................................................................................... 2-1 2.1.1 Introduction to Principles......................................................................................... 2-1 2.1.2 Frequently-used Troubleshooting Methods ............................................................ 2-1 2.1.3 Fault Case Study..................................................................................................... 2-3 2.2 E1 Line Connection Fault .................................................................................................. 2-4 2.2.1 Introduction to Principles......................................................................................... 2-4 2.2.2 Frequently-used Troubleshooting Methods ............................................................ 2-5 2.2.3 Fault Case Study..................................................................................................... 2-8 2.3 ATM Optical Interface Interconnection Fault ................................................................... 2-15 2.3.1 Introduction to Principles....................................................................................... 2-15 2.3.2 Frequently-used Troubleshooting Methods .......................................................... 2-16 2.4 Ethernet Port Interconnection Fault ................................................................................. 2-18 2.4.1 Introduction to Principles....................................................................................... 2-18 2.4.2 Frequently-used Troubleshooting Methods .......................................................... 2-21 Chapter 3 Narrowband Service Troubleshooting ...................................................................... 3-1 3.1 Overview ............................................................................................................................ 3-1 3.2 Narrowband Voice Service ................................................................................................ 3-1 3.2.1 Frequently-used Troubleshooting Methods ............................................................ 3-1 3.2.2 Fault Case Study..................................................................................................... 3-7 3.3 MTA Service .................................................................................................................... 3-11 3.3.1 Introduction to Principles....................................................................................... 3-11 3.3.2 Frequently-used Troubleshooting Methods .......................................................... 3-12
i

Troubleshooting Manual HONET Integrated Services Access Network

Table of Contents

3.3.3 Fault Case Study................................................................................................... 3-13 3.4 HSL Service ..................................................................................................................... 3-14 3.4.1 Introduction to Principles....................................................................................... 3-14 3.4.2 Frequently-used Troubleshooting Methods .......................................................... 3-16 3.4.3 Fault Case Study................................................................................................... 3-20 Chapter 4 Broadband Service Troubleshooting ........................................................................ 4-1 4.1 Overview ............................................................................................................................ 4-1 4.1.1 Broadband Service Classification ........................................................................... 4-1 4.1.2 Application of Cell Statistics in Fault Location ........................................................ 4-1 4.2 BAS Service....................................................................................................................... 4-3 4.2.1 Introduction to Principles......................................................................................... 4-3 4.2.2 Frequently-used Troubleshooting Methods ............................................................ 4-6 4.2.3 Fault Case Study..................................................................................................... 4-9 4.3 L2 Transparent Transmission Service............................................................................. 4-12 4.3.1 Introduction to Principles....................................................................................... 4-12 4.3.2 Frequently-used Troubleshooting Methods .......................................................... 4-12 4.4 ADSL Service................................................................................................................... 4-14 4.4.1 Introduction to Principles....................................................................................... 4-14 4.4.2 Frequently-used Troubleshooting Methods .......................................................... 4-15 4.4.3 Fault Case Study................................................................................................... 4-21 4.5 Flow Control..................................................................................................................... 4-24 4.5.1 Introduction to Principles....................................................................................... 4-24 4.5.2 Frequently-used Troubleshooting Methods .......................................................... 4-24 4.6 Circuit Emulation Service................................................................................................. 4-25 4.6.1 Introduction to Principles....................................................................................... 4-25 4.6.2 Frequently-used Troubleshooting Methods .......................................................... 4-25 4.6.3 Fault Case Study................................................................................................... 4-27 Chapter 5 Other Troubleshooting................................................................................................ 5-1 5.1 PV8/PV4 Board Loading.................................................................................................... 5-1 5.1.1 Introduction to Principles......................................................................................... 5-1 5.1.2 Frequently-used Troubleshooting Methods ............................................................ 5-4 5.1.3 Fault Case Study..................................................................................................... 5-6 5.2 Board Registration ............................................................................................................. 5-9 5.2.1 Introduction to Principles......................................................................................... 5-9 5.2.2 Frequently-used Troubleshooting Methods .......................................................... 5-10 5.2.3 Fault Case Study................................................................................................... 5-11 5.3 Environment Monitoring................................................................................................... 5-13 5.3.1 Introduction to Principles....................................................................................... 5-13 5.3.2 Frequently-used Troubleshooting Methods .......................................................... 5-14 5.3.3 Fault Case Study................................................................................................... 5-15 Chapter 6 Alarm Analysis and Processing................................................................................. 6-1 6.1 Analysis and Processing of System Alarms ...................................................................... 6-1
ii

Troubleshooting Manual HONET Integrated Services Access Network

Table of Contents

6.1.1 Can Not Lock SDH Clock Source ........................................................................... 6-1 6.1.2 Can Not Lock TDM Clock Source ........................................................................... 6-2 6.1.3 Board Fault.............................................................................................................. 6-2 6.1.4 Loss of Clock Source .............................................................................................. 6-2 6.1.5 Abnormal Clock Subboard Communication ............................................................ 6-3 6.1.6 Loss of BITS Clock Source ..................................................................................... 6-3 6.1.7 Inconsistent Active and Standby Board Software Version...................................... 6-3 6.1.8 Abnormal Communication of Active Board with Standby Board............................. 6-3 6.2 Analysis and Processing of E1 Link Alarms ...................................................................... 6-4 6.2.1 CRC4 Error of PCM ................................................................................................ 6-4 6.2.2 PCM Slip Code........................................................................................................ 6-4 6.2.3 PCM Line Disconnection......................................................................................... 6-4 6.2.4 Remote Frame Alarm of PCM................................................................................. 6-5 6.2.5 Loss of Multiframe Alignment of PCM..................................................................... 6-5 6.2.6 Loss of Frame Alignment of PCM ........................................................................... 6-5 6.2.7 E-Bit Remote Alarm Indication of PCM................................................................... 6-6 6.2.8 Abnormal PCM Line ................................................................................................ 6-6 6.3 Analysis and Processing of Optical Port Alarms ............................................................... 6-6 6.3.1 Abnormal Optical Port ............................................................................................. 6-6 6.3.2 Receiving Signal Deterioration Alarm ..................................................................... 6-7 6.3.3 No Optical Signal at Port......................................................................................... 6-7 6.3.4 Optical Port Fault..................................................................................................... 6-7 6.4 Analysis and Processing of LAN Alarms ........................................................................... 6-8 6.4.1 Peer End Not Supporting Auto-Negotiation ............................................................ 6-8 6.5 Analysis and Processing of Narrowband Voice Alarms..................................................... 6-8 6.5.1 Abnormal Frame...................................................................................................... 6-8 6.5.2 Insufficient TS Resources ....................................................................................... 6-8 6.5.3 Local Port Blocking Indication ................................................................................. 6-9 6.5.4 Peer End Port Blocking Indication........................................................................... 6-9 6.5.5 Port Locking Indication............................................................................................ 6-9 6.5.6 V5 Interface Interruption........................................................................................ 6-10 6.5.7 Receiving V5 Protection Switching Command...................................................... 6-10 6.5.8 Originating Protection Switching Request............................................................. 6-10 6.5.9 Link Blocking ......................................................................................................... 6-11 6.5.10 V5 Interface Restart Failure ................................................................................ 6-11 6.5.11 V5 Link ID Failure................................................................................................ 6-11 6.6 Analysis and Processing of SPC Alarms......................................................................... 6-12 6.6.1 Semi-permanent Connection Interruption ............................................................. 6-12 6.7 Analysis and Processing of MTA Alarms......................................................................... 6-13 6.7.1 Abnormal MTA Communication ............................................................................ 6-13 6.7.2 MTA B1/B2 Channel Local End LFA..................................................................... 6-13 6.7.3 MTA B1/B2 Channel Peer End LFA...................................................................... 6-13

iii

Troubleshooting Manual HONET Integrated Services Access Network

Table of Contents

6.7.4 Equipment Connected with MTA Data Port Not Ready ........................................ 6-14 6.8 Analysis and Processing of HSL Alarms ......................................................................... 6-14 6.8.1 LFA of FE1 Port of HSL Board.............................................................................. 6-14 6.8.2 Loss of Signal of FE1 Port of HSL Board.............................................................. 6-14 6.9 Analysis and Processing of BAS Alarms ......................................................................... 6-15 6.9.1 Accounting Server Communication Interruption ................................................... 6-15 6.9.2 Authentication Server Communication Interruption .............................................. 6-15 6.9.3 Bill Pool Overflow .................................................................................................. 6-15 6.9.4 Bill Pool Full........................................................................................................... 6-16 6.9.5 Flash Bill Pool Full................................................................................................. 6-16 6.9.6 Flash Card Damaged or Not in Position ............................................................... 6-16 6.9.7 TFTP Server Having No Route or Unreachable ................................................... 6-16 6.9.8 IPoA User Creation Failure ................................................................................... 6-17 6.10 Analysis and Processing of CES Alarms....................................................................... 6-17 6.10.1 LOS of CES E1 Line ........................................................................................... 6-17 6.10.2 LFA of CES E1 Line ............................................................................................ 6-17 6.10.3 CES E1 Line Remote Alarm................................................................................ 6-18 6.10.4 E1 Line CRC4 Alarm........................................................................................... 6-18 Appendix Abbreviations and Acronyms ........................................................................................ 1

iv

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

Chapter 1 General Procedures for Troubleshooting


1.1 Overview
The HONET mainly consists of the MD5500 and the UA5000. The former is located at the Central Office end and gets interconnected with the backbone layer equipment to implement protocol processing and service crossing, converge various service flow and distribute them to different backbone network such as PSTN, DDN, ATM and IP. The latter is located at the remote end to provide various subscriber interfaces to access the integrated services. The general procedure for troubleshooting is shown in Figure 1-1, and this chapter will describe it in details based on this figure.

Finding out whether the fault occurs suddenly, after the upgrade, or during a new deployment Finding out fault range Collecting details about fault Finding out a fault Finding out whether alarms are reported to Console Finding out board indicator status

Collecting board configuration Collecting equipment version information Conducting statistic analysis Collecting equipment configuration information Collecting detailed LOG information Collecting equipment alarm information Troubleshooting

Analyzing configuration data

Performing instrument and meter test and analysis

Finding out equipment version

Performing loopback test Finding out service application type on the equipment Finding out status of the relevant interface Finding out the statuses of upstream and downstream equipment Finding out human operations before and after the fault occurs Collecting detailed networking information Collecting information about interconnected equipment interface Comparing, exchanging, and analyzing

Collecting detailed alarm information of interconnected equipment

Figure 1-1 General procedure for troubleshooting

1-1

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

1.2 Finding out a Fault


Once a fault occurs, the engineer should first of all find out its phenomena. By this, the engineer is able to judge the detailed information about the fault, such as severity, complexity, and the incidence, so as to further determine if it is necessary to collect the detailed information about the fault on site, and determine what the key information is. This judgment will have a direct influence on the subsequent processing of the fault, and plays a very important role in troubleshooting. Accordingly, the engineer is required to find out phenomena of the fault completely and correctly.

1.2.1 Finding out Phenomena of a Fault


I. Finding out the occurrence time of a fault
It is required to find out the occurrence time of a fault, for example, it suddenly occurs in the normal running status of the equipment, occurs after the upgrade, or occurs during the new deployment. Besides, it is required to find out and record the operations that have ever been made, and view the log.

II. Finding out fault scope


It is required to find out the fault scope, that is, whether this fault occurs to all access subscribers of the MD5500, or part of the access subscribers. If this fault occurs to all access subscribers of the MD5500, it should be further found out that whether the fault occurs to other equipment or subscribers that are connected to the same upper layer equipment. If this fault only occurs to part of the access subscribers of the MD5500, the following three points should be made clear: First, what the service category of these subscribers is, and whether this fault occurs to subscribers of other service categories. Second, whether the access mode and service processing board that are used by these subscribers are the same with those of other subscribers (whose service is in normal status), Third, what the distribution state of these subscribers on the downstream access equipment is.

III. Finding out status of console


Find out whether the console has received alarms. If no alarm is received, then check whether the alarm output switch is enabled. View alarm history records to know the alarm information level, and judge whether the alarm is associated with the actual fault.

1-2

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

IV. Finding out status of each board indicator


Find out the status of each board indicator. In normal situation, the RUN LED indicator should be one second on and one second off, and the ALARM LED indicator should be steady off. If the indicator status is abnormal, keep a record of it. Each board has different running and alarm LED indicators. The status of these indicators can reflect the current running status of the board. We can approximately locate the fault by viewing the status of these board indicators.

V. Finding out version information about equipment


The maintenance personnel should be familiar with the characteristics and functions of the equipment of the current version.

VI. Finding out service category applied by equipment


It is necessary to find out all service categories that the MD5500 and the UA5000 provide and the sameness and differences between each service category to see whether they belong to the same service, and whether they are processed by the same system module.

VII. Finding out interface status


If a fault occurs to all subscribers, the upstream interface should be checked primarily.
z

If the upstream interface is an FE or a GE one, check whether the physical layer and protocol layer of the interface are UP, whether the working mode is auto-negotiation, and whether the interface traffic varies.

If the upstream interface is an ATM optical one, check whether its optical module is consistent with that of the opposite equipment, whether the optical interface can emit the laser, whether the loop back is set, whether there is any alarm generated, and whether the port traffic varies.

If the upstream interface is an E1 interface, check whether the E1 link status is normal, whether the loop back is set, and whether there is any alarm generated. If the interface is connected with a local exchange, check whether the V5 interface works normally, whether the V5 link status is normal, whether there is any alarm generated, whether the E1 interface impedance matches that of the opposite equipment, and whether the E1 interface CRC4 setting is consistent with that of the opposite equipment.

If the upstream interface is an IMA one, check whether the IMA packet configuration is consistent with that of the opposite equipment, and whether the E1 connection sequence is correct.

If a fault occurs to part of subscribers, the physical interface that is used to access these subscribers and the status of this interface should be checked primarily.

1-3

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

VIII. Finding out upstream and downstream equipment status


If a fault occurs to all subscribers, the upstream equipment status should also be checked primarily. This includes: the status of interface interconnected with the MD5500, whether there is other equipment that is interconnected with this upstream equipment becomes faulty, and whether this upstream equipment itself has any alarm or is in abnormal status. At the same time, it is necessary to find out the running status of upstream interface and boards of the MD5500, and the status of transmission equipment. If a fault occurs to part of subscribers, the downstream equipment status should also be checked primarily. This includes: the distribution state of these subscribers on the downstream equipment, and whether there is relevant alarms generated. At first, check whether the transmission between equipment is in the normal status (including connection line of distribution frame), and then determine whether these subscribers are all connected to some E1 or STM-1 interface.

1.2.2 Finding out Human Factors


I. Finding out operations to equipment before and after fault occurs
For a burst of fault, find out whether some maintenance personnel has operated the equipment before the fault occurred. If yes, find out whether there were any alarms generated during the operation. Then, find out whether some maintenance personnel has operated the equipment after the fault occurred. If yes, find out the influence of such operation upon the fault.

II. Finding out operations to other related equipment before and after fault occurs
Find out whether some maintenance personnel has operated the upstream and downstream equipment before and after the fault occurred.

III. Finding out construction in the equipment room


Find out whether the local and remote equipment rooms have been reconstructed. If yes, pay more attention to fibers and network cables that are paved during the construction, and whether they have influenced upon the original fibers and network cables.

1-4

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

1.2.3 Working out Subsequent Processing Procedures


By finding out the above-mentioned aspects, the engineer should be able to master the severity degree, complexity, and scope of the fault, and then work out the subsequent processing procedures. If the fault phenomena can obviously reflect the cause of such fault, then some actions can be taken under the direction of engineer. For example: If the physical interface is DOWN suddenly, and it is found that the equipment room is under the construction, then the fibers and network cables should be checked immediately. If the physical or virtual interface is DOWN suddenly, and it is found that some maintenance personnel operated the equipment just now, then check immediately whether the command shutdown was executed unintentionally. If yes, run the command no shutdown to the interface. If the board indicator blinks abnormally, attempt to reset the board by the command at first. Do not plug/unplug the board at will. If a fault is found complicated to handle, and the cause of fault is unclear based on the available information, it is necessary to go to the site to collect more detailed information about the fault.

1.3 Collecting Detailed Information about a Fault


The collected information should be detailed and completed as much as possible. That is to say, all information that might have direct or indirect relationship with the troubleshooting should be collected. For example, when finding out networking diagram of the equipment, youd better collect the information about how many optical distribution frames (ODF) are between two devices in the equipment room. The essential causes of a great number of faults are far concealed. Relying on some seeming fault phenomena, it is uncertain of what kind of information should be collected for troubleshooting. Therefore, it is necessary for us to collect detailed information as possible as we can. For an experienced engineer, he can almost find out the cause of the fault after collecting the primary information about it.

1-5

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

1.3.1 Collecting Detailed Fault-related Equipment Information


I. Collecting board configuration
According to the fault scope and type judged, collect the relative board and subboard information, including slot, type and quantity, such as two ASX boards (slots 7 and 8, CKMB clock subboard), two CESH boards (slots 0 and 1, 120/75 impedance), and two AIC boards (slots 9 and 10, 155M optical subboard).

II. Collecting equipment version information


This includes the host version information, and the software, hardware, logic, and BIOS version information of the key boards. The collected information can be used to locate the faults resulting from the following causes: 1) 2) 3) 4) The host software version does not match the board software and hardware versions, The software version has bug, The board fails to register and start during the upgrade, The board resets automatically during the operation.

III. Collecting equipment data configuration information


The show command can be used to collect the data configuration information to check whether the data configuration contains error or collides with other configuration. The collected information can be used to locate the faults resulting from abnormal services, especially for the faults happened during the new deployment.

IV. Collecting detailed log information


The command show log all can be used to collect all log information about the host system of the MD5500 and the UA5000. The log information of the host system can be used to view operations performed to the equipment before and after the fault occurs. It should be pointed out that the log information of the show command is excluded from that of the host system. For the MD5500 and the UA5000, all log information is stored in the Static Random Access Memory (SRAM). Therefore, the log information will not disappear even if the system resets or in case of power failure. Note that the host can store up to 512 pieces of log records. With this limit exceeded, the old one will be overwritten. So, if the system becomes faulty, view the system logs and make records on them as soon as possible, otherwise the helpful information might be overwritten.

1-6

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

In addition, some important information (including operation records) is stored on the UNIX host (which is also called Log Server) of the internal network by means of syslog mechanism. Note to add and activate this Log Server to backup system logs. For the NMS and Log Server, the number of log records is not limited by the memory capacity, and therefore, they are recommended to store log records.

Note: To get exact operation information, you had better confirm the system time before any service configuration.

V. Collecting equipment alarm information


Usually, a large number of alarms will be generated if the MD5500 or the UA5000 becomes faulty. Accordingly, it is feasible to know the fault type and fault position by analyzing these alarm information. By collecting the equipment alarm information, we can know the running status of the equipment in detail. Therefore, the alarm information can be used to locate the fault correctly and easily. However, using alarm information to analyze the system fault requires you to be much familiar with the detailed equipment alarms. Refer to Chapter 6 Alarm Analysis and Processing for the description of causes of frequent alarms of the MD5500 and the UA5000, as well as the corresponding analysis and processing methods.

1.3.2 Collecting Detailed Networking Information


I. Collecting equipment simple networking diagram
Collect the topology structure, including the positions and quantities of all relevant equipment in the network. This topology structure can be represented by characters or a simple diagram. See Figure 1-2.

1-7

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

PSTN exchange

iSN8850

ROUTER

MD5500

MA5103

BSL

PV8

UA5000

Figure 1-2 Simple network topology The simple network topology is fundamental for locating most faults, especially for faults of service type.

II. Collecting equipment detailed physical networking diagram


It includes upstream and downstream equipment connected with each physical interface of the MD5500. See Figure 1-3.
ISP

LE

DDF

ODF

iSN8850

IP

DDF

ODF

E1
C E S H C E S H

155M
A S X

PVC

A I C

MD5500

E1
DDF

SDH

SDH

DDF

E1
A S L P V 8 B S L

RTU

...
Figure 1-3 Detailed physical networking diagram

PC

The information should be as detailed as possible, including whether the transmission equipment is used between upstream and downstream equipment, the number of ODFs that are used in the equipment room, and so on. The detailed physical networking diagram is also fundamental for fault locating. Make sure that the information related to the fault, such as state of the downlink/uplink equipment and interface type, must be completed and correct.

1-8

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

III. Collecting detailed information about network segment, PVC and route
The information about network segment and PVC of each subscriber connected with the downstream equipment should be collected and marked in the detailed physical networking diagram. The equipment route policy should be collected too. If the Open Shortest Path First (OSPF) dynamical routing protocol is enabled, mark out which Area the network segment belongs to. 1) 2) 3) The collected information can be used for locating the following faults. User network connection interruption, Internet access failure, Slow network rate.

IV. Collecting detailed packet information


Use the software such as NetxRay and Sniffer to collect packets at the user side or upstream egress. The collected information can be widely used for locating the following service faults. 1) 2) 3) 4) Slow Internet access rate IP address assignment failure User authentication and charging failure User DNS resolution failure

1.3.3 Collecting Upstream and Downstream Equipment Information


I. Collecting information about interconnected equipment interface
Find out whether the interfaces of the upstream and downstream equipment that are interconnected with the MD5500 work abnormally when any fault occurs. The collected information can be used for locating the following faults. 1) 2) 3) Some interface of the MD5500 is DOWN suddenly, A large number of alarms are generated at some interface of the MD5500, Some subscriber terminal connected with the downstream equipment becomes faulty.

II. Collecting detailed alarm information of interconnected equipment


Find out whether the upstream and downstream equipment have generated alarms when any fault occurs. If yes, find out the specific meanings of these alarms

1-9

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

1.4 Troubleshooting
1.4.1 Overview
Chapter 1.2 Finding out a Fault introduces how to find out a fault, and chapter 1.3 Collecting Detailed Information about a Fault introduces how to collect the detailed information about the fault and locate the fault, and this section introduces how to confirm the fault location by using instruments and tests, and finally remove the fault.

Note: 1) For troubleshooting, it is important to ascertain whether the cause of fault comes from the MD5500 (or the UA5000) itself, so as to avoid unnecessary fault locating efforts. 2) To improve the efficiency of troubleshooting, during the actual operation, check the connection status of external cables and running status of indicators at first, then check the overall running status of the system by the console, and finally check the running status of each module.

Table 1-1 lists the process and methods for fault locating. Table 1-1 Process and methods for fault locating
Process Exclude the fault from external equipment Locate the fault to the specific equipment Locate the fault to the specific board and remove it finally. Frequently-used methods Comparison analysis, replacement analysis, instruments and meters analysis Loop test Replacement query Other methods Alarm performance analysis Alarm performance analysis Alarm query, indicator query, loop test, configuration modification, and configuration data check.

1.4.2 Determining Fault Type


I. Apparent equipment fault
This kind of fault includes: the board cannot be activated, the interface cannot be activated, the indicator prompts the alarm is generated, the console reports critical alarm, and son on.

1-10

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

II. Equipment interconnection fault


Usually, there are more problems related to equipment interconnection, and most of them are easy to be located. The interconnection ports of the MD5500 include E1 line, IMA interface, optical interface, and Ethernet interface. The port interconnection fault includes: E1 line reverse connection, IMA E1 packet error, optical interface type mismatch, optical fiber type mismatch, and so on.

III. Service fault


The HONET can provide a wide variety of service categories. Different service faults need different troubleshooting methods. The following part presents some frequently-used ones.

1.4.3 Frequently-used Troubleshooting Methods


I. Statistics and analysis
It is important to view the system statistics information during the troubleshooting. However, different fault types have different statistics information. Therefore, the maintenance personnel should be much familiar with the system architecture and running mechanism, system statistics information available, and how to view and analyze the information. See Table 1-2. Table 1-2 Commands used to view system statistics information
Command Show statistics Show cell statistics Description View the ports specific statistics information in ATM/CES port configuration mode. View the cell statistics information about port, board, or specific connection.

II. Instruments and meters test analysis


Instruments and meters play an irreplaceable role in the troubleshooting. They can directly present the fault by means of visual and quantitative data, thus are very useful at fault locating and improving troubleshooting efficiency. Instruments and meters that are frequently used for troubleshooting include:
z z z z z z z

Multimeter Optical power meter Oscillometer E10 meter (bit error tester) PFA-35 meter (bit error tester) Liner tester Signaling trace meter

1-11

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

By comparing the measured performance parameters with the normal parameters, the maintenance personnel can find out the possible causes of a fault.

III. Configuration data analysis


Usually, the incorrect data configuration will cause system faults. By analyzing the configuration data, the fault, especially the fault that occurs during the new deployment, can be located.

IV. Loop test


The loop test is one of the frequently used methods for fault locating. It adopts hardware or software to make the equipment or port transmit and receive packets by itself, and then it can judge whether the equipment/port works normally, and whether the software parameter setting is correct based on the test results. The relevant commands are listed in Table 1-3. Table 1-3 Loop test commands
Command loopback ima group loopback loop Description ATM/CES/E3/SHDSL port loopback Inverse Multiplexing over ATM (IMA) group loopback Plain Old Telephone Service (POTS) port loopback

Caution: Sometimes, the maintenance personnel may forget to cancel the software loopback operation, thus bringing operation hidden trouble to the system. To avoid such kind of event, it is recommended that the maintenance personnel should make a record on it at regular intervals.

V. Comparison and exchange


In case of single fault, the maintenance personnel can find it out by comparing the faulty component with the normal one. In case of complex fault, the maintenance personnel can exchange the component (such as board or fiber) that is in normal status with the suspicious component, and compare the running status of these two components to locate the fault.

1-12

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 1 General Procedures for Troubleshooting

Caution: Exchange operation is at risk. For example, if you exchange a normal board in the frame with a board in short-circuited state, the frame might be damaged. Therefore, be cautious to conduct exchange operation so as not to produce any new fault. It is advisable to check if the fault is caused by or related to the board. When necessary, use a normal board to replace the suspicious board.

VI. Reset operation


Reset operation can be used to diagnose software problems such as software operation disorder, program breakdown, however, it is not recommended. Compared with other methods, reset operation cannot find out the cause of fault accurately, and due to the randomness of software operation, the fault is not likely to recur after the reset operation, thus covering the actual cause of the fault, which may bring hidden trouble to the security and reliability of equipment. Therefore, the reset operation is not recommended unless using as a temporary measure.

Caution: Before resetting or reinstalling boards, do backup the system data to avoid ticket data loss. Due to the fact that resetting or reinstalling boards will interrupt the system service, or even cause the system breakdown, this operation should be performed by the authorized personnel, or after the backup measure has been taken. Usually, it is not recommended for fault locating.

1-13

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

Chapter 2 Physical Connection Troubleshooting


2.1 Transmission Interconnection Fault
2.1.1 Introduction to Principles
As an Optical Line Terminal (OLT), the MD5500 is usually located at the central office, while the subscriber access layer equipment Optical Network Unit (ONU), such as the UA5000, is usually located at the residential community or access intensive area. There is such a long distance between these two devices that the common E1 cable cannot transmit all kinds of voice and data signals effectively. The optical transmission equipment can multiplex and demultiplex electrical signals in the E1 cable, and then transmit optical signals by fibers. By this, the MD5500 can be connected with its lower layer access equipment effectively. In the actual applications, service faults resulting from the improper interconnection of optical transmission equipment with the MD5500 and its lower layer access equipment often occur. This may be caused by incorrect optical interface type, data configuration of optical transmission equipment, or poor fiber quality.

2.1.2 Frequently-used Troubleshooting Methods


Such interconnection problems can be handled by the following methods.

I. Checking status of optical interface indicator


If the optical transmission system is the OptiX 155/622H of Huawei, when normal optical signals received, the red LED indicator beside the optical interface is off. Without optical signals received, this red LED indicator is on. In this case, please check whether the fibers are connected correctly.

II. Checking optical interface type and fiber type


Optical interface and optical fiber can be distinguished by mode as multi-mode and single mode. And the interface can be divided by rate as 155M interface and 622M interface. Correct interconnection requires mode consistency between optical interface and optical fiber, rate consistency and mode consistency between the interconnected optical interface pair. Otherwise, interconnection fault may occur.

2-1

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

III. Querying equipment alarm information


For the OptiX NES platform, it is easy to query alarm information by man-machine interface. The frequent alarm information includes: fiber cut, equipment communication terminal fault, and so on. For the MD5500 and the UA5000, the fault resulting from improper interconnection of optical transmission equipment will cause E1 link fault alarm. By these alarm information, the fault can be located and removed effectively. The command show alarm history is used to query these alarm information.

IV. Querying configuration data of optical transmission equipment


If the Huawei OptiX 155/622H optical transmission equipment is adopted, run the iManager T2000 check the configuration data of tributary board, optical subboard and service category. For other optical transmission equipment, the query method is quite similar.

V. Loop test
General procedures for locating a transmission interconnection fault are: 1) 2) 3)
z

Perform local loopback test at the opposite equipment to check if it works normally. Perform loopback test to the E1 port at the farthest end to check if the E1 connection is OK. If not, perform loopback test to different segment from near end to far end to locate the fault. Loopback test to the E1 port of the MD5500

Perform loopback test to the E1 port that is interconnected with the optical transmission equipment with a loopback line to query the status of E1 port. If there are still alarms, check if the E1 port and the cable are in normal state. If there is no alarm, check further whether the optical transmission equipment and fibres work normally.
z

Loopback test to the transmission optical interface

Perform loopback test to the transmitting and receiving ports of the optical interface of the optical transmission equipment with fibres. If the optical transmission equipment still is generating alarms, check if the optical transmission equipment works normally. If the optical transmission equipment does not generate any alarms, check if the transmission fibres are in good condition. 4) Loopback test to transmission electrical interface

Besides the previous fault locating procedures, the electrical interface of the transmission equipment can also be loopbacked, and then query the equipment state at the optical transmission NMS. If the optical transmission is found at normal state, it

2-2

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

means that the optical fibres and the optical transmission equipment work normally. Further check E1 port and E1 cable to locate the fault.

2.1.3 Fault Case Study


I. The optical subbaord type does not match, which results in communication fault between upper layer equipment and lower layer equipment.
[Fault Description] The MD5500 is connected with lower layer equipment PV8 frame through two OptiX 155/622H equipment, the link data has been configured, but the MD5500 cannot connect with the PV8 frame normally, and the link is in faulty state. [Alarm Information] Link failure [Fault Analysis] Perform hardware loopback test to the E1 port of the CESH board, and the optical interface of the transmission equipment at the MD5500 side. The E1 port and optical transmission equipment are proved normal. Then, connect the fibres correctly, perform hardware loopback test to the optical interface and electrical interface of the transmission equipment successively at the PV8 side. The transmission equipment is proved normal. Then, perform loopback test to the E1 port of the PV8, and the E1 port is proved normal. Then, connect the fibres correctly, and the red indicator is off constantly, which means the fibres function normally. However, these two optical transmission devices cannot communicate mutually all along. It is estimated that these two optical transmission equipment do not match. [Troubleshooting] Check the optical subboards used by these two transmission equipment. One equipment uses 155M subboard, and the other one uses 622M subboard. Replace the 622M subboard with a 155M one, then the communication is recovered, and the service becomes normal. [Suggestion & Conclusion] Before interconnecting the optical transmission equipment, check the hardware information first, including optical interface type, the difference between single-mode fiber and multi-mode fiber, and so on. The loopback test is very important and useful for fault location.

2-3

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

II. The IP address of transmission equipment collides, which causes that the lower layer transmission equipment cannot be maintained, and the service configuration cannot reach.
[Fault Description] The MD5500 is connected with the remote PV8 frame through two OptiX 155/622H devices. The link data has been configured. But the transmission NMS can not configure the OptiX 155/622H at the PV8 side through the OptiX 155/622H at the MD5500 side. . [Alarm Information] Link failure [Fault Analysis] Perform loopback test to optical interfaces, electrical interfaces, and fibers between the upper and lower layer equipment, so as to remove the physical fault. Check if the second bit of DIP switch S2 on each System Control Unit (SCB) of two optical transmission devices is placed into ON state. The DIP switch S2 indicates the last bit of the IP address of the equipment. Here, the IP addresses of these two devices are both 129.9.0.2. Due to the IP address collision of these two devices, the upper layer transmission equipment cannot maintain the lower layer one, and the service is interrupted. [Troubleshooting] Place the third bit of the DIP switch S2 of one transmission equipment into ON state, that is, the IP address is 129.9.0.6. Then, the IP address collision is removed, the upper layer equipment can maintain the lower layer one, and the service becomes normal. [Suggestion & Conclusion] When two transmission devices cannot communicate mutually, checking DIP switch on the SCB is a basic troubleshooting method.

2.2 E1 Line Connection Fault


2.2.1 Introduction to Principles
The MD5500 is interconnected with the lower layer equipment by means of E1 connection, which is realized by CES board. No matter what kind of optical transmission equipment is adopted, the system must employ E1 connection mode, that is to say, the MD5500 is connected to the optical transmission equipment through E1 cables. After transmitted through fibers, the E1 signals are further transmitted to the

2-4

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

corresponding E1 port of the access layer equipment by the tributary board of the opposite optical transmission equipment. Accordingly, the E1 line connection is very important for the MD5500, and much attention should be paid to it if any service fault occurs.

2.2.2 Frequently-used Troubleshooting Methods


I. Checking physcial connection (including cables and grounding)
The physical connection must be correct and meet the requirements of the engineering. Seen from the former cases, many frequent faults are caused by engineering problems. In addition, such kind of problems is not easy to be located and handled because they are hidden relatively. So, once a fault occurs, check the basic physical connection at first. Usually, the physical connection fault may occur to the following aspects: 1) 2) 3) 4) E1 interface cable impedance (75 ohm or 120 ohm) E1 interface cable grounding Connection of cables with main distribution frame (MDF) Grounding of main distribution frame and frame

II. Checking E1 interface cable impedance (75 ohm or 120 ohm)


The different equipment may employ different cables, that is, 75/120-ohm E1 interface cable. Corresponding to different cables, the DIP switch for E1 interface board should be set differently. Any inconsistent settings will result in interconnection faults. The settings of DIP switches of E81D subboard attached to CES boards are shown in Table 2-1. Table 2-1 settings of DIP switches of E81D subboard attached to CES boards
DIP switch S1~S4 S5 S5 E1 interface impedance (75) Bits 1~8 are ON. Bits 1 and 4 are OFF. Bits 2 and 3 are ON. E1 interface impedance (120) Bits 1~8 are OFF. Bits 1 and 3 are OFF. Bits 2 and 4 are ON.

III. Checking if the transmitting and receiving cables are connected wrongly
During the actual applications, the case that E1 links can work normally while the service cannot be transmitted normally may often occur. In this case, check if the transmitting and receiving cables are connected to improper ports, that is, mismatched wires. If such fault occurs, perform hardware or software loopback test at one end of the E1 link, and then query the E1 link status at the other end. In case that the E1 link works

2-5

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

normally, it indicates that this E1 link is connected with error port. In case of E1 Link failure, it indicates that this E1 link is connected with the port correctly.

IV. Checking if the CRC settings are consistent at both sides of the equipment
The CRC4 function should be set consistently at both sides of the equipment.

V. Checking if the PV8 software matches


If the E1 link between the PV8 and RSP keeps on working normally and abnormally, then check if the PV8 and RSP boards in this frame are confirmed, and check if the correct PV8 software is loaded.

VI. Checking working mode of board and port

Note: The CES series of boards of the MD5500 include CESH, DT16, and EA16.

The CES series of boards can work in two working modes, E1 and Time Division Multiplexing (TDM). The narrowband E1 link works in TDM mode. In case of E1 mode, the port can work in the User Network Interface (UNI), Structured Data Transfer (SDT), or Unstructured Data Transfer (UDT) modes to realize ATM cell adaptation, structured and unstructured data transfer. Therefore, when the MD5500 is interconnected with the switch, or with the lower layer equipment such as the RSP and PV8, the CES board must work in the TDM mode. The following command is used to query the working mode of the board:
MD5500(config-if-ces-0/1)#show runmode Run mode of the board is: TDM

The following command is used to query the E1 port:


MD5500(config-if-ces-0/1)#show port mode

or
MD5500(config-if-ces-0/1)#show board 0/1

This command can be used to show the working status, port mode and service type of all the ports of some CES board. If the working status is normal, it means the E1 line is normal physically. If the port mode is E1, it means this port is connected to the E1 link. The service type indicates to which this port is connected, V5 link of the LE, or the PV8/RSP frame.

2-6

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

For the PV8/RSP board, the following command can be used to query the E1 port status:
MD5500(config-narrow-user)#show port state 1/10

VII. Checking indicators


For the RSP/PV8 board, there are two methods to query the port status, the first is to use the command show port state, and the second is to use the indicators on the front panel of the board. There is one E1S indicator on the front panel of the PV8 board, which can indicate the physical status of eight E1 ports on the PV8 board respectively by the combination of the first three bits of the DIP switch on the front panel (for example, place the bit SW1 into OFF state, SW2 into ON state and SW3 into OFF state, that is, the combination of 010, and it represents the third E1 port). If the indicator is constantly on, it means this E1 port works normally, otherwise abnormally. There are four E1 indicators on the front panel of the RSP board, E1, E2, E3, and E4, which are used to indicate the status of four E1 ports of the RSP. Different from the PV8 board, if the indicator is constantly off, it means this E1 port works normally, otherwise abnormally.

VIII. Checking alarms


The command show alarm can be used to query the E1 port alarm status. If the relevant alarm information is NO, it means no alarm is created, and if it is YES, it means some alarm is created. Only the alarm information of LOS, LFA, RRA, AIS, LMFA, CRC4 are all shown as NO, it means the port works normally. Otherwise, the physical connection needs to be checked. The detailed description of each alarm and the relevant handling methods are as follows: 1) Loss of Signal (LOS)

This alarm is created in case of loss of received signals. There are two cases for creating this alarm: one is that the line is in disconnection state when the system is during the startup, and the other is that no signals are detected on the receiving line during the running of the system, which is usually caused by the line fault. 2) Loss of Frame Alignment (LFA)

This alarm is created in case of loss of received frames. There are two cases for creating this alarm: one is that the line is in disconnection state when the system is during the startup, and the other is that the loss of synchronous signals are detected during the running of the system, which is usually caused by the error frame format that is sent from the opposing party, for example, when the port works in SDT mode, the opposite party sends UDT data. 3) Receive Remote Alarm (RRA)

2-7

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

When detecting the LOS or LFA, the remote device will insert an alarm signal into the data that is sent to the local device. Usually, this alarm is generated when this E1 port can receives the opposite signals normally, while the opposite port cannot receives the E1 signals normally. In this case, check if these two ports are connected correctly. 4) Loss of Multiframe Alignment (LMFA)

This alarm is created in case of loss of received multiframes. If the CRC4 function is enabled at this end, but the received frames are not multiframes, then this alarm is created. 5) Alarm Indication Signal (AIS)

This alarm is created when it is detected that there are only two or less than two zeros in the received data during a certain time segment.

IX. Performing port loopback test


There are two kinds of port loopback modes: hardware loopback and software loopback. The hardware loopback means using loopback cable to perform loopback test to the E1 line at the LE or MD5500 side. At the LE side, performing loopback test to the E1 line of the MD5500 can check if the line and equipment between the MD5500 and the port of LE work normally. At the MD5500 side, performing loopback test to the E1 line of the LE can check if the line and equipment between the LE and the port of the MD5500 can work normally. For the E1 port of the MD5500, there are two kinds of software loopback modes: LOCAL and REMOTE. The former can check if the E1 port works normally, and the latter can check if the physical line and equipment between the LE and E1 port work normally.

2.2.3 Fault Case Study


I. The service between upper layer equipment and lower layer equipment is interrupted because of the reverse connection of receiving and transmission lines
[Fault Description] The E1 cable of the CESH is connected to the optical transmission equipment, the equipment reports 2M alarm, the communication between upper layer equipment and lower layer equipment becomes faulty, and the service is interrupted. [Alarm Information] Link failure

2-8

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

[Fault Analysis] At first, remove the faults of fiber and port type. Since the receiving and transmitting lines of the E1 cable are separated, the service interruption may be resulted from the reverse connection of receiving and transmission ends. [Troubleshooting] Exchange the receiving and transmitting lines of the E1 cable of the CESH, and then the communication between upper layer equipment and lower layer equipment becomes normal. [Suggestion & Conclusion] The reverse connection of receiving and transmitting lines of E1 cable often occurs, and much attention should be paid to it during the troubleshooting.

II. The E1 cable of the PV8 board is connected wrongly, which makes the PV8 frame unable to communicate with the MD5500.
[Fault Description] The tributary board of the transmission equipment leads out E1 cable to the PV8 board, but the PV8 frame is unable to communicate with the MD5500. [Alarm Information] Link failure [Fault Analysis] After removing the fault of fibers, port type, reverse connection of receiving and transmitting lines, the PV8 board still cannot communicate with the MD5500 normally. Then, check the connection position of the E1 cable of the PV8 board to find that the E1 cable is plugged into the 16th pin row of the upper HEADER, while the correct position is 17th pin row. [Troubleshooting] Connect the E1 cable of the PV8 board to the 17th pin of the upper HEADER, and the communication is recovered.

III. The differential HW cable of the RSP is connected wrongly, which makes the RSP frame unable to communicate with the MD5500 normally.
[Fault Description] The tributary board of the transmission equipment leads out the E1 cable to the PV8 board, which is cascaded with the RSP board through the differential HW cable, while the RSP frame cannot communicate with the MD5500 normally.
2-9

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

[Alarm Information] Link failure [Fault Analysis] After removing the fault of fibers, port type, reverse connection of receiving and transmitting lines, the RSP board still cannot communicate with the MD5500 normally. Then, check the connection position of the differential HW cable of the RSP board to find that the cable is plugged into the 17th pin of the upper HEADER, while the correct position is 17th pin of the lower HEADER. At the same time, place the second bit of the DIP switch of the front panel of the RSP board into the ON state. [Troubleshooting] Connect the differential HW cable of the RSP board to the 17th pin of the lower HEADER, and the communication is recovered. [Suggestion & Conclusion] Be familiar with the different connection positions of PV8 and RSP boards in the different networking applications.
z

In case that the MD5500 and RSP form a network through E1 cables, it is called remote mode. The connection position of E1 cables of the RSP board starts from the 17th pin of the upper HEADER, and all bits of the DIP switch of this board should be placed into OFF state.

In case that the PV8 and RSP form a network through differential HW cables, it is called quasi-local mode. The connection position of cables of the RSP board starts from the 17th pin of the lower HEADER, and all bits of the DIP switch of this board should be placed into OFF state except that the second bit into ON state.

IV. When the MD5500 is connected with the RSP through trunk cables, a transmission alarm is created because the data has not been configured.
[Fault Description] When the MD5500 is connected with the RSP through the CESH board and through the transmission equipment, after the transmission channel is through, the trunk interrupted alarm is created. According to the NM of the MD5500, the corresponding port is in faulty state, and the service type is empty. [Alarm Information] On the transmission NM, there are continuous trunk alarm that is connected with the RSP, that is, RFA alarm, and trunk transmission recovery alarm.

2-10

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

On the NM of the MD5500, the PCM line fault alarm and recovery alarm are created in pairs repeatedly. The E1 port that corresponds to this PCM line is the port that is connected with the port 0 of the left RSP board (seen from the front side of the frame) through the trunk. [Fault Analysis] In this networking mode, the possible causes of the transmission interrupted alarm are: 1) 2) 3) The transmission line is not stable, short-lived interruption occurs, and then is recovered. The board fault. The data configuration is incorrect.

[Troubleshooting] Locate the fault based on the fault analysis one by one. On the MDF, perform loopback test to the transmission line, and then observe the transmission NM if the frequent interruption and recovery alarm occur. Actually, they do not occur, thus removing the possibility of unstable transmission line. 1) Check the CESH board of the MD5500 (which provides the RSP with the E1 port) to find that the CESH board works normally, however, the port is in faulty state. On the MDF, perform loopback test to the port of the CESH board, and then query the port state on the maintenance terminal of the MD5500 to find that the port is in normal state, and the service type is empty. This indicates that the port of the CESH board of the MD5500 works normally. 2) Check the data configuration to find that part of data of the RSP has not been configured. Then, on the maintenance terminal of the MD5500, configure the frame data and link data of the RSP correctly, confirm the RSP board and RSP link, and query the corresponding port of the CESH board to find that it is in normal state, the service type is RSP, and no more PCM line interruption alarm and recovery alarm are created. Observe the transmission NM, no RFA alarm is created. The problem is resolved. [Suggestion & Conclusion] Analyze the causes of this fault: Actually, the physical layer here is in normal state. Since the link layer does not work normally, the RSP board will send the request of establishing links to the main control board, and the MD5500 can receive this request. That is to say, the link here is in normal state, and the link recovery alarm is created. On the other hand, since the RSP frame data has not been configured, the link layer negotiation becomes failed, and the establishment of link becomes failed too. Thus, the link failure occurs. In this case, the RSP will reset to reestablish the link, and the above-mentioned process will repeat, thereby, the transmission interruption recovery alarm is created repeatedly.

2-11

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

When configuring the MD5500 narrowband services, if the trunk alarm is created, and the physical channel is proved normal, then take this case as reference.

V. The link failure and loading failure of the PV8/PV4 frame connected with the MD5500 that is caused by mismatch of line impedance set by DT16 board
[Fault Description] Networking mode: MD5500----DDF----PV8/PV4 The MD5500 is connected with the PV4/PV8 board through the E1 port (working in TDM mode) provided by the DT16 board. Only single PV8/PV4 board is configured, and the trunk cable is 120-ohm twisted pair. The board, which is running on the HONET platform, is to be upgraded. Fault: On the MD5500 maintenance terminal, query the link state of the connected PV8 board to find that it is in faulty state. The board cannot be loaded and upgraded no matter what kind of loading method is used. Observe the maintenance terminal of the MD5500, no loading request of the PV4/PV8 board is received. [Alarm Information] 1) 2) 3) 4) PCM alarm E bit remote alarm LFA alarm RRA alarm

[Fault Analysis] The possible causes of the alarms are: 1) 2) 3) The cause of PCM alarm is that the line may be in poor quality, or the line is disconnected. The cause of E bit remote alarm is the poor grounding, or the electric potential difference across the line. The cause of LFA alarm is the asynchronization of received and transmitted frames, different format of received and transmitted frames, and loss of synchronous signals that are caused by the incorrect clock. In addition, if the received signals at the receiving end is the too weak may also cause such alarm. Sometimes, the system may also create such alarm by mistake due to the influence of line noise. 4) If the LFA or LOS alarm occurs to the far-end received frame, the far end will insert a bit into the transmitting frame, indicating the existence of alarm, that is, the RRA alarm is created.

2-12

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

5)

Since the MD5500 cannot receive the loading request from the PV4/PV8, while in the PV8/PV4 frame, only one PV8/PV4 is configured, there is no problem of message packets congestion, and no interference problem exists. Therefore, the cause of loading failure is the link.

[Troubleshooting] Locate the fault based on the fault analysis one by one. Check the grounding status, and no problem is found. 1) On the digital distribution frame (DDF), perform loopback test to the MD5500 and PV8/PV4 respectively, the test result indicates that the link is in normal state. Then, perform loopback test from the PV8/PV4, but the corresponding port of the DT16 board cannot be recovered. Check it and no line crossover is found, and it seems that the line is in poor quality. 2) Check the connected trunk lines. The E1 cables between the DT16 board and the PV8/PV4 board are all 120-ohm twisted pairs. Since the loopback tests performed on the DDF are succeeded, it means the physical connection of cables is in good condition. At the same time, the connection points are also made properly. The signals transmitted from the DT16 board will attenuate rapidly over the external cable with mismatched line impedance, and become too weak to be obtained correctly after some transmission distance. By default, the DT16 board is connected with the 75-ohm coaxial cable, while the current connection cable is 120-ohm twisted pair, the fault will surely occur. 3)
z z z

Take off the E1 subboard on the DT16 board, and make the following settings according to the line status: S5: 1-ON, 2-OFF, 3-OFF, 4-ON, S1 and S3: All OFF, S2 and S4: All OFF.

Install the DT16 board back to the frame. When this board is registered, enter the board interface mode, perform remote loopback test at the PV4/PV8 side, and then check the port to find it is in normal status. Connect the PV8/PV4 frame, configure the frame link and TFTP-SERVER well, and then start to load the PV8/PV4 board program through the DIP switch on the board. The loading request is transmitted to the MD5500 correctly, and the board program is loaded successfully. [Suggestion & Conclusion] There are many causes for E1 line problem, for example, poor grounding, transmission interruption, incorrect clock, line cross, and so on. In addition, since the transmission line characteristic impedance depends on the attenuation rate of the signals, whether the line characteristic impedance matches is also an important factor. By default, the E1 subboard on the DT16 board adopts 75-ohm coaxial cable, if the 120-ohm twisted pair is adopted, please set the DIP switch properly on the E1 subboard. In addition, in case

2-13

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

of E1 line fault, use the corresponding alarm to analyze the possible cause of it. In this way, the fault can be found and handled promptly and efficiently.

VI. The transmission loopback results in NMS communication and service transmission failure.
[Fault Description] Some MA5105 is connected to E1 port of the upper layer equipment MD5500 through the E1 line and transmission equipment. The MA5105 can work normally. The MD5500 and MA5105 have been configured correctly, but both the service transmission and NMS communications fail. [Alarm Information] None [Fault Analysis] The NMS communication or service transmission failure may be caused by the following reasons: 1) 2) Data configuration error E1 physical line fault

[Troubleshooting]
z

Checking data configuration

The data has been planned well before the deployment. Check carefully, and the data are found correct.
z

Checking physical line

Check the port status by command line mode and observing indicators. It is found that all ports of the MA5105 are in normal state, and the four E1 indicators are constantly on, that is, the physical connection is in normal state. Although E1 ports are found normal, it does not mean the connection between E1 ports and MD5500 is undoubtedly normal. By E1 loopback, the E1 port of the MA5105 can receive and transmit data normally even if it fails to connect with the MD5500. How to judge this? When the MA5105 is interconnected with the MD5500, the setting of CRC4 function is required for ports at both sides, if the settings are consistent, the E1 indicators at both sides will work normally. Otherwise, they will go out. This characteristic can be used to judge if the E1 port works normally because of the E1 loopback. Solution: Enable the CRC4 function to the E1 port at the MA5105 side, the corresponding indicator is on, and the port is proved normal by using the command. Then, disable the CRC4 function to the same port, the corresponding indicator is still on, and the port is also proved normal by using the command. However, the CRC4 setting
2-14

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

of the E1 port at the MD5500 has not been changed. By this, we can draw a conclusion that the loopback is performed on the transmission line, which is directed to the MA5105. So, the E1 port of the MA5105 is found normal no matter how it is set, and that is why the CRC4 is found consistent no matter how it is set. After the check, it is found that the loopback is performed on some part of the transmission line, cancel the loopback and the fault is removed immediately. [Suggestion & Conclusion] We can utilize the consistency of CRC4 setting at both the MA5105 side and MD5500 side to locate the fault such as E1 line loopback.

2.3 ATM Optical Interface Interconnection Fault


2.3.1 Introduction to Principles
I. Description of optical subboard
To work normally, the H511AIC must be installed with the optical subboard. With different subboards configured, the AICA board can provide 155/622M single/multi-mode ATM optical interfaces. Table 2-2 Specifications of subboard
Name H511HXA H511HXB H511HXC H511O1CPG H511O1CPB H511O2CPG H511O2CPB Description 622M short distance, multi-mode 500m 622M middle distance, single-mode 15km 622M long distance, single-mode 40km 1-port 155M, single-mode 30km 1-port 155M, multi-mode 2km 2-port 155M, single-mode 30km 2-port 155M, multi-mode 2km

The 622M optical subboard must be installed at the lower slot for the subboard on the AIC board. To replace different types of subboards attached to the AIC board that is already registered to the host, if the current host version is earlier than MD5500V100R003B02D051, the board should be deleted before it can successfully register again; if the current host version is MD5500V100R003B02D051 or later, the board should be deleted or the subboard type should be modified before the board can successfully register again.

II. Jumper description


There is a jumper J3 on the AIC board. If the pins 2-3 are short connected, the optical subboard uses the system clock, and if the pins 1-2 are short connected, the optical
2-15

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

subboard uses the clock of this board. Usually, the pins 2-3 are connected, that is, the system clock is used.

III. Technical parameters of optical interface


Item Operating wavelength range Characteristics of transmitter at Point S Characteristics of receiver at Point R Maximum average transmitting power Minimum average transmitting power Minimum sensitivity Minimum overload point STM-1 Single-mode 1261~1360n m -8 dBm -15 dBm -28 dBm -8 dBm Multi-mode 1270~1380n m -14 dBm -23.5 dBm -30 dBm -14 dBm STM-4 Single-mode 1274~1356nm -8 dBm -15 dBm -28 dBm -8 dBm Multi-mode

2.3.2 Frequently-used Troubleshooting Methods


I. Optical interface interconnection interuption
Check if the settings of interconnected interfaces are consistent, including the following content:
z

Check if the rates of the interconnected interfaces are consistent, for example, 155M or 622M, Check if the interface modes of the interconnected interfaces are consistent, for example, single-mode interface or multi-mode interface, Check if the interface wavelength of the interconnected interfaces matches, for example, 1310nm or 1550nm, When optical signals transmitted from the local equipment reach the opposite equipment, check if the optical power is in the receiving range of the opposite equipment (the transmitted optical signals will be attenuated due to the transmission over fibers, and the optical power should be between the receiver sensitivity of the opposite equipment and the overload optical power).

II. AIC board optical interface alarm


Possible causes 1) 2) 3) Jumper J3 on the AIC board does not set properly, If the red indicator on the optical subboard blinks rapidly, please reinstall the fiber to check if the physical connection is correct. If the fiber is connected normally, while the indicator on the optical subboard turns red (which indicates an alarm occurs to the optical interface), change the setting of Jumper J3 to check if the system clock subboard is damaged.

2-16

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

Fault locating method 1) In case of optical interface LOS alarm, perform port loopback test by using the fiber to check if this fiber can function normally. In case that the alarm is created during the running of service, it is recommended that a tester should be used to measure the optical signals at the receiving end. 2)
z

In case of Loss of Cell Delimitation (LOCD) alarm, it indicates the cell delimitation of optical subboard fails, and the following operations are recommended: Run the command loopback portid local to perform loopback test. If the LOCD alarm is recovered, it indicates that the LOCD is caused by external factors. If the LOCD alarm cannot be recovered, it indicates that the optical subboard does not function normally temporarily. In this case, reset the AIC board.

Run the command loopback portid remote to perform loopback test. If the opposite equipment alarm is recovered, it indicates the optical subboard on the AIC board becomes faulty. In this case, reset the AIC board or reinstall/replace the optical subboard on the AIC board. If the opposite equipment alarm still exists after you run the command loopback portid remote, much attention should be paid to the opposite equipment.

3) 4)

In case of optical interface LOP alarm, check if there is relevant alarm indicating the system clock is lost, In case of optical interface L-RDI/P-RDI alarm, it indicates that the receiving end of the opposite equipment is in the faulty state. In this case, check if the fibers are connected well.

III. Service interruption of AIC board


Possible causes 1) 2) 3) Check the configuration data to see if the local VPI/VCI values are consistent with the opposite values, Check if there are optical interface alarms such as LOS, LOCD, LOF, and so on, In the AIC port configuration mode, run the command show statistic portid to check if the port is in loopback mode. Fault locating method In the AIC port configuration mode, run the command show statistic portid to check if the statistics of cells received and transmitted by the optical interface are increased continuously.

IV. Bit error of AIC service test


Possible causes 1) 2) The transmission link signals are in poor quality, Check if Jumper J3 on the AIC board is set correctly (pins 1-2 should be short connected),

2-17

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

3) 4)

Check if the host has created the alarm indicating the abnormal clock, Check if the fiber and the optical subboard are in loose contact, and reinstall the fiber to observe if the bit error disappears.

Fault locating method 1) For the 622M optical subboard, check if the host has created the SD alarm (only the 622M optical interface can create the SD alarm). 2) In the AIC port configuration mode, run the command show statistic portid to check if the statistics of optical interface bit error are increased continuously.

V. Optical module damage


Possible causes Optical power is too large, or the optical module is damaged after a long-term service. Fault locating method Use an optical power meter to measure the optical power of the optical interface. For an STM-1 optical interface, the normal optical power should be -15dBm around. If the measured optical power is too large, it is necessary to add an optical attenuator on the fiber, or replace the existing subboard with an optical subboard of another type.

2.4 Ethernet Port Interconnection Fault


2.4.1 Introduction to Principles
An Ethernet port can work in half duplex or duplex mode at the rate of 10M, 100M, or 1000M. So, when it is interconnected with other ports, pay attention to the consistency of the port settings.

I. Duplex or half dulpex mode


In the Ethernet, the half duplex and duplex modes belong to the physical layer concepts. Corresponding to these two modes, the data link layer provides different media access control modes, Carrier Sense Multiple Access (CSMA)/Carrier Detect (CD) for half duplex mode, while in the duplex mode, the data can be received and transmitted directly, not needing to judge the link status in advance. The half duplex transmission mode can realize the CSMA/CD. The traditional Local Area Network (LAN) works in the half duplex mode, which is very sensitive to the transmission conflict over the cables. The working process of CSMA/CD is as follows:

2-18

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

The terminal equipment continuously detects the shared line status, and only when the line is in idle state will the data be transmitted. If the line is occupied, the terminal equipment will keep on waiting. If two terminal devices transmit data simultaneously, these data must collide, which will result in unstable line signals over the line. Once the terminal equipment detects the unstable signals, it will stop sending data immediately, then send a series of interference pulse, and then send data after a while. The 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. The frames transmitted from two connected ports will not collide because they use two pairs of separated lines of the twisted pair. The traditional network equipment, such as HUB, does not support duplex transmission mode because the HUB only has one shared bus inside, and all data are transmitted and received over this bus. Therefore, it cannot perform duplex transmission at one time. An Ethernet switch has multiple ports, and each port can be connected with terminal equipment and other equipment that contains multiple ports for duplex communications. There is a digital crossover network inside the Ethernet switch, which can connect all terminals temporarily, and these terminals can transmit data independently. In addition, the switch can allocate buffer for each port, which can store the data from terminal temporarily, and exchange the data after the transmission resource is available.

II. Auto negotiation mode


In the actual applications, there are many kinds of combinations of Ethernet operation mode. It will be too complicated to configure all terminal equipment manually. To handle various operation modes, the auto negotiation function comes into being. By this function, one network equipment can transfer the working mode supported by itself to the opposite party, and can receive the relevant information from the opposite party. It uses a kind of standard physical layer signal, Fast Link Pulse (FLP) or Normal Link Pulse (NLP), to transmit the negotiation information, and make the equipment at both sides work with the highest transmission efficiency. The auto negotiation function is realized by physical chip completely, so it does not use any special data packet, or occupy any overhead. Since it is established over the lower layer mechanism of the twisted pair Ethernet, it is only effective on the twisted pair Ethernet. The auto-negotiated content includes: duplex mode, operating rate, flow control, and so on. Once the negotiation is succeeded, the equipment at both sides of the link will work in the negotiated mode until the equipment reboots or the cable is reconnected. The auto negotiation can be applied in the following cases: 1) Both parties support auto negotiation.

After the auto negotiation, both parties will work at the highest rate that is supported by both parties, thus ensuring the highest transmission efficiency. For example:

2-19

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

The highest rate of both parties is all 100M duplex, and the auto-negotiated rate is 100M duplex. The highest rate of both parties is 10M and 100M respectively, and the auto-negotiated rate is 10M. If one party only supports half duplex mode, then the auto-negotiated result is: both parties work in half duplex mode. If the auto negotiation between two parties is succeeded, the interconnection will be succeeded too. Otherwise, it indicates that the both parties have no matched rate. 2) One party supports auto negotiation function, while the other party does not.

The problem may happen when one network interface that supports auto negotiation function is interconnected with another network interface that does not support such function. The network interface that supports auto negotiation function can judge the opposite partys rate by received signals, but cannot judge its duplex/half duplex mode because there is no FLP or NLP information carried by the received signals. Therefore, this network interface can only set its own rate as 100M half duplex or 10M half duplex according to the opposite partys rate. Such a case can be divided into the following two conditions: If one network interface that supports auto negotiation function interconnects with one 10M/100M half duplex mode network interface, the former will set its own working mode as 10M/100M half duplex mode, in this case, the both parties have the same working modes and can communicate normally. If one network interface that supports auto negotiation function interconnects with one 10M/100M duplex mode network interface, the former will set its own working mode as 10M/100M half duplex mode, in this case, one port works in half duplex mode and the other duplex mode, the communication link may collide, which will result in loss of packets or error packets. One of the basic principles of setting networking interface mode is: the settings of interconnected network interfaces should be consistent, and avoid setting that one network interface works in auto negotiation mode, while the other network interface works in duplex mode. If one network interface does not support the auto negotiation function, disable such function of the interconnected network interface, and then set that both parties work at the same rate and in the same duplex/half duplex mode.

III. 1000M Ethernet


The IPU board of the MD5500 supports 1000M Ethernet (GE) optical interfaces. At present, the GE technology is well developed and widely used in backbone layer of data network and used for connection with some high end database servers. The data link layer of the GE basically follows the link layer of the traditional Ethernet (except for

2-20

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 2 Physical Connection Troubleshooting

the half duplex mode), which can better protect the former investment. To transmit a maximum of 1000M data bit over the physical medium, the GE adopts the fiber channel technology. Currently, the GE port of the IPU board supports auto negotiation function and duplex mode, not half duplex mode.

2.4.2 Frequently-used Troubleshooting Methods


When network interface interconnection faults occur, the frequently-used

troubleshooting methods are: check by PING command and view the statistics information. Refer to the following part for detailed operation steps.

I. Pinging the opposite port from the MD5500


If the Ethernet interface of the MD5500 fails to connect with the opposite interface, you can use the command PING to locate the fault. There are two kinds of channels used to transmit PING packets, network management (NM) channel and service channel. Select them properly based on actual needs. When pinging the IP address of the maintenance network interface or that of the PC connected with the maintenance network interface, use the following command:
MD5500(config)#ping -b 10.10.1.55

When pinging the IP address of the interface of the IPU/EPU board or that of the opposite interface that is connected with the board, use the following command:
MD5500(config)#ping 192.168.0.1

The parameter -b means using NM channel to transmit the PING request packets. If this parameter is not adopted, the service channel is used to transmit the PING request packets.

II. Viewing interface state


The command show interface can be used to show the physical state and link protocol state of the interface, which is helpful for the troubleshooting.

III. Viewing port statistics information


The IPU and EPU boards support port statistics function, and the relevant command is as follows:
MD5500(config-if-fast-ethernet-0/10/0)#port statistic -------------------------------------------------------------------Flow|Flow-Time Five-Minutes-Flow One-Hour-Flow One-Day-Flow All-Flow

-------------------------------------------------------------------Up-Packet Up-Octet(byte) 0 0 0 0 0 0 0 0

2-21

Troubleshooting Manual HONET Integrated Services Access Network


Up-Packet-Times Up-Octet-Times Down-Packet Down-Octet(byte 0 0 0 0

Chapter 2 Physical Connection Troubleshooting


0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Down-Packet-Times 0 Down-Octet-Times 0

--------------------------------------------------------------------

The LANC board can also support the port statistics function, and the relevant command is as follows:
MD5500(config-if-lan-0/2)#show port statistic 2 MD5500(config-if-lan-0/2)# inquire port all statistic info success good receive frame good transmit frame =511 =385 =0 =103

receive frame CRC error num receive good broadcast frame

discard frame num in receive frames =76 receive oversized frame receive undersized frame transmit good broadcast frame transmit good multicast frame receive good multicast frame transmit Pause frame receive Pause frame =0 =0 =0 =0 =0 =0 =0

The interface status can be found out by showing the number of received/transmitted frames. By the above-mentioned methods, you can judge the status of channel between the MD5500 Ethernet interface and the opposite interface. In addition, you can know the line quality by the delay and packet loss ratio of the PING packets. If the packet loss ratio and delay are rather large, or the communication fails, please check if the physical line is connected normally, if the straight through cable or crossover cable is used correctly, and then check if the port settings (duplex/half duplex mode and rate) are consistent with those of the opposite port. If the fault still exists, try another port. The maintenance network interface of the ASX board of the MD5500 is connected with the PC through the crossover cable, and the network interface of the LANC/IPU/ EPU board is connected with the PC through the straight through cable. The maintenance network interface of the APM board of the UA5000 is connected with the PC through the crossover cable.

2-22

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

Chapter 3 Narrowband Service Troubleshooting


3.1 Overview
The narrowband services are composed of the narrowband voice service and data service. The following diagram shows the role of the MD5500 and the UA5000 in the narrowband access network.
PSTN exchange
E1

PSTN

V5
MD5500

E1 or CES

E1

E1

UA5000
HW Subscriber line

PV8
Subscriber line

RSP
Subscriber line

RSP

Narrowband subscriber

Narrowband subscriber

Narrowband subscriber

Narrowband subscriber

Figure 3-1 Networking diagram of HONET narrowband voice service The narrowband data services of the MD5500 are provided by the data service boards installed into the ONU frame (such as UA5000 frame, PV8 frame and RSP frame). For example, the High-speed Subscriber Line Board (HSL) provides the N64kbps access service, the DSL board provides the 2B+D access service, and DSL + Multifunctional Terminal Adapter (MTA) provides the sub rate access service.

3.2 Narrowband Voice Service


3.2.1 Frequently-used Troubleshooting Methods
I. No Feeding Current for Phone
[Fault Description]

3-1

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

After the subscriber picks up the phone, there is no dial tone, and the running indicator or line indicator of the phone is off. [Fault Analysis]
Serial number 1 2 3 4 5 Fault cause Subscriber loop line disconnected Subscriber loop line short-circuited Subscriber loop line mixed with other lines Subscriber circuit fault on ASL board Subscriber phone set fault Remarks It indicates that the subscriber loop line is open-circuited; the voltages of outgoing line A and line B of the phone are 0, and the grounding voltage is 0. The voltages of outgoing line A and line B are 0, and the grounding voltage is 0. It is also called cross wire, which will lead to the equal potential between subscriber lines A and B and loss of feeding current in the phone. For example, the lightning strike may lead to burning of the fuse and loss of feeding current for the subscriber circuit. For example, the rectification circuit of the phone fails, which leads to loss of feeding current in the phone.

[Troubleshooting] 1) Determine whether it is short circuiting or disconnection that leads to no feeding current in the phone Perform loop line test to the corresponding subscriber port. The specific causes leading to loop line fault can be obtained based on the test result. These causes include loop line self-mixing, touch the power line, loop line mixed with others, loop line grounding and loop line disconnected.

Note: Method for judging quickly whether the subscriber loop is short-circuited: check the state of the subscriber port. If it is at the locked state, the loop is short-circuited. If you are far from the maintenance console and direct check is unavailable, you can call the subscriber. If ring back tone can be heard, it indicates that the loop line is not short-circuited. If busy tones or such prompt tones as subscriber line fails are heard, it indicates that the loop line is short-circuited or other faults exist.

2)

Determine whether the subscriber port on the ASL board fails

In the testing system, perform circuit test to the corresponding subscriber port. The following conclusions can be drawn from the test results: if there is no feeding current or the feeding voltage is too low, it indicates the port is damaged. In this case, the subscriber circuit should be connected to another port or just replace the ASL board. 3) Determine whether the loop line fails or the circuit fails

Isolate the subscriber loop line at the distribution frame and use a testing phone or multimeter to test the subscriber lines A and B. If there is dial tone or the voltage is -48V,

3-2

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

it indicates the circuit is normal. Otherwise, check the ASL board and the subscriber cable, and conduct such operations as replacing the ASL board and measuring the continuity of the subscriber cable with a multimeter. 4) Determine whether lines are mixed

If there is no feeding current in the phone due to mixed lines (lines wrongly matched), the potential of line A and line B must be equal. Therefore, after other possible causes are excluded, whether the fault of mixed lines exists can be determined by measuring the grounding potential of line A and line B. If the potential of line A is equal to that of line B and it is not 0, the possibility of line a mixed with line B is rather high. 5) Determine whether the subscriber phone fails

Fault of the subscriber phone is also a common cause leading to no feeding current in the phone. This measure is generally conducted at the beginning or the final stage of fault handling. Whether the subscriber phone fails can be determined by replacing the phone or using a multimeter to measure the voltage of line A and line B.

Note: Among all the possible causes, the percentage of the subscriber loop line fault and ASL board fault is rather high. Therefore, regular test on the subscriber line and the ASL board as well as timely understanding of the running parameters of the line and running state of the ASL board are conducive to timely prevention of such faults and fast handling.

II. Noise Fault


[Fault Description] The current noise exists in the conversation, which influence the conversation quality. [Fault Analysis] The subscriber line fault, transmission clock or ground wire fault, telephone set fault, or 2M link fault at the access network (AN). [Troubleshooting] 1) 2) 3) Test subscriber line, and replace phone set. After confirming that the subscriber line and phone set work in normal status, check the transmission equipments clock, ground wire and relative alarms. At last check the 2M link at the AN.

III. Cross Talk Fault


[Fault Description]
3-3

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

Cross talk exists in the conversation between the AN subscribers, the voice of other subscribers being heard in the conversation. [Fault Analysis] LE fault, line fault, or 2M link fault. [Troubleshooting] 1) 2) Find out if the fault occurs to individual subscriber, or to all subscribers of the ONU. If cross talk exists in the conversation between AN subscribers, determine further the range of the cross talk. In general, check AN subscriber loop line, and interior line of the corresponding LE (such as HW line in C&C08). And wrong V5 link connection between LE and AN may also lead to cross talk.

IV. No Tone after Off-hook


[Fault Description] The fault of no tone after off-hook refers to the situation that the feeding current in the phone is normal and the comfort noise can be heard after off-hook but there is no dial tone. [Fault Analysis] 1) 2) 3) 4) 5) 6) 7) The LE or AN has not configured the correct subscriber data. The board on the LE which provides signal tone resource (such as the SIG board in C&C08) is faulty. There is a semi-permanent connection (SPC) established at the port, including non-V5 pre-connection. The E1 link connection is faulty, for example, mismatched links. Some port is fault, for example, the port is locally blocked, remotely blocked or in parking state. The V5 link timeslot assignment has error, which might be caused by the V5TK connection error, or the inconsistent configuration of the LE and AN. The PV8 board installed into the right slot is active, but the active/standby cable is not connected correctly (this cable should be connected well before delivery). [Troubleshooting] Determine the fault range: If only individual subscriber is in trouble, check the subscriber line. The major method is to connect a test phone at the Main Distribution Frame (MDF) to check if any fault occurs to the user phone. If no fault is found, it means the subscriber line must have trouble. If any fault is found, then connect the phone to the subscriber backplane to check if the fault exists. In this way, the subscriber line problem can be excluded. 1) Then check the data, mainly checking whether there is any problem with the subscriber data at both the AN and the LE. If they are inconsistent, the fault of no

3-4

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

tone after off-hook may be occurred. Then, trace signaling at AN. It is found that AN sends ESTABLISH incessantly but the LE makes no response. 2) If this fault exists in multiple narrowband frames, first check whether it happens sometimes or all the time. If it happens all the time, check whether subscribers of the corresponding LE are also experiencing this problem. If so, it is most likely that the problem is caused by the signal tone board (such as SIG board of the C&C08). In this case, exchange this board to check if the problem still exists. 3) If the fault happens sometimes, it is most likely that E1 line of the V5 has problem, that is, mismatched E1 lines. In this case, generally, the call is unidirectional (monologue) when the LE subscriber calls the AN subscriber.

V. Monologue
[Fault Description] The monologue means that after the called party B hooks off, party B can hear party A, while party A cannot hear party B. Another phenomenon is that the dial tone cannot stop, which indicates monologue occurs and upstream communication breaks off. [Fault Analysis] Physical faults, including fault of the E1 link, HW, backplane or circuit board may lead to the monologue. [Troubleshooting] If this fault happens between the AN subscriber and the other LE subscriber (this LE is not interconnected with the AN directly by V5 interface), it indicates that Signaling System No. 7 (SS7) or Signaling No. 1 between the exchanges might have trouble. If this fault happens between two AN subscribers, with the same exchange used, or between the AN subscriber and the subscriber of LE that is interconnected with the AN directly by V5 interface, then it is necessary to check if the V5 data configuration between the AN and LE is consistent, and if the E1 link is faulty, or mixed with another link.

VI. Non-stop Dial Tone


[Fault Description] The subscriber hears dial tone all the time after picking up the phone and dialing the number. [Fault Analysis] There are four kinds of frequent causes of it, as listed below: 1) 2) Single pass LE has no resources to receive and process numbers.
3-5

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

3)

The subscriber loop resistance is too high. That is to say, the variation of the loop resistance generated when the calling phone is picked up exceeds the range of monitoring sensitivity of the LE.

4)

Phone set fault.

[Troubleshooting] Try to dial by pulse dialing mode and Dual-Tone Multifrequency (DTMF) mode respectively. If the fault happens in the pulse dialing mode, trace signaling to check if the dial tone is sent to the LE, thus determining which equipment leads to the fault. If the fault happens in the DTMF mode, it might because that the loop resistance decreases, or the upstream HW is monologue. In this case, use the multimeter and oscillometer to measure the loop resistance and the status of HW. The subscriber loop resistance can also be measured by maintenance console. Perform loop line test to the corresponding subscriber port. If the measured Rab is far over 1800 ohm, the subscriber loop resistance is beyond the standard.

Note: Such fault occurs more frequently in rural areas. Generally, the problem can be solved by replacing the subscriber loop line and enlarging the loop line diameter, or using ASL board with better remote supply capability.

VII. Noisy and Non-stop Dial tone


[Fault Description] The dial tone is noisy, and does not stop. [Fault Analysis] The A/ law setting of subscriber board property does not match that of the exchange. [Troubleshooting] Reconfigure the subscriber board properties base on the settings of exchange.

3-6

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

3.2.2 Fault Case Study


I. There is unsteady dial tone (sometimes there is dial tone, sometimes there is not) after the AN subscriber picks up the phone because some inter-frame links are reversely connected.
[Fault Description] The MD5500 is connected with the LE through V5 interface, and connected with the RSP frame through four E1 links. The V5 interface functions normally, subscriber lines inside the RSP frame are normal, but there is unsteady dial tone (sometimes there is dial tone, sometimes there is not) after the AN subscriber picks up the phone. [Fault Analysis] After the subscriber picks up the phone, the system should send dial tone, allocate the timeslot and establish the connection. At the same time, the subscriber side should send the establish message to the LE, which processes this message and then sends the establish ack message to the AN, and allocates bearer channel based on the allocation message. Only after the channel is established, can the dial tone be sent. Any fault on the V5 link between the MD5500 and the LE, and the links between the MD5500 and the RSP frame will cause the failure in setting up the connection channel, thus causing the unsteady dial tone after the subscriber picks up the phone. Since this fault occurs at random, it can be judged that not all links are faulty. If the timeslot is allocated on the error link, there will be no dial tone. [Troubleshooting] Based on the fault analysis, check the V5 link between the MD5500 and the LE, and the links between the MD5500 and the RSP frame section by section. 1) 2) 3) 4) 5) Check the V5 interface link, and it is found normal. Check if the V5 link data configuration is consistent with the physical interface position based on the Link ID. Check the four links between the MD5500 and the RSP frame, as well as the ports, and they are found normal. Check if the frame link data configuration is consistent with the physical interface position, and it is found that the third and fourth links are reversely connected. Connect the third and fourth links correctly, and the fault is removed.

II. There is unsteady dial tone (sometimes there is dial tone, sometimes there is not) after the AN subscriber picks up the phone due to the inconsistent link.
[Fault Description]

3-7

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

The MD5500 is interconnected with some LE through eight E1 channels. When interconnected, the V5 interface is established correctly. The other E1 lines are in normal status physically. When a call is made, there is no dial tone most of time when the subscriber picks up the phone, however, sometimes, the dial tone appears regularly. [Fault Analysis] The ID of E1 link between the MD5500 and LE is incorrect, which causes part of subscribers to hear no dial tone upon picking up the phone. [Troubleshooting] Since the fault occurs regularly, the E1 link fault is located at first. Check the E1 link between the MD5500 and the RSP, and that between the MD5500 and the LE, use a signaling analyzer to analyze the V5 signaling, but no problem is found. As a matter of fact, the subscribers timeslots have already been assigned successfully before the fault occurs. It is estimated that it is the E1 link ID error that leads to timeslot assignment error. Reconfirmation of the E1 link ID shows that 6 E1 link IDs are mismatched. Modify them, and the fault is removed.

III. There is no dial tone after the narrowband subscriber picks up the phone due to the V5 link ID error.
[Fault Description] The MD5500 is interconnected with the LE by V5 interface through two E1 channels. After restart, the V5 interfaces of the LE and the MD5500 are normal. During the call test, it is found that there is no dial tone when the narrowband voice service subscriber of the MD5500 picks up the phone, and there are alarms generated on the maintenance terminal of the MD5500 when the subscriber picks up and hangs up the phone, indicating this subscriber port is locked and recovered. [Alarm Information]
ALARM 298119 INFO MINOR 0x0a100063 ----- 2002-09-06 08:57:19 ALARM NAME : Port locked indication PARAS INFO : Frame No.: 1, slot No.: 11, port No.: 1

DESCRIPTION : User port locked REASON : The subscriber is off hook or the subscriber line on MDF is short circuit ADVICE : Confirm if the subscriber is on-hook normally and the phone is normal. If necessary, check the MDF --- END

ALARM 298120 INFO WARN 0x0a100064 ----- 2002-09-06 08:57:21 ALARM NAME : Port unlocked indication

3-8

Troubleshooting Manual HONET Integrated Services Access Network


PARAS INFO : Frame No.:

Chapter 3 Narrowband Service Troubleshooting


1, slot No.: 11, port No.: 1

DESCRIPTION : User port unlocked REASON : Subscriber is on-hook, port resetting or user data is deleted ADVICE : No process --- END

[Fault Analysis] When the MD5500 is interconnected with the LE by the V5 interface, the V5 interface IDs at both parties should be consistent. In addition, such data as link ID, variable, should be consistent too. However, if the link IDs are not consistent, or in some other cases, the V5 interface can also show to be normal, that is to say, whether or not the V5 interface shows to be normal cannot be regarded as the judging standard during the [Troubleshooting] As we know, the dial tone of the AN narrowband voice service subscriber is transmitted over the bearer channel, therefore, the cause of this fault is most likely to be that the bearer channel has not been assigned, or the bearer channels assigned to the LE and AN do not match. The possible reasons the subscriber cannot be allocated with bearer channel are: this subscriber port has not been configured with subscriber data, the link IDs are not consistent, and the possible reason for the mismatched bearer channel is that the E1 link is mismatched. [Troubleshooting] Observe the V5 signaling, and it is found that after the subscriber picks up the phone, the ALLOCATION signaling sent from the LE contains the information about link ID and timeslot, but the MD5500 returns the ALLOCATION REJ signaling because of the incorrect link ID. Once receiving this refusal information, the LE delivers the command to lock the subscriber port. That is why the maintenance terminal of the MD5500 shows the alarm information of subscriber port being locked. Check the data and find that two link IDs of the V5 interface on the LE are 0 and 1, whereas those on the MD5500 are 2 and 3. Modify the latter V5 link IDs to 0 and 1, then restart the V5 interface, and the fault is removed. [Suggestion & Conclusion] Many kinds of problems may occur when V5 interface is interconnected, and signaling tracing is conducive to fault location. However, in case that the V5 interface shows to be normal, but there is no dial tone after off-hook, we can utilize link ID for fault location. If the interconnected link IDs are not consistent, an alarm will be created, indicating the link IDs are incorrect, and the V5 interface will not show to be normal, which will facilitate the fault location.

3-9

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

IV. All subscriber boards fail because of the reverse connection of two trunk cables in the same subscriber frame
[Fault Description] The trunk is debugged normally before ONU service configuration, and the E1 indicator of the RSP board is normal but no call can be made. Seeing from the maintenance terminal, the RSP board shows to be normal while the subscriber board shows to be faulty. [Fault Analysis] The trunk cable between the built-in SDH and the subscriber frame has two AMP connectors at the side of the subscriber frame, and they are not numbered, therefore, it is easy to connect the E1 line in reverse. There are two solutions for such problem: one is to exchange the two AMP connectors in the subscriber frame directly, and the other is to reconfigure the link data of these two RSP boards. [Troubleshooting] Based on the fault analysis, it is suspected that the digital trunk cables are connected in reverse. 1) Connect the port of the DT16/CESH board to the left RSP board, and then the right RSP board becomes faulty. It indicates that the trunk cables of the two RSP boards are connected in reverse. 2) Check the status of DT16/CESH board connected to the left and right RSP boards, and they show to be normal. It further indicates the two E1 trunk cables are connected in reverse. Exchange these two AMP connectors, and the fault is removed.

V. ISDN digital telephone set fails to make calls due to inconsistent PCM coding
[Fault Description] The MD5500 is connected with an RSP frame, and the DSL board in the frame is connected with a common ISDN digital telephone set. 1) 2) The port cannot be activated after the telephone set is connected. After solving the problem that the port cannot be activated, connect the telephone set with the NT1, and then make an outgoing call. The conversation quality is bad with too much noise. Trace the signaling and find that the bearer capacity is not approved. [Alarm Information] Trace the signaling on the LE and find that after the dial-up the system prompts that bearer capacity is not approved.

3-10

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

[Fault Analysis]
z z z

Physical connection line Data configuration NT1

[Troubleshooting] It is suspected that the physical connection line is faulty. Replace the telephone set and the NT1, and the port is found activated. It is suspected that the telephone set is faulty. Pick up the receiver, and there is no dial tone. After a while, the port is found activated. Hang up, the port is found deactivated. That is to say, only when the telephone set is in use, will the port be activated. Since the voice service becomes normal after the telephone set and the NT1 are replaced, it means that the data configuration of the MD5500 and LE is correct. Trace signaling on the LE, and the system prompts that bearer capacity is not approved. Because the MD5500 transparently transmits the ISDN signaling, and the bearer capacity is judged by LE, it is suspected that the voice coding of the telephone set must be wrong. To prove the above assumption, set the PCM coding of this ISDN telephone set as A law, and it is found that the port is activated normally, and voice service becomes normal. By now, the fault is removed. [Suggestion & Conclusion] There are two voice PCM coding modes available, A law and law. The former is applied in Europe and Mainland of China, and the latter is applied in America and Japan. These two coding modes cannot interwork directly, unless there is a conversion device between them. The baseband transmission rate corresponding to A law is 2048bps (E1), which is PCM30/31 coding, and the baseband transmission rate corresponding to law is 1544bps (T1), which is PCM24 coding. If one part of line transmits E1 signals, and the other part transmits T1 signals, the line will not be connected, and the system will prompt that the V5 bearer capacity is not approved.

3.3 MTA Service


3.3.1 Introduction to Principles
In the MD5500, the MTA is connected with the DSL board in the ONU frame by the 2B1Q interface, and it can provide one V.35/V.24 compatible interface and two V.24 interfaces at the user side. The V.35 interface supports synchronous rate of 128kbit/s and 64kbit/s, while the V.24 interface supports synchronous rate of 64kbit/s, and synchronous/asynchronous rate of 19.2kbit/s, 9.6kbit/s, 4.8kbit/s and 2.4kbit/s. That is

3-11

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

to say, the MTA can provide not only the N64k (N=2) service, but also the sub rate service, thus meeting the needs of multiple kinds of services. For the MTA service, the emphasis should be put on the following two cases: activation of the U port of DSL board, and rate settings of three ports of the MTA.

3.3.2 Frequently-used Troubleshooting Methods


Since the DSL board works together with the MTA, they must negotiate normally so that the port can be activated, which is fundamental to the normal operation of the equipment. The most frequent fault is that the U port of the DSL board cannot be activated, and the relevant handling methods are as follows:

I. Checking the quality of line and port


The loopback test can be used to check the quality of line and port. Since the hardware loopback test is hard to perform, the software loopback test can be adopted by command line mode. The MD5500 provides three kinds of software loopback modes for the MTA: 1) 2BDLoop

This kind of loopback is performed to the 2B1Q interface of the MTA. The loopback mode includes LOCAL and REMOTE. The local loopback can test whether the physical port and circuit from the upper layer equipment to the MTA 2B1Q interface work normally. The remote loopback can test the working state of physical port and circuit line from MAT 2B1Q interface to the terminal equipment. For example:
MD5500(config)#mta loopback 1/4/0 2BDLoop local

2)

BChannelLoop

This kind of loopback is performed to the B-channel in the 2B1Q interface, and the B-channel available includes B1 and B2. Such kind of loopback mode also consists of LOCAL and REMOTE. The local loopback can test if the physical lines of channel B1/B2 and the physical ports work normally by testing the service in channel B1/B2, while the remote loopback can test if the physical lines between channel B1/B2 and the terminal equipment, as well as the physical ports work normally. For example:
MD5500(config)#mta loopback 1/4/0 bChannelLoop remote

The following command is used to cancel the loopback:


MD5500(config)#no mta loopback 1/4/0

3)

Channel Loop

The MTA has three service output channels, 0, 1, 2. This kind of loopback is performed to these three service output channels. Such kind of loopback mode also consists of LOCAL and REMOTE. The local loopback can test if the physical channel in front of the terminal equipment, as well as the physical port work normally, while the remote

3-12

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

loopback can test if the physical channels between the terminal equipment and the MTA output port work normally. For example:
MD5500(config)#mta loopback 1/4/0 channelLoop 0 local

The following command is used to cancel the loopback:


MD5500(config)#no mta loopback 1/4/0

II. Checking the status of the U port of the DSL board and that of the MTA
1) Checking the status of the U port of the DSL board

MD5500(config)#narrow user MD5500(config-narrow-user)#show port state 1/4

The U port of the DSL board could be in the following kinds of status: activated, deactivated, and faulty. 2) Checking the working status of the MTA

MD5500(config)#show mta state 1/4/0

III. Replacing the DSL board


If the physical line and the MTA work normally, but the port cannot be activated, consider to replace the DSL board.

Caution: 1) When Port 0 serves as V.35 port, the second bit of the DIP switch on the back panel of the MTA should be placed into OFF state. If the service rate does not comply with the data configuration, the data configuration of the MTA needs checking. 2) The total bandwidth of three ports of the MTA cannot exceed 128k.

3.3.3 Fault Case Study


I. The MTA service is interrupted because of the incorrect data configuration.
[Fault Description] Three ports of the MTA are configured with the data services, but cannot be used. [Alarm Information] None [Fault Analysis]

3-13

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

Since the DSL port has been activated successfully, the physical line must be in normal status. The MTA has been powered on already. Check the data configuration of these three ports of the MTA, and it is found that the port rates of them are all 64k. For the 2B1Q interface, the bandwidth required for transmitting service is 128k. The function of the MTA is to multiplex the bandwidth of 128k to three ports. Therefore, the total service rate of these three ports cannot exceed 128kbit/s. [Troubleshooting] Disable Port 2 to transmit service, or lower the rate of any two ports, so that the total rate of these three ports does not exceed 128kbit/s, and then the MTA service becomes normal. [Suggestion & Conclusion] The total bandwidth of three ports of the MTA cannot exceed 128k. Only Port 2 is disabled, can Port 1 be disabled, and only Port 1 is disabled, can Port 0 be disabled.

3.4 HSL Service


3.4.1 Introduction to Principles
At present, there are two kinds of HSL service boards: H302HSL and H303HSL. The former is used in the HONET system, and the latter is new board developed based on Single-Pair High Rate Digital Subscriber Loop (SHDSL) technologies. The H302HSL is a kind of data service board, which can provide the N64k (N=31) data services of two V.35 ports and two E1 ports. The V.35 port works in Data Communications Equipment (DCE) mode, and the clock mode of the port includes: Internal, External, and Slave. The E1 port is used to access the remote data service unit downstream, or used as upstream interface to transmit data access from the V.35 port. In this case, the V.35 port data does not occupy the HW resources. The board is capable of locking different clock sources. It can use the clock provided by the backplane or lock the clock extracted from the E1 port. The H303HSL also supports the N64k service, at the same time, it also supports the G.SHDSL port, which can provide a symmetric rate of 2Mbit/s at most, and its transmission distance exceeds that of the Asymmetric Digital Subscriber Line (ADSL). It can extend the transmission distance of the E1/V.35 interface, which is used for accessing high-speed data service. Since the board can provide symmetric upstream and downstream data transmission rates, it is suitable for the service of which bi-directional rates are almost the same, such as video conference, and voice binding services.

3-14

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

I. Description of cables
The cables for the HSL board are connected to Pins 1~8 of the upper HEADER and Pins 25~32 of the lower HEADER respectively through AMP connectors. However, the cable for the H303HSL is different from that for the H302HSL: The first V.35 port and the E1 port of the H302HSL are led out of the upper HEADER through one cable, and the second V.35 port and the E1 port are led out of the lower HEADER through another cable. While the two E1 ports of the H303HSL are led out of the upper HEADER through one cable, and the two G.SHDSL port are led out of the lower HEADER through another cable.

II. Description of G.SHDSL port


1) Working mode

The two SHDSL ports must work in the same working mode (E1/V.35) simultaneously. When the first bit of the DIP switch S7 on the board is place into ON, the board works in E1 mode, and the connected terminal must use E1 modem. When the first bit of the DIP switch S7 is place into OFF, the board works in V.35 mode, and the connected terminal must use V35 modem.

Note: When the G.SHDSL port works in V.35 or E1 mode, its transmission distance is different. 1) In E1 mode, the maximum transmission distance is 3km; 2) In V.35 mode, the higher the port rate, the short the transmission distance: If N=3, the maximum transmission distance is 6km, and if N=32, the maximum transmission distance is 3km. However, considering the cable quality, the cable between the board and the terminal equipment should be as short as possible.

2)

Modem settings

Set the terminal type as CPE, and the SHDSL Standard as ANNEX_B, E1 modem: Set E1 frame structure as PCM31, without CRC function, V.35 modem: Set V.35 rate property as adaptive mode. 3) Port indicators

Since the SHDSL port cannot report alarms to the host, the indicators WAN1 and WAN2 of the SHDSL port are very important.

3-15

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

Whether the SHDSL port is activated can be determined by the indicator of the corresponding port. If the indicator is constantly ON, it means the connected Modem has been activated and the port can transmit data. If the indicator flashes quickly, it means the port is being activated. If the indicator is constantly OFF, it means the port did not receive the activating command. On the host, you can view the working status of the V35 port to find out the working status of the SHDSL port. If the V35 port is in working status, it means the SHDSL port has been activated and can transmit data. If the V35 port is unavailable, it means the SHDSL port is being activated or the port rate is 0.

3.4.2 Frequently-used Troubleshooting Methods


I. Checking physical connections (including cable and grounding)
The physical connection must be correct and meet the requirements of the engineering. Seen from the former cases, many frequent faults are caused by engineering problems. In addition, such kind of problems is not easy to be located and handled because they are hidden relatively. So, once a fault occurs, check the basic physical connection at first. Usually, the physical connection fault may occur to the following aspects: 1) 2) 3) 4) 5) 6) 7) E1 interface cable impedance (75 ohm or 120 ohm), E1 interface cable grounding, SHDSL cable connection, Connection of cables with main distribution frame (MDF), Grounding of main distribution frame and frame, Connection of subscriber terminal, In addition, the twisted pair connected to the subscriber terminal should make less joint, so as to avoid reducing the transmission distance caused by the noise.

II. Checking physical line and port through loopback test


The HSL can provide software loopback function through command line mode to test the physical line and port. The loopback mode includes LOCAL and REMOTE. The local loopback is performed to the inside of the HSL board to test if the physical lines inside the HSL board are in normal status. The remote loopback is performed to the outside of the HSL board to test if the if the physical lines outside the HSL board, as well as the remote equipment and ports, are in normal status.
z

To perform loopback to the HSL port, use the following command:

MD5500(config-if-hsl-1/5)#port loopback 0 local MD5500(config-if-hsl-1/5)#port loopback 0 remote

3-16

Troubleshooting Manual HONET Integrated Services Access Network


z

Chapter 3 Narrowband Service Troubleshooting

To cancel the loopback, use the following command:

MD5500(config-if-hsl-1/5)#no port loopback 0

For the V.35 port of the H302HSL, the PFA-35 BER tester can be used to assist in the loopback test. See Figure 3-2. The test procedures are as follows. 1) 2) 3)
z

Create an SPC between the V.35 ports of the HSL boards in the two frames. Connect the V.35 port of the local HSL board to the V.11/X.24 INTERFACE of the PFA-35, that is, Interface 20. Set the PFA-35 before the test: Turn on the PFA-35, and the version of the instrument and some menu options appear. Press button S1 on the front panel to select Menu1 on the screen. The parameter setting of the Menu1 is as follows:

Table 3-1 Parameter setting of Menu1


Parameter item Mode Interface Framing Emulation Tx clock Rx clock kbit/s(Tx) Parameter value Rx/Tx V.35 OFF DTE EXT:TC EXT: RC 64

Note: kbit/s(Tx): Please set according to the actual Nx64kbit/s rate. After the setting, press button S6 to select Menu2.

In the parameter setting interface of Menu2, press button S1 to select PRBS, and then press button S2 to select 29-1. Then press button S6 to enter the setting interface of Menu3.

The parameter setting of Menu3 is as follows:

Table 3-2 Setting of parameters in Menu3


Parameter name Timer Autoprint G.821 Alarms Resolution Beeper Parameter value OFF OFF USER ALL OFF HRS/MINS OFF

Press button S6 to select RUN, and the channel test starts. If the test result is normal, then the prompt OK will appear on the upper right corner of the interface.

3-17

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

4)

Perform local loopback test to the V.35 port of the opposite HSL board for twenty minutes. If no bit error is found, it indicates that this Nx64kbit/s digital channel is normal status. If any bit error appears, please locate the fault according to the following procedures:
MD5500 E1 channel
local loopback remote loopback V.35

E1 loopback E1 channel remote loopback

PFA-35

H S L

P V 8

P V 8

H S L

V.35

router

Local end

Opposite end

Figure 3-2 Networking diagram for HSL loopback test 5) Perform remote loopback test to the V.35 port of the local HSL to check whether the test result of the PFA-35 is normal. If not yet, please carefully check whether the settings of the PFA-35 are correct, whether the V.35 subscriber cable is normal, whether the local HSL works normally, and whether the HSL data are configured correctly. 6) If the previous test result is normal, please cancel the remote loopback of the local V.35 port and find the E1 channel bearing the channel at the local end. Then, perform local hardware loopback to this E1 signal and check whether the test result of the PFA-35 is normal. If not, please replace the E1 channel and test again. 7) If the previous test result is normal, perform hardware loopback to the E1 channel bearing this sub rate at the remote end. If the test result is abnormal, please replace the E1 channel and test again, test E1 channel with a 2M port BER tester, replace the transmission tributary, or test the optical transmission power. 8) If the previous test result is normal, please carefully check whether the data configuration of the remote HSL is correct. If necessary, replace the V.35 port, and HSL board to test again. 9) If the previous test results are normal, please cancel the local loopback of the remote V.35 port, and then connect both ends with data terminals for data transmission test. If everything is OK, the debugging ends. If the data transmission is Blocked or any bit error appears, please locate the fault according to the following procedures: 10) Please use a multimeter to test and make sure that all HSL cables are correct. Or locate the fault by performing loopback test section by section. For example, perform hardware loopback test to subscriber cable of the remote V.35 port to check if the test result is normal. If not, check the subscriber cable. If it is normal, please perform hardware loopback to the corresponding port of the distribution frame (if any) until the cause is found.
3-18

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

11) Check the data terminal settings at both ends. If necessary, please conduct interconnection test to the two terminals. Generally, the test result will show whether the fault occurs on the channel or the terminal.

Note: If data analyzer of other type is used for the test, the test procedures may differ, but the fault location method and process are the same.

III. Checking the data configuration, especially the timeslot fragment in the SPC list
The timeslot fragment means the discontinuous timeslot in the port of the HSL board. Too many fragments will cause the failure of establishment of the SPC of the port of the HSL board, or the interruption of the service. To show the SPC list, use the following command:
MD5500(config)#show spc from-connectid 0

This command can be used to show all SPC lists in the system, so as to determine if the port of the HSL board contains excessive timeslot fragments. In addition, the command MD5500(config-if-hsl-1/3)#show time_slot can be used to show the timeslots occupied by the port of the HSL board.

IV. Checking the setting of clock source


The HSL board has different clock setting modes based on different applications. The HSL board has three kinds of clock sources: First_E1_Clock (the first E1 clock), Second_E1_Clock (the second E1 clock), and HW_Clock (HW clock). To keep the data synchronous, if the service is transmitted upstream through E1 channel of this HSL board, then the E1 clock is selected. If the service is transmitted upstream through the system E1 channel, then the HW clock is selected. To set the clock source, use the following command: clock source {First_E1_Clock |Second_E1_Clock |HW_Clock}. Usually, the clock for the V.35 port is set as DCE external, and that of the V.35 port of the interconnected equipment should be consistent with this setting. To configure the clock for the V.35 port, use the following command:

MD5500(config-if-hsl-1/5)#v35_port modify 2 clock external mode dce.

3-19

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

V. Service interruption of SHDSL port


1) 2) Check if the port has been activated and can transmit data. Refer to Section 3.4.1 Introduction to principles. If the port has not been activated, check the line and the settings of Modem at first. For example, if the line length exceeds the actual transmission distance, and if configuration of the connected user terminal is consistent with that at the central office. 3) If no problem is found, check the working status of the board, for example, if the clock setting and the service data configuration are correct, and if the timeslot connection meets the actual requirements. 4) The SHDSL port also supports local and remote loopback commands, which can be used to determine if the SHDSL port service works normally.

VI. E1 interconnection Interruption


1) 2) 3) Check if the E1 port of the opposite equipment is set as PCM31 without CRC function, if not, modify it. Check if the board clock is set correctly. If the board clock is correct correctly, check if the port works normally by performing local loopback test to the E1 port. If necessary, perform remote loopback test to check if the physical line between the opposite equipment and this port is in normal state.

3.4.3 Fault Case Study


I. The HSL service is interrupted due to excessive timeslot fragments.
[Fault Description] Establish an SPC between the V.35 port of the HSL board and the E1 port of this board, configure N64k (N=10) data, but the service is interrupted all along. [Alarm Information] None [Fault Analysis] After the HSL board is checked, the physical fault is removed. To provide all kinds of services, an SPC must be created between the HSL board and the E1 port of the system or the E1 port of local board. To reach the N times rate, the SPCs of N timeslots need to be established. Query the SPC list to find that an SPC is established between the V.35 port and the E1 port of this board, and the timeslot starts with TS10, with the channelnum being 10. However, on the E1 port, TS12, TS16, and TS19 have been occupied by other SPCs, that is to say, ten timeslots allocated to the HSL board are

3-20

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

discontinuous, and excessive timeslot fragments exist, which causes the service interruption. [Troubleshooting] Check the SPC list to find that TS17 to TS26 of the other E1 port of the HSL board are not occupied, that is to say, no timeslot fragment exists. Recreate the SPC between the V.35 port and the other E1 port, and then the service is realized. [Suggestion & Conclusion] For the allocated timeslots, two or more fragments will result in the service interruption. During the establishment of semi-PVC, the semi-PVC at higher rate will be established first, and then comes the semi-PVC at lower rate.

II. The port on the HSL board connected with the MD5500 cannot be activated due to improper wire connection on MDF.
[Fault Description] The MD5500 is connected with the RSP frame, and the H303HSL in the frame is connected with a remote G.SHDSL Modem by V.35 interface. After the modem and the HSL H303HSL are connected correctly, the port cannot be activated all along. [Alarm Information] None [Fault Analysis]
z z z z z z

Board software does not match the host software. The semi-PVC is not configured correctly. The port is not configured correctly. The modem is not configured correctly. The port and the modem cannot interwork normally. The H303HSL and the modem are not connected properly.

[Troubleshooting] 1) 2) 3) 4) Upgrade the board software to make it match the host software. However, the port cannot be activated yet. Check the semi-PVC data, and no error is found. The port and the modem are of the same type (V.35), and they are connected well. Usually, the ex-factory settings of the port and the modem can ensure the normal activation of the both ports. There should be problem if the ex-factory settings have not been modified. 5) On the MDF, perform hardware loopback to the H303HSL and the modem, and it is found that the port can be activated. It is suspected that the wires on the MDF are not connected properly. Check it carefully, and it is found that the wire

3-21

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 3 Narrowband Service Troubleshooting

corresponding to this port is in loose contact, which results in line disconnection. That is why the port cannot be activated. 6) Reconnect the wire on the MDF, and the port is activated normally.

3-22

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

Chapter 4 Broadband Service Troubleshooting


4.1 Overview
4.1.1 Broadband Service Classification
The MD5500 can provide the following broadband services: 1) Implement the broadband access server (BAS) function by IPU board.

It supports multiple kinds of access protocols:


z z z z z

Point-to-Point Protocol over Ethernet over ATM (PPPoEoA) Point-to-Point Protocol over Ethernet (PPPoE) Point-to-Point Protocol over ATM (PPPoA) Internet Protocol over Ethernet over ATM (IPoEoA) Internet Protocol over ATM (IPoA) Implement the transparent transmission function of user services by AIC board. Implement the transparent transmission function of user services by EPU board. Provide circuit emulation service.

2) 3) 4)

4.1.2 Application of Cell Statistics in Fault Location


The cell statistics analysis method is often used to locate and handle the broadband service faults. It can query differentiated cell statistics of a specified connection based on the given query conditions to facilitate locating the problem. The following part lists the cell statistics functions supported by the boards in the MD5500:
z z z z z z z

ASX: Support PVC-based and board-based cell statistics. AIC: Support PVC-based, board-based, and optical interface-based cell statistics. IPU: Support PVC-based and board-based cell statistics. CES: Support port-based cell statistics. LANC: Support board-based cell statistics. FR: Support board-based cell statistics. AIU: Support PVC-based, board-based, and port-based cell statistics.

The following part lists the cell statistics function supported by the boards in the UA5000:
z z

APM: Support PVC-based, board-based, and port-based cell statistics. AIU: Support PVC-based, board-based, and port-based cell statistics.

4-1

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

1)

Locating fault by PVC traffic statistics

The following example queries the PVC cell statistics of AIC board at frame 0 slot 14:
MD5500(config)#show cell statistics 0/14/0 vpi 0 vci 33 --------------------------------------------------------------Up stream traffic Receive cells Send cells 277 277 0 Down stream traffic 2914 2914 0 Difference 2637 2637

Difference

---------------------------------------------------------------

Seen from the statistics data, the number of received cells and that of the sent cells in both the upstream direction and downstream direction are equal. It means this connection is normally processed by AIC board, without any loss of cells. 2) Locating port fault by loopback and port cell statistics

Perform loopback test from the opposite port to the AIC port, and then query the cell statistics of the AIC port:
MD5500(config)#show cell statistics 0/12/0 --------------------------------------------------------------Port Receive cells 0 39 Send cells 45 Difference 6

---------------------------------------------------------------

Ping the IP address of the opposite port, and then query the cell statistics of the AIC port again:
MD5500(config)#show cell statistics 0/12/0 --------------------------------------------------------------Port Receive cells 0 54 Send cells 60 Difference 6

---------------------------------------------------------------

If the queried results show that the numbers of received and sent cells are increased, and the difference between the two numbers keeps equal, it means the line between the local port and opposite port is in normal state.

Note: Port receive cells mean the cells that are transmitted from this port to the inside of the MD5500, and send cells mean the cells that are transmitted from this port to the outside of the MD5500.

4-2

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

4.2 BAS Service


4.2.1 Introduction to Principles
I. Overview
The IPU board of the MD5500 is used to implement broadband access service function, which connects the MD5500 with the IP network. It can bear multiple kinds of protocols, such as PPPoA, PPPoE, PPPoEoA, IPoA, IPoE, IPoEoA, and so on. The IPU board implements the subscribers access, authentication and accounting, and routing functions in combination with the ASX. Having received users packets, the IPU board analyzes them first. If they are control packets, they are transmitted to the ASX board and processed by the host software. After the host authenticates the subscriber, it will deliver the lists related to the subscriber to the IPU board, who will process the data packets to be transmitted to the subscriber based on these lists. In addition, the host can configure the relevant network-side routes based on analyzing and processing packets received from IPU board.

II. PPPoEoA
PPPoEoA is a widely-used dial up access authentication mode in the ADSL access mode. In this mode, it is easy to manage and maintain the Remote Terminal Unit (RTU), which only needs to configure the RFC1483B protocol. The subscriber end needs to install the PPP over Ethernet (PPPoE) dial-up software to access the IP network in real time based on the actual needs. The following diagram shows the principle of PPPoEoA dial-up access mode.

PC
IP PPP MAC

RTU

DSLAM

MD5500
IP PPP

ISP
IP

MAC 1483b

MAC 1483b ATM ADSL ATM PHY ATM PHY PHY PHY MAC MAC

PHY

PHY

ATM ADSL

Figure 4-1 PPPoEoA dial-up access of the ADSL subscriber The principle of such dial up access mode is: Media Access Control (MAC) frames are transparently transmitted between the RTU and MD5500 by means of RFC1483B. The subscriber gets access to the Internet through the Ethernet port of the RTU. The relevant realization process is as follows: When the subscriber wants to get access to

4-3

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

the Internet, he can initiate a PPPoE call through the PPPoE dial-up software, and then the MD5500 authenticates the subscriber based on the username and password contained in the PPPoE call message. If the authentication is succeeded, the system will allocate an IP address for this subscriber, then, the subscriber can get access to the websites of Internet through the routing function provided by the MD5500. Disadvantages of PPPoEoA: The client software needs installing. Currently, almost all client software has defects, which makes the maintenance cost rather high.

III. PPPoA
PPPoA is intended for the Always online subscribers, who can get access to the Internet at any time once he passes the one-stage dialing authentication through the RTU. The following diagram shows the working mode of PPPoA dial-up access.

PC
IP MAC

RTU
IP PPP MAC 1483R ATM ADSL

DSLAM

MD5500
IP PPP 1483R MAC

ISP
IP

MAC

ATM ADSL

ATM PHY

ATM PHY PHY PHY

PHY

PHY

Figure 4-2 PPPoA dial-up access mode of ADSL subscriber As shown in the figure, the PPP call is initiated by the RTU and is terminated by the MD5500. Then, the MD5500 will authenticate the subscriber based on the username and password. If the authentication is succeeded, the system will allocate a public address from the address pool for the subscriber. Thus, the subscriber can transmit IP packets from PC to the MD5500 through such PPP link, and then the MD5500 further transmits the IP packets to the IP network. It should be pointed out that the RTU is interconnected with the MD5500 by means of RFC1483R, so the MAC-based TCP/IP cannot be supported between them. An Ethernet port of the RTU can be connected with either a PC or a LAN. Since the authenticated IP address is allocated to the RTU, the connected PC or the LAN needs to configure the private address for Network Address Translation (NAT) on the RTU when transmitting IP data packets. This will cause other subscribers of the MD5500 unable to access PPPoA subscribers. This access mode is difficult for carriers to maintain and operate the RTU, and is usually not suitable for number allocation for large amount of individual users at the same time. In addition, this access mode cannot provide more functions than the

4-4

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

dedicated line access mode for the small-sized enterprise or Internet cafe. Thats why it is seldom applied.

IV. IP over Ethernet over ATM (IPoEoA)


In this mode, the subscriber terminal does not need to be authenticated and apply for IP address (but it needs to configure fixed IP address). Disadvantages: In this mode, the subscriber management and authentication cannot be performed. The MD5500 supports IPoEoA access mode of both the ADSL subscriber and LAN subscriber. The service process of them is as follows:

PC
IP MAC

RTU

DSLAM

MD5500
IP

MAC 1483B

MAC 1483B ATM ADSL ATM PHY ATM PHY

PHY

PHY

ATM ADSL

Figure 4-3 IPoEoA access mode of the ADSL subscriber

PC
IP MAC

LAN Switch

DSLAM

MD5500
IP

MAC

MAC 1483B

MAC 1483B ATM PHY

PHY

PHY

PHY

ATM PHY

Figure 4-4 IPoEoA access mode of the LAN subscriber The ADSL subscriber gets access to the Internet through the Ethernet port of the RTU. The relevant realization process is as follows: After the subscriber PC is connected to the Ethernet port of the RTU, the RFC1483B is realized, the MAC frames are adapted into ATM cells, which are transmitted from the RTU to Digital Subscriber Line Access Multiplexer (DSLAM) over the PVC, and then to the IPU board of the MD5500. Here, the RFC1483B is implemented. At the same time, the IP packets are transmitted to the higher layer network by the routing forward function of the IPU board.

4-5

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

The LAN subscriber gets access to the Internet through the Ethernet port of the LAN board of the MD5500 or DSLAM. At the same time, the RFC1483B function is performed by the LAN board. The other realization process is the same as the ADSL access mode. It should be pointed out that the MD5500 needs to implement L3 transfer function under this condition.

V. Internet Protocols over ATM (IPoA)


Usually, the IPoA access mode is suitable for enterprise users. It needs no user authentication, and the user has fixed IP address. The MD5500 only implements L3 transfer function. Figure 4-5 shows the principle of IPoA access mode.
PC
IP MAC MAC

RTU
IP 1483R ATM ADSL

DSLAM

MD5500
IP 1483R

ISP
IP

MAC

MAC

PHY

ATM ADSL

PHY

ATM PHY

ATM PHY PHY PHY

Figure 4-5 IPoA access mode In IPoA access mode, IP packets are encapsulated directly into ATM cells for transmission based on the RFC1483R between the RTU and MD5500. It should be pointed out that this access mode is different from the IPoEoA access mode. The IPoEoA access mode needs RFC1483B encapsulation, and the RTU should be configured with IP address. In addition, if the RTU does not support routing function, the NAT should be performed before IP packets can be transmitted, and the connected PC or the LAN needs to be configured with the private address, which is converted into public address by the RTU. The IPoA access mode is also suitable for the ATM subscribers who do not adopt ADSL access mode, i.e., ATM UNI subscribers (including E1 IMA, E1 ATM, 155M ATM, and E3 ATM subscribers).

4.2.2 Frequently-used Troubleshooting Methods


There are many reasons for the service faults occurring to the deployment and daily maintenance. However, seeing from the experience and statistics, most of the faults are resulted from incorrect service configuration data, mismatched equipment interconnection mode, and faulty user terminal.

I. PPPoA subscriber cannot get online.


1) 2) Check username and password, Use the command show online user to observe if this user is online,

4-6

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

3) 4) 5) 6) 7) 8)

Check if the port of the ADSL board of the DSLAM is activated, Check if the PVC configured by the RTU is consistent with that configured by the DSLAM, Check if the authentication mode configured at the RTU (PAP, CHAP) is consistent with that configured at the virtual template of the MD5500, In case of the local address pool, check if the user group configured on the MD5500 has idle address pool, and if this address pool is activated, In case of remote authentication, check if the RADIUS server configuration is consistent with the RTU user configuration, Check the MD5500 to see if the PVC of this online user is in UP state.

The troubleshooting method for failure of PPPoEoA subscriber getting online is the same as the above-mentioned methods.

II. PPPoE subscriber dials up successfully, but cannot get access to the Internet.
It is might caused by the routing problem of the PC. Please check if the PC has multiple routes directing to the same destination, and check if the route created by the PC after dialup is correct.

III. The MD5500 cannot ping PPPoE/PPPoA subscribers


The virtual template (VT) of the MD5500 has not bound the IP address of the upstream interface.

Note: Only after the virtual template leases the IP address of the upstream interface, can the terminal of the MD5500 ping the PPP subscriber. Whether the virtual template leases the IP address of the upstream interface does not influence the users access to the Internet. The specific configuration is as follows: MD5500(config-if-virtual-template1) # MD5500(config-if-virtual-template-1)#ip unnumbered fast-ethernet 0/12/0 (lease the IP address of the upstream interface, which must be activated, i.e., the state is UP.)

IV. Some packets are lost when passing FE/GE port.


Check if the working mode of the port is consistent with that of the opposite equipment. They should work in the same mode after negotiation.

4-7

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

V. IPoEoA subscriber cannot get access to Internet normally.


Check if the ATM sub-interface address has been configured, and if the subscriber IP address and the sub-interface address are in the same network segment.

VI. Use ping command to locate fault


You can run the ping command (packet capture tool can be used if necessary) to judge whether the upstream or downstream equipment becomes faulty. The detailed method is: ping from the subscribers PC to the IP address of the interface of the MD5500 and that of the interface of the interconnected upstream equipment respectively, and then ping from the MD5500 to the IP addresses of the interfaces of the interconnected upstream and downstream equipment respectively.

VII. Frequently-used methods for fault location


1) 2) Check the packet receiving and sending status of the port. View routing table

Query the next hop based on the destination address in the routing table. And make sure if the address is consistent with the actual routing. Use show ip route command to view the information of the routes that are currently operating normally. Use show ip route static command to query all static routes. And use show ip route detail command to query detailed routing information. After the IP address of an ATM sub-interface is configured, the system should add the corresponding route entry to the routing table automatically, the destination address is the network segment corresponding to the sub-interface, and the next hop is the IP address of this interface. 3) Query fib entry

Use the command show fib to query the corresponding relationship between the IP address and interface. This entry describes the corresponding relationship between the destination IP address and forwarding interface, and this entry corresponds to the entry of the routing table. 4) Query ARP entry

Use the command show arp all to query the ARP entry. This entry describes the corresponding relationship between the IP address and MAC address. Based on queried results, check if their relationship is lost or mismatched.

4-8

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

4.2.3 Fault Case Study


I. PPPoEoA subscribers cannot get access to the Internet because the ATM sub-interface is shutdown.
[Fault Description] Networking mode: BSL + MD5500 Fault: PPPoEoA subscribers cannot get access to the Internet by dial-up mode. [Alarm Information] No alarm occurs to the equipment. The dial-up program returns the information timeout. [Fault Analysis] 1) 2) 3) 4) Check if the BAS cannot be found, or the authentication failed. Check if the physical line E1 port is in faulty state. Check if the BSL sends cells to the MD5500, if yes, the MD5500 might have problems. If the cells are sent to the MD5500, check carefully the data configuration of the MD5500. [Troubleshooting] If the dial-up program returns the information timeout, it usually indicates the BAS has not been found. If the dial-up program returns the information indicating the failed authentication, it indicates the authentication configuration has some problem. Here, the former case is presented, so it is only necessary to check the configuration related to the protocol. 1) Check the E1 line between the MD5500 and BSL.

Use the command MD5500(config-if-ces-0/1)# show port mode to find that Port 1 is in normal state. 2) Query the cell statistics information of the CES port.

MD5500(config)#show cell statistics 0/1/1 -------------------------------------------------Port Receive cells 1 18 0 Send cells 18 Difference

--------------------------------------------------

According to the queried results, the Send cells value is 0, while the Receive cells value is not. Receives cells mean the cells sent from the BSL and received by this E1 port. Run the dial-up program and query the cell statistics information of the CES port again to find that the Receive cells are increased, while the Send cells are still 0. Based on

4-9

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

such results, it can be concluded that the BSL has sent cells to the MD5500, but the MD5500 has discarded them directly without processing, therefore, the fault of BSL can be excluded. 3) Check the basic information about the configuration of protocol.

The following commands can be used to query the information about the virtual template, VPDN group, and PVC respectively, which are fundamental to the protocol configuration.
MD5500(config)#show interface virtual-template 1 MD5500(config)#show vpdn-group 1 ------------------------------------------------------VPDN-Group number Protocol type Accept dialin PPPoE VT PPPoE limit per-VC/port PPPoE limit per-mac PPPoE limit per-IPU : : : : : : 1 PPPOE 1 100 5 2048

------------------------------------------------------MD5500(config-if-atm-0/13/8.1)#show pvc -----------------------------------------------------------------------------Index interface Vpi/Vci Encap Proto Para Car State VCC Site

-----------------------------------------------------------------------------40 atm0/13/8.1 0/ 400 aal5snap pppoe ------ OFF/OK down up 1 10 uni

Total Number of PVC is:

------------------------------------------------------------------------------

According to the queried results, the configuration of virtual template and VPDN are normal. However, the PVC is DOWN. This may be caused by the shutdown operation performed to the interface. Continue to use the following command:
MD5500(config)#show interface atm 0/13/8.1

atm0/13/8.1 current status: administratively down layer protocol: DOWN Interface description: MD5500, Sub Atm Interface Maximum transmission unit: 1500 Internet protocol processing is disable

Current status of link

The current status of the interface is administratively down, which indicates the shutdown operation is performed to the interface. By now, the fault is located.

4-10

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

4) 5)

Use the command MD5500(config-if-atm-0/13/8.1)#no shutdown to restart the interface. Run the dial-up program, and the problem is resolved.

II. Service interruption caused by setting static ARP on the MD5500 after changing the interconnected port
[Fault Description] The Port 0 (IP address: 202.102.3.1/28) of the IPU board of the MD5500 is interconnected with Port 22 (IP address: 202.102.3.2/28) of some router. Both the port work in duplex 100M mode. Due to the service needs, change the interconnected Port 22 to Port 24, without changing the port address. After that, the service is found interrupted. The MD5500 cannot ping the IP address of the interconnected interface, as well as the IP address of any public network. [Alarm Information] Service is interrupted, and the MD5500 cannot ping the IP address of the interconnected upstream interface. [Fault Analysis] 1) The MD5500 can ping the IP address (202.102.3.1) of the local upstream interface, while the prompt time out is given when pinging the IP address (202.102.3.2) of interconnected interface. 2) Reuse the interconnected port 22, the MD5500 can ping this port, and the service resumes. It means the local upstream interface of the MD5500 and the network cable is in normal status. 3) 4) Connect Port 24 with a PC, and this PC can ping the IP address of this port, indicating the port is in normal status. Connect the MD5500 with Port 24 again, change the IP address of this port as 202.102.3.3/28, the service resumes, and the MD5500 can ping the IP address of this port. 5) It is doubted that this IP address (202.102.3.2) is bound with the MAC address of Port 22. Use the following command to show the static ARP of the MD5500:
MD5500(config)#show arp --------------------------------------------------------------IpAddress 202.102.3.2 Mac_Address aa-bb-cc-11-22-33 Type static Status

--------------------------------------------------------------Total 1 items ---------------------------------------------------------------

4-11

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

This address is the MAC address of Port 22. When Port 24 is used, the MAC address is changed accordingly, thus making the MD5500 upstream channel interrupted. [Troubleshooting] On the MD5500, run the command no arp to delete this static ARP. 1) 2) Change the interconnected port as Port 24 (IP address: 202.102.3.2/28), and the other settings remain unchanged. The MD5500 can ping the IP address of the interconnected port, and the service resumes. [Suggestion & Conclusion] Usually, the dynamic ARP is applied, that is to say, when the system sends out ARP packets, the opposite equipment makes response to the local end, sometimes, however, in order to reduce the intermediate ARP request and response process, the static ARP is applied. In this case, if the MAC address of the opposite equipment is changed, the static ARP should be modified accordingly.

4.3 L2 Transparent Transmission Service


4.3.1 Introduction to Principles
The EPU board of the MD5500 provides the L2 transparent transmission function, i.e., the MD5500 transparently transmits L2 packets accessed from the PVC or FE interface through the high speed service board (EPU board), and FE/GE interfaces are provided in the upstream direction. Currently, the EPU board supports the following packet formats: at the user side, PPPoEoA, PPPoE, IPoEoA and IPoE modes, at the network side, PPPoE and IPoE modes. At the same time, the network port supports tagged and untagged types of packets, and the packet type supported by the access port must be consistent with that of its bound network port.

4.3.2 Frequently-used Troubleshooting Methods


There are many reasons for the service faults occurring to the deployment and daily maintenance However, seeing from the experience and statistics, most of the faults are resulted from incorrect service configuration data, mismatched equipment interconnection mode, and faulty user terminal.

4-12

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

I. Checking points in case of service interruption


1) When the EPU board interconnects with other equipment, the working mode (auto, 100full, 100half, 10full, 10half) and the property (Untagged, Tagged) of the interconnected port must be consistent with those of the local port, 2) 3) When the EPU board connects with some downstream equipment, if the upstream equipment supports VLAN, then check if the VLAN ID is correct, If the upstream interface property is Tagged, the accessed PVC must be configured with VLAN ID, and the different PVCs on the same EPU board must have different VLAN ID, 4) In case that the upstream interface property is Tagged, if the VLAN user accessed from the access port cannot get online, check if the VLAN ID of this user has been bound with the PVC, and check if the network port is UP.

II. Fault location by querying traffic information


1) Query the traffic information about the specified PVC.

The following command can be used to query the upstream and downstream traffic of the PVC bound with the network port.
MD5500(config-if-fast-ethernet-epu-0/10/0)#statistic { pvc<K> }:pvc { vpi<U><0,255> }:0 { vci<U><256,2255> }:256 command statistic pvc 0 256 VPI:0 VCI:256 UNIT:KByte :220 :23 :0 :0 :84 :5 :0 :0

UpPacket UpByte

UpPacket Overturn UpByte Overturn DownPacket DownByte

DownPacket Overturn DownByte Overturn

2)

Query the traffic information about the specified port.

MD5500(config-if-epu-0/10)#statistic { port<U><0,7> }:0 command: statistic 0 epu-fast-ethernet0/10/0, UNIT:KByte UpPacket UpByte :23 :0 :220

UpPacket Overturn

4-13

Troubleshooting Manual HONET Integrated Services Access Network


UpByte Overturn DownPacket DownByte :5 :0 :0 :0 :84

Chapter 4 Broadband Service Troubleshooting

DownPacket Overturn DownByte Overturn

4.4 ADSL Service


4.4.1 Introduction to Principles
The HONET accesses the ADSL service by ONU. The ADSL service boards of the ONU include ADL, CSL, BSL, and B08. Besides ADSL subscriber interfaces, the BSL and B08 can also provide E1 or IMA E1 upstream interfaces. The BSL services are accessed to the MD5500 through EA16 board. The BSL service faults mainly include two major parts: one is the user-side faults (mainly ADSL service faults, it will not be discussed here), and the other is upstream network-side E1 faults. The following part will introduce how to locate such faults by loopback test.

I. Conditions for BSL upstream E1 interface interconnecting with E1 port of the MD5500
There are three conditions for such kind of interconnection: Firstly, the physical line between the two ports should be in normal status. Secondly, the port should be ATM UNI. Thirdly, the setting of CRC4 function should be consistent.

II. Fault location by loopback test


The H521E41T of the H521BSL (H521B08) consists of three units: E1 interface unit (LIU), cellE1 transfer unit (ETU), and cell buffer transfer unit (Logic). All the units support the loopback test function. There are three kinds of loopback forms, LIU loopback, ETU loopback and LOGIC loopback.
UTOPIA

E1

LIU

ETU

Logic

ADSL chipset

ADSL

remote local remote local remote local

LIU loopback

ETU loopback

UTOPIA loopback

Logic loopback

Figure 4-6 Loopback diagram 1) Logic loopback


4-14

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

The logic loopback means the loopback performed to the PVC, and only remote loopback is provided. As shown in Figure 4-6, the loopback direction is in the direction of E1 side. After the logic loopback, all cells from the E1 port are sent back along the original path. 2) ETU loopback

The ETU loopback is located at the EMU. It includes ETU LOCAL, ETU REMOTE, Universal Test & Operations PHY Interface for ATM (UTOPIA) LOCAL, and UTOPIA REMOTE loopback forms. After the ETU LOCAL loopback, cells from the ADSL port to this port will return back along the original path. After the ETU REMOTE loopback, cells from the E1 port to this port will return back along the original path. The UTOPIA LOCAL loopback and UTOPIA REMOTE loopback are the same as the ETU loopback, except for the loopback position. See Figure 4-6. 3) LIU loopback

The LIU loopback means the loopback performed to the LIU. After the LIU remote loopback, cells received by the E1 port will still be sent out from this port. After the LIU local loopback, cells received by the ADSL port will return back along the original path.

4.4.2 Frequently-used Troubleshooting Methods


I. Both the Internet access service and voice serivce fail.
Usually, this kind of fault is caused by line malfunction. Report this fault to the subscriber line test system to remove the line fault at first. After that, make sure the telephone service is OK, and then check if the Internet access service is available.

II. The voice service is in normal condition, but the Internet access service fails.
This is a kind of typical fault. The cause of it may be concerned with all equipment or elements of the broadband network, which include upstream ATM node, broadband access server, ADSL port at the central office end, RTU, user terminal, line, and so on. By finding out the status of RTU indicator, operation and setting of user PC, the fault can be located with the help of the NM function. The specific operations are as follows: 1) Query the type of RTU and the status of RTU indicator.

Each kind of RTU has Ethernet indicator, ADSL connection indicator and power supply indicator, although the English name of indicator is varied from each other. 2) Locate the fault based on status of the indicator.

4-15

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

The following part takes indicators of E_TEK MODEM as example to describe how to locate the ADSL fault based on the RTU status indicators. This process is also effective on other kind of ADSL MODEM (RTU), but note that different RTUs have different English names for the indicator.
z

Status of RTU power supply indicator (PWR)

If the RTU power supply indicator is off, it indicates the power supply of RTU is not connected well, or the RTU is faulty. If the power supply of RTU can surely work normally, but all indicators of the RTU are off, then it is undoubted that the RTU becomes faulty. If the power supply works and is connected normally, the RTU power supply indicator is on, but the Internet access still fails, please proceed with the following steps.
z

Status of RTU WLK indicator

If the WLK indicator is on, it means the wide area network is connected normally, that is to say, the ADSL line connection is in normal state. If the WLK indicator is off, it means the RTU does not work normally. In this case, reconnect the RTU and then power it on to check if it can work normally. If the WLK indicator flashes ceaselessly, it means the ADSL line is connecting or cannot be connected all along, which is caused by the line malfunction. In this case, check first of all if the telephone line between the RTU and splitter is in good contact, and then check the indoor telephone line joint. If the fault still remains, ask the subscriber line test system to check the external line.
z

Status of RTU LLK indicator

If the LLK indicator is on, it means the Ethernet is connected normally. Otherwise, it means the network cable between the RTU and PC network interface card (NIC) is not connected well, or the NIC has fault (two indicators of the NIC is helpful for fault location). Confirm the network cable connection, replace NIC (if necessary) and the fault is removed.
z

Status of RTU LAC indicator

If the LAC indicator flashes, it means the PC is communicating with the LAN (which connects with the RTU) normally. It is an auxiliary indicator for the LLK indicator.
z

Status of RTU ALM indicator

If the ALM indicator is on, it means bit error or other fault occurs. If it becomes on frequently, it means the line bit error or the line interference is severe. The Internet access rate is rather slow. In this case, power on the equipment again. If the fault still remains, report it to the subscriber line test system to check the external line. 3) If the above-mentioned indicators work normally, but the Internet access service still fails, the user end, including user PC, upstream port, or the user operation must have errors. In this case, proceed with the following methods for troubleshooting.

4-16

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

Usually, the subscriber access mode is PPPoE mode. Please check if the PPPoE authentication phase can be presented. If it can be presented, but the authentication fails, or the authentication is succeeded but the Internet access service still fails, the fault might occurs to the upper layer of the access server. Check if the same fault occurs to the other port. If the PPPoE dialing phase cannot be presented, please reinstall the dial-up program and try it again after setting the PC correctly. The following errors should be specially paid attention to:
z

TCP/IP property is set incorrectly. The IP address should be set as <Obtain IP address automatically>. The logon username and password are incorrect. The dial-up program has not been installed properly.

z z

If the PPPoE authentication is succeeded, but all websites cannot be accessed, it means the access server is faulty. If only some website cannot be accessed, then this website has problem.

III. The Internet access is succeeded, but the access rate is rather slow.
1) Find out if the access rate is slow all along, or sometimes.

If the access rate is lower than 500kbit/s all along, it is usually caused by line malfunction. In this case, check the physical access rate, if the port access rate is limited, and what the limit access rate is. If the physical access rate is rather high, it indicates the line is in normal status, and the possible cause of the fault might be: the port of the broadband access server needs expansion. If the Internet access rate reaches the limited rate of the port, the reason of the fault is caused by the limited access rate. 2) If the line is rather short, but the Internet access rate cannot reach 2Mbit/s, then check the physical access rate of this port, and the line attenuation. If the physical access rate reaches 2Mbit/s or the limited access rate, it means the line is in normal status. Then, it is necessary to check the interleaved depth setting. If the interleaved depth is 64, then the TFTP file transmission rate can only reach 1.5Mbit/s at most due to the limit of the TCP/IP. 3) Check the physical access rate of this port. If this access rate is normal, but is greatly different from the file transmission rate, it means the upstream interface node rate encounters bottleneck problem. 4) In addition, the Internet access might slow down if the line is rather long, the line noise is rather large, or the internal line is in poor quality.

4-17

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

IV. The Internet acccess is not stable, and the access is often disconnected.
Usually, this kind of fault is caused by too large high frequency attenuation resulting from the poor line quality, rather long line, rather large line noise, loose contact of the line. In this case, refer to the following troubleshooting methods. 1) 2) 3) 4) 5) 6) 7) 8) Check if the line is over 3km. If yes, the line might be too long. Compare with the nearby ADSL subscribers to see if the same fault exists. Check if any voice equipment is installed ahead of the MODEM, if yes, remove it. Check if the splitter is installed correctly. Check if the telephone or other electric equipment is being used when the access is disconnected so as to judge if any equipment interferes with the Internet access. Check if the internal line joint and the telephone jack are in good contact. Check if the internal line is in good quality. Check the constrained conditions for the connection. Check the connection parameters related to this port. Ask the subscriber line test system to check the external line.

V. BSL board E1 loopback test


BSL

E1

loopback PVC

ADSL

modem
PC

Figure 4-7 E1 loopback test diagram Steps: 1) 2) 3) Connect the PC to Port 1 of the BSL through the Modem, and then activate the port. Create a service PVC between the ADSL port 1 and E1 port 1. Set the loopback.

BSL(config-ATM-0/0)#loopback etu local <portId>{1-4}:1 Are you sure to set ETU local loopback? (y/n) [n]:y Set ETU port loopback successfully.

4)

Run the command ping 192.168.1.2 -t on the PC. Then, run the command show statistics cid 1 to query the PVC cell statistics. It can be seen that the upstream and downstream cells are increased simultaneously (bold characters below), that is to say, the cells are looped back at the ETU.

BSL(config-ATM-0/0)#clear statistics cid 1 Are you sure to clear VCC statistics information?(y/n) [n]:y PVC 1: cell statistics data has been cleared.

4-18

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

BSL(config-ATM-0/0)#show statistics cid 1 E1 <-> ADSL cell count: ----------------------PVC 1: Number of service PVC downstream received cells : 6 PVC 1: Number of service PVC downstream discarded cells: 0 PVC 1: Number of service PVC upstream received cells PVC 1: Number of service PVC upstream discarded cells : 6 : 0

Number of service PVC downstream invalid cells: 0 Number of service PVC upstream invalid cells : 6

CPU <-> ADSL cell count: -----------------------Number of TMS PVC downstream received cells : 0 Number of TMS PVC downstream discarded cells: 0

This PVC is not used to manage ADSL terminal.

BSL(config-ATM-0/0)#show statistics cid 1 E1 <-> ADSL cell count: ----------------------PVC 1: Number of service PVC downstream received cells : 14 PVC 1: Number of service PVC downstream discarded cells: 0 PVC 1: Number of service PVC upstream received cells PVC 1: Number of service PVC upstream discarded cells : 14 : 0

Number of service PVC downstream invalid cells: 0 Number of service PVC upstream invalid cells : 14

CPU <-> ADSL cell count: -----------------------Number of TMS PVC downstream received cells : 0 Number of TMS PVC downstream discarded cells: 0

This PVC is not used to manage ADSL terminal

5)

Cancel the loopback, and then query the PVC cell statistics again. It can be seen that only the upstream cells are increased, while the downstream cells not.

BSL(config-ATM-0/0)#no loopback etu local <portId>{1-4}:1 Cancel ETU port loopback successfully.

BSL(config-ATM-0/0)#clear statistics cid 1

4-19

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

Are you sure to clear VCC statistics information?(y/n) [n]:y PVC 1: cell statistics data has been cleared.

BSL(config-ATM-0/0)#show statistics cid 1 E1 <-> ADSL cell count: ----------------------PVC 1: Number of service PVC downstream received cells : 0 PVC 1: Number of service PVC downstream discarded cells: 0 PVC 1: Number of service PVC upstream received cells PVC 1: Number of service PVC upstream discarded cells : 4 : 0

Number of service PVC downstream invalid cells: 0 Number of service PVC upstream invalid cells CPU <-> ADSL cell count: -----------------------Number of TMS PVC downstream received cells : 0 Number of TMS PVC downstream discarded cells: 0 : 4

This PVC is not used to manage ADSL terminal. BSL(config-ATM-0/0)#show statistics cid 1 E1 <-> ADSL cell count: ----------------------PVC 1: Number of service PVC downstream received cells : 0 PVC 1: Number of service PVC downstream discarded cells: 0 PVC 1: Number of service PVC upstream received cells PVC 1: Number of service PVC upstream discarded cells : 6 : 0

Number of service PVC downstream invalid cells: 0 Number of service PVC upstream invalid cells : 6

CPU <-> ADSL cell count: -----------------------Number of TMS PVC downstream received cells : 0 Number of TMS PVC downstream discarded cells: 0 This PVC is not used to manage ADSL terminal.

This method is suitable for the loopback in the downstream direction: LIU local loopback: loopback liu local ETU local loopback: loopback ETU local UTOPIA local loopback of ETU: loopback etu local_utopia

4-20

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

The loopback test in the upstream direction is similar with that in the downstream direction, except that the packets are sent out from different directions.

4.4.3 Fault Case Study


I. The CES port of the MD5500 is connected with the BSL board normally, while the port is DOWN.
[Fault Description] The 100M Ethernet port of the IPU board of the MD5500 is connected to some switch in the upstream direction, and provides ADSL service through CESH board connecting with BSL in the downstream direction. On the MD5500, use the command show port mode to find that the E1 port 4 on the CESH board that is interconnected with the BSL board is DOWN, and the indicator of the port on the BSL board that is interconnected with the MD5500 is off. [Alarm Information] Port 4 is DOWN, and the indicator of the port on the BSL board that is interconnected with the MD5500 is off. [Fault Analysis] 1) 2) 3) CES port hardware is faulty, The parameters of the CES port are not correctly set, or some parameter is not consistent with that of the BSL port, The working mode of the CESH board is not correct. [Troubleshooting] 1) Run the command show runmode to query the working mode of the CESH board. The board works in E1 mode, removing the possible problem of board working mode, 2) 3) On DDF, perform local hardware loopback test to the CES port, and the port is UP, removing the possible problem of CES port hardware, Run the command show port mode to query parameters of the CES port: the port mode is UNI, and the clock is SYSTEM. The CRC4 setting of the CES port should be consistent with that of the BSL port. However, the current setting of the BSL port is OFF, while that of the CES port is ON. Therefore, enter the CES configuration mode (interface ces 0/1) in the config mode, and set the CRC4 of the port as OFF (crc4 7 off), 4) After that, save the data, run the command show port mode to find that this port is UP, and the status indicator of the BSL port is on. By now, the fault is removed. [Suggestion & Conclusion]

4-21

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

Pay attention to the port settings, especially the parameter such as working mode, clock and CRC4 of the CES port. Parameters should be set according to different opposite equipment, so as to ensure the normal operation of the equipment.

II. The Internet access of the BSL subscriber cannot speed up due to rather low activation rate.
[Fault Description] The MD5500 is interconnected with the BSL board, the MD5500 does not perform flow control, and the BSL performs flow control by setting the port activation rate. Perform downloading test on a local website. Set the downstream activation rate as 480k, 512k, 768k, 1024k, 1920k, and 2048k respectively, and download the files of 5M, 10M, 20M, 50M, and 100M respectively. According to the test results, the maximum downloading rate can only reach 1M around. [Fault Analysis] 1) 2) The line is in poor quality, The upper layer equipment performs flow control.

[Troubleshooting] Replace the test port, the test result is the same. Test the E1 line and no bit error is found, removing the possible problem of physical line. 1) The upper layer equipment does not perform flow control, the configuration data are consistent with other interconnected equipment, and the equipment has not such kind of fault. 2) Check the data configuration and find that all upstream activation rates are 64kbit/s. Modify it to 640kbit/s, then make the test again, and the downloading rate becomes normal. [Suggestion & Conclusion] When data are transmitted by means of TCP, the system requires interaction. Too small upstream flow will increase the interaction time, and then influence the transmission rate. The larger the interleaved depth is, the more obvious the case may be. It is recommended that the upstream rate in the deployment should be 128kbit/s at least.

III. The Internet access rate is rather slow because of the bit error in the BSL upstream direction.
[Fault Description] The networking mode is as follows: PC-->RTU-->BSL-->SDH transmission

equipment-->MD5500-->ATM switch-->Internet. Run the dial-up program enternet500 to make a test, the Internet access is OK, but the access rate is rather slow. Sometimes, it takes five minutes to open a webpage. On the BSL board, ping the IP address of a
4-22

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

public network such as Sina.com with packets of 32 bytes, the packet loss ratio is 10% around, and ping it with packets of 1000 bytes, the packet loss ratio is 30% around. Then, ping the inband NM IP address of the MD5500 with packets of 32 bytes, the packet loss ratio is 10% around, and ping it with packets of 1000 bytes, the packet loss ratio is 35% around. [Alarm Information] None [Fault Analysis] The subscriber can get access to the Internet, it means the subscribers IP address is correct, and the data configurations of the MD5500 and BSL are correct. For the slow access rate, the following aspects can be checked: 1) 2) 3) The MD5500 performs flow control, The Internet access account performs flow control, The E1 line or the intermediate transmission line becomes faulty.

[Troubleshooting] Check the data configuration of the MD5500, disable the flow control, and perform the test again, but the Internet access rate is not changed. 1) Plug a LANC board in the MD5500, connect a PC to the board directly, configure the required data, and then perform the test again, the Internet access rate becomes normal. This indicates that the Internet access account can be used normally, and the upper layer equipment can work normally. At the same time, it also indicates that the BSL or intermediate transmission line becomes faulty. 2) On the MD5500, ping the inband NM IP address of the connected BSL board with packets of 32 bytes, the packet loss ratio is 3% around, and ping it with packets of 1000 bytes, the packet loss ratio is 18% around. Then, ping the IP address of a public network such as Sina.com with packets of 32 bytes, the packet loss ratio is 2% around, and ping it with packets of 1000 bytes, the packet loss ratio is 15% around. Seeing from the above tests, the packet loss ratios in these two cases are the same, and it can be concluded that some part of the SDH transmission line between the MD5500 and BSL might be faulty. On the DDF, perform loopback test to the MD5500, and no fault is found. Then, test the SDH transmission line between the DDF and BSL board with BER tester, and bit errors are found. 3) Since the bit error is not pretty severe, it does not influence the voice service. However, since the BSL requires the line of high quality, the bit error influences the Internet access rate severely. By now, the fault is located. 4) Replace the BSL board to another residential community, that is to say, replace the SDH transmission line between the DDF to BSL, then configure the relevant data, and the Internet access rate becomes normal. This can further testify that it

4-23

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

is the SDH transmission line between the DDF and BSL that causes the slow Internet access rate. [Suggestion & Conclusion] When removing faults, do not neglect the intermediate SDH transmission part, besides checking the data configuration of the MD5500.

4.5 Flow Control


4.5.1 Introduction to Principles
I. Flow types supported by each module of the MD5500
Table 4-1 Flow types supported by each module of the MD5500
CBR IPU E1 UNI E1 UDT/SDT ATM optical interface Supported Supported Supported Supported rt-VBR Supported Supported Not supported Supported nrt-VBR Supported Supported Not supported Supported UBR Supported Supported Not supported Supported

II. Flow control configuration for common Internet access subscriber in the networking mode of MD5500+BSL
1) 2) 3) Do not perform flow control on the MD5500. When creating the PVC, disable the UPC, and select the service category as UBR. Perform flow control to the ADSL port that is connected to the BSL board. Do not perform flow control to any part of the whole PVC channel except the ADSL port.

4.5.2 Frequently-used Troubleshooting Methods


1) 2) Use BER tester and optical power meter to check the physical line. Check if the service bottleneck exists in the network. Check the networking mode to see if the Internet access rate of all subscribers connected with the same port is slow. 3) 4) Check the relevant data configuration based on the MD5500 flow control configuration principle. Check if parameters in the access rate table are consistent with those in the traffic table.

4-24

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

4.6 Circuit Emulation Service


4.6.1 Introduction to Principles
Circuit Emulation Service (CES) is a kind of technology that realizes the adaptation from the traditional narrowband circuit service to broadband ATM network, i.e., realizes the technology of ATM Adaptation Layer Type 1 (AAL1) defined by ATM Forum. By this technology, the broadband ATM network can support the constant bit rate (CBR) service, such as the traditional 64k voice service. At the same time, it guarantees the character of Quality of Service (QoS). The CES E1 port can work in three modes, structured data transfer (SDT), unstructured data transfer (UDT), and user network interface (UNI). An SDT E1 port can provide a maximum of 31 independent 64kbit/s channels, and supports continuous or discontinuous timeslot division. A UDT E1 port can provide one 2048kbit/s channel. The UNI is the basic interface of the ATM equipment, which can be used to connect the private network with small service traffic to the ATM network.

4.6.2 Frequently-used Troubleshooting Methods


I. Checking line quality
When the CES series boards work in the TDM mode, check the line quality. You can refer to the troubleshooting methods for E1 link fault. When the CES series boards work in E1 mode, you can use the following methods to locate the fault: check the line quality, use the hardware loopback and software loopback (local and remote) in combination with the received and sent cells statistics, or query the UNI/UDT port or the SDT channel statistics information in the port mode. The loopback command is:
MD5500(config-if-ces-0/2)#loopback 0 local

The cells statistics query command is:


MD5500(config)#show cell statistics 0/2/0 --------------------------------------------------------------Port Receive cells 0 21141 Send cells 55606 Difference 34465

---------------------------------------------------------------

The port statistics information query command is:


MD5500(config-if-ces-0/2)#show statistics portId 0 channelId 3

4-25

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

In case of normal CES port statistics information, all statistics numbers are 0, otherwise, part of them are not.

II. Fault location by checking clock configuration


According to the actual application of CES, most faults are caused by the incorrect configurations, for example, incorrect flow control and clock configuration, and so on. Therefore, do not forget do check the clock configuration when any CES fault occurs.

III. Querying working mode of the board


The board working mode query command is: MD5500(config-if-ces-0/1)#show runmode Working modes supported by CES series boards include:
z z

The H511DT16 and H512CESH work in the TDM mode, The H511EA16, H511CE8, and H512CESH work in the E1 mode.

In case of narrowband E1 service, then the board works in the TDM mode. In case of UNI/SDT/UDT service, the board works in the E1 mode, or in the CES E1 group of the TDM mode.

IV. Querying port status


The port status query command is: MD5500(config-if-ces-0/1)#show port mode Port modes supported by CES series boards include:
z z z z

The H511CESH, H512CESH and H511DT16 support the narrowband E1 service. The H511CESH, H512CESH, H511EA16 and H511CE8 support the UNI service. The H511CE8, H511CESH and H512CESH support the UDT service. The H511CE8, H511CESH and H512CESH support the SDT service.

V. Querying bit error by loopback test


Figure 4-8 shows the loopback test circuit. 1) Remote loopback

The CES port of the MD5500-A is connected with a BER tester (which should adopt internal clock) for Remote loopback test. No bit error should be found in the test. 2) Local loopback 1

The AIC optical interface of the MD5500-A is connected to the Radium 8750. Create one PVC from two CES ports to the AIC optical interface respectively, which are interchanged by the Radium 8750.

4-26

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

Set the Local loopback to one CES port (which should adopt system clock) of the MD5500-A. Connect a BER tester to the other CES port for loopback test, and no bit error should be found. 3) Local loopback 2

Connect the AIC optical interface of the MD5500-A and the MD5500-B to the Radium 8750 respectively. Create one PVC from the CES port of the MD5500-A and the MD5500-B to the AIC optical interface respectively, which are interchanged by the Radium 8750. Set the Local loopback to the CES port of the MD5500-B. Connect a BER tester to the CES port of the MD5500-A for loopback test, and no bit error should be found. If no bit error is found in this test, it indicates the fault is not caused by broadband network, but by the opposite equipment of the CES port or the connection line between the equipment. This test also shows that the broadband network clock is synchronized.
Radium8750

PVC2 PVC1 PVC1 PVC2

MD5500-A

C E S

A A S I X C

C E S

MD5500-B

C E S

A A S I X C

Remote loopback
BER tester

Local loopback

Local loopback

Figure 4-8 Loopback test circuit connection diagram

4.6.3 Fault Case Study


I. The CESH board is used, but its working mode cannot be modified.
[Fault Description] The CESH board works in the TDM mode, to meet the requirements of the service, the board needs to work in the E1 mode, but the command line prompts that the working mode cannot be modified. [Alarm Information] The working mode cannot be modified. [Fault Analysis]

4-27

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 4 Broadband Service Troubleshooting

The CESH can work in the TDM or E1 mode, but can only work in one kind of mode at one time. According to the equipment management method of the MD5500, if the working mode of the CESH is to be modified, it is necessary to delete the CESH board at first, then add the board and set the new working mode. [Troubleshooting] Use the command board delete to delete the original CESH board, use the command board add to add the new board, use the command runmode E1 to set the working mode as E1, and the board works normally. [Suggestion & Conclusion] To modify the working mode of the CESH board, it is necessary to delete this CESH board at first, then add the board and set the new working mode.

4-28

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

Chapter 5 Other Troubleshooting


5.1 PV8/PV4 Board Loading
5.1.1 Introduction to Principles
In the HONET, the PV8/PV4 serves as the narrowband frame main control board to provide local, remote and quasi-local service processing abilities. It can be interconnected with the V5 interface of the local exchange (LE) to serve as the OLT of the HONET to access the narrowband subscribers of the access network or cascade with the RSP frame. It can also be interconnected with the V5 interface of the HONET GV5 frame (including GV5-I, GV5-II and GV5-III) to access the subscribers or cascade with the RSP frame. In the MD5500, the function of the PV8/PV4 frame is also to access the narrowband subscribers or cascade with the RSP frame, which is the same as that in the HONET. However, the PV8/PV4 is no more the main control node due to the centralized NM solution of the MD5500. It only serves as the primary node board for communication with the secondary node board in the frame, while the service and data processing (including the V5 protocol processing, timeslot assignment and crossover, subscriber port control and management, connection management, and so on) are done by the main control board (ASX board) of the MD5500. Therefore, the PV8/PV4 board in the MD5500 and that in the HONET work in different ways. When working in the MD5500, the PV8/PV4 board must load the board software that is different from the board software applied in the HONET. In addition, if the host software of the MD5500 is upgraded, the PV8/PV4 board software should be upgraded accordingly, so as to make the whole system work reliably and stably.

I. Loading channel
The PV8/PV4 has two loading channels: It can be loaded by the connection of Timeslot 16 of the first E1 link of this board with the timeslot configured by the HDLC resources (in case of one PV8 board configured), It can be loaded by the HDLC resources of the active PV8/PV4 board and the channel between the active and standby PV8/PV4 boards (the inter-board channel also works in HDLC mode), under the conditions that the active PV8 board has been configured with the board software for the MD5500 system, and can communicate with the MD5500 main control frame normally.

5-1

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

II. Loading methods

Caution: In the MD5500, no matter what kind of loading method is used, the first E1 line of the board to be loaded must be through.

The PV8/PV4 board software can be loaded by the following ways:


z

Loading by setting DIP switch: Place the DIP switch 1 on the front panel of the PV8/PV4 board into ON state, so that the PV8/PV4 board can make the request for loading automatically. In the MD5500, the command load set is used to specify the loading server.

Forced loading: In the MD5500, the command load program force is used to load the PV8/PV4 board software forcibly. Common loading: In the MD5500, the command load program is used to load the PV8/PV4 board software, as well as the broadband service board software.

The following part introduces the loading methods of the PV8/PV4 board software based on the actual application. 1) Loading by setting DIP switch

Application: If the physical link between the first E1 port of the PV8/PV4 board and the CESH or DT16 board of the MD5500 is in normal status, no matter whether the PV8/PV4 board is in normal status, the board can make the request for loading automatically by setting its DIP switch. When the DIP switch 1 on the front panel of the PV8/PV4 board is placed into ON state, the PV8/PV4 is reset, and then the board can make the request for loading automatically through the first port (port 1). Therefore, if the PV8/PV4 board is connected with the MD5500, and the board software is to be loaded by placing the DIP switch 1, the initial condition is that the E1 line connecting with port 0 of the PV8/PV4 board must be in good condition physically. Otherwise, the loading request cannot be reported, not to mention the loading. Advantages: The PV8/PV4 board software can be loaded stably, and the loading risk is rather low. Disadvantages: The maintenance personnel must be presented at the ONU site, where the PV8/PV4 board is applied. 2) Forced loading

5-2

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

Application: If the physical link between the first E1 port of the PV8/PV4 board and the CESH or DT16 board of the MD5500 is in normal status, no matter whether the PV8/PV4 board is in normal status, or the PV8/PV4 communicates with the MD5500 normally, the board software can be loaded forcibly. Advantages: The maintenance personnel neednt be present at the ONU site, and so long as the physical link between the MD5500 and the first E1 port of the PV8/PV4 board is in normal condition, the loading can be performed. Disadvantages: If the physical link is not stable during the loading, the loading might fail, while the time-out time for loading failure is over 10 minutes. It would be troublesome to handle this case during the loading. 3) Common loading

Application: The PV8/PV4 board software for the MD5500 system is normally running, and the MD5500 can communicate with the PV8/PV4 board normally. In the MD5500, when the command load program is used to deliver the loading command, the PV8/PV4 board will receive this command and make the corresponding processing of it. At this time, if the board software running in the PV8/PV4 board is not for the MD5500, but for the HONET or, the PV8/PV4 board does not work normally, and then the PV8/PV4 cannot communicate with the MD5500 normally. In this case, the PV8/PV4 board software cannot be loaded normally. Advantages: It is convenient to start loading so long as the PV8/PV4 board can communicate with the MD5500 normally, and the maintenance personnel neednt be present at the site. Disadvantages: If the PV8/PV4 board fails to communicate with the MD5500, or the PV8/PV4 board does not work normally, the loading cannot proceed. During the actual maintenance, you can select the most suitable method to load the PV8/PV4 board software based on the actual conditions.

Note: It is highly recommended that you load board software for two PV8 boards one by one. If there is no maintenance personnel at the job location, disconnect the first E1 trunk cable of one PV8 board at the Central Office end, and then reconnect it after the other board finishes loading the board software.

5-3

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

5.1.2 Frequently-used Troubleshooting Methods


During the loading of PV8/PV4 board software, the frequently-used troubleshooting methods are as follows:

I. The PV8/PV4 board makes the request of loading automatically after its DIP switch is set correctly, but the MD5500 cannot receive the loading request.
Possible cause: The trunk 2M link connected with the first E1 port of the PV8/PV4 board is disconnected physically, so the loading request cannot be transmitted to the MD5500. Troubleshooting method: Check the trunk link to ensure that the link works normally and stably.

II. The PV8/PV4 board makes the request of loading automatically after its DIP switch is set correctly, but the MD5500 cannot process the loading request.
Possible cause: The Trivial File Transfer Protocol (TFTP) server on the MD5500 is not set properly, so it cannot process the loading request from the PV8/PV4 board. Troubleshooting method: Use the command load set tftp_server ip to set the TFTP server correctly, and reset the PV8/PV4 board.

III. After the forced loading command is delivered, the loading request from the PV8/PV4 board cannot be received.
Possible cause 1: The E1 port of the CESH board of the MD5500 does not work normally. Troubleshooting method: Try another E1 port that can work normally and is connected with the PV8/PV4 board to perform the forced loading. Possible cause 2: Two PV8/PV4 boards are configured in the PV8/PV4 frame, and the loading request results in congestion of channel massage capsule, or the two PV8/PV4 boards have been configured with different board software before. Troubleshooting method: Remove one PV8/PV4 board from the frame, and then deliver the forced loading command. After the loading is finished, remove this board, and then plug in the previously removed PV8/PV4 board for loading.

IV. The PV8/PV4 board makes the request of loading automatically after its DIP switch is set correctly, and the loading starts but fails at 40%.
Possible cause: The physical link is not stable or disconnected.

5-4

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

Troubleshooting method: If there are two PV8/PV4 boards configured in the frame, when the loading failure information is given, unplug one board and check the transmission line. Make sure the line is in normal status and the connection is stable. Then, restart the loading. After that, replace the other PV8/PV4 board for loading.

V. Use the forced loading mode to load the PV8/PV4 board software, and the loading starts but fails at 40%.
Possible cause 1: The physical link is not stable or disconnected. Troubleshooting method: If there are two PV8/PV4 boards configured in the frame, when the loading failure information is given, unplug one board and check the transmission line. Make sure the line is in normal status and the connection is stable. Then, restart the loading. After that, replace the other PV8/PV4 board for loading. Note: It will be over ten minutes before the loading failure information is given due to the protection mechanism of the forced loading mode. During this period of time, do not pull out or plug in the board, disconnect the link or reset the host so as not to result in new problems. Possible cause 2: At least one PV8/PV4 board in the frame has been configured with the software for the HONET system before, and the board to be loaded is in standby mode. Troubleshooting method: when the loading failure information is given, remove one PV8/PV4 board from the frame, and then restart the loading of the other board. After that, replace the previously removed PV8/PV4 board for loading. Note: It will be over ten minutes before the loading failure information is given due to the protection mechanism of the forced loading mode. During this period of time, do not pull out or plug in the board, disconnect the link or reset the host so as not to result in new problems.

VI. The loading carries on smoothly, but resumes at 40% suddenly.


Possible cause: Usually, this fault occurs when there are two PV8/PV4 boards configured in the frame. When one PV8/PV4 board in under the loading, and the MD5500 receives the new loading request (usually, it is because that the loading request message capsule reaches the main control board of the MD5500 with rather large delay, which is caused by message congestion of the loading channel), the new loading will start. That is why the loading resumes at 40% suddenly. Troubleshooting method: remove one PV8/PV4 board from the frame, and then restart the loading of the other board. After that, replace the previously removed PV8/PV4 board for loading.

5-5

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

VII. Use the command load program to load the PV8/PV4 board software, the board fault information is given, and the loading fails.
Possible cause: The PV8/PV4 board has been loaded with the software for the HONET system before, or the link is currently disconnected, which makes the current PV8/PV4 board unable to communicate with the MD5500 normally. Query the PV8/PV4 board in the command line mode of the MD5500, and it is in faulty status. Troubleshooting method: If the PV8/PV4 board has been loaded with the software for the HONET system before, use the forced loading mode to load the PV8/PV4 board software, or set the DIP switch of the PV8/PV4 correctly to enable it to make the request of loading automatically, under the condition that the link between the MD5500 and the PV8/PV4 board is normal. If the PV8/PV4 board has been loaded with the software for the MD5500 system before, then check if the link between the MD5500 and the PV8/PV4 board is in normal status, and then check if the DIP switches of the PV8/PV4 and DT16/CESH boards are set correctly. If not, correct them. After that, use the forced loading mode to load the PV8/PV4 board software, or set the DIP switch of the PV8/PV4 correctly to enable it to make the request of loading automatically.

5.1.3 Fault Case Study


I. Forced loading of PV8 board software fails because different board software have been loaded before.
[Fault Description] Networking mode: The MD5500 is connected with the PV8 frame through E1 link, and the physical link is in normal status. Only one PV8 board has been installed into the left slot of the PV8 frame before, and the board software for the MD5500 system has been configured (This board is referred to as PV8-A board below). Later, a new PV8 board has been installed, and the board software for the HONET system has been configured (This board is referred to as PV8-B board below). Operation: MD5500 host software upgrade. Version: MD5500: upgrade from V100R002B03D009 version to V100R002B03D070 version. The PV8-A board software version: 210

5-6

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

The PV8-B board: it is configured with the board software for the HONET system. Fault: Query the two PV8 boards on the MD5500, and both of them are in faulty state. The forced loading mode is used to load the new software for the PV8-A board. The system prompts to deliver the forced loading command, and then waits for the delivery of the command. After a period of time, the loading failure information is given. Restart the loading, and the fault repeats. [Alarm Information] Both PV8 boards are in faulty state. [Fault Analysis] The system worked normally before the upgrade of the MD5500 host software, that is to say, the PV8 board has no hardware fault. The possible causes are analyzed as follows: 1) 2) The link between the MD5500 and PV8 board is disconnected. The command delivered by the MD5500 is discarded by the PV8 board.

In these two cases, the PV8 board will not return any message to the MD5500, or make a response to the command delivered by the MD5500. If the MD5500 does not receive the command response all along, the loading failure information is given. [Troubleshooting] Perform loopback test section by section to the link between the MD5500 and PV8 board, but no fault is found. So, the fault is located at the PV8 board side. During the upgrade of the host software, since the PV8-A board fails to communicate with the MD5500, this board must reset repeatedly, however, at the same time, the PV8-B board in the frame works normally. During the resetting of the PV8-A board, the BIOS will check the running status of the PV8-B board. Here, the PV8-B board is found working normally. Then, the BIOS will think that these two PV8 boards work in the active/standby mode, and the active PV8 board should be responsible for receiving and processing messages. Since the PV8-A board does not work normally at present, the message capsule sending to it will not be forwarded (actually it is discarded), that is to say, the forced loading command cannot be delivered to the PV8-B board through the channel between PV8 boards. That is why the forced loading of the PV8 board cannot be carried on, and the MD5500 cannot receive any response message capsule. Based on the above analysis, there are two troubleshooting methods available to solve the problem.

5-7

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

The first troubleshooting method is suitable for the case that the PV8 frame is far away from the central office of the MD5500, and there are no maintenance personnel on site. 1) 2) 3) Use the forced loading mode to load the PV8-B board software. After the PV8-B board works normally, use the same mode to load the PV8-A board software. After the loading, check if the PV8 boards work normally, and if the board software version is correct. The second troubleshooting method is suitable for the case that the PV8 frame is located at the central office of the MD5500, or there are maintenance personnel on site. 1) Unplug the PV8-B board, use the forced loading mode to load the PV8-A board software, or set the DIP switch of the PV8-A board correctly to enable it to make the request of loading automatically. 2) 3) After the PV8-A board works normally, remove it and then plug the PV8-B board for loading. After the loading, plug the PV8-A board into the frame, and then check if the PV8 boards work normally, and if the board software version is correct. [Suggestion & Conclusion] The troubleshooting method introduced here is very helpful if the same fault occurs during the deployment or upgrade, especially the upgrade. If the maintenance personnel are present at the site, the second troubleshooting method should be used. If the first troubleshooting method is used, do not start until the loading failure information is given.

II. The PV8 board becomes faulty because the upper and lower AMP connectors of it are connected reversely.
[Fault Description] Networking mode: This is a new deployment. The MD5500 is connected with the PV8-10 frame, which is configured with two PV8 boards. The port 16 of the CESH board installed at the slot 0 of the MD5500 frame is connected with the left PV8 board (seen from the front view, and the same below), and the port 16 of the CESH board installed at the slot 1 of the MD5500 frame is connected with the right PV8 board. The MD5500 host software version is V100R002B03D070. Fault: When the link is in normal status, use the forced loading mode to load the PV8 board software. After the loading is succeeded, the board is in faulty state, and after a while, the board resets. [Alarm Information] After the loading is finished, the PV8 board is in faulty state.

5-8

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

[Fault Analysis] It is doubted that the board has hardware fault, so try another PV8 board, but the fault still occurs. Since these boards are newly delivered, they might not be damaged at the same time. Therefore, the possible cause is narrowed down to that the link connection cannot be established between the PV8 board and the MD5500 successfully after the board software is loaded. Physically, it is because, on the one hand, the CRC4 setting at both sides do not match, on the other hand, the link might be connected wrongly, so Port 0 of the PV8 board does not communicate with the MD5500. The board will reset if it does not communicate with the MD5500 host within a period of time. [Troubleshooting] 1) Disable the PV8 board, delete the inter-frame link, use the command show port mode to query the two ports of the two CESH boards, and both are in normal status. This can testify that the physical link connection is correct, 2) 3) Check the CRC4 setting on the PV8 board and the port of the CESH board to find that they are consistent. This indicates the CRC4 setting has no problem, Then, analyze the port link connection. The forced loading should be performed normally through the first four E1 ports of the PV8 board except that line crossover occurs. Check the cable between the transmission equipment of the ONU and the PV8 board. The B75 acts as a conversion device. The E1 line from the transmission equipment is connected to the first E1 line of the B75, and the two AMP connectors are connected with Pins 17~24 and Pins 25~32 of the left PV8 board respectively. The wiring mode of the right PV8 board is the same as the left board. Since the left PV8 board only has one E1 line, if the line crossover fault occurs, it is only because that the AMP connectors are reversely connected. Reversely connect the AMP connector, load the board software again, and the board works normally after the loading is finished. [Suggestion & Conclusion] If the upper and lower AMP connectors are reversely connected, the port 16 of the CESH board does not connect with the port 0 of the left PV8 board, but with the port 3, (8 E1 ports of the PV8 board are arranged with the following sequence: 1, 5, 2, 6, 3, 7, 4, 8). The MD5500 implements the forced loading to the PV8 board through the port 3. Afterward, the port 0 of the PV8 board cannot communicate with the MD5500 normally, causing the PV8 board fault. After a period of time, the board resets.

5.2 Board Registration


5.2.1 Introduction to Principles
Boards of the MD5500 support plug-and-play function, which facilitates maintenance operation greatly.
5-9

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

The system can find the board automatically. If a board is installed into an unoccupied slot of the system, it will be identified automatically, after that, the board can work normally. In some cases, for example, replace the board, load the database stored in other environment, the board data might have been configured already before the board is installed, then, the board to be installed must have the same parameter configuration with the replaced board, otherwise, it will not work normally. Here, the same parameter configuration includes: board type, subboard type, and subboard position. If the board that has registered to the system replaces the subboard of different type, then this board needs to be deleted before it can register successfully again. For some board, for example, the AIC board, it must be attached with subboard in order to register successfully. In case of a 622M optical subboard, it must be attached to the lower subboard slot on the AIC board. If the CESH board is attached with the E1 subboard, the setting of DIP switch on the subboard should be checked.

5.2.2 Frequently-used Troubleshooting Methods


I. AIC board fails to register.
Possible cause: 1) 2) 3) There are still configuration data for a board other than AIC at the slot for this AIC board. The board is not attached with any subboard, or the subboard is not attached closely, The subboard type does not match the board. For the MD5500V100R002, the AIC board supports the 155M optical subboard and 622M optical subboard. For the MD5500V100R003, the AIC board supports the 155M optical subboard, 622M optical subboard and 155M electrical subboard, 4) 5) The 622M optical subboard is not attached to the lower subboard slot, or it intermixes with other subboards, For the version earlier than MD5500V100R003B02D051, when the AIC board is attached with a subboard of different type, the AIC board is not deleted through the host command line. For the MD5500V100R003B02D051 and the later, when the AIC board is attached with a subboard of different type, the subboard type is not modified through the host command line, or modified incorrectly. 6) The offline data is inconsistent with the actual board, especially the subboard position (refer to fault case study),

5-10

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

7)

The board is not plugged into the backplane closely, which makes the board get illegal slot ID to reset, or the registered slot ID is inconsistent with the actual one.

Fault location: 1) 2) 3) Delete the previous board configuration data, Plug the board into the backplane closely, Use the command show board to check if the type of board that has been plugged into this slot before is consistent with the type of the board to be registered, and if the subboard type and position parameters carried by the board to be registered are consistent with those recorded by the ASX board.

5.2.3 Fault Case Study


I. The AIC board fails to register due to the incorrect AIC subboard configuration.
[Fault Description] Upgrade the MD5500 host software from R002B03D009 version to R002B03D070 version. At first, configure a new ASX board offline, and then replace the current ASX board with this new board. After the upgrade, the AIC board cannot register, and the board resets repeatedly. Reload the board software, the problem is not resolved. [Alarm Information] The running LED indicator of the board flashes rapidly, and the board resets repeatedly. [Fault Analysis] 1) 2) 3) 4) The board is not attached with any subboard, or the subboard is not attached closely, The subboard type does not match the board, The 622M optical subboard is not attached to the lower subboard slot, or it intermixes with other subboards, For the version earlier than MD5500V100R003B02D051, when the AIC board is attached with a subboard of different type, the AIC board is not deleted through the host command line. For the MD5500V100R003B02D051 and the later, when the AIC board is attached with a subboard of different type, the subboard type is not modified through the host command line, or modified incorrectly, 5) The board is not plugged into the backplane closely, which makes the board get illegal slot ID to reset, or the registered slot ID is inconsistent with the actual one. [Troubleshooting] 1) Pull out and plug into the board again to make sure it is closely attached with the backplane, but the board still cannot register successfully. This excludes the possibility of fault that the board gets the illegal slot ID to reset.

5-11

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

2) 3)

Check if the subboard type in the offline configuration data is correct. After check, all subboards are O1CTG optical subboard, that is, the subboard type is correct. Delete all data configuration related to the AIC board in the host, the AIC board is found automatically, confirm it and then the board can work normally. It is doubted that the offline configuration data have errors. Check the offline configuration data and it is found that the subboard position is subboard 1:

MD5500#show board 0 -------------------------------------------------SlotID 0 1 2 7 8 9 10 ...... -------------------------------------------------H511AIC Failed O1CTG H511ASX Active_Normal Type H511CESC Status Normal SubType1 E1_CES SubType2 E1_CES

Whereas the actual subboard position is subboard 2:


--------------------------------------------------------------------------------------------------SlotID 0 1 2 7 8 9 10 ...... -------------------------------------------------H511AIC Auto_find O1CPG H511ASX Active_Normal Type H511CESC Status Normal SubType1 E1_CES SubType2

E1_CES

Since the subboard of the AIC board is numbered according to logic number, if there is only one subboard attached to the position of subboard 2, the first port is still numbered 0, while in configuring the data offline, another AIC board is used to replace the actual one, and the positions of subboards of these two AIC boards are not consistent, however, the PVC is not aware of it (because the port number is the same). That is the reason of such fault. After the modification, the board registers successfully. [Suggestion & Conclusion]

5-12

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

Upgrade method by replacing the board is widely applied at present. Pay attention to the consistency of data before and after the upgrade, so as not to cause unnecessary troubles.

5.3 Environment Monitoring


5.3.1 Introduction to Principles
Ambient environment, such as temperature, humidity, power supply voltage, and so on, may have an influence on the performance and service life of an electronic component. To guarantee the long-term stable operation of the equipment, an appropriate should be maintained. It is necessary to monitor the environment so that the system can be informed when the ambient environment of the equipment changes and can automatically take measures or generate alarm to instruct the maintenance personnel to improve the environment.

I. EMUs supported by MD5500


z

Environment & power monitoring board (ESC), including H302ESC, H303ESC and H304ESC Power distribution frame EMU (DIS) PS4875 EMU (POWER4875) PS4845 EMU (POWER4845) Fan frame EMU (FAN)

z z z z

To realize the environment monitoring function, the EMU should be connected with the frame, including correct cable and connection. In addition, the data should be configured correctly, including the EMU type, correspondence between cable connection position and data configuration, and correspondence between EMU DIP switch and data configuration. When external sensors are used, they should function normally.

II. Secondary node scope of all EMUs


1)
z z z z z

For MD5500V100R002 and MD5500V100R003B01 H302ESC EMU and H303ESC EMU: 30. Power distribution frame EMU: 0. PS4875 EMU: 0. PS4845 EMU: 0. Fan frame EMU: 1~5. The secondary node can be set by the DIP switch SW2 on the fan monitor control board. (Bits 1~4 of the SW2 indicates the four bits of the secondary node in binary, among which bit 1 indicates the most significant bit and

5-13

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

bit 4 indicate the least significant bit. ON means this bit is 0, while OFF means this bit is 1.) 2)
z z

For MD5500V100R003B02 and the later H302ESC EMU, H303ESC EMU and H304ESC EMU: 30. PS4875 EMU, PS4845 EMU, power distribution frame EMU and fan frame EMU: 0. The secondary node of the four EMUs mentioned above can be modified by DIP switch. Note that this secondary node should be consistent with the configuration on the MD5500.

5.3.2 Frequently-used Troubleshooting Methods


Environment monitoring faults include:
z z

EMUs failure in communicating with host Error alarms generated by EMU

I. EMU fails to communicate with the host.


Possible cause: 1) 2) EMU data configuration on the MD5500 is incorrect. The EMU is disconnected with the system physically.

Fault location: 1)
z

Judge whether the EMU data configuration is incorrect. Check the EMU type. H303ESC corresponds to H303ESC, fan frame corresponds to FAN, power distribution frame corresponds to DIS, PS4875 corresponds to POWER4875, and PS4845 corresponds to POWER4845.

Check if the frame the EMU is connected is consistent with the configured frame. For example, if the EMU is configured to be connected with the Frame 1, then it should be connected with the Frame 1 physically.

Check if the EMU secondary node is configured correctly. Judge whether the EMU is well connected with the system physically. Use a meter to test if the cable between the monitoring board and the system works normally. Check if the EMU is connected with the correct port of the system. The cable connection varies with cabinet, as shown in Table 5-1.

2)
z

5-14

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

Table 5-1 EMU cable connection mode


Connected equipment Cable connection when EMU only connects to one port For B68 cabinet produced before October of 2003, connect the EMU to the environment monitoring serial port COM1 of the active ASX board. For B68 cabinet produced after October of 2003, connect the EMU to the JP8 port of the MD5500 backplane. In the H66-22 cabinet, connect the EMU to the Test Line/RS485 port of the fan frame. Connect the EMU to the lowest serial port on the front panel of the PV8/RSP board. Connect the EMU to the ESC_1 port of the PV8/RSP board. Cable connection of the second port when EMU connects to two ports Connect the EMU to the environment monitoring serial port COM1 of the standby ASX board. Connect the EMU to the environment monitoring serial port COM1 of the standby ASX board. Connect the EMU to the environment monitoring serial port COM1 of the standby ASX board. Connect the EMU to the lowest serial port on the front panel of the left PV8/RSP board. Connect the EMU to the ESC_0 port of the PV8/RSP board.

MD5500

ONU

Check if the EMU connected with the standby ASX board of the MD5500: EMU provides two ports. If only one port is to be connected, the EMU should be connected by the way indicated in Table 5-1. In addition, if two PV8/RSP boards are configured, the EMU should be connected to the right PV8/RSP board or the ESC_1 port.

II. Error alarms generated by EMU


Possible cause: Error alarms from EMU include: (1) The environment parameters are correct, and no alarm is generated, but the ALM indicator, and row and column alarm indicator are on. (2) The environment parameters are correct, but alarms are generated and reported. Fault location: 1) Check EMU alarm information. When no external sensor is configured, for the analog parameters, set the effective level to the largest applicable extent to remove the alarm; for the digital parameters, reverse the level to remove the alarm. 2) Check EMU version. EMU of earlier version may generate error alarms. Make sure to use the EMU of latest version.

5.3.3 Fault Case Study


I. When the environment monitoring cable is connected to the left RSP board, the communication fails.
[Fault Description]

5-15

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

The CES board of the MD5500 is connected with an ONU frame configured with two RSP boards. The ESC board is installed into the ONU frame, which communicates with the left RSP board in the RSP frame by serial port cable. As a result, the RUN indicator blinks rapidly, and the ALM indicator is steady on. [Troubleshooting] In the MD5500, the secondary node of the ESC board is set as 30 fixedly, while in the narrowband frame, the secondary node 30 should be configured to the right half-frame. Therefore, in this case, connect the ESC cable to the environment monitoring serial port of the right RSP board, or to the ESC_1 serial port of the backplane.

II. Communication fails because data configuration on the MD5500 is inconsistent with the hardware setting of monitoring board.
[Fault Description] After the data for power distribution frame EMU is configured, the EMU state is abnormal. The configured secondary node is 0, and the environment monitoring cable is connected to the COM1 port of the active ASX board. The host reports EMU communication fault alarm. [Troubleshooting] The problem is caused by the inconsistency of system data configuration with the hardware setting of the monitoring board. Check the DIP switch S1 of the monitoring board, and set bits 1~5 as ON, and then reset the monitoring board.

III. H303ESC fails to monitor the power supply status


[Fault Description] The ONU employs the PS4810 power supply. The H303ESC EMU for this ONU is configured on the MD5500, but it cannot monitor the status of the PS4810 and the battery. There is no relevant alarm on the MD5500 (the relevant alarm is not masked on the MD5500). [Fault Analysis]
z

The PS4810 power supply is not configured in the H303ESC EMU on the MD5500, and therefore the H303ESC EMU cannot monitor it. The communication cable between the intelligent monitoring module PSM-8 of the PS4810 power supply and the H303ESC becomes faulty, or the PSM-8 becomes faulty, which makes the H303ESC unable to monitor the power supply status.

[Troubleshooting] 1) Use the following command to configure the PS4810 power supply on the H303ESC EMU of the MD5500.

5-16

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

MD5500(config-if-h303esc-1)#esc power powertype 2:4810

2)

Check the communication cable between the PSM-8 of the PS4810 power supply and the SIO2 of the H301ESB/H301ESIB (the backplane of the H303ESC). In addition, check the PSM-8. If necessary, replace the communication cable or PSM-8 for test.

IV. The BIOS version of the power distribution frame monitoring board is low, which causes error alarms.
[Fault Description] The power distribution frame is configured properly, and is in normal status. However, the ALM indicator is steady on. Query the EMU alarm information, and there is access control alarm. Reverse the access control level, the ALM indicator is off, and no access control alarm is generated. Close the cabinet door, access control alarm is generated again. [Troubleshooting] The BIOS version of the power distribution frame monitoring board is low, which causes error alarms. Query the BIOS version of the monitoring board, and upgrade it to the version 103 or later.

V. The EMU of the MD5500 generates error alarms due to the incorrect configuration of extended parameters.
[Fault Description] The MD5500 with the host software version of V100R002B03D009 is connected with four PV8 nodes, and each PV8 node is configured with one H303ESC, which is used for environment monitoring. After the service is configured, each row and column alarm indicator of the cabinet of the four nodes is on, and the alarm persists. The cabinet alarm indicator is on. [Alarm Information] The NMS terminal of the MD5500 prompts the same alarm continuously, indicating that analog parameters with ID from 2 to 7 are beyond the measurement. [Fault Analysis] The H303ESC can monitor the analog parameters such as temperature and humidity, and the digital parameters such as access control and smog through the various sensor interfaces on its backplane. By default, the analog parameter 0 indicates temperature, and analog parameter 1 indicates humidity. The H303ESC has configured these two sensors already. Analog parameters with ID from 2 to 7 belong to the extended analog parameters. Based on actual application, external sensors can be connected to the backplane of the H303ESC. Only after the measurement range and alarm range of
5-17

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 5 Other Troubleshooting

these external sensors are configured in the system, can they monitor the extended analog parameters. As for this fault case, the extended analog parameters persist alarm, there are two possible causes excluding the environment factor: 1) If there is external sensor connected, it might be faulty, which causes error alarms. 2) If there is no external sensor connected, the extended analog parameters may be configured in the system by mistake, which causes the continuous alarms. [Troubleshooting] 1) Check the interfaces JTA1~JTA6 (corresponding to the extended analog parameters 2~7) on the backplane of the H303ESC, and no external sensors are connected, thus removing the possibility of sensor fault. 2) 3) 4) Use the show version 0/7 command to query the MD5500 host software version (it is V100R002B03D009). Use the show emu command to query all EMUs statuses of the system. Enter the EMU configuration mode, use the show esc system parameter command to query all the analog parameters, and it is found that extended analog parameters with ID from 2 to 7 are configured in the system. However, interfaces JTA1~JTA6 are not connected with external sensors. 5) Use the no esc analog command to delete external analog parameters with ID from 2 to 7 in turn. The row and column alarm indicator on the cabinet is off, the NMS terminal stops prompting the alarm, and the fault is removed. [Suggestion & Conclusion] Such kind of fault may occur on the system with version earlier than MD5500V100R002B03D070. For the system with version MD5500V100R002B03D070 or the later, the system sets the measurement range and the alarm range for the extended analog parameters by default. When the external sensors are connected, the extended analog parameters should be configured, and then they will function normally and report alarms. For the system with version earlier than V100R002B03D070, when no external sensors are connected, do not configure the extended analog parameters to avoid the error alarms. After the undesired extended analog parameters are deleted, if the alarm persists, reverse the level of the useless digital parameter.

5-18

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

Chapter 6 Alarm Analysis and Processing


Description of common alarm attributes
z

An alarm ID is the unique alarm identity composed of four bytes. Each alarm ID corresponds to an alarm. Alarm class is defined as running information (info), fault alarm (fault), and recovery alarm (recovery). Alarm level is used to identify the severity of an alarm, which can be divided into critical alarm (critical), major alarm (major), minor alarm (minor), and warning alarm (warning) in the descending order of severity.

A critical alarm refers to a global alarm that will damage the normal equipment operation and should be repaired immediately, such as power circuit fault, output clock fault, and so on. A major alarm refers to local board or line alarm that may lead to abnormal service operation if not handled in time, such as fiber broken, physical line fault, and so on. A minor alarm refers to a generic state fault alarm and event alarm that describe whether the boards or lines operate normally, such as bit error in a certain physical line. A warning alarm refers to state changes and events that will not influence the system performance and user services, however, the operator may be interested in it. Some of the warning alarms are the prompt information on recovery of equipment to normal state. The following describes some alarms and the corresponding handling methods.

6.1 Analysis and Processing of System Alarms


6.1.1 Can Not Lock SDH Clock Source
Alarm ID Description Parameters Cause description Processing suggestion 0x02300006 Alarm class Event Alarm level Major

Fail to lock SDH clock source FrameID, SlotID, Clock SourceID The former clock source port is abnormal, or the clock source with higher priority is recovered. (1) Check if lead-in cable for clock source connects well, (2) Measure the input signal quality of the clock source.

6-1

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.1.2 Can Not Lock TDM Clock Source


Alarm ID Description Parameters Cause description Processing suggestion 0x02300007 Alarm class Event Alarm level Major

Fail to lock TDM clock source FrameID, SlotID, Clock SourceID The former clock source port is abnormal, or the clock source with higher priority is recovered. (1) Check if lead-in cable for clock source connects well, (2) Measure the input signal quality of the clock source.

6.1.3 Board Fault


Alarm ID Description Parameters Cause description Processing suggestion 0x02310000 Board fault FrameID, SlotID, and Name Communication with the main control board abnormal (1) If the communication failure is caused by board reset command or loading board program, there is no need to proceed. (2) Check if the board and the backplane are in good contact. (3) Reset the board manually or pull it out and then plug it in. Alarm class Fault Alarm level Major

6.1.4 Loss of Clock Source


Alarm ID Description Parameters Cause description Processing suggestion 0x02310001 Alarm class Fault Alarm level Critical

Loss of clock source input FrameID, SlotID, PortID, and Clock SourceID Loss of clock source Check if the input cable for clock reference source connects well.

6-2

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.1.5 Abnormal Clock Subboard Communication


Alarm ID Description Parameters Cause description Processing suggestion 0x02310002 Alarm class Fault Alarm level Critical

Clock subboard communication abnormal FrameID, SlotID Communication of the clock subboard with the main control board abnormal (1) Check if the clock subboard connects well. (2) Replace the clock subboard.

6.1.6 Loss of BITS Clock Source


Alarm ID Description Parameters Cause description Processing suggestion 0x0231000a Alarm class Fault Alarm level Critical

Loss of BITS clock source FrameID, SlotID, and BITS Port Index There is no input on BITS clock port. Check if the input cable for BITS clock reference source connects well.

6.1.7 Inconsistent Active and Standby Board Software Version


Alarm ID Description Parameters Cause description Processing suggestion 0x07200003 Alarm class Event Alarm level Major

Inconsistent active and standby board software version None The active and standby boards have been loaded with the software of different versions. (1) Check if the software version loaded to the active and standby boards are consistent. (2) Load the same software to the active and standby boards.

6.1.8 Abnormal Communication of Active Board with Standby Board


Alarm ID Description Parameters Cause description Processing suggestion 0x07210000 Alarm class Fault Alarm level Major

Active board cannot communicate with standby board. None (1)Standby board faulty (2) Standby board not in position Check whether the standby board is working normally.

6-3

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.2 Analysis and Processing of E1 Link Alarms


6.2.1 CRC4 Error of PCM
Alarm ID Description Parameters Cause description Processing suggestion 0x0a300070 PCM CRC4 error FrameID, SlotID, and PortID. PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office. Alarm class Event Alarm level Major

6.2.2 PCM Slip Code


Alarm ID Description Parameters Cause description Processing suggestion 0x0a300071 PCM slip code FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office. Alarm class Event Alarm level Warning

6.2.3 PCM Line Disconnection


Alarm ID Description Parameters Cause description Processing suggestion 0x0a300072 Alarm class Event Alarm level Warning

PCM line disconnection FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office.

6-4

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.2.4 Remote Frame Alarm of PCM


Alarm ID Description Parameters Cause description Processing suggestion 0x0a300073 Alarm class Event Alarm level Warning

PCM remote frame alarm (RFA) FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office.

6.2.5 Loss of Multiframe Alignment of PCM


Alarm ID Description Parameters Cause description Processing suggestion 0x0a300074 Alarm class Event Alarm level Major

Loss of multiframe alignment (LMFA) of PCM FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office.

6.2.6 Loss of Frame Alignment of PCM


Alarm ID Description Parameters Cause description Processing suggestion 0x0a300075 Alarm class Event Alarm level Major

Loss of frame alignment (LFA) of PCM FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office.

6-5

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.2.7 E-Bit Remote Alarm Indication of PCM


Alarm ID Description Parameters Cause description Processing suggestion 0x0a300076 Alarm class Event Alarm level Major

E-bit remote alarm indication (RAI) of PCM FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office.

6.2.8 Abnormal PCM Line


Alarm ID Description Parameters Cause description Processing suggestion 0x0a310078 Alarm class Fault Alarm level Major

PCM line abnormal FrameID, SlotID, and PortID PCM line or phase-locked clock abnormal (1) Check if the line distribution and connection in the E1 transmission line are normal. (2) Check if the transmitting PCM line is normally connected. (3) Check if the clock system selects the correct phase locking mode. In general, select to lock the DT8K clock derived from the E1 line of the senior office.

6.3 Analysis and Processing of Optical Port Alarms


6.3.1 Abnormal Optical Port
Alarm ID Description Parameters 0x0a310000 Optical port abnormal FrameID, SlotID, and PortID (1) Optical fiber breaks off or is not connected correctly. (2) LOS error found (3) LOF error found (4) LOP error found (5) LOCD error found (6) OOF error found (7) LOL error found (8) LAIS signal received (9) PAIS signal received (10) LRDI signal received (11) PRDI signal received (1) Check if optical fiber is connected correctly, and measure the received optical signals. (2) Check if the local Tx optical fiber is connected correctly, and measure the local Tx optical signals. (3) Check if there is any alarm at remote end. Alarm class Fault Alarm level Critical

Cause description

Processing suggestion

6-6

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.3.2 Receiving Signal Deterioration Alarm


Alarm ID Description Parameters Cause description Processing suggestion 0x0a310001 Alarm class Running information Alarm level Critical

Signal deterioration (SD) alarm from board is received. FrameID, SlotID, and PortID The number of bit errors in unit time exceeds the threshold due to the degraded signals on the optical lines, and the board reports SD alarm. Check if the clock of main control board is operating normally, if the fiber type is correct, and measure the optical signals.

6.3.3 No Optical Signal at Port


Alarm ID Description Parameters Cause description Processing suggestion 0x11310021 Alarm class Fault Alarm level Major

Exception occurs in the corresponding hardware, which may result in switchover. Please refer to alarm parameter information. FrameID, SlotID, and PortID No optical signal received Check if optical fiber is connected correctly, and measure the received optical signals.

6.3.4 Optical Port Fault


Alarm ID Description Parameters Cause description Processing suggestion 0x1131002a Alarm class Fault Alarm level Major

Optical fiber broken off or connected incorrectly FrameID, SlotID, and PortID Optical fiber breaks off or is not connected correctly. Check if optical fiber is connected correctly, and measure the received optical signals.

6-7

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.4 Analysis and Processing of LAN Alarms


6.4.1 Peer End Not Supporting Auto-Negotiation
Alarm ID Description Parameters Cause description Processing suggestion 0x0a3000d0 Alarm class Event Alarm level Major

This port supports negotiation while the peer end does not, so loss of packets may happen. FrameID, SlotID, and PortID Peer end port is not working in auto-negotiation mode. Set peer end to operate in auto-negotiating mode, or set this end to work in the non-auto-negotiating mode and to keep following parameters be consistent with those of peer end port, including duplex mode, rate and whether supporting PAUSE frame.

6.5 Analysis and Processing of Narrowband Voice Alarms


6.5.1 Abnormal Frame
Alarm ID Description Parameters Cause description Processing suggestion 0x0231001d Alarm class Fault Alarm level Major

Communication of the upper-level with lower-level frame abnormal FrameID Communication of the upper-level with lower-level frame abnormal (1) Check if the data configurations are correct. (2) Check if the main node board of this frame and superior board operate normally. (3) Check if the inter-frame communication link is normal.

6.5.2 Insufficient TS Resources


Alarm ID Description Parameters Cause description Processing suggestion 0x12100000 Alarm class Event Alarm level Major

No TS resources are available for the port. FrameID, SlotID, PortID, V5ID, and Protocol Address TS resources are not enough for allocation. (1) Check if the fault is caused by suddenly increased traffic, if yes, check what makes it increase suddenly, and there is no need to handle the equipment. (2) Check if the user convergence ratio is rather high. If the number of subscribers in the ONU frame is large while the number of trunk lines is small, then the number of trunk lines should be increased.

6-8

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.5.3 Local Port Blocking Indication


Alarm ID Description Parameters Cause description Processing suggestion 0x0a000060 Alarm class Event Alarm level Minor

Local port blocking indication FrameID, SlotID, and PortID Blocking command is executed, or the port is blocked automatically due to port fault. In case of not manual blocking operation, check if the board that contains this port works normally.

6.5.4 Peer End Port Blocking Indication


Alarm ID Description Parameters Cause description Processing suggestion 0x0a000061 Alarm class Event Alarm level Minor

Peer end port blocking indication FrameID, SlotID, and PortID Blocking command is executed, or the port is blocked automatically due to port fault. In case of not manual blocking operation, check if the board that contains this port works normally.

6.5.5 Port Locking Indication


Alarm ID Description Parameters Cause description Processing suggestion 0x0a100063 Alarm class Event Alarm level Minor

Subscriber port locked FrameID, SlotID, and PortID The subscriber is off hook for a long time, or the subscriber external line is abnormal. Check the subscriber external line.

6-9

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.5.6 V5 Interface Interruption


Alarm ID Description Parameters Cause description 0x0d010002 Alarm class Event Alarm level Major

V5 interface interrupted V5 ID (1) Trunk line of V5 interface is abnormal. (2) Trunk board of V5 interface is abnormal. (3) Peer end V5 interface is abnormal. (1) Check if the trunk line related to the V5 interface is interrupted. (2) Check if the trunk board related to the V5 interface is in position or works normally. If it is not in position, plug in the board. If it does not work normally, reset it or reinstall it. (3) Restart the V5 interface. (4) Check if the interconnected V5 interface works normally. If not, reset it.

Processing suggestion

6.5.7 Receiving V5 Protection Switching Command


Alarm ID Description Parameters Cause description Processing suggestion 0x0d10000b Alarm class Event Alarm level Major

Receiving protection switching command V5 ID, logic C-channel ID, link ID, TS No. The V5 interface at LE side initiates the protection switching command. No need to proceed

6.5.8 Originating Protection Switching Request


Alarm ID Description Parameters Cause description Processing suggestion 0x0d10000c Alarm class Event Alarm level Major

Originating protection switching request V5 ID, logic C-channel ID, link ID, TS No. AN V5 interface originates protection switching request. No need to proceed

6-10

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.5.9 Link Blocking


Alarm ID Description Parameters Cause description Processing suggestion V5 ID, and link ID The link is blocked from the LE or AN side. The unblocking command is executed at the LE or AN side. 0x0d110010 Alarm class Fault Link blocking Alarm level Major

6.5.10 V5 Interface Restart Failure


Alarm ID Description Parameters Cause description Processing suggestion 0x0d200004 Alarm class Fault Alarm level Major

V5 interface restart failure V5 ID Restarting V5 interface fails. (1) Check the E1 link. (2) Check the interface data, and restart the interface. Meanwhile, open the information trace window, and check the receiving and transmitting of the information on both sides.

6.5.11 V5 Link ID Failure


Alarm ID Description Parameters Cause description Processing suggestion 0x0d200013 Alarm class Event Alarm level Major

Link ID unsuccessful V5 ID, link ID (1) Link ID mark failure (2) Link ID unsuccessful, no response from the LE side (3) Link ID unsuccessful, LE side refused (1) Check if the 2M link physical connection is correct. (2) Check if the local or remote end supports the link ID program.

6-11

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.6 Analysis and Processing of SPC Alarms


6.6.1 Semi-permanent Connection Interruption
Alarm ID Description Parameters 0x0c310001 Alarm class Fault Alarm level Major

Semi-permanent connection (SPC) fault alarm SPC NO. (1) SPC start port busy (2) SPC end port busy (3) SPC start port fault (4) SPC end port fault (5) SPC start port loopback (6) SPC end port loopback (7) SPC start port locked (8) SPC end port locked (9) SPC data paradox (10) SPC data invalid (11) SPC system resource insufficient (12) SPC timeout (13) SPC type not configured (14) SPC start data consistent with end data (15) SPC start channel number invalid (16) SPC end channel number invalid (17) SPC start port data invalid (18) SPC end port data invalid (19) SPC peer end data invalid (20) SPC maximum channel number invalid (21) SPC application type invalid (22) SPC start port under test (23) SPC end port under test (1) Wait until this device becomes idle, or force it idle. (2) Wait until this device becomes idle, or force it idle. (3) Check if the board of this device works normally. If yes, reset the board, otherwise, reinstall the board and check the configuration data. If the fault persists, change the board. (4) Check if the board of this device works normally. If yes, reset the board, otherwise, reinstall the board and check the configuration data. If the fault persists, change the board. (5) Cancel the loopback of the start port. (6) Cancel the loopback of the end port. (7) Hang up the phone connected to the start port. (8) Hang up the phone connected to the end port. (9) Some equipment in SPC list is used for different SPC. Delete this connection. (10) The equipment in SPC does not exist. Check the data configuration related to the equipment in the SPC. (11) The SPC fails to allocate system resources due to some cause. This fault will be recovered automatically. (12) The SPC internal timer is timeout. If the SPC can not be established, reconfigure it. (13) Reconfigure the SPC type. (14) Reconfigure the SPC start or end data. (15) Reconfigure the SPC start channel ID. (16) Reconfigure the SPC end channel ID. (17) Reconfigure the SPC start port data. (18) Reconfigure the SPC end port data. (19) Reconfigure the SPC peer end data. (20) Reconfigure the maximum channel quantity of the SPC. (21) Reconfigure the application type of the SPC. (22) Wait until the test is finished. (23) Wait until the test is finished.

Cause description

Processing suggestion

6-12

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.7 Analysis and Processing of MTA Alarms


6.7.1 Abnormal MTA Communication
Alarm ID Description Parameters Cause description Processing suggestion 0x0a010067 Alarm class Fault Alarm level Minor

MTA communication abnormal FrameID, SlotID, and PortID Communications of MTA with the board interrupted (1) Check if the MTA is powered on. (2) Check the U-interface line. If it is normal, power off and then power on the MTA. Otherwise, replace the U-interface line. (3) Replace the MTA.

6.7.2 MTA B1/B2 Channel Local End LFA


Alarm ID Description Parameters Cause description Processing suggestion 0x0a000069 Alarm class Event Alarm level Minor

MTA B1/B2 channel local end LFA FrameID, SlotID, and PortID MTA local end equipment has sub-rate adaptation LMFA. (1) Check the SPC. If it is abnormal, reconnect it. (2) Check if the board has fault. If it has, replace the board. (3) Check the remote loopback. If it is abnormal, replace the board. (4) Check if the transmission line is connected normally.

6.7.3 MTA B1/B2 Channel Peer End LFA


Alarm ID Description Parameters Cause description Processing suggestion 0x0a00006a Alarm class Event Alarm level Minor

MTA B1/B2 channel peer end LFA FrameID, SlotID, and PortID MTA peer end equipment has sub-rate adaptation LMFA. (1) Check the SPC. If it is abnormal, reconnect it. (2) Check if the board has fault. If it has, replace the board. (3) Check the remote loopback. If it is abnormal, replace the board. (4) Check if the transmission line is connected normally.

6-13

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.7.4 Equipment Connected with MTA Data Port Not Ready


Alarm ID Description Parameters Cause description Processing suggestion 0x0a00006b Alarm class Event Alarm level Minor

Equipment connected with the MTA data port not ready FrameID, SlotID, and PortID MTA does not detect data port external equipment ready signal (1) Check the SPC. If it is abnormal, reconnect it. (2) Check if the board has fault. If it has, replace the board. (3) Check the remote loopback. If it is abnormal, replace the board. (4) Check if the transmission line is connected normally.

6.8 Analysis and Processing of HSL Alarms


6.8.1 LFA of FE1 Port of HSL Board
Alarm ID Description Parameters Cause description Processing suggestion 0x0a11007d Alarm class Fault Alarm level Major

LFA of FE1 port of HSL board FrameID, SlotID, and PortID FE1 port LFA alarm is received. Check if the equipment connected with the FE1 port works normally.

6.8.2 Loss of Signal of FE1 Port of HSL Board


Alarm ID Description Parameters Cause description Processing suggestion 0x0a01007c Alarm class Fault Alarm level Major

Loss of signal (LOS) of FE1 port of HSL board FrameID, SlotID, and PortID FE1 port signal is lost. Check if the equipment connected with the FE1 port works normally.

6-14

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.9 Analysis and Processing of BAS Alarms


6.9.1 Accounting Server Communication Interruption
Alarm ID Description Parameters Cause description Processing suggestion 0x0f310003 Alarm class Fault Alarm level Major

Communication of the Authentication, Authorization and Accounting (AAA) with the RADIUS Accounting Server is interrupted. IP address Communication line fault Check the line.

6.9.2 Authentication Server Communication Interruption


Alarm ID Description Parameters Cause description Processing suggestion 0x0f310004 Alarm class Fault Alarm level Major

Communication of AAA with the RADIUS Authentication Server is interrupted. IP address Communication line fault Check the line.

6.9.3 Bill Pool Overflow


Alarm ID Description Parameters Cause description Processing suggestion 0x0f310008 Alarm class Fault Alarm level Major

Local bill pool exceeds the threshold, and bills in it need to be moved. Bill pool occupancy Bill pool exceeds the threshold. Backup bills to Flash Memory.

6-15

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.9.4 Bill Pool Full


Alarm ID Description Parameters Cause description Processing suggestion 0x0f310009 Alarm class Fault Alarm level Major

The occupancy of bill pool reaches 100%, and it is necessary to backup bills at once. None The occupancy of bill pool reaches 100% Backup the bills to the Flash Memory.

6.9.5 Flash Bill Pool Full


Alarm ID Description Parameters Cause description Processing suggestion 0x0f31000f Alarm class Fault Alarm level Major

The occupancy of Flash bill pool reaches 100%, and it is necessary to move bills at once. None The occupancy of Flash bill pool reaches 100%. Move the bills from the Flash bill pool at once.

6.9.6 Flash Card Damaged or Not in Position


Alarm ID Description Parameters Cause description Processing suggestion 0x0f300012 Alarm class Event Alarm level Major

Flash card damaged, or not in position None Flash card expired or not in position Insert a Flash card or replace the old card.

6.9.7 TFTP Server Having No Route or Unreachable


Alarm ID Description Parameters Cause description Processing suggestion 0x0f000013 Alarm class Event Alarm level Major

TFTP Server has no route or is unreachable. IP address TFTP Server has no route or is unreachable. Check the route and TFTP Server.

6-16

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.9.8 IPoA User Creation Failure


Alarm ID Description Parameters Cause description Processing suggestion 0x0f100014 Alarm class Event Alarm level Major

IPoA user creation failed FrameID, SlotID, PortID, VPI, and VCI Number of users of IPU board may reach the limit. Reactivate the user.

6.10 Analysis and Processing of CES Alarms


6.10.1 LOS of CES E1 Line
Alarm ID Description Parameters Cause description Processing suggestion 0x0a310007 LOS of E1 line FrameID, SlotID, and PortID Local receiving fault or remote transmitting fault (1) Check if the Tx and Rx lines at both ends are connected correctly. (2) Check if the line is broken. (3) Check if the opposite end device is normal. Alarm class Fault Alarm level Major

6.10.2 LFA of CES E1 Line


Alarm ID Description Parameters Cause description Processing suggestion 0x0a310008 E1 line LFA FrameID, SlotID, and PortID System detects loss of synchronous signal, which is caused by wrong frame format of the peer end. (1) Check if frame formats at both ends are consistent. (2) Check if the clocks at both ends are synchronized. Alarm class Fault Alarm level Major

6-17

Troubleshooting Manual HONET Integrated Services Access Network

Chapter 6 Alarm Analysis and Processing

6.10.3 CES E1 Line Remote Alarm


Alarm ID Description Parameters Cause description Processing suggestion 0x0a310009 Alarm class Fault Alarm level Major

E1 line remote alarm FrameID, SlotID, and PortID (1) Local Tx or remote Rx is faulty. (2) Peer end detects loss of synchronization signal. (1) Check if the local Tx or remote Rx is normal. (2) Check if the frame formats at both ends are consistent. (3) Check if the clocks at both ends are synchronized.

6.10.4 E1 Line CRC4 Alarm


Alarm ID Description Parameters Cause description Processing suggestion 0x0a310012 Alarm class Fault Alarm level Major

E1 line CRC4 alarm FrameID, SlotID, and PortID CRC4 settings at both ends are different. Modify the CRC4 setting at local end or peer end to make the setting consistent.

6-18

Troubleshooting Manual HONET Integrated Services Access Network

Appendix Abbreviations and Acronyms

Appendix Abbreviations and Acronyms


Abbreviation A AAA AAL1 ADSL AN ARP ASL ATM B BAS BITS C CBR CD CES CPE CPU CRC CSMA D DCE DNS DSLAM DTE DTR E F FAS FE FLASH FLP G GE H HSL HW I IMA IP IPoA IPoEoA J K L LAN LE LOCD LOF LOP LOS M MAC MODEM Full expression Authentication, Authorization and Accounting ATM Adaptation Layer Type 1 Asymmetric Digital Subscriber Line Access Network Address Resolution Protocol Analog Subscriber Line Board Asynchronous Transfer Mode Broadband Access Server Building Integrated Timing Supply system Constant Bit Rate Carrier Detect Circuit Emulation Service Customer Premises Equipment Center Processing Unit Cyclic Redundancy Check Carrier Sense Multiple Access Data Communications Equipment Domain Name Server Digital Subscriber Line Access Multiplexer Data Terminal Equipment Data Terminal Ready Frame Aligning Signal Fast Ethernet FLASH memory Fast Link Pulse Gigabit Ethernet High-speed Subscriber Line Board Highway Inverse Multiplexing over ATM Internet Protocol Internet Protocols over ATM IP over Ethernet over ATM

Local Area Network Local Exchange Loss Of Cell Delimitation Loss Of Frame Loss Of Pointer Loss Of Signal Media Access Control MOdulator-DEModulator 1

Troubleshooting Manual HONET Integrated Services Access Network Abbreviation MTA N NAT NLP NNI NRT-VBR O ODF OLT ONU OSPF P PCM POTS PPP PPPoE PRBS PVC Q QoS R RARP RSP RTU RT-VBR S SCB SDH SDT SIG SRAM STM-1 STM-4 T TCP TDM TFTP U UBR UDT UNI UPC UTOPIA V VC VCC VCI VP VPI W X Y Z

Appendix Abbreviations and Acronyms Full expression

Multifunctional Terminal Adapter Network Address Translation Normal Link Pulse Network-Network Interface Non-Real Time Variable Bit Rate Optical Distribution Frame Optical Line Terminal Optical Network Unit Open Shortest Path First Pulse Code Modulation Plain Old Telephone Service; Point-to-Point Protocol PPP Over Ethernet Pseudo-Random Binary Sequence Permanent Virtual Channel Quality of Service Reverse Address Resolution Protocol Remote Subscriber Processor Remote Terminal Unit real time Variable Bit Rate System Control Unit Synchronous Digital Hierarchy Structured Data Transfer Signal Tone Board Static Random Access Memory Synchronous Transport Mode -1 Synchronous Transport Module -4 Transfer Control Protocol Time Division Mulitiplexing Trivial File Transfer Protocol Unspecified Bit Rate Unstructured Data Transfer User Network Interface Usage Parameter Control Universal Test & Operations PHY Interface for ATM Virtual Channel Virtual Channel Connection Virtual Channel Identifier Virtual Path Virtual Path Identifier

You might also like