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

•
Do not attempt to join a domain in which the controlling primary domain controller (PDC) does not
have a WINS entry on the WINS server. This may lead to the NAS server not being able to join
any domains in the future, even if the WINS entry is entered later.
•
For user mappings to work correctly, the mapping needs to happen prior to the client attaching to
the NAS server. If the client is currently attached and then the mapping takes place, the client
must be rebooted to update the connection information and save any information to the NAS
server with the correct owner.
•
After installation, if Windows users are not being correctly mapped, a reboot can fix the situation.
This problem can be identified by checking the mapped users on the system after an attempted
connection. If the user was not mapped, the domain probably did not register correctly, and the
NAS server needs to be rebooted to clear this problem.
•
Some Windows clients that have mapped NAS 8000 shares show zero free space available on
shares that in reality have free space. In such a case, there is a textApi command that will direct
the NAS 8000 to use a different way to report free space to Windows clients. Enter the following
command from the NAS 8000 command line:
% setNetworkSmbDfreeCommandEnabled T
Afterward, NAS 8000 shares should correctly report the free space to Windows clients. One
negative side effect is slower CIFS read/write performance. NFS performance is unaffected. To
go back to the default way of reporting free space to Windows clients, enter:
% setNetworkSmbDfreeCommandEnabled F
High Availability Windows Monitor
•
In some complex Windows domain environments, the clustered NAS 8000 Samba package
monitor randomly fails to authenticate and thus causes the package to fail over unnecessarily. If
this becomes an intolerable problem, then it is possible to tell the NAS 8000 Samba package
monitor to use a less rigorous monitoring algorithm. The default algorithm is enabled using the
following command:
% setNetworkSmbMonitorCommand "/sbin/smbMonitor"
The less rigorous monitoring algorithm is enabled using the following command:
% setNetworkSmbMonitorCommand "/sbin/smbMonitorLite"
It is possible to create another monitoring algorithm. The argument to the
setNetworkSmbMonitorCommand() command is the absolute pathname of a program or script
that returns 0 when Samba is functioning properly, and returns 1 when it is not. To enable
another algorithm, install the program or script on the NAS 8000, and then enter:
% setNetworkSmbMonitorCommand "<Program>"
where <Program> is the absolute pathname of the new program or script that monitors Samba.
High Availability (HA) Cluster Configuration
•
Volume groups that are not a part of a package appear to be available to create file volumes.
However, an error will occur if the user attempts to create a file volume on a volume group that is
not a part of a package.
•
Certain storage objects such as file volumes, directories, shares, snapshots, and scheduled
snapshots may be administered, viewed, and managed only via the Command View NAS
interface for the node on which they are active.
•
If an HA package is failed over to a node that already has Command View NAS running, it may
be necessary to refresh the Volume Group page before the existing browser session will
recognize the newly failed over storage.
HP StorageWorks NAS 8000
Version 1.6.3 Release Notes 5