Note: If you create an SCF file twice on two different occasions , you can compare the contents of the two files. Note: If you include the. The system gathers all of the commands that make up the running configuration, and then saves the configuration to a. The system also creates a corresponding. Important: If you run a load command or restart the system before you save your changes to the stored configuration, you will lose any changes.
Note: To successfully load a configuration that you have replicated, make sure that no line of the configuration is longer than characters.
If there are more than characters in a single line, the system reverts to the previous running configuration. If a backup SCF already exists, the system appends a number to the name of the existing backup file, and then creates a new backup file. Note: You must run the save sys config partitions all command to save the running configuration in the stored configuration files. Have a Question? Follow Us. F5 Sites F5. All rights reserved.
Saves a copy of the currently running configuration to an SCF. If the file's configuration has been altered, a dialog box opens asking if you want to continue importing the file.
The current configuration and the imported configuration display next to each other, and show any configuration differences that might be found between the two files. Make sure to review all of the differences between the two files to verify that this is the configuration you want to import.
Importing past configurations for deployment Before you import past configurations for deployment, complete all areas in General Properties. Before deploying a configuration, you can roll back to previously successful deployment configurations and examine any differences between the current configuration and the past configuration.
The current configuration and the past configuration display next to each other, and show any configuration differences that might be found between the two files. A Deploy Comments popup dialog box opens where you can enter information specific to the successfully deployed past configuration.
Exporting configurations for deployment Before you export configurations for deployment, complete all areas in General Properties. You can export previously successful deployment configurations as JSON files and examine configuration settings prior to exporting it to your local system. The Export Configurations screen opens. Note: If you do not have any previously saved deployments, no information displays.
The configuration information you selected to export is downloaded to your local system as a JSON file, and can be imported and used to deploy configurations in other Herculon SSL Orchestrator environments.
0コメント