Previously, we assumed that each org vdc edge gateway can be connected to one provider gateway and hence have only 1 uplink. Recently, a customer issue has uncovered that it is indeed possible for an edge gateway to have multiple uplinks. One of the uplink will be the uplink to Provider Gateway, while rest would be uplink to NSX-T imported external networks.
in this PR, we are modifying the check to test IP space support on an edge gateway to ignore all NSX-T import network uplinks and only use the Provider gateway uplink for determination of IP space support.
Testing done:
On a fresh VCD 10.5 testbed,
We created two provider gateways.
First gateway supports ip space, the second one doesn't.
We also created an external network from existing NSX-T segment and assigned it to provider gateway 1.
We created two edge gateways, one of them connected to the first provider gateway and the other one connected to the second provider gateway.
We created two org vdc networks connected to these edge gateways (individually).
Verified using POSTman that the gateway supporting IP Spaces has two uplinks
Previously, we assumed that each org vdc edge gateway can be connected to one provider gateway and hence have only 1 uplink. Recently, a customer issue has uncovered that it is indeed possible for an edge gateway to have multiple uplinks. One of the uplink will be the uplink to Provider Gateway, while rest would be uplink to NSX-T imported external networks.
in this PR, we are modifying the check to test IP space support on an edge gateway to ignore all NSX-T import network uplinks and only use the Provider gateway uplink for determination of IP space support.
Testing done: On a fresh VCD 10.5 testbed,