HP StorageWorks NAS 8000 Version 1.6.0 Release Notes These release notes are for NAS operating system (OS) version 1.6.0. The version number of the NAS OS software appears on the Identity tab of the Command View NAS interface.
These release notes appear in the following main categories: Product Changes and Improvements Operating System Command View NAS Web Interface NAS Data Path Manager Release Notes Operating System and Web Interface Applications NAS Data Path Manager Product Changes and Improvements Operating System • • • • • • • • • Three new disaster recovery commands: - recoverSystemStorageDedicatedAttachConfig – rebuilds configuration on dedicated attached arrays by examining NAS head storage configuration - recoverSyst
NAS Data Path Manager • • Introduced the new, optional Data Path Manager product. - Provides complete fibre channel multipath functionality including path load balancing, path failover, and automatic failback - Allows NAS 8000 to continue to operate after failures of HBAs, switches, and disk system controllers - Customizable use of paths for load balancing or failover See the product data sheet on the web for details. It is located at: http://storage.inet.cpqcorp.
Command View NAS Tested Configurations • Any browsers that support the Sun Microsystems Java Plug-in (version 1.3.1 or later) should be able to run the Command View NAS interface. Tested configurations include: Client OS/NOS Browser Java plug-in Windows 98 Internet Explorer (IE) 5.5 Service Pack (SP) 0, SP1, SP2 1.3.1.0 Windows 2000 IE 5.5 SP0, SP1, SP2 1.3.1.0 Windows NT IE 5.5 SP0, SP1, SP2 1.3.1.0 Windows ME IE 5.5 SP0, SP1, SP2 1.3.1.0 Windows XP IE 5.5 SP0, SP1, SP2 1.3.1.0 HP-UX 11.
• • • On an HA system, users may run into difficulty deleting a volume group if they delete the failover package containing the volume group without first deleting any file volumes on that volume group. A volume group cannot be deleted without first removing all file volumes that it contains. However, once a package has been removed, any associated file volumes will not be visible/deletable.
LUN Management • Do not use another storage array management tool, such as Command View SDM, to delete LUNs associated with NAS 8000 volume groups. Once a volume group is created and associated with a LUN, it is recognized by the NAS 8000 user interface, and must be managed from it to ensure that you do not lose data.
Storage Quotas For Users and Groups • In quotas, the user/group list is not filtered. Therefore, it is possible to add a user/group quota for a user/group that already has a quota. In this case, the previous user/group quota is overwritten. • There is a single grace period per file volume. A grace period set for a file volume will be enforced on BOTH users and groups regardless of which type of quota was set.
• In an HA environment, CA Unicenter reports the first package IP address discovered as the IP address for the cluster. • The NAS icon does not appear correctly in HP TopTools. Virus Guard • A volume being scanned cannot be deleted while the scan task is running. Wait until scan task is complete to delete volume. • RTP ignores volumes with NFS mount points defined. Only volumes with CIFS shares will be scanned. Volumes with both NFS mounts and CIFS shares will not be scanned in real time.
• NetBackup reports "130 - system call" error when encountering large inode values, the backup will fail. With NetBackup 4.5 this can be avoided by setting the NDMP environment variable "SET HIST=P" in the “policy” on sub-tab “file” as the first line. NetBackup 3.4.1 users could add "SET HIST=N", but only complete session restores are then possible. NetBackup 3.4.1 users are recommended to upgrade to NetBackup 4.5 to support the NAS 8000 large file capacity. Check Veritas website for future patches.
- From the Command Line Interface Error message: com.hp.HpPanDev.SanDevice.DeviceException: Non Responding Device: c9b0t0l0 Unknown SCSI status at com.hp.HpPanDev.Array2001Obj.CBridge.scsiErrorCheck( CBridge.java: 8674) . . . Solution: From the Command Line Interface, execute the following command: % scanStorageHbaScsi These corrective actions will only work if an alternate management path is available for use (usually through another HBA).
