The following is an example of a correctly configured services.cfg file in an FSE implementation using a private network. The server variable is redundant in such FSE implementation:

hostname = fseserver.fsenet

server = fseserver.fsenet

2.In the omniORB.cfg file, configure the parameters in the section

--- Private network parameters --- with the following information:

•the FQDN that identifies the system 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 hostname variable in the

services.cfg file.

The following example is an excerpt from a properly configured omniORB.cfg file:

#--- Private network parameters ---

#Which interface omniORB uses for IORs

endPoint = giop:tcp:fseserver.fsenet:

#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 server connections:

#Only localhost and private network. Others are denied.

serverTransportRule = localhost tcp serverTransportRule = 192.168.240.0/255.255.255.0 tcp serverTransportRule = * none

The following is an example excerpt from the local /etc/hosts file that matches the above services.cfg and omniORB.cfg files:

123.45.67.89fse-server1.company.com fse-server1

192.168.240.1

fseserver.fsenet

fseserver

123.45.67.90fse-client1.company.com fse-client1

192.168.240.2

fseclient.fsenet

fseclient

HP StorageWorks File System Extender Software installation guide for Linux 41