Skip to main content

NetApp Cloud Insights Preview, Part 1: Installing the Acquisition Unit



For those of you that aren't familiar with NetApp Cloud Insights, it is an infrastructure monitoring tool that is currently available as a Public Preview. It is designed to provide, well, insight into the often diverse sets of storage and networking components in use across your entire environment - everything from on-premises ONTAP deployments to public cloud offerings from Amazon, Microsoft, and others.

Recently, I registered for the preview and just received my email welcoming me into the preview last week. I am planning a series of posts to cover my experiences with Cloud Insights and share the information with other people for whom a vendor-agnostic SaaS monitoring solution might be a good fit.

As a disclaimer: my experiences will be limited to what is in use in my environment, so the coverage of the public cloud features will likely not be covered in great detail - it will primarily be on-premises ONTAP and VMware monitoring data that I'm looking at.

However, there is a lot of good information about the offering in general if you'd like to get more information on the things that I gloss over. If you'd like to sign up for the preview yourself, there is a link below as well.

Cloud Insights product page
Tech Field Day video with James Holden
Register for Cloud Insights Preview

Now, with all of the introduction out of the way, onto the first step in getting your Cloud Insights deployment up and running - the Acquisition Unit (AU). It is a small application designed to run on a Linux server (CentOS 7 in my case) that connects to your various services (via Data Collectors configured in Cloud Insights) and sends inventory and performance data to the Cloud Insights servers.

When you have been accepted into the preview program, you will get an email with instructions on how to log into your tenant environment via NetApp Cloud Central. Once you have that email, you will be able to log in and download the .zip file that contains the Acquisition Unit software.

The installation is very straightforward and consists of unzipping a file and running the installation script contained within. You'll accept a EULA which I totally read in its entirety and then be prompted for several key pieces of information - server name, port, acquisition user password - all of which are provided in your welcome email. I think the installation took me roughly 10 minutes total and was relatively painless.

One quick note: I did not see any specific system requirements for the Acquisition Unit, but I had originally provisioned my virtual machine with 1 vCPU and 2GB of RAM, and the acquisition service would not start due to (evidently) Java failing to allocate sufficient memory to the application. I allocated 4GB of RAM to the AU instead, and all was well. So I would use 1 vCPU/4GB of RAM for your virtual machine.

Edit: As Rafael kindly pointed out (thank you!) in the comments section, here are the AU requirements:

- CPU: 4 cores
- RAM: 16GB
- Disk: 40GB

Once your Acquisition Unit is installed, you can make sure the service is running by issuing the sudo oci-service.sh status acquisition command. You should see a message like this if all is well:

[user@au-server ~]# sudo oci-service.sh status acquisition
OnCommand (R) Insight
acquisition is running
[user@au-server ~]#

From there, you should be able to see the AU in Cloud Insights as well under Admin -> Data Collectors -> Acquisition Units. The status should say "OK" assuming your AU is able to communicate with the Cloud Insights servers.

