Compaq_SNA_Peer_Server______________________________ Release Notes December 2001 This document contains information not included in the Compaq SNA Peer Server V1.5A documentation. It includes information about required and optional software, installation notes, operating notes, problem corrections, and known problems with this software version and known restrictions in companion software. ______________________ IMPORTANT ______________________ Please read these notes before installing or using the software. ______________________________________________________ Revision Information: This is a new document. Operating System Version: Compaq Tru64 UNIX, V5.1 or V5.1A DECnet Version: DECnet-Plus for Tru64 UNIX, V5.0B Software Version: Compaq SNA Peer Server, Version 1.6 © 2001 Compaq Information Technologies Group, L.P. COMPAQ, the Compaq logo, the DIGITAL logo, DECnet, DECnet-Plus, and Tru64 UNIX are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the U.S. and/or other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without any warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. _________________________________________________________________ Contents 1 Introduction.................................. 1 1.1 Version 1.6 Overview...................... 1 1.2 Appendices Removed in NCL Reference Manual.................................... 1 1.3 LLC2 Entity Changes....................... 1 2 Required Software............................. 2 2.1 Compaq Tru64 UNIX......................... 2 2.2 DECnet-Plus for Tru64 UNIX................ 2 2.3 Compaq WAN for Tru64 UNIX................. 3 3 Installation Notes............................ 3 3.1 Removing Prior Versions................... 3 3.2 Installing or Upgrading Peer Server Required Software......................... 4 3.3 NCL Initialization File Reuse............. 4 4 Operating Notes............................... 5 4.1 System Requirements for Supporting up to 10,000 Concurrent Sessions................ 5 4.2 Synchronous Data Link Control Support (SDLC).................................... 5 4.2.1 Supported SDLC Devices.................. 5 4.2.2 Naming of Synchronous Lines............. 7 4.2.3 SDLC Receive Frame Size Limitation...... 7 4.2.4 Modem Connect Line Speed Characteristic.......................... 7 4.2.5 SCC Device Name......................... 8 4.2.6 CCITT V.24 Incompatibility with EIA RS-232C (DSYT1 and DNSES Only).......... 9 iii 4.3 Logical Link Control Type 2 (LLC2)........ 9 4.3.1 Token Ring Support...................... 9 4.3.2 Ethernet Support........................ 10 4.3.3 FDDI Support............................ 10 4.3.4 Operation in Bridged Token-Ring and FDDI Environments............................ 10 4.3.5 Mapping Between IBM LLC2 and EMA LLC2 Parameters.............................. 10 4.4 WANDD Loader.............................. 11 4.5 Automatic Generation of NOTIFY(ONLINE) and NOTIFY(OFFLINE)........................... 11 4.6 Specifying PU Name and Session Number on Client Connections........................ 12 4.7 Session Termination Support for Non-IBM Mainframes................................ 12 4.8 Startup Initialization Delay.............. 12 4.9 OS/2 LAN Support Withheld................. 13 5 Known IBM Restrictions........................ 13 5.1 Configuring Multiple Lines as PU T2.1 on the Peer Server........................... 13 5.2 IBM 3745 Scanner Problem Running Above 230Kbps................................... 13 5.3 NCP Problems with SDLC Mixed Modulo Stations on a Multipoint Line............. 14 5.4 NCP Problems with Modulo 128 Token Ring Stations.................................. 14 5.5 INIT-SELF Rejected with Sense Code 10105006.................................. 14 5.6 VTAM ABEND S0C4 at ISTATCTR+1F0........... 14 6 Known Problems and Product Restrictions....... 15 6.1 Common Trace Facility (CTF) Restrictions.............................. 15 6.1.1 LU Tracepoints Not Supported............ 15 6.2 Network Management Restrictions........... 15 6.2.1 NCL Delete Transmission Group Generates "Wrong State" Exception................. 15 6.2.2 NCL Enable SDLC Link Station Generates "Invalid Parameter" Exception........... 16 6.2.3 LocalEntityName Instance Specification........................... 16 iv 6.3 SDLC Datalink Restrictions................ 17 6.3.1 Multipoint Full Duplex Configuration Requires TWA............................ 17 6.3.2 Using the PBXDI ISA-Bus Synchronous Communications Controller............... 17 6.4 QLLC Datalink Restrictions................ 18 6.4.1 Temporary TGs Lack Automated Call Startup................................. 18 6.4.2 Filter Name Mismatch Error is Ambiguous............................... 18 6.4.3 QLLC Link and Station Must Be Enabled Before TG............................... 18 6.5 TN3270 Server Restrictions................ 19 6.5.1 TN3270 Server Default Port (2301) Used by Insight Manager...................... 19 6.5.2 TN3270 Server Drops Connection When Client Does Not Respond Properly........ 19 6.6 LLC2 Datalink Performance Issues.......... 19 6.6.1 FDDI Performance........................ 19 7 Files Installed/Modified...................... 20 Tables 1 Peer Server Installed Files............... 20 2 Peer Server Configuration Files........... 22 3 Peer Server Files Used for Logging........ 22 4 Peer Server Modified Files................ 23 v 1 Introduction These release notes are for Version 1.6 of the Compaq SNA Peer Server. Following product installation, these release notes can be found in the file /var/sna/t21_V16-0_release_notes. The abbreviated Peer Server product name is used throughout this document. 1.1 Version 1.6 Overview The primary enhancements provided by Version 1.6 of the Peer Server are: o Support for Tru64 UNIX V5.1 and V5.1A. o Support for WAN device PBXDD. The release includes all fixes from Compaq SNA Peer Server V1.4 through ECO 05 and Compaq SNA Peer Server V1.5A-002. Version 1.6 is a functional superset of Version 1.5A. All capabilities supported in Version 1.5A are supported in Version 1.6. Please note that there is no new release of the Peer Server documentation in conjunction with this release of the Peer Server software. 1.2 Appendices Removed in NCL Reference Manual The Token Ring, CSMA-CD, and FDDI appendices in the Peer Server's NCL Reference manual have been removed. Some of the information in these appendices was out of date. To prevent this possibility in the future, these appendices have been removed. You should use the DECnet-Plus for Compaq Tru64 UNIX NCL Reference manual for information about these entities. 1.3 LLC2 Entity Changes The LLC2 material in the Peer Server's Management and NCL Reference manuals has been updated to reflect the latest LLC2 implementation. Because of the close association of this entity with the Peer Server, the description of this module was kept in the Peer Server's documentation. However, the DECnet-Plus for Compaq Tru64 UNIX NCL Reference may contain more up-to-date information. 1 The online help for the LLC2 entities has been removed from the SNA_Peer_Server help topic. You should use the LLC2 help available under the individual command descriptions. 2 Required Software You must have the required software installed before you can install the Peer Server software. This includes the correct version of the Compaq Tru64 UNIX operating system and certain required, DECnet-Plus for Tru64 UNIX, V5.0B and Compaq WAN V3.2-1 subsets. For optional DECnet and/or X.25 functionality, DECnet-Plus for Tru64 UNIX and/or Compaq WAN software must also be installed and configured. The Compaq SNA Peer Server Installation and Configuration manual describe these requirements. See DECnet-Plus for Tru64 UNIX and/or Compaq WAN documentation if these functionalities are required. 2.1 Compaq Tru64 UNIX The Peer Server V1.6 software requires Tru64 UNIX V5.1 or V5.1A. 2.2 DECnet-Plus for Tru64 UNIX The Peer Server can use both TCP/IP and DECnet networks. If you plan to use DECnet, you must install DECnet-Plus for Tru64 UNIX V5.0B or later. If you wish to install or upgrade DECnet-Plus software on a system that is already running a version of the Peer Server, then you must delete the Peer Server subsets before installing DECnet-Plus for Tru64 UNIX. See Section 3.1 for instructions on removing the Peer Server software. Once you have installed and configured DECnet-Plus, you should install the Peer Server V1.6 software. Unless you are planning to use DECnet communications to access the Peer Server, there is no requirement that the DECnet-Plus for Tru64 UNIX layered product be installed on the Peer Server system. (However, certain DECnet-Plus subsets are required to be installed and configured on the Peer Server system. See the Compaq SNA Peer Server Installation and Configuration manual.) 2 2.3 Compaq WAN for Tru64 UNIX With the Peer Server, SNA traffic may be sent over X.25 Packet Switched Data Network (PSDN) backbones using the Qualified Logical Link Control (QLLC) protocol. This enables X.25 customers to communicate with their IBM machines using SNA protocols over X.25 networks. To do so, you need Compaq WAN for Tru64 UNIX V3.2-1 or later software product (available separately) installed prior to installing the Peer Server. You must also have the IBM software resident and configured on the IBM machine (for example, X.25 Network Control Program Packet Switching Interface (NPSI) for IBM mainframe front end communications processors). The use of QLLC is supported with both types of X.25 PSDN access provided by the Compaq WAN for Tru64 UNIX product, namely: by direct synchronous communications link (LAPB) or by LAN access to an X.25 Relay node (LLC2). Unless you are planning to use the QLLC protocol with the Peer Server, there is no requirement that the Compaq WAN for Tru64 UNIX layered product be installed on the Peer Server system. However, certain WAN subsets are required to be installed and configured on the Peer Server system. See the Compaq SNA Peer Server Installation and Configuration manual. If you wish to install or upgrade Compaq WAN software on a system that has a previous version of the Peer Server installed, then you must delete the Peer Server subsets before installing the WAN software. See Section 3.1 for instructions on removing the Peer Server software. Once you have installed and configured Compaq WAN, you should install the Peer Server V1.6 software. 3 Installation Notes 3.1 Removing Prior Versions If you have an earlier version of the Peer Server software installed on your node, you must delete it prior to installing this kit. To see whether a previous version is installed, issue the setld command as shown: setld -i | grep T21 3 The following subsets must be deleted to completely remove the Peer Server software prior to installing a new version of the Peer Server software. T21MGMTnnn T21SRVRnnn Delete the named subsets listed as installed (substituting the correct subset numbers for "nnn") using the setld command as shown: # setld -d subset subset ... 3.2 Installing or Upgrading Peer Server Required Software If you install or upgrade DECnet-Plus for Tru64 UNIX and/or Compaq WAN required software, then you must delete and reinstall the Peer Server software. See Section 3.1 for instructions on removing the Peer Server software. Once you have installed and configured DECnet-Plus and/or Compaq WAN software, you should reinstall the Peer Server software. The following is the list of software that requires reinstallation of the Peer Server if upgraded or installed after Peer Server is installed. CTAANALnnn (Compaq WAN) CTABASEnnn (Compaq WAN) WDABASEnnn (Compaq WAN) WDADATALNKSnnn (Compaq WAN) WDADRIVERSnnn (Compaq WAN) ZZAUTILnnn (Compaq WAN) DNAKBINnnn (DECnet-Plus) DNANETMANnnn (DECnet-Plus) DNABASEnnn (DECnet-Plus) 3.3 NCL Initialization File Reuse Previous Peer Server customers can retain the NCL initialization scripts configured for earlier versions of the Peer Server, provided they anticipate the same configuration for their Version 1.6 installation. (The default startup script is t21_init_sna_server.ncl in the /var/sna directory.) 4 4 Operating Notes 4.1 System Requirements for Supporting up to 10,000 Concurrent Sessions By default, DECnet-Plus for Tru64 UNIX is configured to allow up to 128 concurrent connections. The Tru64 UNIX operating system software limits the number of open files (sockets) that a process can have to 4096. Appendix F of the Compaq SNA Peer Server Installation and Configuration manual discusses how to raise these limits to allow the Peer Server to support up to 10,000 concurrent DECnet connections. 4.2 Synchronous Data Link Control Support (SDLC) As with earlier versions of the Peer Server, Version 1.6 supports IBM's Synchronous Data Link Control (SDLC) WAN datalink protocol for the SNA connection to the adjacent PU T2.1 or PU T4 node. (The AS/400 is an example of a PU T2.1 node. A mainframe front-end communications processor, such as a 3745 running IBM's NCP software is an example of a PU T4 node.) 4.2.1 Supported SDLC Devices The synchronous port used by the Peer Server is provided by a combination of the WAN Device Drivers software and the synchronous communications hardware itself. The following types of synchronous hardware are supported with Version 1.6 of the Peer Server: o The built-in SCC sync port: The SCC port is present on all DIGITAL 3000 systems supported by the Peer Server. However, for 3000-300 and 3000-300L, the SCC port may only be used with the Peer Server when it is otherwise not used as the console port (that is, a monitor must be used for the console). The SCC port supports the V.24/RS-232 interface only, at speeds up to 19.2 kb/s. o The DSYT1-BA high speed TURBOchannel adapter: The optional DSYT1 (also known as the DIGITAL WANcontroller 720) contain two lines per device and supports SDLC up to T1/E1 (2.048 Mb/s for a single line and up to 64 kb/s when both lines are used). The DSYT1 adapter supports the V.24/RS-232 interface. 5 o The DNSES EISA adapter: The optional DNSES adapter contains two lines per device and supports SDLC up to T1/E1 (2.048 Mb/s for a single line and up to 64 kb/s when both lines are used). It supports the V.24/RS-232 interface. o The PBXDI ISA adapter: The PBXDI controller supports two lines. One model (PBXDI-AA) supports the V.24/RS-232 interface; the other model (PBXDI-AB) supports both RS- 232 and V.35 interfaces. A third model (PBXDI-AC) exists but should not be used for SDLC. o The PBXDP PCI adapter: The PBXDP-AA adapter supports two lines; the PBXDP-AB adapter supports four lines; the PBXDP-AC adapter supports eight lines. The PBXDP supports the V.24, X.21, and V.35 interfaces. o The PBXDD PCI adapter: The PBXDD-AA supports supports two lines; the PBXDD-AB supports four lines. The PBXDD adapter supports the V.24, X.21, and V.35 interfaces. External clocking (modems, modem eliminators, or NCP "direct attach" lines) are required for all above cases. For more information on the "Supported SDLC Devices" refer to the Software Product Description (SPD) for Compaq Wide Area Networking for Tru64 UNIX, V3.2. Multiple DSYT1, DNSES, PBXDI, PBXDP, or PBXDD devices may be used for a higher number of concurrent links. All require a free bus slot (TURBOchannel, EISA, PCI, and ISA bus, respectively), and slot availability varies by specific system model. For example, the 3000 Model 800/S has up to 6 free TURBOchannel slots (thus 13 links - 6 DSYT1's and a single SCC - may be used in the extreme case). Similarly, the maximum number of PBXDD units is limited by free PCI slots and specific hardware configuration. Consult the Compaq Systems and Options Catalog (Alpha product hardware information) for full configuration details. 6 4.2.2 Naming of Synchronous Lines The following device names are used for the configuration of the modem connect line entities: o pwb - PBXDD o pwa - PBXDP o fsi - PBXDI o dns - DNSES o dsy - DSYT1 o scc - SCC sync port The Modem Connect Line entities are assigned names based on the order that the devices are named during configuration. When you execute or re-execute wddsetup, make sure that the devices are named in the same order as previously, or else the existing configurations of Peer Server or other products may become invalid. For example: Please specify which device(s) {pwb pwa fsi dns dsy scc none} are to be used. [scc]: pwb pwa 4.2.3 SDLC Receive Frame Size Limitation The Peer Server Configuration utility prompts you to enter the SDLC maximum receive frame size for the selected link. If you are using the built-in synchronous adapter (SCC) on the Alpha system instead of a DEC WANcontroler 720 (DSYT1), this value cannot exceed 1000 bytes due to hardware limitations. If you are using a DEC WANcontroller 720 line, this value cannot exceed 4000 bytes. 4.2.4 Modem Connect Line Speed Characteristic The following pertains to half-duplex and multipoint configurations, in which the local Peer Server DTE is toggling its Request to Send (RTS). Because of a limitation with the SCC, DSYT1, and DNSES hardware with regard to transmit interrupts, the respective device driver must compute the time to retain RTS assertion following the last data byte transmitted. The delay time is a function of the actual line speed, and the driver must therefore be aware of the speed of the link. 7 To accommodate the RTS drop delay computation, the Modem Connect Line entity includes a characteristic attribute called "Speed." If the Peer Server is to be used in a half-duplex or multipoint configuration, the Speed characteristic must be set to the actual speed at which the line is being externally clocked. Speed is entered in bits per second, for example a 19.2 kb/s link would have Speed set to 19200. (When set to zero, the default RTS computation assumes an actual line speed of 1200 bits per second.) Failure to set the speed accurately results in unpredictable results with half-duplex and multidrop lines, from reduced line throughput to transmission failures. On a multipoint line, it is possible that a misconfigured Peer Server line could affect data transfer between other tributary stations and the primary station. The wddsetup step of the V1.6 Peer Server (/usr/sbin/wddsetup), invoked as part of the product installation, includes prompting for line speed when the line specified is half duplex or full duplex multipoint. If the WAN Device Drivers are already present and configured on the Peer Server target node and the wddsetup step is not re-run during the Peer Server installation, you must ensure that the Speed characteristic is properly set for the lines to work properly in half duplex and multipoint modes. Re-running /usr/sbin/wddsetup or manually editing the Modem Connect startup NCL file in /var/dna/scripts/wdd.mconnect.ncl and restarting renders the change permanent. 4.2.5 SCC Device Name The SCC built-in synchronous port is referred to by NCL management and the WAN Device Driver scripts (wddsetup) as the "sscc" device, and as communications port "sscc0". The latter forms must be used when entering network management or configuration commands. 8 4.2.6 CCITT V.24 Incompatibility with EIA RS-232C (DSYT1 and DNSES Only) An incompatibility exists between the CCITT V.24 and EIA RS-232C physical interface standards with respect to pins 18, 21 and 23. The DSYT1 and DNSES are engineered for strict accordance with the newer V.24 standard, and are therefore incompatible with the older RS-232C interface. In order to permit the DSYT1 and DNSES to be used with RS-232C compliant devices, a V.24 hardware adapter connector part number 12-27591-01 is supplied with the BS19D-02 V.24 cable set. The adapter is attached to the DCE end of the BC19D- 02 V.24 cable. Refer to the information sheet supplied with the cable hardware for more information (info sheet EK-BS19D-IS-001). Failure to use the adapter where indicated results in an inability to activate the line and may possibly damage the modem or interface module. If you are unsure whether the adapter should be used or not, it should be fitted as a matter of course. Note that doing so may disable remote and local loop functions. This issue does not apply to the SCC sync port, which has tolerance for the difference in the standards. No adapter is required with the SCC. 4.3 Logical Link Control Type 2 (LLC2) 4.3.1 Token Ring Support The hardware adapter required for Token Ring is the DIGITAL TRNcontroller 700 (DETRA) TURBOchannel card or the EISA Token Ring Communications Controller (DW300/DT424). Both accommodate 4 and 16 Mb/s ring speeds (selectable). A single hardware adapter may be used simultaneously with multiple protocols (for example DECnet-Plus, IP, and Compaq WAN), using different SAPs. 9 4.3.2 Ethernet Support All Compaq-supplied Alpha Ethernet adapters supported under Tru64 UNIX are supported with this version of the Peer Server. Peer Server V1.6 supports Ethernet using IEEE 802.3 frame format, and not Ethernet V2. This may be an issue when configuring SNA over Ethernet to an IBM SNA node, which typically has a configuration option for Ethernet 802.3 or V2 (with protocol type 80d5). Ensure that your IBM Ethernet implementations (both destination nodes and bridges, such as the IBM 8209) are configured to use the 802.3 format for Ethernet frame transmission for communication with the Peer Server. 4.3.3 FDDI Support All Compaq-supplied Alpha FDDI adapters supported under Tru64 UNIX V5.1 and V5.1A are supported with this version of the Peer Server. 4.3.4 Operation in Bridged Token-Ring and FDDI Environments When running the Peer Server in a bridged environment, it is possible that an intervening bridge or LAN segment supports a maximum frame size smaller than that configured in the two communicating systems. The Peer Server detects this and automatically reduces the maximum frame size used in this case. 4.3.5 Mapping Between IBM LLC2 and EMA LLC2 Parameters Appendix E of the Compaq SNA Peer Server Installation and Configuration manual contains a mapping between the IBM LLC2 parameters and the EMA LLC2 parameters (settable through NCL). ________________________ Note ________________________ The default value for Holdback Timer is 500ms. To achieve a reasonable level of throughput, this parameter must be set to a value of 10ms. For a further discussion of this requirement, see Section 6.6.1. ______________________________________________________ 10 4.4 WANDD Loader The wdd_loader program runs as a daemon process and is responsible for handling microcode loading and dumping for those synchronous devices that require it. This daemon must not be killed; doing so may result in a system panic. 4.5 Automatic Generation of NOTIFY(ONLINE) and NOTIFY(OFFLINE) Starting with V1.2, the Peer Server sends ACTLU responses that indicate the LU is not available by default. The product then sends NOTIFY(ONLINE) when an access routine connects to the LU, and NOTIFY(OFFLINE) when the access routine disconnects. This is different from previous versions of the product and also different from the PU2.0 Gateway-ST and Gateway-CT products. This behavior can be modified such that the Peer Server behaves exactly as before if necessary, but doing so means that the product cannot be used for 3270 Terminal Emulator access to AS/400 systems. While the new behavior is typically closer to real IBM equipment, it does cause problems when connections to the LU are made and broken in quick succession. It also causes problems when the LU is in session when the Peer Server is deactivated, as the next time the LU is used the host application may attempt to re-BIND to the LU (which can override the real session activation request sent by the client). To turn off this feature, you should edit the file /var/subsys/t21scl.stanza and modify the line: use-notify = 1 to be: use-notify = 0 then enter the following command (as root): # sysconfigdb -u -f /var/subsys/t21scl.stanza t21scl This modifies the permanent database, which takes affect next time the system is booted. To modify the running system, use the following command: # sysconfig -r t21scl use-notify=0 11 The new setting takes effect the next time each LU is activated. 4.6 Specifying PU Name and Session Number on Client Connections The Peer Server Logical Units (LUs) are named entities and have an attribute called "Old Name" that can be set so that existing client applications can continue to connect to specific LUs using the PU name and Session Address syntax used with DECnet/SNA Gateway-ST and -CT. Specify the Old Name in the format [pu-name.][session-number]. If a client connection is received by the Peer Server specifying only a PU-name and no session number, the Peer Server will not use the PU-name when attempting to match the connection to an LU with an "old name" set. 4.7 Session Termination Support for Non-IBM Mainframes Certain IBM plug compatible (PCM) mainframe SNA implementations, e.g. Fujitsu, are known to require dependent SLU initiated session termination with (Rq)TERM-SELF instead of (Rq)UNBIND. Peer Server LU Services supports this feature. In the case where an LU-LU session (Rq)UNBIND sent from Peer Server to the mainframe is rejected with 1003 -Rsp, a TERM-SELF is sent from Peer Server to solicit an UNBIND from the PLU. This feature addresses PCM compatibility without affecting standard IBM mainframe session behavior. 4.8 Startup Initialization Delay The time between starting the Peer Server (from system boot running the t21icu Configuration utility, or by explicit execution of "t21_sna_server start" from /sbin/init.d) and full initialization may be on the order of minutes, particularly if your specific t21_init_sna_server.ncl has a very large number of LUs and related entities specified. Confirmation of initialization completion can be seen by running a Tru64 UNIX system utilization utility (for example iostat), to show CPU utilization dropoff following completion) or by interactively running NCL on the Peer Server machine, confirming final entity enabling. In addition, the file /var/tmp/t21_init_sna_server.log contains the output from the initialization. 12 4.9 OS/2 LAN Support Withheld As documented in Compaq SNA Peer Server Guide to IBM Resource Definition, formal support for connections to OS/2 Extended Services and Communications Manager are limited in this release to SDLC. 5 Known IBM Restrictions The following sections list problems identified with IBM software that you may encounter when installing/running the Peer Server in your environment. APAR and PTF numbers are provided that can be used to ensure that your VTAM/NCP installation has the fixes applied. 5.1 Configuring Multiple Lines as PU T2.1 on the Peer Server If you are configuring multiple lines on the Peer Server to connect to the IBM front-end (3725/3745) as a PU T2.1 link (XID=YES on the PU macro) you need to code CONNTYPE=LEN on the PU macro also. If CONNTYPE=LEN is not coded, the activation of the second line fails with a sense code of 081D. This problem is due to the Peer Server sending the same CP Name on each link (which is consistent with an SNA LEN node). 5.2 IBM 3745 Scanner Problem Running Above 230Kbps When connecting a DSYT1 or DNSES high speed SDLC line to an IBM 3745 communications controller running a line speed of 256 kbps, the IBM controller may report hardware underruns. The symptoms of the problem on the Peer Server are that the link fails and restarts, or that a large number of SDLC frames are retransmitted. This problem is not seen on links running at 230 kbps or below. Contact your Compaq Customer Support Center for an update or resolution to the problem if you plan to run SDLC links at speeds above 230Kbps. 13 5.3 NCP Problems with SDLC Mixed Modulo Stations on a Multipoint Line A problem exists in NCP V4, V5, and V6 whereby an SDLC multipoint line configured with PU T2.1 stations of both normal (modulo 8) and extended (modulo 128) SDLC window sizes can erroneously issue a modulo 128 SDLC poll from the NCP to a modulo 8 station. This has been corrected with the following APARS from IBM: o NCP V4 IR24362 o NCP V5 IR24307 o NCP V6 IR24170 5.4 NCP Problems with Modulo 128 Token Ring Stations A problem exists in NCP, whereby NCP always indicates that it is able to receive 128 frames between acknowledgments from a modulo 128 token ring station, when in fact it can only receive much fewer. This results in many unnecessary retransmissions, and can seriously degrade performance. This has been corrected with the following APARs from IBM: o NCP V6 IR25667 5.5 INIT-SELF Rejected with Sense Code 10105006 Under heavy traffic conditions, VTAM can intermittently reject INIT-SELF requests with a sense code of 10105006, when in fact the response should be positive. This has been corrected with the following APARs from IBM: o VTAM V4R1 OW02909 o VTAM V4R2 OW04173 5.6 VTAM ABEND S0C4 at ISTATCTR+1F0 VTAM can intermittently ABEND while writing an internal trace record when the Peer Server has just established the data link connection over X.25 or token ring. This has been corrected with the following APARs from IBM: o VTAM V4 OW06433 14 6 Known Problems and Product Restrictions Known restrictions existing in the Version 1.6 software are detailed in this section. 6.1 Common Trace Facility (CTF) Restrictions 6.1.1 LU Tracepoints Not Supported Because of a CTF limitation in the maximum number of concurrently declared tracepoints, Peer Server V1.6 does not support tracing on the LU entity (LU tracepoints) as described in Compaq SNA Peer Server Management. Tracing can be done by Transmission Group to trace activity across all sessions on the TG, or on an individual session basis (Session tracepoints). Despite the lack of LU tracepoints, tracing of all sessions belonging to a specific LU can be accomplished as shown in the following CTF command example (LU name "t001"): ctf>start sna lu services lu t001 session * 6.2 Network Management Restrictions 6.2.1 NCL Delete Transmission Group Generates "Wrong State" Exception A Transmission Group that is dependent LU capable and has one or more enabled LU Services dependent LUs referencing it cannot be deleted until the LUs are themselves disabled. An attempt to delete a Transmission Group with active dependent LUs results in a "Wrong State" error exception. "Wrong State" is also produced for failed attempts to delete a Transmission Group when it is not first disabled (entity state OFF and protocol state RESET), and both conditions must be considered when "Wrong State" is returned. An example of the failure follows: ncl> dele sna cp serv t g tg005 Node 0 SNA CP Services Transmission Group TG005 AT 1994-11-23-10:11:07.000-05:00I----- FAILED IN DIRECTIVE: Delete DUE TO: Error specific to this entity's class 15 REASON: Wrong state Description: Wrong state 6.2.2 NCL Enable SDLC Link Station Generates "Invalid Parameter" Exception An ambiguous NCL exception of "Invalid Parameter" is produced when attempting to enable an SDLC link station where the station and/or the parent link have an invalid Send or Receive Frame Size set, respectively. This is most commonly a problem when configuring SDLC for the built-in SCC device, which has an upper limit size of 1021 bytes. Note the exception occurs when enabling the station and not the link. For example, a link configured with a Receive Frame Size of 1024 (too high) is successfully enabled. Its child station, with a Send Frame size of 1000 (legal) incurs an NCL "Invalid Parameter" exception when it is enabled. The solution in this example is to disable and correct the link Receive Frame Size, re-enable the link, and enable the station. An example of the failure follows: ncl> enable sdlc link sdlc-0 sta stn-40 Node 0 SDLC Link sdlc-0 Station stn-40 AT 1994-05-03-13:04:59.000-04:00I----- FAILED IN DIRECTIVE: Enable DUE TO: Error specific to this entity's class REASON: Failure Description: Failure Reason = Invalid Parameter 6.2.3 LocalEntityName Instance Specification With Peer Server V1.0 it was possible to specify a LocalEntityName instance using parenthesis, for example: set sna cp services trans group tg-1 - datalink = (sdlc link foo station bar) In fact, the V1.0 Initialization and Configuration Utility (t21icu) generated this syntax automatically. 16 Due to some changes in NCL processing introduced with DECnet-Plus V1.6, it is no longer valid to specify LocalEntityNames using parenthesis, and doing so generates an NCL syntax error, e.g. "SYNTAX ERROR: No match was found for this string." The Peer Server t21icu has been modified to accommodate the new requirement; however, if you were a Peer Server V1.0 customer and will be running NCL scripts generated with the older t21icu utility (or generated manually), those scripts must be modified in order to work properly with 1.6. The t21_init_sna_server.log file, located in /var/tmp and created at the time of Peer Server startup, reveals this error. 6.3 SDLC Datalink Restrictions 6.3.1 Multipoint Full Duplex Configuration Requires TWA The use of two-way simultaneous (TWS) transfer mode (as specified on the SDLC link station) in the full duplex multipoint case is not recommended. A known restriction with RTS/CTS handling in the WAN Device Drivers (wdd) can cause aborted frame retransmission and, ultimately, link failure. 6.3.2 Using the PBXDI ISA-Bus Synchronous Communications Controller o Only those models which support RS-232C or V.35 interfaces (PBXDI-AA and PBXDI-AB) are supported for use with SDLC. o Half-duplex is not supported. o Transmission of frames larger than 1022 bytes (including SDLC header) is not supported. The SDLC Link Send Frame Size should not exceed 1020 for modulo 7, and 1019 for modulo 127. o The Interface Type attribute for the Modem Connect Line entity does not accurately reflect whether an RS-232C or V.35 interface is currently in use. This inaccuracy lies in the management attribute only and does not actually affect the operation of the controller. 17 6.4 QLLC Datalink Restrictions 6.4.1 Temporary TGs Lack Automated Call Startup Dependent LU session traffic (for example, 3270 LU2 terminal sessions) does not automatically activate a temporary Transmission Group when initiated from the client (Secondary LU) side. This handling is based on the assumption that an SLU not yet activated from the IBM host (that is, no ACTLU yet received) cannot initiate an LU-LU session (using INIT-SELF). There are circumstances with QLLC and X.25 networks where call initiation based on an SLU request for session could benefit from such behavior. 6.4.2 Filter Name Mismatch Error is Ambiguous As explained in Peer Server documentation, the use of filter names must be consistent between the Compaq WAN product and Peer Server QLLC entity configurations. If a QLLC link is set up with a filter name that doesn't exist in the X.25 configuration, an Enable of the TG fails with: FAILED IN DIRECTIVE: Enable DUE TO: The target implementation does not support this entity class Should this error occur, CTF may be used to determine if the problem is due to a filter mismatch as shown below (no event message is generated in this case). ctf>start qllc link *,live . . 08:06:31.94| Tx| 14| X_LISTEN_RE| 08:06:31.95|Rx | 16| X_ERROR_ACK (xerrno=-176) Specified . filter does not exist . 6.4.3 QLLC Link and Station Must Be Enabled Before TG When configuring a Transmission Group (TG) for use with a QLLC link, the link and underlying link station must be enabled before enabling the corresponding TG. The enable of the TG fails with an "Facility = DLPI, Reason = 1" exception error if this order is not followed. 18 6.5 TN3270 Server Restrictions 6.5.1 TN3270 Server Default Port (2301) Used by Insight Manager The default TCP port for the TN3270 Server is the port number following the last defined port number for the last TN3270 configuration (or TCP port 2301 if no port numbers are defined). If the default port of 2301 is used and the system is running Insight Manager, port 2301 will be in use by the Insight daemon. The error message is: Error binding socket to listening port, errno=48 Workaround: Select another port other than 2301 as the listening TCP port for the TN3270 Server. 6.5.2 TN3270 Server Drops Connection When Client Does Not Respond Properly When a client has successfully negotiated the RESPONSES function and then does not respond appropriately when receiving a RU when in definite response mode, the TN3270 server drops the connection. While the client is required to respond to every RU when in definite response mode, the TN3270 server could be more tolerant with such a minor infraction by the client. However, the current version of the TN3270 server is intolerant of such infractions and drops the connection every time the client fails to properly respond. Workaround: If this is happening with your client, you can disable the RESPONSES function when configuring the TN3270 server. 6.6 LLC2 Datalink Performance Issues 6.6.1 FDDI Performance In order to allow high throughput of data via the FDDI datalink, it is necessary to change the LLC2 Sap Link Holdback Timer characteristic attribute from the default value of 500ms to 10ms. To have this value set when the Peer Server is started, it is necessary to change the Peer Server startup NCL file /var/sna/t21_init_sna_server.ncl. The Peer Server uses this NCL startup configuration file every time the Peer Server starts. Because of the overhead associated with data processing through the UNIX kernel, FDDI performance is a function of system capability, in 19 particularly CPU speed. (This is also true when using TCP over a FDDI datalink.) Testing has indicated that with the Holdback Timer set to 10 ms, and a properly sized system, FDDI data rates in access of 80 megabit/second can be achieved when using Peer Server. (Note: The degradation in performance associated with the Holdback Timer is also manifested in CSMA-CD and Token Ring data links. Although it is more noticeable in FDDI, performance degradation can be significant in any of the datalinks and the default setting of the Holdback Timer attribute should be changed for all data links.) 7 Files Installed/Modified Table 1 lists all the files placed onto the system during the Peer Server installation, or created during configuration. Table_1_Peer_Server_Installed_Files________________________ ___Directory_____________Filename__________________________ /dev/streams/ t21_smgd t21cpnm t21ctrl t21mgmt t21llc q25_qllc q25_mgd q25_xpi t21sd_ctrl t21sd_mgmt t21cd_ctrl t21cd_mgmt t21trc t21sdlc t21cdlc (continued on next page) 20 Table_1_(Cont.)_Peer_Server_Installed_Files________________ ___Directory_____________Filename__________________________ t21sess0 t21wadd /sbin/init.d/ t21_sna_server /sbin/rc0.d/ K09t21_sna_server /sbin/rc3.d/ S90t21_sna_server /sys/opt/T21SRVR200/ config.file files /usr/sbin/ t21cad t21cadgas t21mad t21mcd t21smd t21smc q25mad q25mcd t21trcd t21setup tn3270_config tn3270_server tn3270_server_start /usr/share/dna/dict/ t21_server.hlp /var/sna/ q25mcd.conf t21icu t21mcd.conf t21smc.conf t21strsetup.conf (continued on next page) 21 Table_1_(Cont.)_Peer_Server_Installed_Files________________ ___Directory_____________Filename__________________________ t21_V16-0_release_notes /var/subsys/ t21llc.mod t21qllc.mod t21scl.mod t21scl.stanza t21sdlc.mod t21cdlc.mod _________________________t21spd.mod________________________ Table 2 lists the Peer Server configuration files. Table_2_Peer_Server_Configuration_Files____________________ ___Directory_____________Filename__________________________ /var/sna/ t21_init_sna_server.ncl t21_init_sna_server.ans ___/usr/sbin/____________tn3270_conf.nnn___________________ Table 3 lists the files that Peer Server uses for logging. Table_3_Peer_Server_Files_Used_for_Logging_________________ ___Directory_____________Filename__________________________ var/tmp/ t21_init_sna_server.log var/adm/ syslog.dated/date/daemon.log ___var/adm/______________syslog.dated/date/kern.log________ Table 4 lists various operating system or layered product files that are replaced or modified by the Peer Server installation and configuration. 22 Table_4_Peer_Server_Modified_Files_________________________ ___Directory_____________Filename__________________________ /usr/bin/ ctf /usr/share/ctf/ ctfua_library.c libctflibs.a ___/usr/share/dna/_______ncl_help.txt______________________ 23