bigpipe config sync vs bigpipe config sync all

I think 'b config sync' and 'b config sync all' are the same. The current full config running in memory is saved to a UCS file, copied to the peer and loaded. The difference seems to be between 'b config sync (all)' and 'b config sync min'. The latter just saves the current running config to the /config/bigip.conf file, copies that to the peer and loads it. The min operation doesn't include the SSL certs/keys, or any of the following files:

 

 

/defaults/config_base.conf.

 

/config/bigip_base.conf.

 

/config/bigip_sys.conf.

 

/usr/bin/monitors/builtins/base_monitors.conf

 

/config/profile_base.conf.

 

/config/daemon.conf.

 

/config/bigip_local.conf.

 

 

Unless you have some specific reason to sync just the bigip.conf, I'd suggest using 'b config sync'.

 

 

Aaron