This is a known issue affecting vCenter Server Appliance 5.1 Update 1a and Update 1b.
To work around this issue if you are unable to upgrade, modify the vpxdva_subsequentboot_net configuration file.
To modify the vpxdva_subsequentboot_net configuration file:
- Connect to the vCenter Server Appliance via SSH. For more information, see Enable or Disable SSH Administrator Login on the VMware vCenter Server Appliance in the vCenter Server and Host Management Guide.
- Navigate to the /usr/sbin/ directory.
- Back up the vpxdva_subsequentboot_net file. Do not skip this step.
- Open the vpxdva_subsequentboot_net file using the vi editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
- Add the line:
/etc/init.d/haveged start
For example, change the default configuration file from:
#!/bin/bash
# this is executed on each boot, except the first,
# after network has been brought up.
COMMONUTILS=/usr/sbin/vpxd_commonutils
. $COMMONUTILS
regenerate_certificates
To:
#!/bin/bash
# this is executed on each boot, except the first,
# after network has been brought up.
COMMONUTILS=/usr/sbin/vpxd_commonutils
. $COMMONUTILS
regenerate_certificates
- Save and close the vpxdva_subsequentboot_net configuration file.
- Reboot the vCenter Server Appliance.