Reassigning disks to the new nodes

You must reassign the disks that belonged to the original nodes to the new nodes.

About this task

You perform the steps in this section on both new nodes, completing each step on one node and then the other node before going on to the next step.


  1. From the new node's boot environment prompt (LOADER prompt), switch to Maintenance mode: boot_ontap maint
  2. If the new node has a root aggregate:
    1. Check the root aggregate of the node: aggr status
    2. Take the root aggregate of the new node offline: aggr offline aggr0
    3. Destroy the root aggregate: aggr destroy aggr0
  3. Display the new node's system ID: disk show -v
    *> disk show -v
    Local System ID: 101268854
    You should record the new node's system ID for later reference.
  4. Reassign the node's spare disks, disks belonging to the root aggregate, and any SFO aggregates: disk reassign -s original_sysid -d new_sysid -p partner_sysID
    The original_sysid value is what you recorded in Step 14, in the Preparing for an upgrade when moving storage topic.
    You specify -p partner_sysID when shared disks are present.
    Note: For disk reassignment on the first node, the partner_sysID value used is the original partner_sysID. However, disk reassignment on the second node uses the new partner node’s partner_sysID.
    The system displays a message similar to the following:
    Partner node must not be in Takeover mode during disk reassignment from maintenance mode.
    Serious problems could result!!
    Do not proceed with reassignment if the partner is in takeover mode. Abort reassignment (y/n)?n
    After the node becomes operational, you must perform a takeover and giveback of the HA partner node to ensure disk reassignment is successful.
    Do you want to continue (y/n)?y
  5. Enter y to continue.
    The system displays a message similar to the following:
    The system displays the following message:
    Disk ownership will be updated on all disks previously belonging to Filer with sysid
    Do you want to continue (y/n)? y
  6. Enter y to continue.
  7. Make sure that the original system's root aggregate is set to the root option and that other aggregates are online: aggr status
    You should see output similar to the following:
    *> aggr status
               Aggr State           Status                Options
              aggr0 online          raid_dp, aggr         root
  8. Exit Maintenance mode: halt