GPON Troubleshooting

Training Objectives

 Understanding methods for troubleshooting.

 Understanding troubleshooting of system faults.
 Understanding troubleshooting of data service.
 Understanding troubleshooting of voice service.
 Understanding troubleshooting of IPTV service.

1
Contents

1 Common Methods for Fault Analysis

2 Troubleshooting Common System Faults

3 Troubleshooting Data Service Faults

4 Troubleshooting Voice Service Faults

5 Troubleshooting IPTV Service Faults

2
Routine Method for Faults Analysis

1. Instrument Test 7. Loopback Tests

2. LED Status Analysis 8. Comparison/Substitution

3. Alarm Analysis 9. Configuration Data Analysis

4. Signal Tracing 10. Status Call-back

5. Log Inspection 11. Optical Line Detection

6. Performance Analysis

3
Instrument Test
 Instrument Test: Using related instruments to measure the equipment
parameters and determine fault causes by comparing the measured values
with normal values.
 Instruments in common use are shown in the following table.
Item Purpose
Multimeter To measure voltage and current of the power system.
Network cable tester To test the connectivity of network cables.
Error detector To test whether the transmission link is normal.

 Application: The instrument test is used to exclude external factors and

hunter for the specific cause of fault.
 For example, a user on the ONU side fails to access the broadband service. In
this case, you can test the network cable between the ONU and the user's
computer with the network cable tester, and you will detect disconnectivity of
the signal line.
4
Status Indicator Analysis
 Definition: The AN5116-06B has operation indicator LEDs and status indicator
LEDs. These indicator LEDs directly reflect the operating status of each card, link
and optical path as well as their active and standby status. These indicators are
important for fault analysis and isolation.
 Purpose: Status indicator analysis is used to quickly approximate the fault
location or cause before the next treatment step. Through observing the indicator
LEDs on the cabinet, subracks and cards, maintenance staff can initially
ascertain and isolate a fault. Information provided by indicator LEDs is often
insufficient; therefore, the status indicator analysis is often used together with the
alarm analysis
 Application: The status indicator analysis is applied in cases where the cause
of the fault is in a relatively narrow scope.For example, when the ACT indicator
LED for the GC8B card of the AN5116-06B blinks slowly, the PON interface cards
are being initialized or the card software is being started, but the communication
between the active and standby cards cannot be set up.

5
Alarm Analysis
 Definition: Alarms are informative messages for various faults and events
during system operation. When the equipment fails, the system will report one or
more alarm messages to the network management system. Users can retrieve
the current alarms, historical alarms and the time an alarm occurred via the
UNM2000.
 Purpose: Alarm information analysis is one of the essential operations in fault
analysis and isolation.
 Application: The alarm information analysis is applied in cases where the fault
is relatively simple.
 For example, when you check the current alarms of the AN5116-06B and find
an alarm for system interruption, the communication between the equipment
reporting the current alarm and the network management server is interrupted.

6
Signal Tracing

 Definition: Signal tracing can trace and save on a real time basis the voice
service signaling interaction flow between the equipment and softswitch platform.

 Purpose: Maintenance personnel can directly acquire the cause of a call failure
by reviewing the signal trace, and thus provide valuable suggestions for

subsequent analysis and troubleshooting.

Application: Signal tracing is applied in shooting troubles with voice services.

 For example: a subscriber fails in making a voice phone call; signal tracing is

then performed and it is found that the ONU that the subscriber belongs to fails

to register in the MGC. A further inspection discovers an error in configuring the

endpoint user name of the ONU.

7
Log Inspection
 Definition: The UNM2000 supports query of command logs and registration
logs. In command logs, users can view the configuration data, configuration time
and command execution results; in registration logs, users can view the
registration name, IP address, registration time and whether a registration is
successful.
 Purpose: A fault may be caused by mistakes made by maintenance personnel
in course of data planning and configuration. In order to isolate this type of fault
quickly, maintenance personnel should view the system logs and analyze
historical configuration data.
 Application: The log inspection is applied to determine the specific cause of a
