Microsoft Virtualization Discussions

Re: Data ONTAP PowerShell Toolkit 3.2

Great Thanks.

Re: Data ONTAP PowerShell Toolkit 3.2

Unable to access provide location.

 

Error message as follows:

 

Unauthorized Access

You have come to a page or module to which you do not have permission.

If you believe you have proper permissions and have reached this notification in error, please submit Feedback.

If you have an urgent technical issue related to a NetApp product, please contact NetApp's Global Support Center

Re: Data ONTAP PowerShell Toolkit 3.2

Hello PSTK Community

 

where can i post Feedback to the actual Release 3.2.1 of the PSTK??

 

as an example:

a) i try to create a cifs share with share-property "Continuously Available", it seems the is not possible with PSTK, but is supported in OnTAP API

b) I likt to use the 8.3 new Failover-Policy with a new created network interface failover-policy can be "broadcast-domain-wide" or "sfo-partner-only"

 

These options or properties i do not find in the PowerShell ToolKit

 

Re: Data ONTAP PowerShell Toolkit 3.2

Hi,

 

Thank you for taking the time to share your feedback. I would suggest using this http://community.netapp.com/t5/Microsoft-Cloud-and-Virtualization-Discussions/Data-ONTAP-PowerShell-Toolkit-3-2-1/m-p/100910#M4160 for posting feedback regarding the 3.2.1 release. We do not have a separate thread monitored for feedback, but the usual practice is to provide feedback in the thread where release was announced.

 

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  (using New-NcNetInterface) or are you attempting to modify an existing lif (using Set-NcNetInterface)?

 

 

PS C:\Users\aparajir\Perforce\aparajir_BTC_pstk_3\main> Add-NcCifsShare -Name cifsvol1 -Path /cifs_vol -VserverContext cifs_vs -ShareProperties "continuously_available"

CifsServer                ShareName       Path                   Comment
----------                   -------                 ----                    -------
PSTK-FILER              cifsvol1            /cifs_vol

 

PS C:\Users\aparajir\Perforce\aparajir_BTC_pstk_3\main> Get-NcCifsShare cifsvol1 -VserverContext cifs_vs | select *


NcController                    : 10.225.183.84
Vserver                         : cifs_vs
Acl                             : {Everyone / Full Control}
AttributeCacheTtl               :
CifsServer                      : PSTK-FILER
Comment                         :
DirUmask                        :
FileUmask                       :
ForceGroupForCreate             :
MaxConnectionsPerShare          : 4294967295
OfflineFilesMode                : manual
Path                            : /cifs_vol
ShareName                       : cifsvol1
ShareProperties                 : {continuously_available}
SymlinkProperties               : {enable}
Volume                          : cifs_vol
VscanFileopProfile              : standard
AttributeCacheTtlSpecified      : False
DirUmaskSpecified               : False
FileUmaskSpecified              : False
MaxConnectionsPerShareSpecified : True

 

Hope this helps!

Re: Data ONTAP PowerShell Toolkit 3.2

Hello And thanks for the help

 

so it looks like the creation of a cifs share with -Share-Properties "continuously_available" does work?

Then it is just not documented in the help

 

 

yes, i try to create a new lif and would like to give the failover-policy either "sfo-partner-only" or "broadcast-domain-wide"

New-NcNetInterface nl_"$SMBv3_bkp_vserver_svm_name"_ha01_n1 -Vserver "$SMBv3_bkp_vserver_svm_name" -Role data -DataProtocols cifs -Node "$nodename_ha01_n1" -Port "$SMBv3_sto_portname" -Address "$SMBv3_bkp_data_lif_ha01_n1" -Netmask "$SMBv3_sto_netmask" -AutoRevert 1 -FailoverGroup "$SMBv3_sto_bdcst_domain" -AdministrativeStatus up

 

So thank you, it seems to work, but i did not find it in the help files.....

 

Thanks for your help!

Re: Data ONTAP PowerShell Toolkit 3.2

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.

Re: Data ONTAP PowerShell Toolkit 3.2

I am having an issue with the Add-NcNetFailoverGroupTarget command. It seems to have a mandatory value of -vserver. Is it possible to add to a fialover group that is cluster wide?

 

You can see here that none of my FG's have a vserver specified:

 

4-16-2015 2-02-54 PM.jpg

 

When I go to add a target, it requires a value for vserver:

 

4-16-2015 2-04-41 PM.jpg

 

Using the pipeline results in an error as well:

 

4-16-2015 2-08-09 PM.jpg

 

Any ideas how to get this to work? I can use the cluster shell, but I am looking for a pure pwershell solution. I am using NetApp Release 8.2.3P2 Cluster-Mode.

 

Thx,

 

Dan

 

Re: Data ONTAP PowerShell Toolkit 3.2

Anyone know where I can get this version of the Powersehll Toolkit? dot.PNG

Re: Data ONTAP PowerShell Toolkit 3.2

I get the same error.  Any solutions?

Re: Data ONTAP PowerShell Toolkit 3.2

Hi Dan,

 

This is a cmdlet introduced for use only on Data ONTAP 8.3 and above.

 

In 8.3, every failover group belongs to a vserver - the cluster wide ones simply belong to the cluster vserver (output from Get-NcNetFailoverGroup below). That is why Add-NcNetFailoverTargets makes vserver a mandatory parameter.

 

I do not have a 8.2.3 system handy right now, but I did verify that addition of failover targets was not supported in 8.2.1. But, if 8.2.3 does support the `network interface failover-groups add-targets` command and does not require the vserver parameter, you can work around this cmdlet by passing the cluster shell command as parameter to the Invoke-NcSystemApi cmdlet.

 

Output from Get-NcNetFailoverGroup on a system running Data ONTAP 8.3

-------------------------------------------------------------------------------------------

 

PS C:\Users\aparajir\Perforce\aparajir_BTC_pstk_1\main> Get-NcNetFailoverGroup

FailoverGroup              Vserver                    Target
-------------                   -------                       ------
Cluster                        Cluster                     {aparajir-vsim1:e0a, aparajir-vsim1:e0b, aparajir-vsim2:e0a, a...
clusterwide                 aparajircluster-1       aparajir-vsim2:e0d
Default                       aparajircluster-1       {aparajir-vsim1:e0c, aparajir-vsim1:e0d, aparajir-vsim2:e0c, a...
test_group                 pstk_peer                 {aparajir-vsim1:e0c, aparajir-vsim2:e0d}

 

Regards,

Aparajita

Forums