Adding Storage
•
To get a current, accurate representation of the available storage after adding new storage
(arrays or LUNs), click on Actions > Scan for New Storage in Command View NAS. Clicking
the Refresh button on the array summary page will not result in newly added storage being
detected and displayed by the interface.
Deleting Directories
•
Directories must be empty prior to being deleted through the Command View NAS interface. If
you attempt to delete a directory that contains files or sub-directories, an error message will
indicate that the command 'rmdir' failed. Manually delete any files or sub-directories prior to
deleting the directory though the Command View NAS interface.
Miscellaneous Device Management
•
After enabling or disabling an application (for example, Data Path Manager), a Command View
NAS browser session needs to be closed and restarted for the effects of the new application to be
visible in Command View NAS.
•
On some occasions, the Exception Handling page under the Support tab will not display any
information in the 'Debug Level' border and the Actions menu is disabled. Closing the browser
and restarting Command View NAS will typically resolve this problem.
•
In a SAN configuration, the array identifiers are missing on the Command View NAS Identity
page.
•
Minimal System requirements for management clients using Sun, Windows and Linux are:
-
CPU: Pentium II, 233 MHz or better
-
Memory: 128 MB recommended
-
Video Card: at least 256 colors
-
Note that Command View NAS is a rich client application, so increased memory and CPU
speed along with good network connections will significantly improve the performance of
Command View NAS.
•
The Command View NAS interface does not always re-size with the browser window, especially
when running in Mozilla. Restart the browser and re-size it to the desired size before accessing
Command View NAS.
•
The Command View NAS interface caches the system time when the user interface is launched.
Subsequent uses of this time from within the user interface will, therefore, be off by the amount of
time that the interface has been up. For example, if the Command View NAS interface is
launched at 1:15pm, and at 1:30pm the administrator creates a snapshot scheduled to expire
after one hour, it will actually expire after 45 minutes. This is because the user interface had a
cached time of 1:15pm when the snapshot was created and scheduled the expiration for 2:15pm
(one hour later) which is really 45 minutes after the snapshot was actually created. There are two
workarounds for this situation:
1. Navigate to Configuration->System Properties, and refresh the page. This will update the
user interface to the current system time.
2. Use the absolute expiration time methodology instead of the relative expiration time
methodology. By setting an absolute time, the snapshot will expire at the desired time as
opposed to a relative offset from the cached system time.
•
The "Add Group Mapping Entries" dialog uses the term "User" rather than "Group" for fields in the
dialog. To know if you're adding group mappings or user mappings, look at the title bar of the
dialog, which is accurate.
Applications
Network Management
•
If you are unable to launch Command View NAS from CA Unicenter, you can access Command
View NAS by manually launching your browser and addressing the NAS 8000 directly.
HP StorageWorks NAS 8000
Version 1.6.3 Release Notes
10
Need help?
Do you have a question about the StorageWorks NAS 8000 - Version 1.6.X and is the answer not in the manual?
Questions and answers