Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!uunet!rufus!drake.almaden.ibm.com!drake
From: drake@drake.almaden.ibm.com
Newsgroups: comp.unix.aix
Subject: Re: strange tcpip problem:  SOLVED!!
Message-ID: <850@rufus.UUCP>
Date: 14 Jun 91 01:02:50 GMT
References: <1991Jun12.230426.22643@milton.u.washington.edu> <843@rufus.UUCP> <676836895.5438@mindcraft.com>
Sender: news@rufus.UUCP
Organization: IBM Almaden Research Center
Lines: 13

In article <676836895.5438@mindcraft.com> karish@mindcraft.com (Chuck Karish) writes:
>
>Record the cards' Ethernet ID numbers, and query them at boot time?

That's another obvious approach ... which leads to similar surprises as
the slot-based method.  With the Ethernet-ID approach you can indeed move
the cards around from slot to slot, but you can't replace a broken card
with a new card without reconfiguring the software.  


Sam Drake / IBM Almaden Research Center 
Internet:  drake@ibm.com            BITNET:  DRAKE at ALMADEN
Usenet:    ...!uunet!ibmarc!drake   Phone:   (408) 927-1861