Question about big3d_install script

In addition to exchanging keys (to allow iquery to use key based authentication) big3d_install also pushes out the big3d binary from the current system. When big3d (re)starts on the remote system, it checks to see if the version in /shared/sbin is newer (based on the file date), and uses that version in preference if it is.

So running big3d_install can cause a momentary disruption to the iquery mesh. If you just want to exchange keys, you can use bigip_add instead, which does the same thing, except without touching big3d.

If you've got some really tight timeouts and you happened to restart big3d at just the wrong moment, then I guess you might end up with GTM briefly marking a virtual or gtm server object as down, but there would no interaction with the LTM side of things.