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).
Configuring Basic IPv6 Bidir-PIM Functions

Configuring Basic IPv6 Bidir-PIM Functions

Context

Basic IPv6 Bidir-PIM functions allow the switch to provide the IPv6 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 IPv6 Bidir-PIM functions, configure an IPv6 unicast routing protocol to provide reachable routes on the IPv6 network.

Configuration Procedure

The following configuration tasks are mandatory:

  1. Enabling IPv6 Bidir-PIM
  2. Configuring an RP

The tasks of adjusting candidate rendezvous point (C-RP) control parameters and adjusting candidate bootstrap router (C-BSR) control parameters are optional.

Enabling IPv6 Bidir-PIM

Context

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

IPv6 Bidir-PIM inherits the neighbor discovery mechanism of IPv6 PIM-SM to reduce protocol complexity. Therefore, interfaces on an IPv6 Bidir-PIM network must run IPv6 PIM-SM to set up IPv6 PIM neighbor relationships.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast ipv6 routing-enable

    IPv6 multicast routing is enabled.

  3. Run pim ipv6

    The PIM-IPv6 view is displayed.

  4. Run bidir-pim

    IPv6 Bidir-PIM is enabled.

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

  5. Run quit

    Quit the PIM-IPv6 view.

  6. Run interface interface-type interface-number

    The interface view is displayed.

  7. 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.

  8. Run pim ipv6 sm

    IPv6 PIM-SM is enabled.

  9. Run commit

    The configuration is committed.

Configuring an RP

Context

Like IPv6 PIM-SM, IPv6 Bidir-PIM also requires a rendezvous point (RP) on the network to forward multicast data as a transit device. When configuring an RP for IPv6 Bidir-PIM, specify the bidir keyword in the configuration command to specify that the RP serves IPv6 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 candidate rendezvous points (C-RPs) and bootstrap router (BSR). RP election through the BSR mechanism simplifies configuration and improves reliability of multicast forwarding because multiple C-RPs are configured.

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 5-16 lists the default settings of C-BSR and C-RP parameters.

Table 5-16 Default settings of the C-BSR and C-RP
Parameter Default Setting

C-BSR priority

0

C-BSR hash mask length

126

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

192

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 ipv6

      The PIM-IPv6 view is displayed.

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

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

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

      NOTE:

      All devices in an IPv6 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 ipv6

        The PIM-IPv6 view is displayed.

      3. Run c-bsr ipv6-address [ hash-length [ priority ] ]

        The IPv6 address of the C-BSR interface is specified.

        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 is recommended because it can solve the problem faced by IP fragmentation that 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 information about RPs.

      5. Run commit

        The configuration is committed.

    2. Configure a C-RP.

      1. Run system-view

        The system view is displayed.

      2. Run pim ipv6

        The PIM-IPv6 view is displayed.

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

        The IPv6 address of the C-RP interface is specified and the C-RP is configured to serve IPv6 Bidir-PIM.

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

      4. 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. Run pim ipv6 bsr-boundary

        A BSR service boundary is configured.

        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 an IPv6 PIM-SM domain.

      5. 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 IPv6 PIM devices. 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 so that the BSR can successfully receive the 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 ipv6

      The PIM-IPv6 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 ipv6

      The PIM-IPv6 view is displayed.

    3. Run c-rp policy { advanced-acl6-number | acl6-name acl6-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 an IPv6 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 losers stop sending Bootstrap messages. The Bootstrap message contains a hash mask which is used for hash calculation in rendezvous point (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 5-17 lists the default settings of the C-BSR.

Table 5-17 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 ipv6

      The PIM-IPv6 view is displayed.

    3. Run c-bsr priority priority

      The priority of the C-BSR is configured.

    4. Run c-bsr hash-length hash-length

      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 an IPv6 PIM device.
    1. Run system-view

      The system view is displayed.

    2. Run pim ipv6

      The PIM-IPv6 view is displayed.

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

      The range of valid BSR addresses is configured.

    4. Run commit

      The configuration is committed.

Verifying the Basic IPv6 Bidir-PIM Function Configuration

Prerequisites

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

Procedure

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

    • display pim ipv6 routing-table [ ipv6-group-address [ mask mask-length ] ] { 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 ipv6 routing-table brief [ ipv6-source-address [ mask mask-length ] | ipv6-group-address [ mask mask-length ] | incoming-interface { interface-type interface-number | register } ] *

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039595

Views: 47266

Downloads: 85

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