If the FTP service does not work after it has been started, switch to passive mode with the following command:

FTP> SET PASSIVE ON
Passive is ON

In passive mode, the FTP client always initiates a data connection. This is useful in virtual machine environments when there is network address translation (NAT) in your network.

To run this command automatically when you invoke FTP, put it into SYS$LOGIN:FTPINIT.INI. For the full description of the SET PASSIVE command, refer to the VSI TCP/IP Services for OpenVMS User’s Guide.

You cannot run the DHCP and the failSAFE IP client on the same NIC on VSI TCP/IP Services V6.0. If a customer is running the DHCP client on a NIC, then failSAFE IP should not be configured on this NIC, because since the address assignment is controlled by DHCP, there is always the possibility that the address could change. If a customer needs to run the DHCP client and provide a failover mechanism, they should configure the NIC in a LAN failover set.

NTPDATE is no longer supported and will be removed from an upcoming release of VSI TCP/IP Services V6.0. To perform the equivalent of NTPDATE, run NTPD making use of the -q and "-G" options.

$ ntpd :== $tcpip$ntp 
$ ntpd "-G" -q
ntp.exe[538969120]: ntpd 4.2.8p15@1.3728 Fri Sep 22 07:00:58 UTC 2020 (2): Starting
ntp.exe[538969120]: Command line: tbd$dka200:[sys0.syscommon.][sysexe]tcpip$ntp.exe -G -q -4
ntp.exe[538969120]: ----------------------------------------------------
ntp.exe[538969120]: ntp-4 is maintained by Network Time Foundation,
ntp.exe[538969120]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
ntp.exe[538969120]: corporation.  Support and training for ntp-4 are
ntp.exe[538969120]: available at https://www.nwtime.org/support
ntp.exe[538969120]: ----------------------------------------------------
ntp.exe[538969120]: proto: precision = 1000.000 usec (-10)
ntp.exe[538969120]: proto: fuzz beneath 0.710 usec
ntp.exe[538969120]: basedate set to 2022-05-21
ntp.exe[538969120]: gps base set to 2022-05-22 (week 2211)
ntp.exe[538969120]: Listen and drop on 0 v4wildcard 0.0.0.0:123
ntp.exe[538969120]: Listen normally on 1 LO0 127.0.0.1:123
ntp.exe[538969120]: Listen normally on 2 WE0 10.10.116.182:123
ntp.exe[538969120]: Listening on routing socket on fd #4 for interface updates
ntp.exe[538969120]: ntpd: time set -50.590756 s
ntpd: time set -50.590756s
$

The following lines in the TCPIP$BIND_CONF.TEMPLATE_FORWARD template file set up the forwarders' addresses and the DNSSEC validation:

//Specifies the IP addresses to be used for forwarding.
//The default is the empty list (no forwarding).
forwarders {
    8.8.8.8;
    8.8.4.4;
};
 
dnssec-validation auto; //Enable DNSSEC validation.
                        //Note dnssec-enable also needs to be set to
                        //yes to be effective. The default is yes.

However, if forwarders are changed to DNS servers that do not support DNSSEC or have it disabled, DNS lookup replies will be discarded when the DNSSEC validation fails.

dnssec-validation auto

When DHCP is enabled for an interface, the SYS$SYSTEM:TCPIP$DHCLIENT-SCRIPT.COM command procedure is called for various DHCP events. Previously, some of those events were not accompanied by notifications in log files or OPCOM messages (specifically, the expiration of a lease, failure to contact a DHCP server, failure to obtain an address from a DHCP server, and user-issued commands to release the address or stop the DHCP client process). Starting from the current release, all that information is saved in the log files in the [TCPIP$DHCP] directory, and the OPCOM messages are saved in SYS$MANAGER:OPERATOR.LOG.

Previously, when a lease expired or was relinquished on user command, the IP address for the interface would not be deleted. This issue has been addressed in the current release.

An issue has been discovered in the scheduling mechanism used by the NTP service to defer work in the event of certain conditions (generally, configuration errors). This issue has been corrected.

VSI OpenVMS V9.2-2 shipped with a version of TCPIP$CLUSTER.TEMPLATE with incorrect record attributes. If a version of TCPIP$CLUSTER.TEMPLATE with incorrect attributes is detected by TCPIP$CONFIG, it will create a corrected version of this file.