No Virtual Machine elements are generated in CA Performance Manager

book

Article ID: 36883

calendar_today

Updated On:

Products

CA Virtual Assurance for IM

Issue/Introduction

Problem:

In CA Performance Manager (CAPM), in the Data Aggregator (DA), after discovering a SystemEDGE server host with a VCAIM installed, configured and running, no Virtual Machine (VM) based elements are discovered. The discovered host is considered the primary vCenter managing the VM inventory. There are VMs in the VCAIM inventory so why are they not being discovered?

 

Cause:

This is related to a unique configuration that is not currently supported as of the latest GA release r2.7.

In this instance we'll find that the inventory for the vCenter host contains other VMs that also have not just a SystemEDGE agent running, but also an active VCAIM plugin installed.

 

Solution:

How can we determine if this is the cause for the problem being observed? To do that first we must learn about what the DA seeks durng discovery from the MIB data for a vCenter server.

 

The primary vCenter in this instance is the primary server with SystemEDGE agent and the VCAIM. It is the one that is discovered before other VM hosts in CAPM.

 

To determine if the vCenter has the unsupported configuration, first we look at the vmvcAimStatVCGroup (1.3.6.1.4.1.546.16.52.2.2) table in the MIB of primary vCenter server. If there are multiple vCenter hosts being managed underneath the primary, this table will be found empty of values. If this table is empty of values, the next table in the MIB that would contain the VM inventory data is the vmvcAimStatVCTable (1.3.6.1.4.1.546.16.52.2.2.46) table.

 

CAPM discovery will only read the first table, the vmvcAimStatVCGroup table. If nothing is found in the vmvcAimStatVCGroup table the system queries for discovery data will stop there. It won't query the VCAIM MIB further for VM inventory. Due to this it also will not create any further vCenter component or device elements.

 

Following that information up by examining the MIB dump received in this instances we can see that the vmvcAimStatVCGroup (1.3.6.1.4.1.546.16.52.2.2) table is indeed empty:

1.3.6.1.4.1.546.16.52.2.1.96,vmvcAimStatGenTotalDVPortGrpCrit,0,Integer,0

1.3.6.1.4.1.546.16.52.2.2.45,vmvcAimStatVCCount,0,Integer,3

1.3.6.1.4.1.546.16.52.2.3.1,vmvcAimStatCustSpecCount,0,Integer,0 

 

Further we do indeed see the vmvcAimStatVCTable (1.3.6.1.4.1.546.16.52.2.2.46) table populated:

1.3.6.1.4.1.546.16.52.2.2.46.1.1,vmvcAimStatVCUID,1,Integer,1

1.3.6.1.4.1.546.16.52.2.2.46.1.2,vmvcAimStatVCName,1,Octet String,vc140101v.corp.scana.com

1.3.6.1.4.1.546.16.52.2.2.46.1.3,vmvcAimStatVCProduct,1,Octet String,VMware vCenter Server

1.3.6.1.4.1.546.16.52.2.2.46.1.4,vmvcAimStatVCOSType,1,Octet String,win32-x64

<<<Many more lines after that cut for brevity...>>> 

 

How can we easily determine if there are VMs with VCAIM installs being managed by the VCAIM host used as the vCenter host? By examining the vmvcAimConfigVCHostName (1.3.6.1.4.1.546.16.52.1.2.3.1.2) data. Looking at that data we see these VM servers hosted by the VCAIM server being discovered as the VCenter also have a VCAIM installed: 

1.3.6.1.4.1.546.16.52.1.2.3.1.2,vmvcAimConfigVCHostName,1,Octet String,hostName1.corp.company.com 

1.3.6.1.4.1.546.16.52.1.2.3.1.2,vmvcAimConfigVCHostName,2,Octet String,hostName2.corp.company.com 

1.3.6.1.4.1.546.16.52.1.2.3.1.2,vmvcAimConfigVCHostName,3,Octet String,hostName3.corp.company.com 

 

The presence of those entries is evidence that there are VCAIM installs on those VMs being managed by the primary vCenter with VCAIM. That is a configuration that is not yet supported by CA Performance Manager as of the latest GA release r2.7.

 

The only supported configuration at this time in CA Performance Manager is a single vCenter with no other vCenters managed underneath it.

 

If this is something you wish to see supported in future erleases of the CA Performance Manager Product, pleas submit an Idea posting to the CA Perfmance Manager public community forums for consideration.

Environment

Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator
Component: