02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 31 PIM Sparse Mode<br />

PIM Sparse Mode is supported only on plat<strong>for</strong>ms: c e<br />

PIM-Sparse Mode (PIM-SM) is a multicast protocol that <strong>for</strong>wards multicast traffic to a subnet only upon<br />

request using a PIM Join message; this behavior is <strong>the</strong> opposite of PIM-Dense Mode, which <strong>for</strong>wards<br />

multicast traffic to all subnets until a request to stop.<br />

Implementation In<strong>for</strong>mation<br />

• The <strong>Force10</strong> implementation of PIM-SM is based on <strong>the</strong> IETF Internet Draft<br />

draft-ietf-pim-sm-v2-new-05.<br />

• The SPT-Threshold is zero, which means that <strong>the</strong> last-hop designated router (DR) joins <strong>the</strong> shortest<br />

path tree (SPT) to <strong>the</strong> source upon receiving <strong>the</strong> first multicast packet.<br />

• <strong>FTOS</strong> reduces <strong>the</strong> number of control messages sent between multicast routers by bundling Join and<br />

Prune requests in <strong>the</strong> same message.<br />

• PIM-SM on VLAN interfaces is supported on TeraScale plat<strong>for</strong>ms only.<br />

Protocol Overview<br />

PIM-SM initally uses unidirectional shared trees to <strong>for</strong>ward multicast traffic; that is, all multicast traffic<br />

must flow only from <strong>the</strong> Rendezvous Point (RP) to <strong>the</strong> receivers. Once a receiver receives traffic from <strong>the</strong><br />

RP, PM-SM switches to shortest path trees (SPT) to <strong>for</strong>ward multicast traffic. Every multicast group has an<br />

RP and a unidirectional shared tree (group-specific shared tree).<br />

Requesting Multicast Traffic<br />

A host requesting multicast traffic <strong>for</strong> a particular group sends an IGMP Join message to its gateway<br />

router. The gateway router is <strong>the</strong>n responsible <strong>for</strong> joining <strong>the</strong> shared tree to <strong>the</strong> RP (RPT) so that <strong>the</strong> host<br />

can receive <strong>the</strong> requested traffic.<br />

1. Upon receiving an IGMP Join message, <strong>the</strong> receiver gateway router (last-hop DR) creates a (*,G) entry<br />

in its multicast routing table <strong>for</strong> <strong>the</strong> requested group. The interface on which <strong>the</strong> join message was<br />

received becomes <strong>the</strong> outgoing interface associated with <strong>the</strong> (*,G) entry.<br />

2. The last-hop DR sends a PIM Join message to <strong>the</strong> RP. All routers along <strong>the</strong> way, including <strong>the</strong> RP,<br />

create an (*,G) entry in <strong>the</strong>ir multicast routing table, and <strong>the</strong> interface on which <strong>the</strong> message was<br />

received becomes <strong>the</strong> outgoing interface associated with <strong>the</strong> (*,G) entry. This process constructs an<br />

RPT branch to <strong>the</strong> RP.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 627

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!