Error: "External IP xx.xx.xx.xx-xx.xx.xx.xx for NAT should belong to the sub-allocated IP range xx.xx.xx.xx-xx.xx.xx.xx of the edge gateway" when attempting to Edit or Create NAT Rules in Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• When users create or update a nat rule they get an error
• Error: "External IP xx.xx.xx.xx-xx.xx.xx.xx for NAT should belong to the sub-allocated IP range xx.xx.xx.xx-xx.xx.xx.xx of the edge gateway" when attempting to Edit or Create NAT Rules in Cloud Director.

 

 

Environment

VMware Cloud Director 10.6.0.1

VMware Cloud Director 10.6.1

Cause

This issue can occur when there are multiple Uplinks with the same CIDR block but different IP ranges, Cloud Director considers only the first uplink with the matching subnet as the valid uplink to set external IPs.

When the first uplink in the list does not have a valid IP allocated. Cloud Director does not check the remaining uplinks that might have an available IP address.

Resolution

This is a known issue in VMware Cloud Director 10.6.0.1 and 10.6.1.

This issue has been resolved in VMware Cloud Director 10.6.1.1 (Release Notes).

Additional Information

If you are facing the same error and this KB does not resolve your issue, please consider the following KB:

Cloud Director 10.6.1.1: Error: "External IP xx.xx.xx.xx-xx.xx.xx.xx for NAT should belong to the sub-allocated IP range xx.xx.xx.xx-xx.xx.xx.xx of the edge gateway" when attempting to Edit or Create NAT Rules in Cloud Director (413396)