Patch Name: PHNE_16502 Patch Description: s700_800 10.20 HSC FDDI B.10.20.0[1-5] cumulative patch Creation Date: 98/09/24 Post Date: 98/10/07 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: HSC FDDI B.10.20.01 B.10.20.02 B.10.20.03 B.10.20.04 HSC FDDI B.10.20.05 Filesets: FDDI-HSC.FDDI3-KRN,B.10.20.01 FDDI-HSC.FDDI3-KRN,B.10.20.02 FDDI-HSC.FDDI3-KRN,B.10.20.03 FDDI-HSC.FDDI3-KRN,B.10.20.04 FDDI-HSC.FDDI3-KRN,B.10.20.05 FDDI-HSC.FDDI3-RUN,B.10.20.01 FDDI-HSC.FDDI3-RUN,B.10.20.02 FDDI-HSC.FDDI3-RUN,B.10.20.03 FDDI-HSC.FDDI3-RUN,B.10.20.04 FDDI-HSC.FDDI3-RUN,B.10.20.05 FDDI-CMD-COM.FDDI-CMD,B.10.20.01 FDDI-CMD-COM.FDDI-CMD,B.10.20.02 FDDI-CMD-COM.FDDI-CMD,B.10.20.03 FDDI-CMD-COM.FDDI-CMD,B.10.20.04 FDDI-CMD-COM.FDDI-CMD,B.10.20.05 Automatic Reboot?: Yes Status: General Superseded Critical: Yes PHNE_16502: PANIC PHNE_15666: OTHER Card hang. PHNE_14792: PANIC PHNE_14078: OTHER Card hang. PHNE_14074: MEMORY_LEAK When multicast packets are received on the HSC FDDI link, the driver leaks memory. Path Name: /hp-ux_patches/s700_800/10.X/PHNE_16502 Symptoms: PHNE_16502: 1. With heavy traffic on the HSC FDDI link, if multiple instances of ioscan(1M) are simultaneously executed, the system may panic with an HPMC. 2. Applications that use the SAP promiscuous mode may not receive packets destined for them from the HSC FDDI link. 3. Under sustained heavy load conditions, the system may sometimes hang or panic. PHNE_15666: 1. The HSC FDDI interface may hang after logging the message "Waited for stat2_ine4 but it never came" to syslog. 2. When the MAC address of the HSC FDDI card is changed, the link becomes unusable for up to 10 seconds during which a large number of void frames are seen on the ring. 3. DLPI applications that use hierarchical sub-binding to SNAP SAPs other than IP or ARP may sometimes receive packets not meant for them from the HSC FDDI link. PHNE_14792: 1. linkloop(1M) over HSC FDDI may panic the system it is run on. PHNE_14078: 1. Under heavy load, the HSC FDDI card may hang (will not receive or send data). 2. Under certain conditions, too many informative driver messages are logged to syslog, causing it to overflow. 3. The fddiif utility sometimes reports negative numbers in the statistics. 4. When the locale is set and lanadmin(1M) is used in the interactive mode, after a certain number of commands, the following error message is displayed: Cannot open shared library ... PHNE_14074: 1. When multicast packets are received on the HSC FDDI link, memory is leaked in the driver. The system eventually runs out of free memory. 2. Multicast packets cannot be sent or received by applications on the HSC FDDI link. PHNE_13190: 1. The HSC FDDI link does not work on D-class 210/310, 220/320 and 230/330 systems. ioscan(1M) shows that the HSC FDDI card is unclaimed. 2. When the HSC bus contention goes high which means many other devices are sharing the same HSC bus with the HSC FDDI link and the HSC bus is heavily used, the HSC FDDI link has too many transmit and receive errors. Defect Description: PHNE_16502: 1. When heavy inbound traffic occurs, and ioscan(1M) is run simultaneously, the bus adapter on the HSC FDDI interface card puts out an invalid address on the bus. This leads to a panic with HPMC. 2. The source and destination MAC addresses on inbound promiscuous SAP packets were being sent up to the DLPI layer in wire format, while DLPI assumes them to be in canonical format. 3. The driver was not freeing allocated memory in certain error paths. PHNE_15666: 1. A software reset mechanism was introduced in the HSC FDDI driver to work around hardware defects in the Motorola FDDI System Interface (FSI) chip. This mechanism did not detect all the circumstances under which the card had to be reset. 2. The HSC FDDI driver is required to disconnect the card from the FDDI ring before changing the MAC address. This was not being done. 3. The driver forwarded SNAP packets that were neither IP nor ARP to all applications registered with SNAP SAPs other than IP or ARP. PHNE_14792: 1. The HSC FDDI driver assumed that MAC addresses were 16-bit aligned. This assumption is incorrect for linkloop packets. PHNE_14078: 1. A defect in the Motorola FSI chip causes the card to hang under heavy load. 2. SMT and other informative messages are incorrectly sent to syslog instead of the NetTL log by the HSC FDDI driver. 3. Though the statistics are maintained as unsigned integers by the driver, fddiif displays them as signed values. 4. The HSC FDDI lanadmin(1M) shared library does not close the catalog file after using it. PHNE_14074: 1. The driver relies on upper layers of the networking stack to free the memory allocated for the packets that are received. When multicast packets are received, they are not sent to the upper layers and consequently the memory allocated is not freed. 2. When checking for multicast packets (while sending or receiving data) the driver erroneously assumes that the link-level multicast address is in canonical format, while, in reality, the address is in wire format. PHNE_13190: 1. The HSC FDDI uses the node "id" property to identify a T600 system. The D-class 210/310, 220/320, and 230/330 systems do not have the "id" property defined. Thus, the HSC FDDI link does not get initialized. 2. The high error rate problem is caused by a combination of contention on the HSC bus and the small amount of memory (8K bytes) on the HSC FDDI card. The problem is seen easily if the HSC FDDI card has been put in the Core HSC slot on a K-Class system. Although the "lanadmin -S tx_threshold" command can adjust the card transmit buffer for the outbound data, in a heavily used bus, the inbound data shows many receive errors. A special setting "lanadmin -S 0" is introduced in this patch. Using this will result in a decrease in HSC bus contention. SR: 1653273540 1653266973 1653266783 1653265728 1653248476 5003413930 5003413948 5003404764 Patch Files: /usr/conf/lib/libfddi3.a /usr/conf/lib/fddi3_header.o /usr/conf/master.d/fddi3 /usr/lib/lanadmin/libdsfddi3.1 /usr/lib/lanscan/libpefddi3.1 /usr/lib/libfddifmt3.1 /usr/lib/nls/msg/C/fddi3.cat /usr/bin/fddiif /usr/bin/fddilink /usr/bin/fddidump what(1) Output: /usr/conf/lib/libfddi3.a: HSC FDDI fddi3 libfddi3 B.10.20.06 PHNE_16502 $Date: 98/09/29 11:16:06 $ /usr/conf/lib/fddi3_header.o: None /usr/conf/master.d/fddi3: None /usr/lib/lanadmin/libdsfddi3.1: libdsfddi3.1 HSC FDDI B.10.20.04 $Date: 98/04/21 02: 07:17 $ /usr/lib/lanscan/libpefddi3.1: libpefddi3.1 HSC FDDI B.10.20.04 $Date: 98/04/21 02: 10:03 $ /usr/lib/libfddifmt3.1: libfddifmt3.1 HSC FDDI B.10.20.05 PHNE_15666 $Date: 98/07/16 16:48:57 $ /usr/lib/nls/msg/C/fddi3.cat: None /usr/bin/fddiif: fddiif EISA/HSC FDDI B.10.20.06 PHNE_16501/2 $Date: 98/09/24 18:21:54 $ /usr/bin/fddilink: fddilink EISA/HSC FDDI B.10.20.06 PHNE_16501/2 $Date : 98/09/24 18:26:32 $ /usr/bin/fddidump: fddidump EISA/HSC FDDI B.10.20.06 PHNE_16501/2 $Date : 98/09/24 18:20:39 $ cksum(1) Output: 1034989769 80352 /usr/conf/lib/libfddi3.a 2715146514 217608 /usr/conf/lib/fddi3_header.o 4146639522 3767 /usr/conf/master.d/fddi3 1015895798 16384 /usr/lib/lanadmin/libdsfddi3.1 4114988726 12288 /usr/lib/lanscan/libpefddi3.1 2664493503 20480 /usr/lib/libfddifmt3.1 3409149713 6468 /usr/lib/nls/msg/C/fddi3.cat 1136568579 20480 /usr/bin/fddiif 3331003948 65536 /usr/bin/fddilink 1646894325 20480 /usr/bin/fddidump Patch Conflicts: None Patch Dependencies: s700: 10.20: PHKL_16448 s800: 10.20: PHKL_16449 Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_13190 PHNE_14074 PHNE_14078 PHNE_14792 PHNE_15666 Equivalent Patches: None Patch Package Size: 520 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_16502 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_16502.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_16502.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_16502. 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_16502.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_16502.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None