Applications Systems

Change timeout interval for VM polling jobs.

This describes the procedure on how to manually configure polling interval configuration of a VM/Node that is being polled by Vmware

First published date

11/15/2018 9:30 PM

Last published date

7/21/2020 10:47 PM

Overview

This is to avoid an issue with polling timing out too quickly, where the VMware statuses will go to unknown.

Product section

Virtualization Manager

Resolution

  1. Check for any related Time out error from the VIM collector log.
    • (C:\ProgramData\Solarwinds\Logs\VIM\Jobs).
  2. If any related Time out error is present from the VIM collector log then access the Orion Database Manager.
  3. From the Database Manager, connect to your SolarWinds Database and search for the VIM_PollingTasks table.
  4. Click Execute Query to populate all results based on the default Select statement.
  5. Search for the corresponding NodeID of the VM that experience the issue and adjust the default value of the following columns to increase the time out.
    • Be sure to use the button option of " Enable Table Editing".
    • PollingInterval  (default is 600)
      JobTimeout       (default is 600)
      APITimeout       (default is 300)
  6. Save changes and click Execute Query again to confirm.
  7. Perform a manual "Poll Now' on the VM/Node in question.

Note: The propagation period depends on the capacity of the environment. Completion can probably take a few hours or days.