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).
Adjusting the Control Parameters for Prune Messages

Adjusting the Control Parameters for Prune Messages

Context

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

Configuration Process

Configuration tasks in this section can be performed in any sequence.

Adjusting Time Related Parameters for Join/Prune Messages

Context

Prune information encapsulated in a Join/Prune message, which is defined by the IPv6 PIM protocol to control multicast forwarding. When the upstream neighbor receives a Join/Prune message, it starts a timer and sets the timer value to the holdtime of the Join/Prune message. If the upstream neighbor does not receive any Join/Prune message when the timer expires, the upstream neighbor starts to forward multicast data to the downstream interface again.

NOTE:

The holdtime of Join/Prune messages is configured in the PIM-IPv6 view or interface view. If the holdtime is configured both in the PIM-IPv6 view and interface view, the configuration in the interface view takes effect.

Default Configuration

Table 5-6 lists the default configuration of time related parameters for Join/Prune messages.

Table 5-6  Default configuration of time related parameters for Join/Prune messages
Parameter Default Setting

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:

      holdtime join-prune interval

      The holdtime of Join/Prune messages is configured.

  • 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. (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 holdtime join-prune interval

      The holdtime of Join/Prune messages is configured.

Adjusting the Information Carrying Capacity of Join/Prune Messages

Context

You can configure the maximum size of each Join/Prune message, maximum number of entries in a Join/Prune message, and Join/Prune message transmission method on the switch to adjust prune information sent to upstream interfaces.

  • If a PIM neighbor spends a long time to process each Join/Prune message, set a smaller size for each Join/Prune message on the switch to reduce the number of (S, G) entries carried in Join/Prune messages. This mitigates the pressure on the PIM neighbor.
  • If the throughput of Join/Prune messages on the PIM neighbor is low, the neighbor may fail to process Join/Prune messages in a timely manner, causing route flapping. To prevent this problem, set a smaller queue size for the Join/Prune message transmission queue to reduce the number of (S, G) entries carried in Join/Prune messages sent to the PIM neighbor per second. Then the switch sends Join/Prune messages in batches to the PIM neighbor, with a few Join/Prune messages in each batch.
  • By default, Join/Prune messages are transmitted to upstream neighbors in a package to improve the transmission efficiency. Disable the package function if needed.
Default Configuration

Table 5-7 lists the default configuration of Join/Prune messages.

Table 5-7  Default configuration of Join/Prune messages
Parameter Default Setting

Maximum size of each Join/Prune message

8100 bytes

Maximum number of entries contained in Join/Prune messages

1020

Join/Prune message transmission method

Encapsulated in a package

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    pim-ipv6

    The PIM-IPv6 view is displayed.

  3. Run:

    join-prune max-packet-length packet-length

    The maximum size of each Join/Prune message to be sent is configured.

  4. Run:

    join-prune periodic-messages queue-size queue-size

    The maximum number of entries in Join/Prune messages sent in a second is configured.

  5. Run:

    join-prune triggered-message-cache disable

    The function to package Join/Prune messages in real time is disabled.

Adjusting the Control Parameters for Prune Delay

Context

LAN-delay specifies the delay from when a device receives a Prune message from a downstream interface to when 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 when a PIM device receives a Prune message to when it performs the prune action is the sum of the LAN-delay and override-interval.

NOTE:

The LAN-delay and override-interval are 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 Configuration

Table 5-8 lists the default configuration of control parameters for prune delay.

Table 5-8  Default configuration 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.

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

Checking the Configuration

Context

After control parameters for Join/Prune messages are configured, 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 display pim ipv6 control-message counters [ message-type { assert | graft | graft-ack | hello | join-prune | state-refresh | bsr } | interface interface-type interface-number ] * command to check the number of sent or received IPv6 PIM control messages.
  • Run the following commands to check the IPv6 PIM routing table.

    • Run the 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 ] ] command to check detailed information about the IPv6 PIM routing table.

    • Run the 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 } ] * command to check brief information about the IPv6 PIM routing table.

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000141903

Views: 154087

Downloads: 111

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