Azure Virtual Networks - Handson.txt - Planning Vnets Planning of Vnets is equivalent to planning the network in On-Premises networking components which

Azure Virtual Networks - Handson.txt - Planning Vnets...

This preview shows page 1 - 3 out of 13 pages.

Planning VnetsPlanning of Vnets is equivalent to planning the network in On-Premises networking components which includes,IP Address Space and SubnetsPrivate IP Range and Public IP addressesStatic and Dynamic IP addressesAzure DNSIP Addresses SpaceA Vnet allows organizations to design IP space in the Vnet, including breaking the IP space into virtual subnets.IP addresses are assigned to Azure resources like VMs, application gateways and load balancers,By connecting through the IP Addresses, Azure resources on same cloud can communicate with each other as well as on other cloud through the internet or on-premises network.IP SubnetsAddress space of the Vnets can be further divided in to smaller networks by using SubnetsFeatures:It provides logical and security isolation of Azure resources.VMs and PaaS role instances deployed to subnets (same or different) within a VNet can communicate with each other without any extra configuration.You can also configure route tables and NSGs to a subnet.CIDR Subnet DefinitionCIDR (Classless Interdomain Routing) notation represents an IP address range by combining an IP address through its network mask. CIDR is the routing system that is now used by all gateway routers.CIDR subnet definitions determine the number of bits in the IP address that defines the network.For example: Consider 216.0.131.0/22 and its in binary representation 11011000.00000000.100000|11.00000000The network address can be defined as first 22 bits of an IP address i.e networkmask of 216.0.128.0.Remaining 10 bits are for specific 258 host addresses.Subnets can be as large as /8 and as small as /29. However, subnets cannot have overlapping address spaces.IP Address Space PlanningWhile creating a VNet, the scope of IP addresses that can be allocated for the network resources is also defined. A VNet can contain both private and public IPaddress spaces.The communication with an Azure virtual network(Vnet) and the On-premises with aVPN configured is done by Private IP addressThe communication within the Internet, including Azure public-facing services, is done by Public IP AddressesThese IP addresses can be allocated in one of the following ways,Static AllocationDynamic AllocationDynamic allocation is the default allocation method.Private IP Address
Background image
Private IPs are assigned to resources, dynamically by Azure-provided Dynamic Host Configuration Protocol (DHCP).An IP address that is allocated by DHCP has infinite duration and is released only if the resource is deallocated (stopped).Private IP address space can be chosen from the RFC 1918 address blocks:10.x.x.x/8 : All addresses from 10.0.0.1 to 10.255.255.255.172.16.x.x/12 172.31.x.x/12 : All addresses from 172.16.0.1 to 172.31.255.255.192.168.x.x/16 : All addresses from 192.168.0.1 to 192.168.255.255.Static Private IP AddressStatic Private IP addresses can be configured from the range of IP addresses defined within the Vnet, which are reserved for specific VMs.
Background image
Image of page 3

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture