An Overview of Cisco IOS Versions and Naming

An Overview of Cisco IOS Versions and Naming

http://www.ciscopress.com/articles/article.asp?p=2106547

• By Sean Wilkins.
• Article is provided courtesy of Cisco Press.
• Date: Jun 28, 2013.

SaveDiggDel.icio.usPrint

Article Information

Article Description　　

Version and naming structure used by Cisco for their IOS images is often confusing. Although the naming used for some of the newer devices is changing to a simpler structure, it will be a while before all the different versions are consolidated. This article covers these different releases and aims to give a single location where network engineers can look to figure out what the different releases mean

From the author of

Designing for Cisco Internetwork Solutions (DESGN) Foundation Learning Guide: (CCDA DESGN 640-864), 3rd Edition

$69.99

 

One thing that is often confusing to any network engineer (regardless of level) is the version and naming structure used by Cisco for their IOS images. Although the naming used for some of the newer devices is changing to a simpler structure, it will be a while before all the different versions are consolidated. This article covers these different releases and aims to give a single location where network engineers can look to figure out what the different releases mean. Although this is not an exhaustive list of every Cisco version, it does cover the most commonly used versions.

IOS Releases

One term that is often used is the IOS release type. With versions of IOS earlier than 15, a specific image could be considered one of the following four different release types:

Early Deployment (ED): These releases provide both new features and new platform support in addition to bug fixes.

Limited Deployment (LD): These releases do not include any new features or platform support but do include bug fixes. LD releases are between an ED release and a GD release.

General Deployment (GD): These releases can be used anywhere in a customer network with the same feature and functionality requirements. These tend to be stable on almost all platforms.

Maintenance Deployment (MD): These releases are used to provide additional support for bug fixes and ongoing software maintenance.

With IOS 15 and later, both the LD and GD deployments will be retired. New releases will be considered either ED or MD. The IOS train paths have also been consolidated. With earlier versions of IOS, the different ED (T trains; for instance, 12.4T) and MD (not T trains; for instance, 12.4) has different code bases. With IOS 15 and later, the code bases will be consolidated. MD releases (called M releases, or extended release) will be released and have a 44-month support window, whereas ED (T releases, or standard release) will have a 18-month support window.

IOS Versions

A number of different versions exist within each release of IOS. This article takes a look at a few of these and how what they are used for.

12

With IOS Version 12, many different sub-versions of IOS exist, including specialized support for specific platforms; the next few sections cover a couple of the most common.

IOS Version 12 has a few different ways to notate version, including those shown in Figure 1.

Figure 1 IOS Version 12 Version Notation

12

The 12 base versions are also referred to as the mainline release of a version. These releases tend to be the most stable and include support for most of the available platforms. Other more specialized versions of IOS are rolled into the mainline as an update when they have been sufficiently tested. (They go through the release process shown in the previous section.)

12T

The T train is used to add the newest features and platforms. After the software has been tested thoroughly, it is rolled into the mainline release.

12S, 12SB, 12SR

Many different IOS versions provide support for specific platforms. The ones shown in the section name are an incomplete list but do show some of the common examples. The 12S, 12SB, and 12SR versions tend to provide support for Cisco’s 7200, 7300, 7400, 7500, and 10000 platforms.

15

The way that different versions are referenced with IOS Version 15 is similar to that of IOS Version 12.

IOS Version 15 has a notation that is similar to IOS Version 12 and is shown in Figure 2.

Figure 2 IOS Version 15 Version Notation

15M

As with IOS version 12, IOS Version 15M provides a mainline release and is also referred to as a maintenance release.

15T

As with IOS version 12T, version 15T is focused on new features and platforms and is supported for a shorter amount of time than the maintenance releases. After 15T releases have been tested thoroughly, they are wrapped into the next 15M release.

15X, 15S, 15SY, 15SG, 15SE

As with IOS Version 12, IOS Version 15 is going to have a number of different versions that are specific to new equipment that needs to support new features (specific to the platform). For IOS Version15, some of those currently available are Version 15X (special or early deployment), 15S (7600), 15Y (Sup-2T-10GE – Catalyst 6500), 15SG (Sup-CS-S2T – Catalyst 6500), and 15SE (2960, 3560, 3650, and 3750 platforms).

IOS Package Naming

The way that Cisco has named their IOS packages has changed over time. With IOS Version 12.3 though 15, this has remained relatively constant. Figure 3 shows the eight different packages that are available.

Figure 3 IOS Software Packaging (Routers and Switches)

Of course, this can get confusing. In an effort to make the software licensing process simpler and provide operational savings, the way that packages are created has changed with the new Integrated Service Routers (ISR) Generation 2. With these devices, a universal image is shipped on each one. The functionality provided by the image is dictated by the features enabled with a license key.

Figure 4 shows the four different packages that are available.

Figure 4 IOS Software Packaging (ISR G2 Routers)

Each of these are then able to be added together to obtain the features required in each situation (for example, UC + Security or Data + Security).

Summary

Well, leave it up to development to have a structure that makes sense to only a small number of people. This certainly seems to have happened with the various iterations of IOS. This article should enable current and new network engineers to break down what every image provides so that future IOS version selection becomes easier. Let’s hope that going forward the model being used for the newer ISR G2 will be used. At the very least, this will make the selection of the most appropriate IOS image feature package possible without considerable time spend with Cisco presales.