Patch Name: PHNE_24025 Patch Description: s700_800 11.00 HP-PB FDDI (J2157B) product cumulative patch Creation Date: 01/04/30 Post Date: 01/06/12 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: FDDI-INIT-COM B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.04 B.11.00.05 B.11.00.08; FDDI-KRN-COM B.11.00 B.11.00.01 B.11.00.02 B.11.00.08; FDDI-MASTER-COM B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.04 B.11.00.05 B.11.00.08; FDDI-SNMP-SUBAGT B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.04 B.11.00.05 B.11.00.08; FDDI67-KRN B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.04 B.11.00.05 B.11.00.08; FDDI67-RUN B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.04 B.11.00.05 B.11.00.08; Filesets: FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP FDDI67-KRN.FDDI-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.04,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_32/64,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_32/64,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_32/64,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_32/64,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP FDDI67-RUN.FDDI-RUN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.01,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.02,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.03,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.04,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.01,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.02,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.03,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.04,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.01,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.02,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.03,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.04,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP Automatic Reboot?: Yes Status: General Release Critical: No (superseded patches were critical) PHNE_19633: PANIC HANG PHNE_19518: PANIC MEMORY_LEAK PHNE_15276: PANIC The system may panic with data page fault or data memory protection fault. PHNE_14722: PANIC Heavy outbound traffic may cause system panic. Combination of heavy inbound traffic and promiscuous mode can cause system panic. Heavy load on the system when running fddiinit command can cause system panic. PHNE_14152: PANIC When an interrupt is received with the xfer_len less than 12, system panics. System panics when LLA read/write is done. Category Tags: defect_repair enhancement general_release critical panic halts_system memory_leak Path Name: /hp-ux_patches/s700_800/11.X/PHNE_24025 Symptoms: PHNE_24025: 1. CR JAGad23522 / SR 8606154204 nio fddi card drops nfs packets if packet is less than 100bytes 2. CR JAGad09810 / SR 8606140443 Too many messages logged into syslog.log 3. CR JAGad58782 / SR 8606189568 GET_ITIMER() macro in lan6.c incorrectly calculates time 4. CR JAGad67822 / SR 8606198633 SUID bit set for libraries used for lanadmin and lanscan PHNE_19633: 1. The system panics with data page fault in hp_dlpi_mblk_fast_in(). 2. FDDI card hangs with lot of resets logged by NetTL. PHNE_19518: 1. Nettl log does not display the full hardware path for HP-PB FDDI cards. 2. Memory leak in 'fddisubagtd'. 3. HP-PB FDDI startup script always builds device file. 4. FDDI bypass does not close the ring after 'shutdown -h' command. 5. Wrong MIB values due to inconsistency between SMT & RFC. 6. HP-PB fddi driver does not reset the MTU properly. 7. 'fddisubagtd' problem with decreasing instance number. 8. HP-PB FDDI driver generates wrong checksum in some situation. 9. The HP-PB FDDI driver does not handle spinlock correctly during the NetTL logging. 10. The system panics during the boot up if the system had very low available memory. 11. The fddi startup script does not set MTU and station address correctly for some card instances. 12. SAM reports error "fddiinit: download /usr/lib/fddi_dnld .............done", when configuring HP-PB FDDI interfaces. 13. HP-PB FDDI subsystem was not being configured for NetTL logging and tracing under some conditions. 14. The system can panic when the network cable (to the HP-PB FDDI adapter) is disconnected / reconnected. PHNE_15875: 1. HP-PB FDDI doesn't update the driver statistics properly. 2. The HP-PB FDDI driver is not optimized for TPC-C. PHNE_15276: 1. The system may panic with data page fault. The panic stack might be different at different times. 2. Lanadmin fails to clear statistics on HP-PB FDDI. 3. HP-PB FDDI sends packets to the DLPI layer with wrong link layer header when PROMISCUOUS SAP mode was enabled. PHNE_14722: 1. Under heavy outbound traffic, system may panic in lan6_compress_and_build_vquads() routine. 2. NIO FDDI panics on promiscuous SAP mode in hp_dlpi_intr() routine. 3. Under heavy load, the system may panic when the card is reset by running the fddiinit command. 4. FDDI interface goes down when the card is in low priority slot and traffic is high. Also excessive resets are seen in the nettl log. 5. When INFORMATIVE and/or WARNING logging type is turned on for the driver (nettl -l i -e FDDI), system may panic under certain conditions. 6. Startup script may not set some parameters correctly. 7. 'netfmt' command dumps core occasionally when tried to format the FDDI trace data. 8. swinstall NIO FDDI driver failed after coldinstall. PHNE_14152: 1. panic in lan6_process_read_pkt() 2. panic:Recover counter overflow/Data page fault 3. SIO/WSIO dependency is missing for HP-PB FDDI LAN driver. 4. lanadmin command fails after sufficient changing of PPA/display commands. Defect Description: PHNE_24025: 1. CR JAGad23522 / SR 8606154204 This is a problem with the NIO FDDI firmware. The header data split logic in the firmware assumes that the entire header is in the first packet. (~ 108 bytes for NFS). (UDP port 2049 corresponds to NFS). But in this case the first fragment has only 40 bytes. Hence the firmware ignores this packet. Resolution: The problem is resolved. 2. CR JAGad09810 / SR 8606140443 Too many messages logged into syslog.log Resolution: Changes are made so that the messages are logged into nettl log file instead of syslog.log. 3. CR JAGad58782 / SR 8606189568 GET_ITIMER() macro in lan6.c incorrectly calculates time. Therefore the value will wrap around about every 4300 seconds (less than an hour and a quarter) Resolution: The problem is corrected so that the time is calculated correctly. 4. CR JAGad67822 / SR 8606198633 setuid bit set for libraries used for lanadmin and lanscan. Setting this bit is not required and may cause problems that are not foreseen. Resolution: The file permissions is changed. PHNE_19633: 1. The data page fault was due to corrupt packet being DMA'ed by the card. Resolution: In the inbound path correctness of the packet being received is validated. 2. FDDI card hangs with lot of 2043 nettl messages logged. Resolution: The driver code has been modified in multiple places to fix the problem. PHNE_19518: 1. The formatted NetTL log was not showing the full hardware path for HP-PB fddi cards. And also the path displayed was not in the correct format. Resolution: The driver and NetTL formatter code has been fixed to log full hardware path in correct format as displayed in lanscan / ioscan output (for eg. 10/4/4). 2. Memory leak with fddisubagtd. Resolution: Fixed subagent code to call FreeOctetString() to free the old resource before allocating new. 3. The startup script for HP-PB FDDI initialization was recreating the device files every time the script was run. The problem was due to wrong string comparison of two variables with different format. Resolution: Startup script "/sbin/init.d/fddi" has been modified to convert both variables to same format before comparison. 4. The FDDI optical bypass was not closing the ring after halting the system using 'shutdown -h' command. 'fddistop' command has to be run when the system is halted using 'shutdown -h' command for FDDI optical bypass switch to bypass the station in a FDDI ring. Resolution: The startup script "/sbin/init.d/fddi" has been modified to run 'fddistop' command on HP-PB FDDI interfaces when system is halted. New kill script "/sbin/rc1.d/K993fddi" is introduced for this purpose. 5. The 'fddisubagtd' supports functionalities to get and set SMT 7.2 attributes. But man pages of 'fddisubagtd' was wrongly referring to RFC 1512. Resolution: The 'fddisubagtd' man page has been modified to refer correct standard. 6. The HP-PB FDDI driver was not resetting MTU size properly, instead it was resetting it to a huge value. This was due to wrong assignment present in the driver code for RESET_MTU request. Resolution: The driver code has been modified to assign correct value (FDDI_MTU) for RESET_MTU request. 7. The 'fddisubagtd' NEXT search requires that the requested object does not lexicographically precede the current object type. So when the system has multiple HP-PB FDDI cards with decreasing instance number, MIB requests for subsequent cards after the first card returns bad object ID. Resolution: The 'fddisubagtd' code has been fixed to sort the ppa list before sending the request. 8. In the outbound routine we walk through the fragment train (fragments of a single packet) got from IP / UDP enqueuing each fragment to the transmit queue. Under heavy load if the transmit queue becomes full after enqueuing some fragments, we drop the subsequent fragments in the mblk train and send ENOBUF to the upper layer but were not dequeu'ing the already enqueued fragment(s). The first fragment that we enqueued contains the checksum assist block which tells the card to keep accumulating the TCP / UDP checksum till he gets a fragment containing checksum insert flag. Since the subsequent fragment(s) are dropped, the card inserts the accumulated checksum in the next wrong fragment / packet which contains checksum insert flag. Resolution: The fix is to check if available space in the transmit queue is equal or more than the number of the fragments in the packet train. If the check fail, drop the whole packet and send error to the upper layer. 9. lan6_error() is always called with lan6 lock held. But in lan6_error() there was an assertion on lan6 lock not held. But assertion should have been to check if the lan6 lock was held. This problem is seen only on the debug kernel. Resolution: The lan6_error() code has been changed to assert if lan6 lock was held. 10. In drivers initialization routine, memory is malloc'ed through io_get_mem(), then accessed via the returned pointer without first checking if the pointer is NULL. This leads to system panic. But under low memory condition io_get_mem() can return NULL. Resolution: The driver's initialization routine code has been modified to check the return value from io_get_mem(). If the return value is NULL, driver does not initialize itself and also the card. 11. In the HP-PB FDDI startup script, device file in question is searched from the 'lanscan' output using 'grep' command. If the system has two devices with device files lan1 and lan10, the search for lan1 from 'lanscan' output used to result in searching for both lan1 and lan10. This leads to problem and subsequent 'lanadmin' does not work properly. Resolution: In the startup script "/sbin/init.d/fddi", 'grep' command has been modified to search only the device file in question. 12. The problem is due to new enhancement in SAM. When a user tries to configure FDDI interface, SAM calls "/usr/sbin/hpfddi_init" FDDI script. If the script is successful, SAM does not expect any output from the script. But "/usr/sbin/hpfddi_init" gives some output even if it is successful, which makes SAM think that the script failed and gives error. Resolution: The output from "/usr/sbin/hpfddi_init" is the success message from 'fddiinit' command. The script has been modified to redirect the the output from 'fddiinit' command to null device. 13. NetTL was not getting configured for HP-PB FDDI subsystem when HSC FDDI card is also present on the system. The problem was in "/sbin/init.d/fddi" startup script searching for fddi and fddi2 from 'ioscan' output using 'grep' command. This search also resulted in searching for fddi3 which leads to problem. Resolution: In startup script "/sbin/init.d/fddi", the 'grep' command has been modified to search only for fddi and fddi2. 14. The drivers should not hold any lock when calling lanc_mib_event(). But HP-PB FDDI holds lan6 lock in some places when calling lanc_mib_event(). This can cause panic when cable is disconnected or reconnected. Resolution: The driver code has been modified to release any held lock when calling lanc_mib_event() and reacquire the lock after the call to lanc_mib_event(). PHNE_15875: 1. In the outbound path, the unicast and non-unicast counters were not updated in some cases. 2. The driver was not compiled with Profile Based Optimization (PBO) data to improve performance. PHNE_15276: 1. The data page fault was due to the change in the semantics of I/O memory allocation module. The memory allocated was not being initialized to zero and this resulted in some arbitrary value for one of the elements of a structure used by FDDI driver. This element was used to index into an array and write to that location. The panic stack varies depending on which memory location was corrupted. This problem was observed with a system having a disk tower with two female SCSI connectors shared between two systems. 2. This feature was not provided by HP-PB FDDI. 3. In the inbound frame, the link layer header can have some padding bytes. However DLPI expects the driver to remove the padding before the driver sends the packet up to DLPI. When SAP PROMISCUOUS mode was enabled, the driver was not stripping the pad bytes. PHNE_14722: 1. HP-PB FDDI (J2157B) driver handles only 64 mblks in a chain for outbound due to performance reasons. If any upper layer protocols sends a mblk chain having more than 64 mblks, driver will try to compress them by copying some of them to a larger buffer and so reduce the number of mblks in the chain. During this compression, if system runs out of memory and driver could not allocate memory, driver calls freeb() function with the NULL parameter which causes the system panic. 2. Whenever an user application turns on and off promiscuous mode in a loop for a FDDI interface, if inbound traffic is high on that interface, system panics in hp_dlpi_intr() function. 3. Under heavy load, HP-PB FDDI driver warning message 3053 (Quad fetch delay) followed by error message 2043 (DMA timeout) may be logged. In this situation driver may be using a callout mechanism to resolve the quad fetch delay problem mentioned in warning message 3053. In this situation, if the fddiinit command is run, there is a possibility that the HP-PB FDDI driver will try to post an outbound packet in the callout routine, after the fddiinit command has already initialized the HP-PB FDDI port data area. This can cause a NULL pointer access when trying to queue the outbound packet and hence a panic. 4. Whenever the card sends an interrupt to the driver, it expects the interrupt acknowledgement within 200ms. But in case of high end systems under heavy system load, the acknowledgement may be delayed. This results in reset of the card. Also in the fddi driver, when the command response times out, the corresponding command, if present was not being dequeued from the command queue. 5. Due to an incorrect parameter passed to lan6_log() routine, when some of the SMT events are received, system panics with "Data page fault". 6. If index used for the parameter array in the shell script file, /etc/rc.config.d/hpfddiconf, does not start from 1, /sbin/rc2.d/S007fddi script will fail to set those parameters. 7. 'netfmt' command which is used for formatting the nettl trace file dumps core occasionally, when it is used for formatting the trace file containing the FDDI packets. The problem is that, subsys_FDDI_format() function which is present in /usr/lib/libfddifmt.sl, calls format_link_raw() with only 7 parameters, instead of expected 8 parameters. The 5th parameter is missed out. This core dump does not happen when nice (-N) or terse (-1) options are used. 8. Checkinstall script of the superseded patch checks to see whether the appropriate version of the HP-PB FDDI product is installed. If checkinstall script could not find the proper version of HP-PB FDDI product installed on the system, it exits with the status code 1. Software Distributor(SD) treats this status code as an error condition and reports this in the logfile. In this patch, the checkinstall script has been changed to exit with the status code 3, which is informing the SD to exclude this patch from installing. PHNE_14152: 1. The cause for panic was firmware sending an interrupt indicating an inbound packet has arrived, but the xfer_len in the IO_RX_STATUS register *NOT* having a proper value. Driver handled the condition where the xfer_len is greater than the MTU, but did *NOT* handle the condition where it is less than the minimum required length. When an inbound complete interrupt is received by the driver, it enters in to a while loop to get the trailer of the packet in which the status information is stored. In the process of searching for the trailer information, driver runs out of mblk chain it had allocated for inbound frame. This is because, if the xfer_len is lesser than 12, xfer_len - 12(where the trailer starts) gives a negative value and this negative value is assigned to an unsigned variable in the driver which becomes a very huge value and driver runs out of mblks and invariably it dereferences a NULL pointer resulting in a panic. Strictly speaking, this situation should never happen because length should at least be equal to 12. The change was to add a condition in the driver to check for minimum length required for an inbound packet processing. 2. Since LLA read/write paths were still using mbufs instead of mblks, wrong de-reference of pointer causes this system crash. 3. The sio/wsio dependency is missing from the master files of all LAN drivers. Consequently, if other drivers, e.g., stape, which specify this dependency are removed from /stand/system, sio/wsio also disappears and an unbootable kernel results. 4. dsname() function in lanadmin command, opens catalog file using catopen() but does not close the same on return. Hence if dsname() is called for sufficiently large number of times, number of open files will cross maxfiles limit causing a failure in the next catopen(). SR: 8606154204 8606140443 8606189568 8606198633 1653276774 1653280768 5003467027 8606101576 1653263657 1653289611 5003424465 1653279869 1653274720 1653286633 1653280024 4701431817 5003412940 5003399253 5003408385 5003402388 Patch Files: FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libfddi.a FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP: FDDI67-KRN.FDDI-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libfddi.a FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_64, v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.01, fa=HP-UX_B.11.00_64,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.02, fa=HP-UX_B.11.00_64,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.03, fa=HP-UX_B.11.00_64,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.04, fa=HP-UX_B.11.00_64,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.05, fa=HP-UX_B.11.00_64,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.08, fa=HP-UX_B.11.00_64,v=HP: /usr/conf/master.d/fddi FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_32, v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.01, fa=HP-UX_B.11.00_32,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.02, fa=HP-UX_B.11.00_32,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.03, fa=HP-UX_B.11.00_32,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.04, fa=HP-UX_B.11.00_32,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.05, fa=HP-UX_B.11.00_32,v=HP: FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00.08, fa=HP-UX_B.11.00_32,v=HP: /usr/conf/master.d/fddi FDDI67-RUN.FDDI-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: FDDI67-RUN.FDDI-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_32/64, v=HP: FDDI67-RUN.FDDI-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_32/64, v=HP: FDDI67-RUN.FDDI-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_32/64, v=HP: FDDI67-RUN.FDDI-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_32/64, v=HP: FDDI67-RUN.FDDI-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64, v=HP: FDDI67-RUN.FDDI-RUN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64, v=HP: /usr/lib/lanadmin/libdslan6.1 /usr/lib/lanadmin/libdslan7.1 /usr/lib/lanscan/libpelan6.1 /usr/lib/lanscan/libpelan7.1 /usr/lib/libfddifmt.1 /usr/lib/libfddifmt2.1 FDDI-INIT-COM.FDDI-INIT,fr=B.11.00,fa=HP-UX_B.11.00_32/64, v=HP: FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.01, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.02, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.03, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.04, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.05, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-INIT-COM.FDDI-INIT,fr=B.11.00.08, fa=HP-UX_B.11.00_32/64,v=HP: /sbin/init.d/fddi /usr/lib/fddi_dnld /usr/sbin/hpfddi_init /sbin/rc1.d/K993fddi FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.01, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.02, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.03, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.04, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.05, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00.08, fa=HP-UX_B.11.00_32/64,v=HP: /usr/sbin/fddisubagtd FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.01, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.02, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.03, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.04, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.05, fa=HP-UX_B.11.00_32/64,v=HP: FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00.08, fa=HP-UX_B.11.00_32/64,v=HP: /usr/share/man/man1m.Z/fddisubagtd.1m what(1) Output: FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libfddi.a: lan6_nm.c $Revision: 1.1.118.6 $ PHNE_24025 J2157B HP-PB FDDI fddi libfddi B.11.00.09 $Date$ lan6.c: $Revision$ $Date$ B.11.00.09 PHNE_24025 FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libfddi.a: lan6_nm.c $Revision: 1.1.118.6 $ PHNE_24025 J2157B HP-PB FDDI fddi libfddi B.11.00.09 $Date$ lan6.c: $Revision$ $Date$ B.11.00.09 PHNE_24025 FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_64, v=HP: /usr/conf/master.d/fddi: PHNE_14152: $Revision: 1.2.118.2 $ FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_32, v=HP: /usr/conf/master.d/fddi: PHNE_14152: $Revision: 1.2.118.2 $ FDDI67-RUN.FDDI-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/lib/lanadmin/libdslan6.1: dslan6.c: PHNE_14152: $Revision: 1.1.119.4 $ $Date: 98/02/18 10:14:10 $ /usr/lib/lanadmin/libdslan7.1: dslan7.c: $Revision: 1.1.119.3 $ $Date: 98/04/08 02 :45:57 $ B.11.00.0[01] PHNE_14722 /usr/lib/lanscan/libpelan6.1: None /usr/lib/lanscan/libpelan7.1: None /usr/lib/libfddifmt.1: subsys_FDDI_fmt.c $Revision: 1.1.119.3 $ B.11.00.06 PHNE_19518 /usr/lib/libfddifmt2.1: subsys_FDDI_fmt.c $Revision: 1.1.119.4 $ B.11.00.0[0 1] PHNE_14722 FDDI-INIT-COM.FDDI-INIT,fr=B.11.00,fa=HP-UX_B.11.00_32/64, v=HP: /sbin/init.d/fddi: fddi $Revision: 1.1.119.5 $ $Date: 97/08/21 23:10:50 $ /usr/lib/fddi_dnld: hppbfddi download code SMT7.2 PHNE_24025 010430-17:3 8 p/n 28670-XXXXX 3705 /usr/sbin/hpfddi_init: hpfddi_init $Revision: 1.1.119.2 $ $Date: 96/12/16 12:06:27 $ /sbin/rc1.d/K993fddi: fddi $Revision: 1.1.119.5 $ $Date: 97/08/21 23:10:50 $ FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00, fa=HP-UX_B.11.00_32/64,v=HP: /usr/sbin/fddisubagtd: Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 fddisubagtd.c $Revision: 1.1.119.2 $Date: 96/12/27 1 4:45:00 B.10.30.00 $ Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 Copyright 1992-1996 SNMP Research, Incorporated SNMP Research Distribution version 14.0.0.0 FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00, fa=HP-UX_B.11.00_32/64,v=HP: /usr/share/man/man1m.Z/fddisubagtd.1m: None cksum(1) Output: FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 3185144705 104618 /usr/conf/lib/libfddi.a FDDI67-KRN.FDDI-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: 4106590707 56220 /usr/conf/lib/libfddi.a FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_64, v=HP: 3656785638 3821 /usr/conf/master.d/fddi FDDI-MASTER-COM.FDDI-MASTER,fr=B.11.00,fa=HP-UX_B.11.00_32, v=HP: 3656785638 3821 /usr/conf/master.d/fddi FDDI67-RUN.FDDI-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: 1326946553 28672 /usr/lib/lanadmin/libdslan6.1 3933802345 16384 /usr/lib/lanadmin/libdslan7.1 3055549911 12288 /usr/lib/lanscan/libpelan6.1 2477882469 12288 /usr/lib/lanscan/libpelan7.1 3179727069 16384 /usr/lib/libfddifmt.1 2280076896 40960 /usr/lib/libfddifmt2.1 FDDI-INIT-COM.FDDI-INIT,fr=B.11.00,fa=HP-UX_B.11.00_32/64, v=HP: 2226166473 9561 /sbin/init.d/fddi 432263677 125538 /usr/lib/fddi_dnld 1547746449 9447 /usr/sbin/hpfddi_init 2226166473 9561 /sbin/rc1.d/K993fddi FDDI-SNMP-SUBAGT.FDDI-SUBAGT,fr=B.11.00, fa=HP-UX_B.11.00_32/64,v=HP: 3523630449 212992 /usr/sbin/fddisubagtd FDDI-SNMP-SUBAGT.FDSA-ENG-A-MAN,fr=B.11.00, fa=HP-UX_B.11.00_32/64,v=HP: 91380131 665 /usr/share/man/man1m.Z/fddisubagtd.1m Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_14152 PHNE_14722 PHNE_15276 PHNE_15875 PHNE_19518 PHNE_19633 Equivalent Patches: PHNE_24024: s800: 10.20 Patch Package Size: 730 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_24025 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHNE_24025.depot By default swinstall will archive the original software in /var/adm/sw/save/PHNE_24025. If you do not wish to retain a copy of the original software, use the patch_save_files option: swinstall -x autoreboot=true -x patch_match_target=true \ -x patch_save_files=false -s /tmp/PHNE_24025.depot 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_24025.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHNE_24025.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_24025.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None