Error: "Static route Network CIDR 0.0.0.0/1 must be allocated to Gateway" upon Quick IP allocation on Edge Gateways

Products

• VMware Cloud Director

Issue/Introduction

• Upon any Quick IP allocation configuration with CIDR 0.0.0.0/1 and/or 128.0.0.0/1 already configured on Edge Gateways we are getting error "Static route Network CIDR 0.0.0.0/1 must be allocated to Gateway" or "Static route Network CIDR 128.0.0.0/1 must be allocated to Gateway" 
• Upon Configuring Quick IP allocation of either 0.0.0.0/1 or 128.0.0.0/1 on Edge Gateways error "Static route Network CIDR 0.0.0.0/1 must be allocated to Gateway"  or "Static route Network CIDR 128.0.0.0/1 must be allocated to Gateway" 
• Impacts every Edge which has static route 0.0.0.0/1 and/or 128.0.0.0/1

Environment

Cloud Director 10.6.1

Cause

• This validation was added in place to avoid IP stealing by tenants in case of Provider Gateway with IP blocks.
• This condition ensures that if the network happens to be within Gateway IP Allocations of Provider Gateway but doesn't belong to allocated IP range of this Edge gateway then a validation error will be thrown.  
• Prior to VCD version 10.6.1, it was possible to create Edge Gateways with two static routes: 0.0.0.0/1 and 128.0.0.0/1

Resolution

Workaround:

This is a new validation logic introduced in VCD 10.6.1, and this is the expected behavior. To work around this validation, you must add the static routes directly in NSX.

Workaround:

Manually add the CIDR entries 0.0.0.0/1 and 128.0.0.0/1 directly in NSX on the tier-0 gateway that is used as the Provider Gateway.

For instructions, see Configure an NSX static Route.

Important: This workaround is temporary. The validation error will reappear if any update or modification is made to the edge gateway from the VMware Cloud Director UI. After any such update, these manual steps in NSX will need to be repeated.