Loading...
Loading...
Affected code versions: FOS 9 FOS 10 In the errdump/Raslog output an SLNK-1005 message is observed with a reason code " Server returned nothing (no headers, no data ": [SLNK-1005], Supportlink login failed due to Server returned nothing (no headers, no data) (reason code: 52 ). If this message is encountered, the switch may be exposed and subsequent symptoms may be observed as the following: Support Link collections stop Loss of WebTools SANnav loses connectivity REST API calls not completing Kernel panic that results in unplanned reboot and data interruption on a fixed port switch Kernel panic that results in an unplanned HA failover on a director class switch Note: If a customer has recently installed and configured SANHealth v5.x and had "Leave Support Link Active" set to true in the Discovery Settings, this will enable Support Link on the switch. Before installing SANHealth 5.x, please upgrade to the versions listed in the below 'Resolution'. Otherwise the switch may encounter the panic.
A corrupted entry in the log file triggered by the failed upload with reason code 52 which can also lead to a kernel panic with the " SWD: SWD:swd_scan_timer:weblinker(3338) failed to refresh " signature in the panic core files. [USWD-1001], 2353, FFDC | CHASSIS, CRITICAL, DS_7710B, A system component failed to refresh. [RAS-1001], 2354, CHASSIS, INFO, DS_7710B, First failure data capture (FFDC) event occurred. [HAM-1004], 2355, CHASSIS, INFO, DS_7710B, Processor rebooted - Software Fault:Kernel Panic. Core files SWD: SWD:swd_scan_timer:weblinker(3338) failed to refresh (477345894 pid = 3338, vipd = 00000000dbfa34d4 pid_task 0000000028a513e0 2026/09/15-21:53:31 (+03), [USWD-1001], 2353, FFDC | CHASSIS, CRITICAL, DS_7710B, A system component failed to refresh. 2026/09/15-21:53:31 (+03), [RAS-1001], 2354, CHASSIS, INFO, DS_7710B, First failure data capture (FFDC) event occurred. The kernel panic occurs because the weblinker process experiences a heap memory overrun while processing the BSL supportlink collection. Specifically, supportlink collect will have this issue if /var/log/slhistory.txt contains an error message string in an incorrect format. The problem stems from an error being added to a log file. The log file holds 20 entries and to hit the panic the log file has to be full and contain this error.
Disable support link with the ' supportlink --disable ' command. To clean up the slhistory file, open a case with Brocade and they will provide a CVR patch. It runs the same way as a firmwaredownload but does not change any code. The patch is also designed to hareboot/hafailover if the log file has more than 18 entries. Otherwise, the cleanup is sufficient. Applying the patch when the SLNK error is observed will prevent the panic. Applying the patch POST panic will correct the issue and restore https functionality. These patches are to be installed via the firmwaredownload procedure (CLI or SANnav). The patch is part of the pre-install script. Details on patch: No Fabric OS code is modified/upgraded in this process The patch is designed to run like it is upgrading the FOS software The patch will only perform the cleanup that was previously performed in a service shell session. The patch may perform an hareboot or hafailover depending if the files were impacted. Note: It is OK to see "Firmwaredownload failed" message as there is no install taking place. Note: FOS v8.x is not exposed to the issue. Here are the two possible outputs from running the patch. Example when no files were impacted Checking system settings for firmwaredownload... The following item(s) need to be addressed before downloading the specified firmware: Emptying /var/log/slhistory.txt Now... /var/log/slhistory.txt successfully cleared Cleanup completed, no further action is needed. Ignore any Firmwaredownload failed message. Firmwaredownload failed. Example when files were impacted (hareboot or hafailover performed) Checking system settings for firmwaredownload... The following item(s) need to be addressed before downloading the specified firmware: Emptying /var/log/slhistory.txt Now... /var/log/slhistory.txt successfully cleared Done with cleanup. System is going for hareboot/hafailover...... Firmwaredownload failed. CID-TAC-G620-10-10:FID128:maintenance-service> Broadcast message from root@CID-TAC-G620-10-10 (Tue Sep 22 15:59:57 2026): The system is going down for reboot NOW! Connection to ##.##.##.## closed by remote host. Connection to ##.##.##.## closed. Note: SLNK message shows the bad entry. The panic only hits if the log has that entry AND is full. If the log is empty with only that entry in it, it won't panic. If 19 other entries roll in later, it will then panic. Applying the patch when the SLNK error is observed will prevent the panic. BSL issue resolved in FOS v9.2.2d2 and v10.0.1a. FOS v9.2.2d2 Release date: 11/2/2026 FOS v10.0.1a Release date: 11/16/2026
Click on a version to see all relevant bugs