Cisco 2960 ios software download

Find A Community. Cisco Community. Join us in congratulating October's Spotlight Award Winners! Turn on suggestions.

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. All Community This category This board. Logan Kampsnider.

Upgrading Cisco X stack. Copy the. Upgrade the Master switch 1 switch first. Save and reload the device. Upgrade the other switches one at a time. Verify all switches upgraded post their reboots. Seems time intensive, but I don't see any other way to do the upgrade. Anyone else? As these features are also identified in the image name below, the following chart will identify execution types and compression formats. As of , Cisco has introduced a new naming convention for feature sets.

This new naming convention started in Below is a feature tree comprised of the new naming convention used for Cisco router images This naming convention is very similar to the router IOS naming convention. Each package contains components that support a specific set of features or functions, such as routing, security, or modular services card MSC support.

Administrators can then add and activate additional optional packages and software maintenance updates SMUs on the device as necessary to provide additional specific features and to address issues. For information about which features and components are included in a specific Cisco IOS XR Software package, see the release notes for the package.

The filename of a software image indicates the target platform, the applicable feature set, and other information about the software image contained in the file. Administrators can determine which software image and release is running on a device by issuing the show version command in the CLI and reviewing the output of the command. The name of each Cisco IOS Software image indicates the applicable hardware, feature set, software release, and other information about the image.

To determine which Cisco IOS Software image and release is running on a device, administrators can log in to the device, issue the show version command in the CLI, and then review the output of the command. To determine which Cisco IOS XE Software image and release is running on a device, administrators can log in to the device, issue the show version command in the CLI, and then review the output of the command.

The output indicates the name and type of the software release that is running on the device Administrators can additionally determine which subpackages and subpackage versions are running on the active route processor RP by issuing the show version rp active running command in the CLI and referring to the value in the Package field of the command output.

The following example shows the output of the command for the Cisco ASR X Router that is used in the preceding example:. To determine which release of Cisco IOS XR Software is running on a device, administrators can log in to the device, issue the show version command in the CLI, and then review the output of the command. Continuing with the preceding example, the output of the command is as follows for the chassis.

Note that the output also indicates where the node stores the active package Boot Device and the location of the minimum boot image MBI that is used to boot the node Boot Image. The name of each Cisco NX-OS Software image indicates the applicable hardware, feature set, software release, and other information about the image.

To determine which release of Cisco NX-OS Software is running on a device, administrators can log in to the device, issue the show version command in the CLI, and then review the output of the command.

Figure 18 shows the typical phases and milestones in the lifecycle of a software release. After the last date of support, the release has reached the end-of-life milestone and is obsolete, which means the release is not sold, manufactured, improved, repaired, maintained, or supported. For detailed information about end-of-sale and end-of-life milestones, see the End-of-Life Policy. Although software retirement is not a formal milestone in the software-release lifecycle, software releases that are published to the Software Center on Cisco.

For applicable platforms that have not reached the end-of-software-maintenance milestone, software releases are not retired and removed from the Software Center unless a viable migration path exists. A viable migration path does not cross critical memory boundaries for supported hardware and, if applicable, has a similar internal or external certification.

In addition, retirement and removal of a software release from the Software Center is subject to deferral at any time in the event that a widespread, catastrophic software defect is discovered. Regardless of whether a release is available from or is eligible for retirement and removal from the Software Center, Cisco recommends that administrators maintain copies of all software releases that are running on a network.

Cisco also recommends that administrators implement only current releases of software; Cisco does not recommend new deployments of retired software releases. However, software releases are retired primarily based on age. If Cisco retires a software release that is running on a network, it does not mean that the software should automatically be replaced on that network. In other words, if the software meets customer needs, the customer can continue to use it. In addition, the Cisco TAC will continue to provide service and support for a retired software release until the release reaches the published, last date of support.

The code selection process involves a number of different variables. Cisco recommends minimizing the number of software releases that are deployed in any network environment and establishing a software strategy that indicates which releases and images will be used by different devices that are deployed throughout the environment.

To maximize operational efficiency, it is ideal to use the same software release on devices that have similar hardware and feature deployments. For professional advice on which software releases to deploy in specific environments, contact Cisco Services.

