VCF installer fails to connect fleet management due to VCF installer using 172.17.0.0/16 subnet.
Article ID: 412502
Updated On:
Products
Issue/Introduction
VCF installer may fail to connect fleet management after its initial deployment by VCF installer. This leads to the failure of subsequent tasks. This issue occurs under the following specific conditions:
- The VCF installer's management network is configured on the 172.17.0.0/16 subnet.
- The management network (eth0) of fleet management is not 172.17.0.0/16. Fleet management needs to access default gateway to connect VCF installer.
Environment
VMware Cloud Foundation 9.0
Cause
Docker is installed in fleet management 9.0 and its default network is 172.17.0.0/16 and 172.18.0.0/16.
For these network is listed in fleet management's routing table, fleet management does not use the default gateway to communicate with these networks.
Resolution
Do not use the 172.17.0.0/16 or 172.18.0.0/16 IP address ranges for networks in the VCF 9.0 environment.
In some customer environments these networks ranges are extensively used and it is not possible to avoid 172.17.0.0/16 or 172.18.0.0/16
In such environments follow the steps in How to change the default Docker 172.17.0.0 range in VMware Cloud Foundation 9.0 Ops Fleet Manager
Additional Information
Feedback
