Ethernet and Fast Ethernet Cards in 3.12 Server (long)

Ethernet and Fast Ethernet Cards in 3.12 Server (long)

Post by Mark Andrew Spenc » Fri, 15 May 1998 04:00:00



(This is a follow-up post on the same topic.)

I am adding a Fast Ethernet card to a 486-DX4-100 server running 3.12.
I've read the instructions from the NIC manufacturer--Global Data
Supply, www.gd.to--but it's not 100-percent clear to me how to proceed.

The instructions--attached--state that for multiple NICs and frame
types, the load statements should be as follows:

        LOAD RTSSRV FRAME=Ethernet_802.2 NAME=LAN_A SLOT=1 SPEED=100
        BIND IPX TO LAN_A NET=22

However, the AUTOEXEC.NCF file we currently have does not use either
NAME=, SLOT=, or SPEED= commands:

---------------------------------------------------------------------------------------------------
file server name  SERVER_A
ipx internal net   ABE
register memory 1000000 7000000

load c:\novell\aha1540 port=330 int=b dma=5 above16=y verbose=y
load c:\novell\aha1540 port=130 int=c dma=6 above16=y verbose=y

set display lost interrupt alerts=off
set maximum directory cache buffer=125
set maximum service processes=30

mount sys

load install

load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.3
load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.2

bind IPX to 3C5X9 [PORT=300 INT=A FRAME=ETHERNET_802.3] net=A
bind IPX to 3C5X9 [PORT=300 INT=A FRAME=ETHERNET_802.2] net=B

spool 0 to PRINTQ_0
SPOOL1 to PRINTQ_1

mount HISTORY
mount HISTORY2
mount HISTORY3

load PSERVER MALONE_PRINT

load RSPX
load REMOTE POGO
load UPS TYPE=STANDALONE PORT=231 DISCHARGE=10 RECHARGE=30
load MONITOR

Also, after typing CONFIG at the console, I get:

File Server Name: SERVER_A
IPX Internal Network Number: 00000ABE

3Com Etherlink 3C5X9 Family
Version 4.01d Jan 13, 1995
Hardware Setting: I/O Port 300h to 30Fh Interrupt Ah
Node Address: 0060083396E6
No board name defined
Frame Type: Ethernet_802.3
LAN Protocol: IPX Network 0000000A

3Com Etherlink 3C5X9 Family
Version 4.01d Jan 13, 1995
Hardware Setting: I/O Port 300h to 30Fh Interrupt Ah
Node Address: 0060083396E6
No board name defined
Frame Type: Ethernet_802.2
LAN Protocol: IPX Network 0000000B

-----------------------------------------------------------------------------------------------------------

My questions are:
        1. Do I need to unload the existing Ethernet drivers, then reload them
with NAME=, SLOT=, and SPEED= commands? How do I determine what the
NAME= and SLOT= are for both cards?

        2. The existing Ethernet drivers are loaded with PORT=300 and int=A. Do
I need to know these values for the new card? How do I determine the new
values of PORT= and int= for the new card?

        3. Can I load the changes from the console without making any changes
to the AUOTEXEC.NCF file, so that in the event something doesn't work
out, I can get back to square one simply by rebooting the server?

Mark Spence

[ Nw31x.txt 3K ]
   Server Driver for NetWare 3.1X

   Introduction:
   -------------
   This document describes the procedure to install the NetWare v3.1X
   server driver for FE-1439TX RTL8139 Fast Ethernet adapter.

   Location of Driver:     \NWSERVER\31X\RTSSRV.LAN

   Installation Procedure:
   -----------------------
      Before you start with the installation  process,  make sure that
      the Novell NetWare v3.1X server is properly installed.
      Similarly, your adapter should also be properly installed in your
      server.

      1. These files can be obtained from FE-1439TX driver disk subdirectory
         A:\NWSERVER\31X

         NBI31X.NLM
         MSM31X.NLM
         ETHERTSM.NLM

      2. If you can log into the server as a supervisor , copy RTSSRV.LAN
         relative files from the FE-1439TX Driver Diskette subdirectory
         A:\NWSERVER\31X into the NetWare 386 subdirectory SYSTEM of your
         server. (If some files exists, rename the existing files in the
         SYSTEM subdirectory).

      3. When the NetWare server prompt appears (indicated by a colon),load
         your server driver. Simply type:

         : LOAD NBI31X <Entet>
         : LOAD RTSSRV <Enter>

         or, you can directly load file from FE-1439TX RTL8139 driver disk :

         : LOAD A:\NWSERVER\31X\NBI31X <Enter>
         : LOAD A:\NWSERVER\31X\RTSSRV <Enter>

      4. Bind IPX to the adapter driver. At the NetWare server prompt
         ,type:

         :BIND IPX TO RTSSRV <Enter>

      5. After pressing <Enter> the computer prompts you for the Network
         Number. For details on how to assign this number,please consult
         your NetWare Server Installation Manual.

      6. Add the load and bind statements you require to the server's
         AUTOEXEC.NCF file so that the LAN driver will load automatically
         each time the server starts up.

   NOTES:
   ------
      1. Installing Multiple LAN Adapters:
         The keyword  "SLOT"  is  provided for multiple LAN adapters in a
         single server by the driver RTSSRV.LAN.  So, add  "SLOT" in LOAD
         commands. For example:

         LOAD RTSSRV FRAME=Ethernet_802.2 NAME=LAN_A SLOT=1
         BIND IPX TO LAN_A NET=11
         LOAD RTSSRV FRAME=Ethernet_802.2 NAME=LAN_B SLOT=2
         BIND IPX TO LAN_B NET=22

      2. The keyword  "SPEED"  is  provided for specifying adapter's speed
         (10M/100M), add SPEED in LOAD commands. For example:

         LOAD RTSSRV FRAME=Ethernet_802.2 NAME=LAN_A SLOT=1 SPEED=100
         BIND IPX TO LAN_A NET=11

      3. Installing One LAN adapter with Multiple Frame Types:
         When  binding multiple frame types to one adapter, enter a LOAD
         and BIND statement for each frame type. Each LOAD statement will
         use a different network number is required on the bind statement.
         You need  to supply  a name on each load line in order to avoid
         being  prompted  for which  board to bind IPX to. If you do not
         have the name option in the AUTOEXEC.NCF , it will not  execute
         completely without user intervention.  Example:

           LOAD RTSSRV FRAME=ETHERNET_802.3 NAME=IEE8023
           BIND IPX TO IEE8023 NET=11111
           LOAD RTSSRV FRAME=ETHERNET_802.2 NAME=IEE8022
           BIND IPX TO LAN8022 NET=22222

   If problems occur during the binding process, your  screen will prompt
   you with error  messages.  Please refer to your NetWare 386 manual for
   details on these messages.

                                                        -- Edward Liu --

 
 
 

