NetApp PowerShell Toolkit 101: Node Configuration

In the last post we looked at some settings that apply to the cluster. This time, let’s look at how to administer nodes.

In this post we will cover using the NetApp PowerShell Toolkit to manage these aspects of nodes:

  • Network Port Configuration
  • Node Management LIFs
  • Service Processor
  • CDP
  • Aggregates

Network Port Configuration

Clustered Data ONTAP has two types of network configuration: ports, which are the physical aspects of the network connectivity, and logicial interfaces (LIFs), which are the logicial entities that receive IP address (or WWPN) assignments.

A port can reference a single port on the controller, such as e0a (for an ethernet port) or 0d (for a FC port). Ports can also reference interface groups, for example when creating an LACP link aggregate, or VLAN ports, which are added onto the physical ports.


Note: This image comes from the NetApp document “Clustered Data ONTAP Network Management Guide”

Getting information about ports is just a cmdlet away…

Let’s look at how we can automate creating some different port configurations.

Port groups provide the ability to aggregate links and provide high availability in the event of link or switch failure. Creating them is a single cmdlet:

Regardless of the type of interface group created, you will need to add ports before it actually works.

The final step is to create any VLAN interfaces. These are tagged VLAN interfaces and can be created on individual ports or interface groups.

Setting port configuration is equally important and can be managed using the Set-NcNetPort cmdlet.

Node Management LIF(s)

Node management LIFs are managed the same as any other LIF, however they have a specific role: node_mgmt. Additionally, node management LIFs can not be migrated off the node they are meant to manage.

Service Processor


Cisco Discovery Protocol (CDP) is extremely helpful for verifying that you have connected your NetApp’s physical network ports to the correct ports on the switch. It also enables the network admins to verify configuration from their end as well.

There is no cmdlet for enabling or disabling CDP on the nodes, so instead we use system-cli API calls and the Invoke-NcSystemApi cmdlet. Here is a convenient wrapper function:

With the above function we can now enable and disable CDP easily.

And with CDP enabled, we can get CDP information using a cmdlet which is part of the toolkit.


Aggregates are the foundation of data storage in Data ONTAP. Without them you can’t create volumes, and without volumes you can’t store data. Let’s look at some common tasks:

I prefer to have my root aggregate names end with “_root” to make them easily identifiable. Here is a short script that will automatically rename them for you:

Leave a Reply