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

S7700 and S9700 V200R010C00

This document describes IP multicast basics and how to configure IP multicast features, including IGMP/MLD, PIM (IPv4&IPv6), MSDP, multicast VPN, Layer 3 multicast CAC, Layer 2 multicast CAC, IGMP/MLD snooping, and multicast VLAN, IPv4&IPv6 multicast route management, static multicast MAC address, multicast network.
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 IPv6 PIM-SM in the ASM Model

Configuring IPv6 PIM-SM in the ASM Model

Context

When unicast routes on an IPv6 are reachable, you can implement IPv6 PIM-SM in the ASM model by:
  • Enabling IPv6 multicast routing on each device
  • Enabling IPv6 PIM-SM on each interface
  • Configuring an RP on the network

Pre-configuration Tasks

Before configuring IPv6 PIM-SM in the ASM model, configure an IPv6 unicast routing protocol to ensure that unicast routes on the network are reachable.

Configuration Process

The mandatory steps for configuring IPv6 PIM-SM in the ASM model are:

  1. Enable IPv6 PIM-SM.
  2. Configure a rendezvous point (RP).

Other configuration tasks are optional.

Enabling IPv6 PIM-SM

Context

IPv6 PIM-DM and IPv6 PIM-SM cannot be enabled simultaneously on a switch.

It is recommended that you enable IPv6 PIM-SM on all interfaces in a PIM-SM domain, so that the interfaces can establish neighbor relationships with all connected PIM devices.

If IPv6 PIM-SM and MLD need to be enabled on the same interface, enable IPv6 PIM-SM, and then enable MLD.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. (Optional) Run:

    set multicast forwarding-table super-mode

    The high specification mode is configured for multicast forwarding.

    In large-scale multicast applications, the switch generates a large number of IPv6 PIM routing entries. When the number of IPv6 PIM routing entries reaches the default limit, new IPv6 PIM routing entries cannot be generated. The high specification mode increases the number of IPv6 PIM routing entries supported on the switch. After this mode is configured, the number of IPv6 PIM routing entries can reach the maximum number supported by the switch, maximizing the switch's capability to support large-scale multicast applications.

    NOTE:
    • The configuration of high specification mode takes effect after a restart.

    • After the high specification mode is configured, the default interval for sending IPv6 PIM-SM Join/Prune messages changes from 210s to 300s.

  3. (Optional) Run:

    assign multicast-resource-mode optimize

    The multicast replication capability of LPUs is improved.

    If the switch needs to replicate a huge number of multicast packets, run this command to improve the multicast replication capability before enabling IPv6 multicast routing.

  4. Run:

    multicast ipv6 routing-enable

    The IPv6 multicast routing function is enabled.

  5. Run:

    interface interface-type interface-number

    The interface view is displayed.

  6. (Optional) 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.

  7. Run:

    pim ipv6 sm

    IPv6 PIM-SM is enabled.

Configuring an RP

Context

A rendezvous point (RP) is configured manually or elected through the bootstrap router (BSR) mechanism. Manually configuring a static RP reduces the bandwidth used for frequent information exchange between the candidate rendezvous points (C-RPs) and BSR. RP election through the BSR mechanism simplifies configuration and improves the reliability of multicast forwarding because multiple C-RPs are configured.

On an IPv6 PIM-SM network, the embedded RP function is enabled on each device by default. When a device receives a multicast packet sent to a multicast group, it can obtain RP information from the group address. The devices with the embedded RP function do not need to know the mapping between RPs and group addresses beforehand. The range of group addresses that a device can parse can be manually changed.

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 Configuration

Table 5-11 lists the default configuration of the C-BSR and C-RP.

Table 5-11  Default configuration 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 (accepting multicast data with any group address)

Multicast group policy of a C-RP

