search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.26k stars 21.43k forks source link

Add/Remove/Change VNET Address Space #20572

Closed SamirFarhat closed 4 years ago

SamirFarhat commented 5 years ago

Hi, It's not mentioned whether or not we can modify the address space of a VNET by changing the address range, and not adding/removing. Example: My Current VNET address space is 10.10.0.0/16 --> Can we change it to 10.10.0.0/24

https://docs.microsoft.com/en-us/azure/virtual-network/manage-virtual-network#add-or-remove-an-address-range

Thanks

Document Details

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

DiegoRamirez-MSFT commented 5 years ago

hello @SamirFarhat

this would be a yes and no answer, you can change the address space completely if you dont have any subnets associated to it, which most of the times is not the case, other than that you can only make the address space subnet mask smaller than originally, for example changing a /16 to a /8 will be possible

@jimdial is it possible to update the documentation to mention this?

best

SamirFarhat commented 5 years ago

Thanks for the answer. In other words, we can resize the VNET address space only by extending it, and not the reverse. So i think a recommendation should be added to the documentation to mentaion that when we are not sure about the future IP addressing needs (the resources count that will consume our space), it's recomanded to use as a small address space, and then extend it or add additional ranges.

curtand commented 5 years ago

Hi @SamirFarhat Thanks for your contribution. I am sitting in for Jim Dial while he is out of the office for a bit. I have a bunch of stuff to wrap up this week, and then I will be OOF until January 7. This looks both interesting and brief, but I will have to wait to pick it up in January. Your request will not be forgotten, though. Thanks!

DiegoRamirez-MSFT commented 5 years ago

hello @curtand and @jimdial just checking if you might have any update on this thanks in advance

curtand commented 5 years ago

Hi @SamirFarhat I’ll see if I can get this staged for review today.

curtand commented 5 years ago

please-close

SamirFarhat commented 5 years ago

Sorry, the answer is for another issue. So i will remove my comment.

Karishma-Tiwari-MSFT commented 5 years ago

@SamirFarhat We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.

curtand commented 5 years ago

Hi @SamirFarhat I will stage this and let you know when. I commented it out after your comment, but it’s right there and I can publish it quickly.

curtand commented 5 years ago

Hi @SamirFarhat and @DiegoRamirez-MSFT I have the change staged at https://review.docs.microsoft.com/en-us/azure/virtual-network/manage-virtual-network?branch=pr-en-us-62761 It would be good if one of you approved it. This is not my usual area to document.

SamirFarhat commented 5 years ago

@curtand, i'm not msft. i wish i can review/approve the Microsoft docs. Is there any way for us (MVPs) ?

curtand commented 5 years ago

Thanks, @SamirFarhat Diego approved. I think I missed the 10 am printing run, so it should be live by 4 pm. @DiegoRamirez-MSFT

scottstout commented 5 years ago

I think the docs are still incorrect/unclear on this. You can change the address space to be smaller even if there is associated subnet . . . as long as the subnet is not in the address space that goes away. I think the docs are unclear on this. For example:

Create VNET with Address Space:172.21.0.0/16 Subnet: 172.21.0.0/24

Changed Address space from 172.21.0.0/16 to 172.21.0.0/18.

Docs currently say: "You can decrease the address range for a virtual network if you don't have any subnets associated with it"

Tagging: @Karishma-Tiwari-MSFT

Karishma-Tiwari-MSFT commented 5 years ago

@curtand Can you please review the doc updates suggested by @scottstout and update the doc as needed. Thanks :)

dcbrown16 commented 5 years ago

please-reopen

@Karishma-Tiwari-MSFT @KumudD The mistaken information that was called out here by @scottstout months ago has not been fixed, and this is causing confusion in a support ticket. Please reconfirm the content and fix this ASAP.

The section below is wrong. I just cut the space of a vnet in half (/24 to /25) since there were no subnets in the back half of the /24 range. This is possible even if there are VMs attached to the vnet (in the range that is still available, of course). "You can decrease the address range for a virtual network if you don't have any subnets associated with it. Otherwise, you can only extend the address range, for example, changing a /16 to /8. You could begin with a small address range, and then extend it later or add additional ranges."

Karishma-Tiwari-MSFT commented 5 years ago

@curtand @jimdial Can either of you please review the suggestions and update the doc accordingly. Thanks. :) CC: @TravisCragg-MSFT

curtand commented 5 years ago

@scottstout @SamirFarhat @TravisCragg-MSFT @Karishma-Tiwari-MSFT I was filling in for Jim Dial in January but this area is now owned by Kumud Dwivedi. Please assign to her. Thanks!

TravisCragg-MSFT commented 5 years ago

@curtand Assignment changed. Please let me know if there are any others.

allegradomel commented 4 years ago

Thank you for your patience in resolving this issue. The doc has been updated to reflect that the address range for a VNet can be reduced as long as it still contains the ranges for any associated subnets.

please-close