No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

EchoLife ONT Maintenance and Troubleshooting Guide

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Multicast Emulation

Multicast Emulation

After multicast services encounter faults, onsite troubleshooting is costly. After sites are deployed, onsite acceptance testing is also costly. To resolve this issue, the multicast emulation function is provided, which is capable of remote troubleshooting and acceptance testing.

Prerequisites

Multicast emulation is not supported on a user port if:

  • The GPON board where the user port resides cannot be detected by the system.
  • The user port is a cascade port.
  • The multicast program is generated in dynamic mode.
  • The group filtering mode is SSM ONLY.
  • The OAM multicast is enabled.
  • The IGMP version is IGMPv2.
  • The IP version is IPv6.
  • The multicast forwarding mode is multicast VLAN+SIP+GIP.

After a multicast emulation task is complete, the task must be manually stopped to release resources. Otherwise, a subsequent multicast emulation task cannot be started. In type B mode, emulation can be performed only on active ports and a type B switchover performed during the emulation may be incorrect. If a type B switchover is performed during emulation, the device must recalculate emulation parameter settings.

Context

A multicast emulation test remotely emulates an end user going online, and engineers query the real-time traffic of the multicast program to determine whether the multicast function is running properly.

Procedure

  • Perform multicast emulation on an ONT. (For IGMP user)
    1. In the Main Topology, double-click the required OLT in the Physical Root navigation tree; or right-click the required OLT and choose NE Explorer from the shortcut menu.
    2. Choose GPON > GPON Management from the navigation tree.
    3. On the GPON ONU tab page, set the filter criteria or click to display the ONUs.
    4. Select an ONU, and click the IGMP User tab in the lower pane.
    5. On the IGMP User tab, right-click a record and choose Multicast Emulation from the shortcut menu.
    6. In the dialog box that is displayed, set the parameters. And then click Start.

Follow-up Procedure

After the multicast emulation, you can query the user status and multicast program's real-time traffic. The following table lists troubleshooting suggestions based on the query results.

NOTE:

Data configurations are seldom changed in daily operation and maintenance. Therefore, multicast faults are usually caused by hardware problems. Hardware must be checked prior to data configuration during fault location.

Table 1-8 Multicast emulation results and troubleshooting suggestions

Results

Description

Troubleshooting Suggestions

The user status parameter State is online.

The multicast user can go online successfully.

  • If the user can go online and the access device can communicate with the multicast source, the fault may be caused by a communication failure between the access device and the set-top box (STB). The reasons are as follows:
    • The hardware of the port on the access device is faulty.
    • The physical line between the access device and the modem is faulty.
    • The modem is faulty.
    • The STB is faulty.
  • If the user can go online but the traffic on the access device's uplink port is abnormal, the fault may be that the hardware connection between the access device and the upper-layer device (multicast router or multicast server) is incorrect, or the software configuration is incorrect. The common software configuration faults are as follows:
    • 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.
  • Common software configuration issues on upper-layer devices:
    • The program is not configured on the multicast server.
    • Time To Live (TTL) of the multicast stream takes a small value on the multicast server.

The user status parameter State is offline.

The multicast user fails to go online and therefore fails to order a program in the emulation.

The case is more complicated than the scenario in which the user is online. Handling suggestions are as follows: Enable the multicast debugging function and start the multicast emulation again to check whether the access device receives the report packet from the user for ordering a program.

  • If the access device receives the report packet, the multicast link is normal but the access device fails to create a corresponding multicast entry. This is generally caused by incorrect multicast configurations on the access device.
  • If the access device does not receive the report packet, the multicast link fails. This is mainly caused by incorrect access device data configurations, faulty physical link between the access device and the modem, or hardware faults of terminals.

The user status parameter State is block.

The multicast user is locked and therefore fails to order a program.

Right-click the multicast user and choose Unblock from the shortcut menu.

The multicast program's real-time traffic parameter Multicast flow statistic result is a small value or zero.

The program's traffic on the uplink port is small or zero.

The hardware connection between the access device and the upper-layer device (multicast router or multicast server) is incorrect, or the software configuration is incorrect. Troubleshoot the fault based on the suggestions providedwhen the user can go online but the traffic on the access device's uplink port is abnormal.

The multicast program's real-time traffic parameter Multicast flow statistic result is close to the program's bandwidth.

The device uplink port can communicate with the multicast source.

  • If the user can go online and the access device can communicate with the multicast source, the fault may be caused by a communication failure between the access device and the STB. The reasons are as follows:
    • The hardware of the port on the access device is faulty.
    • The physical line between the access device and the modem is faulty.
    • The modem is faulty.
    • The STB is faulty.
  • If the access device can communicate with the multicast source but the user cannot go online, troubleshoot the fault based on the suggestions provided when the user status parameter State is offline.
Translation
Download
Updated: 2019-07-10

Document ID: EDOC1100009118

Views: 32161

Downloads: 5577

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next