Prior to version 2.1 of UCSM, the versions of firmware needed to match on blades and infrastructure. Ideally Major, Minor, and bugfix versions match exactly, but Major and Minor matching are officially supported. However, the infrastructure needs to be at the highest level.
For UCSM the Major release is the first two numbers, the Minor is the first number in the parenthesis and the bugfix letter is the letter. For example, in 2.0(4a), 2.0 is the Major, 4 is the Minor, and "a" is the bugfix version.
Starting at version 2.1 we support the current version and two minor releases prior. So currently with version 2.1(1f) you can run blades with version 2.0(5) and 2.0(4).
Specifically in your case, I'm going to double check that the infrastructure would need to be at 2.0(4b) or if it could remain at 2.0(4a) and have the blades at 2.0(4b)
Was trying to get neworking to work on a new Ubuntu install on a UCS server. I did a "shutdown -r" and rebooted the server. Now it seems to be stuck in the Aptio setup utility. I either choose "save and exit" or exit without saving changes and I am brough...
Just wonder we recently try to add 2 M200 with firmware 4.1.1b, our UCS manager version is 4.0.2d, we got error said cannot donwgrade. I know we can update ucs manager from 4.0 to 4.1, bur wonder we can downgrade
OpenStack Neutron project offers pluggable framework means you can extend the capability of Neutron by orchestrating the Neutron functions to your upstream networking gears. For example, if you have provisioned a VLAN tagged Neutron network in Op...
https://soundcloud.com/user-327105904/s7e25-from-the-office-to-anywhere-empowering-secure-remote-work-with-cisco-vdi-solutions As organizations have had to rapidly respond and transition in the face of swift change, Cisco VDI solutions have enabled ...