Peer a spoke built from an old template
Problem
vnet-spoke2 won't peer with vnet-hub, so vm-spoke2 can't reach vm-hub on 443.
Your job
- Clear whatever stops vnet-spoke2 peering with vnet-hub
- Get the peering Connected on both sides
- Get vm-spoke2 reaching vm-hub on 443
Background
vnet-spoke2 was built from an old template. Its only subnet, subnet-app, holds vm-spoke2 at 10.20.1.4. It isn't peered to anything yet. Peer it with vnet-hub so vm-spoke2 can reach the shared service on vm-hub (10.0.1.4) on port 443.
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.0.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.0.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
- 5Explain it
Sources on Microsoft Learn (2)
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-hub:443should work: not working
Goals 0/4
Cloud Shell · bashVMsrg-lab · eastus2
cloudshell:~$