Forum Discussion

dstogsdill_2492's avatar
dstogsdill_2492
Icon for Nimbostratus rankNimbostratus
Jul 08, 2009

GTM-LTM Redundant Pair

I just added a new GTM-LTM as a standby redundant node to an existing and already confingured GTM-LTM. After doing this I have a couple questions i cant seem to answer from searching askF5.com.

 

 

1. I have noticed that config changes do not automatically flow from the active node to the standby node and a manual sync is required. Is there a way to setup automatic synchronizations? I'm sure this can be accomplished through scripting but I figured this would be a builtin function.

 

 

2. The changes i make to Wide IP's do not synchronize to the standby unit. Is there anything I need to check in my configuration? DNS records and Virtual Server changes synchronize just fine.

 

 

I am running version 9.4.4 Build 73.1 HF1. Any help is much appreciated.
  • I think what you might be missing is gtm_add utility. This utility is designed for situations in which you are installing the system in a networkt hat already has one or more GTM managers. Take a look at the Configuration for BIGIP Global Traffic Manager and look at pages 2-5 to 2-6, 2-9 to 2-13.

     

     

    Hope this helps

     

    CB

     

  • Thanks for the reply, however, I have used the gtm_add utility to initially synchronize the configuration and that does work. The problem is that subsequent changes made to Wide IP's on the active node do not synchronize with the standby node even though DNS and LTM changes do synchronize.
  • How about your GTM Group name setup?

     

     

    What settings are check boxes did you select or not select?

     

     

  • I'm assuming your referring to the GTM synchronization group name and options from System -> General Properties -> Global Traffic -> General

     

     

    I've attached screen shots from both units. The first screen shot is the active node while the second is the standby.

     

     

  • I finally opened a ticket with F5. They found that my ssl certificate had expired. I renewed the cert on the active node and ran the bigip_add utility on the standby node to exchange the certs.

     

    https://support.f5.com/kb/en-us/solutions/public/6000/300/sol6353.html

     

     

    It's strange how everything else synchronized but the wide IP's didnt, go figure. At least this is resolved.