Export command, bigpipe
From NetworkCommands
A command available on most F5 BigIP platforms; used to create a Single Configuration File (SCF) that can be used either as a configuration backup or to configure another device. SCF files contain the LTM and Linux operating system configuration.
Contents |
Usage Syntax
bigpipe export [path/]filename
Usage Examples
bigpipe export /tmp/test - create an SCF file called test.scf in the /tmp/ directory
bigpipe export test - create an SCF file called test.scf in the /var/local/scf/ directory
Usage Notes
Unless you specify a path, files will be saved to: /var/local/scf/
There is no need to specify the .scf extension, this will be added automatically.
If you don't specify a file name the command outputs to the screen/terminal instead.
This command is very different to the bigpipe save command which saves the running configuration to the device's local configuration files. This command will not do so.
This command is similar to the bigpipe config command which creates UCS files containing only the LTM configuration.
You cannot use bigpipe export help to view the help page for this command as this will create a help.scf file. Use man export instead.
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 import command is used to import existing SCF file on a device.
The bigpipe config command creates User Configuration Set (UCS) files containing only the LTM configuration and also synchronises configurations between devices in a HA pair.
The bigpipe save command saves the running configuration to the device's local configuration files.
Availability
v9.4 onwards
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.
 We really do appreciate all feedback so please do send your comments, suggestions or corrections to steve#networkstuff.eu (replacing the # with an @)
|
