Forum Discussion
bstickel_12435
May 19, 2010Nimbostratus
F5 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 e...
Julian_Balog_34
Jul 29, 2010Historic F5 Account
Brian,
We tried to repro on our end the behavior you're reporting, on a v9.3.1 LTM Platform (build 37.1), but without success.
From the F5 gtm logs I can see that the big3d still reports unknown MCP tags (as in gtm.2.gz):
Jul 25 04:59:42 SCOLO1LTM02 big3d[9585]: 012b9000:3: Error adding rules to collection: Can't find rule for MCP tag
So it almost looks like the big3d agent is still the old one with the problem...
I assume on Jul 25th (as the log showns) you already had the lastest F5 Management Pack (v2.1.2.187) installed. I would also like to make sure that you had re-discovered the F5 Device AND you had the "Authorize Big3d Update" checked in your discovery wizard.
On these assumptions and given that you still get the Event ID 806 warnings, I still think the big3d agent has not been updated. The easiest way to check this is to SSH into the F5 device and run the following command:
iqsh localhost
This command will initiate an internal connection to your big3d agent. You should be getting a response similar to:
[root@bp1500-118:Active] config iqsh localhost9.3.1big3d Version 10.2.1.3.0linux[root@bp1500-118:Active] config
Please check the content of the element in your response, and make sure the version is 10.2.1.3.0. If it's not, then the big3d agent has not been updated by the F5 MP. And we'll need to investigate that.
Let us know the result of the iQuery Shell / iqsh command.
Thank you!
Julian
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects