VMware vSphere

 View Only
  • 1.  impact of restarting esx management service

    Posted Jun 03, 2013 03:19 PM

    Dear team,

    in my environment i have esx 3.5.0 (64607),4.0,4.1 hosts, just want to know is there any impact if i restart management service on production esx hosts 3.5.0, 4.0,4.1

    be fore restarting this service do i need to take check anything, is there any pre-requisite ?????

    regards

    Mr VMware



  • 2.  RE: impact of restarting esx management service

    Posted Jun 03, 2013 03:52 PM

    Restarting Management agents will not have any impact for the guest VM's running



  • 3.  RE: impact of restarting esx management service

    Posted Jun 03, 2013 04:10 PM

    They will disconnect from vCenter and any monitoring solutions you have will trigger alerts (If they are configured) but as aravnds3107 said, there will be no impact on your running guest VM's other than no vMotion capability.



  • 4.  RE: impact of restarting esx management service

    Posted Jun 04, 2013 05:27 AM

    thanks friends....

    u means to say that if we restart management service it won't impact vm performance , network, i/o, management service console ip connectivity noting will be impacted but is there any impact on esx if we restart the same???

    regards

    Mr VMware



  • 5.  RE: impact of restarting esx management service

    Posted Jun 04, 2013 06:38 AM

    No Impact on the ESX or Vms, The VMs will continue to run, but will show as disconnected. It will be stopping and starting the management service and during this time you will see the vms are disconnected from the vcenter.

    Also your vm console via vcenter will get disconnected. Once agent gets restarted the host and vm gets connected to VC back within a minute or so.

    M4You



  • 6.  RE: impact of restarting esx management service

    Posted Jun 04, 2013 08:42 AM

    but is there any impact on esx if we restart the same???

    During the period you will noticed host gets disconnected from the vCenter and gets re-connected



  • 7.  RE: impact of restarting esx management service

    Posted Jun 04, 2013 01:13 PM

    The management service IP connectivity will be lost during a restart of the management agents on the ESXi hosts.  The only thing that won't be affected will be the actual VM's running on that host.  When you say "impact on esx if we restart the same?" are you talking about rebooting the host or just the management agents?  The management agent(s) are on the hosts so that's what would be affected - again, only connectivity to the service console, the connection to vCenter, and the ability of HA/vMotion.



  • 8.  RE: impact of restarting esx management service

    Posted Jun 30, 2013 03:54 PM

    Cloning, Image backup (VCB), vMotion, SVMotion will be impacted, in other words running task on that ESX will be impacted , let me know if i m wrongs and contribute if you know any other things will also impacted if we retsrat ESX management service.



  • 9.  RE: impact of restarting esx management service

    Posted Jul 01, 2013 01:12 PM

    No impact to ESX/ESXi hosts and VM's.



  • 10.  RE: impact of restarting esx management service

    Posted Jul 01, 2013 01:44 PM

    Restarting of management agents will stop/terminate the current running process in the host (Cloning, Image backup (VCB), vMotion, SVMotion) the vms will not be impacted but there is something called APD (All path dead) introduced in 4.0 i guess, if your ESXi host LUN/LUNs are in APD state there are more possibility that the hostd agent will not restart successfully. You will have to end up in restarting the host to remove APD condition.


    So before restarting the managament agents make sure you do not have LUNs in APD condition. You can have a look at the below article

    VMware KB: ESXi/ESX hosts in APD may appear Not Responding in vCenter Server