Our Linux admin is asking us for a way to have SCOM alert if a mount becomes unmounted. I checked around in SCOM and it appears as if the "Logical Disk Health" monitor should do the trick. The monitor's Product knowledge states specifically under "Cause" that : "An unhealthy state indicates that a file system has gone offline. This may be caused by a disk being unmounted."
It also says it checks the health by "inspecting the mount table to identify permanent, mounted file systems. If a mounted file system identified in a previous iteration is not included in the current enumeration, it is considered unhealthy."
However, to test this, our Linux admin unmounted a mount, and SCOM still shows it as mounted and healthy. It has been unmounted for a day now and still no luck. I've tried recalculating the health, and resetting the health, and it still comes back green. I can even still get performance data off of this mount that no longer exists, because it's probably grabbing the space of the parent mount like you would get from doing a "df -h /'mountname' " command on the server on an unmounted disk. Can someone explain why this monitor isn't working, and provide a possible way to get SCOM to alert when a previously mounted mount is no longer...mounted?
Thanks
- Edited by Alvin Cartuyvels Thursday, April 30, 2015 8:36 PM