• In this architecture, each vSphere supervisor cluster is configured on a dedicated NSX overlay transport zone. There is network isolation between the vSphere supervisors as the segments created for one supervisor are visible and consumable only by that specific vSphere supervisor.
  • There will be dedicated T0 gateways for each vSphere supervisor.
  • The T0 edge cluster of each vSphere supervisor will be co-located on the same vSphere cluster.
  • Each supervisor will have dedicated service & pod CIDRs, namespace networks, ingress networks and egress networks
  • There is a 1:1 mapping between an NSX overlay transport zone and AVI cloud connector. Hence each supervisor will use separate NSX cloud connectors in AVI.
  • Because each supervisor has a dedicated NSX cloud connector in AVI, the AVI SE management network can use the same T0 gateway of the supervisor, as in the above architecture.
  • A dedicated SE Group will be used per supervisor, and this SE group belongs to the respective NSX cloud connector.
  • Optionally, a dedicated SE Group per vSphere supervisor can be used to host the system DNS for L7 Ingress / GSLB / AMKO use cases.
  • VxDC01-C01 is prepared on overlay transport zone TZ-Overlay-VxDC01-C01
  • VxDC01-C02 is prepared on overlay transport zone TZ-Overlay-VxDC01-C02
  • VxDC01-C01-EC01: This is the dedicated edge cluster for vSphere supervisor 1 and is co-located with the same vSphere cluster VxDC01-C01.
  • VxDC01-C02-EC01: This is the dedicated edge cluster for vSphere supervisor 2 and is co-located with the same vSphere cluster VxDC01-C02.
  • VxDC01-NSXMGR01-C01: for overlay transport zone TZ-Overlay-VxDC01-C01
  • VxDC01-NSXMGR01-C02: for overlay transport zone TZ-Overlay-VxDC01-C02
  • SEs for vSphere supervisor 1 will be co-located on the vSphere cluster VxDC01-C01, and
  • SEs for vSphere supervisor 2 will be co-located on the vSphere cluster VxDC01-C02

Similar Posts