https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMjY4IiwiaGFzaCI6IjI5ZjI1OGMzLTVmZWQtNDdlNy1hYzA0LThjZDFkYjA1ODJmZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

The service discovery portion of the SPI frequently fails due to a timeout

KB ID: 1268
Version: 5.x
Published: 2011-10-06
Last Modified: 2020-08-13

Challenge

Due to weak virtual infrastructure, the discovery process takes more time than the default timeout in the HP agent.

Cause

Performance related problems on VMware vCenter side.

Solution

Workaround is to adjust settings of the agent timeout by using the following commands:

ovconfchg -ns eaagt -set OPC_KILL_AUTO_ACTION TRUE

ovconfchg -ns eaagt -set OPC_KILL_AUTO_ACTION_TIMEOUT 1200

ovconfchg -ns eaagt -set OPC_NO_SHELL_TO_EXEC_ACTION TRUE

Restart the agent after adjusting the settings.

Also increasing the collection interval will help to decrease vCenter load.

In the VEM UI, go to the Enterprise Manager tab, and in the global collection settings set Collection Interval to 10 minutes (this affects performance metrics). Also in the Advanced settings, set NetTimeout parameter to 600 (default is 210). After making these changes, restart the collectors.

More information


KB ID: 1268
Version: 5.x
Published: 2011-10-06
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.