fault.
 For example, when you find an inconsistency between a configuration item
and the planning data during routine maintenance of the AN5116-06B, and
suspect that an illegal user has modified the equipment configuration data, you
can inspect the registration name, IP address, registration time of the user by
checking the logs.
8
Performance Analysis
 Definition: Performance statistics are for monitoring the equipment operation,
collecting and counting essential parameters during equipment operation.

 Purpose: Through data collection and analysis, maintenance personnel can

obtain adequate data on equipment operation. Performance analysis provides a
powerful means of diagnosing faults.

 Application: The performance analysis is applied in cases where the system

operation is unstable or the transmission rate is abnormal.

 For example, when the HSWA card of the AN5116-06B is restarted repeatedly
or runs slowly so that you cannot perform normal operation of the equipment,
you can monitor the CPU and memory utilization ratio of the HSWA card via
the real-time performance statistics function. Then you can analyze the
statistics data and ascertain whether the phenomenon is caused by excessive
occupation of the CPU or memory by programs.
9
Loopback Test
 Definition: The loopback test uses hardware or software methods to verify the
operational status of the equipment or a transmission channel by transmitting and
receiving a known signal or data pattern.
 Purpose: The purpose of a loopback test is to confirm the operational status of
the associated hardware or equipment and of the software parameter settings by
ascertaining whether the channel is performing normally during the test. The
loopback test is one of the most common ways for determining transmission
problems and relay parameter settings.
 Application: The loopback test is used to exclude faults in peripheral
equipment.
 For example, when a fault occurs in the TDM service of the AN5116-06B, you
can apply the loopback test to the TDM line. Details as follows:
 Internal loopback: checks whether the line from the E1 interface of the ONU
to the C155A card is faulty.
 External loopback: checks whether the line from the STM-1 interface of the
SDH device to the C155A card is faulty.
10
Comparison/Substitution
Definition:
 Comparison involves comparative analysis of faulty parts with the normal parts,
so as to find out differences, and then locate the problem.
 Substitution involves replacing a possibly faulty part with a normal part (such as
a card, an optical fiber), and then comparing the equipment operation before
and after the substitution, so as to determine fault scope or location. Refer to
AN5116-06B Optical Line Terminal Equipment Component Replacement for
details.
 Purpose: Comparison/substitution method is used to isolate fault point quickly.
 Application: The comparison/substitution method is generally used to exclude
the fault in peripheral equipment, determine the fault scope, and find out the
specific cause of the fault.
 For example, when the ONU of an GPON subscriber cannot be authorized
normally, you can isolate the fault by replacing the ONU or by comparing the
ONU with other ONUs under the same optical splitter to see whether the same
phenomenon occurs in other ONUs.
11
Configuration Data Analysis

 Definition: Configuration data analysis entails analyzing the fault cause by

viewing and analyzing current data configuration.

 Purpose: When the fault has been localized to the local system, analyzing the
current configuration data of the equipment can lead to identification of a
configuration error.

 Application: The configuration data analysis is applied in cases where the fault
is relatively simple.

 For example, when all subscribers under the AN5116-06B fail to use the voice
phone, you can find an error with the MGC address configuration through
configuration data analysis. This error contributes to abnormal registration of the
ONU in the MGC address table.

12
Status Call-back Definition
 Definition: Status call-back can trace current equipment configuration and
relevant parameters in a real-time manner.

 Purpose: Maintenance personnel can acquire relevant configuration data about

the equipment via status call-back, which can provide reference for subsequent
analysis and troubleshooting.

 Application: The status call-back is applied in cases where the cause of the
fault is in a relatively narrow scope.
 For example, when a subscriber under the AN5116-06B cannot access any
service carried by the equipment, and the REG indicator LED on the ONU
where the subscriber belongs to is extinguished, you can query the information
about the unauthorized ONU via the status call-back command on the
UNM2000. Accordingly, you will find that the OLT does not authorize the ONU;
and when you check the ONU physical address authentication white list, you
will find that the physical address of the ONU is not included into the white list.

