- Information About PIM and PIM6
- Licensing Requirements for PIM and PIM6
- Prerequisites for PIM and PIM6
- Guidelines and Limitations for PIM and PIM6
- Default Settings
- Configuring PIM and PIM6
- 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
- Configuring BFD for PIM
- Verifying the PIM and PIM6 Configuration
- Displaying Statistics
- Configuration Examples for PIM
Configuring PIM and PIM6
This chapter describes how to configure the Protocol Independent Multicast (PIM) and PIM6 features on Cisco NX-OS devices 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
- Default Settings
- Configuring PIM and PIM6
- Verifying the PIM and PIM6 Configuration
- Displaying Statistics
- Configuration Examples for PIM
- Where to Go Next
- Additional References
- Feature History for PIM and PIM6
Information About PIM and PIM6
Note Beginning with Cisco NX-OS Release 5.0(2a), Bidirectional Forwarding Detection (BFD) supports PIM. See the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x, for information on BFD.
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.
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 1, “Configuring IGMP” and Chapter1, “Configuring MLD”
Note Beginning with Cisco NX-OS Release 5.2(1) for the Nexus 7000 Series devices, you can configure PIMv4 to run over generic routing encapsulation (GRE) tunnels including outgoing interfaces (OIFs).
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 shared 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
- Bidirectional Forwarding Detection for PIM
- 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, 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.
The hello message also contains a hold-time value, which is typically 3.5 times the hello interval. If this hold time expires without a subsequent hello message from its neighbor, the device detects a PIM failure on that link.
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.
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:
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.
Figure 1-1 shows 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.
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.
Figure 1-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).
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.
Multiple RPs Configured in a PIM Domain
This section describes the election process rules when multiple RPs are configured in a PIM domain and includes the following topics:
PIM BSR Bootstrap/Auto-RP Mapping-Agent Election Process
This section includes the following topics:
If the BSR priorities are different, the BSR with the highest priority (highest numerical value) is elected as the BSR router for the PIM domain (see configuration example 1).
- Configuration example 1—Different BSR-candidate priorities: In this example, the system elects the device labeled N7K-1 as the BSR candidate for the PIM domain because it has the highest priority. The device labeled N7K-2 has the default priority of 64.
If the BSR priorities are the same, the BSR with the highest BSR-candidate IP address is elected as the BSR router for the PIM domain (see configuration example 2).
- Configuration example 2—Identical BSR-candidate priorities: In this example, the system elects the device labeled N7K-2 as the BSR for the PIM domain because it has the highest BSR-candidate IP address.
The router with the highest mapping-agent IP address is elected as the mapping agent for the PIM domain. You cannot configure the priority for the Auto-RP mapping agent (see configuration example):
PIM RP versus RP Election Process
Table 1-1 shows the process that the system uses to select the RP for a multicast group if multiple RPs are configured in the network using BSR, Auto-RP, or static RP configurations.
Table 1-1 PIM RP Versus RP Election Process Summary Table
Note BSR-RP versus Auto-RP is not listed in Table 1-1 because we recommend that you do not run both simultaneously in the same network.
This section includes the following topics:
- PIM BSR RP-Candidate vs. BSR RP-Candidate Election Process
- PIM BSR RP-Candidate vs. Static RP Election Process
- PIM Auto-RP-Candidate vs. Auto-RP-Candidate Election Process
- PIM Auto-RP-Candidate vs. Static RP Election Process
The BSR RP-candidate with the most specific group-list is elected as the RP for any multicast addresses specified in its configured group list. The most specific group list takes priority over the BSR RP-candidate priority and the highest BSR RP-candidate IP address (see configuration example 1).
- Configuration example 1—Most specific group-list: In this example, the system elects the device labeled N7K-1 as the RP for all multicast addresses specified in the 224.1.1.0/24 group-list. The system elects the device labeled N7K-2 for the multicast addresses within the less specific 224.0.0.0/4 group-list.
When multiple BSR RP-candidates advertise the same group list (for example, 224.0.0.0/4), the system elects the BSR RP-candidate with the highest priority (lowest numerical value) as the RP for any multicast address specified in its group-list (see configuration example 2).
- Configuration example 2—Identical group-list with different RP priorities: In this example, the system elects the device labeled N7K-1 as the RP for all multicast addresses specified in the 224.0.0.0/4 group-list because it has the lowest RP-candidate priority. The device labeled N7K-2 has a default priority of 192.
When multiple BSR RP-candidates advertise the same group list (for example, 224.0.0.0/4) and are configured with the same BSR RP-candidate priority, the system elects the BSR RP-candidate with the highest IP address as the RP for any multicast address specified in its group list (see configuration example 3).
- Configuration example 3—Identical group list with identical RP priorities: In this example, the system elects the device labeled N7K-2 as the RP for all multicast addresses specified in the 224.0.0.0/4 group list because it has the highest RP-candidate IP address.
The RP with the most specific group list is elected as the RP for any multicast addresses specified in its configured group list. The most specific group list takes priority over the highest RP IP address (see configuration example 1). (RP priorities are not applicable when comparing BSR RP-candidates to static RPs.)
- Configuration example 1—Most specific group list: In this example, the system elects the device labeled N7K-1 as the BSR RP for all multicast addresses specified in the 224.1.1.0/24 group-list. The system elects the device labeled N7K-2 as the RP for the multicast addresses within the less specific 224.0.0.0/4 group list because of the static RP statement.
When a static RP and the BSR RP-candidate advertise the same group list (for example, 224.0.0.0/4), the system elects the system with the highest RP IP address as the RP for any multicast addresses specified in its group-list (see configuration example 2).
- Configuration example 2—Identical RP group list: In this example, the system elects the device labeled N7K-2 as the RP for all multicast addresses specified in the 224.0.0.0/4 group list because it has the highest RP IP address.
Because you cannot configure a static RP and its default value is 0, the RP priority has no impact. You can configure the BSR RP-candidate with a value between 0 and 255. The system elects the device with the most specific group list. If both devices have the same group list, the system elects the device with the highest RP IP address (see configuration example 3).
- Configuration example 3—Identical group list and identical RP priorities: In this example, the system elects the device labeled N7K-2 as the RP for all multicast addresses specified in the 224.0.0.0/4 group list because it has the highest RP IP address. The system does not compare RP priorities between BSR RPs and static RPs.
The auto-RP-candidate election is similar to the BSR RP-candidate election process, but it does not support priorities (see the “PIM BSR RP-Candidate vs. BSR RP-Candidate Election Process” section). You cannot configure the priority for an auto-RP, and the default value is 0.
The auto-RP-candidate versus static RP election uses the same rules as the election process for the BSR RP-candidate versus static RP (see “PIM BSR RP-Candidate vs. Static RP Election Process” 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.
You must configue PIM on the loopback interface that is used for the PIM Anycast 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.
You can use the ip pim register-source command to configure the IP source address of register messages when the IP source address of a register message is not a uniquely routed address to which the RP can send packets. This situation might occur if the source address is filtered so that the packets sent to it are not forwarded or if the source address is not unique to the network. In these cases, the replies sent from the RP to the source address will fail to reach the DR, resulting in Protocol Independent Multicast sparse mode (PIM-SM) protocol failures.
The following example shows how to configure the IP source address of the register message to the loopback 3 interface of a DR:
Note In Cisco 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.
Bidirectional Forwarding Detection for PIM
Beginning with Cisco NX-OS Release 5.0(2a), Bidirectional Forwarding Detection (BFD) allows the system to rapidly detect failures in a network. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x for more information about BFD.
In PIM, a link or neighbor group failure is detected when the hold-time, which is set as part of the hello interval, expires. However, BFD provides a more efficient method to detect a failure. This protocol establishes a session between the two endpoints over a link and uses the forwarding engine. When BFD is enabled, the PIM process attempts to add a BFD session as each neighbor is discovered. If a BFD session already exists, no duplicate is created but PIM receives a callback that contains the state of the BFD session. You can enable BFD for PIM per VRF or per interface.
PIM removes the BFD session when you disable BFD for that VRF or interface, the interface is no longer a PIM interface, or the neighboring BFD session goes down.
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.2 .
For information about configuring VRFs, see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x .
Licensing Requirements for PIM and PIM6
The following table shows the licensing requirements for this feature:
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
PIM and PIM6 have the following guidelines and limitations:
- Tunnel interfaces do not support PIM until Cisco NX-OS Release 5.2(1). Beginning with Release 5.2(1), you can configure multicast on GRE tunnel interfaces.
- Cisco NX-OS PIM and PIM6 do 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 do not receive the correct BSM.
- While using avirtual port channel (vPC) with dual supervisors, you must use the default timers as follows:
– While using dual supervisors where we recommend high default timer values; convergence will suffer on a link failure. If you want to perform ISSU or you want the system to do an SSO without any network reconvergence, you must specify higher default timer values.
– Beginning with Release 5.x, we recommend that you use BFD for PIM instead of nondefault timers.
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 1-3 .
To configure PIM and PIM6, follow these steps:
Step 1 From the multicast distribution modes described in Table 1-3 , 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
- Configuring BFD for PIM
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
4. (Optional) show running-configuration pim
DETAILED STEPS
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 1-4 .
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. |
|
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. |
|
Configures the number of Bidir RPs that you can configure for IPv4 and IPv6. The maximum number of Bidir RPs supported per VRF for PIM and PIM6 combined cannot exceed 8. Values range from 0 to 8. The default is 6 for IPv4 and 2 for IPv6. |
|
Configures the IPv4 or IPv6 register rate limit in packets per second. The range is from 1 to 65,535. The default is no limit. |
|
Configures the IPv4 or IPv6 initial holddown period in seconds. This holddown period is the time it takes for the MRIB to come up initially. If you want faster convergence, enter a lower value. The range is from 90 to 210. Specify 0 to disable the holddown period. The default is 210. |
|
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. |
|
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:
The authentication key can be up to 16 characters. The default is disabled. |
|
Configures the interval at which hello messages are sent in milliseconds. The range is from 1 to 4294967295. The default is 30000. |
|
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. |
|
Configures which PIM neighbors to become adjacent to based on a route-map policy 1 where you can specify IP addresses to become adjacent to with the match ip [ v6 ] address command. If the policy name does not exist, or no IP addresses are configured in a policy, 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. |
|
For information about configuring multicast route maps, see the “Configuring Route Maps to Control RP Information Distribution” section.
Note To configure the join-prune policy, see the “Configuring Message Filtering” section.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. (Optional) ip pim auto-rp { listen [ forward ] | forward [ listen ]}
3. (Optional) ip pim bsr { listen [ forward ] | forward [ listen ]}
4. (Optional) show ip pim rp [ ip-prefix ] [ vrf vrf-name | all ]
5. (Optional) ip pim bidir-rp-limit limit
6. (Optional) ip pim register-rate-limit rate
7. (Optional) [ ip | ipv4 ] routing multicast holddown holddown-period
8. show running-configuration pim
11. (Optional) ip pim dr-priority priority
12. (Optional) ip pim hello-authentication ah-md5 auth-key
13. (Optional) ip pim hello-interval interval
15. (Optional) ip pim neighbor-policy policy-name
16. (Optional) show ip pim interface [ interface | brief ] [ vrf vrf-name | all ]
17. (Optional) copy running-config startup-config
2. (Optional) ipv6 pim bsr { listen [ forward ] | forward [ listen ]}
3. (Optional) show ipv6 pim rp [ ipv6-prefix ] [ vrf vrf-name | all ]
4. (Optional) ipv6 pim bidir-rp-limit limit
5. (Optional) ipv6 pim register-rate-limit rate
6. (Optional) ipv6 routing multicast holddown holddown-period
7. show running-configuration pim6
10. (Optional) ipv6 pim dr-priority priority
11. (Optional) ipv6 pim hello-interval interval
12. (Optional) ipv6 pim border
13. (Optional) ipv6 pim neighbor-policy policy-name
14. (Optional) show ipv6 pim interface [ interface | brief ] [ vrf vrf-name | all ]
DETAILED STEPS
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, Release 5.x.
Configuring Static RPs
You can configure an RP statically by configuring the RP address on every router that will participate 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 prefix-list method of configuration in addition to existing route-map method.
- Added support for policy actions (route-map or prefix-list).
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.
The following example configuration produce the same output using Cisco NX-OS (231.1.1.0/24 is always denied irrespective of the sequence number):
This behavior differs from Cisco IOS. See the Cisco Nexus 7000 Series NX-OS Multicast Routing Command Reference, Release 5.x , behavior for more samples for the ip pim rp-address command.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. ip pim rp-address rp-address [ group-list ip-prefix | route-map policy-name ] [ bidir ]
3. (Optional) show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ]
4. (Optional) copy running-config startup-config
2. ipv6 pim rp-address rp-address [ group-list ipv6-prefix | route-map policy-name ] [ bidir ]
3. (Optional) show ipv6 pim group-range [ ipv6-prefix ] [ vrf vrf-name | all ]
DETAILED STEPS
Configuring BSRs
You configure BSRs by selecting candidate BSRs and RPs.
You can configure a candidate BSR with the arguments described in Table 1-5 .
You can configure a candidate RP with the arguments and keywords described in Table 1-6 .
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.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
3. ip pim [ bsr ] bsr-candidate interface [ hash-len hash-length ] [ priority priority ]
4. ip pim [ bsr ] rp-candidate interface {group-list ip-prefix | route-map policy-name }[ priority priority ] [ interval interval ] [ bidir ]
5. (Optional) show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ]
6. (Optional) copy running-config startup-config
2. ipv6 pim [ bsr ] bsr-candidate interface [ hash-len hash-length ] [ priority priority ]
3. ipv6 pim [ bsr ] rp-candidate interface {group-list ipv6-prefix | route-map policy-name } [ priority priority ] [ interval interval ] [ bidir ]
4. (Optional) show ipv6 pim group-range [ ipv6-prefix ] [ vrf vrf-name | all ]
DETAILED STEPS
Configures listen and forward. Ensure that you have entered this command in each VRF on the remote PE. |
||
ip pim [ bsr ] bsr-candidate interface [ hash-len hash-length ] [ priority priority ] 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 1-5 . |
|
ip pim [ bsr ] rp-candidate interface { group-list ip-prefix | route-map policy-name } [ priority priority ] [ interval interval ] [ bidir ] switch(config)# ip pim rp-candidate ethernet 2/1 group-list 239.0.0.0/24 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. |
|
show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ] |
||
ipv6 pim [ bsr ] bsr-candidate interface [ hash-len hash-length ] [ priority priority ] 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 1-5 . |
|
ipv6 pim [ bsr ] rp-candidate interface { group-list ipv6-prefix | route-map policy-name } [ priority priority ] [ interval interval ] [ bidir ] switch(config)# ipv6 pim rp-candidate ethernet 2/1 group-list ff1e:abcd:def1::0/24 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 1-6 . |
|
show ipv6 pim group-range [ ipv6-prefix ] [ vrf vrf-name | all ] |
||
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.
You can configure an Auto-RP mapping agent with the arguments described in Table 1-7 .
Interface type and number used to derive the IP address of the Auto-RP mapping agent used in bootstrap messages. |
|
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 and keywords described in Table 1-8 .
Interface type and number used to derive the IP address of the candidate RP used in Bootstrap messages. |
|
Multicast groups handled by this RP. It is specified in a prefix format. |
|
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. |
|
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. |
|
If not specified, this RP will be in ASM mode. If specified, this RP will be in Bidir mode. |
|
Route-map policy name that defines the group prefixes where this feature is applied. |
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.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
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 | route-map policy-name } [ scope ttl ] [ interval interval ] [ bidir ]
4. (Optional) show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ]
DETAILED STEPS
ip pim { send-rp-discovery | { auto-rp mapping-agent }} interface [ scope ttl ] |
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 1-7 . |
|
ip pim {send-rp-announce | {auto-rp rp-candidate}} interface { group-list ip-prefix | route-map policy-name } [ scope ttl ] [ interval interval ] [ bidir ] switch(config)# ip pim auto-rp rp-candidate ethernet 2/1 group-list 239.0.0.0/24 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 1-8 . Note We recommend that you configure the candidate RP interval to a minimum of 15 seconds. |
|
show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ] |
||
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.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
5. ip pim anycast-rp anycast-rp-address anycast-rp-peer-address
6. Repeat Step 5 using the same anycast-rp for each RP in the RP set (including local router)
7. (Optional) show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ]
8. (Optional) copy running-config startup-config
5. ipv6 pim anycast-rp anycast-rp-address anycast-rp-peer-address
6. Repeat Step 5 using the same anycast-rp for each RP in the RP set (including local router)
7. (Optional) show ipv6 pim group-range [ ipv6-prefix ] [ vrf vrf-name | all ]
DETAILED STEPS
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 with the match ip [ v6 ] multicast command. This option does not affect the normal operation of the router when a source tree join-prune message is received.
Note The Cisco NX-OS software does not support the shared-tree feature on vPCs. For more information about vPCs, see the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x.
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.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. ip pim use-shared-tree-only group-list policy-name
3. (Optional) show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ]
4. (Optional) copy running-config startup-config
2. ipv6 pim use-shared-tree-only group-list policy-name
3. (Optional) show ipv6 pim group-range [ ipv6-prefix ] [ vrf vrf-name | all ]
DETAILED STEPS
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 a group to source mapping using SSM translation. For more information, see Chapter 1, “Configuring IGMP”and Chapter1, “Configuring MLD”
You can configure the group range that is used by SSM by specifying values on the command line. By default, the SSM group range for PIM is 232.0.0.0/8 and for PIM6 is FF3x/96.
You can specify a route-map policy name that lists the group prefixes to use with the match ip multicast command.
Note If you want to use the default SSM group range, you do not need to configure the SSM group range.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. ip pim ssm { range { ip-prefix | none } | route-map policy-name }
no ip pim ssm { range { ip-prefix | none } | route-map policy-name }
3. (Optional) show ip pim group-range [ ip-prefix ] [ vrf vrf-name | all ]
4. (Optional) copy running-config startup-config
2. ipv6 pim ssm { range { ipv6-prefix | none } | route-map policy-name }
no ipv6 pim ssm { range { ipv6-prefix | none } | route-map policy-name }
3. (Optional) show ipv6 pim group-range [ ipv6-prefix ] [ vrf vrf-name | all ]
DETAILED STEPS
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.
Note IPv6 static multicast routes are not supported.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. ip mroute { ip-addr mask | ip-prefix } { next-hop | nh-prefix | interface } [ route-preference ] [ vrf vrf-name ]
3. (Optional) show ip static-route [ multicast ] [ vrf vrf-name ]
DETAILED STEPS
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.
See the “Configuring BSRs” section and “Configuring Auto-RP” section for more information.
Note Only the match ip [v6] multicast command has an effect in the route map.
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. route-map map-name [ permit | deny ] [ sequence-number ]
3. match ip multicast {{ rp ip-address [ rp-type rp-type]} {{ group-range {gadrr_start to gadrr_end} | { group ip-prefix}} { source source-ip-address}
5. (Optional) copy running-config startup-config
2. route-map map-name [ permit | deny ] [ sequence-number ]
3. match ipv6 multicast {{ rp ip-address [ rp-type rp-type]} {{ group-range {gadrr_start to gadrr_end} | { group ip-prefix}} { source source-ip-address}
DETAILED STEPS
Configuring Message Filtering
Note Prefix matches in the rp-candidate-policy must be exact relative to what the c-rp is advertising. Subset matches are not possible.
You can configure filtering of the PIM and PIM6 messages described in Table 1-9 .
Enables syslog messages that list the neighbor state changes to be generated. The default is disabled. |
|
Enables PIM register messages to be filtered based on a route-map policy 2 where you can specify group or group and source addresses with the match ip [ v6 ] multicast command. 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. |
|
Enables BSR candidate RP messages to be filtered by the router based on a route-map policy 1 where you can specify the RP and group addresses and whether the type is Bidir or ASM with the match ip [ v6 ] multicast command. This command can be used on routers that are eligible for BSR election. The default is no filtering of BSR messages. |
|
Enables BSR messages to be filtered by the BSR client routers based on a route-map policy 1 where you can specify BSR source addresses with the match ip [ v6 ] multicast command. This command can be used on client routers that listen to BSR messages. The default is no filtering of BSR messages. |
|
Enables Auto-RP announce messages to be filtered by the Auto-RP mapping agents based on a route-map policy 1 where you can specify the RP and group addresses, and whether the type is Bidir or ASM with the match ip multicast command. This command can be used on a mapping agent. The default is no filtering of Auto-RP messages. |
|
Enables Auto-RP discover messages to be filtered by client routers based on a route-map policy 1 where you can specify mapping agent source addresses with the match ip multicast command. This command can be used on client routers that listen to discover messages. The default is no filtering of Auto-RP messages. |
|
Enables join-prune messages to be filtered based on a route-map policy 1 where you can specify group, group and source, or group and RP addresses with the match ip [ v6 ] multicast command. The default is no filtering of join-prune messages. |
|
For information about configuring multicast route maps, see the “Configuring Route Maps to Control RP Information Distribution” section.
Route maps as a filtering policy can be used (either permit or deny for each statement) for the following commands:
- jp-policy can use (S,G), (*,G), or (RP,G)
- register-policy can use (S,G) or (*,G)
- igmp report-policy can use (*,G) or (S,G)
- state-limit reserver-policy can use (*,G) or (S,G)
- auto-rp rp-candidate-policy can use (RP,G)
- bsr rp-candidate-policy can use (RP,G)
- autorp mapping-agent policy can use (S)
- bsr bsr-policy can use (S)
Route maps as containers can be use for the following commands, where route-map action ( permit or deny ) is ignored:
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
2. (Optional) ip pim log-neighbor-changes
3. (Optional) ip pim register-policy policy-name
4. (Optional) ip pim bsr rp-candidate-policy policy-name
5. (Optional) ip pim bsr bsr-policy policy-name
6. (Optional) ip pim auto-rp rp-candidate-policy policy-name
7. (Optional) ip pim auto-rp mapping-agent-policy policy-name
9. (Optional) ip pim jp-policy policy-name [ in | out ]
11. (Optional) copy running-config startup-config
2. (Optional) ipv6 pim log-neighbor-changes
3. (Optional) ipv6 pim register-policy policy-name
4. (Optional) ipv6 pim bsr rp-candidate-policy policy-name
5. (Optional) ipv6 pim bsr bsr-policy policy-name
DETAILED STEPS
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:
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license and enabled PIM or PIM6.
SUMMARY STEPS
4. (Optional) show running-configuration pim
5. (Optional) copy running-config startup-config
DETAILED STEPS
Removes routes when the PIM process is restarted. By default, routes are not flushed. |
||
(Optional) Displays the PIM running-configuration information, including the flush-routes command. |
||
BEFORE YOU BEGIN
Ensure that you have installed the Enterprise Services license, enabled PIM or PIM6, and enabled BFD.
DETAILED STEPS
Verifying the PIM and PIM6 Configuration
To display the PIM and PIM6 configurations information, perform one of the following tasks. Use the show ip form of the command for PIM and the show ipv6 form of the command for PIM6.
show ip [ v6 ] mroute { source group | group [ source ]} [ vrf vrf-name | all ] |
|
Displays the designated forwarder (DF) information for each RP by interface. |
|
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 ] |
|
show ip [ v6 ] pim oif-list group [ source ] [ vrf vrf-name | all ] |
|
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. |
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. |
|
Displays the bootstrap router (BSR) RP hash information. For information about the RP hash, see RFC 5059 . |
|
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 5.x .
Displaying Statistics
You can display and clear PIM and PIM6 statistics by using the commands in this section.
This section includes the following topics:
Displaying PIM and PIM6 Statistics
You can display the PIM and PIM6 statistics and memory usage using the commands listed in Table 1-11 . Use the show ip form of the command for PIM and the show ipv6 form of the command for PIM6.
Displays policy statistics for Register, RP, and join-prune message policies. |
|
Displays global statistics. If PIM is in vPC mode, displays vPC 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 5.x .
Clearing PIM and PIM6 Statistics
You can clear the PIM and PIM6 statistics using the commands listed in Table 1-12 . Use the show ip form of the command for PIM and the show ipv6 form of the command for PIM6.
Configuration Examples for PIM
Note See the “Multiple RPs Configured in a PIM Domain” section for more 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
- Prefix-Based and Route-Map-Based Configurations
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.
Step 2 Configure the parameters for IGMP that support SSM. See Chapter 1, “Configuring IGMP” Usually, you configure IGMPv3 on PIM interfaces to support SSM.
Step 3 Configure the SSM range if you do not want to use the default range.
Step 4 Configure message filtering.
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.
Step 2 Configure whether that router should listen and forward BSR messages.
Step 3 Configure the BSR parameters for each router that you want to act as a BSR.
Step 4 Configure the RP parameters for each router that you want to act as a candidate RP.
Step 5 Configure message filtering.
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:
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.
Step 2 Configure whether that router should listen and forward Auto-RP messages.
Step 3 Configure the mapping agent parameters for each router that you want to act as a mapping agent.
Step 4 Configure the RP parameters for each router that you want to act as a candidate RP.
Step 5 Configure message filtering.
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:
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.
Step 2 Configure the RP address that you configure on all routers in the Anycast-RP set.
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.
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.
Step 5 Configure message filtering.
The following example shows how to configure PIM ASM mode using two Anycast-RPs:
Additional References
For additional information related to implementing PIM, see the following sections:
- Related Documents
- Standards
- MIBs
- Appendix 1, “IETF RFCs for IP Multicast”
- Feature History for PIM and PIM6
Related Documents
MIBs
To locate and download MIBs, go to the following URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml |
Feature History for PIM and PIM6
Table 1-13 lists the release history for this feature.
Feedback