• Please review our updated Terms and Rules here

DEC/Compaq DS-SWXRA-HC

M

maxfli

Experienced Member
Joined
Oct 21, 2012
Messages
179
I'm looking at the DEC/Compaq DS-SWXRA-HC as a disk array solution for my two DEC 3000-700 systems (they have onboard Centronics 50 pin SCSI interface).

I have been looking for a manual to explain how this array works and a hardware diagram but have been unable to find one.

It looks like the array uses a different SCSI connector, I was wondering if I could convert the Centronics 50 pin to what is on the DS-SWXRA-HC, I've just been unable to determine what SCSI interface it uses.

Does anyone have any insight into this array?

Thanks!!
 
From a quick look around for information those StorageWorks RAID systems probably have 16-bit LVD interface RAID controllers. I don't know if they would work in 8-bit SE mode if connected to an 8-bit SE host.

One possible option which might improve the disk performance of your TURBOchannel system is a KZTSA 16-bit SCSI host adapter. The issue there is that is an HVD interface, so you would need an HVD to LVD converter.

KZTSA SCSI Storage Adapter Installation and User’s Guide
Order Number: EK–KZTSA–UG .C01
http://www.vaxhaven.com/images/2/23/EK-KZTSA-UG-C01.pdf

There is currently a KZTSA-AA listed on eBay for $30 in the US.
 
Is the SW301-AA a better fit, can’t seem to fin any manuals on that array?
 
For StorageWorks RAID systems it depends on the controller. There are at least three flavors, HSZxx = SCSI, HSDxx = DSSI, HSJxx = CI.

The HSZ10, HSZ15, HSZ40, and HSZ50 are Fast, Wide, Differential SCSI interface controllers for 8-bit Single-Ended SCSI–2, and should be compatible with a TURBOchannel KZTSA Fast, Wide, Differential SCSI host adapter.

StorageWorks™ Array Controllers HS Family of Array Controllers User’s Guide
Order Number: EK–HSFAM–UG. D01
The StorageWorks Array Controllers HS Family of Array Controllers User’s Guide contains instructions for installing and using HSJ30, HSJ40, HSD30, HSZ40–Ax, and HSZ40–Bx array controllers.
sup.xenya.si/sup/info/digital/MDS/jun99/Cd3/STORAGE/HSFAMUGD.PDF

StorageWorks™ Solutions
SW300-Series RAID Enclosure Installation and User’sGuide
Order Number: EK–SW300–UG. A01
This manual describes the SW300-series redundant array of independent disks (RAID) enclosure, the rules for unpacking and installing, configuring the enclosure, and its associated components, and describes error analysis and fault isolation. Procedures for replacing the major components also are described.
www.vaxhaven.com/images/9/91/EK-SW300-UG-A01.pdf


This SW301 manual specifically mentions DSSI, which is not what you would want for a controller interface.

StorageWorks™ Solutions
24 SBB, DSSI RAID Subsystem, Deskside Expansion Unit (SW301) User’s Guide
Order Number: EK–SW301–UG. A01
This guide describes the procedures that install and operate the 24 SBB, DSSI RAID Subsystem deskside expansion unit (SW301).
manx-docs.org/collections/mds-199909/cd3/storage/sw301uga.pdf


The only StorageWorks controllers I have used are the simple HSD10 DSSI interface controllers, which plug into a single BA350 slot. The more advanced controllers seem to require a separate cache module, and seem to be installed in redundant pairs, and need flash cards for their internal OS. I'd be interested in trying an HSD30 DSSI controller setup sometime, but putting all of the parts together would be more expensive that it would be worth to me.
 
Last edited:
If you did add a TURBOchannel KZTSA FWD (Fast, Wide, Differential, also known as HVD) SCSI host adapter to your DEC 3000-700 systems from what I understand that should be compatible with that DUAL HSZ50 controller setup in the BA350-MB shelf.

