EM 3.0.0 HF1 reports incorrect device versions

Hi Wire,

 

 

I haven't seen that. What are some of the incorrect and actual device versions?

 

 

Aaron

As an example:

 

 

On EM:

 

Host X: BIG-IP v10.2.4 (Build 595.0)

 

Data Collection Agen: big3d v11.2.0.2446.3

 

Active Boot Location: HD1.1

 

Clock Skew: 0

 

Last Refresh Date: Tue Sep 25 12:49:50 UTC 2012

 

 

On Device:

 

 

[root@X:Active:Standalone] config date

 

Tue Sep 25 13:15:38 UTC 2012

 

[root@X:Active:Standalone] config /shared/bin/big3d -v

 

/shared/bin/big3d version big3d Version 11.2.0.2446.3 for linux

 

[root@X:Active:Standalone] config tmsh show /sys version

 

 

Sys::Version

 

Main Package

 

Product BIG-IP

 

Version 11.2.0

 

Build 2557.0

 

Edition Hotfix HF2

 

 

Hotfix List

 

ID391016 ID362739 ID385457 ID389565 ID387732 ID391517

 

ID392159 ID391315 ID387264 ID388256 ID387462 ID389269

 

ID337583 ID387686 ID391313 ID388084 ID385495 ID391073

 

ID388222 ID387834 ID388670 ID388242 ID391092 ID388646

 

ID384220 ID392484 ID389111 ID386825 ID385918 ID382366

 

ID385193 ID388336 ID371880 ID385135 ID367066 ID388930

 

ID391826 ID387843 ID388514 ID391096 ID386607 ID386758

 

ID389675 ID392333 ID393721 ID383793 ID390322 ID384408

 

ID389258 ID392481 ID389345 ID387964 ID389617 ID389262

 

ID385579 ID385870 ID388130 ID387763 ID392255 ID392699

 

ID392361 ID384940 ID387811 ID386698 ID394488 ID358442

 

ID392208 ID388460 ID384228 ID388625 ID387438 ID387355

 

ID392029 ID387799 ID387471 ID394201 ID386154 ID388014

 

ID384138 ID388220 ID381620 ID391514 ID388474 ID384627

 

ID389944 ID391368 ID390951 ID365654 ID387917 ID388023

 

ID388360 ID391497 ID388678 ID392250 ID392745 ID391810

 

ID389564 ID386051

 

[root@X:Active:Standalone] config switchboot -l

 

 

Current boot image:

 

HD1.2 - title BIG-IP 11.2.0 Build 2557.0

 

Default boot image:

 

HD1.2 - title BIG-IP 11.2.0 Build 2557.0

 

Available boot image(s):

 

HD1.1 - title BIG-IP 10.2.3 Build 123.0

 

HD1.2 - title BIG-IP 11.2.0 Build 2557.0

 

HD1.3 - title BIG-IP 10.2.4 Build 595.0

 

[root@X:Active:Standalone] config

 

We encountered this too, where the EM continued to show the previously running version of code. Easiest way to get it to update is to install a new dummy partition on the target device, or remove an inactive partition, and then update the device status in the EM.

 

 

We have 18 BIG-IP devices in our environment and at least five of them presented this issue when upgrading over the past two weeks. Adding or removing a partition fixed the issue in each case.

 

 

Now if only we could get resolution to our LTM devices showing "Multiple Peers" despite not having multiple peers...

Thanks for the reply, I am currently configuring 2 EMs for 30 BIG-IPs. I just keep finding stupid bugs with them like these:

 

 

SOL13749: The Enterprise Manager (2.3.0) cannot install BIG-IP version 11.2.0 on certain platforms - Even though I upgraded to this version because I needed v11.x support.

 

 

ID 388512If you upgrade to Enterprise Manager version 3.0.0 from version 2.3.0 after importing a BIG-IP version 11.2.0 image, some BIG-IP platforms (1600, 3600, 6900, and 8900) may be listed as unsupported in the install software wizard.To work around this issue, delete the BIG-IP version 11.2.0 image from Enterprise Manager, and re-import it. - Joke!

 

 

 

This behavior seems to point to big3d and iquery, however it may be icontrol reporting incorrect versions not sure. Funny thing is that I did the upgrades using an EM 3.0.0 task, so really it should at least know which slot it instructed the device to boot to - lol

 

 

Unless anyone knows of a process that I can restart to force EM to re-evaluate the device versions I think I will have to raise this issue with support.

 

 

Also, does anyone know if there is a big3d version history document with fixes / features introduced per version. I find it difficult to explain to the customer why they have to upgrade their big3d agent from 11.2.0.2446.0 to 11.2.0.2446.3 - which of course causes GTM - LTM iquery meshes to drop - because EM has marked the newly upgraded devices as Impared with the message Data collection agent needs upgrading.

 

 

 

 

Just noticed in the Release Notes for 3.0.0 that this issue was apparently fixed:

 

 

ID 361908Now, after a device refresh, Enterprise Manager correctly updates the boot location information for the device.

 

 

Your issues with multiple peers seems to have been resolved in 3.0.0:

 

From the release notes:

 

 

ID 376474, 375942 Previously, when managing BIG-IP devices with similar mirroring configurations, Enterprise Manager sometimes displayed the message Multiple Peers on the device properties screen, even though the device had only one peer. This issue is fixed, and you should no longer see this message.

 

 

I am also running v3.0.0 HF1, and the issue is still present. F5 support has assigned bug ID 398228 to this issue. I guess they fixed it in some cases, but not all.

Upgraded to EM 3.1.1.

 

Had to remove the Device LTM(11.3) and rediscover it to correct the incorrect code and active boot volume from displaying.

 

D