Cisco IOS and NX-OS Software Release Families
Cisco IOS and NX-OS Software continues to evolve to meet the rapidly changing requirements of the most demanding enterprise and service provider networks. To better meet the requirements of different market segments, the software is organized into software release families and trains.
A software release family is software that shares a code base, applies to related hardware platforms, and has some overlap in the timeframe when it is actively supported. A train is a vehicle for delivering Cisco software to a specific set of platforms and features. Trains are grouped into software release families. Because different software release families can apply to different platforms or market segments, several trains can be current at any point in time. For example the Cisco IOS Software 12.2SX train coexists with the 12.4T train and each train will have a corresponding latest release that incorporates the newest features and hardware support for the particular platforms on which they run. For the same reason, some trains may outlast seemingly newer trains; for example the 12.3 and 12.3T trains reached end-of-life status while several trains in the Cisco IOS 12.2S software release family continue to be active in their respective lifecycles.
Within a software release family there may be two closely related active trains. For example, in the Cisco IOS Software 12.4 release family the two closely related trains are the 12.4 and the 12.4T trains. The Cisco IOS Software 12.4 train is considered the mainline train or M train and is meant to receive mostly software fixes with the goal of increasing software quality. Meanwhile, the 12.4T or technology train receives new software features and hardware support along with software fixes.
Not all software families have separate mainline and technology trains. An example of this is the Cisco IOS Software 12.2SX train, which instead has extended maintenance and standard maintenance releases. In the 12.2SX train, an extended maintenance release incorporates the features and hardware support of previous releases (both standard and extended) and remains active for a total of 30 months before reaching end of maintenance status. Standard maintenance releases stay active only for 18 months and do not receive any software fixes after that time. Both extended maintenance and standard maintenance releases initially deliver new features and hardware support, but later rebuilds of extended maintenance releases will typically contain only bug fixes. For more information about the Cisco IOS Software 12.2SX train, see the Cisco IOS Software Release 12.2SX and 12.2SY on the Cisco Catalyst 6500 Series Product Bulletin.
In the Cisco IOS Software 15.0 release family a new strategy is in place, reminiscent of the one used in the Cisco IOS Software 12.2SX train. Unlike previous software release families, the Cisco IOS 15.0 release family does not diverge into separate M and T trains but into M and T releases in the same train. For example, the first release in the Cisco IOS Software 15.0 release family is 15.0(1)M, where M indicates it is an extended maintenance release. An extended maintenance release is ideal for long-term maintenance and will provide rebuilds for 44 months. Not all releases in the Cisco IOS Software 15.0 release family will be extended maintenance releases; there will also be standard maintenance releases that receive the latest features and hardware support. The standard maintenance releases will have an uppercase T in their designation.
To expedite the availability of new hardware support, a short-lived release can branch out of the technology train. For example, Cisco IOS Software Release 12.4(4)XD was a short-lived release that contained features from 12.4(4)T and introduced support for the Cisco 7200 VXR Series Routers with NPE-G2, then support for the NPE-G2 was integrated into the 12.4T train with 12.4(11)T. The releases that start with an uppercase X after the closing parenthesis are called X-releases and are considered a short-lived release.
Table 1. Summary of the Most Significant Trains in the Cisco IOS and NX-OS Software Release Families
Software selection depends on a number of factors, including hardware and software feature requirements, current lifecycle status of applicable trains, and outstanding caveats. For guidance on selecting software for specific requirements, please use the Cisco Feature Navigator or the Software Center on Cisco.com (registered customers only). A general overview of hardware support is shown in Table 2, which correlates the most common Cisco hardware platforms to the primary Cisco IOS and NX-OS Software family releases.
Table 2. Primary Cisco IOS Software Trains Used by Hardware Families
Note 1: The Cisco IOS Software 12.0SY train is a descendant of the highly popular 12.0S train. The Cisco IOS Software 12.0S train was used in several platforms, but it is currently deployed mostly on the Cisco 12000 platform.
In order to effectively manage Cisco IOS and NX-OS Software within your network, it is important to understand the release numbering and terminology.
A train consists of individual releases, such as Cisco IOS Software Release 12.4(20)T. Individual releases contain a number of software fixes and, in most trains, this individual releases contain new hardware support and software features.
The term release indicates an instance of the software as released on Cisco.com. For example Cisco IOS Software Release 12.4(7a) is a release of the 12.4 train.
Cisco IOS Software trains typically contain an uppercase letter, the exception is called a mainline train. For example, the Cisco IOS Software 12.4 and 12.3 trains are both mainline trains. In a few cases, mainline trains have been referred to as the “M” trains. A mainline train is always associated with a technology or T train.
Through the Cisco IOS Software 12.4 release family, the mainline and technology trains were separated, which means a mainline train would evolve from the previous technology train and then would primarily receive bug fixes and occasionally new features or hardware support. From the mainline train a technology train would branch out and become a separate code base that received new features and hardware support. For example, Cisco IOS Software Release 12.3(14)T received new features and functionality and became 12.4(1). After that, the following releases in the Cisco IOS Software 12.4 mainline train were Cisco IOS Software Release 12.4(3) and 12.4(5), both of which primarily integrated bug fixes. Meanwhile Cisco IOS Software Release 12.4(1) received new features and hardware support and became 12.4(2)T, which again received multiple new features and hardware support to become 12.4(4)T. The net effect is that, as new releases become available, the latest technology and mainline releases continue to diverge as new functionality accumulates in the technology releases, which is mostly absent from the newer mainline releases.
Figure 1 illustrates the relationships between the Cisco IOS Software 12.4 mainline train and the 12.4T train releases. The mainline releases are designated as Maintenance Deployment releases (MD) while releases in the Cisco IOS Software 12.4T train are considered Early Deployment (ED).
Figure 1. Mainline and T Train Relationships
The Cisco IOS Software 15 M and T train uses a different release model from the traditional separate mainline and technology trains. Instead of diverging into separate trains, Cisco IOS Software 15 M and T will have extended maintenance releases and standard maintenance releases. An extended maintenance release incorporates the features and hardware support of all the previous standard maintenance releases. This makes newer extended maintenance releases available that contain the full functionality of the train at the time of release. In the Cisco IOS Software 15 M and T train, extended maintenance releases are planned to become available every twenty months.
Figure 1a. Cisco IOS Software 15.0 Train Relationships
The Cisco IOS Software 12.4 train receives software fixes on a regular basis, but does not normally receive new software features or hardware support. Note that fixes applied to the 12.4 mainline train are synchronized with subsequent releases of the 12.4T train. Derived from the Cisco IOS Software 12.4 mainline train, the 12.4T train receives regular software fixes and provides new features and hardware support.
Figure 2. Cisco IOS Software Mainline and T Train Numbering
A single set of individual release numbers are used for all Cisco IOS Software 12.4 trains. Cisco IOS Software Maintenance Release 12.4 and Cisco IOS Software Release 12.4T use a pool of individual release numbers that are shared across the whole Cisco IOS Software 12.4 release family. For example Cisco IOS Software Release 12.4(6)T was followed by 12.4(7) and 12.4(8). This permits the administrator to track changes introduced in the code. For example, say a caveat was fixed in Cisco IOS Software Release 12.4(6)T, then it is possible to conclude that this specific caveat has also been fixed in 12.4(7), 12.4(8), and 12.4(9)T, but not in 12.4(5).
The releases within the Cisco IOS Software 12.2S release family share a common code base from the Cisco IOS Software 12.2S train. In addition to the common code base, software fixes and new software features are included in each individual release of the Cisco IOS Software 12.2SB, 12.2SX, 12.2SE, 12.2SG, and 12.2SR trains. After their inclusion, where applicable, additional software fixes and software features are propagated to other trains in the Cisco IOS Software 12.2S release family.
The key elements of the Cisco IOS Software 12.2S release family numbering scheme are the release number, individual release number, and rebuild identifier (see Figure 3). Note that Cisco IOS Software 12.2SX releases that include new functionality will typically include a third uppercase letter right after the 'SX' designation, such as 12.2(18)SXF, 12.2(33)SXH, and 12.2(33)SXI. This model is also followed by other trains, for example, 12.2(25)SE is followed by 12.2(25)SEA, 12.2(25)SEB, 12.2(25)SEC and so on, where each new individual release includes new features or hardware support.
Figure 3. Cisco IOS S Software Family Numbering
In the Cisco Catalyst 6500 Series, an individual release can be either extended maintenance or standard maintenance and there is additional terminology specific to Cisco IOS Software 12.2SX Major Release. For more information, see the Cisco IOS Software Release 12.2SX and 12.2SY on the Cisco Catalyst 6500 Series Product Bulletin.
Cisco integrates fixes to high severity issues in an individual release via rebuilds to reduce the possible impact on customers that have already deployed and certified an individual release. A rebuild typically includes fixes to a limited number of caveats and is indicated by a lowercase letter inside the parenthesis of mainline trains or by a final number in other trains. For example, Cisco IOS Software Release 12.4(21) received a few caveat fixes and the resulting rebuild was named 12.4(21a). In a similar way, 12.4(15)T8 is the eight rebuild of 12.4(15)T.
Rebuilds of other trains, like those in the SX train also include a final ascending number to indicate a rebuild. For example, Cisco IOS Software Release 12.2(33)SXH2 is the second rebuild of the 12.2(33)SXH individual release.
Occasionally, Cisco might rebuild an individual release number when a very significant defect is found. For example, 12.2(18)SXF15 was shortly followed by 12.2(18)SXF15a which included a single fix for a very significant defect.
The Cisco IOS XE Software numbering scheme uses a major release, release version, and rebuild scheme. For details, see:
Cisco IOS XE Software contains a number of components, including IOS daemon (IOSd), Interface Manager, Forwarding Manager, Chassis Manager, and others. For a list of Cisco IOS XE Software components, see Troubleshoot Cisco ASR 1000 Series Aggregation Services Routers Crashes. The numeric scheme is the primary designation for Cisco IOS XE Software and applies to the collection of all components. The IOSd is a very visible component, it incorporates the routing protocol functionality and is essentially Cisco IOS Software code running as a user process. The origins of IOSd trace back to the Cisco IOS Software 12.2S release family. The IOSd uses a release designation that includes the letters XN and has a versioning scheme that is similar to the one used by Cisco IOS Software. Each version of Cisco IOS XE Software has an associated IOSd Cisco IOS Software version. See the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers for the mapping of ASR IOS XE Software versions to IOSd Cisco IOS versions.
Figure 4. Cisco IOS XE Software Numbering
Cisco IOS XE Software is classified as either standard-support or extended-support. Standard-support software has a sustaining support lifetime of one year from First Customer Shipment (FCS) with two scheduled rebuilds. Extended-support software provides a sustaining support lifetime of two years from FCS with four scheduled rebuilds. For more information about Cisco IOS XE Software support models, see Cisco IOS XE Software End-of-Life Guidelines.
Cisco IOS XR Software is comprised of modular packages. Each package contains the components to perform a specific set of functions, such as routing, security, or line card support. The key elements of the Cisco IOS XR Software numbering scheme consist of the major release identifier, minor release identifier, and maintenance revision identifier (see Figure 5).
Figure 5. Cisco IOS XR Software Numbering
The major release identifier is the major release number for a package. A major release occurs when there is a significant architectural change to the product (for example, an important new capability is introduced). All packages that operate on the router must be at the same major release level.
The minor release version does not have to be identical for all software packages that operate on the router. But the operating packages must be certified by Cisco as compatible with each other. For example, a router running Cisco IOS XR Software could use an MPLS package with a different minor release version than the multicast package if they are certified by Cisco as compatible. The maintenance revision identifier is the maintenance release number for a given package. A maintenance release contains a collection of software fixes.
The Cisco IOS XR Software mechanism for providing software fixes for critical issues is called a System Maintenance Update (SMU). An SMU provides a release and platform specific patch. The impact of the SMU on the running system varies. Some updates are designed to allow uninterrupted operation of the node while the SMU is applied. This is called a hitless SMU. Each SMU indicates the expected impact on traffic flowing through the router when the SMU is activated.
Cisco NX-OS Software is a data-center-class operating system that provides high availability with a modular design. Cisco NX-OS Software is based on the Cisco MDS 9000 SAN-OS Software and it supports the Cisco Nexus Series and the Cisco MDS 9000 Series Multilayer Switch. The Cisco NX-OS Software contains a kick start image and a system image, both images contain a major release identifier, a minor release identifier, and a maintenance release identifier, and they can also contain a rebuild identifier, which may also be referred to as a Support Patch. (See Figure 6.)
Cisco NX-OS Software for Nexus 7000 Series Switches and MDS 9000 Series Switches uses the numbering scheme that is shown in Figure 6.
Figure 6. Cisco IOS NX-OS Numbering for the Cisco Nexus 7000 and MDS 9000 Series Switches
For other members of the family, Cisco NX-OS Software uses a combination of platform-independent and platform-dependent schemes as shown in Figure 6a.
Figure 6a. Cisco IOS NX-OS Software Numbering for the Nexus 4000 and 5000 Series Switches and Nexus 1000 Virtual Switches
The platform designator is N for the Nexus 5000 Series Switches, E for the Nexus 4000 Series Switches, and S for the Nexus 1000 Series Switches. In addition, the Nexus 1000 virtual switch uses a two-letter platform designation where the second letter indicates the hypervisor vendor that the virtual switch is compatible with, for example V for VMware. Applicable features, functions, and fixes in the platform independent code are present in the platform dependent release, in Figure 6a above, applicable fixes in Cisco NX-OS Software Release 4.0(1a) are present in the 4.0(1a)N1(1a) release.
The code selection process involves a number of different variables. Cisco recommends minimizing the number of releases that are deployed in any network and to establish a software strategy that indicates which releases and images will be used in the different devices that are deployed throughout the environment. To maximize operational efficiency, it is ideal to have devices with similar hardware and feature deployment using the same Cisco IOS Software release. For professional advice on software versions to deploy in specific environments, refer to Cisco Advanced Services.
New features or hardware support is the most common reason to upgrade to a newer train. A single device is likely to run different trains at different times during its deployment cycle. For example, a device could have been initially deployed using the Cisco IOS Software 12.3T train, then upgraded to the 12.4 train to take advantage of caveat fixes. As new services are deployed in the network, the device might have the need for a new feature available in the Cisco IOS Software 12.4T train.
When there is no need to change the train that is used by a device, the general migration path for the device is to the latest release of that train. If that train has an end-of-sale notification, the migration options found on the notification will list the trains or releases that can be used to upgrade. The latest version incorporates the most current software fixes, software features, and hardware support.
The Cisco IOS Software Migration Examples section presents high-level examples of migration for some of the currently deployed releases.
Note: Cisco IOS Software migration is an ongoing process that takes detailed planning. Customers should work closely with their account managers when they take inventory of their deployed Cisco IOS Software and create a plan to migrate to more current releases.
Tables 3 through 7 describe example migration paths from Cisco IOS Software releases. The examples include general guidelines, code selection must include analysis of outstanding caveats that apply to the environment where the code will be deployed. To cover the minimum due diligence, the administrator needs to review the open and fixed caveats section of the Release Notes for the version under evaluation.
Table 3. Migration Paths from Cisco IOS Software Release 12.4(18)
Table 4. Migration Paths from Cisco IOS Software Release 12.4(15)T
Table 5. Migration Paths from Cisco IOS Software Release 12.2(33)SB
Table 6. Migration Paths from Cisco IOS Software Release 12.2(18)SXF
Table 7. Migration Paths from Cisco IOS XR Software Release 3.4.1
The Cisco IOS Software Release Policy is a structured plan that addresses the Cisco Software lifecycle from First Customer Shipment through end-of-life (EoL). The Release Policy addresses lifecycle guidelines and migration planning for Cisco IOS Software Releases 12.4, 12.4T, 12.2SR, 12.2SB, 12.2SE, 12.2SG, 12.2S, and 12.0S.
Figure 7 shows the Cisco IOS Software lifecycle milestones for the indicated releases.
Figure 7. Cisco IOS Software Lifecycle Milestones
Refer to Cisco IOS Software Product Lifecycle Dates & Milestones for more information.
For information about EoL releases, see Cisco IOS and NX-OS End-of-Sale and End-of-Life Products and the End-of-Life Policy.
Note: Cisco recommends that release review and migration planning start at 36 months after FCS.
Cisco IOS Software placed on the Cisco IOS Software Center remains available for customer download for 18 months. After 18 months, the software is eligible for retirement and removal from the Cisco IOS Software Center.
Software on the Cisco IOS Software Center is not retired for platforms that have not reached EoSWM 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. Cisco IOS Software is subject to deferral at any time should a widespread, catastrophic software defect be discovered.
Software retirement is not a formal lifecycle milestone, but it does underscore the recommendation from Cisco that you implement current versions of Cisco IOS Software. Cisco does not recommend new deployments of retired software.
Cisco IOS Software is retired based on age. If the Cisco IOS Software that runs in a customer network is retired, it does not mean the software should be automatically replaced. If the software meets customer needs, then the customer can continue to use it. Cisco TAC provides assistance support for retired software until it reaches the published last-day-of-support.
Regardless of its status on the Cisco IOS Software Center, Cisco recommends that you maintain copies of all Cisco IOS Software that is running on the network.
Cisco issues many software advisories to customers for informational purposes only. Often, software advisories describe problems with Cisco IOS Software that are hardware-specific or occur under unusual circumstances and therefore do not affect most customers. Often, no action is required by the customer.
The following communications from Cisco do require customers to evaluate the impact of the underlying problem on their networks and take appropriate action:
For more information about Cisco security publications, see "Types of Security Publications" in the Cisco Security Vulnerability Policy.
Cisco IOS Software Packaging consists of eight packages for Cisco routers (see Figure 8). This packaging scheme was introduced in the Cisco IOS Software 12.3 mainline train and was later used in other trains as well. For additional information about Cisco IOS Software packaging, see Cisco IOS Packaging Customer Q&A.
Figure 8. Cisco IOS Software Packaging for Cisco Routers and Switches
Five packages are designed to satisfy requirements in four typical service categories:
Three additional premium packages offer new Cisco IOS Software feature combinations that address more complex network requirements. All features merge in the Advanced Enterprise Services package that integrates support for all routing protocols with Voice, Security, and VPN capabilities:
Feature inheritance is another powerful aspect of Cisco IOS Packaging. After a feature is introduced, it is included in the more comprehensive packages. The feature inheritance facilitates migration by clarifying the feature content of the different packages and how they relate to each another.
Cisco IOS Packaging also simplifies image naming. Each name is designed to effectively convey the high-level feature content of and inheritance characteristics for the new packages.
These categories summarize the new naming convention:
Cisco IOS Packaging was introduced on Cisco access routers in May 2003, Cisco LAN switches in April 2005, and Cisco mid-range routers in July 2005. Refer to the Cisco IOS Packaging page for additional information about Cisco IOS Packaging.
Cisco IOS Software Packaging Changes in Cisco IOS Software Release 15.0 for Cisco Integrated Services Routers Generation Two
Cisco Integrated Services Routers Generation Two (ISR G2) 1900, 2900, and 3900 Series support services on demand through the use of software licensing which enables customers to realize operational savings through ease of software ordering and management. When an order is placed for a new ISR G2 platform, the router is shipped with a single universal Cisco IOS Software image and a license is used to enable the corresponding feature set packages as shown in Figure 8a below.
Figure 8a. Cisco IOS Software Packaging Model for 1900, 2900, and 3900 Series Integrated Services Routers
There are two types of universal images supported in ISR G2:
Cisco IOS switches can use seven different packages. Seven switch packages satisfy requirements in different market categories.
Cisco IOS Software Packaging for Switches
Note: Not all switch packages are available for all switch models.
The switch packages are:
The Catalyst 3560-E and 3750-E series switches can run a universal image that has the code for multiple feature sets.
Currently, universal images for Catalyst 3560-E and 3750-E provide the following feature sets depending on the installed license:
For more information about software activation, see the Cisco Software Activation and Compatibility Document.
Cisco IOS XE Software is released using consolidated packages. Each consolidated package contains a collection of software sub-packages. Each software sub-package is an individual software file that controls a different element or elements of the Cisco ASR Series Routers. Each individual software sub-package can be upgraded individually, or all software sub-packages for a specific consolidated package can be upgraded as part of a complete consolidated package upgrade.
The consolidated packages are available as images and the integrated IOSd or RPIOS (Route Processor IOS).
For further information on the advantages and disadvantages of running individual sub-packages or a complete Cisco IOS XE Software consolidated package, and the process of extracting the individual sub-packages, see the Cisco ASR 1000 Series Aggregation Services Router Software Configuration Guide and the Cisco IOS XE Software for Cisco ASR 1000 Series Routers Product Bulletin.
The IOS XR Software equivalent of feature sets is called packages. Unlike Cisco IOS Software, in which the feature sets are defined at image build time and remain static while the system is in operation, Cisco IOS XR Software can dynamically load and unload software packages that can deliver one or many features. These software packages are created in versions and can be updated or patched if necessary to add features or resolve problems, allowing system enhancement and maintenance to take place without requiring a system restart or disrupting traffic traversing the system In the latest versions of Cisco IOS XR Software for the ASR 9000 series routers there are two feature sets available, they differ in that one contains 3DES support. For more details, see the Cisco ASR 9000 Series Aggregation Services Routers for Cisco IOS XR Software Release Notes.
There is no special feature packaging for Cisco NX-OS. The system image is a single file.
The Cisco IOS Software image name represents the hardware, feature set, format, and other information about the image file. Figure 9 shows the image name of Cisco IOS Software Release 12.4(22)T with the Enterprise Base feature set for the Cisco 3825 router.
Figure 9. Example of a Cisco IOS Software Image Name
The show version command displays the name of the Cisco IOS image (see Figure 10).
Figure 10. Cisco IOS Software Release 12.4(22)T Output from the show version Command
Router>show version Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 12.4(22)T, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2008 by Cisco Systems, Inc. Compiled Fri 10-Oct-08 00:05 by prod_rel_team ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1) Router uptime is 1 week, 6 days, 8 hours, 26 minutes System returned to ROM by reload at 19:45:36 UTC Thu Jan 15 2009 System image file is "flash:c2800nm-adventerprisek9-mz.124-22.T.bin" This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to firstname.lastname@example.org. Cisco 2851 (revision 53.50) with 239616K/22528K bytes of memory. Processor board ID FTX1244A6JG 2 Gigabit Ethernet interfaces 1 terminal line 1 Virtual Private Network (VPN) Module 1 cisco Integrated Service Engine(s) Cisco Unity Express 3.1.1 in slot 1 DRAM configuration is 64 bits wide with parity enabled. 239K bytes of non-volatile configuration memory. 1982232K bytes of ATA CompactFlash (Read/Write) Configuration register is 0x2102
Figure 11 shows the image name of Cisco IOS XE Software Release 2.1.1 with the IP Base package. This image contains a Cisco IOS Software kernel or IOS daemon (IOSd) version 12.2(33)XNA1.
Figure 11. Example of a Cisco IOS XE Image Name
Figure 12 shows the output of the show version command on a Cisco 1002 router. The system image file name is shown in bold.
Figure 12. Cisco IOS XE Software Release 2.1.1 Output from the show version Command
ASRrouter#show version Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-IPBASE-M), Version 12.2(33)XNA1, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2008 by Cisco Systems, Inc. Compiled Tue 08-Jul-08 14:40 by mcpre Cisco IOS-XE software, Copyright (c) 1986-2008 by Cisco Systems, Inc. All rights reserved. Certain components of Cisco IOS-XE software are licensed under the GNU General Public License ("GPL") Version 2.0. The software code licensed under GPL Version 2.0 is free software that comes with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such GPL code under the terms of GPL Version 2.0. For more details, see the documentation or "License Notice" file accompanying the IOS-XE software, or the applicable URL provided on the flyer accompanying the IOS-XE software. ROM: IOS-XE ROMMON Router uptime is 5 weeks, 5 days, 10 hours, 41 minutes Uptime for this control processor is 5 weeks, 5 days, 10 hours, 42 minutes System returned to ROM by reload System image file is "bootflash:asr1000rp1-ipbase.02.01.01.122-33.XNA1.bin" Last reload reason: Unknown reason cisco ASR1002 (RP1) processor with 1791829K/6147K bytes of memory. 4 Gigabit Ethernet interfaces 32768K bytes of non-volatile configuration memory. 4194304K bytes of physical memory. 8137567K bytes of eUSB flash at bootflash:. Configuration register is 0x2102
To determine the versions of the individual sub-packages that are running on the active resource processor (RP) use the show version rp active running command (see Figure 13).
Figure 13. Cisco IOS XE Software 2.1.1 Output from the show version rp active running Command
ASR#show version rp active running Package: Provisioning File, version: n/a, status: active File: consolidated:packages.conf, on: RP0 Built: n/a, by: n/a File SHA1 checksum: 6a5070d5b280487d5f89b6f3fc70ff2225728204 Package: rpbase, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-rpbase.02.01.01.122-33.XNA1.pkg, on: RP0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: 33204d0f8ef544cdcf5889dd5f56b4a7740a0ef3 Package: rpaccess, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-rpaccess.02.01.01.122-33.XNA1.pkg, on: RP0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: 9206c32bf4893076f7af1d522b07b4202de6e5d7 Package: rpcontrol, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-rpcontrol.02.01.01.122-33.XNA1.pkg, on: RP0/0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: fa1465740d1b1b8288b38e353cb068bcc835cf71 Package: rpios-ipbase, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-rpios-ipbase.02.01.01.122-33.XNA1.pkg, on: RP0/0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: 045b89df5ed1a711dc7906efee29693a8560a8e0 Package: espbase, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-espbase.02.01.01.122-33.XNA1.pkg, on: ESP0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: 9ff0f8627b0acc282aa31c35e1b9cd3b1b9f2ac2 Package: sipbase, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-sipbase.02.01.01.122-33.XNA1.pkg, on: SIP0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: 6e18c01677e7de04c5eea51dec1e6d461a0b5e91 Package: sipspa, version: 02.01.01.122-33.XNA1, status: active File: consolidated:asr1000rp1-sipspa.02.01.01.122-33.XNA1.pkg, on: SIP0/0 Built: 2008-07-08_16.38, by: mcpre File SHA1 checksum: ac8c61b4061905f3e94ef273b2c665e6c2eae0d2
Figure 14 shows the image name of Cisco IOS XR Software Release 3.6.1 with the IP/MPLS Core Software 3DES package for the CRS-1.
Figure 14. Example of a Cisco IOS XR Software Image Name (TAR)
Figure 15 shows the image name of Cisco IOS XR Release 3.6.1 with the Cisco IOS XR Diagnostics package for the CRS-1. The acronym hfr was an early name for the Cisco CRS-1 Carrier Routing System.
Figure 15. Example of a Cisco IOS XR Software Image Name (PIE)
Figure 16 shows an example of the output of the show version command on a Cisco CRS-1 router.
Figure 16. Cisco IOS XR Software 3.8.1 Output from the show version Command
RP/0/RP0/CPU0:XR-ROUTER# show version Thu Jul 30 14:27:41.521 PST Cisco IOS XR Software, Version 3.8.1 Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.53(20090311:225342) [CRS-1 ROMMON], XR-ROUTER uptime is 11 hours, 48 minutes System image file is "bootflash:disk0/hfr-os-mbi-3.8.1/mbihfr-rp.vm" cisco CRS-16/S (7457) processor with 4194304K bytes of memory. 7457 processor at 1197Mhz, Revision 1.2 2 Management Ethernet 5 TenGigE 29 SONET/SDH 28 Packet over SONET/SDH 1 WANPHY controller(s) 8 GigabitEthernet 1 Asynchronous Transfer Mode 1019k bytes of non-volatile configuration memory. 38079M bytes of hard disk. 2052832k bytes of disk0: (Sector size 512 bytes). Boot device on node 0/0/CPU0 is bootflash: Package active on node 0/0/CPU0: hfr-fpd, V 3.8.1, Cisco Systems, at disk0:hfr-fpd-3.8.1 Built on Wed Jul 29 03:41:40 PST 2009 By edde-bld1 in /auto/srcarchive3/production/3.8.1/hfr/workspace for c4.2.1-p0 !-- Output Truncated --
Figure 17 shows the system image name of Cisco NX-OS Software Release 4.2(1).
Figure 17. Example of a Cisco NX-OS Software Image Name
Figure 18 shows the output of the show version command and highlights the system image version and system image file.
Figure 18. Cisco NX-OS Software 4.2(1) Output from the show version Command
switch# show version Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php Software BIOS: version 3.15.0 loader: version N/A kickstart: version 4.2(1) [gdb] system: version 4.2(1) [gdb] BIOS compile time: 03/04/09 kickstart image file is: bootflash:/n7000-s1-kickstart.4.2.1.bin kickstart compile time: 3/6/2009 2:00:00 [04/02/2009 09:49:07] system image file is: bootflash:/n7000-s1-dk184.108.40.206.bin system compile time: 3/6/2009 2:00:00 [04/02/2009 10:28:32] Hardware cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X") Intel(R) Xeon(R) CPU with 2063436 kB of memory. Processor Board ID JAB10380101 Device name: switch bootflash: 1023120 kB slot0: 0 kB (expansion flash) Kernel uptime is 2 day(s), 17 hour(s), 26 minute(s), 1 second(s) Last reset at 121426 usecs after Sun Apr 13 20:38:08 2009 Reason: Reset Requested by CLI command reload System version: 4.2(1) Service: !-- Output Truncated --
Table 8 briefly describes some of the most useful Cisco tools for planning a Cisco IOS Software release migration.
Table 8. Tools and Resources
A number of individuals contributed to this document.
Cisco IOS Network Foundation Protection (NFP) White Papers
Cisco IOS XE Software for Cisco ASR 1000 Series Routers
Cisco IOS XE Software Support Timeline
Cisco IOS Software Packaging Product Bulletin (Registered customers only)
Cisco IOS Software Product Lifecycle Dates & Milestones
Cisco IOS Packaging Customer Q&A (Registered customers only)
Cisco Software Activation and Compatibility Document
This document is part of the Cisco Security Center.
This document is provided on an "as is" basis and does not imply any kind of guarantee or warranty, including the warranties of merchantability or fitness for a particular use. Your use of the information on the document or materials linked from the document is at your own risk. Cisco reserves the right to change or update this document at any time.