+4I created a basic infrstructure in Azure with terraform, consisting of 2 spoke gateways and 1 transit gateway.
VNETs, Gateways and peerings are created correctly.
However, on the AirSpace Topology view, I can see the subnet and the controller object only for VNET1 and not for VNET2 and Transit VNET.
What could be wrong?
Best answer by Brad_Hedlund
If you click the VNET icon it should expand. You can also try setting the Fetch Instances and Fetch Topology tasks in Copilot to a shorter time period which will cause it to run again.
+1If you click the VNET icon it should expand. You can also try setting the Fetch Instances and Fetch Topology tasks in Copilot to a shorter time period which will cause it to run again.
+4If you click the VNET icon it should expand. You can also try setting the Fetch Instances and Fetch Topology tasks in Copilot to a shorter time period which will cause it to run again.
I clicked the VNET icon, but it doesn’t expand. It should behave exactly like VNET-1.
I’ll try to set the values to a shorter timeframe, can you confirm in which menu are those values present?
Additionally is it correct that also the transit VNET doesn’t show any content (including the Transit GW)?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.