Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson
From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson)
Newsgroups: comp.sys.apollo
Subject: 400t nodes
Message-ID: <9009222118.AA24683@pan.ssec.honeywell.com>
Date: 22 Sep 90 21:18:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

One tiny 'gotcha' with the new series 400t nodes running in a token
rung environment.  It's not anything major, but it might confuse
someone else like it confused me for a while.

We run TCP/IP services, and, since we have very few nodes (3) with
more than one controller, we used the 'net0' device on ifconfig.
Then we got the 400t nodes in, and they didn't want to start TCP/IP
service up automagically.

GOTCHA!  These nodes have 2 controllers!  'net0' is now an ambiguous
device reference, and ifconfig does nothing.  Changing to 'dr0'
made it work.

Question for HP/Apollo people who are reading this:  
Could you make 'net0' be the primary boot device?  Failing that, a
mention of this 'feature' would be nice if included in the upgrade
literature.


John Thompson (jt)
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

As ever, my opinions do not necessarily agree with Honeywell's or reality's.
(Honeywell's do not necessarily agree with mine or reality's, either)