We proceed to update from version 2.2 (8i) to 4.1 (2a) through automatic installation with the infrastructure firmware option.
The entire procedure is performed as expected and once the infrastructure upgrade (UCSM, Fabrics, IOM) is finished.
But later we see that each Blade is in discovery mode even though they have User Ack policy.
Subsequently, we see in the events of each server that apparently the discovery restarted the blade but at the Vmware level (vmware 6.5 cluster) the uptime of the hosts that did not reboo. However, all virtual machines were restarted due to communication failures with the storage (this communication is redundant using both fabric interconnect)
This platform had already been updated to version 2.2 (8i) in Jan-2018 in an equivalent way without problems.
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 ...