<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Vsphere on sigtar.com</title>
		<link>https://sigtar.com/tags/vsphere/</link>
		<description>Recent content in Vsphere on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Mon, 18 Feb 2013 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/vsphere/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>vmware - powercli enable remote scripts</title>
				<link>https://sigtar.com/2013/02/18/vmware-powercli-enable-remote-scripts/</link>
				<pubDate>Mon, 18 Feb 2013 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2013/02/18/vmware-powercli-enable-remote-scripts/</guid>
				<description>&lt;p&gt;Neccesary commands to get vmware vsphere power cli scripts runnign in power cli;&lt;/p&gt;&#xA;&lt;p&gt;(post installation of vsphere power cli extensions)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Set-ExecutionPolicy RemoteSigned&lt;/strong&gt; &lt;strong&gt;Set-PowerCLIConfiguration -InvalidCertificateAction &amp;ldquo;Ignore&amp;rdquo; -Confirm:$false&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://blogs.vmware.com/vipowershell/2011/06/back-to-basics-part-1-installing-powercli.html&#34;&gt;http://blogs.vmware.com/vipowershell/2011/06/back-to-basics-part-1-installing-powercli.html&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Jumbo Frames on your vSphere ESXi box</title>
				<link>https://sigtar.com/2010/03/02/jumbo-frames-on-your-vsphere-esxi-box/</link>
				<pubDate>Tue, 02 Mar 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/03/02/jumbo-frames-on-your-vsphere-esxi-box/</guid>
				<description>&lt;p&gt;Continuing on from this /2010/02/04/vsphere-and-multipathing-iscsi/&lt;/p&gt;&#xA;&lt;p&gt;you may want to implement jumbo frames to your iSCSI backend&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Enable jumbo frames on your iSCSI target and switches then complete the following on the ESXi hosts (iSCSI initiators)&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;This to list your current switch details and port group names&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;esxcfg-vswitch -l&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;The following to allow jumbo frames onto your vswtich (insert your vSwich in following)&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;esxcfg-vswtich -m 9000 vSwitch0&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Then create your kernel port groups that you want to use for iscsi, my commands looked like this&amp;hellip; (repeat for each iscsi kernel port you have) &amp;ndash; note : DO NOT ADD ANY VMKERNEL(s) from the GUI, instead use the steps below&lt;/p&gt;</description>
			</item>
			<item>
				<title>vSphere and Multipathing iSCSI</title>
				<link>https://sigtar.com/2010/02/04/vsphere-and-multipathing-iscsi/</link>
				<pubDate>Thu, 04 Feb 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/02/04/vsphere-and-multipathing-iscsi/</guid>
				<description>&lt;p&gt;This is just a quick reference to create a multiplathing iSCSI setup&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Create two virtual kernel switches, one called &amp;ldquo;iSCSI-1&amp;rdquo; and the other called &amp;ldquo;iSCSI-2&amp;rdquo; (and so on if you have more nics)&lt;/p&gt;&#xA;&lt;p&gt;Then per kernel portgroup ensure that only one of the nics is active. For the &amp;ldquo;iSCSI-1&amp;rdquo; portgroup configure it to override the virtual switch settings and move nic 0 to active and nic 1 to &lt;strong&gt;unused&lt;/strong&gt;. For the &amp;ldquo;iSCSI-2&amp;rdquo; portgroup configure it to override the virtual switch settings and move nic 1 to active and nic 0 to &lt;strong&gt;unused&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>vSphere - ctrl-alt-del greyed out</title>
				<link>https://sigtar.com/2009/09/30/vsphere-ctrl-alt-del-greyed-out/</link>
				<pubDate>Wed, 30 Sep 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/09/30/vsphere-ctrl-alt-del-greyed-out/</guid>
				<description>&lt;p&gt;This bug has hit me. Looks like users with roles like vm user / power user cannot send &amp;ldquo;ctrl-alt-del&amp;rdquo; via the console even though they have the correct permissions. Our users cannot use ctrl-alt-ins as they are connected via RDP to a machine that has the console installed.&lt;/p&gt;&#xA;&lt;p&gt;Found this : &lt;a href=&#34;http://communities.vmware.com/thread/220683;jsessionid=480C8A2C9B9EACA9FF2BB4E1BECA2D53?start=15&amp;amp;tstart=0&#34;&gt;http://communities.vmware.com/thread/220683;jsessionid=480C8A2C9B9EACA9FF2BB4E1BECA2D53?start=15&amp;amp;tstart=0&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Looks like its a known bug and will be fixed in the upcoming VC4.0 update 1 sometime Q3 2009 :(&lt;/p&gt;</description>
			</item>
			<item>
				<title>ESX - network utilization</title>
				<link>https://sigtar.com/2009/08/22/esx-network-utilization/</link>
				<pubDate>Sat, 22 Aug 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/08/22/esx-network-utilization/</guid>
				<description>&lt;p&gt;One of the best articles i have found on this subject is here : &lt;a href=&#34;http://blog.scottlowe.org/2008/07/16/understanding-nic-utilization-in-vmware-esx/&#34;&gt;http://blog.scottlowe.org/2008/07/16/understanding-nic-utilization-in-vmware-esx/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;There is some additional information here on setting up an etherchannel on the cisco side : &lt;a href=&#34;http://blog.scottlowe.org/2006/12/04/esx-server-nic-teaming-and-vlan-trunking/&#34;&gt;http://blog.scottlowe.org/2006/12/04/esx-server-nic-teaming-and-vlan-trunking/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;This can be handy if you need a single VM to use both physical nics in a load-balanced manner - both outbound and &lt;strong&gt;inbound&lt;/strong&gt;. Of course its not really that simple though. This will really only add a benefit if the VM is communicating to &lt;em&gt;multiple&lt;/em&gt; destinations (using ip hash - a single destination from a single VM with one IP will always be limited to the same physical nic).&lt;/p&gt;</description>
			</item>
			<item>
				<title>ESX 4 (vSphere) - installation issues</title>
				<link>https://sigtar.com/2009/08/10/esx-4-vsphere-installation-issues/</link>
				<pubDate>Mon, 10 Aug 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/08/10/esx-4-vsphere-installation-issues/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve had a couple of installation issues with ESX4&lt;/p&gt;&#xA;&lt;p&gt;One was particularly strange, the install process would freeze every now and again until i pressed a key on the keyboard. This was related to AMD&amp;rsquo;s power saving C1 mode - disable this in the bios to fix this problem.&lt;/p&gt;&#xA;&lt;p&gt;Secondly it was a problem with my nic. Essentially i didn&amp;rsquo;t have card that was supported (realtek). After inserting a intel card all was well. This fires up a ambiguous error and cans the whole install. (lvmdriver error)&lt;/p&gt;</description>
			</item>
			<item>
				<title>Citrix XenServer 5.5 - First impressions</title>
				<link>https://sigtar.com/2009/07/28/citrix-xenserver-5-5-first-impressions/</link>
				<pubDate>Tue, 28 Jul 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/07/28/citrix-xenserver-5-5-first-impressions/</guid>
				<description>&lt;p&gt;I had decided to try out Citrix Xen Server at home since i work a lot with vmware during my working week and felt like a change. It all seemed well&amp;hellip; That is until i had to deal with &lt;em&gt;snapshots&lt;/em&gt;. I suppose i have taken for granted almost all other virtual host software that provides a simple &amp;ldquo;revert to snapshot&amp;rdquo; option. From what i can tell this is totally absent from Citrix XenServer 5.5.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
