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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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 IGMP

Configuring IGMP

This section describes the procedures for configuring IGMP.

Configuring Basic IGMP Functions

After basic IGMP configurations are complete on interfaces connected to user networks, user hosts can access the IPv4 multicast network and receive IPv4 multicast data.

Pre-configuration Tasks

Before configuring IGMP basic functions, configure a unicast routing protocol to ensure that multicast devices have reachable unicast routes to each other.

Configuration Process

Among the following configuration tasks, Enabling IGMP and Configuring the IGMP Version are mandatory. The other configuration tasks are optional.

Enabling IGMP

Context

IP multicast routing is the prerequisite for all the multicast functions. Enable IP multicast routing before configuring any multicast protocol.

To configure IGMP functions on the multicast switch, first enable IGMP on interfaces connected to group members.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    multicast routing-enable

    IP multicast routing is enabled.

    By default, the IP multicast routing function is disabled.

  3. Run:

    interface interface-type interface-number

    The interface view is displayed.

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

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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.

  5. Run:

    pim sm

    Protocol Independent Multicast-Sparse Mode (PIM-SM) is enabled on the interface.

    By default, PIM-SM is disabled on an interface.

  6. Run:

    igmp enable

    IGMP is enabled on the interface.

    By default, IGMP is disabled on an interface.

    NOTE:

    When configuring IGMP on interfaces of CX11x&CX31x&CX91x series switch modules, you must also enable PIM-SM on these interfaces so that they can forward multicast data packets.

  7. Run:

    commit

    The configuration is committed.

Configuring the IGMP Version

Context

A multicast switch modules can identify IGMP messages of a version earlier than its own IGMP version but cannot identify IGMP messages of a later version. To ensure normal IGMP operation, ensure that the switch modules runs the same IGMP version as member hosts or a later IGMP version.

If there are multiple multicast switch moduleses on a shared network segment of hosts, all host-side interfaces of these multicast switch moduleses must run the same IGMP version. If they are running different IGMP versions, IGMP cannot function normally on the network.

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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp version { 1 | 2 | 3 }

    The IGMP version is specified for the interface.

    By default, an interface runs IGMPv2 after IGMP is enabled on the interface.

  5. Run:

    commit

    The configuration is committed.

(Optional) Configuring a Static Multicast Group on an Interface

Context

This configuration applies to some special scenarios, for example:

  • There are long-term group members on a network segment.

  • Hosts on a network segment cannot send Report messages, but multicast data needs to be forwarded to the network segment.

In these scenarios, you can configure a static multicast group on the switch modules interface connected to the network segment. Then multicast data can be forwarded fast, stably to the network segment or be directed to the interface. After a static multicast group is configured on an interface, the switch modules considers that the multicast group always has members on the network segment of the interface and always forwards multicast data of the multicast group to the interface.

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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp static-group group-address [ inc-step-mask { group-mask | group-mask-length } number group-number ] [ source source-address ]

    A static multicast group or source-group is configured on the interface.

    By default, no static multicast group is configured on an interface.

    NOTE:

    If a static multicast group or source-group is configured on a loopback interface, the multicast switch modules forwards multicast data to this group only when users request the data, which reduces traffic on the network. If a static multicast group or source-group is configured on other IGMP-capable interfaces, the switch modules forwards multicast data to the group immediately after receiving the data. For example, you can configure static multicast groups on a loopback interface if users may request data of these groups but have not requested the data at present. If some multicast groups have stable receivers on a network segment, you can configure the static multicast groups on the interface connected to this network segment.

  5. Run:

    commit

    The configuration is committed.

(Optional) Configuring the Range of Multicast Groups That an Interface Can Join

Context

To control the range of multicast groups that hosts on an interface's network segment can join, use an ACL to filter Membership Report messages received on the interface. This ACL allows the switch modules to maintain only memberships of the interface in these multicast groups. For details on how to configure an ACL, see "ACL Configuration" in the CX11x&CX31x&CX91x Series Switch Modules Configuration Guide - Security.

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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp group-policy { acl-number | acl-name acl-name } [ 1 | 2 | 3 ]

    An ACL is applied to specify the range of multicast groups that the interface can join.

    By default, an interface can join any multicast group.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Context

After completing basic IGMP configuration on an interface, you can run the following commands in any view to check the IGMP configuration, IGMP running information, and membership information on the interface.

Procedure

  • Run the display igmp interface [ interface-type interface-number | up | down ] [ verbose ] command to check the IGMP configuration and running information on an interface.
  • Run the display igmp group [ group-address | interface interface-type interface-number ]* [ verbose ] command to check information about the members that have dynamically joined a multicast group.
  • Run the display igmp group [ group-address | interface interface-type interface-number ]* static [ verbose ] command to check information about members of a static multicast group.

Optimizing IGMP Performance

After you configure basic IGMP functions, the switch modules can work normally using the default IGMP configurations. You can optimize IGMP parameter settings to enhance network security and performance.

Pre-configuration Tasks

Configuring Basic IGMP Functions

Configuration Process

The following tasks are optional and can be performed in any sequence.

Configuring the Router-Alert Option

