More technical and security articles on Catalyst switch can be found at our Cisco Catalyst Switches Section. Back to Cisco Switches Section. Deal with bandwidth spikes Free Download. Web Vulnerability Scanner Free Download. Network Security Scan Download Now. Password Recovery — Reset Procedure The procedure described below assumes the password recovery mechanism is enabled by default, it is and there is physical access to the switch or stack X only. Step 1 On a X switch, Power off the entire stack or standalone switch.
Step 2 Reconnect the power to the switch standalone X or X or stack master X stack only. If the process has been followed correctly, the following message should be displayed:.
Some feature sets contain the same features as others; this will be discussed later in the lab. First way being to examine the boot dispatch, this will display the image name that is loaded from flash which in return can be used to identify the IOS Version and Feature Set of the image. Provided below is an example of the required dispatch from the boot process which can be used to identify which IOS Version and Feature Sets the router is currently loading.
Turn your attention to line 2 where you see CIK9O3S7-M ; this displays the features that are included in the image and the loading type which will be discussed later for the image that is currently be loaded by the Router. Following the feature set being loaded you can also see the Version of the IOS. As shown in this example, the router is currently booting IOS Version The most common way of obtaining IOS identification information is by using the show version command.
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. Throughout the lifecycle of a software release, Cisco publishes software advisories for informational purposes.
These advisories often describe problems that are hardware-specific or occur under unusual circumstances and therefore do not affect most customers. Often, no customer action is required. However, the following communications do require customers to evaluate the potential impact of the underlying problem on their networks and take appropriate action:. This document is part of the Cisco Security portal.
Cisco provides the official information contained on the Cisco Security portal in English only. Your use of the information in the document or materials linked from the document is at your own risk. Cisco reserves the right to change or update this document without notice at any time. Provides Cisco IOS Software functionality and hardware support for enterprise, access, and commercial networks.
This software release family incorporates hardware support and software features that were introduced in the Cisco IOS Software But the ports that are configured to be trunk and that are in the 'notconnected' status also show up in the show vlan output. Note: The ports that display are only those ports that you have configured as Layer 2 nontrunk access ports.
The ports that are configured to be trunk and that are in the 'notconnected' status also show up in the show vlan output. There is currently no specific troubleshooting information available for this configuration. For common problems that relate to trunking and Contents Introduction. Use your! For more details,! This is visible only when you set VTP mode!
0コメント