Forum Discussion
bstickel_12435
Nimbostratus
NimbostratusF5 Event 806
F5 MP 2.1.0.43
LTM 9.3.1
Every minute get this for cpu_info:
(Data)Unable to process device [F5 Device [xxx.xxx.xxx.xxx]] statistics due to data failure: Could not look up entity info based on statistic: IP=xxx.xxx.xxx.xxx Statistic=(stats)(time)1274286864(/time)(type)cpu_info(/type)(name)0(/name)(slot_id)0(/slot_id)(cpu_usage_ratio)100(/cpu_usage_ratio)(user)296431053(/user)(niced)5535(/niced)(system)157421470(/system)(idle)201098(/idle)(irq)1677(/irq)(softirq)109818(/softirq)(iowait)1619316(/iowait)(tm_user_cycles)289280938(/tm_user_cycles)(tm_system_cycles)153726349(/tm_system_cycles)(/stats)(/Data)
Thanks,
Brian
- Hi Brian,
The warning that you get about the cpu_info device statistic is caused by the fact that with a 9.3.1 LTM platform there is no direct support in the F5 Management Pack for getting the cpu_info device CONFIGURATION from the F5 device. This is a known problem when discovering a 9.3.1 platform and we're looking into addressing this issue in a future release of our F5 Management Pack, either by providing a better user experience (by suppressing the warning in this particular case) or possibly attempting to fix the cpu_info device configuration discovery for LTM v.9.3.1. As you probably noticed, I mentioned CONFIGURATION when failing to retrieve the cpu_info. STATISTICS would still be collected (as you can see in your logs/warnings), but obviously they are useless in your case. This is rather a 9.3.1 platform related inconsistency which has been fixed in newer LTM platform versions.
This being said, you can either disregard the warnings or better, you can completely disable the collection of cpu_info related stats, alltogether, in our F5 Management Pack. You would do this following the step-by-step procedure described in the "Performance Collection and Monitoring" article: http://devcentral.f5.com/wiki/default.aspx/MgmtPack/PerformanceCollectionAndMonitoring.html, in the "Subscribing to Device Statistics: Collection Rules" section. In your case you will look for the CPU info collection rule and creating an override with disabling it. This would make the warning go away.
Let me know if this works for you, at least for the time being, or if you need further assistance.
Thank you,
Julian - Hi Brian,
Just to keep you updated, we have a fix for this problem and we're looking into including it in our next release of the F5 Management Pack. The fix is related to the big3d agent (part of the LTM platform), and with the upcoming release of the F5 Management Pack you will have to authorize the update of the big3d agent (shipped with the F5 MP) on the LTM v9.3 platform. You have this option in the F5 Device discovery user interface in SCOM (or f5mpcmd command line utility). With the new big3d agent in place, the F5 device discovery will correctly process the cpu_info configuration and stats, so you won't see any errors / warnings about this issue anymore.
Thank you for your patience.
Julian 
bstickel_12435Hi Julian,
Thanks for the update. What is the time frame for the next release?
Thanks,
Brian- Hi Brian,
The next release of the F5 Management Pack is scheduled to be out very soon, in the first half of June 2010.
Julian - Brian,
We have just released a new version of the F5 Management Pack that includes a number of fixes, including the one for the issue you've been having.
You can download this release from: http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/54/aft/1174022/aff/2301/afv/topic/showtab/groupforums/Default.aspx
Let us know if this works or if you still run into any issues.
And thank you for your patience through all of this!
Julian - bstickel_12435Hi Julian,
Still getting the same errors with both 2.1.1.140 and 2.1.2.187. Did a manual update of big3d to 10.2.1.3.0 as well.
Thanks,
Brian - Brian,
Please archive and send us (to managementpack(at)f5(dot)com) the following logs:
- F5 Monitoring Log (in the Event Viewer > Applications and Services Log)
- /var/log/gtm (on the F5 device discovered by the F5 Management Pack)
I'm not sure exactly why the 806 events are still showing up, with the update of the big3d to v10.2.1.3. Our tests with the LTM platform v9.3.1 couldn't produce this behavior with the latest big3d, but I'll re-run the tests and double-check.
Julian 
sooner_man79_86I as well am still getting F5 Event ID 806 every minute. Just upgraded today to F5 MP 2.1.2.187. BIG-IP is ver. 9.3.1- If you have forced the big3d agent update on the F5 device and you still get the 806 error, please provide us the logs requested in my previous post:
- F5 Monitoring Log (in the Event Viewer > Applications and Services Log)
- /var/log/gtm (on the F5 device discovered by the F5 Management Pack)
You can send the logs to managementpack(at)f5(dot)com
Thank you.
Julian - sooner_man79_86I don't have access to update the big3d agent. I will have to get with our network engineering team. Is that a simple step that is done on a frequent basis?