Context

Generally, a network device sends a message to the corresponding protocol module for processing only when the destination address of the message is the address of a local interface. According to this rule, IGMP messages cannot be sent to the IGMP module 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 module without checking the destination IP address of the message.

By default, the switch modules sends received IGMP messages to the IGMP module for processing no matter whether the messages have the Router-Alert option in their IP headers. This ensures compatibility between the switch modules and other devices. To improve device performance, reduce transmission cost, and enhance protocol security, configure the switch modules to discard IGMP messages without the Router-Alert option.

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

NOTE:

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

  • The configuration in the IGMP view is valid globally, whereas the configuration in the interface view is valid only for the specific interface.
  • If the Router-Alert option is configured in the interface view and the IGMP view, the configuration in the interface view takes precedence over the 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

      The IGMP view is displayed.

    3. Run:

      require-router-alert

      The switch modules 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 switch modules does not check whether the received IGMP messages contain the Router-Alert option, and it accepts all the received IGMP messages.

    4. Run:

      undo send-router-alert disable

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

      By default, IGMP messages sent by the switch modules 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.

      If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    5. Run:

      undo igmp send-router-alert disable

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

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

    6. Run:

      commit

      The configuration is committed.

Configuring IGMP Querier Parameters

Context

IGMP maintains group memberships using Query and Report messages. When multiple multicast switch moduleses exist on a network segment, an IGMP querier is elected among them to send IGMP Query messages. The IGMP querier can work normally using default settings of querier parameters. You can modify the querier parameters to enable the querier to update group membership in a timely manner and avoid network congestion.

Table 8-22 lists description and default setting of IGMP querier parameters.

Table 8-22 Description and Default setting of IGMP querier parameters

Parameter

Description

Default Setting

Interval for sending IGMP General Query messages

The querier sends IGMP General Query messages at the specified interval to maintain memberships of interfaces. This parameter specifies the interval for sending IGMP General Query messages.

60s

Robustness variable of the IGMP querier

The robustness variable of the IGMP querier specifies the retransmission count of IGMP packets to minimize impact of packet loss on the network.

The robustness variable defines the following values:
  • Number of times the querier sends General Query messages after startup.
  • Number of times the querier sends Multicast Address Specific Query messages or Multicast Address and Source Specific Query messages after receiving a Done message.

2

Maximum response time for IGMP General Query messages

After a multicast member receives an IGMP General Query message, it must send a Report message to the IGMP querier within the maximum response time.

10s

Other querier present interval

If non-queriers do not receive any Query message within the Keepalive period, they consider the querier invalid and trigger election of a new querier.

125s if the robustness variable, interval for sending IGMP General Query messages, and maximum response time are all default values

Interval for sending IGMP Group-Specific Query messages or IGMP Group-and-Source-Specific Query messages

When the querier receives a Done message that a host sends to leave a multicast group, the querier periodically sends Multicast Address Specific Query messages or Multicast Address and Source Specific Query messages to check for other members in the multicast group. This parameter specifies the interval for sending Multicast Address Specific Query messages or Multicast Address and Source Specific Query messages.

1s

NOTE:

If IGMP is enabled on user-side interfaces of multiple devices on a shared network segment, the devices must have the same querier configuration. Otherwise, IGMP may not function normally.

The IGMP querier parameters can be configured in the IGMP view or interface view.

  • The configuration in the IGMP view is valid globally, whereas the configuration in the interface view is valid only for the specific interface.
  • If a querier parameter is configured in the interface view and the IGMP view, the configuration in the interface view takes precedence over the configuration in the IGMP view. If a querier parameter 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 global IGMP querier parameters
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      igmp

      The IGMP view is displayed.

    3. Run:

      timer query interval

      The interval for sending IGMP General Query messages is configured.

    4. Run:

      robust-count robust-value

      The robustness variable of the IGMP querier is configured.

    5. Run:

      max-response-time interval

      The maximum response time for IGMP General Query messages is configured.

    6. Run:

      timer other-querier-present interval

      The other querier present interval is configured.

    7. Run:

      lastmember-queryinterval interval

      The interval at which the device sends IGMP Group-Specific Query messages or IGMP Group-and-Source-Specific Query messages is configured.

    8. Run:

      commit

      The configuration is committed.

    NOTE:

    Ensure that the interval for sending General Query messages is larger than the maximum response time for IGMP Query messages and is smaller than the other querier present interval.

  • Configuring IGMP querier parameters 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.

      If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

      igmp timer query interval

      The interval for sending IGMP General Query messages is configured.

    5. Run:

      igmp robust-count robust-value

      The robustness variable of the IGMP querier is configured.

    6. Run:

      igmp max-response-time interval

      The maximum response time for IGMP General Query messages is configured.

    7. Run:

      igmp timer other-querier-present interval

      The other querier present interval is configured.

    8. Run:

      igmp lastmember-queryinterval interval

      The interval at which the interface sends IGMP Group-Specific Query messages or IGMP Group-and-Source-Specific Query messages is configured.

    9. Run:

      commit

      The configuration is committed.

    NOTE:

    Ensure that the interval for sending General Query messages is larger than the maximum response time for IGMP Query messages and is smaller than the other querier present interval.

