Patch Name: PHNE_20009 Patch Description: s700_800 10.20 EISA FDDI B.10.20.[01-11] cumulative patch Creation Date: 99/12/27 Post Date: 00/04/06 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: EISA FDDI B.10.20.01 B.10.20.02 B.10.20.03 B.10.20.04 B.10.20.08 B.10.20.11 Filesets: FDDI-EISA.FDDI0-KRN,B.10.20.01 FDDI-EISA.FDDI0-KRN,B.10.20.02 FDDI-EISA.FDDI0-KRN,B.10.20.03 FDDI-EISA.FDDI0-KRN,B.10.20.04 FDDI-EISA.FDDI0-KRN,B.10.20.08 FDDI-EISA.FDDI0-KRN,B.10.20.11 FDDI-EISA.FDDI0-RUN,B.10.20.01 FDDI-EISA.FDDI0-RUN,B.10.20.02 FDDI-EISA.FDDI0-RUN,B.10.20.03 FDDI-EISA.FDDI0-RUN,B.10.20.04 FDDI-EISA.FDDI0-RUN,B.10.20.08 FDDI-EISA.FDDI0-RUN,B.10.20.11 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.08 FDDI-CMD-COM.FDDI-CMD,B.10.20.11 Automatic Reboot?: Yes Status: General Superseded Critical: Yes PHNE_20009: PANIC MEMORY_LEAK PHNE_18869: PANIC PHNE_17285: PANIC OTHER Items 5 and 6 of the defect description cause system panics. Item 4 of the defect description results in a critical customer application failure and is classified as a critical defect in the corresponding SR. PHNE_17061: MEMORY_LEAK PANIC HANG ABORT CORRUPTION OTHER Item 3 of the Symptoms/Defect Description fields causes data corruption, leading to degraded link performance. PHNE_15665: OTHER Card hang. PHNE_14791: PANIC PHNE_14077: MEMORY_LEAK OTHER Card hang. PHNE_12974: CORRUPTION PHNE_12973: CORRUPTION PHNE_11708: CORRUPTION It has a fix for data corruption, a reset panic, a bootup panic, a hang and transmit underruns. PHNE_11707: CORRUPTION It has a fix for data corruption, a reset panic, a bootup panic, a hang and transmit underruns. PHNE_10818: PANIC If there is FDDI traffic destined for a host while it is booting up, the host may panic. Path Name: /hp-ux_patches/s700_800/10.X/PHNE_20009 Symptoms: PHNE_20009: 1. CR JAGab73997 / SR 8606105737: Data page fault panic in driver open routine. 2. CR JAGab75690 / SR8606106494: IOVR leak in EISA/HSC FDDI in the Card reset path. 3. CR JAGab64949 / SR 5003451047: ER: Add option for fddiif/fddilink to support writing to an output file. 4. CR JAGab75863 / SR 8606106601: Multicast addresses not reloaded after a Card reset. 5. CR JAGab74656 / SR 8606105918: Spinlock held during copyout. 6. CR JAGac40038 / SR 8606124655: Potential Memory leak in EISA/HSC FDDI drivers. 7. CR JAGac40041 / SR 8606124658: Panic in fddi0_bcopy routine. 8. CR JAGac87837 / SR 8606129502: Linkloop fails on EISA/HSC FDDI after a card reset. 9. CR JAGac88808 / SR 8606129893: lanscan shows interface as up, even though cable is disconnected. 10.CR JAGac97430 / SR 8606130828: netfmt dumps core without -N option. PHNE_18869: 1. The system panics with an instruction page fault with promiscuous mode enabled on the EISA FDDI interface. 2. The lanscan command does not show the interface status correctly for EISA FDDI interface. 3. Aborts/Underruns are observed when frames larger than 3000 bytes are transmitted, with EISA SCSI present on the system. 4. The EISA FDDI driver does not report any errors when an invalid multicast address is added by a user. 5. EISA FDDI nettl log messages do not appear after a card reset. 6. Enhancement request to have SNMP subagent supported on the EISA FDDI driver. 7. Disable of Multicast addresses fails on EISA FDDI. 8. Data page fault panic in fddi0_open. PHNE_17285: 1. When the MTU of the EISA FDDI interface is set or reset using the lanadmin(1M) command with -M or -R options respectively, the command completes without any errors but does not set/reset the MTU value for the interface. 2. When lanadmin(1M) is used to set the physical address of the interface to the broadcast address ( 0xffffffffffff ) or to 0 ( 0x000000000000 ), the command succeeds. 3. netstat(1M) used with the -i option shows a large number of inbound errors on the EISA FDDI interface. 4. When the EISA FDDI interface is configured down using the ifconfig(1M) command, an unbound SAP promiscuous stream opened on the interface fails to receive IP/ARP packets coming in on the interface. 5. The system may panic with a 'Data page fault' when the EISA FDDI interface is operating in promiscuous mode with heavy inbound traffic. 6. The system panics with a 'Data page fault' when promiscuous mode is repeatedly turned on and off over the EISA FDDI interface. 7. The 'Operation Status' of the EISA FDDI interface, as displayed by the lanadmin(1M) command, is not marked 'down' when there is a cable disconnect. PHNE_17061: 1. The system panics with a data page fault, when many Input/Output (I/O) cards are configured on a system with EISA FDDI card/driver. 2. NFS server daemons operating over EISA FDDI hang, eventually followed by a system hang. 3. High checksum errors and degraded network performance, observed over EISA FDDI interface, on B and D class systems which are non cache coherent I/O (ie. CCIO). 4. When OSI stack is configured on top of EISA FDDI interface, it fails to communicate with its peers, resulting in application aborts. 5. System panics during system shutdown when OSI stack is configured over EISA FDDI driver. 6. System crashes, with either a HPMC or a memory protection fault panic, under high network traffic over the EISA FDDI interface. 7. System panics with an instruction page fault, when multiple promiscuous streams are enabled over the EISA FDDI interface. 8. The netfmt(1M) output for traces generated by the EISA FDDI driver is incorrect. PHNE_15665: 1. The EISA FDDI interface may hang after logging the message "Waited for stat2_ine4 but it never came" to syslog. 2. When an attempt is made to change the MAC address of the card using lanadmin(1M), the link becomes unusable for up to 10 seconds and the MAC address remains unchanged. 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 EISA FDDI link. PHNE_14791: 1. linkloop(1M) over EISA FDDI may panic the system it is run on. PHNE_14077: 1. Under heavy load, the EISA FDDI card may hang (will not receive or send data). 2. When multicast packets are received on the EISA FDDI link, memory leaks occur in the driver. The system eventually runs out of free memory. 3. Applications cannot send or receive multicast packets over EISA FDDI. 4. Under certain conditions, too many informative driver messages are logged to syslog, causing it to overflow. 5. The fddiif utility sometimes reports negative numbers in the statistics. 6. 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_12974: 1. Inbound data corruption is seen on non-cache-coherent systems when UDP checksum is turned off. This problem is observed readily on D200/D210 systems with EISA FDDI. 2. Inability to bind SNAP SAPs through DLPI. 3. Underrun on transmission of every frame larger than 3000 bytes when EISA SCSI is present. PHNE_12973: 1. Inbound data corruption is seen on non-cache-coherent systems when UDP checksum is turned off. This problem is observed readily on D200/D210 systems with EISA FDDI. 2. Inability to bind SNAP SAPs through DLPI. 3. Underrun on transmission of every frame larger than 3000 bytes when EISA SCSI is present. PHNE_11708: 1. Data written from non-coherent NFS clients gets badly corrupted when UDP checksumming is turned off. With UDP checksumming turned on, data transfer rate is very slow. 2. EISA FDDI interface hangs when EISA bus is stressed. 3. lanadmin(1M) reset panics sometimes; hangs at times. 4. Transmit underruns occur when the EISA bus is loaded. PHNE_11707: 1. Data written from non-coherent NFS clients gets badly corrupted when UDP checksumming is turned off. With UDP checksumming turned on, data transfer rate is very slow. 2. EISA FDDI interface hangs when EISA bus is stressed. 3. lanadmin(1M) reset panics sometimes; hangs at times. 4. Transmit underruns occur when the EISA bus is loaded. PHNE_10818: 1. ServiceGuard fails to startup with EISA FDDI Application Release of March 1997. 2. If there is EISA FDDI traffic destined for a host while it is booting up, the host may panic. 3. EISA FDDI card reset using lanadmin hangs at times. Defect Description: PHNE_20009: 1. CR JAGab73997 / SR 8606105737: A local pointer variable in the driver open routine was not being initialized, thus causing data page fault panics. Resolution: This has been fixed now by initializing the pointer to NULL. 2. CR JAGab75690 / SR8606106494: During a card reset, the buffers on the transmit ring were freed, but not unmapped. This was causing an IOVR leak. Resolution: The pending buffers on the transmit ring are now unmapped in the card reset code. 3. CR JAGab64949 / SR 5003451047: Enhancement request for fddiif/fddilink to support writing to output file. Resolution: Added a '-o' command line option to fddiif/fddilink to support writing the output to a file. 4. CR JAGab75863 / SR 8606106601: Multicast addresses are not reloaded after a Card reset. Resolution: All multicast addresses are now reloaded after a card reset. 5. CR JAGab74656 / SR 8606105918: The driver calls copyout while still holding a spinlock. However design considerations do not allow spinlocks to be held across copyout, since a call to copyout can block. Resolution: The spinlock is now released prior to calling copyout and is locked again after the call. 6. CR JAGac40038 / SR 8606124655 There were 2 potential problems in the code: a) When a packet is sent up in the receive path, the write pointer of the receive ring is updated with the local write pointer value. This can create a memory leak, if the watchdog runs on another processor when the packet is sent up, and allocs buffers for the receive ring, thus changing the write pointer. b) Similarly, when all the packets have been processed in the receive path, the read and write pointers of the receive ring are updated with the local pointer values. This would again cause a leak if the watchdog had run on another processor and allocated receive buffers. Resolution: The fix is to not update the ring write pointers when processing received packets, since the write pointers do not change in this code path. 7. CR JAGac40041 / SR 8606124658 The NIO FDDI Subagent was querying the HSC FDDI driver with the SMT_GET ioctl. Since the format of the calls are different in the two drivers, the system panics. Resolution: The fix is to check for illegal format of the SMT_GET ioctl calls and return EINVAL for invalid format calls. 8. CR JAGac87837 / SR 8606129502: If a card reset occurs when a linkloop is in progress, subsequent linkloops will fail with a BIND error. The problem was occurring due to DLPI ioctls being blocked when a reset is in progress. This results in an unbind request failing, causing subsequent binds to the same SAP to fail. Resolution: The fix is to not block DLPI ioctls during a card reset. 9. CR JAGac88808 / SR 8606129893: If the EISA FDDI interface is flagged up using ifconfig, the interface state remains UP even if the cable is not connected. Resolution: This has been fixed by monitoring the ring state in the watchdog routine and setting the if_flags appropriately. 10.CR JAGac97430 / SR 8606130828: The function format_link_raw() was being passed 7 arguments when it expects 8 arguments. This was causing a core dump. Resolution: This has been fixed by passing a NULL string as the 8th argument to format_link_raw(). PHNE_18869: 1. While dismantling a promiscuous stream, the promiscuous mode function pointer in the driver's board structure is set to NULL. If a packet destined for the same stream is processed on another processor simultaneously, it could result in an instruction page fault panic, due to the function pointer being NULL. Resolution: The fix is to lock the critical portion of code where the promiscuous mode related structures are accessed/modified. 2. The problem was that the if_flags in the ifnet structure was not being updated properly on a ring disconnect indication being received. This results in the lanscan and ifconfig commands showing the interface status as up even when the cable is disconnected. Resolution: The fix is to update the if_flags in the ifnet structure to reflect the correct interface status, whenever a ring disconnect or connect indication is received. 3. This problem was fixed in an earlier patch by increasing the transmit FIFO watermark on the FSI chip to MTU size. However the FIFO watermark was getting reset to the default value after a card reset. Resolution: The transmit FIFO watermark is now set to MTU size after a card reset also. 4. All FDDI multicast addresses have the I/G (Individual/Group) bit set to 1. The Driver code was not checking for attempts to add multicast addresses with the I/G bit 0, and would return success. Resolution: The code has now been changed to return EINVAL for an invalid multicast address (i.e I/G bit set to 0). 5. Since nettl is not started when the card init is done during bootup, EISA FDDI error messages are not logged to nettl during boot. To determine whether error messages can be logged with nettl, a flag in the driver's board structure, which indicates whether a card init has been done, is used. This flag was getting reset during a card reset, and so subsequent error log messages were not getting logged with nettl. Resolution: The problem has been rectified by ensuring that the flag is always set, once a card init is done. 6. The EISA FDDI SNMP subagent was not being supported. The reasons to have this feature was to maintain consistency between the different FDDI cards, and the ability to manage all the FDDI networks from OpenView management station. Resolution: The EISA FDDI SNMP subagent 'fddi0agt' is now being provided. This will allow the systems having EISA FDDI cards to be managed by OpenView. 7. The DLPI ioctl, DL_HP_DISABMULTI would return success, but the multicast address in the CAM on the EISA FDDI card was not getting deleted. This was happening because the multicast address was not being sent to the card in the correct format. Resolution: This has been fixed by byte swapping the multicast address in the command control block, before sending the command to the card. 8. The panic was happening when the EISA FDDI device file is opened, with no EISA FDDI card configured on the system. Under the above circumstances, the open routine tries to access a null board structure pointer, resulting in a data page fault panic. Resolution: The fix is to check for a null board structure pointer and return ENODEV if it is null. PHNE_17285: 1. When lanadmin(1M) is run with the -M option to set the MTU for the interface or with the -R option to reset it to the default value, it sends 'change MTU' ioctl (I/O Control) request to the driver. The driver neither handled this ioctl request nor returned an error. As a result, the lanadmin(1M) command completed without errors, but did not set/reset the MTU. Resolution: The driver has been fixed to handle the ioctl request and hence set/reset the MTU as expected. An error ( EINVAL ) is returned if the driver cannot handle the request. For example, EINVAL is returned when the requested MTU value is too high (>4352) or too low (<100). 2. When the lanadmin(1M) command is used with the -A option to set the physical address of the interface to either 0xffffffffffff or 0x000000000000, the driver did not check for these addresses and set the physical address as such. This is inconsistent with the behavior of other networking cards/drivers, that prevent the physical address being set to the above values. Resolution: The driver has been fixed to return an error (EINVAL) for the above values. 3. Packets which were being dropped, either due to the interface being configured down ( using the ifconfig(1M) command ), or due to the driver not being able to decipher the protocol type of the packet, were counted as inbound errors for IP. Resolution: The driver has been fixed to increment the card specific statistics but not increment the network (IP) statistics, in the above cases. 4. When an unbound stream in SAP promiscuous mode is operating over the EISA FDDI interface and the interface is configured down using the ifconfig(1M) command, the driver stops sending up IP/ARP packets to the promiscuous stream. The expected behavior is to continue sending these packets up to the promiscuous stream. 5. Under heavy network traffic, with the EISA FDDI interface in promiscuous mode, when a call to allocate memory failed, an inbound buffer could be freed more than once, resulting in a system panic. 6. When promiscuous mode is turned on/off repeatedly, there was a time window during which the stream which had previously turned promiscuous mode off was closed before the card's promiscuous mode was turned off by the driver. The time window was introduced because of the order in which the driver carried out the steps to disable promiscuous mode on the interface. Due to this time-window, some packets were still sent up to a non-existent stream. This led to a system panic. 7. The ifOper MIB variable, that is displayed as the 'Operation Status' by the lanadmin(1M) command, shows the operational state of the interface. The EISA FDDI driver did not update the value of ifOper to 'down' when it detected a cable disconnect. Resolution: The driver has been fixed to update the state of the ifOper MIB variable on cable disconnects and reconnects. PHNE_17061: 1. When multiple I/O cards are configured, it is possible that the driver's attempt to map its I/O buffer fails. Under these conditions, when the driver attempts to unmap these I/O buffers, the system panics with a data page fault. 2. When the driver fails to enqueue packets for transmission ( as was seen under heavy NFS traffic ), the driver treats these packets as dropped. However, it failed to free the buffers for the packet. This resulted in kernel memory leak, eventually leading to a system hang. 3. On systems without CCIO support, the driver needs to maintain cache coherency during DMA transactions, by flushing/purging the CPU cache as necessary. The EISA FDDI driver did not synchronize its inbound data buffer pool with the processor cache. Hence stale data was passed up to the upper layers, resulting in checksum errors and re-transmissions, leading to degraded performance. To verify this problem, run netstat(1M) to display bad checksums. In addition, to check if the system supports ccio, run the following command on the system : /usr/bin/grep "^ccio" /stand/system If the above command does not display 'ccio', then the system is non cache coherent and this patch needs to be installed, to rectify the problem. 4. The control field in the packet header of outbound Unnumbered Information (UI) packets in the EISA FDDI driver was not initialized. As a result, communication was not established with remote hosts, causing application aborts. 5. During system shutdown, the OSI stack sends the OSIUNBIND request to the driver. The driver failed to unbind the protocol stack stream as it incorrectly compared the service access point (SAP) values and returned an error. However, the OSI stack was unbound and any attempt by the driver to send packets on that stream resulted in a system panic. 6. Under heavy network traffic conditions, the EISA FDDI driver may sometimes invoke internal card resets to recover from transmit hangs. In the driver's watchdog timer, when attempting an internal reset ( for automatic recovery ), the driver invokes a kernel sleep routine while waiting for reset completion. Since the watchdog timer executes in an interrupt system context, calling sleep leads to a system crash ( HPMC or memory protection fault ). An alternate mechanism of completing resets in driver interrupt routine has been implemented. 7. When multiple streams enable promiscuous mode on a single interface, the driver failed to distinguish between bound and unbound streams. As a result the streams queue pointer was corrupted, resulting in a panic. 8. The EISA FDDI formatting routines were using incorrect offsets into the trace buffers, resulting in incorrect output. PHNE_15665: 1. A software reset mechanism was introduced in the EISA 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 MAC address of the card cannot be changed. Users were not prevented from attempting to do this. 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_14791: 1. The EISA FDDI driver assumed that MAC addresses were 16-bit aligned. This assumption is incorrect for linkloop packets. PHNE_14077: 1. A defect in the Motorola FSI chip causes the card to hang under heavy load. 2. 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. 3. 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. 4. SMT and other informative messages are incorrectly sent to syslog instead of the NetTL log by the EISA FDDI driver. 5. Though the statistics are maintained as unsigned integers by the driver, fddiif displays them as signed values. 6. The EISA FDDI lanadmin(1M) shared library does not close the catalog file after using it. PHNE_12974: 1. A missing cache purge at the time the receive buffer is set up causes stale data to appear in the received packet. The stale data starts at cache line boundaries and can run to multiples of the cache line size. 2. Incorrect coding of the protocol binding functionality makes the driver think the protocol has been bound already. 3. When EISA SCSI is present, system firmware automatically disables BCLK stretching resulting in a slight slowdown of the EISA bus. This, coupled with the limited bandwidth of the EISA bus, restricts the ability of the EISA FDDI card to DMA the packet at the rate needed by the FDDI network. The EISA FDDI card, by default, sets its transmit FIFO watermark to 2 KB, which means that it starts transmission on the FDDI network after it has got 2 KB of data in its FIFO. This patch increases the watermark to the FDDI MTU (4352 bytes). PHNE_12973: 1. A missing cache purge at the time the receive buffer is set up causes stale data to appear in the received packet. The stale data starts at cache line boundaries and can run to multiples of the cache line size. 2. Incorrect coding of the protocol binding functionality makes the driver think the protocol has been bound already. 3. When EISA SCSI is present, system firmware automatically disables BCLK stretching resulting in a slight slowdown of the EISA bus. This, coupled with the limited bandwidth of the EISA bus, restricts the ability of the EISA FDDI card to DMA the packet at the rate needed by the FDDI network. The EISA FDDI card, by default, sets its transmit FIFO watermark to 2 KB, which means that it starts transmission on the FDDI network after it has got 2 KB of data in its FIFO. This patch increases the watermark to the FDDI MTU (4352 bytes). PHNE_11708: 1. Open GL requires that drivers do not assume that the data buffers they handle will be in Space ID 0. As NFS passes down buffers with non-zero space ID to the driver, cache flushes performed assuming space ID 0, result in the intended data not being flushed. 2. FDDI interface goes into CB running state under stress testing. 3. In reset sequence, freeing an already freed mbuf panics the system. 4. Under heavy load, the EISA bus is not able to supply outbound data at the rate expected by the FDDI link, thus requiring packets to be cached in on-board memory before sending on the wire. PHNE_11707: 1. Open GL requires that drivers do not assume that the data buffers they handle will be in space ID 0. As NFS passes down buffers with non-zero space ID to the driver, cache flushes performed assuming space ID 0 result in the intended data not being flushed. 2. FDDI interface goes into CB running state under stress testing. 3. In the reset sequence, freeing an already freed mbuf panics the system. Also, driver support for the card reset operation was not adequate. 4. Under heavy load, the EISA bus is not able to supply outbound data at the rate expected by the FDDI link, thus requiring packets to be cached in on-board memory before sending on the wire. 5. ServiceGuard requires the first word in the mib.ifDescr field to be the interface name and unit number, e.g., lan0. Unfortunately, EISA FDDI in the Application Release of March 1997 replaced the word with fddi0. ServiceGuard attempted to find an interface named fddi0 and failed. 6. Interrupts are enabled and the inbound path is initialized in the driver before IP initializes the ipintrq. If there is traffic destined for the host on the EISA FDDI interface before IP gets a chance to initialize ipintrq, the interrupt service routine in the driver attempts to lock the ipintrq and enqueue the packet and this results in a panic. The solution is to discard IP/ARP packets unless the interface is configured up (IFF_UP is set). PHNE_10818: 1. ServiceGuard requires the first word in the mib.ifDescr field to be the interface name and unit number, e.g., lan0. Unfortunately, EISA FDDI in the Application Release of March 1997 replaced the word with fddi0. ServiceGuard attempted to find an interface named fddi0 and failed. 2. Interrupts are enabled and the inbound path is initialized in the driver before IP initializes the ipintrq. If there is traffic destined for the host on the EISA FDDI interface before IP gets a chance to initialize ipintrq, the interrupt service routine in the driver attempts to lock the ipintrq and enqueue the packet and this results in a panic. The solution is to discard IP/ARP packets unless the interface is configured up (IFF_UP is set). 3. Driver support for card reset operation was not adequate. SR: 8606105737 8606106494 5003451047 8606106601 8606105918 8606124655 8606124658 8606129502 8606129893 8606130828 5003463802 1653301168 1653287607 5003389254 1653264069 5003451187 1653272146 1653278499 1653288043 5003418723 1653266965 1653266973 1653243592 1653248484 5003394668 5003413955 5003375485 1653233015 1653228262 1653223008 4701349886 4701343954 Patch Files: /usr/conf/lib/libfddi0.a /usr/conf/lib/fddi0_header.o /usr/conf/master.d/fddi0 /usr/lib/lanadmin/libdsfddi0.1 /usr/lib/lanscan/libpefddi0.1 /usr/lib/libfddifmt0.1 /usr/lib/nls/msg/C/fddi0.cat /usr/bin/fddiif /usr/bin/fddilink /usr/bin/fddidump /sbin/init.d/eisafddi /usr/sbin/fddi0agt /sbin/init.d/SnmpFddi0 /sbin/rc2.d/S572SnmpFddi0 /sbin/rc2.d/K428SnmpFddi0 what(1) Output: /usr/conf/lib/libfddi0.a: EISA FDDI fddi0 libfddi0 B.10.20.12 PHNE_20009 $Date : 2000/01/05 21:34:06 $ /usr/conf/lib/fddi0_header.o: None /usr/conf/master.d/fddi0: None /usr/lib/lanadmin/libdsfddi0.1: libdsfddi0.1 EISA FDDI B.10.20.12 PHNE_20009 $Date: 99/12/27 02:07:03 $ /usr/lib/lanscan/libpefddi0.1: libpefddi0.1 EISA FDDI B.10.20.12 PHNE_20009 $Date: 99/12/27 02:09:45 $ /usr/lib/libfddifmt0.1: libfddifmt0.1 EISA FDDI B.10.20.12 PHNE_20009 $Date: 99/12/27 17:08:22 $ /usr/lib/nls/msg/C/fddi0.cat: None /usr/bin/fddiif: fddiif EISA/HSC FDDI B.10.20.12 PHNE_20009/10 $Date: 99/12/27 21:37:41 $ /usr/bin/fddilink: fddilink EISA/HSC FDDI B.10.20.12 PHNE_20009/10 $Dat e: 99/12/27 21:40:00 $ /usr/bin/fddidump: fddidump EISA/HSC FDDI B.10.20.12 PHNE_20009/10 $Dat e: 99/12/27 18:20:39 $ /sbin/init.d/eisafddi: None /usr/sbin/fddi0agt: -DUNIX -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 LAN: Version: B.10.10 $Date: 96/05/09 11:26:21 $ fddisubagtd.c $Revision: 1.1.117.1 $Date: 98/02/25$ B.10.20.06 DART 39 -DUNIX -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -DSR_SNMPv2 -DSR_SNMPv1 -DSR_HPUX10 -DSR_BSD -DHPUX -DEMANATE Copyright 1992-1995 SNMP Research, Incorporated SNMP Research Distribution version 12.3 -DUNIX -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 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 /sbin/init.d/SnmpFddi0: SnmpFddi0 $Revision: 1.1 $ $Date: 99/06/15 B.10.20.1 2 PHNE_20009$ /sbin/rc2.d/S572SnmpFddi0: SnmpFddi0 $Revision: 1.1 $ $Date: 99/06/15 B.10.20.1 2 PHNE_20009$ /sbin/rc2.d/K428SnmpFddi0: SnmpFddi0 $Revision: 1.1 $ $Date: 99/06/15 B.10.20.1 2 PHNE_20009$ cksum(1) Output: 2698246373 81612 /usr/conf/lib/libfddi0.a 1590360283 229824 /usr/conf/lib/fddi0_header.o 3782332780 3765 /usr/conf/master.d/fddi0 238052532 16384 /usr/lib/lanadmin/libdsfddi0.1 123900632 12288 /usr/lib/lanscan/libpefddi0.1 3325237880 20480 /usr/lib/libfddifmt0.1 3034189258 6740 /usr/lib/nls/msg/C/fddi0.cat 3203640971 20480 /usr/bin/fddiif 3829802221 69632 /usr/bin/fddilink 483166708 20480 /usr/bin/fddidump 4139331745 808 /sbin/init.d/eisafddi 3918341444 335872 /usr/sbin/fddi0agt 197994974 2546 /sbin/init.d/SnmpFddi0 197994974 2546 /sbin/rc2.d/S572SnmpFddi0 197994974 2546 /sbin/rc2.d/K428SnmpFddi0 Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_10818 PHNE_11707 PHNE_11708 PHNE_12973 PHNE_12974 PHNE_14077 PHNE_14791 PHNE_15665 PHNE_17061 PHNE_17285 PHNE_18869 Equivalent Patches: None Patch Package Size: 870 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_20009 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_20009.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_20009. 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_20009.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_20009.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: If any of the versions B.10.20.01 through B.10.20.04 of the HSC FDDI product is installed on the system, PHNE_15666 or a superseding patch, should also be installed for the common utilities fddiif, fddidump and fddilink to work over both the links. This is not needed if version B.10.20.08 of the HSC FDDI product is installed.