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 MLD

Configuring MLD

This section describes the detailed MLD configuration procedure.

Configuring Basic MLD Functions

After basic MLD functions are configured on a multicast device interface connected to a user network segment, user hosts can access the IPv6 multicast network and receive IPv6 multicast data.

Pre-configuration Tasks

Before configuring basic MLD functions, complete the following task:

Configuring an IPv6 unicast routing protocol to ensure that IPv6 routes between nodes are reachable.

Configuration Process

Enabling MLD and configuring the MLD version are mandatory. Other configurations are optional.

Enabling MLD

Context

IPv6 multicast routing is the prerequisite for configuring all IPv6 multicast functions. You must enable IPv6 multicast routing before configuring an IPv6 multicast protocol.

Before configuring MLD on a multicast switch, enable MLD on an interface connected to receiver hosts.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    multicast ipv6 routing-enable

    IPv6 multicast routing is enabled.

  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 ipv6 sm

    PIM-SM (IPv6) is enabled on the interface.

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

  6. Run:

    mld enable

    MLD is enabled on the interface.

    By default, MLD is disabled on an interface.

    NOTE:

    An interface of the CX11x&CX31x&CX91x series switch modules must run both PIM-SM (IPv6) and MLD to forward multicast data packets.

  7. Run:

    commit

    The configuration is committed.

Configuring the MLD Version

Context

A multicast switch modules can identify MLD messages of a version earlier than its own MLD version but cannot identify MLD messages of a later version. To ensure normal MLD operation, ensure that the switch modules runs the same MLD version as receiver hosts or a later MLD 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 MLD version. If they are running different MLD versions, MLD 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:

    mld version { 1 | 2 }

    The MLD version is specified for the interface.

    By default, an interface runs MLDv2 after MLD is enabled on the interface.

  5. Run:

    commit

    The configuration is committed.

(Optional) Configuring Static MLD Multicast Groups on Interfaces

Context

In some scenarios such as when:

  • Stable multicast members exist on the network, so that fast and stable multicast data forwarding is required.

  • Hosts require multicast data but cannot send Multicast Listener Report messages.

You can configure a static multicast group on the user-side interface of a switch modules. After a static multicast group is configured on the interface, the switch modules considers that multicast group members exist on the network segment to which the interface belongs. Therefore, the switch modules always forwards multicast data sent to the multicast group.

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:

    mld static-group ipv6-group-address [ inc-step-mask ipv6-group-mask-length number group-number ] [ source ipv6-source-address ]

    One or more static multicast groups are configured on the interface.

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

    NOTE:

    If a static MLD group is configured on a loopback interface, the switch modules forwards multicast data to this group only when users request the data, which reduces traffic on the network. If a static MLD group is configured on other MLD-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 limit the range of IPv6 multicast groups that an interface can join, configure ACL6 rules to filter received Multicast Listener Report messages so that the interface maintains multicast membership only in the allowed multicast groups..
NOTE:

Before specifying the range of multicast groups that an interface can join, configure an ACL6 to define the range of multicast groups. For details about the ACL6 configuration, 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:

    mld group-policy { acl6-number | acl6-name acl6-name } [ 1 | 2 ]

    The range of multicast groups that the interface can join is configured.

    By default, an interface can join any multicast group.

    NOTE:

    When configuring an ACL6 rule for an interface, use the permit parameter in the rule command to allow hosts connected to the interface to join groups within the specified range. If no rule is configured in the ACL6, hosts connected to the interface cannot join any multicast groups.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Context

After basic MLD functions are configured, run the following commands in any view to check the MLD configuration, running status, and information about receiver hosts.

Procedure

  • Run the display mld interface [ interface-type interface-number | up | down ] [ verbose ] command to check the MLD information on an interface.
  • Run the display mld group [ ipv6-group-address | interface interface-type interface-number ] * [ verbose ] command to check information about MLD groups that hosts have dynamically joined by sending Multicast Listener Report messages.
  • Run the display mld group [ ipv6-group-address | interface interface-type interface-number ]* static [ verbose ] command to check information about members of a static MLD multicast group.

Optimizing MLD Performance

After basic MLD functions are configured, the multicast switch modules can properly work by default. You can modify parameters to optimize MLD performance according to requirements for network security and performance optimization.

Pre-configuration Tasks

Configuring basic MLD functions

Configuration Process

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

Configuring the Router-Alert Option

Context

An IPv6 network device sends received messages whose destination IPv6 addresses are local interface addresses to the routing protocol module. If the destination address of a message is not the local interface address, the message cannot be sent to the correct module. For example, the destination address of an MLD message is a multicast address, the message cannot be sent to the MLD module and membership cannot be maintained. The Router-Alert option is introduced to solve this problem. If a message contains the Router-Alert option in the IPv6 header, devices that receive the message send the message to the corresponding protocol module without checking the destination IPv6 address of the message.

