Cisco 2960-24tt ios 15 download

When creating a switch cluster or adding a switch to a cluster, follow these guidelines:. Cisco IOS A subdirectory contains the files needed for web management. The image is stored on the system board flash device flash:. You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version. You can also use the dir filesystem : privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.

The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. Catalyst LAN Base cryptographic image file and device manager files. Catalyst LAN Lite cryptographic image file and device manager files.

Catalyst C image with all supported universal image features and Web-based device manager. Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.

You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.

We recommend that you download the tar file from Cisco. You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help. Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins.

Wait until after the upgrade process completes. This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.

Step 1 Use Table 3 to identify the file that you want to download. Step 2 Download the software image file:. If you are a registered customer, go to this URL and log in. Navigate to your switch model. Download the image you identified in Step 1. For more information, see Appendix B in the software configuration guide for this release.

Step 4 Log into the switch through the console port or a Telnet session. For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release. If you are installing the same version of software that is currently on the switch, overwrite the current image by entering this privileged EXEC command:.

Directory and image names are case sensitive. This example shows how to download an image from a TFTP server at Use these methods to assign IP information to your switch:.

Note Device Classifier has been disabled by default starting from Release Any features dependent on device classifier should enable it if required.

Provides quick and easy access to all relevant documentation for specific platforms. Look for Quick Links to Platform Documentation on the respective platform documentation pages. Provides platform and software documentation for two technologies:. Eliminates the overhead of manual post install configuration on all the switches, in the smart install network.

This is a read--only DHCP functionality. The banner page allows you to logon to the server when the session is invalid or expired. This feature is enabled by default and requires no configuration. This feature also permits hard binding between the end device and the interface.

Autoconfig falls under the umbrella of Smart Operations solution. An interface template is a container of configurations or policies that can be applied to specific ports. The existing NMSP connections will use the default cipher. Catalyst P Switch Smart Install is a plug-and-play configuration and image-management feature that provides zero-touch deployment for new switches. You can ship a switch to a location, place it in the network and power it on with no configuration required on the device.

Table 4 lists the minimum software release required to support the major features of the Catalyst S, C, and C switches and the Cisco EtherSwitch service modules. NEAT enhancement to control access to the supplicant port. Auto Smartports enhancements to enable auto-QoS on a digital media player. Auto Smartport enhancements including global macros. MAC replace to end a session when a host disconnects from a port.

You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software. The workaround is to enter the no switchport block unicast interface configuration command on that specific interface.

There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. The workaround is to configure aggressive UDLD. The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. The workaround is to disable authorization and accounting or to enter the configuration change for one interface at a time. If this happens, uneven traffic distribution will happen on EtherChannel ports.

Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:. For example, with load balance configured as dst-ip with distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal. The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state.

The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. The workaround is to power the access point by using an AC wall adaptor. The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value.

The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic. The workaround is to enter the clear ip mroute privileged EXEC command on the interface. After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.

The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. The workaround is to choose compatible buffer sizes and threshold levels.

The workaround to this issue is to use an on-demand upgrade to upgrade switches in the stack by entering the vstack download config and vstack download image commands.

You should also configure the tar image name instead of the image-list file name in the stored images. FIPS is a cryptographic-focused certification, required by many government and enterprise customers, which ensures the compliance of the encryption and decryption operations performed by the switch to the approved FIPS cryptographic strengths and management methods for safeguarding these operations. For more information, see:. REP is a Cisco proprietary protocol that provides an alternative to Spanning Tree Protocol STP to control network loops, handle link failures, and improve convergence time in ring topologies.

See the Configuring Resilient Ethernet Protocol chapter in the software configuration guide on cisco. The vstack startup-vlan command has been added. For more information, see the command reference on Cisco. LAN Base image for Catalys t For more information, see the Configuring Port-Based Traffic Control chapter in the software configuration guide.

Table 5 lists the minimum software release required to support the major features of the Catalyst , , S, and switches and the Cisco EtherSwitch service modules. Customizable web authentication enhancement to allow the creation of user-defined pages. Cisco Medianet to enable intelligent services in the network infrastructure for video applications. You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround.

Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.

Unless otherwise noted, these limitations apply to the Catalyst , and , and switches and the Cisco EtherSwitch service modules:. The workaround is to reconfigure the static IP address. The problem is observed only when the switch is receiving frames. The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.

The switch rejects a CLI command to change the baud rate. To change the baud rate, reload the Cisco EtherSwitch service module with the bootloader prompt. You can then change the baud rate and change the speed on the TTY line of the router connected to the Cisco EtherSwitch Service module console. This does not affect switch functionality. However, the client does not keep trying to download the configuration.

