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 12800 and 12800E 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 Basic IPv4 Bidir-PIM Functions

Configuring Basic IPv4 Bidir-PIM Functions

Context

Basic Bidir-PIM functions allow the switch to provide the Bidir-PIM service for hosts. A host can send multicast data to other hosts in the same multicast group as a multicast source and receive multicast data from other hosts as a receiver.

Pre-configuration Tasks

Before configuring basic Bidir-PIM functions, configure a unicast routing protocol to provide reachable routes on the network.

Configuration Procedure

The following configuration tasks are mandatory:

  1. Enabling Bidir-PIM
  2. Configuring an RP

The tasks of configuring a BSR administrative domain, adjusting C-RP parameters, and adjusting C-BSR parameters are optional.

Enabling Bidir-PIM

Context

Enabling Bidir-PIM globally is the prerequisite for configuring other Bidir-PIM parameters.

Bidir-PIM inherits the neighbor discovery mechanism of Protocol Independent Multicast Sparse Mode (PIM-SM) to reduce protocol complexity. Therefore, interfaces on a Bidir-PIM network must run PIM-SM to set up PIM neighbor relationships.

Procedure

  1. Run system-view

    The system view is displayed.

  2. (Optional) Run multicast forwarding optimization

    Multicast forwarding optimization is enabled.

    By default, multicast forwarding optimization is disabled.

    After multicast forwarding optimization is enabled on a standalone switch or a stack, the switch or stack dynamically adjusts traffic forwarding on switch fabrics or stack ports for each multicast group based on multicast traffic distribution in the system. This function saves multicast forwarding resources, but it consumes some processing resources and increases the response time to users' multicast requests. To enable multicast traffic to be transmitted to users quickly, disable the multicast forwarding optimization function.

    NOTE:

    The CE12800 supports this function. The CE12800E does not support this function after FD-X series cards are installed.

  3. Run multicast routing-enable

    IP multicast routing is enabled.

  4. Run pim

    The PIM view is displayed.

  5. Run bidir-pim

    Bidir-PIM is enabled.

    A multicast network does not allow routes that are destined for the same group address and generated by different PIM protocols. Therefore, when you enable Bidir-PIM , the system displays a message telling you that some multicast routes may be deleted. Determine whether multicast services will be affected if multicast routing information is deleted.

  6. Run quit

    Quit the PIM view.

  7. Run interface interface-type interface-number

    The interface view is displayed.

  8. On an Ethernet interface, run undo portswitch

    The interface is switched to Layer 3 mode.

    By default, an Ethernet interface works in Layer 2 mode.

    The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

    NOTE:

    If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

  9. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.
    1. Run quit

      Return to the system view.

    2. Run interface interface-type interface-number.subinterface-number

      The Layer 3 sub-interface view is displayed.

      The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

    3. Run dot1q termination vid vid

      Termination of Dot1q packets is configured on the Layer 3 sub-interface.

      By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

  10. Run pim sm

    PIM-SM is enabled.

  11. Run commit

    The configuration is committed.

Configuring an RP

Context

Like Protocol Independent Multicast Sparse Mode (PIM-SM), Bidir-PIM also requires a rendezvous point (RP) on the network to forward multicast data as a transit device. When configuring an RP for Bidir-PIM, specify the bidir keyword in the configuration command to specify that the RP serves Bidir-PIM.

An RP can be configured manually or elected through the BSR mechanism. Manually configuring a static RP reduces bandwidth used for frequent information exchange between the C-RPs and BSR. RP election through the BSR mechanism simplifies configuration and improves reliability of multicast forwarding because multiple C-RPs are configured.

To allow the local device to receive Auto-RP Announcement or Discovery messages from other devices, enable listening of Auto-RP messages.

You can configure a static RP and multiple C-RPs for dynamic RP election. The static RP functions as a backup RP because it has a lower priority. Ensure that all the devices on the network have the same RP information. Inconsistent RP information may cause forwarding failures on the network.

