Fwd: SSM Video Group


There is a persistent, off and on again, problem between Level 3 and I2 which 
affects all multicasts into I2 from Multicast Tech. The symptom is that multicast
packets only flow for about 5-10 seconds, and then stop for alost 5 minutes, then repeat the
pattern.

As part of the debugging for this I updated the beacon server here to 1.1. I notice
that the beacon loss stats do NOT seem to match this. For example, the problem occurs between
here and IU, but the loss right now between 
63.105.122.14 and wingrid.ads.iu.edu (which I presume is Matt's beacon) is currently listed at
0%. 

How can this be ? This sounds like a bug to me.

A long discussion of the problem is below.

Regards
Marshall Eubanks

--- the forwarded message follows ---
--- Begin Message --- 
More data:

10# ./rtpqual 63.105.122.28@232.64.133.120 8020
Defaulting to: ./rtpqual 63.105.122.28@232.64.133.120 8020 rtp
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:33:27 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:33:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27  10   0   0   0   8036 |    10    0   0    0       7 63.105.122.28
28  11   0   0   0   8929 |    21    0   0    0      16 63.105.122.28
29  11   0   0   0   8886 |    32    0   0    0      25 63.105.122.28
30  11   0   0   0   8763 |    43    0   0    0      33 63.105.122.28
31  10   0   0   0   8082 |    53    0   0    0      41 63.105.122.28
32   6   0   0   0   4849 |    59    0   0    0      46 63.105.122.28
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:38:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27  10  99  90   0   7972 |    69   99  58    0      54 63.105.122.28
28  11   0   0   0   8940 |    80   99  55    0      62 63.105.122.28
29  10   0   0   0   7836 |    90   99  52    0      70 63.105.122.28
30   7   0   0   0   5721 |    97   99  50    0      76 63.105.122.28
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:43:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27   7  122  94   0   5680 |   104  221  68    0      81 63.105.122.28
28  11   0   0   0   8920 |   115  221  65    0      90 63.105.122.28
29  12   0   0   0   9675 |   127  221  63    0      99 63.105.122.28
30  10   0   0   0   8023 |   137  221  61    0     107 63.105.122.28
31  11   0   0   0   8818 |   148  221  59    0     116 63.105.122.28
32  10   0   0   0   8048 |   158  221  58    0     124 63.105.122.28
33  11   0   0   0   8876 |   169  221  56    0     132 63.105.122.28
34   8   0   0   0   6317 |   177  221  55    0     139 63.105.122.28
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:48:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27   8  77  90   0   6464 |   185  298  61    0     145 63.105.122.28
28  11   0   0   0   8782 |   196  298  60    0     153 63.105.122.28
29  12   0   0   0   9789 |   208  298  58    0     163 63.105.122.28
30   9   0   0   0   7145 |   217  298  57    0     170 63.105.122.28
31  11   0   0   0   8904 |   228  298  56    0     179 63.105.122.28
32  11   0   0   0   8928 |   239  298  55    0     187 63.105.122.28
33  11   0   0   0   8887 |   250  298  54    0     196 63.105.122.28
34  10   0   0   0   8016 |   260  298  53    0     204 63.105.122.28
35   9   0   0   0   7142 |   269  298  52    0     211 63.105.122.28
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:53:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27   7  67  90   0   5639 |   276  365  56    0     216 63.105.122.28
28  11   0   0   0   9024 |   287  365  55    0     225 63.105.122.28
29  10   0   0   0   7920 |   297  365  55    0     233 63.105.122.28
30   9   0   0   0   7320 |   306  365  54    0     240 63.105.122.28
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 10:58:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27   1  126  99   0    804 |   307  491  61    0     241 63.105.122.28
28  11   0   0   0   8866 |   318  491  60    0     250 63.105.122.28
29  10   0   0   0   8057 |   328  491  59    0     257 63.105.122.28
30  11   0   0   0   8845 |   339  491  59    0     266 63.105.122.28
31  11   0   0   0   8850 |   350  491  58    0     275 63.105.122.28
32  11   0   0   0   8675 |   361  491  57    0     283 63.105.122.28
33  10   0   0   0   8110 |   371  491  56    0     291 63.105.122.28
34  11   0   0   0   8898 |   382  491  56    0     300 63.105.122.28
Report from: ./rtpqual 232.64.133.120 8020 rtp at Tue Dec 14 11:03:28 2004
T Pkts Loss  % Late Bytes |  Pkts  Loss  %  Late     kB Sender
27   3  79  96   0   2308 |   385  570  59    0     302 63.105.122.28
28  11   0   0   0   8845 |   396  570  59    0     311 63.105.122.28
29  11   0   0   0   8893 |   407  570  58    0     319 63.105.122.28
30  11   0   0   0   8864 |   418  570  57    0     328 63.105.122.28
31  10   0   0   0   8029 |   428  570  57    0     336 63.105.122.28
32  11   0   0   0   8870 |   439  570  56    0     344 63.105.122.28
33  11   0   0   0   8857 |   450  570  55    0     353 63.105.122.28
34  11   0   0   0   8916 |   461  570  55    0     362 63.105.122.28
35  10   0   0   0   7889 |   471  570  54    0     370 63.105.122.28


Matthew Davy wrote:
> And I'm seeing the same behavior for the beacon (63.105.122.14, 
> 233.4.200.19) as I am for americafree.tv (63.105.122.28, 233.64.133.120).
> 
> - Matt
> 
> 
> 
> On Dec 14, 2004, at 10:35 AM, Alan Crosswell wrote:
> 
>>> Just confirming that it is still broken (5 seconds on, n minutes off).
>>> /a
>>>
>>> Marshall Eubanks wrote:
>>>
>>>> Note : L3 email addresses removed.
>>>> Can anyone figure out why the beacon group monitoring 
>>>> http://beacon.dast.nlanr.net/
>>>> does not reveal this ? Aren't ALL MCT -> Level3 -> I2 multicasts 
>>>> affected because they
>>>> take the same path ? And yet most of the MCT beacon entries are 
>>>> green. Is this a clue
>>>> or a bug in the beacon software ?
>>>> Marshall
>>>> On Tue, 14 Dec 2004 09:40:30 -0500
>>>>  Matthew Davy <mpd@grnoc.iu.edu> wrote:
>>>> On Dec 14, 2004, at 9:24 AM, Marshall Eubanks wrote:
>>>>
>>>>> I had thought that Matt had tracked it down to a specific L3 router, 
>>>>> and am a little surprised that this hasn't been confirmed by now.
>>>>
>>>> Indeed, that was confirmed last week.   I was on a call with 2 Level3 
>>>> engineers.   They said the problem appeared to be between their 
>>>> Houston router and their Denver router.   I asked them what the 
>>>> output of 'show ip mroute count' showed on the Houston router.  They 
>>>> said it showed something like 45Kbps.    Then I asked them what the 
>>>> same output on the Denver router showed.  They said "0 bps".   They 
>>>> also said on the Houston router, the interface to the Denver router 
>>>> was dropping out of the PIM outgoing interface list.
>>>> We ended that call and they were going to go figure out what the 
>>>> problem was.    The next thing I heard from Level3 was an email last 
>>>> night saying the issue was resolved.
>>>> - Matt
>
--- End Message ---
Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index