No multicast group policy configured (accepting 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

Scope ID of the administrative domain served by a C-RP

No scope ID is specified

Group address range for embedded RP

FF7x::/12 (x is 0 or any value ranging from 3 to F)

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 ]

      Address of a static RP is specified.

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

      NOTE:

      All devices in the PIM-SM domain must be configured with the same static RP address so that the static RP works properly.

  • 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 ] ]

        A C-BSR is configured.

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

        NOTE:

        To avoid frequent protocol changes caused by interface flapping, using loopback interfaces is recommended.

      4. (Optional) Run:

        bsm semantic fragmentation

        The BSR message fragmentation function is enabled.

        NOTE:

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

    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 } | scope scope-id } | holdtime hold-interval | priority priority ] *

        A C-RP is configured.

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

        NOTE:

        To avoid frequent protocol changes caused by interface flapping, using loopback interfaces is recommended.

    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. (Optional) 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.

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

  • Configure the embedded RP function.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim-ipv6

      The PIM-IPv6 view is displayed.

    3. Run:

      embedded-rp [ basic-acl6-number | acl6-name acl6-name ]

      The embedded RP function is enabled and the range of group addresses that can be parsed is configured.

      NOTE:

      If an IPv6 ACL is specified in the command, the final group address range for embedded RP is the intersection of the group address range specified by the IPv6 ACL and the default group address range. All the devices in the PIM-SM domain must be configured with the same group address range.

(Optional) Configuring a BSR Administrative Domain

Context

To facilitate PIM-SM domain management, a PIM-SM 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.

NOTE:

When configuring the boundary of a BSR administrative domain on an IPv6 network, you can specify the group address range served by the domain and set a scope ID for the domain. On candidate BSRs (C-BSRs), you only need to specify the scope ID of the BSR administrative domain and do not need to specify the group address range served by the BSR administrative domain.

Procedure

  1. Enable BSR administrative domain on all devices in the PIM-SM domain.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim-ipv6

      The PIM-IPv6 view is displayed.

    3. Run:

      c-bsr admin-scope

      The BSR administrative domain is enabled.

  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. (Optional) 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.

    4. Run:

      multicast ipv6 boundary { ipv6-group-address ipv6-group-mask-length | scope scope-id }

      The boundary of the BSR administrative domain is configured.

      • Multicast packets that belong to the BSR administrative domain cannot traverse the boundary.
      • After the scope ID of a BSR administrative domain is specified on an interface, multicast packets with this scope ID cannot be forwarded through the interface.

  3. Configure the scope ID of the administrative domain served by the C-BSR in each BSR administrative domain.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim-ipv6

      The PIM-IPv6 view is displayed.

    3. Run:

      c-bsr scope scope-id [ hash-length hash-length | priority priority ] *

      The scope ID of the administrative domain served by the C-BSR is specified.

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

      system-view

      The system view is displayed.

    2. Run:

      pim-ipv6

      The PIM-IPv6 view is displayed.

    3. Run:

      c-bsr global [ hash-length hash-length | priority priority ] *

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

(Optional) Configuring SPT Switchover Conditions

Context

A high volume of multicast data traffic increases the load of an RP and may result in a fault. The DR at the group member side triggers an SPT switchover to reduce the burden of the RP.

By default, a DR at the group member side immediately triggers an SPT switchover after receiving the first multicast data packet. You can configure a traffic rate threshold on a DR at the group member side to trigger an SPT switchover or prevent the DR from triggering an SPT switchover.

NOTE:

Setting the traffic rate for triggering an SPT switchover may affect multicast service operations. You are advised to use the default triggering condition. That is, an SPT switchover is triggered immediately after the first multicast data packet is received from the RPT. The default triggering condition reduces the number of multicast packets forwarded on the RPT.

Default Configuration

Table 5-12 lists the default configuration of SPT switchover conditions.

Table 5-12  Default configuration of SPT switchover conditions
Parameter Default Setting

Group policy that specifies the groups to which the SPT switchover conditions apply

No group policy configured (The SPT switchover conditions apply to all multicast groups.)

Interval for checking the forwarding rate of multicast data

15s

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    pim-ipv6

    The PIM-IPv6 view is displayed.

  3. Run:

    spt-switch-threshold { traffic-rate | infinity } [ group-policy { basic-acl6-number | acl6-name acl6-name } [ order order-value ] ]

    The SPT switchover condition is configured.

    traffic-rate specifies the rate threshold that triggers an SPT switchover. infinity indicates that the SPT switchover is never triggered.

  4. Run:

    timer spt-switch interval

    The interval for checking the forwarding rate of multicast data is configured.

