Flashes (Alerts)
Abstract
Adding a new 2145-SV3 or 2147-SV3 node to a existing SVC cluster running V8.5 may result in all nodes rebooting simultaneously, causing a loss of access to hosts.
Content
When a new SV3 node (2145-SV3 or 2147-SV3) is added to a cluster running V8.5 this will cause a 3015 error to be logged, indicating that the pre-installed PSU firmware does not match the rest of the cluster. This is because newly-shipped SV3 nodes run V8.6 software.
Attempting to mark this 3015 error as fixed will trigger all cluster nodes to reboot simultaneously, causing a temporary loss of I/O access to all hosts.
How to add a SV3 node to a cluster running V8.5
To add a SV3 node to a cluster running V8.5, first upgrade the cluster code to V8.6. If that is not possible due to hardware compatibility then upgrade to a V8.5 level containing the fix for SVAPAR-112707 once this is available.
What to do if a SV3 node has already been added to a cluster running V8.5 and a 3015 error is present
It is critical that no action is taken to repair the 3015 error (including marking the error as fixed or servicing the PSU) as this will trigger a reboot of all nodes. In this scenario contact IBM Support for assistance, referencing this My Notification alert for assistance to safely resolve the 3015 error.
[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STPVGU","label":"SAN Volume Controller"},"ARM Category":[{"code":"a8m0z000000bqPvAAI","label":"Hardware"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Type":"MASTER"}]
Was this topic helpful?
Document Information
Modified date:
09 January 2024
UID
ibm17097705