Now you can install Data Collectors, which are designed to connect to your on-premises or cloud services and collect inventory and performance data (bet you couldn't have guessed their function by their name!). That is accomplished via the Admin -> Data Collectors -> Available Data Collectors screen. At the time of writing, there are 49 available data collectors.




If you click on one of the boxes, you'll be able to install that particular Data Collector (or be given a choice of multiple Collectors offered by the same vendor. I'll be using the NetApp ONTAP Management Software collector in my example, but the logic is the same for other Data Collectors. 

I am using an existing service account with read-only access to my NetApp clusters, so if you have one of those, great. If not, you'll probably want to create one to use for monitoring use cases like this one. 

Once you click on the Data Collector, you'll see a screen to put in all of the relevant information for your NetApp deployment:



















Once you have all the information added, click on Test Configuration in order to validate that the AU is able to connect to the management IP and run a test command. You'll see a message indicating whether or not the test passed. 

From there, you can see the status of all of your installed Data Collectors by going to Admin -> Data Collectors -> Installed Data Collectors. There you can see high-level information about the status of the polling for your Data Collectors - the default polling interval appears to be 20 minutes and is configurable on a per-Data Collector basis. 

Once the Data Collectors have been polled successfully for inventory and performance data, you can begin to build some dashboards to get some use out of all the data. I'll be covering dashboards in a future blog post, so keep an eye out for a post with pretty graphs in the next few weeks.

So far, I'm pretty excited about what Cloud Insights has been able to offer, even just for on-premises ONTAP and VMware deployments. Hopefully I'll get to dig in even deeper and find out how I can use it in my environment to accelerate troubleshooting and get VM-level monitoring data to correlate with storage performance data. 

Thanks for reading and as always, stay tuned for future posts!





Comments

  1. Hi,

    You can see what Minimum AU Server Requirements are in the "Add an Acquisition Unit" wizard.

    Regards,
    Rafael Guedes

    ReplyDelete
    Replies
    1. Hey Rafael, thanks for the comment! All I see in the wizard under "Acquisition Unit Requirements" is:

      The Acquisition Unit server or virtual machine must have access to the internet. At least one port needs to be open and available between the acquisition unit and the Cloud Insights tenant in order to forward information to Cloud Insights. The default acquisition port is 443.

      I may be looking in the completely wrong place though. :)

      Donny

      Delete
    2. Hi Donny,

      The requirements are:
      - CPU: 4 cores
      - RAM: 16GB
      - Disk: 40GB

      Regards,
      Rafael Guedes

      Delete

Post a Comment

Popular posts from this blog

How To: Unjoin NetApp Nodes from a Cluster

Let me paint you a word picture:

You've upgraded to a shiny new AFF - it's all racked, stacked, cabled and ready to rock. You've moved your volumes onto the new storage and your workloads are performing beautifully (of course) and it's time to put your old NetApp gear out to pasture.

We're going to learn how to unjoin nodes from an existing cluster. But wait! There are several prerequisites that must be met before the actual cluster unjoin can be done.


Ensure that you have either moved volumes to your new aggregates or offlined and deleted any unused volumes.Offline and delete aggregates from old nodes.Re-home data LIFs or disable/delete if they are not in use.Disable and delete intercluster LIFs for the old nodes (and remove them from any Cluster Peering relationships)Remove the old node's ports from any Broadcast Domains or Failover Groups that they may be a member of.Move epsilon to one of the new nodes (let's assume nodes 3 and 4 are the new nodes, in th…

Cisco UCS Platform Emulator Installation

To continue my series of posts on building the framework for a functional lab environment, I'd like to talk about the Cisco UCS Platform Emulator (UCSPE). It is a software appliance packaged as a vSphere OVA that approximates a UCS deployment, including the networking components (a pair of switches called the Fabric Interconnects) and both blade and rackmount UCS servers (B- and C-Series, respectively). It can be a great tool for learning and becoming more familiar with the UCS platform. I will be deploying my UCSPE on vSphere 6.7 in my lab, but it should work similarly in other recent versions.

1. Start by downloading the UCS Platform Emulator OVA from https://communities.cisco.com/docs/DOC-71877 - you will need a Cisco Connection Online (CCO) login in order to begin the download. I am using version 3.1(2ePE1) of the emulator for this guide as that appeared to be the latest version available at the time of writing. Side note, I also noticed during the boot process that this versi…

NetApp ONTAP 9.3 Simulator Deployment - Part 1

I am going to be doing a few of these simulator/lab posts in an effort to set up an environment that will pave the way for future guides and blog posts. Hopefully it'll also be a good resource for folks that want to set up their own labs to test out new features and software versions. Today I'm going to show the steps required to deploy Netapp's ONTAP Simulator 9.3 on vSphere 6.5.  I'll also be doing a follow-up article that will detail the process of clustering a second node with this first one.

Note: My lab has vCenter 6.5 deployed along with a Distributed vSwitch, so the steps will be specific to that deployment. I will also assume that you already have basic networking and storage for your virtual machines in place.

Step 1: Deploying the Simulator

1. Browse out to https://mysupport.netapp.com, click on "Sign In" in the upper right-hand corner and log in using your NetApp account credentials.

2. Click on the Downloads drop-down at the top of the screen and c…