User's Manual

hp StorageWorks File System Extender User Guide 75
1. At the command prompt, use the cd command to change the current directory to the mount point of the
HSM file system, and run the dir command.
2. Invoke the following command:
In the command output, the corresponding FSE partition should have its status set to mounted.
NOTE: For information on how to determine the access mode for a particular HSM file system or
troubleshoot potential problems with disk volume access, see the description of the fse command in the
FSE command-line reference.
Reconfiguring FSE interprocess communication
FSE interprocess communication is configured according to the FSE implementation (consolidated,
distributed, or mixed FSE implementation) and the network type used for FSE interprocess communication
(ordinary LAN, private network). The initial configuration must be performed after the FSE software
package installation, before the FSE implementation is put into operation for the first time. Afterwards, if
the implementation or the network type is changed, the communication settings must be reconfigured.
CAUTION: An appropriate configuration of the FSE interprocess communication is of crucial importance
for normal FSE operation. An improperly modified communication configuration may lead to a
non-operating FSE implementation.
FSE interprocess communication settings consist of two plain text files installed on each FSE host. The files
and their locations are the following:
NOTE: .Depending on the network type used for interprocess communication in your FSE implementation
(LAN, private network), omniORB.cfg may not be present in the specified directory. You can always find
its template in the directory /opt/fse/newconfig and copy the file to its target location, if needed.
You can also change the default path where FSE searches for the omniORB.cfg file using the
OMNIORB_CONFIG environment variable.
The reconfiguration procedure
The general procedure for reconfiguring interprocess communication is as follows:
1. Stop all FSE processes with the fse --stop command.
Note that you must first stop the processes on external FSE clients, and then stop the processes on a
consolidated FSE implementation or on the FSE server.
2. Stop the omniNames service with the omniNames --stop command.
3. Purge the omniNames (CORBA) service data files. Their location is platform-dependent.
Linux specific
On Linux platform, omniNames service data files are located in the directory
/var/opt/fse/omniorb.
Windows specific
On Windows platform, omniNames service data files are located in the directory
%InstallPath%\var\omniorb.
C:\>fsepartition --list
Configuration file Location on Linux platform Location on Windows platform
services.cfg /etc/opt/fse %InstallPath%\etc
omniORB.cfg /etc/opt/fse %InstallPath%\etc