The SCSI connectors on the front of the HSZ50 are 12-39921-01 H885-AA Tri-Link connector blocks for the host adapter connection. The Tri-Link connector block is removable and connects to a single SCSI connector on the front of the HSZ50. The idea there is that the host SCSI bus can chain in and out through the Tri-Link block and if the HSZ50 controller fails and needs to be replaced the Tri-Link block can be removed with the host side SCSI cables still attached, keeping the host side SCSI bus intact.

The device side SCSI bus connectors downstream of the HSZ50 controller are on the backplane under the lower HSZ50 controller. There should be six HD50 SCSI-2 connectors. Each one is a separate bus. If there are dual HSZ50 controllers installed each bus is connected to both controllers as SCSI IDs 7 and 6, so only 6 devices can be connected to each bus.

BA350-MA-Shelf-Layout.jpg

StorageWorksFamily
BA350–MA Controller Shelf User’sGuide
Order Number: EK–350MA–UG. A02
This manual describes the BA350–MA StorageWorks controller shelf
and the rules for configuring the shelf and its associated power supplies,
device addresses, and SCSI buses. Procedures for replacing power
supplies, blowers, and shelves are also described
sup.xenya.si/sup/info/digital/MDS/jun99/Cd3/STORAGE/350MAUGA.PDF

For the SCSI devices downstream of the HSZ50 controllers they could be installed in a BA350-LA 8-bit shelf.

BA350–LA Modular Storage Shelf User’s Guide
Order Number: EK–350LA–UG–001
This manual describes the BA350–LA storage shelf and the rules for
configuring the shelf to include power, system building blocks (SBBs),
device addressing, and SCSI buses. Procedures for determining shelf
status and replacing blowers are also included.
sup.xenya.si/sup/info/digital/MDS/jun99/Cd3/STORAGE/350LAUG1.PDF

16-bit SCSI devices could be installed in a 16-bit BA356 shelf and connected through an 8-bit I/O module installed in the BA356.

7 Device, 16-Bit SBB Shelf (BA356−S Series) User’s Guide
Order Number: EK–BA356–UG. B01
This publication describes the major StorageWorks 16-bit components (such as
shelves, power units, SBBs, SCSI buses, I/O modules, and cables), status displays,
specifications, and replacement procedures.
www.vaxhaven.com/images/b/bf/EK-BA356-UG.B01.pdf

8-Bit I/O Module (BA35X−MG) User’s Guide
EK−BA35X−MG. A01
This document describes the 8-bit I/O module (see Figure 1). It explains how to install the I/O module in the
BA356 shelf, and how to set the shelf small computer system interface (SCSI) addresses. The basic documentation
set for the I/O module is StorageWorks Solutions, 7 Device, 16-Bit SBB Shelf (BA356–S series) User’s Guide
(EK–BA356–UG. B01).
sup.xenya.si/sup/info/digital/MDS/jun99/Cd3/STORAGE/35XMGUGB.PDF


In a real DEC installation all of the storage shelf blocks would be installed in a purpose built rack. For your own use they could just be stacked on top of each other.


My only actual experience with these is with an HSD10 DSSI controller installed in a BA350–LA storage shelf connected between a VAX host DSSI interface and 8-bit SCSI devices installed in the same BA350–LA, or connected to 16-bit SCSI devices in a BA356 shelf with a BA35X-MG 8-bit I/O module installed. I have no actual experience with HSZxx SCSI controllers.
 
Just in case it helps: I was in the StorageWorks team in CXO, and I had a minor role in writing firmware for the HSZ40, HSZ70, HSG80, etc. There's a "chance" that I could tell you something useful, if reminded with pictures and such (the official product names were not used much in the hallways, because by the time those names were chosen, we were moving on to something else).
I used to have an HSZ10 (or was it Z20?) box at home, to use with my PC. It would support 1 or 2 controllers, and 6(?) SBB's. As I recall, the FW card from an HSZ40 was the same - the Z10 was just a stripped-down Z40 (architecturally).
I think the SBB shelves could be configured with an adaptor module to let you use narrow SCSI, wide SCSI, or wide differential SCSI, at least in some situations.

