MultiNet v4.3 Release Notes Table of Contents Chapter 1 Introduction 1.1 Typographical Conventions.............................1 1.2 Obtaining Technical Support...........................1 1.2.1 Before Contacting Technical Support.........2 1.2.2 Sending Electronic Mail.....................3 1.2.3 Calling Technical Support...................3 1.2.4 Contacting Technical Support by Fax.........3 1.3 Obtaining Online Help.................................4 1.4 MultiNet Frequently Asked Questions (FAQs)............4 1.5 Accessing the MultiNet Public Mailing List............4 1.6 Process Software World Wide Web Server................4 1.7 Obtaining Software Patches Over the Internet..........5 1.8 Documentation Comments................................6 1.9 CD-ROM Contents.......................................6 1.9.1 Online Documentation........................6 1.9.1.1 PDF Format................................6 1.9.1.1.1 Using Acrobat Reader....................7 1.9.1.1.2 Using XPDF..............................7 1.9.1.2 HTML Format...............................8 1.9.1.3 PostScript Format........................10 Chapter 2 Enhancements and Changes 2.1 Mandatory VMS Patch..................................10 2.2 Disabled Services....................................10 2.3 Logical Name Changes.................................11 2.4 Enhancements Devices..........................................11 Paired Network Interface on Common Ethernet Cable11 SSH..............................................12 DHCP v.3.........................................12 DNS..............................................14 SNMP.............................................15 2.5 Changes IP AddressWorks..................................17 REMIND...........................................17 Kernel...........................................17 XNTP.............................................18 DECnet...........................................19 UCXDRIVER........................................19 NOTDRIVER........................................20 INETDRIVER.......................................20 NSLOOKUP.........................................20 2.5.1 Server NFS......................................20 RCD......................................21 DNS......................................21 DHCP.....................................22 FTP......................................24 OPCOM....................................26 NTY......................................26 PRINTING.................................27 MASTER SERVER............................28 SMTP.....................................28 SNMP.....................................29 i 2.5.2 Client WHOIS....................................29 TN3270...................................29 SNMP.....................................30 TCPDUMP..................................30 NFS......................................30 Chapter 3 Documentation Updates 3.1 MultiNet for OpenVMS Installation and Introduction...31 3.2 MultiNet for OpenVMS Administrator's Guide...........31 3.3 MultiNet for OpenVMS Administrator's Reference.......40 3.4 MultiNet for OpenVMS Programmer's Reference..........43 3.5 MultiNet for OpenVMS User's Guide....................43 3.6 MultiNet for OpenVMS Messages and Logicals...........44 3.7 MultiNet for OpenVMS Online Help.....................44 3.8 TCP/IP Services for DECnet Applications..............44 3.9 Changes Made After the Documentation Went to Press...44 3.10 Changes Not Made to the PostScript, PDF, and HTML Documentation....................................46 Table Table 1-1 System Information..............................2 ii Chapter 1 Introduction These Release Notes describe the changes and enhancements made to the MultiNet product in version 4.3. This chapter describes conventions used in the MultiNet documentation set and the various methods to contact and receive technical support. o For information about product changes and enhancements in the MultiNet v4.3 Consolidated Distribution, refer to chapter 2. o For information about changes to the documentation set, refer to Chapter 3 of these release notes. 1.1 Typographical Conventions ============================= Examples in these release notes use the following conventions: Convention Example Meaning ======================================= Angle brackets Represents a key on your keyboard. Angle brackets with a slash Indicates that you hold down the key labeled or while simultaneously pressing another key; in this example, the "A" key. Square brackets [FULL] Indicates optional choices; you can enter none of the choices, or as many as you like. When shown as part of an example, square brackets are actual characters you should type. Underscore or file_name Between words in commands, indicates the hyphen or item is a single element. file-name 1.2 Obtaining Technical Support ================================ Process Software provides technical support if you have a current Maintenance Service Agreement. If you obtained MultiNet from an authorized distributor or partner, you receive your technical support directly from them. You can contact Technical Support by: o Sending electronic mail (Section 1.2.2) o Calling Technical Support (Section 1.2.3) o Faxing a description of your problem to the Technical Support Group (Section 1.2.4) 1 1.2.1 Before Contacting Technical Support ========================================== Before you call, or send email or a fax: 1. Verify that your Maintenance Service Agreement is current. 2. Read the online Release Notes completely. 3. Have the following information available: -Your name -Your company name -Your email address -Your voice and fax telephone numbers -Your Maintenance Contract Number -OpenVMS architecture -OpenVMS version -MultiNet layered products and versions 4. Have complete information about your configuration, error messages that appeared, and problem specifics. 5. Be prepared to let a Development engineer connect to your system either with TELNET or by dialing in using a modem. Be prepared to give the engineer access to a privileged account to diagnose your problem. You can obtain information about your OpenVMS architecture, OpenVMS version, MultiNet version, and layered products with the MULTINET SHOW /LICENSE command. Execute the following command on a fully loaded system and email the output to support@process.com: $ MULTINET SHOW /LICENSE Process Software MultiNet v4.3, VAXstation 4000-90, OpenVMS VAX v7.1 In this example: The machine or system architecture is VAX. The OpenVMS version is v7.1. The MultiNet version is v4.3. Use Table 1-1 as a template to record the relevant information about your system. Table 1-1: System Information ============================== Required Information Your System Information =============================================================== Your name Company name Your email address Your voice and fax telephone numbers System architecture VAX | Alpha OpenVMS version MultiNet version 2 MultiNet optional software components: -MultiNet NFS Client Installed? Yes | No -MultiNet NFS Server Installed? Yes | No -MultiNet Secure/IP Client Installed? Yes | No -MultiNet Secure/IP Server Installed? Yes | No -TCP/IP applications Installed? Yes | No -Online documentation Installed? Yes | No -MultiNet Programmer's Kit Installed? Yes | No 1.2.2 Sending Electronic Mail ============================= For many questions, electronic mail is the preferred communication method. Technical support via electronic mail is available to customers with a current support contract. Send electronic mail to support@process.com. At the beginning of your mail message, include the information listed in Section 1.2.1. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your electronic support request. Electronic mail is answered within the desired goal of two hours, during our normal business hours, Monday through Friday from 8:30 a.m. to 5:00 p.m., United States Eastern Time. 1.2.3 Calling Technical Support ================================= For regular support issues, call 800-394-8700 or 508-628-5074 for support Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. For our customers in North America with critical problems, an option for support 7 days per week, 24 hours per day is available at an additional charge. Please contact your Account Representative for further details. Before calling, have available the information described in Section 1.2.1. When you call, you will be connected to a Technical Support Specialist. Be prepared to discuss problem specifics with your Technical Support Specialist and to let that person connect to your system. If our Support Specialists are assisting other customers and you are put on hold, please stay on the line. Most calls are answered in less than five minutes. If you cannot wait for a Specialist to take your call, please take advantage of our automatic call logging feature by sending email to support@process.com (see the section Sending Electronic Mail). 1.2.4 Contacting Technical Support by Fax =========================================== You can send fax transmissions directly to Technical Support at 508-879-0042. Before faxing comments or questions, complete the steps in Section 1.2.1 and include all your system information at the beginning of your fax message. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your fax support request. 3 Faxed questions are answered Monday through Friday from 8:30 a.m. to 7:00 p.m. United States Eastern Time. 1.3 Obtaining Online Help ========================== Extensive information about MultiNet is provided in the MultiNet help library. For more information, enter the following command: $ HELP MULTINET 1.4 MultiNet Frequently Asked Questions (FAQs) List ==================================================== You can obtain an updated list of frequently asked questions (FAQs) and answers about MultiNet products from the Process Software home page located at http://www.process.com. Choose the "Support" link to access useful information on FAQs and patch ECOs. 1.5 Accessing the MultiNet Public Mailing List =============================================== Process Software maintains two public mailing lists for MultiNet customers: --Info-MultiNet@process.com --MultiNet-Announce@process.com The Info-MultiNet@process.com mailing list is a forum for discussion among MultiNet system managers and programmers. Questions and problems regarding MultiNet can be posted for a response by any of the subscribers. To subscribe to Info-MultiNet, send a mail message with the word "SUBSCRIBE" in the body to Info-MultiNet-request@process.com. The information exchanged over Info-MultiNet is also available via the USENET newsgroup vmsnet.networks.tcp-ip.multinet. You can retrieve the Info-MultiNet archives by anonymous FTP to ftp.multinet.process.com. The archives are located in the directory [CUSTOMER_SUPPORT.MAIL_ARCHIVES.INFO-MULTINET]. You can also find the Info-MultiNet archives on the MultiNet consolidated CD-ROM in the directory: [INFOMULTINET] The MultiNet-Announce@process.com mailing list is a one-way communication (from Process Software to you) used to post announcements relating to MultiNet (patch releases, product releases, etc.). To subscribe to MultiNet-Announce, send a mail message with the word "SUBSCRIBE" in the body to MultiNet-Announce-request@process.com. 1.6 Process Software World Wide Web Server ========================================== Electronic support is provided through the Process Software World Wide Web server, which you can access with any World Wide Web browser; the URL is http://www.process.com (select "Support"). 4 1.7 Obtaining Software Patches Over the Internet ================================================ Process Software provides software patches in save set and ZIP format on its anonymous FTP server, ftp.multinet.process.com. For the location of software patches, read the .WELCOME file in the top-level anonymous directory. This file refers you to the directories containing software patches. To retrieve a software patch, enter the following commands: $ MULTINET FTP /USERNAME=ANONYMOUS/PASSWORD="emailaddress" - _$ FTP.MULTINET.PROCESS.COM A message welcoming you to the Process Software FTP directory appears next followed by the FTP prompt. Enter the following at the FTP> prompts: FTP.MULTINET.PROCESS.COM>CD [.PATCHES.MULTINETxxx] FTP.MULTINET.PROCESS.COM>GET update_filename In these commands: -emailaddress is your email address in the standard user@host format. -xxx is the version of MultiNet you want to transfer. -update_filename is the name of the file you want to transfer. To transfer files from Process Software directly to an OpenVMS system, you can use the GET command without any other FTP commands. However, if you need to transfer a software patch through an intermediate non-OpenVMS system, use BINARY mode to transfer the files to and from that system. In addition, if you are retrieving the software patch in save set format, make sure the save set record size is 2048 bytes when you transfer the file from the intermediate system to your OpenVMS system: o If you use the GET command to download the file from the intermediate system, use the FTP RECORD-SIZE 2048 command before transferring the file. o If you use the PUT command to upload the file to your OpenVMS system, log into the intermediate system and use the FTP quote site rms recsize 2048 command before transferring the file. Process Software also supplies UNZIP utilities for OpenVMS VAX and Alpha for decompressing ZIP archives in the [THIRD_PARTY_TOOLS.VMS] directory. To use ZIP format kits, you need a copy of the UNZIP utility. The following example shows how to use the UNZIP utility, assuming you have copied the appropriate version of UNZIP.EXE to your current default directory: $ UNZIP := $SYS$DISK:[]UNZIP.EXE $ UNZIP filename.ZIP Use VMSINSTAL to upgrade your MultiNet system with the software patch. 5 1.8 Documentation Comments ========================== Your comments about the information in these Release Notes can help us improve the documentation. If you have corrections or suggestions for improvement, please let us know. Be as specific as possible about your comments: include the exact title of the document, version, date, and page references as appropriate. You can send your comments by email to: techpubs@process.com or mail them to: Process Software 959 Concord Street Framingham, MA 01701-4682 Attention: Marketing Manager You can also fax your comments to us at 508-879-0042. Your comments about our documentation are appreciated. 1.9 CD-ROM Contents =================== The directory structure on the CD is as follows: [MULTINET043] MultiNet Kit [Documentation] HTML format (.htm) PDF format (.pdf) PostScript format (.ps) TEXT format (.txt) Release Notes TEXT format (.txt) [ECOs] [INFO-MULTINET] [RFCs] [BIND-DOC] [XPDF] [XPDF.AXP] for Alpha images [XPDF.VAX] for VAX images [LYNX] [LYNX.AXP] for Alpha images [LYNX.VAX] for VAX images 1.9.1 Online Documentation ========================== The MultiNet documentation set is available on the product CD in PDF, text, PostScript, and HTML formats. 1.9.1.1 PDF Format ================== The MultiNet documentation set has the following PDF files: Installation MULTINET_INSTALLATION_GUIDE.PDF Administrator MULTINET_ADMIN_GUIDE.PDF Admin Reference MULTINET_ADMIN_REFERENCE.PDF Programmer's Reference MULTINET_PROGRAMMERS_REFERENCE.PDF Messages MULTINET_MESSAGES.PDF User's Guide MULTINET_USER_GUIDE.PDF DECnet Apps MULTINET_DECNET_APPS.PDF 6 The PDF format is readable from a PC, a VAX, or an Alpha system. There is a PDF reader on the CD for each platform. o Use Acrobat Reader to read the PDF files from a PC. Your PC must have 386 architecture or later to use Acrobat Reader. You can get Acrobat Reader from Adobe Systems website: www.adobe.com. It is free! o Use the XPDF Reader (found in the [XPDF] directory) to read the PDF files from a VAX or Alpha system. The [XPDF.AXP] directory contains the Alpha architecture reader XPDF_AXP.EXE. The [XPDF.VAX] directory contains the VAX architecture reader XPDF_VAX.EXE. NOTE: The XPDF Reader does not work on a PC. PCs running the Windows or NT operating system cannot read Process Software's CD. You cannot load files from the MultiNet CD directly to a PC. Load them to your VAX or Alpha machine, then transfer them to your PC. To read the MultiNet CD on a PC, load the files to your VAX or Alpha machine, then transfer them to your PC. We suggest using FTP to transfer these files. The following is an example using MS-DOS: C:> ftp node ftp> binary ftp> mget cd:*.pdf In addition, Process Software has included LYNX, the character-cell web browser for VMS. It is in the [LYNX] directory. 1.9.1.1.1 Using Acrobat Reader ============================== To read the PDF files using Acrobat Reader: 1. Double click Acrobat Exchange. 2. Choose Open from the File menu. 3. Select the .pdf file you want to open. 4. Use the menu bar at the top of the screen to navigate the document or click a Table of Contents entry (on the left) to go directly to that information. Hints: The binocular icon opens search functions. The magnifying glass icon enlarges the text and illustrations. 1.9.1.1.2 Using XPDF ==================== Thanks to Derek B. Noonburg for letting us download his XPDF application. NOTE: You need a three-button mouse to use XPDF. At the DCL prompt from the directory in which XPDF_VAX.EXE or XPDF_AXP.EXE is stored, do the following: 7 1. Type RUN XPDF_VAX.EXE or RUN XPDF_AXP.EXE. The XPDF screen appears. 2. Position the arrow on any of the icons (except the ? icon) on the bottom of the screen. 3. Press the right mouse button to display choices. 4. Select OPEN to display the list of PDF files. 5. Select the PDF file you want and click OPEN to read the file. 6. Use the icons on the bottom of the screen to search for the information you want. To view the online help for XPDF: 1. Position the cursor on the question mark (?) icon. 2. Press the left mouse button to open the online help. 1.9.1.2 HTML Format =================== Online documentation is available as HTML files you can use either with a PC browser or with a character cell browser. The documentation files and their contents are listed next. Document Directory HTML File Contents Title Names =========================================================================== Installation and Introduction INSTALLATION CH1.HTM Installing and Upgrading MultiNet for OpenVMS CH2.HTM Example Installations CH3.HTM Files that may be Added to your System Disk CH4.HTM Removing MultiNet for OpenVMS CH5.HTM MultiNet Documentation and Online Help CH6.HTM Introduction to MultiNet and TCP/IP Concepts CH7.HTM Devices, Protocols, and MultiNet Internals CH8.HTM Getting Additional Information User's Guide USER_GUIDE Ch2.HTM Exploring Your Network Environment CH3.HTM Sending and Receiving Electronic Mail CH4.HTM Using Kerberos Authentication CH5.HTM Accessing Remote Systems with the RSHELL, RLOGIN, and TELNET Utilities CH6.HTM Remote File Access with the RCP, FTP, and TFTP Utilities CH7.HTM Using DECwindows with MultiNet CH8.HTM Accessing Remote Systems with Secure Shell (SSH) Utilities 8 APPA.HTM DCL User Commands APPB.HTM FTP Command Reference APPC.HTM TELNET Command Reference APPD.HTM TFTP Command Reference Administrator's Reference ADMIN_REF CH1.HTM MultiNet DCL Command Reference CH2.HTM MultiNet Secure/IP DCL Commands CH3.HTM DECNET-CONFIG Command Reference CH4.HTM MAIL-CONFIG Command Reference CH5.HTM NET-CONFIG Command Reference CH6.HTM NFS-CONFIG Command Reference CH7.HTM NTYCP Command Reference CH8.HTM ACCESS-CONFIG Command Reference CH9.HTM PRINTER-CONFIG Command Reference CH10.HTM SERVER-CONFIG Command Reference CH11.HTM SNMP-CONFIG Command Reference Administrator's Guide ADMINISTRATOR CH1.HTM Configuration Overview CH2.HTM Establishing IP Connectivity CH3.HTM Configuring MultiNet Services CH4.HTM Configuring Network Routing CH5.HTM Host Tables and DNS CH6.HTM System Clock and Timezone CH7.HTM Configuring Electronic Mail CH8.HTM Printer Configuration CH9.HTM RMT Server and Client CH10.HTM Configuring and Managing FTP CH11.HTM Configuring Remote Systems with RARP, BOOTP, and DHCP CH12.HTM Managing the XDM Server CH13.HTM Configuring the Font Server CH14.HTM Configuring MultiNet SNMP Agents CH15.HTM Configuring MultiNet Kerberos Authentication Service CH16.HTM X11-Gateway Configuration CH17.HTM Configuring DECnet-over-IP Circuits CH18.HTM Configuring the MultiNet NFS Server CH19.HTM Using the NFS Client CH20.HTM Server Configuration Parameters CH21.HTM Configuring the Secure Shell (SSH) Server Programmer's Reference PROGRAMMER Ch2.HTM MultiNet Programming Tutorial Ch3.HTM Socket Library Functions Ch4.HTM QIO Interface APPA.HTM Example TCP Client Program APPB.HTM Example TCP Server Programs APPC.HTM Example UDP Client Program APPD.HTM Example UDP Server Programs 9 TCP/IP Services for DECnet Applications DECNET Ch1.HTM Introduction Ch2.HTM Configuring DECnet Application Services APPA.HTM NOT-CONFIG Commands Messages and Logicals MESSAGES Ch1.HTM Troubleshooting Ch2.HTM MultiNet Messages Ch3.HTM MultiNet Logicals APPA.HTM Utility Return Codes APPB.HTM Error Codes 1.9.1.3 PostScript Format ========================= Online documentation is available in the following PostScript files. Document Directory PostScript Name Title File Names ========================================================================== Installation INSTALL-CONFIG_DOCS MULTINET_INSTALLATION_GUIDE.PS Administrator's ADMIN_DOCS MULTINET_ADMIN_GUIDE.PS Admin Reference ADMIN-REF_DOCS MULTINET_ADMIN_REFERENCE.PS Programmer's PROGRAMMER_DOCS MULTINET_PROGRAMMERS_REFERENCE.PS User's Guide USER_DOCS MULTINET_USER_GUIDE.PS Messages MESSAGE_DOCS MULTINET_MESSAGES.PS DECnet Apps DECNET_DOCS MULTINET_DECNET_APPS.PS Chapter 2 Enhancements and Changes ======================================== This chapter describes the enhancements and changes made for MultiNet v4.3. 2.1 Mandatory VMS Patch ======================= o The patch kit VAXCDUO1_061, or its successor, from Compaq Computer Corporation must be installed for OpenVMS VAX v5.5-2 through v6.1 in order for MultiNet v4.3A to install. Without this patch the following error message will display while installing MultiNet v4.3A: %CDU-F-INTNODESPACE. Internal error: Node space exhausted 2.2 Disabled Services ===================== The following services have been disabled by default for V4.3 for new installations: ACCESS IMAP RLOGIN TELNET VIAPSI CHARGEN LPD RPCPORTMAP TIME CLUSTERALIAS NETSTAT RHELL UDPCHARGEN DAYTIME NOT SMTP UDPDAYTIME DISCARD NTALK SPXTELNET UDPDISCARD ECHO POP2 SNMP UDPECHO FINGER POP3 SYSTAT UDPTIME FTP REXEC TALK VIADECNET These disabled services can be enabled using $ MULTINET CONFIGURE/SERVER. 10 The following service has been eliminated: SNMPTRAP The following service has been added: SSH This service is disabled by default. NTDS is not supported. If you need NTDS, contact Process Software Technical Support. Process Software recommends using NFS or PATHWORKS (advanced server). 2.3 Logical Name Changes ======================== o The FTP server has changed the logical name MULTINET_ANONYMOUS_PASSWORD to MULTINET_FTP_ANONYMOUS_PASSWORD. If your FTP_SERVER.COM uses the definition of MULTINET_ANONYMOUS_PASSWORD to determine whether or not the login is anonymous, you should change it to MULTINET_FTP_ANONYMOUS_PASSWORD. 2.4 Enhancements ================ Devices o IP over Galaxy Shared Memory interfaces are now supported. Configuration is the same as any Ethernet or FDDI (se) device. o MULTINET SET /INTERFACE will now set the MTU of an interface automatically to the maximum byte size revealed by the VMS Device, if available. This allows for more devices to get their proper MTU setting automatically, without defaulting to 1500 or having to be set by the system manager with the /MTU qualifier. Paired Network Interface on a Common Ethernet Cable MultiNet v4.3 has been enhanced to include support for systems that have multiple interfaces on a common Ethernet, FDDI, or Token Ring cable. Configure this support using the following MULTINET SET/INTERFACE command: $ MULTINET SET/INTERFACE xxx/COMMON_LINK=(yyy,[zzz...]) With this command MultiNet links the interfaces internally. A performance benefit of this linking occurs if data is to be transmitted on an interface that happens to be busy; MultiNet assigns the data to the least busy linked interface for transmission. This linking also provides a level of redundancy. If a linked interface is shut down using MULTINET SET/INTERFACE/DOWN or if a fatal error is detected with the interface and an automatic restart cannot be attempted, then any routing table entries or pseudo devices associated with the shut down interface will be failed over to one of the common link interfaces. Restrictions: - The joined interfaces must be connected to the same cable. - The joined interfaces must have the same MTU. 11 SSH o MultiNet Secure Shell (SSH) server and client have been added in v4.3. MultiNet v4.3 SSH supports SSH version 1 only. Both the server and the client allow secure interactive connections to other computers in the manner of rlogin/rshell/telnet. Refer to Chapter 21 of the MultiNet for OpenVMS Administrator's Guide for information on how to configure the SSH server. Refer to Chapter 8 of the MultiNet for OpenVMS User's Guide for information on how to configure the SSH client. o You must install the DEC C 6.0 backport library on all OpenVMS VAX v5.5-2 and v6.0 systems prior to using SSH. This is the AACRT060.A file. You can find the ECO on the MultiNet CD in directory: VAXI5_DECC_RTL.DIR. o When using the SSH server on a OpenVMS VAX v5.5-2 system, the number of failed login attempts and the last interactive login fields within SYSUAF.DAT will not be updated during SSH sessions. This is a limitation of the OpenVMS v5.5-2 operating system. In addition, the following message will be generated in the SSHD.LOG files generated on OpenVMS VAX v5.5-2 systems: "Failed to update failed login count: 20" This message may be ignored. o When performing the following sequence using Process Software's SSH client, 1. Log into an OpenVMS system from another OpenVMS system using SET HOST. 2. From that system, use SSH to another host. the following message appears when you terminate SSH: SENSEMODE:%SYSTEM-F-ABORT, abort Apparently, this error is an internal OpenVMS error for which Process Software has neither a fix nor a workaround. DHCP v.3 o DHCP has been upgraded to ISC DHCP v3.0 which contains the following new features: Conditional behavior Client classing Per-class limits on the number of addresses assignable More than one pool of addresses per network segment allowed DHCPINFORM messages supported Vendor-specific data option User-defined options, including site-specific options Relay agent options o ISC DHCP version 3 includes the ability to handle unknown clients differently from the known clients, the ability, for example, to deliver a different set of options based on the first three octets of a given clients Ethernet address and more. 12 o The following config file statements have been added, in addition to the ones related to the new features listed above: min-lease-time min-secs always-broadcast one-lease-per-client allow dynamic-bootp; deny dynamic-bootp; o A new command line flag -T on dhcpd.exe is available to verify the syntax of the lease file in addition to the configuration file. o The default for "authoritative" has been changed to "not authoritative". If you want the MultiNet v4.2 behavior, you will have to add "authoritative;" to the top of your configuration file. o The default for "allow/deny dhcpinform" is now "allow" for authoritative subnets and "deny" for not-authoritative subnets. If you want the MultiNet v4.2 behavior (always allow), you will have to add "allow dhcpinform;" to the top of your configuration file. o The MultiNet v4.2 statements "vendor-class" and "user-class" have been supplanted by the more powerful "class" and "subclass" statements (see Chapter 12 of the Administrator's Guide for more information). o The DHCP configuration file command "unicast-bootp-reply" which was introduced in an ECO for MultiNet v4.2 is not recognized in MultiNet v4.3. It is no longer needed because the DHCP code will unicast BOOTP (and DHCP) replies whenever possible. There is a new config file statement "always-broadcast" to tell the DHCP server to broadcast instead of unicast. Note that the DHCP server now honors the broadcast flag as sent by the client. o The DHCP server now defaults to logging to the file MULTINET:DHCPDEBUG.LOG if you turn off logging to OPCOM by setting the LOG-TO-OPCOM server parameter to 0. Please be aware of this new default. You can override the file name and location by setting the DEBUG-FILE server parameter. o The DHCP V2.0 (MultiNet V4.2) style allow and deny statements (e.g. allow/deny unknown-clients;) do not mix well with the DHCP V3 (MultiNet V4.3) pool permit lists (e.g. allow/deny unknown clients). A V2-style deny statement overrides the pool permit lists, and the dynamic-bootp keyword on the range statement is ignored inside of pools. o The default for allowing dynamic bootp assignments of IP addresses changes from DENY for range statements outside of pool statements (the MultiNet 4.2 way) to ALLOW for range statements inside of pool statements. If you want the default to be DENY for pool statements, you have to add "deny dynamic-bootp;" to the top of your configuration file. Note that if you do this, it will override completely the "allow dynamic bootp client" and "deny dynamic bootp clients" permit lists in all of your pools. 13 DHCP v.3 (cont'd) o The new pools and classes are displayed by various NETCONTROL SHOW commands. See the Administrator's Reference, Chapter 1. o There are new entries in the lease file to record lease-limited classes. DNS o The DNS server has been updated to ISC BIND version 8.2.3. The key benefits within BIND 8.2 include efficiency mechanisms such as incremental zone transfers and forward type zone support. o The BIND 8.2.3 nameserver has the following new features: -- Support for the following RFCs: RFC 2308 (Negative Caching) RFC 2181 (DNS Clarifications) -- Split DNS via zone type "forward" -- New zone file directives $TTL and $GENERATE -- Incremental Zone Transfer (IXFR) -- Zone transfers can be done from an alternate port by specifying the port on the "masters" statement -- Security measures based on DNSSEC and split DNS support -- Transaction Signatures (TSIG) -- Multiple methods of sorting multiple Resource Records (sortlist) -- Zone transfers can be done from an alternate port by specifying the port on the "masters" statement. o For MultiNet 4.3, the file names generated for Dynamic zone log files and incremental zone transfer (IXFR) files has been changed. If you have files in your DNS directory with names such as filename_filetype.log filename_filetype.ixfr filename_filetype_ixfr.tmp and you want the nameserver to continue using them, you need to rename them as follows so the server can find them. filename.filetype_log filename.filetype_ixfr filename.filetype_ixfr_tmp The method for generating these file names has been changed to support longer file names. o The MultiNet v4.2 nameserver sorted A, NS, and MX records in a round-robin order, and used a fixed order for other record types. The v4.3 nameserver by default sorts all record types in round-robin order. To get the same behavior as v4.2, put the following lines into the options section of your NAMED.CONF file: rrset-order { class IN type A name "*" order cyclic; class IN type NS name "*" order cyclic; class IN type MX name "*" order cyclic; order fixed; }; 14 o The "sortlist" directive from BIND 4.x has been brought back in BIND 8.2.x. In order to get the sorting behavior similar to the default sorting behavior in BIND 4.x, that is, list IP addresses on local networks first, you must put the following lines into the options section of your NAMED.CONF file: sortlist { { localhost; localnets; }; { localnets; }; }; o The MULTINET:NAMED_CONF.DEFAULT file that was shipped with MultiNet v4.2A had an error. If you have a NAMED.CONF file based on 4.2's NAMED_CONF.DEFAULT, change the following line in the "localhost" zone: file "MULTINET:DOMAIN-NAME-SERVICE.LOCAL"; to file "MULTINET:DOMAIN-NAME-SERVICE.LOCALHOST"; o The meaning of the last field in the SOA record has changed for BIND 8.2.x. It is now used as a negative caching time-to-live (TTL) value instead of a default TTL. A new $TTL directive has been defined for zone files to specify the default TTL. You should add a $TTL line to the top of each of your zone files to specify the default time-to-live. If your zone files do not contain a $TTL directive, you will see the following warning and the nameserver will perform the old behavior of using the last SOA field as the default TTL: named: Zone "" (file ): No default TTL ($TTL) set, using SOA minimum instead o If you have a zone containing CNAME records and other type records for the same name, that zone is rejected by the 8.2.x nameserver with a "CNAME and other data" error. In previous versions of BIND, this was just a non-fatal warning. You must modify your zones to remove the CNAME or other type records. The error messages are: named: has CNAME and other data (invalid) named: ::: CNAME and OTHER data error named: master zone "" (IN) rejected due to errors (serial ) SNMP o A new SNMP agent is included with this version of MultiNet. It provides the ability to use subagents. o SNMP Subagents - this feature gives you the ability to write your own subagents o Enabling SMUX (DEFINE/SYSTEM/EXEC MULTINET_SNMP_SMUX 1) when there are no SMUX subagents to use it can interfere with walking of the SNMP management base due to the SMUX MIB returning NoSuchName when no subagents exist. SMUX is an historical protocol, and should not be enabled unless there are subagents that will be using it. Specific items in the SNMP management base that appear after the SMUX MIB can still be queried when they are accessed from the start of their management base. 15 o SNMP parameters can not be modified with the SNMP-CONFIG or MENU-CONFIG utilities. The MULTINET CONFIGURE/SNMP and MULTINET CONFIGURE/MENU commands are not supported with MultiNet v4.3 and beyond. o To reload the SNMP configuration using NETCONTROL: $ MULTINET NETCONTROL SNMP RELOAD o Agent X has been added to MultiNet in v4.3. Agent X is a standardized protocol (RFC-2257) allowing the list of managed objects available from an SNMP agent to be dynamically extended. Having the extension mechanism outside the SNMP agent has many benefits, among them: -- Allows extensions to be started and shutdown independently of the main SNMP agent. -- Allows the main SNMP management agent to be developed and maintained independently of the extensions. -- Allows management to be done close to the item being managed. The item being managed can be either hardware or software. -- Protects the SNMP agent from errors in a single extension shutting down all SNMP management. The new ESNMP client interface in Compaq's TCP/IP services v5.1 uses Agent X to allow others to provide additional objects for SNMP to manage. Compaq's Insight Management Agents for OpenVMS are written to use the ESNMP client interface, hence the addition of Agent X protocol allows them to be used with MultiNet. By using the ESNMP library, or Agent X directly, writers of TCP/IP services can allow the state of the service to be queried and controlled remotely. This can be useful if the service does not have a user interface, or runs under batch, or as a detached process. o Compaq Insight Manager support has been added to MultiNet for v4.3. The Compaq Insight Manager (CIM) uses the SNMP extensibility provided by Agent X to allow remote examination and notification of system conditions that may need attention. Remote management agents like CIM allow systems administration personnel to manage more systems while still meeting response time goals by providing access to critical information from a central location. The remote management agent communicates with the SNMP agent on the system being managed, which then sends the request to a program specifically designed to manage a particular component of the system. Customers desiring to run Compaq Insight Manager (v7.1 and later of OpenVMS for Alpha) will need to obtain TCP/IP Services v5.1 for OpenVMS from Compaq in order to get the TCPIP$ACCESS_SHR.EXE, TCPIP$ESNMP_SHR.EXE, and TCPIP$HR_MIB.EXE images. Contact Compaq (compaq.com) to get the field test kit for TCP/IP Services v5.1. 16 Compaq Insight Manager is available on AXP systems with VMS v7.* only. Please follow these instructions. 1. Install MultiNet v4.3 2. Add the following line to MULTINET:SNMPD.CONF: AGENTX_PEER 127.0.0.1 3. Extract TCPIP$ACCESS_SHR.EXE and TCPIP$ESNMP_SHR.EXE (PRODUCT EXTRACT FILE/SELECT=) from the TCPIP Services kit and place them in SYS$SHARE:. 4. Copy TCPIP$ESNMP_SHR.EXE to SYS$SHARE:UCX$ESNMP_SHR.EXE 5. Extract TCPIP$HR_MIB.EXE from the TCPIP Services kit and place in SYS$SYSTEM: $ DEFINE/SYSTEM/EXECUTIVE MULTINET_SNMP_AGENTX 1 $ DEFINE/SYSTEM TCPIP$AGENTX_INET_PORT 705 $ DEFINE/SYSTEM TCPIP$AGENTX_LOCAL_PORT 705 6. Start MultiNet 7. Start Compaq Insight Manager 8. Run /process=HR_MIB SYS$SYSTEM:TCPIP$HR_MIB The Host Resources MIB (RFC 1514) supplied with TCP/IP Services will now work with MultiNet's SNMP. To enable it, extract the file TCPIP$HR_MIB.EXE from the TCPIP Services kit and place in SYS$SYSTEM. Define MULTINET_SNMP_AGENTX, TCPIP$AGENTX_INET_PORT and TCPIP$AGENTX_LOCAL_PORT as mentioned in setting up the Compaq Insight Manager, and RUN/PROCESS=HR_MIB SYS$SYSTEM:TCPIP$HR_MIB. 2.5 Changes =========== This section describes the changes made in this release. IP AddressWorks Process Software no longer supports IP AddressWorks. For help with IP AddressWorks, call the IPWorks, Inc. tech support number at 1-888-626-3356. IPWorks, Inc. is the owner of IP AddressWorks. REMIND o This has been modified to send LEAP-DAY reminders only in leap years. (D/E 6035) Kernel o Fixed a crash due to a value not being stored in a local variable that determines what code path may be taken. (D/E 3204) o System no longer bug checks when trying to load a large packet filter file. (D/E 3949) o The MultiNet Kernel now uses hashing to maintain the TCP connection tables rather than linked lists. This change is a major performance improvement on systems with many active TCP connections. (D/E 4285) 17 XNTP MultiNet no longer supports NTP. XNTP is the new application for running network time protocol functions. It is the latest version of NTP and complies with RFC 1305. You need to update your system to use XNTP. If you are running NTP now, you must convert existing NETCONTROL parameters to the NTP.CONF file for use with XNTP. To convert from NTP to XNTP, use the conversion tool called CONVNTP. To use CONVNTP, do the following from the SYSTEM account: $ SET DEFAULT MULTINET $ @CONVNTP The following conversions are made: NTP parameter XNTP keyword XNTP file ------------- ------------ --------- peer peer NTP.CONF passive peer NTP.CONF server server NTP.CONF trusting trustedkey NTP.KEYS In addition, if the "configuration-file" parameter is encountered, a warning message is printed, informing you that this file must be examined manually, and its contents added to the NTP.CONF file as necessary. All other NTP parameters are ignored. NOTE: Each time CONVNTP is executed, it creates a new NTP.CONF file (and, as required, NTP.KEYS). An example run would look like: $ @MULTINET:CONVNTP New MULTINET_SPECIFIC_ROOT:[MULTINET]NTP.CONF created New MULTINET_SPECIFIC_ROOT:[MULTINET]NTP.KEYS created $ An example where the "configuration-file" parameter is encountered: $ @MULTINET:convntp *** *** A separate configuration file multinet:ntp.configuration *** was specified as an NTP parameter. This file should be *** examined to determine if its contents should be *** incorporated into the new NTP.CONF file. *** New MULTINET_SPECIFIC_ROOT:[MULTINET]NTP.CONF created $ A system running XNTP will interact with other systems, either clients, servers, or peers that are running NTP just fine. XNTP servers/clients exchange version information with each other and operate with the lowest common denominator. 18 Note that NTP is still on the distribution, but Process Software strongly encourages the conversion of NTP to XNTP for all customers. Therefore, you will not have to make an immediate and total cutover all at once for all systems. CONVNTP is designed to create the configuration file required by XNTP, by converting entries such as PEER, PASSIVE, SERVER and TRUSTING. It will not modify statements like DEBUGLEVEL and WAYTOOBIG; those parameters are set for XNTP via the MULTINET NETCONTROL XNTP commands. DECnet o Phase/IP no longer fails under MultiNet v4.2A when trying to SET HOST 0 after installing. (D/E 3884) UCXDRIVER o Closing a socket that was involved in a select did not clean up all the internal data structures. This could lead to dangling pointers and occasional crashes. This has been corrected. (D/E 991) o MultiNet now cleans up after vectored operations when removing pending reads/writes in CANCEL operations. (D/E 5367) o MultiNet now works with the Apache web server without requiring the web server to run with privileges. (D/E 5730) o Handles the DEC C values of the following set/getsockopt() socket options (which differ from the UCX values already supported): (D/E 5731) IP_TOS IP_TTL IP_MULTICAST_IF IP_MULTICAST_TTL IP_MULTICAST_LOOP IP_ADD_MEMBERSHIP IP_DROP_MEMBERSHIP o A memory corruption in the UCXDRIVER has been fixed in the ACCEPT processing. (D/E 5616) o The UCX device (BG) now supports an IP address being passed to the gethostbyname subfunction of IO$_ACPCONTROL. (D/E 4892) o Reading zero bytes on a BG device now returns a successful status instead of SS$_BADPARAM. This fixes a problem found with the interaction between Mozilla M15 and MultiNet. (D/E 6216) o Support for the BSD 4.4 style sockaddr data structure has been added to the BGDRIVER (UCX interface). If any of the following I/O functions have the IO$V_EXTEND bit set, then the sockaddr structure passed is assumed to be in BSD 4.4 format. IO$_READVBLK (when P3 is specified for an UDP or raw IP message) IO$_WRITEVBLK (when P3 is specified for an UDP or raw IP message) IO$_ACCESS (connect) IO$_ACCESS | IO$_ACCEPT (Accept) IO$_SENSEMODE (GETSOCKNAME, GETPEERNAME) IO$_SETMODE (BIND) 19 Operations that return a sockaddr (READVBLK (read_from), ACCEPT, GETSOCKNAME, GETPEERNAME), will return the sockaddr in BSD 4.4 format. Operations that accept a sockaddr (WRITEVBLK (send_to), connect, BIND) will expect the address family value to be in the position that is in for the BSD 4.4 structure. When a CONNECT/BIND /ACCEPT operation is done for a TCP connection using the IO$V_EXTEND bit set, it is remembered for the duration of the connection. All sockaddr structures are expected to be in BSD 4.4 format when they are specified. Operations that return a sockaddr will return it in BSD 4.4 format. For IO$_ACCESS (connect) and IO$_SETMODE (BIND), if the portion of the sockaddr structure that is used to specify the address family in BSD 4.4 format is non-zero, then the sockaddr structure is assumed to be in BSD 4.4 format. (D/E 5901) NOTDRIVER o The NOTDRIVER no longer bugchecks the system if certain invalid arguments are passed to it. (D/E 3780) INETDRIVER o Some versions of DECC$SHR have problems with printf() when SYS$OUTPUT points to a device with the Default Buffer Size of 65535. If you have an application as a service registered with the master server using printf() to send the data back down the connection, DECC$SHR will go into an infinite loop down in the printf() code. MultiNet now provides an INETDRIVER with the default buffer size of 65534 to work around the problem. (D/E 5866) NSLOOKUP o The NSLOOKUP command set port= now works on the VAX platform. (D/E 4841) o A /PORT qualifier has been added to the MULTINET NSLOOKUP command to specify an alternative port to use instead of the standard port 53. This is equivalent to specifying the nslookup "set port" command. o The format of the output of the "ls" command has been improved. If you have any command procedures that parse the output of the "ls" command, they will have to be changed. 2.5.1 Server ============ NFS o The NFS_SERVER process no longer crashes the system (while in KERNEL mode) when a CREATE request is received under certain circumstances. (D/E 5057) o There is no longer a delay in file creation due to the timing of system IO completion. (D/E 5031) o The NFS_SERVER process no longer incorrectly truncates files when it processes write requests out of sequence. (D/E 4246) o During large file transfers a consecutive series of blocks could be overwritten with NULLs starting at a random 16-block boundary. This has been fixed. (D/E 4634) 20 o The NFS_SERVER process no longer crashes the system (while in KERNEL mode) if a request to access a file coincides with a concurrent access which is converting the file to stream, causing the second request to wait. (D/E 4045) o Request Scheduling has been fixed which will eliminate potential corruption and bugcheck problems. RCD o The RCD server no longer issues an "illegal block number" message. (D/E 4384) DNS o A problem where the nameserver would hang indefinitely if reloaded has been fixed. This occurred when the server was finished sending the data for a zone transfer, but the client requesting the zone transfer had not yet closed its end of the connection. System managers experiencing this problem may notice lingering TCP connections to the domain port on the system in FIN-WAIT-2 state. If this is a problem it is recommended the system manager take steps to disallow that remote system from doing zone transfers [see the documentation on the allow-transfers statement in the NameD configuration]. (D/E 4901) o A timing window that could cause nameservers to prematurely terminate large outgoing zone transfers has been corrected. (D/E 5478) o A timing issue has been corrected where the nameserver could hang intermittently until another TCP connection is received. (D/E 5175) o A timing window existed that could potentially cause the nameserver to abort with errors similar to d_rcnt-- == 0 or db_freedata: DB_F_FREE set This has been corrected. (D/E 6283) o MULTINET NETCONTROL DOMAIN RELOAD queues a reload request with the nameserver. On nameservers with no incoming queries, it could take up to 15 minutes before the nameserver would do the reload. Otherwise, the reload would occur when it received the next query. The code has been reworked so that reloads should occur shortly after issuing the reload command. (D/E 6221) o Secondary servers no longer create a new version of the backup zone file when they transfer the zone; now, they replace the old file with the new file. Customers are encouraged to check the directories where their backup zone files are stored and purge the excess from MultiNet v4.2, if desired. (D/E 5207) o If you specify "versions" on the "file" statement in the NAMED configuration file, the NAMED server creates a new version and maintains the specified number of versions. If "versions" is not specified, NAMED performs the v4.2 behavior of appending to the existing file. Also, log files are now flushed to disk periodically. The "size" parameter of the "file" statement is supported now. (D/E 4519, 4520) 21 For example: logging { channel queries_log { file "multinet:queries.log" versions 3 size 20K; /*bytes*/ severity info; } category queries { queries_log; }; } o If logging has been configured to have multiple channels to the same log file, there is no longer an access violation from the server when a message is sent to the second channel. (D/E 3911) o Outgoing TCP connections from the nameserver are now non-blocking. (D/E 6177) o When the nameserver sends zone transfer data to a secondary server, and the zone contains NS records for a subzones that is delegated to a cluster alias name, the nameserver includes a glue record that relates to the IP address of the master server only, not to all the cluster members. While this problem has been corrected, and the primary server will not include glue information for NS records that delegate to cluster alias addresses, delegating a zone in this fashion is not recommended. Administrators should have NS records referencing each member of the cluster directly; one NS record for each authoritative server in the cluster, rather than using one NS record that references the cluster alias name. (D/E 3793) DHCP o The DHCP server was not parsing option 81 (Client-FQDN) correctly if the client sent it in the DHCPDISCOVER or DHCPREQUEST message. This caused memory leaks that used up all pagefile quota and caused the DHCP server to exit with insufficient memory. This has been fixed. (D/E 4978) o When using DHCP Safe-failover, a lease pool could get used up and report the following error: "no free leases on subnet". The reclaiming of expired leases has been improved when Safe-failover is in use. (D/E 4983) o The DHCP server could crash if a client sent option 81 (client FQDN) and the configuration file did not have a domain name option specified for the client. This has been fixed. (D/E 5615) o The DHCP server no longer exits with the following fatal errors: PSCDHCPD-E-Abandoning IP address x.x.x.x: pinged before offer PSCDHCPD-E-dhcp_reply was supplied lease with no state! PSCDHCPD-F-exiting. (D/E 5539) o For statically assigned IP addresses, the DHCP server no longer performs unnecessary dynamic DNS updates upon a renewal of the lease. (D/E 5474) o When using DHCP Safe-failover, the sending of DHCPOFFERs could be delayed. Delays no longer occur. (D/E 5570) 22 o When using DHCP Safe-failover, the following error displayed during normal operations: PSCDHCPD-E- -> update's expiration seems obsolete:xxxxxxxx The error no longer appears. (D/E 5371) o For DHCP Safe-failover, the following statement has been added to the lease file: last-partner-transaction ; This indicates the last time the failover partner modified the lease (for example, renewed it). The 'starts' time indicates when this server itself last modified the lease. (D/E 5442) o The DHCP server no longer hangs if the following error appears: PSCDHCPD-E-receive_packet failed on xxx: I/O stream empty (D/E 5610) o The "deny ras-servers;" configuration file statement supports the latest Microsoft(R) NT RAS servers (Windows 2000). (D/E 4441) o Sites with large numbers of subnets or IP addresses could get the following error: "Error: output buffer overflow, data truncated" on various NETCONTROL DHCP SHOW commands. This has been fixed. (D/E 6272) o If a DHCPRELEASE was received through a relay agent, the debug message indicating its arrival now prints both the released IP address and the relay agent IP address correctly. (D/E 4441) o The following configuration file parameter has been added: max-delayed-acks ; To improve performance under heavy loads, the DHCP server delays sending DHCPACK messages by up to 2 seconds. All DHCPACKs accumulated in that time are sent in a batch. The max-delayed-acks parameter specifies the maximum number of DHCPACKs to batch up. The default is 8. To disable the delaying of DHCPACKs, specify a value of 1. (D/E 4294) o The DHCP server conversion tool now correctly creates 'subnet' statements in the new configuration file (DHCPD.CONF) for the IP addresses in the old BOOTP configuration file (BOOTP-SERVER.CONFIGURATION). (D/E 3831) o The DHCP server could access violate while in Safe-failover mode, when processing a Binding Update from the peer. This has been fixed. (D/E 5592) o When using DHCP Safe-failover, the numbers reported by the NETCONTROL commands SHOW POOLS and STATISTICS are no longer incorrect and possibly negative. (D/E 5791) 23 o MultiNet v4.3 has the following new hostname generator key: %P Printable characters from the Client ID. For example: if the client ID was 0174657374, the 01 is thrown away and the resulting hostname is "test". (D/E 6267) o The MultiNet v4.3 DHCP server has three different options for handling invalid hostname characters for Dynamic DNS updates (DDNS): -- fail (the v4.2 behavior) -- discard the invalid characters -- replace the invalid characters This behavior is specified using the following DHCPD.CONF command: invalid-ddns-chars { fail | discard | replace [""] }; If 'invalid-ddns-chars replace;' is specified without what character to replace the invalid characters with, the default replacement character is the hyphen ('-'). (D/E 5590) o With very long lease lengths (for example an infinite lease), the lease end time could be incorrectly shown as Jan 1, 1970. This has been fixed. (D/E 6325) FTP o The FTP server displays the creation month, day, and year of a file for a UNIX mode directory if the file is older than 1 year (365 days). If the logical MULTINET_FTP_UNIX_YEAR_OLD_FILES is defined as False, No, or 0 (zero), the old behavior is restored, displaying all files with Month, Day, and Time. (D/E 4644) o The FTP client now sends RESET when disconnecting due to a timeout, rather than sending RESET when the user closes the connection with a client command. (D/E 6223) o The DELETE command now accepts wildcarded filenames. When a wildcarded name is specified, the names of all the deleted files may not be reported in the response message. (D/E 885) o A problem with GETting files in image mode with a fixed length record of an odd number of bytes has been corrected. (D/E 4774) o A problem where a possible denial of service attack would occur in the FTP server has been corrected. (D/E 5346) o A problem has been corrected that caused the FTP server to crash when deleting or renaming a file on VMS v7.2 with the logical MULTINET_FTP_UNIX_STYLE_BY_DEFAULT being set. (D/E 4545) o The FTP client program translates UNIX-style filenames in an MGET operation (which may contain directory information) into VMS-style filenames. If directory information is present it is removed and the files are stored in the local directory. (D/E 3362) 24 o The FTP client has been modified to assume /ANONYMOUS for DIR/FTP and COPY/FTP. This gives the desired effect (to assume /ANONYMOUS) when a username and password are not specified, and improves the error message when anonymous is disabled. (D/E 1580) o The following commands have been added to the FTP server: SIZE and MDTM. The 150 reply line returned by the server at the start of the RETR (get) command transfer phase has been modified to include an estimate of the number of bytes to be transferred. (D/E 5005) o The new logical MULTINET_FTP_DELAY_TRANSFER_NEGOTIATION causes a delay in negotiating the STRU O VMS transfer mode until after successful login. (DE 5624) o The FTP server now returns a 552 status when a wildcard specification to an NLST command returns no files. The result of this is that an MGET to a directory with no matching files will now return a 552 status instead of showing a transfer complete code of 226. (D/E 2317) o The following system logical has been added to limit the information given out on connection and when using the STAT command. MULTINET_FTP_CONNECT_BANNER This system logical replaces the banner issued in an FTP connect with the value of the logical. If the system logical is defined to be just white space, operating system and TCP stack vendor information will be removed from the FTP server connection banner. If this system logical is defined at all, the information banner will not be presented in response to the STAT command. (D/E 3078) o The parameters used to open a file that is transferred via a GET operation in FILE or RECORD format have been modified to allow a greater level of sharing. STRU FILE and STRU RECORD are often used when accessing the system from a non-VMS system. The default for an FTP client written for VMS is to negotiate STRU VMS mode (which allowed the transfer). Note: Although the file can now be transferred in all modes, there is no guarantee of the quality of the data if the file is open currently for write access by another process. Users GETting files they believe might be open for write access by another process should attempt to get the other process to an inactive state before GETting the file and proceed with caution when processing the data that was transferred. (D/E 5839) o Directory listings of files on ODS-5 disks where erroneously being translated to UNIX file names when in UNIX mode. Since no transla- tion is done on file open/create for ODS-5 disks, translating on listings can be confusing and problematic. (D/E 6172) o Some errors in processing filenames on ODS-5 disks when operating in UNIX mode have been corrected. When the default disk is an ODS-5 disk and the FTP server is operating in UNIX mode, the FTP server only translates the file specification from UNIX format to VMS format when there is a slash (/) in the file specification. (D/E 6316) 25 o The FTP client has been modified to display the elapsed time in HH:MM:SS format if the logical MULTINET_FTP_STATISTICS_IN_HHMMSS starts with 1, T (true), or Y (yes). (D/E 1113) o The format of the directory string displayed by CD, PWD, STATUS, and at initial login has changed when the FTP server is operating in UNIX mode. The trailing / (slash) has been removed. (D/E 6420) OPCOM o OPCOM messages generated by the exiting and restarting of the NAMED_SERVER and the SERVER MANAGER (SM) now go to the NETWORK operator only. (D/E 5286) NTY o Corrected a problem where the connection to the remote printer was not being closed in all cases once the print job had been sent. The failure to close the connection could prevent a printer from accepting jobs from other sources. (D/E 4287) o Corrected the problem that caused queues to remain in a "busy" state with the top or first job remaining in a "starting" state. Also, corrected redundant reporting of completed operations. (D/E 3694) o Corrected the problem with processes which do not terminate when all associated queues have been stopped. Also known as "Lingering Symbionts". (D/E 2925) o We recommend you restart the queue manager to clear any existing state misinformation. o NTYSMB no longer has a queue manager problem with its reporting operation while it is in the process of stopping queues. o NTYSMB now produces a single report of completed operations. o Enhanced debug logging in the following way: -- If you define the MULTINET_NTYSMB_DEBUG logical to a numeric, non-0 (zero) value, it is used as a bit-mask. Bit 0 (zero) enables debug logging. Bit 2 causes the log to be flushed to disk after every write. -- If you define the MULTINET_NTYSMB_DEBUG logical as a non-numeric value, the symbiont treats it as if it is defined as 7. o Errors closing the NTY device and its associated connection are now treated as errors. o Support has been added for the POSTWAIT configuration logicals. When defined, the symbiont pauses at the end of each job, before initiating the connection for the next job. This allows the remote end extra time to complete processing and negotiation of the connection close between jobs. The delay time is specified in seconds, with a default value of 0. $ define/system/exec multinet_ntysmb__postwait 7 should be replaced with the actual name of the print queue you are configuring, or * to indicate all NTYSMB queues. 26 o Corrected a problem where, under certain timing and error conditions, data could be sent out of order. This could result, for example, in the job's setup module being sent after some portion of the job has already been printed. (D/E 4287) o MULTINET_VMS_SHAREABLE image no longer crashes on a VAX if you have a large number of NTY devices and run NTYCP> sho port and will not display garbage output on either Alpha or VAX when executing NTYCP> sho port. (D/E 3824) o Page length in forms definition does not change NTY characteristics. (D/E 6410) o The potential for creating BADLOGIC errors and associated symbiont process dumps have been eliminated. (D/E 6415) PRINTING o MULTINET CONFIGURE/PRINTERS no longer causes an access violation when you forget to enter a remote host name when adding a remote printer queue. (D/E 3718) o Support has been added for options which force a linefeed at the end of each print job, rather than a carriage return. This feature is useful when continuous feed stock is used in conjunction with /NOFEED options. Without this option, existing applications may exhibit output "creep" unless modified. To set this option as the global default: $ define/system/executive MULTINET_LPD_SYMBIONT_LFTAIL "Y" This can also be used on a per-printer basis with the MULTINET_NLPx_REMOTE_PRINTER option "LFTAIL=Y" or "LFTAIL=N". (D/E 3525) o The MultiNet REMOTE-PRINTER-QUEUES.COM command procedure (generated by MULTINET CONFIGURE/PRINTERS) now includes checks for the architecture of the system the procedure is executed on, and uses the appropriate driver loading commands for the architecture (SYSGEN on VAX, SYSMAN IO on Alpha). This allows REMOTE-PRINTER-QUEUES.COM to be used on either architecture. (D/E 5353) o Modified the STREAM symbiont to use an asynchronous gethostbyname rather than the synchronous call. This resolves the problem of other queues being serviced by a given symbiont process stalling when the DNS translation takes an unusually long period of time. (D/E 4268) o A problem with the stream symbiont dumping when it encountered a remote printer specification whose DNS name would not translate was corrected. (D/E 3349) o You can now configure a "description" for each print queue using the MU CONFIG/MENU interface. (D/E 4775) 27 o You can now use the wildcard ("*") for the queue name with the RETAIN_CR configuration logical. (D/E 4903) For example: $ define/executive/table=multinet_printer_table - _$ MULTINET_PRINTER_*_RETAIN_CR_DEFAULT "Y" MASTER SERVER o The Master Server no longer access violates when restarting a hung or non-existent NAMED_SERVER process. (D/E 5192) o A PCNFSD problem which caused the Master Server to crash when the server ran out of pagefile space has been corrected. (D/E 3069) o On systems with extremely high numbers of connections, UDP connections to the default nameserver are cleaned up if the connect fails. (D/E 4119) o A potential buffer overflow in the Master Server that could cause a stack corruption has been corrected. (D/E 4340) o An uninitialized debug variable has now been initalized. o A potential rpc.statd buffer overflow that could corrupt the master server's stack has been corrected. (D/E 5847) RSERVICES o A performance enhancement has been made. (D/E 6373) SMTP o A problem preventing proper processing of the host aliases file has been corrected. (D/E 3519) o The MultiNet SMTP symbiont no longer exits prematurely when processing some mail. (D/E 3921) o MULTINET SMTP no longer starts a queue manager without knowing where to put the queue manager data files and without notifying the queue manager. Now, a message displays before starting the queue manager and the data files are placed at QMAN$MASTER if that has been defined. (D/E 3904) o A problem that resulted in bad addresses being formed when a mail forwarder was specified has been fixed. (D/E 4571) o The code has been improved to make it more tolerant of syntax errors in alias files like MULTINET:SMTP_ALIASES. to prevent them from having an access violation. (Syntax errors may still cause mail to not be delivered as intended.) (D/E 6235) o Added the following system logical to the SMTP server to limit the information given out on connection, HELP, and QUIT. MULTINET_SMTP_SUPPRESS_VENDOR This system logical removes operating system and TCP stack vendor information from SMTP server text responses. (D/E 3077) 28 o Corrected an error with the RFC822 header example in the SMTP_SERVER_REJECT template. The "Message-ID:" now reads ":Message-ID:". o Added a rule for Unix-to-Unix CoPy (UUCP) "bang" style relaying (*!*@*) in the SMTP_SERVER_REJECT template to reject UUCP relay attempts immediately. o The <> rule in the SMTP_SERVER_REJECT template (allowing bounced mail messages with null MAIL FROM: strings) was misleading. This line has been commented out of the template. The example has been corrected and a better default rule was placed in the file allowing for null MAIL FROM: messages to be sent out from internal IP addresses. o Old MultiNet Mail code had some cases where its routines could get passed parameters that were not properly initialized. These have been fixed. Debugging messages that were left in accidently have been removed. (D/E 4142) o The MULTINET_SMTP_MAXIMUM_822_TO_LENGTH logical can be used to override the 1024 byte default length of the To: and Cc: header fields. The upper limit of the range the logical can be set to has been changed from 5122 to 65535. (D/E 6089) o An error which could cause the forwarder not to be appended to the MX list has been corrected. This could cause mail to not get delivered when there are no MX entries and the site is just relying on the value of the forwarder to provide the first step in delivering the mail. (D/E 6246) o MultiNet v4.3 provides a new version of the SMTP symbiont that resolves names out of either the HOSTS file or DNS. (D/E 6266) SNMP o Added the MULTINET NETCONTROL commands to start, shutdown, and reload the SNMP process. o Created a separate SNMP_AGENT process. Once the SNMP service is enabled via the MULTINET CONFIGURE/SERVERS command, the SNMP_AGENT process can be accessible via the NETCONTROL commands. You can also enable the SNMP service using the MULTINET CONFIGURE/MENU command. 2.5.2 Client ============ WHOIS The /PORT= number qualifier has been added to WHOIS. It specifies the number of a non-standard port. (D/E 5701) TN3270 o Added the /[NO]COLOR qualifier. The DPC TN3270 Emulation [which can be enabled by defining MULTINET_TN3270_EMULATOR to "DPC"] includes a feature that causes different field attributes to appear as different text colors. Some users do not like these colors. Users can now disable the foreground colors with the /NOCOLOR qualifier. (D/E 5743) 29 o Added the /[NO]YALE qualifier. Yale Improved Null is a TN3270 feature enabled by default. This feature replaces NULL characters found in fields with spaces when the TN3270 client writes the fields back to the server. Some IBM TN3270 applications do not expect the NULLs to be returned, and have problems with the Yale Improved Null feature. The Yale Improved Null feature can now be disabled with the /NOYALE qualifier. (D/E 5679) SNMP o A mechanism to generate an SNMP trap has been added to MultiNet. To use it, define the symbol: trap_gen :== $multinet:trap_gen Then type: $ trap_gen [....] identifies the location in the MIB tree that this trap pertains to. An example would be: 1.3.6.1.4.105.3, denoting a location in Process Software's portion of the MIB tree. is an integer representing the generic trap value. is an integer representing the specific trap value. are arbitrary strings separated by spaces that are passed to the agent receiving the trap as octet strings. The TRAP_GEN program uses the trap community definitions in the MULTINET:SNMPD.CONF file to determine where to send the trap. (D/E 5831) TCPDUMP o TCPDUMP NFS reply headers now report correct xids. (D/E 5313) o TCPDUMP now knows a little more about TELNET authentication suboptions. (D/E 6360) o TCPDUMP now shows the SNMP public group in VERBOSE mode. NFS o SS$_NOPRIV is no longer returned incorrectly when deleting multiple directories with the second and subsequent files processed on the same command line. (D/E 5783) -- To restore the old behavior (on a system-wide basis only), define the system logical MULTINET_NFS_CLIENT_OLD_DIRFIND to any value, and then restart any ACP processes. o On OpenVMS systems v7.1, v7.2, and v7.21, listings for directories greater than 127 blocks returned SS$_BADIRECTORY (can't read directory). This has been fixed to accept requests of greater than 127 blocks. (D/E 5325) o On VAX systems v7 and AXP systems V6 and V7, ACL entries can now be added to or read from files on NFS volumes. (D/E 4141) 30 o The first call to $SEARCH or f$search returns correct filespec, but the second call incorrectly returns "no more files" (RMS$_NMF) status. This has been fixed. (D/E 3784) o Fixed the RPC mount error when attempting to access a symlink or when using the nfs lockmanager. The client NFS error message: "RPC: Program unavailable" no longer appears. (D/E 3515, 3580) o Filenames including certain character sequences, often including dollar signs ($), cause "bad file name syntax" errors. This behavior has been changed. The old behavior may be restored (on a system-wide basis only) by defining a system logical MULTINET_NFS_CLIENT_OLD_SRIMAP to any value, and then restarting any ACP processes. Sites with existing affected filenames may find it convenient to use the old behavior. (D/E 1543) o Attempts to write to VBN 0 were not being prevented yielding unpredictable results. Such attempts are now screened and IOSB status will now contain SS$_BADPARAM. (D/E 139) Chapter 3 Documentation Updates =============================== This chapter contains a summary of changes to the documentation for MultiNet v4.3. 3.1 MultiNet for OpenVMS Installation and Introduction ====================================================== Chapter 1 Added information about what to do before running the Secure Shell (SSH) and about Galaxy Shared Memory. Chapter 5 Removed SNMP-CONFIG commands for configuring SNMP agents from the Administrator's Reference section. 3.2 MultiNet for OpenVMS Administrator's Guide ============================================== Chapter 1 Added Chapter 15 to the "Contents of this Guide" table. Added Chapter 21 to the "Contents of this Guide" table. Updated the version of MultiNet to v4.3. Chapter 2 Added the following to Table 2-2: SNMP SNMPD.CONF -- Contains configuration information for the MultiNet SNMP (Simple Network Management Protocol) agent. Edit this file manually. Updated the MultiNet Configuration Menu illustration. Chapter 3 Changed VAX/VMS v5.5 to VAX/VMS v5.5-2 and OpenVMS Alpha v1.5 to OpenVMS Alpha v6.1. Under "Setting the Filter List at Startup", added: $ MULTINET SET/INTERFACE interface - $_/FILTER=MULTINET:FILTER-line-id.DAT 31 and added this paragraph: If you want to know if filtering is enabled and what the settings are, use the MULTINET SHOW/INTERFACE/FILTER SE0 command. Chapter 4 Corrected 127.0.0/255.0.0 to read 127.0.0.0/255.0.0.0. Under "Using UCX-Compatible Services under MultiNet" added the following paragraph: Performing a close (dassgn) operation on any TCP/IP Services (BG) device used in a select list cancels the select operation. Chapter 6 Added the following paragraph to the introduction: The chapter also describes how to use DNS load balancing for TCP-based services on cluster nodes. Load balancing helps to provide uninterrupted services if an individual server crashes or cannot handle the number of users trying to access it simultaneously. Added the following to Table 6-5: Zone Statements: masters [ port ] {; [; ... ]}; type (master | slave | stub | hint | forward); allow-query { }; allow-transfer { }; also-notify {; [; ...] }; forward (only | first); forwarders {[;...]}; ixfr-base ; pubkey ; transfer-source ; Changed/added to the definitions of the following items in Table 6-6: Zone Types: forward hint 32 Added the following to Table 6-7: NAMED.CONF Options: allow-recursion {}; also-notify {; [; ...] }; blackhole {}; maintain-ixfr-base ( yes | no ); max-ixfr-log-size ; min-roots ; rrset-order {; [; ... ] } sortlist {}; transfer-source ; version ; Changed the syntax on the following in Table 6-7: allow-query {}; allow-transfer {}; forwarders {; [; ... ]}; listen-on [port ] {}; topology {}; Added the following to the "Address_match_list" bulleted list: A key ID, as defined by the key statement Revised the table in the "Address_match_list" section as follows: Added: with the listen-on option Removed the second paragraph in: as an access control list Added the following sections: Resource Record Sorting Incremental Zone Transfer DNS Security Added the following paragraph to the "DNS Zone Information Files" section: The $TTL statement sets the default time-to-live for records that do not have explicit ttl fields. If the zone file does not have a $TTL statement, the DNS server prints a warning on your computer screen and uses the minimum value from the SOA record. Added the following to Table 6-9: DNS Resource Record Types: KEY The public key associated with a domain name [flags protocol algorithm key] NXT Used for secure negative responses. Tells a querier which record is lexicographically next in the zone [next-domain-name type-bitmap] 33 SIG A security signature for an RRset [type algorithm labels ttl expiration inception tag name signature] SRV Specifies the location of services [priority weight port target] Removed the DNS NETCONTROL Operations table. Added the following to Table 6-10: NSLOOKUP Commands: exit Exits NSLOOKUP. finger [user] Finger the optional user at the current default host. help or ? Prints help information. set port=port Sets the port number on which to send a query set srchlist=name1 Sets the domain to name1 and the [/name1/.../name6] search list to name 1 through name6. Chapter 7 Added the section on how to configure and manage the Network Time Protocol (XNTP). NTP functions Implementing NTP Converting to the NTP.CONF File Timekeeping hosts Determining peer hosts Modifying the NTP configuration file Basic configuration commands Advanced configuration Basic configuration example Troubleshooting NTP NTPQ XNTPDC NTPDATE NTPTRACE Removed the following sections: Setting the System Clock on Hosts Not Connected to the Internet RDATE utility Chapter 8 Deleted information that no longer applies to how MultiNet lets you configure electronic mail. Changed the following section to read: Modifying the MultiNet SMTP Configuration File 34 The MultiNet SMTP configuration is stored in the START_SMTP.COM and START_SMTP_LOCAL.COM startup command procedures. Use the MAIL-CONFIG utility to edit these files. You start the utility by entering the MULTINET CONFIGURE /MAIL command. After using this configuration utility, stop and restart the mail queues. Enter @MULTINET:START_SMTP.COM to update the VMScluster. @MULTINET:START_SMTP_LOCAL.COM to update the local host only. Added the following paragraph to the "Translating UNIX-Style Linefeeds to SMTP-Compliant End-of-Line Character Sequences" section: The logical name MULTINET_SMTP_ACCEPT_UNIX_LF has been added as a synonym for MULTINET_SMTP_ACCEPT_UNIX_LF_BRAIN_DAMAGE. You can define either to have the same effect. Added this section: Configuring the SMTP Server to Limit System/Vendor Information MultiNet provides you with a way to limit the system/vendor information given out on connection, HELP, and QUIT. The MULTINET_SMTP_SUPPRESS_VENDOR logical removes operating system and TCP stack information from SMTP server text responses. Added the following to the "Forwarding Local Mail" section: The logical name MULTINET_SMTP_APPEND_FORWARDER_TO_MX can be used to prevent SMTP from appending the forwarder to the MX list by default. To do this: $ DEFINE/SYSTEM/EXECUTIVE MULTINET_SMTP_APPEND_FORWARDER_TO_MX FALSE If the logical name is not defined (or is defined to anything not beginning with F, N, or 0), then the FORWARDER is appended to the MX list. Corrected the RFC822 header example by adding a : before the Message-ID: line; thus, :Message-ID:. Changed the information for MULTINET_SMTP_MAXIMUM_822_TO_LENGTH logical to read: The default header length is 1024 characters. The logical name MULTINET_SMTP_MAXIMUM_822_TO_LENGTH can be used to override the 1024 byte default length of the To: and Cc: header fields. The logical can set the maximum length to anywhere from 256 to 65535. 35 Added the following to the IMAP Server section: Inhibiting Output in Command Procedures for the IMAP Service Problems arise when remote users log into systems using a login command procedure (SYS$LOGIN:SYLOGIN.COM or SYS$MANAGER:SYLOGIN.COM) that requires screen output. To inhibit this behavior, make sure the following lines are included at the top of all login command procedures: $ VERIFY = 'F$VERIFY(0) ! Turn off verify ! without echoing $ IF F$MODE() .EQS. "OTHER" THEN EXIT ! If a DETACHED ! process (IMAP)... $ IF VERIFY THEN SET VERIFY ! If a batch job, may ! want to turn verify ! back on. Note: This additional section will be in the HTML and PostScript versions of MultiNet v4.3, but not in the hardcopy version because the books had already gone to press by the time this was noticed. Corrected all occurrences of HOST_ALIAS to HOST_ALIASES. Chapter 9 Added the following to the "Configuring an LPD Protocol Queue" section: The following parameters are used with the MULTINET_LPD_SYMBIONT: ADDRESS=host_addr or ADDRESS:host_addr CLASS=class_string or CLASS:class_string FILTER=filter_char or FILTER:filter_char NOFFLF=Y/T/1 or NOFFLF:Y/T/1 PRINTER=remote_queue_name or PRINTER:remote_queue_name RETAIN_CR=Y/T/1 or RETAIN_CR:Y/T/1 Corrected MULTINET:REMOTE_PRINTER_QUEUES.COM to read MULTINET:REMOTE-PRINTER-QUEUES.COM Added the following to Table 9-1: User-Specified Print Parameters: CLASS=class_string Specifies the string to put on the "class" line in the control file. This gets used in various ways, but mostly appears on the banner page if one is printed. NOFFLF=Y/T/1 Specifies whether the symbiont should not add a Line Feed (LF) after a Form Feed (FF) when sending a text file to the remote system. 36 Added information on the MULTINET_STREAM_SYMBIONT_TIMER logical. Chapter 11 Added the following to the "Managing FTP Security" section: The following logical limits the information given out on connection or when using the STAT command: MULTINET_FTP_CONNECT_BANNER FTP server name If this logical is defined as whitespace, operating system and TCP stack information are removed from the FTP server connection banner. If this logical is defined with a specific FTP server name, the information banner does not appear in response to the STAT command. Added the following to the "UNIX File Names" section: The FTP server displays the creation month, day, and year of a file for a UNIX mode directory if the file is older than 1 year (365 days). If the logical MULTINET_FTP_UNIX_YEAR_OLD_FILES is defined as False, No, or 0 (zero), the old behavior is restored, displaying all files with Month, Day, and Time. Added the following sections: Defining FTP Messages Specifying the Name of a Log File Defining a File Name Password Lifetime Warnings Defining Password Messages Checking IP Address Added information on the following logicals: MULTINET_FTP_PASSWORD_WARNING_MESSAGE MULTINET_FTP_PASSWORD_WARNING_TIME MULTINET_FTP_PWDEXPIRED MULTINET_FTP_PWDPREEXP MULTINET_FTP_INCLUDE_DEVICE_IN_NLST MULTINET_FTP_LOGFILE MULTINET_FTP_LOG_ALL_USERS MULTINET_FTP_SERVER_RELAXED_PORT_COMMAND Added the following to the Configuring the FTP Client section: The FTP client program translates UNIX-style filenames in an MGET operation (which may contain directory information) into VMS-style filenames. If directory information is present it is removed and the files are stored in the local directory. 37 Added the following to the Specifying UNIX Style Listings section: If you want the device name, the file name, and the directory name included in the results of all NLST commands, define the logical MULTINET_FTP_INCLUDE_DEVICE_IN_NLST. This logical may be declared system wide or in the user's LOGIN.COM file. Chapter 12 Changed the version of MultiNet to 4.3. Upgraded DHCP to version 3.0. Updated Figure 12-1. Added new DHCP commands and removed those that no longer apply. Added the following to Table 12-4: option dhcp-max-message-size uint16; Use this option to specify the maximum length DHCP message that the client is able to accept. Use this option in the DHCP configuration file to supply a value when the client does not. Note: Use this option with caution. Make sure that the client can accept a message of the specified size. option dhcp-parameter-request-list Use this option to request that the uint8[,uint8...]; server return certain options. Use this option in the DHCP configuration file to override the client's list, or to supply a list when the client does not. The value is a list of valid DHCP option codes as listed in RFC 2132. option mobile-ip-home-agent Use this option to list mobile IP ip-address [, ip-address ...]; home agents in order of preference. Usually there will be only one agent. option nisplus-domain string; Use this option to specify the client's NIS+ domain. Use the NVT ASCII character set to define the domain character string. Added these two commands to NETCONTROL SHOW: SHOW LEASES SHOW POOLS Added these sections to the NETCONTROL SHOW section: Viewing Lease Information for all Leased IP Addresses Viewing IP Address Pool Availability Corrected this sentence: Safe-failover adds support for network, not server, failure. 38 to read: Safe-failover adds support for network failure, as well as server failure. Added the following to Table 12-10: safe-lease; This is used in the Partner Down state to indicate that the IP address belongs to this server. o Added the following to the Hostname Generator section: %P Printable characters from the Client ID. For example: if the client ID was 0174657374, the 01 is thrown away and the resulting hostname is "test". o Added allow dynamic-bootp; and deny dynamic-bootp; information Chapter 15 Changed the definitions of SNMP agent and traps in the first table. Added these sections: Configuring the SNMP Subagent Configuration File File Format Values for MIB Objects SYSDESCR SYSCONTACT SYSLOCATION INTERFACE SYSSERVICES Community Parameters Disabling Traps SNMP Multiplexing Peers SNMP Agent Extensibility (AgentX) Peers SMUX_PEER AGENTX_PEER Template Configuration File Private MIB Application Program Interface SNMP Log File Remote Host Information Added this note: SNMP parameters can not be modified with the SNMP-CONFIG or MENU-CONFIG utilities. The MULTINET CONFIGURE/SNMP and MULTINET CONFIGURE/MENU commands are not supported with MultiNet v4.3 and beyond. Chapter 21 Added this chapter to explain the Secure Shell (SSH) Server. Appendix A Added the following to Table A-2: SMUX SNMP Multiplexing Protocol 39 3.3 MultiNet for OpenVMS Administrator's Reference ================================================== Chapter 1 Changed the following definitions in Table 1-1: MULTINET SHOW /STATISTICS Displays network interface or protocol or both. MULTINET SHOW /WIDTH Specifies the width of displayed output when used with the /ARP, /CONNECTION, /ROUTE qualifiers. Removed NTP from the MULTINET NETCONTROL table. Added to Table 1-4: NETCONTROL DHCP Commands: - Debugging levels to the DEBUG command - "RESTART or" to the RELOAD command - The following commands were reformatted: SHOW SHOW ALL SHOW CID SHOW CLIENT SHOW HADDR SHOW SUBNET SHOW LEASES SHOW POOLS Changed the description for the following in Table 1-5: NETCONTROL DOMAINNAME Commands: DEBUG Sets the debug level of the Domain Nameserver (the default is no debugging). The larger the number, the more verbose the output. DUMP Dumps the Domain Nameserver cache to the file MULTINET:DOMAIN-NAME-SERVICE.DB. Use to diagnose database problems. RELOAD Causes the Domain Nameserver to re-read the configuration file, and subsequently re-read any zone files that have changed. STATISTICS Appends Domain Nameserver server statistics to the file MULTINET:DOMAIN-NAME-SERVICE.STATS and memory statistics to the file MULTINET:DOMAIN-NAME-SERVICE.MEMSTATS. Added "SHUTDOWN or" to STOP. Changed the version of OpenVMS VAX to 5.5-2. Removed Table 1-8: NETCONTROL NTP Commands Removed Table 1-12: NETCONTROL RPCPORTMAP Commands Added Table 1-13: NETCONTROL SNMP Commands 40 Added the following to the MULTINET SET/INTERFACE command: /COMMON_LINK=line-ids The /COMMON_LINK qualifier works for systems that have multiple interfaces on a common Ethernet, FDDI, or Token Ring cable. The system manager configures this support using the following new qualifier: $ MULTINET SET /INTERFACE xxx/COMMON_LINK=(yyy[,zzz...]) xxx, yyy, and zzz are device names like se0, se1, and se2. With this qualifier, MultiNet links the interfaces together. A performance benefit of this linking occurs if data is to be transmitted on an interface that happens to be busy, MultiNet assigns the data to the least busy linked interface for transmission. This linking also provides a level of redundancy. If a linked interface is shut down using MULTINET SET/INTERFACE/DOWN or if a fatal error is detected with the interface and an automatic restart can not be attempted, then any routing table entries or pseudo devices associated with the shut down interface will be failed over to one of the common link interfaces. Restrictions: The joined interfaces must be connected to the same cable. The joined interfaces must have the same MTU. Updated the MULTINET_NSLOOKUP commands table. Added the MULTINET NSUPDATE, MULTINET DIG, MULTINET DNSKEYGEN, and the MULTINET DNSSIGNER sections. Added Table 1-14: NETCONTROL SSH Commands Chapter 5 Added the following to Table 5-2: ADD Interfaces and Parameters pd Interface name: pd0 Device type: Secondary Ethernet Address Parameter Prompt Example Value TCP/IP 161.44.128.21 Hardware-Device se0 IP SubNet Mask None Non-Standard IP Broadcast Address: None pd0 (Secondary Ethernet Address): Csr=None, Flags=%X0 41 Careless assignment of a secondary address can cause network problems. In general, you should assign pseudo devices (pd) addresses on the same network or subnet as the se device to which the pd device is linked. If the pd interface is not in the same IP network as its associated se interface, some TCP/IP packages (such as early versions of SunOS) retransmit broadcast packets for the other IP network back to the network segment from which they were transmitted. This can cause network storms. NOTE: Some services listen to traffic on se interfaces only and ignore traffic on pd interfaces. One such service is the RIP listener in GATED. Added values to the MULTINET_NAMESERVER_RETRANS and MULTINET_NAMESERVER_RETRY examples. Chapter 9 Replaced the example for the ADD command with this one: $ MULTINET CONFIGURE /PRINTERS MultiNet Remote Printer Configuration Utility v4.3(nn) [Reading in configuration from MULTINET:REMOTE-PRINTER-QUEUES.COM] PRINTER-CONFIG>ADD SYS$LASER [Adding new configuration entry for queue "SYS$LPTERM"] Remote Host Name: 192.0.0.15 Protocol Type: [LPD] LPD TCP Port Number: [23] 1495 [SYS$LPTERM => 192.0.0.15, TCP port 1495 (no telnet option negotiation)] PRINTER-CONFIG> Chapter 10 Added the following to the SET FLAGS command: SNMP_MONITORED Tells the service handling routines to connect to SNMP Agent X and provide information about the state of the service. You need to define MULTINET_SNMP_AGENTX 1 and add AGENTX_PEER 127.0.0.1 in the SNMPD.CONF file. The following values are displayed with: - Service name - Service port number - Maximum servers allowed - Number of active servers - Number of times the service processing code has been called - Last I/O status value for the service (generally 0 or 1) Corrected the format example to read: SET FLAGS [ flag1 | flag2 | flag3 ] 42 3.4 MultiNet for OpenVMS Programmer's Reference =============================================== Chapter 2 Added the following to the BSD section: If the IO$M_EXTEND modifier is set on any one of the following QIO operations, the sockaddr parameter passed in these operations is assumed to be in BSD 4.4 format. IO$_SETMODE/IO$_SETCHAR (socket, bind) IO$_ACCESS (connect, listen) IO$_SENSEMODE/IO$_SENSECHAR(getsockname, getpeername) IO$_READVBLK (recv_from, UDP only) IO$_WRITEVBLK (send_to, UDP only) When the IO$M_EXTEND modifier is used in the creation of a socket via IO$_SETMODE/IO$_SETCHAR (socket, bind), the setting is remembered for the lifetime of the socket and all sockaddr structures passed in are assumed to be in BSD 4.4 format. Refer to the Compaq TCP/IP Services for OpenVMS System Services and C Socket Programming manual for additional information. Chapter 3 Added FORMAT and ARGUMENTS information to the following socket library functions: socket ioctl SIOCDARP socket ioctl SIOCGARP socket ioctl SIOCSARP Chapter 4 Added IO$_SENSEMODE and IO$_SENSEMODE | IO$M_CTRL. Chapter 5 Added this chapter: SNMP Extensible Agent API Routines 3.5 MultiNet for OpenVMS User's Guide ===================================== Chapter 3 Added the following to the section on Using OpenVMS Mail Across the Internet: If the address contains an apostrophe, enter the address with either \' or \s as shown in the following example formats: To: SMTP%"Thomas.O\'Malley@alley.cat.net" To: SMTP%"Thomas.O\sMalley@alley.cat.net" For the address Chapter 5 Added the TN3270 Emulation section. Chapter 8 Added this chapter to explain Secure Shell (SSH) Client. Appendix B Added information in STATISTICS about the FTP client being modified to display the elapsed time in HH:MM:SS format if the logical MULTINET_FTP_STATISTICS_IN_HHMMSS starts with 1, T (true), or Y (yes). 43 3.6 MultiNet for OpenVMS Messages and Logicals ============================================== Title Changed the title to reflect the addition of the MultiNet logicals table. Chapter 2 Removed the following error messages: NTP logical clock adjust timeout NTP peer syntax Chapter 3 Added this chapter containing the MultiNet logicals with definitions. 3.7 MultiNet for OpenVMS Online Help ==================================== Updated the online help to reflect new and changed information. 3.8 MultiNet for OpenVMS TCP/IP Services for DECnet Applications ================================================================ Chapter 2 Updated the MultiNet Configuration Menu illustration Replaced the code examples under "Modifying Your System Startup" with the following: $ SYS$SYSDEVICE:[MULTINET.nodename.SYSCOMMON.MULTINET]- _$ START_NOTDRIVER ! Start DECnet application service $ @SYS$MANAGER:STARTNET ! Start DECnet $ SYS$SYSDEVICE:[MULTINET.nodename.SYSCOMMON.MULTINET]- _$ START_MULTINET ! Start MultiNet $ SYS$SYSDEVICE:[MULTINET.nodename.SYSCOMMON.MULTINET]- _$ START_NOTDRIVER ! Start DECnet application services $ SYS$SYSDEVICE:[MULTINET.nodename.SYSCOMMON.MULTINET]- _$ START_MULTINET ! Start MultiNet 3.9 Changes Made After the Documentation Went to Press ====================================================== The following information was added to the MultiNet v4.3 books after the documentation set went to the printer's. These changes are in the HTML, PostScript, and PDF versions of these books on the product CD. They are NOT in the hardcopy version. MultiNet documentation set Removed all instances of BOOKREADER and related information. Administrator's Reference Chapter 1 Added this table: Table 1-19 shows the NETCONTROL commands you can use with the XNTP server. 44 Table 1-19 NETCONTROL XNTP Commands Command Description =================================================================== DEBUG level Sets the debug level as specified. NOOP *PING!* RELOAD Causes the server to reload the configuration file by stopping and restarting. SHOW Shows the current state of all server and peer connections. For example: $ MULTINET NETCONTROL XNTP SHOW SET ANONYMOUS_FTP_ACCESS NOWRITE,NOSPAWN to read NET-CONFIG> SET ANONYMOUS-FTP-ACCESS NOWRITE,NOSPAWN Messages and Logicals Chapter 3, Table 3-1 changed MULTINET_HOSTALIASES to read MULTINET_HOST_ALIASES 3.10 Changes Not Made to the PostScript, PDF, and HTML Documentation ==================================================================== The following changes have not been made to the PostScript, PDF, HTML, or hardcopy documentation because they were submitted after these files were closed. Administrator's Guide Chapter 21, page 21-12, Step 4: $ SHOW PROCCESS "SSHD MASTER" is incorrect. It should be $ SHOW PROCESS "SSHD Master" Note the single C in PROCESS and the change in case of Master. What to do if you have already enabled SSH and make a change to its configuration file. The proper commands should be: $ multinet netcontrol Connected to NETCONTROL server on "LOCALHOST" < bluto.process.com Network Control V4.3(10) at Thu 24-Aug-2000 11:40AM-EDT NETCONTROL>select ssh SSH> RESTART < SSH server restarting SSH>quit 46