Microsoft Azure Traffic Manager allows you to control the distribution of user traffic for service endpoints in different datacenters and region. Traffic Manager support distribution of traffic for Azure VMs, Web Apps, cloud services and non-Azure endpoints.
Traffic Manager uses the Azure DNS to direct client requests to the most appropriate endpoint based on a traffic-routing method and the health of the endpoints.
Traffic Manager uses vanity domain name to direct traffic to desired endpoints based on geographic location of the user and nearest Azure Datacentre where endpoint is located.
||Vanity Domain Name
||Public IP Address of endpoint
||Public IP Address of endpoint
Traffic Manager act like a DNS routing system to direct clients to specific service endpoints based on the rules of the traffic-routing method. Clients connect to the selected endpoint directly. Traffic Manager is not a proxy or a gateway. Traffic Manager does not see the traffic passing between the client and the service.
To Create Traffic Manager Profile,
- From a browser, sign in to the Azure portal.
- Click Create a resource > Networking > Traffic Manager profile > Create
- In the Create Traffic Manager profile, Select Geographic Routing Method, Resource Group Location and create profile.
- Select the Profile, Navigate to Settings -> Endpoints in Traffic Manager.
- Click Add to show the Add Endpoint.
- Click Add and in the Add endpoint, Type the Name and Source Type then Add geo-mapping to the endpoint.
- To test the Geo-mapping and Traffic routing, you can use any free VPN service or subscribe a VPN service and connect to region using the VPN service and access your endpoint. You will be directed to the nearest endpoint you have configured in step 5 & 6.
Windows server 2012 R2 can be configured as a Gateway VM in a two or four node cluster on Hyper-v Host. Gateway VM or router enhance Data Center by providing them a secure router for public or private cloud. Gateway VM cluster can provide routing functionality up to 200 tenants. Each Gateway VM can provide routing functionality for up to 50 tenants.
Two different versions of the gateway router are available in Windows Server 2012 R2.
RRAS Multitenant Gateway – The RRAS Multitenant Gateway router can be used for multitenant or non-multitenant deployments, and is a full featured BGP router. To deploy an RRAS Multitenant Gateway router, you must use Windows PowerShell commands
RRAS Gateway configuration and options:
- Configure the RRAS Multitenant Gateway for use with Hyper-V Network Virtualization
- Configure the RRAS Multitenant Gateway for use with VLANs
- Configure the RRAS Multitenant Gateway for Site-to-Site VPN Connections
- Configure the RRAS Multitenant Gateway to Perform Network Address Translation for Tenant Computers
- Configure the RRAS Multitenant Gateway for Dynamic Routing with BGP
Windows Server 2012 R2 Gateway – To deploy Windows Server Gateway, you must use System Center 2012 R2 and Virtual Machine Manager (VMM). The Windows Server Gateway router is designed for use with multitenant deployments.
Multi-tenancy is the ability of a cloud infrastructure to support the virtual machine workloads of multiple tenants, but isolate them from each other, while all of the workloads run on the same infrastructure. The multiple workloads of an individual tenant can interconnect and be managed remotely, but these systems do not interconnect with the workloads of other tenants, nor can other tenants remotely manage them.
This feature allow service provider the functionality to virtually isolate different subnets, VLANs and network traffic which resides in same physical core or distribution switch. Hyper-v network virtualization is a Network Virtualization Generic Routing Encapsulation NVGRE which allows tenant to bring their own TCP/IP and name space in cloud environment.
||2 Socket NUMA Node
||8 vCPU for two VMs
4 vCPU for four VMs
||Two 10GB NICs connect to Cisco Trunk Port1
||4 virtual NICs
- Operating Systems
- Clustering heartbeat
- External network
- Internal network
||Active-Active or Active-Passive
1-NIC Teaming in Hyper-v Host- You can configure NIC teaming in Hyper-v Host for two 10GB NICs. Windows Server 2012 R2 Gateway VM with four vNIC that are connected to the Hyper-V Virtual Switch that is bound to the NIC Team.
Windows Server 2012 R2 RRAS Deployment Guide
Test Lab Guide: Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 VMM
Clustering Windows Server 2012 R2