Forum Discussion
Kevan_Brown_504
Nimbostratus
NimbostratusDevice Statistics Processing Failure
Environment:
OS: Windows Server 2003 R2 x64
SCOM: SCOM 2007 R2
SCOM Topology: Single management server, single management group
F5 MP: 1.4.0
Issue:
After installing the F5 MP and discovering a couple of BIG-IP's in an HA configuration, I get a SCOM alert after a while for "Device Statistics Processing Failure". In the F5 Monitoring Log event log, I have the following two warning events:
Event ID: 401
Event Type: Warning
Event Source: F5 Events
Event Category: None
Event Details:
The PerformanceDataSourceConnector connection to Operations Manager Health Service host localhost was lost: Failed to write to an IPC Port: The pipe is being closed.
Event ID: 806
Event Type: Warning
Event Source: F5 Events
Event Category: None
Event Details:
Unable to process device [F5 Device [1.1.1.2]] statistics due to data failure: The PerformanceDataSourceConnector connection to Operations Manager Health Service host strvascom01 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: scomserver01
Also, the "F5 Management Pack Monitoring Services" state view shows the "F5.MonitoringService" in a critical state. The "F5 Monitoring Service" Windows service is, in fact, running.
Attached are the output of the SystemInformation.ps1 PowerShell script and the trace log.
Any assistance in resolving this issue is greatly appreciated.
Thanks,
Kevan
7 Replies
- Hey Kevan,
Thanks for getting those logs to us, they help a lot. We had put in a fix due to your previous issue, which we are pretty sure is completely related. We are now getting the visibility we were hoping for. Can you do us a big favor and turn on verbose logging for a couple of hours and send us the new logs. We want to see the raw data coming in from the Big-IP(s).
Here are the steps you should follow to turn on verbose logging:
1. Open up the C:\Program Files\F5 Networks\Management Pack\ folder (or wherever you installed to).
2. Locate the file named f5mpsvc.exe.config.
3. Create a backup copy of the file. (from a command shell shell: "cp f5mpsvc.exe.config f5mpsvc.exe.config.bak").
4. Open the original file in a text editor. (from a command shell window: "notepad f5mpsvc.exe.config").
5. Locate the following line towards the bottom of the file:
6. Change "Warning" to "All" so that it reads:
7. Save and close the file.
8. You shouldn't have to, but you may want to restart the F5 Monitoring Service just to make sure the config file loads.
Good luck, and thanks for your patience,
-Dave 
Kevan_Brown_504Just changed the config file based on your guidance and restarted the F5 Monitoring Service. I will upload the new trace log after a couple of hours.
Yes, I did install to the default path of "C:\Program Files\F5 Networks\Management Pack", because I found that if you don't, the tasks (such as the discovery wizard) fail to launch as they refernece that specific path. Maybe you shouldn't even give the user this choice when installing the management pack if changing this value will result in erratic behavior.
Thanks in advance for your continued assistance,
Kevan- Kevan_Brown_504The verbose trace log is 20MB+ in size and ~1.5MB compressed. This is too large to post in this forum. Do you have a place where I can upload the compressed file for you?
Thanks,
Kevan - Hi Kevan,
You can mail the attachments to ManagementPack (at) F5 (dot) com, and we'll review the contents, and post back here with the results.
Thank you,
Stephen
Manager, Product Development - Kevan_Brown_504Just in case the folks who've been replying are not the same on that e-mail address, I sent the verbose trace log to that e-mail address last night shortly after 9pm (Eastern) or so.
Thanks,
Kevan - Hi Kevan,
Yes, we received your trace log. We'll let you know what we find.
Thank you,
Stephen
Manager, Product Development - Kevan_Brown_504FYI, I upgraded to 1.4.1.93 on 10/1/2009 and still received a "Device Statistics Processing Failure" alert and the 401 and 806 warnings in the Application event log.
