I hit an interesting issue the other day when attempting to reconfigure remote syslog on some ESXi hosts. What followed was an exercise on troubleshooting remote syslog on an ESXi host and I wanted to share some tips.
I ran into a frustrating issue the other day when attempting to add multiple new virtual disks to an existing VM. Upon doing so, I received the dreaded “Operating System not found” message when the VM was started. While the underlying issue was easy to discover, the way to fix the problem became tedious due to issues with the vSphere web client. This post contains some tips and tricks to make the process easier.
A while back, I came across an entry from Michael White’s newsletter about changing VMware ESXi host logging levels:
Changing VMware ESXi host logging level
Someone was talking about doing this, and using this as a guide, but I would like to say you may not want to do this. There may be a reason for the log levels, and if you change them it may be harder to support you if you call VMware for help. And your syslog of choice should be able to handle the volume and I know – in fact better than most – that ESXi logs are noisy, but you can deal with that with good searching.
One of the great features of Log Insight is its tight integration with other VMware products. One of these integrations is with vSphere. I have talked about vSphere integration in the past, however I would like to do so in more details to clear up some questions I have received lately.
In part 1 of the article, I talked about a bug in ESXi when using AutoDeploy that log messages would have the hostname set to localhost. Now, I would like to talk about the impact of this bug on Log Insight and the vSphere content pack.
Have you ever seen ESXi syslog events that have a the hostname field set to localhost no matter how the ESXi host or the syslog server is configured? Are the ESXi hosts experiencing this issue using AutoDeploy? If so, this article is for you!
Back in May of last year I wrote about how ESXi would stop sending syslog messages to remote syslog destinations if a remote syslog destination became unavailable. I would like to provide an exciting update to this story!
Now that you have vCenter Log Insight deployed and configured, you need to configure sources to send their log messages to Log Insight. If you enabled vCenter Server integration then you should start to receive log messages, but this is only the beginning of configuring remote syslog sources.
IMPORTANT: Configuring vCenter Server integration does not configure vCenter Server or ESX/ESXi hosts connected to vCenter Server to send remote syslog to Log Insight. For more information continue reading!
Let’s start by going over what Log Insight supports today and what mechanisms it has to configure vSphere devices for you.
VMware has had the following KB article for some time now, but I think it is important to highlight it: http://kb.vmware.com/kb/2003127.
So what do you need to know?
I ran into a interesting problem the other day. I was brought into an environment that had a pair of ESXi 5.1 hosts connected to an iSCSI datastore. One host could see and access the datastore without issue while the other host showed no datastore attached. Per the administrator both hosts had been mounted to the datastore and the claim was that the environment had not be touched/changed in any way.
What was going on and how can you fix it?