Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!cec2!news
From: jab0396@cec1.wustl.edu (John A. Breen)
Newsgroups: comp.sys.apollo
Subject: Re: Networking Apollo rings together with Cisco router boxes.
Keywords: cisco DDS
Message-ID: <1991Feb2.202024.8027@cec1.wustl.edu>
Date: 2 Feb 91 20:20:24 GMT
References: <1991Feb1.000434.244@zoot.avgrp.cr.rok.com> <86164@unix.cis.pitt.edu>
Distribution: comp.sys.apollo
Organization: Washington University, St. Louis MO
Lines: 25

In article <86164@unix.cis.pitt.edu> fuller@nye.nscee.edu (Charles S. Fuller) writes:
>The first thing you'll notice when configuring the cisco is that they
>don't provide a node id; you'll have to make one up.

It's been a while since we hooked up to the ethernet (and I had
retired from sys-adminning just before that, so I just watched), but
as I recall, the ciscos were pretty much transparent (they were
already set up for general ethernet connections).  I think we just
assigned network IDs to each ring and one to the ethernet as a whole,
and that was it.  In fact, I remember when we enabled routing, we saw
a network we didn't recognize: it turned out to be a ring at one of
our facilities on the west coast (although that did cause a minor
problem, since they had assigned a different network ID to the
ethernet).  But from the Apollo filesystem point of view we've had
virtually no problems.

Now, subnetting for TCP/IP is a different problem; some day I'll have
to relate that horror story...

John A. Breen
McDonnell Douglas Missile Systems Co.
-----------------------------------------------------------------------------
John A. Breen                |     "Where is fancy bread,
    jab0396@cec1.wustl.edu   |         in the heart or in the head?"
    johnb@hobbes.mdc.com     |                   -- Willy Wonka