Operational Defect Database
BugZero updated this defect 44 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 2149196
vSAN Health Service - Online Health - Internet Connectivity Check
Last update date:
4/5/2024
Affected products:
vCenter Server
Affected releases:
8.07.06.0
Fixed releases:
No fixed releases provided.
Description:
Details
To perform the online health checks for vSAN, vCenter Server must be able to communicate over the Internet. This communication uses the management network to reach the customerconnect.vmware.com website and it's extensions.
Solution
The Internet connectivity check verifies that vCenter Server can communicate with vmware.com over the HTTPS/443 interface.If communication is successful, this check passes. If communication fails, the check indicates that the Internet connectivity is not available. Please verify vCenter is able to access vmware.com via HTTPS/443. Open an SSH session to the vCenter and use the following command to confirm if TCP HTTPS/443 handshake is completed :# curl -v https://customerconnect.vmware.com The output must indicate that the TCP handshake was either completed or accepted. See the image below for the expected output: If the output on your vCenter Server does not look similar to the image above: Check if your proxy server is configured to use the same TCP port, please take a look at https://kb.vmware.com/s/article/87793.Otherwise you should engage your networking team to validate the physical infrastructure as there might be restricted internet access in the environment which can be either expected or caused by a firewall or proxy preventing this communication. Note: If the Customer Improvement Experience Program (CEIP) is not enabled, the Internet connectivity check is unavailable. If the environment is a secure site or has restricted internet access, alternatively this alarm can be simply silenced. For more information on silencing, vSAN health check see Silencing a vSAN health check
Related Information
See https://kb.vmware.com/s/article/87793 when you experience this issue while using a proxy server configured with the same TCP port for both HTTP and HTTPS traffic.
