Analyzing vSphere with Free Tools “Syslog”

Virtualization is a great technology, but sometimes it can be hard getting a closer look into your environment.  Over the next few post I am going talk about a few free tools that I use in my environment.  They have given me a lot of support in managing my environment, and I would like to think the people who made them.

Syslog can be a very useful tool.  The problem with it is that it can be very painful to use.  Luckly VMware has a great tool for that and that tool is LogInsight. It makes a great syslog server and has a lot of other features that you may find invaluable.  It is a paid product so what is a great alternative?  Sexilog is that great alternative.  With it you point all your esx host to it and watch the magic happen. Very quickly you get a better insight what is happening inside your environment. It may not have as many features as LogInsight, but nothing beats it on feature compared to price.

Using PowerCLI to change the Syslog server for your ESX host.

I recently discovered SexiLog to use with VMware ESX host.  I needed a quick and easy way to change where the ESX host sent there logs to.  Doing some google searches I was able to put together a quick PowerCLI script.  In about 5 minutes I was able to change the syslog for all of my ESX host.

$ESXLOG = “1.2.3.4”
Get-VMHost | Foreach {
Write-Host “Adding $ESXLOG as Syslog server for $($_.Name)”
$SetSyslog = Set-VMHostSysLogServer -SysLogServer $ESXLOG -SysLogServerPort 514 -VMHost $_
Write-Host “Reloading Syslog on $($_.Name)”
$Reload = (Get-ESXCLI -VMHost $_).System.Syslog.reload()
Write-Host “Setting firewall to allow Syslog out of $($_)”
$FW = $_ | Get-VMHostFirewallException | Where {$_.Name -eq ‘syslog’} | Set-VMHostFirewallException -Enabled:$true
}

Blog at WordPress.com.

Up ↑