Forum Discussion
Julian_Balog_34
Oct 21, 2009Historic F5 Account
Problem with malformed device (big3d) version
(originally posted by: Roquencourt, Jean-Baptiste
I have done the installation with the default installation path (using v.1.4.93).
I’ve manually upgraded the big3d version.
I ...
Julian_Balog_34
Oct 21, 2009Historic F5 Account
Hi Jean-Baptiste,
You mentioned that you’ve done a manual upgrade on the big3d version. Would be correct to assume that you have not authorized the big3d version upgrade within the F5 Management Pack setup? It’s the checkbox on the bottom of the install window (see the screen capture attached).
Or, did you follow the procedure described here?
http://devcentral.f5.com/Wiki/default.aspx/MgmtPack/Big3dManualUpdate.html (Click here).
If you ran a device discovery task without authorizing the big3d update on your device, then probably the big3d version on your device is different from the one the F5 Management Pack would update to (10.0.1.600.0.0). We could find out more by looking at the trace logs, but we would recommend running the discovery with authorizing the big3d update on the device, or make sure the big3d version on the device is at least matching the one the F5 Management Pack is shipped with, or is newer.
What is the current big3d version on the device you tried to discover?
We can further assist you if you send us the trace logs related to the device discovery.
Just follow the steps described here to activate (and gather) the trace logs (see the "Verbose Logging Support" section):
http://devcentral.f5.com/Wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html (Click here).
Thanks.
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
