Search the VMware Knowledge Base (KB)
View by Article ID

How to configure a standalone instance of vRealize Operations Manager in a VMware Cloud Foundation environment (2150028)

  • 0 Ratings

Purpose

This article provides instructions that can be used to deploy a standalone version of vRealize Operations Manager in a VMware Cloud Foundation environment.

Resolution

The vRealize Operations Manager version deployed must be at least 6.6.1.

The installation is not clustered or highly available by default but additional data nodes can be deployed for this purpose. Small nodes sizes should be sufficient but the vRealize Operations Manager sizing guide should be consulted to ensure that there are no sizing concerns: vRealize Operations Manager 6.6 Sizing Guidelines (2150421).
 
There is no support for remote collector nodes. 

vRealize Operations Manager should be deployed in the Management Workload Domain. Ensure that there is sufficient capacity in the Management Workload Domain to deploy vRealize Operations Manager nodes based on the sizes selected.
 
Additional management packs can be downloaded from the Solutions Exchange website.
 
The vRealize Operations Manager OVA and the Horizon Solution PAK file will need to be downloaded from MyVMware prior to starting.

  1. Pick a new IP address from the management subnet. Set an exclusion in SDDC Manager on the Settings-->Network Settings-->IP Distribution-->Exclusions page.

    Note: For the remainder of this article, 10.0.1.7 is used for the vRealize Operations Manager IP address.

  2. On the VRM virtual machine, edit the /etc/unbound/unbound.conf with a text editor. Add two lines similar to the following:

    local-data: "rack-1-vrops-2.vrack.vmware.com. IN A 10.0.1.7"
    local-data-ptr: "10.0.1.7 rack-1-vrops-2.vrack.vmware.com"


    Note: The hostname of "rack-1-vrops-2.vrack.vmware.com" was chosen to closely mimic the naming convention already in use but is not necessary.

  3. Restart the unbound DNS server on the VRM  virtual machine by issuing the following commands:

    kill $(ps -ef |grep unbound |grep -v grep|awk '{print $2}')
    unbound-control start


  4. Deploy the vRealize Operations Manager OVA.

    Note: The following is an example of the information to be supplied during deployment. The Storage and Network values must match this example but the other parameters can be set as appropriate or at the user's discrection:

    Name: vrops-ext
    Configuration: small
    Storage: vsandatastore, thin provision
    Network: vRack-DPortGroup-Mgmt
    Properties: gateway=10.0.0.253, dns=10.0.0.4 (VRM VM IP), IP=10.0.1.7, netmask=255.255.252.0

  5. When the deployment is finished, power on the vRealize Operations Manager virtual machine. When the OS is at the splash screen, navigate to the URL shown (https://10.0.1.7 in this example).
  6. Choose New Installation.
  7. If desired, set the password to the same password as the admin user has in the original vRealize Operations Manager instance. Otherwise, choose a  new password.
  8. Use default certificates.
  9. Set the Cluster master node name to the fully qualified host name of the new vRealize Operations Manager node and the NTP server to the same.
  10. Click the Start vRealize Operations Manager button. When the cluster is online, navigate to the same URL noted in Step 5.
  11. Accept the EULA.
  12. Enter the license key

    Note: If the VMware Cloud Foundation version is below 2.2, the same license in use on the pre-deployed vRealize Operations Manager Administration-->Licensing page can be reused.

  13. Navigate to the Administration-->Solutions page and click the Add button.
  14. Click the Browse button and choose the Horizon Solution PAK file. Click the Open button.
  15. Click the Upload button. When the PAK upload is completed, click the Next button.
  16. Click the checkbox to accept the EULA and then click the Next button.
  17. Click the Finish button when the installation is completed.
  18. Navigate to the Administration-->Licensing page and click the Add button.
  19. Select Product or Solution: VMware Horizon and enter the license key.

    Note: If the VMware Cloud Foundation version is below 2.2, the same license in use on the pre-deployed vRealize Operations Manager Administration-->Licensing page can be reused. 
     
  20. Navigate to the Administration-->Solutions page.
  21. Select VMware vSphere and then click the Configure button. 
  22. Enter <FQDN of Management vCenter Server>-adapter for the Display Name.
  23. Enter <FQDN of Management vCenter Server> for the vCenter Server name.
  24. Click the Add button next to Credentials. Enter the following information:

    Credential Name: FQDN_of_Management_vCenter_Server
    User Name: administrator@vsphere.local
    Password: administrator@vsphere.local_password

  25. Click the Test Connection button and accept the certificate when prompted.
  26. Click the Save Settings button.
  27. Repeat Steps 20 through 26 for any other Workload Domain vCenter Sever instances.
Note: If the version of VMware Cloud Foundation is below 2.2, the pre-deployed vRealize Operations Manager instance will need to be disabled.
  1. Log in to the pre-deployed vRealize Operations Manager instance.
  2. Go to the Administration page and click on Solutions.
  3. Select the first Solution type listed on the top-right.
  4. If any adapter instances are listed in the bottom-right pane, select them and click the Stop Collecting button.
  5. Repeat steps 3 and 4 for all adapter instances.
 
Note: If desired, SSH access to the vRealize Operations Manager virtual machine can be enabled and the root password can be set. 
  1. Log in to the vRealize Operations Manager virtual machine at the console as the root user and enter no password.
  2. A prompt will be presented requesting to change the root password immediately. Enter no password for the old password and enter the new password twice.
  3. Enter the following commands to enable ssh:

    chkconfig sshd on
    service sshd start








Additional Information

In VMware Cloud Foundation versions below 2.2, any time a new Workload Domain is created a new vCenter Server adapter instance will be created in the pre-deployed vRealize Operations Manager instance. These will need to be manually disabled per the steps noted in the Resolution section above. 

In all VMware Cloud Foundation versions, a new vCenter Server adapter instance will need to be manually created in the standalone vRealize Operations Manager instance. vCenter Server adapter instances created in the standalone vRealize Operations Manager instance will need to be manually deleted when a Workload domain is destroyed.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: