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).
DHCP & Ping Emulation

DHCP & Ping Emulation

In a DHCP emulation test, an access node simulates the DHCP client to implement remote acceptance for services that obtain IP addresses in DHCP mode (such as IPTV, IPoE, and VoIP services) and locate faults, which reduces the O&M costs.

Prerequisites

A DHCP emulation test locates the network segment where a fault has occurred, but cannot identify the cause of the fault. To identify the cause of a fault, the maintenance personnel need to take other fault locating measures.

Restrictions on Setting DHCP emulation Parameters

  • The MAC address used for DHCP emulation must be unique in the service VLAN to prevent emulation instances from being affected by each other and prevent user services from being affected.
  • To truly simulate the packets sent by the actual DHCP client, use the actual MAC address of the DHCP client to set DHCP emulation parameters.
  • The configured DHCP emulation parameters must conform to the carrier's network plan. If parameters do not conform to the network plan, DHCP simulation may fail and the simulation result will not reflect the actual link condition. For example, if the DHCP server is configured with MAC address or DHCP option 61 verification, the MAC address and DHCP option 61 must be correctly specified during the DHCP simulation test.

Restrictions on the DHCP emulation Process

  • Services of the simulated user may be affected during DHCP simulation because DHCP emulation occupies the system resources.
  • During DHCP emulation, users cannot create, delete, or modify a WAN port on an ONT.
  • DHCP emulation and PPPoE emulation cannot be concurrently performed on an ONT.

Context

In a DHCP simulation test, an access node simulates a DHCP client to apply for an IP address from a DHCP server. By doing so, the access node can test the connectivity between the access node and DHCP server and therefore the validity of DHCP configurations on the DHCP relay agent, DHCP agent, and DHCP server. In addition, the access node can ping a remote server to test the connectivity between them.

Procedure

  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 GPON ONUs.
  4. Right-click an online ONT and choose Test > DHCP & Ping Emulation from the shortcut menu.
  5. In the dialog box that is displayed, set the parameters. And then click Start.

    Figure 1-14 DHCP & Ping Emulation

Follow-up Procedure

Locate the fault based on the obtained DHCP simulation result.

Table 1-5 Mapping between the simulation result and fault range

Simulation Result

Description

Fault Scope

send packet fail

The access node failed to send packets to the DHCP server.

The access node is faulty.

DHCP server not found

After sending DHCP Discover packets, the access node did not receive response packets from the DHCP server.

The network segment between the access node and DHCP server is faulty.

DHCP server refuse request

The DHCP server rejected the DHCP request from the access node.

The DHCP server is faulty.

get IP overtime

After sending a DHCP request, the access node did not receive confirmation packets from the DHCP server.

The network segment between the access node and DHCP server is faulty.

get IP successful

The access node obtained an IP address from the DHCP server, indicating that the DHCP interaction was successful.

The possible fault scopes are as follows:

  • The network segment between the user terminal and access node is faulty.
  • The network segment between the BRAS and remote server is faulty.

all ping succeed

The access node succeeded in pinging all the specified remote servers.

The network segment between the user terminal and access node is faulty.

partial ping succeed

The access node succeeded in pinging some of the specified remote servers.

The network segment between the BRAS and remote server that failed to be pinged is faulty.

all ping fail

The access node failed to ping all the specified remote servers.

Network segments between the BRAS and all remote servers are faulty.

system resource not enough

On the access node, resources for DHCP simulation are insufficient.

On the access node, resources for DHCP simulation are insufficient.

Translation
Download
Updated: 2019-07-10

Document ID: EDOC1100009118

Views: 29783

Downloads: 5449

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