|
Command or Action |
Purpose |
Step 1 |
enable
Example:
|
Enables privileged EXEC mode.
-
Enter your password if prompted.
|
Step 2 |
configure terminal
Example:
Device# configure terminal
|
Enters global configuration mode. |
Step 3 |
ip multicast-routing [distributed]
Example:
Device(config)# ip multicast-routing
|
Enables IP multicast routing.
-
Use the distributed keyword to enabled Multicast Distributed Switching.
|
Step 4 |
Either perform Steps 5 through 7 or perform Steps 6 and 8. |
-- |
Step 5 |
ip pim autorp listener
Example:
Device(config)# ip pim autorp listener
|
Causes IP multicast traffic for the two AutoRP groups 224.0.1.39 and 224.0.1.40 to be PIM dense mode flooded across interfaces operating in PIM sparse mode.
-
Skip this step if you are configuring sparse-dense mode in Step 8.
|
Step 6 |
interface type number
Example:
Device(config)# interface Gigabitethernet 1/0/0
|
Selects an interface that is connected to hosts on which PIM can be enabled. |
Step 7 |
ip pim sparse-mode
Example:
Device(config-if)# ip pim sparse-mode
|
Enables PIM sparse mode on an interface. When configuring AutoRP in sparse mode, you must also configure the AutoRP listener in the next step.
-
Skip this step if you are configuring sparse-dense mode in Step 8.
|
Step 8 |
ip pim sparse-dense-mode
Example:
Device(config-if)# ip pim sparse-dense-mode
|
Enables PIM sparse-dense mode on an interface.
-
Skip this step if you configured sparse mode in Step 7.
|
Step 9 |
exit
Example:
|
Exits interface configuration mode and returns to global configuration mode. |
Step 10 |
Repeat Steps 1 through 9 on all PIM interfaces. |
-- |
Step 11 |
ip pim send-rp-announce {interface-type interface-number | ip-address} scope ttl-value [group-list access-list] [interval seconds] [bidir]
Example:
Device(config)# ip pim send-rp-announce loopback0 scope 31 group-list 5
|
Sends RP announcements out all PIM-enabled interfaces.
-
Perform this step on the RP device only.
-
Use the interface-typeand interface-number arguments to define which IP address is to be used as the RP address.
-
Use the ip-address argument to specify a directly connected IP address as the RP address.
Note |
If the ip-address argument is configured for this command, the RP-announce message will be sourced by the interface to which this IP address is connected (that is, the source address in the IP header of the RP-announce message is the IP address of that interface). |
-
This example shows that the interface is enabled with a maximum of 31 hops. The IP address by which the device wants to be identified as RP is the IP address associated with loopback interface 0. Access list 5 describes the groups for which this device serves as RP.
|
Step 12 |
ip pim send-rp-discovery [interface-type interface-number] scope ttl-value [interval seconds]
Example:
Device(config)# ip pim send-rp-discovery loopback 1 scope 31
|
Configures the device to be an RP mapping agent.
-
Perform this step on RP mapping agent devices or on combined RP/RP mapping agent devices.
Note |
AutoRP allows the RP function to run separately on one device and the RP mapping agent to run on one or multiple devices. It is possible to deploy the RP and the RP mapping agent on a combined RP/RP mapping agent device. |
-
Use the optional interface-type and interface-number arguments to define which IP address is to be used as the source address of the RP mapping agent.
-
Use the scope keyword and ttl-value argument to specify the Time-to-Live (TTL) value in the IP header of AutoRP discovery messages.
-
Use the optional interval keyword and seconds argument to specify the interval at which AutoRP discovery messages are sent.
Note |
Lowering the interval at which AutoRP discovery messages are sent from the default value of 60 seconds results in more frequent floodings of the group-to-RP mappings. In some network environments, the disadvantages of lowering the interval (more control packet overhead) may outweigh the advantages (more frequent group-to-RP mapping updates). |
-
The example shows limiting the AutoRP discovery messages to 31 hops on loopback interface 1.
|
Step 13 |
ip pim rp-announce-filter rp-list access-list group-list access-list
Example:
Device(config)# ip pim rp-announce-filter rp-list 1 group-list 2
|
Filters incoming RP announcement messages sent from candidate RPs (C-RPs) to the RP mapping agent.
-
Perform this step on the RP mapping agent only.
|
Step 14 |
no ip pim dm-fallback
Example:
Device(config)# no ip pim dm-fallback
|
(Optional) Prevents PIM dense mode fallback.
-
Skip this step if all interfaces have been configured to operate in PIM sparse mode.
Note |
The no ip pim dm-fallback command behavior is enabled by default if all the interfaces are configured to operate in PIM sparse mode (using the ip pim sparse-mode command). |
|
Step 15 |
interface type number
Example:
Device(config)# interface gigabitethernet 1/0/0
|
Selects an interface that is connected to hosts on which PIM can be enabled. |
Step 16 |
ip multicast boundary access-list [filter-autorp]
Example:
Device(config-if)# ip multicast boundary 10 filter-autorp
|
Configures an administratively scoped boundary.
-
Perform this step on the interfaces that are boundaries to other devices.
-
The access list is not shown in this task.
-
An access list entry that uses the deny keyword creates a multicast boundary for packets that match that entry.
|
Step 17 |
end
Example:
|
Returns to global configuration mode. |
Step 18 |
show ip pim autorp
Example:
Device# show ip pim autorp
|
(Optional) Displays the AutoRP information. |
Step 19 |
show ip pim rp [mapping] [rp-address]
Example:
Device# show ip pim rp mapping
|
(Optional) Displays RPs known in the network and shows how the device learned about each RP. |
Step 20 |
show ip igmp groups [group-name | group-address| interface-type interface-number] [detail]
Example:
Device# show ip igmp groups
|
(Optional) Displays the multicast groups having receivers that are directly connected to the device and that were learned through Internet Group Management Protocol (IGMP).
-
A receiver must be active on the network at the time that this command is issued in order for receiver information to be present on the resulting display.
|
Step 21 |
show ip mroute [group-address | group-name] [source-address | source-name] [interface-type interface-number] [summary] [count] [active kbps]
Example:
Device# show ip mroute cbone-audio
|
(Optional) Displays the contents of the IP multicast routing (mroute) table. |