Posts

Showing posts from 2021

Replacing vROPS Certificates

Image
Issue:  When using default certificates in vROPS  Due to security requirements it was necessary to replace the default self-signed certificates with a trusted certificate signed by an internal CA. Unlike vCenter, vROPS uses a common name vc-ops-slice-1 followed by slice-2 for data and other node, where vCenter has SAN names in the default certificate so when you add the root of the local machine trusted store then the vCenter url shows secured. In order to make the secure SSL we have to generate the CSR and get it signed by any third party SSL vendors or our own Microsoft CA.  I will be generating a CSR and getting signed by internal Microsoft CA .We can refer this below article from VMware as reference.  https://kb.vmware.com/s/article/2046591?lang=en_us Steps:  1.The first step is to create a new private key from taking a SSH session to master node vROPS. openssl genrsa -out vrops.key 2048 2. Using the configuration file below make sure to provide de...

vCloud Usage Meter 4.3 DNS settings is not updated after the UM 4.3 ovf Deployment

Image
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 Workaround 1:  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. Workaround 2: Navigated to the file: /etc/systemd/netwo...

Usage Meter 4.3 Fails to connect to vRNI (Network Insight) fails with API ERROR

Image
 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                                                                                                                                                                       Resolution : In `conf` directory modify `vrnicollector_process.conf` file, add the following lines and restart the vRNI collector service. Ensure the backup the file before making the changes below.         -httpCon...