FW 07.00.00/HAFM SW 08.06.00 HP StorageWorks HA-Fabric Manager User Guide (AA-RS2CF-TE, March 2005)

HA-Fabric Manager user guide 171

-Dsmp.zoning.wait.timeout=180000 -Dsmp.debug

-Dsmp.webServer -Dsmp.callback.passive

-Dsmp.flavor=%APP_FLAVOR% Server

...............

:end

popd

endlocal

TCP port numbers

This section provides information about configuring TCP port numbers for remote management

interface (RMI) servers and registries to allow the HAFM client and server application to function

across firewalls.

HAFM function with RMI at TCP port level

The HAFM appliance communicates with clients through the RMI server (Figure 99). This is a

full-duplex function. However, the HAFM client must know the TCP/IP port number of the RMI server

on the HAFM appliance before they can communicate. The RMI registry communicates this TCP port

number to the HAFM client. The HAFM appliance obtains the TCP port number of the RMI Server on

the Client during initial communications.

Figure 99 HAFM appliance and client communications

The TCP port numbers of the RMI server are randomly and automatically selected on both the HAFM

appliance and client as a full-duplex function. Firewalls are configured to block all unknown

incoming connections with no mapping of outgoing connections based on a socket part of TCP and

IP.

To work around this problem, administrators can configure the port numbers into appropriate batch

files, and then configure the firewall to unblock the configured port numbers. The procedure that you

follow depends on how the firewall is set up:

• If the firewall prevents the client from connecting to arbitrary ports on the server, then perform the

following procedures:

•”Forcing the RMI registry to use a specific port” on page 172

HAFM appliance

RMI server RMI registry

HAFM client

RMI server RMI registry

RMI servers’s TCP/IP port #

Full-duplex communication