topic Re: PowerShell Parameters Not Working in Application Integration

PowerShell Parameters Not Working

wave2453 — Tue, 12 Mar 2019 15:23:23 GMT

Hi All,

I have been trying to script out some LUN creation with the PSTK and noticed that some parameters come back a unrecognized. Below is an example.

PS C:\WINDOWS\system32> New-NSVolume -name test -size 10240 -perfpolicy 0316a3d10c4302926200000000000000000000001f -folder 2f16a3d10c4
3029262000000000000000000000001 -multi_initiator 1 -access_control_records
New-NSVolume : A parameter cannot be found that matches parameter name 'access_control_records'.
At line:1 char:162
+ ... 62000000000000000000000001 -multi_initiator 1 -access_control_records
+                                                   ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-NSVolume], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-NSVolume

PS C:\WINDOWS\system32>

I know that -access_control_records is a parameter I can call but it doesn't work. Has anyone else run into this issue? Does anyone know of a fix? I may be doing something wrong and if I am the help commands and error messages are not making that clear.

Re: PowerShell Parameters Not Working

Thomas_Lam_HK — Wed, 13 Mar 2019 06:07:55 GMT

From the command help:

DESCRIPTION
Create operation is used to create or clone a volume. Creating volumes requires name and size attributes. Cloning
volumes requires clone, name and base_snap_id attributes where clone is set to true. Newly created volume will not
have any access control records, they can be added to the volume by create operation on access_control_records
object set. Cloned volume inherits access control records from the parent volume.

Re: PowerShell Parameters Not Working

wave2453 — Mon, 18 Mar 2019 12:22:21 GMT

Then why even have that as an option on the New-NSVolume command?