Hi,
I defined through Cloud Foundation (VCF) two running Workload Domains (WLD), addressed to different environments each.
In one WLD, in which there is already a running Edge VM cluster for nort-south communications, we would like to have a second Edge VM cluster to communicate to another external network. So we deployed it through VCF, with the following outcome:
VCF effectively created an additional 2xVM Edge cluster which allows defining T0, T1s, segments etc. like the first Edge Cluster. But VCF didn't create new vmkernel ports to get thereby a fully segregated fabric as we expected, since the existing vmkernel ports keep being vmk10 & 11. So this new Edge cluster keeps using the existing TEP host subnet, but with a new transport zone for itself.
I would like to know if sharing the same existing fabric and TEP subnet is the expected behaviour when defining this second Edge Cluster through Cloud Foundation.
Or maybe the best approach woud be not to deploy this second Edge Cluster but keep using a single Edge Cluster in the WCF and reconsidering its design by setting proper isolations to integrate this new external network (filters, vrfs, etc)? I don't discard this option since, even the possibility of defining multiple Edge per WLD exists in VCF, I haven't seen much reported on that.
Best regards.
Albert.