Upgrade the Software
See the Cisco ASA Upgrade Guide for full upgrade procedures.
- Software and Configurations
- Upgrade the Software
- Load an Image Using ROMMON (ISA 3000)
- Upgrade the ROMMON Image (ISA 3000)
- Downgrade Your Software
- Manage Files
- Set the ASA Image, ASDM, and Startup Configuration
- Back Up and Restore Configurations or Other Files
- Perform a Complete System Backup or Restoration
- Configure Automatic Backup and Restore (ISA 3000)
- Back up the Single Mode Configuration or Multiple Mode System Configuration
- Back Up a Context Configuration or Other File in Flash Memory
- Back Up a Context Configuration within a Context
- Copy the Configuration from the Terminal Display
- Back Up Additional Files Using the Export and Import Commands
- Use a Script to Back Up and Restore Files
Software and Configurations
This chapter describes how to manage the ASA software and configurations.
Load an Image Using ROMMON (ISA 3000)
To load a software image onto an ASA from the ROMMON mode using TFTP, perform the following steps.
Procedure
|
Step 1 |
Connect to the ASA console port according to the instructions in Access the ISA 3000 Console. |
||
|
Step 2 |
Power off the ASA, then power it on. |
||
|
Step 3 |
During startup, press the Escape key when you are prompted to enter ROMMON mode. |
||
|
Step 4 |
In ROMMOM mode, define the interface settings to the ASA, including the IP address, TFTP server address, gateway address, software image file, and port, as follows:
|
||
|
Step 5 |
Validate your settings: |
||
|
Step 6 |
Ping the TFTP server: |
||
|
Step 7 |
Save the network settings for future use: |
||
|
Step 8 |
Load the software image: After the software image is successfully loaded, the ASA automatically exits ROMMON mode. |
||
|
Step 9 |
Booting the ASA from ROMMON mode does not preserve the system image across reloads; you must still download the image to flash memory. See Upgrade the Software. |
Upgrade the ROMMON Image (ISA 3000)
Follow these steps to upgrade the ROMMON image for the ISA 3000. For the ASA models, the ROMMON version on your system must be 1.1.8 or greater. We recommend that you upgrade to the latest version.
You can only upgrade to a new version; you cannot downgrade.
 Caution |
