Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!cbosgd!ucbvax!SUN.COM!melohn%sluggo
From: melohn%sluggo@SUN.COM (Bill Melohn)
Newsgroups: mod.protocols.tcp-ip
Subject: Re:  problems reaching cu20b
Message-ID: <8606061834.AA00127@sluggo.sun.uucp>
Date: Fri, 6-Jun-86 14:34:32 EDT
Article-I.D.: sluggo.8606061834.AA00127
Posted: Fri Jun  6 14:34:32 1986
Date-Received: Fri, 6-Jun-86 23:50:21 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 11
Approved: tcp-ip@sri-nic.arpa

Chances are good that the network which cu20b is on has fallen out of
the limited size EGP reachablity table that you (or more likely your
core gateway) use. This appears to happen to our non-backbone network
every once in a while.  The solution is to get more powerful core
gateways that implement EGP and provide more space for the ever
increasing numbers of non-backbone internet networks. If access to cu20b
is really important to your site, you might consider adding the entry
for the columbia gateway to ECLx's INTERNET.GATEWAYS file. That way you
will not have to ask your core gateway how to get to cu20b.  

Bill