Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New-AzNetworkWatcherPacketCapture - TotalBytesPerSession with incorrect data type #16061

Closed
lucabovo opened this issue Oct 11, 2021 · 6 comments
Closed

New-AzNetworkWatcherPacketCapture - TotalBytesPerSession with incorrect data type #16061

lucabovo opened this issue Oct 11, 2021 · 6 comments
Labels
customer-reported Network - Network Watcher question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@lucabovo
Copy link

Good morning,
I'm getting an error with "New-AzNetworkWatcherPacketCapture" command, in detail with this parameter: [-TotalBytesPerSession Int32] --> Cannot convert value "4294967295" to type "System.Int32". Error: "Value was either too large or too small for an Int32."Exception --> screenshot: image

I think the Type Int32 is wrong because it allows a MaxValue of 2147483647, instead of the Maximum Value allowed in Azure Portal that is 4294967295 as you can see in this screenshot --> image

Is it possible to fix the Type of TotalBytesPerSession with Unsigned-Int32 [Uint32]?

I keep waiting your feedback.
Thanks in advance for your cooperation and helpfulness.
Luca Bovo - beanTech

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported labels Oct 11, 2021
@dingmeng-xue dingmeng-xue added Network - Network Watcher Service Attention This issue is responsible by Azure service team. labels Oct 11, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Oct 11, 2021
@ghost
Copy link

ghost commented Oct 11, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @netwatchsuppgithub.

Issue Details

Good morning,
I'm getting an error with "New-AzNetworkWatcherPacketCapture" command, in detail with this parameter: [-TotalBytesPerSession Int32] --> Cannot convert value "4294967295" to type "System.Int32". Error: "Value was either too large or too small for an Int32."Exception --> screenshot: image

I think the Type Int32 is wrong because it allows a MaxValue of 2147483647, instead of the Maximum Value allowed in Azure Portal that is 4294967295 as you can see in this screenshot --> image

Is it possible to fix the Type of TotalBytesPerSession with Unsigned-Int32 [Uint32]?

I keep waiting your feedback.
Thanks in advance for your cooperation and helpfulness.
Luca Bovo - beanTech

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Author: lucabovo
Assignees: -
Labels:

Network - Network Watcher, Service Attention, question, customer-reported, needs-triage
Milestone: -

@lucabovo
Copy link
Author

Good morning,
any news about this case?

Thanks a lot

@dcaro
@netwatchsuppgithub

@lucabovo
Copy link
Author

Good morning,

@dingmeng-xue
@dcaro
@netwatchsuppgithub
@msftbot

this issue is still unassigned.

Any update?

Thanks,
Luca Bovo

@lucabovo
Copy link
Author

Good morning,
@dingmeng-xue
@dcaro
@netwatchsuppgithub
@msftbot

this issue is already 1 year old...

Any news?

Thanks,
Luca Bovo

@dingmeng-xue
Copy link
Member

Sorry for slow response. I pinged owner team just now. Let's wait their response. Ping me again please if there is no update in the next week.

This was referenced Dec 20, 2022
Closed
Merged
@v-sapanchal
Copy link
Contributor

Closing this issue, PR has been merged, #20504
and changes has been rolled out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer-reported Network - Network Watcher question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dingmeng-xue @lucabovo @v-sapanchal