By default, the switch modules sends received MLD messages to the MLD module for processing no matter whether the messages have the Router-Alert option in their IPv6 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 MLD messages without the Router-Alert option.

You can also configure the switch modules to send MLD messages with or without the Router-Alert option. By default, the switch modules sends MLD 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 MLD messages without the Router-Alert option

NOTE:

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

  • The configuration in the MLD view is globally valid, whereas the configuration in the interface view takes effect only for the specified interface.
  • If the Router-Alert option is configured in the interface view and the MLD view, the configuration in the interface view takes effect. If the Router-Alert option is not configured on an interface, the interface uses the configuration in the MLD view.
  • If the non-default configuration is performed in the MLD 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:

      mld

      The MLD view is displayed.

    3. Run:

      require-router-alert

      The device is configured to check for the Router-Alert option in MLD messages and discard MLD messages without the Router-Alert option.

    4. Run:

      undo send-router-alert disable

      The switch modules is configured to send MLD messages with 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:

      mld require-router-alert

      The interface is configured to check for the Router-Alert option in MLD messages and discard MLD messages without the Router-Alert option.

    5. Run:

      undo mld send-router-alert disable

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

    6. Run:

      commit

      The configuration is committed.

Setting MLD Querier Parameters

Context

MLD Query and Report messages are used to maintain membership. When multiple IPv6 multicast devices exist on a network segment, the MLD querier sends MLD Query messages. The MLD querier uses multiple parameters whose default values can support proper working of the MLD querier. You can modify the querier parameters to enable the querier to update multicast membership in a timely manner and prevent network congestion.

Table 8-29 lists the description and default setting of MLD querier parameters.

Table 8-29 Description and Default setting of MLD querier parameters

Parameter

Description

Default Setting

Interval for sending MLD General Query messages

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

125s

Robustness variable of the MLD querier

The robustness variable of the MLD querier specifies the retransmission count of MLD 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 MLD General Query messages

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

10s

Other querier present timer

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.

If the default values of the robustness variable, interval for sending MLD General Query messages, and maximum response time are used, the other querier present timer value is 255 seconds.

Interval for sending Multicast Address Specific Query messages or Multicast Address 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:

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

  • The configuration in the MLD view is globally valid, whereas the configuration in the interface view takes effect only for the specified interface.
  • If a querier parameter is configured in the interface view and the MLD view, the configuration in the interface view takes effect. If a querier parameter is not configured on an interface, the interface uses the configuration in the MLD view.
  • If non-default configuration is performed in the MLD view, the default configuration in the interface view does not take effect.

Procedure

  • Configuring global MLD querier parameters
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      mld

      The MLD view is displayed.

    3. Run:

      timer query interval

      The interval for sending MLD General Query messages is set on the device.

    4. Run:

      robust-count robust-value

      The robustness variable of the MLD querier is set.

    5. Run:

      max-response-time interval

      The maximum response time for MLD General Query messages is set.

    6. Run:

      timer other-querier-present interval

      The other querier present timer is configured.

    7. Run:

      lastlistener-queryinterval interval

      The interval for sending Multicast Address Specific Query messages or Multicast Address and Source Specific Query messages is set.

    8. Run:

      commit

      The configuration is committed.

    NOTE:

    During MLD querier configuration, ensure that the interval for sending General Query messages is larger than the maximum response time for MLD Query messages and is smaller than the other querier present timer.

  • Configuring MLD 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:

      mld timer query interval

      The interval for sending MLD General Query messages is set on the interface.

    5. Run:

      mld robust-count robust-value

      The robustness variable of the MLD querier is set.

    6. Run:

      mld max-response-time interval

      The maximum response time for MLD General Query messages is set.

    7. Run:

      mld timer other-querier-present interval

      The other querier present timer is configured.

    8. Run:

      mld lastlistener-queryinterval interval

      The interval for sending Multicast Address Specific Query messages or Multicast Address and Source Specific Query messages is set.

    9. Run:

      commit

      The configuration is committed.

Configuring MLD Fast Leave

Context

In some scenarios, a MLD 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 Multicast Listener Done messages sent from the host.

After fast leave is configured, the querier does not send a Multicast Address Specific Query message or Multicast Address and Source Specific Query message after receiving a Multicast Listener Done message. 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 Done messages and saves network bandwidth.

NOTE:

To limit the range of multicast groups that member hosts can leave fast, configure an ACL6 to define the range of multicast groups and then reference this ACL6. For details about the ACL6 configuration, 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:

    mld prompt-leave [ group-policy { acl6-number | acl6-name acl6-name } ]

    Fast leave is configured on the interface.

    By default, the switch modules sends Multicast Address Specific Query messages or Multicast Address and Source Specific Query messages after receiving a Done message.

    NOTE:

    When configuring an ACL6 rule for an interface, use the permit parameter to allow the hosts connected to the interface to quickly leave multicast groups with addresses in a specified range. If no rule is configured in the ACL6, hosts connected to the interface cannot quickly leave any multicast groups.

  5. Run:

    commit

    The configuration is committed.

