ONTAP 9 – Introduction to OnCommand System Manager (GUI)

In my last screencast I make a quick introduction to ONTAP 9’s Graphical User Interface – OnCommand System Manager. System Manager is developed and updated for a long time, since ONTAP 8.3 it is already included in standard ONTAP build as a webservice that can be accessed via most modern internet browsers via cluster management IP address. However, with ONTAP 9 NetApp has re-design the GUI, completely modifying the Navigation Pane. Watch the screencast (7:30 mins) to see the GUI in a nutshell.

To access a Graphical User Interface for Your ONTAP cluster, You can either access:




In this screencast I’m going through available menus and options and also briefly show You how easy it is to create a brand new volume, check or edit the namespace and share it via CIFS. To validate the work, I also accessed the share via Windows Explorer and created a test-file to provide I have a read-write access to that particular share. Of course, there are quite a few things to consider in Your every-day production environment when it comes to creating new shares. For one I do not mention anything about share permissions, or even a security style of my volume. However, this was just a brief introduction of how easy it is to start. You can also check my post about NetApp cDOT – Namespace, junction path if you are not sure what namespace is.

In Your everyday activities, operations such as aggregate creation, or SVM creation will most likely not be Your everyday tasks. In most cases, You will probably focus more on SVM management, or event/incident monitoring and troubleshooting. That’s why I have focused a little bit more on the Storage Virtual Machine management. In case of any questions please feel free to leave a comment here or on Youtube, I will try to answer as soon as possible.

NetApp cDOT or ONTAP 9 ?

Within ONTAP 9 the naming convention has been slightly modified for the ONTAP family products. I feel I have to explain it a little bit further, since the term I’m using often (NetApp cDOT) might soon be outdated. So here are the details:

  • NetApp cDOT  – cDOT stands for clustered Data ONTAP. It is the product name for clustered-mode ONTAP 8.x. ONTAP 8.x is available in two versions: clustered and 7-mode, therefore this division.
  • ONTAP 9  – With version 9, NetApp ONTAP is available only as clustered mode (7-mode is no longer developed), therefore the product name was actually shorten from Clustered Data ONTAP  to just ONTAP.

Articles regarding NetApp cDOT are also for ONTAP 9. If some feature is only available from specific ONTAP version, I mention that in the article.

NetApp cDOT – quorum and epsilon

In today’s entry I would like to introduce quorum and epsilon concepts. Both are related with cluster health, needed in case of potential communications and connectivity issues.

What is Quorum?

When a cluster is in quorum, it means that majority of nodes are healthy and can communicate with each other. In other words, quorum is a precondition for a functioning cluster. When quorum is lost, the cluster does not have the ability to accomplish normal operations. Continue reading