Release Notes
HSJ30/40 Array Controller Operating Software
HSOF Version 3.7
This document summarizes features and characteristics of the HSJ30 and HSJ40 Array Controllers using operating software
Versions 3.7, 3.6, 3.4, 3.3, 3.2, and 3.1 that are not covered elsewhere in the documentation. These release notes also
contain instructions for installing the software and should be retained for future reference
EK-HSFAM-RN. U01
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
Notice
2000 Compaq Computer Corporation.
COMPAQ, the Compaq logo, and StorageWorks Registered in U. S. Patent and Trademark Office. OpenVMS is a trademark
and/or service mark of Compaq Information Technologies Group, L.P.
Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States
and/or other countries.
UNIX is a registered trademark of The Open Group.
All other product names mentioned herein may be trademarks or registered trademarks of their respective companies.
Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial
Items are licensed to the U.S. Government under vendor's standard commercial license.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is
subject to change without notice.
The information in this publication is subject to change without notice and is provided "AS IS" WITHOUT WARRANTY OF
ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS INFORMATION REMAINS WITH RECIPIENT.
IN NO EVENT SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL,
PUNITIVE OR OTHER DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF
BUSINESS PROFITS, BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION), EVEN IF COMPAQ HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL APPLY REGARDLESS OF
THE NEGLIGENCE OR OTHER FAULT OF EITHER PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY
SOUNDS IN CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGAL LIABILITY, AND
NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.
The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products.
Nothing herein should be construed as constituting a further or additional warranty.
Printed in the U.S.A.
Release Notes HSJ30/40 Array Controller Operating Software HSOF Version 3.7
Eighteenth Edition (May 2000)
EK-HSFAM-RN. U01
Page 2 EK-HSFAM-RN. U01
Release Notes
Visit our Web Site for the Latest Information
Visit out our web site for the latest technical tips and documentation. We can be found in the technical area of our
web page:
http://www.compaq.com/storage/
Release Notes Contents
These release notes cover the following topics:
1.0 Identifying Your HSOF Revision Level
2. 0 Hardware and Software Support
3.0 New Items
4. 0 Features From Previous Releases
5. 0 Clarifications
6.0 Operating Constraints
7.0 Avoiding Problem Situations
8.0 Documentation Additions and Corrections
9.0 Software Installation
10.0 Part Numbers
Order Numbers
11.0
Replacing or Adding an HSJ Controller or Cache Module
12.0
The HSUTIL Utility
13.0
Release Package Contents
The Version 3.7 release package consists of the following:
A cover letter
A PCMCIA program card containing HSOF Version 3.7 software
The HS Family of Array Controllers documentation set
- HS Family of Array Controllers User's Guide
- HS Family of Array Controllers Service Manual
- HS Family of Array Controllers CLI Reference Manual
- HSJ30/40 Array Controller Operating Software Version 3.7 Release Notes
- HSJ30/40 Array Controller Operating Software (HSOF), Version 3.7 Software Product Description
License keys to enable optional features: write-back cache, disk mirroring, and RAID (each to be purchased
separately)
Intended Audience
These release notes provide information for the HSJ30 and HSJ40 Array Controllers running HSOF Software Ver-
sion 3.7. Individuals responsible for configuring, installing, and using the HSJ30 or HSJ40 controller should use
this document.
Read this entire document before upgrading the controller's software. The information in these release notes takes
precedence over the information in the HS Family of Array Controllers User's Guide.
EK-HSFAM-RN. U01 Page 3
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
1.0 Identifying Your HSOF Revision Level
The release package you received includes a PCMCIA program card containing the new HSOF software.
You can identify your software revision level by entering the SHOW this_controller command at the Command
Line Interpreter (CLI) prompt. The resulting display lists the software revision level that is currently installed.
When you have completed the installation process for the new version HSOF software, you should see the fol-
lowing displayed: Version V37Z-x (where x represents the number of patches associated with this version of
software that are correctly installed).
2.0 Hardware and Software Support
Sections 2.1 through 2.5 list the hardware and software compatible with HSOF Software Version 3.7:
Hardware Support
Operating System Support
Host Adapter Support
PKQdriver Version
Device Support
2 .1 Hardware Support
HSOF Software Version 3.7 supports the following revisions or higher for the RAID Array HSJ30 and HSJ40
Controllers and associated hardware:
HSJ30-Ax and HSJ30-Cx controller modules
HSJ40-Ax and HSJ40-Cx controller modules
Cache module Version 1, hardware revision A and Version 2, hardware revision A or B
BA350-MA controller shelf
BA350-Sx 8-bit SCSI device shelf
BA356-Sx wide device shelf with 8-bit or 16-bit personality module (controller operates in 8-bit mode only)
BA35x-HF power supply
2 .2 Operating System Support
HSOF Version 3.7 software on HSJ30 and HSJ40 controllers is supported by the following operating system ver-
sions:
OpenVMSTM Alpha:
V6.2-1H3, V7.1-1H1, V7.1-1H 2, V7.1-1H 3, V7.1-2, V7.2, and V7.2-1
OpenVMS VAX:
V6.2, V7.1, and V7.2
Page 4 EK-HSFAM-RN. U01
Release Notes
NOTE
With the release of HSOF Version 3.7, the StorageWorks
Command Console V2.3 Agent is used. An update of the
PKQdriver is required for use with this Agent. Please view the
following Section, 2.4 "PKQdriver Version" for PKQdriver
update information.
2 .3 Host Adapter Support
The following adapters have been tested and are supported in this release.
CIXCD-AB
CIXCD-AC (both for XMI-based systems)
CIBCA-Bx (for BI-based systems)-VAX
CIPCA (for PCI-based systems)-Alpha
2.4 PKQdriver Version
All OpenVMS systems, using the StorageWorks Command Console V2.3 Agent and HSOF V3.7 Software, need
to update their PKQdriver. Sections 2.4.1 through 2.4.3 describe the following:
Link Date and Image Identification Information
Identifying Your PKQdriver
Installing the Current PKQdriver
CAUTION
If you do not use the proper PKQdriver when using SWCC
V2.3 Agents with HSOF Software V3.7, your system may ex-
perience an operating system crash.
2.4.1 Link Date and Image Identification Information
Table 2-1 provides Link Dates and Image Identification information for each OpenVMS version. Please refer to
this table when identifying your current PKQdriver.
Table 2-1 PKQdriver Identification Information
OpenVMS Version Link Date Image Identification
Number
V6.2-1H* 16-Nov-1999 4U4A3A3A3A8
V7.1-1H* 11-Nov-1999 6A13A13A6A11
V7.1-2 11-Nov-1999 6A13A13A6A11
V7.2 (Alpha) 11-Nov-1999 6A52
V7.2-1 10-Jan-2000 6A52
EK-HSFAM-RN. U01 Page 5
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
To identify your PKQdriver, observe both the Link Date and the Image Identification information. If your driver,
with one of the above Image Identification numbers, does not have the corresponding Link Date or later, you will
need to upgrade your driver.
2.4.2 Identifying Your PKQdriver
The most important factor in identifying your current PKQdriver is the Image Identification number you will see
and then its corresponding Link Date. Please use the Table 2-1 to view the Image Identification number for each
OpenVMS version and its corresponding Link Date.
To identify your PKQdriver and obtain the Image Identification and Link Date information, issue the follow-
1.
ing command:
$ ANALYZE/IMAGE/INTERACTIVE SYS$LOADABLE_IMAGES:SYS$PKQDRIVER.EXE.
You will receive the first data screen.
2. Press enter three times until you come to the fourth data screen.
The fourth data screen contains the Image Identification and Link Date information.
Below is an example of the fourth data screen showing the Image Identification and Link Date infor-
mation.
Press RETURN to continue, or enter a period (.) for next file:
Image Identification Information
image name: "SYS$PKQDRIVER"
image file identification: "X-6A52"
image file build identification: "X6TE-0050130101"
link date/time: 10-Jan-2000 17:50:12.67
linker identification: "A11-39"
Press RETURN to continue, or enter a period (.) for next file:
In this example:
The Image Identification number is 6A52
The Link Date is 10-Jan-2000
If the above screen did not show the 10-Jan-2000 Link Date or later for the Image Identification num-
ber 6A52 for an OpenVMS V7.2-1 system, then this driver would need to be updated.
2.4.3 Installing the Current PKQdriver
If your driver does not have the Image Identification number and corresponding Link Date or later that were pro-
vided in the Table 2-1 then your driver will need to be updated.
If additional support with PKQdriver installation is needed, please contact your Customer Service Representative.
Page 6 EK-HSFAM-RN. U01
Release Notes
2 .5 Device Support
HSOF Software V3.7 supports the devices described in Tables 2-2 through 2-5:
Supported Disk Drives
Supported Tape Drives
Supported Solid State Devices
Supported CD-ROM Readers
Table 2-2 Supported Disk Drives
Minimum Minimum
Capacity in Microcode Hardware
Device Gigabytes Version Version
RZ25-VA 0.43 0900 B01
RZ26-VA 1.05 T392 D02
1
RZ26L-VA/VW 1.05 440C A01
1
RZ26N-VA/VW 1.05 446 A01
1
SWXD3-SF/WF 1.05 446 A01
1
DS-RZ26N-VZ 1.05 1003 A01
DS-RZ1BB-VW 2.10 LYJO/0656 A01
1
RZ28-VA/VW 2.10 435E B03
RZ28B-VA 2.10 0003 A01
1
RZ28D-VA/VW 2.10 0008 A01
1
SWXD3-SG/WG 2.10 0008 A01
1
RZ28M-VA/VW 2.10 0466 A01
1
DS-RZ28M-VZ 2.10 1003 A01
1
SWXD3-SH/WH 2.10 0466 A01
RZ74-VA 3.57 T427B B07
DS-RZ1CB-VW 4.1 LYJO/0656 A01
1
RZ29B-VA/VW 4.3 0007 B01
1
SWXD3-SE/WE 4.3 0007 C02/A01
DS-RZ1CF-VA/VW 4.3 0370/ 0371 A01
DS-RZ1DB-VW 9.1 LYJO/0307 A01
DS-RZ1DF-VA/VW 9.1 0372/ 1614 A01
DS-RZ40-VA 9.1 LYGO A01
DS-RZ1DD-VA/VW 9.1 0305/3B07 A01
DS-RZ1EF-VA/VW 18.2 0372/N1H1 A01
DS-RZ1ED-VW 18.2 0306/0305/3B07 A01
DS-RZ1EA-VW 18.2 3B05/ B016 A01
DS-RZ1DA-VW 9.1 3B06/ B016 A01
DS-RZ1FC-VW 36.4 3B07 A01
EK-HSFAM-RN. U01 Page 7
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
Table 2-2 Notes:
1. Wide disk drives require a SWXSS-06 shelf.
All drive "VW" models require DS-SWXSS-06 wide device shelves.
NOTE
Any accidental use of the ADD TAPE command will result in con-
ditions requiring reinitialization of the controller.
Table 2-3 Supported Tape Drives
Device Capacity Minimum Minimum Notes
Microcode Hardware
G= Gigabytes
Version Version
T=Terabytes
TL812 960/ 1920G 1.2 robot /CC33 drive A01 1,2,3,4,5
TL822 5280/10560G 1g4F robot /CC33 drive A01 1,2,3,4,5
TL826 3520/7040G 1g4F robot /CC33 drive A01 1,2,3,4,5
DS-TL893 924/ 1848T V2A/5A A01 1,2,3,4,5
DS-TL894 1.68/3.36T V1.24 A01 1,2,3,4,5
DS-TL895 3.1/6.2T 230 A01 1,2,3,4,5
DS-TL896 6.16/12.32T V2A/5A A01 1,2,3,4,5
TZ87-VA 10/ 20G 930A A01 3,5,6
TZ87N-VA 10/ 20G 930A A01 3,4,5,6
TZ87-TA 10/ 20G 9514 B02 1,2,3,6
DS-TZ820 25/ 50G 01aj A01 1,2,3,6
TZ875-NT 50/ 100G 930A A01 1,3,5,6
TZ875-TA 50/ 100G 930A A01 1,3,5,6
TZ877-AE/AF 70/ 140G 930A A01 1,3,5,6
TZ88N-VA 20/ 40G CC33 A01 3,4,5,6
TZ885-NT/NE 100/ 200G CC33 A01 1,3,4,5,6
TZ887- NT/NE 140/ 280G CC33 A01 1,3,4,5,6
DS-TZ89N-VW 35/ 70G V80 A01 3,4,5,7
DS-TZ89N-TA 35/ 70G 141F A01 1,3,4,5,6
DS-TL890 560/ 1120G 3.23 robot/V55 drive A01 1,2,3,4,5
DS-TL891 350/ 700G 3.23 robot/V55 drive A02 1,2,3,4,5
DS-TL892 350/ 700G 3.23 robot/V55 drive A02 1,2,3,4,5
DS-AIT35-VW 35/ 70G 4.03 A01 5,6,7
Page 8 EK-HSFAM-RN. U01
Release Notes
Table 2-3 Notes:
1. Requires 0.2 meter SCSI-1 to SCSI-2 transition cable, Compaq internal part number 17-03831-01 for
DWZZA-AA, and Compaq part number 17-04367-01 for SSB DWZZA-VA and DWZZB-VW.
2. Requires SWXA2 single-ended to differential SCSI signal converter.
3. Capacity values represent compressed data. The compression factor is device dependent based on individ-
ual device algorithms.
4. Cannot read TK50, TK70 or TZ30 formatted tapes.
5. Requires a KZPSA or PMAZC host adapter.
6. Tape device code load is supported.
7. Wide tape devices require a SWXSS-06 shelf with an 8-bit I/O
m odul e.
Table 2-4 Supported Solid State Devices
Device Capacity in Giga- Minimum Minimum Notes
bytes Microcode Ver- Hardware
sion Version
EZ31-VW 0.134 V064 A01 2, 3
EZ32-VW 0.268 V064 A01 2, 3
EZ51R-VA 0.10 V096 D01 2, 3
EZ54R-VA 0.42 V109 C02 2, 3
EZ58R-VA 0.85 V110 D01 1, 2, 3
EZ64-VA 0.475 V064 A01 2, 3
EZ64-VW 0.475 V070 A01 2, 3
EZ69-VA 0.950 V064 A01 2, 3
EZ69-VW 0.950 V070 A01 2, 3
EZ454 .536 Y018 A01 2, 3
EZ832 3.2 Y018 A01 2, 3
EZ41 0.134 V012 A01 2, 3
EZ42 0.268 V012 A01 2, 3
EZ51 .107 V109 C02 2, 3
EZ54 .428 V109 C02 2, 3
EZ705 0.536 V012 A01 2, 3
EZ711 1.1 V012 A01 2, 3
EZ716 1.6 V012 A01 2, 3
Table 2-4 Notes:
1. Code load is not supported for these drives
2. Formatting supported for these drives
Do not warm-swap solid-state disk drives. Make sure power to the device shelf is turned off before removing or
inserting this device.
EK-HSFAM-RN. U01 Page 9
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
Table 2-5 Supported CD-ROM Readers
Device Capacity in Giga- Minimum Minimum Hardware
bytes Version
Microcode Version
RRD42-VB/VU 0.6 1.1a A01
RRD43-VA 0.6 0064 A02
RRD44-VA 0.6 3493 A02
RRD45-VA/VU 0.6 1645 A01
RRD46-VA 0.6 1337 A01
RRD47-VA 0.6 1206 A01
Table 2-5 Notes:
Do not warm-swap CD-ROM drives. Make sure power to the device shelf is turned off before removing or in-
serting this device.
3.0 New Items
Sections 3.1 and 3.2 briefly describe the new items in HSOF Software V3.7.
New Devices Supported in HSOF Software
Issue Resolutions
3.1 New Devices Supported in HSOF V3.7 Software
3.1.1 Disk devices
DS-RZ1EA-VW with 18GB
DS-RZ1DA-VW with 9GB
DS-RZ1DD-VW with 9GB
DS-RZ1FC-VW with 36GB
3.1.2 Tape Devices
DS-AIT35-VW with 35/70GB
NOTE
Although some of the above listed Devices may have been supported
in previous releases, all of these Devices have been classified as "new"
for the HSOF V3.7 Software Release. Please see Section 2.5 for addi-
tional information on Device Support.
Page 10 EK-HSFAM-RN. U01
Release Notes
3.2 Issue Resolutions
This section addresses issues that occurred in a previous release of the HSOF software and have been resolved in
the HSOF V3.7 release. The issues addressed by HSOF V3.7 Software are as follows:
A rare occurrence of controller reset when running backup with compare during the reading and writing of
EBCDIC formatted tapes on the TSZ07 tape device.
An occasional problem with failover on a dual-redundant controller pair during certain unusual cache battery
states.
An occasional issue of a disk entering a mount verification timeout state when changing the preferred path on
a stripeset.
A rare occurrence of a drive error causing an "online with lost data" message and a spareset lockup or I/O
failure when a drive was being added to the storageset.
A rare occurrence of a medium offline error generated for the OpenVMS loader when a mount command was
issued immediately after a dismount or when a tape was mounted in a magazine loader that was set to the
automatic mode and the backup spanned from one tape volume to the next.
A rare occurrence of a TKZ61 tape device becoming misconfigured.
A rare occurrence in which RAIDsets were not properly failing over in the event of battery failure.
In a rare occurrence the HSJ30 and HSJ40 controllers may not be able to use the HSUTIL program to perform
a "code load" firmware upgrade to TZ87/88/89 tape drives or any associated Automated Tape Library. In
such a case the HSUTIL program refuses to perform the upgrade because it incorrectly determines that there
is a tape present in the target tape drive when there is none. Please see Section 7.1 HSUTIL Program Failure
During a Code Load Firmware Upgrade for a description of this issue and directions for resolution.
A rare occurrence of a drive reporting "Not Ready/Becoming Ready" where the drive was unable to recover,
triggering a controller reset.
A rare occurrence of a TZ89 tape device error causing a controller reset with a last failure code of 103360188
4.0 Features from Previous Releases
Sections 4.1 through 4.5 briefly describe changes that were introduced in the code version previous to HSOF V3.7
Software release that are not covered in other documentation.
Correction for TILX Incompatibility with Disks
NOR/DDL Errors
Action for repeated Reboots Problem Resolution
Support for Large Drive Formatting
Support for up to Fourteen 18GB Drives
4.1 Correction for TILX Incompatibility with Disks
In previous versions of HSOF software, data integrity problems could infrequently occur if the tape in-line exer-
ciser (TILX) was run on tapes attached to a controller on which disks were also configured. This problem is cor-
rected in HSOF Version 3.4.
EK-HSFAM-RN. U01 Page 11
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
4 .2 NOR/DDL Errors
A small number of NOR/DDL (No Response/Dual Data Link) errors may occur during cluster transitions and
other normal cluster events. However, some customers have experienced a NOR/DDL error rate higher than ex-
pected. Under certain rare conditions on the CI bus, the HSJ controller CI interface ASIC may become unable to
recognize the host's acknowledgment that a packet from the controller has been received. When this condition
persists on both paths, the controller closes the virtual circuit with an error log of NOR/DDL. This version of
HSOF software corrects this specific problem.
4 .3 Action for Repeated Reboots
Very rarely, a hardware failure might cause a controller to reboot repeatedly, preventing preferred disk devices
from completing failover to the dual-redundant partner. HSOF Version 3.4 contains a modification so that if the
same bugcheck repeats itself three times in a ten minute period, the controller will shutdown with no restart to
permit the disk devices to failover to the working controller in a dual-redundant pair.
4 .4 Support for Large-Drive Formatting
This release supports formatting of larger disk devices (9 GB and 18 GB).
4 .5 Support for up to Fourteen 18 GB Drives
The maximum storageset size was increased to 256 GB so that the controller can support up to fourteen 18 GB
drives.
5.0 Clarifications
Sections 5.1 through 5.16 contain clarification on the following subjects:
EMU Alarm Clarification
Write-Back Cache Batteries and Battery Handling
Logical Device Event Reports
SHOW on Both Controllers
Logical Block Address Does Not Match for MEDIUM ERROR
Adding RAIDsets When Battery Condition is Low
Drive-Level Event Reports
Saving the Subsystem Configuration
RRD42 CD-ROM Reader
CLI Type Ahead, Recall, and Editing
DILX Enhancement
Support for Larger Storagesets
Faster Storageset Initialization
Multiple Disk Drive Formatting
Ability to Install New Microcode on a Tape Drive and Solid State Disk Drives
Last Failure Code 010E0110 Normal Occurrence After Upgrade
Page 12 EK-HSFAM-RN. U01
Release Notes
5.1 EMU Alarm Clarification
The environmental monitoring unit (EMU) alarm sounds for individual device failures, but does not sound for
storageset failures.
5.2 Write-Back Cache Batteries and Battery Handling
Diagnostic testing is performed on the write-back cache batteries when the controller first initializes and then
periodically after the batteries have become fully charged. The following paragraphs clarify battery-related topics.
5.2.1 CACHE_UPS Switch Use
If the SET controller CACHE_UPS switch is activated, the only action taken in the event of battery failure is to
send an error message.
The CACHE_UPS is not intended to replace batteries. The switch is intended to control the impact that the current
battery state has on cache policy. Battery state is still reported and if the power fails and UPS is broken or ex-
hausted the batteries will still maintain cache contents.
When the CACHE_UPS switch is enabled, an uninterruptible power supply (UPS) is assumed to be in use to
maintain power to the write-back cache module in the event of a power failure. Note that the HSOF software does
not have the capability to monitor the remaining capacity of an external UPS. There are many variables in an UPS
configuration; some configurations might put data at risk if the UPS is exhausted. If UPS power is lost to the
host/storage system without warning, write-back cache data is maintained by the cache batteries only. With
CACHE_UPS set, if UPS power is last and if the cache batteries have failed, data could be at risk.
CAUTION
Use of this setting without a functional UPS in place could result in
data loss if power is interrupted and batteries have failed.
5.2.2 Cache Policy
The setting chosen for SET controller CACHE_POLICY (to either A or B) affects access to RAIDsets and Mirror-
sets during the initial test only and determines the cache mode the controller uses during initial test only.
Initial Test begins when the controller is turned on and continues until the batteries are charged, or up to ten
hours. Initial testing includes a recharge of the battery after potential discharge during shut down. The battery is
tested by the software every four minutes. Full caching operations begin when the batteries are fully charged.
Cache Policy A is the default setting. Cache Policy A and B apply only to a "low" battery situation during con-
troller initialization until either the:
Battery becomes fully charged or
10 hours elapse without the battery becoming fully charged.
In the latter case, failed battery action is taken as described in the "Failed Battery Action" section of these Release
Notes.
Once a battery has become fully charged, Cache Policy A and B no longer apply, and regular periodic battery tests
are performed.
EK-HSFAM-RN. U01 Page 13
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
Table 5-1 summarizes the effect of both cache policy settings on access to RAIDsets and mirrorsets when a bat-
tery is "low" during the initial test period.
Table 5-1 Cache Policy Settings
Cache Policy RAID/Mirrorset Access Cache Mode
Cache Policy A No access Write-through on individual disk
units (also called JBOD)
Cache Policy B Access Write-through on RAID/mirrorsets
and individual disk units
NOTE
Write-through cache mode is not a 100% guarantee of user data consis-
tency within storagesets (RAID and mirrorsets). This is because of an
inherent delay in the writing of data to the different members of these
storagesets. If a power failure occurs between the writing of some mem-
bers and others (an extremely narrow window), data on the various mem-
bers will be inconsistent.
Therefore, Cache Policy A (which denies access to RAID/mirrorsets on
controllers with low batteries) is the only 100% guarantee of user data
consistency. That is why Cache Policy A enforces loss of storageset ac-
cess when a battery does not pass the battery test.
HSOF software makes every attempt to notify the user that a battery
problem ("not good" or "open circuit") has occurred by printing a mes-
sage to the console and posting an error to the host errorlog. However, not
all operating systems present errorlogs reliably.
5.2.3 Failed Battery Action
If a battery passes the initial test, cache policy no longer applies, and periodic testing begins. During periodic
testing, the battery is tested every 24 hours. The following failed battery action is taken when a failed battery is
detected during either initial or periodic testing:
Dual-controller HSJ30/40s (dual batteries on each cache module and the partner controller is running and has
good batteries)
- Controller performs controlled shut down
- All units failover to partner
- No auto-reboot after shut down
- Manual restart before battery replacement causes units to "failback" leading to no access to RAIDsets
and mirrorsets
Single-controller HSJ30/40s
- No shut down
- No RAIDset or mirrorset access permitted
- Individual disk units accessed in write-through mode
Page 14 EK-HSFAM-RN. U01
Release Notes
5.2.4 Extending the Life of the External Cache Batteries
Occasionally, circumstances will require you to shut down your controller and restart it. If the correct steps for
turning off power to an HSJ30/40 array controller configuration with write-back cache are not followed, there is
potential for loss of data that may exist on any devices connected with them. In addition, if you are turning off the
power to the controller subsystem for any reason for longer than one day (such as a holiday, system move, or re-
placing a bad SCSI host cable), you will need to turn off the external cache batteries (ECBs) to prevent them from
discharging. To avoid problems when the controller restarts, always use the following process to shut it down:
CAUTION
Allowing the write-back cache batteries to discharge completely,
and leaving them in a discharged state for any length of time,
could result in permanent and irreversible degradation to the bat-
teries.
5.2.4.1 Shutting Down a Controller
1. Use the proper procedures for shutting down the operating system if the host system is also going to be turned
off.
2. If the host is not going to be turned off, it is not necessary to shut down the host system, but use the proper
operating system procedures to dismount any units that are accessed through the HSJ30/40 array controllers.
3. If the controller configuration contains any devices or storagesets that are write-back cache enabled, and the
system is going to be turned off for an extended length of time, the batteries on the write-back cache modules
drain, causing the data in the cache modules to be lost. If you have RAIDset or mirrorset units, or single de-
vices with write-back caching turned on, set norun on all units.
4. When the dismount and/or the operating system shutdown procedures are complete, invoke the controller
shutdown commands on the controllers.
CAUTION
Do not turn off the power to the controller subsystem until all
shutdown procedures have successfully completed.
5. If you have a dual-redundant controller configuration, shut down each controller one at a time using the fol-
lowing commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER
If you have a non-redundant controller configuration, only the shutdown this_controller command is
necessary.
The green reset LED stops blinking when the SHUTDOWN command completes.
6. When the controller SHUTDOWN command successfully completes, turn off power to the controller subsystem
(or just the controller shelf, if you are not shutting down the entire system), by unplugging the power supplies
in the controller shelf.
EK-HSFAM-RN. U01 Page 15
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
5.2.5 Disabling the Write-Back Cache Batteries
Refer to Chapter 2 in HSFAM of Array Controllers Service Manual, for instructions on removing and replacing
the controller module and write-back cache module.
1. Stop all host activity and dismount all device units from the host system. Device service is interrupted for the
duration of the service cycle. You can shut down the host operating system to accomplish this.
2. Connect a maintenance terminal to the controller's maintenance terminal port on the front bezel.
3. Take the controller out of service by issuing the one of the following two CLI command steps.
Single Controller:
SHUTDOWN THIS_CONTROLLER
Dual Controllers:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER
When the shut down completes, the controller or controllers' green reset LED on the operator control
panel (OCP) stops blinking.
4. Power off the entire storage subsystem.
5. Press the battery disable switch, the small button labeled SHUT OFF next to the flashing status LED on the
ECB, and hold it in for approximately two seconds (refer to Figure 5-1). The cache LED will flash once, then
shut off.
NOTE
The battery is no longer powering the cache.
6. To return to normal operation, the cache battery is enabled when the RAID subsystem is powered on.
7. Restart the Controller
PCMCIA Card Removed: Hold down the reset button while inserting the PCMCIA Card. When
you release the reset button, the controller restarts.
PCMCIA Card Not Removed: Press the reset button and the controller restarts.
Page 16 EK-HSFAM-RN. U01
Release Notes
Figure 5-1. External Cache Battery Disable Switch
ECB 1
ECB 2
Power
connector
Status Battery
LED disable
switch
CXO6164A
5.2.5.1 Restarting the Controller
1. Before you restore power to the subsystem, remove the controller module and the write-back cache module.
Remove the battery disable jumper and replace it so it is only covering one pin, then reassemble the unit.
2. If you removed the PCMCIA card, hold down the reset button while inserting the PCMCIA card. When you
release the reset button, the controller restarts.
3. If you did not remove the PCMCIA card, press the reset button and the controller restarts.
5 .3 Logical Device Event Reports
Under certain circumstances the Port, Target, and LUN fields contained in event reports associated with storageset
logical devices, Event Log displays as well as sense data responses, will be set to 255 (decimal) instead of the
Port, Target, and LUN of the first physical device in the storageset. In addition, when the Port, Target, LUN are
set to 255, the Device Type is set to 0 (magnetic disk device), and the Device Product ID and Device Firmware
Revision Level fields will be ASCII space filled.
5.4 SHOW on Both Controllers
Some devices, such as tape devices, may not show correctly on one controller if they are preferred to the other
c ont rol l e r.
If the expected information is not displayed from one controller, use the SHOW command again to view the in-
formation on the other controller.
5.5 Logical Block Address Does Not Match for MEDIUM ERROR
The Logical Block Address (LBA) is a number used to identify a block on a mass storage device. The LBA that
appears in the Information field of an Event Log (%EVL) displays when the Sense Key field is MEDIUM ERROR
does not agree with the LBA number contained in the Information field of the extended sense data that is sent to
the host system. It is one less than the number in the extended sense data.
EK-HSFAM-RN. U01 Page 17
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
5 .6 Adding RAIDsets When Battery Condition is Low
You can use the add raidset and add mirrorset commands, regardless of the write-back cache battery condition.
However, if the cache_policy is set to A and the batteries are low, the controller does not allow access to any
RAIDsets or mirrorsets. Cache_policy A requires that the cache batteries be fully charged before you can use
RAIDsets or mirrorsets.
5.7 Drive-Level Event Reports
Under certain circumstances the "devtype" (device type) field contained in drive-level event reports %EVL dis-
plays as well as error logs, will contain the value 1F(hexadecimal). When "devtype" is 1F the content of the "de-
vice identification" and "device serial number" fields are undefined and should be ignored.
This is a permanent restriction.
5.8 Saving the Subsystem Configuration
The save_configuration switch is intended to be used to provide a means to restore nonvolatile (NVRAM) con-
tents when a controller in a single-controller module configuration is replaced. The save_configuration switch
cannot cross hardware revisions or software versions. save_configuration is not available for upgrades of firmware
or hardware, and does not perform inter-platform conversions. For example, do not use save_configuration to up-
grade from HSOF Version 3.2, or from an HSJ30/40 to an HSJ50 array controller.
The controller stores the subsystem's configuration-the storagesets you configured, the switches set for each, the
HSOF patches you've installed, and so on-in its nonvolatile memory. This means that, if the controller fails in a
nonredundant configuration, you would have to reconfigure the subsystem from scratch. (In a dual-redundant con-
figuration, this information is stored by both controllers, which effectively eliminates the risk of losing it.)
NOTE
Compaq recommends that the SAVE_CONFIGURATION switch only
be used for nonredundant controller configurations. To save the
configuration information for dual-redundant configurations use
the SET FAILOVER COPY= command.
If you are operating a nonredundant configuration subsystem, Compaq recommends saving the subsystem's con-
figuration on at least one of the devices or storagesets with the following command:
INITIALIZE STORAGESET_NAME SAVE_CONFIGURATION
When initializing a device or storageset with the save_configuration switch, the controller copies the subsystem's
configuration to the disk drives. If you use the switch for a multi-device storageset, such as a stripeset, the com-
plete information is stored on each device in the storageset. The capacity of a device that is initialized with the
save_configuration switch is reduced by 256KB. This capacity reduction applies to each member of a storageset.
After initializing a storageset with this switch, the controller keeps the copy up-to-date. For example, every time a
new patch or storageset is added to the HSOF software, the controller re-copies the new configuration to all stor-
agesets that were initialized with the save_configuration switch.
Page 18 EK-HSFAM-RN. U01
Release Notes
If a controller in a nonredundant-configuration fails, its replacement automatically searches the devices in the sub-
system for a saved configuration. If it finds a saved configuration, it transparently loads it into nonvolatile mem-
ory and brings the subsystem online. It is unnecessary to issue an initialize command again after reconfiguring the
devices with a new controller.
Compaq does not recommend initializing all of your storagesets with the save_configuration switch. Every time
you change the subsystem's configuration, the controller writes the new configuration to the storagesets that you
initialized with this switch. Too many write operations can adversely affect performance.
If you are upgrading from HSOF Version 3.2 to Version 3.4 in a single-controller configuration, you can refresh
the SAVE_CONFIGURATION data on your storagesets to include the new software revision by issuing the following
command:
SET UNIT XXX WRITE_PROTECT
[where xxx is any existing unit on the controller]
SET UNIT XXX NOWRITE_PROTECT
These commands, which have no net effect, serve to change the contents on nonvolatile memory, causing the up-
dated SAVE_CONFIGURATION information to be automatically written to the SAVE_CONFIGURATION area of all units
that have been initialized with this option.
5.9 RRD42 CD-ROM Reader
Mounting an RRD42 might put a message in the OpenVMS error log. In earlier versions of OpenVMS, the first
four digits in Longword 19 of the controller dependent information is 02D1. New versions of OpenVMS report
ASC: 209.(D1) ASCQ: 2.(02). The message indicates "Unexpected bus phase," and can be ignored safely.
5.10 CLI Type Ahead, Recall, and Editing
With HSOF Version 3.1 or higher, you no longer need to wait for the current command to complete before enter-
ing the next command. You can recall any of the last four commands entered, and then edit that command to save
time when entering new commands.
Refer to HS Family of Array Controllers User's Guide for more information on entering CLI commands.
5.11 DILX Enhancement
The HSJ30 and HSJ40 controllers with HSOF Version 3.1 software have a new version Disk In-Line Exerciser
(DILX) that acts on disks configured as single-device, RAIDset, stripeset, mirroret, or striped-mirrorset units. In
addition, you can choose to perform either an auto half test or an auto full test.
5.12 Support for Larger Storagesets
HSOF Version 3.1 or higher allows you to use storagesets with capacities of up to 120GB. You can configure
drives of any size into storagesets, such as RAIDsets or stripesets. The maximum size of a storageset is 120GB,
regardless of the size of the member drives.
EK-HSFAM-RN. U01 Page 19
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
5.13 Faster Storageset Initialization
The initialize command has been optimized in Version 3.1, and runs significantly faster than on previous versions
of HSOF software. It takes less than 30 seconds to initialize a large RAIDset.
5.14 Multiple Disk Drive Formatting
You can perform a low-level format on up to seven disk drives at once with HSOF Version 3.1 software. See the
"Formatting a disk using HSUTIL" section 13.1.2, -in these release notes for instructions on how to format disk
drives.
5.15 Ability to Install New Microcode on a Tape Drive and Solid State Disk Drives
HSOF Version 3.1 software allows you to use the controller's HSUTIL program to install new microcode to the
TZ89 tape drive.
HSOF Version 3.1 software also allows you to use the controller's HSUTIL program to install new microcode to
solid state disk devices.
5.16 Last Failure Code 010E0110 Normal Occurrence After Upgrade
When updating firmware on the controllers, the following message may appear suggesting that there is a problem
with the controller or that there was an issue during the update process. The below message is normal and is not
cause for alarm.
Last fail code: 010E0110
Press " ?" at any time for help.
%CER-HSZ_2> --13-JAN-1946 04:32:20 (time not set)-- System Information Page-and
Last Failure entries reset to default settings. Last Failure Entry: 1. Flags:
00000002 Template: 1.(01) Description: Last Failure Event Power On Time: 1.
Years, 127. Days, 3. Hours, 27. Minutes, 5. Seconds Controller Model: HSJ30 Se-
rial Number: ZG05051997 Hardware Version: 0000(00) Firmware Version: V37Z(00)
Instance Code: 0102030A Description:
An unrecoverable firmware inconsistency was detected or an intentional restart or
shutdown of controller operation was requested.
This is a normal occurrence for the first boot following manufacture of the controller module and during the tran-
sition from one firmware version to another if and only if the format of the System Information Page (SIP) is dif-
ferent between the two versions.
If this event is reported at any other time, follow the recommended repair action associated with this Last Failure
Code.
Page 20 EK-HSFAM-RN. U01
Release Notes
6.0 Operating Constraints
Paragraphs 6.1 through 6.23 describe the operating constraints for HSOF Version 3.7 software. An operating con-
straint is defined by the parameters within which the controller is designed to operate. Constraints of other system
components, such as host adapters, may also be described in this section. Keep these constraints in mind to avoid
problems and to obtain the maximum performance available from your controller:
Updated Storageset Limits
Maintenance Terminal Port Speeds
Restrictions on Moving Storagesets to Previous Software Versions
Initialization Devices
OVERRIDE_ONLINE Switch
Unable to Access Tape Drives After Power Cycle
CFMENU Constraints
Device Adds, Moves, and Changes
Tape Drive Firmware Revision
Running CONFIG or CFMENU Utilities During Backup or Copy Operations
Changing Host Adapter Types
CLONE Utility
Moving Write-Back Cache Modules
Set Tape Density When Adding Drive and Changing Cartridge Types
Moving Drives from HSC Controllers
Set SCSI Speed for Devices
Configuration Saved on Disk
Host Tape Density Selection
Disk Code Load Capability
Disk Formatting Capability
Disk Geometries of Mirrorsets and Clones
New CLEAR_ERRORS INVALID_CACHE Functionality
New Cache Battery Diagnostic
6.1 Updated Storageset Limits
The following limits apply to storagesets configured on single controller or dual-redundant controller configura-
tions:
A mirrorset can have a maximum of 6 members.
A stripeset or RAIDset can have a maximum of 14 members.
There can be a maximum of 20 mirrorsets and/or RAIDsets.
There can be a maximum of 30 storagesets (RAIDsets, mirrorsets, and/or stripesets).
There can be no more than 32 physical device members for a unit.
Each storageset can store a maximum of 256 GB.
EK-HSFAM-RN. U01 Page 21
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
NOTE
When building RAIDsets with drives of capacity 4GB or greater, if
you are using OpenVMS 6.2, the largest RAIDset that can be built
contains 12 members. For OpenVMS V7.0, this limitation does not
exist.
6.2 Maintenance Terminal Port Speeds
HSOF Version 3.4 software supports terminal port connections at 4800, 9600, and 19200 bits per second (bps).
Connection speeds at 300, 1200, and 2400 bps are not supported.
6.3 Restrictions on Moving Storagesets to Previous Software Versions
In HSOF Version 2.5 software, striped mirrorsets reported a different disk geometry than the same nonmirrored
stripeset. This has been resolved in Versions 2.7, 3.1, 3.2, and 3.4, such that striped mirrorsets initialized under
these versions report a disk geometry identical to the same nonmirrored stripeset.
Due to this improvement, be aware of the following when moving stripesets to previous versions of software:
Striped mirrorsets created under HSOF Software Versions 2.7, 3.1, or 3.2 cannot be used on previous ver-
sions; the metadata is incompatible.
Any stripeset that is converted to a striped mirrorset using the mirror command under HSOF Software Ver-
sions 2.7, 3.1 or 3.2 cannot be used on previous versions. You must unmirror each of the members to return
the stripeset to an earlier version.
Any stripeset clone that is created under Versions 2.7, 3.1 or 3.2 (using the Clone utility) cannot be used with
previous software versions.
Containers initialized with the SAVE_CONFIGURATION switch introduced in HSOF Version 2.7 cannot be used
with versions prior to Version 2.7.
Striped mirrorsets created under previous software versions and used with Versions 2.7, 3.1 or 3.2 carry forward
the same geometry they had under the previous version. If possible, back up all data and reinitialize the stripesets
under Versions 2.7, 3.1 or 3.2 to take full advantage of geometry improvements.
6.4 Initialization Devices
Controller-attached devices can serve as initialization devices for VAX 7000 and VAX 10000 systems, provided
the VAX 7000/10000 console code is at Version 4.0 or higher.
6.5 OVERRIDE_ONLINE Switch
Attempting to delete tape-based units using the OVERRIDE_ONLINE switch results in conditions requiring controller
reinitialization. Do not enter the OVERRIDE_ONLINE switch when deleting tape-based units.
6.6 Unable to Access Tape Drives after Power Cycle
You might not be able to access a tape drive after the power for the drive is turned off and back on. Use the
CLEAR_ERRORS UNKNOWN DEVICE-NAME command to place the device in a known state.
Page 22 EK-HSFAM-RN. U01
Release Notes
6 .7 CFMENU Constraints
CFMENU can only delete single sparesets. Delete sparesets one at a time.
6.8 Device Adds, Moves, and Changes
The controller maintains configuration maps of device types and locations and uses those maps for communicat-
ing with devices. If you add, move, or change devices while the controller is powered off and without changing
the controller configuration first, the controller is not able to work with the changed devices when it returns to
service.
6.9 Tape Drive Firmware Revision Upgrade
If you are not using HSUTIL to install your new tape firmware, do the following: Before installing a new version
of tape drive firmware, delete the tape drive completely from the controller configuration. You can re-add the tape
drive after the firmware installation is complete.
6.10 Running CONFIG or CFMENU Utilities During Backup Operations
Do not run the CONFIG or CFMENU utilities during a tape backup operation.
6.11 Changing Host Adapter Types
If you change the host adapter and maintain the same node number, restart your controller(s).
6.12 CLONE Utility
When running the clone utility in a dual-redundant controller configuration, do not issue any CLI commands to
devices that are involved in the clone operation.
6.13 Moving Write-Back Cache Modules
When moving a write-back cache module to a new environment (that is, different controller, different devices), it
is very important that you perform a clean shut down of the controller and clear any data from the cache. Follow
these steps to move a write-back cache module:
Shut down the controller and flush unwritten data from the cache module using the appropriate CLI com-
1.
mand:
SHUTDOWN THIS_CONTROLLER
SHUTDOWN OTHER_CONTROLLER
2. Wait for the shutdown command to complete and verify that the controller does not report any errors.
3. Remove the controller and cache module following the instructions in the HS Family of Array Controllers
User's Guide or the HS Family of Array Controllers Service Manual.
The shutdown command flushes cache data to the devices, and you can install the module in another location
without problems caused by uncleared cache data.
EK-HSFAM-RN. U01 Page 23
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
6 .1 4 Set Tape Density When Adding Drive and Changing Cartridge Types
The default_format switch allows you to specify the tape format for use by the controller for write operations to a
tape drive. Also use this switch to tell the controller to allow the host to set the tape format.
Not all tape devices support all formats. The easiest way to determine what formats are supported by a specific
device is to enter the set tape-unit-number default_format=? command. The controller displays the valid options
for the unit.
NOTE
Host system software must support the density selection for the
affected device for this option to operate correctly. Using the
HOST_SELECTED switch for other devices may yield
unpredictable results.
Compaq recommends the use of the set tape-unit-number default_format=host_selected command with only
TSZ07 tape drives. Set the switch to host_selected to allow the host to set the tape format.
When first adding a tape drive to the controller configuration, set the tape density with the set tape-unit-number
default_format= command before using the OpenVMS initialize command. In dual-redundant controller configu-
rations, set the tape density from both controllers in the pair before the tape drive is mounted. Not setting the tape
density might cause the tape to be written at the wrong density, or the OpenVMS initialize command to fail with
an invalid format error.
6.15 Moving Drives from HSC Controllers
Software Vesrions 3.1 and 3.2 contain an undocumented local program, CHVSN, for viewing and changing vol-
ume serial numbers that you can use to move drives from an HSC controller to an HSJxx controller. Use this pro-
gram when moving drives because the HSC controller accepts volume serial numbers of zero and duplicate serial
numbers, but HSJxx controllers do not.
Run CHVSN for drives in nontransportable mode that originated on an HSC controller. If the volume serial num-
ber is zero or a duplicate of another drive's volume serial number, answer "yes" to the "Update CHVSN" ques-
tion. The controller then generates a new volume serial number:
RUN CHVSN
Device (port target lun) [EXIT] ? 4 1 0
CHVSN: Volume Serial Number is 00000000 00000000 Update
CHVSN (Y/N) [N] ? Y
CHVSN: Volume Serial Number is 00012010 00580010
Device (port target lun) [EXIT] ? Return
CHVSN - Normal Termination
Page 24 EK-HSFAM-RN. U01
Release Notes
If you attempt to run the subsystem with zero or duplicate volume serial numbers present, two symptoms appear:
The Open VMS operating system reports "medium is offline."
$ MOUNT/FOR $3$DUA324 %MOUNT-F-MEDOFL, medium is offline
$
command reports "MEDIA
The controller SHOW UNIT FORMAT ERROR."
SHOW D324
MSCP unit Uses
-------------------------------------------------------
D324 DISK240
Switches:
RUN
NOWRITE_PROTECT
READ_CACHE
NOWRITEBACK_CACHE
MAXIMUM_CACHED_TRANSFER_SIZE = 32
State:
MEDIA FORMAT ERROR
NOPREFERRED_PATH
6.16 Set SCSI Speed for Devices
HSOF Version 3.1 software makes it possible for the initiator and target to negotiate a faster data rate than is sup-
ported by the cable length. HSOF Version 3.1 software has a new CLI command to set a maximum data transfer
rate between the controller and any device. Possible settings are 10MHz, 5MHz, or asynchronous mode.
To set the transfer speed, use the set command as follows:
SET DEVICE-NAME TRANSFER_RATE_REQUESTED=RATE
where rate can be one of the following:
ASYNCHRONOUS
10MHZ
5MHZ
The default is 10MHZ.
Refer to HS Family of Array Controllers User's Guide for more information on setting the data transfer rate ac-
cording to SCSI cable lengths.
EK-HSFAM-RN. U01 Page 25
HSJ30/40 Array Controller Operating Software HSOF Version 3.7
6.17 Configuration Saved on Disk
A new CLI option causes the controllers to save a copy of the controller configuration (nonredundant controllers
only) on one or more disk drives in the subsystem. The saved information is updated whenever the configuration
of the nonredundant controller is changed. Should a nonredundant controller be replaced by another controller
with no configuration, the saved configuration is restored from one of the devices to the controller.
The information saved includes the controller settings, device, storageset and unit configurations, and software
patches. The section "Using SAVE_CONFIGURATION to Save the Subsystem's Configuration" further describes
this feature. Note that any container initialized with the SAVE_CONFIGURATION option cannot be used on pre-
vious HSJ30/40 array controller HSOF software versions. See the section entitled "Replacing a Controller or
Cache Module with C_SWAP" in these release notes for instructions on how to replace a failed controller.
6.18 Host Tape Density Selection
You can now set the density for tape drive writes from the host operating system, and from the controller CLI.
Currently, the TSZ07 is the only tape drive for which you can set tape density from OpenVMS through the HSJ
controller using openvms init and openvms mount. Do not use these commands to set tape density on other tape
drives. Set tape density on other tape drives through programs that issue QIOs, as some customer applications do.
Inform the controller to allow the host to set tape density with the CLI command:
SET UNIT-NAME DEFAULT_FORMAT=HOST_SELECTED
When using dual-redundant controllers, tape format changes only appear on the controller that the device is
mounted through. SHOW UNIT only shows the updated format on the controller that has the tape online.
6.19 Disk Code Load Capability
| 17-03831-01
17-04367-01
DS-AIT35-VW
DS-RZ1BB-VW
DS-RZ1CB-VW
DS-RZ1CF-VA
DS-RZ1DA-VW
DS-RZ1DB-VW
DS-RZ1DD-VA
DS-RZ1DD-VW
DS-RZ1DF-VA
DS-RZ1EA-VW
DS-RZ1ED-VW
DS-RZ1EF-VA
DS-RZ1FC-VW
DS-RZ26N-VZ
DS-RZ28M-VZ
DS-SWXSS-06
DS-TZ89N-TA
DS-TZ89N-VW
EK-HSFAM-RN
EK-WBCIN-FI
QA-2YJAC-HS
XO-4820A-MC
XO-5002A-MC
XO-5005A-MC
XO-5135A-MC
XO-5172A-MC
|
