HP TCP/IP Services for OpenVMS Version 5.6

HP TCP/IP Services for OpenVMS Version 5.6 SPD 46.46.21
The main benefit of NFS Version 3 is increased max-
imum file size—up to 1 terabyte for an OpenVMS file
system and up to 4 gigabytes for a container file sys-
tem. Performance gains may result from the improve-
ments to file-size processing and the enhanced write
performance that allows the NFS server to acknowledge
a write operation before the files are actually written to
disk. Afterward, the server’s response to a commit mes-
sage confirms that the data has been written to disk.
The NFS server supports communication over both TCP
and UDP. NFS over TCP offers better support for file
access over wide area links than UDP. The NFS client
is limited to UDP only.
The NFS server and client support OpenVMS Extended
File Specifications, including long file names, deep di-
rectories, and extended character sets on ODS-5 file
structures.
Mail Services
• Secure IMAP (SSL support)
• Secure POP (SSL support)
With the Simple Mail Transfer Protocol (SMTP),
OpenVMS users can send and receive electronic
mail to and from local and remote hosts. The
TCP/IP Services for OpenVMS implementation of SMTP
uses the OpenVMS Mail facility, which automatically
recognizes an SMTP host address in the format
[e-mail]. SMTP provides support for SFF
(Send From File) and outbound alias specification.
The following mail systems work with SMTP, providing
reliable, server-based mail repositories for clients:
• Post Office Protocol (POP) server
• IMAP Mail server (Alpha systems only)
Note: Secure IMAP and Secure POP require the use
of the HP SSL for OpenVMS software.
Network Services
New Features:
• BIND 9 Resolver
• DNS/BIND V9.3 Server
• NTP Security Update (SSL)
With the following TCP/IP Services for OpenVMS man-
agement components, network and system managers
can provide consistent, reliable, and efficient services
to their users with minimal interruption:
• Simple Network Management Protocol (SNMP) Ver-
sion 2 includes a master agent and subagents that
allow the OpenVMS system to be managed by a
management station on the network. SNMP sup-
ports IPv4 only.
• Network Time Protocol (NTP) Version 4 provides a
means to synchronize time and coordinate time dis-
tribution throughout a TCP/IP network. NTP provides
accurate and dependable timekeeping for OpenVMS
hosts on TCP/IP networks.
• Berkeley Internet Name Domain (BIND) is a dis-
tributed database system that distributes and man-
ages host information so that hosts do not need to
locally manage the address of every other host on the
internet. The BIND 9 server is based on the Internet
Software Consortium’s (ISC) BIND 9.2.1 implemen-
tation. It includes dynamic updates and BIND server
cluster failover, which allows multiple BIND master
servers to share a common database, thus provid-
ing both redundancy and a failover mechanism when
one of the servers becomes unavailable.
The BIND server is based on the ICS’s BIND 9.2.1 im-
plementation, and supports IPv4 and IPv6.
The BIND resolver is based on the BIND 8.1.2 imple-
mentation. The BIND resolver supports communication
over IPv4 only, but it is capable of querying for IPv6
addresses (AAAA records).
The BIND server and the BIND resolver are available
on OpenVMS I64 and OpenVMS Alpha systems.
• Load broker supplies cluster load balancing, round-
robin scheduling, and automatic failover.
• Metric server calculates and reports the DNS load on
the local host. It includes dynamic configuration of
logical names, which can be defined for CPU rating,
compute interval, and debug level, as well as support
for multihomed systems to allow load balancing of
incoming traffic across multiple IP addresses.
• Portmapper allocates ports so that system managers
do not need to preconfigure client applications with
port numbers for each service.
• Auxiliary server process is the TCP/IP Services for
OpenVMS implementation of the UNIX internet dae-
mon (inetd). The auxiliary server greatly simplifies
application writing, manages overhead by reducing
simultaneous server processes, provides system se-
curity through authentication of service requests, and
supports event and error logging.
• Dynamic Host Configuration Protocol (DHCP) is a su-
perset of the Bootstrap Protocol (BOOTP). In addi-
tion to BOOTP functionality (answering bootstrap re-
quests), DHCP offers robust configuration services,
including IP address, subnet masks, and default
gateways. The DHCP server can be configured to
support BOOTP clients. If BOOTP is enabled with-
out DHCP, DHCP functionality is not available.
4