Download complete user manual (PDF). - Brocade
Download complete user manual (PDF). - Brocade
Download complete user manual (PDF). - Brocade
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
IPv6 PIM Sparse 4<br />
To optimize PIM traffic, the protocol contains a mechanism for calculating the Shortest Path Tree<br />
(SPT) between a given source and a receiver. PIM Sparse routers can use the SPT as an alternative<br />
to using the RP for forwarding traffic from a source to a receiver. By default, the device forwards the<br />
first packet it receives from a given source to a given receiver using the RP path, but subsequent<br />
packets from that source to that receiver through the SPT. In Figure 10, router A forwards the first<br />
packet from group fec0:1111::1 source to the destination by sending the packet to router B, which<br />
is the RP. Router B then sends the packet to router C. For the second and all future packets that<br />
router A receives from the source for the receiver, router A forwards them directly to router C using<br />
the SPT path.<br />
RFC 3513 and RFC 4007 compliance for IPv6<br />
multicast scope-based forwarding<br />
The IPv6 multicast implementation recognizes scopes and conforms to the scope definitions in<br />
RFC 3513. Per RFC 3513, scopes 0 and 3 are reserved and packets are not forwarded with an IPv6<br />
destination multicast address of scopes 0 and 3. Additionally, scopes 1 and 2 are defined as<br />
Node-Local and Link-Local and are not forwarded. Thus, the implementation forwards only those<br />
packets with an IPv6 multicast destination address with scope 4 or higher.<br />
RFC 4007 defines ‘scope zones’ and requires that the forwarding of packets received on any<br />
interface of a particular scope zone be restricted to that scope zone. Currently, the device supports<br />
one zone for each scope, and the default zone for scope 4 and higher consists of all interfaces in<br />
the system. Thus, the default zones for scope 4 and higher are the same size.<br />
Configuring PIM Sparse<br />
To configure the device for IPv6 PIM Sparse, perform the following tasks:<br />
• Enable the IPv6 PIM Sparse of multicast routing.<br />
• Configure VRF then enable IPv6 Protocol Independent Multicast Sparse mode (PIM-SM) for a<br />
specified VRF, if applicable.<br />
• Configure an IPv6 address on the interface.<br />
• Enable IPv6 PIM Sparse.<br />
• Identify the interface as an IPv6 PIM Sparse border, if applicable.<br />
• Identify the device as a candidate PIM Sparse Bootstrap Router (BSR), if applicable.<br />
• Identify the device as a candidate PIM Sparse Rendezvous Point (RP), if applicable.<br />
• Specify the IP address of the RP (if you want to statically select the RP).<br />
NOTE<br />
It is recommended that you configure the same device as both the BSR and the RP.<br />
IPv6 PIM-Sparse mode<br />
To configure a device for IPv6 PIM Sparse, perform the following tasks:<br />
• Identify the Layer 3 switch as a candidate sparse Rendezvous Point (RP), if applicable.<br />
• Specify the IPv6 address of the RP (to configure statically).<br />
FastIron Ethernet Switch IP Multicast Configuration Guide 155<br />
53-1002638-02
Change language