Technical data

Managing TCP/IP Services

1.3 Setting Up User Accounts and Proxy Identities

The conﬁguration procedure TCPIP$CONFIG creates a proxy database ﬁle

called TCPIP$PROXY. You add proxies to this database with the ADD PROXY

command. The TCP/IP Services product allows two types of proxies:

• Communication proxy

A communication proxy provides an identity for remote users of RSH,

RLOGIN, RMT/RCD, and LPD. For each host, be sure to deﬁne the host

name and any aliases. Proxy entries are case sensitive. Be sure to use the

appropriate case when adding entries for remote users. Enter the ADD

PROXY command as follows:

TCPIP> ADD PROXY user /HOST=host /REMOTE_USER=user

You can use wildcards when adding proxy entries for users on remote

systems. For example, the following command provides the identity STAFF to

any user on the remote host STAR:

TCPIP> ADD PROXY STAFF /HOST=STAR /REMOTE_USER=*

• NFS proxy

NFS proxies provide identities for users of NFS client, NFS server, and

PC-NFS. In addition to host and user information, NFS proxies provide UNIX

identities with UID/GID pairs. NFS proxies can specify access to the NFS

client or the NFS server, or both.

For example, the following command provides the OpenVMS identity

CHESTER for a local NFS client user with the UID/GID pair 23/34.

TCPIP> ADD PROXY CHESTER /NFS=OUTGOING /UID=23 /GID=34 /HOST="orbit"

This user can access remote ﬁles from the NFS server

orbit

See the Compaq TCP/IP Services for OpenVMS Management Command Reference

manual for a complete description of the ADD PROXY command. For a more

complete discussion about UNIX style identities and how the NFS server and

client use the proxy database, see Chapter 20.

1.4 Conﬁguring a TCP/IP Cluster

If your host is part of an OpenVMS Cluster, you can use a cluster alias to

represent the entire cluster or selected host members. In this case, the network

sees the cluster as a single system with one name. Alternatively, you can

conﬁgure clustering using a DNS alias, as described in Chapter 5.

Incoming requests are switched among the cluster hosts at the end of each cluster

time interval (speciﬁed with the SET COMMUNICATION command).

Note

The cluster name is not switched from a host if there are any active TCP

connections to the cluster interface on that host.

A remote host can use the cluster alias to address the cluster as a single host or

the host name of the cluster member to address a cluster member individually.

All of the TCP/IP services support automatic failover and can be run on multiple

nodes in an OpenVMS Cluster. For example, if more than one host in the cluster

is running the NFS server, the cluster can appear to the NFS client as a single

1–6 Managing TCP/IP Services