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 the status of the MSDP peers is Up.

    Run the display msdp brief command on the devices setting up an MSDP peer relationship to check whether the status of the MSDP peers is Up.

    • If the command output shows that the status of MSDP peers is Down, check whether the MSDP peer interfaces are correctly configured and the MSDP peers can ping each other.

    • If the MSDP peers are both in the Up state, go to Step 2.

  2. Check whether SA cache is enabled.

    Run the display this command on the MSDP peers to view their current configurations in the MSDP view.

    • If the command output contains cache-sa-disable, SA cache is disabled in the MSDP view. In this case, run the undo cache-sa-disable command in the MSDP view to enable SA cache.

    • If SA cache is enabled, go to Step 3.

  3. Check whether any SA messages have reached the MSDP peers.

    Run the display msdp sa-count command on the MSDP peers to check the contents of the SA cache.

    • If no information is displayed, run the display msdp peer-status command to check whether the Count of RPF check failure field value is 0.
      • If the field value is not 0, check whether the RPF routes are configured correctly.

      • If the field value is 0, check the Incoming/outgoing SA messages field value to see whether any received SA messages exist.

        • If no SA message is received, check whether the mesh group is configured correctly.

        • If received SA messages exist, go to Step 5.

    • If the value of the Number of source or Number of group field in the command output is non-zero, the SA messages have reached the peers. Go to Step 4.

  4. Check whether any export policies are configured on the MSDP peers.

    Run the display this command on the MSDP peers to view their current configurations in the MSDP view.

    • If export policies are configured on the MSDP peers, perform the following:
      • If the command output contains the configurations of the peer peer-address sa-policy export without any parameters, the MSDP peers are prevented from forwarding the messages received from the multicast source. In this case, run the undo peer peer-address sa-policy export command to delete the configurations of the export policies.

      • If the command output contains the configurations of the peer peer-address sa-policy export advanced-acl-number or the peer peer-address sa-policy export acl-name with an ACL specified, the MSDP peers can forward only the (S, G) entries permitted by the ACL. Check whether the ACL-related commands are running on the MSDP peers and the (S, G) entries are permitted by the ACL. You can run the undo peer peer-address sa-policy export command to delete the ACL configurations or change the ACL rule configurations.

    • If no export policies are configured on the MSDP peers, go to Step 5.

  5. Check whether any import policies are configured on the MSDP peers.

    Run the display this command on the MSDP peers to view their current configurations in the MSDP view.

    • If import policies are configured on the MSDP peers, perform the following:
      • If the command output contains the configurations of the peer peer-address sa-policy import without any parameters, the MSDP peers are prevented from receiving messages from the multicast source. In this case, run the undo peer peer-address sa-policy import command to delete the configurations of the export policies.

      • If the command output contains the configurations of the peer peer-address sa-policy import advanced-acl-number with an ACL specified, the MSDP peers can receive only the (S, G) entries permitted by the ACL. Check whether the ACL-related commands are running on the MSDP peers and the (S, G) entries are permitted by the ACL. You can run the undo peer peer-address sa-policy import command to delete the ACL configurations or change the ACL rule configurations.

    • If no import policies are configured on the MSDP peers, go to Step 6.

  6. Check whether the current MSDP peer receives multicast data from the multicast source.
    • If the current MSDP peer does not receive multicast data from the multicast source, troubleshoot the upstream device following the preceding steps.

    • If the current MSDP peer receives multicast data from the multicast source, go to Step 7.

  7. Check whether the current MSDP peer is an RP.

    Run the display pim routing-table command on the MSDP peer closest to the multicast source to view the routing table.

    • If the (S, G) entry is without a 2MSDP flag, the MSDP peer is not an RP. Change the configurations of the RP or MSDP peer on the PIM-SM network to ensure that the MSDP peer is an RP.

    • If the MSDP peer is an RP, go to Step 8.

  8. Check whether any import-source policies are configured on the current MSDP peer.

    The import-source [ acl acl-number ] command is used to enable an MSDP peer to filter the (S, G) entries to be advertised based on source addresses when creating SA messages. The MSDP peer can control the transmission of information about multicast sources. By default, SA messages can be used to advertise information about all known multicast sources.

    Run the display this command on the MSDP peer closest to the multicast source to view the current configurations in the MSDP view.

    • If import-source policies are configured on the MSDP peer, do as follows:
      • If the command output contains the configurations of the import-source without any parameters, the MSDP peer is prevented from advertising multicast source information. Run the undo import-source command to delete the configurations of these import-source policies.

      • If the command output contains the import-source acl acl-number with an ACL specified, the MSDP peer advertises only (S, G) information that matches the ACL. Check whether any ACL-related commands are running on the MSDP peer and the (S, G) entries are permitted by the ACL. Run the undo import-source command to delete the ACL configurations or change the ACL rule configurations.

    • If no import-source policies are configured on the MSDP peer, go to Step 9.

  9. If the fault persists after this troubleshooting procedure, contact technical support personnel.
Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 607139

Downloads: 2948

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next