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

Charles_Harris's avatar
Charles_Harris
Icon for Nimbostratus rankNimbostratus
Feb 05, 2008

Is it advisable to config sync after iControl updates?

Just a quick question....     We use iControl to manipulate node session states & pool member states from within our applications: Is it a good idea (time / resources / performance etc) to do a ...
dev
devops
iControl
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Feb 06, 2008
If you're disabling a node on one unit, it would make sense to synchronize the change to the peer to ensure it has the same configuration in case you needed to fail over to it. If you're only making changes to the high level configuration (the bigip.conf), you could just save that (like running a 'b save') and then sync the config (like running 'b config sync').

 

 

 

http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&forumid=1&postid=2655

 

 

System.ConfigSync.save_configuration (SaveMode), where

 

SaveMode = SAVE_HIGH_LEVEL_CONFIG will save the configuration to /config/bigip.conf (similar to "b save")

 

SaveMode = SAVE_BASE_LEVEL_CONFIG will save the configuration to /config/bigip_base.conf (similar to "b base save")

 

 

 

 

Aaron