HP -UX B6941-90001 Administrator's Reference Manual page 129

hostname is truncated after the first dot (.), and the first part of the
ARPA hostname becomes the NS node name for the vt3k operation. This
mechanism assumes that the truncated name identifies a node in the
same NS domain as the management server, since a fully-qualified NS
node name is unavailable.
If the truncated ARPA host name differs from the NS node name or the
MPE/iX managed node belongs to a different NS domain, ITO supports
the mapping file below to avoid this problem:
/etc/opt/OV/share/conf/OpC/mgmt_sv/vt3k.conf
This file can be a symbolic link to /etc/xnmvt3k.conf or the file below,
used by ITO for remote logins on HP 3000 systems via vt3k:
/etc/opt/OV/share/conf/xnmvt3-k.conf
ITO resolves the ARPA host name to NS node name as follows:
1. It searches for the first line in the vt3k.conf file that begins with a
matching ARPA hostname. If a matching name is found, the NS node
name in the second column is input to the vt3k operation.
2. If no matching ARPA hostname is found in the vt3k.conf file, the
search is repeated with only the first part of the ARPA host name (the
part preceding the first dot). If a matching name is found, the NS
node name in the second column is input to the vt3k operation.
3. If no matching name is found in the /vt3k.conf file or the mapping
file does not exist (the default case), the truncated hostname is input
to the vt3k operation. This case assumes that the name identifies a
node in the same NS domain as the management server, since a
fully-qualified NS node name is missing.
You can configure the vt3k.conf file at any time; you do not have to exit
the ITO GUI or restart any ITO services.
Chapter 3
File Tree Layouts on the Managed-Node Platforms
File Tree Layout on MPE/iX Managed Nodes
129