Cisco IOS Reference Guide.PDF

White Paper: Cisco IOS® Reference Guide

All you need to know about Cisco IOS software:

• Cisco IOS release process

• Release naming convention

• Software maintenance numbering convention

• Relationship between various Cisco IOS releases

Mack M. Coulibaly

Cisco IOS® Serviceability Program Manager

mack@cisco.com

Cisco IOS® software enables networking solutions with support for the most comprehensive set

of industry-leading features that provide the intelligence of the Internet. Cisco IOS software is a

broad and cohesive internetworking operating system that offers a scalable migration path for

data, voice, and video with unmatched security, protocols, and network management integrated

services. Cisco IOS network services deliver the best breed of functionality around scalable

Internetworks that support new, leading-edge Internet applications.

Table of Contents

White Paper: Cisco IOS® Reference Guide ............................................................................................. 1

Table of Contents ..................................................................................................................................... 2

Glossary of Terms .................................................................................................................................... 3

1. Cisco IOS Overview ....................................................................................................................... 7

1.1. Background ............................................................................................................................. 7

1.2 The Foundation of Cisco IOS Release Models........................................................................... 7

1.3 Scope ...................................................................................................................................... 9

1.4. Introduction to Cisco IOS Releases ........................................................................................ 10

1.4.1. Cisco IOS Main Releases................................................................................................ 10

1.4.2. Cisco IOS Early Deployment Releases............................................................................ 11

1.4.3. Consolidated Technology Early Deployment Releases .................................................... 11

1.4.4. CTED Release Train Before Cisco IOS 12.0 ................................................................... 13

1.4.5. Specific Technology Early Deployment Releases ............................................................ 14

1.4.6. Specific Market Early Deployment Releases (SMED) ..................................................... 14

1.4.7. X Releases or Short-lived ED Releases (One-time Releases) ........................................... 16

1.5. Cisco IOS Features Integrated into the Releases ..................................................................... 16

1.5.1. Commit to Cisco IOS CTED........................................................................................... 17

1.5.2. Feature Commit to Cisco IOS STED and SMED............................................................. 18

1.5.3. Feature Commit to Cisco IOS XED ................................................................................ 19

1.5.4. Importance of Unifying Cisco IOS Releases.................................................................... 20

1.6. Relationship Between the Releases and the Cisco IOS Roadmap ............................................ 21

2. Cisco IOS Release Naming Convention ........................................................................................ 22

2.1. Cisco IOS Version Numbering Convention ............................................................................ 24

2.1.1. Cisco Main Release Rebuild Numbering System ............................................................. 25

2.1.2. Cisco IOS ED Rebuild Numbering System ..................................................................... 25

2.1.3. Exception to the Rule: Wx Releases................................................................................ 27

2.1.4. Cisco IOS XED Rebuild Numbering System................................................................... 28

2.2. Cisco IOS Image Naming Convention ................................................................................... 29

2.2.1. Platform Identifiers......................................................................................................... 29

2.2.2. Cisco IOS Image Names for Boards................................................................................ 29

2.2.3. Feature Content of Cisco IOS Images ............................................................................. 30

2.2.4. Cisco IOS Run-time Memory Space................................................................................ 30

2.2.5. File Type Extensions ...................................................................................................... 31

2.3. How to Identify Cisco IOS Images Using Cisco IOS Banners................................................. 31

2.3.1. Release Type Definitions and Examples.......................................................................... 32

2.3.2. Example of show version Banner Output ................................................................. 33

2.3.2.1. Release Software ..................................................................................................... 33

2.3.2.2. Early Deployment Release Software ........................................................................ 33

2.3.2.3. Maintenance Interim Software ................................................................................. 33

2.3.2.4. Early Deployment Maintenance Interim Software .................................................... 34

2.3.2.5. Cisco Development Test Version ............................................................................. 34

2.3.2.6. Beta Test Software .................................................................................................. 34

2.3.2.7. Early Deployment Beta Test Software...................................................................... 34

2.3.2.8. Software ‘fc1’ versus ‘fc2’ Build ............................................................................. 34

2.3.2.9. Cisco IOS X Releases .............................................................................................. 35

