Tag Archives: installation

NetApp DFM Installation: part 2

In the previous article, we’ve got the NetApp OnCommand installed. If you tick the check box to auto-launch, you get a browser window on the Windows machine you installed it. I installed the software on a machine called sddc-jump-box.vmsg.lab, as you can see from the URL.

For the ID, provide either the local Windows administrator, or the Domain Admin. I used the Domain Admin as my Windows is part of the domain.

15 configure - domain admin or local admin

Once login, you get to see a screen like this. It automatically discovers my NetApp, which is cool!

16 auto discover

I’m not sure if the Management Console is required by Blue Medora. Since I’m curious what it is, I’m going to proceed to install it. From the File menu, choose Download Management Console.

17 download the Management Console

It opens another application, which has links to download. No, it is not from the Internet, so it’s pretty fast and you do not need to login.

18 mgmt console install

I clicked the above link, which was a Windows exe file. I launched it, followed the simple wizard as shown below.

19 install

This started the installation. The progress is as shown below.

19 install 2

Some more example of the installation progress.

19 install 3

After a few short minutes, it’s completed.

19 install 4

I clicked Next, and was presented with the screen below. It’s handy to tick the check box.

19 install 5

And below is the NetApp Management Console. Notice it’s still using DFM (Data Fabric Manager), which is why the name still sticks with many NetApp admin. The Server is where you installed the product. The User is your MS AD Domain Admin.

19 install 6

And that’s basically it! From what I know, from vRealize Operations purpose, there is nothing else I need to do on the NetApp DFM end.

vRealize Operations 6: Express Installation

vRealize Operations provides 3 installation options, as you can see below:


In the earlier post, I have covered the “New Installation”. To refresh, it looks like the one below.


The Express Installation looks like the one below. You notice that the Administration phase is now called Startup. The only thing you need to do is set the password! This means it’s much easier in my experience. This is great for a majority of cases. I think most deployments will have less than 2000 VM, which means vSphere HA will be sufficient. This keeps the deployment simpler.


I clicked Next button, set the password, followed the wizard, and ended up with the following screen. So it’s basically done!



I clicked the Finish button, and ended up with the following screen. The screen took only a few minutes, as per what it says.


Once done, it’s presenting the login dialog.


So that’s it! Much simpler, and definitely what I recommend for POC use case.

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.