F5 Event 806

The simplest way for you to update the big3d agent would be to rediscover the F5 device from the System Center Operations Console and check the 'big3d agent update' check-box at the bottom of the F5 discovery wizard window. And of course the account that you are authenticating with to the F5 device should have enough privileges to perform the update. If you do this, the discovery wizard will upgrade the big3d agent 'transparently' during the device discovery process. Otherwise you still have the manual upgrade option, if you follow the Dev Central article on this topic:

 

 

http://devcentral.f5.com/wiki/default.aspx/MgmtPack/Big3dManualUpdate.html

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

Julian,

 

 

I did not do a rediscover f5 device configuration after the management pack upgrade, ran that today and the 806 events stopped.

 

 

Brian

Thank you for the update, Brian. I'm glad that the error went away.

 

Let us know if you run into any other problems with the F5 Management Pack.

 

 

Thanks!

 

Julian

I did a re-discover with the same account that I use for the initial discover and it gave me the error 'the authentication credentials are not cached with this account. Use interactive mode or cached credentials.' I had already set the device configuration token.

Have you tried to run the re-discovery task with the 'Run-as' option and use the account that you used for the initial discovery of the device? Do you still get the device configuration token error? But keep in mind, that the rediscovery task by itself won't update the big3d agent automatically on the F5 device. I would run to the rediscovery using a command prompt, and running the following command (from the folder where the F5 Management Pack is deployed, by default the %Program Files%\F5 Networks\Management Pack):

 

 

f5mpcmd /d:updatebig3d ip_address

 

 

where ip_address = the IP address of the F5 device

 

 

Julian

 

The command line discovery worked. The set device token configuration was successful. Also the re-discover was finally successful. I still get the 806 events every minute. It was mentioned that you can override the rules that try to discover these objects?

Can you doublecheck the big3d version on the F5 device? You shouldn't be getting any 806 events if the big3d agent has been upgraded to v10.2.1.3. You can follow the steps described in this post (a few replies above), about running the iqsh command on the F5 device. If you rather prefer to override / disable the rules producing the 806 warnings, you can do so by following this article: http://devcentral.f5.com/wiki/default.aspx/MgmtPack/PerformanceCollectionAndMonitoring.html and look for the specific [collection] rule that causes the problem. Are the 806 events about the cpu_info rule?

 

 

Let us know about the big3d version or if you need any assistance disabling the collection rule(s).

 

 

Julian

The simplest way for you to disable the F5 collection rule (cpu_info?), to save you the time of going through the article I mentioned above, would be to go the Operations Console > Authoring > Rules, look for the F5 rule you'd like to disable > right-click > Overrides > Disable the Rule > For all objects of another class > set the target to the "F5 Monitoring Service" and click OK.

 

 

Julian

It is the cpu_info stat that keeps throwing a Warning event. There are quite a few rules under the F5 Monitoring Service. Do you know which rule would pertain to the cpu_info? Would it be anyone that says something about 'CPU Metrics'?