Load balancer down after a port change
Problem
Every request to lb-app at 10.1.1.10 times out since the port change.
Your job
- Get vm-client reaching lb-app on 443
Without breaking
- Keep SSH from vm-client to the backends blockedbroken
Background
The web app on vm-web1 and vm-web2 moved to port 443. Since then every request from vm-client to lb-app at 10.1.1.10 times out. Both web servers are running and serving HTTPS locally. nsg-web filters the web subnet, and SSH from the client subnet must stay blocked.
How to work it
- 1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMsssh vm-clientWhat's this?
Opens a shell on vm-client, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.
nc -zv 10.1.1.10 443What's this?
netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.
-zonly check whether the port answers. Send no data-vprint the result in words10.1.1.10where to connect443the port to try
Ticks off when the test runs on vm-client.
- 2Find where it stops
- 3Name the cause
- 4Fix it and test again
- 5Explain it
0/2 changes
Network map
?
- Resource group, the outer dashed frame
- Virtual network, with its address space top right
- Subnet, with range and usable IPs (5 reserved)
- Network security group. A small shield on a VM's NIC means the NIC has one too
- Route table on the subnet
- VM Appliance Private endpoint
- Peering Connected Initiated or access off
- Goal working Goal broken, X marks where it stops
- Private DNS zone, dotted lines go to linked VNets
- Orange pulse: what your last command changed. Drag to pan, Ctrl and scroll to zoom.
vm-client → lb-app-fe:443should work: not working
Goals 0/3
Cloud Shell · bashVMsrg-lab · eastus2
cloudshell:~$