Patch Name: PHNE_28778 Patch Description: s700_800 11.11 B.11.11.[00-07] APA cumulative patch Creation Date: 03/07/23 Post Date: 03/09/01 Hardware Platforms - OS Releases: s700: 11.11 s800: 11.11 Products: HP Auto-Port Aggregation/9000 B.11.11.00 B.11.11.04 B.11.11.07 Filesets: HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP HP-APA-KRN.APA-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_32,v=HP HP-APA-KRN.APA-KRN,fr=B.11.11.07,fa=HP-UX_B.11.11_32,v=HP HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP HP-APA-KRN.APA-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,v=HP HP-APA-KRN.APA-KRN,fr=B.11.11.07,fa=HP-UX_B.11.11_64,v=HP HP-APA-RUN.APA-RUN,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-RUN.APA-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-RUN.APA-RUN,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-RUN.APA-INIT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-RUN.APA-INIT,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-RUN.APA-INIT,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-FMT.APA-FORMAT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-FMT.APA-FORMAT,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-FMT.APA-FORMAT,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-SAM.SAM-APA,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-SAM.SAM-APA,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-SAM.SAM-APA,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-LM.APA-LM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-LM.APA-LM,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64,v=HP HP-APA-LM.APA-LM,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64,v=HP Automatic Reboot?: Yes Status: General Release Critical: Yes PHNE_28778: PANIC CORRUPTION Symptom 4, 5, 12 fixes panic. Symptom 7, 17 fixes corruption. PHNE_27951: PANIC PHNE_27198: PANIC PHNE_26774: PANIC PHNE_25456: CORRUPTION PHNE_24309: PANIC PHNE_24072: PANIC PHNE_23160: PANIC Category Tags: defect_repair enhancement general_release critical panic corruption manual_dependencies Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28778 Symptoms: PHNE_28778: 1. If more than one failover groups are configured in /etc/lanmon/lanconfig.ascii file, and if one fails to be configured for any reason, other failover groups may not be formed. 2. lanqueryconf, lancheckconf and lanapplyconf may fail if Hyperfabric, X25, ACC, or ATM interfaces are in the system. 3. The LAN_MONITOR commands display various hard to understand error messages such as : "ERROR: Call to APA_SET_LANMON_CONFIGURE failed for Fail-Over Group lan900. errno= 219" 4. LACP: system may panic under Low Memory condition. 5. System may panic when running "hpapa stop" and "hpapa start" after VLAN is configured on some physical interface. 6. lanadmin command shows the incorrect speed of LAN_MONITOR failover group PPA. 7. When the cable is disconnected from a PCI or NIO FDDI card, which is an active member of a failover group, the traffic may take more than 30 secs to switch-over to the standby lan interface. Because of this behaviour there may be a data loss. 8. When selecting the lanadmin "specific" menu for a linkagg, and entering a 2 digit port number, improper data is displayed. 9. An informative nettl message should be logged when the linkagg becomes UP. 10. landeleteconf command causes a nettl DISASTER message to be logged. 11. User can not enable the same multicast address on different streams of the same linkagg. 12. System may panic when stopping LACP while the port is negotiating. 13. Startup script "hplm" does not return a correct exit status when /etc/lanmon/lanconfig.ascii does not exist. 14. Source Routing does not work on a token ring LAN_MONITOR failover group. 15. If PAgP is stopped on the last port running PAgP, the Group capability of all ports in the system will be set to 0. 16. for LAN_MONITOR failover group, if primary port has both lan and snap IP configured, then only lan (or snap) will be switched to the failover group. This is not a supported configuration. 17. Using bound promiscuous mode with LAN_MONITOR failover group may cause data loss when a downed interface comes up and becomes an active link in a failover group when STP is enabled on the switch. 18. When using lanadmin command to clear a LAN_MONITOR failover group, the port number displayed in the error message is -1. 19. When APA receives an unsupported IOCTL request, the error number returned is not accurate. 20. When trunking links with different arpmod_name or mac_type, if all other features (Speed, MTU etc.) match for them, the aggregte will be formed. This is not supported and expected. 21. When non-member port is being deleted from a linkagg using "lanadmin -X -d" command, the error output message does not make sense with the reason. e.g. see the wrong output when following command is issued when port 0 is not in the linkagg 900, lanadmin -X -d 0 900 Error: Too many ports for the operation to succeed on LinkAgg 900. 22. If a port's mode is set to FEC_AUTO in hp_apaportconf file and the port is down, then "hpapa start" will not be able to start the auto negotiation and lanadmin command shows the port mode to be MANUAL which is incorrect. 23. In the scenario where HP_APA_DEFAULT_PORT_MODE is set to MANUAL in hp_apaconf file, run "hpapa start", "hpapa stop", then comment out HP_APA_DEFAULT_PORT_MODE and re-run "hpapa start", the default mode will be MANUAL instead of FEC_AUTO. 24. When user runs "hpapa stop", the ports in auto mode linkagg will go to LAN_MONITOR mode. 25. When starting auto negotiation, some error handling is not consistent. 26. Incorrect information in lanapplyconf and landeleteconf manpage. 27. Incorrect linkagg name in lanqueryconf and landeleteconf manpage. PHNE_27951: 1. An application which issues a connect() call at the same time the MAC address of a linkagg changes may get an ENETUNREACH error. 2. System may panic when accessing linkagg statistics while resetting ports in the linkagg. PHNE_27198: 1. When the mac_address of the failover group changes, APA should allow user to choose to send RAPID_ARP followed by normal ARP. 2. When using LB_PORT load-balance algorithm, APA panics occasionally when a TCP packet is fragmented by IP and the data part of TCP packet starts with an unaligned address. PHNE_26774: 1. System panics when the following sequences of events happen: (1) Adding link-down ports into an aggregate. (2) Non-IP protocols are bound on the aggregate. (3) A link-down port comes up. 2. LACP: Swap cables between switches may break the link aggregate. 3. LACP: The Marker Information in Marker Response PDU is shifted. 4. LACP: Ports go to the first empty linkagg instead of the linkagg with the same specific Key. 5. LAN_MONITOR: If all ports in a FDDI failover group go down while traffic is running on the failover group, system may panic. 6. Error logs generated in SAM while configuring APA are not user friendly. 7. LACP: Ports with "Port Priority" > 0 may goto STANDBY state. 8. Transient inconsistency exists for internal data of unbound promiscuous mode. 9. "Unknown error" is displayed when trying to configure an IP address on a link aggregate which has not been initialized. 10. Default admin_key value is not set to PPA number of the port as per the comment specified in 'hp_apaportconf' file. 11. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, when the user changes a port's mode to LACP/FEC_AUTO from MANUAL, if there is IP or any other protocol logged on to the port, no error message is displayed and the /etc/rc.config.d/hp_apaportconf file is updated. 12. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no error message is displayed if a link aggregate is configured with a valid IP address but an invalid subnet mask. 13. In the terminal version of SAM, on entering the SAM -> Networking and Communications -> Autoport Aggregation sub-area, the attributes of a port in the "modify" screen are displayed in an incorrect order. 14. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, when a user configures a link aggregate, SAM displays a syntax error message. 15. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, whenever a port is removed from or added to a link aggregate, the following error message is displayed: ERROR MESSAGE: ERROR: lan902 interface | -X -g 902 0 902 : Error: LinkAggregate 902 is already enabled (LINK_UP) 16. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, SAM modifies the /etc/rc.config.d/hp_apaconf file despite the failure of the "Configure Link aggregate" task. 17. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, redundant error messages are displayed when the "Modify Network Physical Port Attributes.." action fails. 18. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no warning or error message is displayed when a user selects a port with different Group capability in the "Add or Delete Network Physical Port" screen. 19. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, SAM disables "Modify Network Physical Port Attributes.." action item when a user selects a port in the LACP_AUTO link aggregate. 20. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no warning or error message is displayed when a user assigns invalid Port Priority for a port in the "modify" screen. 21. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no warning or error message is displayed when a user assigns invalid Group Capability for a port in the "modify port" screen or a link aggregate in the "configure link aggregate" screen. 22. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no warning or error message is displayed when a user assigns an invalid IP address to a link aggregate in the "configure link aggregate" screen. 23. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no warning or error message is displayed when a user assigns an incorrect key for a port in the "modify port" screen. 24. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, SAM disables the "add" (<) btn, which is used to add the eligible ports with non-zero group capability into a link aggregate with zero group capability and status DOWN. 25. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, when a user assigns the same IP address to a link aggregate which has been assigned to another interface, the above action fails but /etc/rc.config.d/netconf is modified.Also, SAM calls the "ifconfig" command evenif a user does not modify the IP address or subnet mask. 26. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, no warning or error message is displayed when a user selects LACP_AUTO mode port for addition to the FEC_AUTO link aggregate in the "Add or Delete Network Physical Port" screen. 27. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, when a user adds a port to a link aggregate or deletes a port from a link aggregate through the "Add or Delete Network Physical Port" screen, the port priority field is not displayed on the screen. 28. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, when a user deletes a port from or adds a port to a MANUAL link aggregate, the group capability value for the link aggregate is deleted from /etc/rc.config.d/hp_apaconf file.Also, if a user adds a port with non zero group capability value into a link aggreagte with zero group capability and in DOWN state, the group capability value for the link aggregate in /etc/rc.config.d/hp_apaconf file is incorrect. 29. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, when a user deletes a port from the FEC_AUTO/LACP_AUTO link aggregate, the /etc/rc.config.d/hp_apaconf file is modified. 30. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, SAM does not disable the add button (<) when a MANUAL port is selected for addition to a LACP_AUTO link aggregate. 31. In SAM -> Networking and Communications -> Autoport Aggregation sub-area, the "Advance Option" button is not disabled for MANUAL link aggregate after ports are added to link aggregate through the "Add or Delete Network Physical Port" screen. PHNE_25833: 1. HOT_STANDBY aggregation does not drop packets incoming from secondary ports. 2. LAN_MONITOR/HOT_STANDBY: after failback to use primary link, traffic is lost for 5 seconds. 3. Sometimes lanadmin output negative MIB value for a link aggregation. 4. When getting port's duplex mode, APA directly references a field of driver's data structure, which may not be there for future driver. 5. LACP: gelan port goes out of link aggregation when promiscuous mode enabled. 6. When using "lanadmin -X -t", "lanadmin -X -g", negative value can be set. 7. Configurable HP_APA_MAX_LINKAGGS may not take effect. 8. Configurable HP_APA_HOT_STANDBY can only be set in lower case. 9. Unecessary memory is allocated for multicast requests. 10. The configurable HP_APAPORT_COLLECTOR_MAX_DELAY is obsolete. 11. Removing APA patch breaks SAM configuration of APA. 12. Unable to form trunk in FEC_AUTO mode on 100BT links with Cisco switch code 6.2.2. PHNE_25456: 1. LAN_MONITOR returns to use primary link before it's usable. 2. Lanadmin output is incorrect after "hpapa stop" and "hpapa start". PHNE_25622: 1. Site Specific: Performance issue. PHNE_24309: 1. LACP:ports that does not receive LACP packet from partner are not removed from link aggregation. 2. LACP:Ports go into a different link aggregation after all ports in the link aggregation go down and then up. 3. LACP:ports going down and up again will NOT join any link aggregation when previous one is used. 4. Enhancement:new configurable parameter to change the default port configuration mode. 5. Service Guard nodes panic when switching back to primary FEC_AUTO link aggregation. 6. The creation of PAgP linkagg, may oscillates when 2 ports from different servers connect to a hub or connect back-to-back with cross over cables. 7. Disconnect and reconnect of cable from ethernet card running PAgP or LACP loses network route and sometimes PAgP takes a long time to converge. 8. Enhance the IP Based algorithm to use the sum of source and destination IP address. 9. APA FEC_AUTO ports can be manually aggregated when the system boot up. 10. LAN MONITOR: lanapplyconf does not move multiple IP addresses to fail-over group. 11.Duplicate MAC addresses are used after an interface is removed from a HOT-STANDBY aggregation. 12.Enhancement: Allow link-down interfaces to be added into manual link aggregations. 13.Enhancement: Allow link-down interfaces to be added into manual link aggregations (including hot_standby link). 14.Manual and PAgP linkagg allow mixture of HalfDuplex and FullDuplex devices. 15.lanadmin can not get statistics of linkagg. 16.Interactive lanadmin APA Outbound Queue Length is wrong. PHNE_24072: 1. APA panic with DLPI scaffold and random reset test over a failover group. 2. 11.11 APA panic with Interrupt stack overflow. PHNE_23160: 1. Lanqueryconf and lanapplyconf dont work with LanMonitor when SNAP is configured. 2. Cannot configure more than 5 link aggregates. 3. LanMonitor: /sbin/init.d/hplm stop loses subnet mask 4. panic - data page fault in apa_output() 5. FEC_AUTO linkagg may not return to its original linkagg after linkdown. 6. Lan Monitor: lanqueryconf puts gelan linkagg and btlan ports in one fail-group. 7. LM: Can't remove failover group if lanapplyconf fails in the middle. 8. LM: lanapplyconf cannot add ports to linkagg with different GC. 9. apa_stop causes a spinlock deadlock with hw_ift_list_lock to occur 10.APA panic in apa_build_and_send_poll_packet() 11.Can not set and remove function addr for token ring LM fail-over group 12.APA-LM fails to enable/disable multicast address for Token Ring FO group 13.APA LB_PORT Load Balancing Doesn't Work 14.Lan Monitor failover groups that have an APA link aggregation as the primary and/or standby link do not communicate with other devices on the network. 15.System panics when nettl trace on APA continues for more than several hours 16.A LAN Monitor fail-over group containing a Link Aggregation as the primary link will intermittently fail to receive data after a bind request. 17.Can't exit Add or Delete Network Physical Ports DIB after an error 18.Add or Delete Network Physical Port DIB does not display and error 19.APA does NOT prevent a non-ether port from being set to MANUAL mode 20.hp_apa Stop crash system on spinlock deadlock/GIGABIT Defect Description: PHNE_28778: Fix Summary: For LAN_MONITOR: 1,2,3,6,7,13,14,16,17,18,26,27 For LACP_AUTO: 4,12 For FEC_AUTO: 15,22 Common to all: 5,8,9,10,11,19,20,21,23,24,25 1. JAGae49071: lanapplyconf aborts the whole process of LAN_MONITOR configuration when there is an error in any of the failover group configuration. Resolution: The lanapplyconf, lancheckconf and lanqueryconf commands, will now properly form all legally configured failover groups. 2. JAGae55561: The lanqueryconf, lancheckconf, and lanapplyconf commands may mistakenly try to process Hyperfabric, X25, ACC, and ATM interfaces if their PPA was the same as that of a LAN device specified in /etc/lanmon/lanconfig.ascii. Resolution: These commands now verify that the device is a LAN device before processing it. 3. JAGad62577: The message catalog contains such messages which are not directly relevant to what customer is doing, but are relevant to product internals. Resolution: The messages are updated to make more sense for the customer and relevant to what they are doing at that time. 4. JAGae28065: LACP aggregators may cause system to panic under Low Memory condition. panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 lacp_add_port_to_aggregator+0x9c lacp_configure_lacp_on_port+0x74 lacp_remove_port_from_trunk+0xf0 lacp_rx_sm+0x3c4 lacp_processing_poll_timer+0x94 lacp_ctrl+0xd8 lacp_poll_timeout+0x1c invoke_callouts_for_self+0x9c sw_service+0x100 mp_ext_interrupt+0x1f0 ivti_patch_to_nop3+0x0 idle_nonpset_loop+0x408 idle+0x4e0 swidle_exit+0x0 Resolution: Create all necessary LACP aggregator objects during system initialization so that it is not necessary to create LACP aggregators during system runtime. 5. JAGae30301: If there is VLAN configured on some physical interface, then run APA start-up script may cause system to panic. panic+0x6c report_trap_or_int_and_panic+0x94 trap+0xed4 nokgdb+0x8 apa_init+0x814 apa_event+0x2a4 hp_dlpi_ioctl+0x24c hp_dlpi_process_ioctl+0xaac hp_dlpi_wput+0x798 putnext+0xcc wait_iocack+0x6c str_istr_ioctl+0x740 hpstreams_ioctl_int+0x264 hpstreams_ioctl+0x50 spec_ioctl+0xac vno_ioctl+0x98 ioctl+0x120 syscall+0x750 $syscallrtn+0x0 Resolution: APA would now exclude any instance numbers which are beyond what is supported by APA. This avoids accessing non-existant data area and thereby avoids a panic. 6. JAGae54889: When the statistics of a linkagg is requested, the speed of the LAN_MONITOR failover group should not be the cumulative speed of all the ports in the failover group. Resolution: The code has been corrected to use the speed of currently active link to be that of LAN_MONITOR failover group. 7. JAGae52066: When there is a cable disconnect on a PCI or NIO FDDI, FDDI driver waits for 30 seconds to generate a link down event which is recieved by APA. After getting this link down event only, LAN_MONITOR will switch-over the traffic to some other link in the failover group. Resolution: When cable disconnect happens, FDDI driver (PCI and NIO) will send back ENOLINK after 5 seconds. When LAN_MONITOR receives the ENOLINK when sending polling packet via the FDDI interface, it will generate an internal link down event, instead of waiting for driver to generate link down event. This will make the fail-over faster and data loss can be minimized. 8. JAGae07711: When displaying aggregation per port data using the lanadmin command "specific" menu, entering a 2 digit Port number causes improper data to be displayed due to not enough arguments being passed to the printing function. Resolution: Correct arguments are passed to the printing function. 9. JAGae05845: A nettl log message should be generated if a linkagg becomes UP. Resolution: When the number of UP ports in the linkagg changes from 0 to 1, generate a nettl logging message. An informative message is now also logged when a port is added to a linkagg. 10. JAGae14210: Clearing a link aggregate, inappropriately logs a DISASTER message in the nettl log. Resolution: Appropriate nettl log events classes are now used to differentiate between temporary and permanent removal of a port from an aggregate. 11. JAGae09117: User can not enable the same multicast address on different streams of the same linkagg. Resolution: APA allows such cases by using reference count for each multicast address enabled on the linkagg. 12. JAGae18792: System may panic when stopping LACP while the port is negotiating. Caused by a lack of lock protection. Resolution: Proper lock protection is added while negotiating. 13. JAGae24042: When /etc/lanmon/lanconfig.ascii does not exist, LAN_MONITOR startup script will not do anything, the return message should be more accurate. Resolution: Correct the exit value and return message to be more accurate. 14. JAGae30014: For TR LAN_MONITOR failover group, the TR ARP help module will not be pushed on the aggregate. Hence when an IP is configured on this failover group, no ARP module is pushed on the stream. Source Routing can not be used. Resolution: When TR LAN_MONITOR failover group is created, its ARP module handler name is copied to the linkagg data structure and used by ifconfig to push that module when plumbing happens on the failover group link. 15. JAGae11150: If PAgP is stopped on the last port running PAgP, the Group capability of all ports in the system will be set to 0. Resolution: Correct the function to keep the Group capability of ports. 16. JAGae51180: When the failover group is being created, the check is made if lan (or snap) is configured on primary port. The check does not include if both lan and snap are configured, in which case should be blocked. Resolution: The check is now made to see if both lan and snap are configured on primary port. If both are configured, then appropriate message is printed and the failover group will be discarded from creation. 17. JAGae57923: When a port belonging to a failover group comes up, it is not allowed to join the failover group immediately. It is allowed to join the failover group only if it receives 3 polling packets successfully. This is done to make sure port can join the failover only after STP on switch stabilizes. When bound promiscuous mode is enabled on a failover group, LAN_MONITOR allows duplicate polling packets to be recieved and make the port join the failover group before STP stabilizes on the switch side. This causes data loss. Resolution: The function which receives the polling packet will now check whether the polling packet received is really intended to the interface which received the polling packet. This way duplicate polling packets due to bound promiscuous mode on failover group, will be ignored. 18. JAGae00528: When using "lanadmin -X -c" to clear a LAN_MONITOR failover group, the port number in the error message was -1. Resolution: Pass correct port number to the function printing the error message. 19. JAGad92707: When APA receives an unsupported IOCTL request, inacurate error number is returned. Resolution: Correct the error number returned. 20. JAGae43347: When port is added to a linkagg, it's mac_type and arpmod_name are not compared along with other features. Resolution: mac_type and arpmod_name are now compared before forming a linkagg. 21. JAGae13538: Wrong error number is used for the case when the non-member port is deleted, hence wrong message. Resolution: Correct error number is used to print the message. With the fix, the message displayed should be as shown below: lanadmin -X -d 0 900 Error: Port 0 is not in LinkAgg 900. 22. JAGad94141: When a port in FEC_AUTO mode is down, lanadmin command may display wrong mode. Resolution: correct the function to display the correct port mode. 23. JAGae14962: The default config mode is not getting reset back during "hpapa stop". Resolution: Reset the default config mode back after "hpapa stop". 24. JAGae27348: When "hpapa stop" tries to stop auto negotiation on a port in AUTO mode, some data structure is not correctly initialized. Resolution: Initialize the data structure correctly and set the port mode to MANUAL after stop the auto negotiation. 25. JAGae38535: When starting auto negotiation, some error handling is not consistent. Resolution: Correct the function to process the error handling in a consistent manner. 26. JAGae01984: In lanapplyconf manpage, the option should be "-c". In landeleteconf manpage, "-g" should take the interface name, e.g "lan900". Resolution: Correct the manpage. 27. JAGae25067: In lanqueryconf and landeleteconf manpage, there are descriptions of "lan90 - lan94" for linkagg name. Resolution: Correct the manpage. PHNE_27951: Fix Summary: For LAN_MONITOR: 1 Common to all modes: 1 1. JAGae42271: When the MAC address of a linkagg changes, in order to send unsolicited ARPs, APA directs the IP layer to take down the link and then bring up the link. This causes an unsolicited ARP to be sent. This is done several times. The process causes IP to unbind and re-bind IP addresses assigned to the device causing the device's network traffic to be interrupted for the device during the down/up sequence. Resolution: Except the first link down and link up, APA/LM will now invoke an IP function that directly causes the unsolicited ARP to be sent. To fix this defect, in addition to this APA patch, you need DLPI's 11.11 patch PHNE_28005, or its superseding patch. 2. JAGae23677: If a port in a linkagg is reset while another process is gathering the statistics of the linkagg, the system may panic. The problem is that during statistics data gathering, APA is not protecting access to the port data structure. So there could be a race between the APA port deletion and the port statistics access. panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 apa_ioctl_get_stats+0x158 apa_ioctl+0x2dc hp_dlpi_get_driver_stats+0xac dlpi_sync_virtual_interfaces+0x1c hp_dlpi_event+0x19c apa_send_link_down_up+0x90 invoke_callouts_for_self+0x9c sw_service+0x100 mp_ext_interrupt+0x1f0 ivti_patch_to_nop3+0x0 idle_nonpset_loop+0x19c idle+0x4e0 swidle_exit+0x0 Resolution: While accessing the statistics of the ports associated with a linkagg, APA now locks the port list to prevent simultaneous deletion of ports by another routine. PHNE_27198: Fix Summary: For LAN_MONITOR: 1 Common to all: 2 1. JAGae17700: When the mac_address of the failover group changes, APA will send Unsolicited_ARP every 5 seconds for 12 times, if the 1st one is lost by the switch or host, then the next ARP is 5s later, which may cause traffic lost for about 5s. Resolution: To let the Unsolicited ARP reach the whole world as soon as possible, 3 new configurables for RAPID_ARP request are provided to user. The RAPID_ARP will be followed by normal ARP of 5s each till 1 minute. 2. JAGae24893: For LB_PORT algorithm, APA assumes all IP packets with protocol type of TCP contain TCP header. But a fragmented TCP packet may contain data only and the data could start with an unaligned address. APA panics when it tries to cast an unaligned address into a TCP header. panic+0x14 report_trap_or_int_and_panic+0x84 interrupt+0x1d4 ihandler+0x928 apa_output+0x3e8 hp_dlpi_wput+0x98 putnext+0xcc ip_wput_frag+0x198 ip_wput_ire+0xf90 ip_wput+0x470 putnext+0xcc tcp_wput+0x478 tcp_rput+0x3824 puthere+0x148 put_release+0x364 ip_rput_local+0x320 ip_rput+0x17c putnext+0xcc hp_dlpi_mblk_fast_in+0x354 hp_dlpi_mblk_intr_put+0x960 streams_put+0xe8 streams_put_release+0x168 hp_dlpi_mblk_intr+0x14c apa_intr+0x184 lanc_ether_ics+0x114 _btlan3_receive_pkts+0x588 _btlan3_isr+0x1a4 sapic_interrupt+0x2c mp_ext_interrupt+0x318 ihandler+0x904 Resolution: When LB_PORT load-balance algorithm is used, one additional check is added for fragmented IP packets. If no TCP header is present, the default port is chosen for output. PHNE_26774: Fix Summary: For LAN_MONITOR: 5 For LACP_AUTO: 2,3,4,7 For SAM-APA: 6,11-31 Common to all: 1,8,9,10 1. JAGae17321: when a protocol is bound on a link aggregate, which only consists of link-down ports, an incorrect inbound processing routine will be used by APA because the link aggregate has not set its features to that of the link-down ports. panic+0x6c m_free+0x170 m_freem+0x14 hp_dlpi_intr_put+0x2a8 streams_put+0xdc hp_dlpi_intr+0x1bc apa_intr+0x188 lanc_802_2_ics+0x4dc btlan_receive_frame+0x658 btlan_isr+0xfc sapic_interrupt+0x2c mp_ext_interrupt+0x2f0 ivti_patch_to_nop3+0x0 idle_nonpset_loop+0xb0 idle+0x4e0 swidle_exit+0x0 Resolution: Set the features of link aggregate to that of link-down ports if the link aggregate has not been initialized yet. 2. JAGae09652: When a LACP linkagg has been formed between server and switch1, if swapping cables to ports running LACP on switch2, ports can not form linkagg again since they can not find a matched aggregator. Resolution: When a port can not find a matched aggregator, create an aggregator of itself, then ports with the same Partner System information can find matched aggregator for trunking. 3. JAGae10727: The Marker Information in Marker Response PDU may shift to the right for NON-CKO driver, it may shift to the left for CKO driver. Since we use the inbound MARKER/MARKER_Response PDU for output, there are some alignment problem. Resolution: Properly process the inbound packet and send it out with correct Marker Information. 4. JAGae16190: When APA allocate linkagg for LACP ports, it fails to compare the Key of the port and that of the linkagg, so it allocate the first free linkagg. Resolution: APA compares the Key of the LACP port and that of the linkagg correctly when allocating linkagg. 5. JAGae17341: When there is traffic on a FDDI failover group, if all the ports in the failover group go down, apa_build_hdr will return without release lock, so system panic on deadlock. panic+0x60 wait_for_lock+0x28c sl_retry+0x18 apa_build_hdr+0x2c hp_dlpi_build_hdr+0xd20 hp_dlpi_unitdata_out+0xfc hp_dlpi_wput+0x524 csq_turnover_with_lock+0x7c puthere+0x244 ire_add_then_put+0x9c ip_wput_nondata+0x470 ip_wput+0x120 csq_turnover_with_lock+0x7c putnext+0x1c8 hp_dlpi_event+0x320 apa_send_link_down_up+0xa0 invoke_callouts_for_self+0x8c sw_service+0xcc mp_ext_interrupt+0x128 ivti_patch_to_nop3+0x0 spinunlock+0x30 trap+0x358 $call_trap+0x30 Resolution: Release Lock before error return in apa_build_hdr. 6. JAGae13333: Reword error messages in hp_apa_init and hp_apaport_init. Resolution: Modified the error messages in hp_apa_init and hp_apaport_init to display user friendly error messages in SAM while configure APA. 7. JAGae10721: LACP ports with "Port Priority" > 0 may goto STANDBY state. In the function where we change port from STANDBY state to SELECT state, we fail to select port with the highest priority. Resolution: Correct the function to select STANDBY ports with highest priority and put it in SELECT state. 8. JAGae15014: Lack of lock protection when changing shared data of unbound promiscuous mode. Resolution: Add lock protection whenever changing the shared data of unbound promiscuous mode. 9. JAGae15016: If a link aggregate has not been initialized, APA returns an internal errno to upper layer when it fails a bind request from DLPI. This internal errno is not understood by upper layer application. Resolution: A standard errno ENXIO will be returned for this case. 10. JAGae16196: hp_apaportconf says default administrative key is PPA number, but it is set to 0. Resolution: Changed the comment in 'hp_apaportconf'. New comment says 'Default Administrative Key is 0.' 11. JAGad89989: Whenever a user modifies the attributes of a port, SAM updates the /etc/rc.config.d/hp_apaportconf file first and then calls the /usr/sbin/hp_apaport_init script to set the new attributes. SAM does not capture the error meesage and hence does not display the same. Resolution: SAM now invokes the /usr/sbin/hp_apaport_init script first, captures the return status and displays the error message if any. The configuration files are not updated in case of an error. 12. JAGad94379: SAM does not capture the value returned by the ifconfig command and no error message is displayed. Resolution: Code has been modified to capture the return value and display an error message, if any. 13. JAGad96981: SAM skips an extra line in the apa_defs.ui file in the terminal version.As a result, values were not displayed against their respective fields. Resolution: The parameters are now displayed properly against their respective fields in the terminal version. 14. JAGae00418: When a user selects the distribution algoirthm for a link aggregate, SAM does not change the distribution algorithm string into corresponding command line value before invoking the /usr/sbin/hp_apa_init script. SAM invokes the /usr/sbin/hp_apa_init script with the incorrect arguments. Resolution: Code has been modified to invoke the /usr/sbin/hp_apa_init script with correct arguments. 15. JAGae01603: Whenever a port is removed from or added to a link aggregate, an incorrect group capability value is passed to the init script. Resolution: SAM now passes correct group capability values in the above case. 16. JAGae01604: When a user configures the link aggregate, SAM updates the /etc/rc.config.d/hp_apaconf file first and then calls the /usr/sbin/hp_apa_init script to set the new attributes. The error meesage is also not captured. The /etc/rc.config.d/hp_apaconf file is modified even if the configuration fails. Resolution: SAM now invokes the /usr/sbin/hp_apa_init script first, captures the return status and displays the error message, if any. The configuration files are not modified in case of an error. 17. JAGae01606: SAM invokes the /usr/sbin/hp_apaport_init script with all the parameters even if one parameter is modified, resulting in multiple error messages being displayed on failure. Resolution: The init script is now invoked only with modified parameters. 18. JAGae01783: When a user selects a port with different Group capability in the "Add or Delete Network Physical Port" screen, SAM calls the Verify_Port_Selected function that fails to display an error message. Resolution: The Verify_Port_Selected function now displays an error message in case the group capability of port is different from link aggregate. 19. JAGae01995: SAM disables "Modify Network Physical Port Attributes .." action item when user selects a port in a link aggregate and not in FEC_AUTO mode. SAM incorrectly assumes that if a port is not in FEC_AUTO mode then it is in the MANUAL mode only. Resolution: Code has been modified to disable action item "Modify Network Physical Port Attributes.." only if a selected port is in a link aggregate and not in FEC_AUTO or LACP_AUTO mode. 20. JAGae03744: SAM does not validate the port Priority field. Resolution: A function is now added to validate the port priority assigned by the user and an error message is displayed in case of an invalid value. 21. JAGae03745: SAM does not validate the Group Capability field for a port and a link aggregate. Resolution: A function is now added to validate the group capability assigned by the user and an error message is displayed in case of an invalid value. 22. JAGae06148: SAM does not validate the IP address assigned by the user. Resolution: A function is now added to validate the IP address assigned by the user and an error message is displayed in case of an invalid IP address. 23. JAGae06150: SAM does not validate the Key value for the port. Resolution: A function is now added to validate the Key value assigned by the user and an error message is displayed in case of an invalid value. 24. JAGae07644: When group capability of a link aggregate with down state is zero, SAM disables the add button,thereby disallowing the addition of port into a link aggregate. Resolution: SAM now enables the "add" button for adding the eligible ports into a link aggregate. 25. JAGae07645: The task manager that configures an interface executes the following commands in sequence: ch_rc - to modify the netconf file ifconfig - to configure the interface. In the above case, even if the ifconfig command fails, the /etc/rc.config.d/netconf file is modified.Also SAM calls "ifconfig" command even if user does not modify IP address or subnet mask. Resolution: The task manager is now split into two and each task manager executes only one command and the error message from ifconfig is trapped. The netconf file is not modified in case of an error. Also, SAM calls "ifconfig" command only if user modifies IP address or subnet mask. 26. JAGae07647: When a user selects a port with configuration mode different from that of link aggregate in ?Add or Delete Network Physical Port? screen, SAM calls the Verify_Port_Selected function that fails to display an error message. Resolution: The Verify_Port_Selected function now displays an error message in all possible cases of configuration mode mismatch. 27. JAGae07648: Whenever a port is added to or deleted from a link aggregate, SAM calls the apa_initialize_ports_avail function to rearrange the ADD/delete screen that fails to display the value of the port priority field. Resolution: The apa_initialize_ports_avail function has been modified to display the port priority field. 28. JAGae07649: When a user does not enter the value for group capability for a link aggregate in the "Advance Options" screen, SAM incorrectly changes it to NULL and updates the "/etc/rc.config.d/hp_apaconf" file with this value. Also, SAM does not change group capability of a link aggregate when a user adds port with non zero group capability into a link aggregate with zero group capability. Resolution: Now SAM does not modify the group capabilty value read from system. In case a user adds a port to a link aggregate with zero group capability and in DOWN state, SAM changes the group capabilty of link aggregate to group capability of the added port. 29. JAGae07651: SAM does not check the configuration mode of thelink aggregate before updating the /etc/rc.config.d/hp_apaconf file. When a user deletes the port from the link aggregate, /etc/rc.config.d/hp_apaconf file is updated. Resolution: The /etc/rc.config.d/hp_apaconf file is not modifed when a user deletes a port from FEC/LACP_AUTO link aggregrate. 30. JAGae08874: SAM enables the add button("<") when a user selects a port which is not in FEC_AUTO mode and if the link aggregate is also not in FEC_AUTO configuration mode. SAM incorrectly assumes that the port's mode is MANUAL if it is not FEC_AUTO. Resolution: Code has been modified to allow addition of port into link aggregate only if the configuration mode of port matches with that of the link aggregate. 31. JAGae10607: SAM does not disable the "Advance option" button if the link aggregate status changes from DOWN to UP on addition of a port into a link aggregate . Resolution: SAM disables the advance option button if link aggregate current status is UP. PHNE_25833: Fix Summary: For FEC_AUTO: 12 For HOT-STANDBY: 1,2 For LAN MONITOR: 2 For LACP_AUTO: 5 Common to all: 3,4,6,7,8,9,10,11 1. JAGad72114: HOT_STANDBY aggregation does not drop packets incoming from secondary ports. Resolution: Add a check for inbound packets. If it does not come from the primary port of a hot_standby linkagg, drop it. 2. JAGae02784: In LAN_MONITOR/HOT_STANDBY trunk, if the primary port goes down and then comes up, the traffic will be switched back to it, but the unsolicited arp will be sent out 5 seconds later, so traffic is lost during this period. Resolution: When traffic is switched back to the primary port, send unsolicited arp immediately. 3. JAGad98498: Sometimes lanadmin shows negative value for some fields in the linkagg's MIB statistics. Because DLPI's local MIB data is not cleared when a linkagg is cleared or when the MIB of the linkagg is cleared. Resolution: In these cases, APA sends an event to DLPI to clear DLPI's MIB data of the linkagg. To fix this defect, in addition to this APA patch, you need DLPI's 11.11 patch PHNE_25388 or its superseding patch. 4. JAGad83618: When getting port's duplex mode, APA directly accesses a field in driver's data structure. The field may not be there for some future driver, it should be treated as an opaque handle that should be simply exchanged between APA and the driver. Resolution: The direct access to the field in driver's data structure is replaced with a call to hp_dlpi_ioctl to get the duplex mode of the driver. 5. JAGad95482: When enabling promiscuous mode of a gelan link aggregation in LACP mode, APA failed to discard the loop back packets. It will think the negotiation packets sent by itself come from partner, so auto negotiation failed, gelan port is kicked out of the aggregation. Resolution: Correct the filtering of loop back packets. 6. JAGad80729: "lanadmin -X -t", "lanadmin -X -g" accept negative value since it didn't check the range of input value. Resolution: APA check the input range for above commands. 7. JAGad91949: In /etc/rc.config.d/hp_apaconf file, if HP_APA_DEFAULT_PORT_MODE is set, the configurable HP_APA_MAX_LINKAGGS may not take effect. Because the implementation of HP_APA_DEFAULT_PORT_MODE overwrites HP_APA_MAX_LINKAGGS with the default value of 50. Resolution: Correct the processing of HP_APA_DEFAULT_PORT_MODE, so that HP_APA_MAX_LINKAGGS is not affected. 8. JAGad92723: In /etc/rc.config.d/hp_apaconf file, configurable HP_APA_HOT_STANDBY doesn't allow uppercase setting. Resolution: Configurable HP_APA_HOT_STANDBY can be set in case INsensitive. 9. JAGad87925: When allocating memory for a multicast request, the size is larger than the correct one. Resolution: Correct the size of the memory allocated for multicast request. 10. JAGad76595: The configurable HP_APAPORT_COLLECTOR_MAX_DELAY in /etc/rc.config.d/hp_apaportconf is obsolete. Resolution: Remove HP_APAPORT_COLLECTOR_MAX_DELAY from /etc/rc.config.d/hp_apaportconf. 11. JAGad93969: When removing APA patch, SAM-APA is unregistered, so SAM-APA is not usable. Resolution: After removing a patch, APA will re-register the SAM-APA which is rolled back. 12. JAGad84692: With Cisco switch code 6.2.2, Servers unable to form trunks in FEC_AUTO mode on 100BT links. Resolution: we corrected the length field of the Ether_header in PAgP hello packets, now the aggregation can be formed with Cisco switch code 6.2.2 PHNE_25456: Fix Summary: For LAN_MONITOR: 1 Common to all: 2 1. JAGad25271: In LAN_MONITOR mode, if the primary port goes down and then comes up, the traffic will be switched back to it immediately. But at this time the port is not in a stable state on the switch side, so the traffic is lost during this period. Resolution: We delay adding the up port back to the fail-over group untill the switch side is stable, we do so by sending poll pkts between ports in a fail-over group. 2. JAGad86621: sometimes after the linkagg goes down or just after the linkagg comes up, the lanadmin shows "INVALID(0)" for some fields. Resolution: we have displayed the information correctly in these cases. PHNE_25622: 1. Site Specific: Trouble shooting code is needed to help monitor performance related issues. Resolution: Temporary Site Specific code was provided to help trouble shoot performance related issues. Future General Release versions of APA will not include this code. PHNE_24309: Fix Summary: For MANUAL: 12,13,14 For FEC_AUTO: 5,6,7,9 For HOT-STANDBY: 11 For LAN MONITOR: 10 For LACP: 1,2,3 Common to all: 4,8,15,16 1. JAGad63198: After a port's parnter stops sending LACP packets for more than several minutes, the port is still in LACP link aggregation. This is a violation of IEEE 802.3ad specifications. Resolution: Code changed to ensure that a time-out port is removed from its current link aggregation. 2. JAGad55785: If all ports in a LACP link aggregation, say lan900, go down and then go up again, the ports will form a new link aggregation other than lan900 because lan900 is reserved by LACP. Resolution: When all ports of a LACP link aggregation go down, the link aggregation is made available for any LACP port. 3. JAGad57002: After all ports in a LACP link aggregation go down, the link aggregation is available for MANUAL, FEC_AUTO and LACP port to join in. Before the ports come up again, the link aggregation could be occupied by MANUAL and FEC_AUTO ports. These ports will fail to be added into their original link aggregation and become standalone ports. Resolution: Code changed to make a LACP link aggregation only available for LACP ports when all of its ports go down. 4. JAGad56988: The default APA port configuration mode is FEC_AUTO and it is not user-configurable. To change port's default configuration mode to non-FEC_AUTO mode, users have to specify each non-FEC_AUTO port's mode in 'hp_apaportconf' file. Failing to do this sometimes leads to unwanted aggregation. Resolution: Added a new variable,APA_DEFAULT_PORT_MODE, to hp_apaconf file that will allow the user to select MANUAL as the default APA port configuration mode. 5. JAGad68730: Service Guard (SG) switches over to the standby FEC_AUTO link aggregation when the primary FEC_AUTO link aggregation goes down. After the primary link aggregation comes up again, SG will try to switch back to the primary link aggregation, and it panics because the primary link aggregation is not stablized yet. Resolution: As a workaround, APA will delay the notification of link-up events to SG until the aggregation becomes stable. 6. JAGad51978: when two ports running PAgP on different machines are connected to a hub or connected back-to-back with cross over cables, the ports may go in and out of linkagg repeatedly. Resolution: The solution changes the process that causes the oscillation on the PAgP port. 7. JAGad55767: problem 1: Sometimes during reboot, if the switch side is not set to be FEC_AUTO mode, ports in FEC_AUTO mode at the server side will not go to Standalone state. problem 2: If an Ethernet NIC is reset,"lanadmin reset" or cable disconnect/reconnect, the NIC hardware will recover, but its IP interface is rendered unusable. Specifically, the IP interface route is removed from the hosts routing table. Resolution: for problem 1: if the other side of the link is not running PAgP, the port in FEC_AUTO mode will be moved to STANDALONE state in specific time period. for problem 2: APA has add a new variable APA_DEFAULT_PORT_MODE in hp_apaconf file, we recommend users to set it to be MANUAL mode when system boot up. If you don't want a port to be part of a linkagg, put it to MANUAL mode is highly recommended. 8. JAGad26600: The APA IP Based Load Balancing algorithm should be updated to use both Source IP address and the Destination IP address instead of just the least significant byte of the destination IP address.This will result in a better distribution of traffic when using this algorithm. Resolution: we enhanced the APA IP Based Load Balancing Algorithm for better distribution. 9. JAGad62161: APA capable ports with their configuration modes set to FEC_AUTO can be aggregated into a manual aggregation with the hp_apaconf file HP_APA_MANUAL_LA variable. This should not be allowed. Resolution: The solution is to check that the mode is FEC_AUTO or LACP_AUTO and not allow it to be included in a MANUAL mode linkagg. 10.JAGad58435: Lanapplyconf assumes only one IP interface exists on the primary port. If multiple IP addresses are configured on the primary port, only the primary IP address is moved on creating fail-over group. Resolution: Code changes made to move all IP interfaces from primary port to fail-over group. 11.JAGad69882: If primary interface is added into a HOT-STANDBY aggregation after secondary interface, the aggregation will have the same MAC address as the secondary interface when the secondary interface is removed from the aggregation. Resolution: Code changes made to ensure that a HOT-STANDBY aggregation always has the MAC address of the primary interface. 12.JAGad66863: If an interface is in link-down (e.g. cable disconnected) state, it cannot be added into a link aggregation. This restriction causes a manual aggregation to fail to form at boot time when a link-down interface is included. Adding a link-down interface to link aggregation via lanadmin command also fails. Resolution: Link-down interfaces are now allowed to be included into a link aggregation as inactive members. The interface will only become functional when it comes up. 13.JAGac94919: If an interface is in link-down (e.g. cable disconnected) state, it cannot be added into a link aggregation. This restriction causes a manual aggregation (including hot_standby link) to fail to form at boot time when a link-down interface is included. Adding a link-down interface to link aggregation via lanadmin command also fails. Resolution: Link-down interfaces are now allowed to be included into a link aggregation as inactive members. The interface will only become functional when it comes up. 14.JAGad67040: when aggregate ports to a linkagg, APA doesn't check for duplex mismatches and does allow the linkagg to form. Resolution: we add the check for Duplex mismatches, and not allow the linkagg to form. 15.JAGad69427: lanadmin fails to give the mib statistics for a linkagg. Resolution: lanadmin now shows the correct mib information for the linkagg. 16.JAGad73544: The interactive lanadmin command is displaying an erroneous value for the APA Outbound Queue Length after booting the system. Resolution: While running lanadmin, the field "Outbound Queue Length" now shows the correct value for linkagg. PHNE_24072: 1. JAGad53984: Sometimes in nested fail-over group, if all linkaggs go down,due to the sync model it takes some time to remove all the linkaggs. Meanwhile if first linkagg's port comes up again, it tries to access the second linkagg's port and since it is down, a page fault occurs. panic+0x14 report_trap_or_int_and_panic+0x84 interrupt+0x3b8 $ihndlr_rtn+0x0 apa_verify_linkagg+0x338 apa_ioctl_add_linkagg_ports+0x778 apa_event_interface_up+0x728 apa_process_event+0x210 apa_process_queue+0x190 invoke_callouts_for_self+0xe4 sw_service+0xb4 mp_ext_interrupt+0x2c0 ivti_patch_to_nop3+0x0 fpdlongloop_2_0+0x58 fdc_more_pages+0x8 hdl_cwfault+0xb64 vm_no_io_required+0xc48 vx_do_pagein+0x100 vx_pagein+0x1d0 virtual_fault+0x668 vfault+0x220 trap+0xa80 nokgdb+0x8 Resolution: To fix the problem, when all ports of a linkagg go down and the linkagg is part of a failover group, the linkagg will be removed immediately intead of being processed via the synch-Q. 2. JAGad56321: This problem is caused when a port is set in outbound promiscuous mode and is running pagp. The driver loops back every packet for an outbound promiscuous port, this causes a pagp function to recursively call itself, at last the stack overflow. panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 pagpXmitConfiguration+0x0 pagp_xmit_sm+0x9d8 pagp_port_up_a7_a8+0x58 pagp_port_sm+0x428 process_info_pkt+0x3d8 pagp_ctrl+0xbc pagp_recv+0x130 lanc_802_2_ics+0x51c btlan_slow_hw_req+0xe3c btlan_hw_req+0xce4 btlan_resolved_output+0x18 pagp_send_hello+0x318 pagp_xmit_sm+0xab4 pagp_port_up_a7_a8+0x58 pagp_port_sm+0x428 process_info_pkt+0x3d8 pagp_ctrl+0xbc . . . pagp_ctrl+0xe4 pagp_poll_timeout+0x1c invoke_callouts_for_self+0x9c Resolution: To fix the problem, PAgP will check the mac address of incoming packet, if it matches the port's own mac address, the packet will be dropped. PHNE_23160: 1. JAGad39337: LAN Monitor configured LinkAggs do not work when SNAP encapsulation is used. Both lanqueryconf and lanapplyconf fail to recognize SNAP as a valid configuration and therefore fail to configure Fail-over groups when this encapsulation is used. Resolution: Previously lanmonconf only checks and sets 'lan' interface. Now both 'lan' and 'snap' interfaces are checked and searched. 2. JAGad39341: When booting a system APA will only configure the first 5 LinkAggs. This is caused because the start-up script uses lanscan to determine the LinkAgg PPA # and since only the first 5 LinkAggs are shown by default in lanscan only these will be configured. Resolution: Modify the /sbin/init.d/hp_apa start-up script to not use lanscan to determine the PPA numbers of the LinkAggs to pre-configure at boottime. 3. JAGad40906 when a /sbin/init.d/hplm stop is performed, LAN Monitor fails to save the netmask information from the fail-over group prior to unplumbing it and moving the IP address back to the primary link. So the mask reverts to standard IP class mask as default. Resolution: This problem is fixed in the landeleteconf code. The netmask address is now saved before the fail-over group is unplumbed. The netmask is then reconfigured on the primary port during the ifconfig process. 4. JAGad44744 An aggregation using LB_PORT load balancing mode can execute a path that uses an uninitialized variable which causes the panic: Interrupt Type 15 (Data page fault): crash event was a panic panic+0x14 report_trap_or_int_and_panic+0x84 trap+0xd9c nokgdb+0x8 apa_output+0x360 hp_dlpi_wput+0x98 putnext+0xcc ip_wput_frag+0x198 ip_wput_ire+0x10a8 ip_wput+0x470 putnext+0xcc udp_wput+0x328 putnext+0xcc svc_clts_ksend+0xe8 svc_sendreply+0x64 rfsexp_dispatch+0x230 svc_getreq+0x1f4 svc_run+0x728 nfsexp_svc+0x1e0 nfs_stub_svc+0xa4 coerce_scall_args+0xcc syscall+0x6f8 $syscallrtn+0x0 Resolution: Correctly initialized the variable. 5. JAGad44820: A window in the PAgP logic causes multiple APA processes to attempt aggregation of the same port. This occurs when all the ports in the linkagg go down and then come back up. The formation of the linkagg may cause to form to a different linkagg than the original. Resolution: A new function is introduced to ensure that only one port can access the pagp record information. 6. JAGad46730: For lan monitor, 'lanqueryconf -s' puts gelan linkagg ports and btlan ports in one fail-group; when 'lanapplyconf' is executed afterwards, it will fail with error number 1023, which means "speed mismatch". Resolution: Added another ioctl to check if two ports can be included in a linkagg. All checks for compatible ports are moved into kernel. 7. JAGad46735 when lancheckconf command attempts to duplicate some of the kernel checks to verify fail-over group configuration, some of the key checks are missing (i.e. CKO support, speed match). Therefore illegal configurations may be allowed during the query process, and therefore may partially fail during the apply. This will cause the binary file to not be created and therefore any partial configurations that completed during the apply will not be able to be deleted. Resolution: Added the missing checks as in JAGad46730. Also lanapplyconf will run to completion thus creating a binary configuration file. Then patially configured groups can be deleted. 8. JAGad46809 In lan monitor mode, a port cannot be added to an empty linkagg with different Group Capability. Resolution: in lanapplyconf, we no longer check the Group Capability for LAN_MONITOR. 9. JAGad48765 When the command /sbin/init.d/hpapa stop is executed a system panic may occur. This occurs when the routine apa_stop holds the hw_ift_list_lock across the call to apa_ioctl_protocol_stop. This function calls into DLPI which can also try to acquire the hw_ift_list_lock. Resolution: All references to the hwift_list_lock were removed from apa since they are no longer needed after changing the apa processing of the hw_ift_list. 10.JAGad49351 function apa_build_and_send_poll_packet attempts to deference a null pointer returned by allocb. Interrupt Type 15 (Data page fault): crash event was a panic panic+0x14 report_trap_or_int_and_panic+0x84 interrupt+0x1d4 $ihndlr_rtn+0x0 apa_build_and_send_poll_packet+0xd8 apa_event_poll_timeout+0x1b0 apa_process_event+0x164 apa_process_request+0x108 apa_event+0x4b0 apa_poll_timeout+0x1c invoke_callouts_for_self+0xc0 sw_service+0xb0 up_ext_interrupt+0x118 ivti_patch_to_nop2+0x0 ar_cmd_dispatch+0x58 ar_rput+0x84 csq_turnover_with_lock+0x84 putnext+0x258 ip_newroute+0x1f0 ip_wput+0x4c8 putnext+0xcc udp_wput+0x328 putnext+0xcc streams_putmsg+0x18c sosend+0x788 sendit+0x150 sendto+0x5c syscall+0x394 $syscallrtn+0x0 Resolution: in function apa_build_and_send_poll_packet add a NULL_pointer check and appropriate processing. 11.JAGad49525 When running DLPI scaffold on a token ring LM fail-over group, all tests related to multicast fails. For token ring, DLPI and token ring driver uses different primitive values to process multicast request, these primitives are not handled by current apa_ioctl. Resolution: Change code in hp_apa_ctrl.c to handle these DLPI primitives. 12.JAGad51186 When a LM failover group of token ring is created, the multicast address cannot be enabled on the ports because the length of multicast address is set to 24 bytes for token ring cards in DLPI, but APA only store a maximum 20 bytes. Resolution: For token ring, now APA will only check and compare the first 6 bytes of the multicast address passed to it by DLPI. 13.JAGad51231 the LB_PORT load balancing mode didn't work, this is caused by a missing "break" in LB_PORT, so it falls into LB_MAC load balancing mode. the second problem is that the algorithm used to determine the index into the link distribution table is faulty. Resolution: Correctly break in LB_PORT, and corrected the algorithm. 14.JAGad39352 When a bind request from DLPI is queued in APA, the mblk from DLPI is copied and saved locally. Because DLPI did not send the correct size of data, some information of the bind request is lost. Resolution: As a work-around, the size of data in the mblk is reset to the correct value before copying the mblk. The final fix should be made in DLPI. 15.JAGad39683 For PAgP and LACP mode, a PAgP/LACP protocol packet is traced after it is sent to a driver for output. The mblk might have been freed before it gets traced, the trace routine then will access a NULL page, which causes a panic. Stack trace: Interrupt Type 15 (Data page fault): panic+0x14 report_trap_or_int_and_panic+0x80 interrupt+0x1d4 $ihndlr_rtn+0x0 ktrc_write+0x618 pagp_send_hello+0x5a0 pagp_xmit_sm+0x13c4 pagp_processing_poll_timer+0xf0 pagp_ctrl+0x118 pagp_poll_timeout+0x24 invoke_callouts_for_self+0xc0 sw_service+0xb0 mp_ext_interrupt+0x144 ivti_patch_to_nop3+0x0 idle+0x49c swidle_exit+0x0 Resolution: The trace routine calls are moved before a packet is sent to a driver. 16.JAGad41160 When a bind request is made for a LAN Monitor fail-over group containing a Link Aggregation as the primary link, the request will be acknowleged OK immediately if the bind on the fail-over succeeds, while the actual binding on the primary link is queued and still waiting to be processed (due to the synchronized queue design ). If data is sent immediately after the bind request (e.g. linkloop command), it will be dropped. Resolution: When a linkagg is included in a fail-over group, the actual binding on it are processed right away rather than goes into the queue. 17.JAGad53023: in SAM-APA, Enter the Add or Delete Network Physical PORTS DIB: 1. Select and remove a port from the linkagg with the > arrow 2. Select a port in the list of physical ports that is in FEC_AUTO mode 3. Click ok on the message that appears saying Cannot add FEC_AUTO port to a MANUAL linkagg... from this point forward you can't exit this DIB with OK. The problem happens because SAM was treating the message that pops up on the screen as an error message. So SAM force the user to cancel out all the changes. Resolution: SAM does not consider the message as an error message and therefore allows the user to exit the screen by clicking OK. 18.JAGad53024: in SAM-APA, Select a port in FEC_AUTO mode does not always display an error message saying Cannont add FEC_AUTO port to a MANUAL linkagg... This problem happens when the Linkaggregate is in the "NOT ENABLED" state. SAM was displaying the error message only when the Linkaggregate is in the "UP" state. Resolution: SAM will now diaplay the error message even if the Link aggregate is in the "NOT_ENABLED" state. 19.JAGad52091: For non-ether port, currently the only valid mode is LAN_MONITOR. But lanadmin can still be used to set the mode to MANUAL. Resolution: before set the port's mode to MANUAL, check driver's type. 20.JAGad53058: Panic spinlock deadlock: too much time crash event was a panic panic+0x6c too_much_time+0x2e8 wait_for_lock+0x23c sl_retry+0x1c gelan_handle_events+0x528 gelan_slow_isr+0x4c gelan_isr+0x558 sapic_interrupt+0x2c mp_ext_interrupt+0x2ec ivti_patch_to_nop3+0x0 idle+0x1c0 swidle_exit+0x0 Resolution: APA code failed to release lock for gelan. This has been corrected. Enhancement: No (superseded patches contained enhancements) PHNE_26774: This patch make SAM's error message more user friendly. PHNE_24309: This patch delivers new functionality for allowing link-down interfaces to be added into MANUAL Linkagg. Add a new configurable APA_DEFAULT_PORT_MODE to hp_apaconf file. Load_Balance algorithm LB_IP is enhanced. SR: 8606278212 8606259359 8606251636 8606260570 8606251255 8606242401 8606244236 8606249804 8606251275 8606246890 8606244230 8606248616 8606248618 8606249810 8606220853 8606225291 8606227924 8606231180 8606232368 8606232369 8606232371 8606232548 8606232767 8606234547 8606234548 8606237102 8606237104 8606238619 8606238620 8606238622 8606238623 8606238624 8606238626 8606241616 8606243377 8606193988 8606186581 8606187793 8606187779 8606199543 8606182762 8606186563 8606157268 8606192949 8606189219 8606200706 8606197671 8606130159 8606197849 8606200243 8606204362 8606184778 8606187113 8606170073 8606170077 8606171642 8606175504 8606175580 8606177498 8606177503 8606177577 8606179541 8606180129 8606180304 8606181970 8606182015 8606170088 8606170419 8606171897 8606183812 8606183813 8606182876 8606183847 8606155960 8606217469 8606202940 8606233561 8606229445 8606214427 8606226413 8606211541 8606222838 8606223626 8606218777 8606207419 8606224881 8606215505 8606285130 8606291797 8606193365 8606263740 8606266048 8606291046 8606288133 8606238687 8606236794 8606247810 8606241860 8606254460 8606259724 8606265757 8606244665 8606287241 8606294183 8606231290 8606223610 8606279293 8606247098 8606225053 8606248564 8606263018 8606274458 8606232754 8606260745 Patch Files: HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP: HP-APA-KRN.APA-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_32,v=HP: HP-APA-KRN.APA-KRN,fr=B.11.11.07,fa=HP-UX_B.11.11_32,v=HP: /usr/conf/lib/libhp_apa.a /usr/conf/lib/libpagp.a /usr/conf/lib/liblacp.a /usr/conf/lib/hp_apa_dbg.o /usr/conf/lib/pagp_dbg.o /usr/conf/lib/lacp_dbg.o /usr/conf/master.d/hp_apa HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP: HP-APA-KRN.APA-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,v=HP: HP-APA-KRN.APA-KRN,fr=B.11.11.07,fa=HP-UX_B.11.11_64,v=HP: /usr/conf/lib/libhp_apa.a /usr/conf/lib/libpagp.a /usr/conf/lib/liblacp.a /usr/conf/lib/hp_apa_dbg.o /usr/conf/lib/pagp_dbg.o /usr/conf/lib/lacp_dbg.o /usr/conf/master.d/hp_apa HP-APA-RUN.APA-RUN,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-RUN.APA-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-RUN.APA-RUN,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64, v=HP: /usr/lib/lanadmin/libdshp_apa.sl /usr/lib/lanscan/libpehp_apa.sl /usr/lib/nls/msg/C/dshp_apa.cat /usr/lib/nls/msg/C/pehp_apa.cat /usr/lib/nls/msg/C/lanmon.cat /opt/networkdocs/hp_apa_relno.pdf /opt/networkdocs/hp_apa_install.pdf HP-APA-RUN.APA-INIT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-RUN.APA-INIT,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-RUN.APA-INIT,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64, v=HP: /usr/sbin/hp_apa_init /usr/sbin/hp_apaport_init /usr/sbin/hp_apa_util /usr/newconfig/etc/rc.config.d/hp_apaconf /usr/newconfig/etc/rc.config.d/hp_apaportconf /sbin/init.d/hpapa /sbin/init.d/hplm /sbin/rc2.d/S337hpapa /sbin/rc2.d/S343hplm HP-APA-FMT.APA-FORMAT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-FMT.APA-FORMAT,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-FMT.APA-FORMAT,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64, v=HP: /usr/lib/libfmthp_apa.sl /usr/lib/libfmthp_apaport.sl /usr/lib/libfmthp_apalacp.sl /usr/lib/nls/msg/C/fmthp_apa.cat /usr/lib/nls/msg/C/fmthp_apalacp.cat /usr/lib/nls/msg/C/fmthp_apaport.cat HP-APA-SAM.SAM-APA,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-SAM.SAM-APA,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64, v=HP: HP-APA-SAM.SAM-APA,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64, v=HP: /usr/sam/lib/C/apa.ui /usr/sam/lib/C/apa_defs.ui /usr/sam/lib/C/apa.cb /usr/sam/help/C/nnc/apa.sdl /usr/sam/help/C/nnc/hplogo.pm /usr/sam/help/C/nnc/noteicon.pm /usr/sam/help/C/nnc/warnicon.pm /usr/sam/help/C/nnc/cauticon.pm /usr/sam/help/C/graphics/nnc_apa.l.pm.Z /usr/sam/lib/apa/apa.tm /usr/sam/lib/apa/apa.da /usr/sam/lbin/apa_utils /usr/sam/lbin/apa_get_info /usr/sam/lib/nnc/apa.sl HP-APA-LM.APA-LM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP: HP-APA-LM.APA-LM,fr=B.11.11.04,fa=HP-UX_B.11.11_32/64,v=HP: HP-APA-LM.APA-LM,fr=B.11.11.07,fa=HP-UX_B.11.11_32/64,v=HP: /usr/sbin/lanmonconf /usr/sbin/lanapplyconf /usr/sbin/lanqueryconf /usr/sbin/lancheckconf /usr/sbin/landeleteconf /etc/lanmon/lanconfig.ascii.sample /usr/share/man/man1m.Z/lanqueryconf.1m /usr/share/man/man1m.Z/lanapplyconf.1m /usr/share/man/man1m.Z/lancheckconf.1m /usr/share/man/man1m.Z/landeleteconf.1m what(1) Output: HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP: /usr/conf/lib/libhp_apa.a: HP Auto-Port Aggregation (APA): hp_apa.c: PHNE_28778 B.11.11.11 Apr 1 2003 16:02:04 /usr/conf/lib/libpagp.a: HP Auto-Port Aggregation (APA): PAGP: PHNE_28778 B.1 1.11.11 Apr 1 2003 16:02:36 /usr/conf/lib/liblacp.a: HP Auto-Port Aggregation (APA): LACP: PHNE_28778 B.1 1.11.11 Apr 1 2003 16:03:08 /usr/conf/lib/hp_apa_dbg.o: None /usr/conf/lib/pagp_dbg.o: None /usr/conf/lib/lacp_dbg.o: None /usr/conf/master.d/hp_apa: None HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP: /usr/conf/lib/libhp_apa.a: HP Auto-Port Aggregation (APA): hp_apa.c: PHNE_28778 B.11.11.11 Apr 1 2003 16:04:53 /usr/conf/lib/libpagp.a: HP Auto-Port Aggregation (APA): PAGP: PHNE_28778 B.1 1.11.11 Apr 1 2003 16:05:25 /usr/conf/lib/liblacp.a: HP Auto-Port Aggregation (APA): LACP: PHNE_28778 B.1 1.11.11 Apr 1 2003 16:05:54 /usr/conf/lib/hp_apa_dbg.o: None /usr/conf/lib/pagp_dbg.o: None /usr/conf/lib/lacp_dbg.o: None /usr/conf/master.d/hp_apa: None HP-APA-RUN.APA-RUN,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: /usr/lib/lanadmin/libdshp_apa.sl: HP Auto-Port Aggregation (APA) LANADMIN: Date: Apr 1 2003 16:07:24 /usr/lib/lanscan/libpehp_apa.sl: HP Auto-Port Aggregation (APA) LANSCAN: Date: Apr 1 2003 16:07:32 /usr/lib/nls/msg/C/dshp_apa.cat: None /usr/lib/nls/msg/C/pehp_apa.cat: None /usr/lib/nls/msg/C/lanmon.cat: None /opt/networkdocs/hp_apa_install.pdf: None /opt/networkdocs/hp_apa_relno.pdf: None HP-APA-RUN.APA-INIT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: /usr/sbin/hp_apa_init: hp_apa_init $Revision: 1.6 $ $Date: 2002/04/09 16:3 9:31 $ /usr/sbin/hp_apaport_init: hp_apaport_init $Revision: 1.4 $ $Date: 2002/04/09 16:40:31 $ /usr/sbin/hp_apa_util: HP Auto-Port Aggregation (APA) hp_apa_util: Date: Ap r 1 2003 16:07:24 /usr/newconfig/etc/rc.config.d/hp_apaconf: hp_apaconf $Revision: 1.12 $ $Date: 2001/06/26 11:21 :20 $ /usr/newconfig/etc/rc.config.d/hp_apaportconf: hp_apaportconf $Revision: 1.8 $ $Date: 2002/04/09 17 :21:11 $ /sbin/init.d/hpapa: hp_apa $Revision: 1.9 $ $Date: 2001/06/26 11:22:11 $ /sbin/init.d/hplm: None /sbin/rc2.d/S337hpapa: hp_apa $Revision: 1.9 $ $Date: 2001/06/26 11:22:11 $ /sbin/rc2.d/S343hplm: None HP-APA-FMT.APA-FORMAT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: /usr/lib/libfmthp_apa.sl: HP Auto-Port Aggregation (APA) FORMAT (LINKAGG) Date : Apr 1 2003 16:07:39 /usr/lib/libfmthp_apalacp.sl: HP Auto-Port Aggregation (APA) FORMAT (LACP) Date: A pr 1 2003 16:07:40 /usr/lib/libfmthp_apaport.sl: HP Auto-Port Aggregation (APA) FORMAT (PORT) Date: A pr 1 2003 16:07:39 /usr/lib/nls/msg/C/fmthp_apa.cat: None /usr/lib/nls/msg/C/fmthp_apalacp.cat: None /usr/lib/nls/msg/C/fmthp_apaport.cat: None HP-APA-SAM.SAM-APA,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: /usr/sam/lib/C/apa.ui: None /usr/sam/lib/C/apa_defs.ui: None /usr/sam/lib/C/apa.cb: None /usr/sam/help/C/nnc/apa.sdl: None /usr/sam/help/C/nnc/cauticon.pm: None /usr/sam/help/C/nnc/hplogo.pm: None /usr/sam/help/C/nnc/noteicon.pm: None /usr/sam/help/C/nnc/warnicon.pm: None /usr/sam/help/C/graphics/nnc_apa.l.pm.Z: None /usr/sam/lib/apa/apa.tm: $Header: /samsrc/nnc/h/nnc_msgs.h 73.13 2000-09-06 0 3:42:18-06 samiso Exp $ /usr/sam/lib/apa/apa.da: None /usr/sam/lbin/apa_utils: None /usr/sam/lbin/apa_get_info: None /usr/sam/lib/nnc/apa.sl: SAM Version Built on date: 08/26/01 13:43:20 with build flags: - g -DDEBUG -DNLS -DIO_CONV -DV4FS Build environment HP-UX jolly B.11.11 U 9000/785 201 0798720 unlimited-user license HP-APA-LM.APA-LM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP: /usr/sbin/lanmonconf: HP Auto-Port Aggregation(LM) lanmonconf: Date: Jun 5 2003 16:29:20 /usr/sbin/lanapplyconf: HP Auto-Port Aggregation(LM) lanmonconf: Date: Jun 5 2003 16:29:20 /usr/sbin/lanqueryconf: HP Auto-Port Aggregation(LM) lanmonconf: Date: Jun 5 2003 16:29:20 /usr/sbin/lancheckconf: HP Auto-Port Aggregation(LM) lanmonconf: Date: Jun 5 2003 16:29:20 /usr/sbin/landeleteconf: HP Auto-Port Aggregation(LM) lanmonconf: Date: Jun 5 2003 16:29:20 /etc/lanmon/lanconfig.ascii.sample: None /usr/share/man/man1m.Z/lanapplyconf.1m: None /usr/share/man/man1m.Z/lancheckconf.1m: None /usr/share/man/man1m.Z/landeleteconf.1m: None /usr/share/man/man1m.Z/lanqueryconf.1m: None cksum(1) Output: HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_32,v=HP: 3006003870 136084 /usr/conf/lib/libhp_apa.a 3490487097 59960 /usr/conf/lib/libpagp.a 812249748 63234 /usr/conf/lib/liblacp.a 758513021 225896 /usr/conf/lib/hp_apa_dbg.o 4261038873 162888 /usr/conf/lib/pagp_dbg.o 3166969320 187512 /usr/conf/lib/lacp_dbg.o 2689439581 3829 /usr/conf/master.d/hp_apa HP-APA-KRN.APA-KRN,fr=B.11.11.00,fa=HP-UX_B.11.11_64,v=HP: 3054670980 252290 /usr/conf/lib/libhp_apa.a 1693045227 119676 /usr/conf/lib/libpagp.a 1903945709 128678 /usr/conf/lib/liblacp.a 3029646086 286448 /usr/conf/lib/hp_apa_dbg.o 467718674 201120 /usr/conf/lib/pagp_dbg.o 568279660 232600 /usr/conf/lib/lacp_dbg.o 2689439581 3829 /usr/conf/master.d/hp_apa HP-APA-RUN.APA-RUN,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: 736786201 65536 /usr/lib/lanadmin/libdshp_apa.sl 3916324377 16384 /usr/lib/lanscan/libpehp_apa.sl 3486429944 20135 /usr/lib/nls/msg/C/dshp_apa.cat 3177170838 581 /usr/lib/nls/msg/C/pehp_apa.cat 1643235463 7621 /usr/lib/nls/msg/C/lanmon.cat 1327875053 20192 /opt/networkdocs/hp_apa_install.pdf 2780012879 79216 /opt/networkdocs/hp_apa_relno.pdf HP-APA-RUN.APA-INIT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: 1129149202 9630 /usr/sbin/hp_apa_init 2520989244 10139 /usr/sbin/hp_apaport_init 1432402441 24576 /usr/sbin/hp_apa_util 3466105271 5531 /usr/newconfig/etc/rc.config.d/hp_apaconf 2467659153 3454 /usr/newconfig/etc/rc.config.d/ hp_apaportconf 2235684658 14791 /sbin/init.d/hpapa 1584107462 2831 /sbin/init.d/hplm 2235684658 14791 /sbin/rc2.d/S337hpapa 1584107462 2831 /sbin/rc2.d/S343hplm HP-APA-FMT.APA-FORMAT,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: 3104156802 12288 /usr/lib/libfmthp_apa.sl 3027729796 12288 /usr/lib/libfmthp_apalacp.sl 4005635768 12288 /usr/lib/libfmthp_apaport.sl 3922540052 11772 /usr/lib/nls/msg/C/fmthp_apa.cat 510379485 1712 /usr/lib/nls/msg/C/fmthp_apalacp.cat 1389899281 2217 /usr/lib/nls/msg/C/fmthp_apaport.cat HP-APA-SAM.SAM-APA,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64, v=HP: 4217341160 13468 /usr/sam/lib/C/apa.ui 1334725058 6546 /usr/sam/lib/C/apa_defs.ui 2159485453 219 /usr/sam/lib/C/apa.cb 3822906708 37774 /usr/sam/help/C/nnc/apa.sdl 269683105 1237 /usr/sam/help/C/nnc/cauticon.pm 3852391127 5892 /usr/sam/help/C/nnc/hplogo.pm 1672832614 1381 /usr/sam/help/C/nnc/noteicon.pm 2686678813 1341 /usr/sam/help/C/nnc/warnicon.pm 3094046151 5089 /usr/sam/help/C/graphics/nnc_apa.l.pm.Z 1878452335 16168 /usr/sam/lib/apa/apa.tm 288078266 2516 /usr/sam/lib/apa/apa.da 1737813034 3177 /usr/sam/lbin/apa_utils 3820886128 45056 /usr/sam/lbin/apa_get_info 516533158 252776 /usr/sam/lib/nnc/apa.sl HP-APA-LM.APA-LM,fr=B.11.11.00,fa=HP-UX_B.11.11_32/64,v=HP: 190887631 57344 /usr/sbin/lanmonconf 190887631 57344 /usr/sbin/lanapplyconf 190887631 57344 /usr/sbin/lancheckconf 190887631 57344 /usr/sbin/landeleteconf 190887631 57344 /usr/sbin/lanqueryconf 2629837085 2209 /etc/lanmon/lanconfig.ascii.sample 3134785037 845 /usr/share/man/man1m.Z/lanapplyconf.1m 2376308309 895 /usr/share/man/man1m.Z/lancheckconf.1m 1740003926 765 /usr/share/man/man1m.Z/landeleteconf.1m 3967761322 3568 /usr/share/man/man1m.Z/lanqueryconf.1m Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: To fix JAGae42271, DLPI GR patch PHNE_28923 (or its superseding patch) and XPORT GR patch PHNE_28089 (or its superseding patch) need to be installed. To fix JAGad98498, DLPI's 11.11 patch PHNE_25388 or its superseding patch need to be installed. Supersedes: PHNE_23160 PHNE_24072 PHNE_24309 PHNE_25622 PHNE_25456 PHNE_25833 PHNE_26774 PHNE_27198 PHNE_27951 Equivalent Patches: None Patch Package Size: 1100 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_28778 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHNE_28778.depot By default swinstall will archive the original software in /var/adm/sw/save/PHNE_28778. 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_28778.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHNE_28778.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_28778.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHNE_28778 1. To fix JAGae17700, 3 new configurables LM_RAPID_ARP, LM_RAPID_ARP_INTERVAL, LM_RAPID_ARP_COUNT are introduced for LAN_MONITOR mode. (See lanqueryconf manpage and /etc/lanmon/lanconfig.ascii.sample file for detail.) These configurables are supported only AFTER APA patch PHNE_26774(version B.11.11.08). When rolling back to those patches not supporting RAPID_ARP, SD command swremove will automatically comment out these 3 configurables from /etc/lanmon/lanconfig.ascii. If user uses config file other than the default config file, user should comment out these 3 configurables explicitly. 2. All special instructions required for PHNE_27198 (see below) are applicable to PHNE_28778. PHNE_27951 1. All special instructions required for PHNE_27198 (see below) are applicable to PHNE_27951. PHNE_27198 1. All special instructions required for PHNE_26774 (see below) are applicable to PHNE_27198. 2. 3 new RAPID_ARP configurables LM_RAPID_ARP, LM_RAPID_ARP_INTERVAL, and LM_RAPID_ARP_COUNT are added to /etc/lanmon/lanconfig.ascii and are delivered as part of this patch. The new version is delivered as /etc/lanmon/lanconfig.ascii.sample file. If you have edited /etc/lanmon/lanconfig.ascii file, you can merge these files, or if you will use lanqueryconf, it will create an ascii file with these new fields. PHNE_26774 1. All special instructions required for PHNE_25833 (see below) are applicable to PHNE_26774. PHNE_25833 1. All special instructions required for PHNE_24309 (see below) are applicable to PHNE_25833. PHNE_24309 A new parameter,HP_APA_DEFAULT_PORT_MODE is added to the file, /etc/rc.config.d/hp_apaconf and is delivered as part of this patch.This new version is delivered as /usr/newconfig/etc/rc.config.d/hp_apaconf file. If you have edited /etc/rc.config.d/hp_apaconf file, you need to merge these files. A new version of file /etc/rc.config.d/hp_apaportconf is delivered as part of this patch,as /usr/newconfig/etc/rc.config.d/hp_apaportconf file. If you have edited /etc/rc.config.d/hp_apaportconf file, you may want to merge these files.