Cisco Cisco Packet Data Gateway (PDG)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
System Changes in Release 16
▀ System and Platform Enhancements for 16.1
▄ Release Change Reference, StarOS Release 16
614
operator username nopassword
end
CSCun71100 - show version changes needed for new version numbering
scheme for 16.0
Applicable Products: All
Feature Changes
New StarOS Version Numbering System
The output of the show version command displays detailed information about the version of StarOS currently running
on the ASR 5x00 or QvPC platform.
on the ASR 5x00 or QvPC platform.
Prior to release 16.1, the Image Version version field displayed a branch of software including the build number, for
example “16.0 (55435)”. Subsequent releases of software for the major release differed only in build number. Lab
Quality/EFT releases versus deployment releases also differed only in build number.
example “16.0 (55435)”. Subsequent releases of software for the major release differed only in build number. Lab
Quality/EFT releases versus deployment releases also differed only in build number.
From release 16.1 onwards the output of the show version command, as well as the terminology used to describe the
Build Version Number fields, has changed. Additionally, show version will display slightly different information
depending on whether or not a build is suitable for deployment.
Build Version Number fields, has changed. Additionally, show version will display slightly different information
depending on whether or not a build is suitable for deployment.
The Version Build Number for 16.1 and onwards releases now include, at minimum, a major, maintenance, and
emergency release number, for example “16.1.2”. The appropriate version number field increments after a version has
been released. The new version numbering format is a contiguous sequential number that represents incremental
changes between releases. This format will facilitate identifying the changes between releases when using Bug Toolkit
to research software releases.
emergency release number, for example “16.1.2”. The appropriate version number field increments after a version has
been released. The new version numbering format is a contiguous sequential number that represents incremental
changes between releases. This format will facilitate identifying the changes between releases when using Bug Toolkit
to research software releases.
The following diagram shows the differences between the old numbering format and the new numbering format.
Figure 2.
Comparison of Old and New StarOS Version Numbering Formats
In the old format, the first two fields of the Build Version Number represented the Major release and subsequent
releases (MRs/ERs) would differ only by build number. Documentation references to a release included descriptive text
releases (MRs/ERs) would differ only by build number. Documentation references to a release included descriptive text