The Usage Meter appliance fails to connect to the Broadcom Cloud Service.
The Usage Meter web interface under Settings > Cloud Connectivity>Test Connection displays error: "Unable to resolve hostname eapi.broadcom.com."
Registration or synchronization with eapi.broadcom.com fails.
Connections to vCenter Server (if located on a different subnet) may also fail.
Usage Meter 9.x
The network settings configured on the Usage Meter appliance do not match the underlying network infrastructure provided by the environment.
Follow the steps below to confirm the connectivity failure and apply the correct network configuration.
1. Verify Connectivity Failure Log in to the Usage Meter console (via SSH or VMRC) and run the following commands to confirm the issue:
Test SSL Connectivity:
openssl s_client -connect eapi.broadcom.com:443 -servername eapi.broadcom.com
Observation: If the connection fails or times out, the appliance cannot reach the endpoint.
Test DNS Resolution:
nslookup eapi.broadcom.com
Observation: If the command returns a failure or cannot find the server, the appliance cannot reach the DNS server due to routing issues.
2. Obtain Correct Network Details Consult with your Network Administrator to confirm the correct settings for the appliance:
Static IP Address
Correct Subnet Mask / CIDR (e.g., /24, /23, /22)
3. Apply the Correct Configuration Once the correct settings are confirmed, use the nmctl command to update the interface.
Command Syntax:
nmctl add-addr dev eth0 a <IP_Address>/<Correct_CIDR_Mask>
Example: If your IP is 192.0.2.2 and the correct mask is /24:
nmctl add-addr dev eth0 a 192.0.2.2/24
4. Validate the Fix After applying the command, verify that connectivity is restored:
Check DNS: Run nslookup eapi.broadcom.com. It should now resolve to an IP address.
Check UI: Refresh the Cloud Connectivity settings. The "Unable to resolve hostname" error should disappear, and the status should show as All data Sent Successfully.