Ethernet and Fast Ethernet Cards in 3.12 Server (long)

Post by Howard Cole » Sat, 16 May 1998 04:00:00


You would be much served by using the NAME=<NIC-NAME> option.  
I am also curious as to why you are manually mounting sys: but that is
another post topic.  Using the NAME= eliminates the need for all that info
you have in the bind statement as follows:

load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.3 NAME=3comA
load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.2 NAME=3comB

bind IPX to 3comA net=A
bind IPX to 3comB net=B

While we're at it using the "Mount all" command instead of mounting each
volume manually is much cleaner.

To answer your questions in order:
1.      If you are adding aditional ethenet Cards a. make sure that they do not
use a driver with the same file name.  and Yes USE The Name= option as that
will simplify what IPX net is binding to what board, but if the drivers are
currently running without those optional parameters, No, you don't have to
add them.

2.      Yes you will definitely need to know those things for the new boards IF
THE DOCS say those parameters are required to load the new drivers.  I
usually only specify the PORT= just so that I can bind multiple Frame types
to the same board without getting the nagging question from the server at
startup, "do you want to add addtional frame types to existing board?"  You
find those out while the server is down, and you run the configuration
utility that came with the new cards.  You must make sure they are not
using the same port number or irq's of any existing boards, including the
two Adaptec SCSI cards you are running.

3.      sure just type the load commands from the console prompt after downing
and powering off the server and inserting the new cards.  (and of course
running the config utility to make sure no other adapter is using the I/O
port or IRQ).  You type them in exactly as it appears in the autoexec.ncf
file. for example to manually load a 3Com ethernet card:
load 3c5x9 port=300 frame=ETHERNET_802.2 NAME=3C5_1
Then bind ipx as follows (if it loads at all):
bind ipx to 3C5_1 NET=A

If the board doesn't load like you like, but loads any way just unload it:
unload 3c5x9

Howard Coles Jr. (CNE)
Please Reply to hcoles at genesco dot com



Quote:> (This is a follow-up post on the same topic.)

> I am adding a Fast Ethernet card to a 486-DX4-100 server running 3.12.
> I've read the instructions from the NIC manufacturer--Global Data
> Supply, www.gd.to--but it's not 100-percent clear to me how to proceed.

> The instructions--attached--state that for multiple NICs and frame
> types, the load statements should be as follows:

>    LOAD RTSSRV FRAME=Ethernet_802.2 NAME=LAN_A SLOT=1 SPEED=100
>    BIND IPX TO LAN_A NET=22

> However, the AUTOEXEC.NCF file we currently have does not use either
> NAME=, SLOT=, or SPEED= commands:

----------------------------------------------------------------------------
-----------------------

- Show quoted text -

Quote:> file server name  SERVER_A
> ipx internal net   ABE
> register memory 1000000 7000000
> load c:\novell\aha1540 port=330 int=b dma=5 above16=y verbose=y
> load c:\novell\aha1540 port=130 int=c dma=6 above16=y verbose=y
> set display lost interrupt alerts=off
> set maximum directory cache buffer=125
> set maximum service processes=30
> mount sys
> load install

> load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.3
> load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.2

> bind IPX to 3C5X9 [PORT=300 INT=A FRAME=ETHERNET_802.3] net=A
> bind IPX to 3C5X9 [PORT=300 INT=A FRAME=ETHERNET_802.2] net=B

