Cisco Cisco IOS Software Release 12.1(1)E3 Références techniques
Corporate Headquarters:
Copyright © 2003. Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Cisco Hybrid IOS Safe Harbor Testing for
Financial Enterprise Customers, Releases 6.4(4a)
and 12.1(8b)E15
Financial Enterprise Customers, Releases 6.4(4a)
and 12.1(8b)E15
Version History
Cisco Safe Harbor is an initiative, the goal of which is customer success through improved quality. Safe
Harbor delivers Catalyst 6500 switch customers with a certified Cisco OS version of choice for critical
deployment. Safe Harbor certified code has shortened customer deployment times while increasing their
overall network stability.
Harbor delivers Catalyst 6500 switch customers with a certified Cisco OS version of choice for critical
deployment. Safe Harbor certified code has shortened customer deployment times while increasing their
overall network stability.
Safe Harbor subjects targeted releases (deployed in topologies consistent with those of identified
customers) to complex levels of testing. The program offers additional benefit by serving as the conduit
through which customer information can influence Cisco premier testing.
customers) to complex levels of testing. The program offers additional benefit by serving as the conduit
through which customer information can influence Cisco premier testing.
The Cisco nEverest program is a similar initiative that leverages Safe Harbor test results and expands its
concept into other vertical market platforms.
concept into other vertical market platforms.
Cisco Hybrid IOS Release 6.4(4a)/12.1(8b)E15 is an iterative Cisco Hybrid IOS 6.4(4a)/12.1(8b)E14
Safe Harbor release that integrates fixes for specific defects (DDTSs). After integration of the DDTS
fixes into Cisco Hybrid IOS Release 6.4(4a)/12.1(8b)E15, the nEverest test team conducted extensive
automated negative stress testing to check stability and to expose any memory leaks. Cisco Hybrid
IOS Release 6.4.(4a)/12.1(8b)E15 passed all performed negative stress testing.
Safe Harbor release that integrates fixes for specific defects (DDTSs). After integration of the DDTS
fixes into Cisco Hybrid IOS Release 6.4(4a)/12.1(8b)E15, the nEverest test team conducted extensive
automated negative stress testing to check stability and to expose any memory leaks. Cisco Hybrid
IOS Release 6.4.(4a)/12.1(8b)E15 passed all performed negative stress testing.
The DDTS fixes in Cisco Hybrid IOS Release 6.4(4a)/12.1(8b)E15 preserved the Cisco Hybrid
IOS Release 6.4(4a)/12.1(8b)E14 Safe Harbor test progression and test plan integrity. Therefore, please
refer to the Cisco Hybrid IOS Safe Harbor Testing for Financial Enterprise Customers, Release 6.4(4a)
and 12.1(8b)E14 document for a summary of the system-level and reliability testing completed atop the
Financial Enterprise profile. If you would like to see the contents of this document and you are a Cisco
customer, it is available at the following URL:
IOS Release 6.4(4a)/12.1(8b)E14 Safe Harbor test progression and test plan integrity. Therefore, please
refer to the Cisco Hybrid IOS Safe Harbor Testing for Financial Enterprise Customers, Release 6.4(4a)
and 12.1(8b)E14 document for a summary of the system-level and reliability testing completed atop the
Financial Enterprise profile. If you would like to see the contents of this document and you are a Cisco
customer, it is available at the following URL:
If you are a Cisco employee and would like to see supplementary information related to this testing,
please go to the documentation page of the nEverest website and select the appropriate Safe Harbor
release under the Enterprise Financial profile. The nEverest website can be found in CEC by searching
on the term “nEverest.”
please go to the documentation page of the nEverest website and select the appropriate Safe Harbor
release under the Enterprise Financial profile. The nEverest website can be found in CEC by searching
on the term “nEverest.”
Version Number
Date
Notes
1
August 08, 2003
This document was created.
2
July 6, 2004
This document was updated.