This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Managed Node not showing in virtualization tree

austinjpoirier over 6 years ago

Hello,

I was hoping someone may be able to chime & and provide some ideas.

We are monitoring 2 vCenter vShere 6 linux appliances through vCenter. This is great for me as I can see the whole VM Tree. The clusters, then the hosts, then the VM Guests. The issue I am experiencing is upon expanding the tree some virtual machines are showing as 'not managed' (grey/italicized) however if you search for that node name in Solarwinds the server is in Solarwinds and collecting stats. When I go to add the machine it will first say 'node is not being managed by solarwinds, do you want to manage this node' I say yes, but when I put the WMI credentials/IP in, it says this node is already in Solarwinds 'view node detail'. I noticed that NEW VM Guests I add in this cluster work fine. It shows the whole VM tree from the cluster to the host to the virtual machine, however when I go to these nodes that are not being recognized as 'managed nodes' through virtualization summary the only thing it shows is 'home' under the node summary view.

It is worth noting that we used to have VIM but no longer do.

If anyone has any suggestions please throw them my way!

Please note I crossed out the specific server names for security reasons but the vm in the top circle is grey (unmanaged), and the one below it is blue (managed), however the grey unmanaged one is a managed node.

node details.JPG

Top Replies

0 grantallenby over 6 years ago

It should pick it up automatically but have you checked that the grayed out node that is being monitored has ticked poll for VM and is using ESX credentials? it might have got confused due to it being already polled through say WMI and not correctly tied the fact its part of the vCentre.
Stranger things have happened with our Solarwinds instance
Cancel
Vote Up 0 Vote Down

Cancel
0 austinjpoirier over 6 years ago in reply to grantallenby

There are guests on 'x' host that are being managed through WMI. All of the VMhosts are being polled through vCenter.
This is only happening for servers that were already in Solarwinds before I setup the Virtualization Manager tree to poll through vCenter.
The weird part is we have servers that were already managed by Solarwinds that went and found their spot in the tree. Its just certain nodes.
Cancel
Vote Up 0 Vote Down

Cancel
0 mesverrum over 6 years ago in reply to austinjpoirier

In a few cases I have seen the synchronization between the the orion.nodes tables and the orion.vim.virtual machines get screwed up, and cause effects like this. The obvious clue would usually be when the nodeid column is null for the vm, so the IVIM side of orion says this vm has no related nodeid in the db, we should have you add it. Then when you click to add it the add nodes interface is working strictly from the orion.nodes tables where it does find a node with the matching IP address already in the list. It would be useful if there was a way to just manually map a nodeid to a VM in cases where you noticed a problem.
In the past when I ran into this support had me break the VMAN integration, get everything cleared from the vim tables (vcenters and hosts and vm's and everything), then add the vcenter back in and wait for it to populate all the child hosts and vm's from there. I think that things get especially messy in cases where you polled the esx hosts directly and then later switch the polling to be from the vcenter.
Cancel
Vote Up +2 Vote Down

Cancel
0 austinjpoirier over 6 years ago

I was able to resolve this with the assistance of support.
You have to delete the node.
Then go into Virtualization tab
Expand the tree and find the node. I left the box 'poll for vmware' checked not sure if it mattered.
Node was re-added that way. It showed up immediately.
The issue was related to Solarwinds essentially the node was being written to 2 different database tables. It sounded like support knew about it & were going to address it with a new release.
Cancel
Vote Up +2 Vote Down

Cancel