Multicast: Difference between revisions

Line 60:
* Sparse mode uses both source based trees and shortest path trees
* RP needs to know the receivers and senders.
* DR on lan segment send (S,G) register mess age to and RP in turns reply register stop process and receivers on lanLAN segment send IGMP join and which will be converted to pim join(*,G) message to RP to form RPT tree.
* So pim join will traverse from receiver till RP every device will have (*,G) entry and from source till RP every device will have (S,G) entry.
* Once RP knows about sender and receiver it will send (S,G) join request back to source and source would start sending the multicast traffic to RP then to receiver.
* Then its up to the last hop router on receiver side for the optimation process weather it want to join directly to source using SPT bypassing RP.
 
* Note - When we do debug only process switched traffic is debug if we want to debug the data plane traffic then we need to disable cef (no ip route cache),if we change the unicast routing it will also change the multicasting routing, To change the unicast routing we can also use Ip mroute command .
 
 
* Source based tree - tree is build based on shortest path from receiver till sender.
* Shared tree - tree from sender to RP and then RP till receiver.
 
* To check RP configured on each transient router - sh ip pim rp mapping :
sh ip pim rp mapping
* RP can be assigned statically (ip pim rp address) or dynamically (auto RP and BSR)
 
Line 77:
* 224.0.1.40 - chooses the RP and advertised to rest of routers for RP information.
 
* To stay on shared tree rather than SPT (ip pm spt-threshold infinity)
ip pm spt-threshold infinity
 
== Sparse-dense-mode ==