Configuration Upload over HTTPS

Support has been added for uploading of a copy of the running configuration file or the startup configuration file from a FastIron device to an HTTPS server. HTTPS configuration upload works in a simple process.

After the copy startup-config https or copy running-config https command is executed specifying the URL to be used to upload ether the startup configuration or the running configuration to a remote HTTPS server, either the running configuration is generated or the startup configuration is read from flash memory. An HTTP PUT request is issued to the URL of the server, along with the contents of the running or startup configuration in the body of the request. The URL is in the form of path/filename. The remote server handles this request. The application on the server receives the configuration and stores it, typically in a file or a database. The server responds with status code 204, indicating success.

Considerations for uploading a configuration file over HTTPS

  • The remote end must have a web service to upload the data in the HTTPS request and store it remotely in a database or file system. The web service must accept the URL specified in the HTTPS request.
  • The HTTPS client uses the device certificate.
  • The Content-Type header is set to plain text.
  • Configuration upload over HTTPS is not available in FIPS or CC mode.

Uploading the running configuration to a web server

The following example uploads a copy of the running configuration file from a device to the HTTPS server, and specifies port 200.


device# copy running-config https 10.1.1.1 upload/backup.cfg port 200

Uploading the startup configuration to a web server

The following example uploads a copy of the startup configuration file from a device to the HTTPS server. Because no port is specified, the default of 443 is used.


device# copy startup-config https 10.1.1.1 backup/icx.cfg