SOFTWARE ADVISORY NOTICE
Dear Cisco Customer,
Cisco engineering has identified the following software issues with the release that you have selected that may affect your use of this software. Please review the Software Advisory notice here to determine if the issues apply to your environment. You may proceed to download this software if you have no concerns with the issue described.
For more comprehensive information about what is included in this software, refer to the Cisco software Release Notes, available from the Product Selector tool. From this page, select the product you are interested in. Release Notes are under "General Information" on the product page.
Affected Software and Replacement Solution for CSCuv04436 |
||
Software Type |
Software Affected |
Software Solution |
Cisco UCS B-Series Blade Servers |
Version: 2.2(5a), 2.2(4b), 3.0(2c)
Affected Images: ucs-k9-bundle-b-series.2.2.5a.B.bin,
|
Version: To be released at the end of July, 2015.
Replacement Images:
|
Reason for Advisory:
This software advisory addresses one software issue.
CSCuv04436
Cisco UCS B200 M4 with Cisco UCS Manager (B Bundle) Releases 2.2(5a), 2.2(4b), 3.0(2c) has performance impact.
Affected Platforms:
Cisco UCS B200 M4 Blade Servers configured with these specific CPUs: E5-2667 v3, E5-2643 v3, E5-2640 v3, E5-2637 v3, E5-2630 v3, E5-2630L v3, E5-2623 v3, E5-2620 v3, E5-2609 v3
Other Intel CPU model SKUs are not impacted by this issue.
Symptom:
The CPU performance on a Cisco UCS B200 M4 Blade Server may decrease while running Cisco UCS Manager (B Bundle) Releases 2.2(5a), 2.2(4b) or 3.0(2c). Performance may drop by three times as compared to the same system running Cisco UCS Manager (B Bundle) Release 2.2(3g).
This issue may be seen on Cisco UCS Manager (B Bundle) releases 2.2(5a), 2.2(4b) and 3.0(2c) on systems with these Intel® Xeon® Processor E5-2600 v3 Product Family CPUs: E5-2667 v3, E5-2643 v3, E5-2640 v3, E5-2637 v3, E5-2630 v3, E5-2630L v3, E5-2623 v3, E5-2620 v3, E5-2609 v3.
Conditions:
See Symptoms.
Workaround: This issue has no known workaround.
More Info: None