bug in Set-VBRNetworkTrafficRule

[AlexL]

Using v11 with latest patches.

get-help shows:

-ThrottlingValue <Int32>
Specifies the maximum speed value that must be used to transfer VM machine data from source to target.

But, the parameter accepts only values up to 999, if you try for example 1024 (mbitpersec) you get this error:

Set-VBRNetworkTrafficRule : Cannot validate argument on parameter 'ThrottlingValue'. The 1024 argument is greater than the maximum allowed range of
999. Supply an argument that is less than or equal to 999 and then try the command again.

[Mildur]

Are you really sure, that it is a bug?
It looks like the value is limited to 999 on purpose (like other parameters on other veeam powershell commands are limited to 999, for example max immutability for object storage)

[AlexL]

In the GUI you can perfectly set any value, for example 1024Mbps or 3072Mbps which is what I needed to limit to 3Gbs.
Since we have multiple servers/proxies I'd rather set this with a simple powershell oneliner rather than using the GUI.
Other commands have absolute limits, for example your max immutability, but for traffic limiting this obviously makes no sense and most likely this is a simple copy/paste error for input validation by the developer which wasn't catched by QA.

[Mildur]

You are right. That makes sense. If it's working in the GUI, then it should be possible in the powershell too.

[Mildur]

You could configure it that way as a workaround until there is a solution from Veeam.
384 Mbyte/s is the same as 3072 Mbit/s.

Code: Select all

$rule = Get-VBRNetworkTrafficRule -Name "Testing"
Set-VBRNetworkTrafficRule -rule $rule -ThrottlingUnit MbytePerSec -ThrottlingValue 384

[oleg.feoktistov]

Hi Alex,

Thanks for your bug report! We scheduled the fix to vNext. For now, you can use the workaround Fabian suggested.

Best regards,
Oleg