save your configuration after making any changes using the 'bigpipe' command:
# bigpipe save all
# this command will save 3 different files.
[root@bigip:Active] config # b save all
/config/bigip_base.conf was renamed to /config/bigip_base.conf.bak (62 lines).
/config/bigip.conf was renamed to /config/bigip.conf.bak (1643 lines).
/config/bigip_local.conf was renamed to /config/bigip_local.conf.bak (0 lines).
# bigpipe save
# this command will save 2 different files.
[root@bigip:Active] config # b save
/config/bigip.conf was renamed to /config/bigip.conf.bak (1643 lines).
/config/bigip_local.conf was renamed to /config/bigip_local.conf.bak (0 lines).
I tend to use 'b save all' out of habit. though, which, logically, you only need to use when using bigpipe command changing the bigip_base.com file. 'b save' works just as well for most cases. I'm really not sure why there is a difference. to be on the save side; it is usually a good idea to save *all* of your work.
some changes are not runtime, and need to be loaded in order for the switch to take the new configuration:
# bigpipe load
# this command will load all of your configuration files
[root@bigip:Active] config # b load
Reading configuration from /config/bigip_base.conf.
Reading configuration from /usr/bin/monitors/builtins/base_monitors.conf.
Reading configuration from /config/profile_base.conf.
Reading configuration from /config/daemon.conf.
Reading configuration from /config/bigip.conf.
Reading configuration from /config/bigip_local.conf.
Loading the configuration ...
as you can see. there 3 additional files loaded than just the one backed up from a 'b save all'. there are some changes that require a restart of the LTM base:
# bigstart restart
[root@bigip:Active] config # bigstart restart
[root@bigip:INOPERATIVE] config #
[root@bigip:Active] config #
the terminal will return after being unreachable for a short time. wait a few more moments and hit <enter> a few times to confirm the load balancer has recovered into 'active' mode.
if you see any errors running this command from the console interface, you should probably contact support and get the issue resolved as quickly as possible.
only a handful of cases require a complete reboot of the system. usually limited to system level changes such as code upgrades and hotfixes.
# full_box_reboot
Comments