What is multicast states

PIM Sparse Mode Overview

Explicit join model

> Receivers join to the Rendezvous Point (RP)
> Senders register with the RP
> Data Flows down the shared tree and goes only to place
that need the data from the sources

RPF check depends on the tree type

> For shared trees, uses RP address
> For source trees, uses Sources address
Pim uses the join messages ,
In case of multicast routing routers looks source
address

Server
255.2.2.2 multicast feed

PIM RP
1.1.1.1

RTRB

Router send msg pim join to RP

With core/shared tree

Now the router is doing the RPF

i.e source ip address

If this receiver shows interest

Client

RPF Failure

PIM uses unicast routing to reach the RP

RPF Failure: RtrB expecting first multicast pkt
from RP , but if it get that pkt from the Server it
will drop that pkt , i. e RPF failure , it will receive
packets via RP
Now RTRB checks its routing table , check its
shortest path to reach the multicast source.
Now the RPF failure path will be excepted .

PIM Sparse Mode Overview

Only one RP is chosen for a particular group

RP statically configured or dynamically learned (Au
Data forwarded based on the source state (S,G)
If it exists , otherwise use the shared state (*,G)
RFC 2362 PIM Sparse Mode Protocol Spec

What is PIM state ?

Describes the state of the multicast
distribution trees as understood by the
router at this point in the network

PIM State (show ip mroute

entries

Represented by entries in the multicast routing (mroute) tab

(*,G) and (S,G) ??

Represented by entries in the multicast routing
(mroute) table
> Used to make multicast traffic forwarding
decisions
> Composed of (*,G) and (S,G) entries

PIM State RPF

Information

Represented by entries in the multicast routing (mroute) tabl

> Used to make multicast traffic forwarding decisions
> Composed of (*,G) & (S,G) entries
> Each entry contains RPF information
- Incoming (i.g RPF) interface
> RPF Neighbor (upstream)

PIM State OIL

Information

esented by entries in the multicast routing (mroute) table

Used to make multicast traffic forwarding decisions
Composed of (*,G) and (S,G) entries
Each entry contains an Outgoing interface List (OIL)
> OIL may be NULL

ncoming interfaces shows from where we learn (*,G) location for RP

) shows
outgoing interfaces shows the interested parties. Generally (*,G) entrie
es to The (S,G) entries , but we have other outgoing interface called OIL