Workflow
Suggest changes
PDFs
Upgrading controller hardware by moving storage is a disruptive procedure. Before starting your upgrade, review the general upgrade scenarios and upgrade considerations:
To upgrade by moving storage, you prepare the original nodes and set up the new nodes. Some platform models support transferring internal storage to the new nodes. You reassign disks and restore root volume configuration to the new nodes and configure network ports.
|
In the steps for upgrading controller hardware by moving storage, the original nodes are called node1 and node2, and the new nodes are called node3 and node4. During the described procedure, node1 is replaced by node3, and node2 is replaced by node4.
The terms node1, node2, node3, and node4 are used only to distinguish between the original and new nodes. When following the procedure, you must substitute these with the real names of your original and new nodes. However, in reality, the names of the nodes do not change: node3 has the name node1, and node4 has the name node2 after the controller hardware is upgraded. |
Before upgrading by moving storage, you gather license information from the original nodes, plan network configuration, record the system IDs, and prepare the files needed for netboot.
When shutting down and removing the original nodes you send an AutoSupport message about the upgrade, destroy the mailboxes, power down the nodes, and remove the chassis.
If the new nodes have internal disks or add-on shelves attached to the system, these can interfere with the controller upgrade. You should remove ownership of any new disks that came with node3/node4.
To confirm that configuration information on the boot media does not interfere with the controller upgrade, you reset the configurations of node3 and node4 to the default configuration settings.
When you upgrade by moving storage, you begin by installing the node3 and node4 and attaching power, console, and network connections to the new nodes.
During the process of upgrading by moving storage, you power on node3 and node4, boot the software image, and configure the nodes. Physical port layout between original and new nodes can be different. Mapping of ports between original and replacement nodes should be done to identify proper layout of ports and connections.
Optionally, if your original node is one of the supported models, you have the option to move its internal SATA drives, SSDs, or SAS drives to a drive shelf that is attached to the new nodes during the process of upgrading by moving storage. You can also convert the system to a drive shelf and attach it to the new nodes.
You reassign the disks that belonged to node1 and node2 to node3 and node4 respectively.
You restore configuration information from the root volume to the boot devices.
Complete the upgrade in ONTAP 9.8 or later, or ONTAP 9.7 or earlier.
-
Upgrade AFF A250 to AFF A400 by converting to a drive shelf (a nondisruptive procedure).