2.4. Interpreting Cisco IOS Special Images or Engineering Built Images ....................................... 35

2.4.1. Software Synchronization Level Banners ........................................................................ 35

3. Appendix ..................................................................................................................................... 36

3.1. Cisco IOS Main Release Life Cycle ....................................................................................... 36

3.2. Cisco IOS Images Identifiers ................................................................................................. 37

3.3. Available Cisco IOS Images .................................................................................................. 45

Page 2

Cisco IOS Reference Guide by Mack M. Coulibaly

Cisco Systems, Inc.

Glossary of Terms

Cisco Connection

Online (CCO)

Cisco’s web site: http://www.cisco.com.

Upgrade Planner

The section of CCO through which Cisco IOS software images can be downloaded

(http://www.cisco.com/cgi-bin/iosplanner/iosplanner.cgi?).

First Commercial

Shipment (FCS)

Date of first shipment to customers through any channel for revenue.

Manufacturing FCS

Date that a software release is made available for shipment through Manufacturing

with hardware or media orders for revenue.

Software Image

The monolithic-compiled software binary delivered to customers. Cisco IOS images

are specific to hardware platforms. For example, “rsp-pv-mz.120-5.S.bin” is a Cisco

IOS 12.0(5)S image for the RSP platforms (RSP7000 and 7500 series routers).

Mainline Branch

The branch used for a particular version of Cisco IOS software. For example, Cisco

IOS 12.0 mainline uses the “connecticut” or “conn” branch. This branch is used to

integrate fixes and to generate weekly interim build images for development test

purposes.

Throttle Branch

The branch pulled from the mainline branch to provide a controlled repository just

prior to FCS. Typically, only customer critical fixes are allowed in the throttle branch,

usually to fix a catastrophic problem or repair software regression. The throttle branch

runs parallel to the mainline branch and any fix applied to the throttle branch is also

applied to the mainline branch. The use of a throttle branch allows the mainline to

remain open to all bug fixes without impacting the upcoming maintenance release.

Throttle Build

Compiled images on the throttle branch which incorporates “showstopper” or critical

fixes into images prior to the final regression testing. Throttle builds are considered

interim builds except that the physical build is performed on a separate branch from

the mainline branch. As such, images banners for throttle build images look similar to

that of interim images and display the “MAINTENANCE INTERIM SOFTWARE”

label.

Renumber Build

A build on the throttle branch that occurs after the throttle build and after regression

testing is completed on throttle build images. The renumber build is designed to

renumber the software image from an interim notation to a maintenance revision

notation (for example, from Cisco IOS 12.0(6.6) to 12.0(7)). Renumber builds

normally do not contain new bug fixes. The renumber build is the final build on the

throttle branch and generates a maintenance revision which is FCSed on CCO and

Mfg. Image banners for renumber build images display the “RELEASE SOFTWARE

(fc1)” label.

Page 3

Cisco IOS Reference Guide by Mack M. Coulibaly

Cisco Systems, Inc.

Work-in-process image builds (typically performed weekly) that are built between

maintenance releases to integrate the latest round of bug fix commits (for example,

12.0(7.3)). This type of a release is periodically submitted to the Automated

Regression Facility (ARF) and the development test teams. ARF will execute a 72

hour regression test run and post a report with any newly found regressions identified.

Since only limited testing is applied to interim releases, images from those releases

should be delivered with caution to customers. Interims are designed to provide an

integrated fix prior to the release of that fix in the next maintenance release. Image

banners for interim build images display the “MAINTENANCE INTERIM

SOFTWARE” label.

Interim Build

A build occurring on the mainline branch in the “shadow” of a throttle branch (in

parallel with builds on the throttle branch). Shadow builds occur so that fixes

committed into the mainline are built and made available for testing weekly. Shadow

builds are not intended for customer consumption and are strictly for internal

engineering purposes. Image banners from shadow build images display the “CISCO

DEVELOPMENT TEST VERSION” label.

Shadow Build

An interim build performed prior to the initial FCS of a software release. The images

produced are available for internal testing and for customers that are formally signed

up (through a non-disclosure agreement signed and received by Cisco) to participate in

the beta program for a release. Image banners from shadow build images display the

“BETA TEST SOFTWARE” label.

Beta Build

Posting

The act of delivering images to CCO and the release archive (/release).

Moving images containing serious customer-impacting defects to a locked directory

and removing them from CCO.

Deferral

A second build performed on a throttle branch after the renumber build was

completed. This happens when a catastrophic defect that significantly impacts

customer usage is found on the renumber build. If the renumber images have already

been formally posted to CCO, the release numbering for the rebuild will be augmented

to clearly identify the rebuild. For example, Cisco IOS 12.0(2a), 12.0(1)T1, and

12.0(3)DB1 are rebuilds of Cisco IOS 12.0(2), 12.0(1)T, and 12.0(3)DB, respectively.

Software Rebuild

A subset of a release built specifically by individual engineers to support a critical

customer who has encountered a special critical defect. Engineering specials are built

by engineers and supported by that engineering group. Images from engineering

specials are not shipped through Manufacturing or posted on CCO. The image

banners will clearly identify them as an “EXPERIMENTAL VERSION.” The

customer should upgrade to a supported release at the earliest availability.

Engineering Special

The Cisco IOS software release vehicles that transcend internal business units (BUs)

and Line of Businesses (LOB) boundaries to provide cross-platform features. The

new Cisco IOS release model has two major releases: the mainline release and the

consolidated technology release.

Major Release

A term not commonly used. Refers to the combined group of Specific Technology

Early Deployment (STED) releases, Specific Market Early Deployment (SMED)

releases and X Releases. Minor releases as opposed to major releases (grouping of

mainline and CTED).

Minor Release

Page 4

Cisco IOS Reference Guide by Mack M. Coulibaly

Cisco Systems, Inc.

Consolidated

Technology Early

Deployment (CTED)

Release

A release of software providing new features and cross-platform support from all BUs.

CTEDs mature to mainline releases and subsequently stop accepting new

functionality.

Specific Technology

Early Deployment

(STED) Release

A release of software with limited platform support and created for strategic business

needs. It provides maintenance revisions until unification back into the next CTED.

A release of software targeted on a specific market segment and providing

maintenance revisions until unification back into the next CTED. SMEDs usually

transcend the LOB boundaries and are managed by the Cisco IOS Technology

Division.

Specific Market Early

Deployment (SMED)

Release

A release of software that enables Cisco IOS and BUs with critical time-to-market

commitments to deliver new features and platforms prior to the release of the

corresponding maintenance release of the parent technology release. Often referred to

as an X release.

Short-lived BU Early

Deployment (XED)

Release

A term used when referring to the creation of a source code repository (or branch)

from the contents of another repository (for example, the Cisco IOS 12.0T branch was

pulled from 12.0).

Branch Pull

Featurette

A small, simple feature with minimal complexity such that risk of introducing new

defects is near zero and the software management burden is minimized.

Limited Deployment

(LD)

This phase is the time frame between FCS and GD for main releases. Cisco IOS ED

releases only live in Limited Deployment phase, as they never attain GD certification.

General Deployment

(GD)

Point at which Cisco declares the release stable on all platforms and in all network

environments.

Mature Maintenance

(MM)

Under normal circumstances, the release would have reached end of engineering

(EOE) at this point. However, customer insistence on keeping the release alive is

addressed by transitioning into mature maintenance phase. While in this phase, the

release will only receive defect repairs for customer-found severity 1 and severity 2

defects. Internally found problems will be applied on a case-by-case basis.

This is the end of the MM phase. During this phase, release source code is locked to

avoid major application of fixes that might adversely affect the quality of the code.

Restricted

Maintenance

Last date for product orderability through Customer Service or Manufacturing. The

product will still be available through Field Support Offices (FSO) and CCO.

End of Sale (EOS)

Last scheduled maintenance revision. Engineering will no longer actively apply any

defect repairs to the release, regardless of origin or severity (except for security and

Y2K defects). The product will still be available through FSO and CCO.

End of Engineering

(EOE)

End of Life (EOL)

Software is no longer supported by Cisco personnel and is removed from CCO.

Page 5

Cisco IOS Reference Guide by Mack M. Coulibaly

Cisco Systems, Inc.

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: