- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- PowerShell Parameters Not Working
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2019 08:23 AM
тАО03-12-2019 08:23 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2019 11:07 PM
тАО03-12-2019 11:07 PM
SolutionFrom 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.
RELATED LINKS
REMARKS
To see the examples, type: "get-help New-NSVolume -examples".
For more information, type: "get-help New-NSVolume -detailed".
For technical information, type: "get-help New-NSVolume -full".
Thomas Lam - Global Storage Field CTO
I work for HPE

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2019 05:22 AM
тАО03-18-2019 05:22 AM
Re: PowerShell Parameters Not Working
Then why even have that as an option on the New-NSVolume command?