Use OMS LogAnalytics with the OpsLogix VMware Management Pack for extended monitoring

Use OMS LogAnalytics with the OpsLogix VMware Management Pack for extended monitoring

How to easily monitor VMware using OMS LogAnalytics with the OpsLogix VMware Management Pack, the extended way!

At OpsLogix, we’re always looking to integrate our products within the latest markets. We’ve already created a fantastic VMware Management Pack ​for SCOM that allows you to monitor your VMware environment without any extra software installations on your VMware boxes. ​Yep! You’re reading it correctly. ​No extra software installation on your VMware production servers! Sounds good doesn’t it?

Since OMS (Operations Management Suite) is a brand new product from Microsoft, we made sure to also integrate our VMware Management Pack into it. I will show you how easy it is to collect all your VMware logs and us it for your analytics.

But that’s not all.

​We also collect over 60 performance metrics for you to use to analyze the VMware health state. For example, Host / VM memory and CPU usage and datastore space etc. and of course all audit / task / alarm / snmp etc. events. Meaning that you can use it to meet all the requirements of your security auditing (NEN, SOX, ISO & etc.) And what’s really neat about our VMware monitoring solution, is that it doesn’t require a vCenter installation. You can also directly connect to a ESX(i) host without almost losing any monitoring features.

Pre requirements

Before we start we must meet the following pre requirements:

  • A working SCOM 2012 R2 environment
  • vCenter or ESXi server Boxes access (read only required at top-level)
  • An OpsLogix VMware Management Pack & license
  • The OpsLogix OMS Extension Management Pack
  • A Microsoft account (it can be live.com / hotmail.com or office365)

Step 1 – Setting up the OMS account

To set up your OMS account follow the on-boarding Instructions on page 3 by clicking here. It will take a few minutes of your time, plus it’s free of charge! There is only a restriction on the daily upload limit of 500 MB of data and a retention time of 7 days. But it’s a decent start for VMware event/performance analytics.

 

 

 

 

Step 2 – Add your SCOM management group to OMS

After finishing the instructions in step 1, check if you’ve also added your SCOM management group to OMS. Go to Overview -> Settings -> Connected Sources. If everything is done correctly, you should see your management group listed as green:

Step 3 – Setup of the VMware Monitoring

Follow the quick steps below, and also make sure to read the installation guide included in the software package:

  1. Open the Operations Manager Console as a SCOM administrator and Import the “OpsLogix VMware Management Pack” files included in the software package.
  2. Apply the VMware License using the OpsLogix Licensing dashboard in the SCOM Operations Management Console.
  3. Add the VMware instances that you want to monitor. You can do this in the SCOM console using the OpsLogix VMware configuration dashboard.
  4. Add the vCenter connection or the direct ESX(i) Host connection.
  5. If you’ve successfully added the VMware connection, you should see the monitoring being populated. Just wait until you see the vCenter/ESX Connections state view become active with a health state.

​Step 4 – Setup the OMS VMware Monitoring

In this step we’re going to enable the VMware Logs to the OMS collection.

  1. Import the OpsLogix OMS VMware extension management pack, using the SCOM console. This is a separate download and not included in the VMware Management Pack, see ‘Pre requirements’.
  2. By default, only VMware connections that are members of the SCOM group “OpsLogix VMware OMS group” are enabled to collect the logs and performance metrics.

Step 5 – Viewing the OMS VMware logs and performance collection

Now let’s check if the VMware log and performance metrics are picked up by OMS.

  1. Open a web browser and go to: https://login.mms.microsoft.com/signin.aspx?ref=ms_mms
  2. Login using the Microsoft account you created in the step “Setup the OMS account”
  3. The main OMS dashboard should appear. Select “Log Search”.
  4. Before we continue in the OMS portal we are going to generate some test VMware Alerts so that OMS can have collected them. As a test we are going to do a vCenter log on.
  5. Just open a vCenter connection and provide a correct log on. This will generate a VMware log event that will be collected in the OMS.
  6. If you have setup a direct ESX(i) connection just do the same using the Web based or telnet access.
  7. Wait for a minute or five to let OMS pick up the generated alert. The event OMS collection interval is per 60 seconds. If everything is working you should see an event in the log search. Please not that this log events will NOT be visible in SCOM because we don’t store this alert into the SCOM databases. Also remember that we are collecting ALL VMware messages, so if we would do this, due to the amount of log messages we could kill the performance/free space of the SCOM environment. However, the OMS environment is exactly configured to handle this big data without any problems!
  8. Next we test if the VMware performance metrics are collected. The query we use to get the performance metrics is: Type=Perf (ObjectName = VM*) or (ObjectName = Host*) or (ObjectName = Datastore*)


