cisco · 62 pp.

Cisco PIM Configuration: User & Service Manual PDF

Related manuals

Contents

Document text

Prerequisites for PIM

Configuring Protocol Independent Multicast (PIM) Prerequisites for PIM, on page 1 Restrictions for PIM, on page 2 Information about PIM, on page 4 How to Configure PIM, on page 21 Enabling High Availability on PIM Using Reverse Path Forwarding (RPF), on page 47 Verifying PIM Operations, on page 48 Monitoring and Troubleshooting PIM, on page 56 Configuration Examples for PIM, on page 58 Feature History for PIM, on page 61 Prerequisites for PIM Before you begin the PIM configuration process, decide which PIM mode to use. This is based on the applications you intend to support on your network. Use the following guidelines:

• In general, if the application is one-to-many or many-to-many in nature, then PIM-SM can be used successfully. • For optimal one-to-many application performance, SSM is appropriate but requires IGMP version 3 support. Before you configure PIM stub routing, check that you have met these conditions: • You must have IP multicast routing configured on both the stub router and the central router. You must also have PIM mode configured on the uplink interface of the stub router. • You must also configure either Enhanced Interior Gateway Routing Protocol (EIGRP) stub routing or Open Shortest Path First (OSPF) stub routing on the device.

• The PIM stub router does not route the transit traffic between the distribution routers. Unicast (EIGRP) stub routing enforces this behavior. You must configure unicast stub routing to assist the PIM stub router behavior. Configuring Protocol Independent Multicast (PIM) 1

Page 1

Restrictions for Configuring PIM Stub Routing

Restrictions for PIM The following are the restrictions for configuring PIM: • Use ACLs to designate a specified port only as a multicast host port and not as a multicast router port. Multicast router control-packets received on this port are dropped. • PIM nonbroadcast multiaccess (NBMA) mode is not supported on an ethernet interface. • Hot Standby Router Protocol-aware (HSRP-aware) PIM is not supported. PIMv1 and PIMv2 Interoperability To avoid misconfiguring multicast routing on your device, review the information in this section. The Cisco PIMv2 implementation provides interoperability and transition between Version 1 and Version 2, although there might be some minor problems.

You can upgrade to PIMv2 incrementally. PIM Versions 1 and 2 can be configured on different routers and multilayer switches within one network. Internally, all routers and multilayer switches on a shared media network must run the same PIM version. Therefore, if a PIMv2 device detects a PIMv1 device, the Version 2 device downgrades itself to Version 1 until all Version 1 devices have been shut down or upgraded. PIMv2 uses the BSR to discover and announce RP-set information for each group prefix to all the routers and multilayer switches in a PIM domain. PIMv1, together with the Auto-RP feature, can perform the same tasks as the PIMv2 BSR.

However, Auto-RP is a standalone protocol, separate from PIMv1, and is a proprietary Cisco protocol. PIMv2 is a standards track protocol in the IETF. We recommend that you use PIMv2. The BSR function interoperates with Auto-RP on Cisco routers and multilayer switches. Note When PIMv2 devices interoperate with PIMv1 devices, Auto-RP should have already been deployed. A PIMv2 BSR that is also an Auto-RP mapping agent automatically advertises the RP elected by Auto-RP. That is, Auto-RP sets its single RP on every router or multilayer switch in the group. Not all routers and switches in the domain use the PIMv2 hash function to select multiple RPs.

Sparse-mode groups in a mixed PIMv1 and PIMv2 region are possible because the Auto-RP feature in PIMv1 interoperates with the PIMv2 RP feature. Although all PIMv2 devices can also use PIMv1, we recommend that the RPs be upgraded to PIMv2. To ease the transition to PIMv2, we recommend: • Using Auto-RP throughout the region. If Auto-RP is not already configured in the PIMv1 regions, configure Auto-RP. Restrictions for Configuring PIM Stub Routing • Only directly connected multicast (IGMP) receivers and sources are allowed in the Layer 2 access domains. The PIM protocol is not supported in access domains.

Configuring Protocol Independent Multicast (PIM) Restrictions for PIM Configuring Protocol Independent Multicast (PIM) 2

Page 2

Restrictions for Configuring Auto-RP and BSR

• In a network using PIM stub routing, the only allowable route for IP traffic to the user is through a device that is configured with PIM stub routing. • The redundant PIM stub router topology is not supported. Only the nonredundant access router topology is supported by the PIM stub feature. Restrictions for Configuring Auto-RP and BSR Take into consideration your network configuration, and the following restrictions when configuring Auto-RP and BSR: Restrictions for Configuring Auto-RP The following are restrictions for configuring Auto-RP (if used in your network configuration):

