Monday, February 27, 2012


Andrew Miller (a new VCDX) took some excellent notes from the VMware Partner Exchange this year. Check them out here:

Friday, February 24, 2012



Sorry folks but last year was terribly busy year with all the projects virtualization was involved with around Health Care. VMware deffinately has moved into servicing Tier 1 application needs.

I was also busy with studying for the VCP 5 test which I passed on the first try...and yes I did think this was one of the more challenging certification tests I have seen from VMware for VCP level certification.

Late last year I started experimenting with the EMC Cellera and VNX virtual storage appliances trying to get some early experience for what I hoped was coming.

But enough of the past and lets look into 2012 now. My vCenter was upgraded to vCenter 5 level in December and now that HP finally got their driver and firmware issues worked out for the HP BL460c G6 and G7 blades and vSphere 5 we are off on our migration to vSphere 5. I just recently moved my virtual vCenter and it separate SQL database vm off of old hardware to newer blades and like the better performance.

In addition we have bought 2 EMC VNX 5500 units which I am looking forward to learning and using starting in March time frame. We have been wanting some EMC storage for a long time so very excited about this. I am most excited about the ability to do some LUN provisioning at the vCenter level. I really think the efficiency and control being closer to the virtual admin level will help make much wiser choices in the LUN work ahead in Migration to VMFS 5 (which to do right really needs to be an empty the LUN and reformat).

I'll try my best to start sharing the many things I am learning!

Wednesday, February 22, 2012


I am using vCenter 5 and fully patched vSphere 5 (build shows 515841). I have VMware's new "Network Syslog Collector" running on my vCenter. I had about 6 new vSphere 5 servers pointing to the vCenter syslog server without issue. I moved my vCenter to a vSphere 5 server and updated the VMware tools and did a reboot. After this I noticed no servers showing in the "Network Syslog Collector" section of vCenter. Worked with VMware support and they are submitting as a bug. Also, apparently vCenter updates this only as you start the client, there is not refresh button, so as you fix this or add servers to this syslog collector you need to exit vCenter and come back in to see them.

Temporary solution for now to fix follows but this would be a pain in large environments like ours.
Restarting syslog on vSphere 5 server:
ps | grep vmsyslog
ps | grep vmsysl~ # ps | grep vmsyslog
62469 62469 vmsyslogd            /bin/python
62470 62469 vmsyslogd            /bin/python
62471 62469 vmsyslogd            /bin/python

VMware RSS Feed