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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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).
PIM/4/CRT_L3ENTRY_FAIL

PIM/4/CRT_L3ENTRY_FAIL

Message

PIM/4/CRT_L3ENTRY_FAIL:In the VPN instance, PIM failed to create entry in the multicast routing table. (VPNName=[VPNName], GrpAddr=[GrpAddr], SrcAddr=[SrcAddr], Reason=[Reason])

Description

In the VPN instance, PIM failed to create a multicast entry.

Parameters

Parameter Name Parameter Meaning

VPNName

VPN instance name

GrpAddr

Group address
  • IPv4 multicast group address
  • IPv6 multicast group address

SrcAddr

Source address
  • IPv4 address
  • IPv6 address

Reason

Reason of PIM entry creating failure

Possible Causes

Cause 1: The multicast source was filtered out.

Cause 2: A multicast forwarding boundary was set.

Cause 3: The RP address was wrong.

Cause 4: The upstream interface could not be found.

Cause 5: The multicast group was in the range of SSM group addresses.

Cause 6: The memory was not enough.

Procedure

  1. Cause 1: The multicast source was filtered out.
    1. Run the display acl { acl-number | name acl-name | all } command to ensure the multicast source address will not be filtered out, that is, ensure that the source address will not be denied by the ACL applied to multicast.

      • If the fault is rectified, proceed to Step 3.
      • If the fault persists, proceed to Step 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
    3. End.
  2. Cause 2: A multicast forwarding boundary was set.
    1. Run the display multicast boundary command to ensure the multicast group address is in the multicast forwarding boundary.

      • If the fault is rectified, proceed to Step 3.
      • If the fault persists, proceed to Step 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
    3. End.
  3. Cause 3: The RP address was wrong.
    1. Run the display pim rp-info command to ensure the configured RP address is right. Besides, the RP address configured on each multicast device should be same.

      • If the fault is rectified, proceed to Step 3.
      • If the fault persists, proceed to Step 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
    3. End.
  4. Cause 4: The upstream interface could not be found.
    1. Run the display ip routing-table command to ensure the unicast routes to multicast source or RP exist.

      • If the fault is rectified, proceed to Step 3.
      • If the fault persists, proceed to Step 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
    3. End.
  5. Cause 5: The multicast group was in the range of SSM group addresses.
    1. Run the display acl { acl-number | name acl-name | all } command to ensure the multicast group address is excluded in the ACL rules used to set SSM group range.

      • If the fault is rectified, proceed to Step 3.
      • If the fault persists, proceed to Step 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
    3. End.
  6. Cause 6: The memory was not enough.
    1. Ensure that system memory is enough.

      • If the fault is rectified, proceed to Step 3.
      • If the fault persists, proceed to Step 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
    3. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 123529

Downloads: 90

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