If there is no need to change the Cisco IOS Software or Cisco NX-OS Software release train that is used by a device, the general migration path for the device is to migrate to the latest software release from that train.

The latest release will include the most current software fixes, software features, and hardware support for the train. If the train has an end-of-sale announcement, the announcement will indicate recommended trains or releases to migrate to. The examples include general guidelines; software selection must include analysis of outstanding caveats that apply to the environment where the software will be deployed.

For minimum due diligence, administrators should review the open and fixed caveats section of the release notes for any software release under evaluation. Note: Software migration is an ongoing process that requires detailed planning. Customers should work closely with their account managers when they inventory their software deployments and create a plan to migrate to more current releases. To minimize downtime during a software upgrade, administrators should review the in-service software upgrade ISSU instructions in the release notes for a release before they migrate to the release.

You can access specific members by using the session stack-member-number privileged EXEC command. The member number is appended to the system prompt. For example, the prompt for member 2 is Switch-2 , and system prompt for the stack master is Switch. Enter exit to return to the CLI session on the stack master. Only the show and debug commands are available on a specific member.

If a stack port is flapping and causing instability in the stack ring, to disable the port, enter the switch stack-member-number stack port port-number disable privileged EXEC command. To reenable the port, enter the switch stack-member-number stack port port-number enable command. A stack is in the full-ring state when all members are connected through the stack ports and are in the ready state.

When you disable a stack port and the stack is in the full-ring state, you can disable only one stack port. This message appears:. When you disable a stack port and the stack is in the partial-ring state, you cannot disable the port. Stack Port 1 on Switch 1 is connected to Port 2 on Switch 4.

While Port 1 on Switch 1 is disabled and Switch 1 is still powered on, follow these steps to reenable a stack port:. Powering on Switch 4 before enabling the Port 1 on Switch 1 might cause one of the switches to reload. If Switch 4 is powered on first, you might need to enter the switch 1 stack port 1 enable and the switch 4 stack port 2 enable privileged EXEC commands to bring up the link.

Displays stack port counters or per-interface and per-stack port send and receive statistics read from the hardware. Displays information about the Ethernet management port, including the port status and the per-interface send and receive statistics read from the hardware.

Displays summary information about the stack, including the status of provisioned switches and switches in version-mismatch mode. Stack master election specifically determined by existing stack masters. Only one of the two stack masters becomes the new stack master. The stack member with the higher priority value is elected stack master. The stack member with the saved configuration file is elected stack master. Assuming that both stack members have the same priority value, configuration file, and feature set , restart both stack members at the same time.

The stack member with the higher priority value retains its stack member number. The other stack member has a new stack member number. The stack master is retained. The new switch is added to the switch stack. One of the remaining stack members becomes the new stack master. All other stack members in the stack remain as stack members and do not reboot. Two switches become stack masters. One stack master has eight stack members. The other stack master remains as a standalone switch. Use the Mode button and port LEDs on the switches to identify which switches are stack masters and which switches belong to each stack master.

This example shows how to configure the persistent MAC address feature for a 7-minute time delay and to verify the configuration:. This example shows how to provision a switch with a stack member number of 2 for the switch stack. The show running-config command output shows the interfaces associated with the provisioned switch:.

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. This table lists the features in this module and provides links to specific configuration information:. In a homogenous stack, the bandwidth for a single stack port is 20 Gbps unlike Flexstack where the port bandwidth is 10 Gbps.

Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 2. Updated: February 18, Chapter: Managing Switch Stacks. Managing Switch Stacks Finding Feature Information Your software release may not support all the features documented in this module. Prerequisites for Switch Stacks All stack members must run the same Cisco IOS software image to ensure compatibility among stack members.

Restrictions for Switch Stacks The following are restrictions for your switch stack configuration: Stacking is not supported on switches running the LAN Lite image. All switches in the stack must be running the LAN Base image. In a mixed stack of Catalyst X and Catalyst S switches, the number of supported stack members is reduced from eight to four.

