Cluster image firmware and driver addons empty due to HSM proxy connection failure

Products

• VMware vCenter Server
• VMware Telco Cloud Platform

Issue/Introduction

1. When attempting to edit a vSphere cluster image to add firmware and driver addons, the section populates as empty, and the system reports that no Hardware Support Manager (HSM) is configured.
   
   
   
   
2. The /var/log/vmware/vpxd/hsm-service.log displays repetitive connection failures and proxy errors when attempting to reach the HSM host:
   
   

   HTTPSConnectionPool(host='################.###.##########.net', port=443): Max retries exceeded with url: /omevv/GatewayService/v1/vsphere-lcm/hw-support/v1/packages (Caused by ProxyError('Your proxy appears to only use HTTP and not HTTPS, try changing your proxy URL to be HTTP. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#https-proxy-error-http-proxy', SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1007)'))))., start retrying list_packages for 5 times with interval: 5

Environment

vCenter: 8.0 U3g

TCP: 5.1

Cause

The issue occurred because the HSM IP address and FQDN were mistakenly added to the proxy configuration in VAMI (vCenter Server Appliance Management Interface) under "Networking > Edit Proxy Settings". As a result, hsm-service was unable to establish proper communication with the Hardware Support Manager until the incorrect proxy configuration was corrected.

Resolution

Steps to Follow to Resolve the Issue:

1. Log in to the vCenter Server Appliance Management Interface (VAMI) as the root user.
   
   
2. Navigate to the Networking section and edit the proxy settings.
   
   
3. Remove the Hardware Support Manager (HSM) IP address and FQDN from the proxy configuration to ensure the traffic is not incorrectly routed.
   
   
4. Save the networking changes.
   
   
5. Connect to the vCenter Server Appliance via SSH and restart the vCenter services using the following command:
   
   

   service-control --stop --all && service-control --start --all

   


6. Log back into the vSphere Client and navigate to Cluster > Updates > Images to verify that the firmware and driver add-ons now populate successfully.

Additional Information

Unable to determine compliance because the firmware version cannot be read from the device. Manually verify firmware compliance

For more information on configuring networking exclusions, see Configure the DNS, IP Address, and Proxy Settings