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

Configuration Guide - IP Multicast

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, PIM (IPv4), PIM (IPv6), MSDP, multicast VPN, multicast route management (IPv4), multicast route management (IPv6), IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN, multicast network management.
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).
Configuring the Content of an SA Message

Configuring the Content of an SA Message

Context

The interval for sending multicast data by some multicast sources is longer than the aging time of (S, G) entries. In this case, the source designated router (DR) can only encapsulate multicast data into Register messages, and send the messages to the source rendezvous point (RP). The source RP transmits (S, G) information contained in Source-Active (SA) messages to the remote RP. Then the remote RP sends an (S, G) Join message to the source DR and creates an SPT. The remote RP cannot receive multicast data sent by this source because the (S, G) entry is aged out.

After the function of encapsulating a multicast packet in an SA message is enabled on a source RP, the source RP encapsulates a multicast packet in an SA message and sends the message out. After receiving the SA message, the remote RP decapsulates it and transmits the multicast packet along RPT to users in the local domain.

In addition, you can set the time to live (TTL) threshold to control what multicast data will be encapsulated in the SA message and forwarded to the MSDP peer.
  • When the RP creates an SA message for the first time, it checks the TTL value of the IP header in the multicast packet. If the value is smaller than the threshold, the RP does not create an SA message. If the value is equal to or larger than the threshold, the RP encapsulates the multicast packet in an SA message and forwards the message to an MSDP peer.
  • When the RP receives an SA message that contains the multicast packet, it reduces the TTL value in the IP header by 1 and checks the TTL value. If the value is smaller than the threshold, the RP does not forward the SA message to any MSDP peer. If the value is equal to or larger than the threshold, the RP forwards the SA message to an MSDP peer.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run msdp [ vpn-instance vpn-instance-name ]

    The MSDP view is displayed.

  3. Run encap-data-enable

    The function of encapsulating multicast data packets in SA messages is enabled.

  4. (Optional) Run peer peer-address minimum-ttl ttl

    The TTL value of multicast data packets is set.

    By default, the TTL value of multicast data packets is set to 0.

  5. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 20497

Downloads: 21

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