cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Field Notice 70545
2394
Views
5
Helpful
6
Replies
navinjk1974
Beginner

Different UCSM and Blade Versions

We have a mix of B200 M3 and B200 M4 servers a total of 20+ Blades running currently on 2.2(5b) UCSM Version and with a recent Infosec update we need to fix some Vulnerabilities with Vmware and wanted to know if can just upgrade the Server Blades to a later version and keep the InfraStructure running at 2.2(5b)

 

Let me know if you need any clarifications.

1 ACCEPTED SOLUTION

Accepted Solutions

2.2.8g is the suggested release at the moment on Cisco.com, no known issues unless documented in release notes.

 

I would suggest using the auto-install feature and do not acknowledge the reboot of the second FI until you have confirmed all the data paths (virtual ethernet interfaces) are back online after the reboot of the subordinate FI. If you use auto-install, you do not need to conduct any manual steps.

 

Please mark this information as helpful or correct if it was.

 

View solution in original post

6 REPLIES 6
Wes Austin
Cisco Employee

Yes, you would utilize server packs.

 

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/CiscoUCSManager-RN-22.html#reference_rv2_xgq_5y

 

Release 2.2(4b) adds support for the following:

 

  • Server Pack—This feature allows you to support new server platforms* on existing infrastructure without requiring a complete firmware upgrade. In this model, new B/C server bundles enabling the new servers will be supported on the previous infrastructure A bundle. For example, Release 2.2(5) B/C server bundles are supported with Release 2.2(4) infrastructure A bundle as highlighted in Updating Cisco UCS Releases. New features introduced in the B/C bundles may only become available after upgrading the A bundle to the respective version.

     

    The Server Pack feature provides the additional flexibility of adding new server platforms to active UCS domains without incurring the operational overhead of upgrading firmware across the whole domain.

     

    *The feature will apply to select server platforms.

rahulk3
Cisco Employee

Hi, 

 

Please be advised that only M4 servers can have higher firmware version than UCSM starting with 2.2(4). 

 

For M1, M2, M3 servers, only N, N-1 cross-version firmware is supported. For example, for B200 M3 servers, the 2.2(4)A bundle will be supported with 2.1(1)B, 2.1(2)B, 2.1(3)B, 2.2(1)B, 2.2(2)B, 2.2(3)B, and 2.2(4)B bundles).

 

In your case, B200 M3 can not be upgraded above 2.2(5c).  

B200 M4, you can upgrade. 

 

Beginning with Cisco UCS Manager Release 2.2(4), and for M4 servers, a lower version of the infrastruc-ture A bundle will be compatible with the previous version and higher version of B and C server bundles. For example, the Cisco UCS Manager Release 2.2(4)A bundle will be supported with any of the following B bundles for B200-M4 servers: 2.1(1)B, 2.1(2)B, 2.1(3)B, 2.2(1)B, 2.2(2)B, 2.2(3)B, 2.2(4)B, 2.2(5)B, 2.2(6)B, 2.2(7)B, 2.2(8)B.

 

Thanks,

rahul Kumar

Thanks for the responses, i would like to add some clarification so to achieve my work.

We would like to plan our Vmware Esxi Env to VMware Vsphere 6.0 Update3 and understand that we need to be at 2.2 (8g).

 

Current UCSM running at 2.2(5b) With B200 M3 and B200 M4 Servers Vmware 6.0 U2. What should be our Upgrade Path to meet the above req ?

 

1- Plan and Upgrade Infrastructure Code to 2.2(8b)

2- Next Upgrade all the Blades to 2.2(8b) and then the Vmware Esxi.

 

Do you see if the above Plan works as expected ?

You are correct. First you would upgrade your UCSM to 2.2.8g, followed by subordinate FI/IOMs. Then you would execute a 'cluster lead change' and follow the same procedure on the now subordinate, once primary FI/IOMs.

 

Next, create a host firmware package for 2.2.8g and apply it to your service profiles. If you are following best practices by utilizing a "user-ack" maintenance policy, you will be able to put the hosts in maintenance mode as you conduct the firmware upgrade. Do not forgot to double check your enic/fnic, etc drivers to ensure they are compatible with the new firmware version.

 

UCS HW and SW Compatibility

Thanks for the details, also is there something quick to share about known issues with the upgrades to the version, apart from reading the release notes for the ver. 

2.2.8g is the suggested release at the moment on Cisco.com, no known issues unless documented in release notes.

 

I would suggest using the auto-install feature and do not acknowledge the reboot of the second FI until you have confirmed all the data paths (virtual ethernet interfaces) are back online after the reboot of the subordinate FI. If you use auto-install, you do not need to conduct any manual steps.

 

Please mark this information as helpful or correct if it was.

 

Create
Recognize Your Peers
Content for Community-Ad