As you can see the test events are collected in OMS. Next we are going to let OMS collect information during a period of couple of days so that we have some data to work with.

​Step 7 – VMware OMS search query’s

We’re going to be writing some nice OMS query’s that can help you analyse the VMware event logs. Here are some examples:

Event log related

All VMware Events Type=Event EventLog=VMWare
All VMware Events with only the message and time Type=Event EventLog= VMWare |  Select Source , TimeGenerated , RenderedDescription
All VMware Events With the word Test in it Type=Event EventLog= VMWare Test |  Select Source , TimeGenerated , RenderedDescription
Count the number of messages grouped by event source Type=Event EventLog= VMWare | measure count() by Source
Count per vCenter the alerts generated Type=Event EventLog= VMWare Source= AlarmActionTriggeredEvent | measure count() by Computer
All Failed user logons to the vCenter or ESX(i) Hosts. Type=Event EventLog=VMWare (Source=UserLoginSessionEvent Or Source=BadUsernameSessionEvent) | measure count() by Source

Performance metric related

All VMware performance counters Type=Perf (ObjectName = VM*) or (ObjectName = Host*) or (ObjectName = Datastore*)
Virtual Machine CPU Usage Top over active time range ObjectName=”VM.CPU” InstanceName=percent CounterName=”% Average CPU time”  | measure percentile99(CounterValue) by Computer
VMware Host CPU Usage >80% over active time range ObjectName=”Host.CPU” InstanceName=percent CounterName=”% CPU Usage” InstanceName=percent  CounterValue > 80  |measure percentile99(CounterValue) by Computer
VMware Host Mem Usage >80% over active time range Type=Perf ObjectName=”Host.Memory” InstanceName=percent CounterName=”Average % Memory Usage” CounterValue > 70 | measure percentile99(CounterValue) by Computer
Datastore % used space with a 1hour aggeration . ObjectName=Datastore CounterName=”Datastore % used space” InstanceName=Total  | measure percentile99(CounterValue) by Computer interval 1hour
Datastore % used space Top over active time range ObjectName=Datastore CounterName=”Datastore % used space” InstanceName=Total  | measure percentile99(CounterValue) by Computer

Please keep in mind to also use the Table view instead of the default List view. In some outputs it makes it easier to read. You can also export it to Excel, which is a good option.

Step 8 – Dashboards

Last but not least we’ve made it possible to combine the most important information to be displayed into one dashboard as an overview.
An example of an end result could be as shown below:

Notice this example is not public yet, but in the meanwhile you can use the ‘normal’ OMS dashboard feature as an overview.

We’re done! Easy right? Hopefully this post was useful and you discovered the Power of OMS and VMware together using the OpsLogix VMware Management Pack.

Thanks,

Michel Kamp

This post is a working example of OMS and VMware. Since the OMS platform is still being extended it is possible that our solution has to be changed to reflect the OMS changes. At writing time all features described in this post are working. The described OpsLogix OMS extension Management Pack at this time is available for free to all customers having an OpsLogix VMware Management Pack license.

New Update for “OpsLogix Capacity Management Pack V1.0.0.98”

We are happy to announce a new update release V1.0.0.98 for our Capacity Management Pack.

This version of the Management Pack is upgrade compatible with the previous release (v1.0.0.67). If you have already purchased the Management Pack and have a valid support contract, you can login to the customer download area and download this version.

Version 1.0.0.98 contains following changes:

  • Fixed bug related to the empty data shown (a zero percentile or incorrect data) in the reports due to server original settings.
  • Various bug fixes related to the performance of retrieving data.
Adding and assigning a license in SCOM 2012

Adding and assigning a license in SCOM 2012

