Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    MLD SSM Mapping Overview

    Source-specific multicast (SSM) mapping enables the router to determine one or more source addresses for group G. The mapping effectively translates a Multicast Listener Discovery version 1 (MLDv1) multicast listener report to an MLDv2 report, enabling the router to continue as if it had initially received an MLDv2 report. After the router is joined to these groups, it sends out Protocol Independent Multicast (PIM) join messages and continues to enable joining from these groups, as long as it continues to receive MLDv1 membership reports and no change occurs to the SSM mapping for the group.

    When you statically configure SSM mapping, the router can discover source addresses from a statically configured table.

    The following applies when you configure SSM mapping:

    • When an SSM map is configured without any matching access list, SSM mapping is not applied on the incoming (*,G) groups. The PIM SSM range must deny any unacceptable SSM group addresses.

      Note: An access list must be explicitly configured with the same name as that of the SSM map and group addresses that are to be SSM mapped.

    • When you issue the no ipv6 mld ssm-map enable command, the router removes all SSM map (S,G) states and establishes a (*,G) state.
    • You can enter multiple ipv6 mld ssm-map static commands for different access lists. Also, you can enter multiple ipv6 mld ssm-map static commands for the same access list, as long as the access list uses different source addresses.
    • SSM maps do not process statically configured groups.

    Published: 2014-08-19