13
Optical Line Detection
 The optical line detection is applied to handle the faults in optical line,
e.g. failure in registering an ONU, disconnection of a registered ONU, system
loss of packets, and light leakage. Below are the main detection measures:

Common optical power detection

 Tests the Tx optical power of the OLToptical module at the central office end.
Generally a normal measured value is about 0dbm.
 Tests the Tx optical power of the ONU optical module at the remote end. A
normal measured value is about 0dbm to 4dbm.
 Tests the Rx optical power of the ONU at the remote end. A normal measured
value is about -17dbm to -26dbm.

Leakage optical power detection

 Unplug the optical fiber from the optical module at the PON interface on the
OLT side, and connect the optical fiber to the Rx end of the optical power meter
dedicated for PON to test the uplink Tx optical power of all ONUs under the
PON.
14
Optical Line Detection
 Application

The optical line detection is applied to determine the specific cause of a

fault.

For example, when all the ONUs under No.1 PON interface on the C8B
card of the AN5116-06B report the fiber breakage alarm, you can use an
optical power meter dedicated for PON to measure relevant optical
power of the PON interface, so as to ascertain whether the optical
module is working normally.

15
Contents

1 Common Methods for Fault Analysis

2 Troubleshooting Common System Faults

3 Troubleshooting Data Service Faults

4 Troubleshooting Voice Service Faults

5 Troubleshooting IPTV Service Faults

16
Common System Faults

Card Faults

All Indicators Extinguished after Power-on

LOS Indicator of ONU illuminated

REG Indicator of ONU Being Abnormal

ONU Network Management Connection Failure

Network Interface Indicator Extinguished

Equipment Management IP Address Ping Timeout

Abnormal Link between Equipment and Switch

17
Card Faults
Fault Symptom
 The working indicator LED of a card is extinguished and the alarm indicator is
illuminated;
 The indicator LED remains extinguished after power-on of the card;
 The services carried by the card are interrupted;
 The active-standby communication between the card and its peer is interrupted.
 The services are normal but configuration commands cannot be issued;
 The card software cannot be started in a normal way.

Fault analysis
 Component or subcard damage;
 Arbitrary removal and/or insertion of the card;

Troubleshooting Procedure
 Restart the card
 Replace the card
18
All Indicators Extinguished after Power-on
Fault Symptom
 All indicators on the AN5116-06B are extinguished after power-on of the
equipment.

Fault analysis
 A fault occurs in the power system.
 The power cables are connected incorrectly.

Troubleshooting Procedure
 Check the power system in the equipment room, and contact related maintenance
personnel for repair if it has failed.
 Turn off the head of row cabinet and the PDP. Check whether the power cables
from the head of row cabinet to the PDP and from the PDP to the AN5116-06B
subracks are securely and properly connected. If not, reconnect the power cables.

19
LOS Indicator of ONU illuminated
Fault Symptom
 The LOS indicator LED of the ONU is illuminated.

Fault analysis
The LOS indicator on the ONU being illuminated indicates that the ONU is not
receiving the optical signal or the received optical power is too low. The possible
causes are shown below:
 The optical fiber connection is incorrect;
 The received optical power of the ONU is too low;
 An OLT device at the central office end is faulty, for example, a PON interface
card is faulty;
 The ONU equipment is faulty.

Fault analysis
 Check whether the ONU equipment operates normally or has abnormal.
 Check the connection of the optical fibers.
20
LOS Indicator of ONU illuminated
Fault analysis
 Connect the optical fiber dedicated for PON test to the PON optical power meter
and the PON port of the ONU respectively, and measure the received optical
power of the ONU. The normal range of the Rx optical power of the ONU is
between -24dBm and -8dBm. If the Rx optical power is abnormal, do as
follows:
 If the fiber connector is dirty, clean it with non-woven lens tissue dampened
