For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jeremy_Bridges_'s avatar
Jeremy_Bridges_
Icon for Nimbostratus rankNimbostratus
Aug 18, 2009

SCOM 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 se...
management
microsoft
scom
Dave_Ruddell_79's avatar
Dave_Ruddell_79
Historic F5 Account
Aug 19, 2009
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