<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle18
{mso-style-name:emailstyle18;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When a PIM router receives an IGMP join request on and interface that is a DR, the next step is for it to send the PIM join to the RP. Make sure your DSR router
knows how to get to the RP. I noticed that each of the routers has two interfaces. If the RP IP address is not on the interface on the shared link between the DSR and the RP, the DSR won’t know how to get there because you are not running a unicast routing
protocol.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Next step: add static routes, or configure OSPF, so that both routers know how to reach all 3 subnets.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Mark Williams<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Vunnava Kesava Srinivas-B32946 [mailto:B32946@freescale.com]
<br>
<b>Sent:</b> Tuesday, March 01, 2011 08:53<br>
<b>To:</b> Williams, Mark; xorp-users@xorp.org<br>
<b>Subject:</b> RE: Help Needed in PIM-Join Messages !!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Courier New";color:black">Thanks Mark for throwing some light on the dark path.I have uncommented the fib2mrib Configuration part & also I have used Bootstrap Mechanism
to learn the RP. I can see that DSR is learning RP through Bootstrap [<show pim rps>]. Even MRIB [<show pim mrib>] is also populated with the Path to the RP. But still ; I am unable to see PIM-JOIN Messages getting generated .<br>
<br>
Some other Observations are ; I can see that Multicast Listener-group was registered in the DSR [<show igmp group>]when the listener sends the IGMPv2 Message. So; there is NO PROBLEM between the Listener & DSR. As per the protocol specification ; once DSR learns
the Group it needs to create (*,G) state and should send the (*,G) JOIN to RP.But that's Not Happening.Is there any provision in DSR to see whether it is creating (*,G) state?? Also I have enabled only PIM-SM Communication between the RP & DSR. I have totally
disabled the IGMP between RP & DSR. When I look at the mfea dataflow [<show mfea dataflow>]., it is empty. I am suspecting if every thing went fine; this data-flow should have got some entries!!!<br>
<br>
Any way ; would request you to suggest me Next step to move on this further.<br>
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Courier New";color:black">-Thanks in advance,<br>
VKS.</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div id="divRpF491780">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Williams, Mark [william@losrios.edu]<br>
<b>Sent:</b> 28 February 2011 21:53:21<br>
<b>To:</b> Vunnava Kesava Srinivas-B32946; xorp-users@xorp.org<br>
<b>Subject:</b> RE: Help Needed in PIM-Join Messages !!</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You need to uncomment the section on fib2mrib in the configuration on your DSR. PIM routers need to use the unicast forwarding table to be able to find the
reverse path back to the RP.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If you configure the RP router as a BSR and candidate RP, then let the DSR learn the RP information using bootstrap; don’t configure it statically.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Mark Williams</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:-moz-use-text-color -moz-use-text-color">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> xorp-users-bounces@xorp.org [mailto:xorp-users-bounces@xorp.org]
<b>On Behalf Of </b>Vunnava Kesava Srinivas-B32946<br>
<b>Sent:</b> Monday, February 28, 2011 08:10<br>
<b>To:</b> xorp-users@xorp.org<br>
<b>Subject:</b> [Xorp-users] Help Needed in PIM-Join Messages !!</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black">Hi Guys,<br>
I have a requirement to bring up Multicast Routing [IPv4 Network] with pimsm4. The Topology that I am trying to configure is ;<br>
"Multicast Sender <--------->RP<------------->DSR<-------------->Multicast Listener". I have connected everything Point- Point. So., No need to worry about routes.<br>
<br>
I am seeing that Listener is sending IGMPv3 Join reports to the DSR. But even though pim-sm is running on DSR; it is NOT sending PIM-Join Messages to the RP. I have configured staticrp in the DSR & and the connectivity between the RP & DSP is Fine. I have attached
the configuration file of both the RP & DSR. Please let me know what configuration am I missing !!!<br>
<br>
Few Doubts:<br>
1] Also another question is., If I am enabling IGMP on both the interfaces of DSR & RP will that matter & effect PIM Routing ??<br>
2] How Plumbing effects Multicast Routing.<br>
<br>
<br>
-Thanks in Advance,<br>
VKS.</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>