Wouldn’t it be nice if we can ask our Virtualized Infrastructure (VI) some questions in ways that won’t leave business people lost in translation? Like “Which VMs have the highest storage utilization and latency?” Or, easily get useful information by simply choosing a link that says: “Get an overall view of how much capacity I have, how much is used and what the usage trends are for a specific vCenter, datacenter or cluster.” On top of providing relevant information to our queries, wouldn’t it be dandy if our VI could monitor itself, then provide recommendations and remediation actions to certain issues as well?
Though we can’t talk to our VI verbally just yet like how we’d do with Sir, Google Assistant, or Bixby, we can use vRealize Operations Manager (vROps) to deliver intelligent operations management.
Using data collected from system resources (objects), vRealize Operations Manager identifies issues in any monitored system component, often before the customer notices a problem. vRealize Operations Manager also frequently suggests corrective actions you can take to fix the problem right away. For more challenging problems, vRealize Operations Manager offers rich analytical tools that allow you to review and manipulate object data to reveal hidden issues, investigate complex technical problems, identify trends or drill down to gauge the health of a single object.
– VMware vROps Guide
On this post, we’ll see how to install and run a test vROps node on VMware Workstation.
1. Download the vRealize Operations Manager 6.6 OVA from My VMware portal (trial version is available).
2. Use VMware Workstation to open the OVA we just downloaded and import the appliance to a drive in our computer. It will give you a warning that some components didn’t pass vROps validation. Let’s click on Retry even though it also say that it might still not work; better than choosing Cancel and pack up empty handed.
3. The vROps appliance will boot up completely to a black/blue screen that looks like the vCenter Appliance DCUI with IP address already assigned to it (given your VMware Workstation is allowed to do DHCP). This is completely different from the deployment guide we all can get from VMware Documentation Central which says we can set things like static IP address during the setup itself.
No worries, click inside the VM and press Alt + F1 to open the console. Log in as root without a password. First time log in will have us change the default password anyway.
4. Use vi to edit /etc/sysconfig/network/ifcfg-eth0 and set the following:
While we’re at it, we could enable SSH using this command:
service sshd restart
5. Point a web browser to the static IP address we just gave our vROps and choose an installation mode: Express (IP address will be set to DHCP, and master node name will be auto-assigned), New Installation, or Expand an existing installation.
I chose New Installation and I find the install wizard easy to follow, enough to leave this part to your hands.
7. The System Status page of the Administration Console comes up as soon as the installation is complete; however, we still one more thing to the finish the setup. For testing purposes, we’ll be content with a single node, and we’ll click on Start vRealize Operations Manager.
We’ll get a reminder to start vROps once we have configured and added all the nodes that we need to monitor our VI in this cluster (more info in this deployment guide). Again, for testing purposes, this lone node is enough to perform master services, data collection, and analysis; so we’ll proceed.
This process will take about 20 – 30 minutes (slightly over 20 minutes on 2 occasions that I did this), and we’ll see the node refreshing once in a while.
After the last step, vROps should be completely installed and ready to be integrated to our VI, which will be the topic of our next post.