For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

kridsana's avatar
kridsana
Icon for Cirrocumulus rankCirrocumulus
Oct 08, 2015

Did GTM+LTM need to remove from sync group before Upgrade HF?

Hi

 

I've plan to upgrade HF GTM+LTM (provision 2 module) from 11.4.1 HF3 to 11.4.1 HF9

 

I've 4 GTM+LTM (First pair at site one , another two at site two), It's all in GTM sync group .

 

Did I need to remove GTM from sync group in site one before upgrade?

 

Or can I Just upgrade both GTM in site one ... and then Upgrade GTM in site two respectively ?

 

Thank you very much

 

BIG-IP DNS
design
hot fix
TMOS
upgrade

2 Replies

  • kridsana's avatar
    kridsana
    Icon for Cirrocumulus rankCirrocumulus
    Oct 08, 2015

    Hi Hannes

     

    Can I use this plan?

     

    In Main site have 2 F5 with redundant pair (Active-standby) 1. Upgrade Standby unit (Unit 2) 2. reboot standby unit to newly upgrade 3. failover 4. Perform upgrade on Unit not yet upgraded (Perform step 1-2 on Unit 1)

     

    Then I've to wait for another day to perform upgrade at Another site (Another DC) with 2 F5. And perform the same step I've done with Main site.

     

    Is this plan work?

     

    Thank you very much

     

  • Hannes_Rapp's avatar
    Hannes_Rapp
    Icon for Nimbostratus rankNimbostratus
    Oct 08, 2015

    No need to do that. During the upgrade, make sure you have 1 appliance active/operational at a time, put the other 3 in "Forced Offline" state.

     

    I'd recommend the following procedure:

     

    1) Sync configurations in all sites

     

    2) Put 3 standby nodes to "Forced Offline" state. Only the active node of active site should be left operational

     

    (license reactivation not needed in case of HF install)

     

    3) Install the Hotfix, and once done, reboot all 3 nodes to the partition where the new Hotfix is installed

     

    4) Confirm all works as expected, and release the "Forced Offline" state

     

    5) Issue a cluster failover in the active site

     

    6) Repeat 2,3,4 with the node not yet upgraded

     

    7) Sync configurations in all sites