KZPDC Product Issues and Restrictions. HP 5300A

KZPDC Product Issues and Restrictions. HP 5300A

KZPDC Product Issues and Restrictions

Platform Specific Issues and Restrictions

Note:

Consult the QuickSpec for the Alpha system on which the KZPDC controller will be installed for numbers of controllers supported and other platform specific information.

DS20E System Issues

Smart Array 5300A controllers are not supported in DS20E systems in Hose 0.

GS80, GS160 and GS320 System Issues

KZPDC controller support under OpenVMS on the GS80, GS160, and GS320 system platform is available beginning with version 7.3-2 of the operating system. The KZPDC controller is not supported under OpenVMS version

7.3-1 on GS80, GS160, and GS320 systems.

OpenVMS Galaxy system environments on the GS80, GS160, and GS320 platform must be updated with a forthcoming release of the Alpha System console version 6.7 (or later) prior to installing the KZPDC controller. System environments which are not partitioned or which employ only hard partitioning are supported with a minimum SRM console version corresponding to the v6.6 Alpha Firmware release.

The ADFU v1.00A shipped on a CD with the Smart Array 5300A option kit does not support GS80, GS160 and GS320 platforms. A future release of the

ADFU utility is planned which will provide the necessary support for these platforms. ADFU utility updates can be downloaded from the Smart Array

5300A web site when available.

10

Release Notes – Smart Array 5300A Backplane RAID Controllers

ES47, ES80 and GS1280 System Issues

KZPDC controller placement and configuration in model ES47, GS80, and

GS1280 systems is governed by the guidelines included in the associated platform QuickSpec.

ES47, ES80, and GS1280 system environments are now fully supported with the Smart Array 5300A runtime utilities under OpenVMS. This support is provided with OpenVMS Management Agents kit version 3.02 and the Smart

Array Configuration Utility XE version B0126. The previous restriction has now been removed which limited support of the KZPDC product on the ES47,

ES80, and GS1280 platform to a single controller instance per partition when the Smart Array 5300A utilities are installed.

The ADFU v1.00A shipped on a CD with the Smart Array 5300A option kit does not support ES47, ES80 and GS1280 platforms. A future release of the

ADFU utility is planned which will provide the necessary support for these platforms. ADFU utility updates can be downloaded from the Smart Array

5300A web site when available.

The SRM console environment variable “HEAP_EXPAND” does not exist on

ES47, ES80, and GS1280 platforms. Customers may disregard any requirement to set this variable when the KZPDC product is installed on these system types.

Alpha System Firmware Issues and Restrictions

Smart Array 5300A logical volumes configured as operating system dump devices must be resident on the KZPDC controller which is specified by the

BOOTBIOS console environment variable.

See the ES47, ES80, and GS1280 platform specific section of this document for considerations in setting the console environment variable

‘HEAP_EXPAND’ on those platforms.

Release Notes – Smart Array 5300A Backplane RAID Controllers

11

Tru64 UNIX Issues and Restrictions

Smart Array 5300A volumes are not supported as shared storage devices in

TruCluster environments.

OpenVMS Issues and Restrictions

Prior restrictions as noted in the Smart Array 5300A Product Release Notes on the use of KZPDC logical volumes in Volume Shadowing environments are removed. Users should consult the Volume Shadowing documentation accompanying their specific OpenVMS release for guidance in configuring this feature.

Smart Array 5300A volumes are not supported as shared storage devices in

OpenVMS Cluster environments.

KZPDC controller support under OpenVMS on the GS80, GS160, and GS320 system platform is available beginning with version 7.3-2 of the operating system. KZPDC controller support is not available under OpenVMS version

7.3-1 on GS80, GS160, and GS320 systems. Consult the platform specific section of these release notes for more information.

Runtime Utility Issues and Restrictions

The following items are known issues with the online utilities provided with Smart

Array 5300A controllers.

Users are referred to the cautionary advice elsewhere in this document concerning compatibility of the B0105 ACUXE kit with the version 3.xx

OpenVMS Management Agents kit.

Resizing (dragging the border of) the Netscape "HP Array Configuration

Utility XE" window, causes the ACU-XE session to end. A new session of

ACU-XE will have to be started. This issue will be fixed in a future release of

Netscape for Tru64 UNIX.

The GIF shown for an Array with a degraded Logical volume is the same as a

GIF for an Array with a failed Logical volume.

In some Tru64 UNIX systems with large configurations and large numbers of

SA5300 logical drives, starting up or exiting the ACU-XE utility might take an extra long time (up to 20 minutes.) The user might get an impression that

12

Release Notes – Smart Array 5300A Backplane RAID Controllers

the utility is “hung” since no indications of what is actually happening are present.

To check if the utility is still in startup or shutdown mode, you can put your cursor in the bar at the top of your window. If the utility is still active, then the cursor will change to an hour glass. This problem will be corrected in a future release of the ACU-XE utility.

