Of course not. vCenter is required to manage/configure distributed vSwitches. The configuration is then pushed out to the ESXi hosts on which it persists.
André
Hello,
nope, but with the vCenter down you are unable to manage the VDS and also unable to attach to a machine a Distributed Port Group for example.
The VDS configuration is saved and maintained at the host level, so when your Center will be back you will have the exact same configuration you left when the center was down.
The distributed port group and the relative network traffic are untouched so you will NOT have any kind of downtime on your services or the host
This is not the entire truth because different vDS Portgroups types exists and showing a different behavior. At least the PG where you have vCenter connected should use the non default "ephemeral" type which can be controlled by the ESXi it self and let him restart a VM there. There is a KB about that.
Otherwise, yes without vCenter you cant made changes to your vNetwork and cant start VMs which is a expected behavior.
Regards,
Joerg
Of course not. vCenter is required to manage/configure distributed vSwitches. The configuration is then pushed out to the ESXi hosts on which it persists.
André
Hello,
nope, but with the vCenter down you are unable to manage the VDS and also unable to attach to a machine a Distributed Port Group for example.
The VDS configuration is saved and maintained at the host level, so when your Center will be back you will have the exact same configuration you left when the center was down.
The distributed port group and the relative network traffic are untouched so you will NOT have any kind of downtime on your services or the host
thanks a lot , that made things clear for me now
thanks a lot, that made things clear for me now 😊
and you're right I have noticed this behavior with a host that was managed by vCenter.
when the vCenter was absent, I couldn't connect any new VMs to any Distributed Port Groups
again thanks for your clarification
This is not the entire truth because different vDS Portgroups types exists and showing a different behavior. At least the PG where you have vCenter connected should use the non default "ephemeral" type which can be controlled by the ESXi it self and let him restart a VM there. There is a KB about that.
Otherwise, yes without vCenter you cant made changes to your vNetwork and cant start VMs which is a expected behavior.
Regards,
Joerg