Windows X9000 Clients; Synchronizing Information On File Serving Nodes And The Configuration Database - HP StorageWorks x9300 Administrator's Manual

Hide thumbs Also See for StorageWorks x9300:
Table of Contents

Advertisement

never migrated back to the primary server. If you execute ibrix_fs -i -f FSNAME, the output
will list No in the ONBACKUP field, indicating that the primary server now owns the segments,
even though it does not. In this situation, you will be unable to complete the failback after you fix
the storage subsystem problem.
Perform the following manual recovery procedure:
1.
Restore the failed storage subsystem.
2.
Reboot the primary server, which will allow the arrested failback to complete.
X9000 client I/O errors following segment migration
Following successful segment migration to a different file serving node, the management console
sends all X9000 clients an updated map reflecting the changes, which enables the clients to
continue I/O operations. If, however, the network connection between a client and the management
console is not active, the client cannot receive the updated map, resulting in client I/O errors.
To fix the problem, restore the network connection between the clients and the management console.

Windows X9000 clients

Logged in but getting a "Permission Denied" message
The X9000 client cannot access the Active Directory server because the domain name was not
specified. Reconfigure the Active Directory settings, specifying the domain name (see the HP
StorageWorks X9000 File Serving Software Installation Guide for more information.).
Verify button in the Active Directory Settings tab does not work
This issue has the same cause as the above issue.
Mounted drive does not appear in Windows Explorer
To make a drive appear in Explorer, after mounting it, log off and then log back on, or reboot the
machine. You can also open a DOS command window and access the drive manually.
Mounted drive not visible when using Terminal Server
Refresh the browser's view of the system by logging off and then logging back on.
X9000 client auto-startup interferes with debugging
The X9000 client is set to start automatically, which can interfere with debugging a Windows
X9000 client problem. To prevent this, reboot the machine in safe mode and change the Windows
X9000 client service mode to manual, which enables you to reboot without starting the client.
1.
Open the Services control manager (Control Panel > Administrative Tools > Services).
2.
Right-click IBRIX Client Services and select Properties.
3.
Change the startup type to Manual, and then click OK.
4.
Debug the client problem. When finished, switch the Windows X9000 client service back to
automatic startup at boot time by repeating these steps and changing the startup type to
Automatic.
Synchronizing information on file serving nodes and the configuration
database
To maintain access to a file system, file serving nodes must have current information about the file
system. HP recommends that you execute ibrix_health on a regular basis to monitor the health
of this information. If the information becomes outdated on a file serving node, execute ibrix_dbck
-o to resynchronize the server's information with the configuration database. For information on
ibrix_health, see
"Monitoring cluster health" (page

Synchronizing information on file serving nodes and the configuration database

48).
81

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents