User's Manual

hp StorageWorks File System Extender User Guide 79
1. Ensure that the value of the server variable in services.cfg equals the fully-qualified domain
name (FQDN) that identifies the consolidated FSE implementation or the FSE server inside the LAN.
The following is an example of a properly configured services.cfg file in FSE implementations
using an ordinary LAN. The file can also include the hostname variable, but this variable is redundant
in such FSE implementation.
2. Rename the omniORB.cfg file (for example, to omniORB.bak) on the consolidated FSE
implementation or the FSE server so that you will be able to retrieve it later if required.
Private network connection
If the external Windows FSE clients and the consolidated FSE implementation or the FSE server will
communicate through a private network, you must modify both configuration files, services.cfg and
omniORB.cfg, on each external Windows client, as follows:
1. Modify the value of the server variable in services.cfg to contain the fully-qualified domain
name (FQDN) that identifies the consolidated FSE implementation or the FSE server inside the private
network.
2. Add the hostname variable (if not present) to services.cfg and set its value to the FQDN that
identifies the Windows FSE client inside the private network.
The following is an example of a properly configured services.cfg file in FSE implementations
using a private network:
3. Rename the omniORB.cfg backup file (for example, omniORB.bak) back to omniORB.cfg. Modify
the following parameters in the file:
• the FQDN that identifies the consolidated FSE implementation or the FSE server inside the private
network
• the IP address of the system
• the subnet mask
All these parameters must be verified against the actual private network configuration. Ensure that the
FQDN you specify in omniORB.cfg matches the FQDN specified for the server variable in the
services.cfg file.
The following is an example of a properly configured omniORB.cfg file:
server = lan-server.company.com
hostname = fse-windows-client.fsenet
server = private-server.company.com
# Which interface omniORB uses for IORs
endPoint = giop:tcp:private-server.company.com:
# The order of network interfaces to use for accepting connections:
# Only localhost and private network. Others are denied.
clientTransportRule = localhost tcp
clientTransportRule = 192.168.240.0/255.255.255.0 tcp
clientTransportRule = * none
# The order of network interfaces to use for opening new connections:
# Only localhost and private network. Others are denied.
serverTransportRule = localhost tcp