Usage Meter IP Address and DNS changes to default after reboot

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

1. On new deployment, the IP address and DNS are set correctly but after deployment and power ON, the DNS or the IP address range is different to that of what was used at the time of deployment.
2. When you try to change the IP address and DNS of the existing Usage Meter appliance, it returns back to the original values after reboot.
   
3. Usage meter hostname not verified-certificate error in the usagemeter UI: Failed to process journal=>read. Error:com.vmware.um.common.err.UmException: Hostname localhost not verified: certificate: sha256/xxxxxxxxxxxxxxxxxxxxxxxx= DN: CN=photon-machine,ST=Statename,C=subjectAltNames: []. Check the appliance logs for more details

Environment

VMware vCloud Usage Meter 4.x

Cause

Usage Meter appliance relies on ovfenv (a feature of vCenter server that leverages IP address pool to automatically lease out or set DNS records on compatible OVF). The virtual machine port group used for Usage Meter is associated to a port group that has an IP address pool associated with the incorrect values (values used gets cascaded over to Usage Meter).

Resolution

Please follow the steps below:

1. Take SNAPSHOT of the UM appliance from vCenter server UI.
2. Open SSH session to UM appliance.
3. Login as “usagemeter” and switch user to root using “su“.
4. Run configure-network command-line utility: /opt/vmware/share/vami/vami_config_net
5. Select the desired option to change the network configuration.
6. Input the values.
7. Exit the network command-line utility by entering option 1.
8. To preserve the changes post reboot, run: /opt/vmware/share/vami/vami_ovf_process -r eth0
9. Reboot the appliance using “reboot -f” to verify if the changes are persistent.

Additional Information

Impact/Risks:

Unable to retain network configuration changes after reboot of UM appliance.

Workaround 2: Usage meter hostname not verified-certificate error: Usage meter hostname not verified-certificate error after Upgrade to Usage Meter versions 4.8