Pete
 
@gslick - So that I understand this, the shelfs that house the SCSI devices (hard drives, solid state drive and tape drives) are connected to the back of the HSZ50 via SCSI cables? Just in the picture(in the ebay link) of the rear of the HSZ50 enclosure I don't see any additional ports.

@saipan59 - Any input you have is helpful.
 
maxfli said:
@gslick - So that I understand this, the shelfs that house the SCSI devices (hard drives, solid state drive and tape drives) are connected to the back of the HSZ50 via SCSI cables? Just in the picture(in the ebay link) of the rear of the HSZ50 enclosure I don't see any additional ports.
Click to expand...

No, the connectors for the SCSI bus downstream of the HS controller in the BA350-M shelf are on the same side of the backplane that the HS controllers plug into. They are located below the lower HS controller and aren't easy to see in photos as they are back inside the shelf. I don't know if the SCSI cables can be connected and disconnected without removing the HS controllers. The gap in the front is too narrow to reach into with the HS controllers installed.

This figure from the manual referenced below shows a BA350-M shelf with two HS controller installed with 6 SCSI cables exiting from the front below (or to the left of the vertically mounted shelf in this case) the lower HS controller.

BA350-MA-Cables.jpg


StorageWorks™Array Controllers
HS Family of Array Controllers User’s Guide
Order Number: EK–HSFAM–UG. B01
The StorageWorks Array Controllers HS Family of Array Controllers
User’s Guide contains instructions for installing and using HSJ30,
HSJ40, HSD30, and HSZ40 array controllers.
vaxhaven.com/images/d/d1/EK-HSFAM-UG-B01.pdf
 
saipan59 said:
Just in case it helps: I was in the StorageWorks team in CXO, and I had a minor role in writing firmware for the HSZ40, HSZ70, HSG80, etc.
Pete
Click to expand...

Are images of the firmware that gets loaded onto the PCMCIA cards for the various HS controllers archived anywhere? That would be very useful.

Do the HS controllers have a boot loader in firmware built into the controllers that allows firmware to be downloaded to a blank PCMCIA card through the serial console interface? If you acquire an HS controller without a firmware card and acquire a compatible blank PCMCIA card, is there a way to get the HS controller up and running with the latest firmware?

I've been able to do that with a DECserver 900TM by booting it over the network and downloading the firmware to a compatible blank PCMCIA card. No idea if there is a similar way to do that with an HS controller.
 
maxfli said:
@gslick - So that I understand this, the shelfs that house the SCSI devices (hard drives, solid state drive and tape drives) are connected to the back of the HSZ50 via SCSI cables? Just in the picture(in the ebay link) of the rear of the HSZ50 enclosure I don't see any additional ports.

@saipan59 - Any input you have is helpful.
Click to expand...

Here's what I see/recall from the eBay listing pictures:
No cabling on the back side - just the two fan assemblies.
The connectors for cabling to the disk shelf comes out of that slot/gap that is *below* the 2nd cache module in the first picture. I don't know if the connectors are recessed, and we can't see them, or if there is an adapter module that is missing. The docs would explain it.
In the picture, each controller has a single host-side connector, but there is a little adapter mounted on there that provides two connectors for each. This allows the cabling and host connections to all be dual-redundant.
Those type of cache modules contain unusual sealed lead-acid batteries that were famous for failing, and leaking acid that corroded things. The actual batteries (two per module) are roughly 4" X 6" X 3/8", green plastic. Some versions of the FW will allow you to ignore a failed battery state and run with writeback caching enabled anyway (normally, a battery issue will cause the controller to go to Writethru mode, which greatly reduces performance).
Note the little short serial cable adapter - that's required to plug in a normal DEC serial cable to see the console.

Pete
 
gslick said:
Are images of the firmware that gets loaded onto the PCMCIA cards for the various HS controllers archived anywhere? That would be very useful.

