<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using vmware-vim-cmd to Modify a Portgroup</title>
	<atom:link href="http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Rich</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-50922</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Fri, 10 Jun 2011 15:19:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-50922</guid>
		<description>Kenneth,

This command worked for me in esxi 4.1:
vim-cmd hostsvc/net/vswitch_setpolicy --nicorderpolicy-active=vmnic5,vmnic0 vSwitch0

That will apply the policy to the vswitch, but not the port group.  However, this fails:
vim-cmd hostsvc/net/portgroup_set --nicorderpolicy-active=vmnic5,vmnic0 vSwitch0 &quot;Management Network&quot;

I would call that a bug.</description>
		<content:encoded><![CDATA[<p>Kenneth,</p>
<p>This command worked for me in esxi 4.1:<br />
vim-cmd hostsvc/net/vswitch_setpolicy &#8211;nicorderpolicy-active=vmnic5,vmnic0 vSwitch0</p>
<p>That will apply the policy to the vswitch, but not the port group.  However, this fails:<br />
vim-cmd hostsvc/net/portgroup_set &#8211;nicorderpolicy-active=vmnic5,vmnic0 vSwitch0 &#8220;Management Network&#8221;</p>
<p>I would call that a bug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-50864</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Thu, 19 May 2011 14:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-50864</guid>
		<description>Antti, I&#039;m not immediately aware of a workaround, but that doesn&#039;t mean a workaround doesn&#039;t exist. Have you tried something other than the VI Perl Toolkit, like PowerCLI or the vCLI?</description>
		<content:encoded><![CDATA[<p>Antti, I&#8217;m not immediately aware of a workaround, but that doesn&#8217;t mean a workaround doesn&#8217;t exist. Have you tried something other than the VI Perl Toolkit, like PowerCLI or the vCLI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antti Pennanen</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-50863</link>
		<dc:creator>Antti Pennanen</dc:creator>
		<pubDate>Wed, 18 May 2011 21:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-50863</guid>
		<description>Hi,

I started to script automated installation process of our ESXi hosts so that when I plug a blade server into our C7000 blade enclosure it basically installs first a fresh copy of ESXi and then our mgmt linux server connects to it by using vi perl toolkit. I first thought about using host profiles but since they don&#039;t support iscsi configurations I decided to go with the scripts. Now I have a problem because it seems that I cannot modify NIC Failover order by using VI Toolkit and I need to configure that to all of my portgroups (including swiscsi and production networks). Is there anyway how to get this done using &quot;supported&quot; methods instead of logging to ESXi Troubleshooting Mode via SSH and using vim-cmd directly from there? I have been googling around for 8 hours and haven&#039;t found a solution for this. 

Cheers,
Andy</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I started to script automated installation process of our ESXi hosts so that when I plug a blade server into our C7000 blade enclosure it basically installs first a fresh copy of ESXi and then our mgmt linux server connects to it by using vi perl toolkit. I first thought about using host profiles but since they don&#8217;t support iscsi configurations I decided to go with the scripts. Now I have a problem because it seems that I cannot modify NIC Failover order by using VI Toolkit and I need to configure that to all of my portgroups (including swiscsi and production networks). Is there anyway how to get this done using &#8220;supported&#8221; methods instead of logging to ESXi Troubleshooting Mode via SSH and using vim-cmd directly from there? I have been googling around for 8 hours and haven&#8217;t found a solution for this. </p>
<p>Cheers,<br />
Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-47346</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Wed, 20 Jan 2010 15:58:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-47346</guid>
		<description>Okay, this rocks!  Exactly what I need.  Now I&#039;m writing a script to ensure that a server has been built correctly and doesn&#039;t have any settings wrong.  What command is equivalent to &quot;get&quot; rather than &quot;set&quot; the active nic and standby nic please?

cheers,
Kevin</description>
		<content:encoded><![CDATA[<p>Okay, this rocks!  Exactly what I need.  Now I&#8217;m writing a script to ensure that a server has been built correctly and doesn&#8217;t have any settings wrong.  What command is equivalent to &#8220;get&#8221; rather than &#8220;set&#8221; the active nic and standby nic please?</p>
<p>cheers,<br />
Kevin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kenneth</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-45502</link>
		<dc:creator>kenneth</dc:creator>
		<pubDate>Tue, 18 Aug 2009 16:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-45502</guid>
		<description>How do i list multiple vmnics when using this command, i tried &quot;,&quot; and brackets but didn&#039;t seem to like it. 

Thanks!</description>
		<content:encoded><![CDATA[<p>How do i list multiple vmnics when using this command, i tried &#8220;,&#8221; and brackets but didn&#8217;t seem to like it. </p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shahar</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-45417</link>
		<dc:creator>Shahar</dc:creator>
		<pubDate>Mon, 10 Aug 2009 06:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-45417</guid>
		<description>This is all great
but
how do I associate a ESX4i guest to a port-group remotly?</description>
		<content:encoded><![CDATA[<p>This is all great<br />
but<br />
how do I associate a ESX4i guest to a port-group remotly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-43590</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Tue, 10 Feb 2009 15:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-43590</guid>
		<description>Chris,

As far as I know, there&#039;s no recommendation for that other than using switches that support Multi-chassis EtherChannel (MEC), also known as cross-stack EtherChannel. The Catalyst 3120 switches, IIRC, do support that. So, you&#039;re covered.

Just know that using link aggregation like this for those particular types of traffic won&#039;t do a whole lot for you, though--EtherChannel/802.3ad/link aggregation really only gets you more throughput when you have multiple source-destination IP address pairs. VMotion is primarily point-to-point, and the Service Console usually communicates most with vCenter Server.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>As far as I know, there&#8217;s no recommendation for that other than using switches that support Multi-chassis EtherChannel (MEC), also known as cross-stack EtherChannel. The Catalyst 3120 switches, IIRC, do support that. So, you&#8217;re covered.</p>
<p>Just know that using link aggregation like this for those particular types of traffic won&#8217;t do a whole lot for you, though&#8211;EtherChannel/802.3ad/link aggregation really only gets you more throughput when you have multiple source-destination IP address pairs. VMotion is primarily point-to-point, and the Service Console usually communicates most with vCenter Server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-43589</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 10 Feb 2009 15:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-43589</guid>
		<description>Is it recommended that the Service Console and VMotion VMKernal port groups not be set to an active/active nic configuration? My vSwitches are set to active/active with &quot;Route based on ip hash&quot; load balancing policy as I am using stacked Cisco 3120 switches.</description>
		<content:encoded><![CDATA[<p>Is it recommended that the Service Console and VMotion VMKernal port groups not be set to an active/active nic configuration? My vSwitches are set to active/active with &#8220;Route based on ip hash&#8221; load balancing policy as I am using stacked Cisco 3120 switches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SVMotion Syntax &#171; H9Newser&#8217;s Blog</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-43397</link>
		<dc:creator>SVMotion Syntax &#171; H9Newser&#8217;s Blog</dc:creator>
		<pubDate>Fri, 16 Jan 2009 20:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-43397</guid>
		<description>[...] Using vmware-vim-cmd to Modify a Portgroup [...]</description>
		<content:encoded><![CDATA[<p>[...] Using vmware-vim-cmd to Modify a Portgroup [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/comment-page-1/#comment-42910</link>
		<dc:creator>William</dc:creator>
		<pubDate>Tue, 23 Dec 2008 00:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/16/using-vmware-vim-cmd-to-modify-a-portgroup/#comment-42910</guid>
		<description>Ed, as Duncan had already mentioned, you need to add an &quot;=&quot; sign to the end of your --nicteaming-policy:

vmware-vim-cmd hostsvc/net/vswitch_setpolicy --nicteaming-policy=loadbalance_ip vSwitch0</description>
		<content:encoded><![CDATA[<p>Ed, as Duncan had already mentioned, you need to add an &#8220;=&#8221; sign to the end of your &#8211;nicteaming-policy:</p>
<p>vmware-vim-cmd hostsvc/net/vswitch_setpolicy &#8211;nicteaming-policy=loadbalance_ip vSwitch0</p>
]]></content:encoded>
	</item>
</channel>
</rss>