In order to import a license you should have received a valid license key from OpsLogix. If you did not receive a valid license key please contact support@opslogix.com or sales@opslogix.com to obtain a license key.

 

  1. In the OpsLogix License Manager in the Monitoring section of the Operations Console click the Add License button.
    OpsLogix License Manager

 

  1. In the Add License popup box paste the license key you received (taking care that there are no trailing spaces, empty lines, or carriage returns) and click the Import License(s) button. The license is now imported.
    Add License

 

  1. Select the Assign tab and select the management pack you wish to assign a license for from the dropdown box. Check the objects for which you would like to use the license and click the Update button.
    Assign licenses
Blackberry 10.2.0.x Management Pack Guide for Operations Manager 2012

Blackberry 10.2.0.x Management Pack Guide for Operations Manager 2012

Blackberry 10.2.0.x Management Pack

Guide for Operations Manager 2012

Published: Feb 2014

Copyright

The information contained in this document represents the current view of OpsLogix on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of OpsLogix, and OpsLogix cannot guarantee the accuracy of any information presented. OPSLOGIX MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

The descriptions of other companies’ products in this document, if any, are provided only as a
convenience to you. Any such references should not be considered an endorsement or support by
OpsLogix. OpsLogix cannot guarantee their accuracy, and the products may change over time. Also,
the descriptions are intended as brief highlights to aid understanding, rather than as thorough
coverage. For authoritative descriptions of these products, please consult their respective
manufacturers.

This deliverable is provided AS IS without warranty of any kind and OPSLOGIX MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OTHERWISE.

All trademarks are the property of their respective companies. © 2009 OpsLogix BV. All rights reserved.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

  1. Table of Contents

2. Copyright 2

3. Table of Contents 3

4. BlackBerry MP Installation Guide 4

5. Document Version 5

6. Prerequisites 6

7. Configuring Prerequisites 7

8. Importing the License Management Pack 8

9. Importing the BlackBerry Management Pack 9

10. Configuring the BlackBerry Management Pack 10

11. Licensing the BlackBerry Management Pack 13

  1. BlackBerry MP Installation Guide

OpsLogix intelligent management pack for BlackBerry 10.2.0.x, checks the status of your BlackBerry service as a whole, checking both BDS (BlackBerry Device Service) and UDS (Universal Device Service) components. Using System Center Operations Manager’s built-in Live Views, it provides the BES administrator insight in the root-cause of the problem. OpsLogix intelligent management pack for BlackBerry provides comprehensive state views and performance views on your BlackBerry infrastructure.

  1. Document Version

This guide was written based on version 10.2.0.501 of the OpsLogix BlackBerry Management Pack.

Release Date Changes
Feb 2, 2014 First draft
  1. Prerequisites

  • The OpsLogix BlackBerry Management Pack requires Microsoft System Center Operations Manager 2012.
  • The OpsLogix BlackBerry Management Pack makes use of Microsoft .NET Framework 3.5.Microsoft .NET Framework 3.5 must be install on all BlackBerry Enterprise Servers 10.x in order to monitor some of the critical BlackBerry components.
  • Agent Proxy must be enabled on all Operations Manager agents installed on BlackBerry servers.
  • A Microsoft Windows Domain account must be present which has local administrator rights on the BlackBerry servers and also has read permissions on the BlackBerry (BESMgmt) database.
  1. Configuring Prerequisites

Enabling Agent Proxy

The BlackBerry Management pack makes use of the Agent Proxy functionality in Operations

Manager 2012. Please make sure you enabled Agent Proxy for all the BlackBerry servers in your environment. To enable agent proxy, in the Operation Manager console, go to the
Administration pane. In the Administration pane select Agent Managed, then from the list right click on you BlackBerry server and select Properties. On the Agent Properties dialog select the Security tab and check the Allow this agent to act as a proxy and discover managed objects on other computers checkbox. Repeat this step for all your BlackBerry servers.

  1. Importing the License Management Pack

If this is the first time you are importing an OpsLogix Management Pack, you need to import the Licensing Management pack. If you have already installed OpsLogix Management Packs in your current SCOM environment previously, please make sure that the version is 2.3.2.7 or later.

In the Administration section of the Operations Manager 2012 Console complete the following steps:

1. Right click Management Packs -> Import Management Packs… -> Add -> Add from Disk

2. Browse to the location where you unpacked the OpsLogix BlackBerry Management Pack.

3. Import the following files:

a. OpsLogix.BaseLibrary.mp

e. OpsLogix IMP – Licensing Dashboard v2.3.2.7.mpb

4. Click Open -> Import

