[Xorp-users] PIM-SM in xorp cvs

[Otto Solares]

On Tue, Aug 22, 2006 at 05:54:44PM -0700, Pavlin Radoslavov wrote:
> You must run PIM-SM on MREN_router even if you are going to use SSM
> only. As I mentioned in one of my earlier emails, you don't have to
> configure MREN_router to be an RP. Instead, configure both My_router
> and MREN_router (e.g., using static-rps entry) to consider
> Internet2_router as the RP.
> 
> You need MSDP if you have your own PIM-SM domain with your own set
> of RPs, and you want to exchange that info with other PIM-SM
> domains. If Internet2_router is already running MSDP for example,
> then you just become part of the Internet2_route's PIM-SM domain and
> you don't need MSDP running on My_router or MREN_router.

Excellent news!  Well it appears that the Internet2_router (cisco)
finally see something, I don't get the neighbor errors anymore,
will test tomorrow with the Internet2 people to see if a multicast
transmition actually works.  Your advise have helped me a lot!

Just for the record, one needs PIM in all interfaces where multicast
packets will flow, why is that technically necessary just for curiosity?

Now I'm getting lots of this errors just with differents interfaces and
differents from IP addresses:

[ 2006/08/22 20:36:07  ERROR xorp_pimsm4:30195 PIM +2623 xrl_pim_node.cc mfea_client_send_protocol_message_cb ] Cannot send a protocol message: 102 Command failed Cannot send PIMSM_4 protocol message from 10.0.2.1 to 200.0.204.169 on vif eth4: sendmsg(proto 103 size 28 from 10.0.2.1 to 200.0.204.169 on vif eth4) failed: Operation not permitted

If you see the 200.0.204.169 router is in eth6, why XORP try to send
from 10.0.2.1 to 200.0.204.169 on eth4? that obviously will fail and
probably is why is not permitted, maybe is the source of the other
problem when I see bogus from IP addresses in PIM-register messages.

It should send to 200.0.204.169 using the primary IP in eth6 which is
the interface towards the RP as we have talked previously.

989.877636 168.234.203.126 -> 200.0.204.169 PIMv2 Register
989.941391 200.0.204.169 -> 168.234.203.126 PIMv2 Register-stop
1576.736525 168.234.203.5 -> 200.0.204.169 PIMv2 Register
1576.800376 200.0.204.169 -> 168.234.203.5 PIMv2 Register-stop

What Register-stop packets means?

And as you can see there are two different IP sources for PIM Register
packets, that is the problem I mentioned above about bogus sources.

Thanks a lot!!!

-otto