Wednesday, August 11, 2021
Wednesday, March 3, 2021
Issue: I had multiple occasions where the UM 4.3 is deployed using ovf template and DNS settings are provided during the deployment and later checked DNS settings rollbacks to default IP address
Actions Performed :
1.Accesses the /op/vmware/share/vami/vami_config_net and updated the DNS settings but still it rollback to default DNS IP address
2. Added the DNS domain server in /etc/resolv.conf file but after the reboot the DNS IP address is not persistent
Cause: We found the resolv.conf is pointing to runtime symbolic which is making not persistent after reboot
- Take an SSH/ console onto the Usage Meter appliance, and run the below commands.
- mv /etc/resolve.conf /etc/resolve.conf.bak
- vi /etc/resolve.conf
- chmod 644 resolve.conf
- Key in the DNS server info in the below format. I have attached a screenshot below.
- nameserver DNSIPAddress1
- nameserver DNSIPAddress1
- Quit out of the file, and perform a reboot.
- Navigated to the file: /etc/systemd/network/10-eth0.network
- vi /etc/systemd/network/10-eth0.network
- Added the DNS entries
- Reboot the Appliance or restart the network by running systemctl restart systemd-networkd
- post which the DNS settings is persistent
Tuesday, January 26, 2021
Usage Meter v4.3 is not able to connect to vRealize Network Insight (vRNI v5.1.0). Product status in UM = collection error Message Notification = Collection error: APIError
Sunday, December 27, 2020
Issue: Unable to add the vCenter endpoint to the usage meter due to certificate error
Error: There was a problem checking the certificate vCenter fqdn:443 .Unexpected exception :java.net.UnknownHostException:fqdn of vCenter
1.Checked the root certificate on the vCenter and machine SSL ,SAN names etc
2. Running an openssl command from Usage meter using the IP address of the vCenter returns the certificate
3. Running and opnessl command from Usage meter using the vCenter FQDN fails to resolve and unable to fetch the vCenter certificate.
1.SSH into the Usage Meter appliance using root
2.Took a backup of /etc/hosts file
3.Added the IP address and the FQDN of the vCenter after which vCenter was successfully added to the Usage Meter.
Thursday, August 6, 2020
Monday, July 20, 2020
Using Custom Certificates in Usage Meter 4.x
As we get to move on with customers and service providers asking to implement to use a secure web browser access to Usage Meter .The old versions of UM has methods to replace the certificates.
Beginning from 3.6.1 versions there is no official or supported methods to use a custom certificates for Usage Meter and we are still allowed with default certificates.
Recently we are receiving request from customer using their own internal or custom signed certificates for Usage Meter 4.x versions. It still in the road map and i believe it will be taken care in the upcoming versions.
I have tested in my lab since the Usage Meter 4.x version uses ngnix web servers so i found a possibility to replace the certificates.
Note: Its official not supported and no supported documentation available at this moment and you have to repeat ever time you upgrade or patch the Usage Meter appliance make sure to take a snapshot or a valid backup before performing the steps
• Please take a snapshot of the Usage Meter Appliance
• Once you have the certificate and the key file generated from your CA
• Access the Usage Meter appliance via SSH using the root account
• Take a backup of the crt and key files from the location and copy the new crt and key files to
• ssl_certificate /etc/ssl/certs/nginx-selfsigned.crt
• ssl_certificate_key /etc/ssl/private/nginx-selfsigned.key
• Edit the configuration file
vi /opt/vmware/cloudusagemetering/conf/nginx.conf to match the crt and key location
Issue: When using default certificates in vROPS Due to security requirements it was necessary to replace the default self-signed certifica...
VAPI Endpoint service failure ERROR | state-manager1 | StsBuilder | Failed to acquire token for the s...
I came across this issue today where vPostgres service was failing on VCSA with error Fatal Error. # service-control --start vmware-vp...
Manually Replacing the solution user certificate on VCSA/PSC 6.x Note : -- Take a snapshot of the VC or PSC before proceeding. ...