Plus sometimes you are unable to perform any changes until you do upgrade the Edges, so if a customer needs to change firewall or NAT rules, you are pretty much forced to upgrade the Edges and you can’t really wait for the ESXi / v Center upgrade.
You cannot install a format with any of the names ".", "..", "register", or "status", as these are used by the filesystem or the binfmt_misc module.Or rather, affected VMs NIC type MISMATCH for [VM – Ubuntu 11.10 64 Bits(vm-25618), VAPP – Ubuntu 11.10 64 Bits, Org – London-Templates, Guest OS -ubuntu64Guest, MAC – :, VCD nic type = VMXNET3, VC nic type = E1000] This is good. Killing the cell while a job is running could cause jobs stay hanging in the DB, requiring you to dig around SQL, trying to get rid of it. But you might forget to remove the permissions again, so you may as well just run it manually in SQL Management Studio (Plus your DBA might not like the idea 😉 ) Now go ahead and start the v Cloud Cell service the DB upgrade.At this stage your v Cloud interface should be up and running.This is important in order to understand limitations, known issues etc. The production environment I worked on was quite large so each step pretty much needed a maintenance window.
I have seen setups where the upgrade would have broken the environment. So whilst the v Center and ESXi upgrade was scheduled for a later date, the v Shield Edges had sometimes a different idea.
Obviously every environment is different, but the guide here should be comprehensive enough for you to get an idea what to look out for.