speaking of multicast debugging...
Robert Olson
olson at mcs.anl.gov
Thu May 8 10:35:26 CDT 2003
Here is the paper trail of the process that led to the repair of the ANL to
Germany multicast path. Note that the debugging was the minor part; it took
more time to bring together the 4-5 different institutions that
participated in finding the solution.
--bob
Date: Tue, 6 May 2003 09:21:58 -0500 (CDT)
From: Robert Olson <olson at mcs.anl.gov>
To: mcast-support at accessgrid.org
Subject: Multicast problem: MCS -> Germany
Message-ID: <Pine.LNX.4.44.0305060919000.22019-100000 at terra.mcs.anl.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=0.5 required=5.0 tests=X_NOT_PRESENT version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
The following traffic isn't going thru:
Sender: 140.221.34.33 or 140.221.8.41
Receiver: 134.94.106.106
Group: 233.4.200.3/19004
The other direction works, and that receiver appears to be getting traffic
fine from other sites in the group (NCSA, BU, Manchester).
--bob
Date: Tue, 6 May 2003 09:56:57 -0500 (CDT)
From: Robert Olson <olson at mcs.anl.gov>
To: mcast-support at accessgrid.org
cc: m.sczimarowsky at fz-juelich.de
Subject: Re: Multicast problem: MCS -> Germany
In-Reply-To: <Pine.LNX.4.44.0305060919000.22019-100000 at terra.mcs.anl.gov>
Message-ID: <Pine.LNX.4.44.0305060946480.22019-100000 at terra.mcs.anl.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-3.9 required=5.0 tests=IN_REP_TO,X_NOT_PRESENT
version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
[Martin, can you forward to an appropriate network admin on your
side?]
Looking at nycmng, which is the last abilene hop before GEANT:
(terra) % traceroute 134.94.106.106
traceroute to 134.94.106.106 (134.94.106.106), 30 hops max, 38 byte
packets
1 hsrp (140.221.11.253) 0.402 ms 0.237 ms 0.215 ms
2 guava-stardust.anchor.anl.gov (130.202.222.74) 0.366 ms 0.247 ms
0.245 ms
3 mren-anl-gige.anchor.anl.gov (192.5.170.214) 0.829 ms 0.852 ms
0.806 ms
4 chin-mren-ge.abilene.ucaid.edu (198.32.11.97) 0.911 ms 0.875 ms
0.845 ms
5 nycmng-chinng.abilene.ucaid.edu (198.32.8.83) 20.892 ms 29.235 ms
20.898 ms
6 abilene.uk1.uk.geant.net (62.40.103.25) 171.524 ms 171.594 ms
171.247 ms
7 uk.fr1.fr.geant.net (62.40.96.89) 151.401 ms 151.157 ms 151.500 ms
8 fr.de1.de.geant.net (62.40.96.49) 151.641 ms 151.412 ms 151.539 ms
9 * * *
10 cr-frankfurt1-po8-2.g-win.dfn.de (188.1.80.37) 151.903 ms 151.742 ms
151.698 ms
11 cr-koeln1-po0-1.g-win.dfn.de (188.1.18.86) 155.954 ms 155.976 ms
157.099 ms
12 ar-aachen1-po1-0.g-win.dfn.de (188.1.84.50) 157.514 ms 157.658 ms
158.299 ms
13 zam301.zam.kfa-juelich.de (134.94.111.238) 158.004 ms 158.166 ms
157.692 ms
14 * * *
Querying NYCMng [New York, New York]: msdp source-active group 233.4.200.3
Group address Source address Peer address Originator Flags
233.4.200.3 140.221.34.33 198.32.8.196 192.5.170.2 Accept
134.55.3.3 192.5.170.2 Reject
193.10.68.85 192.5.170.2 Reject
199.109.5.1 192.5.170.2 Reject
Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
Instance: PIM.master Family: INET
Group: 233.4.200.3
Source: 140.221.34.33
Flags: sparse
Upstream interface: so-0/0/0.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 181
Downstream Neighbors:
Interface: so-2/3/0.0
192.5.89.9 State: Join Flags: S Timeout: 193
Looks like perhaps missing joins from the GEANT side? A working source
looks like this:
Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
Instance: PIM.master Family: INET
Group: 233.4.200.3
Source: 141.142.66.75
Flags: sparse
Upstream interface: so-0/0/0.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 204
Downstream Neighbors:
Interface: so-2/2/0.0
62.40.103.25 State: Join Flags: S Timeout: 209
Interface: so-2/3/0.0
192.5.89.9 State: Join Flags: S Timeout: 183
--bob
On Tue, 6 May 2003, Robert Olson wrote:
> The following traffic isn't going thru:
>
> Sender: 140.221.34.33 or 140.221.8.41
> Receiver: 134.94.106.106
> Group: 233.4.200.3/19004
>
> The other direction works, and that receiver appears to be getting traffic
> fine from other sites in the group (NCSA, BU, Manchester).
>
> --bob
>
>
>
X-Sender: olson at pop.mcs.anl.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 06 May 2003 10:53:32 -0500
To: mcast-support at accessgrid.org
From: Robert Olson <olson at mcs.anl.gov>
Subject: Re: Multicast problem: MCS -> Germany
Cc: m.sczimarowsky at fz-juelich.de
In-Reply-To: <Pine.LNX.4.44.0305060946480.22019-100000 at terra.mcs.anl.gov
>
References: <Pine.LNX.4.44.0305060919000.22019-100000 at terra.mcs.anl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
I am now seeing a similar situation with:
source 140.221.34.34
receiver 192.150.184.66
group 233.2.171.251/59988
where the ANL->Manchester traffic does not go through. Again, on nycmng a
show pim going shows a missing join toward geant for the 140.221.34.34 source.
--bob
X-Sender: olson at pop.mcs.anl.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 06 May 2003 12:38:05 -0500
To: operations at dante.org.uk
From: Robert Olson <olson at mcs.anl.gov>
Subject: Multicast problem from Argonne National Laboratory to Juelich
Cc: mcast-support at accessgrid.org, m.sczimarowsky at fz-juelich.de
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mcs.anl.gov id
h46Hc7t143844
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
Hello --
I am trying to track down a problem with multicast routing between a
machine at Argonne National Laboratory in the US with a machine at the
Forschungszentrum Jülich.
The following traffic isn't going through:
Sender: 140.221.34.33
Receiver: 134.94.106.106
Group: 233.4.200.3/19004
A traceroute from ANL to the Jülich machine looks like this:
traceroute to 134.94.106.106 (134.94.106.106), 30 hops max, 38 byte packets
1 hsrp (140.221.11.253) 0.362 ms 0.276 ms 0.217 ms
2 guava-stardust.anchor.anl.gov (130.202.222.74) 0.305 ms 0.235
ms 0.223 ms
3 mren-anl-gige.anchor.anl.gov (192.5.170.214) 2.173 ms 0.875 ms 0.798 ms
4 chin-mren-ge.abilene.ucaid.edu (198.32.11.97) 0.909 ms 0.867
ms 0.863 ms
5 nycmng-chinng.abilene.ucaid.edu (198.32.8.83) 33.148 ms 20.940
ms 20.982 ms
6 abilene.uk1.uk.geant.net (62.40.103.25) 171.763 ms 171.916
ms 171.701 ms
7 uk.fr1.fr.geant.net (62.40.96.89) 151.610 ms 152.076 ms 151.510 ms
8 fr.de1.de.geant.net (62.40.96.49) 152.223 ms 151.415 ms 151.269 ms
9 * * *
10 cr-frankfurt1-po8-2.g-win.dfn.de (188.1.80.37) 151.739 ms 152.068
ms 151.766 ms
11 cr-koeln1-po0-1.g-win.dfn.de (188.1.18.86) 155.971 ms 157.902
ms 155.772 ms
12 ar-aachen1-po1-0.g-win.dfn.de (188.1.84.50) 157.484 ms 157.541
ms 157.526 ms
13 zam301.zam.kfa-juelich.de (134.94.111.238) 158.034 ms 157.818
ms 158.415 ms
14 * * *
15 * * *
16 * * *
Looking at the NYCMNG Abilene router proxy, I find this:
Querying NYCMng [New York, New York]: msdp source-active group 233.4.200.3
Group address Source address Peer address Originator Flags
233.4.200.3 140.221.34.33 198.32.8.196 192.5.170.2 Accept
134.55.3.3 192.5.170.2 Reject
193.10.68.85 192.5.170.2 Reject
199.109.5.1 192.5.170.2 Reject
Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
Instance: PIM.master Family: INET
Group: 233.4.200.3
Source: 140.221.34.33
Flags: sparse
Upstream interface: so-0/0/0.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 181
Downstream Neighbors:
Interface: so-2/3/0.0
192.5.89.9 State: Join Flags: S Timeout: 193
It appears that the join is missing toward geant.net; a working source
(from earlier today) showed this state at NYCMNG:
Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
Instance: PIM.master Family: INET
Group: 233.4.200.3
Source: 141.142.66.75
Flags: sparse
Upstream interface: so-0/0/0.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 204
Downstream Neighbors:
Interface: so-2/2/0.0
62.40.103.25 State: Join Flags: S Timeout: 209
Interface: so-2/3/0.0
192.5.89.9 State: Join Flags: S Timeout: 183
Please let me know if there is any more information I can give you, or if
there is a better location to which this report can be sent.
Thank you,
--bob
X-Sender: olson at pop.mcs.anl.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 07 May 2003 07:10:46 -0500
To: mcast-support at accessgrid.org
From: Robert Olson <olson at mcs.anl.gov>
Subject: Fwd: Re: Multicast problem
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
>Date: Wed, 07 May 2003 12:52:53 +0200
>From: "M.Sczimarowsky" <M.Sczimarowsky at fz-juelich.de>
>Organization: Forschungszentrum Juelich GmbH
>X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u)
>X-Accept-Language: en
>To: Robert Olson <olson at mcs.anl.gov>
>Subject: Re: Multicast problem
>X-Spam-Status: No, hits=0.5 required=5.0 tests=FROM_NAME_NO_SPACES
>version=2.21
>X-Spam-Level:
>
>Hi Bob,
>
>here is the traceroute 140.221.34.3 result from
>ag-audio.zam.kfa-juelich.de,
>although I dont see that this helps much, I am quite sure the multicast
>routing is different. I will try to find it out. I passed your info
>to our networking experts. Thanks very much for your help.
>
>Martin
>
>
>ag-audio:~ # traceroute 140.221.34.3
>traceroute to 140.221.34.3 (140.221.34.3), 30 hops max, 40 byte packets
> 1 zam047-106.zam.kfa-juelich.de (134.94.106.1) 1 ms 0 ms 0 ms
> 2 zam301-p2p.zam.kfa-juelich.de (134.94.111.186) 0 ms 0 ms 0 ms
> 3 ar-aachen1.g-win.dfn.de (188.1.43.193) 1 ms 1 ms 1 ms
> 4 cr-koeln1-po2-0.g-win.dfn.de (188.1.84.49) 4 ms 3 ms 3 ms
> 5 cr-frankfurt1-po9-1.g-win.dfn.de (188.1.18.85) 7 ms 7 ms 7 ms
> 6 so-6-0-0.ar2.FRA2.gblx.net (208.48.23.141) 7 ms 7 ms 7 ms
> 7 pos5-0-2488M.cr2.FRA2.gblx.net (62.16.32.77) 7 ms 7 ms 7 ms
> 8 so2-0-0-2488M.cr1.PAO2.gblx.net (208.51.224.210) 153 ms 153 ms
>153 ms
> 9 so-5-0-0-2488M.br2.PAO2.gblx.net (208.51.224.142) 153 ms 153 ms
>153 ms
>10 208.50.13.54 (208.50.13.54) 154 ms 154 ms 154 ms
>11 snv-paix-pa.es.net (134.55.208.206) 154 ms 154 ms 155 ms
>12 snvcr1-ge0-snvrt1.es.net (134.55.209.89) 155 ms 156 ms 155 ms
>13 chicr1-oc192-snvcr1.es.net (134.55.209.54) 203 ms 204 ms 202 ms
>14 anl-oc12-chicr1.es.net (134.55.209.202) 209 ms 206 ms 213 ms
>15 guava-esnet.anchor.anl.gov (192.5.170.77) 157 ms 157 ms 157 ms
>16 stardust-guava.anchor.anl.gov (130.202.222.73) 157 ms 157 ms 158
>ms
>17 ws-audio.mcs.anl.gov (140.221.34.3) 158 ms 157 ms 157 ms
>
>
>
>
>Robert Olson wrote:
> >
> > Hi --
> >
> > It looks like we've exhausted the debugging we can do from this end; we'll
> > need to get someone from either your site or the GEANT network folks to
> > look into it.
> >
> > One thing you can do is send us the result of a tracroute from your audio
> > machine to 140.221.34.33.
> >
> > thanks,
> > --bob
>
>--
>_______________________________________________________________________
> Martin Sczimarowsky
> Forschungszentrum Juelich / Zentralinstitut fuer Angewandte Mathematik
> D 52425 Juelich Tel/Fax : +49 2461 61 6411/6656
>_______________________________ M.Sczimarowsky at fz-juelich.de __________
X-Sender: ana at mail.dante.org.uk
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 07 May 2003 14:21:10 +0100
To: multicast at noc.geant.net
From: Ana Romero <Ana.Romero at dante.org.uk>
Subject: Re: Multicast problem from Argonne National Laboratory to
Juelich
Cc: mcast-support at accessgrid.org, m.sczimarowsky at fz-juelich.de,
Robert Olson <olson at mcs.anl.gov>, operations at dante.org.uk,
noc at noc.geant.net
In-Reply-To: <5.2.0.9.2.20030506123053.0163eec8 at pop.mcs.anl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.21
X-Spam-Level:
Hi NOC,
could you help Mr. Olson to debug this multicast problem?
regards,
ana
At 12:38 06/05/2003 -0500, Robert Olson wrote:
>Hello --
>
>I am trying to track down a problem with multicast routing between a
>machine at Argonne National Laboratory in the US with a machine at the
>Forschungszentrum Jülich.
>
>The following traffic isn't going through:
>
>Sender: 140.221.34.33
>Receiver: 134.94.106.106
>Group: 233.4.200.3/19004
>
>A traceroute from ANL to the Jülich machine looks like this:
>
>traceroute to 134.94.106.106 (134.94.106.106), 30 hops max, 38 byte packets
> 1 hsrp (140.221.11.253) 0.362 ms 0.276 ms 0.217 ms
> 2 guava-stardust.anchor.anl.gov (130.202.222.74) 0.305 ms 0.235
> ms 0.223 ms
> 3 mren-anl-gige.anchor.anl.gov (192.5.170.214) 2.173 ms 0.875
> ms 0.798 ms
> 4 chin-mren-ge.abilene.ucaid.edu (198.32.11.97) 0.909 ms 0.867
> ms 0.863 ms
> 5 nycmng-chinng.abilene.ucaid.edu (198.32.8.83) 33.148 ms 20.940
> ms 20.982 ms
> 6 abilene.uk1.uk.geant.net (62.40.103.25) 171.763 ms 171.916
> ms 171.701 ms
> 7 uk.fr1.fr.geant.net (62.40.96.89) 151.610 ms 152.076 ms 151.510 ms
> 8 fr.de1.de.geant.net (62.40.96.49) 152.223 ms 151.415 ms 151.269 ms
> 9 * * *
>10 cr-frankfurt1-po8-2.g-win.dfn.de (188.1.80.37) 151.739 ms 152.068
>ms 151.766 ms
>11 cr-koeln1-po0-1.g-win.dfn.de (188.1.18.86) 155.971 ms 157.902
>ms 155.772 ms
>12 ar-aachen1-po1-0.g-win.dfn.de (188.1.84.50) 157.484 ms 157.541
>ms 157.526 ms
>13 zam301.zam.kfa-juelich.de (134.94.111.238) 158.034 ms 157.818
>ms 158.415 ms
>14 * * *
>15 * * *
>16 * * *
>
>Looking at the NYCMNG Abilene router proxy, I find this:
>
>Querying NYCMng [New York, New York]: msdp source-active group 233.4.200.3
>Group address Source address Peer address Originator Flags
>233.4.200.3 140.221.34.33 198.32.8.196 192.5.170.2 Accept
> 134.55.3.3 192.5.170.2 Reject
> 193.10.68.85 192.5.170.2 Reject
> 199.109.5.1 192.5.170.2 Reject
>Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
>Instance: PIM.master Family: INET
>Group: 233.4.200.3
> Source: 140.221.34.33
> Flags: sparse
> Upstream interface: so-0/0/0.0
> Upstream State: Local RP, Join to Source
> Keepalive timeout: 181
> Downstream Neighbors:
> Interface: so-2/3/0.0
> 192.5.89.9 State: Join Flags: S Timeout: 193
>
>It appears that the join is missing toward geant.net; a working source
>(from earlier today) showed this state at NYCMNG:
>
>Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
>Instance: PIM.master Family: INET
>Group: 233.4.200.3
> Source: 141.142.66.75
> Flags: sparse
> Upstream interface: so-0/0/0.0
> Upstream State: Local RP, Join to Source
> Keepalive timeout: 204
> Downstream Neighbors:
> Interface: so-2/2/0.0
> 62.40.103.25 State: Join Flags: S Timeout: 209
> Interface: so-2/3/0.0
> 192.5.89.9 State: Join Flags: S Timeout: 183
>
>Please let me know if there is any more information I can give you, or if
>there is a better location to which this report can be sent.
>
>Thank you,
>--bob
From: "GEANT MULTICAST" <multicast at noc.geant.net>
To: "Robert Olson" <olson at mcs.anl.gov>,
"Abilene Network Operations Center" <noc at abilene.iu.edu>
Cc: <mcast-support at accessgrid.org>, <m.sczimarowsky at fz-juelich.de>,
<operations at dante.org.uk>, "Ana Romero" <Ana.Romero at dante.org.uk>,
<multicast at noc.geant.net>
References: <4.3.1.0.20030507141932.022b1810 at mail.dante.org.uk>
Subject: Re: Multicast problem from Argonne National Laboratory to Juelich
Date: Wed, 7 May 2003 16:38:20 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.21
X-Spam-Level:
Hi Robert,
The thing is that we receive well your source active (SA) MSDP from Abilene
network (AS11537) but our router (UK POP) reject it because your prefix
140.221.0.0/16 is not receive by the same gateway . In fact we received this
prefix via Global Crossing Network (AS3549). So you can create the RP tree.
Please find below :
admres at uk1.uk.re0> show msdp source-active group 233.4.200.3
Group address Source address Peer address Originator Flags
233.4.200.3 140.221.34.33 62.40.103.26 192.5.170.2 Reject
146.97.36.13 192.5.170.2 Reject
233.4.200.3 192.73.7.34 62.40.103.26 134.55.200.25 Accept
To the Abilene NOC : Could you please have a look at this routing problem
(?) and get back to us as soon as you get some news ?
Best Regards,
--------------
Jean-Luc HELION
Network Engineer
********************************************************************
GEANT NOC
Tel : +33 1 4313 8108
Fax : +33 1 4078 6400
Email :
trouble at noc.geant.net -- to report network problems
help at noc.geant.net -- to request help/information
abuse at noc.geant.net -- to report network abuse
********************************************************************
----- Original Message -----
From: "Ana Romero" <Ana.Romero at dante.org.uk>
To: <multicast at noc.geant.net>
Cc: <mcast-support at accessgrid.org>; <m.sczimarowsky at fz-juelich.de>; "Robert
Olson" <olson at mcs.anl.gov>; <operations at dante.org.uk>; <noc at noc.geant.net>
Sent: Wednesday, May 07, 2003 3:21 PM
Subject: Re: Multicast problem from Argonne National Laboratory to Juelich
Hi NOC,
could you help Mr. Olson to debug this multicast problem?
regards,
ana
At 12:38 06/05/2003 -0500, Robert Olson wrote:
>Hello --
>
>I am trying to track down a problem with multicast routing between a
>machine at Argonne National Laboratory in the US with a machine at the
>Forschungszentrum Jülich.
>
>The following traffic isn't going through:
>
>Sender: 140.221.34.33
>Receiver: 134.94.106.106
>Group: 233.4.200.3/19004
>
>A traceroute from ANL to the Jülich machine looks like this:
>
>traceroute to 134.94.106.106 (134.94.106.106), 30 hops max, 38 byte packets
> 1 hsrp (140.221.11.253) 0.362 ms 0.276 ms 0.217 ms
> 2 guava-stardust.anchor.anl.gov (130.202.222.74) 0.305 ms 0.235
> ms 0.223 ms
> 3 mren-anl-gige.anchor.anl.gov (192.5.170.214) 2.173 ms 0.875
> ms 0.798 ms
> 4 chin-mren-ge.abilene.ucaid.edu (198.32.11.97) 0.909 ms 0.867
> ms 0.863 ms
> 5 nycmng-chinng.abilene.ucaid.edu (198.32.8.83) 33.148 ms 20.940
> ms 20.982 ms
> 6 abilene.uk1.uk.geant.net (62.40.103.25) 171.763 ms 171.916
> ms 171.701 ms
> 7 uk.fr1.fr.geant.net (62.40.96.89) 151.610 ms 152.076 ms 151.510 ms
> 8 fr.de1.de.geant.net (62.40.96.49) 152.223 ms 151.415 ms 151.269 ms
> 9 * * *
>10 cr-frankfurt1-po8-2.g-win.dfn.de (188.1.80.37) 151.739 ms 152.068
>ms 151.766 ms
>11 cr-koeln1-po0-1.g-win.dfn.de (188.1.18.86) 155.971 ms 157.902
>ms 155.772 ms
>12 ar-aachen1-po1-0.g-win.dfn.de (188.1.84.50) 157.484 ms 157.541
>ms 157.526 ms
>13 zam301.zam.kfa-juelich.de (134.94.111.238) 158.034 ms 157.818
>ms 158.415 ms
>14 * * *
>15 * * *
>16 * * *
>
>Looking at the NYCMNG Abilene router proxy, I find this:
>
>Querying NYCMng [New York, New York]: msdp source-active group 233.4.200.3
>Group address Source address Peer address Originator Flags
>233.4.200.3 140.221.34.33 198.32.8.196 192.5.170.2 Accept
> 134.55.3.3 192.5.170.2 Reject
> 193.10.68.85 192.5.170.2 Reject
> 199.109.5.1 192.5.170.2 Reject
>Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
>Instance: PIM.master Family: INET
>Group: 233.4.200.3
> Source: 140.221.34.33
> Flags: sparse
> Upstream interface: so-0/0/0.0
> Upstream State: Local RP, Join to Source
> Keepalive timeout: 181
> Downstream Neighbors:
> Interface: so-2/3/0.0
> 192.5.89.9 State: Join Flags: S Timeout: 193
>
>It appears that the join is missing toward geant.net; a working source
>(from earlier today) showed this state at NYCMNG:
>
>Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
>Instance: PIM.master Family: INET
>Group: 233.4.200.3
> Source: 141.142.66.75
> Flags: sparse
> Upstream interface: so-0/0/0.0
> Upstream State: Local RP, Join to Source
> Keepalive timeout: 204
> Downstream Neighbors:
> Interface: so-2/2/0.0
> 62.40.103.25 State: Join Flags: S Timeout: 209
> Interface: so-2/3/0.0
> 192.5.89.9 State: Join Flags: S Timeout: 183
>
>Please let me know if there is any more information I can give you, or if
>there is a better location to which this report can be sent.
>
>Thank you,
>--bob
>
X-Sender: olson at pop.mcs.anl.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 07 May 2003 15:45:17 -0500
To: Jon-Paul Herron <jpherron at iu.edu>, <multicast at noc.geant.net>
From: Robert Olson <olson at mcs.anl.gov>
Subject: Re: Abilene - Geant not receiving ANL multicast prefixes
ENTRY=3567
Cc: <Ana.Romero at dante.org.uk>, <perations at dante.org.uk>,
<m.sczimarowsky at fz-juelich.de>, mcast-support at accessgrid.org
In-Reply-To: <BADED983.2184%jpherron at iu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
Very cool!
Martin - can you restart your rat on 233.4.200.3/19004 so we can see if the
traffic is flowing again?
thanks,
--bob
At 03:40 PM 5/7/2003 -0500, Jon-Paul Herron wrote:
>I took a look at the issue that was preventing Geant host from receiving
>multicast traffic from ANL. It looks like the issue was that we were
>preventing all ANL (and other Fednets) prefixes, both unicast and multicast
>from being advertised to ITNs. I've changed this to allow all multicast
>prefixes to flow freely to ITNs and Fednets, sinc multicast is AUP-free on
>Abilene. Can you verify that there is no longer a problem?
X-Sender: olson at pop.mcs.anl.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 08 May 2003 06:50:07 -0500
To: Jon-Paul Herron <jpherron at iu.edu>, <multicast at noc.geant.net>
From: Robert Olson <olson at mcs.anl.gov>
Subject: Re: Abilene - Geant not receiving ANL multicast prefixes
ENTRY=3567
Cc: <Ana.Romero at dante.org.uk>, <perations at dante.org.uk>,
<m.sczimarowsky at fz-juelich.de>, mcast-support at accessgrid.org
In-Reply-To: <BADED983.2184%jpherron at iu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.21
X-Spam-Level:
Sender: owner-mcast-support at accessgrid.org
Precedence: bulk
X-Whitelist-by-bob: yes
At 03:40 PM 5/7/2003 -0500, Jon-Paul Herron wrote:
>I took a look at the issue that was preventing Geant host from receiving
>multicast traffic from ANL. It looks like the issue was that we were
>preventing all ANL (and other Fednets) prefixes, both unicast and multicast
>from being advertised to ITNs. I've changed this to allow all multicast
>prefixes to flow freely to ITNs and Fednets, sinc multicast is AUP-free on
>Abilene. Can you verify that there is no longer a problem?
Traffic from ANL is indeed now flowing to Julich, as verified by the
application. Thank you to all for helping resolve this.
--bob
Querying NYCMng [New York, New York]: msdp source-active group 233.4.200.3
Group address Source address Peer address Originator Flags
233.4.200.3 140.221.34.33 198.32.8.196 192.5.170.2 Accept
62.40.102.47 192.5.170.2 Reject
62.40.103.25 192.5.170.2 Reject
134.55.3.3 192.5.170.2 Reject
193.10.68.85 192.5.170.2 Reject
199.109.5.1 192.5.170.2 Reject
Querying NYCMng [New York, New York]: pim join 233.4.200.3 extensive
Instance: PIM.master Family: INET
Group: 233.4.200.3
Source: 140.221.34.33
Flags: sparse
Upstream interface: so-0/0/0.0
Upstream State: Local RP, Join to Source
Keepalive timeout: 182
Downstream Neighbors:
Interface: so-2/2/0.0
62.40.103.25 State: Join Flags: S Timeout: 209
Querying NYCMng [New York, New York]: multicast route group 233.4.200.3
source-prefix 140.221.34.33/32 extensive
Family: INET
Group Source prefix Act Pru NHid Packets IfMismatch Timeout
233.4.200.3 140.221.34.33 /32 A F 368 338331 0 360
Upstream interface: so-0/0/0.0
Session name: Static Allocations
Forwarding rate: 36 kBps (101 pps)
More information about the ag-dev
mailing list