Patch Name: PHKL_7297 Patch Description: s700 9.01 Diskless packets cumulative patch Creation Date: 96/04/15 Post Date: 96/04/24 Hardware Platforms - OS Releases: s700: 9.01 Products: N/A Filesets: KERN-BLD Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_7297: PANIC PHKL_6891: PANIC PHKL_6054: PANIC PHKL_5244: PANIC Path Name: /hp-ux_patches/s700/9.X/PHKL_7297 Symptoms: PHKL_7297: panic: recv_ack: bad serving_array state PHKL_6891: See PHKL_7297 PHKL_6054: panic: close_serve: illegal fs type panic: stprmv: illegal fs type panic: getrmount: no mount PHKL_5244: If corrupted dux packets are not caught, the user could see panics such as close_serve: illegal fs type. This patch will not allow a bad packet to get through thus causing a resend and eliminating a system panic. Defect Description: PHKL_7297: Request ID in a DUX packet is incremented sequentially from zero on each cnode. If a serving_array entry on the server is used and freed for one client, then a second client acquires the same serving_array entry and uses the same request ID, then a duplicate ACK arrives from the first client (perhaps due to the use of smart routers), the server assumes the ACK is for the second client. This patch also checks client information to reject the duplicate packet. PHKL_6054 could not be installed on a mixed cluster. This patch does NOT verify checksums on packets originating from Series 300/400 clients, so it can be installed on a mixed cluster WITH THE UNDERSTANDING that communication between the server and Series 300/400 clients is not protected from corrupt packets with a checksum. PHKL_6891: See PHKL_7297 PHKL_6054: Dux Packets are becoming corrupt during the transfer from client to server or server to client. Dux did not have a check sum capability to detect corrupt packets. PHKL_5244: There are various hardware and software that could be respon sible for causing a corrupt dux packet. However, by adding checksumming to dux, a corrupt packet can be caught and rejecting before causing a panic. The system will automatic ally resend the request so that nothing is lost. SR: 1653117689 5003243428 5003301424 Patch Files: /etc/conf/libdskless.a(cluster.o) /etc/conf/libdskless.a(protocol.o) what(1) Output: /etc/conf/libdskless.a(cluster.o): cluster.c $Revision: 1.11.81.3 $ $Date: 96/03/04 15:11:00 $ PATCH_9.01 (PHKL_6891) /etc/conf/libdskless.a(protocol.o): protocol.c $Revision: 1.13.81.7 $ $Date: 96/04/1 5 16:13:04 $ PATCH_9.01 (PHKL_7297) sum(1) Output: 19862 27 /etc/conf/libdskless.a(cluster.o) 23962 69 /etc/conf/libdskless.a(protocol.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_5244 PHKL_6054 PHKL_6891 Equivalent Patches: PHKL_7298: s700: 9.03 9.05 9.07 Patch Package Size: 110 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. Copy the patch to your /tmp directory and unshar it: cd /tmp cp patch_source/PHKL_7297 . sh PHKL_7297 3. Become root and run update: /etc/update [-r [kernel_gen_file]] -s \ /tmp/PHKL_7297.updt PHKL_7297 Update moves the original software to /system/PHKL_7297/orig. Keep this file to recover from any potential problems. You should move the .text file to /system/PHKL_7297 for future reference. To put this patch on a magnetic tape and update from the tape drive, use dd: dd if=PHKL_7297.updt of=/dev/rmt/0m bs=2048 Special Installation Instructions: None