The ISA 3000 ROMMON upgrade for 1.0.5 takes twice as long as previous ROMMON versions, approximately 15 minutes. Do not power cycle the device during the upgrade. If the upgrade is not complete within 30 minutes or it fails, contact Cisco technical support; do not power cycle or reset the device. |
Before you begin
Obtain the new ROMMON image from Cisco.com, and put it on a server to copy to the ASA. The ASA supports FTP, TFTP, SCP, HTTP(S), and SMB servers. Download the image from:
Procedure
|
Step 1 |
Copy the ROMMON image to the ASA flash memory. This procedure shows an FTP copy; enter copy ? for the syntax for other server types. copy ftp://[username:password@]server_ip/asa5500-firmware-xxxx.SPA disk0:asa5500-firmware-xxxx.SPA |
|
Step 2 |
To see your current version, enter the show module command and look at the Fw Version in the output for Mod 1 in the MAC Address Range table: |
|
Step 3 |
Upgrade the ROMMON image: upgrade rommon disk0:asa5500-firmware-xxxx.SPA Example: |
|
Step 4 |
Confirm to reload the ASA when you are prompted. The ASA upgrades the ROMMON image, and then reloads the operating system. |
Downgrade Your Software
In many cases, you can downgrade your ASA software and restore a backup configuration from the previous software version. The method of downgrading depends on your ASA platform.
Guidelines and Limitations for Downgrading
See the following guidelines before downgrading:
-
There is no official Zero Downtime Downgrade support for clustering—However, in some cases, Zero Downtime Downgrading will work. See the following known issues for downgrading; note that there may be other issues that require you to reload your cluster units, thus causing downtime.
-
Downgrade to a pre-9.9(1) release with clustering—9.9(1) and later includes an improvement in the backup distribution. If you have 3 or more units in the cluster, you must perform the following steps:
-
Remove all secondary units from the cluster (so the cluster consists only of the primary unit).
-
Downgrade 1 secondary unit, and rejoin it to the cluster.
-
Disable clustering on the primary unit; downgrade it, and rejoin the cluster.
-
Downgrade the remaining secondary units, and join them back to the cluster, one at a time.
-
-
Downgrade to a pre-9.9(1) release when you enable cluster site redundancy—You should disable site redundancy if you want to downgrade (or if you want to add a pre-9.9(1) unit to a cluster). Otherwise, you will see side effects, for example, dummy forwarding flows on the unit running the old version.
-
Downgrade from 9.8(1) with clustering and crypto-map—There is no Zero Downtime Downgrade support when downgrading from 9.8(1) when you have a crypto-map configured. You should clear the crypto-map configuration before downgrading, and then re-apply the configuration after the downgrade.
-
Downgrade from 9.8(1) with clustering unit health check set to .3 to .7 seconds—If you downgrade your ASA software after setting the hold time to .3 - .7 (health-check holdtime ), this setting will revert to the default of 3 seconds because the new setting is unsupported.
-
Downgrade from 9.5(2) or later to 9.5(1) or earlier with clustering (CSCuv82933)—There is no Zero Downtime Downgrade support when downgrading from 9.5(2). You must reload all units at roughly the same time so that a new cluster is formed when the units come back online. If you wait to reload the units sequentially, then they will be unable to form a cluster.
-
Downgrade from 9.2(1) or later to 9.1 or earlier with clustering—Zero Downtime Downgrade is not supported.
-
-
Downgrade issue for the Firepower 2100 in Platform mode from 9.13/9.14 to 9.12 or earlier—For a Firepower 2100 with a fresh installation of 9.13 or 9.14 that you converted to Platform mode: If you downgrade to 9.12 or earlier, you will not be able to configure new interfaces or edit existing interfaces in FXOS (note that 9.12 and earlier only supports Platform mode). You either need to restore your version to 9.13 or later, or you need to clear your configuration using the FXOS erase configuration command. This problem does not occur if you originally upgraded to 9.13 or 9.14 from an earlier release; only fresh installations are affected, such as a new device or a re-imaged device. (CSCvr19755)
-
Downgrade from 9.10(1) for smart licensing—Due to changes in the smart agent, if you downgrade, you must re-register your device to the Cisco Smart Software Manager. The new smart agent uses an encrypted file, so you need to re-register to use an unencrypted file required by the old smart agent.
-
Downgrade to 9.5 and earlier with passwords using PBKDF2 (Password-Based Key Derivation Function 2) hash—Versions before 9.6 do not support PBKDF2 hashing. In 9.6(1), enable and username passwords longer than 32 characters use PBKDF2 hashing. In 9.7(1), new passwords of all lengths use PBKDF2 hashing (existing passwords continue to use MD5 hashing). If you downgrade, the enable password reverts to the default (which is blank). Usernames will not parse correctly, and the username commands will be removed. You must re-create your local users.
-
Downgrade from Version 9.5(2.200) for the ASAv—The ASAv does not retain the licensing registration state. You need to re-register with the license smart register idtoken id_token force command (for ASDM: see the Configuration > Device Management > Licensing > Smart Licensing page, and use the Force registration option); obtain the ID token from the Smart Software Manager.
-
VPN tunnels are replicated to the standby unit even if the standby unit is running a version of software that does not support the Ciphersuite that the original tunnel negotiated—This scenario occurs when downgrading. In this case, disconnect your VPN connection and reconnect.
Incompatible Configuration Removed After Downgrading
When you downgrade to an old version, commands that were introduced in later versions will be removed from the configuration. There is no automated way to check the configuration against the target version before you downgrade. You can view when new commands were added in ASA new features by release.
You can view rejected commands after you downgrade using the show startup-config errors command. If you can perform a downgrade on a lab device, you can preview the effects using this command before you perform the downgrade on a production device.
In some cases, the ASA migrates commands to new forms automatically when you upgrade, so depending on your version, even if you did not manually configure new commands, the downgrade could be affected by configuration migrations. We recommend that you have a backup of your old configuration that you can use when you downgrade. In the case of upgrading to 8.3, a backup is automatically created (<old_version>_startup_cfg.sav). Other migrations do not create back-ups. See the "Version-Specific Guidelines and Migrations" in the ASA Upgrade guide for more information about automatic command migrations that could affect downgrading.
See also known downgrade issues in Guidelines and Limitations for Downgrading.
For example, an ASA running version 9.8(2) includes the following commands:
access-list acl1 extended permit sctp 192.0.2.0 255.255.255.0 198.51.100.0 255.255.255.0
username test1 password $sha512$1234$abcdefghijklmnopqrstuvwxyz privilege 15
snmp-server user snmpuser1 snmpgroup1 v3 engineID abcdefghijklmnopqrstuvwxyz encrypted auth md5 12:ab:34 priv aes 128 12:ab:34
When you downgrade to 9.0(4), you will see the following errors on startup:
access-list acl1 extended permit sctp 192.0.2.0 255.255.255.0 198.51.100.0 255.255.255.0
^
ERROR: % Invalid input detected at '^' marker.
username test1 password $sha512$1234$abcdefghijklmnopqrstuvwxyz pbkdf2 privilege 15
^
ERROR: % Invalid input detected at '^' marker.
snmp-server user snmpuser1 snmpgroup1 v3 engineID abcdefghijklmnopqrstuvwxyz encrypted auth md5 12:ab:34 priv aes 128 12:ab:34
^
ERROR: % Invalid input detected at '^' marker.In this example, support for sctp in the access-list extended command was added in version 9.5(2), support for pbkdf2 in the username command was added in version 9.6(1), and support for engineID in the snmp-server user command was added in version 9.5(3).
Downgrade the Firepower 1000, 2100 in Appliance Mode, Secure Firewall 3100
You can downgrade the ASA software version by setting the ASA version to the old version, restoring the backup configuration to the startup configuration, and then reloading.
Before you begin
This procedure requires a backup configuration of the ASA before you upgraded, so you can restore the old configuration. If you do not restore the old configuration, you may have incompatible commands representing new or changed features. Any new commands will be rejected when you load the old software version.
Procedure
|
Step 1 |
Load the old ASA software version using the upgrade procedure in the ASA upgrade guide for standalone, failover, or clustering deployments. In this case, specify the old ASA version instead of a new version. Important: Do not reload the ASA yet. |
|
Step 2 |
At the ASA CLI, copy the backup ASA configuration to the startup configuration. For failover, perform this step on the active unit. This step replicates the command to the standby unit. copy old_config_url startup-config It's important that you do not save the running configuration to the startup configuration using write memory ; this command will overwrite your backup configuration. Example: |
|
Step 3 |
Reload the ASA. ASA CLI reload ASDM Choose . |
Downgrade the Firepower 2100 in Platform Mode
You can downgrade the ASA software version by restoring the backup configuration to the startup configuration, setting the ASA version to the old version, and then reloading.
Before you begin
This procedure requires a backup configuration of the ASA before you upgraded, so you can restore the old configuration. If you do not restore the old configuration, you may have incompatible commands representing new or changed features. Any new commands will be rejected when you load the old software version.
Procedure
|
Step 1 |
At the ASA CLI, copy the backup ASA configuration to the startup configuration. For failover, perform this step on the active unit. This step replicates the command to the standby unit. copy old_config_url startup-config It's important that you do not save the running configuration to the startup configuration using write memory ; this command will overwrite your backup configuration. Example: |
|
Step 2 |
In FXOS, use the Firepower Chassis Manager or FXOS CLI to use the old ASA software version using the upgrade procedure in the ASA upgrade guide for standalone, failover, or clustering deployments. In this case, specify the old ASA version instead of a new version. |
Downgrade the Firepower 4100/9300
You can downgrade the ASA software version by restoring the backup configuration to the startup configuration, setting the ASA version to the old version, and then reloading.
Before you begin
-
This procedure requires a backup configuration of the ASA before you upgraded, so you can restore the old configuration. If you do not restore the old configuration, you may have incompatible commands representing new or changed features. Any new commands will be rejected when you load the old software version.
-
Make sure the old ASA version is compatibile with the current FXOS version. If not, downgrade FXOS as the first step before you restore the old ASA configuration. Just make sure the downgraded FXOS is also compatible with the current ASA version (before you downgrade it). If you cannot achieve compatibility, we suggest you do not perform a downgrade.
Procedure
|
Step 1 |
At the ASA CLI, copy the backup ASA configuration to the startup configuration. For failover or clustering, perform this step on the active/control unit. This step replicates the command to the standby/data units. copy old_config_url startup-config It's important that you do not save the running configuration to the startup configuration using write memory ; this command will overwrite your backup configuration. Example: |
|
Step 2 |
In FXOS, use the Firepower Chassis Manager or FXOS CLI to use the old ASA software version using the upgrade procedure in the ASA upgrade guide for standalone, failover, or clustering deployments. In this case, specify the old ASA version instead of a new version. |
|
Step 3 |
If you are also downgrading FXOS, use the Firepower Chassis Manager or FXOS CLI to set the old FXOS software version to be the current version using the upgrade procedure in the ASA upgrade guide for standalone, failover, or clustering deployments. |
Downgrade the ISA 3000
The downgrade feature provides a shortcut for completing the following functions on ISA 3000 models:
-
Clearing the boot image configuration (clear configure boot ).
-
Setting the boot image to be the old image (boot system ).
-
(Optional) Entering a new activation key (activation-key ).
-
Saving the running configuration to startup (write memory ). This sets the BOOT environment variable to the old image, so when you reload, the old image is loaded.
-
Copying the old configuration backup to the startup configuration (copy old_config_url startup-config ).
-
Reloading (reload ).
Before you begin
-
This procedure requires a backup configuration of the ASA before you upgraded, so you can restore the old configuration.
Procedure
|
Downgrade the software and restore the old configuration. downgrade [/noconfirm] old_image_url old_config_url [activation-key old_key] Example:The /noconfirm option downgrades without prompting. The image_url is the path to the old image on disk0, disk1, tftp, ftp, or smb. The old_config_url is the path to the saved, pre-migration configuration. If you need to revert to a pre-8.3 activation key, then you can enter the old activation key. |
Manage Files
View Files in Flash Memory
You can view files in flash memory and see information about files.
Procedure
|
Step 1 |
View files in flash memory: dir [disk0: | disk1:] Example:Enter disk0: for the internal flash memory. The disk1: keyword represents the external flash memory. The internal flash memory is the default. |
|
Step 2 |
View extended information about a specific file: show file information [path:/]filename Example:The file size listed is for example only. The default path is the root directory of the internal flash memory (disk0:/). |
Delete Files from Flash Memory
You can remove files from flash memory that you no longer need.
Procedure
|
Delete a file from flash memory: delete disk0: filename By default, the file is deleted from the current working directory if you do not specify a path. You may use wildcards when deleting files. You are prompted with the filename to delete, and then you must confirm the deletion. |
Erase the Flash File System
To erase the flash file system, perform the following steps.
Procedure
|
Step 1 |
Connect to the ASA console port according to the instructions inAccess the ISA 3000 Console. |
|
Step 2 |
Power off the ASA, then power it on. |
|
Step 3 |
During startup, press the Escape key when you are prompted to enter ROMMON mode. |
|
Step 4 |
Enter the erase command, which overwrites all files and erases the file system, including hidden system files: rommon #1> erase [disk0: | disk1: | flash:] |
Configure File Access
The ASA can use an FTP client, secure copy client, or TFTP client. You can also configure the ASA as a secure copy server so you can use a secure copy client on your computer.
Configure the FTP Client Mode
The ASA can use FTP to upload or download image files or configuration files to or from an FTP server. In passive FTP, the client initiates both the control connection and the data connection. The server, which is the recipient of the data connection in passive mode, responds with the port number to which it is listening for the specific connection.
Procedure
|
Set the FTP mode to passive: ftp mode passive Example: |
Configure the ASA as a Secure Copy Server
You can enable the secure copy (SCP) server on the ASA. Only clients that are allowed to access the ASA using SSH can establish a secure copy connection.
Before you begin
-
The server does not have directory support. The lack of directory support limits remote client access to the ASA internal files.
-
The server does not support banners or wildcards.
-
Enable SSH on the ASA according to Configure SSH Access.
-
The ASA license must have the strong encryption (3DES/AES) license to support SSH Version 2 connections.
-
Unless otherwise specified, for multiple context mode, complete this procedure in the system execution space. To change from the context to the system execution space, enter the changeto system command.
-
The performance of secure copy depends partly on the encryption cipher used. By default, the ASA negotiates one of the following algorithms in order: 3des-cbc aes128-cbc aes192-cbc aes256-cbc aes128-ctr aes192-ctr aes256-ctr. If the first algorithm proposed (3des-cbc) is chosen, then the performance is much slower than a more efficient algorithm such as aes128-cbc. To change the proposed ciphers, use the ssh cipher encryption command; for example, ssh cipher encryption custom aes128-cbc
Procedure
|
Step 1 |
Enable the SCP server: ssh scopy enable |
|
Step 2 |
(Optional) Manually add or delete servers and their keys from the ASA database: ssh pubkey-chain [no] server ip_address {key-string key_string exit| key-hash {md5 | sha256} fingerprint} Example:The ASA stores the SSH host key for each SCP server to which it connects. You can manually manage keys if desired. For each server, you can specify the key-string (public key) or key-hash (hashed value) of the SSH host. The key_string is the Base64 encoded RSA public key of the remote peer. You can obtain the public key value from an open SSH client; that is, from the .ssh/id_rsa.pub file. After you submit the Base64 encoded public key, that key is then hashed via SHA-256. The key-hash {md5 | sha256} fingerprint enters the already hashed key (using an MD5 or SHA-256 key); for example, a key that you copied from show command output. |
|
Step 3 |
(Optional) Enable or disable SSH host key checking. For multiple context mode, enter this command in the admin context. [no] ssh stricthostkeycheck Example:By default, this option is enabled. When this option is enabled, you are prompted to accept or reject the host key if it is not already stored on the ASA. When this option is disabled, the ASA accepts the host key automatically if it was not stored before. |
Examples
From a client on the external host, perform an SCP file transfer. For example, in Linux enter the following command:
scp -v -pw password [path/]source_filename username @asa_address :{disk0|disk1}:/[path/]dest_filename
The -v is for verbose, and if -pw is not specified, you will be prompted for a password.
The following example adds an already hashed host key for the server at 10.86.94.170:
ciscoasa(config)# ssh pubkey-chain
ciscoasa(config-ssh-pubkey-chain)# server 10.86.94.170
ciscoasa(config-ssh-pubkey-server)# key-hash sha256 65:d9:9d:fe:1a:bc:61:aa:
64:9d:fc:ee:99:87:38:df:a8:8e:d9:e9:ff:42:de:e8:8d:2d:bf:a9:2b:85:2e:19
The following example adds a host string key for the server at 10.7.8.9:
ciscoasa(config)# ssh pubkey-chain
ciscoasa(config-ssh-pubkey-chain)# server 10.7.8.9
ciscoasa(config-ssh-pubkey-server)# key-string
Enter the base 64 encoded RSA public key.
End with the word "exit" on a line by itself
ciscoasa(config-ssh-pubkey-server-string)# c1:b1:30:29:d7:b8:de:6c:97:77:10:d7:
46:41:63:87
ciscoasa(config-ssh-pubkey-server-string)# exit
Configure the ASA TFTP Client Path
TFTP is a simple client/server file transfer protocol, which is described in RFC 783 and RFC 1350 Rev. 2. You can configure the ASA as a TFTP client so that it can copy files to or from a TFTP server. In this way, you can back up and propagate configuration files to multiple ASAs.
This section lets you predefine the path to a TFTP server so you do not need to enter it in commands such as copy and configure net.
Procedure
|
Predefine the TFTP server address and filename for use with configure net and copy commands: tftp-server interface_name server_ip filename Example:You can override the filename when you enter the command; for example, when you use the copy command, you can take advantage of the predefined TFTP server address but still enter any filename at the interactive prompts. For the copy command, enter tftp: to use the tftp-server value instead of tftp://url. |
Copy a File to the ASA
This section describes how to copy the application image, ASDM software, a configuration file, or any other file that needs to be downloaded to internal or external flash memory from a TFTP, FTP, SMB, HTTP, HTTPS, or SCP server.
Before you begin
-
You cannot have two files with the same name but with different letter case in the same directory in flash memory. For example, if you attempt to download the file, Config.cfg, to a location that contains the file, config.cfg, you receive the following error message:
%Error opening disk0:/Config.cfg (File exists) -
For information about installing the Cisco SSL VPN client, see the Cisco AnyConnect VPN Client Administrator Guide. For information about installing Cisco Secure Desktop on the ASA, see the Cisco Secure Desktop Configuration Guide for Cisco ASA 5500 Series Administrators.
-
To configure the ASA to use a specific application image or ASDM image if you have more than one installed, or have installed them in external flash memory, see Set the ASA Image, ASDM, and Startup Configuration.
-
For multiple context mode, you must be in the system execution space.
-
(Optional) Specify the interface through which the ASA communicates with the server. If you do not specify the interface, the ASA checks the management-only routing table; if there are no matches, it then checks the data routing table.
-
If you use the CiscoSSH stack, to use the ASA copy command to copy a file to or from an SCP server, you have to enable SSH access on the ASA for the SCP server subnet/host using the ssh command. See Configure SSH Access.
Procedure
|
Copy a file using one of the following server types.
|
Copy a File to the Startup or Running Configuration
You can download a text file to the running or startup configuration from a TFTP, FTP, SMB, HTTP(S), or SCP server, or from the flash memory.
Before you begin
When you copy a configuration to the running configuration, you merge the two configurations. A merge adds any new commands from the new configuration to the running configuration. If the configurations are the same, no changes occur. If commands conflict or if commands affect the running of the context, then the effect of the merge depends on the command. You might get errors, or you might have unexpected results.
(Optional) Specify the interface through which the ASA communicates with the server. If you do not specify the interface, the ASA checks the management-only routing table; if there are no matches, it then checks the data routing table.
Procedure
|
To copy a file to the startup configuration or running configuration, enter one of the following commands for the appropriate download server:
|
Examples
For example, to copy the configuration from a TFTP server, enter the following command:
ciscoasa# copy tftp://209.165.200.226/configs/startup.cfg startup-config
To copy the configuration from an FTP server, enter the following command:
ciscoasa# copy ftp://admin:letmein@209.165.200.227/configs/startup.cfg startup-config
To copy the configuration from an HTTP server, enter the following command:
ciscoasa# copy http://209.165.200.228/configs/startup.cfg startup-config
Set the ASA Image, ASDM, and Startup Configuration
If you have more than one ASA or ASDM image, you should specify the image that you want to boot. If you do not set the image, the default boot image is used, and that image may not be the one intended. For the startup configuration, you can optionally specify a configuration file.
See the following model guidelines:
-
Firepower 4100/9300 chassis—ASA upgrades are managed by FXOS; you cannot upgrade the ASA within the ASA operating system, so do not use this procedure for the ASA image. You can upgrade the ASA and FXOS separately from each other, and they are listed separately in the FXOS directory listing. The ASA package always includes ASDM.
-
Firepower 2100 in Platform mode—The ASA, ASDM, and FXOS images are bundled together into a single package. Package updates are managed by FXOS; you cannot upgrade the ASA within the ASA operating system, so do not use this procedure for the ASA image. You cannot upgrade the ASA and FXOS separately from each other; they are always bundled together.
-
Firepower 1000, 2100 in Appliance mode, Secure Firewall 3100—The ASA, ASDM, and FXOS images are bundled together into a single package. Package updates are managed by the ASA using this procedure. Although these platforms use the ASA to identify the image to boot, the underlying mechanism is different from legacy ASAs. See the command description below for more information.
-
ASDM for the models—ASDM can be upgraded from within the ASA operating system, so you do not need to only use the bundled ASDM image. For the Firepower 2100 in Platform mode and Firepower 4100/9300, ASDM images that you upload manually do not appear in the FXOS image list; you must manage ASDM images from the ASA.
Note
When you upgrade the ASA bundle, the ASDM image in the bundle replaces the previous ASDM bundle image on the ASA because they have the same name (asdm.bin). But if you manually chose a different ASDM image that you uploaded (for example, asdm-782.bin), then you continue to use that image even after a bundle upgrade. To make sure that you are running a compatible version of ASDM, you should either upgrade ASDM before you upgrade the bundle, or you should reconfigure the ASA to use the bundled ASDM image (asdm.bin) just before upgrading the ASA bundle.
-
ASAv—The initial deployment ASAv package puts the ASA image in the read-only boot:/ partition. When you upgrade the ASAv, you specify a different image in flash memory. Note that if you later clear your configuration (clear configure all), then the ASAv will revert to loading the original deployment image. The initial deployment ASAv package also includes an ASDM image that it places in flash memory. You can upgrade the ASDM image separately.
See the following default settings:
-
ASA image:
-
Firepower 1000, 2100 in Appliance mode, Secure Firewall 3100—Boots the previously-running boot image.
-
Other Physical ASAs—Boots the first application image that it finds in internal flash memory.
-
ASAv—Boots the image in the read-only boot:/ partition that was created when you first deployed.
-
Firepower 4100/9300 chassis—The FXOS system determines which ASA image to boot. You cannot use this procedure to set the ASA image.
-
Firepower 2100 in Platform mode—The FXOS system determines which ASA/FXOS package to boot. You cannot use this procedure to set the ASA image.
-
-
ASDM image on all ASAs—Boots the first ASDM image that it finds in internal flash memory, or if one does not exist in this location, then in external flash memory.
-
Startup configuration—By default, the ASA boots from a startup configuration that is a hidden file.
Procedure
|
Step 1 |
Set the ASA boot image location: boot system url Example:The URL can be:
Firepower 1000, 2100 in Appliance mode, Secure Firewall 3100: You can only enter a single boot system command. If you upgrade to a new image, then you must enter no boot system to remove the previous image you set. Note that you may not have a boot system command present in your configuration; for example, if you installed the image from ROMMON, have a new device, or you removed the command manually. The boot system command performs an action when you enter it: the system validates and unpacks the image and copies it to the boot location (an internal location on disk0 managed by FXOS). The new image will load when you reload the ASA. If you change your mind prior to reloading, you can enter the no boot system command to delete the new image from the boot location, so the current image continues to run. You can even delete the original image file from the ASA flash memory after you enter this command, and the ASA will boot correctly from the boot location; however, we recommend keeping any images you want to use in flash memory because the boot system command only works with images in flash memory. Unlike other models, this command in the startup configuration does not affect the booting image, and is essentially cosmetic. The last-loaded boot image will always run upon reload. If you do not save the configuration after you enter this command, then when you reload, the old command will be present in your configuration, even though the new image was booted. Be sure to save the configuration so that the configuration remains in sync. You can only load images with the original filename from the Cisco download site. If you change the filename, it will not load. You can also reimage to the FTD by loading the FTD image. In this case, you are prompted to reload immediately. Other models: You can enter up to four boot system command entries to specify different images to boot from in order; the ASA boots the first image it finds successfully. When you enter the boot system command, it adds an entry at the bottom of the list. To reorder the boot entries, you must remove all entries using the the clear configure boot system command, and re-enter them in the order you desire. Only one boot system tftp command can be configured, and it must be the first one configured.
Example: |
||
|
Step 2 |
Set the ASDM image to boot: asdm image {disk0:/ | disk1:/}[path/]filename Example:If you do not specify the image to boot, even if you have only one image installed, then the ASA inserts the asdm image command into the running configuration. To avoid problems with Auto Update (if configured), and to avoid the image search at each startup, you should specify the ASDM image that you want to boot in the startup configuration. |
||
|
Step 3 |
(Optional) Set the startup configuration to be a known file instead of the default hidden file: boot config {disk0:/ | disk1:/}[path/]filename Example: |
Back Up and Restore Configurations or Other Files
We recommend that you make regular backups of your configuration and other system files to guard against system failure.
Perform a Complete System Backup or Restoration
These procedures describe how to back up and restore configurations and images to a tar.gz file and transfer it to your local computer.
Before You Begin Backup or Restore
-
You should have at least 300 MB of disk space available at the backup or restore location before you start a backup or restore.
-
If you make any configuration changes during or after a backup, those changes will not be included in the backup. If you change a configuration after making the backup, then perform a restore, this configuration change will be overwritten. As a result, the ASA might behave differently.
-
You can start only one backup or restore at a time.
-
You can only restore a configuration to the same ASA version as when you performed the original backup. You cannot use the restore tool to migrate a configuration from one ASA version to another. If a configuration migration is required, the ASA automatically upgrades the resident startup configuration when it loads the new ASA OS.
-
If you use clustering, you can only back up or restore the startup-configuration, running-configuration, and identity certificates. You must create and restore a backup separately for each unit.
-
If you use failover, you must create and restore a backup separately for the active and standby units.
-
If you set a master passphrase for the ASA, then you need that master passphrase to restore the backup configuration that you create with this procedure. If you do not know the master passphrase for the ASA, see Configure the Master Passphrase to learn how to reset it before continuing with the backup.
-
If you import PKCS12 data (with the crypto ca trustpoint command) and the trustpoint uses RSA keys, the imported key pair is assigned the same name as the trustpoint. Because of this limitation, if you specify a different name for the trustpoint and its key pair after you have restored an ASDM configuration, the startup configuration will be the same as the original configuration, but the running configuration will include a different key pair name. This means that if you use different names for the key pair and trustpoint, you cannot restore the original configuration. To work around this issue, make sure that you use the same name for the trustpoint and its key pair.
-
You cannot back up using the CLI and restore using ASDM, or vice versa.
-
Each backup file includes the following content:
-
Running-configuration
-
Startup-configuration
-
All security images
Cisco Secure Desktop and Host Scan images
Cisco Secure Desktop and Host Scan settings
AnyConnect Client (SVC) images and profiles
AnyConnect Client (SVC) customizations and transforms
-
Identity certificates (includes RSA key pairs tied to identity certificates; excludes standalone keys)
-
VPN pre-shared keys
-
SSL VPN configurations
-
Application Profile Custom Framework (APCF)
-
Bookmarks
-
Customizations
-
Dynamic Access Policy (DAP)
-
Plug-ins
-
Pre-fill scripts for connection profiles
-
Proxy Auto-config
-
Translation table
-
Web content
-
Version information
-
Back Up the System
This procedure describes how to perform a complete system backup.
Procedure
|
Step 1 |
Back up the system: backup [/noconfirm] [context ctx-name] [interface name] [passphrase value] [location path] Example:If you do not specify the interface name, the ASA checks the management-only routing table; if there are no matches, it then checks the data routing table. In multiple context mode from the system execution space, enter the context keyword to backup the specified context. Each context must be backed up individually; that is, re-enter the backup command for each file. During the backup of VPN certificates and preshared keys, a secret key identified by the passphrase keyword is required to encode the certificates. You must provide a passphrase to be used for encoding and decoding the certificates in PKCS12 format. The backup only includes RSA key pairs tied to the certificates and excludes any standalone certificates. The backup location can be a local disk or a remote URL. If you do not provide a location, the following default names are used:
|
|
Step 2 |
Follow the prompts: Example: |
Restore the Backup
You can specify configurations and images to restore from a zip tar.gz file on your local computer.
Procedure
|
Step 1 |
Restore the system from the backup file. restore [/noconfirm] [context ctx-name] [passphrase value] [location path] Example:When using the context keyword to restore multiple contexts, each backed up context file must be restored individually; that is, re-enter the restore command for each file. |
|
Step 2 |
Follow the prompts: Example: |
Configure Automatic Backup and Restore (ISA 3000)
On the ISA 3000, you can configure automatic backups to a particular location every time you save your configuration using write memory .
Automatic restore lets you easily configure new devices with a complete configuration loaded on an SD flash memory card. Automatic restore is enabled in the default factory configuration.
Configure Automatic Backup (ISA 3000)
On the ISA 3000, you can configure automatic backups to a particular location every time you save your configuration using write memory .
Before you begin
This feature is only available on the ISA 3000.
Procedure
|
Step 1 |
Set the back-up package parameters: backup-package backup [interface name] location {diskn: | url} [passphrase string]
These settings are also used by default with the manual backup command. See Back Up the System. Note that if you use the manual backup command when you have automatic backup or restore enabled, then the system saves a backup file with the specified name, as well as the "auto-backup-asa.tgz" name used by automatic backup and restore. Example: |
|
Step 2 |
Enable automatic mode for back-up and restore: backup-package backup auto When you save the configuration using write memory , the configuration is automatically saved to the backup location as well as to the startup configuration. The backup file has the name "auto-backup-asa.tgz". To disable automatic backups, use the no form of the command. Example: |
Configure Automatic Restore (ISA 3000)
Automatic restore mode restores the system configuration on a device without any user intervention. For example, you insert an SD memory card containing a saved backup configuration into a new device and then power the device on. When the device comes up, it checks the SD card to decide if the system configuration needs to be restored. (The restoration is only initiated if the backup file has the "fingerprint" of a different device. The fingerprint of the backup file is updated to match the current device during a backup or restore operation. So if the device has already completed a restore, or if it has created its own backup, then the automatic restore is skipped.) If the fingerprint shows a restoration is required, the device replaces the system configuration (startup-config, running-config, SSL VPN configuration, and so on; see Back Up the System for details about the contents of the backup). When the device finishes booting, it is running the saved configuration.
Automatic restore is enabled in the default factory configuration, so you can easily configure new devices with a complete configuration loaded on an SD memory card without having to perform any pre-configuration of the device.
Because the device needs to decide early in the boot process if the system configuration needs to be restored, it checks ROMMON variables to determine if the device is in automatic restore mode and to obtain the location of the backup configuration. The following ROMMON variables are used:
-
RESTORE_MODE = {auto | manual}
The default is auto.
-
RESTORE_LOCATION = {disk0: | disk1: | disk2: | disk3:}
The default is disk3:.
-
RESTORE_PASSPHRASE = key
The default is cisco.
To change the automatic restore settings, complete the following procedure.
Before you begin
-
This feature is only available on the ISA 3000.
-
If you use the default restore settings, you need an SD memory card installed (part number SD-IE-1GB=).
-
If you need to restore the default configuration to ensure that automatic restore is enabled, use the configure factory default command. This command is only available in transparent firewall mode, so if you are in routed firewall mode, use the firewall transparent command first.
Procedure
|
Step 1 |
Set the restore package parameters. backup-package restore location {diskn: | url} [passphrase string]
These settings are also used by default with the manual restore command. See Back Up the System. Example: |
|
Step 2 |
Enable or disable automatic mode for restore. [no] backup-package restore auto The name of the file that is restored is "auto-backup-asa.tgz". Example: |
Back up the Single Mode Configuration or Multiple Mode System Configuration
In single context mode or from the system configuration in multiple mode, you can copy the startup configuration or running configuration to an external server or to the local flash memory.
Before you begin
(Optional) Specify the interface through which the ASA communicates with the server. If you do not specify the interface, the ASA checks the management-only routing table; if there are no matches, it then checks the data routing table.
Procedure
|
Back up the configuring using one of the following server types:
|
Back Up a Context Configuration or Other File in Flash Memory
Copy context configurations or other files that are on the local flash memory by entering one of the following commands in the system execution space.
Before you begin
(Optional) Specify the interface through which the ASA communicates with the server. If you do not specify the interface, the ASA checks the management-only routing table; if there are no matches, it then checks the data routing table.
Procedure
|
Back up a context configuration using one of the following server types:
|
Back Up a Context Configuration within a Context
In multiple context mode, from within a context, you can perform the following backups.
Procedure
|
Step 1 |
Copy the running configuration to the startup configuration server (connected to the admin context): |
|
Step 2 |
Copy the running configuration to a TFTP server connected to the context network: |
Copy the Configuration from the Terminal Display
Procedure
|
Step 1 |
Print the configuration to the terminal: more system:running-config |
|
Step 2 |
Copy the output from this command, and then paste the configuration into a text file. |
Back Up Additional Files Using the Export and Import Commands
Additional files essential to your configuration might include the following:
-
Files that you import using the import webvpn command. Currently, these files include customizations, URL lists, web content, plug-ins, and language translations.
-
DAP policies (dap.xml).
-
CSD configurations (data.xml).
-
Digital keys and certificates.
-
Local CA user database and certificate status files.
The CLI lets you back up and restore individual elements of your configuration using the export and import commands.
To back up these files, for example, those files that you imported with the import webvpn command or certificates, perform the following steps.
Procedure
|
Step 1 |
Run the applicable show command(s) as follows: |
|
Step 2 |
Run the export command for the file that you want to back up (in this example, the rdp file): |
Use a Script to Back Up and Restore Files
You can use a script to back up and restore the configuration files on your ASA, including all extensions that you import via the import webvpn CLI, the CSD configuration XML files, and the DAP configuration XML file. For security reasons, we do not recommend that you perform automated backups of digital keys and certificates or the local CA key.
This section provides instructions for doing so and includes a sample script that you can use as is or modify as your environment requires. The sample script is specific to a Linux system. To use it for a Microsoft Windows system, you need to modify it using the logic of the sample.
Note |
You can alternatively use the backup and restore commands. See Perform a Complete System Backup or Restoration for more information. |
Before You Begin Using Backup and Restore Scripts
To use a script to back up and restore an ASA configuration, first perform the following tasks:
-
Install Perl with an Expect module.
-
Install an SSH client that can reach the ASA.
-
Install a TFTP server to send files from the ASA to the backup site.
Another option is to use a commercially available tool. You can put the logic of this script into such a tool.
Run the Script
To run a backup-and-restore script, perform the following steps.
Procedure
|
Step 1 |
Download or cut-and-paste the script file to any location on your system. |
|
Step 2 |
At the command line, enter Perlscriptname , where scriptname is the name of the script file. |
|
Step 3 |
Press Enter. |
|
Step 4 |
The system prompts you for values for each option. Alternatively, you can enter values for the options when you enter the Perlscriptname command before you press Enter. Either way, the script requires that you enter a value for each option. |
|
Step 5 |
The script starts running, printing out the commands that it issues, which provides you with a record of the CLIs. You can use these CLIs for a later restore, which is particularly useful if you want to restore only one or two files. |
Sample Script
#!/usr/bin/perl
#Description: The objective of this script is to show how to back up configurations/extensions.
# It currently backs up the running configuration, all extensions imported via "import webvpn" command, the CSD configuration XML file, and the DAP configuration XML file.
#Requirements: Perl with Expect, SSH to the ASA, and a TFTP server.
#Usage: backupasa -option option_value
# -h: ASA hostname or IP address
# -u: User name to log in via SSH
# -w: Password to log in via SSH
# -e: The Enable password on the security appliance
# -p: Global configuration mode prompt
# -s: Host name or IP address of the TFTP server to store the configurations
# -r: Restore with an argument that specifies the file name. This file is produced during backup.
#If you don't enter an option, the script will prompt for it prior to backup.
#
#Make sure that you can SSH to the ASA.
use Expect;
use Getopt::Std;
#global variables
%options=();
$restore = 0; #does backup by default
$restore_file = '';
$asa = '';
$storage = '';
$user = '';
$password = '';
$enable = '';
$prompt = '';
$date = ‘date +%F‘;
chop($date);
my $exp = new Expect();
getopts("h:u:p:w:e:s:r:",\%options);
do process_options();
do login($exp);
do enable($exp);
if ($restore) {
do restore($exp,$restore_file);
}
else {
$restore_file = "$prompt-restore-$date.cli";
open(OUT,">$restore_file") or die "Can't open $restore_file\n";
do running_config($exp);
do lang_trans($exp);
do customization($exp);
do plugin($exp);
do url_list($exp);
do webcontent($exp);
do dap($exp);
do csd($exp);
close(OUT);
}
do finish($exp);
sub enable {
$obj = shift;
$obj->send("enable\n");
unless ($obj->expect(15, 'Password:')) {
print "timed out waiting for Password:\n";
}
$obj->send("$enable\n");
unless ($obj->expect(15, "$prompt#")) {
print "timed out waiting for $prompt#\n";
}
}
sub lang_trans {
$obj = shift;
$obj->clear_accum();
$obj->send("show import webvpn translation-table\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
@items = split(/\n+/, $output);
for (@items) {
s/^\s+//;
s/\s+$//;
next if /show import/ or /Translation Tables/;
next unless (/^.+\s+.+$/);
($lang, $transtable) = split(/\s+/,$_);
$cli = "export webvpn translation-table $transtable language $lang $storage/$prompt-$date-$transtable-$lang.po";
$ocli = $cli;
$ocli =~ s/^export/import/;
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
}
sub running_config {
$obj = shift;
$obj->clear_accum();
$cli ="copy /noconfirm running-config $storage/$prompt-$date.cfg";
print "$cli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
sub customization {
$obj = shift;
$obj->clear_accum();
$obj->send("show import webvpn customization\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
@items = split(/\n+/, $output);
for (@items) {
chop;
next if /^Template/ or /show import/ or /^\s*$/;
$cli = "export webvpn customization $_ $storage/$prompt-$date-cust-$_.xml";
$ocli = $cli;
$ocli =~ s/^export/import/;
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
}
sub plugin {
$obj = shift;
$obj->clear_accum();
$obj->send("show import webvpn plug-in\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
@items = split(/\n+/, $output);
for (@items) {
chop;
next if /^Template/ or /show import/ or /^\s*$/;
$cli = "export webvpn plug-in protocol $_ $storage/$prompt-$date-plugin-$_.jar";
$ocli = $cli;
$ocli =~ s/^export/import/;
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
}
sub url_list {
$obj = shift;
$obj->clear_accum();
$obj->send("show import webvpn url-list\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
@items = split(/\n+/, $output);
for (@items) {
chop;
next if /^Template/ or /show import/ or /^\s*$/ or /No bookmarks/;
$cli="export webvpn url-list $_ $storage/$prompt-$date-urllist-$_.xml";
$ocli = $cli;
$ocli =~ s/^export/import/;
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
}
sub dap {
$obj = shift;
$obj->clear_accum();
$obj->send("dir dap.xml\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
return 0 if($output =~ /Error/);
$cli="copy /noconfirm dap.xml $storage/$prompt-$date-dap.xml";
$ocli="copy /noconfirm $storage/$prompt-$date-dap.xml disk0:/dap.xml";
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
sub csd {
$obj = shift;
$obj->clear_accum();
$obj->send("dir sdesktop\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
return 0 if($output =~ /Error/);
$cli="copy /noconfirm sdesktop/data.xml $storage/$prompt-$date-data.xml";
$ocli="copy /noconfirm $storage/$prompt-$date-data.xml disk0:/sdesktop/data.xml";
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
sub webcontent {
$obj = shift;
$obj->clear_accum();
$obj->send("show import webvpn webcontent\n");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
@items = split(/\n+/, $output);
for (@items) {
s/^\s+//;
s/\s+$//;
next if /show import/ or /No custom/;
next unless (/^.+\s+.+$/);
($url, $type) = split(/\s+/,$_);
$turl = $url;
$turl =~ s/\/\+//;
$turl =~ s/\+\//-/;
$cli = "export webvpn webcontent $url $storage/$prompt-$date-$turl";
$ocli = $cli;
$ocli =~ s/^export/import/;
print "$cli\n";
print OUT "$ocli\n";
$obj->send("$cli\n");
$obj->expect(15, "$prompt#" );
}
}
sub login {
$obj = shift;
$obj->raw_pty(1);
$obj->log_stdout(0); #turn off console logging.
$obj->spawn("/usr/bin/ssh $user\@$asa") or die "can't spawn ssh\n";
unless ($obj->expect(15, "password:" )) {
die "timeout waiting for password:\n";
}
$obj->send("$password\n");
unless ($obj->expect(15, "$prompt>" )) {
die "timeout waiting for $prompt>\n";
}
}
sub finish {
$obj = shift;
$obj->hard_close();
print "\n\n";
}
sub restore {
$obj = shift;
my $file = shift;
my $output;
open(IN,"$file") or die "can't open $file\n";
while (<IN>) {
$obj->send("$_");
$obj->expect(15, "$prompt#" );
$output = $obj->before();
print "$output\n";
}
close(IN);
}
sub process_options {
if (defined($options{s})) {
$tstr= $options{s};
$storage = "tftp://$tstr";
}
else {
print "Enter TFTP host name or IP address:";
chop($tstr=<>);
$storage = "tftp://$tstr";
}
if (defined($options{h})) {
$asa = $options{h};
}
else {
print "Enter ASA host name or IP address:";
chop($asa=<>);
}
if (defined ($options{u})) {
$user= $options{u};
}
else {
print "Enter user name:";
chop($user=<>);
}
if (defined ($options{w})) {
$password= $options{w};
}
else {
print "Enter password:";
chop($password=<>);
}
if (defined ($options{p})) {
$prompt= $options{p};
}
else {
print "Enter ASA prompt:";
chop($prompt=<>);
}
if (defined ($options{e})) {
$enable = $options{e};
}
else {
print "Enter enable password:";
chop($enable=<>);
}
if (defined ($options{r})) {
$restore = 1;
$restore_file = $options{r};
}
}
Hot Swap an SSD on the Secure Firewall 3100
If you have two SSDs, they form a RAID when you boot up. You can perform the following tasks at the CLI while the firewall is powered up:
-
Hot swap one of the SSDs—If an SSD is faulty, you can replace it. Note that if you only have one SSD, you cannot remove it while the firewall is powered on.
-
Remove one of the SSDs—If you have two SSDs, you can remove one.
-
Add a second SSD—If you have one SSD, you can add a second SSD and form a RAID.
Caution |
Do not remove an SSD without first removing it from the RAID using this procedure. You can cause data loss. |
Procedure
|
Step 1 |
Remove one of the SSDs. |
|
Step 2 |
Add an SSD. |
History for Software and Configurations
|
Feature Name |
Platform Releases |
Feature Information |
|---|---|---|
|
Secure Copy client and server |
9.1(5)/9.2(1) |
The ASA now supports the Secure Copy (SCP) client and server to transfer files to and from a SCP server. We introduced the following commands: ssh pubkey-chain, server (ssh pubkey-chain), key-string, key-hash, ssh stricthostkeycheck. We modified the following command: copy scp. |
|
Configurable SSH encryption and integrity ciphers |
9.1(7)/9.4(3)/9.5(3)/9.6(1) |
Users can select cipher modes when doing SSH encryption management and can configure HMAC and encryption for varying key exchange algorithms. You might want to change the ciphers to be more or less strict, depending on your application. Note that the performance of secure copy depends partly on the encryption cipher used. By default, the ASA negotiates one of the following algorithms in order: 3des-cbc aes128-cbc aes192-cbc aes256-cbc aes128-ctr aes192-ctr aes256-ctr. If the first algorithm proposed (3des-cbc) is chosen, then the performance is much slower than a more efficient algorithm such as aes128-cbc. To change the proposed ciphers, use ssh cipher encryption custom aes128-cbc , for example. We introduced the following commands: ssh cipher encryption, ssh cipher integrity |
|
Auto Update server certificate verification enabled by default |
9.2(1) |
The Auto Update server certificate verification is now enabled by default; for new configurations, you must explicitly disable certificate verification. If you are upgrading from an earlier release, and you did not enable certificate verification, then certificate verification is not enabled, and you see the following warning: The configuration will be migrated to explicitly configure no verification. auto-update server no-verification We modified the following command: auto-update server {verify-certificate | no-verification}. |
|
System backup and restore using the CLI |
9.3(2) |
You can now back up and restore complete system configurations, including images and certificates, using the CLI. We introduced the following commands: backup and restore. |
|
Recovering and loading a new ASA 5506W-X image |
9.4(1) |
We now support the recovery and loading of a new ASA 5506W-X image. We introduced the following command: hw-module module wlan recover image. |
|
Automatic Backup and Restore for the ISA 3000 |
9.7(1) |
You can enable auto-backup and/or auto-restore functionality using pre-set parameters in the backup and restore commands. The use cases for these features include initial configuration from external media; device replacement; roll back to an operable state. We introduced the following commands: backup-package location, backup-package auto, show backup-package status, show backup-package summary |
|
CiscoSSH stack requires SSH access when using the SCP client |
9.17(1) |
If you use the CiscoSSH stack, to use the ASA copy command to copy a file to or from an SCP server, you have to enable SSH access on the ASA for the SCP server subnet/host using the ssh command. |
|
RAID support for SSDs on the Secure Firewall 3100 |
9.17(1) |
The SSDs are self-encrypting drives (SEDs), and if you have 2 SSDs, they form a software RAID. New/Modified commands: raid, show raid, show ssd |
Feedback