Multicast Config
Multicast Config
Multicast Config
Traffic can only flow away from the router to an IGMP or MLD interface; it can flow both to
and from a PIM interface. A router directly connected to a source of multicast traffic must
have PIM enabled on the interface to that source. The traffic travels through a network from
PIM interface to PIM interface, and arrives on an IGMP- or MLD-enabled interface.
You can filter traffic on an IGMP or MLD interface by defining and importing a routing
policy. You can also define the maximum number of groups to which the interface can
belong.
Note: Before an IP interface can be specified in an IGMP or MLD context, it must be created
on the 7705 SAR (config>router>interface or config>service>ies>
interface).
Static Groups
Static IGMP and MLD group memberships can be configured so that multicast forwarding
can be set up without any host receivers in the group. When static IGMP or MLD group
membership is enabled, data is forwarded to an interface even though membership reports
from one or more host members have not been received.
When static IGMP or MLD group entries on point-to-point links that connect routers to a
rendezvous point (RP) are configured, the static IGMP or MLD group entries do not generate
Join messages toward the RP. When a host wants to receive multicast sessions, it sends a Join
message to each multicast group it wants to join. When a host wants to leave a multicast
session, it sends a Leave message to each multicast group it wants to leave.
A multicast router keeps a list of multicast group memberships for each attached network and
an interval timer for each membership. Host receivers issue a Multicast Group Membership
Report when they want to receive a multicast session. In MLDv2, Leaves and Joins are both
sub-messages of Report messages. These reports are sent to all multicast routers.
SSM Translation
The 7705 SAR supports SSM translation at both the protocol level and the interface level for
both IGMP and MLD. When configured at the protocol level, the specified group and source
addresses apply to all newly created IGMP and MLD interfaces. Configuring ssm-
translation at the interface level overrides any protocol-level values for the specified
interface.
PIM
Use the config>router>pim command to create the PIM CLI context. The PIM protocol
is not operational until at least one interface is specified for it, at which time the interface is
enabled for PIM and is called a PIM interface. Once enabled, a PIM interface can be
configured with PIM parameters, which are in addition to the standard parameters for the
interface when it is created. When PIM is operational, data is forwarded to network segments
with active host receivers that have explicitly requested the multicast group.
Note:
• Before an IP interface can be specified in the PIM context, it must be created on the
7705 SAR (config>router>interface or config>service>ies>interface).
• PIM interfaces can be automatically created once an IP or IES interface has been
created by using the apply-to command.
Hardware Support
IGMP and MLD are supported on the following:
• all Ethernet adapter cards except for the 8-port Ethernet Adapter card, version 1
• the following module ports when the module is installed in the 7705 SAR-M: GPON,
DSL, and the 2-port 10GigE (Ethernet) module
• all datapath Ethernet ports on all fixed 7705 SAR platforms
• all Ethernet adapter cards except for the 8-port Ethernet Adapter card, version 1
• the following module ports when the module is installed in the 7705 SAR-M: GPON,
DSL, and the 2-port 10GigE (Ethernet) module
• all T1/E1 adapter cards
• all OC3/STM1 adapter cards
• the 4-port DS3/E3 Adapter card
• all datapath Ethernet ports on all fixed 7705 SAR platforms
For IGMP:
For MLD:
For PIM:
The following examples show information displays for IGMP, MLD, and PIM, with each
protocol showing the following output:
IGMP
MLD
*A:7705custDoc:Sar18>config>router>mld# info
----------------------------------------------
interface "mld_interface"
exit
----------------------------------------------
*A:7705custDoc:Sar18>config>router>mld#
PIM
*A:7705custDoc:Sar18>config>router>pim# info
----------------------------------------------
interface "pim_interface"
exit
rp
exit
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim#
The following displays an enabled IGMP example. An MLD display would look similar.
The following displays an IGMP configuration example. An MLD example would look
similar.
IGMP and MLD are supported on both access and network interfaces.
Note: MLD “query” parameters can be configured at both the MLD protocol and interface
levels. When configured at the protocol level, settings apply to all new interfaces added to
the context. Configuring the “query” parameters at the interface level overrides the protocol-
level configuration for the specified interface.
See Configuring IGMP and MLD for an example of query parameter configuration.
The following example displays IGMP interface configuration command usage. An MLD
interface example would look similar.
Example: config>router#
config>router>igmp# interface "igmp_interface"
config>router>igmp>if# max-groups 3
config>router>igmp>if# import igmp_policy1
config>router>igmp>if# exit
Use the following syntax to configure an IGMP or MLD static multicast group and source for
a multicast interface:
The following example displays an IGMP interface configuration for static multicast. An
MLD interface example would look similar except that it would use IPv6 group and source
addresses.
config>router>igmp>if>static>group# source
172.22.184.197
config>router>igmp>if>static>group# source
172.22.184.198
config>router>igmp>if>static>group# exit
config>router>igmp>if>static# exit
config>router>igmp>if# exit
The following example displays the configuration for IGMP. An MLD example would look
similar except that it would use IPv6 group and source addresses.
A:7705custDoc:Sar18>config>router>igmp# info
----------------------------------------------
interface "igmp_interface"
static
group 229.255.0.2
source 172.22.184.197
source 172.22.184.198
exit
group 229.255.0.3
source 172.22.184.197
source 172.22.184.198
exit
exit
exit
----------------------------------------------
A:7705custDoc:Sar18>config>router>igmp#
SSM translation can be configured for IGMP and MLD at the protocol and the interface
levels. When configured at the protocol level, settings apply to all new interfaces added to the
context. Configuring SSM translation at the interface level overrides the protocol-level
configuration for the specified interface.
The following example displays the command usage to configure IGMP SSM translation.
Examples for the MLD protocol, as well as for IGMP and MLD interfaces, would look
similar. MLD would use IPv6 group and source addresses.
The following example displays the SSM translation configuration at the IGMP level:
A:7705custDoc:Sar18>config>router>igmp# info
----------------------------------------------
ssm-translate
grp-range 229.255.0.1 231.2.2.2
source 10.10.10.100
exit
----------------------------------------------
A:7705custDoc:Sar18>config>router>igmp# exit.
• Enabling PIM
• Configuring PIM Interface Parameters
• Importing PIM Join Policies
Enabling PIM
When configuring PIM, make sure to enable PIM on all interfaces for the routing instance;
otherwise, multicast routing errors can occur.
The following example displays the detailed output when PIM is enabled without a PIM
interface configured. See Configuring PIM Interface Parameters for the additional
configuration settings when a PIM interface is configured.
The following example displays the command usage to configure PIM interface parameters:
The import command provides a mechanism to control the (S,G) state that gets created on
a router. Import policies are defined in the config>router>policy-options context.
Note: In the import policy, if a policy action is not specified in the entry, then the
default-action takes precedence. Similarly, if there are no entry matches, then the
default-action takes precedence. If no default-action is specified, then the default
default-action is executed.
The following example displays the commands used to apply a policy statement named
“pim_join”. To define a join policy and to see details of the “pim_join” policy statement, see
the “Configuring PIM Join Policies” section in the 7705 SAR OS Router Configuration
Guide”:
A:7705custDoc:Sar18>config>router>pim# info
----------------------------------------------
...
import join-policy "pim_join"
interface "pim_interface"
exit
...
----------------------------------------------
A:7705custDoc:Sar18>config>router>pim#
Use the following CLI syntax to disable IGMP, MLD, and PIM:
no bootstrap-export
exit
no non-dr-attract-traffic
no ipv4-multicast-disable
ipv6-multicast-disable
----------------------------------------------
*A:7705custDoc:Sar18>config>router>pim#