search

HewlettPackard / POSH-HPEOneView

PowerShell language bindings library for HPE OneView.
http://hewlettpackard.github.io/POSH-HPEOneView/
125 stars 52 forks source link

New-OVNetwork does not allow combining the parameters "vlanRange" and "NetworkSet" #515

Closed mstreibe closed 2 years ago

mstreibe commented 3 years ago

Expected Behavior

To create bulk networks and assign them to an existing network set, one should be able to specify a VLAN range and a network set to assign them to, but the cmdlet throws an error when trying this.

Actual Behavior

New-OVNetwork : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1
+ New-OVNetwork -Name VLAN -VlanRange "2-2823,2826-3966" -Type Ethernet -Netwo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-OVNetwork], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,New-OVNetwork

Steps to reproduce

Execute this command: PS > New-OVNetwork -Name VLAN -VlanRange "100-2823,2826-3966" -NetworkSet "Production"

Version Information

HPE OneView PowerShell Library Version (`Get-HPOVVersion` or `$PSLibraryVersion`):
HPE OneView Appliance Version (`Get-HPOVVersion -ApplianceVer`):  
PS > Get-HPOVVersion

synergy.local                       LibraryVersion Path
--------------------                -------------- ----
ApplianceVersion: 5.40.00.423953.00 5.30.2560.2096 C:\Program Files\Hewlett Packard Enterprise\PowerShell\Modules\HP...

Output from $PSVersionTable on your Windows Host:

PS > $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14409.1018
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1018
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
ChrisLynchHPE commented 3 years ago

This was addressed in the recent 5.00 and 5.20 library updates. This will be fixed in the 5.30, 5.40 and 5.50 libraries soon.

ChrisLynchHPE commented 3 years ago

While this was fixed in prior 5.50 and 5.40 libraries, it is also within the following releases:

Please confirm prior to closing this issue.

ChrisLynchHPE commented 2 years ago

Closing due to no further activity. If you wish, feel free to re-open to discuss further.