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

CLI-based Configuration Guide - IP Multicast

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the basic concepts, configuration procedures, and configuration examples of the interfaces supported by the device.
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).
Source DR Does Not Send Register Messages to the RP After Receiving Multicast Data Packets

Source DR Does Not Send Register Messages to the RP After Receiving Multicast Data Packets

Fault Description

After multicast configuration is complete on a network, a multicast source sends multicast data. However, the rendezvous point (RP) does not generate any multicast routing entry, and the source designated router (DR) does not send any Register message to the RP.

Procedure

  1. Run the display pim routing-table group-address command on the source DR to check whether the source DR considers itself as a source DR.

    Only a source DR can send Register messages to the RP. The following information shows that the source DR considers itself as a source DR.

    <Huawei> display pim routing-table 225.0.0.1
     VPN-Instance: public net
     Total 0 (*, G) entry; 1 (S, G) entry
    
     (172.16.0.12, 225.0.0.1)
         RP: 10.2.2.2
         Protocol: pim-sm, Flag: SPT LOC ACT
         UpTime: 02:54:43
         Upstream interface: GigabitEthernet1/0/0
             Upstream neighbor: NULL
             RPF prime neighbor: NULL
         Downstream interface(s) information:
         Total number of downstreams: 1
             1: GigabitEthernet2/0/0
                 Protocol: pim-sm, UpTime: 02:54:43, Expires: 00:02:47

  2. If the LOC flag is not displayed, the device does not consider itself as a source DR. Run the display rm interface interface-type interface-number command to check whether the peer address of the upstream interface is the multicast source address.

    In this example, the upstream interface is GE1/0/0. Run the following command to check the peer address of GE1/0/0:

    <Huawei> display rm interface gigabitethernet 1/0/0
    Name: GigabitEthernet1/0/0
    Physical IF Info:
     IfnetIndex: 0x6
     State: DOWN P2P MULT
     Hardware Address: 286E-D4D4-4F54
     Slot: 0(Logic Slot: 0)
     IntType: 3, PriLog: 0, MTU: 1500, Reference Count 1
     Bandwidth: 0, 64000
     Baudrate: 0, 64000
     Delay: 0, Reliability: 0, Load: 0
     LDP-ISIS sync capability: disabled
     LDP-OSPF sync capability: disabled
     InstanceID: 0, Instance Name: Public
     Age: 1236sec
    Logical IF Info:
     IfnetIndex: 0x3E, PhyIndex: 21 Logical Index : 3,
     Dest: 172.16.0.12, Mask: 255.255.255.0
     State: UP PRM BCA MULT , Reference Count 3
     Age: 1623973sec 
    

  3. If the peer address is not the multicast source address, change the multicast source address to the peer IP address. Then the source RP can complete registration successfully.
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100069332

Views: 18353

Downloads: 44

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