44-18
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-12247-04
Chapter 44 Configuring IP Multicast Routing
Configuring IP Multicast Routing
Configuring Source Specific Multicast Mapping
The Source Specific Multicast (SSM) mapping feature supports SSM transition when supporting SSM
on the end system is impossible or unwanted due to administrative or technical reasons. You can use
SSM mapping to leverage SSM for video delivery to legacy STBs that do not support IGMPv3 or for
applications that do not use the IGMPv3 host stack.
This section covers these topics:
•
Configuration Guidelines, page 44-18
•
SSM Mapping Overview, page 44-18
•
Configuring SSM Mapping, page 44-20
•
Monitoring SSM Mapping, page 44-23
Configuration Guidelines
These are the SSM mapping configuration guidelines:
•
Before you configure SSM mapping, enable IP multicast routing, enable PIM sparse mode, and
configure SSM. For information on enabling IP multicast routing and PIM sparse mode, see the
“Default Multicast Routing Configuration” section on page 44-10
.
•
Before you configure static SSM mapping, you must configure access control lists (ACLs) that
define the group ranges to be mapped to source addresses. For information on configuring an ACL,
see
Chapter 34, “Configuring Network Security with ACLs.”
•
Before you can configure and use SSM mapping with DNS lookups, you must be able to add records
to a running DNS server. If you do not already have a DNS server running, you need to install one.
You can use a product such as Cisco Network Registrar. Go to this URL for more information:
http://www.cisco.com/warp/public/cc/pd/nemnsw/nerr/index.shtml
These are the SSM mapping restrictions:
•
The SSM mapping feature does not have all the benefits of full SSM. Because SSM mapping takes
a group join from a host and identifies this group with an application associated with one or more
sources, it can only support one such application per group. Full SSM applications can still share
the same group as in SSM mapping.
•
Enable IGMPv3 with care on the last hop router when you rely solely on SSM mapping as a
transition solution for full SSM. When you enable both SSM mapping and IGMPv3 and the hosts
already support IGMPv3 (but not SSM), the hosts send IGMPv3 group reports. SSM mapping does
not support these IGMPv3 group reports, and the router does not correctly associate sources with
these reports.
SSM Mapping Overview
In a typical STB deployment, each TV channel uses one separate IP multicast group and has one active
server host sending the TV channel. A single server can send multiple TV channels, but each to a
different group. In this network environment, if a router receives an IGMPv1 or IGMPv2 membership
report for a particular group, the report addresses the well-known TV server for the TV channel
associated with the multicast group.
When SSM mapping is configured, if a router receives an IGMPv1 or IGMPv2 membership report for a
particular group, the router translates this report into one or more channel memberships for the
well-known sources associated with this group.