We are pleased to announce the availability of NetApp PowerShell Toolkit 4.2
The NetApp PowerShell Toolkit 4.2 unifies all of NetApp’s PowerShell modules into a single package; The unified toolkit provides end-to-end automation and storage management across NetApp’s storage platforms of your datacenter and Hybrid Cloud – spanning 7-mode and clustered Data ONTAP running on FAS or AFF in your datacenter, ONTAP Select running on commodity hardware and ONTAP Cloud instances running on the public cloud. This release provides complete API coverage to ONTAP 9.0 and is backward compatible with previous ONTAP releases as well. NetApp PowerShell Toolkit 4.2 is compatible with Microsoft Windows Server 2016.
Please download the new PowerShell ToolKit from here.
Check the value of "$env:PSModulePath" for both users. It should include "C:\Program Files (x86)\NetApp\NetApp PowerShell Toolkit\Modules\". If not, follow these directions to add a path to that variable.
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Sorry about the lack of documentation - I'll raise a bug report for that. I could swear I wrote a help file for this, but apparently not.
To help you out right now - the New-NcCluster is equivalent to the 'cluster create' command on the CLI and cluster-create zapi. It starts the process to create a cluster using the node you're currently connected to.
The Base License param of course takes the cluster base license.
The NodeCount parameter is used to discover and add nodes to a new cluster. You can specify maximum how many discovered nodes (which are not already a part of any cluster) should be added.
Get-NcClusterCreateProgress can be used to track the status of the operation.
Add-NcClusterNode can be used to discover and join more nodes to this cluster later.
The "-NcController" is a common field for all cmdlets. To answer how it would be useful - suppose you've 4 newly provisioned nodes in the network and want to create two 2-node clusters out of it. The steps you could do is
`Connect-NcController $node -Add` for each of your nodes. This stores all the nodes in PowerShell session memory (and any cmdlet you execute will by default be executed on all 4 nodes/controllers)
`New-NcCluster -BaseLicense <> -NcController $node1,$node3` - this ensures a cluster-create operation is initiated only on the first and third node. If you didn't provide the NcController option, the cmdlet would be iterated over all currently connected nodes.
Run Add-NcCluster on $node2 and $node4 to finish the cluster creation.