Configuring MLD On-Demand

Context

In a standard MLD working process, a querier periodically sends Query messages and receives Multicast Listener Report and Done messages from the receiver hosts to learn information about multicast members.If group members on a network seldom change, you can configure MLD on-demand on the querier. After MLD on-demand is configured on the querier, the querier does not send Query messages, reducing MLD packets exchanged between the querier and receiver hosts. The querier maintains multicast membership according to requirements of receiver hosts without actively sending Query messages.

After MLD on-demand is configured, the switch modules:

  • Does not send MLD Query messages through the interface.
  • Generate MLD group entries that will never age out after receiving Multicast Listener Report messages.
  • Delete MLD group entries immediately when receiving Multicast Listener Done 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:

    mld on-demand

    MLD on-demand is enabled on the interface. The interface then does not send MLD Query messages and MLD group entries on the interface are never aged.

    By default, a querier does not maintain group memberships according to requirements of group members, and dynamic entries are aged out when the aging time expires.

    NOTE:

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

  5. Run:

    commit

    The configuration is committed.

Filtering MLD Messages Based on Source IPv6 Addresses

Context

MLD runs between member hosts and the Layer 3 multicast device that is directly connected to the host network segment. A multicast device processes all received Report messages. To improve security and prevent multicast services from being affected by MLD messages maliciously forged by other devices, you can configure the switch modules to filter MLD messages received on an interface. Messages that can be filtered include MLD Query messages, MLD Report and Done messages.

NOTE:

Before configuring MLD mesages filtering based on source IPv6 addresses, configure an ACL6 to define the range of source IPv6 addresses for packet filtering. For details about the ACL6 configuration, 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:

    mld query ip-source-policy { basic-acl6-number | acl6-name acl6-name }

    A policy is configured to filter MLD Query messages.

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

    NOTE:

    When configuring an ACL6 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 ACL6, the interface discards Query messages from all source addresses.

  5. Run:

    mld ip-source-policy { basic-acl6-number | acl6-name acl6-name }

    A policy is configured to filter Report/Done messages.

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

    NOTE:

    When configuring an ACL6 rule for the interface, use the permit parameter to configure the interface to accept only Report and Done messages with source addresses in a specified range. If no rule is configured in the ACL6, the interface discards Report and Done messages from all source addresses.

  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, MLD configuration, and MLD running status.

Procedure

  • Run the display mld interface [ interface-type interface-number | up | down ] [ verbose ] command to check the MLD information on an interface.
  • Run the display mld group [ ipv6-group-address | interface interface-type interface-number ]* [ verbose ] command to check information about MLD groups that hosts have dynamically joined by sending Multicast Listener Report messages.

Configuring MLD SSM Mapping

To allow an IPv6 host running MLDv1 to use SSM, you can configure MLD SSM mapping on the switch modules to provide the SSM service for MLDv1 receiver hosts.

Pre-configuration Tasks

Enabling MLD

Context

The SSM model allows MLDv2 hosts to specify the multicast sources from which they want to receive data. However, some hosts can only run MLDv1. To allow these hosts to use SSM, configure MLD SSM mapping on the switch modules. MLD SSM mapping is implemented based on static SSM mapping entries on the switch modules. The switch modules converts (*, G) information in MLDv1 Multicast Listener Report messages to (S, G) information according to static SSM mapping entries to provide the SSM service for MLDv1 hosts. By default, the range of IPv6 SSM group addresses is FF3x::/32, in which x cannot be 1 or 2. You can expand the range of IPv6 SSM group addresses. For the configuration, 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:

    mld ssm-mapping enable

    SSM mapping is enabled on the interface.

    To ensure that hosts running any MLD version on a network segment can obtain SSM services, it is recommended that you enable MLDv2 on switch modules interfaces.

  5. Run:

    quit

    Return to the system view.

  6. Run:

    mld

    The MLD view is displayed.

  7. Run:

    ssm-mapping ipv6-group-address ipv6-group-mask-length ipv6-source-address

    One or more multicast group addresses are mapped to a multicast source address.

  8. Run:

    commit

    The configuration is committed.

Checking the Configuration

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

  • Run the display mld interface [ interface-type interface-number | up | down ] [ verbose ] command to check the MLD information on an interface.
  • Run the display mld group [ ipv6-group-address | interface interface-type interface-number ]* ssm-mapping [ verbose ] command to check information about multicast group entries established with MLD SSM mapping.
  • Run the display mld ssm-mapping { group [ ipv6-group-address ] | interface [ interface-type interface-number ] } command to check the configuration of MLD SSM mapping.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59397

Downloads: 3623

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