Оффлайн
- Регистрация
- 1 Мар 2015
- Сообщения
- 1,481
- Баллы
- 155
Virtual networks (VNets) are foundational to modern cloud-based architectures, enabling secure, isolated, and scalable connectivity among various Azure resources, the internet, and on-premises networks. This piece provides a technical guide to establishing and configuring VNets, focusing on Azure Virtual Network as a reference implementation.
All Azure resources within this virtual network are provisioned into designated subnets. To successfully deploy Vnet, an Azure subscription with the Contributor RBAC role assigned is required.
Two virtual networks, app-vnet and hub-vnet, are necessary to emulate a hub-and-spoke network architecture.
The app-vnet will support the application and requires two subnets: the frontend subnet for hosting web servers and the backend subnet for database servers.
The hub-vnet needs only a single subnet dedicated to the firewall.
Secure and private communication between the two virtual networks must be enabled through virtual network peering as Both virtual networks must reside within the same Azure region.
Establish hub-and-spoke virtual networks along with their respective subnets.
Sign in to the Azure portal. Search for and select Virtual Networks
Select + Create and complete the configuration of the app-vnet using the value given. This virtual network requires two subnets, frontend and backend.
Configure the frontend subnet by specifying the required value, then apply the default settings for all subsequent parameters, Repeat the identical procedure for your backend subnet.
Leave all other settings as their defaults. When finished select “Review + create and then Create.
Establish the configuration for the Hub-vnet virtual network, which incorporates the firewall subnet
Resource group==>RG1
Name==>hub-vnet
Region==>East US
IPv4 address space==>10.0.0.0/16
Subnet name==>AzureFirewallSubnet
Subnet address range==>10.0.0.0/26
Set up the subnet specifically allocated for the firewall. Subsequently, adopt the default configurations for all remaining parameters. When finished select “Review + create and then Create.
Upon completion of the deployments, locate and select your 'virtual networks' via search functionality. Confirm that both your virtual networks and subnets have been successfully deployed.
Establish a peering connection between the virtual networks.
Virtual network peering facilitates the seamless interconnection of two or more Azure Virtual Networks.
Search for and select the app-vnet virtual network. In the Settings blade, select Peering. + Add a peering between the two virtual networks. Using this specified required values.
Remote peering link name==>app-vnet-to-hub
Virtual network==>hub-vnet
Local virtual network peering link name==>hub-to-app-vnet
Retain all other configurations at their default values. Click "Add" to establish the virtual network peering. After the deployment is completed, confirm that the Peering status indicates Connected.
Whoolah!!! Its Conneted.
In a nutshell, Establishing and configuring virtual network infrastructures involves creating VNets with optimized subnets, securing them with NSGs and firewalls, and enabling robust connectivity via VPN or peering. These technical measures ensure a secure, scalable, and high-performing network environment, critical for corporate operations.
All Azure resources within this virtual network are provisioned into designated subnets. To successfully deploy Vnet, an Azure subscription with the Contributor RBAC role assigned is required.
Two virtual networks, app-vnet and hub-vnet, are necessary to emulate a hub-and-spoke network architecture.
The app-vnet will support the application and requires two subnets: the frontend subnet for hosting web servers and the backend subnet for database servers.
The hub-vnet needs only a single subnet dedicated to the firewall.
Secure and private communication between the two virtual networks must be enabled through virtual network peering as Both virtual networks must reside within the same Azure region.
Establish hub-and-spoke virtual networks along with their respective subnets.
Sign in to the Azure portal. Search for and select Virtual Networks
Select + Create and complete the configuration of the app-vnet using the value given. This virtual network requires two subnets, frontend and backend.
- Resource group==>>RG1
- Virtual network name==>>app-vnet
- Region==>>East US
- IPv4 address space==>>10.1.0.0/16
- Subnet name==>>frontend
- Subnet address range==>>10.1.0.0/24
- Subnet name==>>backend
- Subnet address range==>>10.1.1.0/24
Configure the frontend subnet by specifying the required value, then apply the default settings for all subsequent parameters, Repeat the identical procedure for your backend subnet.
Leave all other settings as their defaults. When finished select “Review + create and then Create.
Establish the configuration for the Hub-vnet virtual network, which incorporates the firewall subnet
Resource group==>RG1
Name==>hub-vnet
Region==>East US
IPv4 address space==>10.0.0.0/16
Subnet name==>AzureFirewallSubnet
Subnet address range==>10.0.0.0/26
Set up the subnet specifically allocated for the firewall. Subsequently, adopt the default configurations for all remaining parameters. When finished select “Review + create and then Create.
Upon completion of the deployments, locate and select your 'virtual networks' via search functionality. Confirm that both your virtual networks and subnets have been successfully deployed.
Establish a peering connection between the virtual networks.
Virtual network peering facilitates the seamless interconnection of two or more Azure Virtual Networks.
Search for and select the app-vnet virtual network. In the Settings blade, select Peering. + Add a peering between the two virtual networks. Using this specified required values.
Remote peering link name==>app-vnet-to-hub
Virtual network==>hub-vnet
Local virtual network peering link name==>hub-to-app-vnet
Retain all other configurations at their default values. Click "Add" to establish the virtual network peering. After the deployment is completed, confirm that the Peering status indicates Connected.
Whoolah!!! Its Conneted.
In a nutshell, Establishing and configuring virtual network infrastructures involves creating VNets with optimized subnets, securing them with NSGs and firewalls, and enabling robust connectivity via VPN or peering. These technical measures ensure a secure, scalable, and high-performing network environment, critical for corporate operations.