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 V200R005C00

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).
Filtering IGMP Messages Based on Source IPv4 Addresses

Filtering IGMP Messages Based on Source IPv4 Addresses

Context

A Layer 3 multicast switch directly connected to a user network segment processes all the IGMP messages received. To improve security and prevent multicast services from being affected by IGMP messages maliciously forged by other devices, you can configure IGMP message filtering on switch interfaces connected to hosts. The switch supports filtering of IGMP Query, Report and Leave 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. 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 query ip-source-policy { basic-acl-number | acl-name acl-name }

    A policy is configured on the interface to filter Query messages based on source IP addresses.

    By default, the switch does not filter Query messages and processes all the received Query messages.

    NOTE:

    When configuring an ACL rule for the interface, use the permit parameter to configure the interface to accept only Query messages with source addresses in a specified range. If no rule is configured in the ACL, the interface denies all IGMP Query messages.

  6. Run igmp ip-source-policy [ basic-acl-number | acl-name acl-name ]

    A policy is configured on the interface to filer Report/Leave messages based on source IP addresses.

    By default, the switch does not filter Report/Leave messages and processes all the received Report/Leave messages.

    After Report/Leave message filtering is configured without specifying an ACL, the switch processes Report messages based on source IP addresses as follows:

    • If the source IP address of a Report message is 0.0.0.0 or on the same network segment as the IP address of the inbound interface, the switch processes the Report message.

    • If the source IP address of a Report message is on a different network segment than the IP address of the inbound interface, the switch discards the Report message.

    NOTE:

    When configuring an ACL rule for the interface, use the permit parameter to configure the interface to accept only Report/Leave messages with source addresses in a specified range. If no rule is configured in the ACL, the interface denies all IGMP Report/Leave messages.

  7. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039595

Views: 47285

Downloads: 85

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