Do the HS controllers have a boot loader in firmware built into the controllers that allows firmware to be downloaded to a blank PCMCIA card through the serial console interface? If you acquire an HS controller without a firmware card and acquire a compatible blank PCMCIA card, is there a way to get the HS controller up and running with the latest firmware?
Click to expand...
I don't know if FW images are archived anywhere.
Bootloading: As I recall, a 'bootloader' capability is built-in. I think it required dual-redundant controllers. There was a host-based tool that allowed downloading a new image, which would overwrite the image on one of the controllers. Then it did some sanity checks, and if it looked OK, it would then burn the other controller with the new image. Throughout the process, one controller stays online to do I/O, so unless there was a problem, the host I/O could stay up. I could be a bit wrong on these details. I suppose it was an internal-use-only tool, but I'm not sure.
Our Test Team used the tool/process to automatically codeload many controllers every night with the latest formal build version, then run a large suite of tests with large and varied configurations.
When doing FW development (by someone like me), developers didn't use the codeload process because it was inconvenient. Don't remember the issues, but it may have required a specific host server config, and/or required a complete dual-redundant config (which a developer like me may not have), etc. So, we had a couple of PCMCIA card burners in the lab - it would burn a card in a minute or two, and I could just plug it into my own test controller. Note: The FW card is under that little cover on the 'front' edge of the controller, so you don't have to change anything to swap a card.

BTW, on the eBay listing, I note that it says serial cable not included. I would ask if the little adapter is included...

Pete
 
Other comments on that eBay listing:
The console shows that FW version is V52Z-0. I'm not familiar with it - when I was doing stuff, the version numbers were V3.2Z on the Z40. I don't know what the difference is between a Z50 and a Z40, but I don't remember touching a Z50 - maybe it was a later variant that replaced the Z40?

Correction on what I said before about the cache modules: This HW does NOT have internal batteries I think (which explains why it can say "Cache is Good" after all these years). Note the little "D" connector that is in the middle of the cache module's panel - that's where a battery cable plugs in. The HSG80 controllers (Fibre Channel) have the same battery connector - on a G80, the battery is in an SBB. Since a battery pair is obviously not included, you should research whether this unit will allow Writeback Caching without a battery. Without writeback, the performance is not very good. The FW probably has a switch called CACHE_UPS. When the switch is on, you are telling it that you have the whole system on a UPS, so you don't care about the battery state.
If you run without a battery, and without a UPS, then a power hit can cause Data Lost on your RAIDsets.

Pete
 
saipan59 said:
Correction on what I said before about the cache modules: This HW does NOT have internal batteries I think (which explains why it can say "Cache is Good" after all these years). Note the little "D" connector that is in the middle of the cache module's panel - that's where a battery cable plugs in.
Pete
Click to expand...

There are some of the Micro D9 connector HSX cache battery cables listed on eBay. Looks like 17-04321-02 is the part number.

Also looks like HS35X-BA (single battery) or HS35X-BB (dual battery) are the cache battery modules. Doesn't look like there are any great deals on those available at the moment.
 
saipan59 said:
Other comments on that eBay listing:
The console shows that FW version is V52Z-0. I'm not familiar with it - when I was doing stuff, the version numbers were V3.2Z on the Z40. I don't know what the difference is between a Z50 and a Z40, but I don't remember touching a Z50 - maybe it was a later variant that replaced the Z40?
Pete
Click to expand...

Identifying Your HSOF Software Revision Level
You can identify HSOF Version 5.2 Software by entering the SHOW
THIS_CONTROLLER command at the CLI prompt. The resulting display lists
the software revision level as Version “V52Z-x” (where x represents the number
of patches associated with this Version of software that are correctly installed).

DIGITAL StorageWorks HSZ50 Array Controller Operating Software
HSOF Version 5.2 Release Notes
Order Number: EK-HSZ50-RN. D01
manx-docs.org/collections/antonio/dec/MDS-2000-01/cd3/STORAGE/HSZ50RND.PDF
 
