Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > After integrating with Virtualization Manager, storage data is missing in the Orion Web Console

After integrating with Virtualization Manager, storage data is missing in the Orion Web Console

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

Views: 74 Votes: 0 Revisions: 8

Issue:
All storage data is missing in the Orion Web Console after integration with Virtualization Manager. No datastores and historical statistics are available, and charts display the message: No Data.

Before you begin:
Before you proceed with the resolution, confirm that you experience this exact issue by performing the following steps:

 

  1. Run the following SQL query against the Orion database: SELECT * FROM Engines
  2. In the IP column, you should see the IP addressess assigned to each poller. If this IP address is not reachable from Virtualization Manager, it means that Virtualization Manager cannot send the data to the Orion database.

 

VMan master.log
2016-03-22 11:52:51,638 [pool-20-thread-1] ERROR com.solarwinds.vman.orion.collector.JobResultDispatcher:138 - sending results to VIM failed
java.net.SocketTimeoutException: connect timed out 

 

Resolution:
To resolve this issue, perform the following procedure:

 

Option 1:

  1. Create a backup of the SolarWinds.VIM.BusinessLayer.dll.config file. This file is located in the VIM installation directory. By default, the installation directory is C:\Program Files (x86)\SolarWinds\Orion\VIM.
  2. In the original SolarWinds.VIM.BusinessLayer.dll.config file, locate a line that contains the following text: <add key="SyncWizardResolvePollerByHostname" value="false"/>
  3. Modify the value to "true", and then save the changes.
  4. In the Orion Service Manager, restart all Orion services.
  5. In the Orion Web Console, go to Settings > Virtualization Settings, and run the synchronization wizard again.

 

Option 2:

1) In the adapter settings with ip 172.16.6.29, select IPv4 Properties, there open Advanced settings. Uncheck the “Automatic metric” option and set Interface metric to 1 and save the changes

 

Once you do that, wait a moment, then check Engines table to see if the table contains correct IP, if it does, re-run the synchronization wizard, that should update IP that VMan is using to send data to

 

Additionally, it may also be necessary to modify the /etc/hosts file in the Virtualization Manager appliance to make sure that it can resolve the host name of the Orion server:

  1. Open the /etc/hosts file in a text editor.
  2. Add the following entry to the file: <IP_Address> <Orion_Server>
    where IP_Address is the IP address of your Orion server, and Orion_Server is the host name of the Orion Server.

After performing these procedures, storage data from Virtualization Manager should be available in the Orion Web Console.

Last modified
21:41, 22 Jun 2016

Tags

Classifications

Public