Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Unable to monitor over 100 ESX(i) nodes in NPM

Unable to monitor over 100 ESX(i) nodes in NPM

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 720 Votes: 1 Revisions: 8

Issue:

If the number of ESX(i) nodes monitored goes above 100, the VIM polling-rate error notifications appear.

Cause:

VIM polling has a limit of 100 ESX(i) at the default polling rates, after this point VIM starts to adjust the polling rate.

Resolution:

The following steps will set all the ESX(i) polling rate to 20 minute collection intervals for the existing and new ESX(i) servers. The default value is 5 minutes (300 seconds). By setting the value to 1200 seconds, you will be able to poll 4 times the number of ESX(i) servers.

Note: Before doing any work on your database please make sure that you have a current backup, as this will make permanent changes to your database - How to Backup Orion Database.

  1. Click Start > All Programs > Solarwinds Orion > Advanced Features > Database Manager.

  2. Click Add Default Server.

  3. Right-click on the database, and then select New Query.

  4. Paste the following query, and then click Execute Query:

    UPDATE VIM_PollingTaskTypes SET PollingInterval = 1200
    UPDATE VIM_PollingTasks SET PollingInterval = 1200
  5. Click Save.
Last modified

Tags

Classifications

Public