schmidt@cadlab.uucp (Michael Schmidt) (03/30/89)
We have a bunch of Apollo's (AEGIS SR9.7.1, DOMAIN/IX SR9.5,
COMAIN TCP/IP 3.0) running on a token ring. One machine has a
real ethernet interface connected to our main ethernet.
The Apollos are doing well with each other as does the gateway
machine with our other hosts. But, the internet routing seems not
to work. Is there anything special, we have to consider?
I thought the routing daemons running on e.g. our Suns should
catch the new Class C network and they would update the routing
tables. That is apparently not the case. A manual "route add ..."
has the desired effect, but is not really, what we want to do (on
each machine).
--
Michael Schmidt, CADLAB / FB 17, Uni-GH Paderborn, Bahnhofstr. 32,
D-4790 Paderborn, West Germany
Mail: schmidt@cadlab.UUCP or schmidt%cadlab@uunet.uu.net
"AMOK - Im Tiefflug ueber Deutschland" HRKdbfunk@ICAEN.UIOWA.EDU (David B. Funk) (03/31/89)
WRT posting <442@cadlab.cadlab.de>, > We have a bunch of Apollo's (AEGIS SR9.7.1, DOMAIN/IX SR9.5, > COMAIN TCP/IP 3.0) running on a token ring. One machine has a > real ethernet interface connected to our main ethernet. > > The Apollos are doing well with each other as does the gateway > machine with our other hosts. But, the internet routing seems not > to work. Is there anything special, we have to consider? TCP/IP 3.0 had a serious bug in its "/etc/routed" that destroyed dynamic routing. The failure mode for the TCP 3.0 Routed/Rip_Server is as follows: The program may appear to work for some period of time, but eventually it will stop working correctly. Gateways may inform neighboring gateways that they have been disconnected from one of their interfaces. Gateways may also broadcast the routing information to the wrong port, so that the routing information will not be received by neighboring gateways. When this happens, gateways will drop routes involving Apollo gateways. The Routed/Rip_Server will generate increasing volumes of broadcast traffic on all networks to which it is connected. Most of these broadcasts will never be received, but they will impose an increased load on the network. There is a patch tape from Apollo that will fix this. You want patch 66 and patch 67. Contact you Apollo service representatives and ask about the patch tape. If possible, consider upgrading to TCP v3.1, it fixes the bug, provides improved performance, and new features. Dave Funk
schmidt%majestix.cadlab.DE%cadlab@unido.UUCP ("Michael Schmidt") (04/03/89)
From: "David B. Funk" <dbfunk%icaen.uiowa.edu@mcvax> Organization: Iowa Computer Aided Engineering Network, University of Iowa Date: Fri, 31 Mar 89 00:27:50 CST There is a patch tape from Apollo that will fix this. You want patch 66 and patch 67. Contact you Apollo service representatives and ask about the patch tape. If possible, consider upgrading to TCP v3.1, it fixes the bug, provides improved performance, and new features. We will upgrade to 3.1. Thank you.