Toolkit 3.2 includes API coverage for Data ONTAP 8.3. This includes 126 new cmdlets and 31 cmdlets with new parameters. There are several categories introduced in Data ONTAP 8.3 and Toolkit 3.2 introduces two of them, namely MetroCluster and Storage Pool.
The following clustered Data ONTAP categories contain new cmdlets:
aggr (16 cmdlets)
cifs (13 cmdlets)
metrocluster (new category - 26 cmdlets)
net (48 cmdlets)
ipspace (4 cmdlets)
firewall (10 cmdlets)
failover group (4 cmdlets)
subnet (5 cmdlets)
port broadcast domain (7 cmdlets)
route (4 cmdlets)
arp (5 cmdlets)
ndp (9 cmdlets)
storage pool (new category - 8 cmdlets)
snapmirror (1 cmdlets)
vserver (7 cmdlets)
Get-NaDiskwill use storage-disk-get-iter when available.
ConvertTo-NaVhdx will create a fully-allocated dynamic VHDX instead of a fixed-size VHDX.
Invoke-NcSysstat now works with Data ONTAP 8.3
Fibre channel port information has been added to the output of Get-NaHostFcAdapter.
ConvertTo-NaVmdk could fail when connecting to a vserver management LIF that is also a CIFS data LIF and a network name was used.
ConvertTo-NaVmdk could fail when connecting to a vserver by name when DNS round robin is used.
Set-NcTime would fail for Data ONTAP 8.2 and higher.
Reset-NcCifsPassword did not have a default parameter set.
Also please specify the share property as "continuously_available" instead of "Continuously Available" (example given below). Regarding the network interface issue, could you please provide more details? Like do you wish to set the failover policy while creating a new network interface (usingNew-NcNetInterface) or are you attempting to modify an existing lif (using Set-NcNetInterface)?
Hello, yeah - the help isn't updated with all the values possible here. We've made a note to set this right.
As a general rule, if you have hyphenated strings that can be provided in cluster shell, then the same will be replaced by a string with underscore characters (instead of hyphen).
So in your case, you could augment the cmdlet with -FailoverPolicy "sfo_partner_only" or with -FailoverPolicy "broadcast_domain_wide".
Also, feel free to create a new discussion thread, possibly with the cmdlet name as title to seek attention or help. That way, it becomes easy for newer people to be able to search and get their queries answered. Thanks once again for bringing this to our notice. Appreciate it.