jumebv

Bouke Groenescheij

My personal adventures in the quest for virtual perfectness.

  • Home
    Home This is where you can find all the blog posts throughout the site.
  • Categories
    Categories Displays a list of categories from this blog.
  • Tags
    Tags Displays a list of tags that have been used in the blog.
  • Login
    Login Login form

VCOPS: 5.7.1 fix for VIN (blacklist)

on
  • Font size: Larger Smaller
  • Hits: 67789
  • 0 Comment
  • Subscribe to this entry
  • Print

In the release notes for VCOPS 5.7.1 one of the fixed issues for VIN is:

"vCenter Infrastructure Navigator adapter discovers too many resources
The vCenter Infrastructure Navigator adapter was configured to discover and calculate resources related to obscure open TCP ports. This configuration increased the load on analytics processing as well as on the storage sub-system that stores this data."

Great! This was one of the issues when running 5.7.0 together with VIN 2.0. ALL the TCP links were also added as a resource in VCOPS. All VMware did is 'blacklisting' the TCP links. The blacklisting and whitelisting was introduced on the VIN adapter in 5.7.0, however, I guess a correct configuration didn't get into that release.

If you still feel there are too many objects being passed from the VIN adapter to VCOPS, you can alter the filterList.txt on the ANALYTICS VM:

# vi /usr/lib/vmware-vcops/user/plugins/inbound/vin_adapter3/conf/filterList.txt

Configuration is quite clear. You can use regular expressions on the name of the resource to stop passing it from VIN into VCOPS.

Take a look at the default content:

# Header syntax:
# [[AppComp|Application] mode=[blackList|whiteList]]
#
# mode: [whiteList|blackList]
# - blackList: vin adapter ignores specified entries.
# - whiteList: vin adapter only reports specified entries.
# AppComp section:
# - Specify product name of application component using regular expression
# - One entry per line.
# - If mode is blackList, matching AppComp will be ignored regardless if its has incoming dependency.
[AppComp mode=blackList]
Service on tcp/\d+

# Application section:
# - Specify application definition name using regular expression
# - One entry per line.
[Application mode=blackList]

As you can see there a two parts, an 'AppComp' section and an 'Application' section. To identify where you should put your filter, check your resources (Environment, Environment Overview) and then the 'Identifier 2' column. Check this screenshot:

The 'vSphere Management' recources are an 'Application' from VIN, the 'Service on TCP' resources are an 'AppComp' from VIN. So if I would like to filter out those 'vSphere Management' resources I would add the following line to [Application mode=blackList] section:

vSphere Management-\d+

After that, restart the VCOPS services (including the important Collector Service):

/etc/init.d/vcops restart

Cleanup

Note that the discovered resources are not deleted from the database. This means they will still be included on your nightly recalculations taking more time. You can delete them from this interface by shift clicking multiple entries an click 'Delete Resource'. That keeps your database clean an tidy - be carefull not to remove too much Wink.

In my small lab environment I went from 213 recources to 132, removed 81 resources. Can you imagine the saving on large enterprise environments?

 

Last modified on

Comments

  • No comments made yet. Be the first to submit a comment

Leave your comment

Guest Saturday, 27 May 2017