ESXi 6.x -Restart Mgmt Agents via CLI

Experiencing issues connecting to an ESXi host from vCenter Server?

A good place to start your troubleshooting is by restarting the ESXi management agents.

The following method uses the CLI option SSH/Local console to restart an ESXi host management agents:

/etc/init.d/hostd restart
/etc/init.d/vpxa restart

Screen Shot 2016-05-01 at 11.16.09

 To restart all management agents on the host, run the command:

services.sh restart

View a list of all management agents restarted as part of the ‘services.sh restart’ cmd:

chkconfig -io

[root@ESXi01:~] chkconfig -io
/etc/init.d/vsanmgmtd
/etc/init.d/vsanObserver
/etc/init.d/vsantraced
/etc/init.d/vsandevicemonitord
/etc/init.d/ntpd
/etc/init.d/SSH
/etc/init.d/DCUI
/etc/init.d/swapobjd
/etc/init.d/usbarbitrator
/etc/init.d/vvold
/etc/init.d/sdrsInjector
/etc/init.d/vmfstraced
/etc/init.d/storageRM
/etc/init.d/rhttpproxy
/etc/init.d/hostd
/etc/init.d/nfcd
/etc/init.d/lbtd
/etc/init.d/sensord
/etc/init.d/rabbitmqproxy
/etc/init.d/slpd
/etc/init.d/dcbd
/etc/init.d/cdp
/etc/init.d/smartd
/etc/init.d/nscd
/etc/init.d/lacp
/etc/init.d/memscrubd
/etc/init.d/vobd
/etc/init.d/vpxa
/etc/init.d/sfcbd-watchdog
/etc/init.d/snmpd
/etc/init.d/sfcbd
/etc/init.d/wsman
/etc/init.d/xorg
/etc/init.d/vmsyslogd
/etc/init.d/vmtoolsd

Confirm what agents are running:

chkconfig –list

[root@ESXi01:~] chkconfig –list
vsanmgmtd on
vsanObserver on
vsantraced on
vsandevicemonitord on
ntpd on
SSH on
DCUI on
ESXShell off
ddecomd off
clomd off
cmmdsd off
epd off
vsanvpd off
swapobjd on
osfsd off
usbarbitrator on
vvold on
sdrsInjector on
iofiltervpd off
vmfstraced on
storageRM on
rhttpproxy on
hostd on
nfcd on
lbtd on
sensord on
pcscd off
vprobed off
rabbitmqproxy on
nfsgssd off
slpd on
dcbd on
cdp on
smartd on
nscd on
lacp on
memscrubd on
vobd on
vpxa on
lwsmd off
sfcbd-watchdog on
snmpd on
sfcbd on
wsman on
xorg on
vmsyslogd on
vmtoolsd on

 

One thought on “ESXi 6.x -Restart Mgmt Agents via CLI

  1. Dave have you run into any issues when restarting the mgmt agents on VSAN?

    I know there is a KB describing issues if VSAN is in a LACP config but I seem to recall it causing additional issues even when it was not. Essentially the backend LSOM components have trouble communicating and ive seen erradict behavior. Just curious on your take.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s