🚀 go-pugleaf

hamish@waikato.ac.nz writes:

>Apparently the new limit is 16 ethernet cards per server. Now all I have to do
>is find a server with that many slots in it :)


SMC has an EISA Ethernet card with two interfaces on it, each its own
separate network.  This could potentially allow 14 networks per EISA
server, if we assume video is built-in on the motherboard and one
slot is used for a SCSI host adapter.

We're about to put two of these cards in our server (once we resolve
the last remaining reliability problem).  My only concerns are the
overhead involved in routing between the interfaces, and the effects
of having NetWare and a high-end router routing between the same
networks.

WHAT I'D REALLY LIKE IS SOME WAY TO TURN-OFF IPX AND APPLETALK ROUTING
IN THE SERVER!!!

As a matter of policy, we prefer all routers to be under the control
of our central Network Operations Group.  Our cisco routers do an
excellent job of handling all the various protocols we use, including
IPX and AppleTalk.  The server's ability to also perform routing is
unneccessary, and seems to me to be a waste of the server's resources.
Having two (or more) routers going between networks makes things more
complex when troubleshooting or doing network planning.  In fact, we
occasionally run into problems with NetWare's routing that requires us
to turn-off particular paths or interfaces to resolve.

So it would be nice, at least from our standpoint, if we could tell
NetWare 2.x and 3.x to NOT route IPX and/or AppleTalk, as can
currently be done with TCPIP (via the "route=NO" bind parameter).

-- 
_________________________________________________________________________
RUCS     | Mark A. Medici, Systems Programmer III, User Services Division
User     | Rutgers University Computing Services, New Brunswick, NJ 08903
Services | [medici@gandalf.rutgers.edu]                    [908-932-2412]