Monthly Archives: November 2014

Part 3: vRealize Operations – vCenter Configuration

In Part 2, we’ve configured the first node (which is also the master node). I only deployed 1 node, so vRealize Operations opened this page below. I login as Admin, as that’s the ID we have so far. We have not setup MS AD integration here yet.


vRealize Operations showed the screen below. Notice now the Administration part is done. The blue check box shows that. From here, we can import data. This is useful if you have vCenter Operations 5. I clicked New Environment since I am not importing any data.


There is that default trial period. This is useful if you do not have the licence key ready. In situation such as short POC, this can be handy. I clicked Next without specifying a key.


This is the end of the Wizard dialog box. I clicked the Finish button on the screen below.


vRealize Operations then showed the page below. This means the installation and initial configuration is done! I did all these without reading any manual, as it’s been guiding me.

Next is adding the vCenter. It’s already guiding us to click the Configure button. vRealize Operations uses the term “Solution” instead of adapter. In version 6, a solution can have multiple adapters, as you will see soon in this post. The default solution that comes out of the box is naturally the vSphere solution. If you have more solution (e.g. from Blue Medora, you will add it here first).


Clicking configure showed the window below. This window is pretty straight forward. The thing you need to know is every vCenter has 2 adapters. One is to get the data, the other one (Phyton) allows you to send command to vCenter, such as changing VM configuration.


I clicked the Test Connection, and the usual certificate warning appear. I clicked OK.


The Advanced Settings is optional, and it looks like the following screenshot. You can choose the Collector, and specify a different user for registration.


If your vCenter is already monitored by another vRealize Operations, you get a warning like below. Naturally, a vCenter can only link back to 1 vRealize Operations. I clicked Yes to overwrite it.


I did the same for all my 3 vCenter servers.


I clicked Next and got the following screen, where you can configure the basic option. What you see below is the default out of the box. I changed it to suit my lab.


The overall progress was shown again. This time around, you can see that all is done.


Clicking next showed the following screen. You can see that all 6 adapter instances are working well. They are collecting and data are being received.


We are done! Now let’s see what it looks like!

Part 2: vRealize Operations 6 – Initial Configuration

In Part 1, we deployed and booted up the appliance. The screenshot below was the first screen when I connected via browser. This is a one-time setup screen. I chose the “New Installation” instead of express as I wanted to see the options available.


That New Installation opened up the Wizard window shown below. It showed clearly the steps required. This screen will be shown throughout your installation, showing each “icon” as completed as you compete them. We are now at the Initial Setup stage under Administration.


Clicking next showed the screen below, where we setup the Admin password.


Clicking next showed the screen below, where you can add your own certificate. I chose the default.


Next is where you name the master node. This is my first node, which is also the master node. You also can set the NTP. It is actually verified, as you can see from the screen below. So keep that NTP server name or IP handy.


I clicked Next, and then completed the dialog box. The Wizard closed and the page below was shown. Notice the cluster status. It is not yet started. Notice that this page can show all the nodes, with a summary of each. Notice my Master Node is powered off. I clicked the button to start it.


Clicking Start turned up the dialog box below. I clicked Yes.


And that’s the initial configuration! Much easier than 5.8 I’d say. Let’s see what it shows on the next blog.

Part 1: vRealize Operations 6 – Installation

Based on 30 October 2014 build. Once it becomes available, I will certainly install the GA version to see if there is any changes.

There are 4 parts to this blog:

The vApp deployment part is pretty straight forward, as it’s similar with other vApp. I will just show the key difference here.

In the deployment, you will get a warning as shown below because 1 extra line of configuration (the NUMA vCPU setting). Other than that, it’s the standard vApp UI.


The appliance version comes with a few default size. I choose Extra Small as the Small deployment is too large for the lab (which is <300 VM). I see a lot of customers will either use the Extra Small or Small deployment. I have not tried the Remote Collector portion.


In the networking configuration, the default setting is static. There is no choice of DHCP, which is not an issue. Unlike version 5.x, it now needs 1 IP address. There is no IP Pool to configure at vCenter datacenter object too. Nice!


And that’s basically it! It got deployed pretty fast as it’s just 1.5 GB. It’s powering on, so I checked the VM console. The white line in the console below is actually a progress indicator.


I clicked on it as I wanted to see the details. You got the usual SuSE Linux boot information.


Within a few minutes, the boot up is completed. I did not set the host name in MS AD, so it’s defaulted to localhost. A good practice is to create the AD entry prior to the vApp deployment.


And that’s the vApp deployment part. Pretty straight forward! Compared with version 5.x, this is certainly easier. No more IP Pool, and no more vApp object to deal with at vCenter 🙂

Let’s login to vC Ops and do the initial config.