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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
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).
ARP Troubleshooting

ARP Troubleshooting

This chapter describes common causes of ARP faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

The ARP Entries on the Local Device Cannot Be Learned By the Peer

This chapter describes common causes of the fault that the ARP entries on the local device cannot be learned by the peer, and provides the corresponding troubleshooting flowcharts and examples.

Common Causes

This fault is commonly caused by one of the following:

  • The interface connecting the local device to the peer exist is not physically Up.
  • The IP addresses of the interfaces connecting the local device and peer are on different network segments.
  • The local device is under the ARP attacks.
  • The link transmission is unstable or the optical power is insufficient.
  • The device software is faulty.
Troubleshooting Flowchart

The HUAWEI ME60 is connected to a peer device but cannot learn the ARP entries on the peer device.

Figure 4-32 shows the detailed troubleshooting procedure for the fault that the ARP entries on the peer device cannot be learned.

Figure 4-32 Troubleshooting flowchart for the fault that the ARP entries on the peer device cannot be learned

Troubleshooting Procedure

Context

NOTE:
Save the results of each troubleshooting step so if your troubleshooting fails to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Run the display interface interface-type interface-number command in the user view to check the physical status of the interface connecting the local device to the peer exist.

    NOTE:

    You can run the display interface interface-type interface-number command to view information about the interface connecting the local device to the peer exist.

    • If the interface is Down, refer to relevant troubleshooting cases for help on changing the interface to Up.
    • If the interface is Up, go to Step 2.

  2. View the Internet Address field. Check whether the IP addresses of the interfaces connecting the two devices are on the same network segment.

    • If the two IP addresses are on different network segments, re-re-configure one of the IP addresses so the two IP addresses are on the same network segment.
    • If the two IP addresses are on the same network segment, go to Step 3.

  3. Run the display arp statistics slot slot-id command in the user view to check whether the number of the ARP entries on the specified interface board of the local device exceeds the upper limit. If the upper limit is reached, refer to the chapter "Configuring the ARP Security" in the ME60 Configuration Guide for help on solving the problem.

    If the number of the ARP entries does not exceed the upper limit but the fault persists, go to Step 4.

  4. View the status information of the interface connecting the local device to the peer exist. Check whether the count displayed in the CRC field increases. If so, a large number of error packets on the interface connecting the local device to the peer exist. In this case, check the link quality to verify if the link transmission is unstable or the optical power is insufficient.

    If the count displayed in the CRC field does not increase but the fault persists, go to Step 5.

  5. View the status information of the interface connecting the local device to the peer exist. Check whether the count in the Broadcast sub-field of the output field increases.

    Before viewing the following information, ping the IP address of the peer device from the local device to trigger the local device to send the ARP request packets.

    • If the number of broadcast packets remains unchanged, no the ARP request packet has been sent. This indicates that the local device is faulty. In this case, go to Step 7.
    • If the number of broadcast packets increases, check whether the peer device or the link is functioning properly.
      • If the peer device or the link is not functioning properly, locate the fault and rectify it.
      • If the peer device and the link function are functioning properly, go to Step 6.

  6. View the status information of the interface connecting the local device to the peer exist. Check whether the count in the Unicast sub-field of the input field increases.

    • If the number of unicast packets remains unchanged, the device has not received any the ARP response packets. The broadcast ARP request packets sent by the local device may have been discarded on the peer device because their format is not standard protocol-compliant.
    • If the number of unicast packets increases, the local device has received the ARP response packets. This indicates that some software modules on the local device are not functioning properly. In this case, go to Step 7.

  7. Collect the following information and contact Huawei.

    • Results of this operation procedure
    • Configuration files, log files, and alarm files of the devices

Relevant Alarm and Log Messages

Alarm Messages

None.

Log Messages

None.

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13856

Downloads: 257

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