This section provides information to configure IP multicast, IGMP, MLD, and PIM.
Topics in this section include:
Nokia 7705 SAR routers use IGMP and MLD to manage membership of host receivers for a given multicast session. The routers use PIM-SSM or PIM-SM to connect to the multicast source and to the network.
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.
The IGMP and MLD CLI contexts are created when the config>router>igmp and config>router>mld commands are run. They are not operational until at least one interface is specified in the context, at which time the interface is enabled for IGMP or MLD and is called an IGMP or MLD interface. When enabled, the interface can be configured with IGMP or MLD parameters, which are in addition to the standard parameters for the interface when it is created.
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 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.
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.
Use the config>router>pim command to enable 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:
|
IGMP and MLD are supported on the following:
PIM-SSM and PIM-SM are supported on the following:
Perform the following basic multicast configuration tasks:
Note: Interfaces are created using the config>router>interface or config>service>ies>interface command (IES only), and then enabled and configured for IGMP, MLD, or PIM using the config>router>igmp>interface or mld>interface or pim>interface command. |
For IGMP:
For MLD:
For PIM:
For MSDP:
The following examples show information displays for IGMP, MLD, PIM, and MSDP. For IGMP, MLD, and PIM, each protocol shows the following output:
IGMP
MLD
PIM
MSDP
The following sections show the CLI syntax and examples for:
This section contains the following subsections:
Use the following CLI syntax to enable IGMP or MLD.
The following displays an enabled IGMP example. An MLD display would look similar.
Use the following CLI syntax to configure IGMP and MLD:
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. |
Use the following CLI syntax to configure an IGMP or MLD interface:
The following example displays IGMP interface configuration command usage. An MLD interface example would look similar.
The following example displays the IGMP interface configuration:
The maximum number of static groups and sources that can be configured on a group interface is controlled by the max-groups and max-grp-sources commands. A static (*,G) cannot be added to a group if an (S,G) exists. Similarly, a static (S,G) cannot be added to a group if a (*,G) exists.
A static group is not created until a source has been specified.
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.
The following example displays the configuration for IGMP. An MLD example would look similar except that it would use IPv6 group and source addresses.
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 group range is not created until a source has been specified.
Use the following syntax to configure IGMP and MLD SSM translation parameters at the protocol and interface levels:
The following example displays the command usage to configure IGMP SSM translation at the protocol and interface levels. Examples for MLD protocol 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 protocol and interface levels:
This section contains the following subsections:
When configuring PIM, make sure to enable PIM on all interfaces for the routing instance; otherwise, multicast routing errors can occur.
Use the following CLI syntax to enable PIM.
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.
Without a PIM interface enabled
With a PIM interface enabled
To create a PIM interface, first create an IP interface using the config>router> interface or the config>service>ies>interface command (IES only). Then use the config>router>pim>interface command to configure PIM interface parameters.
The following example displays the command usage to configure PIM interface parameters:
The following example displays the detailed PIM interface configuration:
When configuring a Rendezvous Point (RP), you can configure parameters for an RP candidate, a BSR candidate, or a static RP.
The following example displays the command usage to configure an RP:
The following example displays the detailed RP configuration:
The import command provides a mechanism to control the (*,G) or (S,G) state that gets created on a router. Import policies are defined in the config>router>policy-options context.
Up to five join policies can be included in a single join-policy command and up to five register policies can be included in a single register-policy command. Each use of the join-policy or register-policy command overrides the previous use and resets the list of import policies.
Note: In the import policy, if a policy action is not specified in the entry, the default-action takes precedence. Similarly, if there are no entry matches, the default-action takes precedence. If no default-action is specified, the default default-action is executed. |
Use the following commands to import PIM join policies:
The following example displays the commands used to import a join policy statement named “pim_join”. The example also displays the commands used to import three register policies. For information on configuring a join or register policy, see the “Configuring PIM Join or Register Policies” section in the 7705 SAR Router Configuration Guide.
The following example displays the PIM configuration:
Use the following CLI syntax to configure MSDP parameters:
The following example displays the command usage to configure basic MSDP parameters.
The following example displays the basic MSDP for configuration.
This section discusses the following multicast configuration management tasks:
To disable IP multicast, disable PIM and disable IGMP or MLD (or both).
Use the following CLI syntax to disable IGMP, MLD, PIM, and MSDP:
The following example displays the command usage to disable multicast:
The following example displays the configuration outputs: