Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Deployment of Virtual Container Host fails with "failed to validate VCH: Firewall must permit dst 2377/tcp outbound to the VCH management interface" (71072)

Last Updated: 7/19/2019Categories: TroubleshootingTotal Views: 21805Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Deployment of Virtual Container Host fails with "failed to validate VCH: Firewall must permit dst 2377/tcp outbound to the VCH management interface"

Cause

ESXi hosts communicate with the Virtual Container Hosts through port 2377 via Serial Over LAN. For deployment of a VCH to succeed, port 2377 must be open for outgoing connections on all ESXi hosts before you run vic-machine create.

Opening port 2377 for outgoing connections on ESXi hosts opens port 2377 for inbound connections on the VCHs.

Resolution

The vic-machine utility includes an update firewall command, that you can use to modify the firewall on a standalone ESXi host or all of the ESXi hosts in a cluster.

You use the --allow and --deny flags to enable and disable a firewall rule named vSPC. When enabled, the vSPC rule allows outbound TCP traffic from the target host or hosts. If you disable the rule, you must configure the firewall via another method to allow outbound connections on port 2377 over TCP. If you do not enable the rule or configure the firewall, vSphere Integrated Containers Engine does not function, and you cannot deploy VCHs.

The vic-machine create command does not modify the firewall. Run vic-machine update firewall --allow before you run vic-machine create.

Open a terminal on the system on which you downloaded and unpacked the vSphere Integrated Containers Engine binary bundle.

Navigate to the directory that contains the vic-machine utility:

Run the vic-machine update firewall command.

To open the appropriate ports on all of the hosts in a vCenter Server cluster, run the following command:

$ vic-machine-operating_system update firewall
--target vcenter_server_address/datacenter
--user "[email-masked]"
--password vcenter_server_password
--compute-resource cluster_name
--thumbprint thumbprint
--allow

Related Information

Link : https://vmware.github.io/vic-product/assets/files/html/1.5/vic_vsphere_admin/open_ports_on_hosts.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Ubuntu 18.4、16.4、SLED12SP3、SLES12SP3、および SLED11SP4 でスマート カードの取り外し時に画面を自動的にロックする (71068)

KB
•
組み込みの Orchestrator ポート 8283 に CA 署名の SSL 証明書を適用する (71060)

KB
•
UAC が有効な Windows に vRealize Operations Manager 7.5 Telegraf エージェントをインストールできない (70780)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.x

Take Our Survey

Support Assistant