User's Manual

HP StorageWorks File System Extender Software user guide 17
Client-server communication in a distributed FSE implementation
An external FSE client communicates with an FSE server through the network using CORBA services. An
external client can connect to only one FSE server.
Figure 5 Client-server communication
The network must provide a bidirectional connection between the FSE server and each of the external FSE
clients. You can verify the network connection using the FSE tool fse_net. For more information about
fse_net, see ”FSE troubleshooting tools” on page 274.
You can check whether a network connection is bidirectional by pinging the server from the client and vice
versa. If there is no response to one of the ping commands, the connection is unidirectional only. In this
case, FSE cannot perform its basic operations.
Unidirectional connections are provided, for example, if NAT (Network Address Translation) is used
between FSE clients and the FSE server.
IMPORTANT: In a distributed or mixed FSE implementation, if the FSE processes on the FSE server or
consolidated FSE system are restarted, you must restart the FSE processes on all external FSE clients to
resume normal FSE operation.
Configuring the communications settings in a distributed FSE implementation
In a distributed FSE implementation, an FSE client needs to know to which FSE server it belongs. To provide
this information, you need to modify the FSE interprocess (client-server) communications settings according
to your particular FSE implementation. These settings are affected by your choice of ordinary LAN