Flashes (Alerts)
Abstract
SAN Volume Controller or Storwize V7000 systems running V6.3, and Storwize V7000 Unified systems running 1.3 may experience Cluster Error 1630 when restarting a node or a node canister, including during software upgrades.
Content
There is a timing window which exists during a node (or node canister) restart where some of the fibre channel logins between the node (or node canister) and the backend storage system may not be configured correctly, and therefore these ports are not available for I/O. When this is detected, the software will log a Cluster Error 1630.
This problem should not cause any loss of access from host systems, however it will cause the system to report the XIV Storage System as degraded.
This issue can only be encountered during a node restart. Discovery of fibre channel logins when the node or node canister is online in the system will not be affected by this issue.
SAN Volume Controller and Storwize V7000 systems running V6.2 and earlier are not affected by this issue.
Workaround
If this issue is encountered, customers should disable and re-enable the XIV ports one at a time, to restart the discovery process, leaving at least 60 seconds between each port. Wherever possible, perform this action plan on the least busy XIV port first, and the busiest XIV port last. The fix procedure for the 1630 error should then be run to clear any remaining 1630 errors in the event log
Solution
This issue was addressed by APAR IC81571 in the V6.3.0.2 PTF release of the SAN Volume Controller and Storwize V7000 software, and will be addressed in a future release of the Storwize V7000 Unified software.
Was this topic helpful?
Document Information
Modified date:
28 March 2023
UID
ssg1S1004018