[Xorp-users] IGMP and PIM-SSM problem

[Jigar]

Pavlin,

Thanks for your kind reply.

I think, I blundered in explaining the setup and the scenario which I 
want to
create.
Just scrap the previous one and start with the scratch.

Actually, I want to test the following scenario given in RFC-4601 
(PIM-SM) in
section 4.5.7 (Sending (S,G) Join/Prune Messages)

#########################################################
Transitions from NotJoined State
   When the upstream (S,G) state machine is in NotJoined state, the
   following event may trigger a state transition:
     JoinDesired(S,G) becomes True
          The macro JoinDesired(S,G) becomes True, e.g., because the
          downstream state for (S,G) has changed so that at least one
          interface is in inherited_olist(S,G).
          The upstream (S,G) state machine transitions to Joined state.
          Send Join(S,G) to the appropriate upstream neighbor, which is
          RPF'(S,G).  Set the Join Timer (JT) to expire after t_periodic
          seconds.
##########################################################

To generate above scenario, I have used setup as mentioned below.
    
 
 
IP address:
host A (eth0): 10.100.3.220/24    (IGMPv3 source specific join report 
sender)
host B (eth1): 10.100.3.107/24    (PIM-SM downstream interface)
host B (eth0): 192.168.14.212/24  (PIM-SM uptream interface)
host C (eth0): 192.168.14.211/24  (configured as static RP on host B)

Brief Information about setup:
- All machines (host A, host B, and host C) are running RHEL4 
(kernel-2.6.9).
- host A and host C can be treated as packet generator.
- host B is running xorp (1.4) with attached configuration
  (config.boot.pim-sm.cfg)
- On host B, i configured host C as static RP for all group (pls see 
attached
  config file).
- Test generates scenario such that
  host A becomes IGMP host (as receiver),
  host B becomes DR (of PIM-SM RPT),
  and host C becomes RP (of PIM-SM RPT).
 
Steps followed in test:
- host C sends PIM-SM hello packet with hold time as 0xffff (infinity) 
using
  packet generator utility. So host B assumes that RP is directly 
connect on its
  interface eth0. Also it ensures that RP remains always alive.
- host A sends IGMPv3 source specific join report using attached 
application
  (igmpv3-join-generator.c).
  IGMP Join report is as following:
   Multicast Group address: 232.11.22.33
   Mode: MCAST_INCLUDE
   No of sources in group: 1
   Source address: 192.168.18.154

Expectation:
- As per RFC, host B should generate PIM-SM join(S,G) (here S-192.168.18.154
   G-232.11.22.33) message on eth0 (upstream interface) after receiving 
IGMPv3
   source specific Join message on eth1 (downstream interface).
 
But, I am not getting any PIM-SM join message on eth0 (upstream interface).

Also, I have attached status of PIM-SM database on XORP.

Can you pls guide me what is going wrong in this test scenario?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081015/2b862fae/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 6218 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081015/2b862fae/attachment.jpe 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config.boot.pim-sm.cfg
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081015/2b862fae/attachment.ksh 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xorp-status.txt
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081015/2b862fae/attachment.txt