I am trying to create virtual network peering between 3 Vnets. But I am getting an error. Can someone help?

ODL_User 846282 0 Reputation points
2023-03-11T01:34:32.5866667+00:00

Background:

I have 2 azure accounts. I was able to create 3 vnets with the default configuration and was able to peer all 3 of them on one account.

On the other account, I am not able to do so, the interface for virtual network creation on the azure portal is different on that account. What could be the problem?

thumbnail_image

The interface is different on both ID's as show below, What could be the reason?

User's image

WhatsApp Image 2023-03-10 at 8.26.37 PM

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,295 questions
{count} votes

2 answers

Sort by: Most helpful
  1. risolis 8,711 Reputation points
    2023-03-11T02:24:25.0133333+00:00

    Hello @ODL_User 846282

    Thank you for posting this concern on this community space.

    I read your case scenario description and I would like to bring few statements down below:

    1-Is this a Global vnet peering or same region vnet peering?

    2-Are you using the defaults settings on the second account or is there any other existing vnet that may interfere?

    3-Did you try to use different IP private allocation? Like using 172.16.x.x/12 Instead of 10.x.x.x/17 or any other block.

    4-There is another way to accomplish the same but depends on using Hub-n-Spoke topology along with NVA (Network virtual Appliance)

    I hope that can be useful for you.

    Looking forward to your feedback,

    Cheers,

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


  2. KapilAnanth-MSFT 41,151 Reputation points Microsoft Employee
    2023-03-12T11:03:13.32+00:00

    @ODL_User 846282

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you have created 3 VNets and peered them successfully in one of your Azure Account.

    However, you are facing an error when you attempt the same in a different account.

    The change in UI between two accounts is an expected behavior.

    Our Product Team is testing out new UI for VNet creation and it is possible that certain accounts may be using the new UI and certain UI may not be .

    You have mentioned that you used the default settings to create the 3 Virtual Networks.

    However, it is safe to say that with the newer UI, the default settings may not be the same and trying to repo the steps you did in the other account may not work here.

    Nevertheless, the error message you are facing is not related to UI.

    It is because there is an Address Range overlap between the VNets and thus, the portal is not allowing you to create a peering between overlapping Address Ranges.

    User's image

    Address Range Start End
    10.0.0.0/16 10.0.0.1 10.0.255.255
    10.0.0.0/17 10.0.0.1 10.0.127.254

    As you can see, there is a overlap of "10.0.0.1 to 10.0.127.254" between the two ranges.

    Now, I see this is a Test Environment. Using the below Address ranges for the three Virtual Networks should work in both of your accounts..

    • VNet1 - 10.0.0.0/16
    • VNet2 - 10.1.0.0/16
    • VNet3 - 10.3.0.0/16

    Kindly let us know if the above helps or you need further assistance on this issue.

    Thanks,

    Kapil


    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments No comments