BIG3D restarting after MP discovers 9.3.0

We resolved the issue by upgrading the LTM's to 10.1 code.

Thanks for the update! Was the upgrade on the ltm's uneventful?

My understanding from our Network guy is the upgrade had to happen in multiple steps... Upgraded to BIG-IP 10.0.1 Build 283.0 and then to BIG-IP 10.1.0 Build 3341.0. I guess there isn't a direct upgrade path.

As RPriesing mentioned, upgrading to a newer version of the BIG-IP platform will fix the big3d coring problem, when discovering devices on v9.3.0 and v9.3.1. We were able to reproduce this problem with F5 Management Pack distributions up to the latest version (v1.7.0.390). To be sure that your problem (of big3d restarting) is the same that we're experiencing, while discovering a 9.3.x device, you can check the /var/log/gtm file on your F5 device, which should report a similar log with:

Apr  8 12:32:10 bp2400-108 big3d[3449]: 012b0001:5: big3d exiting ===============================
Apr  8 12:33:04 bp2400-108 big3d[9401]: 012b0000:5: big3d started ===============================
Apr  8 12:33:37 bp2400-108 big3d[9401]: 012b6010:3: MCP returned an error - possible invalid mcp tag in client request
Apr  8 12:33:37 bp2400-108 big3d[9401]: 012b6010:3: MCP returned an error - possible invalid mcp tag in client request
Apr  8 12:33:38 bp2400-108 big3d[9401]: 012b6010:3: MCP returned an error - possible invalid mcp tag in client request
Apr  8 12:59:12 bp2400-108 big3d[9475]: 012b0000:5: big3d started ===============================

basically complaining about an invalid mcp tag in the client request. You can also send us the log to managementpack(at)f5.com, if you think you may have a different problem and we can further investigate.

To be on the safe side, on addressing the big3d coring problem with the F5 Management Pack discovering v9.3.x BIG-IP, I would recommend following RPriesing's advice to upgrade to v10.1 (or later) the F5 device.

Thank you.

Julian