Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) Line Card Configuration Guide

Restrictions and Usage Guidelines

When configuring the IGMP/PIM Snooping for VPLS Pseudowire on Cisco 7600 Series ES+ line cards, follow these restrictions and usage guidelines:

• IGMP snooping is enabled by default under the bridge-domain VLAN (use the no ip igmp snooping command to disable the default behavior).
• Globally enabling IGMP snooping enables IGMP snooping on all the existing VLAN interfaces. Globally disabling IGMP snooping disables IGMP snooping on all the existing VLAN interfaces.
• System support for 32,000 IGMP groups with no line card-specific limitation.
• Supports MultiPoint Bridging over Ethernet on Cisco 7600 Series ES+ line cards.
• Supports Virtual Private LAN Service (VPLS).
• Use the show ip igmp snooping privileged EXEC command to verify your IGMP settings.
• IGMP snooping works only when no tunneling operation occurs (there should not be any VLAN tags in the packet when it is put on the bridge-domain VLAN).
• During snooping, all traffic for a particular group are dropped if there are no interested receivers for that group.
• MROUTER port information should be available to all devices in the snooping domain. You can find out the MROUTER ports by:

– Using the IP address and PIM on SVI.

– Using the IGMP query messages heard on the segment.

– Forcefully configuring a particular port on a switch as mrouter port using the ip igmp snooping mrouter interface command.

• By default, IGMP snooping is on.
• All routers acting as PE devices in a VPLS domain should have the IP address and PIM enabled on the VPLS SVI.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface vlan vlanid

4. no ip address ip-address mask [secondary]

5. ip igmp snooping

6. ipv6 mld snooping

7. xconnect vfi vfi name

DETAILED STEPS

Example

This is a VLAN configuration.

Verification

Use the show ip igmp interface vlan command to verify a configuration.

Restrictions and Usage Guidelines

Follow these restrictions and usage guidelines when configuring QoS with the IP and PPPoE Session Coexistence with Multicast:

• All multicast traffic on a non-access subscriber interface will be treated as priority level2 packets.
• Use the platform subscriber-multicast priority-level2 police command to configure the percentage rate of port bandwidth that the multicast traffic will be policed at.
• The percentage rate configured will be applicable on a per port basis.
• When configured, all multicast traffic on non-access subscriber interface will be treated as priority level 2 and policed at the configured percent of the individual ports bandwidth.
• When not configured, multicast traffic is not treated as priority level2 traffic.
• The IP and PPPoE Session Coexistence with Multicast feature is not supported on sub-interfaces created with access keyword option.
• Maximum number of IP and PPPoE subscriber sessions suported per port group is 4000.
• Maximum number of IP and PPPoE subscriber sessions supported per line card is 16000.

Configuring IP and PPPoE Session Coexistence with Multicast

Summary Steps

1. enable

2. configure terminal

3. ip multicast-routing [vrf vrf-name] [distributed]

4. ip pim rp-address ip-address [group-access-list-number] [override]

5. interface gigabitethernet slot/port or interface tengigabitethernet slot/port

6. encapsulation dot1q vlan-id

7. [no] ip address

8. [no] ip pim {sparse-mode | sparse-dense-mode | dense-mode [proxy-register {list access-list | route-map map-name}]}

9. ip subscriber routed

10. initiator {dhcp [class-aware] | static | nclassified ip-address}

11. end

DETAILED STEPS

Configuring a PQ2 Policer Under the Main Interface

Summary Steps

1. enable

2. configure terminal

3. interface gigabitethernet slot/port or interface tengigabitethernet slot/port

4. encapsulation dot1q vlan-id

5. [no] ip address

6. load-interval seconds

7. platform subscriber-multicast priority-level2 police rate_in_kbps

8. end

DETAILED STEPS

Note This command is applicable to multicast traffic being sent on the main or subinterfaces that are configured with ip subscriber command or pppoe enable command. Multicast traffic on other interfaces on the same port are not impacted by this command. In case of port-channel interfaces, the command should be configured on the member interfaces of the port-channel.

Examples

This is an example of how to configure a nonaccess subinterface for multicast and ISG sessions:

This is an example of how to configure PQ2 policer under main interface:

Verification

Use the following commands to verify operation.

Using MVR in a Multicast Television Application

In a multicast television application, a PC or a television with a set-top box receives the multicast stream. Multiple set-top boxes or PCs can be connected to one subscriber port, which is a switch port configured as an MVR receiver port. Figure 5-1 illustrates this configuration.

The MVR feature in a multicast television application functions in this sequence:

• DHCP assigns an IP address to the set-top box or the PC. When a subscriber selects a channel, the set-top box or PC sends an IGMP report to Switch A to join the appropriate multicast. If the IGMP report matches one of the configured IP multicast group addresses, the Source Port (SP) CPU modifies the hardware address table to include this receiver port and VLAN as a forwarding destination of the specified multicast stream when it is received from the multicast VLAN. Uplink ports that send and receive multicast data to and from the multicast VLAN are called MVR source ports.

Figure 5-1 Multicast VLAN Registration

• When a subscriber changes channels or switches off the television, the set-top box sends an IGMP leave message to the multicast stream. The SP CPU sends a MAC-based general query through the receiver port VLAN. If there is another set-top box in the VLAN still subscribing to this group, that set-top box must respond within the maximum response time specified in the query. If the CPU does not receive a response, it eliminates the receiver port as a forwarding destination for this group.
• Unless the Immediate Leave feature is enabled, when the router receives an IGMP leave message from a subscriber on a receiver port, it sends out an IGMP query on that port and waits for IGMP group membership reports. If no reports are received in a configured time period, the receiver port is removed from multicast group membership. With the Immediate Leave feature enabled, an IGMP query is not sent from the receiver port on which the IGMP leave was received. As soon as the leave message is received, the receiver port is removed from multicast group membership, which speeds up leave latency. Enable the Immediate Leave feature only on receiver ports to which a single receiver device is connected.
• MVR eliminates the need to duplicate television-channel multicast traffic for subscribers in each VLAN. Multicast traffic for all channels is only sent around the VLAN trunk once—only on the multicast VLAN. The IGMP leave and join messages are in the VLAN to which the subscriber port is assigned. These messages dynamically register for streams of multicast traffic in the multicast VLAN on the layer 3 device, Switch B. The access layer switch, Switch A, modifies the forwarding behavior to allow the traffic to be forwarded from the multicast VLAN to the subscriber port in a different VLAN, selectively allowing traffic to cross between two VLANs.
• IGMP reports are sent to the same IP multicast group address as the multicast data. The Switch A CPU must capture all IGMP join and leave messages from receiver ports and forward them to the multicast VLAN of the source (uplink) port.

Configuring MVR

For information on configuring and troubleshooting the MVR, see: http://www.cisco.com/en/US/docs/routers/7600/ios/15S/configuration/guide/snooigmp.html