HP-UX SNAplus2 R7 Administration Guide

ManualsBrandsHP ManualsSoftwareHP-UX SNAplus2 Software

171

172

173

174

175

176

177

178

179

180

Managing SNAplus2 Client/Server Systems

Managing HP-UX Clients

If the client uses the broadcast method to contact a server (speciﬁed by the * entry), this parameter speciﬁes

the maximum number of broadcasts to be made in one attempt to contact a server. The minimum value is 1;

if a higher value is speciﬁed, the client retries every 10 seconds until it contacts a server or until this count

is reached. If the count is reached without contacting a server, the client then attempts to contact a named

server.

This parameter is optional; if it is not speciﬁed, the default is 5.

server_lost_timeout

If the client loses contact with a server and needs to reconnect, or if it has failed to contact a server using

either broadcasts or named servers, this parameter speciﬁes the time in seconds for which the client waits

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 speciﬁed timeout; this is to avoid bursts of network trafﬁc caused by large numbers of clients attempting

to contact a server at the same time.

This parameter is optional; if it is not speciﬁed, 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 speciﬁed by the

broad-

cast_attempt_count parameter, until it contacts a server. If the limit speciﬁed 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 (speciﬁed by the following lines of the ﬁle).

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 ﬁle.

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 subnets, and there are no SNAplus2 servers in any TCP/

IP subnet that the client can access using UDP

• When UDP support is not installed on the client

server names

Specify the names of one or more SNAplus2 conﬁguration servers that the client should contact to obtain

conﬁguration information. This list should contain the names of the master conﬁguration server and any

backup servers in the same domain as the client. For information about conﬁguring master and backup

servers, see Section 4.1, Conﬁguring Client/Server Functions.

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 received no response, the client attempts to contact the ﬁrst server listed using a directed

message. If this fails, the client tries the second server listed, and so on. This means that you can balance

the load between two or more conﬁguration servers by changing the order in which the servers are listed.

If the * line (to indicate the use of UDP broadcasts) is not included, at least one server name must be speciﬁed;

otherwise, server names are optional.

If the client tries all the servers listed without success, it waits for the time speciﬁed by server_lost_timeout

above, and then restarts the process of trying to contact a server (either with UDP broadcasts or with the ﬁrst

server listed).

171