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).
Configuring the IPv4 Router-Alert Option

Configuring the IPv4 Router-Alert Option

Context

Generally, a network device sends a message to the corresponding protocol stack for processing only when the destination address of the message is the address of a local interface. IGMP messages therefore cannot be sent to the IGMP stack because their destination addresses are multicast addresses but not a local interface address. As a result, the network device cannot maintain group memberships. The Router-Alert option is introduced to solve this problem. If a message contains the Router-Alert option in the IP header, devices that receive the message send the message to the corresponding protocol stack without checking its destination IP address.

By default, the switch sends received IGMP messages to the IGMP stack for processing regardless of whether the messages contain the Router-Alert option in their IP headers. This ensures compatibility between the switch and other devices. Configuring the switch to discard IGMP packets without the Router-Alert option can improve device performance, reduce transmission cost, and enhance protocol security.

You can also configure the switch to send IGMP messages with or without the Router-Alert option. By default, the switch sends IGMP messages with the Router-Alert option. If the switch needs to communicate with a device that does not support the Router-Alert option, configure the switch to send IGMP messages without the Router-Alert option.

NOTE:

The Router-Alert option can be configured in the IGMP view or interface view.

  • Configuration in the IGMP view is valid globally, whereas configuration in the interface view is valid only for the specific interface.
  • If the Router-Alert option is configured in both the interface view and IGMP view, configuration in the interface view takes precedence over configuration in the IGMP view. If the Router-Alert option is not configured on an interface, the interface uses the configuration in the IGMP view.
  • If non-default configuration is performed in the IGMP view, the default configuration in the interface view does not take effect.

Procedure

  • Configuring the Router-Alert option globally
    1. Run system-view

      The system view is displayed.

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

      The IGMP view is displayed.

    3. Run require-router-alert

      The switch is configured to check the Router-Alert option in received IGMP messages and drop IGMP messages without the Router-Alert option.

      By default, the switch does not check whether the received IGMP messages contain the Router-Alert option, and accepts all the received IGMP messages.

    4. Run undo send-router-alert disable

      The switch is configured to send IGMP messages with the Router-Alert option.

      By default, IGMP messages sent by the switch contain the Router-Alert option.

    5. Run commit

      The configuration is committed.

  • Configuring the Router-Alert option 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 igmp require-router-alert

      The interface is configured to check the Router-Alert option in received IGMP messages and drop the IGMP messages without the Router-Alert option.

      By default, the device does not check for the Router-Alert option in IGMP messages and processes all the IGMP messages received on an interface.

    6. Run undo igmp send-router-alert disable

      The interface is configured to send IGMP messages with the Router-Alert option.

      By default, IGMP messages sent by an interface contain the Router-Alert option.

    7. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 20490

Downloads: 21

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