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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Troubleshooting Procedure

Troubleshooting Procedure

During troubleshooting, pay attention whether the commands you use will take effect in immediate or two-phase mode. Unless otherwise specified, commands mentioned in this manual take effect immediately.
  • In immediate mode, configuration takes effect after you enter a command and press Enter.
  • In two-phase mode, configuration takes effect after you run the commit command to commit the configurations.

Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide technical support personnel.

Procedure

  1. Check whether PIM is enabled on the interface that needs to forward multicast data packets.

    Run the display this command on the interface that needs to forward multicast data packets. Check whether pim sm or pim dm is displayed in the command output.

    • If neither pim sm nor pim dm is displayed in the command output, run the pim sm or pim dm command on the interface. For a Bidir-PIM network, run the bidir-pim command in the PIM view, and then run the pim sm command on the interface.

    • If pim sm or pim dm is displayed, go to step2.

  2. Check whether the PIM status on the interface is Up.

    Run the display pim interface interface-type interface-number command to check whether the PIM status on the interface is Up.

    • If the PIM status is Down, run the display interface interface-type interface-number command to check the physical status and protocol status of the interface.
      • If the physical status (current state) is Down, refer to An Interface Does Not Go Up to rectify the fault.
      • If the protocol status (Line protocol current state) is Down, locate and rectify this fault to make the protocol status Up. For example, the protocol status cannot go Up if the interface has no IP address configured.
    • If the PIM status on the interface is Up, go to step 3.

  3. Check whether the PIM neighbor relationship has been set up.

    Run the display pim neighbor command to check whether the interface has a PIM neighbor.

    • If not, check whether any of the following situations occurs and take measures accordingly:
      • There are no reachable routes between the Layer 3 interfaces of the neighboring PIM routers. In this case, rectify the fault of unicast routing.
      • A PIM neighbor filtering policy is configured on the interface and the address of the PIM neighbor is filtered out by the policy. In this case, delete or modify the policy.
      • The interface is configured to reject Hello packets without a Generation ID, whereas the PIM neighbor sends Hello packets without a Generation ID. This situation usually happens when a Huawei switch connects to a non-Huawei device. In this case, configure the interface to accept such Hello packets.
    • If the interface has a PIM neighbor, go to step 4.

  4. Check whether IGMP is enabled on the interface connected to the user network segment.

    Run the display this command on the interface connected to the user network segment. Check whether igmp enable is displayed in the command output.

    • If igmp enable is not displayed, run the igmp enable command on the interface. To enable an interface to forward multicast data packets, you must enable PIM and IGMP on the interface. It is recommended that you enable PIM before IGMP on an interface.

    • The igmp enable is displayed:

      • For a PIM-SM or Bidir-PIM network, go to step 5.
      • For a PIM-DM network, go to step 6.

  5. If the multicast network is running PIM-SM or Bidir-PIM, check whether the RP information is correct.

    Run the display pim rp-info command to check whether the switch has learned information about the RP serving the corresponding multicast group and whether the learned RP information is the same as information about the RP serving the same multicast group on other devices.

    • If no RP information is available on the switch, set RP information. To use a static RP, run the static-rp command to specify the same RP address for the multicast group on all the devices on the entire network.

    • If the RP is configured on the local switch but the RP information is different from that on other devices, the static RP address may be configured incorrectly. Ensure that the static RP address on the local switch is the same as that on other devices.

    • If the correct RP information has been configured on all the devices, go to step 6.

  6. Check whether there is a reachable RPF route to the RP or multicast source.

    If multicast traffic is forwarded along a rendezvous point tree (RPT), run the display multicast rpf-info source-address command to check whether there is an RPF route to the RP. If multicast traffic is forwarded along a shortest path tree (SPT), run the display multicast rpf-info source-address command to check whether there is an RPF route to the multicast source.

    • If there is no RPF route to the RP or multicast source, rectify the unicast routing fault. Run the ping command on the local switch and the RP or multicast source to check connectivity between them. If the ping test fails, refer to A Ping Failure Occurs to rectify the fault.

    • If an RPF route to the RP or multicast source is available and the Referenced route type field of this RPF route displays mstatic (indicating a static multicast route), run the display current-configuration command to check whether the static multicast route is configured correctly. If so, go to step 7. If not, modify the routing configuration.

    • If an RPF route to the RP or multicast source is available and the Referenced route type field of this RPF route displays unicast (indicating a unicast route), run the display ip routing-table command to check whether the unicast route is the same as the RPF route. If so, go to step 7. If not, modify the routing configuration.

  7. Check whether multicast boundary is configured on the interface that needs to forward multicast data packets.

    Run the display this command on the interface, and check whether multicast boundary is displayed in the command output.

    • If multicast boundary is displayed, run the undo multicast boundary { group-address { mask | mask-length } | all } command to delete the configuration or modify the network plan to ensure that no multicast boundary is configured on the RPF interface or the RPF neighbor interface.

    • The multicast boundary is not displayed:
      • For a PIM-SM or Bidir-PIM network, go to step 8.
      • For a PIM-DM network, go to step 9.

  8. If the multicast network is running PIM-SM or Bidir-PIM, check whether a multicast source filtering policy is configured.

    Run the display this command in the PIM view, and check whether source-policy is displayed in the command output.

    • If source-policy is displayed, a multicast source filter policy is configured. In this case, the switch drops the received multicast data packets that are not allowed by the ACL referenced in the policy. Run the undo source-policy command to delete the multicast source filtering policy or configure new ACL rules to permit the multicast data requested by the user hosts.

    • If source-policy is not displayed, go to step 9.

  9. Check whether multicast entries have been generated.

    1. Run the display pim routing-table command to check whether PIM routing entries have been created.

      A PIM routing entry is similar to a routing entry of a unicast routing protocol. For multicast group G, corresponding (*, G) and (S, G) entries must exist on the switch to ensure that requested data can be forwarded to receivers. When the switch receives a Report message from a user, it creates the (*, G) entry for group G. When data packets of multicast group G reach the switch, the switch creates the matching (S, G) entry.

    2. Run the display multicast routing-table command to check multicast routing entries and the display multicast ip fib command to check the multicast forwarding entries.

      Multicast routing and forwarding entries are similar to unicast routing and FIB entries. If the multicast routing and forwarding entries are not generated for a group, multicast traffic cannot be forwarded to receivers.

    • If the matching multicast entries have been created, collect the entries and go to step 10.

    • If the matching multicast entries have not been created, go to step 10.

  10. Collect the following information and contact technical support personnel:
    • Results of the preceding troubleshooting procedure

    • Configuration file, logs, and alarms of the switch

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 617114

Downloads: 2967

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next