cisco — 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