Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
HPE SN3600B FC Switches that have Fabric OS (FOS) v9.1.0x installed and are then later upgraded to any version of FOS v9.1.1x or to FOS v9.2.0 could be at risk to fail start up if they lose power or are power cycled. Once the SN3600B fails to start, it must be replaced. Starting with v9.1.1, during post-installation of G6_ENTRY code, symbolic links of Linux image files are used on the SN3600B platform. The name of one of the symbolic links created has the same name as the Linux security boot image rpm file created during FOS v9.1.0x. After upgrading from v9.1.0x to v9.1.1x/v9.2.0, the previously installed boot file is deleted as the new symbolic link file is created; however, since the symbolic link has the same name, it is also deleted by mistake. This incident is not detected due to an issue with the u-boot code. The symbolic link file is recreated on any future upgrade, but while the SN3600B remains at a FOS version with the file deleted, it will be unable to boot following a power failure or power cycle. HA events and reboots are not affected by this missing file. Only SN3600B switches are at risk. To encounter this issue, the SN3600B switch must have at one time been loaded with a version of FOS v9.1.0x to be at risk. The same SN3600B switch must then have been upgraded to any version of FOS v9.1.1x (v9.1.1_01, v9.1.1a, v9.1.1b) or to FOS v9.2.0 and not upgraded again after that, while remaining on this new code level. Finally, the switch must be powered off while still at this firmware version. The following upgrade scenarios would leave SN3600B at risk of encountering this condition: FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.1.1_01 and then powered off while at this code level FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.1.1a and then powered off while at this code level FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.1.1b and then powered off while at this code level FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.2.0 and then powered off while at this code level Switches that are upgraded from v9.1.1x to a later FOS version or that are upgraded directly from v9.0.1x to v9.1.1x are not at risk as shown in the following upgrade path examples: FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.1.1_01 to v9.1.1b Not at risk to power off issue FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.1.1a to v9.1.1b Not at risk to power off issue FOS v9.0.1x to v9.1.0 or v9.1.0b to v9.1.1b to v9.2.0 Not at risk to power off issue FOS v9.0.1x to v9.1.1_01 Not at risk to power off issue FOS v9.0.1x to v9.1.1a Not at risk to power off issue FOS v9.0.1x to v9.1.1b Not at risk to power off issue Switches that were shipped originally loaded with v9.1.1a or v9.1.1b, and never downgraded to a v9.1.0x FOS version, are also not at risk to encounter this issue. The condition is only encountered following a power cycle: Switch reboot does not cause the condition HA reboot does not cause the condition SN3600B switches with Lifetime Warranty (LW) are not at risk, as only the v9.0.1e1_LW and v9.1.1b_LW FOS versions were ever posted for download. FOS v9.1.0b_LW was never posted for download onto a SN3600B LW switch, and SN3600B LW switches never having been loaded with a FOS v9.1.0x FOS version will not be at risk. The SN3600B switch will fail to start after being powered back on with the following reason, “Error: can’t get kernel image!” An example of the failure message from the serial console is shown here: Secure Boot Mode Enabled, System in Trusted State Hit ESC to stop autoboot: 0 ** File not found /boot/signed_bzImage.itb ** 2805 bytes read in 409 ms (5.9 KiB/s) ## Executing script at 00200000 sha1,rsa2048:dev+ sha1+ WARNING: adjusting available memory to 30000000 Wrong Image Format for bootm command ERROR: can't get kernel image! Once this condition is encountered, there is no way to recover the switch. The SN3600B will need to be returned and replaced. Contact HPE Support using the instructions at the HPE Support Center website to open a support case.”
The HPE B-series SN3600B Fibre Channel Switch is affected by this issue.
A software solution provided in FOS v9.1.1c (HPE release target July 14, 2023), v9.2.0a (HPE release target August 2023) and later versions corrects this condition. SN3600B switches that were previously installed with v9.1.0x FOS versions may safely be power cycled after upgrading to FOS v9.1.1c or FOS v9.2.0a or later. As a workaround, when running a SN3600B switch on any v9.0.1x version of FOS: Do not upgrade an SN3600B through any of the v9.1.0x FOS versions (v9.1.0, v9.1.0b). Instead, upgrade directly from v9.0.1x to one of the v9.1.1x versions of FOS. When running an SN3600B switch on any v9.1.0x versions of FOS: Remain on v9.1.0x and only upgrade to v9.1.1c or v9.2.0a or later versions of FOS. When running an SN3600B switch on FOS v9.1.1x or FOS v9.2.0 that had been previously loaded with a version of FOS v9.1.0x prior to this single-time upgrade: Upgrade to a later version of FOS; the v9.1.0x file has already been deleted, and the symbolic link file will be recreated on this second upgrade. Or optionally perform a firmwarecleaninstall to the same version of v9.1.1x or v9.2.0 FOS that is currently running. This will also restore the missing file and avoid any issues due to a power event. The switch configuration file should be saved prior to the firmware clean install as the switch will be reset to factory defaults. Refer to documentation manuals for the steps and procedures required to perform a firmware clean install. Finally, upgrade to v9.1.1c or v9.2.0a or later version of FOS with the resolution. Brocade branded user and reference guides for FOS, SANnav and switch hardware is available on the Broadcom external website: Go to the Broadcom website. Select your Product. Once you reach the Product Page, select Documentation. NOTE : For legacy Products not listed, enter the requested FOS version in the Search bar. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Support Alerts. Sign up for Support Alerts at the following URL: HPE Email Preference Center