Table Of Contents
Configuring PIM and PIM6
Information About PIM and PIM6
Hello Messages
Join-Prune Messages
State Refreshes
Rendezvous Points
Static RP
BSRs
Auto-RP
Anycast-RP
PIM Register Messages
Designated Routers
Designated Forwarders
ASM Switchover from Shared Tree to Source Tree
Administratively Scoped IP Multicast
Virtualization Support
Licensing Requirements for PIM and PIM6
Prerequisites for PIM and PIM6
Guidelines and Limitations for PIM and PIM6
Configuring PIM and PIM6
Enabling the PIM and PIM6 Features
Configuring PIM or PIM6 Sparse Mode
Configuring ASM and Bidir
Configuring Static RPs
Configuring BSRs
Configuring Auto-RP
Configuring a PIM Anycast-RP Set
Configuring Shared Trees Only for ASM
Configuring SSM
Configuring RPF Routes for Multicast
Configuring Route Maps to Control RP Information Distribution
Configuring Message Filtering
Restarting the PIM and PIM6 Processes
Verifying PIM and PIM6
Displaying Statistics
Displaying PIM and PIM6 Statistics
Clearing PIM and PIM6 Statistics
PIM Configuration Examples
SSM Configuration Example
BSR Configuration Example
Auto-RP Configuration Example
PIM Anycast-RP Configuration Example
Where to Go Next
Default Settings
Additional References
Related Documents
Standards
Technical Assistance
Configuring PIM and PIM6
This chapter describes how to configure the Protocol Independent Multicast (PIM) and PIM6 features in your IPv4 and IPv6 networks.
This chapter includes the following sections:
•
Information About PIM and PIM6
•Licensing Requirements for PIM and PIM6
•Prerequisites for PIM and PIM6
•Guidelines and Limitations for PIM and PIM6
•Configuring PIM and PIM6
•Verifying PIM and PIM6
•Displaying Statistics
•PIM Configuration Examples
•Where to Go Next
•Default Settings
•Additional References
Information About PIM and PIM6
PIM, which is used between multicast-capable routers, advertises group membership across a routing domain by constructing multicast distribution trees. PIM builds shared distribution trees on which packets from multiple sources are forwarded, as well as source distribution trees on which packets from a single source are forwarded. For more information about multicast, see the "Information About Multicast" section on page 1-1.
Cisco NX-OS supports PIM sparse mode for IPv4 networks (PIM) and for IPv6 networks (PIM6). (In PIM sparse mode, multicast traffic is sent only to locations of the network that specifically request it.) You can configure PIM and PIM6 to run simultaneously on a router. You can use PIM and PIM6 global parameters to configure RPs, message packet filtering, and statistics. You can use PIM and PIM6 interface parameters to enable multicast, identify PIM borders, set the PIM hello message interval, and set the designated router (DR) priority. For more information, see the "Configuring PIM or PIM6 Sparse Mode" section.
Note Cisco NX-OS does not support PIM dense mode.
In Cisco NX-OS, multicast is enabled only after you enable the PIM or PIM6 feature on each router and then enable PIM or PIM6 sparse mode on each interface that you want to participate in multicast. You can configure PIM for an IPv4 network and PIM6 for an IPv6 network. In an IPv4 network, if you have not already enabled IGMP on the router, PIM enables it automatically. In an IPv6 network, MLD is enabled by default. For information about configuring IGMP and MLD, see Chapter 2, "Configuring IGMP and MLD."
You use the PIM and PIM6 global configuration parameters to configure the range of multicast group addresses to be handled by each of the three distribution modes:
•Any Source Multicast (ASM) provides discovery of multicast sources. It builds a shared tree between sources and receivers of a multicast group and supports switching over to a source tree when a new receiver is added to a group. ASM mode requires that you configure an RP.
•Single Source Multicast (SSM) builds a source tree originating at the designated router on the LAN segment that receives a request to join a multicast source. SSM mode does not require you to configure RPs. Source discovery must be accomplished through other means.
•Bidirectional shared trees (Bidir) build a shared tree between sources and receivers of a multicast group but do not support switching over to a source tree when a new receiver is added to a group. Bidir mode requires that you configure an RP. Bidir forwarding does not require source discovery because only the share tree is used.
You can combine the three modes to cover different ranges of group addresses. For more information, see the "Configuring PIM and PIM6" section.
For more information about PIM sparse mode and shared distribution trees used by ASM and Bidir modes, see RFC 4601.
For more information about PIM SSM mode, see RFC 3569.
For more information about PIM Bidir mode, see draft-ietf-pim-bidir-09.txt.
This section includes the following topics:
•Hello Messages
•Join-Prune Messages
•State Refreshes
•Rendezvous Points
•PIM Register Messages
•Designated Routers
•Designated Forwarders
•ASM Switchover from Shared Tree to Source Tree
•Administratively Scoped IP Multicast
•Virtualization Support
Hello Messages
The PIM process begins when the router establishes PIM neighbor adjacencies by sending PIM hello messages to the multicast address 224.0.0.13. Hello messages are sent periodically at the interval of 30 seconds. When all neighbors have replied, then the PIM software chooses the router with the highest priority in each LAN segment as the designated router (DR). The DR priority is based on a DR priority value in the PIM hello message. If the DR priority value is not supplied by all routers, or the priorities match, the highest IP address is used to elect the DR.
For added security, you can configure an MD5 hash value that the PIM software uses to authenticate PIM hello messages with PIM neighbors.
For information about configuring hello message authentication, see the "Configuring PIM or PIM6 Sparse Mode" section.
Join-Prune Messages
When the DR receives an IGMP membership report message from a receiver for a new group or source, the DR creates a tree to connect the receiver to the source by sending a PIM join message out the interface toward the rendezvous point (ASM or Bidir mode) or source (SSM mode).The rendezvous point (RP) is the root of a shared tree, which is used by all sources and hosts in the PIM domain in the ASM or the Bidir mode. SSM does not use an RP but builds a shortest path tree (SPT) that is the lowest cost path between the source and the receiver.
When the DR determines that the last host has left a group or source, it sends a PIM prune message to remove the path from the distribution tree.
The routers forward the join or prune action hop by hop up the multicast distribution tree to create (join) or tear down (prune) the path.
Note In this publication, the terms "PIM join message" and "PIM prune message" are used to simplify the action taken when referring to the PIM join-prune message with only a join or prune action.
Join-prune messages are sent as quickly as possible by the software. You can filter the join-prune messages by defining a routing policy. For information about configuring the join-prune message policy, see the "Configuring PIM or PIM6 Sparse Mode" section.
State Refreshes
PIM requires that multicast entries are refreshed within a 3.5-minute timeout interval. The state refresh ensures that traffic is delivered only to active listeners, and it keeps routers from using unnecessary resources.
To maintain the PIM state, the last-hop DR sends join-prune messages once per minute. State creation applies to both (*, G) and (S, G) states as follows:
•(*, G) state creation example—An IGMP (*, G) report triggers the DR to send a (*, G) PIM join message toward the RP.
•(S, G) state creation example—An IGMP (S, G) report triggers the DR to send an (S, G) PIM join message toward the source.
If the state is not refreshed, the PIM software tears down the distribution tree by removing the forwarding paths in the multicast outgoing interface list of the upstream routers.
Rendezvous Points
A rendezvous point (RP) is a router that you select in a multicast network domain that acts as a shared root for a multicast shared tree. You can configure as many RPs as you like, and you can configure them to cover different group ranges.
This section includes the following topics:
•Static RP
•BSRs
•Auto-RP
•Anycast-RP
Static RP
You can statically configure an RP for a multicast group range. You must configure the address of the RP on every router in the domain.
You can define static RPs for the following reasons:
•To configure routers with the Anycast-RP address
•To manually configure an RP on a device
For information about configuring static RPs, see the "Configuring Static RPs" section.
BSRs
The bootstrap router (BSR) ensures that all routers in the PIM domain have the same RP cache as the BSR. You can configure the BSR to help you select an RP set from BSR candidate RPs. The function of the BSR is to broadcast the RP set to all routers in the domain. You select one or more candidate BSRs to manage the RPs in the domain. Only one candidate BSR is elected as the BSR for the domain.
Caution Do not configure both Auto-RP and BSR protocols in the same network.
Figure 3-1 shows where the BSR mechanism. router A, the software-elected BSR, sends BSR messages out all enabled interfaces (shown by the solid lines in the figure). The messages, which contain the RP set, are flooded hop by hop to all routers in the network. Routers B and C are candidate RPs that send their candidate-RP advertisements directly to the elected BSR (shown by the dashed lines in the figure).
The elected BSR receives candidate-RP messages from all the candidate RPs in the domain. The bootstrap message sent by the BSR includes information about all of the candidate RPs. Each router uses a common algorithm to select the same RP address for a given multicast group.
Figure 3-1 BSR Mechanism
In the RP selection process, the RP address with the best priority is determined by the software. If the priorities match for two or more RP addresses, the software may use the RP hash in the selection process. Only one RP address is assigned to a group.
By default, routers are not enabled to listen or forward BSR messages. You must enable the BSR listening and forwarding feature so that the BSR mechanism can dynamically inform all routers in the PIM domain of the RP set assigned to multicast group ranges.
For more information about bootstrap routers, see RFC 5059.
Note The BSR mechanism is a nonproprietary method of defining RPs that can be used with third-party routers.
For information about configuring BSRs and candidate RPs, see the "Configuring BSRs" section.
Auto-RP
Auto-RP is a Cisco protocol that was prior to the Internet standard bootstrap router mechanism. You configure Auto-RP by selecting candidate mapping agents and RPs. Candidate RPs send their supported group range in RP-Announce messages to the Cisco RP-Announce multicast group 224.0.1.39. An Auto-RP mapping agent listens for RP-Announce messages from candidate RPs and forms a Group-to-RP mapping table. The mapping agent multicasts the Group-to-RP mapping table in RP-Discovery messages to the Cisco RP-Discovery multicast group 224.0.1.40.
Caution Do not configure both Auto-RP and BSR protocols in the same network.
Figure 3-2 shows the Auto-RP mechanism. Periodically, the RP mapping agent multicasts the RP information that it receives to the Cisco-RP-Discovery group 224.0.1.40 (shown by the solid lines in the figure).
Figure 3-2 Auto-RP Mechanism
By default, routers are not enabled to listen or forward Auto-RP messages. You must enable the Auto-RP listening and forwarding feature so that the Auto-RP mechanism can dynamically inform routers in the PIM domain of the Group-to-RP mapping.
Note Auto-RP is not supported for PIM6.
For information about configuring Auto-RP, see the "Configuring Auto-RP" section.
Anycast-RP
Anycast-RP has two implementations: one uses Multicast Source Discovery Protocol (MSDP) and the other is based on RFC 4610, Anycast-RP Using Protocol Independent Multicast (PIM). This section describes how to configure PIM Anycast-RP.
You can use PIM Anycast-RP to assign a group of routers, called the Anycast-RP set, to a single RP address that is configured on multiple routers. The set of routers that you configure as Anycast-RPs is called the Anycast-RP set. This method is the only RP method that supports more than one RP per multicast group, which allows you to load balance across all RPs in the set. The Anycast RP supports all multicast groups.
PIM register messages are sent to the closest RP and PIM join-prune messages are sent in the direction of the closest RP as determined by the unicast routing protocols. If one of the RPs goes down, unicast routing ensures these message will be sent in the direction of the next-closest RP.
For more information about PIM Anycast-RP, see RFC 4610.
For information about configuring Anycast-RPs, see the "Configuring a PIM Anycast-RP Set" section.
PIM Register Messages
PIM register messages are unicast to the RP by designated routers (DRs) that are directly connected to multicast sources. The PIM register message has the following functions:
•To notify the RP that a source is actively sending to a multicast group.
•To deliver multicast packets sent by the source to the RP for delivery down the shared tree.
The DR continues to send PIM register messages to the RP until it receives a Register-Stop message from the RP. The RP sends a Register-Stop message in either of the following cases:
•The RP has no receivers for the multicast group being transmitted.
•The RP has joined the SPT to the source but has not started receiving traffic from the source.
Note In NX-OS, PIM register messages are rate limited to avoid overwhelming the RP.
You can filter PIM register messages by defining a routing policy. For information about configuring the PIM register message policy, see the "Configuring Shared Trees Only for ASM" section.
Designated Routers
In PIM ASM and SSM modes, the software chooses a designated router (DR) from the routers on each network segment. The DR is responsible for forwarding multicast data for specified groups and sources on that segment.
The DR for each LAN segment is determined as described in the "Hello Messages" section.
In ASM mode, the DR is responsible for unicasting PIM register packets to the RP. When a DR receives an IGMP membership report from a directly connected receiver, the shortest path is formed to the RP, which may or may not go through the DR. The result is a shared tree that connects all sources transmitting on the same multicast group to all receivers of that group.
In SSM mode, the DR triggers (*, G) or (S, G) PIM join messages toward the RP or the source. The path from the receiver to the source is determined hop by hop. The source must be known to the receiver or the DR.
For information about configuring the DR priority, see the "Configuring PIM or PIM6 Sparse Mode" section.
Designated Forwarders
In PIM Bidir mode, the software chooses a designated forwarder (DF) at RP discovery time from the routers on each network segment. The DF is responsible for forwarding multicast data for specified groups on that segment. The DF is elected based on the best metric from the network segment to the RP.
If the router receives a packet on the RPF interface toward the RP, the router forwards the packet out all interfaces in the OIF-list. If a router receives a packet on an interface on which the router is the elected DF for that LAN segment, the packet is forwarded out all interfaces in the OIF-list except the interface that it was received on, and also out the RPF interface toward the RP.
Note Cisco NX-OS puts the RPF interface into the OIF-list of the MRIB, but not in the OIF-list of the MFIB.
ASM Switchover from Shared Tree to Source Tree
In ASM mode, the DR that is connected to a receiver switches over from the shared tree to the shortest-path tree (SPT) to a source unless you configure the PIM parameter to use shared trees only. For information about configuring the use of shared trees only, see the "Configuring Shared Trees Only for ASM" section.
During the switchover, messages on the SPT and shared tree may overlap. These messages are different. The shared tree messages are propagated upstream toward the RP, while SPT messages go toward the source.
For information about SPT switchovers, see the Last-Hop Switchover to the SPT section in RFC 4601.
Administratively Scoped IP Multicast
The administratively scoped IP multicast method allows you to set boundaries on the delivery of multicast data. For more information, see RFC 2365.
You can configure an interface as a PIM boundary so that PIM messages are not sent out that interface. For information about configuring the domain border parameter, see the "Configuring PIM or PIM6 Sparse Mode" section.
You can use the Auto-RP scope parameter to set a time-to-live (TTL) value. For more information, see the "Configuring Shared Trees Only for ASM" section.
Virtualization Support
A virtual device context (VDC) is a logical representation of a set of system resources. Within each VDC, multiple virtual routing and forwarding (VRF) instances can be defined. For each VRF in a VDC in the system, independent multicast system resources are maintained, including the MRIB and M6RIB.
You can use the PIM and PIM6 show commands with a VRF argument to provide a context for the information displayed. The default VRF is used if no VRF argument is supplied.
For information about configuring VDCs, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 4.0.
For information about configuring VRFs, see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 4.0.
Licensing Requirements for PIM and PIM6
The following table shows the licensing requirements for this feature:
Product
|
License Requirement
|
NX-OS
|
PIM and PIM6 require an Enterprise Services license. For a complete explanation of the NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco Nexus 7000 Series NX-OS Licensing Guide, Release 4.0.
|
Prerequisites for PIM and PIM6
PIM and PIM6 have the following prerequisites:
•You are logged onto the device.
•You are in the correct virtual device context (VDC). A VDC is a logical representation of a set of system resources. You can use the switchto vdc command with a VDC number.
•For global commands, you are in the correct virtual routing and forwarding (VRF) mode. The default configuration mode shown in the examples in this chapter applies to the default VRF.
Guidelines and Limitations for PIM and PIM6
Follow these guidelines and limitations for PIM and PIM6:
•Tunnel interfaces do not support PIM.
•NX-OS PIM and PIM6 will not interoperate with any version of PIM dense mode or PIM sparse mode version 1.
•Do not configure both Auto-RP and BSR protocols in the same network.
•Configure candidate RP intervals to a minimum of 15 seconds.
•If a device is configured with a BSR policy that should prevent it from being elected as the BSR, the device ignores the policy. This behavior results in the following undesirable conditions:
–If a device receives a BSM that is permitted by the policy, the device, which incorrectly elected itself as the BSR, drops that BSM so that routers downstream fail to receive it. Downstream devices correctly filter the BSM from the incorrect BSR so that these devices do not receive RP information.
–A BSM received by a BSR from a different device sends a new BSM but ensures that downstream devices will not receive the correct BSM.
Configuring PIM and PIM6
You can configure both PIM and PIM6 on the same router. You configure either PIM or PIM6 for each interface, depending on whether that interface is running IPv4 or IPv6.
Note Cisco NX-OS supports only PIM sparse mode version 2. In this publication, "PIM" refers to PIM sparse mode version 2.
You can configure separate ranges of addresses in the PIM or PIM6 domain using the multicast distribution modes described in Table 3-1.
Table 3-1 PIM and PIM6 Multicast Distribution Modes
Multicast Distribution Mode
|
Requires RP Configuration
|
Description
|
ASM
|
Yes
|
Any source multicast
|
Bidir
|
Yes
|
Bidirectional shared trees
|
SSM
|
No
|
Single source multicast
|
RPF routes for multicast
|
No
|
RPF routes for multicast
|
To configure PIM and PIM6, follow these steps:
Step 1 From the multicast distribution modes described in Table 3-1, select the range of multicast groups that you want to configure in each mode.
Step 2 Enable the PIM and PIM6 features. See the "Enabling the PIM and PIM6 Features" section.
Step 3 Configure PIM or PIM6 sparse mode on each interface that you want to participate in a PIM domain. See the "Configuring PIM or PIM6 Sparse Mode" section.
Step 4 Follow the configuration steps for the multicast distribution modes that you selected in Step 1 as follows:
•For ASM or Bidir mode, see the "Configuring ASM and Bidir" section.
•For SSM mode, see the "Configuring SSM" section.
•For RPF routes for multicast, see the "Configuring RPF Routes for Multicast" section.
Step 5 Configure message filtering. See the "Configuring Message Filtering" section.
The CLI commands used to configure PIM or PIM6 differ as follows:
•Commands begin with ip pim for PIM and begin with ipv6 pim for PIM6.
•Commands begin with show ip pim for PIM and begin with show ipv6 pim for PIM6.
This section includes the following topics:
•Enabling the PIM and PIM6 Features
•Configuring PIM or PIM6 Sparse Mode
•Configuring ASM and Bidir
•Configuring SSM
•Configuring RPF Routes for Multicast
•Configuring Route Maps to Control RP Information Distribution
•Configuring Message Filtering
•Restarting the PIM and PIM6 Processes
Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.
Enabling the PIM and PIM6 Features
Before you can access the PIM or PIM6 commands, you must enable the PIM or PIM6 feature.
SUMMARY STEPS
1. config t
2. feature pim
3. feature pim6
4. show running-config | grep feature
5. copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
feature pim
Example:
switch(config)# feature pim
|
Enables PIM. By default, PIM is disabled.
|
Step 3
|
feature pim6
Example:
switch(config)# feature pim6
|
Enables PIM6. By default, PIM6 is disabled.
|
Step 4
|
show running-config | grep feature
Example:
switch(config)# show running-config |
grep feature
|
(Optional) Shows specified feature or all feature commands if you specify the feature argument.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Configuring PIM or PIM6 Sparse Mode
You configure PIM or PIM6 sparse mode on every device interface that you want to participate in a sparse mode domain. You can configure the sparse mode parameters described in Table 3-2.
Table 3-2 PIM and PIM6 Sparse Mode Parameters
Parameter
|
Description
|
Global to the device
|
Auto-RP message action
|
Enables listening and forwarding of Auto-RP messages. The default is disabled, which means that the router does not listen or forward Auto-RP messages unless it is configured as a candidate RP or mapping agent.
Note PIM6 does not support the Auto-RP method.
|
BSR message action
|
Enables listening and forwarding of BSR messages. The default is disabled, which means that the router does not listen or forward BSR messages unless it is configured as a candidate RP or BSR candidate.
|
Per device interface
|
PIM sparse mode
|
Enables PIM or PIM6 on an interface.
|
Designated router priority
|
Sets the designated router (DR) priority that is advertised in PIM hello messages on this interface. On a multi-access network with multiple PIM-enabled routers, the router with the highest DR priority is elected as the DR router. If the priorities match, the software elects the DR with the highest IP address. The DR originates PIM register messages for the directly connected multicast sources and sends PIM join messages toward the rendezvous point (RP) for directly connected receivers. Values range from 1 to 4294967295. The default is 1.
|
Hello authentication mode
|
Enables an MD5 hash authentication key, or password, in PIM hello messages on the interface so that directly connected neighbors can authenticate each other. The PIM hello messages are IPsec encoded using the Authentication Header (AH) option. You can enter an unencrypted (cleartext) key, or one of these values followed by a space and the MD5 authentication key:
•0—Specifies an unencrypted (cleartext) key
•3—Specifies a 3-DES encrypted key
•7—Specifies a Cisco Type 7 encrypted key
The authentication key can be up to 16 characters. The default is disabled.
Note PIM6 does not support hello authentication.
|
Hello interval
|
Configures the interval at which hello messages are sent in milliseconds. The range is from 1 to 4294967295. The default is 30000.
|
Domain border
|
Enables the interface to be on the border of a PIM domain so that no bootstrap, candidate-RP, or Auto-RP messages are sent or received on the interface. The default is disabled.
Note PIM6 does not support the Auto-RP method.
|
Neighbor policy
|
Configures which PIM neighbors to become adjacent to based on a routing-rules policy1 where you can specify IP addresses to become adjacent to. If the policy name does not exist, or no IP addresses are configured in a policy, then adjacency is established with all neighbors. The default is to become adjacent with all PIM neighbors.
Note We recommend that you should configure this feature only if you are an experienced network administrator.
|
Note To configure the join-prune policy, see the "Configuring Message Filtering" section.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim auto-rp {listen [forward] | forward [listen]}
3. ip pim bsr {listen [forward] | forward [listen]}
4. show ip pim rp [ip-prefix] [vrf vrf-name | all]
5. interface interface
6. ip pim sparse-mode
7. ip pim dr-priority priority
8. ip pim hello-authentication ah-md5 auth-key
9. ip pim hello-interval interval
10. ip pim border
11. ip pim neighbor-policy policy-name
12. show ip pim interface [interface | brief] [vrf vrf-name | all]
13. copy running-config startup-config
PIM6 Commands
1. config t
2. ipv6 pim bsr {listen [forward] | forward [listen]}
3. show ipv6 pim rp [ipv6-prefix] [vrf vrf-name | all]
4. interface interface
5. ipv6 pim sparse-mode
6. ipv6 pim dr-priority priority
7. ipv6 pim hello-interval interval
8. ipv6 pim border
9. ipv6 pim neighbor-policy policy-name
10. show ipv6 pim interface [interface | brief] [vrf vrf-name | all]
11. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim auto-rp {listen [forward] |
forward [listen]}
Example:
switch(config)# ip pim auto-rp listen
|
(Optional) Enables listening or forwarding of Auto-RP messages. The default is disabled, which means that the software does not listen to or forward Auto-RP messages.
|
Step 3
|
ip pim bsr {listen [forward] | forward
[listen]}
Example:
switch(config)# ip pim bsr forward
|
(Optional) Enables listening or forwarding of BSR messages. The default is disabled, which means that the software does not listen or forward BSR messages.
|
Step 4
|
show ip pim rp [ip-prefix] [vrf vrf-name
| all]
Example:
switch(config)# show ip pim rp
|
(Optional) Displays PIM RP information, including Auto-RP and BSR listen and forward states.
|
Step 5
|
interface interface
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface mode on the interface type and number, such as ethernet slot/port.
|
Step 6
|
ip pim sparse-mode
Example:
switch(config-if)# ip pim sparse-mode
|
Enables PIM sparse mode on this interface. The default is disabled.
|
Step 7
|
ip pim dr-priority priority
Example:
switch(config-if)# ip pim dr-priority
192
|
(Optional) Sets the designated router (DR) priority that is advertised in PIM hello messages. Values range from 1 to 4294967295. The default is 1.
|
Step 8
|
ip pim hello-authentication ah-md5
auth-key
Example:
switch(config-if)# ip pim
hello-authentication ah-md5 my_key
|
(Optional) Enables an MD5 hash authentication key in PIM hello messages. You can enter an unencrypted (cleartext) key, or one of these values followed by a space and the MD5 authentication key:
•0—Specifies an unencrypted (cleartext) key
•3—Specifies a 3-DES encrypted key
•7—Specifies a Cisco Type 7 encrypted key
The key can be up to 16 characters. The default is disabled.
|
Step 9
|
ip pim hello-interval interval
Example:
switch(config-if)# ip pim hello-interval
25000
|
(Optional) Configures the interval at which hello messages are sent in milliseconds. The range is from 1 to 4294967295. The default is 30000.
|
Step 10
|
ip pim border
Example:
switch(config-if)# ip pim border
|
(Optional) Enables the interface to be on the border of a PIM domain so that no bootstrap, candidate-RP, or Auto-RP messages are sent or received on the interface. The default is disabled.
|
Step 11
|
ip pim neighbor-policy policy-name
Example:
switch(config-if)# ip pim
neighbor-policy my_neighbor_policy
|
(Optional) Configures which PIM neighbors to become adjacent to based on a routing-rules policy. The policy name can be up to 63 characters. The default is to become adjacent with all PIM neighbors.
Note We recommend that you should configure this feature only if you are an experienced network administrator.
|
Step 12
|
show ip pim interface [interface |
brief] [vrf vrf-name | all]
Example:
switch(config-if)# show ip pim interface
|
(Optional) Displays PIM interface information.
|
Step 13
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ipv6 pim bsr {listen [forward] | forward
[listen]}
Example:
switch(config)# ipv6 pim bsr forward
|
(Optional) Enables listening or forwarding of BSR messages. The default is disabled, which means that the software does not listen or forward BSR messages.
|
Step 3
|
show ipv6 pim rp [ipv6-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ipv6 pim rp
|
(Optional) Displays PIM6 RP information, including BSR listen and forward states.
|
Step 4
|
interface interface
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface mode on the specified interface.
|
Step 5
|
ipv6 pim sparse-mode
Example:
switch(config-if)# ipv6 pim sparse-mode
|
Enables PIM6 sparse mode on this interface. The default is disabled.
|
Step 6
|
ipv6 pim dr-priority priority
Example:
switch(config-if)# ipv6 pim dr-priority
192
|
(Optional) Sets the designated router (DR) priority that is advertised in PIM hello messages. Values range from 1 to 4294967295. The default is 1.
|
Step 7
|
ipv6 pim hello-interval interval
Example:
switch(config-if)# ipv6 pim
hello-interval 25000
|
(Optional) Configures the interval at which hello messages are sent in milliseconds. The range is from 1 to 4294967295. The default is 30000.
|
Step 8
|
ipv6 pim border
Example:
switch(config-if)# ipv6 pim border
|
(Optional) Enables the interface to be on the border of a PIM domain so that no bootstrap, candidate-RP, or Auto-RP messages are sent or received on the interface. The default is disabled.
|
Step 9
|
ipv6 pim neighbor-policy policy-name
Example:
switch(config-if)# ipv6 pim
neighbor-policy my_neighbor_policy
|
(Optional) Configures which PIM neighbors to become adjacent to based on a routing-rules policy. The policy name can be up to 63 characters. The default is to become adjacent with all PIM neighbors.
Note We recommend that you should configure this feature only if you are an experienced network administrator.
|
Step 10
|
show ipv6 pim interface [interface |
brief] [vrf vrf-name | all]
Example:
switch(config-if)# show ipv6 pim
interface
|
(Optional) Displays PIM6 interface information.
|
Step 11
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
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.
This section includes the following topics:
•Configuring Static RPs
•Configuring BSRs
•Configuring Auto-RP
•Configuring a PIM Anycast-RP Set
•Configuring Shared Trees Only for ASM
Configuring Static RPs
You can configure an RP statically by configuring the RP address on every router that will participate in the PIM domain.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim rp-address rp-address [group-list ip-prefix] [bidir]
3. show ip pim group-range [ip-prefix] [vrf vrf-name | all]
4. copy running-config startup-config
PIM6 Commands
1. config t
2. ipv6 pim rp-address rp-address [group-list ipv6-prefix] [bidir]
3. show ipv6 pim group-range [ipv6-prefix] [vrf vrf-name | all]
4. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim rp-address rp-address [group-list
ip-prefix] [bidir]
Example 1:
switch(config)# ip pim rp-address
192.0.2.33 group-list 224.0.0.0/9
Example 2:
switch(config)# ip pim rp-address
192.0.2.34 group-list 224.128.0.0/9
bidir
|
Configures a PIM static RP address for a multicast group range. The default mode is ASM unless you specify the bidir keyword. The default group range is 224.0.0.0 through 239.255.255.255.
Example 1 configures PIM ASM mode for the specified group range.
Example 2 configures PIM Bidir mode for the specified group range.
|
Step 3
|
show ip pim group-range [ip-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ip pim group-range
|
(Optional) Displays PIM modes and group ranges.
|
Step 4
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ipv6 pim rp-address rp-address
[group-list ipv6-prefix] [bidir]
Example 1:
switch(config)# ipv6 pim rp-address
2001:0db8:0:abcd::1 group-list
ff1e:abcd:def1::0/24
Example 2:
switch(config)# ipv6 pim rp-address
2001:0db8:0:abcd::2 group-list
ff1e:abcd:def2::0/96 bidir
|
Configures a PIM6 static RP address for a multicast group range. The mode is ASM unless you specify the bidir keyword. The default group range is ff00::0/8.
Example 1 configures PIM6 ASM mode for the specified group range.
Example 2 configures PIM6 Bidir mode for the specified group range.
|
Step 3
|
show ipv6 pim group-range [ipv6-prefix]
[vrf vrf-name | all]
Example:
switch(config)# show ipv6 pim
group-range
|
(Optional) Displays PIM6 modes and group ranges.
|
Step 4
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
Configuring BSRs
You configure BSRs by selecting candidate BSRs and RPs.
Caution Do not configure both Auto-RP and BSR protocols in the same network.
You can configure a candidate BSR with the arguments described in Table 3-3.
Table 3-3 Candidate BSR Arguments
Argument
|
Description
|
interface
|
Interface type and number used to derive the BSR source IP address used in bootstrap messages.
|
hash-length
|
Hash length is the number of high order 1s used to form a mask that is ANDed with group address ranges of candidate RPs to form a hash value. The mask determines the number of consecutive addresses to assign across RPs with the same group range. For PIM, this value ranges from 0 to 32 and has a default of 30. For PIM6, this value ranges from 0 to 128 and has a default of 126.
|
priority
|
Priority assigned to this BSR. The software elects the BSR with the highest priority, or if the BSR priorities match, the software elects the BSR with the highest IP address. This value ranges from 0, the lowest priority, to 255 and has a default of 64.
|
You can configure a candidate RP with the arguments described in Table 3-4.
Table 3-4 BSR Candidate RP Arguments and Keywords
Argument or Keyword
|
Description
|
interface
|
Interface type and number used to derive the BSR source IP address used in Bootstrap messages.
|
group-list ip-prefix
|
Multicast groups handled by this RP specified in a prefix format.
|
interval
|
Number of seconds between sending candidate-RP messages. This value ranges from 1 to 65,535 and has a default of 60 seconds.
Note We recommend that you configure the candidate RP interval to a minimum of 15 seconds.
|
priority
|
Priority assigned to this RP. The software elects the RP with the highest priority for a range of groups, or if the priorities match, the highest IP address. This value ranges from 0, the highest priority, to 65,535 and has a default of 192.
|
bidir
|
Unless you specify bidir, this RP will be in ASM mode. If you specify bidir, then the RP will be in Bidir mode.
|
Tip You should choose the candidate BSRs and candidate RPs that have good connectivity to all parts of the PIM domain.
You can configure the same router to be both a BSR and a candidate RP. In a domain with many routers, you can select multiple candidate BSRs and RPs to automatically fail over to alternates if a BSR or an RP fails.
To configure candidate BSRs and RPs, follow these steps:
Step 1 Configure whether each router in the PIM domain should listen and forward BSR messages. A router configured as either a candidate RP or a candidate BSR will automatically listen to and forward all bootstrap router protocol messages, unless an interface is configured with the domain border feature. For more information, see the "Configuring PIM or PIM6 Sparse Mode" section.
Step 2 Select the routers to act as candidate BSRs and RPs.
Step 3 Configure each candidate BSR and candidate RP as described in this section.
Step 4 Configure BSR message filtering. See the "Configuring Message Filtering" section.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim [bsr] bsr-candidate interface [hash-len hash-length] [priority priority]
3. ip pim [bsr] rp-candidate interface group-list ip-prefix [priority priority] [interval interval] [bidir]
4. show ip pim group-range [ip-prefix] [vrf vrf-name | all]
5. copy running-config startup-config
PIM6 Commands
1. config t
2. ipv6 pim [bsr] bsr-candidate interface [hash-len hash-length] [priority priority]
3. ipv6 pim [bsr] rp-candidate interface group-list ipv6-prefix [priority priority] [interval interval] [bidir]
4. show ipv6 pim group-range [ipv6-prefix] [vrf vrf-name | all]
5. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim [bsr] bsr-candidate interface
[hash-len hash-length] [priority
priority]
Example:
switch(config)# ip pim bsr-candidate
ethernet 2/1 hash-len 24
|
Configures a candidate bootstrap router (BSR). The source IP address used in a bootstrap message is the IP address of the interface. The hash length ranges from 0 to 32 and has a default of 30. The priority ranges from 0 to 255 and has a default of 64. For parameter details, see Table 3-3.
|
Step 3
|
ip pim [bsr] rp-candidate interface
group-list ip-prefix [priority priority]
[interval interval] [bidir]
Example 1:
switch(config)# ip pim rp-candidate
ethernet 2/1 group-list 239.0.0.0/24
Example 2:
switch(config)# ip pim rp-candidate
ethernet 2/1 group-list 239.0.0.0/24
bidir
|
Configures a candidate RP for BSR. The priority ranges from 0, the highest priority, to 65,535 and has a default of 192. The interval ranges from 1 to 65,535 seconds and has a default of 60.
Note We recommend that you configure the candidate RP interval to a minimum of 15 seconds.
Example 1 configures an ASM candidate RP.
Example 2 configures a Bidir candidate RP.
|
Step 4
|
show ip pim group-range [ip-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ip pim group-range
|
(Optional) Displays PIM modes and group ranges.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ipv6 pim [bsr] bsr-candidate interface
[hash-len hash-length] [priority
priority]
Example:
switch(config)# ipv6 pim bsr-candidate
ethernet 2/1 hash-len 24 priority 192
|
Configures a candidate bootstrap router (BSR). The source IP address used in a bootstrap message is the IP address of the interface. The hash length ranges from 0 to 128 and has a default of 126. The priority ranges from 0, the lowest priority, to 255 and has a default of 64. For parameter details, see Table 3-3.
|
Step 3
|
ipv6 pim [bsr] rp-candidate interface
group-list ipv6-prefix [priority
priority] [interval interval] [bidir]
Example 1:
switch(config)# ipv6 pim rp-candidate
ethernet 2/1 group-list
ff1e:abcd:def1::0/24
Example 2:
switch(config)# ipv6 pim rp-candidate
ethernet 2/1 group-list
ff1e:abcd:def2::0/24 bidir
|
Configures a candidate RP for BSR. The priority ranges from 0, the highest priority, to 65,535 and has a default of 192. The interval ranges from 1 to 65,535 seconds and has a default of 60. For parameter details, see Table 3-4.
Example 1 configures an ASM candidate RP.
Example 2 configures a Bidir candidate RP.
|
Step 4
|
show ipv6 pim group-range [ipv6-prefix]
[vrf vrf-name | all]
Example:
switch(config)# show ipv6 pim
group-range
|
(Optional) Displays PIM6 modes and group ranges.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
Use the show ipv6 pim group-range command to display the configured PIM6 modes and group ranges.
Configuring Auto-RP
You can configure Auto-RP by selecting candidate mapping agents and RPs. You can configure the same router to be both a mapping agent and a candidate RP.
Note Auto-RP is not supported by PIM6.
Caution Do not configure both Auto-RP and BSR protocols in the same network.
You can configure an Auto-RP mapping agent with the arguments described in Table 3-5.
Table 3-5 Auto-RP Mapping Agent Arguments
Argument
|
Description
|
interface
|
Interface type and number used to derive the IP address of the Auto-RP mapping agent used in bootstrap messages.
|
scope ttl
|
Time-To-Live (TTL) value that represents the maximum number of hops that RP-Discovery messages are forwarded. This value can range from 1 to 255 and has a default of 32.
Note See the border domain feature in the "Configuring PIM or PIM6 Sparse Mode" section.
|
If you configure multiple Auto-RP mapping agents, only one is elected as the mapping agent for the domain. The elected mapping agent ensures that all candidate RP messages are sent out. All mapping agents receive the candidate RP messages and advertise the same RP cache in their RP-discovery messages.
You can configure a candidate RP with the arguments described in Table 3-6.
Table 3-6 Auto-RP Candidate RP Arguments and Keywords
Argument or Keyword
|
Description
|
interface
|
Interface type and number used to derive the IP address of the candidate RP used in Bootstrap messages.
|
group-list ip-prefix
|
Multicast groups handled by this RP. Specified in a prefix format.
|
scope ttl
|
Time-To-Live (TTL) value that represents the maximum number of hops that RP-Discovery messages are forwarded. This value can range from 1 to 255 and has a default of 32.
Note See the border domain feature in the "Configuring PIM or PIM6 Sparse Mode" section.
|
interval
|
Number of seconds between sending RP-Announce messages. This value can range from 1 to 65,535 and has a default of 60.
Note We recommend that you configure the candidate RP interval to a minimum of 15 seconds.
|
bidir
|
If not specified, this RP will be in ASM mode. If specified, this RP will be in Bidir mode.
|
Tip You should choose mapping agents and candidate RPs that have good connectivity to all parts of the PIM domain.
To configure Auto-RP mapping agents and candidate RPs, follow these steps:
Step 1 For each router in the PIM domain, configure whether that router should listen and forward Auto-RP messages. A router configured as either a candidate RP or an Auto-RP mapping agent will automatically listen to and forward all Auto-RP protocol messages, unless an interface is configured with the domain border feature. For more information, see the "Configuring PIM or PIM6 Sparse Mode" section.
Step 2 Select the routers to act as mapping agents and candidate RPs.
Step 3 Configure each mapping agent and candidate RP as described in this section.
Step 4 Configure Auto-RP message filtering. See the "Configuring Message Filtering" section.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim {send-rp-discovery | {auto-rp mapping-agent}} interface [scope ttl]
3. ip pim {send-rp-announce | {auto-rp rp-candidate}} interface group-list ip-prefix [scope ttl] [interval interval] [bidir]
4. show ip pim group-range [ip-prefix] [vrf vrf-name | all]
5. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim {send-rp-discovery | {auto-rp
mapping-agent}} interface [scope ttl]
Example:
switch(config)# ip pim auto-rp
mapping-agent ethernet 2/1
|
Configures an Auto-RP mapping agent. The source IP address used in Auto-RP Discovery messages is the IP address of the interface. The default scope is 32. For parameter details, see Table 3-5.
|
Step 3
|
ip pim {send-rp-announce | {auto-rp
rp-candidate}} interface group-list
ip-prefix [scope ttl] [interval
interval] [bidir]
Example 1:
switch(config)# ip pim auto-rp
rp-candidate ethernet 2/1 group-list
239.0.0.0/24
Example 2:
switch(config)# ip pim auto-rp
rp-candidate ethernet 2/1 group-list
239.0.0.0/24 bidir
|
Configures an Auto-RP candidate RP. The default scope is 32. The default interval is 60 seconds. By default, the command creates an ASM candidate RP. For parameter details, see Table 3-6.
Note We recommend that you configure the candidate RP interval to a minimum of 15 seconds.
Example1 configures an ASM candidate RP.
Example 2 configures a Bidir candidate RP.
|
Step 4
|
show ip pim group-range [ip-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ip pim group-range
|
(Optional) Displays PIM modes and group ranges.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Configuring a PIM Anycast-RP Set
To configure a PIM Anycast-RP set, follow these steps:
Step 1 Select the routers in the PIM Anycast-RP set.
Step 2 Select an IP address for the PIM Anycast-RP set.
Step 3 Configure each peer RP in the PIM Anycast-RP set as described in this section.
SUMMARY STEPS
PIM Commands
1. config t
2. interface loopback number
3. ip address ip-prefix
4. exit
5. ip pim anycast-rp anycast-rp-address anycast-rp-peer-address
6. Repeat Step 5 using the same anycast-rp for each peer RP in the RP set
7. show ip pim group-range [ip-prefix] [vrf vrf-name | all]
8. copy running-config startup-config
PIM6 Commands
1. config t
2. interface loopback number
3. ipv6 address ipv6-prefix
4. exit
5. ipv6 pim anycast-rp anycast-rp-address anycast-rp-peer-address
6. Repeat Step 5 using the same anycast-rp for each peer RP in the RP set
7. show ipv6 pim group-range [ipv6-prefix] [vrf vrf-name | all]
8. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
interface loopback number
Example:
switch(config)# interface loopback 0
|
Configures an interface loopback.
This example configures interface loopback 0.
|
Step 3
|
ip address ip-prefix
Example:
switch(config-if)# ip address
192.0.2.3/32
|
Configures an IP address for this interface.
This example configures an IP address for the Anycast-RP.
|
Step 4
|
exit
Example:
switch(config)# exit
|
Returns to configuration mode.
|
Step 5
|
ip pim anycast-rp anycast-rp-address
anycast-rp-peer-address
Example:
switch(config)# ip pim anycast-rp
192.0.2.3 192.0.2.31
|
Configures a PIM Anycast-RP peer address for the specified Anycast-RP address. Each command with the same Anycast-RP address forms an Anycast-RP set. The IP addresses of RPs are used for communication with RPs in the set.
|
Step 6
|
Repeat Step 5 using the same Anycast-RP address for each peer RP in the Anycast-RP set.
|
—
|
Step 7
|
show ip pim group-range [ip-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ip pim group-range
|
(Optional) Displays PIM modes and group ranges.
|
Step 8
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
interface loopback number
Example:
switch(config)# interface loopback 0
|
Configures an interface loopback.
This example configures loopback 0.
|
Step 3
|
ipv6 address ipv6-prefix
Example:
switch(config-if)# ipv6 address
2001:0db8:0:abcd::3/32
|
Configures an IP address for this interface.
This example configures an IP address for the Anycast-RP.
|
Step 4
|
exit
Example:
switch(config)# exit
|
Returns to configuration mode.
|
Step 5
|
ipv6 pim anycast-rp anycast-rp-address
anycast-rp-peer-address
Example:
switch(config)# ipv6 pim anycast-rp
2001:0db8:0:abcd::3 2001:0db8:0:abcd::31
|
Configures a PIM6 Anycast-RP peer address for the specified Anycast-RP address. Each command with the same Anycast-RP address forms an Anycast-RP set. The IP addresses of RPs are used for communication with RPs in the set.
|
Step 6
|
Repeat Step 5 using the same Anycast-RP address for each peer RP in the Anycast-RP set.
|
—
|
Step 7
|
show ipv6 pim group-range [ipv6-prefix]
[vrf vrf-name | all]
Example:
switch(config)# show ipv6 pim
group-range
|
(Optional) Displays PIM6 modes and group ranges.
|
Step 8
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Configuring Shared Trees Only for ASM
You can configure shared trees only on the last-hop router for Any Source Multicast (ASM) groups, which means that the router never switches over from the shared tree to the SPT when a receiver joins an active group. You can specify a group range where the use of shared trees is to be enforced. This option does not affect the normal operation of the router when a source tree join-prune message is received.
The default is disabled, which means that the software can switch over to source trees.
Note In ASM mode, only the last-hop router switches from the shared tree to the SPT.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim use-shared-tree-only [ip-prefix]
3. show ip pim group-range [ip-prefix] [vrf vrf-name | all]
4. copy running-config startup-config
PIM6 Commands
1. config t
2. ipv6 pim use-shared-tree-only [ipv6-prefix]
3. show ipv6 pim group-range [ipv6-prefix] [vrf vrf-name | all]
4. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim use-shared-tree-only [ip-prefix]
Example:
switch(config)# ip pim
use-shared-tree-only
|
Builds only shared trees, which means that the software never switches over from the shared tree to the SPT. You can specify an optional range of groups. By default, the software triggers a PIM (S, G) join toward the source when it receives multicast packets for a source for which it has the (*, G) state.
|
Step 3
|
show ip pim group-range [ip-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ip pim group-range
|
(Optional) Displays PIM modes and group ranges.
|
Step 4
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ipv6 pim use-shared-tree-only
[ipv6-prefix]
Example:
switch(config)# ipv6 pim
use-shared-tree-only
|
Builds only shared trees, which means that the software never builds source trees. You can specify an optional range of groups. By default, the software triggers a PIM (S, G) join toward the source when it receives multicast packets for a source for which it has the (*, G) state.
|
Step 3
|
show ipv6 pim group-range [ipv6-prefix]
[vrf vrf-name | all]
Example:
switch(config)# show ipv6 pim
group-range
|
(Optional) Displays PIM6 modes and group ranges.
|
Step 4
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Configuring SSM
Source-Specific Multicast (SSM) is a multicast distribution mode where the software on the DR connected to a receiver that is requesting data for a multicast source builds a shortest path tree (SPT) to that source.
On an IPv4 network, a host can request multicast data for a specific source only if it is running IGMPv3 and the DR for that host is running IGMPv3. You will usually enable IGMPv3 when you configure an interface for PIM in the SSM mode. For hosts running IGMPv1 or IGMPv2, you can configure group to source mapping using SSM translation. For more information, see Chapter 2, "Configuring IGMP and MLD."
You can configure the group range that is used by SSM. By default, the SSM group range for PIM is 232.0.0.0/8 and for PIM6 is FF3x/96.
Note If you want to use the default SSM group range, you do not need to configure the SSM group range.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim ssm range ip-prefix
3. ip pim ssm policy policy-name
4. show ip pim group-range [ip-prefix] [vrf vrf-name | all]
5. copy running-config startup-config
PIM6 Commands
1. config t
2. ipv6 pim ssm range ipv6-prefix
3. ipv6 pim ssm policy policy-name
4. show ipv6 pim group-range [ipv6-prefix] [vrf vrf-name | all]
5. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim ssm range ip-prefix
Example:
switch(config)# ip pim ssm range
239.128.1.0/24
|
Configures a group range to be treated in SSM mode. The default range is 232.0.0.0/8.
|
Step 3
|
ip pim ssm policy policy-name
Example:
switch(config)# ip pim ssm policy
my_pim_ssm_policy
|
Configures a group range defined in a policy to be treated in SSM mode. The default range is 232.0.0.0/8.
|
Step 4
|
show ip pim group-range [ip-prefix] [vrf
vrf-name | all]
Example:
switch(config)# show ip pim group-range
|
(Optional) Displays PIM modes and group ranges.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ipv6 pim ssm range ipv6-prefix
Example:
switch(config)# ipv6 pim ssm range
FF30::0/32
|
Configures a group range to be treated in SSM mode. The default range is FF3x/96.
|
Step 3
|
ipv6 pim ssm policy policy-name
Example:
switch(config)# ipv6 pim ssm policy
my_pim6_ssm_policy
|
Configures a group range defined in a policy to be treated in SSM mode. The default range is FF3x/96.
|
Step 4
|
show ipv6 pim group-range [ipv6-prefix]
[vrf vrf-name | all]
Example:
switch(config)# show ipv6 pim
group-range
|
(Optional) Displays PIM6 modes and group ranges.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
Configuring RPF Routes for Multicast
You can define RPF routes for multicast when you want multicast data to diverge from the unicast traffic path. You can define RPF routes for multicast on border routers to enable reverse path forwarding (RPF) to an external network.
Multicast routes are used not to directly forward traffic but to make RPF checks. RPF routes for multicast cannot be redistributed. For more information about multicast forwarding, see the "Multicast Forwarding" section on page 1-5.
Note IPv6 static multicast routes are not supported.
SUMMARY STEPS
PIM Commands
1. config t
2. ip mroute {ip-addr mask | ip-prefix} {next-hop | nh-prefix | interface} [route-preference] [vrf vrf-name]
3. show ip static-route [multicast] [vrf vrf-name]
4. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip mroute {ip-addr mask | ip-prefix}
{next-hop | nh-prefix | interface}
[route-preference] [vrf vrf-name]
Example:
switch(config)# ip mroute 192.0.2.33/1
224.0.0.0/1
|
Configures an RPF route for multicast for use in RPF calculations. Route preference values range from 1 to 255. The default preference is 1.
|
Step 3
|
show ip static-route [multicast] [vrf
vrf-name]
Example:
switch(config)# show ip static-route
multicast
|
(Optional) Displays configured static routes.
|
Step 4
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Configuring Route Maps to Control RP Information Distribution
You can configure route maps to help protect against some RP configuration errors and malicious attacks. You use route maps in commands that are described in the "Configuring Message Filtering" section.
By configuring route maps, you can control distribution of RP information that is distributed throughout the network. You specify the BSRs or mapping agents to be listened to on each client router and the list of candidate RPs to be advertised (listened to) on each BSR and mapping agent to ensure that what is advertised is what you expect.
Note Only the match ip [v6] multicast command has an effect in the route map.
SUMMARY STEPS
PIM Commands
1. config t
2. route-map map-name [permit | deny] [sequence-number]
3. match ip multicast {{rp ip-address [rp-type rp-type] [group ip-prefix]} | {group ip-prefix [rp ip-address [rp-type rp-type]]}
4. show route-map
5. copy running-config startup-config
PIM6 Commands
1. config t
2. route-map map-name [permit | deny] [sequence-number]
3. match ipv6 multicast {{rp ipv6-address [rp-type rp-type] [group ipv6-prefix]} | {group ipv6-prefix [rp ipv6-address [rp-type rp-type]]}
4. show route-map
5. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
route-map map-name [permit | deny]
[sequence-number]
Example for ASM only:
switch(config)# route-map ASM_only
permit 10
switch(config-route-map)#
Example for Bidir only:
switch(config)# route-map Bidir_only
permit 10
switch(config-route-map)#
|
Enters route-map configuration mode. This configuration method uses the permit keyword.
|
Step 3
|
match ip multicast {{rp ip-address
[rp-type rp-type] [group ip-prefix]} |
{group ip-prefix [rp ip-address [rp-type
rp-type]]}
Example for ASM only:
switch(config)# match ip multicast group
224.0.0.0/4 rp 0.0.0.0/0 rp-type ASM
Example for Bidir only:
switch(config)# match ip multicast group
224.0.0.0/4 rp 0.0.0.0/0 rp-type Bidir
|
Matches the group, RP, and RP type specified. You can specify the RP type (ASM or Bidir). This configuration method requires the group and RP specified as shown in the examples.
|
Step 4
|
show route-map
Example:
switch(config-route-map)# show route-map
|
(Optional) Displays configured route maps.
|
Step 5
|
copy running-config startup-config
Example:
switch(config-route-map)# copy
running-config startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
route-map map-name [permit | deny]
[sequence-number]
Example for ASM only:
switch(config)# route-map ASM_only
permit 10
switch(config-route-map)#
Example for Bidir only:
switch(config)# route-map Bidir_only
permit 10
switch(config-route-map)#
|
Enters route-map configuration mode. This configuration method uses the permit keyword.
|
Step 3
|
match ipv6 multicast {{rp ipv6-address
[rp-type rp-type] [group ipv6-prefix]} |
{group ipv6-prefix [rp ipv6-address
[rp-type rp-type]]}
Example for ASM only:
switch(config)# match ipv6 multicast
group ff0e::2:101:0:0/96 rp
2001::0348:0:0/96 rp-type ASM
Example for Bidir only:
switch(config)# match ipv6 multicast
group ff0e::2:101:0:0/96 rp
2001::0348:0:0/96 rp-type Bidir
|
Matches the group, RP, and RP type specified. You can specify the RP type (ASM or Bidir). This configuration method requires the group and RP specified as shown in the examples.
|
Step 4
|
show route-map
Example:
switch(config-route-map)# show route-map
|
(Optional) Displays configured route maps.
|
Step 5
|
copy running-config startup-config
Example:
switch(config-route-map)# copy
running-config startup-config
|
(Optional) Saves configuration changes.
|
Configuring Message Filtering
You can configure filtering of the PIM and PIM6 messages described in Table 3-7.
Table 3-7 PIM and PIM6 Message Filtering
Message Type
|
Description
|
Global to the device
|
Log Neighbor changes
|
Enables syslog messages that list the neighbor state changes to be generated. The default is disabled.
|
PIM register policy
|
Enables PIM register messages to be filtered based on a routing-rules policy1 where you can specify source and group addresses. This policy applies to routers that act as an RP. The default is disabled, which means that the software does not filter PIM register messages.
|
BSR candidate RP policy
|
Enables BSR candidate RP messages to be filtered by the router based on a routing-rules policy1 where you can specify the RP, group addresses, and whether the type is Bidir or ASM. This command can be used on routers that are eligible for BSR election. The default is no filtering of BSR messages.
|
BSR policy
|
Enables BSR messages to be filtered by the BSR client routers based on a routing-rules policy1 where you can specify BSR addresses. This command can be used on client routers that listen to BSR messages. The default is no filtering of BSR messages.
|
Auto-RP candidate RP policy
|
Enables Auto-RP announce messages to be filtered by the Auto-RP mapping agents based on a routing-rules policy1 where you can specify the RP, group addresses, and whether the type is Bidir or ASM. This command can be used on a mapping agent. The default is no filtering of Auto-RP messages.
Note PIM6 does not support the Auto-RP method.
|
Auto-RP mapping agent policy
|
Enables Auto-RP discover messages to be filtered by client routers based on a routing-rules policy1 where you can specify mapping agent addresses. This command can be used on client routers that listen to discover messages. The default is no filtering of Auto-RP messages.
Note PIM6 does not support the Auto-RP method.
|
Per device interface
|
Join-prune policy
|
Enables join-prune messages to be filtered based on a routing-rules policy1 where you can specify source and group addresses. The default is no filtering of join-prune messages.
|
For information about configuring route maps, see the "Configuring Route Maps to Control RP Information Distribution" section.
SUMMARY STEPS
PIM Commands
1. config t
2. ip pim log-neighbor-changes
3. ip pim register-policy policy-name
4. ip pim bsr rp-candidate-policy policy-name
5. ip pim bsr bsr-policy policy-name
6. ip pim auto-rp rp-candidate-policy policy-name
7. ip pim auto-rp mapping-agent-policy policy-name
8. interface interface
9. ip pim jp-policy policy-name
10. show run pim
11. copy running-config startup-config
PIM6 Commands
1. config t
2. ipv6 pim log-neighbor-changes
3. ipv6 pim register-policy policy-name
4. ipv6 pim bsr rp-candidate-policy policy-name
5. ipv6 pim bsr bsr-policy policy-name
6. interface interface
7. ipv6 pim jp-policy policy-name
8. show run pim6
9. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim log-neighbor-changes
Example:
switch(config)# ip pim
log-neighbor-changes
|
(Optional) Enables syslog messages that list the neighbor state changes to be generated. The default is disabled.
|
Step 3
|
ip pim register-policy policy-name
Example:
switch(config)# ip pim register-policy
my_register_policy
|
(Optional) Enables PIM register messages to be filtered based on a routing-rules policy.
|
Step 4
|
ip pim bsr rp-candidate-policy
policy-name
Example:
switch(config)# ip pim bsr
rp-candidate-policy
my_bsr_rp_candidate_policy
|
(Optional) Enables BSR candidate RP messages to be filtered by the router based on a routing-rules policy where you can specify the RP, group addresses, and whether the type is Bidir or ASM. This command can be used on routers that are eligible for BSR election. The default is no filtering of BSR messages.
|
Step 5
|
ip pim bsr bsr-policy policy-name
Example:
switch(config)# ip pim bsr bsr-policy
my_bsr_policy
|
(Optional) Enables BSR messages to be filtered by the BSR client routers based on a routing-rules policy where you can specify BSR addresses. This command can be used on client routers that listen to BSR messages. The default is no filtering of BSR messages.
|
Step 6
|
ip pim auto-rp rp-candidate-policy
policy-name
Example:
switch(config)# ip pim auto-rp
rp-candidate-policy
my_auto_rp_candidate_policy
|
(Optional) Enables Auto-RP announce messages to be filtered by the Auto-RP mapping agents based on a routing-rules policy where you can specify the RP, group addresses, and whether the type is Bidir or ASM. This command can be used on a mapping agent. The default is no filtering of Auto-RP messages.
|
Step 7
|
ip pim auto-rp mapping-agent-policy
policy-name
Example:
switch(config)# ip pim auto-rp
mapping-agent-policy
my_auto_rp_mapping_policy
|
(Optional) Enables Auto-RP discover messages to be filtered by client routers based on a routing-rules policy where you can specify mapping agent addresses. This command can be used on client routers that listen to discover messages. The default is no filtering of Auto-RP messages.
|
Step 8
|
interface interface
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface mode on the specified interface.
|
Step 9
|
ip pim jp-policy policy-name
Example:
switch(config-if)# ip pim jp-policy
my_jp_policy
|
(Optional) Enables join-prune messages to be filtered based on a routing-rules policy. The default is no filtering of join-prune messages.
|
Step 10
|
show run pim
Example:
switch(config-if)# show run pim
|
(Optional) Displays PIM configuration commands.
|
Step 11
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
| |
Command
|
Purpose
|
Step 1
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ipv6 pim log-neighbor-changes
Example:
switch(config)# ipv6 pim
log-neighbor-changes
|
(Optional) Enables syslog messages that list the neighbor state changes to be generated. The default is disabled.
|
Step 3
|
ipv6 pim register-policy policy-name
Example:
switch(config)# ipv6 pim register-policy
my_register_policy
|
(Optional) Enables PIM register messages to be filtered based on a routing-rules policy. The default is disabled.
|
Step 4
|
ipv6 pim bsr rp-candidate-policy
policy-name
Example:
switch(config)# ipv6 pim bsr
rp-candidate-policy
my_bsr_rp_candidate_policy
|
(Optional) Enables BSR candidate RP messages to be filtered by the router based on a routing-rules policy where you can specify the RP, group addresses, and whether the type is Bidir or ASM. This command can be used on routers that are eligible for BSR election. The default is no filtering of BSR messages.
|
Step 5
|
ipv6 pim bsr bsr-policy policy-name
Example:
switch(config)# ipv6 pim bsr bsr-policy
my_bsr_policy
|
(Optional) Enables BSR messages to be filtered by the BSR client routers based on a routing-rules policy1 where you can specify BSR addresses. This command can be used on client routers that listen to BSR messages. The default is no filtering of BSR messages.
|
Step 6
|
interface interface
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface mode on the specified interface.
|
Step 7
|
ipv6 pim jp-policy policy-name
Example:
switch(config-if)# ipv6 pim jp-policy
my_jp_policy
|
(Optional) Enables join-prune messages to be filtered based on a routing-rules policy. The default is no filtering of join-prune messages.
|
Step 8
|
show run pim6
Example:
switch(config-if)# show run pim6
|
(Optional) Displays PIM6 configuration commands.
|
Step 9
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Restarting the PIM and PIM6 Processes
You can restart the PIM and PIM6 processes and optionally flush all routes. By default, routes are not flushed.
When routes are flushed, they are removed from the Multicast Routing Information Base (MRIB and M6RIB) and the Multicast Forwarding Information Base (MFIB and M6FIB).
When you restart PIM or PIM6, the following tasks are performed:
•The PIM database is deleted.
•The MRIB and MFIB are unaffected and forwarding of traffic continues.
•The multicast route ownership is verified through the MRIB.
•Periodic PIM join and prune messages from neighbors are used to repopulate the database.
SUMMARY STEPS
PIM Commands
1. restart pim
2. config t
3. ip pim flush-routes
4. show running-config | include flush-routes
5. copy running-config startup-config
PIM6 Commands
1. restart pim6
2. config t
3. ipv6 pim flush-routes
4. show running-config | include flush-routes
5. copy running-config startup-config
DETAILED STEPS
PIM Commands
| |
Command
|
Purpose
|
Step 1
|
restart pim
Example:
switch# restart pim
|
Restarts the PIM process.
|
Step 2
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 3
|
ip pim flush-routes
Example:
switch(config)# ip pim flush-routes
|
Removes routes when the PIM process is restarted. By default, routes are not flushed.
|
Step 4
|
show running-config | include
flush-routes
Example:
switch(config)# show running-config |
include flush-routes
|
(Optional) Shows flush-routes configuration lines in the running configuration.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
PIM6 Commands
| |
Command
|
Purpose
|
Step 1
|
restart pim6
Example:
switch# restart pim6
|
Restarts the PIM6 process.
|
Step 2
|
config t
Example:
switch# config t
switch(config)#
|
Enters configuration mode.
|
Step 3
|
ipv6 pim flush-routes
Example:
switch(config)# ipv6 pim flush-routes
|
Removes routes when the PIM6 process is restarted. By default, routes are not flushed.
|
Step 4
|
show running-config | include
flush-routes
Example:
switch(config)# show running-config |
include flush-routes
|
(Optional) Shows flush-routes configuration lines in the running configuration.
|
Step 5
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves configuration changes.
|
Verifying PIM and PIM6
You can verify the PIM and PIM6 configurations using the commands listed in Table 3-8. Use the show ip form of the command for PIM and the show ipv6 form of the command for PIM6.
Table 3-8 PIM show Commands
Command
|
Description
|
show ip [v6] mroute {source group | group [source]} [vrf vrf-name | all]
|
Displays the IP or IPv6 multicast routing table.
|
show ip [v6] pim df [vrf vrf-name | all]
|
Displays the designated forwarder (DF) information for each RP by interface.
|
show ip [v6] pim group-range [vrf vrf-name | all]
|
Displays the learned or configured group ranges and modes. For similar information, see also the show ip pim rp command.
|
show ip [v6] pim interface [interface | brief] [vrf vrf-name | all]
|
Displays information by the interface.
|
show ip [v6] pim neighbor [vrf vrf-name | all]
|
Displays neighbors by the interface.
|
show ip [v6] pim oif-list group [source] [vrf vrf-name | all]
|
Displays all the interfaces in the OIF-list.
|
show ip [v6] pim route {source group | group [source]} [vrf vrf-name | all]
|
Displays information for each multicast route, including interfaces on which a PIM join for that (S, G) has been received.
|
show ip [v6] pim rp [vrf vrf-name | all]
|
Displays rendezvous points (RPs) known to the software, how they were learned, and their group ranges. For similar information, see also the show ip pim group-range command.
|
show ip [v6] pim rp-hash [vrf vrf-name | all]
|
Displays the bootstrap router (BSR) RP hash information. For information about the RP hash, see RFC 5059.
|
show ip [v6] pim vrf all [detail]
|
Displays per-VRF information.
|
For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Multicast Routing Command Reference, Release 4.0.
Displaying Statistics
You can display and clear PIM and PIM6 statistics by using the commands in this section.
This section has the following topics:
•Displaying PIM and PIM6 Statistics
•Clearing PIM and PIM6 Statistics
Displaying PIM and PIM6 Statistics
You can display the PIM and PIM6 statistics and memory usage using the commands listed in Table 3-9. Use the show ip form of the command for PIM and the show ipv6 form of the command for PIM6.
Table 3-9 Statistics Commands
Command
|
Description
|
show ip [v6] pim policy statistics
|
Displays policy statistics for Register, RP, and join-prune message policies.
|
show ip [v6] pim statistics [vrf vrf-name | all]
|
Displays global statistics.
|
For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Multicast Routing Command Reference, Release 4.0.
Clearing PIM and PIM6 Statistics
You can clear the PIM and PIM6 statistics using the commands listed in Table 3-10. Use the show ip form of the command for PIM and the show ipv6 form of the command for PIM6.
Table 3-10 Commands to Clear Statistics
Command
|
Description
|
clear ip [v6] pim interface statistics interface
|
Clears counters for the specified interface.
|
clear ip [v6] pim policy statistics
|
Clears policy counters for Register, RP, and join-prune message policies.
|
clear ip [v6] pim statistics [vrf vrf-name | all]
|
Clears global counters handled by the PIM process.
|
PIM Configuration Examples
This section describes how to configure PIM using different data distribution modes and RP selection methods.
This section includes the following topics:
•SSM Configuration Example
•BSR Configuration Example
•Auto-RP Configuration Example
•PIM Anycast-RP Configuration Example
SSM Configuration Example
To configure PIM in SSM mode, follow these steps for each router in the PIM domain:
Step 1 Configure PIM sparse mode parameters on the interfaces that you want to participate in the domain. We recommend that you enable PIM on all interfaces.
switch(config)# interface ethernet 2/1
switch(config-if)# ip pim sparse-mode
Step 2 Configure the parameters for IGMP that support SSM. See Chapter 2, "Configuring IGMP and MLD." Usually, you configure IGMPv3 on PIM interfaces to support SSM.
switch(config)# interface ethernet 2/1
switch(config-if)# ip igmp version 3
Step 3 Configure the SSM range if you do not want to use the default range.
switch(config)# ip pim ssm range 239.128.1.0/24
Step 4 Configure message filtering.
switch(config)# ip pim log-neighbor-changes
The following example shows how to configure PIM SSM mode:
ip pim ssm range 239.128.1.0/24
ip pim log-neighbor-changes
BSR Configuration Example
To configure PIM in ASM mode using the BSR mechanism, follow these steps for each router in the PIM domain:
Step 1 Configure PIM sparse mode parameters on the interfaces that you want to participate in the domain. We recommend that you enable PIM on all interfaces.
switch(config)# interface ethernet 2/1
switch(config-if)# ip pim sparse-mode
Step 2 Configure whether that router should listen and forward BSR messages.
switch(config)# ip pim bsr forward listen
Step 3 Configure the BSR parameters for each router that you want to act as a BSR.
switch(config)# ip pim bsr-candidate ethernet 2/1 hash-len 30
Step 4 Configure the RP parameters for each router that you want to act as a candidate RP.
switch(config)# ip pim rp-candidate ethernet 2/1 group-list 239.0.0.0/24
Step 5 Configure message filtering.
switch(config)# ip pim log-neighbor-changes
The following example shows how to configure PIM ASM mode using the BSR mechanism and how to configure the BSR and RP on the same router:
ip pim bsr forward listen
ip pim bsr-candidate ethernet 2/1 hash-len 30
ip pim rp-candidate ethernet 2/1 group-list 239.0.0.0/24
ip pim log-neighbor-changes
Auto-RP Configuration Example
To configure PIM in Bidir mode using the Auto-RP mechanism, follow these steps for each router in the PIM domain:
Step 1 Configure PIM sparse mode parameters on the interfaces that you want to participate in the domain. We recommend that you enable PIM on all interfaces.
switch(config)# interface ethernet 2/1
switch(config-if)# ip pim sparse-mode
Step 2 Configure whether that router should listen and forward Auto-RP messages.
switch(config)# ip pim auto-rp forward listen
Step 3 Configure the mapping agent parameters for each router that you want to act as a mapping agent.
switch(config)# ip pim auto-rp mapping-agent ethernet 2/1
Step 4 Configure the RP parameters for each router that you want to act as a candidate RP.
switch(config)# ip pim auto-rp rp-candidate ethernet 2/1 group-list 239.0.0.0/24 bidir
Step 5 Configure message filtering.
switch(config)# ip pim log-neighbor-changes
The following example shows how to configure PIM Bidir mode using the Auto-RP mechanism and how to configure the mapping agent and RP on the same router:
ip pim auto-rp mapping-agent ethernet 2/1
ip pim auto-rp rp-candidate ethernet 2/1 group-list 239.0.0.0/24 bidir
ip pim log-neighbor-changes
PIM Anycast-RP Configuration Example
To configure ASM mode using the PIM Anycast-RP method, follow these steps for each router in the PIM domain:
Step 1 Configure PIM sparse mode parameters on the interfaces that you want to participate in the domain. We recommend that you enable PIM on all interfaces.
switch(config)# interface ethernet 2/1
switch(config-if)# ip pim sparse-mode
Step 2 Configure the RP address that you configure on all routers in the Anycast-RP set.
switch(config)# interface loopback 0
switch(config-if)# ip address 192.0.2.3/32
Step 3 Configure a loopback with an address to use in communication between routers in the Anycast-RP set for each router that you want to be in the Anycast-RP set.
switch(config)# interface loopback 1
switch(config-if)# ip address 192.0.2.31/32
Step 4 Configure the Anycast-RP parameters and repeat with the IP address of each Anycast-RP for each router that you want to be in the Anycast-RP set. This example shows two Anycast-RPs.
switch(config)# ip pim anycast-rp 192.0.2.3 193.0.2.31
switch(config)# ip pim anycast-rp 192.0.2.3 193.0.2.32
Step 5 Configure message filtering.
switch(config)# ip pim log-neighbor-changes
The following example shows how to configure PIM ASM mode using two Anycast-RPs:
ip pim anycast-rp 192.0.2.3 192.0.2.31
ip pim anycast-rp 192.0.2.3 192.0.2.32
ip pim log-neighbor-changes
Where to Go Next
You can configure the following features that work with PIM or PIM6:
•Chapter 2, "Configuring IGMP and MLD"
•Chapter 4, "Configuring IGMP Snooping"
•Chapter 5, "Configuring MSDP"
Default Settings
Table 3-11 lists the default settings for PIM and PIM6 parameters.
Table 3-11 Default PIM and PIM6 Parameters
Parameters
|
Default
|
Use shared trees only
|
Disabled
|
Flush routes on restart
|
Disabled
|
Log Neighbor changes
|
Disabled
|
Auto-RP message action
|
Disabled
|
BSR message action
|
Disabled
|
SSM multicast group range or policy
|
232.0.0.0/8 for IPv4 and FF3x::/96 for IPv6
|
PIM sparse mode
|
Disabled
|
Designated router priority
|
0
|
Hello authentication mode
|
Disabled
|
Domain border
|
Disabled
|
RP address policy
|
No message filtering
|
PIM register message policy
|
No message filtering
|
BSR candidate RP policy
|
No message filtering
|
BSR policy
|
No message filtering
|
Auto-RP mapping agent policy
|
No message filtering
|
Auto-RP RP candidate policy
|
No message filtering
|
Join-prune policy
|
No message filtering
|
Neighbor adjacency policy
|
Become adjacent with all PIM neighbors
|
Additional References
For additional information related to implementing PIM, see the following sections:
•Related Documents
•Standards
•Appendix A, "IETF RFCs"
•Technical Assistance
Related Documents
Related Topic
|
Document Title
|
PIM Bidir
|
draft-ietf-pim-bidir-09.txt
|
VDCs
|
Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 4.0
|
CLI commands
|
Cisco Nexus 7000 Series NX-OS Multicast Routing Command Reference, Release 4.0
|
Configuring VRFs and Policy Based Routing
|
Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 4.0
|
Standards
Standards
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
Technical Assistance
Description
|
Link
|
Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/public/support/tac/home.shtml
|
