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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Applications

Applications

This section describes the applicable scenario of PIM.

PIM-SM Application in a Single AS

Figure 8-60 shows multicast services deployed on a large-scale network. The Interior Gateway Protocol (IGP) protocol 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 8-60 PIM-SM application in a single AS
Implementation Plan

As shown in Figure 8-60, 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 parameters, such as the interval for querying IGMP packets and hold time for memberships. If IGMP versions or parameters are inconsistent, IGMP member relationships on routers are different.

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

    NOTE:

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

Bidir-PIM Application in a Single AS

Figure 8-61 illustrates multicast service deployment on a large-scale network. An Interior Gateway Protocol (IGP) protocol is running on the network, and all network segments are reachable. A multicast protocol is required on the network to allow multi-party video conferences among users connected to the network.

Figure 8-61 Bidir-PIM application in a single AS
Implementation

As shown in Figure 8-61, HostA, HostB, HostC, and HostD need to join a multi-party video conference, and the entire PIM domain runs Bidir-PIM.

The network deployment is as follows:

  1. Enable Bidir-PIM on all routers in the PIM domain.

  2. Enable PIM-SM on all router interfaces so that they can set up PIM neighbor relationships.

  3. Select a router at the meeting point of multicast streams as the RP and configure the RP to serve Bidir-Pim. For example, RouterE in Figure 8-61 can act as the RP.

    Recommended RP deployment is as follows:

    • On small and medium networks, configure a static RP because the static RP is stable and has low requirements on device configurations.

      If a static RP is configured, all routers (including the RP) in the domain must be configured with the same RP information and multicast group range.

    • On large networks, deploy dynamic RP to improve reliability and facilitate maintenance.

    NOTE:

    Do not use both static and dynamic RP configurations in the same PIM domain because this may cause inconsistent RP information on routers.

  4. Run IGMP between RouterA and HostA, RouterB and HostB, RouterC and HostC, and RouterD and HostD.

    All router interfaces on the same network segment must run the same IGMP version (IGMPv2 is recommended) and have the same parameter settings, such as the query intervals and timeout period of group memberships. If router interfaces run different IGMP versions or use different parameter settings, routers cannot maintain consistent IGMP group membership.

  5. After the configurations are complete, routers on the network set up a bidirectional RPT rooted at the RP, and the hosts can communicate in a video conference.

    NOTE:

    To enable user hosts to receive multicast data stably, statically bind the multicast groups requested by user hosts to the interfaces directly connected to the user network segments.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57946

Downloads: 3621

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