Installation guide

Administration guide. If you do not make this change before adding the new

interface, the Common Desktop Environment (CDE) Network Conﬁguration

application ( netconfig) and the netsetup utility might yield

unpredicable results.

This problem will be addressed in a future release of the operating system. If

you conﬁgure a NetRAIN set, you will need to migrate your set to a new

conﬁguration at that time.

4.4.8 LAT and NetRAIN

By default, the latsetup utility attempts to conﬁgure LAT for operation

over all network interfaces on a system.

If you have conﬁgured a NetRAIN virtual interface on your system, and the

latsetup utility attempts to run LAT over any of the physical network

adapters that comprise the NetRAIN set, the latstartup command will

hang.

To prevent this problem, conﬁgure LAT to run over speciﬁc network

interfaces on the system as documented in Section 5.7 of the Network

Administration guide. Run LAT over an interface that is not part of the

NetRAIN set.

4.4.9 NetRAIN and Microsoft Windows NT Clients

While using the default NetRAIN settings on a Tru64 UNIX server,

Microsoft Windows NT clients reset their TCP/IP connections before the

server is able to complete the failover to another interface. There are two

possible solutions:

• For environments with a few Windows NT clients, you can modify the

TcpTimedWaitDelay and TcpMaxDataRetransmissions NT

TCP parameters as follows:

TcpTimedWaitDelay= 30//The maximum retransmission timer.

TcpMaxDataRetransmissions=20//The maximum number of retransmissions.

• For environments with many Windows NT clients, it is more easier to

modify two NetRAIN kernel attributes on the server instead of modifying

the TCP retry timing parameter on each client system. On the Tru64

UNIX server system, modify the nr_max_retries and

netrain_timeout kernel attributes using the sysconfig -r

command or dxkerneltuner. For example, you can set the attributes

Base System Software Notes 4–31