Example: Enabling IGMP Querier
Example: Enabling IGMP Querier
The following example shows how to enable IGMP Querier:
switch# configure terminal
switch(config)# interface ethernet 2/1
switch(config-if)# ip pim sparse-mode
switch(config-if)#end
switch# show ip igmp interface
IGMP Interfaces for VRF "default", count: 2 Ethernet2/1, Interface status:
protocol-up/link-up/admin-up
IP address: 10.11.11.1, IP subnet: 10.11.11.0/24
Active querier: 10.11.11.1, version: 2, next query sent in: 00:01:57
Membership count: 1
.
.
Configuring ASM and Bidir
Any Source Multicast (ASM) and bidirectional shared trees (Bidir) are multicast distribution modes that
require the use of RPs to act as a shared root between sources and receivers of multicast data.
To configure ASM or Bidir mode, you configure sparse mode and the RP selection method, where you indicate
the distribution mode and assign the range of multicast groups.
Note
Bidir mode is not supported for vPCs. For more information about vPCs, see the Cisco Nexus 7000 Series
NX-OS Interfaces Configuration Guide.
Configuring Static RPs
You can configure an RP statically by configuring the RP address on every router that participates in the PIM
domain.
You can specify a route-map policy name that lists the group prefixes to use with the match ip multicast
command.
Beginning with Cisco NX-OS Release 5.1(3), the ip pim rp-address command has been enhanced with the
following functionalities:
• Added the prefix-list method of configuration in addition to existing route-map method.
• Added support for policy actions (route-map or prefix-list).
The following example configuration produces the same output using Cisco NX-OS (231.1.1.0/24 is always
denied irrespective of the sequence number):
Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide
88
Note
Cisco NX-OS always uses the longest-match prefix to find the RP. So, the behavior
is the same irrespective of the position of the group prefix in the route map or in
the prefix list.
Configuring PIM and PIM6