Virtualization And Cloud Computing

Recently customer had a issue where they have changes the vCenter IP address and after making the old vCenter endpoint as inactive is Usage Meter .Once the Changes have done we tried to add the vCenter and it adds successfully as per the collector logs but we were unable to see the vCenter with the new IP address. We later found that the old vCenter has the same instance UUID of the New vCenter IP address cache in the Usage Meter DB causing the issue. In order to resolve the issue we had to replace the FQDN or IP address on the Usage Meter database table with the new vCenter IP address . vCenter with old IP address is highlighted in the screenshot below after making its as inactive catalina logs [ ERROR ] [04/23/2020 15:49:46.151] [default-akka.actor.default-dispatcher-19] [akka://default/user/vcenterSaver] Exception while executing statement : ERROR: duplicate key value violates unique constraint "VcServer_instanceUuid" Detail: Key ("instanceUuid...

I had question from one of the customer is there any way or a possibility to find the installation date of the usage meter. Actually it is  possible from the 3.6.x - um.log should contain the initial boot-up instance along with the date and timestamp. Try the following command cat /var/log/usgmtr/um.log | grep liftweb.Boot 2020-02-27 10:29:56 ,878 INFO [localhost-startStop-1] liftweb.Boot : VMware vCloud Usage Meter 3.6.1 Build 7359407 starting

I had a issue registering vCloud director 10 with Usage Meter 3.6.1 HP3 Error : Service Unavailable  Checked on the compatibility guide the versions  is supported Port 443 is open even (customer had a firewall between them but firewall doesn’t seems to be a issues) Found out there is know issue with vCloud director v10. If you disable the provider access to the legacy API login endpoint,   all API integrations that rely on the system administrator login stop working, including vCloud Usage Meter and vCloud Availability for vCloud Director Workaround: Re-enable the service provider access to the legacy /api/sessions  endpoint by using the cell management tool. To enable the provider access to the /api/sessions API endpoint, run the following command on the vCloud Direcotor /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vcloud.api.legacy.nonprovideronly -v false ...