Updating vmware esxi
A related change we also made was to set up syslogging for a larger timeframe (full details via link below) :- The Syslog server creates a subfolder under ..\VMware Syslog Collector\Data\ for the Management IP of each host sending Syslog data. language=en_US&cmd=display KC&external Id=1003564 Configuring Syslog on ESXi 5.0:
Install ESXi from the dedicated server control panel.
Once installed go to the dedicated server IP address in a web browser and download the v Sphere Client.
This new feature negates the need to run shell commands to setup the route. The gateway of your Main IP not your failover IP, the IP that you are connecting to vsphere client on and .254 as the last octet. “Use non-local gateway through interface specific route.” Click save.
Now go back to the WAN interface and make sure the Gateway is assigned to the WAN interface.
Create and buy a Failover IP from your dedicated server provider.
language=en_US&cmd=display KC&external Id=2003322 Configure persistent scratch location:
Once booted, load up Firefox and go to 192.168.1.1 and login with admin/pfsense.The HP Proliant G6s even came with an onboard SD card slot to make it easy to leave those disk slots empty.However, ESXi 5 moved the goalposts, with USB or SD storage no longer suitable for persistent storage: hosts without local storage now mount a 32Mb Ram Disk to mount the scratch partition to.After upgrading to ESXi 5 we saw several instances of host instability as the Ramdisk ram out of space, symptoms including :- The VMs themselves continued to run on the host, just not able to manage the host properly.As a short term fix to bring the server under control again – providing the Shell is enabled – we logged onto the shell, navigated to the /var/log folder and deleted any archived log files (ending .gz) and created a new, empty wtmp file (the file recording shell access).If lost you need to configure the parameter again and bounce the server.