Cisco Cisco Packet Data Interworking Function (PDIF)
System Changes in Release 16
System and Platform Enhancements for 16.1 ▀
Release Change Reference, StarOS Release 16 ▄
615
to indicate whether the release was an MR or ER. For instance, “16.0.65781 MR1” indicates via its descriptor that it is
the first maintenance release for 16.0.
the first maintenance release for 16.0.
In the new format, the maintenance release number changes with subsequent Maintenance Releases (MRs). For
example, “16.2” would represent the second maintenance release (MR2) of release 16.
example, “16.2” would represent the second maintenance release (MR2) of release 16.
A third digit in the Build Version Number now indicates an Emergency Release for a previous FCS or MR build. For
example “16.1.3” indicates the third ER of the first MR of the 16.0 major release.
example “16.1.3” indicates the third ER of the first MR of the 16.0 major release.
The Build Version Number may now also include an optional variant indicator just before the ER number to identify the
release as a variant of an MR or ER Release. A variant release is one that is given to a particular customer or group of
customers, as opposed to a mainstream release which is suitable for all customers.
release as a variant of an MR or ER Release. A variant release is one that is given to a particular customer or group of
customers, as opposed to a mainstream release which is suitable for all customers.
Important:
For detailed information on other changes associated with this numbering scheme, refer to the
StarOS Version Numbering appendix in the System Administration Guide and the show version chapter of the Statistics
and Counters Reference.
and Counters Reference.
Performance Indicator Changes
show version
Changes relative to the adoption of a new StarOS numbering system now appear in the output of the show version
command for deployment builds that appear on customer systems.
command for deployment builds that appear on customer systems.
A deployment build has been qualified as suitable for deployment in customer networks. The build number only appears
in the Image Build Number line.
in the Image Build Number line.
A sample output of the 16.1 show version command for a deployment build appears below.
[local]asr5000# show version
Active Software:
Image Version: 16.1.0
Image Build Number: 56012
Image Description: Deployment_Build
Image Date: Mon Jun 30 17:05:09 EDT 2014
Boot Image: Unknown
CSCuo70354 - Unable to set more than one BGP extended community using
route-map
Applicable Products: All
Feature Changes
Multiple BGP Community and Extcommunity Destinations