Configuring IGMP Fast Leave

Context

In some scenarios, a querier interface connects to only one receiver host. If the host frequently switches between multiple multicast groups, you can configure the fast leave function on the interface so that the interface can quickly respond to Leave messages sent from the host.

After the fast leave function is configured, the querier does not send a Group-Specific Query message after receiving a Leave message from the host. Instead, the querier directly notifies the upstream multicast device that the host has left the multicast group. The fast leave function reduces delay in response to Leave messages and saves network bandwidth.

IGMP fast leave applies only to IGMPv2 and IGMPv3.

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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp prompt-leave [ group-policy { acl-number | acl-name acl-name } ]

    Fast leave is configured on the interface.

    By default, the switch modules sends a Group-Specific Query message after receiving a Leave message.

  5. Run:

    commit

    The configuration is committed.

Configuring IGMP On-Demand

Context

In a standard IGMP working process, the querier periodically sends Query messages and collects group membership information based on Report and Leave messages sent from hosts. If group members on a network seldom change, you can configure IGMP on-demand on the querier. IGMP on-demand enables the querier to maintain group memberships based on requirements of hosts, without sending Query messages. This function reduces the number of IGMP messages exchanged between the querier and hosts, conserving bandwidth on the network.

After IGMP on-demand is configured on an interface of the switch modules:

  • The interface no longer sends IGMP Query messages.
  • The switch modules creates IGMP group entries after receiving IGMP Report messages. The entries will never age out.
  • The switch modules deletes a group entry immediately after receiving an IGMP Leave message for the group.

IGMP on-demand applies only to IGMPv2 and IGMPv3.

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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp on-demand

    IGMP on-demand is enabled on the interface. The interface then does not send IGMP Query messages, and IGMP group entries on the interface will never age out.

    By default, an interface periodically sends Query messages and participates in querier election.

    NOTE:

    The querier does not process dynamic IGMP entries that have been generated before IGMP on-demand is enabled on it.

  5. Run:

    commit

    The configuration is committed.

Filtering IGMP Messages Based on Source IP Addresses

Context

IGMP runs between receiver hosts and the Layer 3 multicast switch modules that is directly connected to the host network segment. A multicast switch modules 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 modules interfaces connected to hosts. The switch modules 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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp query ip-source-policy { basic-acl-number | acl-name acl-name }

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

    By default, the switch modules 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.

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

  6. Run:

    commit

    The configuration is committed.

Checking the Configuration

Context

After completing the preceding configuration, you can run the following commands in any view to check the adjusted membership information, IGMP configuration, and IGMP running information.

Procedure

  • Run the display igmp group [ group-address | interface interface-type interface-number ]* [ verbose ] command to check information about IGMP groups that hosts have dynamically joined by sending IGMP Report messages.
  • Run the display igmp interface [ interface-type interface-number | up | down ] [ verbose ] command to check the IGMP configuration and running information on an interface.

Configuring IGMP SSM Mapping

To enable IGMPv1 or IGMPv2 hosts to use the SSM service, configure IGMP SSM mapping on the switch modules.

Pre-configuration Tasks

Enabling IGMP

Context

The SSM model allows IGMPv3 hosts to specify the multicast sources which they want to receive data from. However, some hosts can only run IGMPv1 or IGMPv2. To enable these hosts to use the SSM service, configure IGMP SSM mapping on the switch modules. IGMP SSM mapping is implemented based on static SSM mapping entries on the switch modules. The switch modules converts (*, G) information in IGMPv1 and IGMPv2 Report messages to (S, G) information according to static SSM mapping entries to provide the SSM service for IGMPv1 and IGMPv2 hosts. By default, SSM group addresses range from 232.0.0.0 to 232.255.255.255. You can expand the range of SSM group addresses. For details, see (Optional) Configuring an SSM Group Policy.

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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

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

    igmp ssm-mapping enable

    IGMP SSM mapping is enabled on the interface.

    By default, IGMP SSM mapping is disabled on an interface.

    NOTE:

    To ensure that hosts running any IGMP version on a network segment can obtain SSM services, enable IGMPv3 on switch modules interfaces.

  5. Run:

    quit

    Return to the system view.

  6. Run:

    igmp

    The IGMP view is displayed.

  7. Run:

    ssm-mapping group-address { group-mask | group-mask-length } source-address

    An SSM mapping rule is configured to map a group address to a multicast source.

    By default, no SSM mapping rule is configured.

  8. Run:

    commit

    The configuration is committed.

Checking the Configuration

After configuring IGMP SSM mapping on an interface, run the following commands in any view to check the configured mapping entries and whether IGMP SSM mapping is enabled on the interface.

  • Run the display igmp group [ group-address | interface interface-type interface-number ]* ssm-mapping [ verbose ] command to check information about group memberships established with IGMP SSM mapping.
  • Run the display igmp ssm-mapping { group [ group-address ] | interface [ interface-type interface-number ] } command to check SSM mapping entries configured and whether IGMP SSM mapping is enabled on an interface.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59530

Downloads: 3623

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