With cpqim310 installed, if you try to resize the windows between the disks

(middle pane) and the detailed info (right pane), the data goes away and both panes turn dark brown/grey. A Netscape reload brings the data back. This issue will be fixed in a future release of Netscape for the Tru64 UNIX.

Critical errors on the Smart Array 5300A controllers are accompanied by red status messages within the Array Configuration Utility. The last statement in each of these messages, "For more information, run the Array Diagnostics

Utility.", should be disregarded. Please use Compaq Analyze to obtain further information about the reported errors.

When a condition occurs, such as a hardware fault, there may be data that needs to be flushed from cache.To perform the actual cache flush, run the

BIOS from the SRM console on the affected controller.

Firmware Issues and Restrictions

The maximum possible number of logical drives that can be configured on a

Smart Array 5300A controller is thirty two.

Logical volume capacity extension is not supported.

The maximum logical volume size supported by the firmware is 2 Terabytes.

If a Hot Spare has replaced a failed physical drive within a redundant array, the ACU-XE may show a logical volume having another volume below with

"???" as the spare capacity. Replacing the failed drive will cause the array to return to the original configuration.

In the event of a SCSI bus failure, all logical devices on this bus might become failed. There is a way these devices can be made available to the user (data integrity cannot be guaranteed, however). You have to shutdown your Alpha

Server and run BIOS on the controller housing these devices, i.e:

>>run bios pya0

Release Notes – Smart Array 5300A Backplane RAID Controllers

13

You will be presented with a choice of either recovering (making optimal) these devices or leaving them in the failed state. There is no default option under this scenario, and mandatory ‘user intervention’ is required.

Storage Enclosure Issues and Restrictions

Users are advised to follow the power sequencing rules below to avoid possible array volume state changes affecting the availability of user data:

When removing power to a storage enclosure attached to a Smart Array controller, first remove power to the host system, followed by powering off the storage enclosure.

When powering a system on, ensure all storage enclosures attached to a Smart

Array controller first receive power before applying power to the host system.

The BA610-6D internal disk cages are only supported with Nile logic cards

P/N 3R-A1629-AA/010615-001 of rev. 0B. Cards with P/N 3R-A1629-

AA/010615-001 of rev. 0A are not supported with Smart Array 5300A controllers. Customers who own BA610-6D modules with logic cards of P/N

3R-A1629-AA/010615-001 of rev. 0A and want to take advantage of internal

RAID must contact HP Field Service to have their 3R-A1629-AA/010615-001 rev. 0A cards replaced.

When configuring a Smart Array 5300A controller attached to a storage enclosure configured with a dual bus I/O module, each of the enclosure’s SCSI bus segments may be attached to a Smart Array controller instance.

Connecting a controller or adapter other than another Smart Array controller to the second SCSI bus segment of the enclosure is however unsupported.

If a Smart Array 5300A controller loses communication with a storage enclosure, then all physical drives in this enclosure are seen via SNMP Agent as located in an enclosure Bay 255. This typically means there is a hardware problem with the enclosure. You should contact HP Services for the enclosure troubleshooting.

14

Release Notes – Smart Array 5300A Backplane RAID Controllers

Hardware and Connection Details

The StorageWorks 4400 (MSA30) series of storage enclosures are supported for use with the KZPDC controller at up to U3 (Ultra160) SCSI data transfer rates.

All supported external enclosures ship with U3 SCSI compliant cables. See the

QuickSpec for your HP StorageWorks storage enclosure for the list of supported cables.

The model 4254 P/N 138151-001 (DS-SSL14-RS) contains an Ultra2 capable

I/O module which is dual bus only.

The model 4354 P/N 190211-001 (DS-SL13R-BA) contains an Ultra3 capable

I/O module which is dual bus only.

The model 4214 P/N 103381-001 (DS-SSL14-RM) contains an Ultra2 capable

I/O module which is single bus only.

The model 4314 P/N 190209-001 (DS-SL13R-AA) contains an Ultra3 capable

I/O module which is a single bus only.

For the models 4254 and 4354, the device ID's on each bus segment will be 0 through 5 and 8. ID's 6 and 7 are reserved.

For the models 4214 and 4314 the device ID's on each bus segment will be 0 through 5 and 8 through 15. ID's 6 and 7 are reserved.

Also contained in the 4254, 4354, 4214 and 4314 is an EMU P/N 70-40064-03 with fault bus support.

HP StorageWorks Enclosure 4200 (models 4254 and 4214) or 4300 (models

4354 and 4314) device shelves cannot be daisy chained together.

With Tru64 UNIX, depending on the particular system configuration, using the MC2 page jumper set for 512MB may cause errors similar to

"ciss_map_data"to appear in the system logs. If this happens, change the jumper to the 128MB position.

All of the cluster members need to have the jumper configured the same way.

Release Notes – Smart Array 5300A Backplane RAID Controllers

15

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project