VCF Automation deployment fails due to blocked ports in micro-segmented environment - VCF
search cancel

VCF Automation deployment fails due to blocked ports in micro-segmented environment - VCF

book

Article ID: 458322

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

 VCF Automation (VCFA) deployment on VCF 9.x stalls during the installation phase. Specifically, the deployment fails to schedule workload containers in the prelude namespace, often resulting in timeout or "URL Not Reachable" errors in log management.

Environment

VCF Automation 9.x

Cause

The environment enforces strict NSX micro-segmentation and Zero-Trust policies. The default deployment documentation may not include exhaustive port requirements for deployments utilizing NSX Distributed Firewall (DFW) and physical firewalls.

Resolution

Ensure the following bi-directional TCP ports are open between the management layer (SDDC Manager, Fleet LCM, VCF Operations) and the VSP IP addresses/Consumption cluster:

  • 443
  • 6443
  • 9100
  • 2381
  • 10257
  • 10259

These rules must be synchronized across both the physical firewalls and the NSX Distributed Firewall (DFW).

Note: PFA for complete list of Port requirements. For additional information on VCF deployment, please refer to the official VMware Ports and Protocols portal. If you encounter similar deployment failures, it is recommended to subscribe to this article for future updates on VCF Automation documentation.

Attachments

Micro_Segmentation_Port_Requirement.xlsx get_app