I have done some blog posts in the past that were about creating some PowerShell scripts to use as the start of your own virtualization toolkit. With the release of vWire you now have the ability to take those PowerShell scripts and with some small changes you can use them in vWire.  vWire passes input along depending on what you want to run the script against so you add $input to your scripts to accept the input. You could consider vWire to be your toolbox to store and use your personal toolkit and have the ability to easily share with others in the community.  I hope to encourage you to give vWire a try but want to make sure you realize that PowerShell is PowerShell, so any scripts that I show you now will be ready for vWire but can be easily modified to use outside of vWire.   

I am going to be sharing my content at the vWire Content Library.  The first scripts that I have posted are to get the last ten lines of the different log files to see if there are any problems that need addressed.  I have six scripts posted to look at these log files

• 1. Messages
• 2. VPXA
• 3. Hostd
• 4. vmksummary
• 5. vmkwarning
• 6. vmkernel

This is a very good starting point when you need to gather information about your virtual infrastructure and is a very quick way to bring up the logs.  You will notice in my descriptions that you can easily edit the “-10″ value to any number you want.  This is the setting for the number of lines of the log file you want displayed.

I thought the logs would be a good place to start for an automated way to get log information and should be able to help out all VI admins.

Happy Scripting!!

Steve

ESX, powershell, vCenter, virtualization, vSphere, vWire

This entry was posted on Thursday, June 11th, 2009 at 9:20 am and is filed under Virtual Tech. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.