Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) Line Card Configuration Guide - Configuring Multicast Features [Cisco 7600 Series Routers]

Table Of Contents

Configuring Multicast Features

IGMP/PIM Snooping for VPLS Pseudowire on Cisco 7600 Series Ethernet Services Plus Line Cards

Restrictions and Usage Guidelines

Example

Verification

IP and PPPoE Session Coexistence with Multicast

Restrictions and Usage Guidelines

Configuring IP and PPPoE Session Coexistence with Multicast

Configuring a PQ2 Policer Under the Main Interface

Verification

Configuring Multicast Features

This chapter provides information about configuring multicast features on the Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) line card on the Cisco 7600 series router. It includes the following topics:

•IGMP/PIM Snooping for VPLS Pseudowire on Cisco 7600 Series Ethernet Services Plus Line Cards

•IP and PPPoE Session Coexistence with Multicast

For more information about the commands used in this chapter, see the Cisco IOS Release 12.2 SR Command References at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sr/cr/index.htm.

Note The information provided in this chapter is applicable to both the ES+ and ES+T line cards unless specified otherwise.

IGMP/PIM Snooping for VPLS Pseudowire on Cisco 7600 Series Ethernet Services Plus Line Cards

The Internet Group Management Protocol (IGMP)/Protocol Independent Multicast (PIM) Snooping for VPLS Pseudowire on Cisco 7600 Series ES+ line cards provides the ability to send Layer 2 multicast frames from customer equipment (CE) in a VPLS virtual forwarding instance (VFI) or from a multipoint bridging VLAN only to those remote peer CEs that have sent an IGMP request to join the multicast group.