Default Settings

Table 4-22 lists the default settings of C-BSR and C-RP parameters.

Table 4-22 Default settings of C-BSR and C-RP parameters
Parameter Default Setting

C-BSR priority

0

C-BSR hash mask length

30

BSR message fragmentation

Disabled

Multicast group policy of a static RP

No multicast group policy configured (receiving multicast data with any group address)

Multicast group policy of a C-RP

No multicast group policy configured (receiving multicast data with any group address)

C-RP priority

0

Interval for sending C-RP Announcement messages

60s

Hold time of C-RP Announcement messages

150s

Procedure

  • Configure a static RP.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run static-rp rp-address [ basic-acl-number | acl-name acl-name ] [ preferred ] bidir

      A static RP address is specified, and the RP is configured to serve Bidir-PIM.

      The preferred keyword indicates that the static RP takes precedence over a dynamic RP.

      NOTE:

      All devices in a PIM domain must be configured with the same static RP address.

    4. Run commit

      The configuration is committed.

  • Configure a dynamic RP.

    1. Configure a C-BSR.

      1. Run system-view

        The system view is displayed.

      2. Run pim

        The PIM view is displayed.

      3. Run c-bsr interface-type interface-number [ hash-length [ priority ] ]

        A C-BSR is configured.

        It is recommended that you configure the C-BSR on the device that aggregates multicast data.

      4. (Optional) Run bsm semantic fragmentation

        The BSR message fragmentation function is enabled.

        NOTE:

        BSR message fragmentation solves the problem in IP fragmentation, where all fragments become unavailable due to loss of fragment information. Enable BSR message fragmentation on all devices. Otherwise, devices that do not fragment BSR messages may receive incomplete RP information.

      5. Run commit

        The configuration is committed.

    2. Configure a C-RP.

      1. Run system-view

        The system view is displayed.

      2. Run pim

        The PIM view is displayed.

      3. Run c-rp interface-type interface-number [ group-policy { basic-acl-number | acl-name acl-name } | priority priority | holdtime hold-interval | advertisement-interval adv-interval ]* bidir

        A C-RP interface is specified and configured to serve Bidir-PIM.

        It is recommended that you configure the C-RP on the device that aggregates multicast data.

      4. Run c-rp load-splitting group-modulo

        The device is configured to select the RP for a multicast group that users have joined based on the modulo of the group address and the number of C-RPs.

        By default, an RP is elected among C-RPs on a Bidir-PIM network according to the following rules:
        • The C-RP with the longest mask length of the served group address range matching the multicast group that users have joined wins.

        • If the mask length is the same, the C-RP with the highest priority (smallest priority value) wins.

        • If the priority is the same, C-RPs use a hash algorithm to calculate their hash values, and the C-RP with the largest hash value wins.

        • If all the preceding values are the same, the C-RP with the largest IP address wins.

        If the mask length and priority of C-RPs are the same, C-RPs use the multicast group that users have joined, their C-RP addresses, and C-RP address masks to calculate hash values. The C-RP with the largest hash value becomes the RP that serves the multicast group. This RP election method cannot evenly distribute multicast groups to RPs. As a result, bandwidth cannot be evenly allocated to multicast traffic, which may result in congestion on the multicast network.

        To solve the preceding problem, you can use the c-rp load-splitting group-modulo command to configure the C-RPs to select the RP for a multicast group that users have joined based on the modulo of the group address and the number of C-RPs. This RP election method can evenly distribute multicast groups to RRs to improve bandwidth efficiency on the multicast network. It is only applicable to networks with multiple C-RPs serving contiguous multicast group addresses.
        NOTE:

        An RP can serve multiple multicast groups simultaneously, but each multicast group can be associated with only one RP.

      5. Run commit

        The configuration is committed.

    3. (Optional) Configure a BSR boundary.

      1. Run system-view

        The system view is displayed.

      2. Run interface interface-type interface-number

        The interface view is displayed.

      3. On an Ethernet interface, run undo portswitch

        The interface is switched to Layer 3 mode.

        By default, an Ethernet interface works in Layer 2 mode.

        The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

        NOTE:

        If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

      4. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.
        1. Run quit

          Return to the system view.

        2. Run interface interface-type interface-number.subinterface-number

          The Layer 3 sub-interface view is displayed.

          The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

        3. Run dot1q termination vid vid

          Termination of Dot1q packets is configured on the Layer 3 sub-interface.

          By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

      5. Run pim bsr-boundary [ incoming ]

        A BSR service boundary is configured.

        NOTE:

        The BSR messages cannot pass through the BSR boundary. Therefore, it is recommended that you configure the BSR service boundary on interfaces at the edge of a PIM domain.

      6. Run commit

        The configuration is committed.

  • Enable listening of Auto-RP messages.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run auto-rp listening enable

      Listening of Auto-RP messages is enabled.

    4. Run commit

      The configuration is committed.

