Smartax Ma5612 2

SmartAX MA5612 Multi-service Access Module
V800R311C00
Maintenance Guide
Issue 01
Date 2012-07-25
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2012-07-25) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Maintenance Guide About This Document
About This Document
Intended Audience
This document provides the routine maintenance guide and troubleshooting guide to the
MA5612, and introduces the methods for replacing the parts. This document helps the intended
audience to perform the routine maintenance, replace the parts, and rectify the faults on the
MA5612.
This document is intended for:
l System maintenance engineers

l Field maintenance engineers
l Network monitoring engineers
NOTE
Based on your requirements, the packet capturing feature may involve using, obtaining, or saving some
information about users' communications for the purpose of safeguarding network operation and protecting
services. Huawei alone is unable to collect or save the content of users' communications. It is suggested that you
activate the interception-related functions based on the applicable laws and regulations in terms of purpose and
scope of usage. You are obligated to take considerable measures to ensure that the content of users'
communications is fully protected when the content is being used and saved.
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

your time.
Issue 01 (2012-07-25) Huawei Proprietary and Confidential ii

Symbol Description
Provides additional information to emphasize or

supplement important points of the main text.
Command Conventions
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... } Alternative items are grouped in braces and separated by

vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
GUI Conventions
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the “>”

signs. For example, choose File > Create > Folder.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Issue 01 (2012-07-25)
Compared with issue 01 (2011-10-28) of V800R310C00, V800R311C00 has the following
changes:
Modified:
Issue 01 (2012-07-25) Huawei Proprietary and Confidential iii

The contents in 4 Troubleshooting Services Transmitted Through a GE Port and 5

Troubleshooting Services Transmitted Through a GPON Port are optimized.
Issue 01 (2012-07-25) Huawei Proprietary and Confidential iv

Maintenance Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Overview.........................................................................................................................................1
1.1 Maintenance Purpose..........................................................................................................................................2
1.2 Maintenance Principle........................................................................................................................................2
1.3 Maintenance Tools.............................................................................................................................................4
2 Field Maintenance Guide............................................................................................................6

2.1 Checking the Grounding of the Device..............................................................................................................7
2.2 Cleaning the Connector of the Optical Fiber......................................................................................................8
2.3 Cleaning the Air Filter of the Cabinet..............................................................................................................10
2.4 Checking Batteries............................................................................................................................................11
2.5 Checking the surge protector............................................................................................................................13
3 Engineers' Must-Read.................................................................................................................15
3.1 Engineer Skill Requirements............................................................................................................................16
3.2 Troubleshooting Precautions............................................................................................................................16
3.3 Precautions for Replacing a Part......................................................................................................................17
3.4 Troubleshooting Procedure...............................................................................................................................21
3.5 Frequently Used Methods for Troubleshooting................................................................................................23
3.6 Contacting Huawei for Assistance...................................................................................................................26
4 Troubleshooting Services Transmitted Through a GE Port ...............................................29

4.1 Troubleshooting LAN Internet Service............................................................................................................30
4.1.1 Troubleshooting the Failure to Access the Internet.................................................................................30
4.1.2 Troubleshooting the Failure to Obtain an IP Address by PPPoE Dialup................................................32
4.1.3 Troubleshooting the Failure to Obtain an IP Address in DHCP Mode...................................................39
4.1.4 Troubleshooting Low Internet Access Rate............................................................................................44
4.1.5 Troubleshooting Frequent Interruptions in Internet Service...................................................................47
4.2 Troubleshooting the Multicast Service.............................................................................................................50
4.2.1 Failure to Go Online of a Multicast User................................................................................................50
4.2.2 Blank Screen After Ordering a Program.................................................................................................59
4.2.3 Pixelation in a Multicast Program...........................................................................................................72
4.3 Troubleshooting VoIP PSTN Service ..............................................................................................................78
4.3.1 No Power Feed After Offhook................................................................................................................78
4.3.2 No Tone After Offhook...........................................................................................................................81
Issue 01 (2012-07-25) Huawei Proprietary and Confidential v

4.3.3 Busy Tone After Offhook........................................................................................................................84

4.3.4 Continuous Dial Tone During Dialing....................................................................................................88
4.3.5 Called Party's Phone Does Not Ring.......................................................................................................90
4.3.6 One-Way Audio or No Audio During Communication..........................................................................93
4.3.7 Noise in Communication.........................................................................................................................95
4.3.8 Discontinuous Communication...............................................................................................................99
4.3.9 Low Communication Voice...................................................................................................................100
4.4 Troubleshooting Fax and Modem Services ...................................................................................................103
4.4.1 Fax Service Failures..............................................................................................................................103
4.4.2 Modem Service Failures........................................................................................................................106
4.5 H.248-Based ISDN PRA Service Troubleshooting........................................................................................109
4.6 SIP-Based ISDN PRA Service Fault Troubleshooting...................................................................................110
5 Troubleshooting Services Transmitted Through a GPON Port.......................................112

5.1 Troubleshooting LAN Internet Service..........................................................................................................113
5.1.1 Troubleshooting the Failure to Access the Internet...............................................................................113
5.1.2 Troubleshooting the Failure to Obtain an IP Address by PPPoE Dialup..............................................115
5.1.3 Troubleshooting the Failure to Obtain an IP Address in DHCP Mode.................................................123
5.1.4 Troubleshooting Low Internet Access Rate..........................................................................................129
5.1.5 Troubleshooting Frequent Interruptions in Internet Service.................................................................133
5.2 Troubleshooting Multicast Service.................................................................................................................135
5.2.1 Failure to Go Online of a Multicast User..............................................................................................136
5.2.2 Blank Screen After Ordering a Program...............................................................................................144
5.2.3 Pixelation in a Multicast Program.........................................................................................................161
5.3 Troubleshooting VoIP PSTN Service.............................................................................................................167
5.3.1 No Power Feed After Offhook..............................................................................................................167
5.3.2 No Tone After Offhook.........................................................................................................................170
5.3.3 Busy Tone After Offhook......................................................................................................................173
5.3.4 Continuous Dial Tone During Dialing..................................................................................................177
5.3.5 Called Party's Phone Does Not Ring.....................................................................................................179
5.3.6 One-Way Audio or No Audio During Communication........................................................................182
5.3.7 Noise in Communication.......................................................................................................................184
5.3.8 Discontinuous Communication.............................................................................................................188
5.3.9 Low Communication Voice...................................................................................................................189
5.4 Troubleshooting Fax and Modem Services....................................................................................................192
5.4.1 Fax Service Failures..............................................................................................................................193
5.4.2 Modem Service Failures........................................................................................................................196
6 System Fault Handling.............................................................................................................199

6.1 Abnormal ONU Status in GPON Upstream Transmission............................................................................200
6.1.1 GPON ONU Registration Failure..........................................................................................................200
6.1.2 Failure to Auto Discover a GPON ONU...............................................................................................216
6.1.3 GPON ONU Frequently Goes Online and Offline................................................................................224
6.2 NMS Fails to Manage a Device......................................................................................................................229
Issue 01 (2012-07-25) Huawei Proprietary and Confidential vi

6.3 The Alarm Information Fails to Be Displayed on the NMS...........................................................................231

6.4 Service Board Is in the Failed State................................................................................................................232
6.5 A Service Board Fails to Register..................................................................................................................234
6.6 Repeated Board Reset.....................................................................................................................................235
6.7 Unexpected Reset of the System....................................................................................................................237
7 Troubleshooting EMU Faults..................................................................................................239

7.1 ESCM Being in Fault State............................................................................................................................240
7.2 EPS30-4815AF Being in Fault State..............................................................................................................241
8 Common Operation...................................................................................................................244
8.1 Performing a Loopback on an E1 Line...........................................................................................................246
8.2 Performing a Loopback on an E1 Port...........................................................................................................247
8.3 POTS Subscriber Circuit Line Test................................................................................................................249
8.4 POTS Subscriber Loop Line Test...................................................................................................................250
8.5 POTS Subscriber Search Tone Test...............................................................................................................251
8.6 POTS Subscriber Signal Tone Test................................................................................................................253
8.7 POTS Port Loop Test.....................................................................................................................................254
8.8 Call Emulation Test........................................................................................................................................255
8.9 PPPoE Dialup Emulation Test........................................................................................................................256
8.10 Multicast Emulation Test..............................................................................................................................258
8.11 DHCP Dialup Emulation Test......................................................................................................................259
8.12 Capturing Voice Packets Remotely..............................................................................................................261
8.13 Capturing Packets by Using Port Mirroring.................................................................................................262
9 FAQ..............................................................................................................................................264
9.1 How Is the Broadband Service Board Powered Off Automatically When the Battery Supplies Power........265
A Appendix....................................................................................................................................266
A.1 Indicators ......................................................................................................................................................267
A.2 Making Cables and Connectors.....................................................................................................................268
A.2.1 Making Console-Ethernet Integrated Cables........................................................................................268
A.2.2 Making External Power Cables and Ground Cables with Cord End Terminals...................................269
A.2.3 Making External Power Cables and Ground Cables with OT Terminals.............................................271
A.2.4 Making Ordinary Network Cables........................................................................................................275
A.2.5 Making Shielded Network Cables........................................................................................................278
A.2.6 Making the E1 Cable............................................................................................................................281
A.3 Cable Labels..................................................................................................................................................295
A.3.1 Introduction to Labels...........................................................................................................................295
A.3.2 Filling Labels........................................................................................................................................297
A.3.3 Usage of Labels....................................................................................................................................299
A.3.4 Attaching Labels...................................................................................................................................301
A.3.5 Label for External Alarm Cables..........................................................................................................303
A.3.6 Label for Network Cables.....................................................................................................................304
A.3.7 Labels for Optical Fibers......................................................................................................................305
Issue 01 (2012-07-25) Huawei Proprietary and Confidential vii

A.3.8 Label for Subscriber Cables..................................................................................................................308

A.3.9 Labels for DC Power Cables................................................................................................................309
A.3.10 Labels for AC Power Cables..............................................................................................................310
A.4 Fault Tag........................................................................................................................................................311
Issue 01 (2012-07-25) Huawei Proprietary and Confidential viii

Maintenance Guide 1 Overview
1 Overview
About This Chapter
Describes the purpose of routine maintenance, basic maintenance principles, and required
maintenance tools.
1.1 Maintenance Purpose

This topic describes the maintenance purpose.
1.2 Maintenance Principle
This topic describes the maintenance principle, including the following five parts: the
preparation for routine maintenance, the principle of routine maintenance, the principle of parts
replacement, the principle of troubleshooting, and the principle of maintaining an outdoor
cabinet.
1.3 Maintenance Tools
This topic describes the maintenance tools required on site.
Issue 01 (2012-07-25) Huawei Proprietary and Confidential 1

1.1 Maintenance Purpose

This topic describes the maintenance purpose.
The purpose of routine maintenance is to detect and rectify latent faults when the device is
running and to collect data for analyzing and optimizing the network. This ensures that the system
runs safely, stably, and reliably for a long time.
1.2 Maintenance Principle

This topic describes the maintenance principle, including the following five parts: the
preparation for routine maintenance, the principle of routine maintenance, the principle of parts
replacement, the principle of troubleshooting, and the principle of maintaining an outdoor
cabinet.
Preparation
Prepare for the operation as follows:
l Make sure that the device is grounded correctly according to the grounding requirements.
l Wear the electrostatic discharge (ESD) wrist strap or ESD gloves to protect the device from
ESD damage.
l Place spare boards or other spare parts in ESD bags.
l Take ESD measures to protect the port on the board. When performing operation on a port,
wear the ESD wrist strap or ESD gloves. Discharge the external cables and the protective
jackets of ports before connecting them to a device.
NOTE
It is recommended that you reserve certain installation materials for boards in the equipment room,
such as the vacuum formed box and the ESD bag.
Principle of Routine Maintenance

When performing routine maintenance, comply with the following principles:
l Keep the equipment room tidy, and prevent rodents or other insects from entering the
device.
l Do not install any software that is irrelevant to device maintenance to the maintenance
terminal.
l Maintain the device daily, weekly, monthly, quarterly, and annually according to the guide
to routine maintenance, and fill in the corresponding device maintenance form.
l In the case of an emergent task that is encountered during routine maintenance, such as a
device fault, handle the task by following the troubleshooting procedure, and keep related
records. In the case of the fault that cannot be rectified, contact the local representative
office of Huawei for technical support.
l Do not insert, remove, or reset a board randomly.
l Remove a faulty board from the cabinet; otherwise, other faults may be caused.
l Back up data before data modification, and keep related records.

Principle of Parts Replacement

When performing parts replacement, comply with the following principles:
l Make sure that operations are feasible.

– Check whether spare parts for the part to be replaced are available in the storehouse. If
not, contact the local Huawei representative office for immediate technical support.
– Make sure that parts replacement is performed by only qualified maintenance engineers,
who meet the following requirements:
– Know the functions of the MA5612 parts.
– Know the basic flow of parts replacement.
– Master the basic skills of parts replacement.
– Make sure that the replacement risks are controllable. Parts replacement is the
maintenance operation that has potential risks. Before replacing a part, estimate whether
the risks can be controlled by technical protective measures without powering off the
device. If yes, replace the part. If not, contact the local Huawei representative office for
immediate technical support.
l Check the interchangeability of spare parts before replacing faulty parts or upgrading parts.
l Use ESD bags and ESD boxes to contain and transport spare parts.
l Arrange, record, and return faulty parts in routine maintenance for obtaining available spare
parts in time, especially certain important parts, such as boards.
Principle of Troubleshooting
When performing troubleshooting, comply with the following principles:
l Actively collect fault information. In case of a fault, learn related information about the
fault, and then make further troubleshooting plan.
l During troubleshooting, record each step and the related result. The details of the
troubleshooting process serve as a ground to apply for Huawei technical support and shorten
the troubleshooting time.
l If a fault cannot be rectified, contact the Huawei Customer Service Center. At the same
time, when you report the problem to Huawei engineers, provide the following information:
– Full name of the site where the fault occurs
– Name and telephone number of the contact person
– Time when the fault occurs
– Fault description
– Software version of the MA5612
– Measures taken after the fault and the measure result
– Level of the fault and the expected solution time
Principle of Maintaining an Outdoor Cabinet

To make sure that a cabinet runs outdoors stably for a long time, comply with the following
principles during routine maintenance:

1. When you open the cabinet door, prevent rain and snow from falling into the inner surface
of the device (including the front panel of the service board), from falling into cables, or
from falling into apertures.
2. Do not open the cabinet door in heavy dust. If the dust enters the cabinet, the service life
of the components is affected seriously.
3. It is recommended that you open the cabinet door to maintain the device when the
temperature is in the range from -5°C to +35°C. In this way, the device can be protected
from dew condensation or impact of extreme temperatures.
4. Exercise caution when opening the cabinet door in the case of strong wind. A strong wind
may cause the cabinet door to be opened or closed fiercely. This is dangerous to the
maintenance engineer and may damage the device. Use a door brake to fix the cabinet door
in a specified position.
1.3 Maintenance Tools

This topic describes the maintenance tools required on site.
Table 1-1 lists the maintenance tools required on site.
Table 1-1 Maintenance tools

Tool Description Appearance
Multimeter Tests the

connectivity of
cables and the
electrical
performance
indexes of the
device, including
voltage, current,
and resistance.
Optical power Tests the optical

meter power.

Tool Description Appearance
Adjustable Adjusts the optical

optical attenuator power of optical
signals by adjusting
the optical
attenuation.
Flathead Fastens small

screwdriver screws and bolts.
The screwdriver
has a flat head.
Cross Fastens small

screwdriver screws and bolts.
The screwdriver
has a cross head.
Diagonal pliers Used as a substitute

of scissors to cut
insulating tubes or
cable ties.
Cable tie Bundles cables.
Network cable Clamp phone lines

crimping pliers and RJ-45
connectors.
Network cable Tests the

tester connectivity and
connections of
network cables.

Maintenance Guide 2 Field Maintenance Guide
2 Field Maintenance Guide
About This Chapter
This topic describes the tasks of maintaining the hardware of the MA5612, and the reference
standard, operation guide, exception handling, and command reference of the tasks.
2.1 Checking the Grounding of the Device

To ensure that the device runs reliably and exclude the potential security risks, you need to check
the grounding of the device periodically. To be specific, you need to check whether the ground
cable is connected properly and whether the earth resistance meets the requirement.
2.2 Cleaning the Connector of the Optical Fiber
This topic describes how to clean the connector of the optical fiber. Frequent insert and remove
or no dustproof treatment for a longtime causes the connector to be dirty and aged, which
deteriorates the quality of the line. Therefore, you need to periodically clean the connector of
the optical fiber, including the ends of the optical fiber connector, optical port of the optical
transceiver, and adapter, and take measures to prevent dust.
2.3 Cleaning the Air Filter of the Cabinet
If the MA5612 is installed in a cabinet, it is recommended that you clean the air filters regularly
to ensure that the cabinet is ventilated properly. The air filters include the air filter at the bottom
of the cabinet and the air filter on the cabinet door. In the case of the outdoor cabinet, it is
recommended that you clean the air filters every three to six months. In the case of the indoor
cabinet, it is recommended that you clean the air filters every six months.
2.4 Checking Batteries
When the alternating current (AC) power supplied to a device is cut off, the system automatically
switches to battery power. To ensure that services continue to operate properly after the AC
power is cut off, check the working status of the batteries periodically.
2.5 Checking the surge protector
It is recommended that you protect the lightning proof system and the power system against the
thunder and storms before the raining season. This operation ensures the reliable running of the
device and prevents the potential security disasters that may exist in the system.

2.1 Checking the Grounding of the Device

To ensure that the device runs reliably and exclude the potential security risks, you need to check
the grounding of the device periodically. To be specific, you need to check whether the ground
cable is connected properly and whether the earth resistance meets the requirement.
Tools and Instruments

l Multimeter
l Earth resistance tester
NOTE
The multimeter and the earth resistance tester are commonly used for checking the link. Therefore, they
are for your reference only.
Impact on the System

l Proper connection of the ground cable ensures secure grounding of the device.
l If the ground resistance exceeds the threshold, the surge protection functions of both the
device and the telecommunications room are affected, posing security risks for device
running. For example, the device shell may not be properly grounded or the protective unit
of the device may be burnt out.
Precautions
l Before the thundery and rainy season comes, check the ground system of the device.
l Pay attention to safety of personnel and equipment during device maintenance.
Procedure
Step 1 Check whether the ground cable is properly connected.
Connect one end of the multimeter to the ground cable and the other end to the ground bar or
ground body. Then, check whether the grounding is reliable through the check on the voltage
between the ground cable and the ground bar or ground body.
NOTE
If the grounding is reliable, the voltage between the ground cable and the ground bar or ground body is 0.
Step 2 Check whether the earth resistance meets the requirement.
Use the earth resistance tester to check whether the resistance between the ground bar or ground
body and the earth meets the requirement.
Step 3 If the connection of the ground cable is abnormal or the earth resistance does not meet the
requirement, troubleshoot the fault by referring to "Exception Handling."
----End
Reference Standard
l Check whether the ground cable meets the following requirements:

– Each connection point is secure and reliable without corrosion and oxidation.
– The ground cable does not deteriorate, and its sheath is not damaged.
– The ground bar is not corroded or oxidized, and anti-corrosion measures are taken
properly.
l Check whether the earth resistance meets the following requirements:
– The lap resistance between the ground cable of the device and the ground bar or ground
body is smaller than 0.1 ohm.
– The ground resistance between the ground bar or ground body and the earth is smaller
than 10 ohms.
Exception Handling
1. If the ground cable deteriorates, or its sheath is damaged, replace it.
2. If the connection point of the ground cable is corroded or aged, replace the ground cable
or ground bar.
3. If the lap resistance between the ground cable of the device and the ground bar or ground
body is larger than 0.1 ohm, route the ground cable again.
4. If the ground resistance between the ground bar or ground body and the earth is larger than
10 ohms, take one of the following measures to decrease the ground resistance:
l Bury the ground body or ground network deeper.
l Use a larger ground body.
l Decrease the resistivity of the earth.
5. If the fault persists, contact Huawei technical support engineers. For details, see 3.6
Contacting Huawei for Assistance.
2.2 Cleaning the Connector of the Optical Fiber

This topic describes how to clean the connector of the optical fiber. Frequent insert and remove
or no dustproof treatment for a longtime causes the connector to be dirty and aged, which
deteriorates the quality of the line. Therefore, you need to periodically clean the connector of
the optical fiber, including the ends of the optical fiber connector, optical port of the optical
transceiver, and adapter, and take measures to prevent dust.
Prerequisites
Prepare the cleaning tools before cleaning, and follow "Precautions".
Tools, Meters, and Materials

l Dust-free cotton: a long silk cotton specially used for cleaning the ends of the optical fiber
connector.
l Dust-free bar: used for cleaning the optical port of the optical transceiver and adapter
(flange). It has two specifications: ф2.5 mm and ф1.25 mm. You can select one according
to the port type (use the dust-free bar with ф2.5 mm for the ports of SC and FC types, and
use that with ф1.25 mm for the ports of LC and MTRJ types).
l Dust-proof cap: used for ends of the optical connector, optical port of the optical transceiver,
and adapter.

l Cleaning tool box: used for placing the dust-free cotton and the dust-free cap. Place the
dust-free cotton and the dust-free cap separately from other tools.
l Cleaning reagent (absolute ethyl alcohol) : used for cleaning the connector of the optical
fiber. It is inflammable, and must be securely saved and kept clean.
l Optical fiber section magnifier: a microscope (400*) used for checking whether the ends
of the optical fiber connector is clean and without damage.

Power off the optical transceiver, and then clean the connector of the optical fiber. In this case,
servers carried on the optical port will be interrupted.
Precautions
DANGER
l Do not look directly into the optical fiber connector or the laser transmit port on the optical
port board without eye protection. Exposure of the combustible to the laser light must be
avoided.
l Do not clean any optical module before powering off the optical transceiver.
l To clean the optical transceiver that can be removed and inserted, wear an ESD wrist strap
or wear ESD gloves.
l Put the dust-free cap into the cleaning tool box immediately after taking it off. Place the
dust-free cap not used in the cleaning tool box, or in the ESD bag for sealed save. Clean it
quarterly (it is recommended to clean it with the ultrasonic cleaner).
l Keep your hands clean and dry before tailoring the dust-free cotton, and place the dust-free
cotton not used in the clean ESD bag or the cleaning tool box for sealed save.
l After the cleaning, cover the optical fiber connector, optical transceiver, and adapter that
will not be immediately used with the dust-free caps.
Procedure
Step 1 Clean the ends of the optical fiber connector.
1. Clip a piece of dust-free cotton into 32 clips with the same size.
2. Use two clips of dry dust-free cotton (double-layer) to clean the ends of the optical fiber
connector along one direction for one time. For the dirty connector, use the clips of dust-
free cotton (two-layer) dipped with little cleanser to clean the ends of the optical fiber
connector along one direction for one time. Use another dry dust-free cotton clip to clean
the ends of the optical fiber connector along one direction once. Make sure that the ends
of the optical fiber connector is dry.
NOTE
Don not cyclically use the dust-free cotton. Use the dust-free cotton not touched by your hands.
3. After the cleaning, cover the optical fibers that will not be immediately used with the dust-
free caps.
Step 2 Clean the optical port of the optical transceiver.

1. If the optical transceiver can be removed and inserted, wear ESD gloves or an ESD wrist
strap to remove it.
2. Select dust-free cotton bars with different diameters according to the type of the optical
port, dip one bar with the cleaning reagent, insert the bar into the inner of the optical port,
and then clean it by rotating the bar 360 degrees along the inner wall of the optical port.
3. Use another dry dust-free cotton bar with the same diameter to insert it into the optical port,
and then clean it by rotating the bar 360 degrees along the inner wall of the optical port.
free caps. Wear the ESD gloves or ESD wrist strap to insert the optical transceiver securely
at the place where it is removed.
Step 3 Clean the adapter (flange).

1. Select dust-free cotton bars with different diameters according to the type of the adapter,
insert one bar into the sleeve of the adapter, and then clean it by rotating the bar 360 degrees
along the inner wall of the sleeve.
2. Use another dry dust-free cotton bar with the same diameter to insert it into the sleeve of
the adapter, and then clean it by rotating the bar 360 degrees along the inner wall of the
sleeve.
NOTE
Use the ultrasonic cleaner to clean the adapters that need to be cleaned uniformly.
free caps.
----End
2.3 Cleaning the Air Filter of the Cabinet

If the MA5612 is installed in a cabinet, it is recommended that you clean the air filters regularly
to ensure that the cabinet is ventilated properly. The air filters include the air filter at the bottom
of the cabinet and the air filter on the cabinet door. In the case of the outdoor cabinet, it is
recommended that you clean the air filters every three to six months. In the case of the indoor
cabinet, it is recommended that you clean the air filters every six months.
Tools and Materials

l Vacuum cleaner
l Cotton cloth
Reference Standard
The cabinet is ventilated properly.
Precaution
l It is recommended that you clean the air filter regularly (In the case of the outdoor cabinet,
it is recommended that you clean the air filters every three to six months. In the case of the
indoor cabinet, it is recommended that you clean the air filters every six months.). You can
adjust the frequency based on the condition of the equipment room.
l Exercise caution when cleaning the air filter and prevent sharp objects from damaging it.

l Do not exert extra force when removing the air filer. Otherwise, the air filter may be
distorted.
l Do not install wet air filter into a cabinet. Otherwise, the cabinet will absorb drops during
the air intake. In this case, the internal components may short-circuit and thus causing a
device fault.
l The air filter must be stuck on the sticking bar firmly to avoid separation. If the sticking
bar is not sticky, replace it.
Procedure
l Clean the air filter on the cabinet door.
1. Open the door of the cabinet, and remove the black air filter from the sticking bar that
is fixed on the inner side of the door.
2. Flap the thick dust off the air filter, and use the vacuum cleaner to remove the
remaining dust; or use water to wash the air filter, and then place the air filter in a
well-ventilated place to dry it.
3. Use a clean and dry cotton cloth to clean the inner side of a cabinet.
4. Install the clean and dry air filter on the sticking bar on the inner side of the cabinet
door.
l Clean the air filter at the bottom of the cabinet.
1. Open the front door of a cabinet, press the two buckles of the air filter at the bottom
of the cabinet. Then, raise the air filter and pull it out.
2. Flap the thick dust off the air filter, and use the vacuum cleaner to remove the
remaining dust; or use water to wash the air filter, and then place the air filter in a
well-ventilated place to dry it.
3. Adjust the air filter position to align with the buckles on the front side, and then press
the buckles to fix the air filter.
4. If the air filter is abnormal, handle the problem according to "Exception Handling."
----End
Exception Handling
If the air filter is damaged or aged, or it is to be damaged, replace it with a new one.
2.4 Checking Batteries

When the alternating current (AC) power supplied to a device is cut off, the system automatically
switches to battery power. To ensure that services continue to operate properly after the AC
power is cut off, check the working status of the batteries periodically.
Context
Note the following when checking the batteries:
l Check the working environment and working status of the batteries and ensure that the
following conditions are met:
– The shells of the batteries are clean and intact without leakage or distortion. The poles
and safety valves do not emit an acid mist.

– The joints between the batteries are firm and free of corrosion.
– The spacing between the batteries is at least 10 mm.
– The battery terminals are not bent or damaged. Damaged terminals cause high contact
resistance or cracks in the battery shell.
– The operating temperature of the batteries ranges from -20°C to 50°C.
– When the mains supply is cut off, the cabinet switches to battery power and the power
supply is proper.
l Check the performance of the batteries.
NOTE
If the batteries are not used for a long period, they go into the floating charging state. Therefore, discharge and
charge them periodically to ensure good battery performance.
Procedure
l Discharge and charge the batteries manually.
1. Connect a special discharge and charge instrument to the batteries.
NOTE
Pay attention to the following points when discharging and charging the batteries:
l The special discharge and charge instrument is used to discharge and charge the batteries. If
such a instrument is unavailable, use a simple power supply or the system power supply at the
central office. Ensure that the discharge and charge parameters are properly set when the batteries
are being discharged and charged.
l Qualified personnel monitor the discharge and charge process to prevent exceptions.
l Keep the battery terminals clear of clutter before connection to reduce contact resistance and to
prevent high voltage drops during connection.
l To avoid electrical shorts, keep all tools insulated during connection.
l The anode and cathode of the batteries are placed properly.
l When the batteries are being discharged or charged, all cables are connected properly and tightly.
Otherwise, a closed circuit may catch fire or overheat. In severe cases, the batteries may be
damaged and accidents may occur.
l The charging voltage is less than or equal to the maximum voltage limit of the charged device.
If there are multiple batteries, charge each one multiple times.
l Overcharging the batteries will reduce their life cycle. When the constant voltage is 2.35V/cell
and the limited current circuit is 0.15C10(A), the charging duration lasts 24 hours at most.
2. Set the discharge and charge parameters properly when the batteries are being
discharged and charged.
l Perform an automatic discharge test.
1. Run the display power run info command in Power4830, SMU, LiBATTERY mode
to query the operating information about the power supply. Ensure that the discharge
test can be performed on the batteries.
The automatic discharge test fails in the following cases:

– There is no battery.
– There is no rectifier module.
– The batteries are in manual control mode.
– The battery charge mode is not automatic mode.

2. Run the power battery-test command to configure the parameters for the automatic
discharge test, such as the test interval, start time, test duration, and end-of-charge
voltage.
3. Run the display power battery-test info command to query the discharge test
information about the batteries.
Determine whether the batteries are working properly based on the discharge test
information.
– If the actual end-of-charge voltage is larger than the preset value when the
discharge duration is equal to the preset value, the batteries are working properly.
– If the actual end-of-charge voltage is equal to the preset value when the actual
discharge duration is less than the preset value, the battery capacity is attenuated.
Maintain or replace the batteries on site.
----End
Follow-up Procedure
l If the shells of the batteries are not clean, clean the batteries immediately.
l If the shells of the batteries are leaking or distorted, replace the batteries immediately.
l If the battery terminals are bent or damaged, replace the batteries immediately.
l If the spacing between the batteries is less than 10 mm, adjust the spacing properly.
l If the joints between the batteries are loose or corroded, fix or replace them based on site
requirements.
l If the operating temperature of the batteries is lower than -20°C or higher than 50°C, identify
the cause and rectify the fault.
NOTE
The operating temperature has a significant impact on the life cycle of the batteries. The life cycle
of a battery reduces by half for every 10°C increase in temperature when the battery is operating
outside the acceptable range.
l If the floating charge voltage is abnormal, replace the batteries.
l If the fault persists, contact Huawei technical support. For details on how to contact Huawei
technical support, see 3.6 Contacting Huawei for Assistance.
2.5 Checking the surge protector

It is recommended that you protect the lightning proof system and the power system against the
thunder and storms before the raining season. This operation ensures the reliable running of the
device and prevents the potential security disasters that may exist in the system.
Context
CAUTION
Before the raining season, protect the lightning proof system and the power system against the
thunder and storms. Prevent the body injury and the short circuit when maintaining the device.

Reference Standard
The green LED on the panel of the surge protector is always on. That is, the surge protector
works in the normal state.
Procedure
Step 1 Check the LED of the surge protector.
Step 2 If the LED of the surge protector is faulty, handle the fault according to "Exception Handling"
until the fault is rectified.
----End
Exception Handling
WARNING
Only professionals are allowed to maintain the single phase surge protector and non-
professionals are not allowed to perform the operation.
1. If the LEDs on the panel of the surge protector are abnormal, handle the fault according to
the surge protector type, working LED status, and fault LED status. The following part
takes the SPD28SZ surge protector as an example.
l If the working LED is green, the surge protector works in the normal state.
l If the work LED is red, the over-voltage occurs.
l If the fault LED is off, the surge protector works in the normal state.
l If the fault LED is red, the lightning proof function of the surge protector deteriorates
or fails. In this case, replace the surge protector in time.
2. If the surge protector is faulty, replace it.
3. If the fault persists, contact Huawei technical support engineers. For details, see 3.6
Contacting Huawei for Assistance.

Maintenance Guide 3 Engineers' Must-Read
3 Engineers' Must-Read
About This Chapter
Engineers are required to have certain maintenance knowledge and troubleshooting skills. This
topic describes the knowledge related to device maintenance and common methods used in
troubleshooting faults.
3.1 Engineer Skill Requirements

Engineers need to possess troubleshooting skills so that they can troubleshoot faults successfully.
3.2 Troubleshooting Precautions
Before locating and troubleshooting faults, carefully read and strictly abide by the following
precautions.
3.3 Precautions for Replacing a Part
To ensure normal service running, read the following precautions carefully before replacing a
part.
3.4 Troubleshooting Procedure
Maintenance engineers must be clear about the troubleshooting procedure of carriers, especially
their procedure for handling emergencies. This topic describes a general troubleshooting
procedure. In practice, however, customize and apply the troubleshooting procedure based on
carriers' requirements.
3.5 Frequently Used Methods for Troubleshooting
There are various of methods for fault location. In fault location, different methods are used
together. Therefore, mastering and using these methods are important for improving the
efficiency of troubleshooting.
3.6 Contacting Huawei for Assistance
If the fault persists even after the troubleshooting measures described in this document have
been taken, contact Huawei for assistance (Huawei engineers will provide guidance remotely
or on site on troubleshooting).

3.1 Engineer Skill Requirements

Engineers need to possess troubleshooting skills so that they can troubleshoot faults successfully.
Engineers need to master the following:
1. Basics of communications technologies

l Knowledge about the computer network, such as Ethernet and TCP/IP
l Principles of the multicast service
l Principles of the POTS service
l Principles of the E1 service
l Principles of the ISDN service
2. Networking, services, and functions of the MA5612
l Actual networking conditions
l Hardware structure and performance specifications of the MA5612
l Functions of boards and slots for boards on the MA5612
l Working principles of services and functions of the MA5612
l Service configurations of the MA5612
l Connections between the MA5612 and the other devices over the network
l Protocols used between the MA5612 and the other devices over the network
3. Common operations for locating faults in the MA5612, in addition to:
l Which operations may completely or partially interrupt the service
l Which operations may result in customer complaints
l Which emergency or backup measures are available
l Which operations may damage the equipment
4. Use of common test tools and instruments, including:
l Multimeter
l Line tester
l Optical power meter
l Optical attenuator
5. How to seek help in case of a fault, including but not limited to referring to the
troubleshooting documents or contacting Huawei for assistance
3.2 Troubleshooting Precautions

Before locating and troubleshooting faults, carefully read and strictly abide by the following
precautions.
For maintenance engineers, they should:
l Strictly follow the regulations on operations and industry safety to prevent personal injury
and equipment damage.

l When replacing and maintaining parts of equipment, take ESD measures (for example,
wear the ESD wrist strap).
l When any problem occurs during the troubleshooting, record the original information in
detail.
l Make a record when performing significant operations (for example, restarting the device
or erasing the database). Before such significant operations are performed by qualified
engineers, check whether these operations are feasible and at the same time carry out the
backup and work out contingency and security measures.
l To improve troubleshooting efficiency, make the following preparations before a fault
occurs on the device:
– Get ready the information about physical connections of the on-site devices.
– Make a table containing information (including VLAN, IP address, interconnected port
ID, firewall configurations, and user name and password) about the communications,
interconnection, and rights of parts and devices.
– Make on-site part/device archives where the software and hardware configurations, the
software and hardware versions, and the change information are recorded.
– Periodically maintain the backup device to ensure that its hardware configuration,
software version, and parameters are the same as the working device running over the
existing network. In this way, when the working device is faulty in an emergency, the
faulty device can be replaced with the backup device quickly.
– Periodically check the remote access device and the fault diagnosis tools (including the
testing tools and the packet capture tools) to ensure their normal use.
– Update the fault-related documents in time and place them in an easily accessible place
(the latest documents can be obtained at http://support.huawei.com).
3.3 Precautions for Replacing a Part

To ensure normal service running, read the following precautions carefully before replacing a
part.
Replaceable Parts
Table 3-1 lists the replaceable parts, and the impact of the replacement on services.
CAUTION
If the replacement affects the running of the live network, perform the replacement when the
device carries minimum traffic.
Table 3-1 Replaceable parts, and impact on services on replacement of the MA5612
Parts Impact on Services
Board Services carried on the board are interrupted.
Chassis Services are interrupted.

Parts Impact on Services
Optical transceiver Services carried on the optical port are interrupted.
Cable Services carried on the cable are interrupted.
Precautions for Replacing Boards

Storage and transportation of boards
l When a board is outside the shelf (chassis), carry and place the board carefully. Take ESD
measures to protect the board. Place the board horizontally. Keep the side with firm parts
facing downward. Do not place any objects on the horizontal surface of the board.
l Do not place a board in an environment of humidity or direct sunlight. Make sure that the
environment where the board is temporarily stored is suitable for storage.
l When transporting multiple boards, if only the ESD bag is used as the protection material,
do not stack the boards together for transportation. Perform operations on only one board
at a time.
Insertion and removal of boards
DANGER
Do not remove or insert the power connector or power board when they are still connected to
the power supply.
l Take ESD measures before the replacement.

l Insert or remove only one board at a time. Do not insert or remove multiple boards at the
same time.
l When inserting or removing a board, make sure that the board is not connected to any
external cables.
l When connecting or disconnecting optical fibers on the front panel of a board to be replaced,
do not look directly at the optical port without wearing protective glasses. The laser emitted
from the optical port can injure your eyes.
l Do not touch the surface of the printed circuit board (PCB).
l Select the screwdriver of a proper type. Using the screwdriver of an unmatched type can
damage the grooves on the head of the screws.
l Prevent short circuit caused by any metallic object, such as tools that are placed improperly
or screws that fall into the shelf accidentally.
l When inserting or removing a board, prevent any collision to the parts on the board, and
make sure that you do not pull the surrounding cables by accident.
l Strictly follow the regulations when using tools to insert or remove a board. Otherwise, the
board may be damaged.
l When removing a board, after the board is separated from the backplane, wait for several
seconds and then remove the board carefully. This protects the other boards from the
electricity discharge of the removed board.

l When inserting the board, make sure that you align the board with the board tracks and
insert the board along the board tracks so that the board is in proper contact with the
backplane.
l Insert a board (in the disconnected state) into or remove it from the slot carefully. Make
sure that the board does not collide with the shelf (chassis) or the boards in adjacent slots.
Parts Precautions Suggestions
Service Removing a service board that is -

boards loading a program can damage the
program. Therefore, before replacing a
service board, make sure that the
service board is not loading any
program. When a board is loading a
program, the running status LED of this
board blinks rapidly.
Precautions for Replacing Optical Transceivers
DANGER
During the replacement of an optical transceiver, do not look directly at an optical port without
wearing protective glasses. The laser emitted from the optical port can injure your eyes.

l Only external optical transceivers (pluggable) can be directly replaced. During the
replacement of an external optical transceiver, you need not remove or install the board
into which the optical transceiver is plugged. Built-in optical transceivers cannot be directly
replaced. To replace a built-in optical transceiver, you need to replace the daughter board
or board to which the built-in optical transceiver is attached.
l During the replacement, make sure that the optical transceiver is not connected to any
optical fibers.
l Exercise caution when inserting or removing an optical fiber. Do not damage the optical
fiber connector.
l During the entire replacement, keep the optical ports of the optical transceiver and the
optical fiber connectors clean. Protect them from dust and other contamination sources.
l After removing the optical fibers from the optical ports of the optical transceiver, cover the
optical fiber connectors with protective caps. Then, place the optical fibers properly and
make sure that they do not swing. Swinging optical fibers may affect the replacement of
the optical transceiver.
l Apply proper force when removing an optical transceiver, because excessive force may
damage the optical transceiver.
l Use assistant tools such as a fiber extractor to remove an optical transceiver if operation
space is limited.

l If an optical transceiver is difficult to remove, you can pull the handle bar of the optical
transceiver and press the optical transceiver with your thumb on the side with the handle
bar against the other side to remove the optical transceiver.
l The curvature radius of the optical fiber must be 20 times greater than the diameter of the
optical fiber. Generally, the curvature radius is greater than or equal to 40 mm.
Precautions for Replacing Cables
DANGER
When installing or maintaining an optical interface board or optical fiber, do not look directly
at the optical port or the optical fiber connector without wearing protective glasses.

l When removing a cable, make sure that you do not pull other cables by accident. When
routing a new cable, make sure that it is not entangled with other cables.
l If the cable to be replaced is inside a bundle, provided that the cabinet is in a good ventilation
condition, it is suggested to directly cut off the connectors at both ends of the cable using
diagonal pliers. In this case, you need not remove the old cable from the bundle.
Power l If software-related operations can -

cable be performed through the GUI and
the CLI in the system, save data
before performing the replacement
in the field. If data fails to be saved,
perform the replacement directly.
l During replacement, make sure
that the input power of the power
cable to be replaced is turned off.
l Insulate the DC terminals and other
exposed electrical parts.
l Connect the positive end and
negative end of a power cable
correctly.

Optical l Select the optical fiber according to You can use a fiber extractor to remove
fiber the type (single-mode or multi- an optical fiber.
mode) of the optical transceiver,
the type of the optical fiber
connector, and the required optical
fiber length.
l Exercise caution when inserting or
removing an optical fiber. Do not
damage the optical fiber connector.
l The curvature radius of the optical
fiber must be 20 times greater than
the diameter of the optical fiber.
Generally, the curvature radius is
greater than or equal to 40 mm.
l Clean the end face of an optical
fiber if its end face is not clean. For
operation details, see Cleaning the
Connector of the Optical Fiber.
3.4 Troubleshooting Procedure

Maintenance engineers must be clear about the troubleshooting procedure of carriers, especially
their procedure for handling emergencies. This topic describes a general troubleshooting
procedure. In practice, however, customize and apply the troubleshooting procedure based on
carriers' requirements.
Figure 3-1 shows the troubleshooting procedure.

Figure 3-1 Troubleshooting procedure
Start
Use the emergency Yes Determine whether a

handling method fault is an emergency
No
Collect and record the

fault information
Locate and rectify

the fault
Check whether the No Contact Huawei for

fault is rectified assistance
Yes
Record the troubleshooting

procedure
End
Determining Whether a Fault Is an Emergency

After being informed of a fault, maintenance engineers need to determine whether the fault is
an emergency according to relevant criteria and take troubleshooting measures accordingly.
Different carriers define emergency differently; therefore, be clear about the specific definition
of emergency of a certain carrier.
If the fault is an emergency, use the pre-defined emergency handling methods to recover services
in a timely manner.
Collecting and Recording the Fault Information

A clear fault description can speed up fault locating no matter whether a fault is reported to a
relevant department of carriers or to Huawei. Therefore, when a fault occurs, collect the fault
information at the earliest time.
According to the form for reporting a fault, collect the fault information and record the
information in the form. This helps to output a troubleshooting report later or to facilitate in
contact Huawei for assistance.

Locating and Rectifying the Fault

According to the fault locating methods provided by the device, find out the root cause of the
fault and take proper troubleshooting measures (for example, repairing the line, replacing the
faulty parts, or modifying the configuration data). This is the core part of troubleshooting
activities. For detailed operations, see relevant information therein for the troubleshooting of
services and functions.
Check Whether the Fault Is Rectified

After the troubleshooting measures are taken against the fault, verify and test the affected
services and functions to confirm that the fault is already rectified.
If the fault persists, fill in fault report form and contact Huawei for assistance.
Contacting Huawei for Assistance

3.5 Frequently Used Methods for Troubleshooting

There are various of methods for fault location. In fault location, different methods are used
together. Therefore, mastering and using these methods are important for improving the
efficiency of troubleshooting.
To improve fault location efficiency, follow the principles of from external to internal and from
large to small. Specifically, check whether the connection of external cables is reliable and
whether the indicators are normal, check the running status of the system through the console,
and check the running status of each module.
Table 3-2 lists the frequently used methods for locating a fault.
Table 3-2 Troubleshooting procedure

Troubleshooting Frequently Used Other Methods
Procedure Methods
Troubleshoot an external l Comparison analysis l Alarm analysis

device fault l Interchange analysis l Performance analysis
l Meter test
l Protocol analysis
Locate a fault to a specified l Exclusive method l Alarm analysis

device l Configuration data l Performance analysis
analysis
Locate a fault to a board l Exclusive method Protocol analysis

l Interchange analysis
l Meter test

Configuration Data Analysis

Incorrect re-configurations and expansion configurations, and outstanding problems of existing
configurations are possible causes of a fault. Therefore, when locating and troubleshooting a
fault, analyze the configuration data. Maintenance engineers need to master configuration
methods and implementation principles of different services and functions to check the
configuration data for different faults and to improve troubleshooting efficiency.
Alarm Analysis
Causes of certain faults can be found by analyzing alarms, or a fault can be located using alarm
analysis together with other methods.
An alarm is an important message when a fault or an event occurs. The alarm information
includes the detailed description and the possible cause of a fault or an abnormality, and the
troubleshooting advice. The information also involves aspects such as the hardware, link,
service, and CPU usage. The volume of the alarm information is large and complete, which is
the important basis for fault analysis and location.
When a fault occurs in the system, check whether an alarm is generated in the system. If an alarm
is generated, analyze the alarm associated with the fault, and clear the alarm to rectify the fault
by referring to Alarm Reference.
Comparison Analysis
Comparison analysis compares the faulty components or symptoms with the normal components
or symptoms, and find out differences, to locate the fault. For example, compare line parameters
of faulty services with line parameters of normal services, or compare devices at the same
network layer. Comparison analysis applies to faults that are caused by a single factor.
Interchange Analysis
When a fault cannot be located after the faulty parts are replaced, maintenance engineers can
locate and troubleshoot the fault using the interchange analysis.
Interchange is to interchange the parts that may be faulty with normal parts (such as boards and
cables), and compare the running conditions to locate the faults. This method applies to the
following scenarios:
l After a part is replaced, the scope or the location of the fault cannot be found.
l The fault is caused by multiple factors.
CAUTION
The interchange operation is risky to certain extent. For example, when users install the short-
circuited board in a normal running subrack, the subrack is damaged. Therefore, to prevent
another fault from occurring, exercise caution when using the interchange analysis.
Exclusive Method
When a fault is complicated and involves multiple stages, maintenance engineers can locate the
fault using the exclusive method to exclude the normal stages.

To use the exclusive method, maintenance engineers must know stages where the fault may
occur, and use applicable methods (such as loopback and configuration data analysis) to locate
the fault. Therefore, maintenance engineers must be familiar with the following information:
l System structure and working principles of the MA5612
l Stages where the fault may occur
l Fault diagnosis operations, such as loopback and configuration data analysis
l Usage of testers
NOTE
The exclusive method involves all the stages on the entire network. It is recommended that maintenance
engineers exclude normal stages in the following principle: remote end first and local end, major cause
first and the minor cause, simpleness first and then complication. This reduces troubleshooting cost and
improves troubleshooting efficiency.
Protocol Analysis
Protocol analysis locates and troubleshoots a fault when the MA5612 is improperly
interconnected with the upper layer device.
Protocol analysis indicates the method for analyzing a fault by tracing the signaling. To use the
protocol analysis method, maintenance engineers must be familiar with the related protocols and
the exchange process for packets so that they can locate the fault based on the obtained packets.
For example, a user fails to order multicast programs. After the packets are captured and
analyzed, it is found that the BRAS discards the Internet Group Management Protocol (IGMP)
packets sent from the user.
Meter Test
Meter test method locates and troubleshoots a fault by comparing the actual values of
performance parameters tested by various instruments and meters with the correct values.
Instruments and meters directly indicate the running status of the device through visual and
quantitative data.
The following instruments and meters are frequently used for troubleshooting:
l Multimeter
l Line tester
l Optical power meter
l Optical attenuator
Performance Analysis
Performance analysis uses the performance statistics provided by the MA5612 to analyze the
performance indexes of the faulty service to locate the fault.
Maintenance engineers must query different performance statistics to locate different faults and
therefore they must be familiar with the following information:
l System structure and operation mechanism
l Statistics provided by the system
l Method of querying and analyzing the statistics

For example, run the display port statistics command in Ethernet port mode to query the
statistics on Ethernet ports. Based on the statistics, maintenance engineers can check whether
the system is running properly.
l If the number of cyclic redundancy check (CRC) error frames increases quickly, the links
between the devices may be unavailable, port negotiation may be incorrect, or that a
physical fault has occurred on the port.
l If a large number of frames are discarded, the traffic transmitted from the interconnected
device exceeds the receive capability of the local port.
3.6 Contacting Huawei for Assistance

Call local Huawei branches or representative offices or contact Huawei Customer Service
Center.
Contact Huawei Customer Service Center: support@huawei.com.
Before contacting Huawei for technical support, fill in the form for reporting a fault shown in
Table 3-3 and deliver this form to Huawei by fax or email. This can help us rectify the fault
quickly for you. The more detailed and accurate the fault information you provide, the more
helpful for subsequent fault locating.
Table 3-3 Form for reporting a fault

[YYYY-MM-DD XX (carrier name) in XX (region name)] XX (brief description of a
fault)
Full name of the office where

the fault occurs
Name and telephone number

(mobile/fixed line telephone
number) of the contact
person
Remote access parameters A remote maintenance environment needs to be set up and

remote access parameters need to be provided.


fault)
Fault symptom Including but not limited to:

l Detailed fault symptom: Describe the fault symptom in
detail.
l Background information about the fault: Describe what
operations have been performed by users or maintenance
engineers before the fault occurs and whether data
modification or relevant operations are performed on
other devices in a same networking.
l Fault time: Write down the time when the fault occurs.
l Fault range: Describe whether the fault occurs on single
offices or all offices, or on a single port or all ports, or on
a single board or all boards.
l Fault probability: Describe whether the fault occurs on
a probability basis.
Networking information Describe all networking information (do not write down only
the name of the access network equipment. Instead, provide
the detailed description of connections between the lower
equipment and the upper equipment). The networking
diagram can be provided.
The description is specific to the minimum NE, including
relevant equipment such as access network equipment,
transmission equipment, and switches. This aims to know
about the peripheral equipment of the access network.
Version Information Including but not limited to:

l Equipment version and patch information: Run the display
language, display version, anddisplay patchcommands
respectively.
l Board configuration, board software, bar code
information: Run the display board 0, anddisplay
version commands to query the board information. You
can read the bar code (close to the ejector level) on the
front panel of the board.
l If terminals are involved, relevant information about the
terminals (such as terminal type and terminal vendor)
needs to be provided.
l If network management system (NMS) equipment or core
network equipment is involved, its version information
needs to be provided.
l In the case of faults in the VoIP service, the DSP version
ID needs to be provided. (The DSP version ID can be
queried by running the display version command.)
(Optional) Fault cause Based on the obtained fault information, analyze possible
analysis causes. This item is optional.


fault)
Operations that have already CAUTION

been performed and relevant When finding a fault (except an emergency that needs to be handled
according to the pre-defined contingency method), follow the
results
guidance described in this document for troubleshooting in the first
place.
l If before fault reporting, certain troubleshooting
operations have already been performed for the fault
under the other guidance than that described in this
document, record all operations (including data
modification and maintenance operations) and provide
operation steps, time, and result.
Operation 1: xxx Result 1: xxx
Operation 2: xxx Result 2: xxx
l If a fault is troubleshot under the guidance described in

this document, attach the specified information here.
Database file and Run the save command to save the database file and
configuration file configuration file. Then, output these two files and attach them
here.

Maintenance Guide 4 Troubleshooting Services Transmitted Through a GE Port
4 Troubleshooting Services Transmitted

Through a GE Port
About This Chapter
This chapter describes how to troubleshoot common faults, such as Internet and Multicast service
faults, when the MA5612 uses a GE port for upstream transmission.
4.1 Troubleshooting LAN Internet Service

This chapter describes how to troubleshoot local area network (LAN) Internet service faults on
the MA5612.
4.2 Troubleshooting the Multicast Service
This chapter describes how to troubleshoot common multicast service faults.
4.3 Troubleshooting VoIP PSTN Service
This chapter describes how to troubleshoot common voice over IP (VoIP) public switched
telephone network (PSTN) service faults, such as when no tone is played after offhook, the busy
tone is played after offhook, the called party's phone does not ring, the calling line identification
presentation (CLIP) is abnormal, and there is only one-way audio or no audio during a call.
4.4 Troubleshooting Fax and Modem Services
This chapter describes how to troubleshoot common fax and modem services based on the H.
248 protocol.
4.5 H.248-Based ISDN PRA Service Troubleshooting
The primary rate adaptation (PRA) is used to access the ISDN users to the media gateway (MG)
through the ISDN primary rate interface (PRI) based on the H.248 protocol. This topic describes
how to troubleshoot the fault of the H.248-based ISDN PRA service.
4.6 SIP-Based ISDN PRA Service Fault Troubleshooting
The PRA is used to access the ISDN users to the MG through the ISDN PRI based on the SIP
protocol. This topic describes how to troubleshoot the fault of the SIP-based ISDN PRA service.


the MA5612.
4.1.1 Troubleshooting the Failure to Access the Internet

This section describes how to troubleshoot failures associated with local area network (LAN)
users accessing the Internet, for example, users fail to open Web pages.
Fault Location
Use the following guidelines to locate the fault.
Fault Location Location Analysis Possible Causes
User terminal A user fails to obtain the IP For the details about how to troubleshoot
address (excludes users this fault, see the following sections:
with a static IP address). l 4.1.2 Troubleshooting the Failure
to Obtain an IP Address by PPPoE
Dialup
l 4.1.3 Troubleshooting the Failure
to Obtain an IP Address in DHCP
Mode
The user obtains the IP l The user's PC is infected with viruses.

address successfully l Internet Explorer (IE) on the user's
(excludes users with a PC is faulty.
static IP address). The user
can access the Internet l The network interface card (NIC) in
after replacing the PC. the user's PC is faulty, or the PC is
slow to respond after running for a
long period.
Web site Certain Web sites fail to The Web site sever is faulty.
open.
No Web site can be The domain name server (DNS) fails to

opened. resolve the domain name.
DNS A Web site can be opened l The DNS is faulty and fails to resolve
by entering its IP address. the domain name.
l The communication between the
user's PC and the DNS is abnormal.
CAUTION
To facilitate fault report, save the results of the following steps.

Procedure
Step 1 Check the user's PC.
1. Check whether the user's PC can obtain the IP address.
NOTE
To view the IP address of the PC, do as follows:

a. Choose Start > Run from the Windows main menu. In the Run dialog box displayed, enter cmd and
press Enter.
b. In the command line interface (CLI) window displayed, run the ipconfig command to view the IP
address obtained by the PC.
l If the PC can obtain the IP address, go to Step 1.3.
l If the PC cannot obtain the IP address, do as follows:
– For PPPoE users, see 4.1.2 Troubleshooting the Failure to Obtain an IP Address
by PPPoE Dialup. Then, go to Step 1.2
– For DHCP users, see 4.1.3 Troubleshooting the Failure to Obtain an IP Address
in DHCP Mode. Then, go to Step 1.2
2. Check whether the user can access the Internet.
l If the user can access the Internet successfully, go to Step 5.
l If the user cannot access the Internet, go to Step 1.3.
3. Replace the user's PC with a test PC that can access the Internet in the same mode as the
user's PC. Then, check whether the user can access the Internet.
l If the user can access the Internet, the fault is on the user's PC. Check whether the user's
PC is infected with viruses, the NIC or IE of the user's PC is faulty, or the PC is slow
to respond after running for a long period. Then, go to Step 5.
l If the user cannot access the Internet, go to Step 2.
Step 2 Check whether the user can access the Internet by going to various Web sites through the Web
server.
l If the user can access certain Web sites, the fault is on the Web site itself. Go to Step 5.
l If the user cannot access any Web sites, go to Step 3.
Step 3 Check the DNS.

1. Enter the IP address of an existing Web site in the address bar of IE (format: http://
192.168.0.2) and check whether the Web site opens.
l If the Web site opens, the fault is on the DNS and the DNS cannot resolve the domain
name. Go to Step 3.2.
l If the Web site does not open, go to Step 4.
2. Check whether the PC can ping the IP address of the DNS.
NOTE
To view the DNS IP address of the PC, do as follows:

press Enter.
b. In the CLI window displayed, run the ipconfig/all command to view the DNS IP address obtained by
the PC.
l If the PC can ping the IP address of the DNS, the link between the PC and the DNS is
normal and the DNS is faulty. Go to Step 3.3.

l If the PC cannot ping the IP address of the DNS, go to Step 4.

3. Rectify the fault on the DNS. Then, check whether the user can access the Internet.
l If the user can access the Internet, go to Step 5.
Step 4 Record the results of the preceding steps in a fault report (see Fault Report Form), fill out the
entire form, and then submit it to Huawei for technical support (see Contacting Huawei for
Assistance).
Step 5 End.
----End
4.1.2 Troubleshooting the Failure to Obtain an IP Address by PPPoE

Dialup
This section describes how to troubleshoot a failure to obtain an IP address by point-to-point
over Ethernet (PPPoE) dialup mode. When a user accessing the Internet in LAN mode fails to
obtain an IP address by PPPoE dialup, refer to the following guidelines to address the issue.
Fault Location
Perform a 8.9 PPPoE Dialup Emulation Test to determine the fault scope first.
If the result of the PPPoE dialup emulation test is "success," the link between the MA5612 and
the upper layer broadband remote access server (BRAS) is normal. Therefore, the fault must be
located on the link between the MA5612 and the user terminal. Use the following guidelines to
locate the fault more accurately.
User terminal If the fault does not recur when the l The dialup software is not
user's PC is replaced, the fault is properly installed on the PC.
on the PC. l The network interface card
(NIC) in the PC is faulty.
If the fault does not recur when the The user's terminal is faulty.
user's terminal is replaced, the
fault is on the user's terminal.
Link between The link state of the user port is A fault has occurred on the
user terminal and offline. subscriber line.
MA5612 l The quality of the subscriber line
is deteriorated.
l The subscriber line is old.
l The subscriber line connectors
are loose.
The user port is deactivated.
MA5612 The fault does not recur when the The user port is faulty.
line of the affected user is
connected to another user port.

The configured service port data is The configured service port data,
inconsistent with the data plan. such as the port ID, is incorrect.
If the result of the PPPoE dialup emulation test is not "success," the fault must be located on the
link between the MA5612 and the upper layer BRAS. Use the following guidelines to address
the fault more accurately.
MA5612 The configured service port data is The configured service port data,
inconsistent with the data plan. such as the VLAN ID, is incorrect.
The uplink port forwards no The uplink port on the MA5612 is

service stream to the upper layer not added to the upstream VLAN.
device.
The security configuration is l The Policy Information Transfer

incorrect. Protocol (PITP) configuration is
incorrect.
l The configured number of MAC
addresses that can be
dynamically learned by the
service port is incorrect.
l The configuration of the anti-
MAC address spoofing function
is incorrect.
l An access control list (ACL) that
does not allow transmission of
PPPoE packets is configured.
A MAC address drift occurs. A user or BRAS MAC address may

drift because of attacks or a loop on
the network.
Upper-layer The configuration of the upper The maximum transmission unit

device layer router is incorrect. (MTU) or the quality of service
(QoS) value configured on the upper
layer router is not correct.
The BRAS configuration is The user's account is restricted on

incorrect. the BRAS.
CAUTION

Procedure
Step 1 Perform a 8.9 PPPoE Dialup Emulation Test on the MA5612 for the affected user.
l If the result of the dialup emulation test is not "success," go to Step 4.
NOTE
If the result of the dialup emulation test is "timeout," "parameter negotiation failure," "user authentication
failure," "offline requested by the peer end," or other errors, the fault is located on the upper layer device
of the MA5612.
l If the result of the dialup emulation test is "success," go to Step 2.
Step 2 Check the user terminal.

1. Replace the user's PC with another and perform a dialup emulation test to check whether
the dialup can be successful.
l If the dialup is successful, the fault is related to a problem on the user's PC. Check
whether the PPPoE software is installed on the PC incorrectly and whether the PC's NIC
is faulty or disabled, and address the problem. Then, go to Step 14.
l If the dialup fails, go to Step 2.2.
2. Replace the user's terminal and perform a dialup check. Then, check whether the dialup is
successful.
l If the dialup is successful, go to Step 14.
l If the dialup fails, go to Step 3.
Step 3 Check the interoperability between the user terminal and the MA5612.
1. In ETH mode, run the display port state portid command on the MA5612 to check whether
Active State of the Ethernet port is active.
l If Active State of the Ethernet port is active, go to Step 3.3.
l If Active State of the Ethernet port is not active, go to Step 3.2.
2. Run the undo shutdown portid command to activate the Ethernet port. Then, check
whether it is in the active state.
l If it is in the active state, go to Step 3.3.
l If it is not in the active state, go to Step 3.9.
3. Run the display port state portid command to check whether Link of the Ethernet port is
online.
l If Link of the Ethernet port is online, go to Step 3.4.
l If Link of the Ethernet port is not online, go to Step 3.5.
4. Perform a dialup check.
5. Check the quality of the physical line between the MA5612 and the user terminal to
determine whether the line is not connected properly or the line is old. Reconnect the line
properly or replace the old line as needed to ensure good line quality. Then, check whether
Link of the Ethernet port is online.


7. In ETH mode, run the display port state portid command to check whether the duplex
mode, rate, network cable adaptation mode of the Ethernet port are consistent with those
of the user terminal.
l If they are consistent, go to Step 3.9.
l If they are inconsistent, modify the parameter settings of the Ethernet port to ensure that
the parameter settings are consistent with those of the user terminal. Then, go to Step
3.8.
NOTE
In ETH mode, modify the parameter settings of the Ethernet port by using the following methods:
l Run the auto-neg command to enable or disable the auto-negotiation mode of the Ethernet port.
After the auto-negotiation mode of the Ethernet port is enabled, the Ethernet port automatically
negotiates the port rate and duplex mode with the interconnected port.
l Run the duplex command to configure the duplex mode of the Ethernet port to full duplex or half
duplex.
l Run the mdi command to configure the network cable adaptation mode of the Ethernet port.
l Run the speed command to configure the rate of the Ethernet port.
9. Replace the port and perform a dialup check. Then, check whether the dialup is successful.
l If the dialup is successful, the original user port is faulty. Change the user's port and
reconfigure the port data. Then, go to Step 14.
Step 4 Check whether the data configuration on the MA5612 is correct.
1. Run the display service-port port frameid/slotid/portid command to check whether the
data configuration of the user's service port, such as the VLAN ID and port ID, is correct.
l If the data configuration of the user's service port is correct, go to Step 4.3.
l If the data configuration of the user's service port is incorrect, go to Step 4.2.
NOTE
l Run the undo service-port command to delete the original service port.
l Run the service-port command to configure a new service port.
3. Run the display port vlan frameid/slotid/portid command to check whether the uplink port
was added to the upstream VLAN.
l If the uplink port was added to the upstream VLAN, go to Step 5.
l If the uplink port was not added to the upstream VLAN, run the port vlan command to
add the uplink port to the upstream VLAN, whose configuration must be the same as
the configuration on the upper layer device.Then, go to Step 4.4.

Step 5 Check the PITP configuration on the MA5612.

1. Run the display pitp config command to check whether the current global PITP function
is enabled.
l If the function is enabled, go to Step 5.2.
l If the function is not enabled, go to Step 6.
2. Run the display pitp config command to check the current PITP mode.
l If the current PITP mode is pmode, go to Step 5.5.
l If the current PITP mode is vmode, go to Step 5.3.
3. Run the display pitp vmode ether-type command to query the currently configured
Ethernet protocol type in the VBRAS packet and check whether the protocol type is the
same as the protocol type configured on the upper layer device.
l If the protocol types are the same, go to Step 6.
l If the protocol types are different, go to Step 5.4.
4. Run the pitp vmode ether-type command to change the current protocol type so it is the
same as the protocol type configured on the upper layer device, and then perform another
dialup check.
5. Run the display pitp permit-forwarding service-port service-portid command to check
whether the function that allows user-side PPPoE packets to carry vendor tags is enabled
on the service port of the affected user.
l If the function is enabled, go to Step 6.
l If the function is not enabled, run the pitp permit-forwarding service-port service-
portid enable command to enable it on the service port. Then, go to Step 5.6.
Step 6 Check the user port MAC address configuration on the MA5612.
1. Run the display mac-address port frameid/slotid/portid command to query the current
number of MAC addresses learned by the service port of the user.
2. Run the display mac-address max-mac-count service-port index command to query the
maximum number of MAC addresses that can be learned by the service port.
3. Check whether the current number of MAC addresses learned by the service port reaches
the maximum number of MAC addresses that can be learned by the service port.
l If the current number has reached the maximum number, run the mac-address max-
mac-count service-port index command to increase the maximum number of MAC
addresses that can be dynamically learned by the service port. Then, go to Step 7.
l If the maximum number has not been reached, go to Step 8.
Step 7 Perform a dialup check.


Step 8 Check whether a user's MAC address has drifted on the MA5612.
1. In global config mode, run the display location mac-addr command to check multiple
times (more than three times is recommended) whether a MAC address drift occurred on
the port that has learned the user's MAC address.
l If the MAC address drift has occurred, go to Step 8.2.
l If no MAC address drift has occurred, go to Step 9.
NOTE
l The mac-addr parameter in the command indicates the user's MAC address. For user terminal
dialup, the user's MAC address is the MAC address of the user terminal. For PC dialup, the user's
MAC address is the MAC address of the PC.
l The F/S/P parameter in the query result indicates the service port where the user's MAC address
has been learned. Generally, the port displayed in the query result should be the service port of
the user. If the displayed port is not the service port of the user, the user's MAC address has
drifted.
2. Check whether a loop has formed or whether there are user attacks on the port to which the
user's MAC address has drifted. If such a problem occurs, disconnect the loop or deactivate
the port where the user attacks are initiated. Then, perform another dialup check.
Step 9 Check whether a BRAS MAC address drift has occurred on the MA5612.
1. Run the display location mac-addr command to check multiple times (more than three
times is recommended) whether a MAC address drift occurred on the port that has learned
the BRAS MAC address.
NOTE
l The mac-addr parameter indicates the MAC address of the BRAS.

l The F/S/P parameter in the query result indicates the uplink port where the BRAS MAC address
has been learned. Generally, the port displayed in the query result should be the uplink port on
the MA5612 connected to the BRAS. If the displayed port is not the uplink port, the BRAS MAC
address drift has occurred.
Step 10 Check whether the security configuration on the MA5612 is correct.
1. Run the display security config command to check whether the anti-MAC address
spoofing function is enabled.
2. Run the display mac-address static command to check whether a static MAC address is
configured on the service port of the user.
NOTE
If a static MAC address and the anti-MAC address spoofing function are configured on a service port
at the same time, the service port user cannot access the Internet.

l If a static MAC address is configured on the service port, go to Step 10.3.

l If no static MAC address is configured on the service port, go to Step 11.
3. Run the security anti-macspoofing disable command to disable the anti-MAC address
spoofing function on the service port or run the undo mac-address static command to
delete the static MAC address configured on the port based on the service planning. Then,
perform another dialup check.
Step 11 Check whether an ACL restricting the transmission of PPPoE packets is configured on the
MA5612.
1. Run the display packet-filter port frameid/slotid/portid command to check whether an
ACL is configured on the user port.
l If an ACL is configured, go to Step 11.2.
l If no ACL is configured, go to Step 12.
2. Run the display acl command to check whether the ACL restricts the transmission of
PPPoE packets.
l If the ACL restricts the transmission of PPPoE packets, go to Step 11.3.
l If the ACL does not restrict the transmission of PPPoE packets, go to Step 12.
3. Change the ACL rule that restricts the transmission of PPPoE packets or delete the ACL
configuration on the port. Then, perform another dialup check.
Step 12 Check the data configuration on the upper layer device.
1. Check whether the MTU and QoS configurations on the upper layer device, such as the
upper layer router, are correct.
l If the configurations are correct, go to Step 12.3.
l If the configurations are incorrect, change the settings and ensure that the required data
configurations are correct. Then, go to Step 12.2.
3. Check whether the user data configuration on the upper layer BRAS is correct. Check, for
example, whether the user's account is restricted on the BRAS.
l If the data configuration on the BRAS is incorrect or the user's account is restricted,
change the settings on the BRAS. Then, go to Step 12.4.
l If the data configuration on the BRAS is correct and the user's account is not restricted,
go to Step 13.
Assistance).

Step 14 End.
----End
4.1.3 Troubleshooting the Failure to Obtain an IP Address in DHCP

Mode
This section describes how to troubleshoot a failure to obtain an IP address in Dynamic Host
Configuration Protocol (DHCP) mode. When a user accessing the Internet in LAN mode fails
to obtain an IP address by DHCP mode, refer to the following guidelines to address the issue.
Fault Location
If the fault occurs, determine the fault location by performing 8.11 DHCP Dialup Emulation
Test.
If the test result is "get IP successful", the link between the MA5612 and the upper-layer BRAS
is available, and the fault occurs on the link between the MA5612 and the user terminal. Use the
following guidelines to locate the fault.
User terminal If the fault does not recur when the The network interface card (NIC) in
user's PC is replaced, the fault is the PC is faulty or disabled.
on the PC.
Link between the The link state of the user port is A fault has occurred on the
the MA5612 l The quality of the subscriber line
is deteriorated.
are loose.
MA5612 The user port is not activated. The user port is deactivated.
The fault does not recur when the The user port is faulty.
line of the affected user is moved
to another user port.
If the test result is not "get IP successful", the link between the MA5612 and the upper-layer
BRAS is unavailable. Use the following guidelines to locate the fault on the link.

inconsistent with the data plan. such as the uplink VLAN ID, is
incorrect.
The uplink port does not forward The uplink port has not been added
service streams to the upper-layer to the uplink VLAN.
device.
A MAC address flapping occurs. A user or BRAS MAC address may

flap because of attacks or a loop on
the network.
The security configuration is l The static IP binding function is

incorrect. enabled.
l The MAC address filtering table
is incorrectly configured and the
affected user is configured in the
table.
Link between the The MA5612 cannot ping the l The DHCP configuration on the
MA5612 and DHCP server. MA5612 is inconsistent with that
DHCP server on the DHCP server.
l The link between the MA5612
and the DHCP server is faulty.
DHCP server The MA5612 can obtain an IP l The IP address resources of the
address when the DHCP server is DHCP server are exhausted.
replaced. l The DHCP server is faulty.
Upper-layer The configuration of the upper- The maximum transmission unit

layer router is incorrect.

CAUTION
Procedure
Step 1 Perform 8.11 DHCP Dialup Emulation Test for the affected user on the MA5612.
l If the test result is not "get IP successful", go to Step 4.

NOTE
If the test result is "send packet fail", "DHCP server not found", "DHCP server refuse request", or "get IP
overtime", the upper-layer device of the MA5612 is faulty.
l If the test result is "get IP successful", go to Step 2.
1. Replace the user's PC with another one and then perform a dialup test to check whether the
new PC can obtain an IP address.
l If the new PC can obtain an IP address, the fault is on the user's PC. Check whether the
PC's NIC is faulty or disabled, and address the problem. Then, go to Step 10.
l If the new PC fails to obtain an IP address, go to Step 2.2.
2. Replace the user terminal with another one and then check whether the new user terminal
can obtain an IP address.
l If the new user terminal can obtain an IP address, go to Step 10.
l If the new user terminal fails to obtain an IP address, go to Step 3.
online.
4. Check whether the PC can obtain an IP address.
l If the PC can obtain an IP address, go to Step 10.
l If the PC fails to obtain an IP address, go to Step 4.
mode, rate, and network cable adaptation mode of the Ethernet port are consistent with
those of the user terminal.

l If they are inconsistent, modify the settings of the Ethernet port to ensure that the settings
are consistent with those of the user terminal. Then, go to Step 3.8.
NOTE
duplex.
9. Replace the user port and then check whether the PC can obtain an IP address.
l If the PC can obtain an IP address, the original user port is faulty. Change the user's port
and reconfigure the port data. Then, go to Step 10.

1. Run the display service-port port frameid/slotid/portid command to check whether such
data configurations of the user's service port as the VLAN ID and port ID are correct.
l If the data configuration is correct, go to Step 4.3.
l If the data configuration is incorrect, refer to the following notes to change the
configuration data. Then, go to Step 4.2.
NOTE
l If the PC fails to obtain an IP address, go to Step 4.3.
the configuration on the upper layer device. Then, go to Step 4.4.

l If a MAC address drift occurred on the port, go to Step 5.2.

l If a MAC address drift did not occur on the port, go to Step 6.
NOTE
l The mac-addr parameter in the command indicates the user's MAC address. For modem dialup,
the user's MAC address is the MAC address of the modem. For PC dialup, the user's MAC address
is the MAC address of the PC.
l The F/S/P parameter in the query result indicates the service port that learned the user's MAC
address. Generally, the port displayed in the query result should be the service port of the user.
If the displayed port is not the service port of the user, the user's MAC address has drifted.
user's MAC address has drifted. If such a problem occurs, disconnect the loop or deactive
port is initiating the attacks. Then, perform another dialup check and check whether the PC
Step 6 Check the security configuration on the MA5612.

1. Run the display security mac-filter command to check whether the user's MAC address
is contained in the filtering list.
l If the user's MAC address is contained in the filtering list, run the undo security mac-
filter command to delete the user's MAC address from the filtering list. Then, go to
Step 6.2.
l If the user's MAC address is not contained in the filtering list, go to Step 7.
Step 7 Check the interoperability between the DHCP server and the MA5612.
1. Run the display dhcp option82 config command to check whether the DHCP Option82
configuration on the MA5612 is consistent with that on the DHCP server.
l If the configurations are consistent, go to Step 7.3.
l If the configurations are inconsistent, change the configuration on one side as needed
to ensure that they are consistent. Then, go to Step 7.2.
3. Check whether the DHCP server is faulty and the IP address of the DHCP server is exhaust.
Ensure the DHCP server work in the normal state. Check whether the PC can obtain an IP
address.

1. Check whether the data configuration on the upper layer device is correct, for example,
whether the MTU and QoS configurations on the upper layer router are correct.

go to Step 9.
Assistance).
Step 10 End.
----End
4.1.4 Troubleshooting Low Internet Access Rate

Low Internet access rate indicates that the attainable Internet access rates for users are lower
than the rates provided them. This section describes how to troubleshoot low access rates when
local area network (LAN) users access the Internet.
Fault Location
User terminal The fault does not recur when the l The PC's network interface card
user's PC is replaced. (NIC) is faulty.
l The user's PC is infected with
viruses.
l The computer does not meet the
minimum configuration
requirements.
The fault does not recur when the The user terminal is faulty.
user terminal is replaced.
Link between Packet loss on the subscriber line l The quality of the subscriber line
user terminal and is severe. is deteriorated.
MA5612 l The subscriber line is old.
are loose.

MA5612 The Internet access rate on a single l The rate restriction configuration
port is low. for the user is incorrect.
l Certain users' Internet access
rates are restricted on the BRAS.
The Internet access rates on all l A user's MAC address has drifted
MA5612 ports are low. between MA5612 ports.
l The upstream bandwidth on the
MA5612 is insufficient.
Upper layer Only certain users' Internet access Certain users' Internet access rates
BRAS rates are low; the services of other are restricted on the BRAS.
users on the BRAS are normal.
CAUTION
Procedure
Step 1 Determine the fault range when identifying the fault causes.
l If the Internet access rates of only certain users on the MA5612 are low whereas the rates of
other users are normal, go to Step 2.
l If the Internet access rates of all users on the MA5612 are low, go to Step 4.
1. Replace the user's PC and test whether the Internet access rate is normal.
l If the Internet access rate is normal, the fault is on the PC. Check whether the NIC in
the user's PC is faulty, the PC is infected with viruses, the PC is slow to respond after
running for a long time, or the PC's configuration is low. Then, go to Step 10.
l If the Internet access rate is low, go to Step 2.2.
2. Replace the user terminal, and then check whether the Internet access rate is normal.
l If the Internet access rate is normal, go to Step 10.
l If the Internet access rate is low, go to Step 3.
Step 3 Check whether the line between the MA5612 and the user terminal is normal.
1. Check whether cyclic redundancy code (CRC) loss occurs on the subscriber line.
l If CRC loss occurs on the subscriber line, go to Step 3.2.
l If CRC loss does not occur on the subscriber line, go to Step 4.

NOTE
Query the statistics of the faulty port multiple times (recommended: 10 times) and then compare the
statistics to check whether packet loss occurs on the subscriber line. The query interval is 20s.
Run the display port statistics portid command on the MA5612 to query all the performance statistics of
the subscriber line after the subscriber line is initialized. Then, check whether the number of CRC error
frames increases. If it increases, packet loss is occurring on the subscriber line.
2. Check whether the physical line between the MA5612 and the user terminal is connected
properly or whether the line is old. Reconnect the line properly or replace the line as needed.
Then, check whether the Internet access is normal.
l If the Internet access is normal, go to Step 10.
l If the Internet access is low, go to Step 4.
Step 4 Check whether unknown traffic is occupying the bandwidth on the MA5612.
1. Ensure that the user is not accessing the Internet. Run the display port statistics portid
command to query the statistics of the Ethernet port multiple times (recommended: five
times). The query interval is 20s.
l If the upstream or downstream traffic increases rapidly, unknown traffic is occupying
the bandwidth. Go to Step 4.2.
l If the upstream or downstream traffic does not increase, go to Step 5.
NOTE
Normally, the query results should be similar when the user is not accessing the Internet.
l Number of transmitted octets: Indicates the current downstream traffic of the user.
l Number of received octets: Indicates the current upstream traffic of the user.
2. Use packet-capturing software, such as Ethereal, to capture packets on the user's PC,
confirm the known traffic source, and then eliminate the unknown traffic source. You can
eliminate the unknown traffic source by checking whether the PC sending the unknown
traffic is infected with viruses. Then, check whether the Internet access rate is restored.
l If the Internet access rate is restored, go to Step 10.
l If the Internet access is not restored, go to Step 5.
Step 5 Check the maximum rate configured for the user.

1. Run the display service-port command to query the indexes of the traffic profiles in the
receive and transmit directions configured for the service port.
2. Run the display traffic table ip command to query the corresponding traffic profile. Then,
check whether the committed information rate (CIR) reaches the bandwidth that the user
applied for.
l If the CIR is less than the bandwidth that the user applied for, the traffic profile bound
to the user is incorrect. Go to Step 5.3.
l If the CIR is equal to the bandwidth that the user applied for, go to Step 6.
3. Run the undo service-port command to delete the service port of the user. Then, run the
service-port command to reconfigure a service port for the user and bind the user to the
proper traffic profile. Check whether the Internet access rate is restored.
l If the Internet access rate is not restored, go to Step 6.

NOTE
When modifying the traffic profile, note the following:

l The service ports bound to the traffic profile take effect at the same time when the traffic profile is
modified.
l If the current traffic profile is bound to multiple service ports, run the traffic table ip command to
create the required traffic profile.
l If the current traffic profile is bound to one service port, run the traffic table ip modify command to
modify the traffic profile.
Step 6 Check whether the user's MAC address has drifted from one MA5612 port to another.
1. In global config mode, run the display location command to check multiple times
(recommended: three times) whether the user's MAC address has drifted away from the
port that originally learned it.
l If the user's MAC address has drifted, go to Step 6.2.
l If the user's MAC address has not drifted, go to Step 7.
NOTE
address. Normally, the port displayed in the query result is the service port of the user. If the
displayed port is not the service port of the user, the user's MAC address has drifted.
2. Check whether a loop has formed or there are user attacks on the port that the user's MAC
address has drifted to. If a loop has formed, disconnect it. If the port that the MAC address
has drifted to is being attacked, deactivate the port initiating the attacks. Then, check
whether the Internet access rate is restored.
Step 7 Check whether the upper layer BRAS is restricting the user rate.
l If the rate of the affected user is restricted on the BRAS, modify the BRAS configuration.
Then, go to Step 8.
l If the rate of the affected user is not restricted on the BRAS, go to Step 9.
Step 8 Check whether the service is restored.

l If service is normal, go to Step 10.
l If service is not normal, go to Step 9.
Assistance).
Step 10 End.
----End
4.1.5 Troubleshooting Frequent Interruptions in Internet Service

This section describes how to troubleshoot frequent interruptions in Internet service when local
area network (LAN) users are accessing the Internet.

Fault Location
User terminal The fault does not recur when the The user's PC is infected with
user's PC is replaced. viruses or the network interface card
(NIC) in the user's PC is faulty.
MA5612 l The subscriber line is old.
are loose.
l There is a strong source of
interference around the user.
MA5612 The Internet service on a single l The user port is faulty.

port is frequently interrupted. l The quality of the subscriber line
is deteriorated and the packet
loss on the subscriber line is
severe.
Internet services on all MA5612 l The MA5612 is faulty.

ports are frequently interrupted. l There is a strong source of
interference around the
MA5612.
l The MAC address has drifted
between MA5612 ports.
Upper layer Internet services of all users The BRAS MAC address has drifted
broadband connected to the BRAS are between MA5612 ports
remote access frequently interrupted.
server (BRAS)
CAUTION
Procedure
1. Replace the user's PC and then check whether Internet service is restored.

l If service is restored, the fault is on the user's PC. Check whether the NIC in the user's
PC is faulty or whether the user's PC is infected with viruses. Then, go to Step 7.
l If service is not restored, go to Step 1.2.
2. Replace the user terminal, and then check whether the service is restored.
l If the service is restored, go to Step 7.
l If the service is not restored, go to Step 2.
Step 2 Check whether the line between the MA5612 and the user terminal is normal.
NOTE
Run the display port statistics portid command on the MA5612 to query all the performance statistics of
the subscriber line after the subscriber line is initialized. Then, check whether the number of CRC error
frames increases. If it increases, packet loss is occurring on the subscriber line.
2. Check whether the physical line between the MA5612 and the user terminal is connected
Then, check whether the service is restored.
l If the service is not restored, go to Step 2.3.
3. Check whether there is a strong source of interference, such as a wireless base station or a
high-frequency switch power system, around the user.
l If there is a strong source of interference around the user, it may be the cause of the
fault. Contact the relevant department to handle it. Then, go to Step 7.
l If there is no strong source of interference around the user, go to Step 3.
Step 3 Change the port for the user and configure the necessary data on the MA5612. Then, check
whether the service is restored.
l If the service is restored, the user port is faulty. Change the user's MA5612 port and
reconfigure the data. Then, go to Step 7.
Step 4 Check whether the user's MAC address has drifted from one MA5612 port to another.
(recommended: three times) whether the user's MAC address on the port that learned it has
drifted.
NOTE

2. Check whether a loop has formed or whether there are user attacks on the port that the user's
MAC address has drifted to. If a loop has formed, disconnect it. If the port that the MAC
address has drifted to is being attacked, deactivate the port initiating the attacks. Then,
check whether the service is restored.
1. Run the display location mac-addr command to check multiple times (recommended: three
times) whether a BRAS MAC address has drifted away from the port that originally learned
it.
l If the BRAS MAC address has drifted, go to Step 5.2.
l If the BRAS MAC address has not drifted, go to Step 6.
NOTE
l The mac-addr parameter in the command indicates the BRAS's MAC address.
l The F/S/P parameter in the query result indicates the uplink port that learned the BRAS MAC
address. Normally, the port displayed in the query result is the uplink port on the MA5612
connected to the BRAS. If the displayed port is not the uplink port, the BRAS MAC address has
drifted.
Assistance).
Step 7 End.
----End
4.2 Troubleshooting the Multicast Service

This chapter describes how to troubleshoot common multicast service faults.
4.2.1 Failure to Go Online of a Multicast User

This topic describes how to troubleshoot the fault when a multicast user fails to order any
programs because the multicast user fails to go online (the queried user status is offline or
block on the MA5612). When such a fault occurs, locate the fault according to the following
procedure.
Location Method
When a multicast user is blocked, run the undo igmp user block command to unblock the user.
When a multicast user is offline, enable the MA5612 debugging function and locate the fault
according to whether the MA5612 receives the report packet from the multicast user.

l If the MA5612 receives the report packet, the multicast link is normal but the MA5612
fails to create a corresponding multicast entry. This is generally caused by incorrect
multicast configurations on the MA5612.
l If the MA5612 does not receive the report packet, the multicast link fails. This is mainly
caused by incorrect MA5612 software configurations, faulty physical link between the
MA5612 and the terminal, and hardware faults of terminals.
Table 4-1 describes fault symptoms and possible causes when a multicast user is offline.
Table 4-1 Fault symptoms and possible causes when a multicast user is offline
Fault Judgment Criterion Possible Cause
Scope
MA5612 The MA5612 receives the l The program ordered is not in the MVLAN to
report packet. which the multicast user belongs.
l No upstream port is configured in the MVLAN
to which the multicast user belongs.
l The multicast user does not have the
permission to watch the program.
l The maximum multicast bandwidth of the user
is lower than the required bandwidth of the
ordered program.
permission to order certain types of programs
(such as HDTV).
The MA5612 does not The IGMP function of the MVLAN is disabled.
receive the report packet
and all users in the
MVLAN fail to go online.
MA5612 The MA5612 does not l The hardware of the port on the MA5612 is
to the receive the report packet faulty.
terminal and a single user fails to go l The set-top box (STB) is faulty.
online.
NOTE
Faults can be located according to specific scenarios because fault scopes are different for deployment and
routine operation and maintenance.
l If the fault occurs during deployment, check initial configurations of the hardware and the software.
l If a multicast user fails to go online during O&M, check only the hardware because the software
configuration of a user is generally not modified in this scenario. Hence, if the status of a user changes
from normal to abnormal, it is generally caused by hardware failures. If a multicast link failure occurs
after a new user is added or an existing user is modified, check whether the configuration is correct.
CAUTION

Procedure
Step 1 On the MA5612, run the display igmp user user-index command to query the multicast user
status (State).
l If State is block, the multicast user is blocked. In this case, run the undo igmp user block
command to unblock the user. Then, go to Step 2.
l If State is offline, go to Step 3.
NOTE
If you need to block a multicast user from watching programs temporarily without deleting the user (for
example, when the user owes charges), run the igmp user block command to block the user. When the
user is blocked, the MA5612 forces the user to go offline from the current program. In addition, the
MA5612 rejects the user from ordering programs until the user is unblocked.
Step 2 Order a program and check whether the user can go online.
l If the user can go online, go to Step 9.
l If the user fails to go online, go to Step 3.
Step 3 Enable the MA5612 debugging function and collect information as follows:
1. Enable the function of multicast user monitoring.
huawei(config)#terminal monitor
huawei(config)#terminal debugging
huawei(config)#debugging igmp user
2. Order the program again. Then, go to Step 4.

NOTE
After the preceding steps are performed, run the following commands to disable the debugging function.
huawei(config)#undo debugging igmp
huawei(config)#undo terminal debugging
huawei(config)#undo terminal monitor
Step 4 Locate the fault according to the receiving condition of the report packet and the fault scope.
l If the MA5612 displays a prompt message of the program, the MA5612 receives the report
packet. In this case, go to Step 5.1.
l If the MA5612 does not display a prompt message of the program, the MA5612 does not
receive the report packet. In this case, locate the fault according to the fault scope.
– If all users in the MVLAN fail to go online, go to Step 5.2.
– If a single user or some users in the MVLAN fail to go online, go to Step 6.
Step 5 Check multicast configurations of the MA5612.
1. If the MA5612 receives the report packet, find the possible cause according to judgment
criteria described in Table 4-2 and then troubleshoot the fault. Then, go to Step 5.3 to check
whether the fault is rectified.

Table 4-2 Incorrect multicast configurations of the MA5612

Possibl Judgment Criterion Troubleshooting Method
e
Cause
The If one of the following symptoms Choose one of the following

maximu occurs, the fault is because the troubleshooting methods
m maximum multicast bandwidth of the according to the purchased service
multica user is lower than the required type:
st bandwidth of the ordered program. l Notify the user of ordering
bandwi l The MA5612 receives the report another program (whose
dth of packet and displays "the user fails to bandwidth is lower than the
the user pass bandwidth CAC". maximum bandwidth of the
is lower user) because the bandwidth is
than the l The maximum bandwidth of the
user is lower than the bandwidth of insufficient and the program
required cannot be watched.
bandwi the ordered program by running the
dth of display igmp user user-index l Increase the user bandwidth
the command to query the maximum and notify the user of ordering
ordered bandwidth (User MaxBandWidth) the program again.
progra of the user and running the display NOTE
m. igmp program name command to Run the igmp user modify user-
query the bandwidth (Bandwidth) index max-bandwidth command to
of the ordered program. modify the maximum bandwidth of
the user to ensure that it is higher than
NOTE the program bandwidth.
If User MaxBandWidth is no-limit, the
multicast bandwidth of the user is not
limited.


e
Cause

multica occurs, the fault is because the multicast troubleshooting methods
st user user does not have the permission to according to the purchased service
does not order certain types of programs. type:
have the l The MA5612 receives the report l Notify the user of ordering
permiss packet and displays "the number of another program (the maximum
ion to the grade program that the user is number of the programs at this
order allowed to watch has reached level must not be 0) because the
certain maximum". user does not have the
types of permission to watch the ordered
progra l The maximum number (watch
limit) of programs at a level that can program.
ms
(such as be watched by the user is 0 by l Set the permission for ordering
HDTV) running the display igmp user the programs at this level for the
. extended-attributes user-index user so that the user can order
command on the MA5612. the program.
NOTE NOTE
l If the maximum number of the You can run the igmp user watch-
programs at a certain level is 0, the user limit command to set the number of
cannot order any programs at this level. programs at each level that a user can
That is, the user's permission to the watch.
programs of the corresponding type is
restricted. For example, if HDTV
watch limit is 0, the user cannot watch
HDTV programs.
l If watch limit is no-limit, the
maximum number of the programs at
this level that a user can watch is not
limited, but the total number of
programs that can be concurrently
watched is limited.


e
Cause

does not watch the program. type:
have the l The MA5612 receives the report l If the user can watch all
permiss packet and displays "the user has no programs without
ion to right". authentication, perform the
watch following two operations:
the l Run the display igmp user 100
command to query the right profile a. In the BTV mode, run the
bound to the multicast user (assume igmp user modify 100 no-
that the service port of the multicast auth command to modify
user is 100). the authentication mode of
– If Bind profiles is 0, the user is the user to "no
not bound to a right profile and authentication" (assume
the user cannot order any that the multicast user index
programs. is 100).
– If Bind profiles is equal to or b. Order the program again.

larger than 1, the user can watch l If the user can watch certain
only the program to which the programs with authentication,
user has the watch permission. In notify the user of ordering
this case, perform operations for another program because the
further check. In the queried user has no permission to watch
result, find the index (assume the program. The permission to
that the index is 1) and name of watch the program is watch or
the program right profile bound preview.
to the user and run the display
igmp profile profile-index 1
command to query the user
permission for ordering the
program.
– If the permission of a
program is forbidden or
idle, the user does not have
the permission to order the
program.
program is watch or
preview, the user can order
the program. Therefore, this
is not the cause for this fault.


e
Cause
progra NOTE NOTE

m. A multicast user can be bound to multiple To set permissions of the user for
right profiles. If these right profiles are ordering some programs, run the igmp
configured with different permissions to a user bind-profile 100 profile-index-
same program, the permission with the list 1 command to bind a correct right
highest priority prevails. By default, the profile to the multicast user (assume
priority of the program permissions is that the multicast user index is 100 and
forbidden > preview > watch > idle. You the right profile index is 1).
can run the igmp right-priority command
to set the priority.


e
Cause
The If the following symptoms occur, the Choose one of the following
progra fault is because the program ordered is troubleshooting methods
m not in the MVLAN to which the according to the purchased service
ordered multicast user belongs. type:
is not in l The MA5612 receives the report l Notify the user of ordering
the packet and displays "match program another program because the
MVLA fail". user has no permission to watch
N to the program (the program is
which l The program ordered is not in the
MVLAN to which the multicast included in the MVLAN to
the which the multicast user
multica belongs).
st user
l Perform the following steps to
add the program to the
MVLAN to which the multicast
user belongs and then order the
program again.
a. Run the display igmp
config vlan command to
query Program match
mode of the program.
– If Program match
mode is enable, the
program is a static
program, which is
manually added.
mode is disable, the
program is a dynamic
program, which is
automatically generated
upon the ordering.
b. Add programs to the
MVLAN.
– To add a static program
to an MVLAN, run the
igmp program add
command.
– To add a dynamic
program to an MVLAN,
run the igmp match
group command to set
the IP address range of
program groups that can
be generated


e
Cause
belongs user belongs by running the display dynamically in the

. igmp program vlan command. MVLAN, and ensure
that the IP address range
includes the IP address
of the ordered program.
No If the following symptoms occur, the Add the upstream port to the
upstrea fault is because no upstream port is MVLAN to which the multicast
m port configured in the MVLAN to which the user belongs and notify the user of
is multicast user belongs. ordering the program again.
configu l The MA5612 receives the report NOTE
red in packet and displays "match program In the MVLAN mode, run the igmp
the fail". uplink-port command to set the
MVLA upstream port as the upstream port of
N to l No upstream port maps the the MVLAN. This allows the
MVLAN to which the multicast upstream port to forward the multicast
which packets of this MVLAN.
the user belongs by running the display
multica igmp uplink-port all command to
st user query the multicast upstream port.
belongs
.
2. If the MA5612 does not receive the report packet and all users in the MVLAN fail to go
online, the IGMP function may be disabled in the MVLAN. In this case, run the display
igmp config vlan command in the MVLAN mode to query IGMP mode of the MVLAN.
l If IGMP mode is off, the IGMP function is disabled in the MVLAN. In this case, run
the igmp mode command in the MVLAN mode to set IGMP mode to proxy or
snooping accordingly. Order a program and then, go to Step 5.3.
l If IGMP mode is proxy or snooping, the IGMP function is enabled in the MVLAN
and it is not the cause of the fault. Then, go to Step 6.
NOTE
If the terminal used by the user does not support multicast management, enable the IGMP function
on the MA5612. Otherwise, the multicast service cannot be provisioned to the user.
3. Check whether the user can go online.
Step 6 If the MA5612 does not receive the report packet and the other users in the MVLAN can go
online, find the possible cause according to judgment criteria described in Table 4-3 and then
troubleshoot the fault. Then, go to Step 7 to check whether the fault is rectified.

Table 4-3 Line and terminal faults

e Cause
The The user can go online after migrating Migrate configurations of the faulty
hardwar configurations of the faulty port to a port to a functional one or replace the
e of the functional one and ordering the program. board to which the faulty port
port on belongs.
the
MA561
2 is
faulty.
The STB The user can go online after resetting the Reset the STB or use a functional
is faulty. STB or using a functional STB and STB.
ordering the program.
Assistance).
Step 9 End.
----End
4.2.2 Blank Screen After Ordering a Program

Blank screen after program ordering is a fault that a user cannot watch the program after the user
orders a program. When blank screen occurs after a user orders a program, locate the fault
according to the following procedure.
Location Method
When blank screen occurs after a user orders a program, Table 4-4 shows possible causes of the
fault in different scopes.
Table 4-4 Possible causes of the fault in different scopes

Fault Scope Possible Cause
User terminal The set-top box (STB), and TV cable are faulty.

MA5612 On the MA5612, check whether the multicast user is online and then
troubleshoot the fault according to the following symptoms:
l If the multicast user is offline or is blocked, troubleshoot the fault
by referring to 4.2.1 Failure to Go Online of a Multicast User.
l If the multicast user goes online but blank screen occurs in the
multicast program, the fault is generally caused by incorrect
multicast configurations on the MA5612. In this case, enable the
MA5612 debugging function and then locate the fault according
to the debugging information displayed on the CLI. Possible
causes:
– The remaining multicast bandwidth of the user is lower than
the required bandwidth of the ordered program.
– The number of programs watched by the multicast user reaches
the upper limit so that the user cannot order a new program.
– The multicast user does not have the permission to watch the
program.
– The program ordered is not in the MVLAN to which the
multicast user belongs.
– The multicast user does not have the permission to order certain
types of programs (such as HDTV).
– The number of programs at a level watched by the multicast
user reaches the upper limit so that the user cannot order a new
program at this level.
– The rate configured in the traffic profile bound to the traffic
stream is far lower than the bandwidth of the multicast program.
– There are too many prejoined static programs, occupying too
many bandwidths.
Upper-layer l The program is not configured on the multicast server.

network and devices l The time to live (TTL) value set for the multicast stream of the
(including the multicast server is very small.
multicast router and
multicast server) of l The network communication fails. The network communication
the MA5612 failure occurs on the line between the MA5612 and multicast
router, and between the multicast router and multicast server.
CAUTION
Procedure
Step 1 Order a program again and perform the following steps to determine the location where program
traffic interruption occurs.

1. On the MA5612, run the display multicast flow-statistic ip 224.1.1.1 vlan 3 command to
query the traffic statistics of the ordered program on the upstream port (assume that the
MVLAN ID is 3 and the IP address of the multicast program is 224.1.1.1). If the queried
program traffic is not 0, the program traffic reaches the MA5612 upstream port.
2. Run the display statistics service-port command two or three times to query the traffic
statistics of the service port to which the multicast user belongs. If values of Number of
downstream packets different greatly, the program traffic reaches the MA5612 user port.
NOTE
The following prerequisites must be met before you run the display statistics service-port command
to query the traffic statistics so as to prevent the queried results from being affected by other services.
l The multicast user is not watching other programs.
l The service port does no carry other heavy-traffic services. For example, the service of
downloading files from the Internet.
3. According to the preceding queried results, determine the fault scope by referring to Table
4-5 and perform operations accordingly.
NOTE
When multiple NEs need to be checked, generally locate the fault from lower-layer devices to upper-
layer devices, that is, in the sequence of user terminal -> MA5612 -> multicast router -> multicast
server from segment to segment.
Table 4-5 Fault scope and troubleshooting method
Fault Scope Judgment Criterion Troubleshooting Method
User terminal If the following symptoms Check the user terminal

occur, the fault is because the following Step 2.
user terminal is faulty.
l Multicast streams reach the
user port of the MA5612.
l Other users of the MA5612
can watch the program.
User terminal and Multicast streams reach the a. Check the user terminal
MA5612 upstream port of the MA5612 following Step 2.
but do not reach the user port. b. Check the MA5612
following Step 3.
User terminal, Multicast streams do not reach a. Check the user terminal
MA5612, and the upstream port of the following Step 2.
upper-layer MA5612. b. Check the MA5612
network and following Step 3.
devices of the
MA5612 c. Check the upper-layer
network and devices
following Step 4.

1. Verify that the TV cable is properly connected to the STB.

2. Check the indicator status of the STB. If the indicator of the STB Ethernet port blinks
quickly, the STB decoding may be incorrect. Reset the STB or use a functional STB.
3. Order a program to check whether the user can watch the program successfully.
l If the user can watch the program successfully, go to Step 6.
l If the user cannot watch the program, go to Step 2.4.
4. Check whether all NEs are checked according to Table 4-5.
l If all NEs are checked, go to Step 5.
l If not all NEs are checked, check the remaining NEs according to Table 4-5.
Step 3 Check the MA5612.
1. Run the display igmp user user-index command to query the multicast user status
(State).
l If State is online, go to Step 3.2.
l If State is offline or block, perform operations by referring to 4.2.1 Failure to Go
Online of a Multicast User. Then, go to Step 6.
2. Enable the MA5612 debugging function and collect information as follows:
a. Enable the function of multicast user monitoring.
b. Order the program again. Then, go to Step 3.3.

NOTE
After the preceding steps are performed, run the following commands to disable the debugging
function.
3. Find the possible cause according to judgment criteria described in Table 4-6 and then
troubleshoot the fault. Then, go to Step 3.4 to check whether the fault is rectified.

Table 4-6 Troubleshooting method of incorrect multicast configurations on the MA5612

e
Cause

bandwi l The MA5612 receives the report another program because the
dth of packet and displays "the user fails to remaining bandwidth is
the user pass bandwidth CAC". insufficient and the program
is lower cannot be ordered.
than the l On the MA5612, run the display
required igmp user user-index command to l Increase the user bandwidth
bandwi query the maximum bandwidth and notify the user of ordering
dth of (User MaxBandWidth) and used the program again.
the bandwidth (Used bandwidth) of NOTE
ordered the user and run the display igmp l You can run the igmp user
progra program name command to query modify user-index max-
m. the bandwidth (Bandwidth) of the bandwidth command to modify
ordered program. The remaining the maximum bandwidth of the
bandwidth (the maximum user.
bandwidth - the used bandwidth) is l When multicast bandwidth
lower than the bandwidth of the management is disabled
ordered program. (multicast CAC disabled), the
system does not guarantee the
NOTE bandwidth of the program ordered
If User MaxBandWidth is no-limit, the by the user.
limited. l The downstream rate of a line is
limited. Therefore, multicast
packets will be lost if the
bandwidth of the downstream
multicast streams is higher than
the maximum rate of the line.
Though multicast packets are lost,
the user can watch the program but
pixelation or delay occurs. Or
even blank screen occurs if a large
number of multicast packets are
lost.


e
Cause

maximu occurs, the fault is because the available troubleshooting methods
m programs reach the preset maximum according to the purchased service
number value. type:
of l The MA5612 receives the report l Notify the user of closing some
progra packet and displays "the number of programs and then ordering the
ms program that the user is allowed to program again because the
(Availa watch has reached maximum". available programs reach the
ble preset maximum value and no
progra l The number of programs that users
are watching is equal to the more programs can be ordered.
ms) that
users available programs by running the l Increase the available programs
can display igmp user user-index and notify the user of ordering
watch at command. the program again.
the NOTE NOTE
same If Available programs is no-limit, the user You can run the igmp user modify
can watch 32 programs concurrently. user-index max-program command
time
to modify the available programs.
reach
the
preset
maximu
m value.


e
Cause

have the l The MA5612 receives the report l If the user can watch all
permiss packet and displays "the user has no programs without
ion to right". authentication, perform the
watch following two operations:
the l Run the display igmp user 100
command to query the right profile a. Run the igmp user modify
bound to the multicast user (assume 100 no-auth command in
that the service port of the multicast the BTV mode to modify the
user is 100). authentication mode of the
– If Bind profiles is 0, the user is user to "no
not bound to a right profile and authentication" (assume
the user cannot order any that the multicast user index
programs. is 100).
– If Bind profiles is equal to or b. Order the program again.

larger than 1, the user can watch l If the user can watch certain
only the program to which the programs with authentication,
user has the watch permission. In notify the user of ordering
this case, perform operations for another program because the
further check. In the queried user has no permission to watch
result, find the index (assume the program. The permission to
that the index is 1) and name of watch the program is watch or
the program right profile bound preview.
to the user and run the display
program.
program.
program is watch or


e
Cause
progra NOTE NOTE



e
Cause
is not in l The MA5612 receives the report l Notify the user of ordering
the packet and displays "match program another program because the
MVLA fail". user has no permission to watch
N to the program (the program is
which l The program ordered is not in the
MVLAN to which the multicast included in the MVLAN to
multica belongs).
st user
program again.
query program match
mode of the MVLAN to
which the user belongs.
mode is enable, the
program is a static
program, which is
manually added.
program, which is
upon the ordering.
MVLAN.
igmp program add
command.
run the igmp match


e
Cause
belongs user belongs by running the display be generated

. igmp program vlan command. dynamically in the
MVLAN, and ensure

have the l The MA5612 receives the report l Notify the user of ordering
permiss packet and displays "the number of another program (the maximum
ion to the grade program that the user is number of the programs at this
ms
command. the program.
NOTE NOTE
If the maximum number of the programs at You can run the igmp user watch-
a certain level is 0, the user cannot order any limit command to set the number of
programs at this level. That is, the user's programs at each level that a user can
permission to the programs of the watch.
corresponding type is restricted. For
example, if HDTV watch limit is 0, the
user cannot watch HDTV programs.


e
Cause

number occurs, the fault is because the number troubleshooting methods
of of programs at a level watched by the according to the purchased service
progra multicast user reaches the upper limit. type:
ms at a l The MA5612 receives the report l Notify the user of ordering
level packet and displays "the number of another program because the
watched the grade program that the user is ordered program is not
by the allowed to watch has reached purchased.
multica maximum".
st user l Increase the maximum number
reaches l The number of programs that users of programs at a level watched
the are watching is equal to the by the multicast user and notify
upper maximum number (watch limit) of the user of ordering the
limit so programs at a level that can be program again.
that the watched by the user by running the NOTE
user display igmp user extended- You can run the igmp user watch-
cannot attributes user-index command. limit command to set the number of
programs at each level that a user can
order a NOTE
watch.
new If watch limit is no-limit, the maximum
number of the programs at this level that a
progra
user can watch is not limited, but the total
m at this number of programs that can be
level. concurrently watched is limited.


e
Cause
The rate Run the display service-port Bind a traffic profile to multicast
configu command to query the index of the Rx streams and order the program
red in traffic and then run the display traffic again.
the table ip command to query the PIR of l If a correct traffic profile is in
traffic the traffic profile. The PIR is far smaller the system, run the service-
profile than the bandwidth of the ordered port 100 outbound traffic-
bound program. table index 6 command to bind
to the NOTE the traffic profile (assume that
traffic If the PIR is smaller than the bandwidth of the index of the multicast traffic
stream the ordered program, the multicast packets
streams is 100 and the index of
is far are lost and pixelation occurs. If the PIR is
very small, the blank screen may occur the traffic profile is 6) to the
lower multicast streams again.
because a large number of multicast packets
than the are lost.
bandwi l If the currently configured
If the service port carrying the multicast traffic profile does not meet the
dth of streams carries streams of other services,
the requirement, run the traffic
ensure that the total traffic of all services is
multica table ip command to add a new
smaller than or equal to the PIR. Otherwise,
st other services may occupy the majority of profile that meets the
progra traffic streams, which leads to insufficient requirement and then bind the
m. multicast bandwidth. As a result, the profile to the traffic streams.
pixelation occurs.
The common programs and high definition
(HD) programs require different
bandwidths, which are determined by the
program sources provided by the program
provider.
l Generally, the rate of a common
program is lower than 5 Mbit/s. In this
case, the default IP traffic profile 6 can
be used.
l An HD program has heavy traffic. For
example, the rate of an HD program is
higher than 12 Mbit/s. In this case, a
new traffic profile for limiting the rate
is required, or the default IP traffic
profile can be used.


e
Cause
There The prejoined static programs occupy Run the igmp program modify
are too too many bandwidths. command to modify Prejoin to
many You can obtain the bandwidth of disable and then order the program
prejoine prejoined static programs following the again.
d static steps below: NOTE
progra You can modify the attributes of all
ms, a. Run the display igmp program multicast programs in any MVLAN.
occupyi all command to query the prejoin When a program is being watched or
ng too attribute (Prejoin) of the program. previewed by a user, however, its
attributes cannot be modified.
many b. Calculate the bandwidth of
bandwi prejoined static programs (Prejoin
dths. is enable) according to the data
plan. For example, if 100 programs
are enabled with the prejoin
function and the bandwidth of each
program is 5 Mbit/s, the total
bandwidth of the prejoined static
programs is 500 Mbit/s.
4. Check whether the user can watch the program successfully.

Step 4 Check the upper-layer network and devices of the MA5612.

Table 4-7 Troubleshooting method of faulty upper-layer network and devices

e
Cause
The The program is not configured on the Add the program to the multicast
progra multicast server. server.
m is not TIP
configu If the user can watch the program, this is not
red on the cause.
the
multica
st
server.


e
Cause
The All users of the MA5612 fail to watch Increase the TTL value of multicast
time to all programs configured on to the packets of the multicast server.
live multicast server.
(TTL)
value
set for
the
multica
st
stream
of the
multica
st server
is very
small.
The Ping the multicast router and multicast Troubleshoot the fault on the line
upper- server from the MA5612 separately. It between the MA5612 and the
layer is found that the MA5612 fails to ping multicast router or the fault on the
network the multicast router and the multicast line between the MA5612 and the
commu server. multicast server.
nication TIP
of the If other users of the MA5612 can watch the
OLT program, the network between the
fails. MA5612 and the multicast server is normal.
2. Order a program again and then check whether the user can watch the program successfully.
Assistance).
Step 6 End.
----End
4.2.3 Pixelation in a Multicast Program

Pixelation in multicast programs is a fault that a user is online and orders a program but the
quality of the program is poor, such as pixelation. When pixelation occurs, locate the fault

Location Method
When pixelation occurs, Table 4-8 shows possible causes of the fault in different scopes.
User terminal to the l The rate configured in the traffic profile bound to the traffic stream
MA5612 is lower than the bandwidth of the multicast program.
l The QoS rate limitation on the port is excessively low.
l If pixelation occurs only in program switching, the maximum
bandwidth used by the user may be higher than the downstream
line rate and the fast leave function may not be enabled.
l The STB is faulty.
l The TV set is faulty.
Upper-layer l The multicast source is abnormal.

network and devices l The network quality is poor. The network communication failure
of the MA5612 occurs on the line between the MA5612 and multicast router, and
between the multicast router and multicast server.
CAUTION
Procedure
Step 1 Order a program again and perform the following steps to determine the location at which
multicast packets are lost.
1. On the MA5612, run the display multicast flow-statistic ip 224.1.1.1 vlan 3 command to
MVLAN ID is 3 and the IP address of the multicast program is 224.1.1.1).
l If the queried result is close to the rate of the program traffic, the program traffic reaches
the MA5612 upstream port. It is assumed that packets loss occurs on the MA5612, user
terminal, or on the line between the MA5612 and the user terminal. Then, go to Step
3.
l If the queried result is far lower than the rate of the program traffic, the program traffic
loses packets before reaching the MA5612 upstream port. It is assumed that the program
traffic loses packets on the line between the MA5612 and the upper-layer network. Then,
go to Step 2.
Step 2 Check the upper-layer network and devices of the MA5612.


Table 4-9 Troubleshooting method of faulty upper-layer network and devices

e
Cause
The Pixelation occurs when a user watches Replace the multicast source.
multica a program ordered from the multicast
st server.
source TIP
is If other users can watch the program
abnorm successfully, the multicast source is
al. normal.
upper- server from the MA5612 separately. It between the MA5612 and the
layer is found that packet loss occurs. multicast router or the fault on the
network TIP line between the MA5612 and the
quality If other users of the MA5612 can watch the multicast server.
of the program, the network between the
MA561 MA5612 and the multicast server is normal.
2 is
poor.
2. Order the program to check whether the user can watch the program successfully.
l If the user cannot watch the program, go to Step 3.
Step 3 Check the MA5612.

Table 4-10 Troubleshooting method of incorrect configurations of the MA5612

e
Cause
The rate Run the display service-port Bind a new traffic profile to
configu command to query the index of the Rx multicast streams.
red in traffic and then run the display traffic l If a correct traffic profile is in
the table ip command to query the PIR of the system, run the service-
traffic the traffic profile. The PIR is smaller port 100 outbound traffic-
profile than the bandwidth of the ordered table index 6 command to bind
bound program. the traffic profile (assume that
to the NOTE the index of the multicast traffic
traffic If the PIR is smaller than the bandwidth of streams is 100 and the index of
the traffic profile is 6) to the
is lower are lost and pixelation occurs. If the PIR is
very small, the blank screen may occur multicast streams again.
than the
because a large number of multicast packets l If the currently configured
bandwi are lost.
dth of traffic profile does not meet the
If the service port carrying the multicast requirement, run the traffic
the streams carries streams of other services,
multica table ip command to add a new
st profile that meets the
progra other services may occupy the majority of requirement and then bind the
m. traffic streams, which leads to insufficient profile to the traffic streams.
multicast bandwidth. As a result, the
pixelation occurs.
provider.
be used.


e
Cause
The Run the display qos-info traffic-limit Run the traffic-limit command to
QoS port command to query the target rate change the target rate to an
rate of the port and then compare the target appropriate value or run the undo
limitati rate with the bandwidth of the ordered traffic-limit command to cancel
on on program. The target rate is lower than the traffic limitation on the port.
the port the bandwidth of the ordered program.
is NOTE
excessi If the user port carries other services (such
vely as the Internet access service), the traffic of
low. all services must be lower than or equal to
the target rate. Otherwise, other services
may occupy the majority of traffic streams,
which leads to insufficient multicast
bandwidth. As a result, the pixelation
occurs.


e
Cause
The If one of the following symptoms Run the igmp user modify user-
maximu occurs, the fault is because the index max-bandwidth command
m maximum bandwidth of the user is to modify the maximum bandwidth
bandwi higher than the downstream line rate of the user to be lower than the line
dth of and the fast leave function is not rate.
the user enabled.
is l Pixelation occurs only when
higher programs are switched.
than the
downstr l Run the display igmp user user-
eam line index command to query the fast
rate and leave attribute (Quick leave) and
the fast the maximum bandwidth of the
leave program (User MaxBandWidth).
function The Quick leave is disable and the
is not maximum bandwidth is higher than
enabled the downstream line rate.
. NOTE
l When a user switches between channels
using a remote controller, two IGMP
packets are transmitted at the same
time, including one leave packet and
one join packet. Before the previous
program stops, traffic of two programs
exists over the subscriber line. If no
sufficient bandwidth is available for the
traffic of two programs over the line,
packet loss occurs due to traffic
overflow. As a result, pixelation occurs.
frequently, traffic of multiple multicast
groups exists over the line.
l After the maximum bandwidth of a user
is limited, the user cannot order a new
program if the bandwidth of the new
ordered program is larger than the value
(the maximum bandwidth - the used
bandwidth). This ensures that the
program that is being watched is not
affected.

Table 4-11 Troubleshooting method of faulty user terminal

e
Cause
The The fault is rectified after the STB is Reset or replace the STB.
STB is reset or replaced.
faulty.
The TV Pixelation persists after the TV cable is Contact the TV set maintenance
set is connected to another video input device engineer to troubleshoot the TV set
faulty. such as a DVD player or VCR player. fault.
Assistance).
Step 6 End.
----End

4.3.1 No Power Feed After Offhook

This section describes how to troubleshoot the fault where there is no power feed when the phone
goes offhook. When this fault occurs, the phone does not respond after going offhook, and the
phone in-use indicator is off, which means that the phone has no power feed.
Location Method
Use the following guidelines to locate the fault:

Start
Identify the fault

scope
The fault occurs on some The fault occurs on all The fault occurs on all ports
ports ports on some boards on the device
Check whether the phone is

functional
Check whether the loop and

circuit lines are functional
Check whether the

Check whether the user Check whether the power
service boards are
ports are functional board is functional
functional
Check whether the device

hardware and ambient
environment are normal
End
CAUTION
Procedure
Step 1 Check whether the fault always occurs on certain ports, occurs on all the ports on certain boards,
or occurs on all the ports on the entire MA5612.
l If the fault always occurs on certain ports, go to Step 2.
l If the fault occurs on all the ports on certain boards, go to Step 7.
l If the fault occurs on all the ports on the entire MA5612, go to Step 8.
Step 2 Replace the phone with another and check whether the fault is rectified.
l If the fault is rectified, go to Step 12.
l If the fault persists, go to Step 3.
Step 3 Perform the 8.4 POTS Subscriber Loop Line Test with the phone on the hook.
l If the test result (shown in Conclusion) is Normal, go to Step 5.
l If the test result (shown in Conclusion) is not Normal, rectify the fault based on the test
result. Then, go to Step 4.

NOTE
If the test result shown in Conclusion is AB all break off or no phone connected, the phone is faulty or
the line between the phone and the MA5612 is not properly connected. In this case, replace the phone or
check whether the line is connected properly.
Step 4 Check whether the fault is rectified.

Step 5 Perform the 8.3 POTS Subscriber Circuit Line Test with the phone on the hook.
l If all the test results are normal, the voice board is normal. Then, go to Step 8.
l If not all the test results are normal, the voice board is faulty. Then, go to Step 6.
Step 6 Use another port on the same board and check whether the fault is rectified.
Step 7 Replacing the service board and check whether the fault is rectified.
Step 8 Check whether the power board is working properly by referring to the power supply indicator
status on the board. For the status description of the power supply indicators, see A.1
Indicators .
l If the power board is working properly, go to Step 10.
l If the power board is not working properly, go to Step 9.
Step 9 Replace the power board with anther one. Then, check whether the fault is rectified.
Step 10 Check MA5612 hardware and the ambient environment.

1. Ensure that the device is grounded according to requirements. For details, see 2.1 Checking
the Grounding of the Device. Check whether the fault is rectified.
l If the fault persists, go to Step 10.2.
2. Check whether the control board is inserted properly.
l If the control board is inserted properly, go to Step 11.
l If the control board is not inserted properly, insert it properly. Then, go to Step 10.3.
3. Take the phone off the hook to check whether the fault is rectified.
4. Check whether the MA5612 is operating properly.
Check for leaks in the roof of the cabinet, water trails on the chassis, dust in the interior of
the chassis, and evidence of vermin. Also check whether the chassis is properly sealed.

l Wipe away any water and clear away any unwanted debris. Ensure that the equipment
room is waterproof and the chassis is properly sealed. (The chassis keeps insects or
rodents out of the cabinet.) Then, go to Step 10.5.
l If there is no evidence of water or vermin, go to Step 11.
l If the fault is not rectified, go to Step 11.
Assistance).
Step 12 End.
----End
4.3.2 No Tone After Offhook

This section describes how to troubleshoot the fault where there is no dial tone or only a weak
current sound when a phone goes offhook.
Fault Location

Start
Identify the fault

scope.
ports. ports on some boards. on the device.

functional.

circuit lines are functional.
Check whether the Check whether the DSP

Check whether the user
service boards are daughter board are properly.
ports are functional.
functional.
Check whether the

configurations are correct.
Check whether the softswitch

End
CAUTION
Procedure
Step 1 Identify the fault scope.
l If the fault occurs on some ports, go to Step 2.
l If the fault occurs on all ports on some boards, go to Step 7.
l If the fault occurs on all ports on the device, go to Step 8.
Step 2 Replace the phone with a functional one and check whether the fault is rectified.
Step 3 Run the pots loop-line-test command to perform a 8.4 POTS Subscriber Loop Line Test on
the affected port. Check whether Conclusion is Normal.
l If Conclusion is Normal, go to Step 5.

l If Conclusion is not Normal, rectify the fault based on the displayed test conclusion. Then,
go to Step 4.
NOTE
For example, if Conclusion is Phone not connected, the phone is faulty or the line between the phone
and the device is not connected properly. In this case, replace the phone or ensure that the line is connected
properly.

Step 5 Run the pots circuit-test command to perform a 8.3 POTS Subscriber Circuit Line Test on
the affected port.
l If the results of all test items are Normal, the user port is functional. Go to Step 8.
l If the results of only some test items are Normal, the user port is faulty. Go to Step 6.
Step 6 Connect the phone to another port on the same board, and check whether the fault is rectified.
l If the fault is rectified, the original user port is faulty. Go to Step 16.
Step 7 Replace the voice service board and check whether the fault is rectified.
Step 8 Run the display boardframeid/slotid command to check whether the state of the DSP daughter
board is Normal.
l If the state is Normal, go to Step 9
l If the state is not Normal, go to Step 15
Step 9 Run the display pstn state command to check whether CTPAdmState of the affected POTS
port is StartSvc.
l If CTPAdmState is StartSvc, go to Step 11.
l If CTPAdmState is not StartSvc, go to Step 10.
Step 10 Run the undo endservice command to reactivate the service on the port, and check whether the
fault is rectified.
Step 11 Ensure that the media gateway (MG) interface is functional. Then, check whether the fault is
rectified.
NOTE
Check whether the following conditions are met:
l Run the display if-h248 all command in H.248 mode or the display if-sip all command in SIP mode to
check whether the media gateway (MG) interface is working properly.
l Check whether the MG interface configuration on MA5612 is the same as that on the interconnected media
gateway controller (MGC).
l Check whether the MA5612 communicates with the MGC properly.

Step 12 Check whether the data configuration on MA5612 conforms to the data plan.
l If the data configuration conforms to the data plan, go to Step 14.
l If the data configuration does not conform to the data plan, go to Step 13.
Step 13 Take the phone off the hook to check whether the fault is rectified.
Step 14 Have a softswitch engineer check whether the softswitch data configuration conforms to the data
plan. If any inconsistency is found, make necessary modifications to ensure data consistency.
Then, check whether the fault is rectified.
Assistance).
Step 16 End.
----End
4.3.3 Busy Tone After Offhook

Busy tone after offhook indicates that when a subscriber picks the phone off the hook, only a
busy tone is heard.
Location Method

Start
Confirm the voice protocol type
H.248 protocol SIP protocol
Check MG interface attributes Check SIP interface attribu
Check the data of MGC

subscribers
Check the RTP format of the MG
Check whether the subscriber

line is normal
End
CAUTION
Procedure
Step 1 Run the display alarm history all command to query the historical alarms and then run the
display event history all command to query the historical events. Check whether the alarms or
events related to the fault are generated.

l If such alarms or events are generated, clear these alarms or events to rectify the fault
according to the relevant guide. Then, proceed to Step 2.
l If such alarms or events are not generated, go to Step 3.
NOTE
The related alarms or events include the following:

l 0x38100005 DSP resources for voice services are insufficient
l 0x3b000002 Remote blocking
l 0x1a010001 H.248 interface interruption
l 0x13010001 Communication between the VAG and the SIP proxy server is interrupted
Step 2 Pick the phone off the hook again and check whether a dial tone is heard.
l If a dial tone is heard, go to Step 16.
l If no dial tone is heard, proceed to Step 3.
Step 3 Run the display protocol support command to query the current used voice protocol.
l If the H.248 protocol is used, proceed to Step 4.
l If the SIP protocol is used, go to Step 13.
Step 4 In the H.248 mode , run the reset coldstart command to reset the MG interface and make the
subscriber register again. If registration is successful, run the display pstn state command in
the global config mode to check whether the service management state (CTPAdmState) of the
POTS port is StartSvc.
CAUTION
In resetting the MG interface, subscriber services carried on this interface will be interrupted.
Therefore, before resetting the MG interface, ensure that no users under this interface are running
services.

l If CTPAdmState is not StartSvc, proceed to Step 5.
Step 5 In the H.248 mode, run the display if-h248 attribute mgid command to check whether MG
interface attributes are the same as those configured on the MGC.
l If MG interface attributes are the same as those configured on the MGC, go to Step 7.
l If MG interface attributes are different from those configured on the MGC, run the if-h248
attribute command in the H.248 mode to modify MG interface attributes to be the same
as those configured on the MGC. Run the reset coldstart command to reset the MG
interface. Then, proceed to Step 6.
Step 7 In test mode, run the pots loop-line-test command to perform the POTS subscriber loop line
test with the phone on the hook.
l If the test result (shown in Conclusion) is Normal, the subscriber line and the phone are
normal. Then, go to Step 9.

NOTE
If the test result shown in Conclusion is Phone not connected, the phone is faulty or the line between the
phone and the MA5612 is not properly connected. In this case, replace the phone or check whether the
line is connected properly.
Step 9 On the MGC, query subscriber data and check whether data of the subscriber who encounters
the fault is configured on the MGC.
l If data of the subscriber who encounters the fault is configured on the MGC, go to Step
11.
l If data of the subscriber who encounters the fault is not configured on the MGC, configure
such data on the MGC. Then, proceed to Step 10.
Step 11 On the MGC, trace H.248 signaling, and check whether error 502 is contained in H.248 signaling.
l If error 502 is contained in H.248 signaling, run the tid-template modify command to
modify the terminal ID format of the MG to be the same as that of the MGC. In the H.248
mode, run the reset coldstart command to reset the MG interface and make the subscriber
register again. Then, go to Step 14.
l If error 502 is not contained in H.248 signaling, go to Step 15.
NOTE
In the protocol, error 502 is defined as invalid termination point, including RTP termination point and
physical termination point. On the MGC, if the traced H.248 signaling contains error 502, it indicates that
the terminal ID format of the MG is different from that of the MGC. For example, RTP configured on the
MGC is in a progressively increase format of RTP1000, RTP1001 and RTP1002; however, RTP configured
on the MG is in a progressively increase format of RTP500, RTP501 and RTP502.
Step 12 In the SIP mode, run the reset command to reset the SIP interface and make the subscriber
register again. If registration is successful, run the display pstn state command in the global
config mode to check whether the service management state (CTPAdmState) of the POTS port
is StartSvc.
CAUTION
services.


Step 13 In the SIP mode, run the display if-sip attribute mgid command to check whether SIP interface
attributes are the same as those configured on the IMS.
l If SIP interface attributes are the same as those configured on the IMS, go to Step 15.
l If SIP interface attributes are different from those configured on the IMS, run the if-sip
attribute basic command in the SIP mode to modify SIP interface attributes to be the same
as those configured on the IMS. Run the reset command to reset the SIP interface. Then,
proceed to Step 14.
Assistance).
Step 16 End.
----End
4.3.4 Continuous Dial Tone During Dialing

This section describes how to troubleshoot the fault where the dial tone does not stop when the
user begins to dial. The dial tone should stop when the user dials a number.
Location Method
Start

working properly
Check whether the gain of a user

port is set to a very small value
Check whether the input gain of the

DSP chip is set to a very small value
Check whether any of the ports on

the same service board or adjacent
service boards are locked
Check whether the subscriber and

circuit lines are normal
End
CAUTION

Procedure
Step 1 Replace the phone and check whether the service is restored.
Step 2 Check whether the gain of the user port is set properly.
1. In pstnport mode, run the display pstnport electric frameid/slotid/portid command to
check whether Sendgain and Recvgain of the affected port are set properly.
l If they are set properly, go to Step 3.
l If they are not set properly, go to Step 2.2.
2. Run the pstnport electric set command to set the gain of the affected port again. Then,
NOTE
Set the gain according to the empirical value. If no empirical value is available, change the gain several
times to different values within the gain range (from small to large) to see if the fault is rectified when the
gain is changed.
l If the fault is rectified when the gain is set to a certain value, go to Step 11.
l If the fault is not rectified when the gain is set to a certain value, go to Step 3.
Step 3 Check whether the gain of the DSP chip is set properly.
1. In ESL user mode, run the display mgpstnuser attribute command to check whether the
gain of the DSP chip is set properly.
l If the gain of the DSP chip is set properly, go to Step 4.
l If the gain of the DSP chip is not set properly, go to Step 3.2.
2. In ESL user mode, run the mgpstnuser attribute set frameid/slotid/portid dsp-input-gain
dsp-input-gain-value dsp-output-gain dsp-output-gain-value command to change the gain
of the DSP chip. Then, check whether the service is restored.
NOTE
gain is changed.
Step 4 In privilege mode, run the display pstn state command check the status of PSTN ports on the
same service board or adjacent service boards. To be specific, check whether CTPSrvState is
Locked.
l If CTPSrvState is Locked, go to Step 5.
l If CTPSrvState is not Locked, go to Step 6.
Step 5 Unblock the blocked ports and check whether the service is restored.
NOTE
Unblock the blocked ports by hanging up the phone or clearing the shorted wires within the same twisted pair.


NOTE

Step 9 User another user port and check whether the service is restored.
l If the service is restored, the original user port is faulty. Allocate another port for the user.
Then, go to Step 11.
Assistance).
Step 11 End.
----End
4.3.5 Called Party's Phone Does Not Ring

This section describes how to troubleshoot the fault where the called party's phone does not ring
when called. However, if the called party picks up the phone, the call is still connected.
Location Method

Start

working properly
Check whether the subscriber line

is normal
Check whether the service boards

are working properly
Check whether the power board is

working properly
Check whether the power supply

system of the device is working
properly
Check whether the device hardware

and ambient environment are
normal

issues the ringing signaling to the
called party
End
CAUTION
Procedure
NOTE


Step 4 Replacing the service board and check whether the service is restored.
Step 5 Check whether the power supply indicator on the power board is working properly. For the status
description of the power supply indicator, see A.1 Indicators .
l If the power supply indicator is working properly, go to Step 9.
l If it is not working properly, go to Step 6.
Step 6 Replace the power board with another one. Then, check whether the fault is rectified.
Step 7 Check whether the power supply system is stable. Specifically, check whether the voltage is
stable and whether the system is frequently powered off.
l If the power supply system is stable, go to Step 9.
l If the power supply system is not stable, go to Step 8.
Step 8 If the power supply system is not stable because of certain objective causes (for example, there
is a large electromechanical device), use a stable standby power source, such as the battery.
Step 9 Check the hardware of the MA5612 and the ambient environment.
1. Ensure that the device is grounded properly. For details, see 2.1 Checking the Grounding
of the Device. Then, check whether the fault is rectified.
l If the control board is inserted properly, go to Step 9.4.
3. Check whether the service is restored.

Step 10 Track the signaling to check whether the softswitch issues the ringing signaling to the called
party.
l If the softswitch issues the ringing signaling to the called party, go to Step 11.
l If the softswitch does not issue the ringing signaling to the called party, contact softswitch
engineers to locate the fault, go to Step 12.
Assistance).
Step 12 End.
----End
4.3.6 One-Way Audio or No Audio During Communication

This section describes how to troubleshoot the fault where only one party (one-way) or neither
party in a call can hear the other party. Regardless of whether there is one-way audio or no audio,
the called party's phone still rings.
Location Method
Start

working properly
Check whether the link between

the MA5612 and the MG is
normal
Check whether the route

configuration on the MA5612 is
correct
Check whether the ACL rules are

configured correctly on the
MA5612 and the bearer network
End

NOTE
This fault is generally caused by an incorrect route configuration on the device or the bearer network. The
signaling stream is deemed normal because the phone's abilities to dial and ring are normal. In this case, users
connected to the same MA5612 can locate the cause by calling each other.
l If the users can call each other successfully, the channel between the device and the bearer network is
faulty.
l If the users cannot call each other, the device is faulty.
CAUTION
Procedure
Step 1 Replace the phone to redial a number and check whether the fault is rectified.
l If the fault is rectified, the original phone is faulty and needs to be replaced, go to Step
11.
Step 2 Check whether users connected to the MA5612 can call each other.
l If users can call each other, go to Step 5.
l If they cannot call each other, go to Step 3.
Step 3 Run the display acl all command to check whether an ACL rule is filtering out the upstream or
downstream voice media stream.
l If an ACL rule is filtering out the upstream or downstream voice media stream, run the
undo acl command to delete the ACL rule. Then, go to Step 4.
l If no ACL rule is filtering out the upstream or downstream voice media stream, go to Step
10.
NOTE
The ACL rule issued to a port cannot be deleted, but you can cancel the application of the ACL rule by
running the undo packet-filter command.
Step 4 Redial the number to check whether the fault is rectified.

Step 5 Run the Ping command on the MA5612 to check whether the link between the MA5612 and
the MG is normal.
l If the IP address of the MG can be pinged, go to Step 8.
l If the IP address of the MG cannot be pinged, go to Step 6.
Step 6 Run the display ip routing-table command to check whether the route configuration on the
MA5612 is correct.
l If the route configuration is correct, go to Step 8.
l If the route configuration is incorrect, run the ip route-static command to reconfigure the
route. Then, go to Step 7.


Step 8 Check whether the ACL rules are configured correctly on the bearer network.
l If the ACL rules are configured correctly, go to Step 10.
l If they are not configured correctly, modify or cancel them as needed. Then, go to Step
9.
Assistance).
Step 11 End.
----End
4.3.7 Noise in Communication

Noise in communication indicates that a subscriber hears a strong current noise and broadcast
noise in communication, but the noise does not include the environment noise of two parties.
Location Method

Start
Confirm
the fault scope.
The fault occurs on all The fault occurs on

subscribers of the device. subscribers of certain ports
on the device.
The electrical attributes of a

PSTN port does not comply
with the local standard.
The input and output gains

of the DSP chip do not
comply with the local
standard.
The DDF and grounding do

not comply with the local The subscriber line and the
standard. phone are faulty.
The voice board is faulty.
The electrical interference

exists in the device or
subscriber line environment.

CAUTION
Procedure
Step 1 Confirm the fault scope.
l If the fault occurs on all subscribers of the device, proceed to Step 2.
l If the fault occurs on subscribers of certain ports on the device, go to Step 7.
l If the fault occurs on subscribers using certain numbers, go to Step 11.
Step 2 Run the display pstnport electric command to query the electrical attributes of a PSTN port.
Check whether the impedance type, current type, transmit gain, and receive gain configured on
the faulty port are the same as those configured on a normal port.
l If the impedance type, current type, transmit gain, and receive gain configured on the faulty
port are the same as those configured on a normal port, proceed to Step 4.
port are different from those configured on a normal port, run the pstnport electric set
command to configure the electrical attributes of the PSTN port again to make the electrical
attributes to be the same as those configured on a normal port. Then, proceed to Step 3.
NOTE
When you need to configure the electrical attributes of the PSTN port in batches, you can run the pstnport
electric batset command.
Different countries and regions have different requirements on the electrical attributes. Therefore, the
configured electrical attributes must comply with the local standard and the interconnection parties must
have the same configurations. For example, the requirements for transmit and receive gains are as follows:
l China: The transmit gain and receive gain of the local network are 0 dB and -3.5 dB respectively. The
transmit gain and receive gain of the toll network are 0 dB and -7 dB respectively.
l Other countries and regions: Generally, the transmit gain the receive gain of the local network and toll
network are 0 dB and -7 dB respectively.
Step 3 Call each other again to check whether the fault is rectified.
l If the fault persists, proceed to Step 4.
Step 4 Run the display mgpstnuser attribute command to query the attributes of a PSTN subscriber,
and check whether the input and output gains of the DSP chip configured on the faulty port are
the same as those configured on a normal port.
l If the input and output gains of the DSP chip configured on the faulty port are the same as
those configured on a normal port, go to Step 6.
l If the input and output gains of the DSP chip configured on the faulty port are different
from those configured on a normal port, run the mgpstnuser attribute setframeid/slotid/
portiddsp-input-gaindsp-input-gain-valuedsp-output-gaindsp-output-gain-value
command to configure the attributes of the PSTN subscriber again and make the attributes
to be the same as those configured on a normal port. Then, proceed to Step 5.

Step 6 Check whether DDF and MA5612 grounding complies with the local standard. Call each other
again to check whether the fault is rectified.
Step 7 Run the pots loop-line-test command to perform a loop-line test for the board where a fault
occurs.
l If the test result is normal, it indicates that the external line and the phone are faulty. Then,
go to Step 9.
l If the test result is that the MA5612 is not connected to a phone, it indicates that the phone
is faulty or the cable between the phone and the MA5612 is not properly connected. In this
case, replace the phone and make sure that the cable between the phone and the MA5612
is properly connected. Then, proceed to Step 8.
l If the test result is others such as line B grounding, it indicates that external lines are faulty.
In this case, troubleshoot the fault according to the prompt message. For example, if the
test result is line B grounding, it indicates that line B may be damaged. In this case, replace
the line B, and then proceed to Step 8.
NOTE
The qualitative loop-line test conclusions include: normal, touch the power line, line A mixed with other lines,
line B mixed with other lines, lines A and B mixed with other lines, line A grounding, line B grounding, lines
A and B grounding, self-mixing (small resistance and self-touch wire), A-B insulation difference, line A leakage,
line B leakage, lines A and B leakage, phone set not connected, offhook, and unknown.
Step 9 Check the voice board for the subscriber who encounters the fault. Call each other again to check
Step 10 Check the environment for the MA5612, and external lines to troubleshoot electrical interference
of the broadcast tower and high voltage cables. Call each other again to check whether the fault
is rectified.
Step 11 Check configurations related to numbers of the softswitch and voice gateway. Compare the
configurations of the faulty numbers with those of the normal numbers and modify the
configurations of the faulty numbers to be the same as those of the normal numbers. Call each
other again to check whether the fault is rectified.
Assistance).

Step 13 End.
----End
4.3.8 Discontinuous Communication

This section describes how to troubleshoot the fault where the call is discontinuous.
Fault Location
Start

working properly
Check whether the QoS

priority of the voice service is
set properly
Check whether the quality of

the bearer network meets
voice service requirements
end
CAUTION
Procedure
Step 1 Replace the phone and check whether the fault is rectified.
Step 2 In VoIP mode, run the display qos ip and display qos vlan commands to check whether the
QoS priority of the voice service is set properly.
l If the QoS priority of the voice service is set properly, go to Step 4.
l If the QoS priority of the voice service is not set properly, go to Step 3.
NOTE
l When packet loss occurs due to network congestion, the packets whose QoS priorities are the lowest
are discarded firstly. The QoS priority ranges from 0 to 7 from low to high.
l The voice service has high requirements on network quality. Therefore, users are recommended to set
the priority of the VoIP service on the MA5612 to 6.

Step 3 Run the qos ip command to set the QoS priorities of the media IP address and signaling IP
address to high values. Run the qos vlan command to set the VLAN priorities of the media IP
address and signaling IP address to 6. Then, check whether the fault is rectified.
Step 4 Check whether the quality of the bearer network meets voice service requirements.
NOTE
Users can use a tool to check whether the quality of the bearer network meets voice service requirements. Users
can also run the ping command on the MA5612 to check whether the IP address of the media gateway (MG)
can be pinged. That is, check whether serious packet loss occurs.
l If serious packet loss occurs, go to Step 5.
l If serious packet loss does not occur, go to Step 6.
Step 5 Check whether the network connection between the MA5612 and the MG is normal and whether
the transmission devices are normal. If there are certain faults on the network or devices, rectify
the faults and ensure that the MG can be pinged from the MA5612 and that no serious packet
loss occurs. Then, check whether the service is restored.
Assistance).
Step 7 End.
----End
4.3.9 Low Communication Voice

This section describes how to troubleshoot the fault where the voices heard by both the calling
party and called party, or one of the two parties, in a voice over IP (VoIP) public switched
telephone network (PSTN) service is very low.
Location Method

Start
Check whether the phone is working

properly
Check whether the loop and circuit

lines are normal
Check whether the service board to

which the affected user is connected
is working properly
Check whether the voice gain of the

PSTN port is set to a very
small value
Check whether the output gain of the

DSP chip is set to a very
small value

working properly
Check whether the hardware and the

ambient environment are normal
End
CAUTION
Procedure
Step 1 Replace the phone with another. Then, check whether the service is restored.
Step 2 Perform a 8.4 POTS Subscriber Loop Line Test with the phone on the hook.
l If the test result (shown in Conclusion) is Normal, the subscriber line is normal. Then, go
to Step 4.
NOTE
When you rectify the fault based on the test result, the phone is faulty or the line between the phone and
the MA5612 is not properly connected if the test result shown in Conclusion is AB all break off or no
phone connected. In this case, replace the phone or check whether the line is connected properly.


Step 4 Perform a 8.3 POTS Subscriber Circuit Line Test with the phone on the hook.
l If the results of all test items are normal, the voice service board is normal. Then, go to
Step 7.
l If the results of all test items are not normal, the voice service board is faulty. Then, go to
Step 5.
Step 5 Perform the test on another port on the same board.

Step 6 Replacing the service board to test whether the fault is rectified.
Step 7 In pstnport mode, run the display pstnport electric command to query the electrical attributes
of the PSTN port. Check whether the impedance type, current type, transmit gain, and receive
gain of the affected port are the same as those of a normal port.
l If the electrical attributes of the PSTN port are the same as those of a normal port, go to
Step 9.
l If they are different, run the pstnport electric set command to reconfigure the electrical
attributes of the PSTN port to ensure that they are the same as the attributes of a normal
port. Then, go to Step 8.
NOTE
Users can run the pstnport electric batset command to configure electrical attributes of multiple PSTN
ports in batches.
Different countries and regions require different electrical attributes. Therefore, ensure that the configured
electrical attributes comply with local standards and interconnected devices use the same electrical
attributes.

Step 9 In ESL user mode, run the display mgpstnuser attribute command to query the PSTN user
attributes and check whether the input and output gains of the DSP chip used on the affected
port are the same as those used on a normal port.
l If they are the same, go to Step 11.
l If they are different, run the mgpstnuser attribute set frameid/slotid/portid dsp-input-
gain dsp-input-gain-value dsp-output-gain dsp-output-gain-value command to
reconfigure the PSTN user attributes of the port to ensure that the attributes are the same
as those of a normal port. Then, go to Step 10.


Step 11 Check whether the power board is working properly by referring to the status of power supply
indicators on the board. For the status description of the power supply indicators, see A.1
Indicators .
Step 13 Check the device hardware and the ambient environment.
1. Ensure that the device is grounded. For details, see 2.1 Checking the Grounding of the
Device. Then, check whether the fault is rectified.
l If there is no evidence of water or vermin, go to Step 13.4.
4. Check whether there is any source of high-frequency electromagnetic interference exists
around the MA5612 and the subscriber line. If there is such a source, remove it from the
area and check whether the fault is rectified.
Assistance).
Step 15 End.
----End

248 protocol.
4.4.1 Fax Service Failures

This section describes how to troubleshoot common fax service failures, such as when a fax fails
to send, the fax image is blurred, or the fax rate is low.

Location Method
CAUTION
Procedure
Step 1 Confirm that the user followed the instructions given in the user manual of the fax machine when
operating it and check whether the fax machine is faulty.
l If the user followed the instructions and the fax machine is normal, go to Step 3.
l If the user did not follow the instructions or the fax machine is faulty, go to Step 2.

NOTE
Fax machines are relatively error-prone, especially multi-function fax machines. If any faults occur when
using the fax services, use the following guidelines to identify the fault causes:
l Check whether the fax machine is connected properly.
l Check whether the user sending the fax pressed the start key before receiving the fax tone from the
peer fax machine.
l Check whether there is paper in the peer fax machine, the fax paper is jammed, the printer ink has run
out, the fax machine is not powered on, or whether some part of the fax machine is faulty.
l Some fax machines have a function that blocks incoming faxes without affecting the machine's ability
to send faxes. Check whether this function is enabled.
l If the fax machine is not automatically enabled to receive faxes, the user may have to push a button to
allow the machine to receive faxes.
Step 2 Rectify the fault on the fax machine, and then try to send or receive the fax again. Then, check
Step 3 Check whether the fax parameter configurations on the local MA5612 and peer MA5612 are
consistent with the data plan.
NOTE
The query method is as follows:

l Run the display fax parameters command to query the fax parameter configurations. Verify that the value
for FAX transfers mode is consistent with that configured on the peer end. The fax coding and decoding
mode can be the transparent transmission mode or the T.38 mode.
l Run the display fax-modem parameters command to query the public fax parameter configurations. Verify
that the value for Rfc2198-start-mode is consistent with that configured on the peer end. The RFC 2198
protocol is used to improve data transmission reliability and service quality using the redundancy
transmission mechanism. This function must be enabled on both the MDU and the softswitch if the function
is used. Otherwise, the fax service will fail.
l Run the display dsp attribute command to query the digital signal processor (DSP) parameter
configurations.
l If the fax parameter configurations on the local MA5612 and peer MA5612 are consistent
with the data plan, go to Step 5.
l If they are not consistent with the data plan, go to Step 4.
Step 4 Modify the fax parameter configurations to ensure that they are consistent with the data plan,
and then check whether the service is restored.
NOTE
l Run the fax parameters command to modify the fax parameter configurations.
l Run the fax-modem parameters command to modify the public fax parameter configurations.
l Run the dsp attribute command to modify the DSP parameter configurations.
Step 5 Have an MGC maintenance engineer check whether the fax service data configurations on the
MGC are consistent with the data plan.
l If the configurations are consistent with the data plan, go to Step 7.
l If the configurations are not consistent with the data plan, go to Step 6.

Step 6 Have the MGC maintenance engineer modify the fax service data configurations on the MGC
so that they are consistent with the data plan. Then, check whether the service is restored.
Step 7 Check whether the quality of the bearer network meets the requirements for the fax service.
NOTE
Users can use an associated tool to test the bearer network quality or run the ping command on the MA5612 to
ping the peer access gateway (AG).
In transparent transmission mode, the packet loss ratio for fax services must be less than 0.5%.
l If the peer AG cannot be pinged or the packet loss ratio is too high, go to Step 8.
l If the peer AG cannot be pinged and there is no packet loss, go to Step 9.
Step 8 Check whether the network connection between the MA5612 and the peer AG is normal and
whether the transmission devices are normal. If there are faults on the network or devices, rectify
the faults and ensure that the peer AG can be pinged from the MA5612 and that there is no packet
loss. Then, check whether the service is restored.
Step 9 In the onhook state, perform a 8.4 POTS Subscriber Loop Line Test.
l If the test result (shown in Conclusion) is not Normal, the subscriber line is faulty. Connect
a fax machine to the main distribution frame (MDF) and perform a test to determine the
location of the fault. Rectify the fault as needed, for example, by replace the subscriber
line. Then, go to Step 10.
Step 11 Perform a test on another port on the same board to check whether the service is restored.
Assistance).
Step 14 End.
----End
4.4.2 Modem Service Failures

This section describes how to troubleshoot common modem service failures, such as when dial-
up Internet access fails or the modem goes offline repeatedly. Common modem services include
the lottery service and point of sale (POS) service.

Location Method
CAUTION
Procedure
Step 1 Replace the modems of the calling and called party with phones, and check whether the two
parties can communicate with each other normally.
l If the two parties can communicate with each other, go to Step 2.
l If the two parties cannot communicate with each other, address the problem by referring
to 4.3 Troubleshooting VoIP PSTN Service .
Step 2 Replace the called party phone with a modem. Use the calling party phone to call the called party
modem. Check whether the modem tone can be heard when the call is connected.
l If the modem tone can be heard, go to Step 4.
l If the modem tone cannot be heard, the called party modem cannot automatically start the
modem service. Check the modem configurations to ensure that it can automatically start
modem service. Then, go to Step 3.


Step 4 Check whether the modem parameter configurations on the local MA5612 and peer MA5612
are consistent with the data plan.
NOTE

l Run the display modem parameters command to query the modem parameter configurations.
l Run the display fax-modem parameters command to query the public modem parameter configurations.
l Run the display dsp attribute command to query the DSP parameter configurations.
l If the modem parameter configurations on the local MA5612 and peer MA5612 are
consistent with the data plan, go to Step 6.
Step 5 Modify the modem parameter configurations so they are consistent with the data plan, and then
NOTE
The modification method is as follows:

l Run the modem parameters command to modify the modem parameter configurations.
l Run the fax-modem parameters command to modify the public modem parameter configurations.
Step 6 Have an MGC maintenance engineer check whether the modem service data configurations on
the MGC are consistent with the data plan.
Step 7 Have the MGC maintenance engineer modify the modem service data configurations on the
MGC so that they are consistent with the data plan. Then, check whether the service is restored.
Step 8 Check whether the quality of the bearer network meets the requirements of the modem service.
NOTE
Users can use a tool to test the bearer network quality or run the ping command on the MA5612 to ping the peer
access gateway (AG). The packet loss ratio must be less than 0.5%.

Step 10 Run the dsp attribute command on the MA5612 to change the static initial jitter buffer value
(the normal-fixed-jb parameter) of the DSP channel to double the packetization duration. (The
packetization duration can be queried on the MGC.) Then, check whether the service is restored.
Assistance).
Step 12 End.
----End
4.5 H.248-Based ISDN PRA Service Troubleshooting

The primary rate adaptation (PRA) is used to access the ISDN users to the media gateway (MG)
through the ISDN primary rate interface (PRI) based on the H.248 protocol. This topic describes
how to troubleshoot the fault of the H.248-based ISDN PRA service.
Location Method
When the H.248-based ISDN PRA service is faulty, locate the fault according to the following
procedure:
1. Check whether the H.248 interface is normal.
2. Check whether the configuration of the device is the same as the configuration of the
softswitch.
3. Check whether the IUA link is normal.
4. Check whether the configuration of the PRA users is correct.
5. Check whether the board connecting the PRA users is normal.
6. Check whether the physical line is faulty.
Procedure
Step 1 Run the display if-h248 state command to query the status of the MG interface.
l If the MG interface is in Normal state, it indicates that the MG interface is normal.
l If the MG interface is in Local Closed state, it indicates that the operator runs the
shutdown command on the MA5612 to shut down the MG interface.
l If the MG interface is in Remote Closed state, it indicates that the operator issues the
shutdown command on the softswitch to the MG interface.
l If the MG interface is in Wait ack state, it indicates that the MG interface is registering with
the media gateway controller (MGC).
l If the MG interface is in Graceful Closed state, it indicates that the MG interface is shut
down gracefully.
Step 2 Run the display if-h248 attribute command to check the attributes of the MG interface.
Contact the engineer on the softswitch side to check and ensure that the attributes of the MG
interface are the same as the attributes of the softswitch.

Step 3 Run the display iua-link state command to check the status of the IUA link.
The IUA link can be used normally only when the IUA link is in active state.
When the IUA link is not in active state, check the configuration of the IUA link. Check whether
the settings of the following parameters of the IUA link are the same as the settings of the
parameters of the softswitch:
l Remote port
l Remote IP address
l Local port
l Local IP address
Step 4 Run the display mgprauser command to check the configuration of the PRA users.
Check whether the settings of the following parameters are correct:

l MGID
l TerminalID
l LinkSetNo
l InterfaceID
Step 5 Run the display board command to query the status of the board.
In normal cases, the board is in Normal state.
If the board is not in Normal state, troubleshoot the fault according to the following procedure:
l Remove and insert the board.
l Replace the board.
Step 6 Check whether the physical line is connected properly.
Check whether the E1 line is connected properly and whether the cables are worn out.
Perform a loopback test to check whether the E1 port on the E1 line is faulty. For details, see
8.2 Performing a Loopback on an E1 Port and 8.1 Performing a Loopback on an E1
Line.
----End
4.6 SIP-Based ISDN PRA Service Fault Troubleshooting

The PRA is used to access the ISDN users to the MG through the ISDN PRI based on the SIP
protocol. This topic describes how to troubleshoot the fault of the SIP-based ISDN PRA service.
Location Method
When the SIP-based ISDN PRA service is faulty, locate the fault according to the following
procedure:
1. Check whether the SIP interface is normal.

2. Check whether the configuration of the device is the same as the configuration of the proxy
server.
3. Check whether the configuration of the PRA users is correct.

4. Check whether the board connecting the PRA users is normal.

5. Check whether the physical line is faulty.
Procedure
Step 1 Run the display if-sip all command to query the status of the SIP interface.
l If the SIP interface is in Normal state, it indicates that the SIP interface is normal.
l If the SIP interface is in Fault state, it indicates that the SIP interface is faulty.
l If the SIP interface is in Not start state, it indicates that the SIP interface is not reset. Run
the reset command to reset the SIP interface.
Step 2 Run the display if-sip attribute command to check the attributes of the SIP interface.
Contact the engineer on the proxy server side to check and ensure that the attributes of the SIP
interface are the same as the attributes of the softswitch.
Step 3 Run the display sipprauser command to check the configuration of the PRA users.
Check whether the settings of the following parameters are correct:
l SIP interface ID
l Phone number
Step 4 Run the display board command to query the status of the board.
In normal cases, the board is in Normal state.
If the board is not in Normal state, troubleshoot the fault according to the following procedure:
l Remove and insert the board.
l Replace the board.
Step 5 Check whether the physical line is connected properly.
Check whether the E1 line is connected properly and whether the cables are worn out or exposed.
Perform a loopback test to check whether the E1 port on the E1 line is faulty. For details, see
8.2 Performing a Loopback on an E1 Port and 8.1 Performing a Loopback on an E1
Line.
----End

SmartAX MA5612 Multi-service Access Module 5 Troubleshooting Services Transmitted Through a GPON
Maintenance Guide Port
5 Troubleshooting Services Transmitted

Through a GPON Port
About This Chapter
This chapter describes how to troubleshoot common faults, such as Internet and voice service
faults, when the MA5612 uses a GPON port for upstream transmission.

the MA5612.
5.2 Troubleshooting Multicast Service
This section describes how to troubleshoot common faults in the multicast service
248 protocol.


the MA5612.
Prerequisites
The ONU and the OLT must communicate with each other normally. If a fault occurs in
communication between the ONU and the OLT, all the services of the ONU are interrupted.
NOTE
The following lists common faults in communication between the ONU and the OLT.
l 6.1.1 GPON ONU Registration Failure
l 6.1.2 Failure to Auto Discover a GPON ONU
l 6.1.3 GPON ONU Frequently Goes Online and Offline
5.1.1 Troubleshooting the Failure to Access the Internet

This section describes how to troubleshoot failures associated with local area network (LAN)
users accessing the Internet on fiber to the building (FTTB) and fiber to the curb (FTTC)
networks, for example, users fail to open Web pages.
Fault Location
User terminal A user fails to obtain the IP For the details about how to troubleshoot
address (excludes users this fault, see the following sections:
with a static IP address). l 5.1.2 Troubleshooting the Failure
to Obtain an IP Address by PPPoE
Dialup
l 5.1.3 Troubleshooting the Failure
to Obtain an IP Address in DHCP
Mode
The user obtains the IP l The user's PC is infected with viruses.

address successfully l Internet Explorer (IE) on the user's
(excludes users with a PC is faulty.
static IP address). The user
can access the Internet l The network interface card (NIC) in
after replacing the PC. the user's PC is faulty, or the PC is
slow to respond after running for a
long period.
Web site Certain Web sites fail to The Web site sever is faulty.
open.
No Web site can be The domain name server (DNS) fails to

opened. resolve the domain name.

DNS A Web site can be opened l The DNS is faulty and fails to resolve
by entering its IP address. the domain name.
l The communication between the
user's PC and the DNS is abnormal.
CAUTION
Procedure
Step 1 Check the user's PC.
1. Check whether the user's PC can obtain the IP address.
NOTE
To view the IP address of the PC, do as follows:

press Enter.
b. In the command line interface (CLI) window displayed, run the ipconfig command to view the IP
address obtained by the PC.
l If the PC can obtain the IP address, go to Step 1.3.
l If the PC cannot obtain the IP address, do as follows:
– For PPPoE users, see 5.1.2 Troubleshooting the Failure to Obtain an IP Address
by PPPoE Dialup. Then, go to Step 1.2
– For DHCP users, see 5.1.3 Troubleshooting the Failure to Obtain an IP Address
in DHCP Mode. Then, go to Step 1.2
2. Check whether the user can access the Internet.
l If the user can access the Internet successfully, go to Step 5.
l If the user cannot access the Internet, go to Step 1.3.
3. Replace the user's PC with a test PC that can access the Internet in the same mode as the
user's PC. Then, check whether the user can access the Internet.
l If the user can access the Internet, the fault is on the user's PC. Check whether the user's
PC is infected with viruses, the NIC or IE of the user's PC is faulty, or the PC is slow
to respond after running for a long period. Then, go to Step 5.
Step 2 Check whether the user can access the Internet by going to various Web sites through the Web
server.
l If the user can access certain Web sites, the fault is on the Web site itself. Go to Step 5.
l If the user cannot access any Web sites, go to Step 3.
Step 3 Check the DNS.

1. Enter the IP address of an existing Web site in the address bar of IE (format: http://
192.168.0.2) and check whether the Web site opens.
l If the Web site opens, the fault is on the DNS and the DNS cannot resolve the domain
name. Go to Step 3.2.
l If the Web site does not open, go to Step 4.
2. Check whether the PC can ping the IP address of the DNS.
NOTE
To view the DNS IP address of the PC, do as follows:

press Enter.
b. In the CLI window displayed, run the ipconfig/all command to view the DNS IP address obtained by
the PC.
l If the PC can ping the IP address of the DNS, the link between the PC and the DNS is
normal and the DNS is faulty. Go to Step 3.3.
l If the PC cannot ping the IP address of the DNS, go to Step 4.
3. Rectify the fault on the DNS. Then, check whether the user can access the Internet.
l If the user can access the Internet, go to Step 5.
Step 4 Record the results of the preceding steps in the form for reporting a fault (see Fault Report Form),
fill out the entire form, and then submit the form to Huawei for technical support (see Contacting
Huawei for Assistance).
Step 5 End.
----End
5.1.2 Troubleshooting the Failure to Obtain an IP Address by PPPoE

Dialup
This section describes how to troubleshoot a failure to obtain an IP address by point-to-point
over Ethernet (PPPoE) dialup mode. When a user accessing the Internet in LAN mode on a fiber
to the building (FTTB) or fiber to the curb (FTTC) network fails to obtain an IP address by
PPPoE dialup, refer to the following guidelines to address the issue.
Fault Location
Perform a 8.9 PPPoE Dialup Emulation Test to determine the fault scope first.
If the result of the PPPoE dialup emulation test is "success", the link between the MA5612 and
the upper layer broadband remote access server (BRAS) is normal. Therefore, the fault must be
located on the link between the MA5612 and the user terminal. Use the following guidelines to
locate the fault more accurately.
User terminal If the fault does not recur when the l The dialup software is not
user's PC is replaced, the fault is properly installed on the PC.
on the PC. l The network interface card
(NIC) in the PC is faulty.

MA5612 l The quality of the subscriber line
is deteriorated.
are loose.
The user port is deactivated.
MA5612 The fault does not recur when the The user port is faulty.
line of the affected user is
connected to another user port.
If the result of the PPPoE dialup emulation test is not "success," the fault must be located on the
link between the MA5612 and the upper layer BRAS. Use the following guidelines to address
the fault more accurately.
inconsistent with the data plan. such as the VLAN ID, is incorrect.
The uplink port forwards no The uplink port on the MA5612 is

service stream to the upper layer not added to the upstream VLAN.
device.
The security configuration is l The Policy Information Transfer

incorrect. Protocol (PITP) configuration is
incorrect.
l The configured number of MAC
addresses that can be
dynamically learned by the
service port is incorrect.
l The configuration of the anti-
MAC address spoofing function
is incorrect.
l An access control list (ACL) that
does not allow transmission of
PPPoE packets is configured.

A MAC address drift occurs. A user or BRAS MAC address may

drift because of attacks or a loop on
the network.
OLT The configured service port data is The configured service port data,
inconsistent with the data plan. such as the upstream VLAN, user
side VLAN, and port ID, is
incorrect.
The uplink port forwards no The uplink port on the OLT is not
service stream to the upper layer added to the upstream VLAN.
device.
Upper-layer The configuration of the upper The maximum transmission unit

layer router is not correct.

CAUTION
Procedure
Step 1 Perform a 8.9 PPPoE Dialup Emulation Test on the MA5612 for the affected user.
l If the result of the dialup emulation test is not "success", go to Step 4.
NOTE
If the result of the dialup emulation test is "timeout", "parameter negotiation failure", "user authentication
failure", "offline requested by the peer end", or other errors, the fault is located on the upper layer device
of the MA5612.
l If the result of the dialup emulation test is "success," go to Step 2.

1. Replace the user's PC with another and perform a dialup emulation test to check whether
the dialup can be successful.
l If the dialup is successful, the fault is related to a problem on the user's PC. Check
whether the PPPoE software is installed on the PC incorrectly and whether the PC's NIC
is faulty or disabled, and address the problem. Then, go to Step 15.
2. Replace the user's terminal and perform a dialup check. Then, check whether the dialup is
successful.


online.
mode, rate, network cable adaptation mode of the Ethernet port are consistent with those
of the user terminal.
l If they are inconsistent, modify the parameter settings of the Ethernet port to ensure that
the parameter settings are consistent with those of the user terminal. Then, go to Step
3.8.
NOTE
duplex.


9. Replace the port and perform a dialup check. Then, check whether the dialup is successful.
l If the dialup is successful, the original user port is faulty. Change the user's port and
reconfigure the port data. Then, go to Step 15.

1. Run the display service-port port frameid/slotid/portid command to check whether the
data configuration of the user's service port, such as the VLAN ID and port ID, is correct.
l If the data configuration of the user's service port is correct, go to Step 4.3.
l If the data configuration of the user's service port is incorrect, go to Step 4.2.
NOTE
Step 5 Check the PITP configuration on the MA5612.

1. Run the display pitp config command to check whether the current global PITP function
is enabled.
2. Run the display pitp config command to check the current PITP mode.
l If the current PITP mode is pmode, go to Step 5.5.
l If the current PITP mode is vmode, go to Step 5.3.
3. Run the display pitp vmode ether-type command to query the currently configured
Ethernet protocol type in the VBRAS packet and check whether the protocol type is the
same as the protocol type configured on the upper layer device.
l If the protocol types are the same, go to Step 6.
l If the protocol types are different, go to Step 5.4.
4. Run the pitp vmode ether-type command to change the current protocol type so it is the
same as the protocol type configured on the upper layer device, and then perform another
dialup check.


5. Run the display pitp permit-forwarding service-port service-portid command to check
whether the function that allows user-side PPPoE packets to carry vendor tags is enabled
on the service port of the affected user.
l If the function is enabled, go to Step 6.
l If the function is not enabled, run the pitp permit-forwarding service-port service-
portid enable command to enable it on the service port. Then, go to Step 5.6.
Step 6 Check the user port MAC address configuration on the MA5612.
1. Run the display mac-address port frameid/slotid/portid command to query the current
number of MAC addresses learned by the service port of the user.
2. Run the display mac-address max-mac-count service-port index command to query the
maximum number of MAC addresses that can be learned by the service port.
3. Check whether the current number of MAC addresses learned by the service port reaches
the maximum number of MAC addresses that can be learned by the service port.
l If the current number has reached the maximum number, run the mac-address max-
mac-count service-port index command to increase the maximum number of MAC
addresses that can be dynamically learned by the service port. Then, go to Step 7.
l If the maximum number has not been reached, go to Step 8.
Step 7 Perform a dialup check.

NOTE
l The mac-addr parameter in the command indicates the user's MAC address. For user terminal
dialup, the user's MAC address is the MAC address of the user terminal. For PC dialup, the user's
MAC address is the MAC address of the PC.
l The F/S/P parameter in the query result indicates the service port where the user's MAC address
has been learned. Generally, the port displayed in the query result should be the service port of
the user. If the displayed port is not the service port of the user, the user's MAC address has
drifted.

1. Run the display location mac-addr command to check multiple times (more than three
times is recommended) whether a MAC address drift occurred on the port that has learned
the BRAS MAC address.
NOTE
l The mac-addr parameter indicates the MAC address of the BRAS.

l The F/S/P parameter in the query result indicates the uplink port where the BRAS MAC address
has been learned. Generally, the port displayed in the query result should be the uplink port on
the MA5612 connected to the BRAS. If the displayed port is not the uplink port, the BRAS MAC
address drift has occurred.
Step 10 Check whether the security configuration on the MA5612 is correct.

1. Run the display security config command to check whether the anti-MAC address
spoofing function is enabled.
2. Run the display mac-address static command to check whether a static MAC address is
configured on the service port of the user.
NOTE
If a static MAC address and the anti-MAC address spoofing function are configured on a service port
at the same time, the service port user cannot access the Internet.
l If a static MAC address is configured on the service port, go to Step 10.3.
l If no static MAC address is configured on the service port, go to Step 11.
3. Run the security anti-macspoofing disable command to disable the anti-MAC address
spoofing function on the service port or run the undo mac-address static command to
delete the static MAC address configured on the port based on the service planning. Then,
perform another dialup check.
Step 11 Check whether an ACL restricting the transmission of PPPoE packets is configured on the
MA5612.
1. Run the display packet-filter port frameid/slotid/portid command to check whether an
ACL is configured on the user port.
l If an ACL is configured, go to Step 11.2.
l If no ACL is configured, go to Step 12.
2. Run the display acl command to check whether the ACL restricts the transmission of
PPPoE packets.
l If the ACL restricts the transmission of PPPoE packets, go to Step 11.3.
l If the ACL does not restrict the transmission of PPPoE packets, go to Step 12.

3. Change the ACL rule that restricts the transmission of PPPoE packets or delete the ACL
configuration on the port. Then, perform another dialup check.
Step 12 Check whether the data configuration on the OLT is correct.

1. Run the display service-port command to check whether the service port configuration on
the OLT, such as the user VLAN, upstream VLAN, ONU ID, and port ID, is correct.
NOTE

1. Check whether the MTU and QoS configurations on the upper layer device, such as the
upper layer router, are correct.
go to Step 14.

Step 15 End.
----End
5.1.3 Troubleshooting the Failure to Obtain an IP Address in DHCP

Mode
This section describes how to troubleshoot a failure to obtain an IP address in Dynamic Host
Configuration Protocol (DHCP) mode. When a user accessing the Internet in LAN mode on
fiber to the building (FTTB) and fiber to the curb (FTTC) network fails to obtain an IP address
by DHCP mode, refer to the following guidelines to address the issue.
Fault Location
If the fault occurs, determine the fault location by performing 8.11 DHCP Dialup Emulation
Test.
If the test result is "get IP successful", the link between the optical network unit (ONU) and the
upper-layer BRAS is available, and the fault occurs on the link between the ONU and the user
terminal. Use the following guidelines to locate the fault.
User terminal If the fault does not recur when the The network interface card (NIC) in
user's PC is replaced, the fault is the PC is faulty or disabled.
on the PC.
ONU l The quality of the subscriber line
is deteriorated.
are loose.
ONU The user port is not activated. The user port is deactivated.
The fault does not recur when the The user port is faulty.
line of the affected user is moved
to another user port.

If the test result is not "get IP successful", the link between the ONU and the upper-layer BRAS
is unavailable. Use the following guidelines to locate the fault on the link.
ONU The configured service port data is The configured service port data,
inconsistent with the data plan. such as the uplink VLAN ID, is
incorrect.
The uplink port does not forward The ONU uplink port has not been
service streams to the upper-layer added to the uplink VLAN.
device.
A MAC address flapping occurs. A user or BRAS MAC address may

flap because of attacks or a loop on
the network.
The security configuration is l The static IP binding function is

incorrect. enabled.
l The MAC address filtering table
is incorrectly configured and the
affected user is configured in the
table.
Link between the The ONU cannot ping the DHCP l The DHCP configuration on the
ONU and DHCP server. ONU is inconsistent with that on
server the DHCP server.
l The link between the ONU and
the DHCP server is faulty.
DHCP server The ONU can obtain an IP address l The IP address resources of the
when the DHCP server is DHCP server are exhausted.
replaced. l The DHCP server is faulty.
OLT The configured service port data is The configured service port data,
inconsistent with the data plan. such as the uplink VLAN, user-side
VLAN, and port ID, is incorrect.
The uplink port does not forward The OLT uplink port has not been
service streams to the upper-layer added to the uplink VLAN.
device.
Upper-layer The configuration of the upper- The maximum transmission unit

layer router is incorrect.


CAUTION
Procedure
Step 1 Perform 8.11 DHCP Dialup Emulation Test for the affected user on the ONU.
l If the test result is not "get IP successful", go to Step 4.
NOTE
If the test result is "send packet fail", "DHCP server not found", "DHCP server refuse request", or "get IP
overtime", the upper-layer device of the MA5612 is faulty.
l If the test result is "get IP successful", go to Step 2.

1. Replace the user's PC with another one and then perform a dialup test to check whether the
new PC can obtain an IP address.
l If the new PC can obtain an IP address, the fault is on the user's PC. Check whether the
PC's NIC is faulty or disabled, and address the problem. Then, go to Step 11.
l If the new PC fails to obtain an IP address, go to Step 2.2.
2. Replace the user terminal with another one and then check whether the new user terminal
l If the new user terminal can obtain an IP address, go to Step 11.
l If the new user terminal fails to obtain an IP address, go to Step 3.
Step 3 Check the interoperability between the user terminal and the ONU.
1. In ETH mode, run the display port state portid command on the ONU to check whether
online.
5. Check the quality of the physical line between the ONU and the user terminal to determine
whether the line is not connected properly or the line is old. Reconnect the line properly or
replace the old line as needed to ensure good line quality. Then, check whether Link of the
Ethernet port is online.


mode, rate, and network cable adaptation mode of the Ethernet port are consistent with
those of the user terminal.
l If they are inconsistent, modify the settings of the Ethernet port to ensure that the settings
are consistent with those of the user terminal. Then, go to Step 3.8.
NOTE
duplex.
9. Replace the user port and then check whether the PC can obtain an IP address.
l If the PC can obtain an IP address, the original user port is faulty. Change the user's port
and reconfigure the port data. Then, go to Step 11.
Step 4 Check whether the data configuration on the ONU is correct.

1. Run the display service-port port frameid/slotid/portid command to check whether such
data configurations of the user's service port as the VLAN ID and port ID are correct.
NOTE

Step 5 Check whether a user's MAC address has drifted on the ONU.
l If a MAC address drift occurred on the port, go to Step 5.2.
l If a MAC address drift did not occur on the port, go to Step 6.
NOTE
address. Generally, the port displayed in the query result should be the service port of the user.
If the displayed port is not the service port of the user, the user's MAC address has drifted.
user's MAC address has drifted. If such a problem occurs, disconnect the loop or deactive
port is initiating the attacks. Then, perform another dialup check and check whether the PC
Step 6 Check the security configuration on the ONU.
1. Run the display security mac-filter command to check whether the user's MAC address
is contained in the filtering list.
l If the user's MAC address is contained in the filtering list, run the undo security mac-
filter command to delete the user's MAC address from the filtering list. Then, go to
Step 6.2.
l If the user's MAC address is not contained in the filtering list, go to Step 7.
Step 7 Check the interoperability between the DHCP server and the ONU.
1. Run the display dhcp option82 config command to check whether the DHCP Option82
configuration on the ONU is consistent with that on the DHCP server.
l If the configurations are consistent, go to Step 7.3.
l If the configurations are inconsistent, change the configuration on one side as needed
to ensure that they are consistent. Then, go to Step 7.2.

3. Check whether the DHCP server is faulty and the IP address of the DHCP server is exhaust.
Ensure the DHCP server work in the normal state. Check whether the PC can obtain an IP
address.
Step 8 Check whether the data configuration on the OLT is correct.
1. Run the display service-port command on the OLT to check whether such service port
configurations on the OLT as the user VLAN, upstream VLAN, ONU ID, and port ID are
correct.
l If the configurations are incorrect, refer to the following notes to change the
NOTE
the configuration on the upper layer device. Then, go to Step 8.4.
1. Check whether the data configuration on the upper layer device is correct, for example,
whether the MTU and QoS configurations on the upper layer router are correct.
go to Step 10.


Step 11 End.
----End
5.1.4 Troubleshooting Low Internet Access Rate

Low Internet access rate indicates that the attainable Internet access rates for users are lower
than the rates provided them. This section describes how to troubleshoot low access rates when
local area network (LAN) users on fiber to the building (FTTB) and fiber to the curb (FTTC)
networks access the Internet.
Fault Location
User terminal The fault does not recur when the l The PC's network interface card
user's PC is replaced. (NIC) is faulty.
l The user's PC is infected with
viruses.
l The computer does not meet the
minimum configuration
requirements.
Link between Packet loss on the subscriber line A fault has occurred on the
user terminal and is severe. subscriber line.
ONU l The quality of the subscriber line
is deteriorated.
are loose.
ONU The Internet access rate on a single l The rate restriction configuration
port is low. for the user is incorrect.
l Certain users' Internet access
rates are restricted on the BRAS.
The Internet access rates on all l A user's MAC address has drifted
ONU ports are low. between ONU ports.
l The upstream bandwidth on the
ONU is insufficient.

OLT The Internet access rates on all The DBA bandwidth that the OLT
ONU ports are low. allocates to the ONU is insufficient.
Upper layer Only certain users' Internet access Certain users' Internet access rates
BRAS rates are low; the services of other are restricted on the BRAS.
users on the BRAS are normal.
CAUTION
Procedure
Step 1 Determine the fault range when identifying the fault causes.
l If the Internet access rates of only certain users on the ONU are low whereas the rates of
other users are normal, go to Step 2.
l If the Internet access rates of all users on the ONU are low, go to Step 7.

1. Replace the user's PC and test whether the Internet access rate is normal.
l If the Internet access rate is normal, the fault is on the PC. Check whether the NIC in
the user's PC is faulty, the PC is infected with viruses, the PC is slow to respond after
running for a long time, or the PC's configuration is low. Then, go to Step 11.
l If the Internet access rate is low, go to Step 2.2.
2. Replace the user terminal, and then check whether the Internet access rate is normal.
l If the Internet access rate is normal, go to Step 11.
l If the Internet access rate is low, go to Step 3.
Step 3 Check whether the line between the ONU and the user terminal is normal.
NOTE
Run the display port statistics portid command on the ONU to query all the performance statistics of the
subscriber line after the subscriber line is initialized. Then, check whether the number of CRC error frames
increases. If it increases, packet loss is occurring on the subscriber line.
2. Check whether the physical line between the ONU and the user terminal is connected
Then, check whether the Internet access is normal.
l If the Internet access is normal, go to Step 11.

l If the Internet access is low, go to Step 4.
Step 4 Check whether unknown traffic is occupying the bandwidth on the ONU.
1. Ensure that the user is not accessing the Internet. Run the display port statistics portid
command to query the statistics of the Ethernet port multiple times (recommended: five
times). The query interval is 20s.
l If the upstream or downstream traffic increases rapidly, unknown traffic is occupying
the bandwidth. Go to Step 4.2.
l If the upstream or downstream traffic does not increase, go to Step 5.
NOTE
Normally, the query results should be similar when the user is not accessing the Internet.
l Number of transmitted octets: Indicates the current downstream traffic of the user.
l Number of received octets: Indicates the current upstream traffic of the user.
2. Use packet-capturing software, such as Ethereal, to capture packets on the user's PC,
confirm the known traffic source, and then eliminate the unknown traffic source. You can
eliminate the unknown traffic source by checking whether the PC sending the unknown
traffic is infected with viruses. Then, check whether the Internet access rate is restored.
l If the Internet access is not restored, go to Step 5.
Step 5 Check the maximum rate configured for the user.

1. Run the display service-port command to query the indexes of the traffic profiles in the
receive and transmit directions configured for the service port.
2. Run the display traffic table ip command to query the corresponding traffic profile. Then,
check whether the committed information rate (CIR) reaches the bandwidth that the user
applied for.
l If the CIR is less than the bandwidth that the user applied for, the traffic profile bound
to the user is incorrect. Go to Step 5.3.
l If the CIR is equal to the bandwidth that the user applied for, go to Step 6.
3. Run the undo service-port command to delete the service port of the user. Then, run the
service-port command to reconfigure a service port for the user and bind the user to the
proper traffic profile. Check whether the Internet access rate is restored.
NOTE
When modifying the traffic profile, note the following:

l The service ports bound to the traffic profile take effect at the same time when the traffic profile is
modified.
l If the current traffic profile is bound to multiple service ports, run the traffic table ip command to
create the required traffic profile.
l If the current traffic profile is bound to one service port, run the traffic table ip modify command to
modify the traffic profile.
Step 6 Check whether the user's MAC address has drifted from one ONU port to another.
(recommended: three times) whether the user's MAC address has drifted away from the
port that originally learned it.


NOTE
2. Check whether a loop has formed or there are user attacks on the port that the user's MAC
address has drifted to. If a loop has formed, disconnect it. If the port that the MAC address
has drifted to is being attacked, deactivate the port initiating the attacks. Then, check
whether the Internet access rate is restored.
Step 7 Query the OLT for the DBA bandwidth that the OLT allocates to the ONU.
1. Run the display ont info portid ontidcommand to query the DBA bandwidth that the OLT
allocates to the ONU.
Query the value of the DBA Profile-ID parameter.

2. Run the display DBA-profile profile-id profile-idcommand to query the bandwidth
configured in the DBA profile.
3. Check whether the bandwidth occupied by the uplink port on the ONU reaches the allocated
DBA bandwidth.
l If the bandwidth occupied by the uplink port on the ONU almost reaches the permitted
maximum bandwidth, the bandwidth of the uplink port on the site is the cause of the
fault. Go to Step 7.4.
l If the bandwidth occupied by the uplink port on the ONU is lower than the maximum
attainable bandwidth, go to Step 8.
4. Change the DBA bandwidth that the OLT allocates to the ONU or reduce the number of
users on the device by cutting users over to another device. Then, check whether the service
is restored.
Step 8 Check whether the upper layer BRAS is restricting the user rate.
l If the rate of the affected user is restricted on the BRAS, modify the BRAS configuration.
Then, go to Step 9.
l If the rate of the affected user is not restricted on the BRAS, go to Step 10.

l If service is normal, go to Step 11.
l If service is not normal, go to Step 10.

Step 11 End.
----End
5.1.5 Troubleshooting Frequent Interruptions in Internet Service

This section describes how to troubleshoot frequent interruptions in Internet service when local
area network (LAN) users on fiber to the building (FTTB) and fiber to the curb (FTTC) networks
are accessing the Internet.
Fault Location
User terminal The fault does not recur when the The user's PC is infected with
user's PC is replaced. viruses or the network interface card
(NIC) in the user's PC is faulty.
optical network l The subscriber line is old.
unit (ONU)
are loose.
l There is a strong source of
interference around the user.
ONU The Internet service on a single l The user port is faulty.

port is frequently interrupted. l The quality of the subscriber line
is deteriorated and the packet
loss on the subscriber line is
severe.
Internet services on all ONU ports l The ONU is faulty.

are frequently interrupted. l There is a strong source of
interference around the ONU.
l The MAC address has drifted
between ONU ports.
Upper layer Internet services of all users The BRAS MAC address has drifted
broadband connected to the BRAS are between ONU ports
remote access frequently interrupted.
server (BRAS)
CAUTION

Procedure
1. Replace the user's PC and then check whether Internet service is restored.
l If service is restored, the fault is on the user's PC. Check whether the NIC in the user's
PC is faulty or whether the user's PC is infected with viruses. Then, go to Step 7.
l If service is not restored, go to Step 1.2.
2. Replace the user terminal, and then check whether the service is restored.
Step 2 Check whether the line between the ONU and the user terminal is normal.
NOTE
Run the display port statistics portid command on the ONU to query all the performance statistics of the
subscriber line after the subscriber line is initialized. Then, check whether the number of CRC error frames
increases. If it increases, packet loss is occurring on the subscriber line.
2. Check whether the physical line between the ONU and the user terminal is connected
3. Check whether there is a strong source of interference, such as a wireless base station or a
high-frequency switch power system, around the user.
l If there is a strong source of interference around the user, it may be the cause of the
fault. Contact the relevant department to handle it. Then, go to Step 7.
l If there is no strong source of interference around the user, go to Step 3.
Step 3 Change the port for the user and configure the necessary data on the ONU. Then, check whether
the service is restored.
l If the service is restored, the user port is faulty. Change the user's ONU port and reconfigure
the data. Then, go to Step 7.
Step 4 Check whether the user's MAC address has drifted from one ONU port to another.
(recommended: three times) whether the user's MAC address on the port that learned it has
drifted.

NOTE
Step 5 Check whether a BRAS MAC address drift has occurred on the ONU.
1. Run the display location mac-addr command to check multiple times (recommended: three
times) whether a BRAS MAC address has drifted away from the port that originally learned
it.
l If the BRAS MAC address has drifted, go to Step 5.2.
l If the BRAS MAC address has not drifted, go to Step 6.
NOTE
l The mac-addr parameter in the command indicates the BRAS's MAC address.
l The F/S/P parameter in the query result indicates the uplink port that learned the BRAS MAC
address. Normally, the port displayed in the query result is the uplink port on the ONU connected
to the BRAS. If the displayed port is not the uplink port, the BRAS MAC address has drifted.
Step 7 End.
----End
5.2 Troubleshooting Multicast Service

This section describes how to troubleshoot common faults in the multicast service
Prerequisites

NOTE
6.1 Abnormal ONU Status in GPON Upstream Transmission
5.2.1 Failure to Go Online of a Multicast User

This topic describes how to troubleshoot the fault when a multicast user fails to order any
programs because the multicast user fails to go online (the queried user status is offline or
block on the ONU). When such a fault occurs in an FTTB or FTTC network, locate the fault
Location Method
When a multicast user in an FTTB or FTTC network is blocked, run the undo igmp user
block command to unblock the user.
When a multicast user in an FTTB or FTTC network is offline, enable the ONU debugging
function and locate the fault according to whether the ONU receives the report packet from the
multicast user.
l If the ONU receives the report packet, the multicast link is normal but the ONU fails to
create a corresponding multicast entry. This is generally caused by incorrect multicast
configurations on the ONU.
l If the ONU does not receive the report packet, the multicast link fails. This is mainly caused
by incorrect ONU software configurations, faulty physical link between the ONU and the
modem, and hardware faults of terminals.
Table 5-1 describes fault symptoms and possible causes when a multicast user in an FTTB or
FTTC network is offline.
Table 5-1 Fault symptoms and possible causes when a multicast user in an FTTB or FTTC
network is offline

Scope
ONU The ONU receives the l The program ordered is not in the MVLAN to
report packet. which the multicast user belongs.
l No upstream port is configured in the MVLAN
to which the multicast user belongs.
permission to watch the program.
l The maximum multicast bandwidth of the user
is lower than the required bandwidth of the
ordered program.
permission to order certain types of programs
(such as HDTV).


Scope
The ONU does not receive The IGMP function of the MVLAN on the ONU
the report packet and all is disabled.
users in the MVLAN fail to
go online.
ONU to The ONU does not receive l The hardware of the port on the ONU is faulty.
the the report packet and a l The set-top box (STB) is faulty.
terminal single user fails to go
online.
NOTE
Faults can be located according to specific scenarios because fault scopes are different for deployment and
routine operation and maintenance.
l If the fault occurs during deployment, check initial configurations of the hardware and the software.
l If a multicast user fails to go online during O&M, check only the hardware because the software
configuration of a user is generally not modified in this scenario. Hence, if the status of a user changes
from normal to abnormal, it is generally caused by hardware failures. If a multicast link failure occurs
after a new user is added or an existing user is modified, check whether the configuration is correct.
CAUTION
Procedure
Step 1 On the ONU, run the display igmp user user-index command to query the multicast user status
(State).
l If State is block, the multicast user is blocked. In this case, run the undo igmp user block
command to unblock the user. Then, go to Step 2.
l If State is offline, go to Step 3.
NOTE
If you need to block a multicast user from watching programs temporarily without deleting the user (for
example, when the user owes charges), run the igmp user block command to block the user. When the
user is blocked, the ONU forces the user to go offline from the current program. In addition, the ONU
rejects the user from ordering programs until the user is unblocked.
Step 3 Enable the ONU debugging function and collect information as follows:
1. Enable the function of multicast user monitoring.

2. Order the program again. Then, go to Step 4.

NOTE
After the preceding steps are performed, run the following commands to disable the debugging function.
Step 4 Locate the fault according to the receiving condition of the report packet and the fault scope.
l If the ONU displays a prompt message of the program, the ONU receives the report packet.
In this case, go to Step 5.1.
l If the ONU does not display a prompt message of the program, the ONU does not receive
the report packet. In this case, locate the fault according to the fault scope.
– If all users in the MVLAN fail to go online, go to Step 5.2.
– If a single user or some users in the MVLAN fail to go online, go to Step 6.
Step 5 Check multicast configurations of the ONU.

1. If the ONU receives the report packet, find the possible cause according to judgment criteria
described in Table 5-2 and then troubleshoot the fault. Then, go to Step 5.3 to check
Table 5-2 Incorrect multicast configurations of the ONU

e
Cause

bandwi l The ONU receives the report packet another program (whose
dth of and displays "the user fails to pass bandwidth is lower than the
the user bandwidth CAC". maximum bandwidth of the
is lower user) because the bandwidth is
than the l The maximum bandwidth of the
user is lower than the bandwidth of insufficient and the program
required cannot be watched.
bandwi the ordered program by running the
dth of display igmp user user-index l Increase the user bandwidth
the command to query the maximum and notify the user of ordering
ordered bandwidth (User MaxBandWidth) the program again.
progra of the user and running the display NOTE
m. igmp program name command to Run the igmp user modify user-
query the bandwidth (Bandwidth) index max-bandwidth command to
of the ordered program. modify the maximum bandwidth of
the user to ensure that it is higher than
NOTE the program bandwidth.
If User MaxBandWidth is no-limit, the
limited.


e
Cause

have the l The ONU receives the report packet l Notify the user of ordering
permiss and displays "the number of the another program (the maximum
ion to grade program that the user is number of the programs at this
ms
command on the ONU. the program.
NOTE NOTE
l If the maximum number of the You can run the igmp user watch-
programs at a certain level is 0, the user limit command to set the number of
cannot order any programs at this level. programs at each level that a user can
That is, the user's permission to the watch.
programs of the corresponding type is
restricted. For example, if HDTV
watch limit is 0, the user cannot watch
HDTV programs.
l If watch limit is no-limit, the
maximum number of the programs at
this level that a user can watch is not
limited, but the total number of
programs that can be concurrently
watched is limited.


e
Cause

have the l The ONU receives the report packet l If the user can watch all
permiss and displays "the user has no right". programs without
ion to authentication, perform the
watch l Run the display igmp user 100
command to query the right profile following two operations:
the
bound to the multicast user (assume a. In the BTV mode, run the
that the service port of the multicast igmp user modify 100 no-
user is 100). auth command to modify
– If Bind profiles is 0, the user is the authentication mode of
not bound to a right profile and the user to "no
the user cannot order any authentication" (assume
programs. that the multicast user index
is 100).
– If Bind profiles is equal to or
larger than 1, the user can watch b. Order the program again.
only the program to which the l If the user can watch certain
user has the watch permission. In programs with authentication,
this case, perform operations for notify the user of ordering
further check. In the queried another program because the
result, find the index (assume user has no permission to watch
that the index is 1) and name of the program. The permission to
the program right profile bound watch the program is watch or
to the user and run the display preview.
program.
program.
program is watch or


e
Cause
progra NOTE NOTE



e
Cause
is not in l The ONU receives the report packet l Notify the user of ordering
the and displays "match program fail". another program because the
MVLA user has no permission to watch
N to l The program ordered is not in the
MVLAN to which the multicast the program (the program is
which included in the MVLAN to
multica belongs).
st user
program again.
query Program match
mode of the program.
mode is enable, the
program is a static
program, which is
manually added.
program, which is
upon the ordering.
MVLAN.
igmp program add
command.
run the igmp match
be generated


e
Cause
belongs user belongs by running the display dynamically in the

. igmp program vlan command. MVLAN, and ensure
No If the following symptoms occur, the Add the upstream port to the
upstrea fault is because no upstream port is MVLAN to which the multicast
m port configured in the MVLAN to which the user belongs and notify the user of
is multicast user belongs. ordering the program again.
configu l The ONU receives the report packet NOTE
red in and displays "match program fail". In the MVLAN mode, run the igmp
the uplink-port command to set the
MVLA l No upstream port maps the upstream port as the upstream port of
N to MVLAN to which the multicast the MVLAN. This allows the
user belongs by running the display upstream port to forward the multicast
which packets of this MVLAN.
the igmp uplink-port all command to
multica query the multicast upstream port.
st user
belongs
.
2. If the ONU does not receive the report packet and all users in the MVLAN fail to go online,
the IGMP function may be disabled in the MVLAN. In this case, run the display igmp
config vlan command in the MVLAN mode to query IGMP mode of the MVLAN.
l If IGMP mode is off, the IGMP function is disabled in the MVLAN. In this case, run
the igmp mode command in the MVLAN mode to set IGMP mode to proxy or
snooping accordingly. Order a program and then, go to Step 5.3.
l If IGMP mode is proxy or snooping, the IGMP function is enabled in the MVLAN
and it is not the cause of the fault. Then, go to Step 6.
NOTE
If the terminal used by the user does not support multicast management, enable the IGMP function
on the ONU. Otherwise, the multicast service cannot be provisioned to the user.
3. Check whether the user can go online.
Step 6 If the ONU does not receive the report packet and the other users in the MVLAN can go online,
find the possible cause according to judgment criteria described in Table 5-3 and then
troubleshoot the fault. Then, go to Step 7 to check whether the fault is rectified.

Table 5-3 Line and terminal faults

e Cause
The The user can go online after migrating Migrate configurations of the faulty
hardwar configurations of the faulty port to a port to a functional one or replace the
e of the functional one and ordering the program. board to which the faulty port
port on belongs.
the ONU
is faulty.
The STB The user can go online after resetting the Reset the STB or use a functional
is faulty. STB or using a functional STB and STB.
ordering the program.
Step 9 End.
----End
5.2.2 Blank Screen After Ordering a Program

Blank screen after program ordering is a fault that a user cannot watch the program after the user
orders a program. When blank screen occurs after a user orders a program in an FTTB or FTTC
network, locate the fault according to the following procedure.
Location Method
When blank screen occurs after a user orders a program in an FTTB or FTTC network, Table
5-4 shows possible causes of the fault in different scopes.

User terminal The set-top box (STB), and TV cable are faulty.

ONU On the ONU, check whether the multicast user is online and then
troubleshoot the fault according to the following symptoms:
l If the multicast user is offline or is blocked, troubleshoot the fault
by referring to 5.2.1 Failure to Go Online of a Multicast User.
l If the multicast user goes online but blank screen occurs in the
multicast program, the fault is generally caused by incorrect
multicast configurations on the ONU. In this case, enable the ONU
debugging function and then locate the fault according to the
debugging information displayed on the ONU CLI. Possible
causes:
– The remaining multicast bandwidth of the user is lower than
the required bandwidth of the ordered program.
– The number of programs watched by the multicast user reaches
the upper limit so that the user cannot order a new program.
– The multicast user does not have the permission to watch the
program.
– The program ordered is not in the MVLAN to which the
multicast user belongs.
– The multicast user does not have the permission to order certain
types of programs (such as HDTV).
– The number of programs at a level watched by the multicast
user reaches the upper limit so that the user cannot order a new
program at this level.
– The rate configured in the traffic profile bound to the traffic
stream is far lower than the bandwidth of the multicast program.
– There are too many prejoined static programs, occupying too
many bandwidths.
OLT l The program ordered is not in the MVLAN that is configured on

the OLT.
l The ONU multicast mode configured on the OLT mismatches the
actual multicast mode configured on the ONU.
l The maximum multicast bandwidth assigned to the PON port is
very low.
Upper-layer l The program is not configured on the multicast server.

network and devices l The time to live (TTL) value set for the multicast stream of the
(including the multicast server is very small.
multicast router and
multicast server) of l The network communication fails. The network communication
the OLT failure occurs on the line between the OLT and multicast router,
and between the multicast router and multicast server.

CAUTION
Procedure
Step 1 Order a program again and perform the following steps to determine the location where program
traffic interruption occurs.
1. On the OLT, run the display multicast flow-statistic vlan 3 ip 224.1.1.1 command to
program traffic is not 0, the program traffic reaches the OLT upstream port.
2. On the ONU, run the display multicast flow-statistic 3 ip 224.1.1.1 vlan command to
program traffic is not 0, the program traffic reaches the ONU upstream port.
3. On the ONU, run the display statistics service-port command two or three times to query
the traffic statistics of the service port to which the multicast user belongs. If values of
Number of downstream packets different greatly, the program traffic reaches the ONU
user port.
NOTE
The following prerequisites must be met before you run the display statistics service-port command
to query the traffic statistics so as to prevent the queried results from being affected by other services.
l The multicast user is not watching other programs.
l The service port does no carry other heavy-traffic services. For example, the service of
downloading files from the Internet.
4. According to the preceding queried results, determine the fault scope by referring to Table
5-5 and perform operations accordingly.
NOTE
When multiple NEs need to be checked, generally locate the fault from lower-layer devices to upper-
layer devices, that is, in the sequence of user terminal -> ONU -> OLT -> multicast router -> multicast
server from segment to segment.
Table 5-5 Fault scope and troubleshooting method

User terminal If the following symptoms Check the user terminal

occur, the fault is because the following Step 2.
user terminal is faulty.
l Multicast streams reach the
user port of the ONU.
l Other users of the ONU can
watch the program.

User terminal and Multicast streams reach the a. Check the user terminal
ONU upstream port of the ONU but do following Step 2.
not reach the user port of the b. Check the ONU following
ONU. Step 3.
User terminal, Multicast streams reach the a. Check the user terminal
ONU, and OLT upstream port of the OLT but do following Step 2.
not reach the upstream port of b. Check the ONU following
the ONU. Step 3.
c. Check the OLT following
Step 4.
User terminal, Multicast streams do not reach a. Check the user terminal
ONU, OLT, and the upstream port of the OLT. following Step 2.
upper-layer b. Check the ONU following
network and Step 3.
devices of the
OLT c. Check the OLT following
Step 4.
d. Check the upper-layer
network and devices of the
OLT following Step 5.

1. Verify that the TV cable is properly connected to the STB.
2. Check the indicator status of the STB. If the indicator of the STB Ethernet port blinks
quickly, the STB decoding may be incorrect. Reset the STB or use a functional STB.
3. Order a program to check whether the user can watch the program successfully.
Step 3 Check the ONU.
1. On the ONU, run the display igmp user user-index command to query the multicast user
status (State).
l If State is online, go to Step 3.2.
l If State is offline or block, perform operations by referring to 5.2.1 Failure to Go
Online of a Multicast User. Then, go to Step 7.
2. Enable the ONU debugging function and collect information as follows:
a. Enable the function of multicast user monitoring on the ONU.
b. Order the program again. Then, go to Step 3.3.

NOTE
After the preceding steps are performed, run the following commands to disable the debugging
function.
Table 5-6 Troubleshooting method of incorrect multicast configurations on the ONU

e
Cause

bandwi l The ONU receives the report packet another program because the
dth of and displays "the user fails to pass remaining bandwidth is
the user bandwidth CAC". insufficient and the program
is lower cannot be ordered.
than the l On the ONU, run the display igmp
required user user-index command to query l Increase the user bandwidth
bandwi the maximum bandwidth (User and notify the user of ordering
dth of MaxBandWidth) and used the program again.
the bandwidth (Used bandwidth) of NOTE
ordered the user and run the display igmp l You can run the igmp user
progra program name command to query modify user-index max-
m. the bandwidth (Bandwidth) of the bandwidth command on the
ordered program. The remaining ONU to modify the maximum
bandwidth (the maximum bandwidth of the user.
bandwidth - the used bandwidth) is l When multicast bandwidth
lower than the bandwidth of the management is disabled
ordered program. (multicast CAC disabled), the
system does not guarantee the
NOTE bandwidth of the program ordered
If User MaxBandWidth is no-limit, the by the user.
limited. l The downstream rate of a line is
limited. Therefore, multicast
packets will be lost if the
bandwidth of the downstream
multicast streams is higher than
the maximum rate of the line.
Though multicast packets are lost,
the user can watch the program but
pixelation or delay occurs. Or
even blank screen occurs if a large
number of multicast packets are
lost.


e
Cause

maximu occurs, the fault is because the available troubleshooting methods
m programs reach the preset maximum according to the purchased service
number value. type:
of l The ONU receives the report packet l Notify the user of closing some
progra and displays "the number of programs and then ordering the
ms program that the user is allowed to program again because the
(Availa watch has reached maximum". available programs reach the
ble preset maximum value and no
progra l The number of programs that users
are watching is equal to the more programs can be ordered.
ms) that
users available programs by running the l Increase the available programs
can display igmp user user-index and notify the user of ordering
watch at command on the ONU. the program again.
the NOTE NOTE
same If Available programs is no-limit, the user You can run the igmp user modify
can watch 32 programs concurrently. user-index max-program command
time
on the ONU to modify the available
reach programs.
the
preset
maximu
m value.


e
Cause

have the l The ONU receives the report packet l If the user can watch all
permiss and displays "the user has no right". programs without
ion to authentication, perform the
watch l On the ONU, run the display igmp
user 100 command to query the following two operations:
the
right profile bound to the multicast a. On the ONU, run the igmp
user (assume that the service port of user modify 100 no-auth
the multicast user is 100). command in the BTV mode
– If Bind profiles is 0, the user is to modify the authentication
not bound to a right profile and mode of the user to "no
the user cannot order any authentication" (assume
programs. that the multicast user index
is 100).
– If Bind profiles is equal to or
larger than 1, the user can watch b. Order the program again.
only the program to which the l If the user can watch certain
user has the watch permission. In programs with authentication,
this case, perform operations for notify the user of ordering
further check. In the queried another program because the
result, find the index (assume user has no permission to watch
that the index is 1) and name of the program. The permission to
the program right profile bound watch the program is watch or
to the user and run the display preview.
command on the ONU to query
the user permission for ordering
the program.
program.
program is watch or


e
Cause
progra NOTE NOTE

same program, the permission with the list 1 command on the ONU to bind a
highest priority prevails. By default, the correct right profile to the multicast
priority of the program permissions is user (assume that the multicast user
forbidden > preview > watch > idle. You index is 100 and the right profile index
can run the igmp right-priority command is 1).
on the ONU to set the priority.


e
Cause
is not in l The ONU receives the report packet l Notify the user of ordering
the and displays "match program fail". another program because the
N to l The program ordered is not in the
MVLAN to which the multicast the program (the program is
which included in the MVLAN to
the user belongs by running the display
which the multicast user
multica belongs).
st user
program again.
config vlan command on
the ONU to query program
match mode of the
MVLAN to which the user
belongs.
mode is enable, the
program is a static
program, which is
manually added.
program, which is
upon the ordering.
MVLAN.
igmp program add
command on the ONU.
run the igmp match
group command on the
ONU to set the IP


e
Cause
belongs igmp program vlan command on address range of

. the ONU. program groups that can
be generated
dynamically in the
MVLAN, and ensure

have the l The ONU receives the report packet l Notify the user of ordering
permiss and displays "the number of the another program (the maximum
ion to grade program that the user is number of the programs at this
ms
command on the ONU. the program.
NOTE NOTE
If the maximum number of the programs at You can run the igmp user watch-
a certain level is 0, the user cannot order any limit command on the ONU to set the
programs at this level. That is, the user's number of programs at each level that
permission to the programs of the a user can watch.
corresponding type is restricted. For
example, if HDTV watch limit is 0, the
user cannot watch HDTV programs.


e
Cause

number occurs, the fault is because the number troubleshooting methods
of of programs at a level watched by the according to the purchased service
progra multicast user reaches the upper limit. type:
ms at a l The ONU receives the report packet l Notify the user of ordering
level and displays "the number of the another program because the
watched grade program that the user is ordered program is not
by the allowed to watch has reached purchased.
multica maximum".
st user l Increase the maximum number
reaches l The number of programs that users of programs at a level watched
the are watching is equal to the by the multicast user and notify
upper maximum number (watch limit) of the user of ordering the
limit so programs at a level that can be program again.
that the watched by the user by running the NOTE
user display igmp user extended- You can run the igmp user watch-
cannot attributes user-index command on limit command on the ONU to set the
the ONU. number of programs at each level that
order a a user can watch.
new NOTE
progra If watch limit is no-limit, the maximum
number of the programs at this level that a
m at this
user can watch is not limited, but the total
level. number of programs that can be
concurrently watched is limited.


e
Cause
The rate On the ONU, run the display service- Bind a traffic profile to multicast
configu port command to query the index of the streams and order the program
red in Rx traffic and then run the display again.
the traffic table ip command to query the l If a correct traffic profile is in
traffic PIR of the traffic profile. The PIR is far the system, run the service-
profile smaller than the bandwidth of the port 100 outbound traffic-
bound ordered program. table index 6 command on the
to the NOTE ONU to bind the traffic profile
traffic If the PIR is smaller than the bandwidth of (assume that the index of the
multicast traffic streams is 100
is far are lost and pixelation occurs. If the PIR is
very small, the blank screen may occur and the index of the traffic
lower profile is 6) to the multicast
than the are lost. streams again.
bandwi
If the service port carrying the multicast l If the currently configured
dth of streams carries streams of other services,
the traffic profile does not meet the
multica requirement, run the traffic
st other services may occupy the majority of table ip command on the ONU
progra traffic streams, which leads to insufficient to add a new profile that meets
m. multicast bandwidth. As a result, the the requirement and then bind
pixelation occurs. the profile to the traffic streams.
provider.
be used.


e
Cause
There The prejoined static programs occupy On the ONU, run the igmp
are too too many bandwidths, which is close to program modify command to
many the maximum downstream bandwidth modify Prejoin to disable and then
prejoine of multicast programs provided by the order the program again.
d static PON port.
progra l You can obtain the bandwidth of
ms, prejoined static programs following
occupyi the steps below:
ng too
many a. On the ONU, run the display
igmp program all command to
query the prejoin attribute
(Prejoin) of the program.
b. Calculate the bandwidth of
prejoined static programs
(Prejoin is enable) according to
the data plan. For example, if
100 programs are enabled with
the prejoin function and the
bandwidth of each program is 5
Mbit/s, the total bandwidth of
the prejoined static programs is
500 Mbit/s.
l You can obtain the maximum
downstream bandwidth of multicast
programs provided by the PON port
following the steps below:
a. On the OLT, run the display
igmp config global command to
query the bandwidth
management function
(Bandwidth management
switch).
b. On the OLT, run the display
igmp bandwidth port
command to query the
bandwidth (Max bandwidth)
assigned to the PON port.
– If Bandwidth management
switch is disable, the OLT does
not perform the multicast
bandwidth management. The
maximum bandwidth is the
maximum downstream
transmission rate supported by
the PON line.


e
Cause
bandwi – If Bandwidth management NOTE

dths. switch is enable and Max You can modify the attributes of all
multicast programs in any MVLAN.
bandwidth is no-limit, the OLT
When a program is being watched or
performs the multicast previewed by a user, however, its
bandwidth management but the attributes cannot be modified.
OLT PON port does not limit the
multicast program bandwidth.
The maximum bandwidth is the
maximum downstream
transmission rate supported by
the PON line.
– If Bandwidth management
switch is enable and Max
bandwidth has a specific value,
the OLT PON port limits the
multicast program bandwidth.
The maximum bandwidth is the
bandwidth (Max bandwidth)
assigned to the PON port.

Step 4 Check the OLT.

Table 5-7 Troubleshooting method of incorrect multicast configurations of the OLT

e
Cause
The On the OLT, run the display igmp Choose one of the following
progra program vlan command to check troubleshooting methods
m whether the program ordered by the according to the purchased service
ordered type:
is not in l Notify the user of ordering
the another program because the
N that is the program (the program is
configu included in the MVLAN to
red on which the multicast user
belongs).
program again.
config vlan command on
the OLT to query program
match mode of the
MVLAN to which the user
belongs.
mode is enable, the
program is a static
program, which is
manually added.
program, which is
upon the ordering.
MVLAN.
igmp program add
command on the OLT.
run the igmp match
group command on the


e
Cause
the multicast user is included in the OLT to set the IP address

OLT. MVLAN. range of program groups
that can be generated
dynamically in the
MVLAN, and ensure
The If the following symptoms occur, the On the OLT, run the igmp
maximu fault is because the maximum multicast bandwidth port command to
m bandwidth assigned to the PON port is modify the maximum bandwidth
multica very low. provided by the PON port to
st l On the OLT, run the display igmp multicast programs to meet the
bandwi config global command to verify total bandwidth requirement of
dth that the bandwidth management ONU multicast users. Order the
assigne function (Bandwidth management program again.
d to the switch) is enable.
PON
port is l On the OLT, run the display igmp
very bandwidth port command to query
low. the bandwidth (Max bandwidth)
assigned to the PON port and the
used bandwidth (Used bandwidth).
The remaining bandwidth (the
maximum bandwidth - the used
bandwidth) is lower than the
bandwidth of the ordered program.
l The bandwidth assigned to the PON
port is very small, which does not
meet the total bandwidth
requirement of ONU multicast
users.


e
Cause
The If the following two queried results are Modify the ONU multicast mode
ONU different, the fault is because the ONU configured on the OLT to match
multica multicast mode configured on the OLT the actual multicast mode
st mode mismatches the actual multicast mode configured on the ONU.
configu configured on the ONU. NOTE
red on l On the OLT, run the display ont In the GPON access mode, run the
the OLT info command to query the multicast mode command on the
mismat OLT to modify the ONU multicast
multicast mode of the ONT. That is, mode.
ches the the ONU multicast mode
actual configured on the OLT.
multica
st mode l On the ONU, run the display igmp
configu config vlan command to query the
red on actual IGMP mode of the ONU.
the
ONU.

Step 5 Check the upper-layer network and devices of the OLT.
Table 5-8 Troubleshooting method of faulty upper-layer network and devices of the OLT
e
Cause
The The program is not configured on the Add the program to the multicast
progra multicast server. server.
m is not TIP
configu If the user can watch the program, this is not
red on the cause.
the
multica
st
server.


e
Cause
The All users of the OLT or the ONU fail to Increase the TTL value of multicast
time to watch all programs configured on to the packets of the multicast server.
live multicast server.
(TTL) NOTE
value If the TTL value of multicast packets on the
set for upstream port of the OLT is smaller than 2,
the the OLT drops multicast packets.
multica
st
stream
of the
multica
st server
is very
small.
upper- server from the OLT separately. It is between the OLT and the multicast
layer found that the OLT fails to ping the router or the fault on the line
network multicast router and the multicast between the OLT and the multicast
commu server. server.
nication TIP
of the If other users of the OLT can watch the
OLT program, the network between the OLT and
fails. the multicast server is normal.
2. Order a program again and then check whether the user can watch the program successfully.
Step 7 End.
----End
5.2.3 Pixelation in a Multicast Program

Pixelation in multicast programs is a fault that a user is online and orders a program but the
quality of the program is poor, such as pixelation. When pixelation occurs in an FTTB or FTTC
network, locate the fault according to the following procedure.

Location Method
When pixelation occurs in an FTTB or FTTC network, Table 5-9 shows possible causes of the
fault in different scopes.

User terminal to the l The rate configured in the traffic profile bound to the traffic stream
ONU is lower than the bandwidth of the multicast program.
l The QoS rate limitation on the port is excessively low.
l If pixelation occurs only in program switching, the maximum
bandwidth used by the user may be higher than the downstream
line rate and the fast leave function may not be enabled.
l The STB is faulty.
l The TV set is faulty.
ONU to the OLT Packet loss occurs on the line between the ONU and the OLT.
Upper-layer l The multicast source is abnormal.

network and devices l The network quality is poor. The network communication failure
of the OLT occurs on the line between the OLT and multicast router, and
between the multicast router and multicast server.
CAUTION
Procedure
Step 1 Order a program again and perform the following steps to determine the location at which
multicast packets are lost.
1. On the OLT, run the display multicast flow-statistic vlan 3 ip 224.1.1.1 command to
the OLT upstream port. Then, go to Step 1.2.
loses packets before reaching the OLT upstream port. Then, go to Step 2.
2. On the ONU, run the display multicast flow-statistic ip 224.1.1.1 vlan 3 command to
the ONU upstream port. It is assumed that packets loss occurs on the ONU, user
terminal, or on the line between the ONU and the user terminal. Then, go to Step 4.

loses packets before reaching the ONU upstream port. It is assumed that the program
traffic loses packets on the line between the OLT and the ONU. Then, go to Step 3.
Step 2 Check the upper-layer network and devices of the OLT.
Table 5-10 Troubleshooting method of faulty upper-layer network and devices of the OLT

e
Cause
The Pixelation occurs when a user watches Replace the multicast source.
multica a program ordered from the multicast
st server.
source TIP
is If other users can watch the program
abnorm successfully, the multicast source is
al. normal.
upper- server from the OLT separately. It is between the OLT and the multicast
layer found that packet loss occurs. router or the fault on the line
network TIP between the OLT and the multicast
quality If other users of the OLT can watch the server.
of the program, the network between the OLT and
OLT is the multicast server is normal.
poor.
3. Check whether packets are lost on the upstream port of the OLT.
l If the packets are lost on the upstream port of the OLT, go to Step 6.
l If no packet is lost on the upstream port of the OLT, the fault on the line between the
OLT and the multicast server is rectified. Then, troubleshoot the fault in other fault
scopes according to the location where packet loss occurs and go to Step 1.
Step 3 Check the line between the OLT and the ONU.
1. On the OLT, run the display alarm history all command to query historical alarms and
run the display event history all command to query historical events to check whether
alarms or events related to the PON line (line between the OLT and the ONU) are generated
on the OLT.
l If such alarms or events are generated, clear them by referring to the relevant instruction
documents. Then, go to Step 3.2.
l If no such alarms or events are generated, go to Step 4.


Step 4 Check the ONU.
Table 5-11 Troubleshooting method of incorrect configurations on the ONU

e
Cause
The rate On the ONU, run the display service- Bind a new traffic profile to
configu port command to query the index of the multicast streams.
red in Rx traffic and then run the display l If a correct traffic profile is in
the traffic table ip command to query the the system, run the service-
traffic PIR of the traffic profile. The PIR is port 100 outbound traffic-
profile smaller than the bandwidth of the table index 6 command on the
bound ordered program. ONU to bind the traffic profile
to the NOTE (assume that the index of the
traffic If the PIR is smaller than the bandwidth of multicast traffic streams is 100
and the index of the traffic
is lower are lost and pixelation occurs. If the PIR is
very small, the blank screen may occur profile is 6) to the multicast
than the streams again.
bandwi are lost.
dth of l If the currently configured
If the service port carrying the multicast traffic profile does not meet the
the streams carries streams of other services,
multica requirement, run the traffic
st table ip command on the ONU
progra other services may occupy the majority of to add a new profile that meets
m. traffic streams, which leads to insufficient the requirement and then bind
multicast bandwidth. As a result, the the profile to the traffic streams.
pixelation occurs.
provider.
be used.


e
Cause
The On the ONU, run the display qos-info On the ONU, run the traffic-limit
QoS traffic-limit port command to query command to change the target rate
rate the target rate of the port and then to an appropriate value or run the
limitati compare the target rate with the undo traffic-limit command on
on on bandwidth of the ordered program. The the ONU to cancel the traffic
the port target rate is lower than the bandwidth limitation on the port.
is of the ordered program.
excessi NOTE
vely If the user port carries other services (such
low. as the Internet access service), the traffic of
all services must be lower than or equal to
the target rate. Otherwise, other services
may occupy the majority of traffic streams,
which leads to insufficient multicast
bandwidth. As a result, the pixelation
occurs.


e
Cause
The If one of the following symptoms On the ONU, run the igmp user
maximu occurs, the fault is because the modify user-index max-
m maximum bandwidth of the user is bandwidth command to modify
bandwi higher than the downstream line rate the maximum bandwidth of the
dth of and the fast leave function is not user to be lower than the line rate.
the user enabled.
is l Pixelation occurs only when
higher programs are switched.
than the
downstr l Run the display igmp user user-
eam line index command to query the fast
rate and leave attribute (Quick leave) and
the fast the maximum bandwidth of the
leave program (User MaxBandWidth).
function The Quick leave is disable and the
is not maximum bandwidth is higher than
enabled the downstream line rate.
. NOTE
using a remote controller, two IGMP
packets are transmitted at the same
time, including one leave packet and
one join packet. Before the previous
program stops, traffic of two programs
exists over the subscriber line. If no
sufficient bandwidth is available for the
traffic of two programs over the line,
packet loss occurs due to traffic
overflow. As a result, pixelation occurs.
frequently, traffic of multiple multicast
groups exists over the line.
l After the maximum bandwidth of a user
is limited, the user cannot order a new
program if the bandwidth of the new
ordered program is larger than the value
(the maximum bandwidth - the used
bandwidth). This ensures that the
program that is being watched is not
affected.

Table 5-12 Troubleshooting method of faulty user terminal

e
Cause
The The fault is rectified after the STB is Reset or replace the STB.
STB is reset or replaced.
faulty.
The TV Pixelation persists after the TV cable is Contact the TV set maintenance
set is connected to another video input device engineer to troubleshoot the TV set
faulty. such as a DVD player or VCR player. fault.
Step 7 End.
----End

Prerequisites
NOTE
5.3.1 No Power Feed After Offhook

This section describes how to troubleshoot the fault where there is no power feed when the phone
goes offhook. When this fault occurs, the phone does not respond after going offhook, and the
phone in-use indicator is off, which means that the phone has no power feed.
Location Method

Start
Identify the fault

scope
ports ports on some boards on the device

functional

circuit lines are functional
Check whether the

Check whether the user Check whether the power
service boards are
ports are functional board is functional
functional
Check whether the device

hardware and ambient
environment are normal
End
CAUTION
Procedure
Step 1 Check whether the fault always occurs on certain ports, occurs on all the ports on certain boards,
or occurs on all the ports on the entire MA5612.
l If the fault always occurs on certain ports, go to Step 2.
l If the fault occurs on all the ports on certain boards, go to Step 7.
l If the fault occurs on all the ports on the entire MA5612, go to Step 8.
Step 2 Replace the phone with another and check whether the fault is rectified.

NOTE

Step 6 Use another port on the same board and check whether the fault is rectified.
Step 7 Replacing the service board and check whether the fault is rectified.
Step 8 Check whether the power board is working properly by referring to the power supply indicator
status on the board. For the status description of the power supply indicators, see A.1
Indicators .
Step 9 Replace the power board with anther one. Then, check whether the fault is rectified.
Step 10 Check MA5612 hardware and the ambient environment.

1. Ensure that the device is grounded according to requirements. For details, see 2.1 Checking
the Grounding of the Device. Check whether the fault is rectified.
l If the control board is inserted properly, go to Step 11.

Assistance).
Step 12 End.
----End
5.3.2 No Tone After Offhook

This section describes how to troubleshoot the fault where there is no dial tone or only a weak
current sound when a phone goes offhook.
Fault Location

Start
Identify the fault

scope.
ports. ports on some boards. on the device.

functional.

circuit lines are functional.
Check whether the Check whether the DSP

Check whether the user
service boards are daughter board are properly.
ports are functional.
functional.
Check whether the


End
CAUTION
Procedure
Step 1 Identify the fault scope.
l If the fault occurs on some ports, go to Step 2.
l If the fault occurs on all ports on some boards, go to Step 7.
l If the fault occurs on all ports on the device, go to Step 8.
Step 2 Replace the phone with a functional one and check whether the fault is rectified.
Step 3 Run the pots loop-line-test command to perform a 8.4 POTS Subscriber Loop Line Test on
the affected port. Check whether Conclusion is Normal.
l If Conclusion is Normal, go to Step 5.

l If Conclusion is not Normal, rectify the fault based on the displayed test conclusion. Then,
go to Step 4.
NOTE
For example, if Conclusion is Phone not connected, the phone is faulty or the line between the phone
and the device is not connected properly. In this case, replace the phone or ensure that the line is connected
properly.

Step 5 Run the pots circuit-test command to perform a 8.3 POTS Subscriber Circuit Line Test on
the affected port.
l If the results of all test items are Normal, the user port is functional. Go to Step 8.
l If the results of only some test items are Normal, the user port is faulty. Go to Step 6.
Step 6 Connect the phone to another port on the same board, and check whether the fault is rectified.
l If the fault is rectified, the original user port is faulty. Go to Step 16.
Step 7 Replace the voice service board and check whether the fault is rectified.
Step 8 Run the display boardframeid/slotid command to check whether the state of the DSP daughter
board is Normal.
l If the state is Normal, go to Step 9
l If the state is not Normal, go to Step 15
Step 9 Run the display pstn state command to check whether CTPAdmState of the affected POTS
port is StartSvc.
l If CTPAdmState is not StartSvc, go to Step 10.
Step 10 Run the undo endservice command to reactivate the service on the port, and check whether the
fault is rectified.
Step 11 Ensure that the media gateway (MG) interface is functional. Then, check whether the fault is
rectified.
NOTE
Check whether the following conditions are met:
l Run the display if-h248 all command in H.248 mode or the display if-sip all command in SIP mode to
check whether the media gateway (MG) interface is working properly.
l Check whether the MG interface configuration on MA5612 is the same as that on the interconnected media
gateway controller (MGC).
l Check whether the MA5612 communicates with the MGC properly.

Step 12 Check whether the data configuration on MA5612 conforms to the data plan.
l If the data configuration conforms to the data plan, go to Step 14.
l If the data configuration does not conform to the data plan, go to Step 13.
Step 13 Take the phone off the hook to check whether the fault is rectified.
Step 14 Have a softswitch engineer check whether the softswitch data configuration conforms to the data
plan. If any inconsistency is found, make necessary modifications to ensure data consistency.
Then, check whether the fault is rectified.
Assistance).
Step 16 End.
----End
5.3.3 Busy Tone After Offhook

Busy tone after offhook indicates that when a subscriber picks the phone off the hook, only a
busy tone is heard.
Location Method

Start
Confirm the voice protocol type
H.248 protocol SIP protocol
Check MG interface attributes Check SIP interface attribu
Check the data of MGC

subscribers
Check the RTP format of the MG
Check whether the subscriber

line is normal
End
CAUTION
Procedure
Step 1 Run the display alarm history all command to query the historical alarms and then run the
display event history all command to query the historical events. Check whether the alarms or
events related to the fault are generated.

l If such alarms or events are generated, clear these alarms or events to rectify the fault
according to the relevant guide. Then, proceed to Step 2.
l If such alarms or events are not generated, go to Step 3.
NOTE
The related alarms or events include the following:

l 0x38100005 DSP resources for voice services are insufficient
l 0x3b000002 Remote blocking
l 0x1a010001 H.248 interface interruption
l 0x13010001 Communication between the VAG and the SIP proxy server is interrupted
Step 3 Run the display protocol support command to query the current used voice protocol.
l If the H.248 protocol is used, proceed to Step 4.
l If the SIP protocol is used, go to Step 13.
Step 4 In the H.248 mode , run the reset coldstart command to reset the MG interface and make the
subscriber register again. If registration is successful, run the display pstn state command in
the global config mode to check whether the service management state (CTPAdmState) of the
POTS port is StartSvc.
CAUTION
services.

Step 5 In the H.248 mode, run the display if-h248 attribute mgid command to check whether MG
interface attributes are the same as those configured on the MGC.
l If MG interface attributes are the same as those configured on the MGC, go to Step 7.
l If MG interface attributes are different from those configured on the MGC, run the if-h248
attribute command in the H.248 mode to modify MG interface attributes to be the same
as those configured on the MGC. Run the reset coldstart command to reset the MG
interface. Then, proceed to Step 6.
test with the phone on the hook.
l If the test result (shown in Conclusion) is Normal, the subscriber line and the phone are
normal. Then, go to Step 9.

NOTE
If the test result shown in Conclusion is Phone not connected, the phone is faulty or the line between the
phone and the MA5612 is not properly connected. In this case, replace the phone or check whether the
line is connected properly.
Step 9 On the MGC, query subscriber data and check whether data of the subscriber who encounters
the fault is configured on the MGC.
l If data of the subscriber who encounters the fault is configured on the MGC, go to Step
11.
l If data of the subscriber who encounters the fault is not configured on the MGC, configure
such data on the MGC. Then, proceed to Step 10.
Step 11 On the MGC, trace H.248 signaling, and check whether error 502 is contained in H.248 signaling.
l If error 502 is contained in H.248 signaling, run the tid-template modify command to
modify the terminal ID format of the MG to be the same as that of the MGC. In the H.248
mode, run the reset coldstart command to reset the MG interface and make the subscriber
register again. Then, go to Step 14.
l If error 502 is not contained in H.248 signaling, go to Step 15.
NOTE
In the protocol, error 502 is defined as invalid termination point, including RTP termination point and
physical termination point. On the MGC, if the traced H.248 signaling contains error 502, it indicates that
the terminal ID format of the MG is different from that of the MGC. For example, RTP configured on the
MGC is in a progressively increase format of RTP1000, RTP1001 and RTP1002; however, RTP configured
on the MG is in a progressively increase format of RTP500, RTP501 and RTP502.
Step 12 In the SIP mode, run the reset command to reset the SIP interface and make the subscriber
register again. If registration is successful, run the display pstn state command in the global
config mode to check whether the service management state (CTPAdmState) of the POTS port
is StartSvc.
CAUTION
services.


Step 13 In the SIP mode, run the display if-sip attribute mgid command to check whether SIP interface
attributes are the same as those configured on the IMS.
l If SIP interface attributes are the same as those configured on the IMS, go to Step 15.
l If SIP interface attributes are different from those configured on the IMS, run the if-sip
attribute basic command in the SIP mode to modify SIP interface attributes to be the same
as those configured on the IMS. Run the reset command to reset the SIP interface. Then,
proceed to Step 14.
Assistance).
Step 16 End.
----End
5.3.4 Continuous Dial Tone During Dialing

This section describes how to troubleshoot the fault where the dial tone does not stop when the
user begins to dial. The dial tone should stop when the user dials a number.
Location Method
Start

working properly
Check whether the gain of a user

port is set to a very small value
Check whether the input gain of the

DSP chip is set to a very small value
Check whether any of the ports on

the same service board or adjacent
service boards are locked
Check whether the subscriber and

circuit lines are normal
End
CAUTION

Procedure
Step 2 Check whether the gain of the user port is set properly.
1. In pstnport mode, run the display pstnport electric frameid/slotid/portid command to
check whether Sendgain and Recvgain of the affected port are set properly.
l If they are set properly, go to Step 3.
l If they are not set properly, go to Step 2.2.
2. Run the pstnport electric set command to set the gain of the affected port again. Then,
NOTE
gain is changed.
l If the fault is rectified when the gain is set to a certain value, go to Step 11.
l If the fault is not rectified when the gain is set to a certain value, go to Step 3.
Step 3 Check whether the gain of the DSP chip is set properly.
1. In ESL user mode, run the display mgpstnuser attribute command to check whether the
gain of the DSP chip is set properly.
l If the gain of the DSP chip is set properly, go to Step 4.
l If the gain of the DSP chip is not set properly, go to Step 3.2.
2. In ESL user mode, run the mgpstnuser attribute set frameid/slotid/portid dsp-input-gain
dsp-input-gain-value dsp-output-gain dsp-output-gain-value command to change the gain
of the DSP chip. Then, check whether the service is restored.
NOTE
gain is changed.
Step 4 In privilege mode, run the display pstn state command check the status of PSTN ports on the
same service board or adjacent service boards. To be specific, check whether CTPSrvState is
Locked.
l If CTPSrvState is Locked, go to Step 5.
l If CTPSrvState is not Locked, go to Step 6.
Step 5 Unblock the blocked ports and check whether the service is restored.
NOTE
Unblock the blocked ports by hanging up the phone or clearing the shorted wires within the same twisted pair.


NOTE

Step 9 User another user port and check whether the service is restored.
l If the service is restored, the original user port is faulty. Allocate another port for the user.
Then, go to Step 11.
Assistance).
Step 11 End.
----End
5.3.5 Called Party's Phone Does Not Ring

This section describes how to troubleshoot the fault where the called party's phone does not ring
when called. However, if the called party picks up the phone, the call is still connected.
Location Method

Start

working properly
Check whether the subscriber line

is normal
Check whether the service boards

are working properly

working properly
Check whether the power supply

system of the device is working
properly
Check whether the device hardware

and ambient environment are
normal

issues the ringing signaling to the
called party
End
CAUTION
Procedure
NOTE


Step 5 Check whether the power supply indicator on the power board is working properly. For the status
description of the power supply indicator, see A.1 Indicators .
l If the power supply indicator is working properly, go to Step 9.
l If it is not working properly, go to Step 6.
Step 7 Check whether the power supply system is stable. Specifically, check whether the voltage is
stable and whether the system is frequently powered off.
l If the power supply system is stable, go to Step 9.
l If the power supply system is not stable, go to Step 8.
Step 8 If the power supply system is not stable because of certain objective causes (for example, there
is a large electromechanical device), use a stable standby power source, such as the battery.
Step 9 Check the hardware of the MA5612 and the ambient environment.
1. Ensure that the device is grounded properly. For details, see 2.1 Checking the Grounding
of the Device. Then, check whether the fault is rectified.
l If the control board is inserted properly, go to Step 9.4.
3. Check whether the service is restored.

Step 10 Track the signaling to check whether the softswitch issues the ringing signaling to the called
party.
l If the softswitch issues the ringing signaling to the called party, go to Step 11.
l If the softswitch does not issue the ringing signaling to the called party, contact softswitch
engineers to locate the fault, go to Step 12.
Assistance).
Step 12 End.
----End
5.3.6 One-Way Audio or No Audio During Communication

This section describes how to troubleshoot the fault where only one party (one-way) or neither
party in a call can hear the other party. Regardless of whether there is one-way audio or no audio,
the called party's phone still rings.
Location Method
Start

working properly
Check whether the link between

the MA5612 and the MG is
normal
Check whether the route

configuration on the MA5612 is
correct
Check whether the ACL rules are

configured correctly on the
MA5612 and the bearer network
End

NOTE
This fault is generally caused by an incorrect route configuration on the device or the bearer network. The
signaling stream is deemed normal because the phone's abilities to dial and ring are normal. In this case, users
connected to the same MA5612 can locate the cause by calling each other.
l If the users can call each other successfully, the channel between the device and the bearer network is
faulty.
l If the users cannot call each other, the device is faulty.
CAUTION
Procedure
Step 1 Replace the phone to redial a number and check whether the fault is rectified.
l If the fault is rectified, the original phone is faulty and needs to be replaced, go to Step
11.
Step 2 Check whether users connected to the MA5612 can call each other.
l If users can call each other, go to Step 5.
l If they cannot call each other, go to Step 3.
Step 3 Run the display acl all command to check whether an ACL rule is filtering out the upstream or
downstream voice media stream.
l If an ACL rule is filtering out the upstream or downstream voice media stream, run the
undo acl command to delete the ACL rule. Then, go to Step 4.
l If no ACL rule is filtering out the upstream or downstream voice media stream, go to Step
10.
NOTE
The ACL rule issued to a port cannot be deleted, but you can cancel the application of the ACL rule by
running the undo packet-filter command.

Step 5 Run the Ping command on the MA5612 to check whether the link between the MA5612 and
the MG is normal.
l If the IP address of the MG can be pinged, go to Step 8.
l If the IP address of the MG cannot be pinged, go to Step 6.
Step 6 Run the display ip routing-table command to check whether the route configuration on the
MA5612 is correct.
l If the route configuration is correct, go to Step 8.
l If the route configuration is incorrect, run the ip route-static command to reconfigure the
route. Then, go to Step 7.


Step 8 Check whether the ACL rules are configured correctly on the bearer network.
l If the ACL rules are configured correctly, go to Step 10.
l If they are not configured correctly, modify or cancel them as needed. Then, go to Step
9.
Assistance).
Step 11 End.
----End
5.3.7 Noise in Communication

Noise in communication indicates that a subscriber hears a strong current noise and broadcast
noise in communication, but the noise does not include the environment noise of two parties.
Location Method

Start
Confirm
the fault scope.
The fault occurs on all The fault occurs on

subscribers of the device. subscribers of certain ports
on the device.
The electrical attributes of a

PSTN port does not comply
with the local standard.
The input and output gains

of the DSP chip do not
comply with the local
standard.
The DDF and grounding do

not comply with the local The subscriber line and the
standard. phone are faulty.
The voice board is faulty.
The electrical interference

exists in the device or
subscriber line environment.

CAUTION
Procedure
Step 1 Confirm the fault scope.
l If the fault occurs on all subscribers of the device, proceed to Step 2.
l If the fault occurs on subscribers of certain ports on the device, go to Step 7.
l If the fault occurs on subscribers using certain numbers, go to Step 11.
Step 2 Run the display pstnport electric command to query the electrical attributes of a PSTN port.
Check whether the impedance type, current type, transmit gain, and receive gain configured on
the faulty port are the same as those configured on a normal port.
port are the same as those configured on a normal port, proceed to Step 4.
port are different from those configured on a normal port, run the pstnport electric set
command to configure the electrical attributes of the PSTN port again to make the electrical
attributes to be the same as those configured on a normal port. Then, proceed to Step 3.
NOTE
When you need to configure the electrical attributes of the PSTN port in batches, you can run the pstnport
electric batset command.
Different countries and regions have different requirements on the electrical attributes. Therefore, the
configured electrical attributes must comply with the local standard and the interconnection parties must
have the same configurations. For example, the requirements for transmit and receive gains are as follows:
l China: The transmit gain and receive gain of the local network are 0 dB and -3.5 dB respectively. The
transmit gain and receive gain of the toll network are 0 dB and -7 dB respectively.
l Other countries and regions: Generally, the transmit gain the receive gain of the local network and toll
network are 0 dB and -7 dB respectively.
Step 4 Run the display mgpstnuser attribute command to query the attributes of a PSTN subscriber,
and check whether the input and output gains of the DSP chip configured on the faulty port are
the same as those configured on a normal port.
l If the input and output gains of the DSP chip configured on the faulty port are the same as
those configured on a normal port, go to Step 6.
l If the input and output gains of the DSP chip configured on the faulty port are different
from those configured on a normal port, run the mgpstnuser attribute setframeid/slotid/
portiddsp-input-gaindsp-input-gain-valuedsp-output-gaindsp-output-gain-value
command to configure the attributes of the PSTN subscriber again and make the attributes
to be the same as those configured on a normal port. Then, proceed to Step 5.

Step 6 Check whether DDF and MA5612 grounding complies with the local standard. Call each other
again to check whether the fault is rectified.
Step 7 Run the pots loop-line-test command to perform a loop-line test for the board where a fault
occurs.
l If the test result is normal, it indicates that the external line and the phone are faulty. Then,
go to Step 9.
l If the test result is that the MA5612 is not connected to a phone, it indicates that the phone
is faulty or the cable between the phone and the MA5612 is not properly connected. In this
case, replace the phone and make sure that the cable between the phone and the MA5612
is properly connected. Then, proceed to Step 8.
l If the test result is others such as line B grounding, it indicates that external lines are faulty.
In this case, troubleshoot the fault according to the prompt message. For example, if the
test result is line B grounding, it indicates that line B may be damaged. In this case, replace
the line B, and then proceed to Step 8.
NOTE
The qualitative loop-line test conclusions include: normal, touch the power line, line A mixed with other lines,
line B mixed with other lines, lines A and B mixed with other lines, line A grounding, line B grounding, lines
A and B grounding, self-mixing (small resistance and self-touch wire), A-B insulation difference, line A leakage,
line B leakage, lines A and B leakage, phone set not connected, offhook, and unknown.
Step 9 Check the voice board for the subscriber who encounters the fault. Call each other again to check
Step 10 Check the environment for the MA5612, and external lines to troubleshoot electrical interference
of the broadcast tower and high voltage cables. Call each other again to check whether the fault
is rectified.
Step 11 Check configurations related to numbers of the softswitch and voice gateway. Compare the
configurations of the faulty numbers with those of the normal numbers and modify the
configurations of the faulty numbers to be the same as those of the normal numbers. Call each
other again to check whether the fault is rectified.
Assistance).

Step 13 End.
----End
5.3.8 Discontinuous Communication

This section describes how to troubleshoot the fault where the call is discontinuous.
Fault Location
Start

working properly
Check whether the QoS

priority of the voice service is
set properly
Check whether the quality of

the bearer network meets
voice service requirements
end
CAUTION
Procedure
Step 1 Replace the phone and check whether the fault is rectified.
Step 2 In VoIP mode, run the display qos ip and display qos vlan commands to check whether the
QoS priority of the voice service is set properly.
l If the QoS priority of the voice service is set properly, go to Step 4.
l If the QoS priority of the voice service is not set properly, go to Step 3.
NOTE
l When packet loss occurs due to network congestion, the packets whose QoS priorities are the lowest
are discarded firstly. The QoS priority ranges from 0 to 7 from low to high.
l The voice service has high requirements on network quality. Therefore, users are recommended to set
the priority of the VoIP service on the MA5612 to 6.

Step 3 Run the qos ip command to set the QoS priorities of the media IP address and signaling IP
address to high values. Run the qos vlan command to set the VLAN priorities of the media IP
address and signaling IP address to 6. Then, check whether the fault is rectified.
Step 4 Check whether the quality of the bearer network meets voice service requirements.
NOTE
Users can use a tool to check whether the quality of the bearer network meets voice service requirements. Users
can also run the ping command on the MA5612 to check whether the IP address of the media gateway (MG)
can be pinged. That is, check whether serious packet loss occurs.
l If serious packet loss occurs, go to Step 5.
l If serious packet loss does not occur, go to Step 6.
Step 5 Check whether the network connection between the MA5612 and the MG is normal and whether
the transmission devices are normal. If there are certain faults on the network or devices, rectify
the faults and ensure that the MG can be pinged from the MA5612 and that no serious packet
loss occurs. Then, check whether the service is restored.
Assistance).
Step 7 End.
----End
5.3.9 Low Communication Voice

This section describes how to troubleshoot the fault where the voices heard by both the calling
party and called party, or one of the two parties, in a voice over IP (VoIP) public switched
telephone network (PSTN) service is very low.
Location Method

Start
Check whether the phone is working

properly
Check whether the loop and circuit

lines are normal
Check whether the service board to

which the affected user is connected
is working properly
Check whether the voice gain of the

PSTN port is set to a very
small value
Check whether the output gain of the

DSP chip is set to a very
small value

working properly
Check whether the hardware and the

ambient environment are normal
End
CAUTION
Procedure
Step 1 Replace the phone with another. Then, check whether the service is restored.
Step 2 Perform a 8.4 POTS Subscriber Loop Line Test with the phone on the hook.
l If the test result (shown in Conclusion) is Normal, the subscriber line is normal. Then, go
to Step 4.
NOTE
When you rectify the fault based on the test result, the phone is faulty or the line between the phone and
the MA5612 is not properly connected if the test result shown in Conclusion is AB all break off or no
phone connected. In this case, replace the phone or check whether the line is connected properly.


Step 4 Perform a 8.3 POTS Subscriber Circuit Line Test with the phone on the hook.
l If the results of all test items are normal, the voice service board is normal. Then, go to
Step 7.
l If the results of all test items are not normal, the voice service board is faulty. Then, go to
Step 5.
Step 5 Perform the test on another port on the same board.

Step 6 Replacing the service board to test whether the fault is rectified.
Step 7 In pstnport mode, run the display pstnport electric command to query the electrical attributes
of the PSTN port. Check whether the impedance type, current type, transmit gain, and receive
gain of the affected port are the same as those of a normal port.
l If the electrical attributes of the PSTN port are the same as those of a normal port, go to
Step 9.
l If they are different, run the pstnport electric set command to reconfigure the electrical
attributes of the PSTN port to ensure that they are the same as the attributes of a normal
port. Then, go to Step 8.
NOTE
Users can run the pstnport electric batset command to configure electrical attributes of multiple PSTN
ports in batches.
Different countries and regions require different electrical attributes. Therefore, ensure that the configured
electrical attributes comply with local standards and interconnected devices use the same electrical
attributes.

Step 9 In ESL user mode, run the display mgpstnuser attribute command to query the PSTN user
attributes and check whether the input and output gains of the DSP chip used on the affected
port are the same as those used on a normal port.
l If they are the same, go to Step 11.
l If they are different, run the mgpstnuser attribute set frameid/slotid/portid dsp-input-
gain dsp-input-gain-value dsp-output-gain dsp-output-gain-value command to
reconfigure the PSTN user attributes of the port to ensure that the attributes are the same
as those of a normal port. Then, go to Step 10.


Step 11 Check whether the power board is working properly by referring to the status of power supply
indicators on the board. For the status description of the power supply indicators, see A.1
Indicators .
Step 13 Check the device hardware and the ambient environment.
1. Ensure that the device is grounded. For details, see 2.1 Checking the Grounding of the
Device. Then, check whether the fault is rectified.
l If there is no evidence of water or vermin, go to Step 13.4.
4. Check whether there is any source of high-frequency electromagnetic interference exists
around the MA5612 and the subscriber line. If there is such a source, remove it from the
area and check whether the fault is rectified.
Assistance).
Step 15 End.
----End

248 protocol.
Prerequisites

NOTE
5.4.1 Fax Service Failures

This section describes how to troubleshoot common fax service failures, such as when a fax fails
to send, the fax image is blurred, or the fax rate is low.
Location Method
CAUTION
Procedure
Step 1 Confirm that the user followed the instructions given in the user manual of the fax machine when
operating it and check whether the fax machine is faulty.

l If the user followed the instructions and the fax machine is normal, go to Step 3.
l If the user did not follow the instructions or the fax machine is faulty, go to Step 2.
NOTE
Fax machines are relatively error-prone, especially multi-function fax machines. If any faults occur when
using the fax services, use the following guidelines to identify the fault causes:
l Check whether the fax machine is connected properly.
l Check whether the user sending the fax pressed the start key before receiving the fax tone from the
peer fax machine.
l Check whether there is paper in the peer fax machine, the fax paper is jammed, the printer ink has run
out, the fax machine is not powered on, or whether some part of the fax machine is faulty.
l Some fax machines have a function that blocks incoming faxes without affecting the machine's ability
to send faxes. Check whether this function is enabled.
l If the fax machine is not automatically enabled to receive faxes, the user may have to push a button to
allow the machine to receive faxes.
Step 2 Rectify the fault on the fax machine, and then try to send or receive the fax again. Then, check
Step 3 Check whether the fax parameter configurations on the local MA5612 and peer MA5612 are
consistent with the data plan.
NOTE

l Run the display fax parameters command to query the fax parameter configurations. Verify that the value
for FAX transfers mode is consistent with that configured on the peer end. The fax coding and decoding
mode can be the transparent transmission mode or the T.38 mode.
l Run the display fax-modem parameters command to query the public fax parameter configurations. Verify
that the value for Rfc2198-start-mode is consistent with that configured on the peer end. The RFC 2198
protocol is used to improve data transmission reliability and service quality using the redundancy
transmission mechanism. This function must be enabled on both the MDU and the softswitch if the function
is used. Otherwise, the fax service will fail.
l Run the display dsp attribute command to query the digital signal processor (DSP) parameter
configurations.
l If the fax parameter configurations on the local MA5612 and peer MA5612 are consistent
with the data plan, go to Step 5.
Step 4 Modify the fax parameter configurations to ensure that they are consistent with the data plan,
and then check whether the service is restored.
NOTE
l Run the fax parameters command to modify the fax parameter configurations.
l Run the fax-modem parameters command to modify the public fax parameter configurations.
Step 5 Have an MGC maintenance engineer check whether the fax service data configurations on the
MGC are consistent with the data plan.

l If the configurations are not consistent with the data plan, go to Step 6.
Step 6 Have the MGC maintenance engineer modify the fax service data configurations on the MGC
so that they are consistent with the data plan. Then, check whether the service is restored.
Step 7 Check whether the quality of the bearer network meets the requirements for the fax service.
NOTE
Users can use an associated tool to test the bearer network quality or run the ping command on the MA5612 to
ping the peer access gateway (AG).
In transparent transmission mode, the packet loss ratio for fax services must be less than 0.5%.
Step 9 In the onhook state, perform a 8.4 POTS Subscriber Loop Line Test.
l If the test result (shown in Conclusion) is not Normal, the subscriber line is faulty. Connect
a fax machine to the main distribution frame (MDF) and perform a test to determine the
location of the fault. Rectify the fault as needed, for example, by replace the subscriber
line. Then, go to Step 10.

Step 11 Perform a test on another port on the same board to check whether the service is restored.
Assistance).
Step 14 End.
----End

5.4.2 Modem Service Failures

This section describes how to troubleshoot common modem service failures, such as when dial-
up Internet access fails or the modem goes offline repeatedly. Common modem services include
the lottery service and point of sale (POS) service.
Location Method
CAUTION
Procedure
Step 1 Replace the modems of the calling and called party with phones, and check whether the two
parties can communicate with each other normally.
l If the two parties can communicate with each other, go to Step 2.
l If the two parties cannot communicate with each other, address the problem by referring
to 4.3 Troubleshooting VoIP PSTN Service .
Step 2 Replace the called party phone with a modem. Use the calling party phone to call the called party
modem. Check whether the modem tone can be heard when the call is connected.
l If the modem tone can be heard, go to Step 4.

l If the modem tone cannot be heard, the called party modem cannot automatically start the
modem service. Check the modem configurations to ensure that it can automatically start
modem service. Then, go to Step 3.

Step 4 Check whether the modem parameter configurations on the local MA5612 and peer MA5612
are consistent with the data plan.
NOTE

l Run the display modem parameters command to query the modem parameter configurations.
l Run the display fax-modem parameters command to query the public modem parameter configurations.
l Run the display dsp attribute command to query the DSP parameter configurations.
l If the modem parameter configurations on the local MA5612 and peer MA5612 are
consistent with the data plan, go to Step 6.
Step 5 Modify the modem parameter configurations so they are consistent with the data plan, and then
NOTE
The modification method is as follows:

l Run the modem parameters command to modify the modem parameter configurations.
l Run the fax-modem parameters command to modify the public modem parameter configurations.
Step 6 Have an MGC maintenance engineer check whether the modem service data configurations on
the MGC are consistent with the data plan.
Step 7 Have the MGC maintenance engineer modify the modem service data configurations on the
MGC so that they are consistent with the data plan. Then, check whether the service is restored.
Step 8 Check whether the quality of the bearer network meets the requirements of the modem service.
NOTE
Users can use a tool to test the bearer network quality or run the ping command on the MA5612 to ping the peer
access gateway (AG). The packet loss ratio must be less than 0.5%.

Step 10 Run the dsp attribute command on the MA5612 to change the static initial jitter buffer value
(the normal-fixed-jb parameter) of the DSP channel to double the packetization duration. (The
packetization duration can be queried on the MGC.) Then, check whether the service is restored.
Assistance).
Step 12 End.
----End

Maintenance Guide 6 System Fault Handling
6 System Fault Handling
About This Chapter
This topic describes how to handle the following typical faults of the MA5612.
6.1 Abnormal ONU Status in GPON Upstream Transmission

This section describes what to do if an optical network unit (ONU) is abnormal when the
MA5612 uses a gigabit-capable passive optical network (GPON) port for upstream transmission.
An ONU can be an optical network terminal (ONT) or a multi dwelling unit (MDU). In this
document, the MA5612 is considered an ONU.
6.2 NMS Fails to Manage a Device
If the NMS fails to manage the device, it means that the NMS loses control over the MA5612.
6.3 The Alarm Information Fails to Be Displayed on the NMS
If the alarm information fails to be displayed, it means that the NMS server does not display the
corresponding alarm information when the MA5612 generates an alarm.
6.4 Service Board Is in the Failed State
This section describes how to troubleshoot the fault when the service board of the MA5612 is
in the failed state.
6.5 A Service Board Fails to Register
This topic describes how to troubleshoot a fault when a service board of an MA5612 fails to
register.
6.6 Repeated Board Reset
This section describes how to troubleshoot the repeated reset of a service board on the
MA5612.
6.7 Unexpected Reset of the System
This section describes how to troubleshoot unexpected reset of the system. When the system is
reset unexpectedly, all services carried on the device are interrupted and the device cannot be
managed by the network management system (NMS).

6.1 Abnormal ONU Status in GPON Upstream

Transmission
This section describes what to do if an optical network unit (ONU) is abnormal when the
MA5612 uses a gigabit-capable passive optical network (GPON) port for upstream transmission.
An ONU can be an optical network terminal (ONT) or a multi dwelling unit (MDU). In this
document, the MA5612 is considered an ONU.
6.1.1 GPON ONU Registration Failure

The ONU registration failure is a fault in which the values of Run state, Config state, and
Match state of an ONU are abnormal as queried by running the display ont info command on
the OLT.
l The ONU running status refers to the current running status of the ONU. It indicates whether
the ONU is online and whether the ONU can carry service. The ONU status is classified
into three types: ONU Run state, ONU Config state, and ONU Match state.
– If the ONU running status is offline, the OLT cannot issue any command to the ONU.
– If the ONU running status is online. In this case, whether the service can be forwarded
is determined by the ONU configuration status.
l The ONU configuration status indicates whether the configuration restoration is enabled
and whether the configuration restoration is complete. The ONU configuration status has
the following states: initial, normal, configuring (config), and configuration failure (failed).
When an ONU goes online, the ONU is in the configuration restoration stage.
– The first status is initial. Soon the initial is complete and the ONU enters the config
state.
– In the config state, the ONU capability and configuration data are restored. The duration
of the config state is determined by the amount of the data configured on the ONU.
– If the configuration restoration is successful, the ONU transitions from the config state
to the normal state.
– If the configuration restoration fails, the ONU transits from the config state to the failed
state and the service cannot be carried forward.
l The ONU matching status indicates whether the actual ONU capability is the same as the
service profile bound to the ONU. The status includes: initial, mismatch, and match. To
some extent, the matching status is determined by the ONU running status and configuration
status.
– The matching status of the ONU can be queried only when the ONU running status is
online and the configuration status is normal. The matching status is match when the
hardware capability is the same as the ONU service profile bound with the ONU.
Otherwise, the status is mismatch.
– In other configuration states, the matching status is initial.
– The ONU matching status does not affect the normal forwarding of the service flow,
and only indicates whether the actual ONU capability is the same as the service profile
bound to the ONU.

Failure to Go Online of a GPON ONU

An ONU connected to a GPON port of an OLT fails to go online normally, but the queried Run
state of the ONU is displayed as offline by running the display ont info command on the OLT.
Location Method
NOTE
Going online refers to a process that after being powered on, an ONU registers with an OLT and sets up a
management channel with the OLT. An ONU can be managed by the OLT and be configured with services
only after going online.
When an ONU fails to go online, locate the fault based on the following fault symptoms and
possible causes.
Fault Symptom Possible Cause

Scope
OLT A single ONU or some l The SN or password configured on the OLT is

ONUs connected to an different from the actual SN or password of the
OLT fail to go online. ONU; hence, the ONU fails to pass
authentication and go online.
l The actual distance between the ONU and OLT
exceeds the ranging compensation distance
configured on the OLT.
l The OLT deactivates the ONU.
All the ONUs connected to l The laser on the PON port is disabled.
a PON port of an OLT fail l The pluggable optical module of the PON is
to go online. faulty.
l The PON port is faulty.
All the ONUs connected to l The board or the slot is faulty.

a board of an OLT fail to go
online.


Scope
ODN A single ONU or some l The branch fiber is bent excessively.

NOTE ONUs connected to an l The branch fiber connector is not clean.
ODN OLT fail to go online.
failures l The quality of branch fiber splicing is poor. For
are example, the splicing point has air bubbles.
generally l Different types of branch fiber connectors are
caused by
large
interconnected.
reflection l The multi-mode optical fiber is used as the
and branch fiber.
attenuatio
n caused l The ODN is not properly planned. For
by example, the split ratio, network coverage and
improper attenuation difference are not planned within
optical the proper ranges.
compone
nts, l The optical attenuation of the optical path is
design, or excessively small.
constructi
on.
l A branch fiber break occurs.
l The optical splitter is faulty or the connectors
on the optical splitter are not clean.
All the ONUs connected to l The backbone fiber is bent excessively.

a PON port of an OLT fail l The backbone fiber connector is not clean.
to go online.
l The quality of branch fiber splicing is poor. For
example, the splicing point has air bubbles.
l Different types of backbone fiber connectors
are interconnected.
l The multi-mode optical fiber is used as the
backbone fiber.
l A backbone fiber break occurs.
ONU A single ONU or some l The ONU is not powered on.

ONUs connected to an l The information (including SN and password)
OLT fail to go online. for ONU authentication conflicts; hence, the
later power-on ONU fails to go online.
l A rogue ONU (such as a continuous-mode
ONU) exists on the network and affects other
ONUs.
l The ONU hardware is faulty.
l The optical module of the ONU is faulty.
l The Patch cord of the ONU is broken or bent
excessively.

CAUTION
The parameters of the optical module in this topic comply with Class B+. Note that such
parameters are slightly different from the parameters in Class C.
Procedure
Step 1 When the queried Run state of the ONU is displayed as offline, check whether the OLT
generates the following alarms. If such alarms are generated, clear them and check whether the
fault is rectified. If the fault persists, proceed to Step 2.
The following alarms may be generated:
l 0x2e305015 The authentication information of the ONTs conflicts
l 0x2e314021 There are illegal incursionary rogue ONTs under the port
l 0x2e314022 The ONT is rogue ONT
l 0x2e11a00b The dying-gasp of ONTi (DGi) is generated
l 0x2e11a001 The feed fiber is broken or OLT can not receive any expected optical signals
(LOS)
l 0x2e112007 The distribute fiber is broken or OLT can not receive expected optical
signals from GPON ONT(LOSi)
l 0x2e11a00a The loss of acknowledgement PLOAM message with ONTi (LOAi) occurs
Step 2 Check for the possible causes on the OLT and troubleshoot the faults accordingly. If the ONU
still fails to go online after that, proceed to Step 3.
Possible Cause Judgment Criterion Troubleshooting Method
The SN configured on Run the display ont info Run the ont add command to
the OLT is different from command to query the ONU re-add an ONU and specify the
the actual SN of the information. It is found that the correct ONU SN and password.
ONU; hence, the ONU SN in the result is different NOTE
fails to pass from the actual ONU SN. The ONU with a different SN is
authentication and to go regarded as a new one and is
online. founded by the OLT.

The actual distance Run the display port info Run the port range command
between the ONU and command to query the to adjust the minimum logical
OLT exceeds the ranging minimum logical reach (Min reach and maximum logical
compensation distance distance) and maximum reach so that the actual distance
configured on the OLT. logical reach (Max distance) between the ONU and OLT is
configured for the GPON port. within the ranging
It is found that the actual compensation distance.
distance between the ONU and NOTE
OLT exceeds the ranging l By default, the ranging
compensation distance. compensation distance of a
For example, the actual length GPON port is from 0 km to 20
km.
of the optical fiber between the
ONU and OLT is about 25 km, l According to Class B+, the
which exceeds the ranging maximum logical reach of a
GPON port must not exceed
compensation distance of 0-20 60 km, and the difference
km. between the minimum logical
reach and maximum logical
reach must not exceed 20 km.
The OLT deactivates the Run the display ont info Run the ont activate command
ONU. command to query the ONU to activate an ONU.
information. It is found that NOTE
Control flag is displayed as When an ONU is activated, its
deactivated. optical module only receives
optical signals but does not
transmit optical signals.
The laser on the PON Run the display port info Run the port laser-switch
port is disabled. command to query the command to enable the laser on
information about the PON the PON port.
port. It is found that Laser NOTE
switch is in the Off state. By default, the laser on a GPON
port is enabled.

The PON port is faulty. If either of the following two Replace the optical module of
situations occurs, the PON pot the PON port or replace the
is faulty. board.
l Run the display port state
status of the PON port. It is
found that abnormal items
exist in the query result. For
example, the laser status
(Laser state) is abnormal
and the transmit optical
power (TX power) exceeds
the normal range (1.5-5.0
dBm).
l Migrate the service to
another port. It is found that
the ONU goes online
normally.
The board or the slot is All the ONUs connected to the Change the board to another
faulty. board fail to go online. slot. If the fault persists, replace
the board.
Step 3 Check for the possible causes on the ODN and troubleshoot the faults accordingly. If the ONU
The optical fiber 1. Test the backbone fiber and Clean the optical fiber
connector is not clean. branch fiber by using the connector. For details about
NOTE OTDR. It is found that the how to clean the connector, see
An unclean optical fiber reflection and return loss 2.2 Cleaning the Connector of
connector will cause are abnormal. the Optical Fiber.
excessive attenuation and
abnormal reflection. 2. Check the optical fiber
connector on site by using
the optical fiber endface
detector. It is found that the
optical fiber connector is
not clean.
The optical fiber is bent 1. Test the backbone fiber and Route and bundle the optical
excessively. branch fiber by using the fiber in a proper manner.
NOTE OTDR. It is found that
Optical signals attenuate abnormal return loss points
seriously on an optical exist on the optical fiber.
fiber with an excessively
small bending radius. 2. Check the optical fiber on
site. It is found that the
optical fiber is bent
excessively.

The quality of optical 1. Test the backbone fiber and Splice the optical fiber again.
fiber splicing is poor. For branch fiber by using the
example, the splicing OTDR. It is found that
point has air bubbles. abnormal return loss points
NOTE exist on the optical fiber.
Poor optical fiber splicing 2. Check the optical fiber
leads to unstable
splicing points by using the
transmission of optical
signals. As a result, packet magnifying glass on site. It
loss occurs. is found that the splicing
points have quality
problems, for example, air
bubbles exist.
The optical fiber is not 1. Test the backbone fiber and l If the optical fiber is not
firmly connected or branch fiber by using the firmly connected, reconnect
different types of optical OTDR. It is found that the optical fiber firmly.
fiber connectors are abnormal return loss points l If different types of optical
interconnected. exist on the optical fiber. fiber connectors are
NOTE 2. Check the optical fiber interconnected, replace the
If the optical fiber is not connectors on site. It is incompatible connector
firmly connected or
found that the optical fiber with a compatible one or
different types of optical
fiber connectors are is not firmly connected or replace relevant devices,
interconnected, the PC connector (blue) and such as the optical splitter.
attenuation and reflection APC connector (green) are NOTE
will be excessively large. interconnected. In the scenario of the CATV
service, it is recommended that
you use APC connectors (green)
only.
The multi-mode optical 1. Check the backbone fiber Replace the multi-mode optical
fiber is used as the and branch fiber by using fiber with the single-mode
backbone or branch the OTDR. It is found that optical fiber.
optical fiber. optical signals attenuate
NOTE seriously.
If the multi-mode optical 2. Check the optical path on
fiber is used as the
backbone or branch optical
fiber, the optical signal multi-mode optical fiber is
attenuates quickly and the used. The multi-mode
return loss increases. optical fiber can be
recognized by its physical
features such as its color.

The optical attenuation If either of the following two Add an optical attenuator on the
of the optical path is situations occurs, the optical optical path between the OLT
excessively small. attenuation of the optical path and ONU.
NOTE is excessively small.
l If the optical l Measure the receive optical
attenuation of the power of the ONU by using
optical path is the optical power meter. It
excessively small, the is found that the actual
optical power received
receive optical power of the
by the ONU will
exceed the overload ONU is greater than -8
optical power of the dBm.
ONU. l Check the optical path
l Such a situation occurs between the OLT and ONU.
usually in labs, where It is found that the optical
the OLT and ONU
attenuation of the optical
may be directly
connected to each path is excessively small.
other through a short The normal attenuation
optical fiber. range is 10-25 dB.
The ODN is not properly The ODN does not meet the Optimize the ODN to meet
planned. requirements of the ODN link Huawei's ODN planning
NOTE plan or GPON Class B+. requirements and protocol
l The split ratio of the l Three-level splitting exists requirements.
ODN link is not in the ODN.
determined by the
number of ONTs l The network coverage of
connected but by the the ODN exceeds 20 km by
split ratio of optical far.
splitters. When an
optical splitter is
l The split ratio exceeds the
connected to the ODN, maximum split ratio that the
attenuation occurs and board allows. Assuming
the split ratio of the that the maximum split ratio
optical splitter needs to of a board is 1:64. If the
be calculated. first-level split ratio is 1:8
l Protocols specify that and the second-level split
the receive optical ratio is 1:16, the actual split
power of the OLT
ratio is 1:128, which
should not exceed 15
dB. In addition, the exceeds the maximum split
difference between the ratio of the board.
maximum optical l The optical attenuation
power and the
minimum optical
difference of two optical
power should not paths exceeds 15 dB.
exceed 15 dB.

The optical splitter is Measure the input and output Replace the faulty optical
faulty or the connectors optical power of the optical splitter or clean the connectors
on the optical splitter are splitter by using the optical on the optical splitter.
not clean. power meter. It is found that the
actual attenuation exceeds the
theoretical attenuation.
NOTE
The faults in the optical splitter
cannot be located by the OTDR
because the OTDR cannot
penetrate the optical splitter.
A backbone fiber break 1. Check the backbone fiber Reconnect the branch optical
occurs. by using the OTDR. It is fiber.
found that a backbone fiber
break occurs.
2. Check the optical fiber on
optical fiber is broken or not
connected.
A branch fiber break 1. Check the branch fiber by Reconnect the branch optical
occurs. using the OTDR. It is found fiber.
that a branch fiber break
occurs.
connected.
Step 4 Check for the possible causes on the ONU and troubleshoot the faults accordingly. If the ONU
The ONU is not powered If either of the following two Restore the power supply of the
on. situations occurs, the ONU is ONU.
not powered on.
l The 0x2e11a00b The
dying-gasp of GPON
ONTi (DGi) alarm is
generated on the OLT, but
the corresponding clear
alarm is not generated.
l Check the power supply of
the ONU. It is found that the
power supply of the ONU
fails or is turned off.

A rogue ONU (such as a If either of the following two Replace the rogue ONU with a
continuous-mode ONU) situations occurs, a rogue ONU normal one.
exists on the network and exists.
affects other ONUs. l The 0x2e314021 There are
NOTE illegal incursionary rogue
If a rogue ONU exists, the ONTs under the port
ONU that fails to go online
alarm is generated on the
may be a normal one and
the ONU that can go online OLT.
may be a rogue one. l The 0x2e314022 The ONT
is rogue ONT alarm is
generated on the OLT.
l Connect the optical fiber of
the OLT port to the optical
power meter for
measurement. If a value can
be read from the optical
power meter, a continuous-
mode ONU or irregular-
mode ONU exists.
The information (SN) for The 0x2e305015 The Replace the ONU with
ONU authentication authentication information conflicted SN.
conflicts; hence, the of the ONTs conflicts alarm is
power-on ONU fails to generated on the OLT.
go online.
The ONU hardware is If either of the following two Replace the faulty ONU or the
faulty. situations occurs, the ONU optical module of the ONU.
hardware is faulty.
l The LEDs of the ONU are
off when the ONU is
powered on.
l After the ONU is replaced
with another ONU, the new
ONU is auto discovered by
the OLT.

The optical module of the Replace the faulty ONU with a Replace the faulty ONU or the
ONU is abnormal. For normal one. It is found that the optical module of the ONU.
example, the transmit new ONU is auto discovered by
optical power of the the OLT.
optical module is An alternative is to locate the
excessively small or its fault as follows:
receiver sensitivity is
low. l Set the optical module of
the ONU to the continuous
mode, and measure the
transmit optical power by
using the optical power
meter. It is found that the
actual transmit optical
power is beyond the normal
range (1.5 dBm to 5.0
dBm).
l Measure the receive optical
power of the ONU by using
the optical power meter. It
is found that the actual
receive optical power is
within the normal range
(-27 dBm to -8 dBm).
The Patch cord of the Check the Patch cord of the Replace the Patch cord of the
ONU is broken or bent ONU. It is found that the Patch ONU.
excessively. cord is broken or bent
excessively.
Step 6 End.
----End
Failure to Recover GPON ONU Configurations

An ONU connected to a GPON port of an OLT can go online successfully, but the queried
Config state of the ONU is displayed as failed by running the display ont info command on
the OLT.
Location Method
NOTE
Configuration recovery refers to a process in which, after an ONU goes online, the OLT issues
configurations to the ONU and then the ONU adjusts its operating parameters based on the issued
configurations.


Scope
OLT ONUs of the same type fail l The configurations issued by the OLT
to recover their mismatch the actual ONU capabilities.
configurations.
ODN A single ONU fails to The optical attenuation is over large or small and
NOTE recover its configurations. the ONU can normally go online but fails to
ODN recover its configurations. The possible causes are
failures as follows:
are
generally l The branch fiber is bent excessively.
caused by l The branch fiber connector is not clean.
large
reflection l Different types of branch fiber connectors are
and interconnected.
attenuatio
n caused
by branch fiber.
improper l The optical splitter is faulty or the connectors
optical on the optical splitter are not clean.
compone
nts, Multiple ONUs connected The optical attenuation is over large or small and
design, or
constructi
to the same PON port of an the ONU can normally go online but fails to
on. OLT fail to recover their recover its configurations. The possible causes are
configurations. as follows:
l The ODN is not properly planned. For
example, the split ratio, network coverage and
attenuation difference are not planned within
the proper ranges.
l The backbone fiber is bent excessively.
l The backbone fiber connector is not clean.
l Different types of backbone fiber connectors
are interconnected.
backbone fiber.
ONU A single ONU fails to l The ONU functions improperly or is faulty.

recover its configurations. l The ONU has been configured at local and the
configurations conflict with configurations
issued by the OLT.
CAUTION

Procedure
Step 1 When Config state of the ONU is displayed as failed, check whether the OLT generates the
following alarm. If such an alarm is generated, clear it and check whether the fault is rectified.
If the fault persists, proceed to Step 2.
0x2e21a102 The GPON ONT configuration recovery fails
fails to recover its configurations, go to Step 3.
The configurations Check configurations issued to Modify OLT configurations

issued by the OLT the ONU by the OLT. It is based on actual ONU
mismatch the actual found that some configurations capabilities.
ONU capabilities. are not supported by the ONU.
For example, the number of
GEM ports exceeds the number
supported by the ONU.
still fails to recover its configurations after that, go to Step 4.
not clean.
The optical fiber is bent 1. The return loss points of the Route and bundle the optical
excessively. backbone fiber and branch fiber in a proper manner.
NOTE fiber are abnormal tested by
Optical signals attenuate using the OTDR.
seriously on an optical
2. The optical fiber is bent
small bending radius. excessively onsite.

The optical fiber is not 1. The return loss points of the l If the optical fiber is not
firmly connected or backbone fiber and branch firmly connected, reconnect
different types of optical fiber are abnormal tested by the optical fiber firmly.
fiber connectors are using the OTDR. l If different types of optical
interconnected. 2. Check the optical fiber fiber connectors are
NOTE connectors on site. It is interconnected, replace the
If the optical fiber is not found that the optical fiber incompatible connector
firmly connected or
is not firmly connected or with a compatible one or
fiber connectors are PC connector (blue) and replace relevant devices,
interconnected, the APC connector (green) are such as the optical splitter.
attenuation and reflection interconnected. NOTE
will be excessively large. In the scenario of the CATV
only.
The multi-mode optical 1. Optical signals of the Replace the multi-mode optical
fiber is used. backbone fiber and branch fiber with the single-mode
NOTE fiber attenuate seriously by optical fiber.
If the multi-mode optical using the OTDR.
2. The multi-mode optical
fiber, the optical signal fiber is used onsite. The
attenuates quickly and the multi-mode optical fiber
return loss increases. can be recognized by its
physical features such as its
color.

NOTE plan or GPON. requirements and protocol
determined by the
number of ONUs l The network coverage of
splitters. When an
optical splitter is
connected to the ODN, specification. For example,
attenuation occurs and a board supports a
the split ratio of the maximum of 1:64 split
optical splitter needs to ratio. If the first-level split
be calculated. ratio is 1:8, the second-level
l Protocols specify that is 1:16, the actual split ratio
the receive optical is 1:128. This exceeds the
power of the OLT
specification (1:64).
dB. In addition, the l The optical attenuation
difference between the difference of two optical
maximum optical lines exceeds 15 dB.
power and the
minimum optical
power should not
exceed 15 dB.
NOTE
still fails to recover its configurations after that, go to Step 5.
The ONU has been The management-related ONU Delete the web page
configured at local and configurations such as IP configurations and issue
the configurations address and management mode configurations to the ONU by
conflict with are configured on the web page. the OLT.
configurations issued by
the OLT.

The ONU functions Run the ont reset command to Replace the faulty ONU with a
improperly or is faulty. reset the ONU. It is found that functional one.
the ONU fails to recover its
configurations.
Step 6 End.
----End
GPON ONU Profile Match state is Mismatch

An ONU connected to a GPON port of an OLT can go online successfully, but the queried
Match state of the ONU is displayed as mismatch by running the display ont info command
on the OLT.
Location Method
NOTE
Match state indicates the consistency between the actual ONU capabilities and the capability set (including
the port type and port quantity) configured in the ONU profiles. If an inconsistency exists, Match state is
displayed as mismatch.
In practice, ONUs in the offline state are bulk pre-configured on the OLT to facilitate service provisioning.
An ONU service profile and an ONU line profile are specified during such configurations. The ONU
profiles together can be regarded as a virtual ONU. Subsequent services are configured based on this virtual
ONU. Inconsistency between the capability set configured in the ONU profiles and the actual ONU
capabilities involves the following two situations:
l The configured capability set outmatches the actual ONU capabilities. If the ONU is bound to such
ONU profiles, ONU configurations will fail to be recovered when the ONU goes online.
l The configured capability set undermatches the actual ONU capabilities. In this case, the ONU
capabilities that are not covered by the ONU profiles will fail to be configured or applied.
When the queried Match state of the ONU is displayed as mismatch, locate the fault according
to the following procedure:
1. Check whether the capability set configured in the ONU line profile matches the actual
ONU capabilities.
CAUTION
Procedure
Step 1 Run the display ont capability command to query the actual ONU capabilities. According to
the data plan, modify the current ONU profiles, or bind matching ONU profiles to the ONU.

l If this problem occurs on all the ONUs of the same type, the configurations of the ONU
profiles may be incorrect.
– If the OLT works in the distributed mode, the profiles that are bound to the ONU cannot
be modified or deleted. In this case, bind matching ONU profiles to the ONU.
– If the OLT works in the profile mode:
1. Run the display ont-lineprofile command to query the information about the ONU
line profile.
2. Modify the ONU profiles.
l If this problem occurs on only one ONU, it is suggested to bind matching ONU profiles to
the ONU.
– If the OLT works in the distributed mode:
1. Run the display ont-profile command to query the current ONU profiles that are
configured on the OLT.
2. If the OLT does not have matching ONU profiles, run the ont-profile add command
to add matching ONU profiles.
3. Run the ont modify command to bind the ONU profiles to the ONU.
– If the OLT works in the profile mode:
1. Run run the display ont-lineprofile command to query the information about the
ONU line profile.
2. If the OLT does not have matching ONU profiles, add matching ONU profiles.
3. In the GPON mode of the OLT, run the ont modify command to bind the ONU
profiles to the ONU.
Step 2 Check whether Match state of the ONU is displayed as match.

l If Match state of the ONU is displayed as match, go to Step 4.
l If Match state of the ONU is displayed as mismatch, proceed to Step 3.
Step 4 End.
----End
6.1.2 Failure to Auto Discover a GPON ONU

The ONU auto discovery failure is a fault in which an OLT fails to auto discover an ONU after
the ONU is powered on.
Location Method
NOTE
The ONU auto discovery is a feature in which a pre-configured ONU automatically registers with an OLT
after the ONU is powered on; if the OLT does not pre-configure the ONU, the ONU enters the auto
discovery state and waits to be configured by the OLT.
When an OLT fails to auto discover an ONU, locate the fault based on the following fault
symptoms and possible causes.


Scope
OLT A single ONU or some The actual distance between the ONU and OLT
ONUs connected to an exceeds the ranging compensation distance
OLT fail to be auto configured on the OLT.
discovered by the OLT.
All the ONUs connected l The ONU auto discovery function is disabled
to a PON port on an OLT on the PON port.
fail to be auto discovered l The laser on the PON port is disabled.
by the OLT.
l The PON port is faulty.
All the ONUs connected The board or the slot is faulty.

to a board on an OLT fail
to be auto discovered by
the OLT.

ONUs connected to an l The branch fiber connector is not clean.
OLT fail to be auto
discovered by the OLT. l Different types of branch fiber connectors are
interconnected.
branch fiber.
l The ODN is not properly planned. For
example, the split ratio, network coverage and
the proper ranges.
l The optical attenuation of the optical path is
excessively small.
l A branch fiber break occurs.
All the ONUs connected l The backbone fiber is bent excessively.

to a PON port on an OLT l The backbone fiber connector is not clean.
fail to be auto discovered
by the OLT. l Different types of backbone fiber connectors
are interconnected.
backbone fiber.
l A backbone fiber break occurs.


Scope
ONU A single ONU or some l The ONU is not powered on.

ONUs connected to an l A rogue ONU (such as a continuous-mode
OLT fail to be auto ONU) exists on the network and affects other
discovered by the OLT. ONUs.
l The ONU hardware is faulty.
l The optical module of the ONU is faulty.
l The Patch cord of the ONU is broken or bent
excessively.
CAUTION
Procedure
still fails to be auto discovered by the OLT after that, proceed to Step 2.
The ONU auto discovery Run the display port info Run the port ont-auto-find
function is disabled on command to query the command to enable the auto
the PON port. information about the PON discovery function of the PON
port. It is found that Autofind port.
is in the Disable state. NOTE
By default, the ONU auto
discovery function is disabled on
a PON port.

The actual distance Run the display port info Run the port range command
between the ONU and command to query the to adjust the minimum logical
OLT exceeds the ranging minimum logical reach (Min reach and maximum logical
compensation distance distance) and maximum reach so that the actual distance
configured on the OLT. logical reach (Max distance) between the ONU and OLT is
configured for the PON port. It within the ranging
is found that the actual distance compensation distance.
between the ONU and OLT NOTE
exceeds the ranging l By default, the ranging
compensation distance. compensation distance of a
For example, the actual length GPON port is from 0 km to 20
km.
of the optical fiber between the
ONU and OLT is about 25 km, l According to Class B+, the
which exceeds the ranging maximum logical reach of a
GPON port must not exceed
compensation distance of 0-20 60 km, and the difference
km. between the minimum logical
reach and maximum logical
reach must not exceed 20 km.
The laser on the PON Run the display port info Run the port laser-switch
port is disabled. command to query the command to enable the laser on
information about the PON the PON port.
port. It is found that Laser NOTE
switch is in the Off state. By default, the laser on a GPON
port is enabled.
situations occurs, the PON port the PON port or replace the
is faulty. board.
dBm).
the ONU is auto discovered
by the OLT.
The board or the slot is Run the display board Run the board reset command
faulty. command to query the status of to reset the board or change the
the board. It is found that the board to another slot. If the fault
board status is not Normal. persists, replace the board.

not clean.
excessively.
firmly connected or
only.

NOTE seriously.
The optical attenuation If either of the following two Add an optical attenuator on the
of the optical path is situations occurs, the optical optical path between the OLT
excessively small. attenuation of the optical path and ONU.
NOTE is excessively small.
l If the optical l Measure the receive optical
attenuation of the power of the ONU by using
optical path is the optical power meter. It
excessively small, the is found that the actual
optical power received
receive optical power of the
by the ONU will
exceed the overload ONU is greater than -8
optical power of the dBm.
ONU. l Check the optical path
l Such a situation occurs between the OLT and ONU.
usually in labs, where It is found that the optical
the OLT and ONU
attenuation of the optical
may be directly
connected to each path is excessively small.
other through a short The normal attenuation
optical fiber. range is 10-25 dB.

determined by the
splitters. When an
optical splitter is
power of the OLT
power and the
minimum optical
exceed 15 dB.
NOTE
A backbone fiber break 1. Check the backbone fiber Reconnect the backbone
occurs. by using the OTDR. It is optical fiber.
found that a backbone fiber
break occurs.
connected.

A branch fiber break 1. Check the branch fiber by Reconnect the branch optical
occurs. using the OTDR. It is found fiber.
that a branch fiber break
occurs.
connected.
The ONU is not powered Check the power supply of the Restore the power supply of the
on. ONU. It is found that the power ONU.
supply of the ONU fails or is
turned off.
The ONU hardware is If either of the following two Replace the faulty ONU or the
faulty. situations occurs, the ONU optical module of the ONU.
hardware is faulty.
l The LEDs of the ONU are
off when the ONU is
powered on.
l After the ONU is replaced
with another ONU, the new
ONU is auto discovered by
the OLT.

The optical module of the Replace the faulty ONU with a Replace the faulty ONU or the
ONU is abnormal. For normal one. It is found that the optical module of the ONU.
example, the transmit new ONU is auto discovered by
optical power of the the OLT.
optical module is An alternative is to locate the
excessively small or its fault as follows:
receiver sensitivity is
low. l Set the optical module of
the ONU to the continuous
mode, and measure the
transmit optical power by
using the optical power
meter. It is found that the
actual transmit optical
power is beyond the normal
range (-1.5 dBm to +5
dBm).
l Measure the receive optical
power of the ONU by using
the optical power meter. It
is found that the actual
receive optical power is
within the normal range
(-27 dBm to -8 dBm).
The Patch cord of the Check the Patch cord of the Replace the Patch cord of the
ONU is broken or bent ONU. It is found that the Patch ONU.
excessively. cord is broken or bent
excessively.
Step 5 End.
----End
6.1.3 GPON ONU Frequently Goes Online and Offline

ONUs connected to a GPON port frequently go online and offline and thus the OLT reports a
large number of ONU LOS alarms and relevant recovery alarms.
Location Method
NOTE
An ONU frequently goes online and offline because the OLT receives weak ONU signals. As a result,
packets exchanged between the OLT and the ONU are lost.
When an ONU frequently goes online and offline, locate the fault based on the following fault
symptoms and possible causes.


Scope
OLT All the ONUs connected to The PON port is faulty.

a PON port on an OLT
frequently go online and
offline.
All the ONUs connected to The board or the slot is faulty.

a board frequently go
online and offline.

NOTE ONUs connected to an l The branch fiber connector is not clean.
ODN OLT frequently go online
failures and offline. l Different types of branch fiber connectors are
are interconnected.
generally
caused by
large branch fiber.
reflection l The ODN is not properly planned. For
and example, the split ratio, network coverage and
attenuatio
n caused
by the proper ranges.
improper l The optical splitter is faulty or the connectors
optical on the optical splitter are not clean.
compone
nts, All the ONUs connected to l The backbone fiber is bent excessively.
design, or
constructi
a PON port on an OLT l The backbone fiber connector is not clean.
on. frequently go online and
offline. l Different types of backbone fiber connectors
are interconnected.
backbone fiber.
ONU A single ONU or some l A rogue ONU (such as a continuous-mode

ONUs connected to an ONU) exists on the network and affects other
OLT frequently go online ONUs.
and offline. l The ONU is restarted repeatedly.
CAUTION

Procedure
Step 1 When the "ONU frequently goes online and offline" alarm is generated, check whether the OLT
generates the following alarms. If such alarms are generated, clear them and check whether the
fault is rectified. If the fault persists, proceed to Step 2.
The following alarms may be generated:
l 0x2e11a001 The feed fiber is broken or OLT can not receive any expected optical signals
(LOS)
l 0x2e112007 The distribute fiber is broken or OLT can not receive expected optical
signals from GPON ONT(LOSi)
l 0x2e314021 There are illegal incursionary rogue ONTs under the port
l 0x2e314022 The ONT is rogue ONT
l 0x2e112002 The loss of GEM channel delineation (LCDGi) occurs
l 0x2e112003 The signal degrade of ONTi (SDi) occurs
l 0x2e112004 The signal fail of ONTi (SFi) occurs
l 0x2e112006 The loss of frame of ONTi (LOFi) occurs
still fails to function properly after that, proceed to Step 3.
situations occurs, the PON port the PON port or replace the
is faulty. board.
dBm).
the ONU functions
properly.
The board or the slot is All the ONUs connected to a Change the board to another
faulty. board frequently go online and slot. If the fault persist, replace
offline. the board.

not clean.
excessively.
firmly connected or
only.
NOTE seriously.

NOTE
determined by the
splitters. When an
optical splitter is
power of the OLT
power and the
minimum optical
exceed 15 dB.

A rogue ONU (such as a If either of the following two Replace the rogue ONU with a
continuous-mode ONU) situations occurs, a rogue ONU normal one.
exists on the network and exists.
affects other ONUs. l The 0x2e314021 There
NOTE are illegal incursionary
If a rogue ONU exists, the rogue ONTs under the
ONU that fails to go online
port alarm is generated on
may be a normal one and
the ONU that can go online the OLT.
may be a rogue one. l The 0x2e314022 The ONT
is rogue ONT alarm is
generated on the OLT.
l Connect the optical fiber of
the OLT port to the optical
power meter for
measurement. If a value can
be read from the optical
power meter, a continuous-
mode ONU or irregular-
mode ONU exists.
The ONU is restarted Check whether the ONU is Replace the ONU or ensure that
repeatedly. faulty or whether the power the power supply of the ONU is
voltage is unstable. normal.
Step 6 End.
----End
6.2 NMS Fails to Manage a Device

If the NMS fails to manage the device, it means that the NMS loses control over the MA5612.
Location Method
When the NMS fails to manage the MA5612, locate the fault according to the following
procedure:
1. Check the fault scope.
2. Check whether the MA5612 can ping the IP address of the NMS server.
3. Check whether NMS parameter configurations of the MA5612 and the NMS server are
correct.

CAUTION
Procedure
Step 1 Check whether the same NMS fails to manage other devices, that is, whether the fault occurs in
a large scale.
l If the same NMS fails to manage other devices, go to Step 2.
l If the same NMS can manage other devices, go to Step 4.
Step 2 Check whether the NMS version matches the device version.
l If the NMS version matches the device version, go to Step 4.
l If the NMS version does not match the device version, upgrade NMS version or device
version so that the NMS version matches the device version. Then, go to Step 3.
Step 4 Run the ping command to ping the IP address of the NMS server.
l If the device can ping the IP address of the NMS server, go to Step 10.
l If the device cannot ping the IP address of the NMS server, go to Step 5.
Step 5 Run the display ip routing-table command to check whether there is a route from the
MA5612 to the NMS server.
l If there is a route from the MA5612 to the NMS server, go to Step 7.
l If there is not a route from the MA5612 to the NMS server, run the ip route-static command
to add a static route from the MA5612 to the NMS server. Then, go to Step 6.
Step 7 Run the display arp command to check on the MA5612 whether the ARP information about
the NMS exists in the ARP mapping table.
l If the ARP information about the NMS exists in the ARP mapping table, go to Step 10.
l If no ARP information about the NMS exists in the ARP mapping table, go to Step 8.
Step 8 Check whether the upper layer device of the MA5612 learns the MAC address of the L3 interface
of the MA5612.
l If the upper layer device of the MA5612 learns the MAC address of the L3 interface of the
MA5612, go to Step 10.
l If the upper layer device of the MA5612 does not learn the MAC address of the L3 interface
of the MA5612, go to Step 9.
Step 9 Check the physical link between the MA5612 and the upper layer device. Ensure that the
communication between the MA5612 and the upper layer device is normal. Then, check whether
the fault is rectified.


Step 10 Check NMS parameter configurations of the MA5612 and the NMS. Make sure that NMS
parameter configurations are correct. Then, check whether the fault is rectified.
NOTE
The following configurations need to be checked.

l Run the display snmp-agent community read command to check whether the read community name
of the device is the same as that of the NMS. If they are inconsistent, run the snmp-agent community
read command to modify the read community name of the device to be the same as that of the NMS.
l Run the display snmp-agent community write command to check whether the write community name
of the device is the same as that of the NMS. If they are inconsistent, run the snmp-agent community
write command to modify the write community name of the device to be the same as that of the NMS.
l Run the display snmp-agent target-host command to check whether the IP address of the NMS server
is included in the target host list for traps. If the IP address of the NMS server is not included in the
target host list for traps, run the snmp-agent target-host trap-hostname command to add the NMS
server to the target host list for traps.
l Run the display snmp-agent trap enable command to check whether traps can be sent to the NMS
from the device. If it is disable, run the snmp-agent trap enable command to enable trap sending from
the device to the NMS.
Assistance).
Step 12 End.
----End
6.3 The Alarm Information Fails to Be Displayed on the

NMS
If the alarm information fails to be displayed, it means that the NMS server does not display the
corresponding alarm information when the MA5612 generates an alarm.
Location Method
If the alarm information fails to be displayed in the window of the NMS server when the
MA5612 generates an alarm, locate the fault as follows:
1. Check whether the communication between the NMS server and the MA5612 is normal.
That is, check whether the NMS server fails to manage the MA5612.
2. Check whether the alarm filtering condition configured on the MA5612 is proper.
3. Check whether the alarm masking policy configured on the NMS server is proper.
CAUTION

Procedure
Step 1 Check whether the communication between the NMS server and the MA5612 is normal. That
is, check whether the NMS server fails to manage the MA5612.
l If the NMS server fails to manage the MA5612, handle the fault according to 6.2 NMS
Fails to Manage a Device. Then, go to Step 2.
l If the NMS server can manage the MA5612, go to Step 3.
Step 3 Run the display trap filter command to check whether the alarm filtering condition configured
on the MA5612 is proper.
l If the alarm filtering condition is proper, go to Step 5.
l If the alarm filtering condition is improper, go to Step 4.
Step 4 Run the trap filter command to reconfigure the alarm filtering condition. Then, check whether
the alarm information can be displayed on the NMS.
l If the alarm information can be displayed on the NMS, go to Step 7.
l If the alarm information fails to be displayed on the NMS, go to Step 5.
NOTE
Run the trap filter command to configure the filtering condition for an alarm or event. If an alarm or event is
filtered, the alarm or event will not be reported to the CLI terminal, will not be saved in the alarm or event history
records. In addition, the corresponding trap packet will not be sent to the NMS.
Step 5 Check whether the alarm masking policy configured on the NMS is proper and make sure that
the alarm masking policy is configured properly. Then, check whether the alarm information
can be displayed on the NMS.
l If the alarm information can be displayed on the NMS, go to Step 7.
l If the alarm information fails to be displayed on the NMS, go to Step 6.
Assistance).
Step 7 End.
----End
6.4 Service Board Is in the Failed State

This section describes how to troubleshoot the fault when the service board of the MA5612 is
in the failed state.
Location Method
When the service board of the MA5612 is in the failed state, locate the fault according to the
following procedure:
1. Check whether the service board is added offline.

2. Check whether the type of the inserted service board is the same as that configured in the
system.
3. Check whether the power supply for the service board is normal.
4. Check whether the service board is inserted properly.
5. Check whether the board is faulty.
CAUTION
l To facilitate fault report, save the results of the following steps.
l Take ESD measures before removing and inserting a board.
Procedure
Step 1 Check whether the service board is added offline.
l If the board is added offline and is not inserted actually, no need to proceed.
l If the board is not added offline, go to Step 2.
Step 2 Run the display board frameid/slotid command to query the type of the faulty board, check the
type of the actual board inserted into the slot, and then check whether their types are the same
or compatible.
l If their types are the same or compatible, go to Step 4.
l If their types are different or not compatible, check whether the system configurations are
correct. If it is confirmed that system configurations are correct, insert a board of the correct
type as configured in the system into the slot. Then, go to Step 3.
l If their types are different or not compatible, check whether the system configurations are
correct. If it is confirmed that system configurations are incorrect, run the board delete
frameid/slotid command to delete the original configurations, after the system displays a
message indicating that the board is automatically found, run the board confirm frameid/
slotid command to confirm the board. Then, go to Step 3.
Step 3 Wait for five minutes and then check whether the service board is working properly.
l If the board is working properly, go to Step 10.
Step 4 Run the display broad-service power-off state command to check whether the function of
powering off the broadband services is in the On state.
l If the function is in the On state, go to Step 5.
l If the function is not in the On state, go to Step 6.
NOTE
When the function of powering off the broadband services is in the On state, the device powered by batteries
automatically cuts off the power supply for the broadband services to extend the narrowband service time.
Step 5 Check whether the MA5612 is currently powered by batteries.

l If the MA5612 is powered by batteries, go to Step 10.
l If the MA5612 is not powered by batteries, go to Step 6.
Step 6 Check whether the board is firmly inserted.

l If the board is firmly inserted, go to Step 8.

l If the board is not firmly inserted, remove and insert the board, and ensure that the board
is firmly inserted. Then, go to Step 7.
NOTE
If the board is not properly installed, component detection fails during board startup and therefore the
startup fails. The fault can be rectified only by removing and inserting the board.

Step 8 Replace the original board, wait for about five minutes, and then check whether the new board
is in the normal state.
NOTE
A board is in the Auto_find state after being discovered automatically. After the board confirm frameid/slotid
command is executed to confirm the board status, the board is in the normal state.
l If the new board is in the normal state, the original board is faulty. Go to Step 10.
Assistance).
Step 10 End.
----End
6.5 A Service Board Fails to Register

This topic describes how to troubleshoot a fault when a service board of an MA5612 fails to
register.
Location Method
1. Check whether the board is properly installed.

CAUTION
Procedure
Step 1 Check whether the board is properly installed.

l If the board is properly installed, go to Step 3.

l If the board is not properly installed, remove and insert the board, and ensure that the board
is properly installed. Then, go to Step 2.
NOTE
If the board is not properly installed, component detection fails during board startup and therefore the
startup fails. The fault can be rectified only by removing and inserting the board.

Step 3 Replace the board, wait about 5 minutes, and then check whether the new board is working
normally.
NOTE
A board is in the Auto_find state after being discovered automatically. Run the board confirm frameid/slotid
command to verify that the board is working normally.
l If the new board is working normally, the original board is faulty. Go to Step 5.
l If the new board is not working normally, go to Step 4.
Assistance).
Step 5 End.
----End
6.6 Repeated Board Reset

This section describes how to troubleshoot the repeated reset of a service board on the
MA5612.
Location Method
1. Check whether the type of the board in use is the same as that configured for the system.
2. Check whether the ambient temperature of the device is too high.
3. Check whether the board is properly installed.
5. Check whether the backplane of the device is working properly.
6. Check whether the board software in the system is correct.
CAUTION

Procedure
Step 1 Run the display board frameid/slotid command to query the board information, and then check
whether the configured board type is the same as the one in use.
l If the configured board type is the same as the one in use, go to Step 3.
l If the configured board type is different from the one in use, replace the current board with
one configured in the system. Then, go to Step 2.
l Conversely, if the configured board type is different from the one in use, run the board
delete frameid/slotid command to delete the board type configured in the system if the
board type configured in the system is incorrect, and then run the board confirm frameid/
slotid command to confirm the board once the system automatically detects the board. Then,
go to Step 2.
Step 2 Wait five minutes. Then, check whether the fault is rectified.
Step 3 Check whether the ambient temperature of the device is too high.
NOTE
A board repeatedly resets if its ambient temperature is too high.

l If the ambient temperature of the device is too high, go to Step 4.
l If the ambient temperature of the device is normal, go to Step 5.
Step 4 Run the fan speed command to adjust the fan speed on the device to improve ventilation effect,
or add cooling equipment to ensure that the device works in a proper ambient temperature. Then,
check whether the fault is rectified.
Step 5 Check whether the board is properly installed.

l If the board is properly installed, go to Step 7.
l If the board is not properly installed, install the board properly, and go to Step 6.

Step 7 Replace the board with a new one, wait about five minutes, and then check whether the new
board repeatedly resets.
l If the new board repeatedly resets, go to Step 8.
l If the new board does not repeatedly reset, go to Step 11.
Step 8 Run the display io-packetfile information command to query the information about board
software packages in the flash memory and then check whether the information contains the
board software package information and whether its version is correct.
l If the information contains the board software package information and its version is
correct, go to Step 10.
l If the information contains no board software package information or its version is
incorrect, go to Step 9.

Step 9 Run the load packetfile command to load the board software. After the board software is loaded,
wait about five minutes, and then check whether the new board works properly.
l If the new board works properly, go to Step 11.
l If the new board does not work properly, go to Step 10.
Assistance).
Step 11 End.
----End
6.7 Unexpected Reset of the System

This section describes how to troubleshoot unexpected reset of the system. When the system is
reset unexpectedly, all services carried on the device are interrupted and the device cannot be
managed by the network management system (NMS).
Location Method
1. Check whether the user has issued a command to reset the device.
2. Check whether the power supply for the device is normal.
3. Check whether the device temperature is within the acceptable range.
CAUTION
Procedure
Step 1 Run the display log all command to check whether the user has issued a command to reset the
device.
l If the device is reset following the execution of a reset command, go to Step 5.
l If no command has been issued to reset the device, go to Step 2.

NOTE
The device displays the following information in the output of the display log all command.
---------------------------------------------------------------------------
No. UserName Domain IP-
Address
343 root --
192.168.0.10
Time: 2011-07-11 00:00:02
+08:00
Cmd: reboot
system
---------------------------------------------------------------------------
If the time when the system is unexpectedly reset is the same as the time when the system reset log is
recorded, the user has issued a command to reset the system.
Step 2 Check whether the power supply for the device is normal.
1. Check whether the power supply for the device has been cut off.
l If the power supply for the device has been cut off, the system reset is caused by the
power cutoff. Go to Step 5.
l If the power supply for the device has always been normal, go to Step 2.2.
2. Check whether the voltage of the device is normal.
l If the voltage of the device is normal, go to Step 3.
l If the voltage of the device is too low, the device may be reset. Go to Step 5.
NOTE
The working voltage range of the system is as follows:

l AC power supply: 90 V to 264 V
l DC power supply: -38.4 V to -72 V
Step 3 Check whether the device temperature is too high.

l If the device temperature is too high, the system will be automatically reset to protect system
components form being burnt out. Go to Step 5.
l If the device temperature is within the range, go to Step 4.
NOTE
The working temperatures of the system range from -40°C to +65°C.
Assistance).
Step 5 End.
----End

Maintenance Guide 7 Troubleshooting EMU Faults
7 Troubleshooting EMU Faults
About This Chapter
The EMU is used to monitor the running environment of devices. When the EMU is faulty, the
fault is troubleshot immediately. This ensures that the devices and the services on the devices
are normal because the running environment of the devices is monitored.
7.1 ESCM Being in Fault State

The ESCM is an environment monitoring unit (EMU) that integrates the environment monitoring
board, terminal blocks, and DIP switches. The ESCM monitors the environment parameters of
the device. This document provides the troubleshooting guide when the ESCM is in Fault state.
7.2 EPS30-4815AF Being in Fault State
The EPS30-4815AF power system is used in the AC-powered cabinet to convert the AC into
the DC and then distribute the power to implement DC power distribution. This document
provides the troubleshooting guide when the EPS30-4815AF is in Fault state.

7.1 ESCM Being in Fault State

The ESCM is an environment monitoring unit (EMU) that integrates the environment monitoring
board, terminal blocks, and DIP switches. The ESCM monitors the environment parameters of
the device. This document provides the troubleshooting guide when the ESCM is in Fault state.
Location Method
The ESCM is displayed as MINIESC on the MA5612 interface. When the ESCM is in Fault
state, locate the fault according to the following procedure:
1. Check whether the serial port mode of the MA5612 is emu.
2. Check whether the sixth switch of the DIP switch on the ESCM is set to on (the baud rate
is 19200 bit/s).
3. Check whether the dedicated environment monitoring cable connecting the ESCM to the
serial port on the MA5612 is faulty.
4. Check whether the settings of the DIP switch on the ESC board are the same as the settings
of the secondary nodes of the EMU on the MA5612.
CAUTION
Procedure
Step 1 Run the display serial-mode command to check whether the serial port mode of the device is
emu.
l If the serial port mode of the device is emu, go to Step 3.
l If the serial port mode of the device is not emu, go to Step 2.
Step 2 Run the serial-mode emu command to set the serial port mode to emu. Run the display emu
command to check whether the ESCM is in Normal state.
l If the ESCM is in Normal state, it indicates that the fault occurs due to the improper serial
port mode. Go to Step 10.
l If the ESCM is not in Normal state, go to Step 3.
Step 3 Check whether the sixth switch of the DIP switch on the ESCM is set to on.
l If the sixth switch of the DIP switch on the ESCM is set to on, go to Step 5.
l If the sixth switch of the DIP switch on the ESCM is not set to on, go to Step 4.
Step 4 When the serial port mode of the MA5612 is emu, the baud rate of the serial port is 19200 bit/
s. In this case, set the sixth switch of the DIP switch on the ESCM to on and the baud rate to
19200 bit/s that is the same as the baud rate of the serial port on the MA5612. Run the display
emu command to check whether the ESCM is in Normal state.
l If the ESCM is in Normal state, go to Step 10.

Step 5 Check whether the dedicated environment monitoring cable connecting the ESCM to the serial
port on the MA5612 is aged, exposed, or broken out.
l If the dedicated environment monitoring cable connecting the ESCM to the serial port on
the MA5612 is aged, exposed, or broken out, go to Step 6.
l If the dedicated environment monitoring cable connecting the ESCM to the serial port on
the MA5612 is not aged, exposed, or broken out, go to Step 7.
Step 6 Replace the dedicated environment monitoring cable connecting the ESCM to the serial port on
the MA5612. Run the display emu command to check whether the ESCM is in Normal state.
Step 7 Check whether the settings of the DIP switch on the ESCM are the same as the settings of the
secondary nodes of the EMU on the MA5612.
l If the settings of the DIP switch on the ESCM are the same as the settings of the secondary
nodes of the EMU on the MA5612, go to Step 9.
l If the settings of the DIP switch on the ESCM are different from the settings of the secondary
nodes of the EMU on the MA5612, go to Step 8.
Step 8 Set the DIP switch on the ESCM or run the emu add command to configure the secondary nodes
of the EMU on the MA5612 again so that the settings of the DIP switch on the ESCM are the
same as the settings of the secondary nodes of the EMU on the MA5612. Run the display
emu command to check whether the ESCM is in Normal state.
Assistance).
Step 10 End.
----End
7.2 EPS30-4815AF Being in Fault State

The EPS30-4815AF power system is used in the AC-powered cabinet to convert the AC into
the DC and then distribute the power to implement DC power distribution. This document
provides the troubleshooting guide when the EPS30-4815AF is in Fault state.
Location Method
The EPS30-4815AF, namely POWER4830, is displayed as Pwr4830 on the MA5612 interface.
When the EPS30-4815AF is in Fault state, locate the fault according to the following procedure:
1. Check whether the serial port mode of the MA5612 is emu.

2. Check whether the sixth switch of the DIP switch on the EPS30-4815AF is set to off (the
baud rate is 19200 bit/s).
3. Check whether the dedicated environment monitoring cable connecting the EPS30-4815AF
to the serial port on the MA5612 is faulty.

4. Check whether the settings of the DIP switch on the EPS30-4815AF are the same as the
settings of the secondary nodes of the EMU on the MA5612.
CAUTION
Procedure
Step 1 Run the display serial-mode command to check whether the serial port mode of the device is
emu.
l If the serial port mode of the device is emu, go to Step 3.
l If the serial port mode of the device is not emu, go to Step 2.
Step 2 Run the serial-mode emu command to set the serial port mode to emu. Run the display emu
command to check whether the EPS30-4815AF is in Normal state.
l If the EPS30-4815AF is in Normal state, it indicates that the fault occurs due to the
improper serial port mode. Go to Step 10.
l If the EPS30-4815AF is not in Normal state, go to Step 3.
Step 3 Check whether the sixth switch of the DIP switch on the EPS30-4815AF is set to off.
l If the sixth switch of the DIP switch on the EPS30-4815AF is set to off, go to Step 5.
l If the sixth switch of the DIP switch on the EPS30-4815AF is not set to off, go to Step 4.
Step 4 When the serial port mode of the MA5612 is emu, the baud rate of the serial port is 19200 bit/
s. In this case, set the sixth switch of the DIP switch on the EPS30-4815AF to off and the baud
rate to 19200 bit/s that is the same as the baud rate of the serial port on the MA5612. Run the
display emu command to check whether the EPS30-4815AF is in Normal state.
l If the EPS30-4815AF is in Normal state, go to Step 10.
Step 5 Check whether the dedicated environment monitoring cable connecting the EPS30-4815AF to
the serial port on the MA5612 is aged, exposed, or broken out.
l If the dedicated environment monitoring cable connecting the EPS30-4815AF to the serial
port on the MA5612 is aged, exposed, or broken out, go to Step 6.
l If the dedicated environment monitoring cable connecting the EPS30-4815AF to the serial
port on the MA5612 is not aged, exposed, or broken out, go to Step 7.
Step 6 Replace the dedicated environment monitoring cable connecting the EPS30-4815AF to the serial
port on the MA5612. Run the display emu command to check whether the EPS30-4815AF is
in Normal state.
Step 7 Check whether the settings of the DIP switch on the EPS30-4815AF are the same as the settings
of the secondary nodes of the EMU on the MA5612.
l If the settings of the DIP switch on the EPS30-4815AF are the same as the settings of the
secondary nodes of the EMU on the MA5612, go to Step 9.

l If the settings of the DIP switch on the EPS30-4815AF are different from the settings of
the secondary nodes of the EMU on the MA5612, go to Step 8.
Step 8 Set the DIP switch on the EPS30-4815AF or run the emu add command to configure the
secondary nodes of the EMU on the MA5612 again so that the settings of the DIP switch on the
EPS30-4815AF are the same as the settings of the secondary nodes of the EMU on the
MA5612. Run the display emu command to check whether the EPS30-4815AF is in Normal
state.
Assistance).
Step 10 End.
----End

Maintenance Guide 8 Common Operation
8 Common Operation
About This Chapter
This topic describes the prerequisite, tools, impact on the system, and procedure of common
operations of the device.
8.1 Performing a Loopback on an E1 Line

The E1 line loopback is also called the 2M link physical loopback. When the services carried
on an E1 port are abnormal, you can perform a loopback on the E1 line to check whether the E1
port is normal and whether the internal communication of the system is normal.
8.2 Performing a Loopback on an E1 Port
When the services carried on an E1 port are abnormal, you can perform a loopback on the E1
port to locate a fault. When the result of the 8.1 Performing a Loopback on an E1 Line is
abnormal, you can perform this operation to further locate the fault.
8.3 POTS Subscriber Circuit Line Test
The POTS subscriber circuit line test is used to test certain functions (such as ringing, power
feeding, and dialing tone) and parameters (such as feed voltage and ringing current voltage) of
the internal circuit of the board. The test result is used to locate faults.
8.4 POTS Subscriber Loop Line Test
The POTS subscriber loop line test is used to test the performance or indexes (such as the
capacitance and resistance between lines) of the subscriber loop line. The test result is used to
check whether the subscriber loop line is faulty.
8.5 POTS Subscriber Search Tone Test
The search tone test allows an MA5612 to send a voice signal with a certain frequency and
amplitude to a plain old telephone service (POTS) line. A maintenance engineer then checks
whether the POTS line receives the signal on the peer side using a phone receiver or other special
instrument. This method helps to determine whether the line is faulty. In addition, the search
tone test helps to locate a specific line among multiple lines.
8.6 POTS Subscriber Signal Tone Test
A signal tone test emulates a plain old telephone service (POTS) user's off-hook, triggering the
system to send a test tone signal to a port on a voice service board. The port then sends the signal
back to the system. By detecting the sent-back test tone signal, engineers can determine whether
the system has processed the user off-hook operation and detected test tone signals properly,

helping them rectify hardware faults related to off-hook and playing of dial tone, busy tone, and
ringback tones.
8.7 POTS Port Loop Test
There are two kinds of loop tests: hardware tests and service tests. Loop tests used to test the
hardware and data configuration associated with the plain old telephone service (POTS) service.
Test personnel can use the test results to locate service faults.
8.8 Call Emulation Test
The call emulation test is used to emulate a voice user to make a call, and then check whether
the configuration of the voice service is correct based on the test result. When the voice service
is faulty, the result of the call emulation test is used to locate faults.
8.9 PPPoE Dialup Emulation Test
In the PPPoE dialup emulation test, the test device is emulated as the PPPoE client to perform
the dialup test on the BRAS. Thus, the test is used to check whether the PPPoE dialup is
successful through the check on the connectivity between the MA5612 and the BRAS. When
the PPPoE dialup fails, the result of the PPPoE dialup emulation test is used to locate faults.
8.10 Multicast Emulation Test
In the multicast emulation test, the test device is emulated as the multicast user to request for
programs. Thus, the test is used to check whether the communication between the device and
the multicast program source is normal through the check on whether the multicast program
stream arrives at the device. When the multicast user fails to request for programs, the result of
the multicast emulation test is used to locate faults.
8.11 DHCP Dialup Emulation Test
In Dynamic Host Configuration Protocol (DHCP) dialup emulation, an MA5612 simulates a
DHCP client and applies for an IP address from a DHCP server. The DHCP emulation tests
connectivity between the MA5612 and the DHCP server and verifies the DHCP configurations
on a DHCP relay, DHCP proxy, and DHCP server.
8.12 Capturing Voice Packets Remotely
You need to collect fault information such as signaling information and Dbwin information to
locate a fault when the voice service is faulty. This topic describes how to use the remote voice
packet capture function to obtain fault information and locate a fault, reducing onsite
maintenance workload.
8.13 Capturing Packets by Using Port Mirroring
Capturing packets on an Ethernet port allows you to monitor the traffic on a device, diagnose
network faults, and analyze the data. This requires a packet capture tool connected to the uplink
Ethernet port, which may interrupt the service on the uplink Ethernet port. Port mirroring
function allows you to mirror the packets on an Ethernet port to an idle Ethernet port and to
capture the packets to the destination port, preventing service interruption on the source port.
This topic describes how to capture packets by using port mirroring on an Ethernet port.

8.1 Performing a Loopback on an E1 Line

The E1 line loopback is also called the 2M link physical loopback. When the services carried
on an E1 port are abnormal, you can perform a loopback on the E1 line to check whether the E1
port is normal and whether the internal communication of the system is normal.
Prerequisites
The services carried on the E1 port must run normally before a fault occurs. That is, the tested
loop must carry service streams.

l E1 self-loop line (When an accurate test for the signal quality is not required, use the E1
self-loop line to perform the loopback on the E1 line.)
l Bit error meter (When an accurate test for the signal quality is required, use the bit error
meter to perform the loopback on the E1 line.)

l Performing a loopback on the E1 line requires the disconnection of the E1 line. In this case,
all the services carried on the E1 port are interrupted. Therefore, perform the loopback
when the E1 line carries the minimum traffic.
l After the loopback is performed on the E1 line, the broadcast storm may occur if the E1
port is not isolated. Therefore, it is recommended that you cancel the loopback in time after
the loopback test is complete.
Precautions
None
Procedure
Step 1 Connect the transmit and receive ends of the tested E1 line to the E1 self-loop line or the
corresponding ports on the bit error meter, and ensure that they are in good contact.
Step 2 Verify the loopback result.

l When you use the E1 self-loop line to perform the loopback, run the display port state
command to query the status of the port involved in the loopback. If the port is in the normal
state, it indicates that the E1 port works in the normal state and the internal communication
of the system is also normal.
l When you use the bit error meter to perform the loopback, you can determine whether the
E1 port and the internal communication of the system are normal through the indication
(whether there is a signal stream or not) on the bit error meter. In addition, you can determine
the signal quality of the line according to the indication on the bit error meter.
----End

References
The E1 line loopback is also called the 2M link physical loopback. It is a type of hardware
loopbacks, namely, the loopback on a manually created hardware loop. Figure 8-1 shows the
E1 line loopback.
Figure 8-1 E1 line loopback
E1 line loopback
interface module
Port processing
Backplane
module E1 self-loop line

Board or bit error meter
8.2 Performing a Loopback on an E1 Port

When the services carried on an E1 port are abnormal, you can perform a loopback on the E1
port to locate a fault. When the result of the 8.1 Performing a Loopback on an E1 Line is
abnormal, you can perform this operation to further locate the fault.
Prerequisites
None

Emulation terminal (such as the E10 meter)
NOTE
The emulation terminal is optional. When you perform a remote loopback if no service stream is carried
on the tested link, you can use the emulation terminal to emulate the peer device to send packets. In addition,
you can determine the link status according to the indication on the meter. When you perform a local
loopback, the emulation terminal is not needed, but you can still determine the link status according to the
indication on the meter.

l After the port loopback is configured, the port cannot forward data packets correctly, and
all the services carried on the port are interrupted. Therefore, backup the service data before
performing the loopback, or perform the operation when the port carries the minimum
traffic.

l After the port loopback is configured, the broadcast storm may occur if the E1 port is not
isolated. Therefore, it is recommended that you run the undo loopback command to cancel
the loopback in time after the loopback test is complete.
Precautions
The loopback cannot be configured if the E1 port is in any of the following states:
l Idle
l Blocked
The loopback of each E1 port is configured independently and only one type of loopback can
be configured each time. That is, if you need to configure another loopback after configuring a
loopback, you need to cancel the existing loopback and then configure another loopback.
Procedure
l Configure a remote loopback on the E1 port.
1. (Optional; perform this operation when using the emulation terminal.) Connect the
transmit and receive ends of the E1 line on the tested E1 port to the corresponding
ports on the emulation terminal, and ensure that they are in good contact.
2. Start the remote loopback on the E1 port.
For example, run the loopback command in TDM mode to start the remote loopback
on port 0/1/0.
huawei(config-if-tdm-0/1)#loopback 0 remote
3. Verify the loopback result.

By checking whether the peer device receives the signal sent by itself (for example,
if the remote loopback is started on a port, the user of the peer device should hear the
voice of himself/herself when making calls), you can determine whether the tested
link is accessible. If an emulation terminal such as the E10 meter is used, you can
determine the result according to the indication on the meter.
l Configure a local loopback on the E1 port.
1. (Optional; perform this operation when using the emulation terminal.) Connect the
transmit and receive ends of the E1 line on the tested E1 port to the corresponding
ports on the emulation terminal, and ensure that they are in good contact.
2. Start the local loopback on the E1 port.
For example, run the loopback command in TDM mode to start the local loopback
on port 0/1/0.
huawei(config-if-tdm-0/1)#loopback 0 local
3. Verify the loopback result. By checking whether the local device receives the signal
sent by itself (for example, if the local loopback is started on the port, the user of the
peer device should hear the voice of himself/herself when making calls), you can
determine whether the tested link is accessible. If an emulation terminal such as the
E10 meter is used, you can determine the result according to the indication on the
meter.
----End
References
The E1 port on the device supports two types of loopbacks.

l Local loopback
l Remote loopback
Local loopback on the E1 port
Local loopback, also called inloop, is the loopback from the port processing module of the board
to the backplane. In the local loopback, the signals that are transmitted from the backplane to
the E1 port are directly sent back to the backplane to check whether the board that houses the
E1 port can communicate with the backplane normally. Figure 8-2 shows the local loopback on
the E1 port.
Figure 8-2 Local loopback on the E1 port

interface module
Port processing
Backplane
module
Local loopback
Board
Remote loopback on the E1 port
Remote loopback, also called outloop, is the loopback from the port processing module of the
board to the line. In the remote loopback, the signals that are transmitted from the peer device
to the port processing module are directly sent back to the peer device to check whether the
board that houses the E1 port can communicate with the peer device normally. Figure 8-3 shows
the remote loopback on the E1 port.
Figure 8-3 Remote loopback on the E1 port

emulation terminal
interface module
Port processing
Peer device or
Backplane
module
Remote loopback
Board
8.3 POTS Subscriber Circuit Line Test

The POTS subscriber circuit line test is used to test certain functions (such as ringing, power
feeding, and dialing tone) and parameters (such as feed voltage and ringing current voltage) of
the internal circuit of the board. The test result is used to locate faults.

Context
l The user port to be tested must not be configured with any semi-permanent connection
(SPC) service.
l The circuit line test (the test mode is mandatory test on busy) interrupts the services carried
on the port to be tested.
l The user port to be tested must be normal.
Procedure
Step 1 In test mode, run the pots circuit-test command to perform the POTS subscriber circuit line
test.
Step 2 Check whether the POTS subscriber circuit line is faulty according to the test result.
----End
Result
The fault can be located and troubleshot according to the test result.
Reference
In many cases, the abnormality of certain functions (such as the signal tone, polarity reversal,
and ringing) of the voice service is caused by the internal circuit. Therefore, the circuit line test
can be used to check whether the functions or parameters of the internal circuit are normal. This
helps locate the faults.
8.4 POTS Subscriber Loop Line Test

The POTS subscriber loop line test is used to test the performance or indexes (such as the
capacitance and resistance between lines) of the subscriber loop line. The test result is used to
check whether the subscriber loop line is faulty.
Context
l The user port to be tested must not be configured with any SPC service.
l The loop line test (the test mode is mandatory test on busy) interrupts the services carried
on the port to be tested.
l The user port to be tested must be normal.
Procedure
test.
Step 2 Check whether the POTS subscriber loop line is faulty according to the test result.
----End

Result
The conclusions of the POTS subscriber loop line test are as follows:
l Normal: The subscriber loop line is normal.
l Touching the power line: The subscriber loop line touches the power line.
l Line A mixed with other lines: Line A touches other subscriber loop lines.
l Line B mixed with other lines: Line B touches other subscriber loop lines.
l Line A and line B mixed with other lines: Line A and line B touch other subscriber loop
lines.
l Line A grounding: Line A is connected to the ground.
l Line B grounding: Line B is connected to the ground.
l Line A and line B grounding: Line A and line B are connected to the ground.
l Self-mixing (small resistance and self-touch wire): Line A touches line B.
l A-B poor insulation: The insulation between line A and line B is poor.
l A-ground leakage: Creepage to ground occurs on line A.
l B-ground leakage: Creepage to ground occurs on line B.
l Creepage of line A and line B to ground: Creepage to ground occurs on line A and line B.
l Telephone unconnected: The subscriber loop line is not connected to a phone or the
subscriber loop line is broken.
l Off-hook: The phone of the subscriber is offhook.
The fault can be located and troubleshot according to the preceding conclusions.
Reference
In many cases, the voice service faults (such as there is no tone after offhook or there is noise
during the communication) are caused by the subscriber loop line. Therefore, the subscriber loop
line test is used to check whether the subscriber loop line is normal. This helps locate the faults.
8.5 POTS Subscriber Search Tone Test

The search tone test allows an MA5612 to send a voice signal with a certain frequency and
amplitude to a plain old telephone service (POTS) line. A maintenance engineer then checks
whether the POTS line receives the signal on the peer side using a phone receiver or other special
instrument. This method helps to determine whether the line is faulty. In addition, the search
tone test helps to locate a specific line among multiple lines.
Context
l The search tone test does not depend on the service status of a port. In other words, the test
is executed after being started.
l The search tone test cannot be implemented when other tests are being performed, such as
the circuit line test, subscriber line test, emulation test, signal tone test, and loop test.
l The search tone test cannot be performed when the port is prohibited.

Procedure
Step 1 Run the pots search-tone-test frameid/slotid/portid test-flag enable command in test mode to
start the search tone test for a POTS user.
Step 2 Use a phone receiver or other special instrument to check whether the tested line receives the
signals.
Step 3 (Optional) Run the pots search-tone-test frameid/slotid/portid test-flag disable command to
stop the search tone test.
NOTE
The duration of the search tone can be set as required.

l When the pre-set duration of the search tone is reached, the system automatically stops the test. No manual
intervention is required.
l Before the pre-set duration is reached, you can run the command in step 3 to stop the test.
Step 4 Check whether the POTS loop line is faulty based on the test result.
----End
Reference
Figure 8-4 shows the procedure for the search tone test.
Figure 8-4 Procedure for the search tone test
The test procedure is as follows:

l After a maintenance engineer starts the search tone test, the test module sends a voice signal
(indicated by the blue wave-line in Figure 8-4) with a certain frequency and amplitude to
the line.
l The maintenance engineer checks whether the line receives the signal using a phone
receiver or other special instrument. If the line receives the signal successfully, the line is
functional.

8.6 POTS Subscriber Signal Tone Test

A signal tone test emulates a plain old telephone service (POTS) user's off-hook, triggering the
system to send a test tone signal to a port on a voice service board. The port then sends the signal
back to the system. By detecting the sent-back test tone signal, engineers can determine whether
the system has processed the user off-hook operation and detected test tone signals properly,
helping them rectify hardware faults related to off-hook and playing of dial tone, busy tone, and
ringback tones.
Prerequisites
l The POTS port must be in the on-hook state during a signal tone test.
Context
l A signal tone test can be performed for the following tones:
– Dial tone
– Special dial tone
– Busy tone
– Ringback tone
l The signal tone test can be performed when digital signal processing (DSP) resources are
available. The test result will be affected if the port goes off-hook during the test.
l The signal tone test cannot be performed when other tests are being performed, such as the
circuit line test, subscriber line test, emulation test, search tone test, and loop test.
l No signal tone test is allowed on a port that is prohibited or is in a loopback.
Procedure
Step 1 Run the pots signal-tone-test frameid/slotid/portid command in test mode to start the signal
tone test for POTS users.
Step 2 (Optional) Run the undo pots signal-tone-test frameid/slotid/portid command to stop the signal
tone test.
NOTE
The playing duration of the signal tone can be set as required. Before the pre-set duration expires, you can run
the command in step 2 to stop the test.
Step 3 Check whether the circuit line is faulty based on the test result.
----End
Reference
Figure 8-5 shows the procedure for the signal tone test.

Figure 8-5 Procedure for the signal tone test
Loopback
Plays signal tones
CODEC SLIC
Detects returned
signal tones
DSP chip Voice service

board
The test procedure is as follows:

l After an engineer starts the signal tone test, the DSP chipset sends a test tone signal to a
port on the service board.
l The voice service board emulates the user's off-hook, sets up a voice channel, and sends
the voice signal back to the DSP chipset (indicated by the blue line in Figure 8-5).
l If the DSP chipset detects the sent-back test tone signal, the signal tone test is successful.
8.7 POTS Port Loop Test

There are two kinds of loop tests: hardware tests and service tests. Loop tests used to test the
hardware and data configuration associated with the plain old telephone service (POTS) service.
Test personnel can use the test results to locate service faults.
Prerequisites
l Voice service has been configured.
l If the dialup mode of a public switched telephone network (PSTN) port is set to DTMF-
only, the loop test cannot be performed.
NOTE
Run the display pstnport attribute command in pstnport mode to query Dial-Mode on the PSTN port.
l Do not take the phone off the hook during a loop test. Otherwise, the test result may be
inaccurate.
Context
A loop test can be one of two types:
l Hardware test: Used to check whether the hardware of a voice service module is normal.
l Service test: Used to check the voice service provisioning capability of the device.
Procedure
l Perform a hardware test on a port.
1. Run the pots path-test frameid/slotid port portid type hardware command in test
mode to perform a hardware loop test on the port.
2. (Optional) Run the undo pots path-test frameid/slotid command to stop a loop test.

3. The test result is displayed after the test is complete.

l Perform a service test on a port.
1. Run the pots path-test frameid/slotid port portid type business command in test
mode to perform a service loop test on the port.
2. (Optional) Run the undo pots path-test frameid/slotid command to stop a loop test.
3. The test result is displayed after the test is complete.
----End
8.8 Call Emulation Test

The call emulation test is used to emulate a voice user to make a call, and then check whether
the configuration of the voice service is correct based on the test result. When the voice service
is faulty, the result of the call emulation test is used to locate faults.
Prerequisites
l The voice service must be configured.
l A normal phone must be provided.
Context
l Currently, the MA5612 supports the call emulation of one voice user at a time.
l During the call emulation test, ensure that the emulation terminal is on-hook.
l The call emulation includes the calling party emulation test, the called party emulation test,
and the call emulation test. If a voice service is faulty, the user can choose one of the
preceding emulation tests to locate faults.
Procedure
Step 1 Run the pots emulational config command in test mode to configure the parameters for the call
emulation test.
The type of the call emulation alert tone and DTMF number must be set before the automatic
call emulation test is performed on the port.
By default, the type of the call emulation alert tone is voice announcement.
Step 2 Run the display pots emulational configuration command to query the parameters configured
for the current call emulation test.
Step 3 Start the call emulation test.
l The procedure for performing a called party emulation test is as follows:
1. The user runs the pots emulational-callee callee-port command to start the called party
emulation test on the voice service port.
2. The calling party that uses the test phone calls the called party.
3. After hearing ringing tones, the called party automatically picks up the phone.
4. After hearing announcements, the calling party presses * to confirm the off-hook.
5. The device exports the emulation test result. The called party emulation test is complete.

l The procedure for performing a calling party emulation test is as follows:

1. The user runs the pots emulational-caller caller-port command to start the calling
party emulation test on the voice service port.
2. The calling party calls the called party that uses the test phone.
3. After hearing ringing tones, the called party picks up the phone.
4. After hearing announcements, the called party presses * to confirm the off-hook.
5. The device exports the emulation test result. The calling party emulation test is
complete.
l The procedure for performing a call emulation test is as follows:
1. The user runs the pots emulational-call command to start the call emulation test on the
voice service port.
2. The device automatically performs the test and exports the emulation test result.
----End
Result
After completing the call emulation test, the device directly outputs the test result. The test result
is used to check whether the call is normal.
Reference
In a calling or called part emulation test, the voice service port on the MA5612 can be used for
the calling or called party manually. A call emulation test is a test in which two ports on the
MA5612 work as the calling and called parties respectively. In this case, the system emulates
on-hook and off-hook by the calling and called parties without manual operations and stops the
test after the call lasts several minutes.
The test phone is placed in the test station. The call emulation test can be performed between
this phone set and the user configured on the MA5612. In this manner, you can remotely check
whether the voice service on the MA5612 is normal.
The call emulation test can be used only to check whether the communication on the network
side of the device is normal.
8.9 PPPoE Dialup Emulation Test

In the PPPoE dialup emulation test, the test device is emulated as the PPPoE client to perform
the dialup test on the BRAS. Thus, the test is used to check whether the PPPoE dialup is
successful through the check on the connectivity between the MA5612 and the BRAS. When
the PPPoE dialup fails, the result of the PPPoE dialup emulation test is used to locate faults.
Context
l The configuration of the PPPoE user is correct.
l If the VLAN that the service stream belongs to is QinQ VLAN, the MA5612 does not
support the PPPoE dialup emulation.
l Currently, the MA5612 supports the dialup emulation of one user at a time.

NOTE
The PPPoE dialup emulation is performed through the software, which occupies the CPU resources. Therefore,
it is recommended that you perform the PPPoE dialup emulation when the system is not busy.
Procedure
Step 1 Run the pppoe simulate start command to perform the PPPoE dialup emulation test.
huawei(config)#pppoe simulate
{ start<K>|stop<K> }:start
Command:
pppoe simulate start
Service-port(index<0-511>):0
User Name(length<1,65>):user-0
User Password(length<0,16>):*******
Authentication Mode:
1. Chap 2. Pap [default 1]:1
Overtime Time(5-60s)[default 5]:10
NOTE
When performing the PPPoE dialup emulation test, do as follows:

l Specify the service stream ID and name of the PPPoE user, the password, authentication mode, and emulation
timeout time.
l Set the user name, password, and authentication mode on the MA5612 to be the same as those on the BRAS.
Step 2 Run the display pppoe simulate info command to query the status of the PPPoE dialup
emulation.
Step 3 Run the pppoe simulate stop command to stop the PPPoE dialup emulation test.
----End
Result
The result of the PPPoE dialup emulation test is as follows:
Run the display pppoe simulate info command to query the status of the PPPoE dialup
emulation.
huawei(config)#display pppoe simulate info
PPPoE simulate information is:
-----------------------------------------------------------------
Service-port: 0
User name: user-0
Current phase: - //*Emulation phase
Result: Success //*Emulation result
Start time: 2011-07-13,15:52:46
End time: 2011-07-13,15:52:46
Session ID: 591
User IP: 192.168.1.172
Gateway IP: 192.168.1.1
-----------------------------------------------------------------
l If the emulation result is "Success", it indicates that the PPPoE dialup passes the BRAS
authentication and the dialup is successful.
l If the emulation result is not "Success", locate faults according to "emulation phase" and
"emulation result".
Reference
The differences between the PPPoE dialup emulation and the PPPoE dialup are as follows:

l The PPPoE dialup emulation is performed by the MA5612 and the PPPoE dialup is started
by a PC, modem, or home gateway.
l The MAC address of the PPPoE dialup emulation packet is the bridge MAC address of the
MA5612. The MAC address of the PPPoE dialup is the MAC address of a PC, modem, or
home gateway.
8.10 Multicast Emulation Test

In the multicast emulation test, the test device is emulated as the multicast user to request for
programs. Thus, the test is used to check whether the communication between the device and
the multicast program source is normal through the check on whether the multicast program
stream arrives at the device. When the multicast user fails to request for programs, the result of
the multicast emulation test is used to locate faults.
Context
l The configuration of the multicast user is correct.
l The multicast user for whom the multicast emulation test is performed has the rights to
watch the configured multicast programs.
l The multicast service that is configured in the dynamic controllable multicast mode does
not support the multicast emulation test.
Procedure
Step 1 Run the igmp static-join user command to perform the multicast emulation test for the multicast
user.
Step 2 Run the display igmp user command to query the status of the multicast user.
l If the multicast is in offline state, it indicates that the multicast user fails to request for
programs.
l If the multicast is in online state, it indicates that the multicast user requests for programs
successfully.
Step 3 Run the display multicast flow-statistic command to query the real-time traffic of the programs
that the multicast user requests for in the multicast emulation test.
l If the real-time traffic of the multicast programs is 0, it indicates that the multicast source
does not deliver multicast programs or the multicast service stream does not arrive at the
device. That is, the communication between the device and the multicast source is abnormal.
l If the real-time traffic of the multicast programs approaches the bandwidth of the multicast
programs, the multicast source delivers the multicast programs to the device. That is, the
communication between the device and the multicast source is normal.
----End
Result
Run the display igmp user command to query the status of multicast user in the multicast
emulation test.
huawei(config)#display igmp user 1
User : 0/1/0
State : online //*Status of the multicast user
Authentication : auth

Quick leave : MAC-based

IGMP flow ID : 500
Video flow ID : 500
Log switch : enable
Bind profiles : 2
IGMP version : IGMP v3
Current version : IGMP v3
Current IGMP IPv6 version : IGMP IPv6 v2
Available programs : 10
Global leave : disable
User max bandwidth : no-limit
Used bandwidth(kbps) : 0
Used bandwidth
to max bandwidth(%) : -
Total video bandwidth : -
Mcast video bandwidth : -
Bound profile list
---------------------------------------------
Index Profile name Program number
---------------------------------------------
0 profile0 2
1 Profile1 8
---------------------------------------------
Total: 2
Active program list
---------------------------------------------------------------------------
Program name VLAN IP/MAC State Start-time
---------------------------------------------------------------------------
PROGRAM-0 8 228.0.0.1 watching 2011-03-15
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
16:02:38+08:00
---------------------------------------------------------------------------
Total: 10
After the query, it is found that multicast user 1 is online. That is, emulating a multicast user to
request for programs is successful.
Run the display multicast flow-statistic command to query the real-time traffic of multicast
programs.
huawei(config-btv)#display multicast flow-statistic ip 224.1.1.1 vlan 4002
Command is being executed, please wait...
Multicast flow statistic result: 296(kbps)
After the query, it is found that the real-time traffic of multicast program whose IP address is
224.1.1.1 is 296 kbit/s, that is, the multicast source delivers the traffic.
8.11 DHCP Dialup Emulation Test

In Dynamic Host Configuration Protocol (DHCP) dialup emulation, an MA5612 simulates a
DHCP client and applies for an IP address from a DHCP server. The DHCP emulation tests

connectivity between the MA5612 and the DHCP server and verifies the DHCP configurations
on a DHCP relay, DHCP proxy, and DHCP server.
Context
l DHCP user configuration is correct.
l An MA5612 initiates DHCP dialup emulation. A PC, set top box (STB), or voice over IP
(VoIP) terminal initiates common DHCP dialup.
l An MA5612 supports a maximum of five DHCP dialup emulation tests at a time.
Procedure
Step 1 Run the simulate dhcp start command to start a DHCP dialup emulation test.
Before running this command, run the service-port command to configure a service port for the
user. Ensure that the service port parameters are the same as those of the actual service.
Otherwise, the emulation fails to start.
Step 2 Run the display simulation dhcp command to query the status of the DHCP dialup emulation.
Only the status of an ongoing DHCP dialup emulation test can be queried. When a DHCP dialup
emulation test is stopped or times out, the resources used by the DHCP dialup emulation are
released and the emulation status cannot be queried. The default emulation timeout period is
210s.
Step 3 Run the simulate dhcp stop command to stop the DHCP dialup emulation test.
----End
Result
The result of the DHCP dialup emulation test is as follows:
Run the display simulation dhcp command to query the status of the DHCP dialup emulation.
huawei(config)#display simulation dhcp
{ <cr>|service-port<K> }:service-port
{ service-portid<U><0-511> }:0
{ mac-address<P><XXXX-XXXX-XXXX> }:0000-1111-2222
Command:
display simulation dhcp service-port 0 0000-1111-2222
Total : 1
-----------------------------------------------------------------------------
-------------------------------- common info --------------------------------
FlowID : 0
User MAC : 0000-1111-2222
User VLAN : 10
Optin60 : HW
Option61 type : 1
Option61 client : 0000-1111-2222
Simulate status : finished //
*Emulation status
Simulate result : partial ping succeed //
*Emulation result
Simulate start time : 2011-06-17 16:51:59+08:00
User IP : 192.168.3.100/24
DHCP server IP : 192.168.3.8
Primary DNS server IP : -
Secondary DNS server IP : -
Relay gateway : 0.0.0.0
Default gateway : 192.168.3.201
-------------------------------- route info ---------------------------------

Route:1 Destination IP : 192.168.5.0/24 Next hop IP : 192.168.3.66

Next hop MAC : - Local interface : -
Route:2 Destination IP : 192.168.4.0/24 Next hop IP : 192.168.3.88
Next hop MAC : 00ee-51f0-dbba Local interface : Y
Route:3 Dstination IP : - Next hop IP : -
Next hop MAC : - Local interface : -
--------------------------------- ping info ---------------------------------
Host:1 IP : 192.168.3.99 Total count : 3 Succeed count : 3
-----------------------------------------------------------------------------
l If the emulation result is "get IP successful", the DHCP dialup is successful.

l If the emulation result is not "get IP successful", locate the fault according to "Simulate
status" and "Simulate result."
8.12 Capturing Voice Packets Remotely

You need to collect fault information such as signaling information and Dbwin information to
locate a fault when the voice service is faulty. This topic describes how to use the remote voice
packet capture function to obtain fault information and locate a fault, reducing onsite
maintenance workload.
Context
The remote voice packet capture function involves basic packet capturing and extended packet
capturing.
l In basic packet capturing, media streams, upper-layer protocol packets, and DSP-related
trace information are captured. DSP is the acronym for digital signal processing.
l In extended packet capturing, signaling and Dbwin packets are captured besides media
streams, upper-layer protocol packets, and DSP-related trace information.
Prerequisite
l The system CPU usage is less than or equal to 80%. If you enable the remote packet capture
function when the system CPU usage is greater than 80%, the system CPU may overload,
causing service interruptions. In addition, the extended packet capturing cannot be enabled.
Specifically, an error message is displayed if users attempt to enable the function using
commands. No error message is displayed if users attempt to enable the function by pressing
a button.
l The packet capture server is equipped with a remote packet capture software such as
Ethereal, and communicates with the MA5612 successfully. The packet capture server can
be a network management system (NMS) or a PC that can communicate with the
MA5612 successfully.
Procedure
Step 1 Configure user and server parameters on the MA5612, and enable the remote packet capture
function for the faulty port.
1. Run the remote-capture parameters server-ip ip-address udp-port udp-port-value
source-ip source-ip-address command in diagnose mode to configure parameters for the
remote packet capture server.

Ensure that the source IP address can ping the IP address of the remote packet capture
server.
2. Run the remote-capture trace trace-value frame/slot/port frame/slot/port command to
configure user information.
Step 2 Start the remote packet capture software and wait until all required packets are captured.
Step 3 Run the undo remote-capture trace command on the MA5612 to stop capturing packets.
----End
Result
After required packets are captured, you can analyze captured data.
8.13 Capturing Packets by Using Port Mirroring

Capturing packets on an Ethernet port allows you to monitor the traffic on a device, diagnose
network faults, and analyze the data. This requires a packet capture tool connected to the uplink
Ethernet port, which may interrupt the service on the uplink Ethernet port. Port mirroring
function allows you to mirror the packets on an Ethernet port to an idle Ethernet port and to
capture the packets to the destination port, preventing service interruption on the source port.
This topic describes how to capture packets by using port mirroring on an Ethernet port.
Context
Figure 8-6 shows the cable connection in port mirroring and packet capturing.
Figure 8-6 Cable connection in port mirroring and packet capturing
Uplink port
Packet capture
tool
Source port Destination port
Description: In the preceding figure, the source port is the uplink port of a device, namely, the
Ethernet port on which packets are to be captured. The packets transmitted through the source
port are mirrored to the destination port. A packet capture tool is connected to the destination
port for capturing the packets.
The packet capture tool (for example, the Ethereal) can be installed on a PC that is connected
to the destination port by using a network cable. (If the destination port is an optical port, an O/
E converter can be used for signal converting.)

Prerequisite
l The source port and destination port for mirroring must be Ethernet ports.
l The destination port cannot be an aggregated port.
l The destination port can be a METH port.
l The devices must be connected according to Figure 8-6.
Procedure
Step 1 Verify that the current Ethernet ports can be used for port mirroring.
1. Run the display board 0/0 command to verify that the source port and destination port are
Ethernet ports.
If the source port and destination port are not Ethernet ports, it cannot be used for port
mirroring.
2. Run the display link-aggregation all command to verify that the destination port is not an
aggregated port.
l If the destination port is an aggregated port, determine whether to cancel port
aggregation based on site requirements.
– If port aggregation can be canceled, run the undo link-aggregation command to
cancel port aggregation. After packet capture operation is complete, run the link-
aggregation command to restore port aggregation.
NOTE
Port aggregation implements port protection and load sharing among the ports in an aggregation
group. After port aggregation is canceled, load sharing cannot be implemented. As a result, packets
may be lost when the traffic is heavy. Therefore, exercise caution when canceling port aggregation.
– Port mirroring cannot be performed if port aggregation is configured.
Step 2 In ETH mode, run the mirror port command to configure port mirroring.
Step 3 Run the display mirror command to verify that port mirroring is configured successfully.
Step 4 Start the packet capture tool to capture packets until the required packets are captured.
Step 5 Run the undo mirror port command to disable the port mirroring.
Step 6 Run the display mirror command to verify that port mirroring is disabled successfully.
----End
Result
After the packets are captured, you can analyze the packets.

Maintenance Guide 9 FAQ
9 FAQ
About This Chapter
Analyze and answer the frequently asked questions of operating and maintaining the device.
9.1 How Is the Broadband Service Board Powered Off Automatically When the Battery Supplies
Power

Maintenance Guide 9 FAQ
9.1 How Is the Broadband Service Board Powered Off

Automatically When the Battery Supplies Power
Question
How is the broadband service board powered off automatically when the battery supplies power
to the MA5612?
Answer
The MA5612 is configured with EPS30-4815AF. Run the broad-service power-off
shutdown command to power off the broadband service board automatically when the battery
supplies power to the MA5612 after the AC power supply is interrupted.
When the external battery supplies power to the MA5612 after the AC power supply is
interrupted, the MA5612 powers off the broadband service board. In this case, the voice service
board can work in the normal state and the battery can supply power to the MA5612 for a longer
time.

Maintenance Guide A Appendix
A Appendix
This topic provides the reference information for maintaining the MA5612.
A.1 Indicators
The MA5612 provides a variety of indicators on its panel to help users learn about the running
status of the device.
A.2 Making Cables and Connectors
This topic describes how to make the power cable, ground cable, and network cable.
A.3 Cable Labels
This topic describes how to make, fill in, and attach the cable label.
A.4 Fault Tag
This is the fault tag provided for the repair or the part replacement.

A.1 Indicators
The MA5612 provides a variety of indicators on its panel to help users learn about the running
status of the device.
Figure A-1 and Table A-1 list the LEDs on the panel of the MA5612.
Figure A-1 LEDs on the panel of the MA5612
Table A-1 Indicators on the MA5612
LED Description
LINK (Link status) Green: on The uplink optical port is

receiving optical signals.
Green: off The uplink port does not

receive an optical signal.
AUTH/ACT Green: on The device is registered with

(Authentication status) the upper layer device
successfully. This status is
available only when data is
transmitted upstream through a
PON port.
Green: blinking l The device is registering

with the upper layer device
when data is transmitted
upstream through a PON
port.
l The port is transmitting or
receiving data when data is
transmitted upstream
through a GE port.
Green: off The uplink port does not

receive an optical signal.
PWR: Power LED Green: on The device is powered by

batteries.
Green: off The device is powered off.

LED Description
RUN/ALM: Running Red: on for 0.25s and off for The device is starting up.
LED 0.25s repeatedly
Green: on for 1s and off for 1s The device works in the normal
repeatedly state.
Red: on The device is faulty.
SYNC: Clock Green: on Clock synchronization success

synchronization LED or the system is not configured
clock source.
Red: on Clock synchronization fails.
LED of the POTS port Green: on At least one service port is busy.
LED: off All the ports are idle.
LED of the FE electrical Green: on A connection is set up on the

port port.
LED: off No connection is set up on the

port.
Green: blinking The port is transmitting or

receiving data.
A.2 Making Cables and Connectors

This topic describes how to make the power cable, ground cable, and network cable.
A.2.1 Making Console-Ethernet Integrated Cables

When a device is running, the serial port on the device can be used as a maintenance serial port
and a network port at the same time. Therefore, a console-Ethernet integrated cable is needed
to support the concurrent use of the serial port. The console-Ethernet integrated cable is a type
of non-standard cable, which must be made on site as required.
Wire Sequence of a Console-Ethernet Integrated Cable

Figure A-2 shows the wire sequence of a console-Ethernet integrated cable.

Figure A-2 Wire sequence of a console-Ethernet integrated cable
A.2.2 Making External Power Cables and Ground Cables with Cord
End Terminals
This topic describes how to make external power cables and ground cables with cord end
terminals.
Recommended Tools and Materials

The recommended tools and materials for making external power cables and ground cables with
cord end terminals are as follows:
l Wire crimping tool

l Hydraulic clump
l Power cables
l Insulating tape
l Paper cutter
l Diagonal pliers
l Wire clipper
l Cord end terminals
Procedure
Step 1 Use the paper cutter to peel off a section of the insulation layer from the power cable based on
the cross-sectional areas of the power cable conductors. A section of the power cable conductor
with a length of L1 is exposed, as shown in Figure A-3. Table A-2 lists the recommended lengths
of the insulation layer to be peeled off (L1).

Figure A-3 Peeling the insulation layer off the power cable
L1
Power cable
Conductor
CAUTION
When peeling off the insulation layer of the power cable, ensure that the conductor of the power
cable is not scratched.
Table A-2 Mapping between the cross-sectional area and the length of insulation layer to be
peeled off (L1)
Cross-sectional Area (mm2) L1 (mm)
1 8
1.5 10
2.5 10
4 12
6 14
10 15
16 15
25 18
35 19
50 26
Step 2 Insert the conductor of the peeled power cable into the cord end terminal, as shown in Figure
A-4.

Figure A-4 Inserting the conductor into the cord end terminal
Power cable
Cord end terminal
CAUTION
After the cord end terminal is inserted into the power cable, the conductor of the power cable
outside the cord end terminal should not be longer than 1 mm.
Step 3 Select a proper cross-sectional area, and use power cable crimping pliers to clamp the head of
the cord end terminal and the conductor of the power cable, as shown in Figure A-5.
Figure A-5 Clamping the cord end terminal
2.0 mm 2 4.0 mm2
1.0 mm2 6.0 mm 2

2.5 mm2
Rough side
----End
A.2.3 Making External Power Cables and Ground Cables with OT

Terminals
This topic describes how to make external power cables and ground cables with OT terminals.
Recommended Tools and Materials

The recommended tools and materials for making external power cables and ground cables with
OT terminals are as follows:

l Hydraulic clump
l Power cables
l Insulating tape
l Paper cutter
l Diagonal pliers
l Wire clipper
l OT terminals
l Heat shrink tubing
l Hot air gun
Procedure
Step 1 Insert the power cable into the heat shrink tubing A, as shown in Figure A-7.
Step 2 Peel off a section of the insulation layer C from the power cable based on the cross-sectional
areas of the power cable conductors. A section of power cable conductor D with a length of L1
is exposed, as shown in Figure A-6. Table A-3 lists the recommended lengths of the insulation
layer to be peeled off (L1).
Figure A-6 Peeling off the insulation layer of the power cable
C
L1
CAUTION
l When peeling off the insulation layer of the power cable, ensure that the conductor of the
power cable is not scratched.
l If the bare crimping terminals are not provided by Huawei, you can adjust L1 according to
the length of the crimping terminal. L1 = L + (1 or 2) mm.

Table A-3 Mapping between the cross-sectional area and the length of the insulation layer to
be peeled off (L1)
Cross-Sectional Area (mm2) L1 (mm)
1 7
1.5 7
2.5 7
4 8
6 9
10 11
16 13
25 14
35 16
50 16
NOTE
If you peel off the insulation layer off the power cable properly on site, you can compare the cable with
the connector to be crimped.
Step 3 Insert the bare conductor of the power cable into the OT terminal B, and then press the OT
terminal close to the insulation layer C, as shown in Figure A-7.
Figure A-7 Installing heat shrink tubing and bare crimping terminal
L2
C

CAUTION
After the OT terminal is installed, the length of the bare conductor outside the bare crimping
terminal (L2) must not be more than 2 mm. If the length (L2) of the bare conductor outside the
bare crimping OT terminal is larger than 2 mm, cut the redundant part by using the diagonal
pliers or wire clipper, as shown in Figure A-7.
Step 4 Use the crimping tool to clamp the tail of the bare crimping terminal and the contact part of the
conductor, as shown in Figure A-8.
Figure A-8 Clamping the tail of the bare crimping terminal with the contact part of the conductor
NOTE
The crimped shapes vary with the crimping molds.
Step 5 Push the heat shrink tubing A towards the connector, and cover the crimping area of the bare
crimping terminal and the conductor. Use a hot air gun to heat the heat shrink tubing, as shown
in Figure A-9.
CAUTION
Do not heat the heat shrink tubing for a long time. Otherwise, the insulation layer may be
damaged.

Figure A-9 Installing the heat shrink tubing
----End
A.2.4 Making Ordinary Network Cables

This topic describes how to make ordinary network cables.
Components of an Ordinary Network Cable

An ordinary network cable consists of two ordinary RJ45 connectors and one category-5
unshielded twisted pair (UTP-5) cable. Figure A-10 shows an ordinary network cable.
Figure A-10 Ordinary network cable
RJ-45 connector Boot
UTP-5 twisted pair
Checking Tools and Materials

Check the following items:
l Ensure that the necessary tools, such as the diagonal pliers, a blade (or knife), and the crimp
pliers, are available.
l Ensure that the materials, such as the RJ45 connectors, UTP-5 twisted pair, and the jacket,
are available.

l Ensure that the jacket is in proper condition. If the jacket is convex, plucked, or damaged,
cut the improper part off the cable.
Procedure
Step 1 Use the diagonal pliers to cut the cable according to the required length.
Step 2 Put the cable through the boot for 100 mm at least. Ensure that the boot is installed in the correct
direction, as shown in Figure A-11.
Figure A-11 Installing the boot for the RJ45 connector
Cable end where the RJ-45

connector is to be installed
100 mm
Step 3 Use a blade or a knife to peel off 20 mm of the jacket, as shown in Figure A-12. Do not damage
the insulation of the wires.
Figure A-12 Peeling the jacket
Twisted pair
20 mm
Step 4 Arrange the four pair of wires properly according to the connection sequence of the network
cable.
Step 5 Ensure that the wires are 13 mm to 15 mm long. Cut off the extra length of the wires, arrange
the wires in the correct order, and then insert the wires into the RJ45 connector, as shown in
Figure A-13. Table A-4 lists the wires assigned to the network cable.

Figure A-13 Assigning the wires to the network cable
Wires arranged according to

the order of network cables
Table A-4 Wires assigned to the network cable

Wire Wire Color
Straight- Straight- Crossover Crossover

Through Cable Through Cable Cable End A Cable End B
End A End B
1 White and orange White and orange White and orange White and green
2 Orange Orange Orange Green
3 White and green White and green White and green White and orange
4 Blue Blue Blue Blue
5 White and blue White and blue White and blue White and blue
6 Green Green Green Orange
7 White and brown White and brown White and brown White and brown
8 Brown Brown Brown Brown
NOTE
In Table A-4, end A and end B refer to both ends of a network cable.
Step 6 Use the crimp pliers to crimp the connector. Ensure that the connector is put correctly in the
crimp pliers. After crimping, the metal cover on the connector must be lower than other area on
the connector.
Step 7 Use a network cable tester or a multimeter to test all wires, and ensure that the wires are connected
properly.
Step 8 Push the boot to cover the RJ45 connector, as shown in Figure A-14.

Figure A-14 Pushing the boot to cover the RJ45 connector
----End
A.2.5 Making Shielded Network Cables

This topic describes how to make shielded network cables.
Components of a Shielded Network Cable

A shielded network cable consists of two shielded RJ45 connectors and one super-UTP-5 cable.
Figure A-15 shows the shielded network cable.
Figure A-15 Shielded network cable

RJ45 connector Boot
Super-UTP-5 cable
Shielded iron cover
Checking Tools and Materials

Check the following items:
l Ensure that all necessary tools, such as the diagonal pliers, crimp pliers, blades or knives,
are available.
l Ensure that the necessary materials, such as the shielded RJ45 connectors and the super-
UTP-5 cables, are available. Figure A-16 shows the shielded RJ45 connector, which has
a shielded iron cover and a wire fastening slot.
l Ensure that the jacket is in proper condition. If the jacket is convex, plucked, or damaged,
cut the improper part off the cable.

Figure A-16 Components of a shielded RJ45 connector

Metal cover on the RJ45 connector
Wire fastening slot

Shielded iron cover
Boot
Plastic cover of the
RJ45 connector
Procedure
Step 1 Install the boot for the RJ45 connector.
1. Select a cable of proper length and install the boot on the RJ45 connector of the cable.
2. Use a blade or a knife to peel off 30 mm of the jacket.
3. Use a blade to slit 5 mm on the jacket and install a shielded iron cover on the cable weaving
layer, and then insert the shielded iron cover into the jacket along the crack. Install the boot
and the shielded iron cover correctly, as shown in Figure A-17.
Figure A-17 Installing the boot for the RJ45 connector and the shielded metal cover
Step 2 Install the wires.
CAUTION
When peeling off the jacket of the power cable, do not damage the cable weaving layer or the
insulation wires.
1. Use the diagonal pliers to cut 20 mm off the cable weaving layer, ground wire, aluminum
foil and polyester band at the head of the cable, and store the wires.
2. Arrange the four twisted pairs properly and insert them into the wire fastening slot. Maintain
the original space for the twisted pairs.
3. Arrange the wires smoothly and straightly at the hole of the cable distribution frame.
Arrange the wires properly and cut off the extra length of the wires along the edge of the
wire fastening slot. Table A-4 lists the wires assigned to the network cable.
4. Install the plastic cover on the wire fastening slot, and then fasten the slot. Push the cover
into the slot until you hear click to ensure that the cover is fitted properly, as shown in
Figure A-18.

Figure A-18 Installing the wires
Step 3 Crimp the RJ45 connector.

1. Insert the RJ45 connector into the metal cover.
2. Use the diagonal pliers to crimp the metal part on the RJ45 connector. Ensure that the
conductors inside the wires are properly connected to the metal part and the RJ45 connector
is placed correctly. After crimping, the metal part on the connector must be lower than the
height of the plastic cover.
3. Use the network cable tester or a multimeter to check and ensure that the wires are connected
properly.
4. Insert the RJ45 connector into the jacket, as shown in Figure A-19.
Figure A-19 Crimping the RJ45 connector

----End
A.2.6 Making the E1 Cable

This topic describes how to make the E1 cable.
Making the E1 Cable with the Straight SMB Female Connector

This topic describes how to make the E1 cable with the straight SMB female connector.
Recommended Tools
The recommended tools for making the E1 cable with the straight SMB female connector are
as follows:
l Wire stripper
l Diagonal pliers
l Wire clipper
l Electric soldering iron
l Tin wire
l Hot air gun
l Paper cutter
l marker
Component
Figure A-20 shows the components of the straight SMB female connector and the coaxial cable.
Figure A-20 Components
C
D
E
F
A: Press-fitting sleeve B: Plug of the connector C: Coaxial jacket
D: Outer conductor of the coaxial E: Insulation layer of the coaxial F: Inner conductor of the coaxial
cable cable cable

Procedure
Step 1 For the coaxial cable made of different materials, peel the coaxial cable to expose its outer
conductor (D), insulation layer (E), and inner conductor (F) according to the lengths shown in
Figure A-21. The lengths of the reserved outer conductor, the reserved insulation layer, and the
exposed jacket are L1, L2, and L3 respectively, as listed in Table A-5.
Figure A-21 Structure of the coaxial cable
L3
L2
L1
D
E
F
CAUTION
l When peeling the coaxial cable, do not damage the outer conductor or the shielded layer of
the coaxial cable.
l You can determine the length of the part to be peeled according to the length of the connector,
as shown in Figure A-22.
Table A-5 Peeled lengths of commonly used coaxial cables
L2 L3
Cable Type External Diameter L1 (mm) (mm) (mm) Remarks
SYFVZ-75-1 2.2 mm 5-6 7-9 10-12 -

-1(A)
SYV-75-2-2 3.9 mm 5-6 7-9 10-12 Dedicated to

national
backbone
155M-I
SYV-75-4-2 6.7 mm 5-6 7-9 10-12 Dedicated to

national
backbone
155M-III
SFYV-75-2-1 3.2 mm 5-6 7-9 10-12 Dedicated to

national
backbone-II

L2 L3
Cable Type External Diameter L1 (mm) (mm) (mm) Remarks
SFYV-75-2-2 4.4 mm 5-6 7-9 10-12 Dedicated to

national
backbone
155M-II
Figure A-22 Lengths of connectors and the peeled part of cables
L1 L1
L2 L2
L3 L3
Step 2 Put a coaxial cable into press-fitting sleeve A, as shown in Figure A-23.
Figure A-23 Putting a coaxial cable into a sleeve
Step 3 Expand outer conductor D of the coaxial cable into a bell-mouthed shape as shown in Figure
A-24.
Figure A-24 Expanding the outer conductor of a coaxial cable

Step 4 Insert the inner conductor and the insulation part of the coaxial cable into plug B of the connector.
Wrap the outer conductor of the connector by using the outer conductor of the coaxial cable, as
shown in Figure A-25.
Figure A-25 Inserting a coaxial cable into a connector plug
Step 5 Solder inner conductor F of the coaxial cable with the inner conductor of plug B, as shown in
Figure A-26.
Figure A-26 Soldering the inner conductor
B F
Welding
NOTE
After the welding, make sure that there is no metal wire (especially of the outer conductor) or redundant
soldering tin between the inner conductor and the outer conductor. Use the multimeter to test the insulation
state between the inner conductor and the outer conductor. Then, press-fit the outer conductor.
Step 6 Push press-fitting sleeve A towards the connector. Compact the outer conductor of the coaxial
cable. Press-fit sleeve A and the plug of the coaxial connector by using press-fitting tools, as

Figure A-27 Press-fitting the outer conductor
----End
Follow-up Procedure
After assembling the cable components, install the components on devices, as shown in Figure
A-28.
Figure A-28 Installing the components of a coaxial cable
Making the E1 Cable with the Straight SMB Male Connector

This topic describes how to make the E1 cable with the straight SMB male connector.
Recommended Tools
The recommended tools for making the E1 cable with the straight SMB male connector are as
follows:
l Wire stripper
l Diagonal pliers
l Wire clipper

l Tin wire
l Hot air gun
l Paper cutter
l marker
Component
Figure A-29 shows the components of the straight SMB male connector and the coaxial cable.
D
E
F
A: Press-fitting sleeve B: Plug of the connector C: Coaxial jacket
D: Outer conductor of the coaxial E: Insulation layer of the coaxial F: Inner conductor of the coaxial
cable cable cable
Procedure
conductor (D), insulation layer (E), and inner conductor (F) according to the lengths shown in
CAUTION
the coaxial cable.

L3
L2
L1
D
E
F
Table A-6 Peeled lengths of commonly used coaxial cables
External L1 L3
Cable Type Diameter (mm) L2 (mm) (mm) Remarks
SYFVZ-75-1- 2.2 mm 5-6 7-9 10-12 -

1(A)
SYV-75-2-2 3.9 mm 5-6 7-9 10-12 Dedicated to national

backbone 155M-I

backbone 155M-III
SFYV-75-2-1 3.2 mm 5-6 7-9 10-12 Dedicated to national

backbone-II

backbone 155M-II
L1 L1
L2 L2
L3 L3

Step 3 Expand outer conductor D of the coaxial cable into a bell-mouthed shape as shown in Figure
A-33.
Figure A-33 Expanding the outer conductor of a coaxial cable
Step 4 Insert the inner conductor and insulation part of the coaxial cable into plug B of the connector.
Wrap outer conductor D of the connector by using the outer conductor of the coaxial cable, as

Step 5 Solder inner conductor F of the coaxial cable with the inner conductor of plug B, as shown in
Figure A-35.
Welding
NOTE
----End
Follow-up Procedure
A-37.

Making the E1 Cable with the Bent SMB Female Connector

This topic describes how to make the E1 cable with the bent SMB female connector.
Recommended Tools
The recommended tools for making the E1 cable with the bent SMB female connector are as
follows:
l Wire stripper
l Diagonal pliers
l Wire clipper
l Tin wire
l Hot air gun
l Paper cutter
l marker
Component
Figure A-38 shows the components of the bent SMB female connector and the coaxial cable.


B
E
F
G
A: Press-fitting sleeve B: Screw of the connector C: Plug of connector D: Coaxial jacket
E: Outer conductor of the F: Insulation layer of the G: Inner conductor of the

coaxial cable coaxial cable coaxial cable
Procedure
conductor (E), insulation layer (F), and inner conductor (G) according to the lengths shown in
L3
L2
L1
E
F
G

CAUTION
the coaxial cable.
Table A-7 Peeling lengths of commonly used coaxial cables

External L1 L2 L3
Cable Type Diameter (mm) (mm) (mm) Remarks
SYFVZ-75-1-1 2.2 mm 5-6 7-9 10-12

(A)

backbone 155M-I

backbone 155M-III

backbone-II

backbone 155M-II
L1 L1
L2 L2
L3 L3

Step 3 Insert the inner conductor and the insulation part of the coaxial cable into plug C of the connector.
Wrap outer conductor E of the connector by using the outer conductor of the coaxial cable, as
Step 4 Solder inner conductor G of the coaxial cable with the inner conductor of plug C, as shown in
Figure A-43.
Welding

NOTE
Step 6 Press-fit upper cover B on plug C of the connector, as shown in Figure A-45.
Figure A-45 Press-fitting the upper cover on the connector
----End
Follow-up Procedure
A-46.

A.3 Cable Labels

This topic describes how to make, fill in, and attach the cable label.
Labels are attached to the cables to identify the physical positions of the cables on different
devices. There are two types of cable labels: labels for the power cables and labels for the signal
cables.
The cable labels can facilitate the cable connection and maintenance.
NOTE
This information must be stated in the self-check report to help the customer to maintain consistency in
labeling the cables of the devices in the telecommunications room.
A.3.1 Introduction to Labels

This topic provides the materials, types, and structure of the labels. It also describes the
requirements for label printing and handwriting, attaching methods, label contents and
precautions.
Material Specification
The material features of the labels are as follows:
l Thickness: 0.09 mm.

l Color: Chalk white.
l Material: Polyester (PET).
l Applicable temperature: -29°C to +149°C.
l Compatible with laser printing or can be hand written by using oil markers.
l The material must pass the authentication of Underwriters Laboratories (UL) and Canadian
Standards Association (CSA).
Types
There are two types of cable labels: the label for the power cable and the label for the signal
cable.

Label for the Signal Cable

The label for the signal cable is L-shaped and of a fixed size. Figure A-47 shows the label for
the signal cable.
Figure A-47 Label for the signal cable
84.0
7.5
7.0
5.5
5.5 Dotted line
11.0 10.0
11.0 TO:
1.5
Dividing line
Dividing line
0.6
5.5
5.5
7.0 1.0
7.5 Dotted line
37.0 2.0
Unit: mm
The dividing lines on the label specify the position of a cable. For example, there is a dividing
line between the cabinet number and the subrack number, and a dividing line between the subrack
number and the slot number. The size of the dividing line is 1.5 mm x 0.6 mm, and its color is
PANTONE 656c (light blue).
The dotted lines mark the position for folding the label when you attach it to the cable.
There is a mark "TO:" (upside down in the figure) at the lower right corner of the label. The
mark identifies the peer end of the cable to which the label is attached.
Label for the Power Cable

The label for the power cable is attached to the identification plate on the cable ties. The size of
the bulge around the identification plate is 0.2 mm x 0.6 mm (symmetric on both sides), as shown
in Figure A-48.

Figure A-48 Label for the power cable

26.2 10 R1.0
TO:
12.2 11
25
0.6
Label paper
1.5
Cable tie
100 0.6
Dividing line on the
label
Unit: mm
A.3.2 Filling Labels

You can print the contents on the labels by using a printer or write the contents on the labels by
using an oil marker. For higher efficiency and nicer layout, it is recommended that you use a
printer.
Template for the Printing

You can obtain the template through the following two ways:
l Download the template from the technical support website "support.huawei.com". The path
is as follows: Related Links > Engineering Service > Engineering Quality > Quality
Standard and Template.
l Obtain the template from the Huawei local representative.
When using the Microsoft Word template, pay attention to the following requirements:
l You can modify the contents on the template according to the positions of the cables
installed on site. However, the settings of center, direction, and fonts of the characters on
the label cannot be changed.
l Generally, the size of the characters is not modified. When there are a lot of contents to be
filled in, change the font size of the characters. Make sure that the contents are clear and
legible.

Setting the Printer

To print the labels, use a laser printer. The type of the laser printer is not limited. Before printing
a label, set up the page and print on an ordinary paper as follows:
1. Place the ordinary printed paper on the label paper. Compare and check whether the printed
paper conforms to the label requirement.
2. Make sure that the printing properties, such as Paper Size and Direction, are set correctly.
If the printed paper meets the requirements, print the required content on the label paper.
Otherwise, adjust the page setup and print the required content again until you obtain the
correct printout. To adjust the page setup, do as follows:
a. Choose File > Page Setup.
b. Select Layout, set Header and Footer to 0.
c. Click the Margins tab. Select Left for Gutter Position. Adjust the values of Top,
Bottom, Left, and Right.
d. If the dialog box as shown in Figure A-49, is displayed before printing, click
Ignore to continue the printing.
Figure A-49 Warning prompt before the printing
After adjusting the page setup, save the printing properties. This page setup is required only
when you use the template for the first time.
Requirements for Feeding Labels in the Printer

The label paper is composed of two pages, and is different from the ordinary paper. Always feed
in the labels manually, one by one regardless of the model of the printer that you use. Do not
use the auto-feed mode to prevent the printer from getting jammed. Different models of printers
have different feeding positions for feeding the labels. Feed in the labels correctly.
Requirements for Printing Labels

The requirements for printing the labels are as follows:
l All the contents should be printed on the label. Ensure that the content is not printed at the
bottom of the label page.
l The contents in the cells should be aligned to the center. In the case of a single-line printout,
the dividing lines and the "TO" mark should not be covered by the printed characters.
l If you merge the cells and print in multiple lines, adjust the contents and do not cover the
"TO" mark. Use the spacebar to move the content to the next line.
Writing Tool

To maintain the labels legible and neat, use the black oil marker (excluding the ball pen) delivered
with the products to write on the labels.
In special cases, you can use a black ballpoint pen, although it is not recommended to use a
ballpoint pen. The oil marker is more effective compared to the ballpoint pen. When you use
the marker to write on the labels, ensure that the surface of the labels is not oily. The oil can
smudge the letters.
NOTE
The delivered marker has two nibs. Use the smaller nib to write on the labels.
Font
The handwritten font must be similar to the standard typeface "Times New Roman" so that it is
clear and legible. Table A-8 lists the standard typeface.
Table A-8 Standard typeface for handwriting
0 1 2 3 4 5 6 7 8
9 A B C D E F G H
I J K L M N O P Q
R S T U V W X Y Z
The typeface for handwriting should be of proper size. When you fill in the label in Chinese
font, the size of the Chinese font must be proper, and the Chinese font must be legible and neat.
Figure A-50 shows the writing direction.
Figure A-50 Writing direction on the label
1 A01 2 A 06
06 A 1 A01 2
TO:
A.3.3 Usage of Labels

This topic describes how to use the labels, the information on the labels, and the precautions to
be taken when using the labels.
Information Carried on Labels
The contents on the signal cable are different from the contents on the power cable.

For the Signal Cable

The two sides of the label attached to the signal cable indicate the location of the ports connected
to both ends of the cable, as shown in Figure A-51.
l Area 1 contains the location information about the cable end to which the label is to be
attached.
l Area 2 (with the "TO:" mark) contains the location information about the other end of the
cable.
l Area 3 is folded between area 1 and area 2.
Figure A-51 Printing parts on the label for the signal cables
Area 1
Area 3
Area 2 TO:
If the label is viewed from the cable leading-out area, it appears on the right side of the cable.
The side with "TO:" that faces outward indicates the peer end; the other side indicates the local
end. Therefore, the information in Area 1 at one end of the signal cable is the same as the
information in Area 2 at the other end of the cable.
For the Power Cable

The label for the power cable is attached only to one side of the identification plates. The
information (the part after the mark "TO:") on the label indicates the location of the peer end
device, control cabinet, cable distribution box or socket of the cable end to which the label is
attached.
Precautions for Using Labels
Pay attention to the following items when using the labels:
l When you print, write, or attach labels, ensure that the labels are clean.
l Do not use ink-jet printers or ink pens to print or write on the labels because the label paper
is made up of moisture proof and waterproof material.
l Attach labels neatly. The new label is of striped type. The appearance of the product is
affected if the attaching position or direction is not correct.
l Bundle the cable ties at the same height, and place all identification plates in the same
direction.
l The positions of "up", "down", "right", and "left" in this topic (excluding the description
of printer setting) are viewed when you face the labels.

A.3.4 Attaching Labels

After printing or writing the label on the base page, remove the label from the base page, and
then attach the label to the cable or the identification plate of the cable tie. The following
describes how to attach the label for the signal cable and the power cable.
Attaching the Label to the Signal Cable

Attach the label to the signal cable, 2 cm away from the connector. In special cases, for example,
to avoid bending the cable or affecting other cables, attach the label at a different position on
the cable.
The labels should be attached to both ends of a cable. When the cable is placed vertically, the
label should point towards the right. When the cable is placed horizontally, the label should point
downwards. Figure A-52 shows how to attach the label to the signal cable at a proper position.
Figure A-52 Attaching the label to the signal cable at a proper position
TO: TO:
1 A01 2
1 A01 2 A 06
A 06
Figure A-53 shows how to attach the label to the signal cable.

Figure A-53 Attaching the label to the signal cable

Affixing side
2-3 mm
TO:
1 A01 2 A 06
Attaching the Label to the Power Cable

Remove the label from the bottom of the label page, and then attach it to the concave part on
one side of the identification plate. The cables can be attached on either side of the identification
plate, but ensure that the label directions are consistent in the telecommunications room. The
cable tie should be fastened 2 cm away from the connectors. In special cases, the labels can be
attached at other positions.
Cable ties should be fastened at both ends of a cable. After bundling the cables, the completed
identification plate should be visible on the top of the cable in the horizontal cabling, or on the
right side of the cable in the vertical cabling. Make sure that the label points outwards, as shown
in Figure A-54.

Figure A-54 Appearance of the label attached to the power cable

Cable
TO:
B03 -48V2
B03
TO:
-48V2
Cable
1-The identification plate is on top 2-The identification plate is at the right

of the cable in horizontal cabling side of the cable in vertical cabling
A.3.5 Label for External Alarm Cables

This topic provides information on labels and example of labels for external alarm cables.
The external alarm cables are connected to the first cabinet that provides power supply of each
row. Labels attached to the first cabinet must indicate the access terminal distribution for the
devices. Labels are not required to be attached to the device unless it is required. Here, only Area
2 of the label should be filled in.
Table A-9 describes the information on the label for the external alarm cable.
Table A-9 Information on the label for the external alarm cable
Content Meaning Example
MN MN: Cabinet l M: Cabinet row, numbered A to Z from front to back.

number. l N: Cabinet column, numbered 01 to 99 from left to right.
For example:
A01: Cabinet in row A and column 01.
NOTE
Generally, the preceding numbering method helps identify the position of a specific cabinet. If two cabinets
are installed back to back, the front direction of the cabinet must be specified. Hence, the numbering method
MNO is used. "O" indicates the direction of the cabinet, which can either be "A" or "B." This numbering
method is also used for the cable labels described in the following sections.
You need to fill only a part of the text area because the label on the alarm cable provides basic
information. It is recommended you reserve the entire length of the label. Do not cut off the
blank area.
Figure A-55 shows a label on the alarm cable. "A01" indicates that the alarm cable is connected
from the first cabinet to the cabinet in row A, column 01.

Figure A-55 Example of the label on the alarm cable
A01
TO:
A.3.6 Label for Network Cables

This topic describes the application scope, content, and meaning of the label for the network
cable, and provides the example of filling in the label.
Application
The labels for the network cables are attached to the network cables that connect to the boards,
or the labels for the network cables are attached to the cables that connect to the hubs, servers
or agents of the value added service (VAS) devices.
Meaning of the Label

Table A-10 describes the information on the label for the network cable that connects to the
board.
Table A-10 Information on the label for the network cable
MN-B-C-D MN: Cabinet "A01" indicates the first cabinet in row A.

number
B: Subrack The subracks are numbered from bottom to top. 01 indicates

number the lowest subrack.
C: Slot The slots are numbered from top to bottom and from left to
number right. 01 indicates slot 1 of the subrack.
D: Network The ports are numbered from top to bottom and from left to
port number right. 01 indicates the first network port.
MN-Z MN: Cabinet "B02" indicates the second cabinet in row B.

number
Z: Position of You can fill the number that indicates the position of the
the terminal terminal device according to actual conditions.
device l For the router connected to the cabinet, specify the cabinet
number, subrack number, and network port number of the
router, such as B02-03-12.
l For the NMS workstation, specify the specific location.

For the network cables that connect to the hubs, servers, or agents of the VAS devices, the
information on the labels is provided according to the actual conditions.
l For the cable from the hub to the server, specify the cabinet number and subrack number
where the hub is located, and specify the serial number on the hub. Specify the cabinet
number and subrack number where the server is located. For a stand-alone server, specify
the specific position of the server.
l For the cable from the hub to the agent, specify the serial number of the network port on
the agent end. The cabinet number and the subrack number should be the same as the cabinet
number and the subrack number described in Table A-10.
l For a stand-alone hub that is not installed in any subrack or cabinet, specify its recognizable
position.
Specify the serial number on the hub, the network port number of the agent and the position of
the stand-alone server according to the actual conditions.
Example of the Label

Figure A-56 shows the label for the network cable.
Figure A-56 Example of the label for the network cable
A01-03-10-05
B02-03-12
TO:
l "A01-03-10-05" indicates that one end of the network cable is connected to Ethernet port
05, slot 10, subrack 03 of the cabinet in row A, column 01.
l "B02-03-12" indicates that the other end of the network cable is connected to Ethernet port
12, subrack 03 of the cabinet in row B, column 02. The slot number is not specified.
A.3.7 Labels for Optical Fibers

This topic provides information on labels and example of labels for optical fibers. There are two
types of labels that are used for optical fibers: one for the optical fiber connecting two cabinets
and one for the optical fiber connecting the cabinet to the ODF.
Meaning of the Label for Optical Fiber Connecting Two Cabinets

Table A-11 describes the information on the label for the optical fiber connecting two cabinets.
Table A-11 Information on the label for the optical fiber connecting two cabinets
MN-B-C-D-R/ MN: Cabinet number A01 indicates the first cabinet in row A.
T

B: Subrack number The subracks are numbered from bottom to

top. 01 indicates the lowest subrack.
C: Slot number The slots are numbered from left to right

and from top to bottom. 01 indicates slot 5
of the subrack.
D: Optical port number The optical port is numbered from left to

right and from top to bottom. 05 indicates
the fifth optical port.
R: Optical receiving -
interface
T: Optical transmitting
interface
MN-B-C-D-R/ MN: Cabinet number It is the same as the preceding example.

T When the local cabinet and the opposite
B: Subrack number cabinet are not in the same telecommunica-
C: Slot number tions room, MN indicates the name of the
telecommunications room.
D: Optical port number
R: Optical receiving
interface
interface
Example of the Label on the Optical Fiber Connecting Two Cabinets

Figure A-57 shows the label on the optical fiber connecting two cabinets.
Figure A-57 Example of the label on the optical fiber connecting two cabinets
A01 01 05 05 R
G01 01 01 01 T
TO:
l "A01-01-05-05-R" indicates that one end of the optical fiber is connected to the optical
receiving interface 05 in slot 05, subrack 01 in the cabinet in row A, column 01.
l "G01-01-01-01-T" indicates that the other end of the optical fiber is connected to optical
transmitting interface 01 in slot 01, subrack 01 in the cabinet in row G, column 01.

Meaning of the Label for Optical Fiber Connecting the Cabinet to the ODF
Table A-12 describes the information on the label for the optical fiber connecting the cabinet
to the ODF.
Table A-12 Information on the label for the optical fiber connecting the cabinet to the ODF
MN-B-C-D-R/T MN: Cabinet number A01 indicates the first cabinet in row A.
B: Subrack number The subracks are numbered from bottom to

top. 01 indicates the lowest subrack.

and from top to bottom. 01 indicates slot 5
of the subrack.
D: Optical port number The optical port is numbered from left to

right and from top to bottom. 05 indicates
the fifth optical port.
interface; T: Optical
transmitting interface
ODF-MN-B-C-R/ MN: ODF row and ODF M: numbered A to Z from front to back in
T column. each row.
N: numbered 01 to 99 from left to right.
G01: ODF in row G and column 01.
B: Row number of the Range: 01-99, such as 01.

terminal
C: Column number of the Range: 01-99, such as 01.

terminal
interface
interface
Example of the Label on the Optical Fiber Connecting the Cabinet to the ODF
Figure A-58 shows the label on the optical fiber connecting the cabinet to the ODF.
Figure A-58 Example of the label on the optical fiber connecting the cabinet to the ODF
ODF G01 01 01 R
T 05 05 01 A01
TO:

l "ODF-G01-01-01-R" indicates that one end of the optical fiber is connected to the optical
receiving terminal in row 01, column 01 of the ODF in row G, column 01.
l "A01-01-05-05-T" indicates that the other end of the optical fiber is connected to optical
receiving interface 05 in slot 05, subrack 01 in the cabinet in row A, column 01.
A.3.8 Label for Subscriber Cables

This topic provides information on labels and example of labels for subscriber cables.
The labels are attached to both ends of the subscriber cable to identify the positions of the cable
on the cabinet and the MDF.
Meaning of the Labels

Table A-13 describes the information on the labels for the subscriber cable.
Table A-13 Information on the labels for the subscriber cable

MN-B-C-D MN: Cabinet number A01 indicates the first cabinet in row A.
B: Subrack number The subracks are numbered from bottom

to top. 03 indicates the third subrack.

and from top to bottom. 01 indicates slot
1 of the subrack.
D: Cable number The cables are numbered from left to right

and from top to bottom. 01 indicates slot
1 of the subrack.
MDF-MN-B- MN: MDF number M: ODF row, numbered from A to Z. N:

C MDF column, numbered from 01 to 99.
G01 indicates the first MDF in row G.
B: Row number of the terminal Range: 01-99, such as 01-01.
C: Column number of the

terminal
Example of the Label

Figure A-59 shows the label for the subscriber cable.
Figure A-59 Example of the label for the subscriber cable
A01 03 01 01
MDF G01 01 01
TO:

l "A01-03-01-01" indicates that the local end of the subscriber cable is connected to terminal
01 in slot 01, subrack 03 of the cabinet in row A, column 01.
l "MDF-G01-01-01" indicates that the peer end of the subscriber cable is connected to the
terminal in row 01, column 01 of the MDF in row G, column 01.
A.3.9 Labels for DC Power Cables

This topic provides information on labels and example of labels for DC power cables.
The labels are attached to the DC cables of the DC-powered cabinet, including the -48 V, PGND
and BGND cables. The label for the DC power cable is attached to one side of the identification
plate on the cable tie.
Table A-14 shows the information on the label for the DC power cables.
Table A-14 Meaning of the label for the DC power cables

Content Meaning
MN(BC)- -48 V1 MN(BC): BC is written right below MN.

On the loaded cabinet side, only MN is used to identify the
MN(BC)- -48 V2
cabinet.
MN(BC)- BGND On the power distribution device side:
MN(BC)- PGND l MN identifies the row and column numbers of the power
distribution device such as the control cabinet and power
distribution box.
l BC identifies the row and column numbers of the -48 V
connector. If the row number or the column number does
not exist, or the connector can be identified without the row
or column number, BC can be omitted.
The BGND and the PGND cables do not require the row or the
column number.
The label indicates only the location of the peer end, control cabinet or distribution box.
Information about the local end is not required. Table A-14 lists the information about the two
inputs of the -48 V power supply on the label. The information about other DC voltages (such
as 24 V, 60 V) should be written in a similar way. Make sure that the labels are attached in the
correct direction. After the cable ties are bundled on to the cable, the identification plates with
the labels should point upward.
The contents on the cable labels in the same cabinet should be in the same direction, as shown
in Figure A-60.

Figure A-60 Example of the labels on the DC power cable
TO:
A01 -48V2
B08
Label on the loaded cabinet side (position of the

cable on the power distribution cabinet side)
TO:
B03 -48V2
Label on the power distribution frame side

(position of the cable on the loaded cabinet side)
l On the loaded cabinet side, the label marked as "A01/B08- -48 V2" indicates that the cable
is used for the -48 V2 DC supply. The cable is routed from the 8th connector in row B of
the -48 V busbar in the power distribution cabinet in row A, column 01.
l On the power distribution cabinet side, the label marked as "B03- -48 V2" indicates that
the cable is used for the -48 V2 DC supply. The cable is routed from the loaded cabinet in
row B, column 03.
The label context is listed:
l In the power distribution cabinet (or the first power cabinet of a row in the transmission
telecommunications room), each terminal on the -48 V connector bar has a numeric
identification. For example, such as "08" (also mentioned as "8") in the label "A01/B08-
-48 V2."
l The PGND and the BGND are two copper bars. The terminals are directly connected to
these copper bars. Therefore, the connection of any of the terminal does not affect the
distribution of the power supply. Only the row and column numbers of the power
distribution cabinet are required. For example, if the label on the loaded cabinet side is
"A01-BGND", the power cable is a BGND cable that is connected to the BGND copper
bar in the power distribution cabinet in row A, column 01. The information on the labels
for the PGND cables must be provided in the similar way.
A.3.10 Labels for AC Power Cables

This topic provides information on labels and example of labels for AC power cables.
The labels are attached to the AC cables, including the 110/220 V, BGND and PGND cables
that supply power to the cabinets. Labels are attached to both ends of the cable. The 110/220 V,

BGND, and PGND cables have the insulation sheath. Hence, you only need to write "AC" and
the cabinet number on each label.
The labels for AC power cables are attached to one side of the identification plate on the cable
tie. Table A-15 describes the meaning of the label for the AC power cable.
Table A-15 Meaning of the label for the AC power cable
Content Meaning
MN-AC MN: Cabinet number or the power socket position. Power socket: Mark the
positions clearly to avoid confusion. If the sockets have multiple rows and
columns, identify their positions as the cabinet.
The label only indicates the location of the peer end or socket. Information about the local end
is not required. Ensure that the labels are attached in the correct direction. After the cable ties
are bundled onto the cable, the identification plates with the labels must point upward, as shown
in Figure A-61.
Figure A-61 Example of the labels on the AC power cable
TO: TO:
A01 AC B01 AC
Label on the loaded cabinet side Label on the power distribution

(position of the cable on the power cabinet side (position of the cable
distribution cabinet side) on the loaded cabinet side)
l On the loaded cabinet side, the label marked as "A01-AC" indicates that the cable is routed
from the power socket in row A and column 01.
l On the power distribution cabinet side, the label marked as "B01-AC" indicates that the
cable is routed from the loaded cabinet in row B and column 01.
A.4 Fault Tag

This is the fault tag provided for the repair or the part replacement.
*Customer's Name:
Address:
Contact person:

Tel.: Fax:
Category*: RMA Return Analysis
BOM Goods Bar Fault Description Category Software

Code Description Code* occurring of the Fault No.* Version*
Date* Phenomena*
Reasons for Repairing (Category No.):

Category No. includes the following 8 types:
l F001–wear out damaged (In warranty Period, Out of Warranty Period)
l F002–deployment damaged
l F003–intransit damaged
l F004–Version upgrade
l F005–batch replace
l F007–overdue spare parts inspecting
l F008–Others
l F011–running circumstance change

Notes:
l For optical boards that are returned, the optical interface should be covered with a safety
cap.
l As usual, the analysis board will not be returned to you , if you have any special
requirements, please contact the technical support.
l Make sure that a fault tag is associated to one return category, such as RMA, Return or
Analysis.
l Please notice the mark "*" is the necessary content that you must fill in.


Smartax Ma5612 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Smartax Ma5612 2

Uploaded by

Copyright:

Available Formats

SmartAX MA5612 Multi-service Access Module

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2012-07-25) Huawei Proprietary and Confidential i

About This Document

This document is intended for:

l System maintenance engineers

Indicates a hazard with a high level of risk which, if not

Indicates a hazard with a medium or low level of risk which,

Indicates a potentially hazardous situation that, if not

Indicates a tip that may help you solve a problem or save

Issue 01 (2012-07-25) Huawei Proprietary and Confidential ii

Provides additional information to emphasize or

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in square brackets [ ] are

{ x | y | ... } Alternative items are grouped in braces and separated by

[ x | y | ... ] Optional alternative items are grouped in square brackets

{ x | y | ... } * Alternative items are grouped in braces and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the “>”

Issue 01 (2012-07-25) Huawei Proprietary and Confidential iii

The contents in 4 Troubleshooting Services Transmitted Through a GE Port and 5

Issue 01 (2012-07-25) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

2 Field Maintenance Guide............................................................................................................6

4 Troubleshooting Services Transmitted Through a GE Port ...............................................29

Issue 01 (2012-07-25) Huawei Proprietary and Confidential v

4.3.3 Busy Tone After Offhook........................................................................................................................84

5 Troubleshooting Services Transmitted Through a GPON Port.......................................112

6 System Fault Handling.............................................................................................................199

Issue 01 (2012-07-25) Huawei Proprietary and Confidential vi

6.3 The Alarm Information Fails to Be Displayed on the NMS...........................................................................231

7 Troubleshooting EMU Faults..................................................................................................239

Issue 01 (2012-07-25) Huawei Proprietary and Confidential vii

A.3.8 Label for Subscriber Cables..................................................................................................................308

Issue 01 (2012-07-25) Huawei Proprietary and Confidential viii

About This Chapter

1.1 Maintenance Purpose

Issue 01 (2012-07-25) Huawei Proprietary and Confidential 1

1.1 Maintenance Purpose

1.2 Maintenance Principle

Principle of Routine Maintenance

Issue 01 (2012-07-25) Huawei Proprietary and Confidential 2

Principle of Parts Replacement

l Make sure that operations are feasible.

Principle of Maintaining an Outdoor Cabinet

Issue 01 (2012-07-25) Huawei Proprietary and Confidential 3

1.3 Maintenance Tools

Table 1-1 Maintenance tools

Multimeter Tests the

Optical power Tests the optical

Issue 01 (2012-07-25) Huawei Proprietary and Confidential 4

Tool Description Appearance

Adjustable Adjusts the optical

Flathead Fastens small

Cross Fastens small

Diagonal pliers Used as a substitute

Cable tie Bundles cables.

Network cable Clamp phone lines

Network cable Tests the

Issue 01 (2012-07-25) Huawei Proprietary and Confidential 5