Config command, bigpipe
From NetworkCommands
A command available on some F5 Networks BigIP platforms; used to install, check and save LTM configurations on the device itself and display synchronisation status and synchronise configurations between two devices in a high availability pair.
Contents |
Usage Syntax
bigpipe config option [filename|all]
Common options include;
- save filename - save the current running configuration to the specified filename
- install filename - replace the current running configuration with the configuration contained in the configuration file specified
- sync [all] - synchronise the current running configuration to the peer device
- sync pull - synchronise the current running configuration from the peer device
- sync show - display current configuration synchronisation status
- check [all] - perform a syntax check of the current startup configuration
Usage Examples
bigpipe config save /config.ucs - Save the current running LTM configuration to file config.ucs on the root of the file system as well as to /config/bigip.conf and saves the base configuration to file /config/bigip_base.conf
bigpipe config sync [all] - Synchronises the current running configuration to the other device in a redundant pair
bigpipe config sync show - Displays configuration synchronisation status and details of the latest configuration change
bigpipe config save all - Save the current running configuration to file /config/bigip.conf and the base configuration to file /config/bigip_base.conf - note this option is only available in older software versions and has been superseded by the bigpipe save command
Typical Output
bigpipe config sync show;
CONFIG SYNC STATUS --
Status 0 - Synchronized
Last change (Self) 2008-03-11 18:21:35
Last change (Peer) 2008-03-11 18:21:38
Last Configsync 2008-03-11 18:21:38
Usage Notes
The save all option is only available in older software versions and has been superseded by the bigpipe save command
The all keyword is optional
The sync and sync pull options will save the current running configuration to either a backup file or the startup configuratino file (depending on the type of sync operation) prior to performing any configuration synchronisation operations
Configuration archives created in the GUI are located in var/local/ucs/
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.
Related Commands
The bigpipe save command should be used to save the running configuration to the device's local configuration files.
The bigpipe export command is used to save the LTM and operating system configuration to a flat text file.
Related Articles
For further information on device file locations see the File locations, F5 BigIP article.
For further information on configuration file contents see the Configuration Files In Detail article.
Information on F5 BigIP commands 
Information on Linux commands 
Information on Cisco commands 
Information on Vyatta commands 
Information on Extreme commands 
Information on Secure Platform commands
Information on Blue Coat SGOS commands
Information on Nokia IPSO commands
 We really do appreciate all feedback so please do send your comments, suggestions or corrections to steve#networkstuff.eu (replacing the # with an @)
|
