Skip to Content.
Sympa Menu

wg-multicast - Re: Foreign-originated SAs [Re: Lot of receive problems in AG beacon]

Subject: All things related to multicast

List archive

Re: Foreign-originated SAs [Re: Lot of receive problems in AG beacon]


Chronological Thread 
  • From: John Haskins <>
  • To: Pekka Savola <>
  • Cc:
  • Subject: Re: Foreign-originated SAs [Re: Lot of receive problems in AG beacon]
  • Date: Thu, 19 Nov 2009 06:49:24 -0800
We see these odd-origin SAs downstream of CENIC too. CENIC NOC probably
has eyes on this list - just in case, I have opened a ticket.
-john

Pekka Savola wrote, On 11/18/09 10:52 PM:
> Hello,
>
> Another thing that's bugging me:
>
> In I2 core router proxy, I see that 137.164.17.3 (cenic) is orinator for
> our source address 193.166.16.111, though the correct originator would
> be 193.166.5.35; the same IP is originating some other foreign sources
> as well. I see that it is the only SA available in GEANT2 as well,
> though NORDUnet sees both our and 137.164.17.3's SA.
>
> Does anyone have any idea what these foreign-originated SAs are for? Is
> this some kind of bug at 137.164.17.3?
>
> .............> show msdp source-active originator 137.164.17.3
> Group address Source address Peer address Originator Flags
> 224.0.5.128 128.117.80.161 211.79.48.157 137.164.17.3 Reject
> 224.2.133.134 128.114.59.163 64.57.28.248 137.164.17.3 Accept
> 134.55.3.3 137.164.17.3 Reject
> 205.189.32.94 137.164.17.3 Reject
> 205.189.32.118 137.164.17.3 Reject
> 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 64.251.63.189 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 130.89.244.17 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 132.239.1.32 64.57.28.248 137.164.17.3 Accept
> 64.57.28.66 137.164.17.3 Reject
> 134.55.3.3 137.164.17.3 Reject
> 198.32.11.51 137.164.17.3 Reject
> 205.189.32.94 137.164.17.3 Reject
> 205.189.32.118 137.164.17.3 Reject
> 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 138.87.237.66 64.57.28.248 137.164.17.3 Accept
> 64.57.28.66 137.164.17.3 Reject
> 134.55.3.3 137.164.17.3 Reject
> 198.32.11.51 137.164.17.3 Reject
> 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 140.221.250.7 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 141.142.2.55 64.57.28.248 137.164.17.3 Accept
> 64.57.28.66 137.164.17.3 Reject
> 134.55.3.3 137.164.17.3 Reject
> 198.32.11.51 137.164.17.3 Reject
> 205.189.32.94 137.164.17.3 Reject
> 205.189.32.118 137.164.17.3 Reject
> 211.79.48.157 137.164.17.3 Reject
> 233.4.200.18 193.166.16.111 64.57.28.248 137.164.17.3 Accept
> 64.57.28.66 137.164.17.3 Reject
> 134.55.3.3 137.164.17.3 Reject
> 198.32.11.51 137.164.17.3 Reject
> 205.189.32.94 137.164.17.3 Reject
> 205.189.32.118 137.164.17.3 Reject
> 211.79.48.157 137.164.17.3 Reject
>
>
>
>
> On Wed, 18 Nov 2009, Pekka Savola wrote:
>> There seem to be some problems with the reverse direction, but on a
>> much smaller scale. I see that most if not all european beacons aren't
>> seen by *.edu.au. Is there anyone from Australia on the list or are
>> there looking glasses etc. to see if our MSDP SAs are getting through?
>>
>> Pekka
>>
>> On Fri, 30 Oct 2009, Chris Robb wrote:
>>> I'm getting an I2 engineer to look into this and report their findings.
>>>
>>> -Chris
>>>
>>> On Oct 30, 2009, at 10:39 AM, Pekka Savola wrote:
>>>
>>>> Let me bring this up again. The AG beacon is not really very useful
>>>> right now, but actually quite few of the problems there are actual
>>>> problems.
>>>>
>>>> Let's take for example *.edu.au sites. Very few of them are seen by
>>>> R&E sites on Internet2 and GEANT.
>>>>
>>>> If you examine source 129.78.221.17 for example, on the I2 core
>>>> router proxy in SEAT gives the following MSDP SA rejects. Ok, quite
>>>> a few of these are rejects due to MSDP RPF mechanism, but there
>>>> should still be at least one accept:
>>>>
>>>> show msdp sa source 129.78.221.17
>>>> Group address Source address Peer address Originator Flags
>>>> 233.4.200.18 129.78.221.17 134.55.3.6 129.78.255.8 Reject
>>>> 137.164.26.141 129.78.255.8 Reject
>>>> 138.18.12.237 129.78.255.8 Reject
>>>> 207.231.240.2 129.78.255.8 Reject
>>>> 207.231.240.21 129.78.255.8 Reject
>>>> 207.231.241.149 129.78.255.8 Reject
>>>> 210.7.36.193 129.78.255.8 Reject
>>>> 210.7.36.194 129.78.255.8 Reject
>>>>
>>>> Maybe someone with better knowledge of AU - I2 multicast
>>>> interconnection could take a look at this ?
>>>>
>>>> [1] http://routerproxy.grnoc.iu.edu/internet2/
>>>>
>>>>
>>>> On Thu, 6 Mar 2008, Pekka Savola wrote:
>>>>> Not sure if this is the best media to reach these sites, but I
>>>>> can't think of a better one..
>>>>>
>>>>> The AG beacon [1] has a lot of sites which don't seem to be able to
>>>>> send multicast that would be received by basically anyone else (the
>>>>> columns where almost every cell is "NA"). As a result, using the
>>>>> AG matrix as one way to measure whether inter-domain multicast is
>>>>> working is not very useful.
>>>>>
>>>>> I guess these sites are likely to have a problem in their or their
>>>>> upstreams' multicast setup (e.g. MSDP) and should be either fixed
>>>>> or removed from the beacon matrix.
>>>>>
>>>>> At least the following seem to be the main offenders:
>>>>>
>>>>> beacon.its.adelaide.edu.au
>>>>> foxbat.services.adelaide.edu.au
>>>>> usq-fos.usq.edu.au
>>>>> darkstar.clemson.edu
>>>>> ndt.ilstu.edu
>>>>> dwarf.ua.edu
>>>>> darkness.nss.udel.edu
>>>>> transducer.nss.udel.edu
>>>>> beacon.net.unc.edu
>>>>> i2-accessgrid-6.unomaha.edu
>>>>> chlt-beacon.ncren.net
>>>>> ecu-beacon.ncren.net
>>>>> ws-beacon.ncren.net
>>>>> vv2.ap-accessgrid.org
>>>>> bridge.ndhu.edu.tw
>>>>> venue.ndhu.edu.tw
>>>>>
>>>>> If you're at these sites or close to them, maybe you a little nudge
>>>>> wouldn't hurt..
>>>>>
>>>>> Thanks!
>>>>>
>>>>> [1]
>>>>> http://beacon.dast.nlanr.net/
>>>>>
>>>
>>> Chris Robb, Internet2 Manager of Operations
>>> O: 812.855.8604 C: 812.345.3188
>>> ****************
>>> SC09: Visit the Internet2 Booth #1355
>>> November 14-20, 2009
>>> Portland, Oregon Convention Center
>>> http://events.internet2.edu/2009/sc09/
>>>
>>>
>>


Archive powered by MHonArc 2.6.16.

Top of Page