IGMP/PIM Snooping for VPLS Pseudowire on Cisco 7600 Series ES+ line cards manages multicast traffic at Layer 2 by configuring Layer 2 LAN ports dynamically to forward multicast traffic only to those ports that want to receive it. In VPLS or multipoint bridging, IGMP snooping can be set up on per VLAN or VFI basis to build the membership tree because each of the remote legs of a VLAN or VFI can be identified with a virtual port and VLAN ID.

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/PIM snooping is enabled by default under the bridge-domain VLAN (use the no ip igmp snooping command to disable 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 only works when there is no tunneling operation (there should not be any VLAN tags in the packet when it is put on the bridge-domain VLAN).

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
Command

Purpose
Step 1
enable
Example:
Router# enable
Enables privileged EXEC mode.

•Enter your password if prompted.
Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface vlan vlanid
Example:

Router(config)# interface vlan 12

Creates a unique VLAN ID number and enters subinterface configuration mode.
Step 4
no ip address ip-address mask [secondary]
Example:
Router(config)# no ip address
Disables IP processing and enters interface configuration mode.
Step 5
ip igmp snooping
Example:
Router(config-if)# ip igmp snooping
Enables IGMP snooping. To disable IGMP snooping, use the no form of this command.
Step 6
ipv6 mld snooping 
Example:
Router(config)# ipv6 mld snooping 
Enables Multicast Listener Discovery version 2 (MLDv2) snooping globally. To disable the MLDv2 snooping globally, use the no form of this command.
Step 7
xconnect vfi vfi name
Example:
Router(config-if)# xconnect vfi vfi16
Specifies the Layer 2 VFI that you are binding to the VLAN port.
Example

This is a VLAN configuration.
Router# enable
Router# configure terminal
Router(config)# interface Vlan700
Router(config)# no ip address
Router(config-if)# ip igmp snooping
Router(config-if)# ipv6 mld snooping
Router(config-if)# xconnect vfi vfi700
Verification

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

IP and PPPoE Session Coexistence with Multicast

The IP and PPPoE Session Coexistence with Multicast feature allows you to converge IP subscribers and multicast users on the same VLAN. IP subscriber sessions are supported on non-access type subinterfaces through which multicast control and data traffic can pass through whether the IP session is absent or present.

The IP and PPPoE Session Coexistence with Multicast feature does not support IP Interface session and PPP session types. When multicast traffic is received by interfaces hosting IP Interface or PPP sessions, the multicast traffic will be treated as part of the session traffic.

•Multicast traffic streams towards the access node (downstream direction) co-exist on the interface that is configured for Sessions (IP or PPPoEoX).

–This is not for per session multicast but allows multicast stream to co-exist on the interfaces on which hosts sessions exist.

–The multicast stream is targeted for an Access-Node (DSLAM/switch) that handles per subscriber replication.

Additionally, QoS priority queueing-2 and policing for multicast traffic is supported.

•From QoS treatment perspective:

–Multicast traffic shaping is not required at subinterface (Dot1Q/QinQ) level.

–Multicast traffic need to be considered as PQ2 traffic (at port level) on the egress side.

•Multicast traffic co-existence is required only for Ethernet main and subinterfaces.

•Support for IP Multicast co-existence on ISG aware sub-interfaces is HA/SSO capable.

Restrictions and Usage Guidelines

When configuring QoS with the IP and PPPoE Session Coexistence with Multicast, follow these restrictions and guidelines:

•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, all multicast traffic will be dropped.

•The IP and PPPoE Session Coexistence with Multicast feature is not supported on sub-interfaces created with access keyword option.

Configuring IP and PPPoE Session Coexistence with Multicast

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. no ip pim {sparse-mode | sparse-dense-mode | dense-mode [proxy-register {list access-list | route-map map-name}]}

7. ip subscriber routed

8. initiator {dhcp [class-aware] | radius-proxy | unclassified ip-address}

9. end

DETAILED STEPS
Command

Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.

•Enter your password if prompted.
Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface gigabitethernet slot/port
Example:

Router(config)# interface gigabitethernet 4/1

Specifies the Gigabit Ethernet interface to configure, where:

•slot/port—Specifies the location of the interface.

Creates the port-channel interface.
Step 4
encapsulation dot1q vlan-id {cos | comma| hyphen|etype}
Example:

Router(config-if-srv)# encapsulation dot1q 100?
Defines the matching criteria to map dot1Q ingress frames on an interface to the appropriate service instance.VLAN ID is an integer in the range 1 to 4094. Hyphen must be entered to separate the starting and ending VLAN ID values that are used to define a range of VLAN IDs. Available options are CoS and ethertype.
Step 5

[no] ip address
Example:

Router(config-if)# no ip address

Assigns an IP address and subnet mask to the EtherChannel.
Step 6
no ip pim {sparse-mode | sparse-dense-mode | dense-mode [proxy-register {list access-list | route-map map-name}]}
Example:

Router(config-if)# ip pim sparse-mode
Enables Protocol Independent Multicast (PIM) on an interface.
Step 7
ip subscriber routed
Example:

Router(config-if)# ip subscriber routed
Specifies the type of IP subscriber to be hosted on the interface, and enters ISG IP subscriber configuration mode.
Step 8

initiator {dhcp [class-aware] | radius-proxy | unclassified ip-address}

Example:

Router(config-if)# ip pim sparse-mode

Configures ISG to create an IP subscriber session upon receipt of the specified packet type.

•dhcp—ISG will initiate an IP session upon receipt of a DHCP DISCOVER packet. The class-aware keyword allows ISG to influence the IP address assigned by DHCP by providing DHCP with a class name.

•radius-proxy—ISG will initiate an IP session upon receipt of a RADIUS Access-Request packet.

•unclassified ip-address—ISG will initiate an IP session upon receipt of the first IP packet with an unclassified IP source address.

•This command can be entered more than once to specify more than one method of IP session initiation.

Step 9

end
Example:

Router(config-if)# end

Ends the current configuration session.
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
Command

Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.

•Enter your password if prompted.
Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface gigabitethernet slot/port
Example:

Router(config)# interface gigabitethernet 4/1

Specifies the Gigabit Ethernet interface to configure, where:

•slot/port—Specifies the location of the interface.

Creates the port-channel interface.
Step 4
encapsulation dot1q vlan-id {cos | comma| hyphen|etype}
Example:

Router(config-if-srv)# encapsulation dot1q 100?
Defines the matching criteria to map dot1Q ingress frames on an interface to the appropriate service instance.VLAN ID is an integer in the range 1 to 4094. Hyphen must be entered to separate the starting and ending VLAN ID values that are used to define a range of VLAN IDs. Available options are CoS and ethertype.
Step 5

[no] ip address
Example:

Router(config-if)# no ip address

Assigns an IP address and subnet mask to the EtherChannel.
Step 6
load-interval seconds
Example:

Router(config-if)# load-interval 30
Changes the length of time for which data is used to compute load statistics.
Step 7
platform subscriber-multicast priority-level2 police rate in kbps
Example:

Router(config-if)# platform subscriber-multicast priority-level2 police 200
Defines the percentage of port bandwidth that the multicast traffic will be policed at.
Step 8

end
Example:

Router(config-if)# end

Ends the current configuration session.
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:
interface GigabitEthernet4/13.200
 encapsulation dot1Q 200
 ip address 192.10.10.1 255.255.255.0
 ip pim sparse-mode
 ip subscriber routed
  initiator unclassified ip-address
end
This is an example of how to configure PQ2 policer under main interface:
interface GigabitEthernet4/13
 ip address 33.0.0.1 255.0.0.0
 load-interval 30
 platform subscriber-multicast priority-level2 police 200
end
Verification

Use the following commands to verify operation.

Table 5-1 Commands for Displaying Traffic Storm Control Status and Configuration

Command

Purpose

Router# show ip igmp groups

Displays the multicast groups with receivers that are directly connected to the router and that were learned through Internet Group Management Protocol (IGMP).