[Xorp-users] Problem setting up PIM-SM with Cisco on Amazon EC2

[Andriy Senkovych]

Hello, Ben!

Thanks for your reply.


> You might try xorp.ct, but I'm not sure if it will help your
> particular problem.
>
> Also, perhaps the problem is that you are not
> using spt?  I think that keeps traffic out of
> the kernel routing tables and just uses messages
> sent directly to/from the router processes.
>
> switch-to-spt-threshold {
>            disable: true
> }

I tried this option both enabled and disabled with no significant
difference, so it seems this shouldn't be it. I just wanted to be
precise to the cisco-like configuration the other side sent.

There's a strange thing.. I tried once to increase TTL of the messages
sent by reciever and got some new output:

[ 2011/02/09 22:41:08 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from
10.100.123.101 to 224.0.0.13 on vif tun123101
[ 2011/02/09 22:41:08 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from
MFEA_4: vif_index = 1 src = 194.247.133.242 dst = 239.10.20.30
[ 2011/02/09 22:41:08 TRACE xorp_pimsm4 PIM ] Add MFC entry:
(194.247.133.242, 239.10.20.30) iif = 1 olist = O..
olist_disable_wrongvif = .OO
[ 2011/02/09 22:41:08 TRACE xorp_pimsm4 PIM ] Add dataflow monitor:
source = 194.247.133.242 group = 239.10.20.30 threshold_interval_sec =
210 threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes
= 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0
is_geq_upcall = 0 is_leq_upcall = 1
[ 2011/02/09 22:41:08 TRACE xorp_fea MFEA ] RX kernel signal:
message_type = 1 vif_index = 1 src = 194.247.133.242 dst =
239.10.20.30
[ 2011/02/09 22:41:08 TRACE xorp_fea MFEA ] Add MFC entry:
(194.247.133.242, 239.10.20.30) iif = 1 olist = O..

And mfc also has this new record:

> show pim mfc
239.10.20.30    194.247.133.242 194.247.133.211
    Incoming interface :      tun247102
    Outgoing interfaces:      O..

And since that time I always get this response even without setting up
TTL. I think someone has done something on the other side. I'll get
the details from the remote side and be back.

BTW, do these log lines show that xorp request has successfully reached RP?

Thanks.
-- 
WBR, Andriy Senkovych