Patch Name: PHNE_26550 Patch Description: s700_800 11.00 PCI FDDI B.11.00-B.11.00.16 cumulative patch Creation Date: 02/06/04 Post Date: 02/07/11 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: PCI FDDI B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.05 B.11.00.08 B.11.00.11 B.11.00.12 B.11.00.13 B.11.00.15 B.11.00.16 Filesets: FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_32,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.11,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.12,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.13,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.15,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.16,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDDI4-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.11,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.12,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.13,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.15,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.16,fa=HP-UX_B.11.00_32/64,v=HP FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP Automatic Reboot?: Yes Status: General Release Critical: No (superseded patches were critical) PHNE_20874: PANIC PHNE_19542: ABORT PANIC PHNE_18524: PANIC CORRUPTION A reset while on the interrupt stack can cause a panic or a data corruption. PHNE_17517: HANG The interface can hang while transmitting UDP packets. PHNE_16689: HANG After an interface hang, manual intervention is required to get the link going again. PHNE_15670: PANIC HANG OTHER The V-class system may panic or hang during boot. With the Gigabit Ethernet card, the system may come up, but the FDDI adapter card will be unusable. PHNE_14555: PANIC PHNE_13212: OTHER The affected interface may appear to be hung. PHNE_13184: PANIC Category Tags: defect_repair enhancement general_release critical panic halts_system corruption Path Name: /hp-ux_patches/s700_800/11.X/PHNE_26550 Symptoms: PHNE_26550: 1. SR: 8606227088 CR: JAGad96150 ftp/rcp applications fail on PCI FDDI link while transferring a file from a NFS mounted file system to a remote node. The following message is logged in syslog.log: "More than one page crossing". 2. SR: 8606182683 CR: JAGad51900 In case of non-cache coherent A and B class systems, PCI FDDI driver prints the following message repeatedly on the system console or syslog.log file: "vmunix FDDI[2] WARNING: cmd=0 failure status=lcee90". However PCI FDDI link continues to function normally. 3. SR: 8606156934 CR: JAGad26268 ER: SNMP sub-agent for PCI FDDI is not available. 4. SR: 8606166638 CR: JAGad35925 PCI FDDI link goes DOWN on an highly loaded system with its entry being removed from the routing table. Reset of the adapter brings the FDDI link UP. 5. SR: 8606168617 CR: JAGad37895 If the system is installed with PHCO_21596 or its superseding patch, and later "insf -e" is run to re-create the device files, fddipciadmin command fails with a message similar to the following : "fddipciadmin:/dev/lan1 is not a valid device, errno = 19". 6. SR: 8606220085 CR: JAGad89226 "Set user ID" bit should not be set for PCI FDDI lanadmin shared library. 7. SR: 8606257419 CR: JAGae21722 ER: The unsolicited events logged in NetTL log file, by PCI FDDI driver do not provide event type information. 8. SR: 8606257686 CR: JAGae21989 Reset of PCI FDDI adapter sometimes fails with the following message on the system console or in syslog.log file: "vmunix fddi4[2], reclaim_res: Card in wrong state 4, ff, 872, fddi4_rest". 9. SR: 8606263674 CR: JAGae27999 If the T_Req value is set using fddipciadmin command and is followed by a lanadmin reset, then PCI FDDI driver sets an invalid T_Req value in the adapter. 10.SR: 8606263677 CR: JAGae28002 PCI FDDI driver logs the same data twice in NetTL trace file, if tracing is enabled for both HDR and PDU trace Kinds. PHNE_20874: 1. ER: An application that has an unbound promiscuous stream running over a PCI FDDI interface does not see packets that are being sent out from the host (outbound packets) on that interface. 2. A command to clear statistics on a functional PCI FDDI interface using the lanadmin(1M) command fails with the message : 'Unable to clear statistics registers.' 3. ER: Storing of per-interface configuration information across boots and hence system boot-time per-interface automatic configuration not possible with the PCI FDDI product. 4. Under heavy network traffic conditions over the PCI FDDI interface, a V class system may panic with 'Epic Channel Error'. 5. The netfmt(1M) command when run over a file containing nettl(1M) network traces for a PCI FDDI interface may core-dump with a 'memory fault'. 6. ER: The ioscan(1M) command does not display the PCI FDDI card hardware revision (namely A3739A or A3739B) installed on a system. 7. ER: The PCI FDDI product fails to function with the Lan-Monitor product. 8. A system with the PCI FDDI product installed from the June 2000 application release may panic with a 'data memory protection fault' when an application running sustained heavy loopback traffic over a PCI FDDI interface is closed. The loopback packets have a non-SNAP destination SAP (Service Access Point). i.e. a destination SAP that is not equal to 0xAA. PHNE_19542: 1. Applications using DLPI Type-2 connection oriented protocol over the PCI FDDI interface are unable to connect to a peer on another system. 2. On a cable disconnect/reconnect or when resetting the card using the lanadmin(1M) command, the system panics with: "panic: wait_for_lock: Already own this lock!" 3. The PCI FDDI interface state as seen using the ifconfig(1M) command does not change on cable disconnects (from UP to DOWN) and reconnects (from DOWN to UP). PHNE_18524: 1. Panic with epic channel error on V-class and panic with data page fault on N-class. 2. When an automatic reset of the card fails, it is not reattempted. 3. I/O address allocation is inefficient. 4. Heavy outbound traffic can cause the timer to falsely detect a DMA timeout, and then reset the card. PHNE_17517: 1. The interface can hang while transmitting UDP packets on a workstation. 2. Nettl tracing for the kinds hdrin, hdrout, and loopback does not provide any output. PHNE_16689: 1. A hung interface with a message "This interface appears to be hung" in dmesg output. 2. The default t_req time is too small. It is not consistent with the other FDDI products. 3. The multicast address displayed by fddipciadmin command is in the wrong byte order. 4. After an online reset, the multicast list, the promiscuous mode and the MAC address are not restored. 5. The B.11.00 version of fddipciadmin is in a different location than other versions. PHNE_15670: 1. On V-class systems, there are two groups of slots in a card cage. Each group is identified by the digit X of the hardware path X/Y/0 in the ioscan command output. The PCI FDDI card cannot be installed in the same slot group as Gigabit Ethernet, Token Ring, ATM, X.25 or HyperFabric card. The system may panic or hang during boot or the FDDI card may be unusable if the system comes up. 2. The driver is not optimized for TPC-C. PHNE_15269: 1. The "netstat -in" command reports an incorrect MTU size after the "lanadmin -R" command was used to reset the size to the FDDI standard (4352 bytes). 2. The TPC-C number is not as high as expected. 3. An unbound SAP promiscuous stream either receives packets of unknown DSAP values or receives packets destined for other promiscuous streams attached to this link. PHNE_14555: 1. V-class system panic with messages like the following: "Global error on Epic 0, Device 0, Driver fddi4" and "Error Info: 80178000:00000012". 2. The "mk_kernel" command fails, if FDDI was the only driver configured in the system that depends on "wsio". 3. lanadmin(1M) fails with a message "Cannot open shared library /usr/lib/lanadmin/libdsfddi4.sl" after repeated use of the statistics display command. PHNE_13212: Observed "FDDI Warning - Code: 2002 4" in dmesg during one stress test on a 6 way V-2200. Linkloop and ping stopped working on the affected interface. Reset the card through lanadmin and brought the interface back. PHNE_13184: Using the LLA interface to the PCI FDDI driver causes a panic. Defect Description: PHNE_26550: 1. SR: 8606227088 CR: JAGad96150 The problem happens when the file system is NFS mounted with a high rsize/wsize value, which is set using mount command. In the outbound path, PCI FDDI driver drops packets received from upper layers, which spans more than 2 physical pages. Resolution: The PCI FDDI driver is modified to handle MBLK's with data buffers spanning more than 2 physical pages. 2. SR: 8606182683 CR: JAGad51900 On non-cache coherent IO systems, PCI FDDI driver did not purge the processor cache while queuing the command response buffers to the card. On command response, the PCI FDDI driver reads the stale command response status, thus resulting in error messages. Resolution: PCI FDDI driver is changed to purge the processor cache before the command response buffers are queued. 3. SR: 8606156934 CR: JAGad26268 PCI FDDI does not have SNMP sub-agent. Resolution: SNMP sub-agent for PCI FDDI is provided. 4. SR: 8606166638 CR: JAGad35925 In case of transient high memory usage in the system, the LINK-UP message sent from PCI FDDI driver during an internal reset fails. As PCI FDDI driver did not check the return status from the LINK-UP call and also as there is no retry involved, the link continues to remain DOWN. Resolution: The PCI FDDI driver is modified to check the return value from LINK-UP call sent to DLPI. In case of failure, the timer routine will retry sending the LINK-UP event. 5. SR: 8606168617 CR: JAGad37895 Minor numbers for PCI FDDI device files were not created and handled as per the IO-TREE standard. When "insf -e" command is run to re-create the device files, the PCI FDDI minor numbers got changed and hence fddipciadmin command fails. Resolution: PCI FDDI startup scripts and the driver are changed to create and handle the minor numbers as per the IO-TREE standard. 6. SR: 8606220085 CR: JAGad89226 "Set user ID" bit is currently set in PCI FDDI lanadmin shared library which is not required. Resolution: The permission of the lanadmin shared library is changed appropriately. 7. SR: 8606257419 CR: JAGae21722 PCI FDDI driver does not interpret the event type information passed from the adapter as part of the unsolicited event. Resolution: PCI FDDI driver is enhanced to interpret the unsolicited event and log the event with event type information in NetTL log file. 8. SR: 8606257686 CR: JAGae21989 After issuing the reset command to the adapter, the hardware state of the adapter is incorrectly read as FDDI4_STATE_DMA_UNAVAIL, though the actual state is FDDI4_STATE_RESET. This results in the failure of reset process and the error message is logged. Resolution: The sampling frequency of reading the "hardware state" is reduced, thereby reducing the chances of driver reading an incorrect hardware state. 9. SR: 8606263674 CR: JAGae27999 When T_Req value is changed using fddipciadmin command, PCI FDDI driver sends the correct T_Req value to the adapter but stores an incorrect T_Req value in the driver structure. This invalid T_Req value is later restored in the adapter during the lanadmin reset. Resolution: PCI FDDI driver is changed to store the correct T_Req value in the driver structure. 10.SR: 8606263677 CR: JAGae28002 PCI FDDI driver logs the same data twice in NetTL trace file, if tracing is enabled for both HDR and PDU trace Kinds. Resolution: PCI FDDI driver is changed to log the data in NetTL trace file, only for PDU trace Kind. PHNE_20874: 1. CR JAGaa22135 The driver passed all inbound packets received on the interface to the unbound promiscuous stream but did not pass packets being sent out of the PCI FDDI interface (outbound packets). There is now a requirement to allow an unbound promiscuous stream to receive inbound as well as outbound packets. Resolution: The driver has been enhanced to make a copy of the outbound packets and send the copy to the unbound promiscuous stream. 2. CR JAGab72054 / SR 8606104480 The PCI FDDI driver did not implement the command to clear statistics of the interface and returned an error value on receiving such a command, resulting in lanadmin(1M) printing the error message 'Unable to clear statistics registers.'. Resolution: The driver has been enhanced to handle the command to clear the statistics on the interface/driver and return a value of 0 to lanadmin(1M) if the command succeeds or a non-zero error value indicating the type of error encountered when the command fails. 3. CR JAGab64952 / SR 5003452128 The PCI FDDI product did not have a configuration file to store per-interface configuration. Hence the product start up scripts that are executed at boot time did not re-configure the interfaces to previously configured values. Resolution: Starting with the application release of June 2000 and patch PHNE_20874 (and later application releases and superseding patches), a per-interface configuration file, hpfddi4conf, is installed. This file enables an user to store the station address, MTU (Maximum Transmission Unit), the T_Req and T_Notify values for FDDI station management on a per interface basis across boots. The existing product start-up script (/sbin/init.d/hppcifddi), that is automatically run during system boot has been enhanced to read the configured values from the above mentioned configuration file and initialize the PCI FDDI interfaces. See field 'Special Installation Instructions' for the location of the configuration file and instructions on using this feature. 4. CR JAGab76910 / SR 8606107182 On a V class, the descriptor block defining the buffers to be used by the card is present in shared memory, rather than the host/system memory. The PCI FDDI driver posted a card descriptor for card receive buffers (for inbound packets) to the shared memory descriptor block and later wrote to card registers indicating the availability of the new receive buffer descriptors for the card. Under heavy network load, the values written to the card register could reach the card before the card descriptor reach the shared memory block. The card then fetched the old/invalid card descriptor and attempted to write to the memory location specified by the descriptor resulting in a system panic with the 'Epic Channel Error' panic string. Resolution: The PCI FDDI driver has been fixed to ensure that the descriptor write is complete before updating the card registers, thus avoiding the situation described above. 5. CR JAGad01877 / SR 8606132729 When the netfmt(1M) command called the PCI FDDI subsystem formatter library to format PCI FDDI traces, an invalid parameter was passed to formatting routine that could result in the process accessing an invalid virtual address, resulting in the netfmt(1M) command dumping core with a 'memory fault' message. Resolution: The PCI FDDI subsystem formatter library routine has been corrected to pass correct valid values as parameters to the formatting routine. 6. CR JAGad01893 / SR 8606132745 The driver did not store the information regarding the PCI FDDI card revision in the database used by the ioscan(1M) command. Hence the information on the PCI FDDI card installed on the system was not displayed by the ioscan(1M) command. Resolution: The PCI FDDI driver now determines the card hardware revision during initialization of the card and logs the information in the database used by the ioscan(1M) command. 7. CR JAGad00071 / SR 8606130913 PCI FDDI driver did not have the enhancements required to direct packets destined for the SAPs (Service Access Points) used by the Lan Monitor product. Hence the Lan Monitor product would not function as expected. Resolution: The PCI FDDI driver has been enhanced to support SAPs used by the Lan Monitor product. 8. CR JAGad08463 / SR 8606139173 This defect could occur when the PCI FDDI product from the June 2000 application release was installed on a system which had a stream bound to a non-SNAP SAP (i.e. the SAP value is not 0xAA) sending packets destined to itself (loopback) in a sustained manner. When the stream/application was closed, there could be a time window during which there were packets destined for the now closed stream. In order to decide on a valid bound stream for the packet, the driver would attempt to parse unaligned fields in the packets resulting in a 'data memory protection fault' panic. Resolution: The PCI FDDI driver now performs additional validations for non-SNAP packets to avoid accessing unaligned fields in the packet and drops the packet if the stream it was destined for could not be found. PHNE_19542: 1. The PCI FDDI driver was dropping inbound DLPI Type-2 packets. Besides the above defect in the PCI FDDI driver, the lan-common module used to convert canonical MAC addresses to wire format for outbound DLPI Type-2 packets before passing on the packet to the PCI FDDI driver. The PCI FDDI card would also make the above conversion resulting in frames with incorrect MAC addresses being sent out on the wire. Either of the above defects would result in DLPI Type-2 packets being dropped and applications using DLPI Type-2 being unable to connect to their peers. Resolution: Inbound DLPI Type-2 packets are now processed by the driver and passed up to the required stream. The lan-common defect has been fixed in the lan-common patch PHNE_19081 (or a superseding patch). 2. When lan-common patch PHNE_19081 or a superseding patch is installed on a system with PCI FDDI, calls from the PCI FDDI driver to send link events upstream (as on cable disconnects/reconnects) will be sent upstream to IP by the lan-common module. In a STREAMS environment, during calls to an upstream module, a turnover could occur with a call back to the driver on the same thread, resulting in a spinlock deadlock, due to the lock being requested already being held by the driver. The above panic occurs only when the lan-common patch PHNE_19081 (or a superseding patch) is installed on the system. Resolution: Spinlocks are released before calls to upstream routines and reacquired on return from the call. 3. Prior to lan-common patch PHNE_19081, link events were not sent upstream to IP. Hence any link events generated by the driver were ignored and not reflected in the ifonfig(1M) output. Additionally the PCI FDDI driver was not generating a 'link up' event upon receiving a 'link up' indication from the adapter. This behavior will not be exposed until PHNE_19081 ( or a superseding patch ) is installed. Resolution: The driver has been changed to send 'link up' event to the IP stream when an interrupt is received from the card indicating link availability. PHNE_18524: 1. An automatic reset, while the driver is still handling inbound traffic, causes the driver to use stale DMA descriptor indices. A spurious link available interrupt can cause the driver to go from a DEAD state to a READY state, causing the driver to use invalid data. Resolution: Always initialize the descriptor indices from the driver's global data structure rather than local data. Don't allow the driver to go directly from the DEAD state to the READY state when a link available interrupt occurs. 2. Reattempting automatic resets was not implemented. Resolution: If an automatic reset fails, it will be reattempted up to six times. 3. I/O address mapping options were not optimized. Resolution: I/O address mapping services perform most efficiently when a default specification of non-interleaved I/O addresses is used when calling the mapping functions. The driver has been modified to use such a specification in all I/O address mapping function calls. 4. The timer assumed that a transmit DMA timeout or a command response timeout were logical reasons to initiate an adapter reset. Resolution: Timeout and reset the adapter only if there are no transmit completion or command response completion interrupts pending. PHNE_17517: 1. The driver did not map the first outbound memory buffer properly if it crossed a page boundary. This condition may occur when running UDP applications on workstations. 2. Nettl tracing for the kinds hdrin, hdrout, and loopback was not implemented. PHNE_16689: 1. Driver did not have a built-in reset mechanism to recover from a card hang, whether it is due to a DMA timeout or a card halt event. 2. The 8ms default t_req time (as opposed to 165ms in other products) was suspected to be the cause for ring drops. Customer also asked for the ability to change t_req time and t_notify time online. 3. A defect in the adapter's firmware caused the card to return the multicast addresses in a wrong format. 4. Driver's reset routine did not restore those parameters. As a result, for example, multicast or promiscuous mode stopped working after a lanadmin reset. 5. The B.11.00 version of fddipciadmin was incorrectly placed in /usr/bin. Subsequent releases place it correctly in /usr/sbin. This patch corrects the location if the B.11.00 version of fddipciadmin is installed. PHNE_15670: 1. The PCI FDDI card expects the shared memory to be aligned on an 8K byte boundary. If any of the drivers allocate shared memory that is not a multiple of 8K before FDDI, the shared memory allocated by the FDDI driver will not be 8K aligned. One such failing case is to have the FDDI card in slot 2 and an ATM card in slot 1. The slot number is identified by the digit Y of the hardware path X/Y/0. 2. The driver was not compiled with profile based optimization (PBO) data to improve the driver performance. PHNE_15269: 1. The driver relied on an MTU size being passed to it but no value is passed in with the "-R" option. 2. The transmit and receive code paths in the driver needed to be shortened in order to improve the efficiency in processing small packets. 3. The promiscuous level of the unbound stream was not kept independent of that of bound streams. If an unbound stream enabled SAP promiscuous and a bound stream enabled physical promiscuous, the driver could not differentiate the two. Hence, it duplicated every packet onto the unbound stream. PHNE_14555: 1. A DMA read was attempted by a card with a PCI address that had no corresponding address mapping. Problem was only seen on 16-way V-class system with heavy SCSI traffic. A race condition could occur. It caused the card to read in a descriptor entry for a DMA address before that entry became valid. 2. The word "wsio" was missing from the dependency section in the master file. 3. The shared library, libdsfddi4.1, opened the catalog file every time it was invoked, but did not close the file when it was done. The command failed when the number of files opened exceeded the "maxfiles" for a process. PHNE_13212: Reproduced the similar symptom using an UDP performance tool on a 4 way V-2200. With three copies of that tool running together, the outbound traffic generated can overwhelm the driver outbound routine and consequently lock out the ISR routine both competing for the same lock. DMA timer pops because the ISR does not get the chance to service transmit completion interrupt within the timeout period. PHNE_13184: The function pointers used by LLA incorrectly pointed to the wrong functions within PCI FDDI. These function pointers have been changed to point to the function "nodev" instead. This function will return the error ENODEV when called. It is to be noted that LLA has been obsoleted as of the 10.30 release of HP-UX and should not be used in 11.00. SR: 8606227088 8606182683 8606156934 8606166638 8606168617 8606220085 8606257419 8606257686 8606263674 8606263677 8606104480 5003452128 8606107182 8606132729 8606132745 8606130913 8606139173 8606103306 8606103307 1653265173 5003428722 5003441279 5003441295 1653249847 4701374314 Patch Files: FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libfddi4.a /usr/conf/master.d/fddi4 FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_32,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_32,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_32,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_32,v=HP: FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libfddi4.a FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.11,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.12,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.13,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.15,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.16,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP: FDDI-PCI.FDDI4-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP: /usr/lib/lanadmin/libdsfddi4.1 /usr/sbin/fddipciadmin /usr/lib/nls/msg/C/fddi4.cat /usr/lib/libfddifmt4.1 /sbin/init.d/hppcifddi /sbin/init.d/SnmpFddi4 /sbin/SnmpAgtStart.d/K424SnmpFddi4 /sbin/SnmpAgtStart.d/S576SnmpFddi4 /sbin/rc1.d/K424SnmpFddi4 /sbin/rc2.d/S576SnmpFddi4 /usr/sbin/hpfddi4_init /usr/sbin/fddi4subagt /usr/newconfig/etc/rc.config.d/hpfddi4conf FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.11, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.12, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.13, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.15, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.16, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/share/man/man1m.Z/fddipciadmin.1m what(1) Output: FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libfddi4.a: PCI FDDI: PHNE_26550: B.11.00.18 $Date: 2002/06/04 1 7:00:00 $ /usr/conf/master.d/fddi4: None FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libfddi4.a: PCI FDDI: PHNE_26550: B.11.00.18 $Date: 2002/06/04 1 7:00:00 $ FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64, v=HP: /usr/lib/lanadmin/libdsfddi4.1: dsfddi4.c: PHNE_26550: B.11.00.18 $Date: 2002/03/13 17:00:00 $ /usr/sbin/fddipciadmin: HP PCI FDDI command: fddipciadmin, Release: B.11.00. 00 fddipciadmin.c: PHNE_26550: B.11.00.18 $Date: 2002/0 3/13 17:00:00$ /usr/lib/nls/msg/C/fddi4.cat: None /usr/lib/libfddifmt4.1: subsys_FDDI_fmt4.c: PHNE_26550: B.11.00.18 $Date: 20 02/03/13 17:00:00 $ /sbin/init.d/hppcifddi: None /sbin/init.d/SnmpFddi4: SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1 3 17:00:00 $ /sbin/SnmpAgtStart.d/K424SnmpFddi4: SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1 3 17:00:00 $ /sbin/SnmpAgtStart.d/S576SnmpFddi4: SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1 3 17:00:00 $ /sbin/rc1.d/K424SnmpFddi4: SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1 3 17:00:00 $ /sbin/rc2.d/S576SnmpFddi4: SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1 3 17:00:00 $ /usr/sbin/hpfddi4_init: None /usr/sbin/fddi4subagt: -DUNIX -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 HP PCI FDDI SNMP Subagent: fddi4subagt, Release: B.1 1.00.16 fddi4subagtd.c: PHNE_26550: B.11.00.18 $Date: 2002/0 3/13 17:00:00 $ -DUNIX -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE_LINES Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_HPUX10 -DSR_BSD -DHPUX Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_HPUX10 -DSR_BSD -DHPUX Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSYSV -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 $ -s Mar 13 2002 17:41:35 $ /usr/newconfig/etc/rc.config.d/hpfddi4conf: None FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08, fa=HP-UX_B.11.00_32/64,v=HP: /usr/share/man/man1m.Z/fddipciadmin.1m: None cksum(1) Output: FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 2614659761 139064 /usr/conf/lib/libfddi4.a 3603701237 3779 /usr/conf/master.d/fddi4 FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP: 309953296 75344 /usr/conf/lib/libfddi4.a FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64, v=HP: 2279026856 16384 /usr/lib/lanadmin/libdsfddi4.1 2152968053 49152 /usr/sbin/fddipciadmin 814246150 7892 /usr/lib/nls/msg/C/fddi4.cat 1250558422 12288 /usr/lib/libfddifmt4.1 2797490883 3534 /sbin/init.d/hppcifddi 1751563072 2581 /sbin/init.d/SnmpFddi4 1751563072 2581 /sbin/SnmpAgtStart.d/K424SnmpFddi4 1751563072 2581 /sbin/SnmpAgtStart.d/S576SnmpFddi4 1751563072 2581 /sbin/rc1.d/K424SnmpFddi4 1751563072 2581 /sbin/rc2.d/S576SnmpFddi4 3269604101 7466 /usr/sbin/hpfddi4_init 75158578 245760 /usr/sbin/fddi4subagt 399402431 1633 /usr/newconfig/etc/rc.config.d/hpfddi4conf FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08, fa=HP-UX_B.11.00_32/64,v=HP: 1618959572 5120 /usr/share/man/man1m.Z/fddipciadmin.1m Patch Conflicts: None Patch Dependencies: s700: 11.00: PHNE_19081 s800: 11.00: PHNE_19081 Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_20874 PHNE_19542 PHNE_18524 PHNE_17517 PHNE_16689 PHNE_15670 PHNE_15269 PHNE_14555 PHNE_13212 PHNE_13184 Equivalent Patches: None Patch Package Size: 650 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_26550 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHNE_26550.depot By default swinstall will archive the original software in /var/adm/sw/save/PHNE_26550. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHNE_26550.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHNE_26550.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_26550.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: If lan common patch PHNE_19081 (or a superseding patch) is not installed on a system with PCI FDDI, then installing patch PHNE_19542 or a superseding patch (including this patch) will : - Not fix defect symptom #1 and #3 for PHNE_19542 - Symptom #2 for PHNE_19542 can never occur as long as PHNE_19081 (or a superseding patch) is not applied. If lan common patch PHNE_19081 (or any superseding patch) is installed on a system with PCI FDDI, then installing patch PHNE_19542 or a superseding patch( including this patch) will fix all 3 defects described in patch PHNE_19542. Note that installing PHNE_19081 (or a superseding patch) will expose defect #2 for PHNE_19542, mentioned in the 'Symptoms' and 'Defect Description' fields, which is fixed by patch PHNE_19542 and superseding patches, including this patch. A note about the fix for item #3 listed in the 'Symptoms' field for patch PHNE_20874: Starting with the application release of June 2000 (and later releases), the product has a per-interface configuration file located at /usr/newconfig/etc/rc.config.d/hpfddi4conf. When the product is installed from the application release of June 2000 or a later application release, the file (hpfddi4conf) is automatically copied into /etc/rc.config.d/hpfddi4conf, if the file does not already exist in the destination directory. If the file hpfddi4conf already exists under /etc/rc.config.d directory it may not be overwritten by the newly delivered file under /usr/newconfig/etc/rc.config.d/ directory as it may contain changes made by the user. The user can then merge the changes, if any into the file under /etc/rc.config.d directory. When patch PHNE_20874 (or a superseding patch) is installed, the file hpfddi4conf is always delivered under the /usr/newconfig/etc/rc.config.d directory and the user is required to merge/copy changes, if any into the file under /etc/rc.config.d directory. The hpfddi4conf file allows per-interface configuration information to be stored across boots and automatic initialization of of interfaces using these per-interface parameters during system boot by the product start-up script (/sbin/init.d/hppcifddi). The following variables are now configurable in the hpfddi4conf file on a per-interface basis: HP_PCIFDDI_INTERFACE_NAME: Name of interface (lan0, lan1 ..., lan10, ...) i.e. any lanX, where X is the instance number of the interface being configured. HP_PCIFDDI_STATION_ADDRESS: The desired unicast hardware address (station address) of the interface. This value must be '0x' followed by 12 hexadecimal digits (i.e. 0x080009xxxxxx). HP_PCIFDDI_MTU: Maximum transmission unit (in bytes) for the interface. A value in the range 257-4352 is valid. HP_PCIFDDI_TREQ: The FDDI station's T_Req value in milli-seconds. A value in the range 4-165 is valid. HP_PCIFDDI_TNOTIFY: The FDDI station's T_Notify value in seconds. A value in the range 2-30 seconds is valid.