> spool 0 to PRINTQ_0
> SPOOL1 to PRINTQ_1
> mount HISTORY
> mount HISTORY2
> mount HISTORY3

> load PSERVER MALONE_PRINT

> load RSPX
> load REMOTE POGO
> load UPS TYPE=STANDALONE PORT=231 DISCHARGE=10 RECHARGE=30
> load MONITOR
> My questions are:
>    1. Do I need to unload the existing Ethernet drivers, then reload them
> with NAME=, SLOT=, and SPEED= commands? How do I determine what the
> NAME= and SLOT= are for both cards?

>    2. The existing Ethernet drivers are loaded with PORT=300 and int=A. Do
> I need to know these values for the new card? How do I determine the new
> values of PORT= and int= for the new card?

>    3. Can I load the changes from the console without making any changes
> to the AUOTEXEC.NCF file, so that in the event something doesn't work
> out, I can get back to square one simply by rebooting the server?

> Mark Spence   Server Driver for NetWare 3.1X
>                                                         -- Edward Liu --


 
 
 

Ethernet and Fast Ethernet Cards in 3.12 Server (long)

Post by Kevin D. Snodgras » Sat, 16 May 1998 04:00:00


...<big snip>...

Quote:>         1. Do I need to unload the existing Ethernet drivers, then reload them
> with NAME=, SLOT=, and SPEED= commands? How do I determine what the
> NAME= and SLOT= are for both cards?

No, each card/driver combo have specific load line
parameters.  If the 3c5X9 loads fine as is, then leave it.

Quote:>         2. The existing Ethernet drivers are loaded with PORT=300 and int=A. Do
> I need to know these values for the new card? How do I determine the new
> values of PORT= and int= for the new card?

No, use the load line parameters that the documention tells
you to use.

Quote:>         3. Can I load the changes from the console without making any changes
> to the AUOTEXEC.NCF file, so that in the event something doesn't work
> out, I can get back to square one simply by rebooting the server?

Yes, NetWare is wonder in this area.  You can load and
unload drivers almost at will on a live production system.
If the new card is installed try loading the driver and
binding IPX and/or IP to it to see how it works.  Unload the
driver and try again.  NT bigots eat your heart out.

BTW, on these load line parameters.  The 3c5X9 is an ISA
card and the important info when dealing with ISA ethernet
cards is the I/O register port address (Port=300 in your
case, configurable with a DOS config util generally), the
IRQ (hardware Interrupt ReQuest, 10 or hex A in your case),
and on cards that use shared memory the shared memory
address (the 3c5X9 appearantly does not use shared memory).
PCI and EISA cards (I assume MCA as well but have no
experience with MCA) often have physical slot number
(SLOT=).

The new card that you have is a 10/100 switchable and you
can, via load line parameters, force it to be either
10base-x or 100base-TX.  The instructions also tell you to
use a LAN= parameter.  This lets you "name" each
driver/frame combo.  You could use that info to change your
current 3c5X9 lines from:

load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.3
load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.2
bind IPX to 3C5X9 [PORT=300 INT=A FRAME=ETHERNET_802.3]
net=A
bind IPX to 3C5X9 [PORT=300 INT=A FRAME=ETHERNET_802.2]
net=B

to something like this:

load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.3
NAME=3C_3
load c:\novell\3C5X9 port=300 int=A frame=ETHERNET_802.2
NAME=3C_2
bind IPX to 3C_3  net=A
bind IPX to 3C_2  net=B

Also, why are you loading both 802.3 and 802.2?  Seems a bit
redundant.  Fix your clients to all run the same frame type
and drop the uneeded frame.

--
Kevin D. Snodgrass

 
 
 

1. Cisco 3640 fast ethernet to fast ethernet routing

I am currently trying to route between two 3640's with fast ethernet
interfaces.  The outside interfaces get sent over a cable company provided
point to point line that has been tested to 45Mbit/s.  However when going
across the routers with FTP traffic we are only seeing about 11-12
Mbits/sec.

Is this a limitation of the routers?

There is no filtering or traffic shaping going on, the Interfaces are
running at 100 Full Duplex and routing is done with 3 static routes,  The
router can pretty much dedicate itself to forwarding these packets.

TIA

Andrew Thornhill

2. AU Privacy Commissioner Unveils Internet guidelines

3. Ethernet and Fast Ethernet in one server

4. RtlUnicodeToMultiByteN

5. 3Com Fast Ethernet card conflict with NT 4.0 Server on Pentium Pro?

6. Migrate Unicode Data from SqlServer to Oracle.

7. To Ethernet card or too not Ethernet card, that is the Question for @Home Service

8. CCIE Lab Test

9. 1 ethernet card rather than 2 ethernet cards?

10. Whats the best (or worst) PCI Ethernet card for 3.12 (25 user)

11. VERY long distance Fast Ethernet

12. pretty long distance multi switch/hub fast.ethernet networking

13. Cisco SOHO 91 Router showing Ethernet 0 instead of Fast Ethernet 0