saipan59 said:
BTW, on the eBay listing, I note that it says serial cable not included. I would ask if the little adapter is included...
Pete
Click to expand...

As far as I can tell some of the earlier HS controllers had MMJ connectors for the serial console, while on the HSZ50 it looks like they changed to using RJ12 connectors. That little 12-43346-01 adapter might just be a straight through RJ12 to MMJ coupler, or maybe it is an MMJ to MMJ coupler and the short 17-03511-04 that plugs into the HSZ50 is a straight through RJ12 to MMJ cable. In either case, a standard BC16E MMJ cable would plug into the terminal or host side of the 12-43346-01 coupler.

This one is listed as a 17-06511-04, while that tag on the cable does say 17-03511-04. Can't really see from the photos whether the plugs on each end are RJ12 or MMJ.

www.ebay.com/itm/DEC-17-06511-04-HSX-RJ12-TO-MMJ-ADAPTER-CABLE/173864040027

Without the original console cable and adapter you could probably just use a straight through RJ12-RJ12 cable and an RJ12 to DB9 adapter such as one of these wired up appropriately:

Monoprice DB9M/RJ-12,Modular Adapter
https://www.monoprice.com/product?p_id=1149

Monoprice DB9F/RJ-12,Modular Adapter
https://www.monoprice.com/product?p_id=1150
 
Last edited:
gslick said:
As far as I can tell some of the earlier HS controllers had MMJ connectors for the serial console, while on the HSZ50 it looks like they changed to using RJ12 connectors. That little 12-43346-01 adapter might just be a straight through RJ12 to MMJ coupler, or maybe it is an MMJ to MMJ coupler and the short 17-03511-04 that plugs into the HSZ50 is a straight through RJ12 to MMJ cable. In either case, a standard BC16E MMJ cable would plug into the terminal or host side of the 12-43346-01 coupler.
Click to expand...
There was some sort of engineering reason for requiring the adapter, but I can't remember what it was... I just remember that it was annoying.

Regarding FW V5.2: Looking at the Release Notes you posted, it's about a year after I was no longer doing HSOF FW stuff. Starting in 1997 I was doing end-user SW in support of the HSG80. I was the lead SW dude on an app called "Enterprise Volume Manager", which helped automate and manage Snapshot and Clone functionality.

Regarding the cache battery: It feels pretty likely that you could run with CACHE_UPS enabled with this FW, and avoid needing a battery. Any battery that you buy has a good chance of being Bad after all this time, unless somebody is refurbing them by replacing the cells. I suppose there's a market for that.

Pete
 
As far as upgrading the controller firmware in place, this manual says you can use the CLCP (Code Load/Code Patch) utility on a running controller and use the Kermit protocol through the console interface to download the firmware image, which could take a half-hour or longer for the download.

I assume you would need a working firmware image on a PCMCIA flash card to boot the controller far enough to be able to run the CLCP utility, along with having the update firmware image file to download.

DIGITAL StorageWorks
HSZ50 Array Controller HSOF Version 5.1
Service Manual
Part Number: EK-HSZ50-SV.C01
manx-docs.org/collections/mds-199909/cd3/storage/hsz50svc.pdf
 
gslick said:
As far as upgrading the controller firmware in place, this manual says you can use the CLCP (Code Load/Code Patch) utility on a running controller and use the Kermit protocol through the console interface to download the firmware image, which could take a half-hour or longer for the download.
I assume you would need a working firmware image on a PCMCIA flash card to boot the controller far enough to be able to run the CLCP utility, along with having the update firmware image file to download.
Click to expand...
Yes - CLCP! The memory cells are still there.
I'm thinking there was also a way to do it in-band over SCSI (rather than via Kermit), but I could be confusing it with a later product...? Our test team wouldn't have been able to deal with the slow Kermit process, I would think, and I don't remember any large-scale card-burning activity.

Anyway, if any of you folks need a more precise answer to the codeload question, I can ask some folks that are still here in town who will know exactly.

Pete
 
You must log in or register to reply here.
Back
Top