VIM.BusinessLayer.Log Chock Full of VMWare Node Not Orphaned WARN messages

xtraspecialj

I mean.  Great.  So the node isn't orphaned.  That kind of sounds like a good thing, right?  So why do I have nearly 10,000 lines in each of my VIM.BusinessLayer.Log files containing nothing but WARN messages saying that a VMware node exists and that it's not orphaned?

It will contain dozens of these messages in a row for each NodeID found in this log.  It's really weird.  Is there a way to fix this?  I didn't notice this prior to upgrading to NPM 12, so I think it may have started after the upgrade, but I may have not been paying attention before.  I've looked at several of the node ID's mentioned in the file and they are just virtual machine nodes in Orion with nothing remarkable about them, so I don't get why I am being warned that the node exists and it's not orphaned...

It doesn't seem to really be affecting anything as far as I know, but maybe it is and it's not apparent.  The reason I discovered this is because the VIM BusinessLayer plugin just crashed while trying to create a discovery but all that is in the log file for that plugin is 10,000 lines of these WARN messages.  So maybe it is affecting something and it caused the VIM Business Layer to crash.  Either way, I can't imagine it's a good idea for it to be wasting resources writing thousands of lines to the log message every couple of minutes for something that doesn't really seem important.

To add a bit more context, each NodeID I've found in this file usually has 81 consecutive lines each before it starts "warning" me about the next node ID that isn't orphaned.  Some NodeID's only have 54 consecutive lines and a very small amount have 27.  Notice that all 3 of those are divisible by 27 (27 x 1 = 27, 27 x 2 = 54, and 27 x 3 = 81).  The reason why I mention that is not because there could be some retry value set that has the ophanedVMwareNodesProcessor retry each node a set amount of times. 

Here is an extremely small sample:

2016-11-16 11:15:02,537 [420] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:02,661 [351] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:02,833 [325] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:02,958 [365] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:03,036 [416] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:03,176 [325] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:03,285 [26] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:492, infrastructureType:Unknown]2016-11-16 11:15:22,722 [312] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:22,768 [437] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:22,831 [325] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:22,893 [325] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:22,940 [325] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:22,987 [28] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:23,034 [28] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]2016-11-16 11:15:23,065 [312] WARN  SolarWinds.VIM.BusinessLayer.Polling.OrphanedVMwareNodesProcessor - Node exists, vmware node not orphaned [nodeId:1689, infrastructureType:Unknown]

xtraspecialj

To add some more info and a touch more mystery to this post, I queried the Nodes table for all of the 32 distinct NodeID's found in this log file and I joined the Nodes table to the VIM.VirtualMachines table too.  What I found was that most of the NodeId's were found in the VIM.VirtualMachines table.  I did find 10 NodeID's not in the VM table, but I don't see anything remarkable about these 10 that would tell me why VIM isn't matching them up to their corresponding Nodes in Orion.  Their Names and IP addresses in the VM table matches the Caption and IP_Address fields in the Nodes table exactly. 

The 22 other Nodes that are in both the VM and Nodes table though means that I have no clue why this log file is singling these 32 NodeID's out to inform me that they aren't orphaned.  Especially since 10 of those 32 seem to actually be orphaned...  So not only do these log entries seem to be wildly irrelevant since they are warning me about Node's not being orphaned, the log entries aren't even correct since 1/3 of the not-orphaned nodes are in fact, orphaned...  What the heck??