Top KB Articles for vRealize Operations Manager Troubleshooting

-
                   KB Articles for vRealize Operations Manager Troubleshooting


  1. Shutdown and Startup sequence for a vRealize Operations Manager cluster
  2. How to reset the admin password in vRealize Operations Manager
  3. Configure a Certificate For Use With vRealize Operations Manager 6.x and later
  4. How to reset the root password in vRealize Operations Manager
  5. Change the IP Address of a vRealize Operations Manager 6.x or later Single Node Deployment
  6. How to change a node hostname in vRealize Operations Manager
  7. Safely cleaning up log files in vRealize Operations 6.x and later
  8. Rebooting nodes in vRealize Operations Manager 6.x and later
  9. Upgrade to vRealize Operations Manager 8.0 fails due to low space on /dev/sdc
  10. Collecting diagnostic information from vRealize Operations Manager 6.x and later
  11. Upgrade to vRealize Operations Manager 8.x fails due to low space on /dev/sda
  12. Adding additional storage to a node in vRealize Operations Manager 6.x and later
  13. Using the Upgrade Assessment Tool for vRealize Operations Manager 8.0.x
  14. VMware Tools and Service Discovery in vRealize Operations Manager 8.0
  15. Upgrade to vRealize Operations Manager 8.0 fails due to the admin or root account password
  16. Reload the default certificate in vRealize Operations Manager 6.x and later
  17. Clearing the Alerts and Alarms Tables in vRealize Operations Manager
  18. vRealize Operations Manager Sizing Guidelines
  19. Replace expired internal certificate in vRealize Operations Manager 6.3 and later
  20. /storage/log is full on vRealize Operations Manager 6.x or later

Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more