Table of Contents
Advertisement
Managing SNAplus2 Clients
Managing HP-UX Clients
before beginning or restarting the attempt to contact a
server. If the client has lost contact with the server,
SNAplus2 does not wait for the full timeout period, but
retries after a random period between 5 seconds and
the specified timeout; this is to avoid bursts of network
traffic caused by large numbers of clients attempting to
contact a server at the same time.
This parameter is optional; if it is not specified, the
default is 200 seconds.
*
This line indicates that the client should attempt to
contact a server running SNAplus2 by using a UDP
broadcast message to all computers on its TCP/IP
subnet (or on all subnets that it can access, if the client
computer contains more than one LAN adapter card).
The client retries the broadcast every 10 seconds, up to
the number of attempts specified by the
broadcast_attempt_count parameter, until it
contacts a server. If the limit specified by
broadcast_attempt_count is reached before a server
has been contacted, the client then tries using directed
messages to one or more named servers (specified by
the following lines of the file).
In situations where the client cannot reach any servers
using UDP broadcasts, do not include this line. This
applies in the following cases:
• When the SNAplus2 LAN spans multiple TCP/IP
• When UDP support is not installed on the client
In other cases, the use of UDP broadcasts is optional; to
specify that broadcasts should not be attempted, do not
include this line.
If this line is included, it must precede any server
names in the file.
server names
Specify the names of one or more SNAplus2 servers
that the client should contact. If the * line (to indicate
the use of UDP broadcasts) is not included, or if the
client tried to contact a server using this method but
298
subnets, and there are no SNAplus2 servers in any
TCP/IP subnet that the client can access using UDP
Chapter 11
Advertisement
Table of Contents
