Forum Discussion

cmeldaq_16882's avatar
cmeldaq_16882
Icon for Nimbostratus rankNimbostratus
May 28, 2014
Solved

TMSH: Load backup configuration without restart of services, drop of connections

Hi,

 

we are using version 11.4 and would like to know if we can apply same behavior as with bigpipe in tmsh.

 

Imagine that we will make a big modification of setup (virtuals, pools, nodes, monitors, ...) and would like to have quick restore procedure. On version 10.x we simply made backup of /config/bigip.conf, perform changes and if something goes wrong we just replaced bigip.conf from backup and execute "b load" which just read the local file and revert changes back in memory.

 

Now in TMSH you have the only option "load /sys config" which will restart almost all services and also drop all connections...

 

Your ideas are more than welcome

 

Thank you

 

  • From version 11.3 onwards there is change in behavior (which I think you might be already aware). It may behave as expected when you try to load only the specific partition on which you made the changes by

    tmsh load /sys config partitions { MyExamplePartition }

10 Replies

  • I didn't think

    tmsh load sys config
    caused a service restart or connection drops. Does it do so in your experience?

  • Hi,

     

    yes, we made SSH connection on box behind BigIP which has been dropped during load of configuration.

     

    Thank you

     

  • Yes load sys config did cause the connections to drop. But when you are making changes or updating some thing lets say pools or VS anything you can use verify/merge and write to the conf file. This will load the changes to the running config in memory. Once satisfied save config. This is the best process in my experience.

     

  • More info - The tmm deamon itself does not get affected by the reload. SO I am not sure why the traffic was getting disrupted. I had a chance to pose the same question to an F5 SME and he said may be some other deamon that effects the traffic was getting recycled. I am still trying to find out which one by doing multiple reboots and checking for uptimes on the deamons. I think that is the only way to nail this down.

     

  • From version 11.3 onwards there is change in behavior (which I think you might be already aware). It may behave as expected when you try to load only the specific partition on which you made the changes by

    tmsh load /sys config partitions { MyExamplePartition }

  • From version 11.3 onwards there is change in behavior (which I think you might be already aware). It may behave as expected when you try to load only the specific partition on which you made the changes by

    tmsh load /sys config partitions { MyExamplePartition }

  • From version 11.3 onwards there is change in behavior (which I think you might be already aware). It may behave as expected when you try to load only the specific partition on which you made the changes by

    tmsh load /sys config partitions { MyExamplePartition }