Administration Guide vA4(1.0), Cisco ACE 4700 Series Application Control Engine Appliance

copy running-config startup-config

Example: 

host1/Admin# copy running-config 
startup-config

Copies the contents of the running-configuration file to the startup-configuration file.

write memory [all]

Example: 

host1/Admin# write memory all

Copies the contents of the running-configuration file to the startup-configuration file.

The optional all keyword saves configurations for all existing contexts. This keyword is available only in the Admin context.

When used without the all keyword, this command copies the contents of the running-configuration file for the current context to the startup-configuration file.

Note After you save the contents of the running-configuration file for the current user context to the startup-configuration file, you should also save the changes to the Admin context startup-configuration file, which contains all configurations that are used to create each user context.

copy {running-config | startup-config} {ftp://server/path[/filename] | sftp://[username@]server/path[/filename] | tftp://server[:port]/path[/filename]}

Example: 

host1/Admin# copy running-config 
ftp://192.168.1.2/running-config_Adminctx

Enter username[]? user1

Enter the file transfer mode[bin/ascii]: [bin]

Password: password1

Passive mode on.

Hash mark printing on (1024 bytes/hash mark).

####

Saves the running-configuration file or startup-configuration file to a remote server using FTP, SFTP, or FTP.

The keywords, arguments, and options are as follows:

•running-config—Specifies the running-configuration file currently residing on the ACE in volatile memory.

•startup-config—Specifies the startup-configuration file currently residing on the ACE in Flash memory.

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, the renamed configuration file.

When using FTP, the bin (binary) file transfer mode is intended for transferring compiled files (executables). The ascii file transfer mode is intended for transferring text files, such as config files. The default selection of bin should be sufficient in all cases when copying files to a remote FTP server.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, the renamed configuration file.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, the renamed configuration file.

When you select a destination file system using ftp:, sftp:, or tftp:, the ACE performs the following tasks:

•Prompts you for your username and password if the destination file system requires user authentication.

•Prompts you for the server information if you do not provide the information with the command.

•Copies the file to the root directory of the destination file system if you do not provide the path information.

copy {running-config | startup-config} disk0:[path/]filename

Example: 

host1/Admin# copy running-config 
disk0:running-config_copy

Copies either the running configuration of the startup configuration to a file on the disk0: file system in Flash memory.

The keywords and arguments are as follows:

•running-config—Specifies the running-configuration file currently residing on the ACE in RAM (volatile memory).

•startup-config—Specifies the startup-configuration file currently residing on the ACE in Flash memory (nonvolatile memory).

•[path/]filename—Path in the disk0: file system. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

copy startup-config running-config

Example: 

host1/Admin# copy startup-config 
running-config

Merges the contents of the startup-configuration file into the running-configuration file.

show running-config [aaa | access-list | action-list | class-map | context | dhcp | domain | ft | interface | object-group | parameter-map | policy-map | probe | resource-class | role | rserver | serverfarm | sticky]

Displays the contents of the running configuration associated with the current context. Configuration entries within each mode appear in the chronological order in which you configure the ACE. The ACE does not display default configurations in the ACE running-configuration file.

The keywords and options are as follows:

•aaa—(Optional) Displays AAA information.

•access-list—(Optional) Displays access control list (ACL) information.

•action-list—(Optional) Displays action-list information.

•class-map—(Optional) Displays all class maps configured for the current context. The ACE also displays configuration information for each class map.

•context—(Optional) Displays the contexts configured on the ACE. The ACE also displays the resource class (member) assigned to each context. The context keyword works only from within the Admin context.

•dhcp—(Optional) Displays Dynamic Host Configuration Protocol (DHCP) information.

•domain—(Optional) Displays the domains configured for the current context. The ACE also displays configuration information for each domain listed.

•ft—(Optional) Displays the redundancy or fault-tolerance (FT) configurations configured for the current context. The ACE also displays configuration information for each FT configuration.

•interface—(Optional) Displays interface information.

•object-group—(Optional) Displays ACL object-group information.

•parameter-map—(Optional) Displays parameter map information.

•policy-map—(Optional) Displays policy map information.

•probe—(Optional) Displays probe information.

•resource-class—(Optional) Displays resource class information.

•role—(Optional) Displays the roles configured for the current context. The ACE also displays configuration information for each role.

•rserver—(Optional) Displays real server information.

•serverfarm—(Optional) Displays serverfarm information.

•sticky—(Optional) Displays sticky information.

write terminal

Displays the contents of the running configuration associated with the current context. The write terminal command is equivalent to the show running-config command.

invoke context context_name show running-config

Displays the running-configuration file of a user context from the Admin context. The context_name argument is the name of the user context.

show startup-config

Displays the contents of the startup configuration associated with the current context.

Step 1 

copy startup-config {ftp://server/path[/filename] | sftp://[username@]server/path[/filename] | tftp://server[:port]/path[/filename]}

Example: 

host1/Admin# copy startup-config 
ftp://192.168.1.2/startup-config_Adminctx

(Optional) Creates a backup of your current startup-configuration file on a remote server.

For details about using this command, see the "Saving Configuration Files to a Remote Server" section.

Step 2 

Clears the contents of the startup-configuration file and resets it to the default settings.

Step 3 

(Optional) Recovers a copy of an startup configuration by copying the contents of the existing running-configuration file to the startup-configuration file.

(Optional) Recovers a copy of an existing startup configuration saved on a remote server.

For details about using this command, see the "Copying Configuration Files from a Remote Server" section.

Configures the ACE using a running-configuration file or startup-configuration file downloaded from a remote server.

For details about using this command, see the "Copying Configuration Files from a Remote Server" section.

show download information [all] [summary]}

Example: 

host1/Admin# show download information all

Displays the state of the configuration download for each interface on the context. If no option is included with this command, the status information for all interfaces in the current context is displayed. The options are as follows:

•all —Displays the configuration download status for all interfaces on all contexts. This option is available in the Admin context.

•summary—Displays the summary status of the download information for the context. When you include the all option with the summary option, the download summary status for all contexts is displayed.

See Table 4-1 for information on the download states that the Download-status field displays.

Step 1 

(Optional) Displays the contents of the disk0: file system.

Step 2 

Copies a file from one directory in the disk0: file system of Flash memory to another directory in disk0:.

The keywords and arguments are as follows:

•[path/]filename1—Name of the file to copy. Use the dir disk0: command to view the files available in the disk0: file system. If you do not provide the optional path, the ACE copies the file from the root directory on the disk0: file system.

•disk0:[path]filename2—Specifies the file destination in the disk0: directory of the current context. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

Creates a backup license for the ACE licenses in .tar format and copies it to the disk0: file system.

The keyword and argument are as follows:

•disk0:—Specifies that the backup license file is copied to the disk0: file system.

•[path/]filename.tar—Destination filename for the backup licenses. The destination filename must have a .tar file extension. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

(Optional) Untars the backup file and reinstalls it if you accidently remove or lose the license on the ACE (see the "Untarring Files in the disk0: File System" section).

Copies an existing packet capture buffer to the disk0: file system.

The keywords, arguments, and options are as follows:

•capture_name—Name of the packet capture buffer on Flash memory. Specify a text string from 1 to 64 alphanumeric characters. If necessary, use the show capture command to view the files available in the disk0: file system. This list includes the name of existing packet capture buffers.

•disk0:—Specifies that the buffer is copied to the disk0: file system.

•[path/]destination_name—Destination path (optional) and name for the packet capture buffer. Specify a text string from 1 to 80 alphanumeric characters. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

Copies a file from the probe: directory to the disk0: file system on the ACE or a remote server using FTP, SFTP, or TFTP.

The keywords, arguments, and options are as follows:

•probe:filename—Specifies the scripted probe file residing on the ACE. Use the dir probe: command to view the files available in the probe: directory.

•disk0:[path/]filename—Specifies a location and filename in the disk0: file system.

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, the renamed file.

When using FTP, the bin (binary) file transfer mode is intended for transferring compiled files (executables). The ascii file transfer mode is intended for transferring text files, such as config files. The default selection of bin mode should be sufficient in all cases when copying files to a remote FTP server.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, the renamed file.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, the renamed file.

When you select a destination file system using ftp:, sftp:, or tftp:, the ACE performs the following tasks:

•Prompts you for your username and password if the destination file system requires user authentication.

•Prompts you for the server information if you do not provide the information with the command.

•Copies the file to the root directory of the destination file system if you do not provide path information.

Copies a file from Flash memory on the ACE to a remote server using FTP, SFTP, or TFTP.

The keywords, arguments, and options are as follows:

•core:filename—Specifies a core dump residing on the ACE in Flash memory (see the "Managing Core Dump Files" section). The copy core: command is available only in the Admin context. Use the dir core: command to view the core dump files available in the core: file system. Copy the complete filename (for example, 0x401_vsh_log.25256.tar.gz) by using the copy core: command.

•disk0:[path/]filename—Specifies a file in the disk0: file system of Flash memory (for example, a packet capture buffer file, ACE licenses in .tar format, or a system message log). Use the dir disk0: command to view the files available in the disk0: file system.

•running-config—Specifies the running-configuration file residing on the ACE in volatile memory.

•startup-config—Specifies the startup-configuration file currently residing on the ACE in Flash memory.

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, the renamed file.

When using FTP, the bin (binary) file transfer mode is intended for transferring compiled files (executables). The ascii file transfer mode is intended for transferring text files, such as config files. The default selection of bin mode should be sufficient in all cases when copying files to a remote FTP server.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, the renamed file.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, the renamed file.

When you select a destination file system using ftp:, sftp:, or tftp:, the ACE performs the following tasks:

•Prompts you for your username and password if the destination file system requires user authentication.

•Prompts you for the server information if you do not provide the information with the command.

•Copies the file to the root directory of the destination file system if you do not provide path information.

Copies a file from a remote server to a location on the ACE using FTP, SFTP, or TFTP.

The keywords, arguments, and options are as follows:

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, the filename.

When using FTP, the bin (binary) file transfer mode is intended for transferring compiled files (executables). The ascii file transfer mode is intended for transferring text files, such as config files. The default selection of bin mode should be sufficient in all cases when copying files to a remote FTP server.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, the filename.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, the filename.

•disk0:[path/]filename—Specifies a file destination in the disk0: file system of Flash memory. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

•image:image_name—Specifies to copy a system software image to Flash memory. Use the boot system command as described in Chapter 1, Setting Up the ACE to specify the BOOT environment variable. The BOOT environment variable specifies a list of image files on various devices from which the ACE can boot at startup.

•running-config—Specifies to replace the running-configuration file currently residing on the ACE in RAM (volatile memory).

•startup-config—Specifies to replace the startup-configuration file currently residing on the ACE in Flash memory (nonvolatile memory).

Step 1 

(Optional) Displays the software system images available in Flash memory.

Step 2 

(Optional) Displays the version information of system software that is loaded in flash memory and currently running on the ACE.

Step 3 

Copies an ACE software system image from Flash memory to a remote server using FTP, SFTP, or TFTP.

The keywords, arguments, and options are as follows:

•filename—Name of the ACE system software image.

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, the renamed software system image.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, the renamed software system image.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, the renamed software system image.

When you select a destination file system using ftp:, sftp:, or tftp:, the ACE performs the following tasks:

•Prompts you for your username and password if the destination file system requires user authentication.

•Prompts you for the server information if you do not provide the information with the command.

•Copies the file to the root directory of the destination file system if you do not provide path information.

Step 1 

(Optional) Displays a list of available zipped files on the disk0: file system.

The arguments are as follows:

•directory/—(Optional) Contents of the specified directory.

•path/—(Optional) Path to display the contents of a specific directory on the disk0: file system.

•filename—(Optional) Information that relates to the specified file, such as the file size and the date it was created. You can use wildcards in the filename. A wildcard character (*) matches all patterns. Strings after a wildcard are ignored.

Step 2 

Uncompresses (unzips) LZ77 coded files in the disk0: file system.

The filename argument identifies the name of the compressed file on the disk0: file system. The filename must end with a .gz extension.

Untars a single file with a .tar extension in the disk0: file system.

The filename argument identifies the name of the .tar file in the disk0: file system. You can optionally provide a path to the .tar file if it exists in another directory in the disk0: file system.

Create a directory in the disk0: file system of Flash memory.

The arguments are as follows:

•path/—(Optional) Path on the disk0: file system to the new directory. Specify the optimal path if you want to create a directory within an existing directory.

•directory—Name of the directory to create in disk0:. If a directory with the same name already exists, the ACE does not create the new directory and the "Directory already exists" message appears.

Step 1 

(Optional) Displays the contents of the disk0: file system.

Step 2 

Removes an existing directory from the disk0: file system of Flash memory.

The directory argument provides the name of the directory to delete from the disk0: file system. The directory must be empty before you can delete it. You can optionally provide a path to a directory in the disk0: file system.

Step 1 

(Optional) Displays the files available in the disk0: file system.

Step 2 

Moves a file between directories in the disk0: file system.

The keywords and arguments are as follows:

•source_directory—(Optional) Name of the source directory in the disk0: file system.

•destination_directory—(Optional) Name of the destination directory in the disk0: file system.

•filename—Name of the file to move in the disk0: file system.

Step 1 

(Optional) Displays the files available in the specified file system.

Step 2 

Delete a file from a specific file system in the ACE.

The keywords and arguments are as follows:

•core:filename—Deletes the specified file from the core: file system (see the "Managing Core Dump Files" section). The delete cores: command is available only in the Admin context.

•disk0:[directory/]filename— Deletes the specified file from the disk0: file system (for example, a packet capture buffer file or system message log). You can optionally provide a path to a file in directory in the disk0: file system.

•image:filename—Deletes the specified file from the image: file system. The delete image: command is available only in the Admin context.

•volatile:filename—Deletes the specified file from the volatile: file system.

dir {core: | disk0:[directory/][filename] | image:[filename] | probe:[filename] | volatile:[filename]}

Displays a detailed list of directories and files contained within the specified file system on the ACE, including names, sizes, and time created.

The keywords and arguments are as follows:

•core:—Displays the contents of the core: file system.

•disk0:—Displays the contents of the disk0: file system.

•image:—Displays the contents of the image: file system.

•probe:—Displays the contents of the probe: file system. This directory contains the Cisco-supplied scripts. For more information about these scripts, see the Cisco 4700 Series Application Control Engine Appliance Server Load-Balancing Configuration Guide.

•volatile:—Displays the contents of the volatile: file system.

•directory/—(Optional) Contents of the specified directory.

•filename—(Optional) Information that relates to the specified file, such as the file size and the date it was created. You can use wildcards in the filename. A wildcard character (*) matches all patterns. Strings after a wildcard are ignored.

show file {disk0: [path/]filename | volatile: filename} [cksum | md5sum]

Displays the contents of a specified file in a directory in Flash memory or in nonvolatile memory.

The keywords, arguments, and options are as follows:

•disk0: [path/]filename—Specifies the name of a file residing in the disk0: file system of Flash memory (for example, a packet capture buffer file or system message log). You can optionally provide a path to a file in a directory in the disk0: file system.

•volatile: filename—Specifies the name of a file in the volatile memory file system of the ACE.

•cksum—(Optional) Displays the cyclic redundancy check (CRC) checksum for the file. The checksum values compute a CRC for each named file. Use this option to verify that the file is not corrupt. You compare the checksum output for the received file against the checksum output for the original file.

•md5sum—(Optional) Displays the MD5 checksum for the file. MD5 is an electronic fingerprint for the file. MD5 is the latest implementation of the internet standards described in RFC 1321 and is useful for data security and integrity.

Saves a show command output to a file.

The arguments, keywords, and options are as follows:

•|—(Optional) Enables an output modifier that filters the command output.

•begin pattern—Begins with the line that matches the pattern that you specify.

•count—Counts the number of lines in the output.

•end pattern—Ends with the line that matches the pattern that you specify.

•exclude pattern—Excludes the lines that match the pattern that you specify.

•include pattern—Includes the lines that match the pattern that you specify.

•last—Displays the last few lines of the output.

•more—Displays one window page at a time.

•>—(Optional) Enables an output modifier that redirects the command output to a file.

•filename—Name of the file that the ACE saves the output to on the volatile: file system.

•disk0:—Specifies that the destination is the disk0: file system on the ACE Flash memory.

•volatile:—Specifies that the destination is the volatile: file system on the ACE.

•[path/][filename]—(Optional) Path and filename to the disk0: or volatile: file system.

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, a filename.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, a filename.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, a filename.

Step 1 

changeto

Example:

host1/Admin# changeto C1

host1/C1#

Changes to the specified context. Be sure that you are in the context that you wish to back up. To back up all contexts in the ACE, you must be in the Admin context.

Step 2 

backup [all][pass-phrase text_string][exclude component]

Example:

host1/Admin# backup all pass-phrase my_pass_phrase exclude checkpoints

host1/Admin#

Backs up configuration files and dependencies in the current context or in all contexts in the ACE.

The keywords and arguments of this command are as follows:

•all—(Optional) Specifies that the ACE should back up the configuration files and dependencies in all contexts. You can specify this keyword only in the Admin context.

•pass-phrase text_string—(Optional) Passphrase that you specify to encrypt the backed up SSL certificates or keys. Enter the passphrase as an unquoted text string with no spaces and a maximum of 40 alphanumeric characters. You must enter the pass-phrase keyword before the exclude keyword. If you enter a passphrase and then exclude the SSL files from the archive, the ACE does not use the passphrase.

Note If you imported SSL certificates or keys with a crypto passphrase, you must use the pass-phrase option to encrpyt the crypto passphrase when you back up these files.

•exclude component—(Optional) Specifies the components that you do not wish to back up.

You can enter any of the following components in any order separated by a comma if you enter more than one:

–checkpoints—Excludes all checkpoints

–ssl-files—Excludes SSL certificate files and key files

Step 3 

show backup status [detail]

Example:

host1/Admin# show backup status detail

(Optional) Displays the progress of the backup process for each component in the different ACE contexts. Use the detail option to view the components or files that have already been backed up in each context. When the backup is finished, the command displays the status as SUCCESS.

Step 4 

show backup errors

Example:

host1/Admin# show backup errors

(Optional) If the backup fails, displays the errors that occurred during the backup process.

Step 1 

changeto

Example:

host1/Acmin# changeto C1

host1/C1#

Changes to the specified context. Be sure that you are in the context in which you wish to restore the backup archive. To restore an ACE-wide backup archive completely, you must be in the Admin context.

Step 2 

restore {[all] disk0:archive_filename} [pass-phrase text_string] [exclude {licenses | ssl-files}]

Example:

host1/Admin# restore disk0:switch_Admin_07_July_2009_11_08_04_A M.tgz pass-phrase MY_PASS_PHRASE

Restores configuration files and dependencies in the current context or in all contexts in the ACE.

The keywords and arguments of this command are as follows:

•all—(Optional) Specifies that the ACE should restore the configuration files and dependencies in all contexts. You can specify this keyword only in the Admin context.

•disk0:archive_filename—Name of the archive file that you want to restore.

•pass-phrase text_string—(Optional) Passphrase that you used to encrypt the backed up SSL keys in the archive. You must enter the pass-phrase option before you enter the exclude option. Enter the passphrase as an unquoted text string with no spaces and a maximum of 40 alphanumeric characters. If you used a passphrase when you backed up the SSL keys, the ACE encrypted the keys with AES-256 encryption using OpenSSL software. To restore the SSL keys, you must enter that same passphrase.

Note If you forget your passphrase, import the required SSL files first. Then, use the exclude option of the restore command to restor e the archive.

•exclude—(Optional) Instructs the ACE not to restore the following specified files:

–licenses—Excludes license files from the restoration. Use this option when you want to keep the license files that are already installed in the ACE and ignore the license files in the backup archive, if any.

Note If you upgrade to software version A4(1.0) or later from a release before A4(1.0), the ACE cannot install the earlier license files because they are unsupported. The ACE ignores these license files and keeps the existing licenses.

–ssl-files—Excludes SSL certificates and keys from the restoration. Use this option only if you want to keep the SSL files already present in your ACE and ignore the SSL files in the backup archive, if any.

Note If you enter the exclude option first, you cannot enter the pass-phrase option.

Step 3 

show restore status [detail]

Example:

host1/Admin# show restore status

(Optional) Displays the progress of the restore process by displaying the context. Use the detail option to view the components or files that have already been backed up in each context. When the restore is finished, the command displays the status as SUCCESS.

Step 4 

show restore errors

Example:

host1/Admin# show restore errors

(Optional) If the restore fails, displays the errors that occurred during the restore process.

Step 1 

changeto

Example:

host1/Admin# changeto C1

host1/C1#

Changes to the specified context. Be sure that you are in the context in which you wish to restore the backup archive. To restore an ACE-wide backup archive completely, you must be in the Admin context.

Step 2 

config

Example:

host1/Admin# config

host1/Admin(config)#

Enters configuration mode on the active member of the FT group.

Step 3 

ft group group_id

no inservice

Example:

host1/Admin(config)# ft group 1

host1/Admin(config-ft-group)# no inservice

Disables redundancy for the members of the FT group. You must take the FT group out of service before you can restore the archive on the standby ACE. Otherwise, configuration mode is disabled on the standby ACE and the restoration will fail with the following error message:

Archive restore not allowed when config mode is disabled.

Step 4 

Ctrl-Z

Example:

host1/Admin(config-ft-group)# Ctrl-Z

host1/Admin#

Returns to Exec mode from any configuration mode.

Step 5 

restore {[all] disk0:archive_filename} [pass-phrase text_string] [exclude {licenses | ssl-files}]

Example:

host1/Admin# restore disk0:switch_Admin_07_July_2009_11_08_04_A M.tgz pass-phrase MY_PASS_PHRASE

Restores configuration files and dependencies in the current context or in all contexts in the ACE.

The keywords and arguments of this command are as follows:

•all—(Optional) Specifies that the ACE should restore the configuration files and dependencies in all contexts. You can specify this keyword only in the Admin context.

•disk0:archive_filename—Name of the archive file that you want to restore.

•pass-phrase text_string—(Optional) Passphrase that you used to encrypt the backed up SSL keys in the archive. You must enter the pass phrase before you use the exclude option. Enter the passphrase as an unquoted text string with no spaces and a maximum of 40 alphanumeric characters. If you used a passphrase when you backed up the SSL keys, the ACE encrypted the keys with AES-256 encryption using OpenSSL software. To restore the SSL keys, you must enter that same passphrase.

Note If you forget your passphrase, import the required SSL files first. Then, use the exclude option of the restore command to restor e the archive.

•exclude—(Optional) Instructs the ACE not to restore the following specified files:

–licenses—Excludes license files from the restoration. Use this option when you want to keep the license files that are already installed in the ACE and ignore the license files in the backup archive, if any.

Note If you upgrade to software version A4(1.0) or later from a release before A4(1.0), the ACE cannot install the earlier license files because they are unsupported. The ACE ignores these license files and keeps the existing licenses.

–ssl-files—Excludes SSL certificates and keys from the restoration. Use this option only if you want to keep the SSL files already present in your ACE and ignore the SSL files in the backup archive, if any.

Step 6 

config

Example:

host1/Admin# config

host1/Admin(config)#

Enters configuration mode on the active member of the FT group.

Step 7 

ft group group_id

inservice

Example:

host1/Admin(config)# ft group 1

host1/Admin(config-ft-group)# inservice

Enables redundancy for both members of the FT group.

Step 8 

Ctrl-Z

Example:

host1/Admin(config-ft-group)# Ctrl-Z

host1/Admin#

Returns to Exec mode from any configuration mode.

Step 9 

show restore status [detail]

Example:

host1/Admin# show restore status detail

(Optional) Displays the progress of the restoration. Use the detail option to view the components or files that have been restored in each context. When the restoration is finished, the command displays the status as SUCCESS.

Step 10 

show restore errors

Example:

host1/Admin# show restore errors

(Optional) If the restoration fails, displays the errors that occurred during the restore process.

Step 1 

changeto

Example:

host1/Admin# changeto C1

host1/C1#

Changes to the specified context. Be sure that you are in the context from which you wish to copy the backup archive.

Step 2 

copy {backup | backup-all} {ftp:[//path] | sftp:[//path}}

Example:

host1/Admin# config

host1/Admin(config)#

Copies a single-context or an ACE-widebackup archive to an FTP or an SFTP server. The keywords of this command are as follows:

•backup—Copies the last successful single-context backup archive to the specified FTP or SFTP server. This keyword is available in both the Admin context and user contexts.

•backup-all—Copies the last successful ACE-wide (all contexts) backup archive to the specified FTP or SFTP server. This keyword is available only in the Admin context.

•ftp:[//path] | sftp:[//path]—Specifies the FTP or SFTP server where you want to copy the backup archive and, optionally, the file path or URI.

Note If you renamed or deleted the backup archive in a context, the copy backup command fails and the ACE displays an error message.

show backup status [detail]

Displays the the status of the last backup operation. Backup status details are not stored across reboots.

Possible values in the Status column are as follows:

•SUCCESS—The component was successfully backed up

•FAILED—The component failed to be backed up

•N/A—The component (for example, a checkpoint or probe script) being backed up contains 0 files

show restore status [detail]

Displays the status of the last restoration. Restoration status details are not stored across reboots.

show backup errors

Displays errors that occur during a backup operation. For information about backup system messages, see the Cisco 4700 Series Application Control Engine Appliance System Message Guide.

show restore errors

Displays errors that occur during a restore operation. For information about restore system messages, see the Cisco 4700 Series Application Control Engine Appliance System Message Guide.

Step 1 

(Optional) Displays the list of available core files. You can copy the complete filename (for example, 0x401_vsh_log.25256.tar.gz) into the copy core: command.

Step 2 

Saves a core dump from the ACE to the disk0: file system or to a remote server.

The keywords, arguments, and options are as follows:

•filename—Core dump that resides on the ACE in Flash memory.

•disk0:[path/][filename]—Specifies a file location for the core dump in the disk0: file system and a filename for the core.

•ftp://server/path[/filename]—Specifies the FTP network server and, optionally, the renamed core dump.

When using FTP, the bin (binary) file transfer mode is intended for transferring compiled files (executables). The ascii file transfer mode is intended for transferring text files, such as config files. The default selection of bin mode should be sufficient in all cases when copying files to a remote FTP server.

•sftp://[username@]server/path[/filename]—Specifies the SFTP network server and, optionally, the renamed core dump.

•tftp://server[:port]/path[/filename]—Specifies the TFTP network server and, optionally, the renamed core dump.

When you select a destination file system using ftp:, sftp:, or tftp:, the ACE performs the following tasks:

•Prompts you for your username and password if the destination file system requires user authentication.

•Prompts you for the server information if you do not provide the information with the command.

•Copies the file to the root directory of the destination file system if you do not provide path information.

Step 1 

(Optional) Displays the list of available core files.

Step 2 

Clears out all of the core dumps stored in the core: file system.

Step 1 

(Optional) Displays the list of available core files. You can copy the complete filename (for example, 0x401_vsh_log.25256.tar.gz) into the delete core: command.

Step 2 

Deletes a core dump file from the core: file system in Flash memory.

The filename argument specifies the name of a core dump file located in the core: file system.

Enables the packet capture function on the ACE for packet sniffing and network fault isolation.

The keywords, arguments, and options are as follows:

•buffer_name—Name of the packet capture buffer. This argument associates the packet capture with a name. Specify a text string from 1 to 80 alphanumeric characters.

•all—Specifies capture packets for all input interfaces.

Note To capture application acceleration and optimization traffic bound for the optional Cisco AVS 3180A Management Station interface, use the all keyword. This keyword captures all the traffic on all interfaces. You can then transfer the packet capture file to a remote machine to be scanned for traffic that is specific to the Management Station interface.

•interface—Specifies the interface from which to capture packets.

•vlan number—Specifies the VLAN identifier associated with the specified input interface.

•access-list name—Selects packets based on an existing access list. A packet must pass the access list filters before the packet is stored in the capture buffer. Specify a previously created access list identifier. Enter an unquoted text string with a maximum of 64 alphanumeric characters.

•bufsize buf_size—(Optional) Specifies the buffer size, in kilobytes (KB), to store the packet capture. The range is from 1 to 5000 KB. The default is 64 KB.

•circular-buffer—(Optional) Enables the packet capture buffer to overwrite itself, starting from the beginning, when the buffer is full.

•remove—Removes the packet capture configuration.

•start—Starts the packet capture function and displays the messages on the session console as the ACE receives the packets. The CLI prompt returns and you can type other commands at the same time that the ACE is capturing packets. To stop the capture process, enter stop. The packet capture function automatically stops when the buffer is full unless you enable the circular buffer function.

•stop—Stops the packet capture process after a brief delay.

Copies an existing packet capture buffer to the disk0: file system

The keywords, arguments, and options are as follows:

•capture_name—Name of the packet capture buffer in Flash memory. Specify a text string from 1 to 80 alphanumeric characters. If necessary, use the show capture command to view the files available in Flash memory. This list includes the name of existing packet capture buffers.

•disk0:—Specifies that the buffer is copied to the disk0: file system. Include a space between disk0: and a destination path.

•[path/]destination_name—Destination path (optional) and name for the packet capture buffer. Specify a text string from 1 to 80 alphanumeric characters. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

show capture buffer_name [detail [connid connection_id | range packet_start packet_end] | status]

Displays the packet information that the ACE traces as part of the packet capture function.

The keywords, arguments, and options are as follows:

•buffer_name—Name of the packet capture buffer. Specify a text string from 1 to 80 alphanumeric characters.

•detail—(Optional) Displays additional protocol information for each packet.

•connid connection_id—(Optional) Displays protocol information for a specified connection identifier.

•range packet_start packet_end—(Optional) Displays protocol information for a range of captured packets.

•status—(Optional) Displays capture status information for each packet.

For all types of received packets, the console display is in tcpdump format.

clear capture buffer_name

Clears the capture packet buffer.

The buffer_name argument specifies the name of the existing packet capture buffer to clear.

Creates a configuration checkpoint.

The name argument specifies the unique identifier of the checkpoint. Enter a text string with no spaces and a maximum of 25 alphanumeric characters.

If the checkpoint already exists, the CLI responds with the following prompt:

Checkpoint already exists

Do you want to overwrite it? (y/n)  [n] y Generating 
configuration....

Created checkpoint 'MYCHECKPOINT'

The default is n. If you do not want to overwrite the existing checkpoint, press Enter. To overwrite the existing checkpoint, enter y.

Step 1 

(Optional) Displays a list of all existing checkpoints.

Step 2 

Deletes a configuration checkpoint.

The name argument specifies the unique identifier of the checkpoint. Enter a text string with no spaces and a maximum of 25 alphanumeric characters.

Step 1 

(Optional) Displays a list of all existing checkpoints.

Step 2 

(Optional) Displays the running configuration of the specified checkpoint.

Step 3 

Rolls back the current running configuration to the previously checkpointed running configuration for the current context.

The name argument specifies the unique identifier of the checkpoint. Enter a text string with no spaces and a maximum of 25 alphanumeric characters.

Step 1 

(Optional) Displays a list of all existing checkpoints.

Step 2 

copy checkpoint:filename 
disk0:[path/]filename | image:image_name | 
startup-config | 
{ftp://server/path[/filename] | 
sftp://[username]server/path[/filename] | 
tftp://server[:port]/path[/filename]}

Example:

host1/Admin# copy 
checkpoint:CHECKPOINT1.txt 
ftp://192.168.1.2 

Enter the destination filename[]? 
[CHECKPOINT1.txt]

Enter username[]? user1

Enter the file transfer mode[bin/ascii]: 
[bin]

Password:

Passive mode on.

Hash mark printing on (1024 bytes/hash 
mark).

Note The bin (binary) file transfer mode is intended for transferring compiled files (executables). The ascii file transfer mode is intended for transferring text files, such as config files. The default selection of bin should be sufficient in all cases when copying files to a remote FTP server.

Copies the specificed checkpoint file to the specified destination.

•filename—Filename of the checkpoint file residing on the ACE in flash memory.

•disk0:[path/]filename—Specifies that the file destination is the disk0: directory of the current context and the filename for the checkpoint. If you do not provide the optional path, the ACE copies the file to the root directory on the disk0: file system.

•image:image_name—Specifies that the file destination is an image in the image: directory.

•startup-config—Specifies that the destination file is the startup-configuration file.

•ftp://server/path[/filename]—Specifies the File Transfer Protocol (FTP) network server and optional renamed checkpoint file.

•sftp://[username@]server/path[/filename]—Specifies the Secure File Transfer Protocol (SFTP) network server and optional renamed checkpoint file.

•tftp://server[:port]/path[/filename]—Specifies the Trivial File Transfer Protocol (TFTP) network server and optional renamed checkpoint file.

Step 1 

(Optional) Displays a list of all existing checkpoints.

Step 2 

Compares the specified checkpoint with the running-configuration file.

The name argument specifies the unique identifier of an existing checkpoint. Enter a text string with no spaces and a maximum of 25 alphanumeric characters.

If the checkpoint configuration is the same as the running-config, the output of this command is the following:

Checkpoint config is same as running config

If the checkpoint configuration is different from the running-config, the output will be the difference between the two configurations.

show checkpoint {all | detail name} [|] [>]

Displays information relating to the configured checkpoints.

•all—Displays a list of all existing checkpoints. The show output includes checkpoint time stamps.

•detail name—Displays the running configuration of the specified checkpoint.

Erases all data on the Flash memory and reformats it with the ext3 base file system.

If the ACE fails to extract a system image from the Grub bootloader, it prompts you to provide the location of an available system image to backup:

Failed to extract system image 
Information from Grub

backup specific imagefile? (yes/no) 
[no] yes 

Enter Image name: 
c4710ace-t1k9-mz.A4_1_0.bin

Saving Image 
[c4710ace-t1k9-mz.A4_1_0.bin]

Formatting the cf.....

Unmounting ext3 filesystems...

Unmounting FAT filesystems...

Unmounting done...

Unmounting compact flash filesystems...

format completed  successfully

Restoring Image backupimage/scimi-3.bin

kjournald starting.  Commit interval 5 
seconds

REXT3 FS on hdb2, internal journal

EXT3-fs: mounted filesystem with 
ordered data mode.

starting graceful shutdown

host1/Admin# Unmounting ext3 
filesystems...

Unmounting FAT filesystems...

Unmounting done...