(Optional) Adjusting the Control Parameters for Source Registering

Context

After receiving multicast data from a multicast source, the source DR encapsulates multicast data in a Register message and forwards the message to the RP. Therefore, you can adjust control parameters for source registering on the RP and source DR.

Perform the following operations on the source DR.

  • Configure the register message suppression time

    .

    After receiving a Register-Stop message, the source DR stops sending Register messages to the RP during register suppression. The source DR forwards packets again when the register suppression time expires and it receives no more Register-Stop messages.

  • Configure the interval at which null Register messages are sent.

    When the timeout period for keeping the register suppression state is too long or too short, multicast data cannot be forwarded normally. Sending null Register messages during register suppression can relieve this problem.

  • Configure the source address for Register messages.

    The RP cannot receive Register messages from a source DR if the source address of the Register messages is not a unique IPv6 address on the network or if the source address is filtered out by a policy configured on the RP. To enable the RP to receive Register messages from the source DR, configure a new source address for the Register messages.

Perform the following operations on the RP.

  • Configure a policy to filter Register messages. You can specify the source address range of Register messages to improve network security.
Default Configuration

Table 5-13 lists default configuration of control parameters for source registering.

Table 5-13  Default configuration of control parameters for source registering
Parameter Default Setting

Filter policy for Register messages

No filter policy configured (receiving Register messages with any group address)

Register message suppression time

60s

Interval for sending null Register messages

5s

Procedure

  • Configure control parameters for source registering on the source DR.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim-ipv6

      The PIM-IPv6 view is displayed.

    3. Run:

      register-suppression-timeout interval

      Register message suppression time is configured.

    4. Run:

      probe-interval interval

      The interval for sending null Register messages is configured.

      NOTE:

      The value of probe-interval must be smaller than half of register-suppression-timeout.

    5. Run:

      register-source ipv6-address

      The source address of Register messages sent from the source DR is configured.

      It is recommended that you use the IPv6 address of a loopback interface on the source DR as the source address of Register messages.

  • Configure control parameters for source registering on the RP.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim-ipv6

      The PIM-IPv6 view is displayed.

    3. Run:

      register-policy { advanced-acl6-number | acl6-name acl6-name }

      A policy for filtering Register messages is configured.

(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:
  1. Collects C-RP information in Advertisement messages into an RP-set.
  2. Encapsulates the RP-set into a Bootstrap message.
  3. 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 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.

NOTE:

For the default values of the parameters carried in Advertisement messages, see Configuring an RP.

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.

  • 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:

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

      NOTE:

      When configuring an ACL rule for the device, use the permit parameter to configure the device to accept only Advertisement messages with addresses in a specified range. If no rule is configured in the ACL, the device discards Advertisement messages.

(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 Configuration

Table 5-14 lists the default configuration of the C-BSR.

Table 5-14  Default configuration of the C-BSR
Parameter Default Setting

Interval for sending Bootstrap messages

60s

Holdtime of Bootstrap messages

130s

NOTE:

For the default values of other C-BSR parameters, see Configuring an RP.

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.

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

      NOTE:

      When configuring an ACL rule for the device, use the permit parameter to configure the device to accept only Bootstrap messages with source addresses in a specified range. If no rule is configured in the ACL, the device discards Bootstrap messages from all source addresses.

Checking the Configuration

Prerequisites

After configuration of IPv6 PIM-SM in ASM model is complete, check information about the BSR, RP, IPv6 PIM interface, IPv6 PIM neighbor, and IPv6 PIM routing table.

Procedure

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

    • display pim ipv6 routing-table [ ipv6-source-address [ mask mask-length ] | ipv6-group-address [ mask mask-length ] | flags flag-value | fsm | incoming-interface { interface-type interface-number | register } | mode { dm | sm | ssm } | outgoing-interface { exclude | include | match } { interface-type interface-number | none | register } ] * [ 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-08-21

Document ID: EDOC1000141903

Views: 147058

Downloads: 111

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