Preparing for the upgrade

Before upgrading to an HA pair, you must verify that your system meets all requirements and that you have all of the necessary information.

Steps

  1. Verify that your system has enough available disks or partitions for the new controller module.
    You need to identify unassigned disks or spare disks with available partitions that you can assign to the new controller module.

    Physical Storage Management Guide

    ONTAP 9 Disks and Aggregates Power Guide

    • If your system does not use root-data partitioning, check disk ownership: storage disk show -ownership

      Two parity disks and one data disk, plus one spare, are required for root aggregate creation.

      Note: You must set the auto_assign option to off on the existing controller module before adding any new disks.
    • If your system uses root-data partitioning, determine the system spare disks and available partition space:
      1. Identify the unassigned disks: storage disk show
        clust01::> storage disk show
        
               Usable              Disk    Container   Container
        Disk   Size     Shelf Bay  Type    Type        Name      Owner
        ------ -------- ----- --- ------- ----------- --------- --------
        1.0.0        -    0   0    SAS     unassigned  -         -
        1.0.1  408.2GB    0   1    SAS     shared      -
        1.0.2  408.2GB    0   2    SAS     shared      -         clust01-01
        1.0.3  408.2GB    0   3    SAS     shared      -         clust01-01
        1.0.4  408.2GB    0   4    SAS     shared      -         clust01-01
        1.0.5  408.2GB    0   5    SAS     shared      -         clust01-01
        1.0.6  408.2GB    0   6    SAS     shared      -         clust01-01
        1.0.7  408.2GB    0   7    SAS     shared      -         clust01-01
        .
        .
        .
        .
        
      2. Identify the disks with usable root and data space: storage aggregate show-spare-disks

        You should look for usable space in the Local Data Usable and Local Root Usable columns for available partition space.

        clust01::> storage aggregate show-spare-disks
        .
        .
        .
        Original Owner: existing_ctlr
        Pool0
          Partitioned Spares
        
                                                  Local   Local 
                                                  Data    Root     Physical
        Disk    Type     RPM    Checksum          Usable  Usable   Size     Status
        -----   -----    -----   ---------        ------ --------  ------   ------- 
        2.3.9    BSAS     7200    advanced_zoned  0B      73.89GB  931.5GB  zeroed
        3.0.6    BSAS     7200    block           0B      0B       828.0GB  offline
        3.5.1    BSAS     7200    block           354.3GB 413.8GB  828.0GB  zeroed
        .
        .
        .
        .
        
        
      • If the system has 12 internal disks, five partitions are required for root aggregate creation and a sixth partition is required as a spare.
      • If the system has 24 internal disks, 10 partitions are required for root aggregate creation and two disks are required as spares.
      • If the system is an All Flash FAS (AFF) system, 22 partitions are required for the root aggregate creation and two disks are required for spares.
  2. Based on the results of the previous step, perform either of the following:
    If the result showed... Then...
    Enough spare disks available for the new controller module Go to the next step.
    Not enough spares for the new controller module on a system without root-data partitioning Complete the following substeps:
    1. Determine where the aggregates for the existing node are located: storage aggregate show
      Note: If you do not have enough free disks for your system, you need to add more storage. Contact technical support for more information.
    2. If disk ownership automatic assignment is on, turn it off: storage disk option modify -node node_name -autoassign off
    3. Remove ownership on disks that do not have aggregates on them: storage disk removeowner disk_name
    4. Repeat the previous step for as many disks as you need for the new node.
    Not enough spares for the new controller module on a system with root-data partitioning Perform either of the following steps:
    • Add more storage to the system.
    • Identify disk partitions that are not part of existing aggregates, so that you can use them when assigning disks.
  3. Verify that you have cables ready for the following connections:
    • Cluster connections

      If you are creating a two-node switchless cluster, you require two cables to connect the controller modules. Otherwise, you require a minimum of four cables, two for each controller module connection to the cluster-network switch. Other systems (like the 80xx series) have defaults of either four or six cluster connections.

    • HA interconnect connections, if the system is in a dual-chassis HA pair
  4. Verify that you have a serial port console available for the controller modules.
  5. Verify that your environment meets the site and system requirements.
  6. Gather all of the IP addresses and other network parameters for the new controller module.