We have an LTM running 10.2.3.112 code. We ran the big3d -v command and get the following:
root@rndltmcore:Active] config big3d -v big3d version
big3d Version 10.2.3.112.0 for linux big3d
version big3d Version 10.2.3.112.0
for linux What is concerning is that SCOM MGMT Pack told us it upgraded the big3d, but the LTM does not reflect that. We also know that when we upgrade the big3d, it will interrupt the communication between GTM's and LTM's, which will affect load balancing for that period. It will also affect communication between Enterprise manager and GTM's and LTM's as they are being discovered. We also know that when we do a code upgrade with a new ISO, it will replace the big3d that was manually upgraded. This could potentially impair SCOM monitoring. Looking for feedback, or comments on this subject.
We attempted discover this LTM with the upgrade box unchecked and it failed. We ran the discovery again with the box checked and it succeeded . The log message indicated that the big3d was upgraded to 1.4.
However, when we run the big3d -v command again, we get the following:
[root@rndltmcore:Active] config big3d -v