The partner API rejects the new job servers
Problem
The new job servers can't call the partner API.
Your job
- Get vm-jobs reaching api.partner.example on 443 through nat-gw
Without breaking
- Keep vm-app going out through nat-gwbroken
- Don't give either VM a public IP of its ownbroken
Background
"The new job servers can't call the partner API. The old app servers still can." The partner only accepts calls from 198.51.100.20, the public IP of nat-gw. vm-app in subnet-app works today. vm-jobs sits in the new subnet-jobs, built yesterday from a network template. Neither VM may get its own public IP.
How to work it
- 1See it fail
This traffic starts outside the lab VMs, so you can't log in to test it. Watch it instead.
Tap Explain on the red line under the map.
Ticks off when you tap Explain on the broken line.
- 2Find where it stops
- 3Fix it and test again
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.
Goals 0/3
Cloud Shell · bashVMsrg-lab · eastus2
cloudshell:~$