If you are upgrading or have upgraded to vSphere 6.0, you should be aware of a couple syslog gotchas. These will be especially important if you are running a central logging system like vRealize Log Insight. Read on to learn more.
Now that you know about the new RBAC feature available in Log Insight 2.5, I would like to walk you through an example on how to configure RBAC with real data.
I frequently get questions around how to forward only certain log files from ESXi or how to collect a log file that is missing. I get the question so frequently that it warrants a quick post. The title of this post says it all – it’s all or nothing. If you configure remote syslog on ESXi then you will get all configured logs files from ESXi. There is no supported way today to customize what logs files are stored locally versus sent remotely. The only customization that you can make is what severity logs messages are forwarded to the remote syslog destinations by changing log verbosity, however this is not recommended (read here for more information).
In my previous post, I discussed how to configure vRA logging. In this post I would like to provide some Log Insight Linux agent configuration samples for common Linux and VMware applications. You may notice some duplication of information. I will be updating this post over time so be sure to check back from time to time!
In case you missed it, William Lam recently put up a couple of excellent posts on how to configure some important vCenter Server alarms. As it turns out, the underlying VOB (VMkernel Observation) messages appear in vSphere logs and if your are running Log Insight you can easily check for environmental issues such as the ones he outlined.
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.
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.
As I am sure you have heard by now, VMware has released update 1 for their vSphere 5.1 products. Updates in the VMware model are considered maintenance releases. They are primarily focused around bug fixes and do not include new features. One thing I would encourage anyone using any product to do is read the release notes when new versions are released.
So why is it important to read the release notes?
I recently connected to a vSphere 5.1 environment using an old Windows Fusion VM. I was attempting to check the hardware status and I noticed that the tab was not available. I checked the plug-ins menu and noticed the following error for the hardware plug-in:
The client could not send a complete request to the server