Workflow
Suggest changes
PDFs
Upgrading controller hardware by moving volumes is a nondisruptive procedure. Before starting your upgrade, review the general upgrade scenarios and upgrade considerations:
To upgrade by moving volumes, you prepare the original nodes and join the new nodes to the cluster. You move volumes to the new nodes, configure LIFs, and unjoin the original nodes from the cluster.
You perform a few preparation steps before upgrading controller hardware by moving volumes.
You install the new nodes and join them to the cluster so that you can move volumes from the original nodes.
Before moving iSCSI SAN volumes to new nodes, you create new iSCSI connections and rescan the iSCSI paths to the new nodes.
You create at least one aggregate on each of the new nodes to store the volumes you want to move from the original nodes. You must identify an aggregate for each volume and move each volume individually
After you have moved the volumes from the original nodes, you migrate the non-SAN data LIFs and cluster-management LIFs from the original nodes to the new nodes.
Depending on your cluster contents and cluster environment, you move, delete, or create SAN LIFs, or re-create deleted SAN LIFs.
After the volumes have been moved to the new nodes, you unjoin the original nodes from the cluster. When you unjoin a node, the node's configuration is erased and all disks are initialized.
To complete the procedure of upgrading by moving volumes, you configure the Service Processor (SP), install new licenses, and set up AutoSupport. You might also need to set up Storage or Volume Encryption and configure the FC or NCA ports.