patch details: DEC-AXPVMS-TCPIP_ECO-V0504-152-4 The most recent patch is : DEC-AXPVMS-TCPIP_ECO-V0504-152-4 **************************** ECO SUMMARY INFORMATION **************************** Release Date: 16-JUN-2004 Kit Name: DEC-AXPVMS-TCPIP_ECO-V0504-152-4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2, V7.3-1, V7.3 Approximate Kit Size: 72096 blocks Installation Rating: INSTALL_2 Reboot Required: Yes Superseded Kits: None. Mandatory Kit Dependencies: Compaq TCP/IP Services for OpenVMS Alpha 5.4 Optional Kit Dependencies: None. DEC-AXPVMS-TCPIP_ECO-V0504-152-4.PCSI-DCX_AXPEXE Checksum: 2056583751 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: TCPIPALP_E02A54 OLD PRODUCT: Compaq TCP/IP Services for OpenVMS Alpha 5.4 NEW PRODUCT: HP TCP/IP Services for OpenVMS Alpha 5.4 ECO 2 1 KIT NAME: DEC-AXPVMS-TCPIP_ECO-V0504-152-4 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: A reboot is necessary after installation of this kit. 2.3 New functionality or new hardware support provided: No. 3 FILES PATCHED OR REPLACED: File Name --------- [SYS$LDR]TCPIP$BGDRIVER.EXE [SYS$LDR]TCPIP$BGDRIVER_PERF.EXE [SYS$LDR]TCPIP$INETDRIVER.EXE [SYS$LDR]TCPIP$INTERNET_SERVICES.EXE [SYS$LDR]TCPIP$INTERNET_SERVICES_PERF.EXE [SYS$LDR]TCPIP$NFS_SERVICES.EXE [SYS$LDR]TCPIP$PWIPDRIVER.EXE [SYS$LDR]TCPIP$TNDRIVER.EXE [SYS$LDR]TCPIP$TNDRIVER_PERF.EXE [SYS$STARTUP]TCPIP$SHUTDOWN.COM [SYS$STARTUP]TCPIP$STARTUP.COM [SYSEXE]HOSTS.DAT [SYSEXE]NETWORKS.DAT [SYSEXE]PROTOCOLS.DAT [SYSEXE]RESOLV.CONF [SYSEXE]TCPIP$BGDRIVER.STB [SYSEXE]TCPIP$BGDRIVER_PERF.STB [SYSEXE]TCPIP$BIND_RUN.COM [SYSEXE]TCPIP$BIND_SERVER.EXE [SYSEXE]TCPIP$BOOTP_RUN.COM [SYSEXE]TCPIP$CONVERT.COM [SYSEXE]TCPIP$CONVERT.FDL [SYSEXE]TCPIP$DHCP_CLIENT_RUN.COM [SYSEXE]TCPIP$DHCP_RUN.COM [SYSEXE]TCPIP$FAILSAFE.EXE [SYSEXE]TCPIP$FAILSAFE_RUN.COM [SYSEXE]TCPIP$FINGER_SRVR_RUN.COM [SYSEXE]TCPIP$FTP_CHILD.EXE [SYSEXE]TCPIP$FTP_CLIENT.EXE [SYSEXE]TCPIP$FTP_RUN.COM [SYSEXE]TCPIP$FTP_SERVER.COM [SYSEXE]TCPIP$FTP_SERVER.EXE [SYSEXE]TCPIP$IFCONFIG.EXE [SYSEXE]TCPIP$IMAP_RUN.COM [SYSEXE]TCPIP$INETACP.EXE [SYSEXE]TCPIP$INETACP.STB [SYSEXE]TCPIP$INETACP_PERF.EXE [SYSEXE]TCPIP$INETACP_PERF.STB [SYSEXE]TCPIP$INETDRIVER.STB [SYSEXE]TCPIP$INETDRIVERSTOP.EXE [SYSEXE]TCPIP$INTERNET_SERVICES.STB [SYSEXE]TCPIP$INTERNET_SERVICES_PERF.STB [SYSEXE]TCPIP$IP6RTRD_RUN.COM [SYSEXE]TCPIP$IP6_TESTADDR.EXE [SYSEXE]TCPIP$IPTUNNEL.EXE [SYSEXE]TCPIP$LBROKER_RUN.COM [SYSEXE]TCPIP$LOCKD_RUN.COM [SYSEXE]TCPIP$LPD_RCV.EXE [SYSEXE]TCPIP$LPD_RECV_RUN.COM [SYSEXE]TCPIP$LPD_SMB.EXE [SYSEXE]TCPIP$LPD_UTILITIES.EXE [SYSEXE]TCPIP$LPQ.EXE [SYSEXE]TCPIP$LPRM.EXE [SYSEXE]TCPIP$LPRSETUP.EXE [SYSEXE]TCPIP$METRIC_RUN.COM [SYSEXE]TCPIP$MOUNTD.EXE [SYSEXE]TCPIP$MOUNTD_RUN.COM [SYSEXE]TCPIP$ND6HOST_RUN.COM [SYSEXE]TCPIP$NETSTAT.EXE [SYSEXE]TCPIP$NET_GLOBALS.STB [SYSEXE]TCPIP$NET_GLOBALS_PERF.STB [SYSEXE]TCPIP$NFSSTAT.EXE [SYSEXE]TCPIP$NFS_GLOBALS.STB [SYSEXE]TCPIP$NFS_RUN.COM [SYSEXE]TCPIP$NFS_SERVER.EXE [SYSEXE]TCPIP$NFS_SERVICES.STB [SYSEXE]TCPIP$NTP-GENKEYS.EXE [SYSEXE]TCPIP$NTP.EXE [SYSEXE]TCPIP$NTPDATE.EXE [SYSEXE]TCPIP$NTPDC.EXE [SYSEXE]TCPIP$NTPQ.EXE [SYSEXE]TCPIP$NTPTRACE.EXE [SYSEXE]TCPIP$NTP_RES_CHILD.EXE [SYSEXE]TCPIP$NTP_RUN.COM [SYSEXE]TCPIP$PCNFSD_RUN.COM [SYSEXE]TCPIP$PING.EXE [SYSEXE]TCPIP$POP_RUN.COM [SYSEXE]TCPIP$PORTM_RUN.COM [SYSEXE]TCPIP$PWIPACP.EXE [SYSEXE]TCPIP$PWIPACP.STB [SYSEXE]TCPIP$PWIPDRIVER.STB [SYSEXE]TCPIP$PWIPSHUT.EXE [SYSEXE]TCPIP$PWIP_GLOBALS.STB [SYSEXE]TCPIP$REXEC_RUN.COM [SYSEXE]TCPIP$ROUTE.EXE [SYSEXE]TCPIP$RSH_RUN.COM [SYSEXE]TCPIP$SMTP_RECEIVER.EXE [SYSEXE]TCPIP$SMTP_RECV_RUN.COM [SYSEXE]TCPIP$SMTP_SFF.EXE [SYSEXE]TCPIP$SMTP_SYMBIONT.EXE [SYSEXE]TCPIP$SNMP_RUN.COM [SYSEXE]TCPIP$SSH_RCMD.COM [SYSEXE]TCPIP$SSH_RUN.COM [SYSEXE]TCPIP$SSH_SCP2.EXE [SYSEXE]TCPIP$SSH_SFTP-SERVER2.EXE [SYSEXE]TCPIP$SSH_SFTP2.EXE [SYSEXE]TCPIP$SSH_SSH-ADD2.EXE [SYSEXE]TCPIP$SSH_SSH-AGENT2.EXE [SYSEXE]TCPIP$SSH_SSH-KEYGEN2.EXE [SYSEXE]TCPIP$SSH_SSH-SIGNER2.EXE [SYSEXE]TCPIP$SSH_SSH2.EXE [SYSEXE]TCPIP$SSH_SSHD2.EXE [SYSEXE]TCPIP$STATD_RUN.COM [SYSEXE]TCPIP$TCPDUMP.EXE [SYSEXE]TCPIP$TELNET.EXE [SYSEXE]TCPIP$TELNETSYM.EXE [SYSEXE]TCPIP$TELNET_RUN.COM [SYSEXE]TCPIP$TELNET_SERVER.EXE [SYSEXE]TCPIP$TFTP_RUN.COM [SYSEXE]TCPIP$TNDRIVER.STB [SYSEXE]TCPIP$TNDRIVER_PERF.STB [SYSEXE]TCPIP$TN_GLOBALS.STB [SYSEXE]TCPIP$TRACEROUTE.EXE [SYSEXE]TCPIP$TTCP.EXE [SYSEXE]TCPIP$UCP.EXE [SYSEXE]TCPIP$UUDECODE.EXE [SYSEXE]TCPIP$UUENCODE.EXE [SYSEXE]TCPIP$VERSIONS.EXE [SYSEXE]TCPIP$XDM_RUN.COM [SYSEXE]TCPIP$XDM_XSESSION.COM [SYSEXE]UCX$LPD_SMB.EXE [SYSEXE]UCX$TELNETSYM.EXE [SYSEXE]UCX$UCP.EXE [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]IPV6.ARPA [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]IPV6.DB [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]IPV6.INT [SYSHLP.EXAMPLES.TCPIP.IPV6.BIND]TCPIP$BIND.CONF_IPV6 [SYSHLP.EXAMPLES.TCPIP]TCPIP$PROXY_RELOAD.COM [SYSHLP.EXAMPLES.TCPIP]TCPIP$RESTART_SMTPQ.COM [SYSHLP.EXAMPLES.TCPIP]TN3270DEF.MAR [SYSHLP]TCPIP$FTP_HELP.HLB [SYSHLP]TCPIP$TELNET_HELP.HLB [SYSHLP]TCPIP$UCP_HELP.HLB [SYSHLP]TCPIP.MSGHLP$DATA [SYSHLP]TCPIP54ECO02.RELEASE_NOTES [SYSLIB]PWIP$SDA.EXE [SYSLIB]TCPIP$ACCESS_SHR.EXE [SYSLIB]TCPIP$CFS_SHR.EXE [SYSLIB]TCPIP$INETDEF.ADA [SYSLIB]TCPIP$INETDEF.BAS [SYSLIB]TCPIP$INETDEF.FOR [SYSLIB]TCPIP$INETDEF.H [SYSLIB]TCPIP$INETDEF.MAR [SYSLIB]TCPIP$INETDEF.PAS [SYSLIB]TCPIP$INETDEF.PLI [SYSLIB]TCPIP$INETDEF.R32 [SYSLIB]TCPIP$IPC_SHR.EXE [SYSLIB]TCPIP$LPD_SHR.EXE [SYSLIB]TCPIP$PPPD_CALLOUT.EXE [SYSLIB]TCPIP$SMTP_MAILSHR.EXE [SYSLIB]TCPIP$SMTP_PARSESHR_TV.EXE [SYSLIB]TCPIP$TEMPLATES.TLB [SYSLIB]TNIODEF.ADA [SYSLIB]TNIODEF.BAS [SYSLIB]TNIODEF.FOR [SYSLIB]TNIODEF.H [SYSLIB]TNIODEF.MAR [SYSLIB]TNIODEF.PAS [SYSLIB]TNIODEF.PLI [SYSLIB]TNIODEF.R32 [SYSLIB]UCX$ACCESS_SHR.EXE [SYSLIB]UCX$INETDEF.ADA [SYSLIB]UCX$INETDEF.BAS [SYSLIB]UCX$INETDEF.FOR [SYSLIB]UCX$INETDEF.H [SYSLIB]UCX$INETDEF.MAR [SYSLIB]UCX$INETDEF.PAS [SYSLIB]UCX$INETDEF.PLI [SYSLIB]UCX$INETDEF.R32 [SYSLIB]UCX$IPC_SHR.EXE [SYSMGR]SYS$NET_SERVICES_TCPIP.COM [SYSMGR]TCPIP$BIND_SHUTDOWN.COM [SYSMGR]TCPIP$BIND_STARTUP.COM [SYSMGR]TCPIP$BOOTP_SHUTDOWN.COM [SYSMGR]TCPIP$BOOTP_STARTUP.COM [SYSMGR]TCPIP$CALLBACKS.COM [SYSMGR]TCPIP$CONFIG.COM [SYSMGR]TCPIP$CUSTOMER_SERVICE_SHUTDOWN.COM [SYSMGR]TCPIP$CUSTOMER_SERVICE_STARTUP.COM [SYSMGR]TCPIP$DEFINE_COMMANDS.COM [SYSMGR]TCPIP$DHCP_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$DHCP_CLIENT_STARTUP.COM [SYSMGR]TCPIP$DHCP_SHUTDOWN.COM [SYSMGR]TCPIP$DHCP_STARTUP.COM [SYSMGR]TCPIP$FAILSAFE_SHUTDOWN.COM [SYSMGR]TCPIP$FAILSAFE_STARTUP.COM [SYSMGR]TCPIP$FINGER_SHUTDOWN.COM [SYSMGR]TCPIP$FINGER_STARTUP.COM [SYSMGR]TCPIP$FTP_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$FTP_CLIENT_STARTUP.COM [SYSMGR]TCPIP$FTP_SHUTDOWN.COM [SYSMGR]TCPIP$FTP_STARTUP.COM [SYSMGR]TCPIP$IMAP_SHUTDOWN.COM [SYSMGR]TCPIP$IMAP_STARTUP.COM [SYSMGR]TCPIP$INET_DRIVER_SHUTDOWN.COM [SYSMGR]TCPIP$INET_DRIVER_STARTUP.COM [SYSMGR]TCPIP$INET_SHUTDOWN.COM [SYSMGR]TCPIP$INET_STARTUP.COM [SYSMGR]TCPIP$IP6_SETUP.COM [SYSMGR]TCPIP$LBROKER_SHUTDOWN.COM [SYSMGR]TCPIP$LBROKER_STARTUP.COM [SYSMGR]TCPIP$LOCKD_SHUTDOWN.COM [SYSMGR]TCPIP$LOCKD_STARTUP.COM [SYSMGR]TCPIP$LPD_SHUTDOWN.COM [SYSMGR]TCPIP$LPD_STARTUP.COM [SYSMGR]TCPIP$METRIC_SHUTDOWN.COM [SYSMGR]TCPIP$METRIC_STARTUP.COM [SYSMGR]TCPIP$NFS_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$NFS_CLIENT_STARTUP.COM [SYSMGR]TCPIP$NFS_SHUTDOWN.COM [SYSMGR]TCPIP$NFS_STARTUP.COM [SYSMGR]TCPIP$NTP_SHUTDOWN.COM [SYSMGR]TCPIP$NTP_STARTUP.COM [SYSMGR]TCPIP$PCNFS_SHUTDOWN.COM [SYSMGR]TCPIP$PCNFS_STARTUP.COM [SYSMGR]TCPIP$POP_SHUTDOWN.COM [SYSMGR]TCPIP$POP_STARTUP.COM [SYSMGR]TCPIP$PORTMAPPER_SHUTDOWN.COM [SYSMGR]TCPIP$PORTMAPPER_STARTUP.COM [SYSMGR]TCPIP$PROXY_SHUTDOWN.COM [SYSMGR]TCPIP$PROXY_STARTUP.COM [SYSMGR]TCPIP$PWIP_DRIVER_SHUTDOWN.COM [SYSMGR]TCPIP$PWIP_DRIVER_STARTUP.COM [SYSMGR]TCPIP$REXEC_SHUTDOWN.COM [SYSMGR]TCPIP$REXEC_STARTUP.COM [SYSMGR]TCPIP$RLOGIN_SHUTDOWN.COM [SYSMGR]TCPIP$RLOGIN_STARTUP.COM [SYSMGR]TCPIP$RMT_CHECK_ACCESS.COM [SYSMGR]TCPIP$RMT_SHUTDOWN.COM [SYSMGR]TCPIP$RMT_STARTUP.COM [SYSMGR]TCPIP$RSH_SHUTDOWN.COM [SYSMGR]TCPIP$RSH_STARTUP.COM [SYSMGR]TCPIP$SMTP_SHUTDOWN.COM [SYSMGR]TCPIP$SMTP_STARTUP.COM [SYSMGR]TCPIP$SNMP_SHUTDOWN.COM [SYSMGR]TCPIP$SNMP_STARTUP.COM [SYSMGR]TCPIP$SSH_CLIENT_SHUTDOWN.COM [SYSMGR]TCPIP$SSH_CLIENT_STARTUP.COM [SYSMGR]TCPIP$SSH_SHUTDOWN.COM [SYSMGR]TCPIP$SSH_STARTUP.COM [SYSMGR]TCPIP$STATD_SHUTDOWN.COM [SYSMGR]TCPIP$STATD_STARTUP.COM [SYSMGR]TCPIP$SYMBOLS.COM [SYSMGR]TCPIP$TELNETSYM_SHUTDOWN.COM [SYSMGR]TCPIP$TELNETSYM_STARTUP.COM [SYSMGR]TCPIP$TELNET_SHUTDOWN.COM [SYSMGR]TCPIP$TELNET_STARTUP.COM [SYSMGR]TCPIP$TFTP_SHUTDOWN.COM [SYSMGR]TCPIP$TFTP_STARTUP.COM [SYSMGR]TCPIP$UCP_SHUTDOWN.COM [SYSMGR]TCPIP$UCP_STARTUP.COM [SYSMGR]TCPIP$V51_CONVERSION.COM [SYSMGR]TCPIP$XDM_SHUTDOWN.COM [SYSMGR]TCPIP$XDM_STARTUP.COM [SYSMGR]UCX$CONFIG.COM [SYSMGR]UCX$STARTUP.COM [SYSTEST]TCPIP$IVP.COM [SYSUPD]TCPIP$CLEANUP.COM [SYSUPD]TCPIP$PCSI_POST_INSTALL.COM [TCPIP$LIB]TCPIP$LIB.OLB [SYSUPD]TCPIP$PCSI_POST_INSTALL.COM 4 PROBLEMS ADDRESSED IN THIS KIT Release Notes for HP TCP/IP Services for OpenVMS V5.4 Update ECO 2 ________________________________________________________________ © 2004 Hewlett-Packard Development Company, L.P. UNIX[R] is a registered trademark of The Open Group. Microsoft[R] is a US registered trademark of Microsoft Corporation. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM. ------------------------------------------------------------------------------- PREVIOUSLY UNDOCUMENTED BEHAVIOR: ------------------------------------------------------------------------------- -------------------------------------------------------------- 1: Dependency for PPP on OpenVMS 7.2-2 and above -------------------------------------------------------------- IPCP negotiation of IP address between PC client and OpenVMS PPP server fails to assign client an IP address. Many problems were fixed in the OpenVMS PPPDRIVER. All customers running PPP on OpenVMS versions 7.3 and higher must install a patch for PPPDRIVER. Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_PPPD-V0200 -------------------------------------------------------------- 2: SMTP dependency on OpenVMS Kits -------------------------------------------------------------- Problem: When you compose a mail message in OpenVMS mail and enter an SMTP address at the To: prompt and at the Cc: prompt, the address originally entered at the Cc: prompt is not put into a Cc: RFC header in the SMTP message but is instead put into the To: RFC header. Dependencies: For this fix to be effective the following OpenVMS kits must be installed. Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_MAIL-V0100 -------------------------------------------------------------- 3: PTRs 30-10-194/30-10-174 IMAP Dependency on OpenVMS Kits -------------------------------------------------------------- The underlying OpenVMS problem has been fixed in OpenVMS versions 7.3-1 and later. For users running earlier versions of OpenVMS, the following two steps must be performed to enable IMAP upload support: 1) Install the following patch if running on VMS V7.3: Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_SYSLOA-V0300 NOTE: This patch need only be installed on the system or systems that are running the IMAP server. Cluster nodes that are not running the IMAP server are not required to install the patch. 2) Add this line to your TCPIP$IMAP.CONF file: Upload-Supported: TRUE WARNING: Do not set the Upload-Supported configuration parameter on an unpatched system running an OpenVMS version prior to 7.3-1 -------------------------------------------------------------- 4: Inability of New IMAP Clients to Connect -------------------------------------------------------------- Problem: Inability of new IMAP clients to connect and of some connected clients to open additional folders. Problem detail: The IMAP server supports an application-specific limit on the number of connections an IMAP server process can handle before it forces the kernel to create a new IMAP server process. This value is set in the TCPIP$IMAP.CONF file to 25 (Max-Connections:25). The service limit default value (currently 16) should not be less than the application limit of 25. In fact it should be set much higher, or a server hang can result. As an example, Netscape uses five connections. Therefore, any more than 3 concurrently attached IMAP Netscape clients would exhaust the default 16-connection limit. Workaround: 1) Update the IMAP service limit from 16 to 1600: $ tcpip set service imap/limit=1600 $ tcpip show service imap/full/perm 2) Stop IMAP: $ @sys$startup:TCPIP$IMAP_SHUTDOWN 3) Wait until there are no more IMAP processes left. Keep entering the following command until all IMAP processes are gone. $ SHOW SYSTEM/PROCESS=*IMAP* 4) Start IMAP: $ @sys$startup:TCPIP$IMAP_STARTUP -------------------------------------------------------------- 5: PTR 75-86-140 nslookup via TELNET Fails on V7.3-1 -------------------------------------------------------------- This problem was reported on OpenVMS V7.3-1 with TCP/IP V5.3. The symptom is that nslookup in interactive mode failed when connected via telnet. Problem detail: For a system that is, for example, accessed via TELNET (rather than SET HOST) that also has set the SYSGEN parameter MAXBUF to greater than 32K, if a C program is executed that uses a C runtime call (such as getc or gets) to read data from the terminal, this problem can occur. The C program may return a generic user I/O error message rather than the specific errors returned by RMS. (The TT driver returns an SS$_IVBUFLEN error. RMS returns RMS-F-QIO in the RAB$L_STS, and SYS-F-IVBUFLEN in the RAB$L_STV to the caller.) Workaround: Reduce the MAXBUF SYSGEN parameter to 32K. This is a dynamic parameter so no reboot is required. After the remedial kit is installed, MAXBUF can be reset to some higher value. Solution: Install the remedial kit: OpenVMS kit VMS731_RMS-V0100 -------------------------------------------------------------- 6: PTR 70-5-2210 ARP Timeouts Not Tunable over 32767 -------------------------------------------------------------- The ARP timeouts arpkillc, arpkilli, and arprefresh are limited to 32767 seconds. This known problem was introduced in V5.3 SSB. -------------------------------------------------------------- 7: PTRs 70-5-2191 and 70-5-2194 SMTP Mail Hang -------------------------------------------------------------- 70-5-2191/CFS-96560: TCP/IP V5.3 ECO1 incoming SMTP mail job stalls during processing. This is because mail hangs on $BRKTHRU, which is called from MAILSHRP with VMS73-SYS patch. 70-5-2194/CFS-96677: SMTP mail hangs with AXPVMS VMS73_SYS V5.0. Solution: Alpha OpenVMS kit (minimum version) ----- ----------------------------- 7.3 VMS73_SYS-V0600 7.3-1 VMS731_SYS-V0300 -------------------------------------------------------------- 8: PTR 70-5-2259 NFS Client Restriction -------------------------------------------------------------- The MOUNT command used by the NFS client is restricted to 255 characters in total length. Depending on where the 255 character limit is reached in the command line, the command might generate an error message. Abbreviate some of the parameter names until the total length is less than or equal to 255 characters. -------------------------------------------------------------- 9: Changes to KERNEL parameter defaults -------------------------------------------------------------- The following sysconfig default settings were changed in previous releases but not documented in the V5.4 release notes: TCP/IP V5.1 changed the defaults that affect the ephemeral (non-privileged) port numbers assigned to sockets. The changes were made to match IANA recommendations. The following changes were carried over to V5.4: ipport_userreserved_min (1024 -> 49152) ipport_userreserved (5000 -> 65535) V5.4 changed the following default setting to comply with RFC 1122. It increases the initial keepalive probe from 75 seconds to 2 hours. tcp_keepidle (150 -> 14400) -------------------------------------------------------------- 10: SMTP receiver doesn't check recipient deliverability -------------------------------------------------------------- Problem: The SMTP receiver does not check to see if the recipient email address in the RCPT TO SMTP protocol command is deliverable (for example that the user account exists on the system). This check is instead deferred to the processing of the mail message in the SMTP queue by the SMTP symbiont process. By this time, the host has taken responsibility for the message and, if there is a problem delivering the message, must bounce the message itself. This behavior is more problematic when the system receives SPAM. SPAM arrives on the host for a non-existent user and is bounced by your host's symbiont process to the email address in the SPAM's Return-Path: header. The SPAM's Return-Path: header contains an invalid email address, so the bounced SPAM is in turn bounced back to your host's POSTMASTER account. The POSTMASTER account's mail is forwarded to the SYSTEM account, which means that the SYSTEM user must constantly separate these doubly bounced SPAMs from their valid email. Solution: The SMTP receiver has been changed to check to see if the recipient email address in the RCPT TO SMTP protocol command is deliverable. This solves the problem by not letting the SPAM for the unknown user onto the host in the first place. A configuration option now exists to turn this new feature on and off. The option is called Symbiont-Checks-Deliverability and is entered in the SMTP.CONFIG SMTP configuration file. Setting this option to TRUE preserves the old behavior - where the receiver does not check the deliverability of RCPT TO recipients, deferring to the symbiont. Setting Symbiont-Checks-Deliverability to FALSE turns on the new behavior, telling the receiver to check the deliverability of RCPT TO recipients itself. To preserve existing behavior, this option is set by default to TRUE for TCP/IP Services Version 5.4. For future versions it will default to FALSE. -------------------------------------------------------------- 11: CERT updates for OpenVMS TCP/IP Service V5.4 SSH: -------------------------------------------------------------- 1. SSRT3629A/B: Code checked; not vulnerable 2. CERT CA-2003-24: OpenSSH only; not vulnerable 3. CERT CA-2002-36: The worst case effect of the vulnerability is a denial of service (DoS) for a single connection of one of these types: - the server process that is handling a connection from a malicious client - the client process that is connecting to a malicious server In either case it is not possible for a malicious remote host to gain access to the OpenVMS host (e.g., to execute arbitrary code). The ability of an OpenVMS server to receive a new connection is not affected. 4. CERT CA-2001-35: Affects SSH version 1 only, which is not supported; not vulnerable 5. CERT CA-1999-15: RSAREF2 library not used; not vulnerable 6. CERT CA-1998-03: Old versions (1.2.17 through 1.2.21) referenced, current release based on much newer code; not vulnerable -------------------------------------------------------------- 12: IPv6 documentation changes (TCPIP_BUGS Note 3040): -------------------------------------------------------------- 1.a. Guide to IPv6, Section 2.5.1 Run TCPIP$IP6_SETUP to Configure Host Update IPv6 host configuration procedure as shown here: Configuring an IPv6 Host To configure your system as an IPv6 host, do the following: 1. Invoke the TCPIP$IP6_SETUP configuration procedure by entering the following command: $ @SYS$MANAGER:TCPIP$IP6_SETUP 2. Choose to configure the system as an IPv6 host by taking the default to the following prompt (press Return or enter NO): Configure this system as an IPv6 router? [NO]: 3. Indicate whether you want to configure a 6to4 interface by responding to the following prompt: Configure a 6to4 interface? [NO]: A 6to4 interface is needed if this host is connected to an IPv4-only network and needs to communicate with other 6to4 or native IPv6 sites. If this system is a host within a 6to4 site, do not create a 6to4 interface; a 6to4 address is automatically configured on this system using standard IPv6 mechanisms. If you do not want to configure a 6to4 interface, press Return. The configuration procedure goes to step 8. If you want to configure a 6to4 interface, enter YES. The configuration procedure then displays the 6to4 tunnel interface, as shown here: The 6to4 tunnel is: TN1 You will be prompted to enter information about the 6to4 interface in subsequent steps. 4. Enter this host's IPv4 address in response to the following prompt: Enter this node's IPv4 address to use when generating your site's 6to4 prefix: Enter the IPv4 address in dotted-decimal format (d.d.d.d). The configuration procedure automatically generates a 6to4 site prefix based on the IPv4 address entered, and displays the prefix as shown here: Your 6to4 site prefix is: 2002:x:x::/48 5. Enter the address prefix for the 6to4 tunnel in response to the following prompt: Enter an address prefix to use on interface TN1 [2002:x:x::/64]: You can accept the IPv6 address prefix generated in the previous step by taking the default. ________________________ Note ________________________ The high-order 48 bits of the 6to4 address prefix must be the same as your 6to4 site prefix. ______________________________________________________ 6. Indicate whether you want to configure a 6to4 relay router: Configure a 6to4 relay router? [NO]: A relay router is needed to connect your system to native IPv6 sites. If you do not configure a relay router, your system can connect to other 6to4 sites but not to native IPv6 sites. If you do not want to configure a 6to4 relay router, press Return. The configuration procedure goes to step 8. If you want to configure a 6to4 relay router, enter YES. 7. Specify the address of a relay router: Enter the 6to4 address of a 6to4 relay router [2002:C058:6301::]: The address of the default relay router is displayed. To use the default, press Return. Otherwise, enter the 6to4 unicast address of a 6to4 relay router. 8. For each network interface on your system, the configuration procedure asks whether you want to enable IPv6 on that interface, as shown below, where ddn is the internet interface name, such as WE0: Enable IPv6 on interface ddn? [YES]: If you want to enable IPv6 on this interface, press Return; if you do not, enter NO. If your system has multiple interfaces, the configuration procedure repeats this question for each interface. 9. Indicate whether you want to configure an automatic tunnel by responding to the following prompt: Configure an IPv6 over IPv4 automatic tunnel interface? [NO]: If you do not want to configure an automatic tunnel, press Return; the configuration procedure goes to step 11. If you want to configure an automatic tunnel, enter YES; the configuration procedure displays the automatic tunnel interface as shown here, and then prompts you for the tunnel's address in step 10. The automatic tunnel is: TN0 ________________________ Note ________________________ Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels. ______________________________________________________ 10. Enter the IPv4 address to use when constructing the automatic tunnel's endpoint. Enter this node's IPv4 address to use when creating your automatic tunnel: Enter the IPv4 address in dotted-decimal format (d.d.d.d). 11. Indicate whether you want to create an IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create IPv6 over IPv4 configured tunnels? [NO]: If you want to create an IPv6 over IPv4 configured tunnel, enter YES and press Return. You will be prompted for information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv4 configured tunnel, press Return; the procedure goes to step 16. 12. Enter the tunnel's source IPv4 address in response to the following prompt: Enter the source IPv4 address of tunnel ITn: Enter the tunnel's source IPv4 address in dotted-decimal format (d.d.d.d). 13. Enter the tunnel's destination IPv4 address in response to the following prompt: Enter the destination IPv4 address of tunnel ITn: Enter the tunnel's destination IPv4 address in dotted-decimal format (d.d.d.d). The tunnel's destination address must differ from the source address entered in the previous step. 14. Enter an address prefix to use on the tunnel interface in response to the following prompt: Enter an address prefix to use on interface ITn [DONE]: If a router is not advertising a global address prefix on this tunnel interface, enter a 64-bit address prefix. You can configure multiple address prefixes for this configured tunnel. You will be prompted for additional address prefixes until you enter DONE. If you do not want the host to use an IPv6 address prefix on the tunnel interface, press Return. 15. Indicate whether you want to create another IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv4 configured tunnel? [NO]: If you want to create another IPv6 over IPv4 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 12 through 14 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv4 configured tunnel, press Return. 16. Indicate whether you want to create an IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create IPv6 over IPv6 configured tunnels? [NO]: If you want to create an IPv6 over IPv6 configured tunnel, enter YES and press Return. You will be prompted for information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv6 configured tunnel, press Return; the configuration procedure goes to step 21. 17. Enter the tunnel's source IPv6 address in response to the following prompt: Enter the source IPv6 address of tunnel ITn: Enter the source IPv6 address of the designated tunnel. 18. Enter the tunnel's destination IPv6 address in response to the following prompt: Enter the destination IPv6 address of tunnel ITn: Enter the destination IPv6 address of the designated tunnel. The tunnel's destination address must differ from the source address entered in the previous step. 19. Enter an address prefix to use on the tunnel interface in response to the following prompt: Enter an address prefix to use on interface ITn [DONE]: If a router is not advertising a global address prefix on this tunnel interface, enter a 64-bit address prefix. You can configure multiple address prefixes for this configured tunnel. You will be prompted for additional address prefixes until you enter DONE. If you do not want the host to use an IPv6 address prefix on the tunnel interface, press Return. 20. Indicate whether you want to create another IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv6 configured tunnel? [NO]: If you want to create another IPv6 over IPv6 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 17 through 19 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv6 configured tunnel, press Return. 21. Indicate whether you want to define manual IPv6 routes by responding to the following prompt: Configure manual IPv6 routes? [NO]: If you want to define a manual IPv6 route to an adjacent router or remote IPv6 network, enter YES; subsequent prompts will ask you for information about the route. Otherwise, press Return; the configuration procedure goes to step 26. 22. Indicate the address prefix of a destination IPv6 network by responding to the following prompt: Enter the destination network address prefix: Enter the address prefix of the destination IPv6 network, or enter DEFAULT for the default route. 23. Enter the name of the interface through which you will send traffic to the remote IPv6 network and press Return. Enter interface to use when forwarding messages: 24. Enter the link-local IPv6 address of the first router in the path to the destination network. This address together with the IPv6 address prefix constitute the static routing table entry. Enter the next node's IPv6 address: If the next node is on the same link as this node or is reachable through a configured tunnel, enter the link- local address. If the next node is reachable through an automatic tunnel, enter the IPv4-compatible IPv6 address. For all other connections, enter the IPv6 address. 25. Indicate whether you want to define another manual IPv6 route to an adjacent router or remote IPv6 network by responding to the following prompt: Configure another manual IPv6 route? [NO]: If you want to define another manual IPv6 route, enter YES and press Return. The configuration procedure repeats steps 22 through 24 for each additional manual IPv6 route you choose to define. If you do not want to define another manual IPv6 route, press Return. 26. The configuration procedure displays a summary of your new IPv6 host configuration, as shown in the following example: You configured this node as a IPv6 host with the following: Daemons: ND6HOST Dynamic Updates Disabled Interfaces: WE0 Dynamic Address Configuration Enabled TN1 6to4 Tunneling Enabled using 5.6.7.8 Prefix 2002:506:708::/64 Relay Router 2002:90A:B0C:1::1 Manual Routes: 2002::/16 TN1 FE80::5.6.7.8 DEFAULT TN1 2002:90A:B0C:1::1 27. Indicate whether you want to create a new host configuration file based on the choices you have made, by responding to the following prompt: Create new IPv6 network configuration files? [YES]: If you are not satisfied with the configuration, enter NO; the configuration procedure will end immediately without changing the current IPv6 network configuration. If you are satisfied with the configuration, press Return. The configuration procedure creates new host configuration file and then displays the following message: A new IPv6 configuration file, SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT, has been created. The previous configuration file (if any) has been renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD. This new IPv6 network configuration will become active the next time TCP/IP Services for OpenVMS is started. 1.b. Guide to IPv6, Section 2.6.1 Running TCPIP$IP6_SETUP to Configure Router Update IPv6 router configuration procedure as shown here: Configuring an IPv6 Router To configure your system as an IPv6 router, do the following: 1. Invoke the TCPIP$IP6_SETUP configuration procedure by entering the following command: $ @SYS$MANAGER:TCPIP$IP6_SETUP 2. Choose to configure the system as an IPv6 router by entering YES and pressing Return at the following prompt: Configure this system as an IPv6 router? [NO]: 3. Indicate whether you want to configure a 6to4 interface by responding to the following prompt: Configure a 6to4 interface? [NO]: A 6to4 interface is needed to configure a border router. If you do not want to configure a 6to4 interface, press Return. The configuration procedure goes to step 7. If you want to configure a 6to4 interface, enter YES and press Return. The configuration procedure then displays the 6to4 tunnel interface, as shown here: The 6to4 tunnel is: TN1 You will be prompted to enter information about the 6to4 interface in subsequent steps. 4. Enter this router's IPv4 address in response to the following prompt: Enter this node's IPv4 address to use when generating your site's 6to4 prefix: The IPv4 address must be in dotted-decimal format (d.d.d.d). The configuration procedure automatically generates a 6to4 site prefix based on the IPv4 address entered, and displays the prefix as shown here: Your 6to4 site prefix is: 2002:x:x::/48 This site prefix is advertised to hosts on the interfaces attached to the IPv6 site. This address must be a valid, globally unique IPv4 address configured on the router's interface to the IPv4 network. 5. Indicate whether you want this system to function as a 6to4 relay router: Configure a 6to4 relay router? [NO]: If hosts in this border router's 6to4 site need to communicate with native IPv6 sites (IPv6 only), enter YES and press Return. If you do not want the system to function as a 6to4 relay router, press Return. The configuration procedure goes to step 7. 6. Specify the address of a relay router: Enter the 6to4 address of a 6to4 relay router [2002:C058:6301::]: The address of the default relay router is displayed. To use the default, press Return. Otherwise, enter the 6to4 unicast address of a 6to4 relay router. 7. For each network interface on your system, the configuration procedure asks whether you want to enable IPv6 on that interface, as shown below, where ddn is the internet interface name, such as WE0: Enable IPv6 on interface ddn? [YES]: If you want to enable IPv6 on this interface, press Return; if you do not, enter NO. For each interface, the configuration procedure repeats steps 7 through 9. 8. Indicate whether you want the router to run the RIPng protocol on the designated interface by responding to the following prompt: Enable RIPng on interface ddn? [YES]: If you want the router to run the RIPng protocol, press Return; otherwise, enter NO and press Return. The RIPng protocol allows this router to exhange IPv6 routes with other routers. 9. Indicate whether you want the router to advertise an IPv6 address prefix on the designated interface, by responding to the following prompt: Enter an address prefix to advertise on interface ddn [DONE]: If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the interface and press Return. You can configure multiple address prefixes for this interface. You will be prompted for additional address prefixes until you enter DONE. If you do not want the router to advertise an IPv6 address prefix on the designated interface, enter DONE and press Return. 10. Indicate whether you want to configure an automatic tunnel by responding to the following prompt: Configure an IPv6 over IPv4 automatic tunnel interface? [NO]: If you do not want to configure an automatic tunnel, press Return; the configuration procedure goes to step 12. If you want to configure an automatic tunnel, enter YES; the configuration procedure displays the automatic tunnel interface as shown here, and then prompts you for the tunnel's address in step 11. The automatic tunnel is: TN0 ________________________ Note ________________________ Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels. ______________________________________________________ 11. Enter the IPv4 address to use when constructing the automatic tunnel's endpoint. Enter this node's IPv4 address to use when creating your automatic tunnel: Enter the IPv4 address in dotted-decimal format (d.d.d.d). 12. Indicate whether you want to create an IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create IPv6 over IPv4 configured tunnels? [NO]: If you want to create an IPv6 over IPv4 configured tunnel, enter YES and press Return. You will be prompted for information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv4 configured tunnel, press Return; the configuration procedure goes to step 18. 13. Enter the tunnel's source IPv4 address in response to the following prompt: Enter the source IPv4 address of tunnel ITn: Enter the tunnel's source IPv4 address in dotted-decimal format (d.d.d.d). 14. Enter the tunnel's destination IPv4 address in response to the following prompt: Enter the destination IPv4 address of tunnel ITn: Enter the tunnel's destination IPv4 address in dotted-decimal format (d.d.d.d). The tunnel's destination address must differ from the source address entered in the previous step. 15. Indicate whether you want to enable the RIPng protocol on the designated interface by responding to the following prompt: Enable RIPng on interface ITn? [YES]: Press Return if you want to enable the RIPng protocol on this interface; enter NO and press Return if you do not. The RIPng protocol allows this router to exhange IPv6 routes with other routers. 16. Indicate whether you want the router to advertise an IPv6 address prefix on the tunnel interface, by responding to the following prompt: Enter an address prefix to advertise on interface ITn? [DONE]: If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the designated interface and press Return. You can configure multiple address prefixes for this interface. You will be prompted for additional address prefixes until you enter DONE. If you do not want the router to use an IPv6 address prefix on the tunnel interface, enter DONE. 17. Indicate whether you want to create another IPv6 over IPv4 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv4 configured tunnel? [NO]: If you want to create another IPv6 over IPv4 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 13 through 16 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv4 configured tunnel, press Return. 18. Indicate whether you want to create an IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create IPv6 over IPv6 configured tunnels? [NO]: If you want to create an IPv6 over IPv6 configured tunnel, enter YES and press Return. You will be prompted to enter information about this tunnel in subsequent steps. If you do not want to create an IPv6 over IPv6 configured tunnel, press Return; the configuration procedure goes to step 24. 19. Enter the tunnel's source IPv6 address in response to the following prompt: Enter the source IPv6 address of tunnel ITn: Enter the source IPv6 address of the designated tunnel. 20. Enter the tunnel's destination IPv6 address in response to the following prompt: Enter the destination IPv6 address of tunnel ITn: Enter the destination IPv6 address of the designated tunnel. The tunnel's destination address must differ from the source address entered in the previous step. 21. Indicate whether you want to enable the RIPng protocol on the interface by responding to the following prompt: Enable RIPng on interface ITn? [YES]: Press Return if you want to enable the RIPng protocol on this interface; enter NO and press Return if you do not. The RIPng protocol allows this router to exhange IPv6 routes with other routers. 22. Indicate whether you want the router to advertise an IPv6 address prefix on the tunnel interface, by responding to the following prompt: Enter an address prefix to advertise on interface ITn [DONE]: If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the designated interface and press Return. You can configure multiple address prefixes for this interface. You will be prompted for additional address prefixes until you enter DONE. If you do not want the router to use an IPv6 address prefix on the tunnel interface, enter DONE. 23. Indicate whether you want to create another IPv6 over IPv6 configured tunnel, by responding to the following prompt: Create another IPv6 over IPv6 configured tunnel? [NO]: If you want to create another IPv6 over IPv6 configured tunnel, enter YES and press Return. The configuration procedure repeats steps 19 through 22 for each additional configured tunnel you choose to create. If you do not want to create another IPv6 over IPv6 configured tunnel, press Return. 24. Indicate whether you want to define manual IPv6 routes by responding to the following prompt: Configure manual IPv6 routes? [NO]: If you want to define a manual IPv6 route to an adjacent router or remote IPv6 network, enter YES; subsequent prompts will ask you for information about the route. Otherwise, press Return; the configuration procedure goes to step 29. 25. Indicate the address prefix of a destination IPv6 network by responding to the following prompt: Enter the destination network address prefix: Enter the address prefix of the destination IPv6 network, or enter DEFAULT for the default route. 26. Enter the name of the interface through which you will send traffic to the remote IPv6 network and press Return. Enter interface to use when forwarding messages: 27. Enter the link-local IPv6 address of the first router in the path to the destination network. This address together with the IPv6 address prefix constitute the static routing table entry. Enter the next node's IPv6 address: If the next node is on the same link as this node or is reachable through a configured tunnel, enter the link- local address. If the next node is reachable through an automatic tunnel, enter the IPv4-compatible IPv6 address. For all other connections, enter the IPv6 address. 28. Indicate whether you want to define another manual IPv6 route to an adjacent router or remote IPv6 network by responding to the following prompt: Configure another manual IPv6 route? [NO]: If you want to define another manual IPv6 route, enter YES and press Return. The configuration procedure repeats steps 25 through 27 for each additional manual IPv6 route you choose to define. If you do not want to define another manual IPv6 route, press Return. 29. The configuration procedure displays a summary of your new IPv6 router configuration, as shown in the following example: You configured this node as a IPv6 router with the following: Daemons: IP6RTRD Interfaces: WE0 RIP Enabled IT0 RIP Enabled Tunnel Source ::1 Tunnel Destination ::2 Prefix AAAA::/64 Prefix BBBB::/64 TN1 6to4 Tunneling Enabled using 1.2.3.4 Relay Router 2002:C058:6301:: Manual Routes: ::4/64 WE0 ::5 30. Indicate whether you want to create new router configuration files based on the choices you have made, by responding to the following prompt: Create new IPv6 network configuration files? [YES]: If you are not satisfied with the configuration, enter NO; the configuration procedure will end immediately without changing the current IPv6 network configuration. If you are satisfied with the configuration, press Return. The configuration procedure creates new router configuration files and then displays the following message: A new IPv6 configuration file, SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT, has been created. The previous configuration file (if any) has been renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD. A new IPv6 configuration file, SYS$SYSTEM:TCPIP$IP6RTRD.CONF, has been created. The previous configuration file (if any) has been renamed to SYS$SYSTEM:TCPIP$IP6RTRD.CONF_OLD. This new IPv6 network configuration will become active the next time TCP/IP Services for OpenVMS is started. -------------------------------------------------------------- 13: Updates for SSH release notes -------------------------------------------------------------- - If you run SSH on OpenVMS V7.3, you need the DECC runtime library kit VMS73_ACRTL-V0600 (SCT 3106). - When using TCPIP$CONFIG.COM to do a disable/re-enable for the SSH server, the following prompt is displayed: * Create a new default server host key? [YES]: Creating a new server host key can cause problems with clients which already have the existing key; enter "N" to override the default value. - If an user default directory in the sysuaf file uses the angle bracket (e.g., ) instead of square bracket ([USERNAME]) syntax, hostkey authentication fails. The workaround is to change the user entry to use square brackets. - For each SSH session, two processes are displayed in a SHOW SYSTEM. One process name has prefix "_FTA", for example: _FTA105: The other name has one of the following prefixes, depending on the number of digits in the TCP/IP Services network (BG) device: Number of digits Prefix Example in BG number less than 4 TCPIP$SSH_BG TCPIP$SSH_BG532 4 TCPIP$SS_BG TCPIP$SS_BG9408 5 TCPIP$S_BG TCPIP$S_BG10000 - The originating client host and username or port identification are not available in an ssh session on the OpenVMS server. For example, with a $ SHOW TERMINAL command for a telnet connection, the following lines are displayed; these lines are missing in SSH sessions: from a UNIX client: Remote Port Info: Host: unixsys.myco.com Port: 2728 from an OpenVMS client: Remote Port Info: Host: mysys.com Locn: _RTA4:/USER - The command line accepted for remote execution through ssh is limited to 153 characters. - In some cases of error or exit, SSH displays UNIX-style signal information, for example, a results in the message: Received signal 2, SIGINT: Interactive attention signal. These messages can be ignored. - The pairing of username and UIC in the sysuaf, as displayed by SHOW/IDENTIFIER must match that in the user account record. If there is a mismatch, the following error occurs when the user attempts to establish an SSH session: Received signal 10, SIGBUS: invalid access to memory objects. The workaround is to correct the pairing of username and UIC value in the sysuaf. - ssh, sftp and scp do not work correctly in batch mode - Packet related warnings may appear when using the sftp and scp commands on an OpenVMS SSH client when accessing an OpenSSH server, for example: sftp> ls . .bash_logout .login Warning: packet length mismatch: expected 27, got 8; connection to non-standard server? { and then after a pause... } sftp> Warning: packet length mismatch: expected 23, got 8; connection to non-standard server? The operation on OpenVMS succeeds despite the warnings. To suppress the warnings, assign the logical name "TCPIP$SSH_TOLERANT_PROTOCOL_STATUS" system-wide, for example: $ ASSIGN/SYSTEM 1 TCPIP$SSH_TOLERANT_PROTOCOL_STATUS To make this assignment persist over reboots, add it to a procedure executed at OpenVMS system startup time. Note that the if you enclose the logical name in quotation marks you must specify it in upper case, for example: $ ASSIGN/SYSTEM 1 "TCPIP$SSH_TOLERANT_PROTOCOL_STATUS" - Any non-OpenVMS client which implements the scp command using the ssh version 1 protocol is incompatibile with the OpenVMS SSH server. - The scp and sftp commands from the following Windows clients have been tested and interoperate correctly withthe OpenVMS SSH server: - PuTTY - SSH Communications Other versions and other clients may work, depending on protocol implemtntation and factors such as whether the formatting used by the client can handle OpenVMS format file paths and names. - When using sftp, before connecting to a remote system, characters entered at the sftp> prompt no longer double echo. Also, the left and arrow keys , , , and now work as expected to erase line, refresh line, and exit, respectively. However pressing does not display "Cancel". Also, does not work as in DCL to display a status line; instead it toggles two adjacent characters, as in UNIX. - The sftp ls command pauses for an extended time before continuing after the display of a page of data. - Using scp or sftp to copy a file back to itself (either in local mode, or by connecting back to the client host) fails with the error: %TCPIP-E-SSH_FC_ERR_INVA, file record format invalid for copy - Any client that uses ssh version 1 as the basis for the scp command will not work with the OpenVMS SSH server, which does not support that version of the protocol. - The -e option for ssh_keygen does not work - The following notes apply to implementation of X11 port forwarding: 1) If you have the system setup to run the remote X client application on your X server, all those applications can now be forwarded via SSH without any setup needed i.e. X11 forwarding works in it's native mode. The transports used for forwarding X applications on ssh is local and tcpip for X server running on a local system, and tcpip for X server running on a remote system. 2) The minimum requirement for X11 forwarding to work in native mode is DEC MOTIF 1.3. X11 forwarding uses the xauth feature of the X server authentication to authenticate the host/user. Xauth needs to be installed on the system for X11 forwarding to work. For more information on how to use xauth, see the documentation for DECwindows Motif for OpenVMS. 3) For X11 forwarding to work in the native mode, enable x11 forwarding on both client and server. To enable it on the client, set the value for forwardx11 to yes in client config file ssh2_config. To enable it on the server set the value for AllowX11Forwarding to yes in the server config file sshd2_config. An alternative way for client to enable x11 forwarding is to use the option +x . It does not matter if both the option are used. But If the X forwarding is enabled in the config file, you can disable it using the -x option. 4) If the X forwarding is enabled on both the ssh client and the ssh server, and you make a simple ssh connection to the remote ssh server, you should be able to run X client applications on your remote system and get the display on your X server. For example, you should be able to run DECW$CLOCK after making an ssh connection to the remote system. 5) SSH chaining of X11 forwarding is also possible. For example, if you are using excursion on a PC to display your remote OpenVMS or a UNIX system. From this system (say system1) you make a ssh connection to remote system (system2) and run X client application, for example, DECW$CLOCK for OpenVMS or xclock for UNIX. You would see the clock on your PC. In fact, you make a ssh connection from system1 to system2 and then to system3 and then to system4 and then to system5 and run an X client application on system5, you should still get the display on system1 even if the intermediate systems are not running X server. Problems user may encounter while forwarding X applications via SSH: 1) Display not set: Make sure that you have the display variable for the display running the ssh client. The display variable tells the ssh client which X server to connect, to display the X client application. You can check the display variable by using the following commands: On OpenVMS: $ SHOW LOGICAL DECW$DISPLAY The logical DECW$DISPLAY should have a value. It can either have a value of unix style display format :server.screen. Examples would be something like 16.20.99.10:0.0 or myhost.myco.com:0.0 or local/0:0.0 or a WSA device name. If it is a WSA device, you should get the display information using the following command (where 16.20.99.10 is a sample IP address): $ SHOW DISPLAY Device: WSA38: [super] Node: 16.20.99.10 Transport: TCPIP Server: 0 Screen: 0 On TRU64 Unix > echo $DISPLAY 16.20.99.10:0.0 If the display variable is not set on the ssh client, you can set it by using the following commands: On OpenVMS $ SET DISPLAY/CREATE/NODE=16.20.99.10/TRANSPORT=TCPIP Note that OpenVMS supports only LOCAL and TCPIP transports. For display using LOCAL transport, you must be logged in directly on the X11 server system, and X11 must be running. $ SET DISPLAY/CREATE/TRANSPORT=LOCAL On TRU64 Unix > setenv display 16.20.99.10:0.0 or for display on the local system: > setenv display :0.0 2) XAUTH not installed Make sure, that the OpenVMS system has xauth (X authentication) installed on the system. If it is not installed, you need to install DEC MOTIF V1.3 to install xauth. 3) X server or client not set up properly. Make sure that the X client is authenticated by the X server. Try running X client application on the X server and it should succeed. If not, then you may have to make appropriate changes for X applications to run on X server. --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 BIND9_SERVER Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 15-MAR-2004 Alpha and I64 Problem: Bind9 Slave server is refusing Notify requests from a zone's Master server. Deliverables: TCPIP$BIND_SERVER.EXE V5.4-15A Reference: PTR 70-5-2357 / CFS.101453 / Req Id: CH_G07608 / UCX Note 9854 TCPIP_BUGS Note 3029 ECO B 18-MAR-2004 5.3 and 5.4 Alpha only, 5.5 Al Problem: The BIND Server process could exit with one of the following footprints being logged to TCPIP$BIND_RUN.LOG: REQUIRE((((task) != 0L) && (((const isc__magic_t *)(task))->magic == ((('T')<< 24 | ('A') << 16 | ('S') << 8 | ('K')))))) failed Sun 19 03:00:13 CRITICAL: exiting (due to assertion failure) %SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80A6C924, PS=0000001B REQUIRE(res->item_out == isc_boolean_true) failed Fri 19 13:12:04 CRITICAL: exiting (due to assertion failure) %SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80E6C924, PS=0000001B Deliverables: TCPIP$BIND_SERVER.EXE V5.4-15B Reference: PTR 70-5-2401 / CFS.103794 TCPIP_BUGS Note 3046 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 FAILSAFE Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO B 24-MAR-2004 Alpha, IA64, and VAX Problem: After implementing the ECO fix described in 3023.0, the log file fills with the following error message every 30 seconds. ERROR: Broadcast failure on device _EIC13: status 8268 Deliverables: TCPIP$FAILSAFE.EXE V5.4-15B Reference: UCX Note 10084 TCPIP_BUGS Note 3023.2 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 FTP_CLIENT Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO D 24-MAR-2004 Alpha, IA64 Problem: After an FTP GET or MGET command issued with wildcards completes, the temporary TCPIP$FTP_TEMPnnnnnnnn.TMD files created by FTP are supposed to be deleted from the SYS$SCRATCH area. However, if no files match the wildcard criteria, FTP fails to delete any of the temporary files. (If at least one file matches the wildcard criteria, FTP does successfully delete any TCPIP$FTP_TEMPnnnnnnnn.TMD files created in SYS$SCRATCH.) Deliverables: TCPIP$FTP_CLIENT.EXE V5.4-15D Reference: PTR 70-5-2456 / CFS.105496 TCPIP_BUGS Note 3058 ECO E 14-MAY-2004 Alpha and VAX Problem: The FTP client fails to parse quoted parameter strings correctly. For example: FTP> rename "a.txt" "b.txt" interprets the above as one parameter passed to rename. Deliverables: TCPIP$FTP_CLIENT.EXE V5.4-15E Reference: PTR 70-5-2466 / CFS.105796 TCPIP_BUGS Note 3105 PTR 70-5-2504 / CFS.106611 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 FTP_SERVER Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO E 10-MAR-2004 Alpha, IA64, and VAX Problem: On an FTP client, if you use a password with an embedded space to log into an OpenVMS FTP server, the following error message will be returned in response to a DCL DIRECTORY or UNIX ls command: 500 Illegal PORT command. Deliverables: TCPIP$FTP_CHILD.EXE V5.4-15E TCPIP$FTP_SERVER.EXE V5.4-15E Reference: PTR 70-5-2410 / CFS.103944 TCPIP_BUGS Note 3063 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 IFCONFIG Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 25-MAR-2004 Alpha, IA64, and VAX Problem: The ifconfig abort command displays the incorrect number of aborted connections. Deliverables: TCPIP$IFCONFIG.EXE V5.4-15A Reference: Req Id: comp.os.vms TCPIP_BUGS Note 3071 ECO B 25-MAR-2004 Alpha, IA64, and VAX Problem: "$ ifconfig ie0 delete" only deletes active IP addresses. Deliverables: TCPIP$IFCONFIG.EXE V5.4-15B Reference: TCPIP_BUGS Note 3075 ECO C 19-APR-2004 Alpha, IA64, and VAX Problem: 1) When an interface, under the control of failSAFE, fails or recovers an alias address, the IP address is not seen with "TCPIP SHOW INTER". (PTR 30-13-200) 2) Since a pseudo address may not be active immediately, (for example, it is a standby address) the TCPIP SET INTER command may return DEVINACT, even though the address is successfully created as a standby. (30-13-205). 3) When creating a duplicate pseudo address on a different interface, TCPIP SET INTER returns BADPARAM error. Deliverables: TCPIP$INETACP.EXE V5.4-15O TCPIP$INETACP_PERF.EXE V5.4-15O PF TCPIP$INTERNET_SERVICES.EXE V5.4-15O TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15O PF TCPIP$IFCONFIG.EXE V5.4-15C TCPIP$UCP.EXE V5.4-15D Reference: PTR 30-13-200 TCPIP_BUGS Note 3080 PTR 30-13-205 PTR 70-5-2517 / CFS.106872 / Req Id: BCGMH0CZL ECO D 20-APR-2004 Alpha, IA64, and VAX Problem: Cannot filter on address family with ifconfig. Deliverables: TCPIP$IFCONFIG.EXE V5.4-15D Reference: TCPIP_BUGS Note 3086 ECO E 4-MAY-2004 Alpha, IA64, and VAX Problem: Using ifconfig several times from a single UCP session results in confusion when creating IP addresses. For example, when creating IP address2, it could inherit some attributes from IP address1. Deliverables: TCPIP$IFCONFIG.EXE V5.4-15E TCPIP$UCP.EXE V5.4-15E Reference: TCPIP_BUGS Note 3088 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 INET_V54 Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO B 16-Apr-2004 Alpha and VAX Problem: Three problems have been found due to investigation of the above PTRs. All three affected the INETDRIVER although one of the problems actually resided in the Kernel VCI module of the TCP/IP Kernel. 1. Problem one cam lead to a crash with pool corruption. 2. Problem two was that the calling sequence to routine, INETVCM$SHUTDOWN() was mis-programmed and that could also lead to a crash. 3. Problem three was that we were leaking mbuf structures each time we were executing a connect request. This could lead to serious memory shortage. Deliverables: TCPIP$INETDRIVER.EXE V5.4-15B TCPIP$INET_GLOBALS.STB TCPIP$INTERNET_SERVICES.EXE V5.4-15P TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15P PF Reference: PTR 70-5-2526 / CFS.107045 TCPIP_BUGS Note 3087 PTR 70-5-2513 / CFS.106516 ECO C 14-May-2004 Alpha and VAX Problem: Leakage of INET UCBs. Please see NET facility, ECO T (SCT 3107). Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15T TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15T PF TCPIP$INETACP.EXE V5.4-15T TCPIP$INETACP_PERF.EXE V5.4-15T PF TCPIP$INETDRIVER.EXE V5.4-15C Reference: TCPIP_BUGS Note 3107 ECO D 24-MAY-2004 Alpha and VAX Problem: Several problems: 1. System crash during shutdown in routine INETACP\INETACP$MALLOC_ACP. 2. INETACP process does not terminate after TCPIP shutdown is issued 3. System crash during shutdown in routine INTERNET_SERVICES\SOFREE. 4. INETACP process does not terminate after TCPIP shutdown is issued 5. Leakage of INET UCBs during TCPIP shutdown. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15V TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15V PF TCPIP$INETACP.EXE V5.4-15V TCPIP$INETACP_PERF.EXE V5.4-15V PF TCPIP$INETDRIVER.EXE V5.4-15D TCPIP$INETDRIVERSTOP.EXE V5.4-15D TCPIP$INET_DRIVER_SHUTDOWN.COM Reference: PTR 70-5-2536 / CFS.107462 TCPIP_BUGS Note 3109 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 INSTALL Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO E 21-APR-2004 Alpha, IA64, and VAX Problem: The TCPIP$NFS_CLIENT_STARTUP.COM command procedure fails to start the NFS client when a client license for TCP/IP Services is used. For example, $ @sys$startup:tcpip$nfs_client_startup.com %TCPIP-E-STARTFAIL, failed to start TCPIP$NFS_CLIENT -TCPIP-E-NOLICENSE, license check failed Deliverables: TCPIP$NFS_CLIENT_STARTUP.COM Reference: PTR 70-5-2528 / CFS.107160 / Req Id: HPAQ40552 / UCX Note 10080 TCPIP_BUGS Note 3089 ECO F 23-APR-2004 Alpha, IA64, and VAX Problem: The TCPIP$RMT_STARTUP.COM command procedure fails to start the RMT server when a client license for TCP/IP Services is used. For example, $ @sys$startup:tcpip$rmt_startup.com %TCPIP-E-STARTFAIL, failed to start TCPIP$RMT -TCPIP-E-NOLICENSE, license check failed Deliverables: TCPIP$RMT_STARTUP.COM Reference: TCPIP_BUGS Note 3091 ECO G 23-APR-2004 Alpha, IA64, and VAX Problem: The TCPIP$BOOTP_STARTUP.COM command procedure fails to start the BOOTP server when the BOOTP database file is moved from TCPIP$SYSTEM. For example, $ @sys$startup:tcpip$bootp_startup.com %TCPIP-E-STARTFAIL, failed to start TCPIP$BOOTP -TCPIP-E-NOFILE, cannot find file TCPIP$SYSTEM:TCPIP$BOOTP.DAT Deliverables: TCPIP$BOOTP_STARTUP.COM Reference: PTR 70-5-2490 / CFS.106292 / Req Id: DE_G09381 / UCX Note 10193 TCPIP_BUGS Note 3094 ECO H 5-MAY-2004 Alpha, IA64, and VAX Problem: The TCPIP$CONFIG.COM configuration procedure fails to correctly handle interface failover configuration. For example, 1. New aliases are added each time interface failover configuration is executed. As a result, redundant alias records accumulate in the configuration database. 2. Failover configuration fails to terminate when all of the available interfaces are selected. 3. Failover configuration prompts users with unnecessary and redundant questions. Deliverables: TCPIP$CONFIG.COM Reference: PTR 30-13-202 TCPIP_BUGS Note 3100 ECO I 24-MAY-2004 Alpha and VAX Problem: Several problems: 1. System crash during shutdown in routine INETACP\INETACP$MALLOC_ACP. 2. INETACP process does not terminate after TCPIP shutdown is issued 3. System crash during shutdown in routine INTERNET_SERVICES\SOFREE. 4. INETACP process does not terminate after TCPIP shutdown is issued 5. Leakage of INET UCBs during TCPIP shutdown. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15V TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15V PF TCPIP$INETACP.EXE V5.4-15V TCPIP$INETACP_PERF.EXE V5.4-15V PF TCPIP$INETDRIVER.EXE V5.4-15D TCPIP$INETDRIVERSTOP.EXE V5.4-15D TCPIP$INET_DRIVER_SHUTDOWN.COM Reference: PTR 70-5-2536 / CFS.107462 TCPIP_BUGS Note 3109 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 IPC Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO D 10-MAY-2004 Alpha, IA64, and VAX Problem: UCP's SET CONFIGURATION INTERFACE and SET INTERFACE commands fail to reject invalid network masks. For example, 1. The following SET CONFIGURATION INTERFACE command fails to signal an INVNETMASK error: $ tcpip set configuration interface wea100 - _$ /host=1.2.3.4 /network_mask=355.255.0.0 2. Hence, an invalid network mask is assigned for this interface in the configuration database as shown here: $ tcpip show configuration interface wea100 Interface: WEA100 IP_Addr: 1.2.3.4 NETWRK: 99.255.0.0 BRDCST: ... Deliverables: TCPIP$IPC_SHR.EXE V5.4-15D Reference: TCPIP_BUGS Note 3101 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 MOUNT_SERVER Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 24-MAR-2004 Alpha, VAX, I64 Problem: The mount server could report a misleading error message when the tcp or udp port 10 (mount port) is already in use. Deliverables: TCPIP$MOUNTD.EXE V5.4-15A Reference: PTR 30-13-345 / UCX Note 10102 TCPIP_BUGS Note 3053 ECO B 23-APR-2004 Alpha, IA64, and VAX Problem: The MOUNT service might exhibit improper verification of mount points for exported file systems. Deliverables: TCPIP$MOUNTD.EXE V5.4-15B Reference: PTR 70-5-2527 / CFS.107072 / UCX Note 10250 TCPIP_BUGS Note 3092 ECO C 23-APR-2004 Alpha, IA64, and VAX Problem: The MOUNT Server could improperly try to verify the clients domain and host name, even if none of the SYSCONFIG mountd_option_* attributes had been set. Now, no domain, hostname, or address verification will occur unless the SYSCONFIG mountd attributes are set. You may use mountd_option_d and/or mountd_option_s to verify that the client and the server are in the same domain or subdomain, respectively. Deliverables: TCPIP$MOUNTD.EXE V5.4-15C Reference: UCX Note 10246 TCPIP_BUGS Note 3093 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NET Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO J 8-Mar-2004 Alpha and VAX Problem: Crash in KVCI$$RECEIVE with null INETKVCI pointer due to zero VCRP$L_CREATOR_DATA1. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15J TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15J PF TCPIP$TNDRIVER.EXE V5.4-15D TCPIP$TNDRIVER_PERF.EXE V5.4-15D PF Reference: PTR 70-5-2481 / CFS.104564 TCPIP_BUGS Note 3067 ECO K 8-Mar-2004 Alpha and VAX Problem: Somewhat unpredictable behavior in TCP/IP scaling kernel using "select". Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15K PF Reference: TCPIP_BUGS Note 3069 ECO L 16-Mar-2004 Alpha and VAX Problem: In V5.4 scaling kernel select() on the write sockbuf can return incorrectly if the socket is not yet connected. That is, if one creates a socket, sets the socket as non-blocking, connects, and then does a select() with the new socket on the write list, select() will return immediately indicating that the socket can be written to, even though the socket may not yet be connected. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15L PF Reference: PTR 70-5-2485 / UCX Note 10182 TCPIP_BUGS Note 3073 ECO M 22-Mar-2004 Alpha and VAX Problem: QIO reads on a TCP socket that specify a non-writable buffer do not return the SS$_ACCVIO status but rather return an SS$_NORMAL status with zero bytes transferred to the buffer. Note the bug does not exist in the scaling kernel. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15M Reference: PTR 70-5-2486 / CFS.106251 TCPIP_BUGS Note 3076.0 ECO N 24-MAR-2004 Alpha, IA64, and VAX Problem: ICMP_MASKREPLY messages would not be sent if the destination was the broadcast address. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15N Reference: PTR 70-5-2469 / UCX Note 10162 TCPIP_BUGS Note 3060 ECO O 8-APR-2004 Alpha, IA64, and VAX Problem: 1) When an interface, under the control of failSAFE, fails or recovers an alias address, the IP address is not seen with "TCPIP SHOW INTER". (PTR 30-13-200) 2) Since a pseudo address may not be active immediately, (for example, it is a standby address) the TCPIP SET INTER command may return DEVINACT, even though the address is successfully created as a standby. (30-13-205). 3) When creating a duplicate pseudo address on a different interface, TCPIP SET INTER returns BADPARAM error. Deliverables: TCPIP$INETACP.EXE V5.4-15O TCPIP$INETACP_PERF.EXE V5.4-15O PF TCPIP$INTERNET_SERVICES.EXE V5.4-15O TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15O PF TCPIP$IFCONFIG.EXE V5.4-15C TCPIP$UCP.EXE V5.4-15D Reference: PTR 30-13-200 TCPIP_BUGS Note 3080 PTR 30-13-205 PTR 70-5-2517 / CFS.106872 / Req Id: BCGMH0CZL ECO P 16-APR-2004 Alpha and VAX Problem: Please see ECO B for component INET_V54 (SCT 3087) for a detailed description. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15P TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15P PF Reference: PTR 70-5-2526 / CFS.107045 TCPIP_BUGS Note 3087 PTR 70-5-2513 / CFS.106516 ECO Q 26-APR-2004 Alpha and VAX Problem: System crash while running the TCP/IP scaling kernel, with corrupted pool. The address of the longword of corruption will have an offset of one of the following: 054 or 058, 254 or 258, 454 or 458, 654 or 658, 854 or 858, A54 or A58, C54 or C58, E54 or E58. These offsets correspond to the offsets MBUF$A_EXT_REF_FORW and MBUF$A_EXT_REF_BACK. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15Q PF Reference: PTR 75-102-785 TCPIP_BUGS Note 3096 ECO R 30-APR-2004 Alpha and VAX Problem: Two problems associated with TCPIP$INETDRIVER: 1. With either the scaling kernel or the classic kernel, but on the scaling kernel it can lead to a system crash; on the classic kernel the result is just a failed application. When running an TCPIP$INETDRIVER application with a server and multiple clients, after accepting 512 client connections the server might hang while reading from the client and no more useful work will be done on any new connections that arrive. If connections keep arriving the server will fail due to quotas being exhausted. 2. With the scaling kernel, while running TCPIP$INETDRIVER applications, the exiting of an application process can trigger a system crash (INCONSTATE). Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15R TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15R PF Reference: PTR 70-5-2513 / CFS.106783 TCPIP_BUGS Note 3099 ECO S 05-MAY-2004 Alpha and IA64 Problem: Pool corruption may occur with the scalable kernel while processing some requests. Examples of such requests are Connect, Accept, Soclose and Soshutdown, when issued from a multi-threaded application. Deliverables: TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15S PF Reference: PTR 75-102-811 TCPIP_BUGS Note 3102 ECO T 14-MAY-2004 Alpha and VAX Problem: Several problems: 1. System crash while running V5.4 Classic Kernel in an environment with TCPIP$INETDRIVER or NFS activity. 2. System crash with pool checking on with V5.4 Scalable kernel where corrupted pool corresponds to the TCPIP_KRP$L_STALL_STATUS longword which is zero. Also the deallocation PC indicates that the call to deallocate arose in SELECT_SETUP_KERNEL_CONTEXT. 3. Leakage of INET UCBs. 4. Select misbehavior in the V5.4 Scalable Kernel. A call to select with zero lists and a valid timeout fails to wait for the timeout period. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15T TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15T PF TCPIP$INETACP.EXE V5.4-15T TCPIP$INETACP_PERF.EXE V5.4-15T PF TCPIP$INETDRIVER.EXE V5.4-15C Reference: PTR 70-5-2518 / CFS.106090 / Req Id: ZPO237681 TCPIP_BUGS Note 3107 ECO U 19-MAY-2004 Alpha and VAX Problem: CPUSPINWAIT crashes due to a deadlock where two CPUs are attempting to acquire spinlocks simultaneously. One of the CPUs holds IOLOCK8 and is attempting to acquire the TCP/IP MBUF mini-lock, while the other CPU holds the MBUF mini-lock and is attempting to acquire IOLOCK8. Note this can occur only with the V5.4 classic kernel. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15U TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15U PF Reference: PTR 70-5-2536 / CFS.107462 TCPIP_BUGS Note 3108.0 ECO V 24-MAY-2004 Alpha and VAX Problem: Several problems: 1. System crash during shutdown in routine INETACP\INETACP$MALLOC_ACP. 2. INETACP process does not terminate after TCPIP shutdown is issued 3. System crash during shutdown in routine INTERNET_SERVICES\SOFREE. 4. INETACP process does not terminate after TCPIP shutdown is issued 5. Leakage of INET UCBs during TCPIP shutdown. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15V TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15V PF TCPIP$INETACP.EXE V5.4-15V TCPIP$INETACP_PERF.EXE V5.4-15V PF TCPIP$INETDRIVER.EXE V5.4-15D TCPIP$INETDRIVERSTOP.EXE V5.4-15D TCPIP$INET_DRIVER_SHUTDOWN.COM Reference: PTR 70-5-2536 / CFS.107462 TCPIP_BUGS Note 3109 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NETSTAT Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 4-MAY-2004 Alpha, IA64, and VAX Problem: netstat -m does not display descriptions for some memory types. Deliverables: TCPIP$NETSTAT.EXE V5.4-15A Reference: PTR 30-14-35 TCPIP_BUGS Note 3085 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NETUTIL6 Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 8-DEC-2003 Alpha and VAX Problem: Traceroute not exiting with proper status code or error message. Deliverables: TCPIP$TRACEROUTE.EXE V5.4-15A TCPIP$IPC_SHR.EXE V5.4-15B Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 2985 ECO B 8-DEC-2003 Alpha, Vax, IA64 Problem: TCPIP$IP6_SETUP.COM required TCP/IP to be started. Deliverables: TCPIP$IP6_TESTADDR.EXE V5.4-15B Reference: PTR 30-10-76 / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 3008 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 NTP4_SERVER Images --------------------------------------------------------------------------- The following NTP problem is fixed in V5.4 Problem: When running on certain high-performance Alpha systems, NTP may be unable to adjust the system clock; therefore, NTP will not be able to provide accurate timekeeping. When this happens, the following error message appears in the NTP log file: %SYSTEM-F-BADLOGIC, internal logic error detected VMS timekeeping is not working as expected - can't proceed Solution: This problem was corrected in the previous release of the product; however, the Version 5.4 Release Notes did not indicate the problem had been fixed. ECO 1 updates ------------- ECO A 5-DEC-2003 Alpha, VAX, and IA64 Problem: NTP bugs uncovered while tracking an IA64 issue. Deliverables: TCPIP$NTP.EXE V5.4-15A Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 2992 ECO B 5-DEC-2003 Alpha, Vax, IA64 Problem: "volatile" bug fixed for IA64 Deliverables: TCPIP$NTP.EXE V5.4-15B Reference: PTR ! / CFS.! / Req Id: ! / UCX Note ! TCPIP_BUGS Note 3007 ECO 2 updates ------------- ECO D 24-MAR-2004 Alpha, IA64, and VAX Problem: NTP creates files with lowercase filenames on ODS-5 Deliverables: TCPIP$NTP.EXE V5.4-15D TCPIP$NTP-GENKEYS.EXE V5.4-15D Reference: PTR 30-14-96 TCPIP_BUGS Note 3077 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 PWIP Images --------------------------------------------------------------------------- ECO 1 updates ------------- ECO A 22-DEC-2003 Alpha and VAX Problem: When PWIP is shut down, the system crashes at location PWIP_WRITE_C+001DC. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15A Reference: TCPIP_BUGS Note 2984 ECO B 22-DEC-2003 Alpha and VAX Problem: While running DECnet/IP applications the system crashes with a corrupt INETKVCI$A_VCRP_FLINK/INETKVCI$A_VCRP_BLINK queue. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15A Reference: PTR 75-83-1514 TCPIP_BUGS Note 2989.1 ECO C Alpha and VAX Problem: System crash if running scaling kernel and PATHWORKS is stopped. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15C Reference: TCPIP_BUGS Note 3034 ECO D Alpha and VAX Problem: Problem seen only with the scaling kernel and will result in a crash due either to pool exhaustion or to CPUSPINWAIT where the wait is for IOLOCK8. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15D TCPIP$INTERNET_SERVICES.EXE V5.4-15G Reference: PTR 70-5-2455 / CFS.105464 TCPIP_BUGS Note 3044 ECO 2 updates ------------- ECO E 6-APR-2004 Alpha, IA64, and VAX Problem: 1) PTR 70-13-1196 A DECnet "tower set" is simply the lower four tiers of the OSI protocol stack, for example: [ DNA_CMIP-MICE ] , [ DNA_SessionControlV3 , number = 19 ] , [ DNA_OSItransportV1 , 'DEC0'H ] , [ DNA_IP , 16.20.208.100 (LASSIE) ] In a DECnet/IP tower set the network level information is obtained by making a T_ADDR request to the PWIPDRIVER. PWIP returns all of the configured addresses, so there can be more than one DECnet/IP tower set. In TCPIP V5.1 and later, the T_ADDR request is broken. The effect of this on DECnet is that the tower set network level information is inaccurate. Advanced Server does not make T_ADDR requests. 2) IPV6 support. PWIP is currently coded to work with only IPV4 sockets; it needs to handle IPV6 sockets. It needs a way to tell callers that it handles IPV6 sockets. 3) Cleanup PWIP does not conform to many of the coding standards that exist in the other parts of the TCP/IP code. Deliverables: PWIP$SDA.EXE V5.4-15E TCPIP$PWIPACP.EXE V5.4-15E TCPIP$PWIPDRIVER.EXE V5.4-15E Reference: PTR 70-13-1196 TCPIP_BUGS Note 3074 ECO G 15-APR-2004 Alpha and VAX Problem: PWIPDRIVER relied on the fact that the TCP/IP kernel, on a call through the VCRP$A_TCPIP_RECEIVE vestor, returned a 32 bit status whose upper 16 bits were guaranteed to be zero. That behavior has now changed in the TCP/IP kernel. The upper 16 bits now may contain a UNIX status. As a result, PWIPDRIVER_WRITE.C is modified slightly to adjust to this change in behavior. This is being done in conjunction with changes to the INETDRIVER and the kernel but this change is completely independent of those changes and is correct even without them. Deliverables: TCPIP$PWIPDRIVER.EXE V5.4-15G Reference: TCPIP_BUGS Note 3083 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 SMTP Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO E 14-MAY-2004 Alpha Problem: scp and sftp cannot copy files larger than 2 gigabytes. If you run SSH on OpenVMS V7.3, you need the DECC runtime library kit VMS73_ACRTL-V0600. Deliverables: TCPIP$SSH_SCP2.EXE V5.4-15E TCPIP$SSH_SFTP-SERVER2.EXE V5.4-15E TCPIP$SSH_SFTP2.EXE V5.4-15E TCPIP$SSH_SSH-ADD2.EXE V5.4-15E TCPIP$SSH_SSH-AGENT2.EXE V5.4-15E TCPIP$SSH_SSH-KEYGEN2.EXE V5.4-15E TCPIP$SSH_SSH-SIGNER2.EXE V5.4-15E TCPIP$SSH_SSH2.EXE V5.4-15E TCPIP$SSH_SSHD2.EXE V5.4-15E Reference: PTR 70-5-2477 / CFS.106027 / Req Id: BE_G09276 TCPIP_BUGS Note 3106 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 TCPDUMP Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 14-MAY-2004 Alpha, and VAX Problem: System crash in tcpip$internet_services inet_*_send_log after completion of a trace using tcpdump. This can happen when there is a lot of traffic on the network. Deliverables: TCPIP$TCPDUMP.EXE V5.4-15A Reference: TCPIP_BUGS Note 3104 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 TCPIPLIB Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO C 20-Feb-2004 Alpha and VAX Problem: During or after TCP/IP system shutdown, the system crashes with INVEXCEPTN in TCPIP$TNDRIVER+5D4 (V5.3). Deliverables: TCPIP$TNDRIVER.EXE V5.4-15C TCPIP$TNDRIVER_PERF.EXE V5.4-15C PF Reference: PTR 70-5-2448 / CFS.105206 TCPIP_BUGS Note 3054 ECO D 8-Mar-2008 Alpha and VAX Problem: Crash in KVCI$$RECEIVE with null INETKVCI pointer due to zero VCRP$L_CREATOR_DATA1. Deliverables: TCPIP$INTERNET_SERVICES.EXE V5.4-15J TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15J PF TCPIP$TNDRIVER.EXE V5.4-15D TCPIP$TNDRIVER_PERF.EXE V5.4-15D PF Reference: PTR 70-5-2481 / CFS.104564 TCPIP_BUGS Note 3067 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 UCP Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO C 11-MAR-2004 Alpha, IA64, and VAX Problem: UCP's SET NOROUTE command deletes routes that do not exactly match the specified selection criteria. For example: consider this: a. Show all network routes, do: $ tcpip show route DYNAMIC Type Destination Gateway . . . AN 136.2.0.0/16 16.20.208.53 AH 136.2.2.250 16.20.208.53 b. Delete only the 136.2.2.250 host route, do $ tcpip set noroute 136.2.2.250 /noconfirm c. Show 136.2.0.0 network route, do: $ tcpip show route 136.2.0.0 %TCPIP-E-ROUTEERROR, error accessing routes database (TCPIP$ROUTE) -TCPIP-W-NORECORD, information not found Both host (136.2.2.250) and network (136.2.0.0) routes were deleted; not just the 136.2.2.250 host route as specified. Deliverables: TCPIP$UCP.EXE V5.4-15C Reference: PTR 70-5-2461 / CFS.105684 / Req Id: HGO175762 TCPIP_BUGS Note 3066 ECO D 19-APR-2004 Alpha, IA64, and VAX Problem: 1) When an interface, under the control of failSAFE, fails or recovers an alias address, the IP address is not seen with "TCPIP SHOW INTER". (PTR 30-13-200) 2) Since a pseudo address may not be active immediately, (for example, it is a standby address) the TCPIP SET INTER command may return DEVINACT, even though the address is successfully created as a standby. (30-13-205). 3) When creating a duplicate pseudo address on a different interface, TCPIP SET INTER returns BADPARAM error. Deliverables: TCPIP$INETACP.EXE V5.4-15O TCPIP$INETACP_PERF.EXE V5.4-15O PF TCPIP$INTERNET_SERVICES.EXE V5.4-15O TCPIP$INTERNET_SERVICES_PERF.EXE V5.4-15O PF TCPIP$IFCONFIG.EXE V5.4-15C TCPIP$UCP.EXE V5.4-15D Reference: PTR 30-13-200 TCPIP_BUGS Note 3080 PTR 30-13-205 PTR 70-5-2517 / CFS.106872 / Req Id: BCGMH0CZL ECO D 19-APR-2004 Alpha, IA64, and VAX Problem: Several problems related to creating and managing pseudo interfaces include: 1. PTRs 30-13-324, 30-13-348 UCP's SET INTERFACE and GENERATE INTERFACE commands generate errors (SYSTEM-F-BADPARAM) resulting from race conditions between creating the pseudo interface's alias address and adding its (UCP) marker. UCP's SET INTERFACE and GENERATE INTERFACE commands generate errors (SYSTEM-F-BADPARAM) when creating an interface that specifies a network address that is already in use by another interface. For example, $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 72828 72828 4096 WE0 10.10.4.2 255.255.255.0 97200 9644 1500 $ tcpip set interface wea100 /host=10.20.30.100 %TCPIP-E-INVINTERNAM, invalid interface name -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-F-BADPARAM, bad parameter value 2. PTR 30-13-349 Pseudo interfaces are not consistently created as address aliases. 3. PTR 70-5-2517 UCP's SET INTERFACE and GENERATE INTERFACE commands generate errors (SYSTEM-F-DEVINACT) when creating pseudo interfaces on systems using TCP/IP Services V5.4 and later (performance kernel disabled). For example, $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 72828 72828 4096 WE0 10.10.4.2 255.255.255.0 97200 9644 1500 $ tcpip set interface wea100 /host=10.20.30.100 %TCPIP-E-INVINTERNAM, invalid interface name -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-F-DEVINACT, device inactive 4. UCP's SET INTERFACE and GENERATE INTERFACE commands will delete an existing pseudo interface when creating a new pseudo interface that specifies the same network address on systems using TCP/IP Services V5.4 and later (performance kernel enabled). For example, $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 100 100 4096 WE0 10.10.4.4 255.255.255.0 329 16 1500 WEA100 10.20.30.100 255.0.0.0 329 16 1500 WEA101 10.20.30.101 255.0.0.0 329 16 1500 WEA102 10.20.30.102 255.0.0.0 329 16 1500 $ tcpip set interface wea103 /host=10.20.30.101 $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 100 100 4096 WE0 10.10.4.4 255.255.255.0 332 20 1500 WEA100 10.20.30.100 255.0.0.0 332 20 1500 WEA102 10.20.30.102 255.0.0.0 332 20 1500 WEA103 10.20.30.101 255.0.0.0 332 20 1500 Deliverables: TCPIP$UCP.EXE V5.4-15D Reference: PTR 30-13-324 TCPIP_BUGS Note 3084 PTR 30-13-348 PTR 30-13-349 PTR 70-5-2517 / CFS.106872 / Req Id: BCGMH0CZL ECO E 4-MAY-2004 Alpha, IA64, and VAX Problem: Using ifconfig several times from a single UCP session results in confusion when creating IP addresses. For example, when creating IP address2, it could inherit some attributes from IP address1. Deliverables: TCPIP$IFCONFIG.EXE V5.4-15E TCPIP$UCP.EXE V5.4-15E Reference: TCPIP_BUGS Note 3088 ECO F 4-MAY-2004 Alpha, IA64, and VAX Problem: UCP's SET CONFIGURATION ENABLE SERVICE command generates an error whenever an attempt is made to enable a service that is already enabled. For example: a. Show configuration enable service list, do: $ tcpip show configuration enable service Enable service BIND, DHCP, FINGER, FTP, FTP_CLIENT, LPD, METRIC, MYSERV, NFS, NFS_CLIENT, NTP, PCNFS, PORTMAPPER, PWIP_DRIVER, REXEC, RSH, SMTP, SNMP, TELNET, XDM b. Now attempt to enable FTP when it is already enabled, do: $ tcpip set configuration enable service ftp %TCPIP-E-CONFIGERROR, error processing configuration request -RMS-F-DUP, duplicate key detected (DUP not set) Deliverables: TCPIP$UCP.EXE V5.4-15F Reference: PTR 30-14-121 TCPIP_BUGS Note 3097 ECO F 4-MAY-2004 Alpha, IA64, and VAX Problem: UCP limits the number of network controller types to 32. Currently, the number of network controller types, as defined by TCPIP$CONFIG.COM, has reached 29. Thus, only 3 slots are left for new network controller types. Deliverables: TCPIP$UCP.EXE V5.4-15F Reference: TCPIP_BUGS Note 3098 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 UCPLIB Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 18-MAR-2004 Alpha, IA64, and VAX Problem: UCPLIB cannot handle adding a new SMTP configuration database record in a cluster environment. For example, the following valid UCP command fails as shown here: $ tcpip set configuration smtp - _$ /gateway=alternate=smtp /zone=dbnl.bil.int.dexwired.net %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000001F0000, PC=FFFFFFFF808FC17C, PS=0000001B Deliverables: TCPIP$ACCESS_SHR.EXE V5.4-15A Reference: PTR 70-5-2402 / UCX Note 9918 TCPIP_BUGS Note 3047 ECO B 13-MAY-2004 Alpha, IA64, and VAX Problem: UCPLIB can not handle adding a new SMTP configuration database record in a cluster environment. For example, the following valid configuration session fails as shown here when configuring SMTP on 2nd or subsequent node in a cluster: $ @sys$manager:tcpip$config.com . . . HP TCP/IP Services for OpenVMS Client Components Configuration Menu Configuration options: 1 - DHCP Client Disabled Stopped 2 - FTP Client Enabled Started 3 - NFS Client Disabled Stopped 4 - REXEC and RSH Enabled Started 5 - RLOGIN Disabled Stopped 6 - SMTP Enabled Started 7 - SSH Client Enabled Started 8 - TELNET Enabled Started 9 - TELNETSYM Disabled Stopped A - Configure options 1 - 9 [E] - Exit menu Enter configuration option: 6 SMTP Configuration Service is defined in the SYSUAF. Service is defined in the TCPIP$SERVICE database. Configuration is not defined in the TCPIP$CONFIGURATION database. Service is not enabled. Service is started. SMTP configuration options: 1 - Enable service on this node 2 - Stop service on this node [E] - Exit SMTP configuration Enter configuration option: 1 %TCPIP-E-CONFIGERROR, error processing configuration request -RMS-W-RTB, 1089972 byte record too large for user's buffer %TCPIP-E-CONFIGERROR, error processing configuration request -RMS-W-RTB, 1089972 byte record too large for user's buffer Deliverables: TCPIP$ACCESS_SHR.EXE V5.4-15B Reference: PTR 75-102-920 TCPIP_BUGS Note 3103 --------------------------------------------------------------------------- Corrections for HP TCP/IP Services V5.4 UNIX_API Images --------------------------------------------------------------------------- ECO 2 updates ------------- ECO A 20-APR-2004 Alpha, IA64, and VAX Problem: Several problems related to creating and managing pseudo interfaces include: 1. PTRs 30-13-324, 30-13-348 UCP's SET INTERFACE and GENERATE INTERFACE commands generate errors (SYSTEM-F-BADPARAM) resulting from race conditions between creating the pseudo interface's alias address and adding its (UCP) marker. UCP's SET INTERFACE and GENERATE INTERFACE commands generate errors (SYSTEM-F-BADPARAM) when creating an interface that specifies a network address that is already in use by another interface. For example, $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 72828 72828 4096 WE0 10.10.4.2 255.255.255.0 97200 9644 1500 $ tcpip set interface wea100 /host=10.20.30.100 %TCPIP-E-INVINTERNAM, invalid interface name -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-F-BADPARAM, bad parameter value 2. PTR 30-13-349 Pseudo interfaces are not consistently created as address aliases. 3. PTR 70-5-2517 UCP's SET INTERFACE and GENERATE INTERFACE commands generate errors (SYSTEM-F-DEVINACT) when creating pseudo interfaces on systems using TCP/IP Services V5.4 and later (performance kernel disabled). For example, $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 72828 72828 4096 WE0 10.10.4.2 255.255.255.0 97200 9644 1500 $ tcpip set interface wea100 /host=10.20.30.100 %TCPIP-E-INVINTERNAM, invalid interface name -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-F-DEVINACT, device inactive 4. UCP's SET INTERFACE and GENERATE INTERFACE commands will delete an existing pseudo interface when creating a new pseudo interface that specifies the same network address on systems using TCP/IP Services V5.4 and later (performance kernel enabled). For example, $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 100 100 4096 WE0 10.10.4.4 255.255.255.0 329 16 1500 WEA100 10.20.30.100 255.0.0.0 329 16 1500 WEA101 10.20.30.101 255.0.0.0 329 16 1500 WEA102 10.20.30.102 255.0.0.0 329 16 1500 $ tcpip set interface wea103 /host=10.20.30.101 $ tcpip show interface Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 100 100 4096 WE0 10.10.4.4 255.255.255.0 332 20 1500 WEA100 10.20.30.100 255.0.0.0 332 20 1500 WEA102 10.20.30.102 255.0.0.0 332 20 1500 WEA103 10.20.30.101 255.0.0.0 332 20 1500 Deliverables: TCPIP$UCP.EXE V5.4-15D Reference: PTR 30-13-324 TCPIP_BUGS Note 3084 PTR 30-13-348 PTR 30-13-349 PTR 70-5-2517 / CFS.106872 / Req Id: BCGMH0CZL