vCenter server is not using configured proxy for all traffic.
search cancel

vCenter server is not using configured proxy for all traffic.

book

Article ID: 387615

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • vCenter Server is not part of a Cloud environment (eg: VMC on AWS)
  • With vCenter proxy configured, you see connections attempts to IP addresses 162.159.140.167* and 172.66.0.165* on port 443 (https) on your firewall.
  • In var/log/vmware/pod/pod-service.log

<timestamp> pod INFO    No-Op-id T-140062943696448 vmware.pod_telemetry Proxy URL not configured.
<timestamp> pod INFO    No-Op-id T-140062943696448 driver.rest_client Calling 'POST':'https://scapi.vmware.com/sc/api/collectors/VMwarePodService.2_0/instances/pod-/batch'
<timestamp> pod WARNING No-Op-id T-140062943696448 vmware.pod_telemetry Failed to send telemetry data: HTTPSConnectionPool(host='scapi.vmware.com', port=443): Max retries exceeded with url: /sc/api/collectors/VMwarePodService.2_0/instances/pod-/batch (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f62ebebf310>, 'Connection to scapi.vmware.com timed out. (connect timeout=120)'))

 

   * These are IP addresses of Broadcom online depot (dl.broadcom.com and scapi.vmware.com)

Environment

  • vCenter Server 8.0 U3

Resolution

Disable vmware-pod service

  1. SSH to vcenter server
  2. Stop vmware-pod service with command:

    service-control --stop vmware-pod

  3. Disable vmware-pod service with command:

    systemctl disable vmware-pod.service