Having an issue with SW. My production environment is all virtual using VMWare ESX . I noticed that SW uses the unique ID of the volume which is my problem. Due to the virtual environment nodes tend to bounce around from host to host every once in a while. This process creates new IDs for each volume, solarwinds doesn't acknowledge the change and continues monitoring that drive (which is now down). I have around 500 virtual servers all with multiple drive letters. Its hard to keep the monitoring updated and correct. When a drive goes down it shoots out an email and since I have a large environment I get flooded with emails and sometimes miss some, the new drive IDs have to be readded manually one at a time and I have to create all new custom properties for the drives. Is there a way to have SW look at just the drives on the node rather than polling a unique ID?
Still an issue... Trying to figure out WHY the volume ID keeps changing. Nothing in Event Viewer, Cluster Manager, or VMware shows any relevant information at the time it dropped off.
I dont think you'll get a straight response for this query - as its a known fact
You will have to look for workarounds, I am pasting a couple of help thread's - you will have to tweak it or try something better
You will either have to cleanup unknown volumes and find a way to discover volumes automatically OR you will have to extend FIxOrionVolume.ps1 to check for both down + unknown volumes and fix it
you could also increase the interval in which your discovery scans run. This would be the easy way to solve this albeit not the most elegant.
Orion Platform 2019.2 includes the ability to automatically delete these 'unknown' volumes. For more information, check the link below.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.