(Optional) Configuring a BSR Administrative Domain

Context

To facilitate PIM domain management, a PIM network is divided into multiple bootstrap router (BSR) administrative domains and a global domain. Each BSR administrative domain maintains only one BSR that serves specified multicast groups. Multicast groups that do not belong to any BSR administrative domain are served by the global domain. A device can join only one administrative domain, so devices in each administrative domain can forward multicast data independently. Data of multicast groups in the global domain can be forwarded through devices in any administrative domain.

The maximum range of multicast groups that a BSR administrative domain can serve is 239.0.0.0 to 239.255.255.255. Multicast addresses in this range are used as private group addresses.

Procedure

  1. Enable BSR administrative domain on all devices in the PIM domain.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run c-bsr admin-scope

      The BSR administrative domain is enabled.

    4. Run commit

      The configuration is committed.

  2. Configure a BSR administrative domain boundary on an edge interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.

      1. Run quit

        Return to the system view.

      2. Run interface interface-type interface-number.subinterface-number

        The Layer 3 sub-interface view is displayed.

        The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

      3. Run dot1q termination vid vid

        Termination of Dot1q packets is configured on the Layer 3 sub-interface.

        By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

    5. Run multicast boundary group-address { mask | mask-length }

      The boundary of the BSR administrative domain is configured.

      NOTE:

      Multicast packets that belong to the BSR administrative domain cannot traverse the boundary.

    6. Run commit

      The configuration is committed.

  3. Configure a group address range for the C-BSR in each BSR administrative domain.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run c-bsr group group-address { mask | mask-length } [ hash-length hash-length | priority priority ] *

      A group address range is configured for the C-BSR in each BSR administrative domain.

    4. Run commit

      The configuration is committed.

  4. Configure a C-BSR in the global domain.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run c-bsr global [ hash-length hash-length | priority priority ] *

      A C-BSR is configured for the global administrative domain.

    4. Run commit

      The configuration is committed.

(Optional) Adjusting C-RP Control Parameters

Context

When a candidate rendezvous point (C-RP) is configured on an interface, the C-RP periodically sends Advertisement messages to a bootstrap router (BSR). The Advertisement messages carry the C-RP priority and the holdtime of Advertisement messages. After receiving Advertisement messages, the BSR starts the C-RP timeout timer. The timer value is set to the holdtime of Advertisement messages. Before the timer expires, the BSR collects the C-RP information in Advertisement messages into an RP-set, encapsulates the RP-set into a Bootstrap message, and advertises the Bootstrap message to all PIM devices in the PIM domain. If the BSR does not receive any Advertisement message from the C-RP after the timer expires, the BSR considers the C-RP invalid or unreachable on the network. The interval for sending Advertisement messages must be smaller than the holdtime of Advertisement messages.

You can manually configure the interval for sending Advertisement messages, C-RP priority and holdtime of Advertisement messages. To prevent C-RP spoofing, set the range of valid C-RP addresses on the BSR. Then the BSR accepts only the Advertisement messages with the source addresses in the specified range.