with a small amount of dedicated detergent , and then reinsert the fiber into the
PON port again.
 If the fiber connector is not smooth, replace it with a good fiber jumper.
 If the bend radius of the fiber is too small, increase the bend radius properly.
 If there are too many optical splitter cascades, reduce the number of cascades.
 Check whether the interface card is present and whether it has abnormal alarms.
If the PON interface card is faulty, replace it.

21
REG Indicator of ONU Being Abnormal
Fault Symptom
 The REG indicator LED on the ONU blinks or goes out.

Fault analysis
If the REG indicator on the ONU blinks or goes out, registration of the ONU with the
OLT has failed. Possible causes are as follows:
 The fiber at the uplink PON port of the ONU is loose or broken.
 The optical power at the PON port of the ONU is abnormal.
 The OLT device at the central office end is faulty; for example, the PON interface
card is faulty.

Fault analysis
 Check the connection of the optical fibers.
If the fiber jumper is incorrectly connected, remove it and reinsert it correctly;
If the fiber is broken, replace it with a good fiber jumper.
 Check the fiber jumper connector.

22
REG Indicator of ONU Being Abnormal
Fault analysis
 Measure the received optical power of the ONU. The normal range of the Rx
optical power of the ONU is between -24dBm and -8dBm.
 If the optical power is too high, add an optical attenuator for recovery;
 If the optical power is too low, resume the optical power.
 Check whether the interface card is present and whether it has abnormal alarms.
If the PON interface card is faulty, replace it.
 Check whether the ONU can be normally authorized. If no, check whether the
current ONU authentication mode is correct, and check whether the MAC address
and the SN logical number of the ONU are in the authentication white list.
If the ONU authentication mode configuration is incorrect, re-configure the
authentication mode according to the planning data.
If the MAC address or the SN logical number of the ONU is not in the
authentication white list, add it to the white list and deliver the configuration
data to the AN5116-06B.
23
ONU Network Management Connection Failure

Fault Symptom
 The ONU status indicator on the UNM2000 is grey (AN5116-06B runs normally).

Fault analysis
Below are the possible causes for the ONU’s failure in connection with the network
management system:
 Fiber at the PON port or at the ONU side is loose or broken;
 The optical power at the PON port is abnormal;
 The ONU equipment is faulty.

Fault analysis
 If the fiber at the PON interface or at the ONU side is loose, broken or the optical
power is abnormal, refer to LOS Indicator of ONU Illuminated for
Troubleshooting.
 Contact FiberHome if the ONU is faulty.

24
Network Interface Indicator Extinguished

Fault Symptom
 The Ethernet interface connection indicator LED of the AN5116-06B is off.

Fault analysis
 The network cable connection is incorrect;
 The AN5116-06B has a fault in hardware.

Fault analysis
 Check peripheral equipment of the AN5116-06B, and notify related maintenance
personnel for troubleshooting if it has failed.
 Check the network cable connection, remove and reinsert the cable again when
necessary.
 Examine the network cable with a network cable tester. Replace the network cable
when it has a fault.
 Contact FiberHome if the above steps do not work.
25
Equipment Management IP Address Ping Timeout

Fault Symptom
 A Ping of the core switch card via the UNM2000 fails to respond and times out.

Fault analysis
 A fault in the peripheral router or switch;
 A fault in physical connection;
 An error in the management VLAN and IP configuration for the AN5116-06B;
 An error in IP address configuration of the UNM2000 computer.

Fault analysis
 Check whether the peripheral router or switch has failed. Notify related
maintenance personnel for troubleshooting if a failure has occurred;
 Check the physical link between the UNM2000 computer and the AN5116-06B
section by section.
 Check whether the management VLAN configuration for the AN5116-06B is correct.

26
Equipment Management IP Address Ping Timeout

Fault analysis
 Perform the fault analysis and troubleshooting according to the port mode of the
management VLAN.
 If the port of the management VLAN is in the tagged mode, check the IP
address configuration of the network management system computer and
correct the IP address if it is incorrect.
 If the port of the management VLAN is in the untagged mode, follow the steps
