Release Notes hp StorageWorks NAS 4000s/9000s Product Version: 4.1 First Edition (November 2003) Part Number: 352398-001 This document is intended for HP StorageWorks NAS 4000s and 9000s running version 4.1 of the NAS software image. This document provides information not available in other documents.
© 2003 Hewlett-Packard Development Company, L.P. Microsoft®, Windows®, and Windows NT® are trademarks of Microsoft Corporation in the U.S. and other countries. Intel®, Pentium®, and Itanium® are trademarks of Intel Corporation in the U.S. and other countries. UNIX® is a trademark of The Open Group in the U.S. and other countries. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein.
Contents Release Notes Information ..................................................................5 General Notes .......................................................................................5 Compaq IML Log Viewer Win32App does not recognize .iml files . 5 Cannot fully install Secure Path Manager.......................................... 6 Shadow Copy for Shared folders is the wrong version ...................... 6 Services for NFS..............................................................
Renaming host forces a restart where the restart page does not refresh ............................................................................................... 13 Altering the Network interface from DHCP to static causes the page not to return ...................................................................................... 14 Managing NTFS Mount points......................................................... 14 Default Username and Passwords ....................................................
Release Notes Information These Release Notes cover the following major topics: • General Notes • Services for UNIX® (SFU) • NAS Web User Interface • Microsoft® Server 2003 • Quick Restore Process General Notes Compaq IML Log Viewer Win32App does not recognize .
Cannot fully install Secure Path Manager When attempting to install Secure Path Manager, the install fails. The Client Tools displays a Java Runtime Engine install. ‘Windows cannot find JREs\j2re1_3_1-win.exe message. To resolve this issue, after installation of Secure Path Manager and BEFORE running Client Tools to install the Java Runtime Engine, exit the installation tool (Automenu.exe) and re-run it. During the second run of the installation tool, the client tools \JRE install will function correctly.
Keep the following in mind when toggling between synchronous and asynchronous writes: 1. When the caching setting for Services for NFS is set to asynchronous writes (caching on), NFS clients may incorrectly assume that all the writes were safely committed to stable storage; the writes were only in the Server for NFS cache. 2.
Clearing the NFS log via the WebUI causes the log file to become inaccessible When clearing the NFS logs via the WebUI, the log file will clear but the file permissions are set incorrectly. Access to the log c:\msnfs\logs with Windows Explorer will be denied. To resolve the issue, stop the Server for NFS service, then clear the NFS log, then start the Server for NFS service. The log file will then be accessible.
All logical disks to be used for NFS sharing should be mounted on a drive letter, not on a reparse or mount point. If no NFS shares will be created on a particular logical disk, that virtual disk may be mounted on a mount point instead of a drive letter. Admin cannot list and map domain users and groups for Services for NSF mapping unless the Services for NFS admin is logged into the domain The administrator must log into the domain before mapping domain users and groups.
The mapping service can be re-started once all network ports become active through a link or port terminator. Help instructions for creating NFS share cluster resource is incorrect The help instructions for the WSS2003 Services for NFS share cluster resource creation lists an incorrect parameter. The GlobalPerm parameter should be documented as GlobalPermV2 instead.
Advanced Cluster Management button yields error on nonconfigured clusters On a system where clustering is not established, clicking on the Advanced Cluster Management button will yield an error from cluster administrator that Cluster service on node xxxx cannot be started. The Service is either not installed or not configured. This message is displayed when attempting to setup the cluster for the first time and is considered normal.
Improper Closure of Remote Desktop Certain operations can leave the utilities running if the browser is closed versus exiting from the program via the application menu or logging off the terminal server session. Some applications may become orphaned in this manner when the Terminal Server Session is exited improperly. Note that a maximum of two Terminal Server sessions may be used at any given time.
Rapid Startup becomes unresponsive if a NIC team is established Rapid Startup becomes unresponsive, if a NIC Team is established and then Rapid Startup is run with the team in place, the network settings pages will become unresponsive, and the wizard page cannot be exited. To exit Rapid Startup, click some other menu item in the Web UI. NOTE: NIC Teams will need to be dissolved when utilizing Rapid Startup.
Altering the Network interface from DHCP to static causes the page not to return If the Web UI is used to alter the IP settings of the port from which you are managing, the host will be unreachable from the current address. When this happens, the network interface page buttons become grayed out and the page does not return, although the settings take affect. To access the Web UI again, close and open the browser and navigate to the newly identified management port.
RESOLUTION There are three methods for removing orphaned CIFS and NFS shares from the system. Methods one and two cause an interruption in service. 1. Restart the Server service: a. Open the web interface to the 4000s/9000s: b. Click Maintenance > Remote Desktop and log in. c. Right-click My Computer and choose Manage. d. Open the Services portion of the management tree. e. Right-click Server and select Restart. 2. Restart the 4000s/9000s: a. Open the web interface. b.
If the orphaned share was also an FTP Share: 1. Click the NAS Management console found on the desktop. 2. Expand Core Operating System. 3. Expand Internet Information Services. 4. Expand the NAS machine name. 5. Expand the Default FTP site tab. 6. Right-click the name of the share to delete. 7. Choose Delete. If the orphaned share was also an HTTP Share: 1. Click the NAS Management console found on the desktop. 2. Expand Core Operating System. 3. Expand Internet Information Services. 4.
DFS root does not update on file share page If a DFS root is created and enabled by default on shares, then later recreated under a new name, the File Share page does not update the DFS local root information and attempts to create DFS entries under the old name. To correct this issue, access the Distributed File System Properties page, update the default DFS information, and click OK. The file share page will now contain the proper DFS information.
Cannot add a new node into existing cluster from new node In a cluster already up and running, if an attempt is made to add a new node from the server which is not a existing member, the action will fail and a message will be displayed The cluster service on new node can not be started. The only way to add new node in a cluster is to add it from a node that is already a member of the cluster.
and reboot the device. The forced cleanup command may then be executed. See Microsoft knowledge base article Q297881 or Knowledge Base article Q282227. Event Log Messages in the Event Log Benign Perflib warnings are seen after opening the Performance Monitor and adding a performance counter to the monitor in the application event log.
Incorrect error when file screening is implemented under Storage Manager If file screening is enabled on a volume or directory for a particular file type and a file transfer of the restricted type is attempted to that volume, an inappropriate error message is returned to the user. The user receives a Not enough free disk space error message when disk space is indeed available, the file is simply blocked.
Creating the DFS Local Root in a cluster 1. Create or make use of a cluster group via the Web UI Cluster Pages. 2. Create or make use of a physical disk resource via the Web UI Cluster Pages. 3. Create or make use of a file share resource via the Web UI Cluster Pages. 4. Create or make use of an IP address via the Web UI Cluster Pages. 5. Create or make use of a network name via the Web UI Cluster Pages, note the network name will become the root mount point. 6.
2. Access the remote desktop feature from the Web UI Maintenance tab and log in into the console. 3. Select Start > Programs > Administrative Tools > Distributed File System, the DFS root should appear. 4. Right-click on the DFS root and select new link. 5. Fill out the appropriate fields including: link name and path to target (ex. \\network_name\file_share) 6. Click OK, the link will be added. 7. From a client, map a network drive to the DFS root and test the share.
Quick Restore will not function when trying to QR on a broken mirror of the operating system When using quick restore on a system with a failed drive or rebuilding mirror set of the operating system drives, an error message will be displayed. Quick restore will not function with a failed or rebuilding mirror set. Resolution: Replace the failed drive and wait for the rebuild to finish.
The default configuration is: Array A: Consists of two logical drives and two physical drives in slots 0 and 1. Logical Drive 1: Raid: 1 Size: 27555 MB Sectors: 32 Stripe Size: 256 Array Accelerator: Enabled Logical Drive 2: Raid: 1 Size: 7171 MB Sectors: 32 Stripe Size: 256 Array Accelerator: Enabled If the Array and Logical Drive configuration has been altered and the Quick Restore fails to work properly, use the Array Configuration Utility to configure the drives as described above.
