All things related to multicast

[Marshall Eubanks <>]

We have had a pattern of suspicious receiver reports (RR), where the first 
shows
a more or less successful join, and then subsequent ones show no packets 
received
successfully. The pattern seems fixed - data only flows after the first join 
briefly, then
the listener looses the stream and cannot rejoin it, not even manually.

Today's logs show another such suspicious RR pattern, this time through AUCS :

RR rfhpc8100.fh-regensburg.de Wed May 30 10:39:34 2001 30001 U 25 30002 U 50
RR rfhpc8100.fh-regensburg.de Wed May 30 10:39:44 2001 0 D 0 0 D 0
RR rfhpc8100.fh-regensburg.de Wed May 30 10:39:52 2001 0 D 0 0 D 0
RR rfhpc8100.fh-regensburg.de Wed May 30 10:40:08 2001 0 D 0 0 D 0 0 D 0
RR rfhpc8100.fh-regensburg.de Wed May 30 10:40:13 2001 0 D 0 0 D 0 0 D 0

multicasttech-2>show ip mbgp 194.95.104.96
BGP routing table entry for 194.94.0.0/15, version 705096
Paths: (3 available, best #1, table NULL)
Flag: 0x208
  Not advertised to any peer
  3300 8933 680
    195.90.65.9 from 195.90.65.9 (195.206.65.6)
      Origin incomplete, localpref 100, valid, external, best
  1239 24 6509 8933 680
    160.81.38.225 from 160.81.38.225 (144.228.242.54)
      Origin incomplete, metric 75, localpref 100, valid, external
  145 24 6509 8933 680
    204.147.129.89 from 204.147.129.89 (204.147.128.136)
      Origin incomplete, localpref 100, valid, external
      Community: 9503719

This has me stumped. Any idea why a tree, once set up, would
be torn down in the face of the usual PIM keep-alive messages ?
--
                                 Regards
                                 Marshall Eubanks


T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624       Fax     : 703-293-9609
e-mail : 

http://www.on-the-i.com

Test your network for multicast : http://www.multicasttech.com/mt/
 Check the status of multicast in real time :
 http://www.multicasttech.com/status/index.html