below.
• Check whether the switch is connected to the correct uplink interface and
whether the switch VLAN is configured correctly.
• Check whether the IP address configuration of the network management
system computer is correct; if not, modify it.
 Contact FiberHome if the above steps do not work.

27
Abnormal Link between Equipment and Switch

Fault Symptom
 The link between a GE optical interface of the AN5116-06B uplink card and the
previous switch is abnormal.

Fault analysis
 Fault in optical fiber connection;
 An error in the interface mode configuration;
 Unmatched optical module types.

Fault analysis
 Check whether the optical fiber connection between the GE optical interface of the
uplink card and the previous switch is normal.
 If the fiber jumper is incorrectly connected, remove it and reinsert it correctly;
 If the fiber is broken, replace it with a good fiber jumper.
 Check the configuration of the uplink port properties. Whether the configuration of
parameters for the uplink port such as port enable / disable, port auto negotiation
and port working mode is identical with that for the switch connected to it.
28
Abnormal Link between Equipment and Switch

Fault analysis
 Checking the status of the uplink port : show port <19/20:1-6 >/all.

 Check whether the type of the optical module at the uplink port of the AN5116-06B
is identical with that at the switch port. If not identical, replace the optical module
concerned and make them identical.
 Contact FiberHome if the above steps do not work.

29
Contents

1 Common Methods for Fault Analysis

2 Troubleshooting Common System Faults

3 Troubleshooting Data Service Faults

4 Troubleshooting Voice Service Faults

5 Troubleshooting IPTV Service Faults

30
Troubleshooting Flow
Check the status of
peripheral equipment
Check the status of
peripheral equipment
Check ONU status

Check OLT uplink

Check the network cable
connection from ONU to
PC network card
Check ONU
registration status
Check the communication
between GPON interface
Check internal card and PC
communication status of
Data
GPON system Check VLAN ID of
Data service service
interruption interruption uplink card
of all Check the service of an
subscribers data of BRAS individual Check the service
subscriber data of BRAS

31
Troubleshooting Data Service Interruption of All Users
1. Checking the Status of Peripheral Equipment
Main peripheral equipment of data service is shown as follows:
 Ethernet switches; Routers; BRAS equipment.
2. Checking OLT Uplink
 Check whether the uplink card port properties configuration is identical with
that of the connected switch. Check the port type, the port enabled / disabled
status, port auto-negotiation status, port rate and port work mode etc.
 Click the HU1A card on the Object Tree pane object and select Card Service
Config → Common Cofig → Uplink Port Properties in the shortcut menu.

32
Troubleshooting Data Service Interruption of All Users

3. Checking the Registration Status of the ONU

 Right click the object in the Object Tree and choose Open NE Manager. Then
click the ONU List in the tool bar. If the REG indicator in the legend is solid
green, it indicates a successful registration. If the REG indicator is grey, it
indicates a failed registration.

33
Troubleshooting Data Service Interruption of All Users

4. Checking Internal Communication Status of the GPON System

The method for checking the internal communication status of the GPON system
is shown below:
Select one cable interface from the uplink card of the AN5116-06B; use a
network cable to connect one test laptop or PC.
Add one service VLAN in the service VLAN configuration screen in the
untagged mode; the VLAN ID should be same as that of the ONU.
Select one remote side ONU and connect to one test laptop or PC using a
network cable.
Set the local computer and the remote computer on one network segment for
mutual PING test.
 If they can ping each other, Ethernet communication is normal in the GPON
system. Then go to check the BRAS equipment.
 If not, contact FiberHome for troubleshooting.

34
Troubleshooting Data Service Interruption of All Users

5. Confirming the Status of the BRAS Service Data

Use a test laptop connected to the uplink interface for PPPoE connection
test.
 If a prompt of 678 error appears, the uplink must be faulty. Maintenance
personnel for the upper BRAS equipment should be notified for inspection
to confirm whether the service data is normal or not.
If it connects successfully, it indicates that the faulty of peripheral
equipment is excluded. Notify FiberHome for troubleshooting.

