Netapp 7-Mode Shelf Connecting to a C-Mode System

If you disconnect a disk shelf from a 7-mode system and have not removed the aggregate or unowned the disk you will notice once you connect it to your c-mode system that:

  1. The disks are seen as still owned by the previous 7-mode system
  2. The 7-mode aggregate is still seen on these disks

There is a specific process and 1 hidden command that will allows you to own the disks on the the new c-mode node and remove the aggregate 7-mode aggregate

The rest of this tutorial assumes you have already attached the 7-mode shelf to the c-mode system and all the cabling SAS and ACP is correct.

In this example we will simulate that the 7-mode shelf has an ID of 5 and we want the node named CLUSTER-01 to own the disks of the entire shelf.

Before we get started please use these steps AT YOUR OWN RISK, and if you are unsure Open a Netapp Support ticket

Taking Ownership of Netapp 7-Mode Shelf

CLUSTER::> disk assign -disk 0a.05.00 -owner CLUSTER-01 -force true

Repeat this command for all disks in the shelf. For example if the disks contains 24 disks repeat the above command from 0a.05.00 in increments of 1 all the way up to 0a.05.23

CLUSTER::> disk show -owner CLUSTER-01

You should see all the disks from shelf 5 assigned to the node CLUSTER-01

Removing the Aggregate

CLUSTER::> node run CLUSTER-01 aggr status

Look for the name of your existing 7-mode aggregate. It will be marked offline. In this example lets assume our 7-mode aggregate is called aggr1_450sas

CLUSTER::> node run CLUSTER-01

This command jumps into the CLUSTER-01 node shell

You will notice in this shell that there is no aggregate destroy command so we must enable it.

CLUSTER-01> options nodescope.reenabledcmds “aggr=destroy”

The above command brings back the aggr destroy command, but you will notice you cannot run any other aggr command while we have this option enabled.

CLUSTER-01> aggregate destroy aggr1_450sas

This command will ask you to confirm that you are sure you would like to destroy this aggregate. MAKE SURE YOU ARE 100% CERTAIN THIS IS THE CORRECT AGGREGATE

Once the aggregate is destroyed, we will need to turn off the aggr destroy option and return the default aggr commands

CLUSTER-01> options nodescope.reenabledcmds “”

CLUSTER-01> exit


You are now back at the cluster prompt and if you type the following:

CLUSTER::> aggregate show -nodes CLUSTER-01

You will notice that the 7-mode aggregate has been deleted and those existing 7-mode disks are now marked as spares.

The final step, probably not necessary but I did it anyway just to make sure. I re-zeroed all my spare disks on this node.

CLUSTER::> disk zerospares -owner CLUSTER-01

If you have any technical questions about this tutorial or any other tutorials on this site, please open a new thread in the forums and the community will be able to help you out.

All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment


  1. You can actually use a wildcard to assign the 7-Mode disks to the Clustered ONTAP node (atleast I did with 8.3P2) by typing:

    disk assign -disk 0a.05.* -owner CLUSTER-01 -force true

    Far easier than editing 24 disk assign commands.

    Thanks for the great write up.

Leave a Reply

Your email address will not be published.



This site uses Akismet to reduce spam. Learn how your comment data is processed.