Uploading an Image File by Using Tftp
Working with the Software Images
- Image Location on the Switch
- File Format of Images on a Server or Cisco.com
- Copying Image Files Using TFTP
- Copying Image Files Using FTP
- Copying Image Files Using RCP
Information About Software Images
Yous tin can archive (download and upload) software epitome files, which incorporate the system software, the Cisco IOS code, and the embedded Device Manager software.
You tin download a switch prototype file from a TFTP, FTP, or RCP server to upgrade the switch software. If you practice not have access to a TFTP server, yous tin download a software image file directly to your PC or workstation by using a spider web browser (HTTP) so by using Device Director or Cisco Network Assistant to upgrade your switch. For information about upgrading your switch by using a TFTP server or a web browser (HTTP), see the release notes.
You tin replace the electric current image with the new one or proceed the current epitome in flash memory later a download.
You can use the archive download-sw /let-characteristic-upgrade privileged EXEC command to allow installation of an image with a unlike characteristic set, for example, upgrading from the universal prototype to the IP services feature set. You tin too use the boot auto-download-sw global configuration control to specify a URL to use to go an image for automated software upgrades. When you enter this command, the principal switch uses this URL in instance of a version mismatch.
You upload a switch image file to a TFTP, FTP, or RCP server for backup purposes. You can use this uploaded prototype for futurity downloads to the same switch or to another of the same blazon.
The protocol that you use depends on which type of server you lot are using. The FTP and RCP transport methods provide faster performance and more reliable delivery of data than TFTP. These improvements are possible because FTP and RCP are built on and use the TCP/IP stack, which is connexion-oriented.
These sections contain this configuration information:
Notation 
For a list of software images and the supported upgrade paths, run into the release notes.
Image Location on the Switch
The Cisco IOS prototype is stored as a .bin file in a directory that shows the version number. A subdirectory contains the files needed for web direction. The image is stored on the organisation board flash retentivity (flash:).
You can utilize the show version privileged EXEC command to see the software version that is currently running on your switch. In the display, check the line that begins with System epitome file is.... Information technology shows the directory name in flash memory where the paradigm is stored.
You can also utilize the dir filesystem : privileged EXEC control to see the directory names of other software images that you might have stored in wink memory. You can utilise the archive download-sw /directory privileged EXEC command to specify a directory in one case followed by a tar file or list of tar files to be downloaded instead of specifying complete paths with each tar file.
File Format of Images on a Server or Cisco.com
Software images on a server or downloaded from Cisco.com are in a file format, which contains these files:
- An info file, which serves as a table of contents for the file
- One or more subdirectories containing other images and files, such as Cisco IOS images and web management files
T
| | |
|---|---|
| version_suffix | Specifies the Cisco IOS image version string suffix. |
| version_directory | Specifies the directory where the Cisco IOS paradigm and the HTML subdirectory are installed. |
| image_name | Specifies the name of the Cisco IOS image in the file. |
| ios_image_file_size | Specifies the Cisco IOS image size in the file, which is an approximate measure of the flash retentivity that the Cisco IOS paradigm needs. |
| total_image_file_size | Specifies the size of all the images (the Cisco IOS image and the web direction files) in the file, which is an approximate measure of the flash retentivity needed. |
| image_feature | Describes the core functionality of the image. |
| image_min_dram | Specifies the minimum corporeality of DRAM needed to run this image. |
| image_family | Describes the family of products on which the software tin be installed. |
Copying Image Files Using TFTP
Y'all can download a switch image from a TFTP server or upload the image from the switch to a TFTP server.
You download a switch image file from a server to upgrade the switch software. You can overwrite the electric current paradigm with the new one or proceed the electric current epitome later on a download.
You lot upload a switch image file to a server for fill-in purposes; this uploaded image can be used for future downloads to the same or some other switch of the same type.
Note Instead of using the re-create privileged EXEC control or the annal tar privileged EXEC command, we recommend using the archive download-sw and archive upload-sw privileged EXEC commands to download and upload software image files. For switch stacks, the annal download-sw and archive upload-sw privileged EXEC commands can simply be used through the stack principal. Software images downloaded to the stack principal are automatically downloaded to the remainder of the stack members.
These sections comprise this configuration information:
- Preparing to Download or Upload an Image File Using TFTP
- Downloading an Paradigm File Using TFTP
- Uploading an Image File Using TFTP
Preparing to Download or Upload an Image File Using TFTP
Before yous begin downloading or uploading an image file past using TFTP, practice these tasks:
- Ensure that the workstation interim equally the TFTP server is properly configured. On a Sun workstation, brand sure that the /etc/inetd.conf file contains this line:
Make sure that the /etc/services file contains this line:
Note Y'all must restart the inetd daemon subsequently modifying the /etc/inetd.conf and /etc/services files. To restart the daemon, either cease the inetd process and restart it, or enter a fastboot command (on the SunOS iv.x) or a reboot command (on Solaris 2.ten or SunOS v.ten). For more information on the TFTP daemon, see the documentation for your workstation.
- Ensure that the switch has a route to the TFTP server. The switch and the TFTP server must exist in the same subnetwork if you exercise not have a router to route traffic between subnets. Check connectivity to the TFTP server past using the ping command.
- Ensure that the image to exist downloaded is in the correct directory on the TFTP server (ordinarily / tftpboot on a UNIX workstation).
- For download operations, ensure that the permissions on the file are gear up correctly. The permission on the file should be world-read.
- Before uploading the epitome file, you lot might need to create an empty file on the TFTP server. To create an empty file, enter the impact filename command, where filename is the name of the file you volition use when uploading the paradigm to the server.
- During upload operations, if you are overwriting an existing file (including an empty file, if you had to create 1) on the server, ensure that the permissions on the file are set correctly. Permissions on the file should be world-write.
Downloading an Image File Using TFTP
You tin download a new paradigm file and supersede the current image or keep the current image.
Starting time in privileged EXEC mode, follow Stride 1 to download a new image from a TFTP server and to overwrite the existing image. To keep the current image, follow Step 2.
| | | |
|---|---|---|
| Stride i | archive download-sw [ /directory ] /overwrite /reload tftp: [[ // location ] / directory ] / prototype-name1 .tar [ image-name2 .tar image-name3 .tar image-name4 .tar ] | (Optional) Downloads the image files from the TFTP server to the switch, and overwrites the current epitome.
|
| Step ii | annal download-sw [ /directory ] /go out-old-sw /reload tftp: [[ // location ] / directory ] / image-name1 .tar [ epitome-name2 .tar image-name3 .tar image-name4 .tar ] | (Optional) Downloads the images file from the TFTP server to the switch and saves the current image.
|
The download algorithm verifies that the prototype is advisable for the switch model and that plenty DRAM is nowadays, or it aborts the process and reports an error. If you specify the /overwrite pick, the download algorithm removes the existing image on the wink device whether or non information technology is the same equally the new one, downloads the new epitome, so reloads the software.
Annotation If the flash device has sufficient space to concur ii images and you want to overwrite one of these images with the aforementioned version, you must specify the /overwrite choice.
If yous specify the /leave-one-time-sw, the existing files are non removed. If in that location is not enough space to install the new image and keep the electric current running prototype, the download process stops, and an error message is displayed.
The algorithm installs the downloaded image on the system board flash device (wink:). The image is placed into a new directory named with the software version string, and the Kicking surround variable is updated to bespeak to the newly installed image.
If you kept the onetime image during the download process (you specified the /exit-old-sw keyword), you can remove it by entering the delete /force /recursive filesystem :/ file-url privileged EXEC command. For filesystem, apply wink: for the organization board wink device. For file-url, enter the directory proper noun of the erstwhile image. All the files in the directory and the directory are removed.
For the download and upload algorithms to operate properly, do not rename epitome names. Uploading an Paradigm File Using TFTP
You lot can upload an image from the switch to a TFTP server. You can subsequently download this prototype to the switch or to another switch of the same type.
Use the upload feature only if the web management pages associated with Device Manager take been installed with the existing epitome.
Beginning in privileged EXEC mode, follow this step to upload an image to a TFTP server:
| | | |
|---|---|---|
| Stride 1 | archive upload-sw tftp: [[ // location ] / directory ] / image-proper name .tar | Uploads the currently running switch paradigm to the TFTP server.
|
The archive upload-sw privileged EXEC command builds an image file on the server past uploading these files in social club: info, the Cisco IOS image, and the spider web management files. After these files are uploaded, the upload algorithm creates the file format.
For the download and upload algorithms to operate properly, practise non rename prototype names. Copying Epitome Files Using FTP
You can download a switch image from an FTP server or upload the image from the switch to an FTP server.
You download a switch image file from a server to upgrade the switch software. You can overwrite the electric current image with the new one or proceed the current prototype afterward a download.
You upload a switch image file to a server for fill-in purposes. Y'all can utilise this uploaded paradigm for futurity downloads to the switch or another switch of the same blazon.
Note Instead of using the copy privileged EXEC control or the archive tar privileged EXEC command, we recommend using the archive download-sw and annal upload-sw privileged EXEC commands to download and upload software image files. For switch stacks, the archive download-sw and archive upload-sw privileged EXEC commands can only be used through the stack master. Software images downloaded to the stack primary are automatically downloaded to the rest of the stack members.
These sections contain this configuration data:
- Preparing to Download or Upload an Image File Using FTP
- Downloading an Image File Using FTP
- Uploading an Epitome File Using FTP
Preparing to Download or Upload an Image File Using FTP
You tin can copy images files to or from an FTP server.
The FTP protocol requires a client to send a remote username and password on each FTP request to a server. When you copy an image file from the switch to a server past using FTP, the Cisco IOS software sends the first valid username in this list:
- The username specified in the archive download-sw or archive upload-sw privileged EXEC command if a username is specified.
- The username set by the ip ftp username username global configuration command if the command is configured.
- Anonymous.
The switch sends the first valid password in this list:
- The password specified in the archive download-sw or archive upload-sw privileged EXEC command if a countersign is specified.
- The password set by the ip ftp password password global configuration command if the control is configured.
- The switch creates a password named username@switchname.domain. The username variable is the username associated with the current session, switchname is the configured hostname, and domain is the domain of the switch.
The username and password must be associated with an account on the FTP server. If you are writing to the server, the FTP server must be properly configured to take the FTP write request from you.
Apply the ip ftp username and ip ftp countersign commands to specify a username and password for all copies. Include the username in the annal download-sw or archive upload-sw privileged EXEC command if you want to specify a username only for that functioning.
If the server has a directory structure, the image file is written to or copied from the directory associated with the username on the server. For example, if the paradigm file resides in the dwelling directory of a user on the server, specify that user's name equally the remote username.
Earlier you begin downloading or uploading an epitome file by using FTP, complete these tasks:
- Ensure that the switch has a road to the FTP server. The switch and the FTP server must exist in the same subnetwork if you practise non have a router to route traffic between subnets. Check connectivity to the FTP server by using the ping command.
- If you lot are accessing the switch through the console or a Telnet session and you practise non have a valid username, make sure that the current FTP username is the one that you want to use for the FTP download. Yous can enter the prove users privileged EXEC control to view the valid username. If yous do non desire to utilize this username, create a new FTP username past using the ip ftp username username global configuration command. This new name will be used during all archive operations. The new username is stored in NVRAM. If y'all are accessing the switch through a Telnet session and you have a valid username, this username is used, and yous do not need to ready the FTP username. Include the username in the archive download-sw or archive upload-sw privileged EXEC command if you want to specify a username for that operation simply.
- When you lot upload an paradigm file to the FTP server, it must be properly configured to accept the write request from the user on the switch.
For more than information, see the documentation for your FTP server.
Downloading an Image File Using FTP
You can download a new image file and overwrite the current epitome or proceed the current image.
Beginning in privileged EXEC mode, follow Steps one through 7 to download a new image from an FTP server and to overwrite the existing prototype. To continue the current image, follow Steps 1 to vi and Step viii.
| | | |
|---|---|---|
| Step 1 | configure final | (Optional) Enters global configuration way on the switch. This step is required merely if you override the default remote username or password. |
| Step 2 | ip ftp username username | (Optional) Changes the default remote FTP username. |
| Step 3 | ip ftp password password | (Optional) Changes the default FTP password. |
| Step four | end | Returns to privileged EXEC mode. |
| Footstep 5 | archive download-sw [ /directory ] /overwrite /reload ftp: [[ // username[:password ] @location ]/ directory ] / epitome-name1 .tar [ image-name2 .tar paradigm-name3 .tar image-name4 .tar ] | (Optional) Downloads the image files from the FTP server to the switch, and overwrites the current image.
|
| Step 6 | archive download-sw [ /directory ] /exit-old-sw /reload ftp: [[ // username[:countersign ] @location ]/ directory ] / image-name1 .tar [ epitome-name2 .tar prototype-name3 .tar paradigm-name4 .tar ] | (Optional) Downloads the image files from the FTP server to the switch and saves the current image.
|
The download algorithm verifies that the image is appropriate for the switch model and that enough DRAM is present, or it aborts the process and reports an error. If y'all specify the /overwrite option, the download algorithm removes the existing image on the wink device, whether or not it is the same as the new one, downloads the new image, and then reloads the software.
Notation If the flash device has sufficient infinite to agree ii images and you want to overwrite i of these images with the same version, you must specify the /overwrite option.
If you specify the /leave-old-sw option, the existing files are not removed. If in that location is non enough space to install the new image and go along the running image, the download process stops, and an mistake bulletin is displayed.
The algorithm installs the downloaded paradigm onto the system lath flash device (wink:). The paradigm is placed into a new directory named with the software version string, and the Kick environs variable is updated to point to the newly installed paradigm.
If you kept the former epitome during the download process (you specified the /get out-former-sw keyword), you can remove it by entering the delete /force /recursive filesystem :/ file-url privileged EXEC control. For filesystem, utilise flash: for the system board wink device. For file-url, enter the directory name of the old software image. All the files in the directory and the directory are removed.
For the download and upload algorithms to operate properly, practise non rename image names. Uploading an Image File Using FTP
You can upload an image from the switch to an FTP server. You lot can later download this image to the same switch or to another switch of the aforementioned type.
Employ the upload characteristic only if the web management pages associated with Device Manager have been installed with the existing image.
First in privileged EXEC way, follow these steps to upload an image to an FTP server:
| | | |
|---|---|---|
| Pace 1 | configure final | (Optional) Enters global configuration mode on the switch. This stride is required merely if yous override the default remote username or password. |
| Step two | ip ftp username username | (Optional) Changes the default remote FTP username. |
| Step 3 | ip ftp password password | (Optional) Changes the default FTP password. |
| Step four | end | Returns to privileged EXEC style. |
| Step 5 | archive upload-sw ftp: [[ // [ username [ : password ] @ ] location ] / directory ] / image-proper noun .tar . | Uploads the currently running switch image to the FTP server.
|
The archive upload-sw command builds an image file on the server by uploading these files in order: info, the Cisco IOS prototype, and the spider web management files. After these files are uploaded, the upload algorithm creates the file format.
For the download and upload algorithms to operate properly, practise non rename image names. Copying Paradigm Files Using RCP
You tin download a switch paradigm from an RCP server or upload the epitome from the switch to an RCP server.
You download a switch image file from a server to upgrade the switch software. You tin can overwrite the current paradigm with the new i or keep the current epitome after a download.
You upload a switch prototype file to a server for backup purposes. You tin can use this uploaded prototype for future downloads to the same switch or another of the same type.
Note Instead of using the copy privileged EXEC command or the annal tar privileged EXEC command, we recommend using the archive download-sw and archive upload-sw privileged EXEC commands to download and upload software paradigm files. For switch stacks, the annal download-sw and archive upload-sw privileged EXEC commands tin can only be used through the stack chief. Software images downloaded to the stack master are automatically downloaded to the rest of the stack members.
These sections comprise this configuration information:
- Preparing to Download or Upload an Image File Using RCP
- Downloading an Image File Using RCP
- Uploading an Prototype File Using RCP
Preparing to Download or Upload an Image File Using RCP
RCP provides another method of downloading and uploading image files betwixt remote hosts and the switch. Different TFTP, which uses User Datagram Protocol (UDP), a connectionless protocol, RCP uses TCP, which is connection-oriented.
To employ RCP to re-create files, the server from or to which yous will exist copying files must support RCP. The RCP copy commands rely on the rsh server (or daemon) on the remote system. To copy files past using RCP, you do not demand to create a server for file distribution every bit you do with TFTP. You only demand to have admission to a server that supports the remote trounce (rsh). (Most UNIX systems back up rsh.) Because yous are copying a file from i place to another, yous must have read permission on the source file and write permission on the destination file. If the destination file does not be, RCP creates information technology for you.
RCP requires a client to transport a remote username on each RCP request to a server. When you copy an prototype from the switch to a server by using RCP, the Cisco IOS software sends the first valid username in this listing:
- The username specified in the archive download-sw or archive upload-sw privileged EXEC command if a username is specified.
- The username gear up past the ip rcmd remote-username username global configuration command if the command is entered.
- The remote username associated with the current TTY (terminal) process. For example, if the user is connected to the router through Telnet and was authenticated through the username control, the switch software sends the Telnet username equally the remote username.
- The switch hostname.
For the RCP re-create request to execute successfully, an account must be defined on the network server for the remote username. If the server has a directory structure, the epitome file is written to or copied from the directory associated with the remote username on the server. For example, if the epitome file resides in the home directory of a user on the server, specify that user's proper noun as the remote username.
Before you lot begin downloading or uploading an image file by using RCP, practice these tasks:
- Ensure that the workstation acting as the RCP server supports the remote shell (rsh).
- Ensure that the switch has a route to the RCP server. The switch and the server must be in the same subnetwork if yous exercise not have a router to road traffic betwixt subnets. Cheque connectivity to the RCP server past using the ping control.
- If you are accessing the switch through the panel or a Telnet session and you practice non have a valid username, make sure that the current RCP username is the one that you want to utilize for the RCP download. Yous can enter the show users privileged EXEC command to view the valid username. If y'all do not want to apply this username, create a new RCP username by using the ip rcmd remote-username username global configuration command to be used during all archive operations. The new username is stored in NVRAM. If yous are accessing the switch through a Telnet session and you accept a valid username, this username is used, and in that location is no need to set the RCP username. Include the username in the annal download-sw or archive upload-sw privileged EXEC command if y'all want to specify a username simply for that performance.
- When y'all upload an image to the RCP to the server, it must be properly configured to accept the RCP write request from the user on the switch. For UNIX systems, you must add together an entry to the.rhosts file for the remote user on the RCP server. For example, suppose the switch contains these configuration lines:
If the switch IP address translates to Switch1.visitor.com, the.rhosts file for User0 on the RCP server should comprise this line:
For more information, see the documentation for your RCP server.
Downloading an Image File Using RCP
You can download a new paradigm file and replace or keep the current image.
Beginning in privileged EXEC mode, follow Steps i through half dozen to download a new prototype from an RCP server and overwrite the existing prototype. To continue the current paradigm, become to Step 6.
| | | |
|---|---|---|
| Step 1 | configure last | Enters global configuration mode. This pace is required just if you override the default remote username (encounter Steps iv and 5). |
| Pace 2 | ip rcmd remote-username username | (Optional) Specifies the remote username. |
| Step 3 | finish | Returns to privileged EXEC manner. |
| Step iv | archive download-sw /overwrite /reload rcp: [[ // [username@location ] / directory ] / image-name1 .tar [ image-name2 .tar image-name3 .tar image-name4 .tar ] | Downloads the images file from the RCP server to the switch and overwrites the current image.
|
| Step 5 | archive download-sw /get out-one-time-sw /reload rcp: [[ // [username@location ] / directory ] / prototype-name1 .tar [ image-name2 .tar prototype-name3 .tar prototype-name4 .tar ] | Downloads the images file from the RCP server to the switch and saves the current image.
|
The download algorithm verifies that the image is advisable for the switch model and that enough DRAM is present, or information technology aborts the process and reports an error. If you specify the /overwrite option, the download algorithm removes the existing image on the flash device whether or not information technology is the aforementioned as the new one, downloads the new image, and and then reloads the software.
Note If the wink device has sufficient space to hold ii images and you want to overwrite one of these images with the same version, yous must specify the /overwrite selection.
If you specify the /go out-old-sw, the existing files are not removed. If in that location is not enough room to install the new prototype and go on the running prototype, the download process stops, and an error message is displayed.
The algorithm installs the downloaded prototype onto the organization board flash device (flash:). The epitome is placed into a new directory named with the software version string, and the BOOT environment variable is updated to indicate to the newly installed paradigm.
If you kept the erstwhile software during the download process (you lot specified the /leave-old-sw keyword), you can remove it by entering the delete /force /recursive filesystem :/ file-url privileged EXEC command. For filesystem, use flash: for the system board wink device. For file-url, enter the directory proper noun of the old software image. All the files in the directory and the directory are removed.
For the download and upload algorithms to operate properly, do non rename image names. Uploading an Epitome File Using RCP
Y'all tin upload an image from the switch to an RCP server. Y'all tin can later download this image to the same switch or to another switch of the aforementioned type.
The upload feature should be used merely if the web direction pages associated with Device Manager have been installed with the existing paradigm.
Outset in privileged EXEC mode, follow these steps to upload an paradigm to an RCP server:
| | | |
|---|---|---|
| Stride 1 | configure terminal | Enters global configuration way. This step is required only if y'all override the default remote username (see Steps 4 and 5). |
| Step 2 | ip rcmd remote-username username | (Optional) Specifies the remote username. |
| Step 3 | terminate | Returns to privileged EXEC way. |
| Step 4 | archive upload-sw rcp: [[[ // [ username @ location ] / directory ] / image-name .tar ] | Uploads the currently running switch prototype to the network server.
|
The annal upload-sw privileged EXEC command builds an epitome file on the server by uploading these files in order: info, the Cisco IOS image, and the web direction files. After these files are uploaded, the upload algorithm creates the file format.
For the download and upload algorithms to operate properly, practice not rename paradigm names. Source: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960xr/software/15-0_2_EX1/file_management/file_management/img_files.html
0 Response to "Uploading an Image File by Using Tftp"
Post a Comment