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

CLI-based Configuration Guide - IP Multicast

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the basic concepts, configuration procedures, and configuration examples of the interfaces supported by the device.
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 Establishing Neighbor Relationships

Adjusting Control Parameters for Establishing Neighbor Relationships

Pre-configuration Tasks

Before configuring control parameters for establishing neighbor relationships, complete the following tasks:

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

Configuration Procedure

You can configure the Hello message control parameters, neighbor tracking function, and neighbor filtering function in any sequence as required.

Adjusting Control Parameters for Hello Messages

Context

PIM devices send Hello messages periodically to maintain PIM neighbor relationships. When a PIM device receives a Hello message from a neighbor, the PIM device starts the timer and sets the timer to the holdtime of Hello messages. If the PIM device does not receive a new Hello message from the neighbor within the holdtime, it considers the neighbor invalid or unreachable. Therefore, the interval for a PIM device to send Hello messages must be smaller than the holdtime of Hello messages.

If multiple PIM devices transmit Hello messages simultaneously, a conflict occurs on the network. To solve this problem, when a PIM device receives a Hello message, it waits a period before transmitting the Hello message. This period can be a random value and is smaller than the maximum delay for triggering Hello messages.

NOTE:

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

You can configure the maximum delay for triggering Hello messages only in the interface view.

Default Settings

Table 4-15 lists the default settings of control parameters for Hello messages.

Table 4-15  Default settings of control parameters for Hello messages
Parameter Default Setting

Interval for sending Hello messages

30s

Holdtime of Hello messages

105s

Maximum delay for triggering Hello messages

5s

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

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

      The PIM view is displayed.

    3. Run timer hello interval

      The interval for sending Hello messages is configured.

    4. Run hello-option holdtime interval

      The holdtime of Hello 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. Run pim timer hello interval

      The interval for sending Hello messages is configured.

    4. Run pim hello-option holdtime interval

      The holdtime of Hello messages is configured.

    5. Run pim triggered-hello-delay interval

      The maximum delay for triggering Hello messages is configured.

Enabling Downstream Neighbor Tracking

Context

When sending a Hello message, a PIM device generates a Generation ID and adds it to the message. If the status of the device changes, the device generates a new Generation ID. When a neighboring device receives the Hello message and finds that the Generation ID changes, it sends a Join message to refresh the neighbor relationship. Devices on a shared network segment use a listening mechanism to prevent multiple devices from simultaneously sending Join messages to the same upstream device. When a device detects the Join message sent from another device to an upstream device, it does not send Join messages to this upstream PIM device. Therefore, the upstream PIM neighbor with a changed Generation ID cannot refresh neighbor relationships with each downstream neighbor.

After the neighbor tracking function is enabled, PIM devices no longer trigger Join message suppression when they detect a Join message sent by another PIM device. Instead, they keep sending Join messages to the same upstream neighbor.

NOTE:

The neighbor tracking function can be enabled globally or on an interface. If you configure the neighbor tracking function in the global PIM view and in the interface view simultaneously, the configuration in the interface view takes effect.

The neighbor tracking function can be implemented only when all devices on the shared network segment have this function enabled.

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

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

      The PIM view is displayed.

    3. Run hello-option neighbor-tracking

      The function of tracking a downstream neighbor is enabled.

  • 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. Run pim hello-option neighbor-tracking

      The function of tracking a downstream neighbor is enabled.

Configuring PIM Neighbor Filtering

Context

The router supports different neighbor filtering policies to ensure secure and effective multicast transmission in a Protocol Independent Multicast Sparse Mode (PIM-SM) domain. You can perform the following operations to filter neighbors:
  • Configure a valid neighbor address range to prevent unauthorized neighbors from connecting to the network.
  • Configure the router to reject Hello messages without Generation IDs so that router connects to normally working PIM neighbors.
  • Enable the PIM neighbor check function to discard Join/Prune messages and Assert messages that are not sent from neighbors or send Join/Prune messages and Assert messages only to neighbors.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run pim neighbor-policy { basic-acl-number | acl-name acl-name }

    The range of valid neighbor addresses is configured.

    • If the IP address of a PIM neighbor that has established a neighbor relationship with the router is not in the configured range of valid neighbor addresses, the router will no longer receive Hello messages from this PIM neighbor. When the holdtime of Hello messages expires, the neighbor relationship between the PIM device and the router is terminated.

  4. Run pim require-genid

    The device is configured to receive only Hello messages that contain Generation IDs.

  5. Run quit

    The system exits from the interface view.

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

    The PIM view is displayed.

  7. Run neighbor-check { receive | send }

    The PIM neighbor check function is enabled.

Verifying the Configuration of Control Parameters for Establishing Neighbor Relationships

Prerequisites

After the control parameters for establishing the neighbor relationship are adjusted, you can check information about the PIM interface and the PIM neighbor.

Procedure

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface [ interface-type interface-number | up | down ] [ verbose ] command to check PIM information on an interface.
  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] neighbor [ neighbor-address | interface interface-type interface-number | verbose ] * command to check information about PIM neighbors.
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100069332

Views: 18365

Downloads: 44

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