Save command, bigpipe
From NetworkCommands
A command available on F5 BigIP platforms; used to save the current running configuration (in memory) to the locally stored configuration files used on system startup.
Contents |
Usage Syntax
bigpipe base save
bigpipe save [all]
See the Usage Notes section for details of the different options.
Usage Notes
All existing files are renamed filename.bak (previous .bak files are deleted.)
The bigpipe base save command should logically be bigpipe save base as currently it suggests a bigpipe base command is available, which it is not. F5 don't seem to have noticed. This option saves relevant configuration commands and parameters to the bigip_base.conf and bigip_sys.conf files.
The bigpipe save command saves relevant configuration commands and parameters to the bigip_sys.conf, bigip.conf and bigip_local.conf files.
The bigpipe save all command saves relevant configuration commands and parameters to the bigip_base.conf, bigip_sys.conf, bigip.conf and bigip_local.conf files.
All the configuration files listed here are saved in the /config/ directory.
See the Configuration Files In Detail article for details of what configuration commands and parameters are saved to each file.
Bigpipe Usage Notes
Don't forget to save your changes using the bigpipe save all command.
Note in most cases, the show keyword displays object status or statistics, the list keyword displays configuration.
The bigpipe command can be abbreviated to just b (e.g. b help instead of bigpipe help.) Alternatively, (from v9.4,) you can use the bigpipe shell to enter commands without prefixing them with bigpipe.
Where curly or normal brackets {} or () or quotes "" or exclamation mark ! are required as part of a command and you are not using the bigpipe shell, they must be proceeded with a back slash \ to prevent the bash shell from parsing them as system commands.
The bigpipe command can be abbreviated to just b (e.g. b help instead of bigpipe help.) Alternatively, (from v9.4,) you can use the bigpipe shell to enter commands without prefixing them with bigpipe.
Typical Output
[user@device-one:Active] ~ # b save all /config/bigip_base.conf was renamed to /config/bigip_base.conf.bak (96 lines). /config/bigip_sys.conf was renamed to /config/bigip_sys.conf.bak (70 lines). /config/bigip.conf was renamed to /config/bigip.conf.bak (458 lines). /config/bigip_local.conf was renamed to /config/bigip_local.conf.bak (2 lines).
Related Commands
The bigpipe config command is used to save (or restore) some of the files saved by this command and other system configuration files to (or from) a User Configuration Set (UCS) file.
The bigpipe export command is used to save some of the configuration stored in the files saved by this command and other system configuration information to a Single Configuration File(SCF.)
Command Equivalents
The Cisco command equivalent is the copy running-configuration startup-configuration command
The Extreme command equivalent is the save config command
Related Articles
See the Configuration Files In Detail article for details of what configuration commands and parameters are saved to each file.
See the File locations, F5 BigIP article for more information on the location of other files used by the system.