The OpsLogix Licensing Dashboard is now visible in the Monitoring section of the Operations Console under the following node:

Monitoring -> OpsLogix -> OpsLogix Licensing Dashboard

  1. Importing the BlackBerry Management Pack

In the Administration section of the Operations Manager 2012 Console complete the following steps:

1. Right click Management Packs -> Import Management Packs… -> Add -> Add from Disk

2. Browse to the location where you unpacked the OpsLogix BlackBerry Management Pack.

3. Import the following files OpsLogix IMP – BlackBerry 10 Management Pack (v10.2.0.501).mpb

4. Click Open -> Import

  1. Configuring the BlackBerry Management Pack

In order for the BlackBerry Management Pack to correctly monitor you BlackBerry environment, the Management Pack needs to be configured. To configure the BlackBerry Management pack the following steps need to be completed:

Configuring the RunAs Accounts

In the Administration section of the Operations Manager 2012 Console complete the following steps:

BlackBerry database Run As Account

  1. Navigate to Run As Configuration -> Accounts in the Administration view and right click Accounts -> Create RunAs Account.
  2. On the Introduction Page click Next.
  3. On the General page in the RunAs Account type dropdown box select Windows and enter BlackBerry Database Account in the Display name text box. Optionally add a description in the Description text box.
  4. On the Windows RunAs Account page, enter the name of the Windows Account that has access to the BlackBerry database and local administrator rights on all BlackBerry Servers which are to be monitored. Enter the password for the account in the Password and Confirm password text boxes. Select the appropriate domain in the Domain text box.
  5. On the Distribution Security page select the security level that is appropriate for your organization. If you chose the More secure option, make sure you include all your BlackBerry servers.
  6. Click Create.
  7. Click Close.

Configuring the RunAs Profiles

In the Administration section of the Operations Manager 2012 Console complete the following steps:

BlackBerry Enterprise Server Database RunAs profile

  1. Navigate to Run As Configuration -> Profiles in the administration view.
  2. In the right pane right click BlackBerry 10.x Database Run As Profile and select
    Properties.
  3. On the Introduction page click Next.
  4. On the General Properties page click Next.
  5. On the Run As Accounts page click Add.
  6. In the Add a Run As Account dialog box, select BlackBerry Database Account from the
    Run As Account dropdown box.
  7. In the Add a Run As Account dialog box, select the A selected class, group, or object radio button and click the Select… button and from the dropdown select Group…
  8. In the Group Search popup dialog search for BlackBerry 10.x Run As Instances (enter BlackBerry 10.x Run As Instances in the Filter by field and click search). From the Available Groups list select BlackBerry 510.x Run As Instances and click OK twice.
  9. Click OK.
    The result should look as in the screenshot:

 

  • Click Save.
  • On the Completion page you can choose to make use of more-secure/less-secure Run As
    account distribution. If you make use of the more-secure distribution, make sure that you
    select all Blackberry servers for account distribution.
  • Click Close.

 

  1. Licensing the BlackBerry Management Pack

In order to import a license you should have received a valid license key from OpsLogix. If you did not receive a valid license key please contact support@opslogix.com or sales@opslogix.com to obtain a license key.

In the OpsLogix License Manager in the Monitoring section of the Operations Console click the Add License button.


In the Add License popup box paste the license key you received (taking care that there are no trailing spaces, empty lines, or carriage returns) and click the Import License(s) button.


The License is now imported. Because of the license model later – after importing and configuring the BlackBerry Management Pack – you will need to return to the licensing console to enable the license for each BlackBerry server you would like to monitor.

To assign a license to a BlackBerry server, navigate to the OpsLogix License Manager in the Monitoring section of the Operations Console and select the Assign tab.


From the Dropdown list box select the OpsLogix.IMP.BlackBerry.5.0 license (Note that the same license is used for the BlackBerry 5.0 Management Pack as the BlackBerry 10 Management Pack). Check all the BlackBerry servers that you wish to license and click the Update button.

VMware Management Pack Installation Guide for Operations Manager 2012 SP1/R2

VMware Management Pack Installation Guide for Operations Manager 2012 SP1/R2

 

VMware Management Pack

Installation Guide for Operations Manager 2012 SP1/R2

Published: October 2013

  1. Copyright

The information contained in this document represents the current view of OpsLogix on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of OpsLogix, and OpsLogix cannot guarantee the accuracy of any information presented. OPSLOGIX MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

