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 Establishing Neighbor Relationships in IPv4 PIM-SM

Adjusting Control Parameters for Establishing Neighbor Relationships in IPv4 PIM-SM

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

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.

Default Settings

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

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

Interval for sending Hello messages

30s

Holdtime of Hello messages

105s

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.

    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. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.

      1. Run quit

        Return to the system view.

      2. Run interface interface-type interface-number.subinterface-number

        The Layer 3 sub-interface view is displayed.

        The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

      3. Run dot1q termination vid vid

        Termination of Dot1q packets is configured on the Layer 3 sub-interface.

        By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

    5. Run pim timer hello interval

      The interval for sending Hello messages is configured.

    6. Run pim hello-option holdtime interval

      The holdtime of Hello messages is configured.

    7. Run commit

      The configuration is committed.

Configuring PIM Neighbor Filtering

Context

The switch 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 switch to reject Hello messages without Generation IDs so that switch connects to normally working PIM neighbors.

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. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.
    1. Run quit

      Return to the system view.

    2. Run interface interface-type interface-number.subinterface-number

      The Layer 3 sub-interface view is displayed.

      The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

    3. Run dot1q termination vid vid

      Termination of Dot1q packets is configured on the Layer 3 sub-interface.

      By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

  5. 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 switch is not in the configured range of valid neighbor addresses, the switch 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 switch is terminated.

  6. Run pim require-genid

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

  7. Run commit

    The configuration is committed.

Verifying the Configuration of Control Parameters for Establishing Neighbor Relationships in IPv4 PIM-SM

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

Document ID: EDOC1100075361

Views: 20778

Downloads: 21

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