• If routed interfaces are configured in sparse mode, Auto-RP can still be used if all devices are configured with a manual RP address for the Auto-RP groups. • If routed interfaces are configured in sparse mode and you enter the ip pim autorp listener global configuration command, Auto-RP can still be used even if all devices are not configured with a manual RP address for the Auto-RP groups. Restrictions for Configuring BSR The following are the restrictions for configuring BSR (if used in your network configuration): • Configure the candidate BSRs as the RP-mapping agents for Auto-RP.

• For group prefixes advertised through Auto-RP, the PIMv2 BSR mechanism should not advertise a subrange of these group prefixes served by a different set of RPs. In a mixed PIMv1 and PIMv2 domain, have backup RPs serve the same group prefixes. This prevents the PIMv2 DRs from selecting a different RP from those PIMv1 DRs, due to the longest match lookup in the RP-mapping database. Restrictions and Guidelines for Configuring Auto-RP and BSR The following are restrictions for configuring Auto-RP and BSR (if used in your network configuration): • If your network is all Cisco routers and multilayer switches, you can use either Auto-RP or BSR.

• If you have non-Cisco routers in your network, you must use BSR. • If you have Cisco PIMv1 and PIMv2 routers and multilayer switches and non-Cisco routers, you must use both Auto-RP and BSR. If your network includes routers from other vendors, configure the Auto-RP mapping agent and the BSR on a Cisco PIMv2 device. Ensure that no PIMv1 device is located in the path a between the BSR and a non-Cisco PIMv2 device. Note There are two approaches to using PIMv2. You can use Version 2 exclusively in your network or migrate to Version 2 by employing a mixed PIM version environment.

Configuring Protocol Independent Multicast (PIM) Restrictions for Configuring Auto-RP and BSR Configuring Protocol Independent Multicast (PIM) 3

Page 3

PIM Versions

• Because bootstrap messages are sent hop-by-hop, a PIMv1 device prevents these messages from reaching all routers and multilayer switches in your network. Therefore, if your network has a PIMv1 device in it and only Cisco routers and multilayer switches, it is best to use Auto-RP. • If you have a network that includes non-Cisco routers, configure the Auto-RP mapping agent and the BSR on a Cisco PIMv2 router or multilayer switch. Ensure that no PIMv1 device is on the path between the BSR and a non-Cisco PIMv2 router. • If you have non-Cisco PIMv2 routers that need to interoperate with Cisco PIMv1 routers and multilayer switches, both Auto-RP and a BSR are required.

We recommend that a Cisco PIMv2 device be both the Auto-RP mapping agent and the BSR. Restrictions for Auto-RP Enhancement The simultaneous deployment of Auto-RP and bootstrap router (BSR) is not supported. Information about PIM Protocol Independent Multicast Overview The Protocol Independent Multicast (PIM) protocol maintains the current IP multicast service mode of receiver-initiated membership.

PIM is not dependent on a specific unicast routing protocol; it is IP routing protocol independent and can leverage whichever unicast routing protocols are used to populate the unicast routing table, including Enhanced Interior Gateway Routing Protocol (EIGRP), Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), and static routes. PIM uses unicast routing information to perform the multicast forwarding function. Although PIM is called a multicast routing protocol, it actually uses the unicast routing table to perform the reverse path forwarding (RPF) check function instead of building up a completely independent multicast routing table.

Unlike other routing protocols, PIM does not send and receive routing updates between routers. PIM is defined in RFC 4601, Protocol Independent Multicast - Sparse Mode (PIM-SM) PIM Versions PIMv2 includes these improvements over PIMv1: • A single, active rendezvous point (RP) exists per multicast group, with multiple backup RPs. This single RP compares to multiple active RPs for the same group in PIMv1. • A bootstrap router (BSR) provides a fault-tolerant, automated RP discovery and distribution function that enables routers and multilayer switches to dynamically learn the group-to-RP mappings. • PIM join and prune messages have more flexible encoding for multiple address families.

• A more flexible hello packet format replaces the query packet to encode current and future capability options. • Register messages sent to an RP specify whether they are sent by a border router or a designated router. • PIM packets are no longer inside IGMP packets; they are standalone packets. Configuring Protocol Independent Multicast (PIM) Restrictions for Auto-RP Enhancement Configuring Protocol Independent Multicast (PIM) 4

Page 4