Non overlapping IP ranges for svc mgmt groups and application groups

[Subrahmanyam Ongole]

Service mgmt subnet is carved from an implicitly created L3 policy for admin owned tenant such as services tenant.

Customer application groups subnets are carved from their own implicitly created L3 policy.

We use the same IP ranges for all implicitly carved L3 policies.

In such a scenario, network service gets service mgmt IP from service mgmt subnet and a data network IP from application group subnet.

It is very likely that service mgmt subnet and app group subnet may get the same IP CIDR and this creates a problem inside service VM.

Service mgmt should use its own L3p and not use default IP ranges for carving its subnets.