HP 1606 HP StorageWorks Fabric OS 6.3.2b Release Notes (5697-0777, November 20 - Page 44

With an invalid http configuration on 4Gb switches, after step upgrading from Fabric OS 5.3.1x to Fabric OS 6.2.x, switch (or standby CP on 4/256 director) ends up in panic loop, and may remain in perpetual reboot state. This occurs when there is an inconsistency between SSL certificate and http configuration. Workaround prior to upgrade: Manually ensure that http.enabled matches with SSL certificate by configshow http.enabled as admin user. If inconsistent with SSL certificate requirement, execute /fabos/ libexec/webdconfigure as root to set "HPPT Enable" to yes. Or schedule a window, disable switch, and configdownload a file with http.ebale:1 [end] when switch is at Fabric OS 5.3.x or 6.1.x to correct the configuration. If switch is already stuck in a reboot loop, login as root via serial console, copy and paste the following command string into the console as one line before the next reboot:sed's/ http.enabled:0/ http.enabled:1/g" tmp;cp tmp/etc/fabos/ fabox.0.conf;cp tmp/mnt/ etc/fabos/fabos.0.conf;rm tmp Fixed in Fabric OS 6.3.2. CALD terminated and logical switch delete failed with reason Could not get port details from EM when attempting to delete two of six logical switches in a DC SAN Backbone director from DCFM. Fixed in Fabric OS 6.3.2. In AG mode, N_Port failover results in F_Ports with attached hosts getting stuck as G_Ports. Occurs when there is a change in the base address for the N_Port due to failover, or when there is no wwn-area mapping for few devices and due to the login sequence of these devices. The PIDs assigned conflicted with the already allocated PID to another device, resulting in the F_Ports getting stuck as G_Ports. Fixed in Fabric OS 6.3.2. Large core file fills up the compact flash and causes file system corruption. If Fabric OS startup files are corrupted, the switch ends up in a reboot loop. Fixed in Fabric OS 6.3.2. QoS circuits running over a 1 Gb/10 Gb bandwidth circuit on 1606 Extension switch or Extension blade will have incorrect QoS distributions with large I/O. Occurs when running all three QoW priorities on a circuit that is a multiple of 1 Gb/s and effects the distribution of traffic, which could lead to performance issue. Fixed in Fabric OS 6.3.2. Webd was seen to terminate from time to time, at the same time as HA status temporarily went to non-redundant, triggering a Call Home event. Webd was killed by a watchdog as it was waiting for a reply from a busy httpd and did not have a timeout mechanism. No other functional impact observed other than Call Home event. Fixed in Fabric OS 6.3.2. 44