Reconfiguring communication on external Linux FSE clients

Ordinary LAN connection

If the external Linux FSE clients and the consolidated FSE system or the FSE server will communicate through an ordinary LAN, you have to modify the services.cfg file on each external Linux FSE client, as follows:

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 implementations using an ordinary LAN. The file can also include the hostname variable, but this variable is redundant in such FSE implementation.

server = fse-server1.company.com

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.

3.Repeat step 2 of this procedure on the external Linux FSE client.

Private network connection

If the external (distributed) Linux FSE clients will communicate through a private network to the FSE server, you must modify both configuration files, services.cfg and omniORB.cfg, on each external Linux 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 system 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 Linux 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:

hostname = fseclient.fsenet

server = fseserver.fsenet

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

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

•the FQDN that identifies the consolidated FSE system 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 example is an excerpt from a properly configured omniORB.cfg file:

#--- Private network paremeters ---

#Which interface omniORB uses for IORs

endPoint = giop:tcp:fseclient.fsenet:

#The order of network interfaces to use for accepting connections:

#Only localhost and private network. Others are denied.

HP StorageWorks File System Extender Software user guide 87