Community

Cluster CLI and Node CLI

In one of my previous blog posts, I discussed clustershell and nodeshell and when and how to use them. Nowadays all my ONTAP storage systems are running Clustered ONTAP, or cDOT in short. I thought I could forget about the 7-mode CLI for good. However, a recent experience taught me a lesson: not so fast.

I was running cDOT version 8.2 on a two-node FAS2240 cluster and would like to create an aggregate. The aggregate create command in 8.1.x has a ‘-B’ switch. If you wish to create a 32-bit aggregate, you use “–B 32-bit”. To create a 64-bit aggregate, use “-B 64-bit”. In cDOT version 8.2, the ‘-B’ switch is gone.

You can still use Cluster CLI to create an aggregate. But how can you tell if it is a 32-bit or 64-bit aggregate? Granted, the aggregate show command can tell you a lot about the aggregate just created (see Figure 1). However, it does not tell you whether the aggregate is of 32-bit or 64-bit.

     Figure 1. Output of the aggr show command

Recall that we can run a subset of 7-mode CLI (i.e., Node CLI) under the “node scope” or in nodeshell; and the 7-mode CLI has an aggr status command. So, I tried this command on the aggregate just created. The result is shown in Figure 2 below.

      Figure 2. Output of the aggr status command

Now we see clearly that it is a 64-bit aggregate!

With the advance of cDOT, 7-mode is gradually fading from the center stage to the back stage. But from time to time, the 7-mode CLI proves itself to be useful for peeking into the nodes of cDOT clusters.

 

Thanks for reading.