Polling client function, Configuring for faster logins, Forcing a client to be polling – HP StorageWorks 2.32 Edge Switch User Manual
Page 212

Configuring HAFM Through a Firewall
212
Polling Client Function
In some cases, a network may use virtual private network (VPN) or firewall
technology, which can prohibit communication between Servers and Clients. In
other words, a Client can find a Server, appear to log in, but will immediately be
logged out because the Server cannot reach the Client. To resolve this issue, the
HAFM application will automatically detect the network configuration and run
the Client in “polling mode” when necessary.
When the Client is not running in polling mode, the Server calls the client
whenever it has new data. When the Client is running in polling mode, the Server
will queue up the data and the Client will periodically (approximately every 5 or
10 seconds) check in and get the data. Thus, the original two-way communication
is transformed into one-way communication, allowing passage through firewalls.
Configuring for Faster Logins
When a Client attempts to log into a Server, the Server normally calls back to
verify communication. In a firewall situation, this call will fail and the Server
automatically treats the Client as a “polling” Client. It may take up to 45 seconds
for this call-back to fail (worst case). You can configure a polling parameter in
Client and Server batch files to let the Server know ahead of time that the Client is
a “polling” Client. This skips the call-back from the Server and decreases the
login time.
Forcing a Client to Be Polling
To force a specific Client to be a polling Client, edit the
HAFM_co.bat
file and
the Client portion of the
HAFM_sc.bat
file, if both files are installed on your
computer. These files are in the
HAFM 8.x\bin
directory (typically in
c:\Program Files\HAFM 8.x\bin
).
The
HAFM_sc.bat
file starts both the Client and Server and is installed on a
computers with the HAFM appliance software. The
HAFM_co.bat
file starts the
Client only and is installed with the Client software.
Add the
-Dsmp.callback.passive
parameter as in the following example.
This parameter only affects this client; all other clients can be regular clients.