Re: Register Stop

From: gladston@br.ibm.com
Date: Thu Sep 30 2004 - 16:23:28 GMT-3

This is a multipart message in MIME format.
--=_alternative 006A85E583256F1F_=
Content-Type: text/plain; charset="US-ASCII"

I was used to just look at the F flag. Beau pointed out that the word
"registering" is what we should see. The flag F is normal behavior
(although I do not undertand why Cisco just do not clear this flag)

So, if we see the word "registering" do not disappear from the (S,G) entry
we should concern and look out for problems

A possible cause would be:

R1----R2----R3

R3 is the RP
R1 is directly connected to the source
Due a mistake, we forget to configure PIM on R2

The source start to send multicast. R1 encapsulates the multicast within
unicast and them to R3 (registering). R3 tries to join (S,G) but R2 does
not participate in multicast.

Make sense?
 

Carlos G Mendioroz <tron@huapi.ba.ar>
30/09/2004 16:06

To
Alaerte Gladston Vidali/Brazil/IBM@IBMBR
cc
ccielab@groupstudy.com
Subject
Re: Register Stop

It would be great if you share the answer too.
That way, the message history builds a database of problems and
solutions that people can search...

gladston@br.ibm.com wrote:

> Found the explanation on Beau, pag 267. Thanks.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
> 

--
Carlos G Mendioroz  <tron@huapi.ba.ar>  LW7 EQI  Argentina

--=_alternative 006A85E583256F1F_=
Content-Type: text/html; charset="US-ASCII"

<br><font size=2 face="sans-serif">I was used to just look at the F flag.
Beau pointed out that the word &quot;registering&quot; is what we should
see. The flag F is normal behavior (although I do not undertand why Cisco
just do not clear this flag)</font>
<br>
<br><font size=2 face="sans-serif">So, if we see the word &quot;registering&quot;
do not disappear from the (S,G) entry we should concern and look out for
problems </font>
<br>
<br><font size=2 face="sans-serif">A possible cause would be:</font>
<br>
<br><font size=2 face="sans-serif">R1----R2----R3</font>
<br>
<br><font size=2 face="sans-serif">R3 is the RP</font>
<br><font size=2 face="sans-serif">R1 is directly connected to the source</font>
<br><font size=2 face="sans-serif">Due a mistake, we forget to configure
PIM on R2</font>
<br>
<br><font size=2 face="sans-serif">The source start to send multicast.
R1 encapsulates the multicast within unicast and them to R3 (registering).
R3 tries to join (S,G) but R2 does not participate in multicast. </font>
<br><font size=2 face="sans-serif"><br>
Make sense?<br>
 <br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Carlos G Mendioroz &lt;tron@huapi.ba.ar&gt;</b>
</font>
<p><font size=1 face="sans-serif">30/09/2004 16:06</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Alaerte Gladston Vidali/Brazil/IBM@IBMBR</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">ccielab@groupstudy.com</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: Register Stop</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>It would be great if you share the answer too.<br>
That way, the message history builds a database of problems and<br>
solutions that people can search...<br>
</tt></font>
<br>
<br><font size=2><tt>gladston@br.ibm.com wrote:<br>
</tt></font>
<br><font size=2><tt>&gt; Found the explanation on Beau, pag 267. Thanks.<br>
&gt;<br>
&gt; _______________________________________________________________________<br>
&gt; Subscription information may be found at:<br>
&gt; http://www.groupstudy.com/list/CCIELab.html>
&gt;<br>
</tt></font>
<br><font size=2><tt>--<br>
Carlos G Mendioroz &nbsp;&lt;tron@huapi.ba.ar&gt; &nbsp;LW7 EQI &nbsp;Argentina</tt></font>
<br>
<br>
--=_alternative 006A85E583256F1F_=--

This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:51 GMT-3