HP StorageWorks NAS 8000 - Version 1.6.X Release Note page 7

•
Share passwords must be created in identical order on each node. Share-level security is not
suggested for an HA cluster.
•
In an HA environment, the mappings that are done on one node must be duplicated exactly on
the second node. The mappings from one node are not propagated to the second node
automatically. If you fail to have identical mappings on both nodes, users can be prevented from
accessing or modifying files in the event of a failure. For example, assume that a Windows user
that is mapped to a Unix user on Node A has access to a file. If the same mapping does not exist
on Node B and Node A fails, the user could be denied access and other rights to the file. An
alternative to using the mapping function in the user interface is to perform mappings using the
following text API command:
mapClusterSystemWindowsUser(Group)NameToUnixUser(Group)Name
•
Snapshots can fail if two or more snapshots are created simultaneously on different nodes of a
cluster. This happens when you schedule the creation of a snapshot for the same time on both
nodes of the cluster. To avoid this problem, stagger the creation time of one of the snapshots by
5 or more minutes.
•
If you use the Configuration Wizard to setup your cluster, note that, on the High Availability
Configuration page, the area called Nodes in Cluster at the bottom is not visible until you expand
the dialog vertically.
•
The Alerts/Logging sections of Command View NAS 8000 do not propagate the settings from one
node to another. Therefore, you must manage each node individually. This applies to SNMP
Alerts, SMTP E-Mail Alerts, and Remote System Logs.
Client Network Configuration Browser Issues
•
Users of Windows 98 clients will need to refresh their Windows Explorer directory view manually
to see changes, additions, or deletions to files contained on the NAS 8000. Windows 2000 and
Windows NT users will not experience this problem.
•
The client command showmount does not return the same mount paths as shown in the user
interface. The command will list much longer path names, but they are valid, mountable paths.
For user convenience, we map the longer paths returned by showmount to shorter, easier-to-
remember paths, in the user interface. Either path will mount correctly.
•
When accessing the Command View NAS interface, the browser may display a "NOT BOUND IN
REGISTRY" exception, or may appear hung with a "Service not bound" exception displayed in
the Java console. (To view the Java console, click on the Java icon in the Windows system tray,
or in the task list.) This problem may be due to the use of a proxy when accessing the NAS 8000.
If so, configure your browser to bypass the proxy server for the NAS 8000. Another possible
cause is that the Command View NAS graphical user interface (GUI) services need to be
restarted on the NAS 8000 server. To do this, telnet to the NAS 8000 server and login as the
administrator. At the command prompt, type restartSystemGui. You should then be able to
access the Command View NAS interface.
•
With the Java 1.4.0 plug-in and Netscape 4.7x, some dialog boxes in the Command View NAS
interface contain un-editable fields after changing the default settings of the dialog box.
- For use with Netscape 4.7x, use the Java 1.3.1 plug-in.
- When an un-editable field is encountered with the Netscape 4.7x/Java 1.4.0 plug-in
combination, click away from (outside of the vicinity of) and back to the problematic dialog
box to force a refresh of the Focus Manager.
•
Command View NAS does not work on a Windows 2000 client that is running Windows
NetMeeting 3.0 with remote desktop sharing active. Command View NAS works fine with
NetMeeting, even if remote desktop sharing is enabled, as long as it is not active.
HP StorageWorks NAS 8000
Version 1.6.3 Release Notes 7