8.5. Configuring Triple Play Multicast Services with CLI
This section provides information to configure multicast parameters in a Triple Play network using the command line interface.
8.5.1. Configuring IGMP Snooping in the BSA
8.5.1.1. Enabling IGMP Snooping in a VPLS Service
8.5.1.2. IGMPv3 Multicast Routers
When multicast routers use IGMPv3, it is sufficient to just enable IGMP snooping, without any further modification of parameters.
The following displays an example of an IGMP snooping configuration:
8.5.1.3. With IGMPv1/2 Multicast Routers
When the multicast routers don't support IGMPv3, some timing parameters need to be configured locally in the SR-series routers.
 | Note: All routers in the multicast network must use the same values for these parameters. |
The following displays an example of a modified IGMP snooping configuration:
8.5.1.4. Modifying IGMP Snooping Parameters
For interoperability with some multicast routers, the source IP address of IGMP group reports can be configured. Use the following CLI syntax to customize this IGMP snooping parameter:
The following displays an example of a modified IGMP snooping configuration:
8.5.1.5. Modifying IGMP Snooping Parameters for a SAP or SDP
Use the following CLI syntax to customize IGMP snooping parameters on an existing SAP. Commands for spoke or mesh SDPs are identical.
To enable and customize sending of IGMP queries to the hosts:
To customize the leave delay:
To enable Fast Leave:
To limit the number of streams that a host can join:
To enable sending group reports on a SAP to standby multicast routers:
The following example displays the modified IGMP snooping configuration on a SAP:
8.5.2. Configuring Static Multicast Groups on a SAP or SDP
Use the following CLI syntax to add static group membership entries on an existing SAP (commands for spoke or mesh SDPs are identical):
The following displays an example of a static IGMP snooping configuration on a SAP:
8.5.2.1. Enabling IGMP Group Membership Report Filtering
Routing policies can be defined to limit the multicast channels that can be joined by a host. For example, it is possible to define a policy listing a group of multicast streams (for example, 'basic' containing a basic set of TV channels or 'extended' containing a more extended set of TV channels), and to apply this policy to subscribers of IGMP snooping (SAPs and/or SDPs).
The following displays an example of a configuration to import a routing policy on a SAP:
For details configuring a routing policy, see the Configuring Route Policies section in the Router Configuration Guide.
The following shows a sample routing policy configuration accepting IGMP messages for only five multicast channels:
8.5.2.1.1. Enabling IGMP Traffic Filtering
For security, it might be advisable to only allow multicast traffic into the SR-series routers from recognized multicast routers and servers. Multicast packets arriving on other interfaces (for example, customer-facing SAPs or spoke SDPs) can be filtered out by defining an appropriate IP filter policy.
For details on how to configure a filter policy, see section Creating an IP Filter Policy in the Router Configuration Guide.
The following example shows a sample IP filter policy configuration dropping all multicast traffic:
The following example shows how to apply this sample IP filter policy to a SAP:
8.5.3. Configuring Multicast VPLS Registration (MVR)
Use the following CLI syntax to configure Multicast VPLS Registration. The first step is to register a VPLS as a multicast VPLS.
The second step is to configure a SAP to take the multicast channels from the registered multicast VPLS.
For MVR by proxy also the destination SAP for the multicast channels should be configured.
8.5.4. Configuring IGMP, MKD, and PIM in the BSR
| Note: Configuring IGMP, MKD, and PIM in the BSR is supported by the 7750 SR only. |
Refer to the Multicast Routing Protocols Guide for information about multicast and the commands required to configure basic IGMP and PIM parameters.
8.5.4.1. Enabling IGMP
The following displays an example of enabled IGMP.
8.5.4.2. Configuring IGMP Interface Parameters
The following example displays an IGMP configuration:
8.5.4.3. Configuring Static Parameters
The following example displays a configuration to add IGMP a static multicast source::
:The following example displays the configuration to add a IGMP static starg entry:
8.5.4.4. Configuring SSM Translation
The following displays an SSM translation configuration:
8.5.4.5. Enabling MLD
The following displays an example of enabled MLD.
8.5.4.6. Configuring MLD Interface Parameters
The following example displays an MLD configuration:
8.5.4.7. Configuring Static Parameters
The following example displays a configuration to add MLD a static multicast source:
The following example displays the configuration to add a MLD static starg entry:
8.5.4.8. Configuring SSM Translation
The following displays an SSM translation configuration:
8.5.4.9. Configuring PIM
8.5.4.9.1. 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 detailed output when PIM is enabled.
8.5.4.9.2. Configuring PIM Interface Parameters
The following displays a PIM interface configuration:
8.5.4.9.3. Importing PIM Join/Register Policies
The import command provides a mechanism to control the (*,g) and (s,g) state that gets created on a router. Import policies are defined in the config>router>policy-options context. See Configuring PIM Join/Register Policies.
| Note: In the import policy, if an action is not specified in the entry then the default-action takes precedence. If no entry matches then the default-action also takes precedence. If no default-action is specified, then the default default-action is executed. |
The following example displays the command usage to apply the policy statement will not allow join messages for group 229.50.50.208/32 and source 192.168.0.0/16 but allows join messages for 192.168.0.0/16, 229.50.50.208:
The following example displays the PIM configuration:
8.5.4.9.4. Configuring PIM Join/Register Policies
Join policies are used in Protocol Independent Multicast (PIM) configurations to prevent the transportation of multicast traffic across a network and the dropping of packets at a scope at the edge of the network. PIM Join filters reduce the potential for denial of service (DoS) attacks and PIM state explosion—large numbers of Joins forwarded to each router on the RPT, resulting in memory consumption.
*,g or s,g is the information used to forward unicast or multicast packets.
- group-address matches the group in join/prune messagesgroup-address 229.55.150.208/32 exact
- source-address matches the source in join/prune messagessource-address 192.168.0.0/16 longer
- interface matches any join message received on the specified interfaceinterface port 1/1/1
- neighbor matches any join message received from the specified neighborneighbor 1.1.1.1
The following configuration example will not allow join messages for group 229.50.50.208/32 and source 192.168.0.0/16 but allows join messages for 192.168.0.0/16, 229.50.50.208.
8.5.4.10. Configuring Bootstrap Message Import and Export Policies
Bootstrap import and export policies are used to control the flow of bootstrap messages to and from the RP.
The following configuration example specifies that no BSR messages received or sent out of interface port 1/1/1.