You can define a network change for lab templates that are deployed across different cloud networks or cloud data centers.
You can group networks, by tagging them with the same tag name. For example, in a template metadata, if a network is set with, "vlp" tag name, and a lab template is deployed on any region or data center, VMware Lab Platform looks up for all the networks that are tagged with the “vlp” tag name, ignoring the cloud org network name.
Network prefix ensures that the lab templates are connected to the available organization virtual data center network. For example, if an organization virtual data center network name is wdc-vcdxx-vlp-xx, you can assign the full name as the organization virtual data center network name, or can make an entry as "wdc-" in the Network page. In this example, XX is a variable.
When a lab is deployed, and there is more than one network available to connect to a lab, the lab is connected to the first network that has IP addresses available.
If both metadata attributes for prefix and tagging are set, tags have the highest priority and are preferred over the prefix. If no match is found by the tag name, then a prefix lookup is performed. If both the criteria are not met, the lab template does not connect to any cloud network.
You can use the
page to:Apply a tag name to cloud networks
Reset a tag
Sync networks
View cloud details
View total IP count available and used IP count
To view all the Cloud Networks options, click the icon.