home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
escsi.exe
/
ESCSI.TXT
< prev
next >
Wrap
Text File
|
1993-09-17
|
8KB
|
194 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: ELS NetWare Level II v2.15 with PS/2 SCSI
DOCUMENT ID: TID000114
DOCUMENT REVISION: A
DATE: 01JUL93
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: ESCSI.EXE
NOVELL PRODUCT and VERSION:
NetWare Pre 3.11 and 2.2
ABSTRACT:
This file is a version of NetWare ELS Level II v2.15c that supports IBM
PS/2 SCSI disk controllers.
_________________________________________________________________
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.
NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.
HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.
_________________________________________________________________
Self-Extracting File Name: ESCSI.EXE
Files Included Size Date Time
ESCSI.TXT (This File)
DISKED.EXE 165468 7-30-90 2:10p
ELS2_2.OBJ 180500 7-30-90 2:12p
NDELS2_2.OBJ 199855 7-30-90 2:12p
INSTOVL.EXE 133554 7-30-90 2:10p
COMPSURF.EXE 103246 7-30-90 2:10p
VREPAIR.EXE 94762 7-30-90 2:11p
INSTALLATION
To install this special version of ELS NetWare Level II v2.15c that
supports IBM PS/2 SCSI disk controllers, follow the steps listed below.
1. Your Novell Authorized Reseller (or some other representative) should
have downloaded a file called ESCSI.EXE from NetWire and unpack it yielding
the following six files.
ELS2_2.OBJ 180500 7-30-90 2:12p
NDELS2_2.OBJ 199855 7-30-90 2:12p
INSTOVL.EXE 133554 7-30-90 2:10p
COMPSURF.EXE 103246 7-30-90 2:10p
VREPAIR.EXE 94762 7-30-90 2:11p
DISKED.EXE 165468 7-30-90 2:10p
2. Copy these files to working copies of your ELS NetWare Level II v2.15c
diskettes (3.5" media) as indicated below.
ELS2_2.OBJ to EDOBJ-2
NDELS2_2.OBJ to ENDOBJ-2
INSTOVL.EXE to ELSGEN
COMPSURF.EXE to UTIL-1
VREPAIR.EXE to UTIL-1
DISKED.EXE to UTIL-1
Be sure to use working copies. If you use original copies, you will lose
the original files. You will need to use them if you ever decide to switch
to a server with a non-SCSI disk controller.
3. Proceed with the installation as described in the ELS NetWare Level II
Installation Manual with one exception described below.
4. Do not run COMPSURF on the server. However, make sure that the server
disk has been low-level formatted using the REFERENCE DISK. If you are
forced into COMPSURF during the installation, answer "No" or "0" to all
questions except the last "Yes" to "Are these parameters correct?"
TECHNICAL NOTES
The following information may be useful in installing and operating this
system.
1. This version supports both caching and non-caching PS/2 SCSI
controllers.
2. The SCSI driver linked with this version of ELS NetWare Level II v2.15c
is IBMSCSI.OBJ v1.02. This information may also be displayed in the Channel
Statistics screen of FCONSOLE.
3. FCONSOLE displays incorrect disk channel information in three of its
screens; Channel Statistics, Disk Mapping Information, and Disk Statistics.
Even if only one SCSI adapter is installed in the server, FCONOLE displays
as if two channels (controllers or drives) exist. Simply ignore the second
entry. This will be corrected in the future version.
4. This version has been tested with PS/2 Models 65SX 16MHz, 70 25MHz, 80
20MHz and 80 25MHz with both caching and non-caching SCSI controllers. LAN
cards used are NE/2 3C523.
The following are more detailed discussion on the limitations of this
version of SCSI driver and PS/2 SCSI controllers in general.
An understanding of this discussion is not required for installing the
system.
IBMSCSI.OBJ v1.02 (900731)
(NOTE: IBMSCSI.OBJ v1.02 supports fixed drives, not removables).
Version 1.02 (900731) of the IBMSCSI.OBJ NetWare 286 disk driver reports
different numbers to NetWare than the actual SCSI ID numbers for attached
disk drives. Thus, the Controller number as indicated by INSTALL or
COMPSURF is not the drive's actual SCSI ID controller number as one might
expect. The way in which the driver maps SCSI ID controller numbers to
NetWare Controller numbers is as follows: it reverses the order of the SCSI
controller numbers and then renumbers them starting with 0 when it reports
the attached devices to NetWare. (See Fig. 1 and 'BACKGROUND' below).
SCSI ID NetWare
Controller # Controller #
------------ ------------
6 --> 0
4 --> 1
2 --> 2
1 --> 3
0 --> 4
Fig. 1. Example Mapping for Five Devices
HARDWARE INSTALLATION
NOTE: The SCSI address of the NetWare boot device attached to an IBM PS/2
SCSI Adapter card must be 6,0. Therefore, the boot device's address jumpers
(or switches) must be set at six.
The default NetWare channel configurations are hard-coded in the v1.02
driver. Channel 0 uses I/O base address 3540h.
The I/O base address 3578h is not supported in the v1.02 driver. Adaptec
4000 Series bridge controllers do not support the full SCSI Common Command
Set and, therefore, do not work with the PS/2 SCSI Adapter.
The v1.02 driver has been tested with: Model 65SX 16 MHz, Model 70 386 25
MHz, Model 80 20 MHz and 25 MHz. LAN cards used: NE/2 and 3C523.
BACKGROUND
During the NetWare 286 network generation process (using either NETGEN or
ELSGEN), and while using other NetWare disk utilities such as COMPSURF, the
user encounters a screen which describes the data storage devices which are
attached to the server. Three numbers are used to identify a device: the
Channel number, the Controller number, and the Drive number.
The Channel number (0 through 4) is the NetWare logical communication path
with a disk controller card. The Controller number (for non-SCSI controller
cards) refers to the disk controller card number (usually 0 or 1). The
Drive number (for non-SCSI devices) refers to the logical number of the
device attached to the disk controller card (usually 0 or 1).
The SCSI (Small Computer System Interface) specification uses SCSI I.D.
(identification) numbers and LUNs (Logical Unit Numbers) to identify SCSI
controllers and devices on a SCSI bus. SCSI I.D. numbers (which range from
0 to 7) represent a SCSI controller address on the SCSI bus. Each SCSI
controller can theoretically have up to eight attached devices, each
identified with a LUN. A device's complete SCSI address consists of the
SCSI I.D. number of its SCSI controller and its own LUN (example: 6,0).
Embedded [controller] SCSI drives, have a built-in SCSI controller.
Therefore, only one LUN is possible (LUN = 0). The drive's SCSI address
jumpers (or switches) correspond to the SCSI controller address. Whatever
address they are set at becomes the first digit in the complete SCSI
address of the device (example: an embedded SCSI drive with address
switches set at 4 has a SCSI address of 4,0).
The way in which SCSI addresses are mapped into NetWare's device
identification method of using a Channel number, a Controller number, and a
Drive number is as follows. The SCSI controller number becomes the NetWare
Controller number and the SCSI LUN becomes the NetWare Drive number. Due
to the way in which NetWare starts at Controller 0 (and goes up to 6) to
scan for the boot device and since the IBM PS/2 SCSI adapter starts the
boot device scan with SCSI controller 6 (and goes down to 0), the
IBMSCSI.OBJ v1.02 disk driver reverses the order of the SCSI controller
numbers and renumbers them starting with 0 when it reports the attached
devices to NetWare.
Therefore, the controller numbers in NetWare device identification screens
do NOT represent the true SCSI controller numbers.