tag:blogger.com,1999:blog-60598742410178584762024-03-16T19:52:10.910+01:00VMware Front ExperienceTaking server virtualization down from the clouds to real life experience ...Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.comBlogger230125tag:blogger.com,1999:blog-6059874241017858476.post-9360408469915273212016-11-24T07:34:00.000+01:002016-12-14T15:07:15.213+01:00ESXi 6.5 Release Notes for free license and white box users<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjVue5NRsSs3kf9VXq8u_CgXDjaB8ioqRiNn6__1qLTt70nv8rc5wMMCAeR8wiVVCDQOIRV51iKCg4MiRTB69mHCxhr50K81EJV0ga6QV9EVPoD3LaakexLzZdhwsGT2aq4-jfG51ioDuqx/s1600/ESXi65-Upgrade_edit5.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjVue5NRsSs3kf9VXq8u_CgXDjaB8ioqRiNn6__1qLTt70nv8rc5wMMCAeR8wiVVCDQOIRV51iKCg4MiRTB69mHCxhr50K81EJV0ga6QV9EVPoD3LaakexLzZdhwsGT2aq4-jfG51ioDuqx/s1600/ESXi65-Upgrade_edit5.gif"></a></div>
<br>
<br>
VMware has made vSphere 6.5 generally available on November 15th, and this includes the core hypervisor platform ESXi 6.5. In the <a href="http://www.vmware.com/go/vsphere65whatsnew" target="_blank">What's New</a> and <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-esxi-vcenter-server-65-release-notes.html" target="_blank">Release Notes</a> documents you can read all about the exciting new features, but most of them require paid licenses and a vCenter server to centrally manage your ESXi hosts.<br>
<br>
This blog post is my first try to explain what free license users and owners of unsupported ("white box") hardware need to know when they are going for an upgrade or installation of ESXi 6.5 ...<br>
<br>
<a href="http://www.v-front.de/2016/11/esxi-65-release-notes-for-free-license.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com38tag:blogger.com,1999:blog-6059874241017858476.post-36508859439975583922016-11-23T14:02:00.002+01:002016-12-09T09:44:42.147+01:00[Update] ESXi-Customizer-PS 2.5 - The ESXi image customization script<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgomsTy1dWXjaElUSIDjRONzg_jf_onuff6FBy0sQvrCTJM0dP4mc4pUH0nBQ6PFr8qYabdtoSaimBDc85iW5oyIY9rbBYF1lqVkawp0IQlAxrbcYNd3OROobmUtLL2IHvG3TlpHnNaoY94/s1600/ECPS25-Icon.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgomsTy1dWXjaElUSIDjRONzg_jf_onuff6FBy0sQvrCTJM0dP4mc4pUH0nBQ6PFr8qYabdtoSaimBDc85iW5oyIY9rbBYF1lqVkawp0IQlAxrbcYNd3OROobmUtLL2IHvG3TlpHnNaoY94/s1600/ECPS25-Icon.png" /></a></div>
This is just a quick heads up for the users of my <a href="https://esxi-customizer-ps.v-front.de/" target="_blank">ESXi-Customizer-PS</a> script for ESXi image builds and customizations. I have just published the new version 2.5 of the script, and that adds<br />
<ul>
<li>full support of vSphere 6.5 (use the new <i>-v65</i> switch to limit Image profile selection)</li>
<li>support of PowerCLI 6.5</li>
<li>enhanced logging capabilities</li>
</ul>
<div>
If you have run into issues with older versions of the script then please update now and let me know how it goes.</div>
<div>
<br /></div>
<div>
In the meantime VMware has also <a href="https://esxi-patches.v-front.de/ESXi-6.5.0.html" target="_blank">published the ESXi 6.5 GA bits to its Online Depot</a>, and that means it is very easy to create an ESXi 6.5 installation ISO or Offline bundle with my script. Just run it without any arguments for the ISO file (or only the <i>-ozip</i> switch for the Offline Bundle), and it will do its magic.</div>
<div>
<br /></div>
<div>
Have fun!</div>
<br />
<hr />
<div>
This post first appeared on the <a href="http://www.v-front.de/" target="_blank">VMware Front Experience Blog</a> and was written by <a href="http://www.v-front.de/p/about-v-front.html" target="_blank">Andreas Peetz</a>.
<a href="https://twitter.com/intent/follow?screen_name=VFrontDe" target="_blank"><img border="0" height="20" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5w5hDVtKqc-NqNixhNdCrCgzANGrL2wXqZvtNJhFe_6hrD2EuDS6H283IWP1L7qLTv3tNi_X1qqFxSOiUu0QIo0O6vq2ysR_q1mo9nve_ljcfkTKZdokSQ5kFA3PpzFE2YCazi-5Cbbcu/s1600/Twitter.png" width="20" /> Follow him on Twitter</a> to keep up to date with what he posts.
</div>
<hr />
<div class="related-posts-widget">
<!-- {
blog_url:'https://www.v-front.de'
,thumbs:0
,post_page_only:1
} -->
</div>
<hr />
<br />Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com12tag:blogger.com,1999:blog-6059874241017858476.post-59384968153550253482016-07-15T15:48:00.004+02:002016-12-09T09:45:00.352+01:00How to deploy Windows Nano Server (TP5) on vSphere<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhN1ujdBxqMgSSgorXXjuUXjZqLIfMo_QESDDz5xEzHC-0LUJz5wzbNsragHypPs8t9sZ29RR0i4Cl3FplkWPUH7WHMFZxLRfJH_F3NYLBLgq_o1_AnKdgMOjJOCnx137Goih70I-eS-AL_/s1600/NanoserverOnvSphere2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhN1ujdBxqMgSSgorXXjuUXjZqLIfMo_QESDDz5xEzHC-0LUJz5wzbNsragHypPs8t9sZ29RR0i4Cl3FplkWPUH7WHMFZxLRfJH_F3NYLBLgq_o1_AnKdgMOjJOCnx137Goih70I-eS-AL_/s1600/NanoserverOnvSphere2.png"></a></div>
With the upcoming release of Windows Server 2016 Microsoft will introduce a new edition of its flagship Operating System: Windows <i>Nano Server </i>is a super lightweight version of Windows Server that was <i>"built for the Cloud"</i>. When I first heard of it I immediately became curious, because it resembles VMware's ESXi in many ways: It is an embedded-like and headless system with a very small footprint and can be managed only remotely. It has limited use cases, but two of them are acting as a fully-featured Hyper-V virtualization host and as a container host.<br>
<br>
When looking for a good way to deploy Nano Server on vSphere I found some guides, but they were all referring to older Tech Preview (TP) versions of Server 2016 (things have changed in the current TP5) and/or did not result in optimal state-of-the art configurations. So I decided to write up my own guide, and here it is ...<br>
<br>
<a href="http://www.v-front.de/2016/07/how-to-deploy-windows-nano-server-tp5.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com8tag:blogger.com,1999:blog-6059874241017858476.post-25523923591231901322016-06-07T13:28:00.000+02:002016-06-15T13:54:11.902+02:00Active Directory issues with ESXi 6.0 Update 2 and an automated fix<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiwrVOla6ZMqTVynMDfjX7e-7G8_ZYc46rJUiPblFXq1pyiaI6x62ap0EwJ0VfGcXup-m2Dq-TSAGlP2iE1uIvqQituZkskQLLbp6U6thmQx6nDzGVjyVt09b0ewhpGfspr9jZohqspU1E7/s1600/LDAPFix-Head.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiwrVOla6ZMqTVynMDfjX7e-7G8_ZYc46rJUiPblFXq1pyiaI6x62ap0EwJ0VfGcXup-m2Dq-TSAGlP2iE1uIvqQituZkskQLLbp6U6thmQx6nDzGVjyVt09b0ewhpGfspr9jZohqspU1E7/s1600/LDAPFix-Head.png"></a></div>
Lately VMware published two new Knowledge Base (KB) articles that should alarm all people using Active Directory (AD) authentication with their ESXi 6.0 hosts:
<br>
<ul>
<li><a href="https://kb.vmware.com/kb/2145611" target="_blank">KB2145611: ESXi 6.0 hosts become unresponsive when joined to an Active Directory domain</a></li>
<li><a href="https://kb.vmware.com/kb/2145400" target="_blank">KB2145400: Actions performed against Active Directory may fail after upgrading to ESXi 6.0 Update 2</a></li>
</ul>
<div>
Let's have a closer look at these articles and make sure that you draw the right conclusions.<br>
<br></div>
<a href="http://www.v-front.de/2016/06/active-directory-issues-with-esxi-60.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com11tag:blogger.com,1999:blog-6059874241017858476.post-73350970332862573952016-04-26T15:27:00.003+02:002016-12-09T09:45:24.303+01:00Using haproxy as a PSC load balancer<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2XLVYO15f5JNZSYm8b4lhBvrV-jtG-Qbeh7MUs6v7K2iMA0PnBTvLuVoPz_QBARdhzsjKXpskcZsadVnzxZIenHjFXw4yH_7RE1fYXPIKFzwOEsIi7ygMnx9lA0v3W2g7AeIPywCNJEK6/s1600/haproxy-post-logo.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2XLVYO15f5JNZSYm8b4lhBvrV-jtG-Qbeh7MUs6v7K2iMA0PnBTvLuVoPz_QBARdhzsjKXpskcZsadVnzxZIenHjFXw4yH_7RE1fYXPIKFzwOEsIi7ygMnx9lA0v3W2g7AeIPywCNJEK6/s1600/haproxy-post-logo.png"></a></div>
<br>
When designing a vSphere 6.0 environment with multiple vCenter servers you will - in most cases - end up with the need to deploy external Platform Services Controllers (PSCs). If you are unsure what topology to choose then you should take a look at the <a href="http://blogs.vmware.com/vsphere/2016/04/platform-services-controller-topology-decision-tree.html" target="_blank">PSC Topology Decision Tree</a> that was recently published by VMware. It will guide you to the topology that suits your requirements best.<br>
<br>
Since the PSC hosts the critical Single-Sign-On (SSO) component a specific requirement is to make an external PSC highly available so that you are still able to log on to vCenter even if one PSC fails. Currently the only supported way to implement a seamless automatic failover from a failing PSC to another one is to put multiple PSCs (of the same SSO domain and site) behind a load balancer. The process of properly configuring the load balancer and the vCenter servers behind it is quite complex, so most people refrain from it and just deploy a secondary PSC to that they manually re-point the vCenter servers if the primary one should fail (as per <a href="https://kb.vmware.com/kb/2113917" target="_blank">KB2113917</a>). But this is a manual process (although it can of course be automated as William Lam explained in <a href="http://www.virtuallyghetto.com/2015/12/how-to-automatically-repoint-failover-vcsa-to-another-replicated-platform-services-controller-psc.html" target="_blank">this post</a>) and it takes a restart of all vCenter services during which vCenter will be unavailable.<br>
<br>
This is why I wanted to try out in the lab how complicated it really is to implement load balanced PSCs and how well they work. However, I did not have a <a href="https://kb.vmware.com/kb/2113315" target="_blank">supported load balancer</a> available in the lab - currently only <a href="https://kb.vmware.com/kb/2116281" target="_blank">Citrix Netscaler</a>, the <a href="https://kb.vmware.com/kb/2098006" target="_blank">F5 BIG-IP</a> and VMware's own <a href="https://blogs.vmware.com/consulting/2015/11/configuring-nsx-v-load-balancer-for-use-with-vsphere-platform-services-controller-psc-6-0.html" target="_blank">NSX-v</a> are officially supported for vSphere 6.0. All quite expensive options and no quick and easy deployments. So I decided to try my luck with <i>the</i> standard Open Source load balancer: <a href="http://www.haproxy.org/" target="_blank">haproxy</a>. It turned out that this works very well and can be implemented quite quickly. Here is how:<br>
<br>
<a href="http://www.v-front.de/2016/04/using-haproxy-as-psc-load-balancer.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com5tag:blogger.com,1999:blog-6059874241017858476.post-54640460547579510042016-03-30T16:06:00.000+02:002016-04-07T21:06:28.938+02:00Re-pointing vCenter Server 5.5: A Survival Guide to KB2033620<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYrFJNXlZJTz4e6RcvD_EDE6rURUpxqSkq_mZprR69XC4qgKwP4630DwdzC7rfaEbUzLz8g8hRmsc7I9ZuVo7LQX4afGE81G5oketSwioQ2l1Xt4kATpRaa7bJsHpaDIPa5n9kp2U9x5Gi/s1600/55detour60.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="170" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYrFJNXlZJTz4e6RcvD_EDE6rURUpxqSkq_mZprR69XC4qgKwP4630DwdzC7rfaEbUzLz8g8hRmsc7I9ZuVo7LQX4afGE81G5oketSwioQ2l1Xt4kATpRaa7bJsHpaDIPa5n9kp2U9x5Gi/s320/55detour60.png" width="320"></a></div>
<br>
vSphere 6.0 has been around for about a year now, but VMware's largest customers are usually one or even two versions behind. With the recent release of Update 2 it looks like the 6.0 version has gained the stability and maturity that enterprise customers are waiting for. This is the reason why I just did extensive testing of vSphere 5.5 to 6.0 upgrades in the lab.<br>
<br>
The main challenge of such an upgrade is to transform your vCenter Single Sign-On (SSO) setup into <a href="https://kb.vmware.com/kb/2108548" target="_blank">a topology that is fully supported and not deprecated</a>. With vSphere 6.0 the SSO component is now part of the new Platform Services Controller (PSC) role that can be separated from the remaining vCenter services. In fact VMware recommends doing this whenever you want to have two or more vCenter servers in the same SSO domain which is a prerequisite for the new Enhanced Linked mode. The separation of SSO was already possible with vSphere 5.5 (although only with the Windows version of vCenter, but not the VCSA 5.5), but I think most people wanted to keep it simple and installed all vCenter services on the same server. So if they have multiple vCenter servers installed in this way then they need to switch to one or more external PSCs now.<br>
<br>
There are many ways and orders in that you can - on the one hand - upgrade all components to 6.0 and - on the other hand - switch to an external PSC/SSO model. But only few of them are documented and supported by VMware. Their general recommendation is to transform into a supported topology first, and then do the upgrade of the PSCs and vCenter servers. <a href="https://kb.vmware.com/kb/2130433" target="_blank">KB2130433</a> e.g. describes how to upgrade/migrate two vCenter 5.5 servers with embedded SSO into the same SSO domain. This and other migration scenarios involve re-pointing your vCenter 5.5 server to a newly installed external SSO 5.5 instance.<br>
<br>
So when preparing the upgrade of a complex vSphere 5.5 environment to 6.0 you will sooner or later stumble over <a href="https://kb.vmware.com/kb/2033620" target="_blank">KB2033620</a> which describes how to do this re-pointing. Unfortunately this KB article and the tools that it refers you to are very poorly written and full of issues. Some of them are mentioned in the KB article itself with workarounds to follow, but a lot are not ... Here is a list of the most annoying issues with KB2033620 and how to fix them.<br>
<br>
<a href="http://www.v-front.de/2016/03/re-pointing-vcenter-server-55-survival.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com3tag:blogger.com,1999:blog-6059874241017858476.post-8964155115454333432016-03-16T09:35:00.001+01:002016-03-16T22:10:44.418+01:00An important heads-up for users of the Embedded Host Client!<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_9DJrSBcWwGbNIchag9M3ADFtmwrZWufWQyeUHCh5bTDlhn0oUMNzplpj3EqEeLk_0km-FZc8b8EEEOUnkxvkr9MUGsyy5JnTernTg21yXAg25hAYGNKeIBpoBpVJ9ilIQ3g2FbhyphenhyphenUNQr/s1600/esx-ui-headsup.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_9DJrSBcWwGbNIchag9M3ADFtmwrZWufWQyeUHCh5bTDlhn0oUMNzplpj3EqEeLk_0km-FZc8b8EEEOUnkxvkr9MUGsyy5JnTernTg21yXAg25hAYGNKeIBpoBpVJ9ilIQ3g2FbhyphenhyphenUNQr/s1600/esx-ui-headsup.png"></a></div>
My <a href="https://esxi-patches.v-front.de/" target="_blank">ESXi Patch Tracker</a> bot never sleeps, so when I woke up this morning it already <a href="https://twitter.com/ESXiPatches/status/709943103776497664" target="_blank">greeted me</a> with the message that VMware has released ESXi 6.0 Update 2 in the middle of the (European) night. As usual with Update releases vCenter was also updated.<br>
<br>
For the record here are the most important URLs for you:
<br>
<ul>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-vcenter-server-60u2-release-notes.html" target="_blank">vCenter 6.0 Update 2 Release Notes</a></li>
<li><a href="https://my.vmware.com/group/vmware/details?downloadGroup=VC60U2&productId=491&rPId=10348" target="_blank">vCenter 6.0 Update 2 Download</a></li>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u2-release-notes.html" target="_blank">ESXi 6.0 Update 2 Release Notes</a></li>
<li><a href="https://my.vmware.com/group/vmware/details?downloadGroup=ESXI60U2&productId=491&rPId=10348" target="_blank">ESXi 6.0 Update 2 Download</a></li>
</ul>
<div>
With this release there are some great news for the users of the Embedded Host Client, but also a caveat that you should be aware of.</div>
<br>
<a href="http://www.v-front.de/2016/03/an-important-heads-up-for-users-of.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com2tag:blogger.com,1999:blog-6059874241017858476.post-60025645861500247672016-02-20T17:40:00.000+01:002016-02-20T17:40:21.927+01:00The VIBMatrix has joined the ESXi Patch Tracker!<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjju0oPVUN0RuIAmfI61pcX4lfsNlT2jVhqOHDJxAalHaUjIlAO5WE_fe6gqPLW9LD7zyL_KKrm9OvTGM9rBkZobwRqtM9lDsrS2kq-R-1qH7BI3Clr_-zUDKFcYDUhYSZQjpI-YhiiIYbX/s1600/ESXiPatches-PimpedBy-DataTables.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="152" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjju0oPVUN0RuIAmfI61pcX4lfsNlT2jVhqOHDJxAalHaUjIlAO5WE_fe6gqPLW9LD7zyL_KKrm9OvTGM9rBkZobwRqtM9lDsrS2kq-R-1qH7BI3Clr_-zUDKFcYDUhYSZQjpI-YhiiIYbX/s400/ESXiPatches-PimpedBy-DataTables.png" width="400"></a></div>
My <a href="https://esxi-patches.v-front.de/" target="_blank">ESXi Patch Tracker</a> service is becoming more and more popular. Many of its users probably don't know that I had a very similar service long before: On the <i>VIBMatrix</i> pages I maintained tables of ESXi Patch releases with lists of all included VIB packages. The original reason why I created these tables more than three years ago was to prove that <a href="http://www.v-front.de/2012/11/are-esxi-5x-patches-cumulative.html" target="_blank">ESXi 5.x/6.x Patch bundles are cumulative</a>.<br>
<br>
Until today the VIBMatrix was a manually maintained Excel sheet that I imported to Google Docs whenever I added a new patch to it. These times are over: I'm happy to announce that the VIBMatrix is now also fully automated and integrated into the ESXi Patch Tracker service!<br>
<br>
<a href="http://www.v-front.de/2016/02/the-vibmatrix-has-joined-esxi-patch.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com2tag:blogger.com,1999:blog-6059874241017858476.post-11167638374405434402016-02-09T20:56:00.001+01:002016-02-09T20:56:04.117+01:00[Unsupported] Defeating the VCSA shell timeout<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8-Jd1Z0ZH4vpKad42cWh0isD-DHC_9iGoxuAT0lp_tZelr7-i5qQkkrVdJN07HW5DKg7n1reNnz8VJAY_WW70_n9OXvnbL3GoVzT2VoPulW3qJvN7T_iR6nnkt_K9_fySDHZ9jQBK-CaN/s1600/vcsa-shell-timeout.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8-Jd1Z0ZH4vpKad42cWh0isD-DHC_9iGoxuAT0lp_tZelr7-i5qQkkrVdJN07HW5DKg7n1reNnz8VJAY_WW70_n9OXvnbL3GoVzT2VoPulW3qJvN7T_iR6nnkt_K9_fySDHZ9jQBK-CaN/s1600/vcsa-shell-timeout.png"></a></div>
<br>
In my earlier post <a href="http://www.v-front.de/2015/03/vcsa-60-tricks-shell-access-password.html" target="_blank">vCSA 6.0 tricks: shell access, password expiration and certificate warnings</a> I showed how can set the VCSA shell timeout to an effectively indefinite value using the command<br>
<br>
<span style="background-color: white; color: #5e5e5e; font-family: "courier new" , "courier" , monospace; font-size: 14.85px; line-height: 20.79px;">shell.set --enabled true --timeout 2147483647</span><br>
<div>
<br></div>
at the appliance shell prompt. I was notified that in recent versions of the VCSA (probably since Update 1) this does no longer work. The maximum timeout that the command will accept is now 86400 seconds (= 1 day). The VAMI interface of the VCSA 6 (that was added in Update 1) also allows enabling the shell and setting the shell timeout, but there the GUI also limits the input to max. 1 day (resp. 1440 minutes).<br>
<div>
<br></div>
<div>
When I checked my own vCSA (that was originally installed with 6.0 GA, then upgraded to Update 1 and Update 1b) I found that my old large timeout setting was still in place and functioning. That means even in the latest build of the VCSA 6 it is still possible to set an arbitrarily large shell timeout, just not through the appliance shell or the VAMI. So how do you do this?<br>
<div>
<br>
</div></div><a href="http://www.v-front.de/2016/02/unsupported-defeating-vcsa-shell-timeout.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com2tag:blogger.com,1999:blog-6059874241017858476.post-74514825934007194942016-01-31T20:30:00.000+01:002016-01-31T20:30:38.989+01:00How to use the ESXi Patch Tracker to update ESXi<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1dA-lQwFf0xhsgvJHplD9Aqmra6P8SKmJPI1vmSnYCO9bFwbPhNla57PjzlUcltHErLaOOcTIxXuj3sNmK4SGvxY27WjeQSdqBEegN8_xzhAMH7QflXzp8dWQDxxthjllehbg2zdBq3Ne/s1600/PopupUpdateCmd.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1dA-lQwFf0xhsgvJHplD9Aqmra6P8SKmJPI1vmSnYCO9bFwbPhNla57PjzlUcltHErLaOOcTIxXuj3sNmK4SGvxY27WjeQSdqBEegN8_xzhAMH7QflXzp8dWQDxxthjllehbg2zdBq3Ne/s1600/PopupUpdateCmd.png"></a></div>
<br>
About a year ago I started my <a href="https://esxi-patches.v-front.de/" target="_blank">VMware ESXi Patch Tracker</a> service. This is a set of automatically generated web pages that show informations about all available ESXi patches. Its primary purpose is to give you an easy way to track the patch history and get alerted about new patches once they are released. You can subscribe to it by RSS feed, E-mail and Twitter.<br>
<br>
Recently I have added new functionality to the Patch Tracker that enables you to update your ESXi hosts in a very convenient way. Here is how:<br>
<br>
<a href="http://www.v-front.de/2016/01/how-to-use-esxi-patch-tracker-to-update.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com15tag:blogger.com,1999:blog-6059874241017858476.post-14135581003145341132015-12-30T13:51:00.002+01:002016-01-08T14:54:20.963+01:00Why upgrading from ESXi 5.5 Update 3b to 6.0 fails<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivMglz2KL0Vsm7Jbuwdfli69HxrLxSnhQAfsNsqS-8iZy-0dJVZkwsJIVA0AIB1-EjRwcKrCw8pnVTFkfNQjCNqefd63nLtuIhL0cFJjUkBr3wDQU1cEY260cg5YIo8p_40ZYYxi7sJEVx/s1600/Upgrade+From+ESXi+55U3b+to+6.0+Error.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="142" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivMglz2KL0Vsm7Jbuwdfli69HxrLxSnhQAfsNsqS-8iZy-0dJVZkwsJIVA0AIB1-EjRwcKrCw8pnVTFkfNQjCNqefd63nLtuIhL0cFJjUkBr3wDQU1cEY260cg5YIo8p_40ZYYxi7sJEVx/s400/Upgrade+From+ESXi+55U3b+to+6.0+Error.png" width="400"></a></div>
<br>
As of now users who are running ESXi 5.5 with the latest patch level <a href="https://esxi-patches.v-front.de/ESXi-5.5.0.html#2015-12-08" target="_blank">Update 3b</a> will find it difficult to upgrade to ESXi 6.0. Trying that with VMware Update Manager (VUM) or the <i>esxcli software profile update</i> method fails with error messages. <i>esxcli </i>throws this error:<br>
<br>
<span style="font-family: Courier New, Courier, monospace;">[DependencyError]</span><br>
<span style="font-family: Courier New, Courier, monospace;">VIB VMware_bootbank_xhci-xhci_1.0-3vmw.550.3.78.3223702 requires com.vmware.usb-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.</span><br>
<div>
<br></div>
<div>
and the VUM remediation process fails with the error event<br>
<br>
<i>The upgrade contains conflicting VIBs. Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again.</i><br>
<br>
The issue is mentioned in an updated version of the <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-esxi-55u3b-release-notes.html#installissues" target="_blank">VMware ESXi 5.5 Update 3b Release Notes</a>, with a refreshingly short list of possible workarounds: <i>None.</i></div>
<div>
<br></div>
<div>
What are our options in this situation, are there really <i>no</i> workarounds?</div>
<br>
<a href="http://www.v-front.de/2015/12/why-upgrading-from-esxi-55-update-3b-to.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com4tag:blogger.com,1999:blog-6059874241017858476.post-14408642296499637892015-12-20T19:15:00.000+01:002015-12-20T19:15:39.967+01:00How to build a customized ESXi installation image for your whitebox server<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_GCFW6thNiq6peWLEiptZiWswfW23oy1SZXHEwLTtFTCfscJvQYgR4F8d7wXxW1xcADf9r1oAueOZ3VO-PzdOMJ8XXBrySpLE7OKfuBbLTRP-1_G3dr5U4Flw3CZmhSn4lWCa8o1tao_P/s1600/LittleKittenDies.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_GCFW6thNiq6peWLEiptZiWswfW23oy1SZXHEwLTtFTCfscJvQYgR4F8d7wXxW1xcADf9r1oAueOZ3VO-PzdOMJ8XXBrySpLE7OKfuBbLTRP-1_G3dr5U4Flw3CZmhSn4lWCa8o1tao_P/s320/LittleKittenDies.jpg" width="320"></a></div>
<br>
My <i>ESXi-Customizer</i> tool has come a long way... Originally built in 2011 it was a great tool for building customized VMware ESXi installation images, it was downloaded over 200k times since then and helped a lot of people who had one quest: getting ESXi installed and running on their whitebox (unsupported) hardware. This year it was even mentioned in a <a href="http://kb.vmware.com/kb/2110557" target="_blank">VMware KB article</a> ... However, please do NOT use it anymore! Because ...<br>
<br>
Since quite a while there is a much better way to build customized ESXi images, and that is my <a href="http://esxi-customizer-ps.v-front.de/" target="_blank">ESXi-Customizer-PS</a> PowerCLI script. I'm writing this post not only to explain how easy it is to create a customized ESXi installation image for your whitebox server with this script, but also to convince the last nonbelievers that it works much better than my legacy ESXi-Customizer tool.<br>
<br>
<a href="http://www.v-front.de/2015/12/how-to-build-customized-esxi.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com3tag:blogger.com,1999:blog-6059874241017858476.post-44899880467492528982015-11-10T13:59:00.001+01:002015-11-10T13:59:45.306+01:00How to embed the VMware Tools version 10.0 into ESXi<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-jWeWtAXHruRQZ4iL94bNdVjIXaMORiNkK_91ZUYHrHR8HR0_usFiKrPenixlQfsTIF3uRcyLzzRqHRzZ2G1ir1_gL8CO79bVZtnO9lHAtonqmPe-K6qLtbwrsLJVldXRGDGFlJW0yc6h/s1600/Embed-VMT10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="108" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-jWeWtAXHruRQZ4iL94bNdVjIXaMORiNkK_91ZUYHrHR8HR0_usFiKrPenixlQfsTIF3uRcyLzzRqHRzZ2G1ir1_gL8CO79bVZtnO9lHAtonqmPe-K6qLtbwrsLJVldXRGDGFlJW0yc6h/s400/Embed-VMT10.png" width="400"></a></div>
<br>
Recently I ranted about the current situation with VMware Tools, and my blog post <a href="http://www.v-front.de/2015/10/the-great-vmware-tools-dilemma.html" target="_blank">The great VMware Tools dilemma</a> caught some attention and got a lot of agreement. The good news is that VMware is listening to its customers and trying to improve things.<br>
<br>
In a <a href="https://blogs.vmware.com/vsphere/2015/11/updating-to-vmware-tools-10-must-read.html" target="_blank">new blog post</a> VMware's Brian Graf elaborates on the recommended solution to use a shared productLocker location for VMware Tools with your ESXi hosts. I complained in my post that it is not easily possible to populate such a shared location with the new <a href="https://my.vmware.com/web/vmware/details?downloadGroup=VMTOOLS1000&productId=491" target="_blank">"standalone" Tools version 10.0</a>. And this has been improved now:
<br>
<ul>
<li>The VMware Tools version 10.0 download now includes all the files that you need to upload to the shared productLocker location, and</li>
<li>Brian <a href="http://www.vtagion.com/automate-vmware-tools-shared-product-locker-configuration/" target="_blank">has shared some scripts on his own blog</a> to automate the process of creating a shared productLocker, uploading the Tools to it and configuring the hosts to use it.</li>
</ul>
<div>
Great news!</div>
<br>
But what if you only have one or few ESXi hosts and want to avoid the overhead of creating a shared productLocker? Wouldn't it be good if we could just update the Tools that are embedded into ESXi to the new version 10.0?<br>
<br>
To say it short: <i>Yes, we can!</i> The embedded Tools is just a VIB package (called <i>tools-light</i>) that can be updated. Unfortunately, VMware refuses (so far) to make VMware Tools 10.0 available as a VIB file, but we can build this ourselves! Here is how ...<br>
<br>
<a href="http://www.v-front.de/2015/11/how-to-embed-vmware-tools-version-100.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com14tag:blogger.com,1999:blog-6059874241017858476.post-30213236534154874452015-11-09T13:35:00.000+01:002015-11-09T14:44:39.779+01:00[Update] ESXi Community Packaging Tools updated to version 2.3<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg2NtiHwsX3JBlx5FoWz8nOaCfPotU7dkhilp0sumjrHcqRRLFC19IEiVYH05YJ08aOikZHrPLtEAp3XWmbY-M3gWnuP7ZdXxgO3F2N-qhQ2B7BfezIDdGU6_NP9h8AI_dYrMRJMyyUOlgU/s1600/ESXi-CPT-23-Notifications.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg2NtiHwsX3JBlx5FoWz8nOaCfPotU7dkhilp0sumjrHcqRRLFC19IEiVYH05YJ08aOikZHrPLtEAp3XWmbY-M3gWnuP7ZdXxgO3F2N-qhQ2B7BfezIDdGU6_NP9h8AI_dYrMRJMyyUOlgU/s1600/ESXi-CPT-23-Notifications.png"></a></div>
<a href="http://esxi-cpt.v-front.de/" target="_blank"><br></a>
After almost two years I decided to touch my <a href="http://esxi-cpt.v-front.de/" target="_blank">ESXi Community Packaging Tools</a> again and give them an important update. These tools consists of two scripts that enable Community Developers to create software packages for ESXi 5.x/6.x in the VMware proprietary formats VIB (VMware Installation Bundle) and ZIP (VMware Offline Bundle).<br>
<br>
Read on to learn what's new and to not miss an exciting sneak peak of what's to come next.<br>
<br>
<a href="http://www.v-front.de/2015/11/update-esxi-community-packaging-tools.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com1tag:blogger.com,1999:blog-6059874241017858476.post-58235264897776733982015-10-08T21:21:00.000+02:002015-10-08T22:34:43.078+02:00VMware introduces support for Intel i219 (Jacksonville) NICs in ESXi<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2UbNLaqZJExB1fF7j6PbQsoMcIyiSfBT1GINfH-_9cpTjB-v6MFTGZzwEQ7Wwj8APy27A3Hs_cWQt7Wzu79amaLyZ1P9Ngz6XmE1A2Bp1oD7S8YhZs4WgRvPF2E31BNN_Pl_-yf4VzUop/s1600/Jacksonville-trans.gif" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2UbNLaqZJExB1fF7j6PbQsoMcIyiSfBT1GINfH-_9cpTjB-v6MFTGZzwEQ7Wwj8APy27A3Hs_cWQt7Wzu79amaLyZ1P9Ngz6XmE1A2Bp1oD7S8YhZs4WgRvPF2E31BNN_Pl_-yf4VzUop/s320/Jacksonville-trans.gif" width="214"></a></div>
<br>
In this year's summer Intel introduced their new Skylake platform. These motherboards are based on the Z170 chipset and often include onboard Intel i219(-V or -LM) Gigabit Ethernet adapters. VMware ESXi did not properly support the Skylake chipset from the beginning, but it looks like this changed with the release of ESXi 6.0 Update 1 and 5.5 Update 3. I do not own such a system myself, but I have heard reports of users who were able to successfully install ESXi 6.0 U1 on such a system.<br>
<br>
However, <a href="https://esxi-patches.v-front.de/ESXi-6.0.0.html#2015-09-10" target="_blank">ESXi 6.0 Update 1</a> does not (yet) include a driver that supports the i219 NICs. But <a href="https://esxi-patches.v-front.de/ESXi-5.5.0.html#2015-09-16" target="_blank">ESXi 5.5 Update 3</a> (that was published only few days later) comes with an updated e1000e driver (version 3.2.2.1) that supports these NICs. Here is how you can make best use of it, even if you are already using ESXi 6.0.<br>
<br>
<a href="http://www.v-front.de/2015/10/vmware-introduces-support-for-intel.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com9tag:blogger.com,1999:blog-6059874241017858476.post-84558387427380451332015-10-05T14:09:00.000+02:002015-10-05T14:09:54.963+02:00The great VMware Tools dilemma<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3JqGYZz-a3Z1gT-SqPt-jdClbxqKfLPgH-_5ZLU4QSvXo3XraqJyLMLMxLpFymyWT8eolymtgr_ejzzI0T-psnI2bCOO12iRepUXsk0Wm_0epyKUrgBwgEftvR2MNOxf6Kam_KkHSf0cj/s1600/VMTools-Status2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3JqGYZz-a3Z1gT-SqPt-jdClbxqKfLPgH-_5ZLU4QSvXo3XraqJyLMLMxLpFymyWT8eolymtgr_ejzzI0T-psnI2bCOO12iRepUXsk0Wm_0epyKUrgBwgEftvR2MNOxf6Kam_KkHSf0cj/s1600/VMTools-Status2.png"></a></div>
<br>
Recently VMware made VMware Tools version 10.0.0 available as a standalone download. This version is now <a href="https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/6_0#drivers_tools" target="_blank">an official downloadable component of vSphere 6.0</a> with its own <a href="https://pubs.vmware.com/Release_Notes/en/vmwaretools/1000/vmware-tools-1000-release-notes.html" target="_blank">Release Notes document</a> and a <a href="https://my.vmware.com/web/vmware/details?downloadGroup=VMTOOLS1000&productId=491" target="_blank">download page in MyVMware</a>.<br>
<br>
In the <a href="https://blogs.vmware.com/vsphere/2015/09/vmware-tools-10-0-0-released.html" target="_blank">announcement blog post</a> VMware's <a href="https://twitter.com/vBrianGraf" target="_blank">Brian Graf</a> writes:<br>
<blockquote class="tr_bq">
Good news. We have decided that there isn’t any specific reason that VMware Tools builds should be tied to vSphere releases/ESXi builds. Rather, when our engineering teams are ready with key features/updates, we should have the ability to get those benefits out to our customers as quickly as possible.</blockquote>
This release was announced and perceived as a great achievement, but - except for this good news that Brian shared with us - I cannot follow any of the other excited statements that were made about it. It's time to debunk some myths, and it's time to admit that the whole VMware Tools story is still a great mess!<br>
<br>
<a href="http://www.v-front.de/2015/10/the-great-vmware-tools-dilemma.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com16tag:blogger.com,1999:blog-6059874241017858476.post-10475656123578329662015-08-24T15:18:00.002+02:002015-08-24T15:18:23.138+02:00Shut up, Windows 10! Here is a free must-have tool to protect your privacy.<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO6a6DJoC6os2kzgAIHPYsNCB3CB-8xrwz-6aYtRVJY8feIbZBDDpdKH4O0vGaYnWbAUEuKtbZL1_DNipZqgbRtJDxSb5O2CLteWUrv686TpK-m2vGv8aQnlnn8HETPs1pj_jubku69fhr/s1600/Win10Express1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="246" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO6a6DJoC6os2kzgAIHPYsNCB3CB-8xrwz-6aYtRVJY8feIbZBDDpdKH4O0vGaYnWbAUEuKtbZL1_DNipZqgbRtJDxSb5O2CLteWUrv686TpK-m2vGv8aQnlnn8HETPs1pj_jubku69fhr/s320/Win10Express1.png" width="320"></a></div>
If you install Windows 10 with the default "Express Settings" then it will collect a plethora of data from you and send it to Microsoft and "trusted partners": Not only whatever you ask Cortana (Microsoft's version of Apple's Siri or Google Now), but also what you type or write by hand, where you are, what networks you connect to, what you search for and more...<br>
<br>
Sure, they are not alone with this: Google does it with Android, Apple with iOS devices, and - if you ask them - they all collect the data only to optimize the personalized services that they offer you <i>for free</i>. Really for free? No, you pay with your data ... However, more and more people are concerned about data privacy and want to have a choice about what data they disclose. Recently I stumbled over a great tool that helps those people when using Windows 10.<br>
<br>
<a href="http://www.v-front.de/2015/08/shut-up-windows-10-here-is-free-must.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com0tag:blogger.com,1999:blog-6059874241017858476.post-64429313569910708682015-08-21T14:51:00.000+02:002015-08-21T14:56:30.507+02:00A fix for Intel i211 and i350 adapters not being detected by ESXi<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3cZKzu9NlGz82nJNjvhR6SSqIWkpW9eS-nCyBHZL4b41K97s96MtL1XnK3Zyl8RZr1tqJij3ZObdMSXssUC0uI-GwtMmF0CzZcDmkhnAWni5RYckf0JdlTghIIrH7BftlthmYxz1T7zpC/s1600/Fitlet-2a.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3cZKzu9NlGz82nJNjvhR6SSqIWkpW9eS-nCyBHZL4b41K97s96MtL1XnK3Zyl8RZr1tqJij3ZObdMSXssUC0uI-GwtMmF0CzZcDmkhnAWni5RYckf0JdlTghIIrH7BftlthmYxz1T7zpC/s1600/Fitlet-2a.png"></a></div>
<br>
Recently two readers of my blog asked me for help with a strange issue that they encountered when trying to install ESXi on their whitebox hardware. The one was a <a href="http://www.shuttle.eu/products/slim/" target="_blank">Shuttle DS57 barebone</a>, and the other one was a <a href="http://www.fit-pc.com/web/products/fitlet/fitlet-x/" target="_blank">Compulab Fitlet-X</a> (an interesting tiny fanless industrial PC with 4 onboard NICs). Both have Intel i211 Gigabit Ethernet adapters that were not detected by ESXi, although they are officially supported by the ESXi 6.0 built-in igb driver (see <a href="http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=37601" target="_blank">VMware HCL entry</a>).<br>
<br>
Looking for a solution I found that this seems to be a common issue. Multiple reports found in the VMware Communities and other forums convinced me that resolving the issue would help a lot of people. Time for some late night troubleshooting ...<br>
<br>
<a href="http://www.v-front.de/2015/08/a-fix-for-intel-i211-and-i350-adapters.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com18tag:blogger.com,1999:blog-6059874241017858476.post-65748123572985065212015-08-04T21:53:00.000+02:002015-08-04T21:53:20.686+02:00Troubleshooting VM network performance using vsish<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgHeiKCmTU2H2jBQkrTtdWl3Diw2KLCQY08RJIBtmDYy7hFNk_bySmH83fXATXK6yCIhHE_6tJpo1NducBJkonP4nhWNqtv3TIGYNlxJ1W3nA7FafELCGDe56sxQNbOud2dwzH5FttU6jpk/s1600/ISeeDroppedPackets.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgHeiKCmTU2H2jBQkrTtdWl3Diw2KLCQY08RJIBtmDYy7hFNk_bySmH83fXATXK6yCIhHE_6tJpo1NducBJkonP4nhWNqtv3TIGYNlxJ1W3nA7FafELCGDe56sxQNbOud2dwzH5FttU6jpk/s200/ISeeDroppedPackets.jpg" width="200"></a></div>
<br>
Long time, no post ... I'm currently busy with several support requests that I opened with VMware. These keep me busy but they are also good opportunities to learn something new.<br>
<br>
One of the cases involves troubleshooting the network performance of Lync 2013 servers running on top of vSphere. It turned out that the VMkernel system information shell (better known as <i>vsish</i>) is a great tool for this.<br>
<br>
<a href="http://www.v-front.de/2015/08/troubleshooting-vm-network-performance.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com2tag:blogger.com,1999:blog-6059874241017858476.post-64287001467006725122015-06-11T14:23:00.000+02:002015-06-11T14:23:52.281+02:00Heads up: The upcoming Leap Second adjustment may affect your IT infrastructure!<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFBk6b6hdeattVtmvN7ZC6SMGRmXMrzIIBOAdUjKkWgGdvLv6FVtgt9JeIDwBefdBcAu2xi4n0gsvXjOM1avB0CSu3jGag8WwUPHAimVN5bm-EjLQ6KBEMGYzZpOH4saXGyEORhzjerMm2/s1600/keep-calm-and-be-prepared-for-the-leap-second.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFBk6b6hdeattVtmvN7ZC6SMGRmXMrzIIBOAdUjKkWgGdvLv6FVtgt9JeIDwBefdBcAu2xi4n0gsvXjOM1avB0CSu3jGag8WwUPHAimVN5bm-EjLQ6KBEMGYzZpOH4saXGyEORhzjerMm2/s200/keep-calm-and-be-prepared-for-the-leap-second.png" width="171"></a></div>
<br>
Okay, probably everyone is aware of the upcoming leap second time adjustment on June 30th, 0:00 UTC. I won't explain the story behind it although it's a very interesting topic, but others have done this already. A good starting point is the Wikipedia <a href="http://en.wikipedia.org/wiki/Leap_second" target="_blank">Leap Second</a> article.<br>
<br>
You might wonder: Okay, this is an anomaly that is confusing, but it's only <i>one second</i>, and modern IT systems should not really stumble over this, right? I was of the same opinion until recently, but the nearer the time comes the more IT vendors alert their customers of leap second related issues in their products, and you might be surprised to hear that very critical parts of your infrastructure can fail on June 30th if you do not patch them before!<br>
<br>
<a href="http://www.v-front.de/2015/06/heads-up-upcoming-leap-second.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com0tag:blogger.com,1999:blog-6059874241017858476.post-56291496582757789042015-05-27T16:43:00.000+02:002015-05-27T16:43:58.547+02:00Filtering logs in ESXi 6.0 - A practical example<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg633eq5ZYD8IJL2UsnKKR4ojp7JnVwr9Jw8-X7RBO4YCv5jZnRdu056MypvNX0nar9A058tlviN0GduFvaTWKCSMimTWy-y2yt9aFfbQXVdMl9u22wPUD7va0dz1lBVwVzXEAfhczsR2DK/s1600/FilterLogs.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg633eq5ZYD8IJL2UsnKKR4ojp7JnVwr9Jw8-X7RBO4YCv5jZnRdu056MypvNX0nar9A058tlviN0GduFvaTWKCSMimTWy-y2yt9aFfbQXVdMl9u22wPUD7va0dz1lBVwVzXEAfhczsR2DK/s1600/FilterLogs.png"></a></div>
<br>
Recently I rented a new server with an LSI MegaRAID SAS 9260-4i controller and - of course - installed VMware ESXi 6.0 on it. I will soon migrate my "production workloads" (the <a href="https://vibsdepot.v-front.de/" target="_blank">V-Front Online Depot</a>, the <a href="https://esxi-patches.v-front.de/" target="_blank">ESXi Patch Tracker</a> site and my Zimbra E-Mail server) onto this box to improve their availability. A disk failure is one of the most likely disaster scenarios, so a hardware RAID controller with two mirrored disks will certainly help.<br>
<br>
After I had the host installed and configured I did a routine check of the log files and found a lot of SCSI errors like these in <i>/var/log/vmkernel.log</i>:
<br>
<pre class="brush:text;gutter:false;">cpu1:34460)NMP: nmp_ThrottleLogForDevice:3178: Cmd 0x1a (0x439d80668b00, 0) to dev "naa.600605b0058b25f01c995a4f0b03da18" on path "vmhba1:C2:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE
cpu1:32779)ScsiDeviceIO: 2646: Cmd(0x439d80716d00) 0x4d, CmdSN 0x1 from world 34425 to dev "naa.600605b0058b25f01c995a4f0b03da18" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.</pre>
<div>
These errors were referring to the RAID 1 disk, and first I was worried about them - according to <a href="http://kb.vmware.com/kb/289902" target="_blank">KB289902</a> the <i>D:0x2</i> translates to "Device: Check condition" and the sense data codes <i>0x5 0x24 0x0</i> and <i>0x5 0x20 0x0</i> mean "Illegal request", "Invalid Field in CDB", resp. "Invalid command operation code". I double checked that the RAID controller <a href="http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=12383" target="_blank">is on the VMware HCL</a>, I searched the Internet for these errors, found few peoples' posts describing this issue, but no solution. I even updated the firmware of the controller, all to no avail ... and then, finally, I stumbled over <a href="http://kb.vmware.com/kb/1031221" target="_blank">KB1031221</a> which - basically - describes that these errors are "normal" and "can be safely ignored".</div>
<div>
<br></div>
<div>
Well, that calmed me down... But I'm a log purist: I wanted to get rid of these false error messages in vmkernel.log!</div>
<br>
<a href="http://www.v-front.de/2015/05/filtering-logs-in-esxi-60-practical.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com4tag:blogger.com,1999:blog-6059874241017858476.post-89770432299687913672015-05-20T21:18:00.001+02:002015-05-20T21:21:38.416+02:00What's new in the V-Front Online Depot - or - how to install ESXi on an HP Pavilion 17 notebook<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5Ehn8RPS8n8J-JIkkbCFpxlb9k0N7O2nmT6YMfOLgGdzBTQ5prPVnp-ZhAfNaEHuhj2lkcl01y4klaG3fkALT_Operxe-RUdLCDSaVbjadnstuRm2Cb2ul0iuPun4IQ_oSENGZet05kD-/s1600/ESXi_On_HPPavilion17.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="92" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5Ehn8RPS8n8J-JIkkbCFpxlb9k0N7O2nmT6YMfOLgGdzBTQ5prPVnp-ZhAfNaEHuhj2lkcl01y4klaG3fkALT_Operxe-RUdLCDSaVbjadnstuRm2Cb2ul0iuPun4IQ_oSENGZet05kD-/s400/ESXi_On_HPPavilion17.png" width="400"></a></div>
<br>
Recently I added some new NIC drivers to the <a href="https://vibsdepot.v-front.de/" target="_blank">V-Front Online Depot</a>. Well, they are not really new, but were created back in 2011/12 by a Japanese guy who goes by the nickname <i>ichi</i>. He was actively participating in Dave Mishchenko's <a href="http://www.vm-help.com/forum/" target="_blank">vm-help.com forums</a> and posted the drivers there.<br>
<br>
Although I was aware of them since then I did not add them to the Depot before - I thought that no one would really need them these days, because the NIC models that they support are pretty old and rarely used today. I was wrong, at least in one case, because I needed one of these drivers myself to install ESXi on a brand new HP Pavilion 17 notebook that I just purchased ...<br>
<br>
<a href="http://www.v-front.de/2015/05/whats-new-in-v-front-online-depot-or.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com4tag:blogger.com,1999:blog-6059874241017858476.post-14707340729218387232015-05-11T14:44:00.000+02:002015-05-11T14:44:53.198+02:00CPU Microcode Updates revisited: What's new in ESXi 6.0?<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHtguPRBiwto3agtNvofZeuXbyw0DHk1UJzyt0k5SBKbPSbmJHNFXt8N_Ph9FDngZhHZxZs2vImCZOeEnG2Fj5T6morDQV80zi2yw-VaQg_cEChDsNp6xgrMcjlXXSVjuP8yzfDT8w_-lY/s1600/A80501-60-150x120.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHtguPRBiwto3agtNvofZeuXbyw0DHk1UJzyt0k5SBKbPSbmJHNFXt8N_Ph9FDngZhHZxZs2vImCZOeEnG2Fj5T6morDQV80zi2yw-VaQg_cEChDsNp6xgrMcjlXXSVjuP8yzfDT8w_-lY/s1600/A80501-60-150x120.png"></a></div>
<br>
Almost two years ago I wrote an <a href="http://www.v-front.de/2013/07/faq-cpu-microcode-updates-and-vmware.html" target="_blank">FAQ post on CPU Microcode updates with ESXi 5.x</a>. This still gets a lot of hits, but - although the general information about Microcodes still applies - the ESXi related information needs an update, because things have changed with ESXi 6.0.<br>
<br>
So what's new and different now?<br>
<br>
<a href="http://www.v-front.de/2015/05/cpu-microcode-updates-revisited-whats.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com3tag:blogger.com,1999:blog-6059874241017858476.post-90117876656240736112015-04-25T18:26:00.001+02:002015-04-25T18:26:23.274+02:00[Release] ESXi-Customizer-PS 2.4 - The ESXi image customization script<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyiuoNcZuMGmTwzN8ilCnyNroBEp0s41WX1r3yDTciGagdcRfTGeGGL721j0xLbuwnma2_E_UihR5UksvJSclM5j1Mj9xoJZ20tHaH_Z46JAbOa6noS1lbmRDiEnt8DXTOFynFq6jMTggp/s1600/ESXi-Customizer-PS-24.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyiuoNcZuMGmTwzN8ilCnyNroBEp0s41WX1r3yDTciGagdcRfTGeGGL721j0xLbuwnma2_E_UihR5UksvJSclM5j1Mj9xoJZ20tHaH_Z46JAbOa6noS1lbmRDiEnt8DXTOFynFq6jMTggp/s1600/ESXi-Customizer-PS-24.png"></a></div>
<br>
I have just released version 2.4 of my <a href="http://esxi-customizer-ps.v-front.de/" target="_blank">ESXi-Customizer-PS</a> script - a PowerCLI script to create customized ESXi installation images and the <a href="http://www.v-front.de/2014/01/a-new-version-of-esxi-customizer-and.html" target="_blank">successor of my legacy ESXi-Customizer tool</a>.<br>
<br>
This is a minor, but important update, because it fixes an annoyance that users of the latest PowerCLI version 6.0 ran into.<br>
<br>
<a href="http://www.v-front.de/2015/04/release-esxi-customizer-ps-24-esxi.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com8tag:blogger.com,1999:blog-6059874241017858476.post-23561747030230703252015-04-17T21:54:00.002+02:002015-04-17T21:54:59.284+02:00ESXi 6.0 hits the VMware Online Depot - What does that mean?<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8zxzoR9ZFStBlrf9Mt9dVxnezkdSOMIJR5mB09vEgP5ZjlVbaC8OmpbK1Rm9cmEfzTL4O_4vEKTqHcotQ4tb-rgUHNtfB6pa_I0ofoioKxL29SzYX6jZVQ4p4X1AVDi_75810BhcGCEy-/s1600/60inVOD.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8zxzoR9ZFStBlrf9Mt9dVxnezkdSOMIJR5mB09vEgP5ZjlVbaC8OmpbK1Rm9cmEfzTL4O_4vEKTqHcotQ4tb-rgUHNtfB6pa_I0ofoioKxL29SzYX6jZVQ4p4X1AVDi_75810BhcGCEy-/s1600/60inVOD.png"></a></div>
<br>
On April 9th VMware published the first ESXi 6.0 patch (see the <a href="https://esxi-patches.v-front.de/ESXi-6.0.0.html#2015-04-09" target="_blank">ESXi Patch Tracker</a> and <a href="http://kb.vmware.com/kb/2111976" target="_blank">KB2111976</a>), and at the same time the Imageprofiles of both this patch and the ESXi 6.0 GA release appeared in the VMware Online Depot. Unfortunately they did not also upload all the ESXi 6.0 VIB packages at that time, but only the one that was updated with the first patch. Today, they finally made up for this, and I cannot only publish this article again, but now the instructions and examples in it will really work :-)<br>
<br>
What does it mean to have ESXi 6.0 available in the VMware Online Depot? It makes it a lot easier to upgrade an ESXi host and to build customized ESXi 6.0 installation images, especially for free license users who do not have easy access to the GA Offline bundle. I wrote about this already in my <a href="http://www.v-front.de/2015/03/vsphere-6-is-ga-ultimate-guide-to.html" target="_blank">Ultimate guide to upgrade your white box</a>, and this is the promised update to it.<br>
<br>
So what are the new possibilities now?<br>
<br>
<a href="http://www.v-front.de/2015/04/esxi-60-hits-vmware-online-depot-what.html#more">Read more »</a>Andreas Peetzhttp://www.blogger.com/profile/12918778845056237847noreply@blogger.com10