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 V200R005C00

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).
PIM-SM Application in a Single AS

PIM-SM Application in a Single AS

Figure 4-23 shows multicast services deployed on a large-scale network. The Interior Gateway Protocol (IGP) is running on the network and all network segments are reachable. Multicast group members are sparsely distributed. Hosts on this network want to receive VoD information, and network bandwidth needs to be used efficiently.

Figure 4-23 PIM-SM application in a single AS

Implementation Plan

As shown in Figure 4-23, HostA, HostB, and HostC are receivers of multicast video streams. The entire PIM domain runs PIM-SM. RouterA connects to multicast source S1 and RouterC connects to multicast source S2. RouterB connects to the network segment of HostA; RouterE and RouterG connect to the network segment of HostB and HostC.

The network deployment must meet the following requirements:

  • PIM-SM is enabled on all router interfaces.

  • The core device closest to the multicast source is used as the C-RP because multicast sources are densely distributed. The interfaces of RouterC and RouterD are configured as the C-BSR and C-RP. The BSR and RP are elected dynamically.

    Recommended RP deployment is as follows:

    • On small- and medium-scale networks, a static RP can be used because the static RP is stable and has low requirements for device configurations.

      If there is only one multicast source, a device directly connected to the multicast source can be used as a static RP so that the source DR does not need to register with the RP.

      If a static RP is deployed, all routers including the RP in the same domain must be configured with the same RP information and the same range of multicast groups.

    • On large-scale networks, a dynamic RP can be used because a dynamic RP is highly reliable and easy to maintain.

      If multiple densely distributed multicast sources exist on the network, a core device close to the multicast sources is used as the C-RP. If there are multiple densely distributed group members, a core device close to the group members is used as the C-RP.

    NOTE:

    To ensure consistent RP information on all devices in the PIM domain, use the same type of RP (static or dynamic) on all the devices.

  • IGMP runs between the routers and hosts on a shared network segment (between RouterB and HostA, and between RouterE/RouterG and HostB/HostC).

    All router interfaces on the same network segment must run the same IGMP protocol version and be configured with the same parameter settings, such as the query interval and timeout period of group memberships. If IGMP versions or parameter settings are inconsistent, IGMP group memberships on routers will be different.

  • After the network is deployed, HostA, HostB, and HostC send Join messages to the RP based on service requirements, and multicast data sent from the multicast source can reach the receivers.

    NOTE:

    It is recommended that members be statically added to a multicast group at the network border. This improves the stability of multicast services.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039595

Views: 47640

Downloads: 85

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