Spoke 2 can't reach Spoke 1
Problem
Nothing in Spoke 2 can reach the app in Spoke 1.
Your job
- Get vm-spoke2 reaching the app on vm-spoke1 (443) through fw-hub
Without breaking
- Don't peer the spokes to each otherbroken
Background
"Since the weekend maintenance, nothing in Spoke 2 can reach the app in Spoke 1." The app runs on vm-spoke1 (10.1.1.4) on 443, and vm-spoke2 calls it. By design, traffic between spokes goes through fw-hub, the hub's network appliance at 10.0.2.4, and the spokes are never peered to each other.
How to work it
- 1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMsssh vm-spoke2What's this?
Opens a shell on vm-spoke2, 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.4 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.4where to connect443the port to try
Ticks off when the test runs on vm-spoke2.
- 2Find where it stops
- 3Name the cause
- 4Fix it and test again
0/3 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-spoke2 → vm-spoke1:443should work: not working
Goals 0/2
Cloud Shell · bashVMsrg-lab · eastus2
cloudshell:~$