Multicast status

jerrys at highway1.org jerrys at highway1.org
Mon Apr 3 18:06:52 CDT 2000


Hi guys-

The ASN-10886 is registered to UMD, but it represents the MAX Layer 3
network.  NSF peers with MAX (at UMD), and MAX peers with Abilene (NYCM) and
VBNS (PYM).

I am not multicast peering with VBNS, just with Abilene.  It is conceivable
this could be contributing to some of the difficulties. NSF is msdp peering
with WASH-CORE (max), and MBGP/PIM-SM with WASH-AG (the max border).
I can bring up the VBNS peering relatively easily.  I'll contact VBNS
tuesday morning to chase this and see if Kevin or Zaid can sanity check my
mcast configs.

BTW- Please check your email address for me- it should be
jerrys at max.gigapop.net

Thanks
Jerry
301-346-1849 mobile



> -----Original Message-----
> From: Gatchell, Douglas [mailto:dgatchel at nsf.gov]
> Sent: Monday, April 03, 2000 6:56 PM
> To: 'Tony Rimovsky'
> Cc: 'ag-tech at mcs.anl.gov'; zalbanna at mci.net; kthomp at mci.net; Jerry
> Sobieski (E-mail)
> Subject: RE: Multicast status
>
>
> I just received a note from Jerry Sobieski. He is aware of
> the problem and
> is working on it for UMD. He expects to have it resolved in a
> couple of
> days.
>
> Doug
>
> -----Original Message-----
> From: Tony Rimovsky [mailto:tony at ncsa.uiuc.edu]
> Sent: Monday, April 03, 2000 6:52 PM
> To: Gatchell, Douglas
> Cc: 'ag-tech at mcs.anl.gov'; zalbanna at mci.net; kthomp at mci.net
> Subject: Re: Multicast status
>
>
> Then the path is asymetric, at least for some sites, which is likely
> contributing to the problem.  Do you know which path the UMD
> folks intend?
>
> (to save people the lookups: ASN-10886 is Univ Maryland.
> ASN-102 is the NSF
> and of course ASN-145 is the vBNS and ASN-11537 is Abilene.))
>
> ACCESS-DC view: (we explicitly prefer vBNS paths for now...)
> ballston-rtr>show ip bgp 192.12.209.24
> BGP routing table entry for 192.12.209.0/24, version 424680
> Paths: (3 available, best #2)
>   Not advertised to any peer
>   11537 10886 102, (received & used)
>     141.142.11.62 from 141.142.11.62 (198.32.8.247)
>       Origin IGP, localpref 100, valid, external
>       Community: 756089732 756089782
>   145 10886 102
>     141.142.11.66 from 141.142.11.66 (204.147.128.136)
>       Origin IGP, localpref 400, valid, external, best
>       Community: 9503620
>   145 10886 102, (received-only)
>     141.142.11.66 from 141.142.11.66 (204.147.128.136)
>       Origin IGP, localpref 100, valid, external
>       Community: 9503620
>
> NCSA view:
> tony at charlie> show route 192.12.209.24
>
> inet.0: 2872 destinations, 2872 routes (2854 active, 0
> holddown, 29 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 192.12.209.0/24    *[BGP/170] 1d 14:34:44, localpref 100
>                       AS path: 145 10886 102 I
>                     > to 141.142.11.1 via at-1/0/0.2
>
> inet.2: 8811 destinations, 8811 routes (8809 active, 0
> holddown, 2 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 192.12.209.0/24    *[BGP/170] 1d 14:34:44, localpref 100
>                       AS path: 145 10886 102 I
>                     > to 141.142.11.1 via at-1/0/0.2
>
>
> On Mon, 03 Apr 2000, Gatchell, Douglas wrote:
>
> > with an IP traceroute we seem to go nsf->umd->abilene
> >
> > -----Original Message-----
> > From: Tony Rimovsky [mailto:tony at ncsa.uiuc.edu]
> > Sent: Monday, April 03, 2000 6:20 PM
> > To: Gatchell, Douglas
> > Cc: 'ag-tech at mcs.anl.gov'; zalbanna at mci.net; kthomp at mci.net
> > Subject: Re: Multicast status
> >
> >
> > I still don't see it at either of my sites.  Looks like your path is
> > nsf->umd->vbns.
> >
> > Zaid/Kevin -- any signs of (S,G) (192.12.209.24,
> 224.2.177.155)?  I don't
> > see any SA's or routes at NCSA or ACCESS-DC.
> >
> > Here is what the beacon server says he sees:
> >
> > Reporter: beacon at tc-view                            Session:
> > 224.2.177.156:56565
> >
> > Receiver                        Last Update        Loss
> Delay   Jitter
> > OutOrd
> >
> -------------------------------+--------------+--------+------
> --+--------+--
> > ----
> > DebA at taz.lbl.gov                17:17:37 04/03     0.00
> -82351.3     4.52
> 0
> > VuiLe at laihwa                    17:17:27 04/03     0.05
> -73084.9     3.56
> 0
> > beacon at IFRAG2                   17:17:36 04/03     0.00
> -82251.8     3.00
> 0
> > beacon at agaudio.bu.edu           17:17:37 04/03     0.00
> -82382.8     4.72
> 0
> > beacon at agaudio.osc.edu          17:17:37 04/03     0.00
> -82380.3     1.30
> 0
> > beacon at agvideo.bu.edu           17:17:37 04/03     0.00
> -82383.5     3.49
> 0
> > beacon at agvideo.osc.edu          17:17:37 04/03     0.00
> -82381.9     1.04
> 0
> > beacon at av1-utah-ag.cs.utah.edu  18:12:44 04/03     0.00
> -3389543     0.86
> 0
> > beacon at blackwidow.engr.ukans.ed 18:17:36 04/03     0.00
> -3681337     1.04
> 0
> > beacon at pdq.cc.ndsu.nodak.edu    17:17:37 04/03     0.00
> -82346.4    11.00
> 0
> > beacon at tc-view                  17:16:14 04/03     0.00
> 0.00     0.21
> 0
> > beacon at video.ccs.uky.edu        17:17:37 04/03     0.00
> -82360.8     1.06
> 0
> >
> > Here is what the beacon server says other people see of him
> (ie. no one
> sees
> > him.)
> >
> > Receiver: beacon at tc-view                            Session:
> > 224.2.177.156:56565
> >
> > Reporter                        Last Update        Loss
> Delay   Jitter
> > OutOrd
> >
> -------------------------------+--------------+--------+------
> --+--------+--
> > ----
> > beacon at tc-view                  17:16:52 04/03     0.00
> 0.00     2.87
> 0
> >
> > On Mon, 03 Apr 2000, Gatchell, Douglas wrote:
> >
> > > Hum - I have vic running: vic -t 127 224.2.177.155/55524
> > >
> > > I just set started transmitting video on this group.
> > >
> > > Doug
> > >
> > > -----Original Message-----
> > > From: Tony Rimovsky [mailto:tony at ncsa.uiuc.edu]
> > > Sent: Monday, April 03, 2000 5:44 PM
> > > To: Gatchell, Douglas
> > > Cc: 'Robert Olson'; ag-tech at mcs.anl.gov
> > > Subject: Re: Multicast status
> > >
> > >
> > > Doug -- in addition to the beacon, do you have vic
> running in one of the
> > > access-grid groups?  I don't see any multicast routes matching
> > > 192.12.209.0/24 at all either here or at ACCESS-DC.
> > >
> > > On Mon, 03 Apr 2000, Gatchell, Douglas wrote:
> > >
> > > > OK - I see the "beacon" sub directory batch file looks
> more like this
> > then
> > > > the "server" sub directory batch file. It's now running
> but I don't
> see
> > > > myself with beacon viewer.
> > > >
> > > > Doug
> > > >
> > > > -----Original Message-----
> > > > From: Robert Olson [mailto:olson at mcs.anl.gov]
> > > > Sent: Monday, April 03, 2000 5:09 PM
> > > > To: Gatchell, Douglas
> > > > Cc: ag-tech at mcs.anl.gov
> > > > Subject: RE: Multicast status
> > > >
> > > >
> > > > At 05:03 PM 4/3/2000 -0400, Gatchell, Douglas wrote:
> > > > >I am now (from 192.12.209.24) - I was reluctant to
> turn it on since
> I'm
> > > not
> > > > >sure what it does. Can you see us now?
> > > >
> > > > Nope ... the beacon config should look something like
> > > >
> > > > multicast_group=224.2.177.156
> > > > multicast_port=56565
> > > > beacon_server=glacier.mcs.anl.gov
> > > > server_port=12345
> > > > time_to_live=127
> > > >
> > > > --bob
> > >
> > > --
> > >
> >
> +-------------------------------------------------------------
> ------------+
> > >  | Tony Rimovsky, Manager -- Network Development    Phone: +1 217
> 244-4728
> > |
> > >  | National Center for Supercomputing Applications  FAX:   +1 217
> 244-1987
> > |
> > >  | 605 E Springfield, Champaign IL, 61820
> tony at ncsa.uiuc.edu
> > |
> > >
> >
> +-------------------------------------------------------------
> ------------+
> >
> > --
> >
> +-------------------------------------------------------------
> ------------+
> >  | Tony Rimovsky, Manager -- Network Development    Phone:
> +1 217 244-4728
> |
> >  | National Center for Supercomputing Applications  FAX:
> +1 217 244-1987
> |
> >  | 605 E Springfield, Champaign IL, 61820
> tony at ncsa.uiuc.edu
> |
> >
> +-------------------------------------------------------------
> ------------+
>




More information about the ag-tech mailing list