The descriptions of other companies’ products in this document, if any, are provided only as a
convenience to you. Any such references should not be considered an endorsement or support by
OpsLogix. OpsLogix cannot guarantee their accuracy, and the products may change over time. Also,
the descriptions are intended as brief highlights to aid understanding, rather than as thorough
coverage. For authoritative descriptions of these products, please consult their respective
manufacturers.

This deliverable is provided AS IS without warranty of any kind and OPSLOGIX MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OTHERWISE.

All trademarks are the property of their respective companies. © 2009 OpsLogix BV. All rights reserved.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

  1. Table of Contents

 

1 Copyright 2

2 Table of Contents 3

3 VMware MP Installation Guide 4

4 Document Version 5

5 Software Prerequisites 6

6 Importing the Management Pack 7

7 Configuring the OpsLogix VMware Management Pack 8

7.1 Adding the appropriate Management Servers to the Resource pool 8

7.2 Configuring the “VMware Management Pack RunAs Profile” Run As Profile 10

7.3 Creating a VMWare monitoring user account 13

7.4 Adding vCenter in System Center Operations Manager 16

7.5 Assigning a license to the OpsLogix VMware Management Pack 18

 

  1. VMware MP Installation Guide

 

Before importing the OpsLogix IMP VMware Management Pack, please read the license agreement carefully.

 

  1. Document Version

 

This guide is based on version 1.1.0.1 of the OpsLogix VMware Management Pack.

Release Date Changes
Oct 28, 2013 First draft

 

  1. Software Prerequisites

 

This management pack requires the following software to be installed:

  • System Center Operations Manager 2012 SP1 / R2
  • VMware vCenter 5.0 or higher

  1. Importing the Management Pack

 

Before importing the OpsLogix Oracle Management Pack make sure that you have the following file available:

  • OpsLogix.BaseLibrary.mp
  • OpsLogix IMP – Licensing Dashboard v2.3.2.5.mpb
  • OpsLogix IMP – VMware Management Pack v1.1.0.1.mpb

 

Note: Some of the management pack files might be of a higher version, if this is so, these should be used.

 

For importing the OpsLogix Oracle Management Pack complete the following steps:

Navigate to the Administration section of the Operations Manager 2012 Console:

 

  1. Right click Management Packs -> Import Management Packs… -> Add -> Add from Disk
  2. Browse to the location where you unpacked the OpsLogix VMware Management Pack.
  3. Import the following files:
    1. OpsLogix.BaseLibrary.mp
    2. OpsLogix IMP – Licensing Dashboard v2.3.2.5.mpb
    3. OpsLogix IMP – VMware Management Pack v1.1.0.1.mpb
  4. Click Open -> Import

 

  1. Configuring the OpsLogix VMware Management Pack

 

There are five main points of configuration to be completed for the OpsLogix VMware Management Pack to function correctly:

  • Adding the appropriate System Center Operations Manager Management Servers to the “OpsLogix Resource Pool for VMWare Management Pack” Resource Pool.
  • Configuring the “VMware Management Pack RunAs Profile” Run As Profile with an account that has the appropriate permissions on the Management Servers.
  • Creating an account that has at least read permissions on all objects in VMware vCenter.
  • Adding vCenter in System Center Operations Manager.
  • Assigning a license to the OpsLogix VMware Management Pack

 

  1. Adding the appropriate Management Servers to the Resource pool

 

A resource pool enables the VMware Management Pack to offer high available monitoring when using more than one System Center Operations Manager Management Server. At this point however it is recommended that one Management Server is appointed to do the monitoring. One single Management Server is appointed by only adding one server to the “OpsLogix Resource Pool for VMWare Management Pack” Resource Pool using the following procedure:

  1. In the Administration section of the SCOM console navigate to Administration -> Resource Pools and right click OpsLogix Resource Pool for VMWare Management Pack. Select Manual Membership.

     

     

     

  2. Click Yes on the Manual Membership popup box.
  3. Add or remove the Management Servers you want the Management Pack to be able to run on. Note: All Management Servers in the OpsLogix Resource Pool for VMWare Management Pack must be able to connect to the vCenter server in your VMWare environment.

     


     

  4. Complete the OpsLogix Resource Pool for VMWare Management Pack Properties wizard.

 

  1. Configuring the “VMware Management Pack RunAs Profile” Run As Profile

 

