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 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).
Adjusting Assert Control Parameters in IPv6 PIM-SM

Adjusting Assert Control Parameters in IPv6 PIM-SM

Pre-configuration Tasks

Before configuring assert control parameters, complete the following tasks:

  • Configure an IPv6 unicast routing protocol to ensure normal unicast routing on the network.
  • Enable IPv6 PIM-SM.

Context

When multiple PIM devices on a network segment pass the reverse path forwarding (RPF) check and forward multicast data to this network segment, assert election is required. When a device receives multicast data through a downstream interface, it knows that other upstream devices exist on this network segment. The device then sends an Assert message to compete with other upstream devices to forward multicast data.

PIM devices that fail the assert election disable their downstream interfaces from forwarding multicast data to this network segment. The assert loser state lasts for a period, which is called the holdtime of Assert messages. After the assert state timer times out, the devices that lost the Assert election restore pruned interfaces to the forwarding state to trigger a new round of Assert election.

NOTE:

The holdtime of Assert messages can be configured globally or on an interface. If you configure the holdtime of Assert messages in the global PIM-IPv6 view and in the interface view simultaneously, the configuration in the interface view takes effect.

Default Settings

The default holdtime of Assert messages is 180s.

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

    2. Run pim ipv6

      The PIM-IPv6 view is displayed.

    3. Run holdtime assert interval

      The holdtime of Assert messages is configured.

    4. Run commit

      The configuration is committed.

  • Configuration on an 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. Run pim ipv6 holdtime assert interval

      The holdtime of Assert messages is configured.

    5. Run commit

      The configuration is committed.

Verifying the Configuration

After assert control parameters are configured, you can check information about the IPv6 PIM interface, statistics about IPv6 PIM control messages, and IPv6 PIM routing table using the following commands:

  • Run the display pim ipv6 interface [ interface-type interface-number | up | down ] [ verbose ] command to check IPv6 PIM information on an interface.

  • Run the following commands in any view to check the number of sent and received IPv6 PIM control packets.

    • display pim ipv6 control-message counters message-type { probe | register | register-stop | crp }

    • display pim ipv6 control-message counters [ message-type { assert | hello | join-prune | bsr } | interface interface-type interface-number ] *

  • 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 { 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-04-20

Document ID: EDOC1100075361

Views: 22869

Downloads: 33

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