35
Troubleshooting Data Service Interruption of One User

1. Checking the Status of Peripheral Equipment

Main peripheral equipment of data service is shown as follows:
 Ethernet switches; Routers; BRAS equipment.
2. Checking ONU Status
 Query the ONU’s authorized status. If the ONU is not authorized, authorize it.
 Query the ONU’s registered status. If the ONU registering is not successful,
the cause is usually a fiber connection problem. Check whether the ONU’s Rx
optical power is within the normal range and whether the fiber is in good
connection.
 Choose the ONU Authentication button and click ONU Whitelist at the bottom
of the window.

36
Troubleshooting Data Service Interruption of One User

3. Checking the Connection between the ONU and the PC

Check whether the ONU port can normally learn the MAC address of user’s PC or not. If
the ONU cannot learn the MAC address of the user’s PC, it may be caused by a
connection fault between the user’s PC and the ONU. Correct the connection fault
between the PC and the ONU.
 Click ONU List, and right click ONU, choose Service Configure and select MAC-
Learning table in ONU to check the connection between ONU and PC .

37
Troubleshooting Data Service Interruption of One User

4.Checking the Communication between the GPON Interface Card and the PC
 Right-click the HSWA card, choose Card Service Configure, select OLT MAC
address Table in the new window.

38
Troubleshooting Data Service Interruption of One User

5. Checking the VLAN ID in the Uplink Card

 Right-click the HSWA card, choose Card Service Configure, and select OLT MAC
address table
 In the OLT MAC address list, if the uplink card slot has no corresponding user’s
service VLAN ID, it indicates that the upstream equipment has not configured this
VLAN ID, so you have to contact related maintenance personnel for resolution.

6. Confirming the Status of the BRAS Service Data

39
Contents

1 Common Methods for Fault Analysis

2 Troubleshooting Common System Faults

3 Troubleshooting Data Service Faults

4 Troubleshooting Voice Service Faults

5 Troubleshooting IPTV Service Faults

40
.

Network Topology of VOIP service

 In the voice service application network, the AN5116-06B is connected with the
ONUs through a splitter. The ONUs provides an RJ-11 port for the telephone
connection. The ONU compresses and encodes the voice signal to implement
analog to digital conversion, and then transfers the voice data to the IP network
through OLT in the form of IP data package. The call control for voice services is
finished by the softswitch equipment
41
Troubleshooting Flow
Check the status of
peripheral equipment

Check connection of
Check the status of
the user’s cable
peripheral equipment

Check status ONU

Check OLT uplink

Check related
configuration of voice
Check NGN uplink
service
interface configuration
Confirm the status of
service data of
VOIP service interruption of softswitch platform
all subscribers
VOIP service interruption of
an individual subscriber

42
Troubleshooting VOIP Service Interruption of All Users
1. Checking the Status of Peripheral Equipment
 When all users’ voice service is interrupted, question maintenance personnel of
peripheral equipment to initially determine whether the fault is caused by the peripheral
equipment.
Main peripheral equipment of data service is shown as follows: Ethernet switches;
Routers; BRAS equipment.
2. Checking OLT Uplink
The OLT voice uplink bears all ONU voice media flows and signal flows under the OLT.
The status of the OLT uplink should be checked after troubleshooting peripheral
equipment.
 Click the HU1A card and select Common Config → Uplink Port Properties.

43
Troubleshooting VOIP Service Interruption of All Users

3. Checking the Local End Service VLAN Data

 Check the local end service VLAN data configuration, check that configuration
of parameters starting VLAN ID / VLAN ID end, TAG / UNTAG, Interface NO.
and configuration is identical with the planned data.
 Right-click the HSWA card, Service Configure VLAN Service Local
End Service VLAN.

44
Troubleshooting VOIP Service Interruption of All Users

4. Checking Configuration of NGN Uplink Interface

 An MGC IP address configuration error will cause communication failure
