2.2.5a Caveat

[Walter Dey]

Just in case you have not seen it

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, ucs-k9-bundle-b-series.2.2.4b.B.bin, ucs-k9-bundle-b-series.3.0.2c.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

[johnd0e88]

Delete this my* comment.

[Walter Dey]

Hi John

Don't understand your comment ? please clarify !

I wanted to download 2.2.5a, and then stepped over this comment, which I first didn't understand, because I didn't scroll down the page.

My 2c

- why is this release still on CCO ? (well it only applies to B200-M4, nevertheless.....)

- why is this release tagged as recommended ?

Walter.

[johnd0e88]

Never mind my comment. I answered my own question. It would not let me delete it so it can be ignored. 

I see the confusion. I was talking to any mods that may see it. I wanted them to delete my own comment, which was previously a question to your post. 

[Walter Dey]

FYI, 2.2.5b has been posted June 30, B200-M4 issue is resolved !

Table 4 Internal Dependencies

Component	Recommended Minimum Software Version 2	Recommended Software Version
Servers
B22 M3 E5-2400 B22 M3 E5-2400 v2	2.1(3g) 2.2(2e)	2.2(5b) 2.2(5b)
B200 M1 and M2	2.2(2e)	2.2(5b)
B200 M3 E5-2600 B200 M3 E5-2600 v2	2.1(3g) 2.2(2e)	2.2(5b)
B200 M4	2.2(3a)	2.2(5b)

[johnd0e88]

Thank you for the heads up, Walter. Here are the resolved caveats:

The following caveats are resolved in Release 2.2(5b):

Defect ID	Description	First Bundle Affected	Resolved in Release
CSCuv04436	Cisco UCS B200 M4 servers with the following CPUs will no longer experience performance degradation: 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	2.2(4b)B	2.2(5b)B 2.2(4c)B
CSCuv29668	When using Cisco UCS 6100 Series Fabric Interconnects with Cisco UCS 2100 IOMs, blade servers with two Cisco UCS M81KR VIC adapters no longer fail discovery after updating Cisco UCS Manager to Release 2.2.(5b) and later releases.	2.2(4b)A	2.2(5b)A
CSCus64439	Cisco UCS Manager Mezz logs and VMware vmkernel logs no longer indicate storage latency and numerous FNIC aborts.	2.2(1d)B	2.2(5b)B
CSCus11782	After rebooting a Cisco UCS 6248UP Fabric Interconnect (FI) that is operating in the FC end-host mode, all member links of the SAN port channel come up.	2.2(1d)A	2.2(5b)A
CSCuu35687	In Cisco UCS B420 M4 servers with UCSB-MRAID12G and UCSB-LSTOR-PT RAID controllers, the Fault/Locator LEDs for disks 3 and 4 are no longer swapped.	2.2(5a)B	2.2(5b)B
CSCuu58282	In Cisco UCS B420 M4 servers with UCSB-MRAID12G and UCSB-LSTOR-PT RAID controllers, in the rare event that Online Controller Reset (OCR) is triggered during normal I/Os on JBOD drives, excessive Fast Path IO failures are no longer seen after the controller is reset.	2.2(5a)B	2.2(5b)B

[yar0slavm]

Hi Walter - just to clarify the bug was resolved in 2.2(4c)B , then re-appeared in 2.2(5a)A and resolved again in 2.2(5b)B ?