Function of NVSRAM Cable Parts IML Limits of Passplay HD LED Does Not Work Cyrix/Non-SOD Type 1 Incompatibility? Cache Size Cache Size Factors Cache Size and Diminishing Returns Generic 30 Pin SIMMs for Cache Accessing the RAID Configuration Configuration Utility FWR Bios Flash Disks BIOS Release Features Complex BIOS Levels Required Slots Passplay Fits LVD on Passplay Specifications For FWR Stuff that is relevant, but chaotic... (fits, doesn't it?)
Fast Wide RAID Adapter (Passplay) FRU 92F0335
There is NO external port on the Passplay! Notes:
NVSRAM Function
Cable Parts
A Better Cable Hack?
My Take on it:
IML/Boot Limits
of Passplays
HD LED Doesn't
Work
Cyrix/Non-SOD
Incompatibility?
Cache Size How important is the amount of cache ram on the PassPlay RAID adapter--4 MB, 16 MB, 64 MB? Under what circumstances will a cache increase pay off? (The system in question is running NetWare 4.1, but I'm interested in general info on this subject.) I notice that the more recent Cheetah RAID adapter has only 4 MB with no upgrade possible. It seems counterintuitive, but I seem to remember reading somewhere that large amounts of controller cache aren't really that useful with modern drives and operating systems. From Peter
Cache Size
Depends On
Like on all caches there is a limit where enlarging the
cache any further makes no sense. And I think this limit is at around 4MB
on a 5 drives Raid-5 system running under OS/2 or WinNT. The content-redundancy
of the data is mostly not given - so the cache is mostly used to buffer
the Raid data-overhead between the drives (during reading / writing / synchronizing
the Raid structure) - on the transfer between drive-subsystem and processor
the cache does not play a major role.
Cache Size
and Diminishing Returns
IBM or Generic
SIMMs?
Access the RAID Configuration Both the FWR (Passplay) and FWSR (Cheetah) are only configurable through the RAID Utilities disk. You CANNOT see the SCSI Disks under "Set and View SCSI Devices" like normal SCSI drives. Boot with FWSR Option Disk, #1 ver. 2.31 in order to view or configure the array. Both adapters use the same Utilities disk of the later IBM F/W Streaming RAID Adapter /A (Codename "Cheetah" - with external port) since both are based on Intel i960 / Mylex / NCR technology. There was a single-disk version 2.22, which should be unique for all /A-Raid adapters of that kind, but not the PCI-versions. The RAIDADM (manager) should work on both /A-adapters. Configuration
Utility version 2.31 consists out of two disks:
Not sure if this fits-
NOTE:All systems, except the 95-466,
95-560, 95 A-466, 95 A-560 and 9585-0Kx, require that the standard SCSI
adapter or system board resident SCSI controller remain connected to the
IML and/or boot hard file.
Fast/Wide RAID Flash Bios for "Passplay" FRU 92F0335
SR
Flash BIOS ver. 1.61 Only for RAID controller WITHOUT an external port
on it!
Passplay
Code Releases
From Peter
1.60
1.61
1.62
1.63
1.99
Complex
BIOS Requirements
Slots Passplay will Fit The Passplay is a Type 5 form factor card (it's big). There are cutouts in 95 and 95A cases that will allow the edge of the card at the bracket end to fit. Dennis Smith turned me on to them. Slots 2-4 have these cutouts- The 95s don't have a cushion in them, 95As do.
LVD on Passplay
From Peter
Specifications for FW RAID
|
From Peter
Remember the "Cheetah"-Adapter's
"Real Trade Name" ? IBM Fast/Wide Streaming Raid Adapter /A.
It it an ordinary Fast / Wide indended
for single-ended SCSI devices. It does however take U/W LVD drives, because
these are downward-compatible to single-ended, which the old
"high-voltage differential" are *not*.
If you get - for
example - a set of U/W "Low Voltage Differential" (LVD) IBM DDRS 4.5 or
9.1GB drives then they will nicely run
with the Cheetah. I have some of them in "Starship" - my Server 520 attached
to the Fast/Wide RAID Adapter PCI. No problem. You can even mix them with
"ordinary" F/W or U/W drives. Same for the Cheetah and even the older Passplay.
# of Drives
Supported
From Peter
>Is it possible to connect more than 7 drives
to a PassPlay adapter? I tried to connect a short cable with an external
connector on both the channels of the PassPlay adapter without any luck.
The adapter supports only 7 devices.
Technically it is a Fast-SCSI adapter, but only a single channel with a
crippled ID-section. It does not use the MSB of the ID signal, even if
you
attach a Wide device to it.
The thing is a bit mixed up and
screwed down. It has two ports to make cabling easier for upper and lower
bay - electronically they are treated as one port.
RAID without
Bays 'n Trays
From Peter
I used a 7-drop cable from an 9585
on the first (inner) channel of the Passplay. Installed six HDs and one
CD-ROM drive with the IDs running 0 - 6 ... and the Passplay did recognize
only the "bays 1 - 4" which correspond with the drive IDs 0 - 3 (0 is the
CD-ROM, IDs 1 - 6 are HDs).
Then I plugged the cable to the
second (rear) channel - and it did show only the bays 5 - 7 (lower triple)
- but shows the drive infos for the devices installed at IDs 1 - 3 and
not ID-0 (the CD-ROM) !!. After that I set the drives to 0-1-2-3 (CD, HD1,
HD2, HD3) connected to inner channel and 1-2-3 (HD4, HD5, HD6) connected
to the outer channel using a second cable.
The drive cages from a 9595A "Array"
machine are designed to send the IDs 1, 2 and 3 - given that the drives
are wired properly with using the thin "drive addressing cable".
(Ed. that's part
of the drive tray)
One cage in the top 5.25" bay, one
in the lower 5.25" bay and using the proper "server 95 internal cables"
result in the IDs 1,2,3 for the top cage, 5,6,7 (!!) for the lower cage
(and ID-0 for the CD-ROM in the single Half Height 5.25" bay). See the
table below for some "visual aid" on the SCSI-ID confusion.
So obviously the two "channel" connectors
are predefined, the first connector uses the IDs directly with ID2 fixed
masked to "0", while the second connector has the ID2 bit fixed set to
"1" here.
This leads to the following dependency:
+-----------------------------------+-------+
| 421 = Binary ID-values
| Bay # |
+-----------------------------------+-------+
| 000 = ID-0 = CD-ROM
| 1 |
| 001 = ID-1 = Top Cage,
drive 1 | 2 |
| 010 = ID-2 = Top Cage,
drive 2 | 3 |
| 011 = ID-3 = Top Cage,
drive 3 | 4 |
+-----------------------------------+-------+
| 101 = ID-5 = Bottom Cage, drive 1 |
5 |
| 110 = ID-6 = Bottom Cage, drive 2 |
6 |
| 111 = ID-7 = Bottom Cage, drive 3 |
7 |
+-----------------------------------+-------+
Attention !!
These "IDs" in the list above used here are the
ones the controller "sees". Not the ones that are really represented through
the device SCSI-ID jumpering. ID-7 under normal circumstances is used for
the SCSI controller itself - and in fact the "seen" IDs seem to be remapped
somehow. See the binary values to explain the dependencies between position
and ID sent back to the controller.
This list proves that the ID4 bit
is used to differ between "upper" and "lower" triple pack.
When referring to this D040 number, please use the entire number, since this will help Technical Support identify specific features.
Mfg.No.
Mylex Model
D040322
DAC960M
D040325
DBX960M
D040331
DAC960M-2
I have an older controller with version 2.xx FW, can I update the FW
to the 3.xx?
Not all boards will support the upgrade to 3.xx firmware.
If the controller has a revision number of D040347 or greater, the board
will support the upgrade. This revision label is usually found on the back
(non-component side of the board).
SCSI type | SCSI-2 Fast/Wide |
SCSI bus path / speed | 16 bit / 20 MB/sec |
I/O bus path / speed | 32 bit / 40 MB/sec streaming |
I/O features | Streaming data transfer
Address parity and data parity |
RAID levels | RAID 0, 1, Hybrid 1, 5
4 ind (A, B, C, D) / 8 logical arrays |
Tagged Command Queuing | Yes |
Processor | i960 at 25 MHz |
Size | Type 5 (only fits Model 85 or 95) |
Channels | Two (both internal) |
Connectors | Two internal only |
Devices supported | 7 devices per adapter |
Cache std / max | 4 MB / 64 MB (with parity) |
Cache method | 4 sockets for 30 pin 80ns SIMMs |
Cache configurations | 4, 16, or 64 MB only |
Cache write policy | Write-through or write-back |