between the equipment and the MGC. To test the link status of the equipment
and MGC, maintenance personnel can connect a PC through the uplink
interface, and then PING the MGC IP address from the PC to check the
connectivity of the equipment and the MGC.
For some softswitch platforms, if the heartbeat is not activated for a long time,
the ONU will lose communication with the softswitch platform, so that the voice
service is interrupted.

45
Troubleshooting VOIP Service Interruption of One User

1. Checking the Status of Peripheral Equipment

Main peripheral equipment of data service is shown as follows: Ethernet
switches; Routers; BRAS equipment.

2. Checking the Connection of Subscriber Lines

Check whether the subscriber line is electrically short-circuited or open at the
ONU side, and whether the wiring scheme is correct.

3. Checking the ONU Status

Check the registration and authorization of the ONU.

4. Checking Related Configuration of Voice Service

For voice service fault of an individual user, check related data configuration
of voice service after troubleshooting the subscriber line and the ONU.

46
Troubleshooting VOIP Service Interruption of One User

Main Parameters
and Influences

47
.

Troubleshooting VOIP Service Interruption of One User

 Right-click the HSWA card select Card Service Config → NGN Uplink → NGN
Configuration from the shortcut menu. Then click the NGN Configuration tab.

48
.

Troubleshooting VOIP Service Interruption of One User

5.Confirming Service Data of the SoftSwitch Platform

Ask the maintenance personnel of the core network to determine
whether the data configuration of softswitch platform equipment is
correct. Number analysis error on the MGC and abnormal user’s data on
HSS/SDC will influence individual user’s service.

 If the upstream softswitch platform has failed, notify the maintenance

personnel for troubleshooting;

 If the upstream softswitch platform has not failed, notify FiberHome for
troubleshooting.

49
Contents

1 Common Methods for Fault Analysis

2 Troubleshooting Common System Faults

3 Troubleshooting Data Service Faults

4 Troubleshooting Voice Service Faults

5 Troubleshooting IPTV Service Faults

50
.

Network Topology of Multicast Service

51
Troubleshooting Flow
Check STB status

Check VLAN
configuration

Check multicast proxy

IP configuration

Check multicast template

and port configuration

Check bandwidth
configuration

Check bandwidth
configuration
52
Multicast Troubleshooting
1.Checking the STB Status
Check the user’s STB and localize the fault by substituting a known good
STB. If the STB status is abnormal, repair or replace the STB.
2. Checking the VLAN Configuration
Check whether the configuration of user’s service VLAN ID and multicast
VLAN ID are identical with the planned data. The multicast VLAN ID should
be within the service VLAN ID scope.

53
Multicast Troubleshooting
3. Checking the Configuration of Multicast Proxy IP.
When the core switch card works under proxy mode, check the proxy IP
address of the core switch card. The multicast proxy IP address and the IP
address of the upstream equipment should be on the same network segment.
 Right-click the HSWA card and select Card Service Configure →
Multicast Service → Multicast IP → IGMP Proxy IP from the shortcut
menu to access the IGMP Proxy IP window.

54
Multicast Troubleshooting
4. Checking the Multicast Template and Port Configuration

55
Multicast Troubleshooting
5. Checking the Bandwidth Configuration
Check the uplink interface and ONU port bandwidth configurations. These must
be greater than the program bandwidth.
 Right-click the HSWA [9] card and select Config → IGMP Config → IGMP
Cascade Ports from the shortcut menu. Then click the Max. Uplink IGMP
Bandwidth tab.

56
Multicast Troubleshooting
6. Checking the ONU Service Configuration

Check the VLAN mode, VLAN ID and VLAN configuration on the ONU.
Treatment of the system to VLAN tags is shown below:
 For FTTB Type ONU, the VLAN mode should be transparent, and a VLAN ID
of HG is translated into a multicast VLAN ID;
 For FTTH Type ONU, the VLAN mode is TAG; the ONU adds a multicast
VLAN ID.

57
Thank you!