NetApp PowerShell Toolkit 101: Cluster Configuration

Using the NetApp PowerShell Toolkit (NPTK) can sometimes be a daunting task. Fortunately, it is pretty intuitive on how to configure most aspects of your storage system. Let’s start by looking at some of the cluster level configuration items that can be managed using the NTPK.

In this post we will cover:

  • AutoSupport
  • Licenses
  • Cluster Management LIF(s)
  • Inter-Cluster LIF(s)
  • SNMP
  • DNS

AutoSupport
Configuring AutoSupport is one of the most important things you can do for your system. AutoSupport enables the system to contact NetApp in the event of an error and allows NetApp to perform proactive and preemptive support for your systems.

  • Note: If you receive an error like the below, this is a known bug with version 3.1 of the toolkit.

    cluster_config_1

    The bug is a result of a type conversion error. The workaround is to simply provide a value for the MinimumPrivateDataLength parameter:

Some common tasks for AutoSupport include:

Licenses
Adding licenses to your cDOT system is trivial:

You can quickly compare the licenses in your cluster using this one-liner:

cluster_config_2

This gives an easy to check comparison if you have the same license count applied to each host. Alternatively, you could use this one-liner to view the licenses and which host they have been applied to:

cluster_config_3

Cluster Management LIF(s)
Each cluster must have at least one LIF which is used for managing the cluster itself.

Moving the cluster management LIF ahead of maintenance operations on the hosting node is a good idea to avoid any potential issues with connectivity. This function will move the cluster management LIF to another host in the failover group:

cluster_config_4

Inter-Cluster LIF(s)
Inter-cluster LIFs are used for SnapMirror and SnapVault realtionships. They are a standard network interface with a specific role and firewall policy assigned.

SNMP
Using just a couple of commands, we can configure and enable SNMP for the cluster.

DNS
DNS is managed much like any other service on the Cluster.

4 thoughts on “NetApp PowerShell Toolkit 101: Cluster Configuration

  1. Question – I’m interested in automating the actual cluster setup process…in 7-mode there is an Initialize-NaController cmdlet but doesn’t appear to be a similar cmdlet for Cluster mode. Any suggestions on how to handle this? It would be specifically for 8.3.x.

    • Hi John,

      This is possible, but not using cmdlets in the NetApp PowerShell toolkit that I’m aware of. Before a cluster has been created, the nodes have extremely limited functionality which does not support the functions of the PowerShell Toolkit.

      You will need to use PowerShell’s ability to import .NET bindings and load the Manage ONTAP dll from the NetApp Manageability SDK. From there, using the .NET ZAPI bindings, you’ll want to connect to the nodes (you’ll need to let them DHCP, then pass that DHCP address to your script) using no password. Once connected there are several steps needed to instantiate the cluster:

      • Set node management IPs
      • Set the admin password
      • Initialize the cluster on one of the nodes (using the cluster-create zapi)
      • Join the second node to the cluster

      Once that is done you will be able to connect to the cluster using the PowerShell toolkit and continue configuring.

      Please reach out to me using the NetApp Community private message system (my username is asulliva) or my NetApp address (my community username at netapp.com). I’ll share what I can about the process.

      Thank you for reading!

      Andrew

Leave a Reply

63e12e41b2d1b0c2e23e84d67faf9be2{{{{{{{{{{{{{{{{{{{{{{{{{{{{