Unable to bring cluster into quorum during switchless A300/FAS8200 to A400/FAS8300 head upgrade
Applies to
- FAS8200
- FAS8300
- AFF A300
- AFF A400
- Head upgrade for 2-node switchless cluster from FAS8200 to FAS8300 or AFF A300 to AFF A400 using nondisruptive aggregate relocation (ARL) procedure or moving storage disruptive procedure
Issue
- Unable to bring cluster into quorum after first AFF A400/FAS 8300 is installed and connected to old AFF A300/FAS 8200 node (using ARL procedure) or after both new nodes are in place (using disruptive procedure when moving storage)
- For ARL procedure, this corresponds to step 3 when joining quorum
- For moving storage/disruptive procedure, this corresponds to final step after new nodes are installed
- Cluster LIFs remain offline
- Node reports that cluster applications are not coming up:
Cluster::> storage failover show
Takeover
Node Partner Possible State Description
-------------- -------------- -------- -------------------------------------
node-01 node-02 true Connected to node-02
node-02 node-01 true Connected to node-01.
Waiting for cluster applications to
come online on the local node.
Offline applications: vldb, vifmgr,
bcomd, crs, scsi blade, clam.
2 entries were displayed. - Attempting to update Cluster broadcast domain to the new ports results in error:
Error: Cannot run this command because the system is not fully initialized. Wait a few minutes, and then try the command again.