Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!jade!ucbvax!sdcsvax!hub!dag
From: dag@hub.ucsb.edu (Darren Daggit)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: routing problems?  Core gateways?
Message-ID: <281@hub.ucsb.edu>
Date: 14 Jan 88 07:05:51 GMT
References: <4481@sdcsvax.UCSD.EDU>
Reply-To: dag@nobbs.ucsb.edu (Darren Griffiths)
Organization: PCS, University of California, Santa Barbara
Lines: 65

In article <4481@sdcsvax.UCSD.EDU> brian@sdcsvax.UCSD.EDU (Brian Kantor) writes:
>I can't ping SEISMO.CSS.GOV from our host 'SDCSVAX.UCSD.EDU' at
>26.5.0.3.  I can ping SEISMO quite nicely from our neighbor on the same
>IMP (NOSC.MIL at 26.0.0.3).  We are both using the same default gateway
>at 26.2.0.73, which seems to be the way the packets are going.
>
>SEISMO isn't an isolated case - I can't ping any of the following hosts
>from SDCSVAX, but I can from NOSC:
>
>	uxe.cso.uiuc.edu	128.174.5.54
>	mcc.com			10.3.0.62
>	ius2.cs.cmu.edu		128.2.254.176
>	cs.utah.edu		10.0.0.4

Brian,

I can get to all of these hosts, and haven't seen any problems routing to them.
We are sending stuff through SDSC to the NSFNET backbone and on from there,
so things probably aren't touching the same piece of ethernet cable that you
are on, but the systems are reachable.

There have been reported problems that affect at least one of these systems
(cs.utah.edu).  The gateway psc.psc.edu has evidently been in trouble over 
the past few days, and things haven't been shuttled around the way they
should.

>There are others.  And there are hundreds of mail messages waiting in
>our queue because we can't get to their nameservers to get delivery 
>addresses.  (There ARE hosts on network 10 that I can ping, btw, such 
>as UCBVAX.)

I don't have my map of how the UCSD campus is connected to SDSC at hand, but
UCBVAX may not be a good example.  If you are routing things through the least
number of hops then stuff to UCBVAX probably isn't going to your default
gateway, the fastest route would be through the SDSC Proteon and out to the 
BARRNET (There are two R's in BARRNET aren't there?) backbone.  Is this right?
I have noticed that when the SDSC link into the NSFNET goes down we can still
get to the BARRNET, so the SDSC Proteon is routing things correctly in that
respect.

>I called the Milnet NOC, and they seemed to think that it's a core
>gateway problem and told me to call BBN.  BBN assures me that they were
>already working on the problem - seems that they see a problem with one
>of the gateways, but I don't know what that problem would be.

That is probably the PSC.PSC.EDU gateway, maybe it is effecting more than
one site.
 
  I hope this helps,
     --darren

>	Brian Kantor
>		UCSD Office of Academic Computing
>		Academic Network Operations Group  
>		UCSD B-028, La Jolla, CA 92093 USA
>		brian@sdcsvax.ucsd.edu	(619) 534-6865


-----------------------------------------------------------------------------
Darren Griffiths                      BITNET   -   DAG@SBITP
Systems Manager                       ARPA     -   DAG@NOBBS.UCSB.EDU
Physics Computer Services                          (128.111.8.50)
University of California              HEPNET   -   NOBBS::DAG  
Santa Barbara, CA  93106                           13326::DAG
(805)961-2602