The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. The workaround is to use the session stack-member-number privileged EXEC command.

The workaround is to disable authorization and accounting or to enter the configuration change for one interface at a time. If the internal Gigabit Ethernet interface on a Cisco EtherSwitch service module connected to the router is configured as a switch port in access mode or in trunk mode, the internal link is not operational until it reaches the STP forwarding state.

Therefore, the PoE that comes from the host router is also not available until the internal Gigabit Ethernet link reaches the STP forwarding state. This is due to STP convergence time. This problem does not occur on routed ports. If the Cisco EtherSwitch service module is in access mode, the workaround is to enter the spanning-tree portfast interface configuration command on the internal Gigabit Ethernet interface. If the service module is in trunk mode, there is no workaround. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address.

More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC. If this happens, uneven traffic distribution will happen on EtherChannel ports. Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:.

For example, with load balance configured as dst-ip with distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal. The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking state, see the "Configuring STP" chapter in the software configuration guide. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring.

Because learning is restricted on IEEE The workaround is to enter the power inline never interface configuration command on all the Fast Ethernet ports that are not powered by but are connected to IP phones if the problem persists.

These access points should be discovered as Cisco pre-standard devices. The workaround is to power the access point by using an AC wall adaptor. The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port.

The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic. The workaround is to enter the clear ip mroute privileged EXEC command on the interface.

After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table. You should use the power inline never interface configuration command on Cisco EtherSwitch service module ports that are not connected to PoE devices.

The remaining power shown is available for allocation to switching ports on all Cisco EtherSwitch service modules in the router.

To display the total power used by a specific EtherSwitch service module, enter the show power inline command on the router. To keep the current image, follow Step 2. Optional Downloads the image files from the TFTP server to the switch, and overwrites 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 there is not enough space to install the new image and keep the current running image, the download process stops, and an error message is displayed.

The algorithm installs the downloaded image on the system board flash device flash:. The image is placed into a new directory named with the software version string, and the BOOT environment variable is updated to point to the newly installed image. For filesystem , use flash: for the system board flash device. For file-url , enter the directory name of the old image. All the files in the directory and the directory are removed. You can upload an image from the switch to a TFTP server.

You can later download this image 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 have been installed with the existing image. Uploads the currently running switch image to the TFTP server. The archive upload-sw privileged EXEC command builds an image file on the server by uploading these files in order: info, the Cisco IOS image, and the web management files.

After these files are uploaded, the upload algorithm creates the file format. You upload a switch image file to a server for backup purposes. You can use this uploaded image for future downloads to the switch or another switch of the same type. You can copy images files to or from an FTP server.

When you copy an image file from the switch to a server by using FTP, the Cisco IOS software sends the first valid username in this list:. The switch sends the first valid password in this list:. 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 accept the FTP write request from you. Use the ip ftp username and ip ftp password commands to specify a username and password for all copies.

Include the username in the archive download-sw or archive upload-sw privileged EXEC command if you want to specify a username only for that operation. 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 image file resides in the home directory of a user on the server, specify that user's name as the remote username. Before you begin downloading or uploading an image file by using FTP, complete these tasks:.

For more information, see the documentation for your FTP server. You can download a new image file and overwrite the current image or keep the current image. To keep the current image, follow Steps 1 to 6 and Step 8. Optional Enters global configuration mode on the switch. This step is required only if you override the default remote username or password. Optional Changes the default remote FTP username.

Optional Downloads the image files from the FTP server to the switch, and overwrites the current image. Optional Downloads the image files from the FTP server to the switch, and saves the current image.

If there is not enough space to install the new image and keep the running image, the download process stops, and an error message is displayed. The algorithm installs the downloaded image onto the system board flash device flash:. For file-url , enter the directory name of the old software image. You can upload an image from the switch to an FTP server. You can later download this image to the same switch or to another switch of the same type.

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 image, and the web management files.

You can use this uploaded image for future downloads to the same switch or another of the same type. RCP provides another method of downloading and uploading image files between remote hosts and the switch.

The RCP copy commands rely on the rsh server or daemon on the remote system. You only need to have access to a server that supports the remote shell rsh.

Most UNIX systems support rsh. Because you are copying a file from one place to another, you must have read permission on the source file and write permission on the destination file.

If the destination file does not exist, RCP creates it for you. For the RCP copy request to execute successfully, an account must be defined on the network server for the remote username.