In a mixed stack of Catalyst X and Catalyst S switches, full stack bandwidth is reduced from 80 Gbps to 40 Gbps. In a mixed stack of Catalyst X and Catalyst S switches, stack convergence time is increased from milliseconds to 1 to 2 seconds. Note In a mixed stack configuration, there is limited support for some features. For more information about a specific feature, see the relevant Catalyst X configuration guide. The stack can have one of these configurations: Homogeneous stack—A Catalyst X stack with only Catalyst X switches as stack members.

A homogenous stack can have up to 8 stack members. From the stack master, you configure: System-level global features that apply to all stack members Interface-level features for each stack member The stack master contains the saved and running configuration files for the switch stack. Supported Features in a Switch Stack Supported Features in a Switch Stack The system-level features supported on the stack master are supported on the entire switch stack. Encryption Features FlexStack-Plus Fast Stack Convergence Related References Restrictions for Switch Stacks Encryption Features If the stack master is running the cryptographic universal software image supports encryption , the encryption features are available on the switch stack.

Fast Stack Convergence When a single link in a full ring stack becomes inoperable, there is a disruption in the forwarding of packets, and the stack moves to a half ring. Switch Stack Membership A switch stack has up to eight stack members connected through their stack ports.

Figure 1. Related Tasks Setting the Stack Port Speed to 10 Gbps Related References Restrictions for Switch Stacks Changes to Switch Stack Membership If you replace a stack member with an identical model, the new switch functions with exactly the same configuration as the replaced switch, assuming that the new switch referred to as the provisioned switch is using the same member number as the replaced switch.

Adding powered-on switches merging causes the stack masters of the merging switch stacks to elect a stack master from among themselves. The reelected stack master retains its role and configuration as do its stack members. All remaining switches, including the former stack masters, reload and join the switch stack as stack members. They change their stack member numbers to the lowest available numbers and use the stack configuration of the reelected stack master.

Removing powered-on stack members causes the switch stack to divide partition into two or more switch stacks, each with the same configuration.

This can cause an IP address configuration conflict in your network. If you want the switch stacks to remain separate, change the IP address or addresses of the newly created switch stacks. Note Make sure that you power off the switches that you add to or remove from the switch stack. If you remove powered-on members but do not want to partition the stack: Power off the switches in the newly created switch stacks.

Reconnect them to the original switch stack through their stack ports. Power on the switches. If you manually change the stack member number by using the switch current-stack-member-number renumber new-stack-member-number global configuration command, the new number goes into effect after that stack member resets or after you use the reload slot stack-member-number privileged EXEC command and only if that number is not already assigned to any other members in the stack.

If the number is being used by another member in the stack, the switch selects the lowest available number in the stack. If you manually change the number of a stack member and no interface-level configuration is associated with that new member number, that stack member resets to its default configuration. You cannot use the switch current-stack-member-number renumber new-stack-member-number global configuration command on a provisioned switch.

If you do, the command is rejected. If you move a stack member to a different switch stack, the stack member retains its number only if the number is not being used by another member in the stack. If it is being used, the switch selects the lowest available number in the stack. If you merge switch stacks, the switches that join the switch stack of a new stack master select the lowest available numbers in the stack. Note We recommend assigning the highest priority value to the switch that you prefer to be the stack master.

The stack master is elected or reelected based on one of these factors and in the order listed: The switch that is currently the stack master. The switch with the highest stack member priority value. To receive an assigned network number, contact your Internet service provider.

Configures the IP address and IP subnet mask. Static unicast routes are user-defined routes that cause packets moving between a source and a destination to take a specified path. Static routes can be important if the router cannot build a route to a particular destination and are useful for specifying a gateway of last resort to which all unroutable packets are sent. Establish a static route. Displays the current state of the routing table to verify the configuration.

The switch retains static routes until you remove them. When an interface goes down, all static routes through that interface are removed from the IP routing table. When the software can no longer find a valid next hop for the address specified as the forwarding router's address in a static route, the static route is also removed from the IP routing table.

You can remove all contents of a particular cache, table, or database. You can also display specific statistics. Displays the current state of the routing table. Displays the current state of the routing table in summary form. Displays platform-dependent IP unicast information.

To help you research and resolve system error messages in this release, use the Error Message Decoder tool. The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

Access to most tools on the Cisco Support website requires a Cisco. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book Updated: June 20,