______________________________________________ DECserver 300, DECserver 700 and DECserver 90TL Release Notes for OpenVMS June 1997 This version of the DECserver Software Release Notes contains information about enhancements, known problems, and workarounds in the DECserver 300 Version 2.2C software, the DECserver 700 Version 1.1C software, and the DECserver 90TL Version 1.1C software. The Release Notes should be distributed to the server manager(s), load host system manager(s), and any other individuals responsible for server maintenance. SOFTWARE VERSION: DECserver 300, Version 2.2C for OpenVMS DECserver 700, Version 1.1C for OpenVMS DECserver 90TL, Version 1.1C for OpenVMS ________________________________________________________________ Contents Contents Contents 1 DECserver 300 V2.2C/DECserver 700 V1.1C/DECserver 90TL V1.1C Specifics............ 1 1.1 Identification of Software Version ........... 1 1.2 Bugfixes from previous releases .............. 2 1.2.1 Bugchecks.................................. 2 1.2.2 LAT Problems............................... 3 1.2.3 Miscelaneous Problems...................... 4 2 How to Report a Problem......................... 6 2.1 Documentation Problems ....................... 6 2.2 Severe Errors ................................ 7 3 Known Problems.................................. 8 3.1 VMS INSTALLATION GUIDE ....................... 8 3.2 SNMP ......................................... 8 iii __________________________________________________________ June 1997 June 1997 June 1997 © Digital Equipment Corporation 1997. All Rights Reserved. ___________________ [TM]ULTRIX is also a trademark of Digital Equipment Corporation [TM]MS-DOS is a trademark of Microsoft Corporation This document was prepared using VAX DOCUMENT, Version 2.1. 1 DECserver 300 V2.2C/DECserver 700 V1.1C/DECserver 90TL V1.1C 1 DECserver 300 V2.2C/DECserver 700 V1.1C/DECserver 90TL V1.1C 1 DECserver 300 V2.2C/DECserver 700 V1.1C/DECserver 90TL V1.1C Specifics Specifics Specifics The purpose of this section is to describe differences between this release and the previous SSB release of the DECserver software. 1.1 Identification of Software Version 1.1 Identification of Software Version 1.1 Identification of Software Version In keeping with past naming conventions, the DECserver software image included in this release kit is titled identicaly to that in previous versions. This may cause some confusion in environments having multiple load hosts unless all load hosts are updated with this version of software. To verify that a server has been loaded with the patched software, connect to the server and enter the SHOW SERVER command at the local prompt. Local> SHOW SERVER This will display server characteristics. The first line of the display contains revision information and will indicate that the DECserver software is "V2.2C BL46-13" for the DECserver 300, "V1.1C BL46-13" for the DECserver 700, or "V1.1C BL46-13" for the DECserver 90TL. 1 1.2 Bugfixes from previous releases 1.2 Bugfixes from previous releases 1.2 Bugfixes from previous releases This section lists problems fixed in this release of the DECserver software. Note that the term "memory leak" is used in several of the following problem descriptions. "Memory leak" refers to an irreversible reduction in the size of the server's free memory pool. It is from this pool that the server allocates the memory required to process user commands and connect requests. As the pool diminishes, the server's performance degrades. Please note that following list of bugfixes encompasses all the fixes added since the last release. 1.2.1 Bugchecks 1.2.1 Bugchecks 1.2.1 Bugchecks o The DECserver would bugcheck on receipt of a LAT message containing an illegal circuit address. o The DECserver would bugcheck when logging out of a password protected port when a connection was not yet established. o The DECserver would bugcheck when a queued connect request was de-queued then rejected due to incompatable group codes. o The DECserver would bugcheck while responding to ICMP ECHO request if the ECHO request included the record route option. o The DECserver would bugcheck with a code of 977, a memory allocation error, under these circumstances: when a port was configured for multisessions, and autoconnect; a user logged into a system using two sessions; the user logged out of both sessions, power cycle the terminal, performed a clear comm, reset session, enable sessions, typed carrage return to get to the username prompt on both sessions, and the ethernet connection was interrupted from the server to the lan. o The DECserver would bugcheck with a code of 977, a memory allocation error, when connecting to service, the service node went away, the user hit the break key trying to get system back, and the system was in a failover state at the time. 2 o The DECserver would bugcheck with a code of 977, a memory allocation error, while servicing queued access requests. This occured in situations where a queued request was being processed on a reverse circuit. o The DECserver would bugcheck with a code of 212, a lance initialization timeout error. o The DECserver would bugcheck with a code of 299, a watchdog timeout error, when a TDSMP user attempted to open a session and the DECserver has no credits to acknowledge the open session. 1.2.2 LAT Problems 1.2.2 LAT Problems 1.2.2 LAT Problems o The DECserver would allow no more than 33 sessions to be created, on the 34th the user would receive a -719- insufficient resources message. o The LAT specification states that terminal servers should be insensitive to case when responding to connect requests. The DECserver did not meet this requirement and would only allow uppercase characters in the port, service, and node names. o Queued remote access requests were not being serviced even though the port was in the idle state. o Queued access requests were being queued by the server instead of rejected if the port was set to an access type of LOCAL or NONE. o A rejection code of 6 was being sent in status message on non-queued LAT requests after port starts disconnect from host requested stop_slot. o Ports did not flush data at the byrt level in response to a LAT flush, i.e. an attention slot having the flush bit set. Because of this if a VMS print queue gets stalled due a port being xoffed, executing the stop /reset /queue command on the VMS host causes the port to enter the session mode state instead of returning to idle mode. 3 o The high active port counter was not incrementing for a host initiated connection. 1.2.3 Miscelaneous Problems 1.2.3 Miscelaneous Problems 1.2.3 Miscelaneous Problems o Using remote break on telnet connections on dedicated ports would cause a memory leak because the server was not able to properly flush a local 305 message. o The server did not respond to Telnet Listener connect requests with a RESET if the targeted port is busy. This causes the host to retry the request several times and then timeout. o On the DEChub900 console, status for the DS90TL was being displayed as a Nonfatal Failure status following software load because the DECserver software did not support the Left Hitchcock protocol. o The DECserver would not assert DTR in response to RING if DTRwait was enabled. o SNMP could not be used to change a port's access type from NONE to LOCAL if the port has a prefered LAT service defined. The access type is changed to LOCAL in NVRAM but attempts to access the port locally fail in such a way that the port appears to be hung. o The SHOW PORT n STATUS command did not always accurately reflect the state of DSR immediately after power-up. o When an attached device was powered on a port set to DSR flow control, the port did not flush data on logout. o On a remote access port which is handling small size files (print jobs) and are one right after another (heavy usage); the XOFF near the end of a job would get reset during disconnect. This causes the next job to start and the printer is not ready (XON has not been sent to server port); causing data overruns (messed up printout at printer) on printer. 4 o The CPU Utilization went to 100% and port is in disconnecting state when a port has modem enabled and data in in the receive holding register in the UART during a disconnect. o Remote or dynamic access ports would not allow remote connections if DTRwait, Signal Check, and Modem or Signal Control were enabled at the same time. o TDSMP sessions did not get restored properly if a CLOSE SESSION command issued from the server times out due to the terminal being powered down. o TDSMP had a return credit problem in session mode. o Port information was not displayed when the SHOW QUEUE command was executed. Executing a SHOW PORT STATUS command indicated that the affected port(s) had a port name of (REMOTE) which indicates partial processing of the queue. o With a port set to DSR flow control and the attached device is powered off, the port did not flush data on logout. o When a MOP connection is established and the user tries to logout from the connection by typing LOGOUT; the connection was lost and the host received a "Target node does not respond" message. 5 2 How to Report a Problem 2 How to Report a Problem 2 How to Report a Problem If you discover a problem with the operation of the DECserver software, please contact your Customer Support Representative and submit a problem report. When completing a problem report please describe one problem at a time. This simplifies record keeping and facilitates a quick response. Keep the description simple yet accurate. Illustrate a general problem with several examples. If a BUGCHECK error occurs, provide a pointer to the upline dump in your report. Because problems are often difficult to reproduce with different system configurations, please include as much detail as possible when reporting a problem. Define as precisely as possible the state of your system when the problem occurred and indicate the sequence of events or commands that caused the problem. Attempt to reproduce the situation, if it can be reproduced, using the minimum number of steps. If one of your user programs causes a problem in the server and you are unable to send the program to Digital, try to reproduce the problem with a standard utility. If this is not possible, try to describe the program's operation before and after the suspected failure. When a problem report contains concise information about a problem, that problem is more likely to be reproduced and corrected. Please ensure that any questions are direct and simply stated so they can be answered clearly and directly. 2.1 Documentation Problems 2.1 Documentation Problems 2.1 Documentation Problems When describing a problem found in a manual, specify the full title of the manual and identify the appropriate section, table, or page number. Describe what the manual says and also describe the suggested correction. You can use the Reader's Comments Card in the back of the manual. If you are reporting an error with on-line HELP, please identify the full command and screen, and specify TUTORIAL or REFERENCE HELP. 6 2.2 Severe Errors 2.2 Severe Errors 2.2 Severe Errors Severe errors may cause your DECserver terminal server to hang or bugcheck. Terminal server hangs which are not recovered from after 20 seconds, require that the terminal server be powered off and on to restore operation. If this should occur, please describe the operating conditions on the terminal server at the time of the hang. If a FATAL BUGCHECK occurs, a message is printed out on the console terminal. The message shows the vital registers at the time of the bugcheck. Normally, an upline dump is automatically created when a fatal bugcheck occurs. For other types of problems, a dump is also an extremely valuable tool. For example, if you experience a problem that is not easily reproducible, a dump will normally allow Digital to fix the problem even though it cannot be reproduced. You can force a dump by typing CRASH at the local mode prompt in privileged local mode. A code 300 fatal bugcheck immediately occurs. The location of the bugcheck dump file is determined as follows: o After the terminal server reinitializes, enter privileged local mode and issue a SHOW SERVER STATUS command. Information in this display will indicate the Ethernet address of the dump host. You can identify the dump host from this address. o The bugcheck dump is located in the SYS$COMMON:[DECSERVER] directory on the dump host, and the file name is DS _ n .DMP, where is 3 for DECserver 300, 7 for ______ _ xxxxxx n DECserver 700, and 9 for DECserver 90TL and ______ xxxxxx is the DECnet node name assigned to the terminal server as defined using the DSVCONFIG configuration procedure. For example, if a DECserver 300 terminal server with node name LAT041 bugchecks, the bugcheck dump will be found on the dump host in SYS$COMMON:[DECSERVER] DS3LAT041.DMP. 7 o Copy the dump file to TK50 (preferred), magnetic tape, or another media if these are not available and indicate on a label the format of the copy (COPY, BACKUP, FLX, and so forth). All media sent to Digital will be returned to the sender. 3 Known Problems 3 Known Problems 3 Known Problems The following list includes some of the known problems with this release of the DECserver software. Workarounds are described where applicable. 3.1 VMS INSTALLATION GUIDE 3.1 VMS INSTALLATION GUIDE 3.1 VMS INSTALLATION GUIDE In the section called 'Preparing to Install the Software' the load host available disk space after installation is incorrectly specified as 1300 Kb. It should be 2100 Kb. 3.2 SNMP 3.2 SNMP 3.2 SNMP Please refer to (snmp_survival.txt) ___ ____ ________ _____ The SNMP Survival Guide included in the release kit for a full description of potential problems. 8