| page_type | languages | products | extensions | ||||||
|---|---|---|---|---|---|---|---|---|---|
sample |
|
|
|
Azure Network sample for managing Internet facing load balancers - High-level ...
- Create an Internet facing load balancer that receives network traffic on port 80 and 443 and sends load-balanced traffic to two virtual machines
- Create NAT rules for SSH and TELNET access to virtual machines behind the load balancer
- Create health probes Details ... Create an Internet facing load balancer with ...
- A frontend public IP address
- Two backend address pools which contain network interfaces for the virtual machines to receive HTTP and HTTPS network traffic from the load balancer
- Two load balancing rules for HTTP and HTTPS to map public ports on the load balancer to ports in the backend address pool
- Two probes which contain HTTP and HTTPS health probes used to check availability of virtual machines in the backend address pool
- Two inbound NAT rules which contain rules that map a public port on the load balancer to a port for a specific virtual machine in the backend address pool
- this provides direct VM connectivity for SSH to port 22 and TELNET to port 23 Create two network interfaces in the frontend subnet ...
- And associate network interfaces to backend pools and NAT rules Create two virtual machines in the frontend subnet ...
- And assign network interfaces Update an existing load balancer, configure TCP idle timeout Create another load balancer Remove an existing load balancer
To run this sample:
Set the environment variable CLIENT_ID,CLIENT_SECRET,TENANT_ID,SUBSCRIPTION_ID with the full path for an auth file. See how to create an auth file.
git clone https://github.com/Azure-Samples/network-dotnet-manage-internet-facing-load-balancers.git
cd network-dotnet-manage-internet-facing-load-balancers
dotnet build
bin\Debug\net452\ManageInternetFacingLoadBalancer.exe
Azure Management Libraries for C# Azure .Net Developer Center If you don't have a Microsoft Azure subscription you can get a FREE trial account here
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.