Default Rgmp Configuration; Rgmp Configuration Guidelines And Restrictions - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Default RGMP Configuration

Table 29-1
Description
Hello
Bye
Join
Leave
Default RGMP Configuration
RGMP is permanently enabled on Layer 2 LAN ports. RGMP is disabled by default on Layer 3
interfaces.

RGMP Configuration Guidelines and Restrictions

When configuring RGMP, follow these guidelines and restrictions:
•
•
•
•
•
•
•
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
29-2
RGMP Packet Types
Action
When RGMP is enabled on the router, no multicast data traffic is sent to the router by
the Catalyst 6500 series switch unless an RGMP join is specifically sent for a group.
When RGMP is disabled on the router, all multicast data traffic is sent to the router
by the Catalyst 6500 series switch.
Multicast data traffic for a multicast MAC address from the Layer 3 group address G
is sent to the router. These packets have group G in the Group Address field of the
RGMP packet.
Multicast data traffic for the group G is not sent to the router. These packets have
group G in the group address field of the RGMP packet.
Either RGMP or PIM snooping can be enabled in a VLAN but not both.
RGMP supports PIM sparse mode. RGMP does not support PIM dense mode. RGMP explicitly
supports the two AutoRP groups in dense mode by not restricting traffic to those groups but by
flooding it to all router ports. For this reason, you should configure PIM sparse-dense mode. If you
configure groups other than the AutoRP groups for dense mode, their traffic will not be correctly
forwarded through router ports that have been enabled for RGMP.
To effectively constrain multicast traffic with RGMP, connect RGMP-enabled routers to separate
ports on RGMP-enabled Catalyst 6500 series switches. (VLAN interfaces satisfy this restriction.)
RGMP only constrains traffic that exits through LAN ports on which it detects an RGMP-enabled
router. If a non-RGMP enabled router is detected on a LAN port, that port receives all multicast
traffic.
RGMP does not support directly connected multicast sources in the network. A directly connected
multicast source will send multicast traffic into the network without signaling through RGMP or
PIM. This multicast traffic will not be received by an RGMP-enabled router unless the router already
requested receipt of that multicast group through RGMP. This restriction applies to hosts and to
functions in routers that source multicast traffic, such as the ping and mtrace commands and
multicast applications that source multicast traffic, such as UDPTN.
RGMP supports directly connected receivers in the network. Traffic to these receivers will be
constrained by IGMP snooping, or if the receiver is a router itself, by PIM and RGMP.
CGMP is not supported in networks where RGMP is enabled on routers. You cannot enable both
RGMP and CGMP on a Layer 3 interface. If RGMP is enabled on a Layer 3 interface, CGMP is
silently disabled and vice versa.
Chapter 29 Configuring RGMP
OL-11439-03