Backing Up the Running Configuration

Manual Chapter : Backing Up the Running Configuration

Applies To:

Show Versions

ARX

6.3.0

Backing Up the Running Configuration

Overview

Setting a Default FTP or SCP User

Saving the Local Running Config

Saving the Global Config

Saving Both Configs

Prepared for Disaster Recovery

Restoring the Configuration

Overview

The switch configuration that you edit with the CLI is called the running configuration, or running config. You can save the running config for the next reboot, disaster recovery, or for exporting the configuration from one switch to another.The running config is divided into two major components: the local-running config for the current switch, and global config for parameters that are shared by both switches in a redundant pair. This chapter explains how to save both config types and restore them later.

Note: We recommend saving both the local-running config and the global config after every configuration change. Both configs are vital for switch replacement.

Note: In addition, to prepare for replacing a single switch in the unlikely event of a failure, you should also save the following:

Master key (extracted and wrapped). Save it to a remote host along with the configs.

Master key wrapping key password. Save it to a secure location.

Setting a Default FTP or SCP User

Before you begin backing up the configuration, you have the option to simplify FTP uploads and/or SCP transfers later. The running config exists in one or more local files, which you can copy to an external FTP or SCP server. The default FTP username/password is anonymous/upgrade-hostname, but you can enter a specific username/password for each copy. There is no default for SCP transfers. To avoid retyping FTP or SCP credentials each time, you can establish a default username and password for each transfer protocol FTP.

From cfg mode, use ip ftp-user to set the FTP username:

ip ftp-user username

where username is 1-32 characters.

From the same mode, you can also (or instead) use ip scp-user to set a default username for SCP:

ip scp-user username

where, as above, username is 1-32 characters.

The CLI then prompts twice for the password.

For example, the following command sequence sets up two default users named juser, one for FTP and another for SCP:

bstnA(cfg)# ip ftp-user juser

Password: jpasswd

Validate Password: jpasswd

bstnA(cfg)# ip scp-user juser

Password: jpasswd

Validate Password: jpasswd

bstnA(cfg)# ...

Saving the Local Running Config

The next step in saving the running configuration is to save the local running config. The local running config applies only to the current switch: this config includes network and chassis parameters. From priv-exec mode, use the copy running-config command to save the local config as an executable script.

copy running-config scripts destination-file

where

scripts is the destination directory, and

destination-file (1-1024 characters) is a name you choose for the running-config file.

For example, the following command sequence exits to priv-exec mode, copies the local running configuration to the scripts directory, then shows the new script file:

bstnA(cfg)# exit

bstnA# copy running-config scripts running

bstnA# show scripts

scripts

running Sep 19 05:03 5.7k

Saving the Config Off to an FTP Server

To save the running config off to a remote FTP server, use a URL in place of the destination-file name. Follow the URL format below:

copy running-config ftp://[username:password@]ftp-site/file

where

username:password@ (optional) is an FTP username and password (the default is the username/password set by the ip ftp-user command, described above),

ftp-site identifies the FTP server with an IP address or FQDN (for example, 172.16.88.3 or ftp.myftpsite.com), and

file is the chosen file name. Lead with an extra / if the path starts at the root of the server machine; for example, aramis//var/cfg/running-config specifies /var/config/running-config on server aramis. Omit the leading slash if the file is going to the home directory for username.

The CLI prints a message with the results of the copy operation.

For example, the following command exits from cfg mode to priv-exec mode, then sends the running config to ftp.wwmed.com:

bstnA(cfg)# exit

bstnA# copy running-config ftp://juser:jpasswd@ftp.wwmed.com/oct24lcl

% INFO: Copy config file to destination file 'oct24running' completed successfully.

bstnA# ...

Saving the Config Off to an SCP Server

For secure sites, you can upload with the Secure Copy (SCP) protocol. The URL has a different syntax for SCP transfers:

copy running-config scp://username@server:file [accept-host-key]

where

username@ (optional) is a valid username at the remote host (the default is the username set by the ip scp-user command, described above),

server identifies the SCP server with an IP address or FQDN (for example, 172.16.100.18 or deb1.mynet.com), and

file is the chosen file name. Lead with a slash (scp-server:/file) if the file path is absolute. Without the slash, the path is presumed to start in the home directory for username.

accept-host-key (optional) tells the CLI to accept an unknown host key if offered by the SCP server. The host key authenticates the server; if the key is unknown, it is possible that an attacker has taken the servers hostname and/or IP address. Note that any SCP server is unknown if the switch has not had an SCP exchange with it since the switchs last reboot.

The CLI prompts for the usernames password, unless you set up a default with the ip scp-user command. If the prompt appears, enter a password that is valid at the remote site.

Another prompt shows the results of the copy operation.

For example, the following command exits from gbl mode to priv-exec mode, then sends the running config to rh1.wwmed.com. This goes to the default users home directory, where the default user was set with the ip scp-user command:

bstnA(gbl)# exit

bstnA# copy running-config scp://rh1.wwmed.com:oct24running

% INFO: Copy config file to destination file 'oct24running' completed successfully.

bstnA# ...

Placing the Config into an ARX Volume

You can also place the config file into an ARX volume. You can use the nfs or cifs clause to send the config file to a given directory in a given volume:

copy running-config {cifs|nfs} namespace volume dest-path

where

cifs | nfs is a required choice. This is the network protocol used to transfer the config file to the ARX volume.

namespace (1-30 characters) identifies the destination namespace.

volume (1-1024 characters) is the destination-volume name.

dest-path (1-1024 characters) is the intended path from the volume root (above) to the config file. The directory you specify here must exist on the volume.

The CLI prints a message with the results of the copy operation.

For example, the following command exits from gbl mode to priv-exec mode, then sends the running-config to a directory in the medarcv~/rcrds volume:

bstnA(cfg)# exit

bstnA# copy running-config cifs medarcv /rcrds admin/oct24running

% INFO: Copy config file to destination file 'oct24running' completed successfully.

bstnA# ...

Sending the Config to an E-Mail Recipient

You can alternatively send the running-config file as an E-mail attachment. Before you use E-mail, you must configure the Simple Mail Transfer Protocol (SMTP) on the switch, starting with the smtp command in cfg mode: see the chapter on E-mail and SMTP in the ARX® CLI Reference.

Use the following syntax to send the running-config file in an E-mail message:

copy running-config smtp://[e-mail-address/]file

where

e-mail-address (optional) identifies the recipient of the E-mail message (for example, myCoWorker@myco.com). If you omit this, it defaults to the E-mail recipient set with the cfg-smtp to command. Use a slash (/) to separate this from the file name.