This is a known issue affecting the vCenter Server Appliance 6.0.
This issue is resolved in VMware vCenter Server 6.0 Update 2, available at
VMware Downloads.
To work around this issue, restart the
snmpd service:
- From the vCenter Server Appliance Shell:
- Connect to the vCenter Server Appliance with SSH using root credentials.
- Run this command to stop the snmpd service:
snmp.disable
- Run this command to start the snmpd service:
snmp.enable
- From the vCenter Server Appliance Bash Shell:
- Connect to the vCenter Server Appliance with SSH using root credentials.
- Run this command to enable the shell:
shell.set --enabled true
- Run this command to launch the shell:
shell
- Run this command to restart the service:
service snmpd stop;service snmpd start
To automate the process, create a cron job to restart the service periodically:
- Connect to the vCenter Server Appliance with SSH using root credentials.
- Run this command to enable the shell:
shell.set --enabled true
- Run this command to launch the shell:
shell
- Run this command to open crontab:
crontab -e
- Add this line:
*/5 * * * * /etc/init.d/snmpd stop && /etc/init.d/snmpd start
- Save and exit the file by typing :x.
You see output similar to:
no crontab for root - using an empty one
crontab: installing new crontab
- Run crontab -l to confirm the entry is added successfully. You should see output similar to:
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.XXXXoox20I installed on Wed Nov 11 16:25:52 2015)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
*/5 * * * * /etc/init.d/snmpd stop && /etc/init.d/snmpd start