Patch Name: PHNE_13604 Patch Description: s700_800 10.01 R4.1/R4.2 SNAplus Link cumulative patch Creation Date: 98/04/17 Post Date: 98/05/19 Hardware Platforms - OS Releases: s700: 10.01 s800: 10.01 Products: SNAplusLink R4.2 Filesets: SNAP-LINK.SNAP-LINK Automatic Reboot?: Yes Status: General Superseded Critical: No (superseded patches were critical) PHNE_9759: PANIC PHNE_9552: PANIC PHNE_7067: HANG PHNE_6652: PANIC Path Name: /hp-ux_patches/s700_800/10.X/PHNE_13604 Symptoms: PHNE_13604: (1) 5003382994 When starting a Node with initially-active connection(s) it may report error SNA0039. The initially-active connections come up correctly on a retry. PHNE_9759: (1) 1653185140 1/ SNAPlus takes the X25 address from the X121 address field instead of the X121 packect address filed in X25 configuration file. 2/ Incoming calls are rejected when an SNA subaddress is configured. (2) 1653201301 Crash occasionally on reboot when there is a small flurry of activity (the RJE workstation is killed and we issue TERM-SELF messages for the LUs). We go into a flow control condition temporarily and this gets released after the SNA software has been terminated (the router terminate log is queued up in the kernel). The token ring glue module tries to process the flow control release event with terminated data structures and the panic occurs. (3) 1653219204 Link failures with SDLC 64K link on D class system while working fine at 19.2K or on 64K link for E class system. SDLC Link fails when activating 3270 sessions, with the message 'LOST INTERUPT' in SNA trace files. (4) 1653207761 Queued operator started TP hangs for 30 seconds when RECEIVE_ALLOCATE issued even though attach has been received. In fact attach received while previous copy of TP still running (that does not issue a second RCV_ALLOC). The DLOAD is retransmitted by the 2.1 DMOD on a 30 second timer which then satisfies the RCV_ALLOCATE. (5) 1653212332 Certain TN3270 products will not connect to TN Server because we do not support the correct TN3270 regime. (6) 1653215681 Raw VTAM application (not CICS) treats our deactivation of SNASVCMG session (when it the only one) as a fatal error for conversations on that mode. Other SNA implementations do not deactivate the SNASVCMG sessions. (7) 1653227611 Parallel mode with initially active sessions. Host resets sessions by UNBIND on all sessions (CICS taken down for the night). Auto-CNOS also rejected with UNBIND. When CICS restarts and session limit set we fail to activate 1 session. Each night another session is lost. Sessions cannot be activated by snamanage. (8) 1653234948 SNAplusLink R4.4 EISA PSI Constant Carrier not raising RTS (9) 1653237644 Crash during start up (link activation). Caused by getting BIND with bad URC field that does not match the URC from INIT-SELF. Failure in s1pcasrp or s1psineg. (10) 5003378166 Could not use multipoint SDLC and configure the link as full duplex because this required that constant carrier be configured. However, constant carrier does not work on with multipoint SDLC - RTS is no longer set on continually when SNAPlus is configured for constant carrier. PHNE_9552: (1) 4701343178 The problem is actually the same as that fixed in SR1653183947 ,even though the stack looks different. The problem occurs because the customer has an unusual configuration and then gets a certain error sequence. Specifically the customer has a dependent LU6.2 local LU with a single remote LU and multiple associated modes which are configured as initially active. (2) 1653183947 The problem occurs because the customer has an unusual configuration and then gets a certain error sequence. Specifically the customer has a dependent LU6.2 local LU with a single remote LU and 2 associated modes. One of these modes (APPC4K) has an initially active session configured (session limits 1,1,0,1) and the other mode (APPC1K) has an on demand session (limits 1,0,0,0). The problem only occurs with the modes in this order (alphabetically sorted by mode name). We have first had a time-out trying to activate the SDLC connection (so the initially active mode is marked as needing retry). We then get an Allocate for the on demand mode before the connection is retried. When we get ACTLU for the LU we try to activate both modes (internally queuing an INIT-SELF for APPC1K) and get into an infinite loop (the kernel trace buffer is full of logs SNA0026 for APPC4K). (3) 1653191924 On R4.2 customer configured incoming peer SDLC connection. DTR was raised but instead of frames being received RX overrun and Lost interrupt events occured. Short frames could be received, frames could be transmitted. (4) 1653112474 SNAplus connections over LAN links fails to detect link outages. (5) 1653185306 The case of a N_PVC_DETACH indication was treated like a N_PVC_DETACH confirmation: The outage was not reported to the Node. (6) 1653185454 Everything works fine for the first connection, but when the customer deactivates the connection from the Host he/she can't reactivate it unless the Link is stopped and started. (7) 1653185348 Following a X25 Virtual Circuit Reset, the customer has to restart SNAplus node/link to reestablish a connection with the Host. (8) 1653161919 Connection stays status 'starting' when a tp hangs. The customer deactivates the connection. After he has activated it again the connection does not come up. It stays in starting state. Even stopping and starting the daemon is useless. Only after a reboot the connections comes up again. (9) 1653179788 A kernel panic with the following stack trace uniquely identifies this problem: panic+0x10 report_trap_or_int_and_panic+0x8c trap+0xbf0 $RDB_trap_patch+0x20 s1pupbnd+0xd4 s1pucsc+0x2f4 s1pusvc+0x3e4 s1pgdisp+0x20c (10) 1653180125 panic: (display==0xbf00, flags==0x0) Data segmentation fault Stack as follows starting sp=0x7ffe6fc0 panic+0x1c ( arguments not stored ) pc=0x2625c0, pfmp=0x7ffe6f60, psp=0x7ffe6f80 trap+0xaac ( arguments not stored ) pc=0x1c15f0, pfmp=0x7ffe6ea0, psp=0x7ffe6ec0 trap marker save state 0x7ffe6c90 sp 0x7ffe6ec0 framesize 0x230 s1pxabnd+0x1b1 ( 0x7ffe1712 ,0x003d0002 ,0x00000000 ,0x7ffe0149 ) pc=0x147ffc, pfmp=0x7ffe6bf0, psp=0x7ffe6c10 s1pxsnd+0x8c9 ( arguments not stored ) pc=0x144f64, pfmp=0x7ffe6b70, psp=0x7ffe6b90 s1pgdisp+0x385 ( 0x004d0028 ,0x7ffe6afc ,0x7ffe0001 ,0x660000fd ) pc=0xe3e94, pfmp=0x7ffe6b30, psp=0x7ffe6b50 sna_1_sbpsched+0x10d ( arguments not stored ) pc=0x158ca8, pfmp=0x7ffe6ab0, psp=0x7ffe6ad0 sna_1_sbpikusv+0x55 ( 0x01263074 ,0x00000000 ,0x00000098 ,0x00004321 ) pc=0x152518, pfmp=0x7ffe6a70, psp=0x7ffe6a90 sq_wrapper+0x5c ( arguments not stored ) pc=0x93188, pfmp=0x7ffe6a30, psp=0x7ffe6a50 csq_lateral+0x80 ( arguments not stored ) pc=0x96174, pfmp=0x7ffe69b0, psp=0x7ffe69d0 runq_run+0x58 ( arguments not stored ) pc=0x930d4, pfmp=0x7ffe6970, psp=0x7ffe6990 str_sched_daemon+0x1b0 ( arguments not stored ) pc=0x934e0, pfmp=0x7ffe68b0, psp=0x7ffe68d0 main+0xa04 ( arguments not stored ) pc=0x24c814, pfmp=0x7ffe67f0, psp=0x7ffe6810 $vstart+0x3d ( arguments not stored ) pc=0x1b1fa4, pfmp=0x7ffe67c0, psp=0x7ffe67e0 istackatbase+0x88 ( arguments not stored ) pc=0x1c5f0, pfmp=0xffffffe0, psp=0x0 (11) 1653181545 The system panics 10 min after starting the SNAPlusLink. panic+0x0010 nio_build_dma_quads+0x0170 snap_nio_write+0x01f4 svphtx+0x01a0 slphtfrm+0x04ed slptxset+0x02d9 slptxpmt+0x0d1d slpprtmg+0x0699 slpwrxfr+0x035d slpwrkmg+0x00c9 sna_l_sbpsched+0x0441 sna_l_sbpikusv+0x004d sq_wrapper+0x00e0 str_sched_up_daemon+0x017c str_sched_daemon+0x00b4 main+0x0918 $vstart+0x003d (12) 5003320341 Snaplus R4.1 ethernet (802.3) connection fail to recover if host link is inactive for greater than 1 & 1/2 hours. The R4.1 system reports the following error every 10secs after the 1 & 1/2 hrs in sna.aud: LAN T10SNA9706: Exceeded maximum connections allowed for 802.3 link LAN on node NODE1 After this error is recorded the only way to recover the connection is to stop and start the link used by that connection. (13) 4701335000 Customer may get a variety of communication path errors on any of the services, but this is most likely to hit those who are running a large number of TPs. (14) 5003287276 3270 sessions are not completely logged off when the user exits 3270 using Ctrl-C, or from the file pull down menu. (15) 4701319681 Deactivating QLLC1 sometimes would cause the system to panic with data page fault. The stack trace showed: panic+0x10 report_trap_or_int_and_panic+0x8c trap+0xb6c $call_trap+0x20 sqpsdisc+0x70 sqpmcllk+0x1a8 sna_q_sbpikuwp+0x710 putnext+0x74 sna_r_svpdrput+0xc38 sna_r_svpdrlrp+0x4bc putnext+0x74 putmsg_subr+0x2c0 putmsg+0x844 syscall+0x1a8 PHNE_7067: (1) 4701325399 APPC TPs will not work when one of the machines is migrated from the R4 line of releases to the R5 line. (2) 1653170928 The SNAplus system hangs when trying to start a connection when the host rejects the session binds. (3) 1653153957 Only one Session Binds successfully when multiple sessions try to use the APPC default LU pool. PHNE_6652: (1) 1653155317 Intermittent System Panic caused by PU2.1 Defect Description: PHNE_13604: (1) 5003382994 The underlying problem is a race between the ADD_SVCE messages from the router and the Node intialisation processing. We suppress the logging of SNA0039 until we have received at least one ADD_SVCE message. PHNE_9759: (1) 1653185140 1/ Coding error: bad field is taken to initialize SNA X25 address value. 2/ QLLC does not pass the SNA subaddress to the Glue so that the Glue registers to X25 only on the X121 address. Then, either X25 rejects the incoming call if called address includes the subaddress or X25 accepts the call if called address does not include subaddress but then SNA rejects the incoming call because it checks the called address against its subaddress. (2) 1653201301 The fix is simply to check for terminated data structures in the lower write service procedure (a similar check to other streams entry points). (3) 1653219204 The 'LOST INTERUPT' message is reported in traces because the firmware detected that the frame size received from the network is too long compared with its configured maximum frame size which is hard-coded to 269. And effectively, the host, configured with a MAX_DATA of 1500 is sending frames of moe than 269 bytes. (4) 1653207761 When ADD_SVCE received at 2.1 DMOD we check to see if the ADD_SVCE is for a QD_OP TP and if there is a queued DLOAD for that TP. If so a copy of it is sent to the TP at once. (5) 1653212332 Since TN3270 regime is an optional part of the protocol, this code has been removed, forcing the negotiation exchange to use alternative supported methods. (6) 1653215681 Test for SNASVCMG before starting deactivation timer (20 seconds). (7) 1653227611 We failed to clean up a suspended pending session in this case. Code change made to do reset the session following the CNOS UNBIND. (8) 1653234948 The firmware has been changed so that it takes into account the Constant Carrier configuration for RTS correct behaviour. (9) 1653237644 Code change made to not allow bad value of mode control block index to be used when trying to send -ve ACT session RSP. (10) 5003378166 A change has been made so that the RTS is dropped at the end of the frame transmission independant of which carrier type is configured. PHNE_9552: (1) 4701343178 The problem can be resolved by either :- a) the customer can reconfigure his system to change the mode records to not have initially active sessions (alter from 1,1,0,1 to 1,1,0,0) or b) install the PU 2.1 node fix (version 207 of libsix1.a in R4.2). (2) 1653183947 The fix is to prevent any looping for ACTLU processing which can only have 1 mode that can be processed. The customer could also prevent the problem by altering the configuration to make the APPC4K mode not initially active (change the session limits to 1,1,0,0) or remove one of the modes. This would also prevent some of the error logs that he will get with this configuration as the two modes compete for the LU. (3) 1653191924 Problem was that the HMOD was being primed with a frame size of 5, the configured frame size in the connection record was not reflected in the link record. Altered the link record to point to link data of the first connection in all cases (already done for Host links). Also sent fix to HMOD. (4) 1653112474 This enhancement request has now been included on the main code for SNAPlus - so will be available in all future SNAP-LINK patches as standard. Because it uses the LAN inactivity timer which is a function of the DLPI interface, it requires the current DLPI patch to be installed, up until SNAplus R4.4 (hp-ux 10.20). (5) 1653185306 The processing of a Disconnect Indication generates two calls to the Close Connection routine. (6) 1653185454 The Connection Control Block structure is released before the reception of the X25 Disconnect Confirm, preventing the glue from completing the Node's CLOSE(LINK). (7) 1653185348 The processing of a Disconnect Indication generates two calls to the Close Connection routine. (8) 1653161919 There was no timer implemented to de-activate a connection after a certain length of time. This problem occurs on FDDI and Ethernet connections as well. (9) 1653179788 The problem occurred because we fail to associate a new control block for an incoming dependent LU BIND with the associated SSCP control block. There is a window in the code where we can re-use a control block before it has been freed after a previous session using the same OAF/DAF has been brought down safely - ensure that under these circumstances we cleanly terminate all reference to the old (now dead) session, and set things up correctly for processing the new session activation. (10) 1653180125 The problem is caused by an unusual LU 6.2 SNA sequence talking to the mainframe: RX BIND (dependent, CL) TX BIND +ve RX FMH5 RQD2 (S.N. 1), TP starts Kill TP, TX -ve RSP, TX FMH7 CEB RQD1 RX FMH7 CEB RQD1 (S.N. 2), TX +ve (S.N. 8000) RX FMH5 BB RQD2 (S.N. 3), TP starts RX +ve (S.N. 8003) - we detect BETB condition as the send chain FSM is pending RSP with CEB in it and then decouple the SCB and RCB leading to later crash when we get lost locality from the TP being killed. The SNA is unusual because there are 2 FMH7 CEBs (Deallocate Abend), the Host's one looks to be superfluous but is allowed through by the APPC protocols. The Host also delays responding to the CEB we send until part way through the next bracket and uses the current bracket sequence number (so the response does not appear stray). (11) 1653181545 This is a duplicate of the SR 4701317925 panic. The fix for 4701317925 was PHNE_7014 but that was R4.3/10.10 and this system can't be upgraded so we need a patch for R4.1/10.01. (12) 5003320341 No timer was implemented on the Ethernet connection. (13) 4701335000 When the customer has used up all of the Service Table entries, the node (PU2.1) will be unable to handle any more requests from the services causing various types of errors. (14) 5003287276 The reason sessions aren't completely logged off is that 3270 exits with a TERMSLF instead of an UNBIND. Since IBM implementations currently send UNBINDs in this type of situation, it is reasonable to change our product to do the same. In fact, our SNAplus2 3270 product already behaves this way. (15) 4701319681 System panic deactivating multiple QLLC link stations. This problem occurred while testing the dual-port PSI card and only occurs with the streams X.25. This is not a problem when running with classic X.25. PHNE_7067: (1) 4701325399 The cause of the problem is the lack of a fully qualified LU name on the R4 side. The R5 behaves correctly and sends the Fully Qualified LU name but then it doesn't match the table entry on the R4 side. This fix makes the R4 Node smart enough to match the LU names. (2) 1653170928 The SNAplus system sits in a loop retrying the BINDS which the host has rejected. Eventually a race condition is hit and the entire system hangs. (3) 1653153957 SNAplus always attempts to use the same LU even if there are other available LUs in the default LU pool. PHNE_6652: (1) 1653155317 Problem seems to occur as a result of killing a TP running on a dependent LU6.2 session. SR: 5003382994 5003378166 5003320341 5003287276 4701343178 4701335000 4701325399 4701319681 1653237644 1653234948 1653227611 1653219204 1653215681 1653212332 1653207761 1653201301 1653191924 1653185454 1653185348 1653185306 1653185140 1653183947 1653181545 1653180125 1653179788 1653170928 1653161919 1653155317 1653153957 1653112474 Patch Files: /usr/conf/lib/libpsi0.a /usr/conf/lib/libsix1.a /usr/conf/lib/libsixet.a /usr/conf/lib/libsixfd.a /usr/conf/lib/libsixl.a /usr/conf/lib/libsixn.a /usr/conf/lib/libsixqs.a /usr/conf/lib/libsixtk.a /opt/sna/bin/snaptnstub /opt/sna/sdlc.dlf /opt/sna/sdlc.pbs what(1) Output: /usr/conf/lib/libsixn.a: A.10.01.100 SNAplus R4.2 TN Server Core (PHNE_9552: 96/09/05 16:37:50) /usr/conf/lib/libsixqs.a: A.10.01.203 SNAplus R4.2 Streams QLLC (PHNE_9759 : 97/03/20 09:53:32) /usr/conf/lib/libsix1.a: A.10.01.303 SNAplus R4.2 PU 2.1 (PHNE_13604 : 98/02/10 18:11:47) /usr/conf/lib/libsixl.a: A.10.01.301 SNAplus R4.2 SDLC in the kernel (PHNE_9759 : 97/06/25 14:25:46) /usr/conf/lib/libsixet.a: A.10.01.205 SNAplus R4.2 802.3 (PHNE_9759 : 97/02/06 19:28:01) /usr/conf/lib/libsixfd.a: A.10.01.204 SNAplus R4.2 FDDI (PHNE_9759 : 97/02/06 19:28:52) /usr/conf/lib/libsixtk.a: A.10.01.205 SNAplus R4.2 Token Ring (PHNE_9759 : 97/02/06 19:26:54) /usr/conf/lib/libpsi0.a: A.10.01.202 SNAplus R4.2 PSI Driver (PHNE_9552 : 96/11/21 16:52:57) /opt/sna/bin/snaptnstub: A.10.01.201 SNAplus R4.2 TN Server Stub (PHNE_9759 : 97/05/06 14:02:22) /opt/sna/sdlc.dlf: SNAPlus EISA FW v2.2 /opt/sna/sdlc.pbs: SNAplus NIO FW v2 cksum(1) Output: 549805578 72992 /usr/conf/lib/libsixn.a 3657313180 191068 /usr/conf/lib/libsixqs.a 2586172605 901944 /usr/conf/lib/libsix1.a 641147996 239448 /usr/conf/lib/libsixl.a 1533807453 184176 /usr/conf/lib/libsixet.a 2248931910 183472 /usr/conf/lib/libsixfd.a 1896325519 183156 /usr/conf/lib/libsixtk.a 3023970227 44712 /usr/conf/lib/libpsi0.a 2591950082 65536 /opt/sna/bin/snaptnstub 523559243 105232 /opt/sna/sdlc.dlf 1667265622 172168 /opt/sna/sdlc.pbs Patch Conflicts: None Patch Dependencies: s700: 10.01: PHNE_13605 s800: 10.01: PHNE_13605 Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_6652 PHNE_7067 PHNE_9552 PHNE_9759 Equivalent Patches: None Patch Package Size: 2360 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHNE_13604 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_13604.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHNE_13604.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_13604. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHNE_13604.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_13604.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Stop SNA daemon before installing patch (snapstop daemon). After installing the patch start the SNA daemon (snapstart daemon).