![background image](http://html.mh-extra.com/html/foundry-networks/switch-and-router/switch-and-router_installation-and-configuration-manual_2324275639.webp)
Configuring IP Multicast Protocols
December 2000
18 - 13
•
BSR – The Bootstrap Router (BSR) distributes RP information to the other PIM Sparse routers within the
domain. Each PIM Sparse domain has one active BSR. For redundancy, you can configure ports on multiple
routers as candidate BSRs. The PIM Sparse protocol uses an election process to select one of the candidate
BSRs as the BSR for the domain. The BSR with the highest BSR priority (a user-configurable parameter) is
elected. If the priorities result in a tie, then the candidate BSR interface with the highest IP address is elected
.
In the example in Figure 18.3, PIM Sparse router B is the BSR. Port 2/2 is configured as a candidate BSR.
•
RP – The RP is the meeting point for PIM Sparse sources and receivers. A PIM Sparse domain can have
multiple RPs, but each PIM Sparse multicast group address can have only one active RP. PIM Sparse
routers learn the addresses of RPs and the groups for which they are responsible from messages that the
BSR sends to each of the PIM Sparse routers. In the example in Figure 18.3, PIM Sparse router B is the RP.
Port 2/2 is configured as a candidate Rendezvous Point (RP).
To enhance overall network performance, Foundry Layer 3 Switches use the RP to forward only the first
packet from a group source to the group’s receivers. After the first packet, the Layer 3 Switch calculates the
shortest path between the receiver and source (the Shortest Path Tree, or SPT) and uses the SPT for
subsequent packets from the source to the receiver. The Layer 3 Switch calculates a separate SPT for each
source-receiver pair.
NOTE:
Foundry Networks recommends that you configure the same ports as candidate BSRs and RPs.
RP Paths and SPT Paths
Figure 18.3 shows two paths for packets from the source for group 239.255.162.1 and a receiver for the group.
The source is attached to PIM Sparse router A and the recipient is attached to PIM Sparse router C. PIM Sparse
router B in is the RP for this multicast group. As a result, the default path for packets from the source to the
receiver is through the RP. However, the path through the RP sometimes is not the shortest path. In this case,
the shortest path between the source and the receiver is over the direct link between router A and router C, which
bypasses the RP (router B).
To optimize PIM traffic, the protocol contains a mechanism for calculating the Shortest Path Tree (SPT) between
a given source and receiver. PIM Sparse routers can use the SPT as an alternative to using the RP for forwarding
traffic from a source to a receiver. By default, Foundry Layer 3 Switches forward the first packet they receive from
a given source to a given receiver using the RP path, but forward subsequent packets from that source to that
receiver through the SPT. In Figure 18.3, Layer 3 Switch A forwards the first packet from group 239.155.162.1’s
source to the destination by sending the packet to router B, which is the RP. Router B then sends the packet to
router C. For the second and all future packets that router A receives from the source for the receiver, router A
forwards them directly to router C using the SPT path.
Configuring PIM Sparse
Limitations in this Release
The implementation of PIM Sparse in the current software release has the following limitations:
•
PIM Border Routers (PMBRs) are not supported. Thus, you cannot configure a Foundry routing interface as
a PMBR interface for PIM Sparse.
•
PIM Sparse and regular PIM (dense mode) cannot be used on the same interface.
•
You cannot configure or display PIM Sparse information using the Web management interface. (You can
display some general PIM information, but not specific PIM Sparse information.)
To configure a Foundry Layer 3 Switch for PIM Sparse, perform the following tasks:
•
Configure the following global parameters:
•
Enable the PIM Sparse mode of multicast routing.
•
If you have not already done so, enable a unicast routing protocol (RIP or OSPF).
Summary of Contents for Switch and Router
Page 2: ...December 2000 Copyright 2000 by Foundry Networks Inc ...
Page 26: ...Foundry Switch and Router Installation and Configuration Guide xxvi December 2000 ...
Page 64: ...Foundry Switch and Router Installation and Configuration Guide 2 34 December 2000 ...
Page 162: ...Foundry Switch and Router Installation and Configuration Guide 5 38 December 2000 ...
Page 196: ...Foundry Switch and Router Installation and Configuration Guide 6 34 December 2000 ...
Page 208: ...Foundry Switch and Router Installation and Configuration Guide 7 12 December 2000 ...
Page 236: ...Foundry Switch and Router Installation and Configuration Guide 8 28 December 2000 ...
Page 258: ...Foundry Switch and Router Installation and Configuration Guide 9 22 December 2000 ...
Page 420: ...Foundry Switch and Router Installation and Configuration Guide 13 32 December 2000 ...
Page 442: ...Foundry Switch and Router Installation and Configuration Guide 14 22 December 2000 ...
Page 554: ...Foundry Switch and Router Installation and Configuration Guide 15 112 December 2000 ...
Page 574: ...Foundry Switch and Router Installation and Configuration Guide 16 20 December 2000 ...
Page 626: ...Foundry Switch and Router Installation and Configuration Guide 17 52 December 2000 ...
Page 682: ...Foundry Switch and Router Installation and Configuration Guide 18 56 December 2000 ...
Page 826: ...Foundry Switch and Router Installation and Configuration Guide 20 20 December 2000 ...
Page 994: ...Foundry Switch and Router Installation and Configuration Guide 26 10 December 2000 ...
Page 1004: ...Foundry Switch and Router Installation and Configuration Guide B 6 December 2000 ...
Page 1044: ...Foundry Switch and Router Installation and Configuration Guide C 40 December 2000 ...
Page 1048: ...Foundry Switch and Router Installation and Configuration Guide D 4 December 2000 ...
Page 1070: ...Foundry Switch and Router Installation and Configuration Guide Index 18 December 2000 ...