HP 3500YL - Manual (Page 118)

PIM-SM (Sparse Mode)
PIM-SM Operation and Router Types
N o t e Where static RPs are configured in the domain to support the same multicast
group(s) as one or more (dynamic) C-RPs, then the RP-set data has the
precedence for assigning RPs for these groups unless the static-RPs have been
configured with the
override option and if the multicast group mask for the
static-RP equals or exceeds the same mask for the applicable C-RP(s). Refer
to the
Note on page 4-17.
BSR Configuration and Election. There should be multiple BSR candi­
dates configured in a PIM-SM domain so that if the elected BSR becomes
unavailable, another router will take its place. In the BSR election process,
the BSR candidate configured with the highest priority number is selected.
Where the highest priority setting is shared by multiple candidates, the candi­
date having the highest IP address is selected. In the event that the selected
BSR subsequently fails, another election takes place among the remaining
BSR candidates. To facilitate a predictable BSR election, configure a higher
priority on the router you want elected as the BSR for the domain. (Refer to
“Changing the Priority Setting for a BSR-Candidate Router” on page 4-36.)
N o t e A router serving as the BSR for a domain should be central to the network
topology. This will help to ensure optimal performance and also reduce the
possibility of a network problem isolating the BSR.
BSR Role in Fault Recovery. If the hold-time maintained in the BSR for a
given C-RP’s latest advertisement expires before being refreshed by a new
advertisement from the C-RP, then the non-reporting C-RP is removed from
the domain. In this case, the removed C-RP’s multicast groups are re-assigned
to other C-RPs. (If no other C-RPs or static-RPs in the domain are configured
to support a multicast group from the non-reporting C-RP, then that group
becomes unavailable in the domain.)
Rendezvous Point (RP)
Instead of flooding multicast traffic as is done with PIM-DM, PIM-SM uses a
set of multiple routers to operate as rendezvous points (RPs). Each RP
controls multicast traffic forwarding for one or more multicast groups as
follows:
■ receives traffic from multicast sources (S) via a DR
■ receives multicast joins from routers requesting multicast traffic
■ forwards the requested multicast traffic to the requesting routers
4-14