Forum Discussion
Jeremy_Bridges_
Nimbostratus
NimbostratusSCOM and F5 Performance Monitors
We are trying to use SCOM in combination with a F5 LTM to solve most of our monitoring needs. However, we have run up against a strange issue. It seems a few of the performance monitors have some settings that cause problems with the displayed health of our applications.
Essentially, a performance monitor of a pool or pool member will determine that its value is a negative number (see attachment). Because the minimum value allowed for most (if not all) of the performance numbers is zero, it causes the health of the item to be shown as critical when it really isn't (attachment shows this as well).
What causes this? Besides using an override to change the lower threshold to something lower, when can we do to fix this?
- This could be an issue on our end, but we'd greatly appreciate it if you could help us get some more information to diagnose the problem. The biggest thing we need is the trace.log file which is located in the C:\Program Files\F5 Networks\Management Pack\logs\ directory. Before sending the log however, if you can turn on the extended logging for a chunk of time, we'll have the information we need from them. To do this, first go to the installation directory (usually C:\Program Files\F5 Networks\Management Pack) and open the file called f5mpsvc.exe.config with notepad. Scroll down to a line that says something like
You will want to change "Warning" to "All" and then restart the F5 Monitoring Service in the services control manager. This should start logging verbose information to the trace.log file, which includes the data we need regarding the statistics coming in from Big3d. Leave this on for a while (maybe an hour) and then you can open up the .config file again and switch it back to "Warning".
Once you have the trace.log, zip it up and send it to ManagementPack(at)F5.com. We'll assist you from there. Good Luck!
-Dave 
Jeremy_Bridges_I have sent the trace.log. Let me know what you find. If you need anything else, don't hesitate to ask.- So I replied in another thread about this, but to make a long story short, there was a bug which produced these negative values. I've made the fix, but it won't be available until the next release (Sept). Thank you for helping us find this, and sorry for the inconvenience it's caused.
-Dave - Jeremy_Bridges_No problem. Thanks for clearing up the issue. We will eagerly wait for the September release.
