Swapping VC with newer firmware VC's

[cesarpegado]

Guys,

Were currently running VC's running version 4.41 and we have problems collecting logs from these, apparently a known issue on this firmware. So ideally we need to upgrade these to a newer version.

We currently have 2 chassis in 1 VC Domain, and from my understanding if we upgrade these it will need to stop servicing blades for a while while the upgrades completes.

I'm not going to get a chance to power off both enclosures to allow the upgrade, so can anyone else suggest another idea? If we got 4 new VC's running a newer o/s would we get away with putting out config on these and swapping the VC's 1 at a time. IOR would the chassi complain that the running VC has older firmware than the newly inserted one?

Thanks

[Torsten.]

AFAIK the firmware update can always be done online.

[cesarpegado]

i was under the impression that potentially the FC had to be stopped for a while it does this. As these blade chassis house ESX hosts we can't afford for the FC to be off any sort of time

[Torsten.]

During the update the firmware is uploaded to the modules first, then you reboot the modules to active the new firmware (activation order setting). While rebooting, the module does not provide service, but the parner module is still working, unless you set to reboot them all at the same time.