Procedure

  • Configure parameters on Advertisement messages on the C-RP.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run c-rp priority priority

      The C-RP priority is configured.

    4. Run c-rp advertisement-interval interval

      The interval for sending Advertisement messages is configured.

    5. Run c-rp holdtime interval

      The time period to hold the Advertisement messages received from the C-RP is configured.

    6. Run commit

      The configuration is committed.

  • Configure the valid C-RP address range on the BSR.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run c-rp policy { advanced-acl-number | acl-name acl-name }

      The range of valid C-RP addresses and the range of groups that C-RPs serve are configured.

    4. Run commit

      The configuration is committed.

(Optional) Adjusting C-BSR Control Parameters

Context

Candidate bootstrap routers (C-BSRs) automatically elect a BSR in a PIM domain. At first, each C-BSR considers itself as a BSR and sends Bootstrap messages to all devices in the domain. When a C-BSR receives a Bootstrap message from another C-BSR, it compares the priority in the received Bootstrap message with its own priority. The C-BSR with a higher priority wins. If the two BSRs have the same priority, the BSR with a larger IP address is preferred. After a C-BSR is elected as the BSR, it encapsulates its own IP address and the RP-Set information into a Bootstrap message and sends the Bootstrap message in the PIM domain. The Bootstrap message contains a hash mask which is used for hash calculation in C-RP election.

The BSR periodically sends a Bootstrap message to the network. When the other C-BSRs receive the Bootstrap message, they start the holdtime timer. If they do not receive any Bootstrap message from the BSR when the holdtime timer expires, they consider that the BSR fails and initiate the election of a new BSR. The interval for sending Bootstrap messages must be smaller than the holdtime of a Bootstrap message.

You can configure the C-BSR priority, the BSR hash mask length, the interval for sending Bootstrap messages, and the holdtime of Bootstrap messages. To prevent BSR spoofing, set a range of valid BSR addresses on devices, so that the devices receive messages only from the BSRs within the address range.

Default Settings

Table 4-23 lists the default settings of the C-BSR.

Table 4-23 Default settings of the C-BSR
Parameter Default Setting

Interval for sending Bootstrap messages

60s

Holdtime of Bootstrap messages

130s

Procedure

  • Configure parameters contained in a Bootstrap message for a C-BSR.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run c-bsr priority priority

      The priority of the C-BSR is configured.

    4. Run c-bsr hash-length priority

      The hash mask length of the C-BSR is configured.

    5. Run c-bsr interval interval

      The interval for the BSR to send Bootstrap messages is configured.

    6. Run c-bsr holdtime interval

      The holdtime of the Bootstrap message received from the BSR is configured.

    7. Run commit

      The configuration is committed.

  • Configure a valid BSR address range on a PIM device.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run bsr-policy { basic-acl-number | acl-name acl-name }

      The range of valid BSR addresses is configured.

    4. Run commit

      The configuration is committed.

Verifying the Basic IPv4 Bidir-PIM Function Configuration

Prerequisites

After basic Bidir-PIM functions are configured, you can check information about the BSR, RP, PIM interfaces, PIM neighbors, and PIM routing table.

Procedure

  • Run the display pim bsr-info command to check BSR information.
  • Run the display pim rp-info [ group-address ] command to check RP information.
  • Run the display pim interface [ interface-type interface-number | up | down ] [ verbose ] command to check PIM information on interfaces.
  • Run the display pim neighbor [ neighbor-address | interface interface-type interface-number | verbose ] * command to check PIM neighbor information.
  • Run either of the following commands to check PIM routing information:

    • display pim routing-table [ group-address [ mask { group-mask-length | group-mask } ] ] { rpf-interface interface-type interface-number | mode bidir } * [ outgoing-interface { include | exclude | match } { interface-type interface-number | none } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]
    • display pim routing-table brief [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } ] *

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 40353

Downloads: 13

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