That means that there have been 8 rounds of bug fixes for this version of IOS. Older ISR mainline versions use lowercase numbers in alphabetical order to indicate the same convention.
In our example the IOS versions would have been:. One thing to note is that when an IOS version is established it effectively has a rebuild number of 0, which is then suppressed.
This may help some understand that each rebuild is just an improvement upon the previous version. You may see sometimes that a software bug has an integrated fix in one of such interim images, For example, Please note that the best practice recommendations below are generic and may not apply to all the networks. Before implementing any of the recommendations below, please evaluate them in context of your network requirements. As a general rule an IOS version with more rebuilds would be expected to be more stable than a previous version with less rebuilds.
When moving from one IOS version to another, closer the destination IOS is to the current IOS, less you need to worry about important things changing, like memory requirements, commands being deprecated, hardware not supported in previous versions, etc. Upgrading to the latest revision, On the other hand, downgrading from When downgrading an IOS glance over the configuration to see if any new features are in use that may not be supported on the downgrade target IOS.
If possible run mainline If possible, avoid running T Train Technology Train, New features are introduced in T Train and generally there is a potential for more issues because of this. Please note that new equipment may require T Train IOS image, as usually there will not be a supported mainline version of IOS at the time the new hardware is released.
You can recognize a modular IOS because it has a "v" in the filename instead of "m". For example:. Skip to content Skip to search Skip to footer. Available Languages. Download Options. Updated: February 17, The feature sets are:. Cisco IOS Software for other models of Cisco switches and routers can use any of seven different software packages, depending on the model, to meet the requirements of different market categories. The software packages are:.
The name of a software image indicates which software package the image contains and whether the image includes strong cryptography features. If an image name contains the k9 designation, the image includes strong cryptography features. For example, if an image name contains adventerprisek9 , the image contains an Advanced Enterprise Services package that includes strong cryptographic features. A consolidated package is a single software image that contains a collection of software subpackages.
A subpackage is an individual software file that provides a specific set of functionality or controls a different element or elements of a router or switch. The diagram also shows how each subpackage provides a different set of functionality that complements or supports the functionality provided by one or more other subpackages in the same consolidated package.
The consolidated package architecture enables administrators to install and upgrade the software by using a holistic or modular approach. Administrators can install and run all the subpackages in a consolidated package or only specific subpackages in a consolidated package.
In addition, administrators can upgrade the software by performing a single, complete upgrade process that upgrades all the subpackages in a consolidated package or they can upgrade each software subpackage independently.
For more information about the advantages and disadvantages of running individual subpackages or complete consolidated packages, and the process of extracting individual subpackages from a consolidated package, see the Cisco ASR Series Aggregation Services Routers Software Configuration Guide.
For information about which consolidated packages are available for a specific release of Cisco IOS XE Software, see the release notes for the release. 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 This train is designed primarily for enterprise campus distribution and core applications.
The first release in this train, Release Provides Cisco IOS Software functionality and hardware support for mid-range and low-end Ethernet LAN switching for enterprise access and distribution networks, and mid-range and low-end Metro Ethernet switching for service provider edge networks. Amsterdam It was built using the C language code. Some of the most notable features of Cisco IOS include authentication, encryption , policy enforcement, firewall capabilities, quality of service, intelligent routing, deep pocket inspection and even proxy capabilities.
The system can also support call processing and unified data communication services. It enables preemptive multitasking which grants CPU time to high priority processes before it does to low priority processes.
However, it has several limitations such as it does not support symmetric multiprocessing. Moreover, it can only run with shared memory space. New versions of the system were launched to rectify these limitations. However, the latter is based in QNX which is like a Unix real-time system. This enables it to support software-defined networking as well as embed the systems market.
Cisco NX-OS is a relatively new release with several improvements in design as well as a plethora of additional features.
0コメント