Mirrored Server Setup Involves:

• Two servers with identical components. One server with NetWare* 4.1 installed on it, and one without.

• NetWare* 4.1 SFT III software installed on both servers.

• A Mirrored Server Link (MSL) connecting the servers (two PRO/100 Smart Adapters connected by a crossover cable or dedicated hub).

Note: See the Hints and Tips section at the end of this document for troubleshooting information.

The Servers:
Novell strongly recommends you use two identical servers. At the very least, the servers should have the same:

• CPU speed, memory, and storage capacity
  
  
• Brand or version of DOS
  
  
• Size non-DOS partition on their hard drive
  
  
• Monitors and monitor boards
  
  
• Amount of RAM (minimum: 16 MB)
  
  
  

The primary server should have NetWare 4.1 already installed.

The primary server is the SFT III server that network workstations see, and the one they send requests for network services. Routers on the internetwork see only the primary server and send routing packets to it.

The secondary server is the SFT III server that is activated when the primary server fails.

Novell SFT III:
NetWare System Fault Tolerance (SFT) III is supplemental Novell software that allows you to mirror one NetWare server to another. An SFT III configuration provides a secondary, identical server to immediately take over network operations when the primary server fails.

SFT III servers can reside on different network segments, as long as they share a dedicated mirrored server link and each can reach the other server on the internetwork.

Installing SFT III
Before installing SFT III, you need three blank disks.

1. Install NetWare 4.1 on the primary server.

2. Install the MSL adapters (PRO/100 Smart Adapters) and any other server adapters in both servers.

3. Boot to DOS on the primary server and switch to the root directory of the CD-ROM drive.

4. Type INSTALL.

5. Select NetWare Server Installation, NetWare 4.1 SFT III Installation, Convert NetWare 4.1 to SFT III, and then follow the instructions on the screen.

6. When asked to specify the MSL driver for the MSL board, press Ins and insert the PRO/100 Smart adapter's Configuration and Driver disk. Enter A:\MSL for the path.

7. When asked to choose a partitioning method, choose:
   "Automatically" - assumes disk storage is identical on both servers

   "Manually" - allows you to specify a NetWare partition size and HotFix* Redirection Area.

8. Follow the instructions on the screen.

When installation is complete, do not bring down the server or turn on Server Test Mode until the hard disks are fully mirrored.

After the initial install, you can start the mirrored servers by typing MSERVER at the DOS prompt on both servers. Then, from one of the server consoles, type ACTIVATE SERVER. This starts server mirroring.

If you have problems, check the parameters in your IOSTART.NCF file (the same file should be on both servers). For a sample IOSTART.NCF file, see the end of this document.

The MSL:
The MSL is a dedicated, high-speed connection between SFT III primary and secondary servers. The MSL manages server synchronization.

Two Intel PRO/100 Smart adapters connected with a TPE CAT 5 crossover cable (or a dedicated hub) can serve as this high speed link. For information on crossover cables, see the help file called "Making a crossover cable."

Follow the instructions in the Installation Guide to install the adapters and the MSL driver.

Hints and Tips:
Sample IOSTART.NCF file

This file, located in the DOS partition, normally contains the IOEngine name and IPX internal network number; loading instructions for disk and MSL drivers, IOEngine SET parameters; loading instructions for NLMs that don't require an active MSEngine or a mounted SYS: volume.

IOENGINE NAME MSERVER_IO1
IOENGINE IPX INTERNAL NET 2F5D65A4
SET Memory IOEngine Borrows Ahead from MSEngine = 100000
SET New Start Address For Unclaimed Memory Block = 15728640
SET Secondary Take Over Wait Time = 5
SET MSL Error Wait Time = 4

LOAD IDE port=1F0 int=E
LOAD E100SMSL.MSL SLOT=48 SPEED=100 NAME=MSL1 <-- Should be the

The disk & MSL drivers should be in same directory as MSERVER.EXE.

Sample IOAUTO.NCF file

This file, located in the DOS partition or SYS: volume, normally contains commands for loading network drivers and binding network protocols; loading instructions for NLMs that require an active MSEngine and a mounted SYS: volume.

LOAD E100S.LAN slot=14 frame=ETHERNET_802.2 name=SMART1
BIND IPX to SMART1 net=12345678

Troubleshooting
MSL isn't activated

Verify that the same MSL driver is loaded on both servers and cables are installed correctly.

MSL times out when a device driver is loaded.

Load the device driver before loading the MSL driver, or add the following line to your IOSTART.NCF file:

SET MSL Error Wait Time = [var.]

Frequent Ups and Downs of the IPX Internet

Add the following lines to your IOSTART.NCF file:

SET IPX Internet Down Wait Time = [var.]
SET MLS deadlock Wait Time = [var.]

Implementing Dual Processing

To implement dual processing with NetWare 4.1 SFT III, you must have a server with two CPUs installed and a dual processor driver.

1. From the IOEngine console of the server with two CPUs installed, load the dual processing driver. For example:

   LOAD 2NDPROC

2. To implement dual processing at startup, put the load command in the IOSTART.NCF file of the server with two CPUs.

This applies to:

Intel® PRO/100 Smart Adapter