CLI Configuration Guide for Cisco Unified SIP Proxy Release 9.1.x
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- September 20, 2015
Chapter: Maintaining the Cisco Unified SIP Proxy System
- Copying Configurations
- Copying the Startup Configuration from the Hard Disk to Another Location
- Copying the Startup Configuration from the Network FTP Server to Another Location
- Copying the Running Configuration from the Hard Disk to Another Location
- Copying the Running Configuration from the Network TFTP Server to Another Location
- Checking Hard Disk Memory Wear Activity
Maintaining the Cisco Unified SIP Proxy System
Copying Configurations
Use module EXEC commands to copy the startup configuration and running configuration to and from the hard disk on the Cisco Unified SIP Proxy module, the network FTP server, and the network TFTP server.
Note
Depending on the specific TFTP server you are using, you might need to create a file with the same name on the TFTP server and verify that the file has the correct permissions before transferring the running configuration to the TFTP server.
- Copying the Startup Configuration from the Hard Disk to Another Location
- Copying the Startup Configuration from the Network FTP Server to Another Location
- Copying the Running Configuration from the Hard Disk to Another Location
- Copying the Running Configuration from the Network TFTP Server to Another Location
Copying the Startup Configuration from the Hard Disk to Another Location
Starting in module EXEC mode, use the following command to copy the startup configuration on the hard disk to another location:
copy startup-config { ftp: user-id:password@ftp-server-url | tftp: tftp-server-url }
Syntax Description
This command is interactive and prompts you for the information. You cannot enter the parameters in one line. In this example, the startup configuration is copied to the FTP server, which requires a username and password to transfer files. The startup configuration file is saved on the FTP server with the filename “start”.
The following example shows the startup configuration copied to the TFTP server, which does not require a username and password. The command saves the startup configuration in the TFTP directory called “configs” as a file called “temp_start”.
Copying the Startup Configuration from the Network FTP Server to Another Location
Starting in module EXEC mode, use the following command to copy the startup configuration on the network FTP server to another location:
copy ftp: {nvram:startup-config | running-config | startup-config | system:running-config}
For a description of this command, see the CLI Command Reference for Cisco Unified SIP Proxy Release 9.1.x.
This command is interactive and prompts you for the information. You cannot enter the parameters in one line. The following example illustrates this process. In this example, the FTP server requires a username and password. This command copies the file called “start” that resides in the FTP server directory called “configs” to the startup configuration.
Copying the Running Configuration from the Hard Disk to Another Location
Starting in module EXEC mode, use the following command to copy the running configuration on the hard disk to another location:
copy running-config {ftp: user-id:password @ftps:// server/dir/filename | startup-config | tftp:tftps:// server/dir/filename }
For a description of this command, see the CLI Command Reference for Cisco Unified SIP Proxy Release 9.1.x.
The command works in two ways, depending on where you are copying the command:
- If you copy the running configuration to the startup configuration, enter the command on one line, like in the following example:
- If you copy the running configuration to the FTP or TFTP server, this command becomes interactive and prompts you for the information. You cannot enter the parameters in one line. In the following example, the running configuration is copied to the FTP server, which requires a username and password. The running configuration is copied to the directory called “configs” as a file called “saved_start”.
Copying the Running Configuration from the Network TFTP Server to Another Location
Starting in module EXEC mode, use the following command to copy the running configuration from the network TFTP server to another location:
copy t ftp: { running-config | startup-config } tftps: //server/dir/filename
Syntax Description
This command is interactive and prompts you for the information. You cannot enter the parameters in one line. The following example illustrates this process. In this example, the file called “start” that resides in the directory called “configs” on the TFTP server is copied to the startup configuration.
Checking Hard Disk Memory Wear Activity
Cisco Unified SIP Proxy tracks the use and wear of the hard disk memory as log and trace data are saved to the module. To display this data, use the show interfaces command in module EXEC mode.
The following is sample output:
Feedback