Loading...
Loading...
An incorrect Fibre Channel Topology Setting May Cause the HPE StoreOnce Appliance on the GUI and console to become unresponsive, or access to the HPE StoreOnce System may be lost.This issue may be caused by an incorrect Fibre Channel Topology setting. The ports are improperly configured for “N_Port” topology without a switch. When connected directly to the host, it should be in "Loop" mode.The "rcu_sched detected stalls on CPUs/tasks" messages may appear on the console such as the example below:This issue may occur with any version of HPE StoreOnce software.
The following HPE StoreOnce systems for Gen4 and Gen4 Plus are affected by this issue:HPE StoreOnce 3620 24TB System (BB954A)HPE StoreOnce 3640 48TB System (BB955A)HPE StoreOnce 5200 Base System (BB956A)HPE StoreOnce 5250 Base System (BB958A)HPE StoreOnce 5650 Base System (BB959A)HPE StoreOnce 3660 80TB Base System (R6U02A)>HPE StoreOnce 5260 Base System (R6U04A)HPE StoreOnce 5660 Base System (R6U04A)
Refer to the Workaround below as there are currently no plans to resolve this issue.As a workaround, complete the following steps to resolve this issue:Stop the StoreOnce system, which may need to be done through iLO as the StoreOnce GUI will not work.Either disconnect the fibre channel cable from StoreOnce or disable the port on the host side. (For example, use Windows Device Manager to disable the fibre channel device). This will allow StoreOnce to boot normally and allows the access to the GUI to change the settings.Start the StoreOnce system.Open the StoreOnce system GUI and go toSettings>Hardware>Fibre Channel.Select the affected port and click on theEditicon. Change port “Topology” to the correct setting (“Loop” mode).Reconnect the fibre channel cable or enable the fibre channel device on the host side.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.