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 IPv4 PIM-SM Anycast RP

Configuring IPv4 PIM-SM Anycast RP

Context

Anycast RP allows several RPs with the same address to be configured in an IPv4 PIM-SM domain and establish peer relationships, so that a multicast source can register with the closest RP and receivers can join the closest RP. This releases burdens on a single RP, implements RP backup, and optimizes multicast forwarding paths. Currently, there are two anycast implementations: Multicast Source Discovery Protocol (MSDP) for Anycast RP and PIM for Anycast RP. In IPv4 network deployment, choose either of the two modes. It is recommended that the two modes be not used together.

Pre-configuration Tasks

Before configuring IPv4 PIM-SM Anycast RP, complete the following tasks:

Configuration Procedure

Perform the configuration tasks in the listed sequence.

Configuring Global Anycast RP

Context

Either a static or dynamic RP can be used on the network. It is recommended that an RP be configured on loopback interfaces. The same RP address is configured on multiple switches where anycast RP will be deployed.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run pim [ vpn-instance vpn-instance-name ]

    The PIM view is displayed.

  3. Run anycast-rp rp-address

    Anycast RP is configured.

    The anycast RP address must be the same as that of the RP address on the current network.

  4. Run commit

    The configuration is committed.

Configuring Local Addresses for Anycast RPs

Context

The devices functioning as Anycast RPs are identified by the same logical address so that the RP in the PIM-SM domain is unique. However, the devices need to distinguish one another during communication, so the Anycast RP addresses cannot be used. In this situation, you need to configure the Anycast RP local address and Anycast RP peers.

After the local address is configured, the RP uses the local addresses as the source addresses of the packets when sending Register packets to Anycast RP peers.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run pim [ vpn-instance vpn-instance-name ]

    The PIM view is displayed.

  3. Run anycast-rp rp-address

    The Anycast RP view is displayed.

  4. Run local-address local-address

    Local addresses are configured for Anycast RP.

    NOTE:

    You are advised to use the address of the Loopback interface as the local address of the Anycast RP.

    The local address of the Anycast RP must be different from the address of the Anycast RP.

  5. Run commit

    The configuration is committed.

Configuring Anycast RP Peers

Context

The devices functioning as Anycast RPs are identified by the same logical address so that the RP in the PIM-SM domain is unique. However, the devices need to distinguish one another during communication, so the Anycast RP addresses cannot be used. In this situation, you need to configure the Anycast RP local address and Anycast RP peers.

After Anycast RP peers are configured, the RP uses the peer addresses as the destination addresses of the packets when sending Register packets to Anycast RP peers.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run pim [ vpn-instance vpn-instance-name ]

    The PIM view is displayed.

  3. Run anycast-rp rp-address

    The Anycast RP view is displayed.

  4. Run peer peer-address [ fwd-msdp-sa [ acl-number | acl-name acl-name ] ]

    Anycast RP peers are configured.

    In a PIM-SM domain, devices functioning as Anycast RP must be fully connected. Anycast RP peer relationships need to be configured between every two Anycast RPs.

  5. Run commit

    The configuration is committed.

Verifying the IPv4 PIM-SM Anycast RP Configuration

Context

After IPv4 PIM-SM Anycast RP is configured, you can check the IPv4 PIM-SM Anycast RP configuration.

Procedure

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info command to check the RP.
  • Run the following commands to check the PIM routing table.

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

    • display pim { vpn-instance vpn-instance-name | all-instance } routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | mode { ssm | sm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]

    • display pim [ vpn-instance vpn-instance-name | all-instance ] 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: EDOC1100039595

Views: 46720

Downloads: 85

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