Pivotal Knowledge Base

Follow

Service Network Deployment on Azure Fails with "Private static IP address falls within reserved IP range"

Environment

Pivotal Cloud Foundry® (PCF) 1.10 and above

Symptom

A new service network is deployed on Microsoft Azure platform, and the deployment fails with the following error:

Error message: {
"error": {
"code": "PrivateIPAddressInReservedRange",
"message": "Private static IP address 1.x.x.2 falls within reserved IP range of subnet prefix 1.x.x.0/24.",
"details": []
}
}

Issue

This is a known issue with Azure infrastructure. Azure reserves some IP addresses within each subnet. The first and last IP addresses of the subnets are reserved for protocol conformance, along with 3 more addresses used for Azure services.

See Azure Virtual Networks FAQ for details.

Resolution

Reserve the first 4 IP addresses and the last ip address within the ip subnet range.

For example: 1.x.x.0-1.x.x.4, 1.x.x.254

The PCF network will then not use these ip addresses in its platform.

Reserved IP Ranges can be added to the Ops Manager Director tile > Create Networks tab:

current-rmq-service-network-setting.png

Additional Information

Optionally, extra IP Addresses can be added in the Reserved IP Range to avoid any future conflicts, however, the deployment would work with just first 4 and last IPs reserved.

The above example can be changed to: 1.x.x.0-1.x.x.10, 1.x.x.254

Comments

Powered by Zendesk