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 Control Parameters for Join/Prune Messages in IPv6 PIM-SM

Adjusting Control Parameters for Join/Prune Messages in IPv6 PIM-SM

Pre-configuration Tasks

Before adjusting control parameters for Join/Prune messages, complete the following tasks:

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

Context

A multicast device sends Join messages upstream to require forwarding of multicast data, and Prune messages upstream for requiring to stop forwarding multicast data. You can adjust control parameters for Join/Prune messages as required. If there is no special requirement, the default values are recommended.

Configuration Procedure

You can configure time parameters for Join/Prune messages, disable Join/Prune packaging, Prune delay, and Join information filtering in any sequence as required.

Adjusting Time Parameters for Join/Prune Messages

Context

A multicast device sends Join messages upstream to require forwarding of multicast data, and Prune messages upstream for requiring to stop forwarding multicast data. Join information and prune information are encapsulated in Join/Prune messages. The PIM device periodically sends Join/Prune messages to an upstream device to update the forwarding state. When the upstream device receives a Join/Prune message, it starts a timer and sets the timer value to the holdtime of the Join/Prune message. If the device does not receive any Join/Prune message when the timer expires, it acts as follows:

  • If the previously received Join/Prune message is sent by a host to join a multicast group, the device stops sending multicast data to the downstream interface of the multicast group.
  • If the previously received Join/Prune message is sent to prune the downstream interface of a multicast group, the device starts to send multicast data packets to the downstream interface.

Therefore, the interval for sending Join/Prune messages must be smaller than the holdtime of a Join/Prune message.

NOTE:

The interval for sending Join/Prune messages and the holdtime of Join/Prune messages can be set globally or on an interface. If you configure the two parameters in the global PIM-IPv6 view and in the interface view simultaneously, the configuration in the interface view takes effect.

Default Settings

Table 5-13 lists the default settings of time parameters for Join/Prune messages.

Table 5-13 Default settings of time parameters for Join/Prune messages
Parameter Default Setting

Interval for sending Join/Prune messages

60s

Holdtime of Join/Prune messages

210s

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

    2. Run pim ipv6

      The PIM-IPv6 view is displayed.

    3. Run timer join-prune interval

      The interval for sending Join/Prune messages is configured.

    4. Run holdtime join-prune interval

      The holdtime of Join/Prune messages is configured.

    5. 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 timer join-prune interval

      The interval for sending Join/Prune messages is configured.

    5. Run pim ipv6 holdtime join-prune interval

      The holdtime of Join/Prune messages is configured.

    6. Run commit

      The configuration is committed.

Disabling Join/Prune Message Packaging

Context

The efficiency for sending Join/Prune messages in a package is higher than that for separately sending a large number of Join/Prune messages. By default, a device sends Join/Prune messages in a package. Because the size of a Join/Prune message package is large, devices that have poor performance cannot receive the Join/Prune message package. To prevent packets from being discarded, disable the Join/Prune message packaging function.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run pim ipv6

    The PIM-IPv6 view is displayed.

  3. Run join-prune triggered-message-cache disable

    The real-time Join/Prune message packaging function is disabled.

  4. Run commit

    The configuration is committed.

Adjusting Control Parameters for Prune Delay

Context

LAN-delay specifies the delay from the time a device receives a Prune message from a downstream interface to the time it sends the Prune message to an upstream interface. A PIM device does not prune the corresponding downstream interface immediately after it sends the Prune message. If another device still requests multicast data, it needs to send a Join message to the upstream device within this period. The period for overriding the Prune message is called override-interval. The delay from the time a PIM device receives a Prune message to the time it performs the prune action is the sum of the lan-delay and override-interval.

NOTE:

The lan-delay and override-interval can be configured globally or on an interface. If you configure the lan-delay and override-interval in the global PIM-IPv6 view and in the interface view simultaneously, the configuration in the interface view takes effect.

Default Settings

Table 5-14 lists the default settings of control parameters for prune delay.

Table 5-14 Default settings of control parameters for prune delay
Parameter Default Setting

LAN-delay

500 ms

Override-interval

2500 ms

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

    2. Run pim ipv6

      The PIM-IPv6 view is displayed.

    3. Run hello-option lan-delay interval

      The delay for transmitting messages in a LAN is configured.

    4. Run hello-option override-interval interval

      The interval for overriding the prune action is configured.

    5. 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 hello-option lan-delay interval

      The delay for transmitting messages in a LAN is configured.

    5. Run pim ipv6 hello-option override-interval interval

      The interval for overriding the prune action is configured.

    6. Run commit

      The configuration is committed.

Configuring a Join Information Filtering Policy

Context

To prevent access of unauthorized users, configure a join information filtering policy to specify a valid source address range for join information contained in Join/Prune messages.

Procedure

  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 join-policy { asm { basic-acl6-number | acl6-name acl6-name } | ssm { advanced-acl6-number | acl6-name acl6-name } | advanced-acl6-number | acl6-name acl6-name }

    A Join information filtering policy is configured and a valid source address range is specified.

  5. Run commit

    The configuration is committed.

Verifying the Configuration of Control Parameters for Join/Prune Messages in IPv6 PIM-SM

Prerequisites

After control parameters for Join/Prune messages are configured, you can check information about the IPv6 PIM interface, statistics about IPv6 PIM control messages, and IPv6 PIM routing table.

Procedure

  • 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 to check the number of sent or received IPv6 PIM control messages.

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

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

Downloads: 23

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