User's Manual

HP StorageWorks File System Extender Software user guide 85
NOTE: SUSE Linux specific
On a SUSE Linux system, do not run YaST2 after you have configured this FSE host to use a private
network for the FSE interprocess communication. Running YaST2 modifies /etc/hosts in such a
way that the subsequent FSE implementation startups fail.
Alternatively, you can modify /etc/sysconfig/suseconfig by changing the line
CHECK_ETC_HOSTS="yes" to CHECK_ETC_HOSTS="no". You can then run YaST2 without
affecting FSE operation, but you cannot modify host names with it.
5. Start the omniNames service and all FSE processes using the fse --start command.
Note that you must first start the processes on a consolidated FSE system or on the FSE server, and then
start the processes on external FSE clients.
CAUTION: In the following procedures for configuring a LAN connection, if you reconfigure a system with
several network adapters enabled, you need to configure the parameters in the section
--- Private network parameters --- in the omniORB.cfg file as described in the procedures
for private network communication configuration, instead of commenting them out.
In this case, the parameters you specify in omniORB.cfg must be verified against the actual LAN
configuration for that system.
Reconfiguring communication on a consolidated FSE system or on an FSE server
Ordinary LAN connection
This section describes the configuration procedure for the following situations:
• if your FSE implementation consists of a consolidated FSE system and you do not plan to connect
external FSE clients to it.
• if you want your external FSE clients to communicate with the consolidated FSE system or with the FSE
server through an ordinary LAN.
Perform the following steps:
1. Ensure that the value of the server variable in services.cfg equals the fully-qualified domain
name (FQDN) that identifies the consolidated FSE system or the FSE server inside the LAN.
The following is an example of a properly configured services.cfg file in FSE implementation using
an ordinary LAN. The file can also include the hostname variable, but this variable is redundant in
such FSE implementation.
2. In the omniORB.cfg file on the consolidated FSE system or the FSE server, comment out all parameters
in the section --- Private network parameters --- and save the changes.
Private network connection
If your external (distributed) FSE clients will use a private network for communicating with the FSE server,
make the following modifications on the FSE server:
1. Add the hostname variable (if not present) to services.cfg and set its value to the fully-qualified
domain name (FQDN) that identifies the system inside the private network.
The following is an example of a correctly configured services.cfg file in FSE implementations
using a private network. The server variable is redundant in such FSE implementation.
server = fse-server1.company.com
hostname = fseserver.fsenet
server = fseserver.fsenet