If you are configuring the VMware Management Pack in a low permission environment, you might need to configure the “VMware Management Pack RunAs Profile” Run As Profile. Configuring the “VMware Management Pack RunAs Profile” Run As Profile is not necessary if the Windows account used for the Default Run As profile on Management Servers already has sufficient permissions to create / delete / read / write to the installation directory of System Center Operations Manager.

If the Default Run As account does not have the sufficient permissions the VMware Management Pack needs to run under a Windows account that has permissions to create / delete / read / write to the installation directory of System Center Operations Manager on all Management Servers. On System Center Operation Manager 2012 SP1 this directory usually is:

C:Program FilesSystem Center 2012Operations Manager

On System Center Operation Manager 2012 R2 this directory usually is:

C:Program FilesMicrosoft System Center 2012 R2Operations Manager

To add an account to the “VMware Management Pack RunAs Profile” Run As Profile you first need a Windows account with sufficient permission, and you need to create a RunAs account by following the steps below.

  1. Navigate to Run As Configuration -> Accounts in the Administration view and right click Accounts -> Create RunAs Account.
  2. On the Introduction Page click Next.

     

  3. On the General page in the RunAs Account type dropdown box select Windows and enter VMware Monitoring Account in the Display name text box. Optionally add a description in the Description text box.
  4. On the Windows RunAs Account page, enter the name of the Windows Account that has the appropriate permissions as described above. Enter the password for the account in the Password and Confirm password text boxes. Select the appropriate domain in the Domain text box.

  1. On the Distribution Security page select the security level that is appropriate for your organization. If you chose the More secure option, make sure you include all your Management Servers.
  2. Click Create.
  3. Click Close.

 

After creating the Run As account you need to link the Run As account to the “VMware Management Pack Run As Profile” Run As Profile. To do this follow the steps below.

 

  1. Navigate to Run As Configuration -> Profiles in the administration view.
  2. In the right pane right click VMware Management Pack Run As Profile and select
    Properties.
  3. On the Introduction page click Next.
  4. On the General Properties page click Next.
  5. On the Run As Accounts page click Add.
  6. In the Add a Run As Account dialog box, select VMware Monitoring Account from the
    Run As Account dropdown box.


  7. Click OK and click Save.
  8. On the Completion page you can choose to make use of more-secure/less-secure Run As
    account distribution. If you make use of the more-secure distribution, make sure that you
    select all Management Servers for account distribution.
  9. Click Close.

 

 

  1. Creating a VMWare monitoring user account

 

  1. On the top level object in vCenter in the view Home -> Inventory -> Hosts and Clusters right click and select Add Permission…
  1. Click the Add.. in the Assign Permissions window.

 

  1. In the Select
    Users and Groups window select the user that you are going to use as the monitoring account. Click OK.

 

 

 

 

  1. Make sure that the dropdown box is set to Read-Only, and that the Propagate to Child Objects checkbox is checked. Click OK.

 

 

 

  1. Adding vCenter in System Center Operations Manager

 

  1. In the Monitoring section of the SCOM console navigate to the dashboard Monitoring -> OpsLogix -> VMWare -> VMWare IMP Configuration Dashboard.
    In the dashboard enter the server information for your vCenter server and click the Test Connect button.

  1. If the test is successful “Connected Successfully” will appear in green under the Test Connect button. Only if the connection test was successful, the Add/Update button will become available. Click the Add/Update button and the vCenter server will appear in the vCenter Servers listbox.

 

 

  1. Assigning a license to the OpsLogix VMware Management Pack

 

In order to import a license you should have received a valid license key from OpsLogix. If you did not receive a valid license key please contact support@opslogix.com or sales@opslogix.com to obtain a license key.

 

  1. In the OpsLogix License Manager in the Monitoring section of the Operations Console click the Add License button.

  1. In the Add License popup box paste the license key you received (taking care that there are no trailing spaces, empty lines, or carriage returns) and click the Import License(s) button. The license is now imported.

 

 

  1. Select the Assign tab and select OpsLogix.IMP.VMWare from the dropdown box. The vCenter servers should now appear that you added in the Operations Console earlier. Check the vCenter servers for which you would like to use the license and click the Update button.

Download OpsLogix VMware Management Pack v1.1.0.1 Installation Guide PDF