<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Enabling  - Editing System TCP/IP NetStack - vMotion in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801714#M175764</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Found your question and had the same exact problem.&amp;nbsp; &lt;/P&gt;&lt;P&gt;I was kind of upset to see you asked this 2 years ago and got no replies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I figure you're well past this, but thought I'd post the solution for anyone else that is looking at this problem.&lt;/P&gt;&lt;P&gt;I'm using ESX 6.5 and PowerCLI, so I'm not sure if it works for older versions, but I suspect it does.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to tap into vmWare's default net stacks, you have to name your custom stacks exactly as follows, case sensitive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vMotion = vmotion&lt;/P&gt;&lt;P&gt;Provisioning = vSphereProvisioning&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For those who could use some demo code, because I've literally spent 2 days slogging through poorly documented commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$vmhost = "EsxServer01"&lt;/P&gt;&lt;P&gt;$vsw = Get-vmHost $vmhost | Get-VirtualSwitch -standard&lt;/P&gt;&lt;P&gt;$portgroup1 = New-VirtualPortGroup -Name "vMotion" -VirtualSwitch $vsw -VLanID 100 -Confirm:$false&lt;/P&gt;&lt;P&gt;$portgroup2 = New-VirtualPortGroup -Name "vMigration" -VirtualSwitch $vsw -VLanID 101 -Confirm:$false&lt;/P&gt;&lt;P&gt;$vmk1 =&amp;nbsp; "vmk1"&lt;/P&gt;&lt;P&gt;$vmk2 = "vmk2"&lt;/P&gt;&lt;P&gt;$esxcli = Get-Esxcli -VMHost $vmhost&lt;/P&gt;&lt;P&gt;$esxcli.network.ip.netstack.add($null,"vmotion") &lt;/P&gt;&lt;P&gt;$esxcli.network.ip.interface.add($null,$null,$vmk1,$null,9000,"vmotion",$portgroup1.Name)&lt;/P&gt;&lt;P&gt;$esxcli.network.ip.netstack.add($null,"vSphereProvisioning") &lt;/P&gt;&lt;P&gt;$esxcli.network.ip.interface.add($null,$null,$vmk2,$null,9000,"vSphereProvisioning",$portgroup2.Name)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps someone.&amp;nbsp; And if you're looking to use a distributed switch, good luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Apr 2017 09:36:04 GMT</pubDate>
    <dc:creator>MikeStanton</dc:creator>
    <dc:date>2017-04-26T09:36:04Z</dc:date>
    <item>
      <title>Enabling  - Editing System TCP/IP NetStack - vMotion</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801713#M175763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm looking to enable the vMotion TCP/IP Stack prior to migrating the VMK to use the Stack. Setting DNS Values, Domain Name and default gateway to allow for L3 capabilities&lt;/P&gt;&lt;P&gt;I ma hoping to compete this using using ESXCLI commands on the newly provisioned host that will read the command via a KS script as there are no CMDlets in PowerCli available as of yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems pretty straight forward to create the fresh new stack and then add the VMK using this method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip netstack add --netstack new-vmotion&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip dns search&amp;nbsp; add&amp;nbsp; --netstack new-vmotion --domain test.domain&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip dns server&amp;nbsp; add&amp;nbsp; --netstack new-vmotion --server 192.168.5.5&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip dns server&amp;nbsp; add&amp;nbsp; --netstack new-vmotion --server 192.168.5.6&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; font-size: 10pt;"&gt;&lt;EM&gt;esxcli network vswitch standard portgroup add --portgroup-name Vmotion_ESX --vswitch-name vSwitch0&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network vswitch standard portgroup set --portgroup-name Vmotion_ESX --vlan-id 202&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip interface add --interface-name vmk10 --portgroup-name Vmotion_ESX --netstack new-vmotion&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip interface ipv4 set --interface-name vmk10 --ipv4 192.168.111.100 --netmask 255.255.255.0 --type static&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip route ipv4 add --network 192.168.111.0/24 --netstack new-vmotion --gateway 192.168.111.1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if i want to use the existing stacks (vMotion, Provisioning ) that are automatically created during install they don't seem to listed. With the exception of the defaultTcpipStack as per below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;esxcli network ip netstack list&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;defaultTcpipStack&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Key: defaultTcpipStack&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Name: defaultTcpipStack&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;State: 4660&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I manually created the VMK and Migrated to the system stack using the web client. Once i Did i re-ran the&amp;nbsp; &lt;EM&gt;esxcli network ip netstack list&lt;/EM&gt; command&amp;nbsp; and both default and the vmotion netstack were listed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;defaultTcpipStack&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; Key: defaultTcpipStack&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; Name: defaultTcpipStack&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; State: 4660&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;vmotion&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; Key: vmotion&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; Name: vmotion&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; State: 4660&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I tried using the "vmotion" Key/Name list from the above command to edit the dns setting etc but to no luck there either.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;One last thing i did try was to enable the Netstack as i noticed you could create them in disabled mode&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;EM&gt;esxcli network ip netstack set --netstack vmotion --enable true&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;STRONG&gt;Unable to find a Netstack instance vmotion&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Any ideas if it is possible to edit the system TCP/IP NetStacks via the esxcli prior to adding the Vmks ? Once the VMk has been migrated it is possible to edit the DNS setting etc via esxcli&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Any help or pointers appreciated&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2015 15:20:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801713#M175763</guid>
      <dc:creator>cliffcahill</dc:creator>
      <dc:date>2015-10-08T15:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling  - Editing System TCP/IP NetStack - vMotion</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801714#M175764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Found your question and had the same exact problem.&amp;nbsp; &lt;/P&gt;&lt;P&gt;I was kind of upset to see you asked this 2 years ago and got no replies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I figure you're well past this, but thought I'd post the solution for anyone else that is looking at this problem.&lt;/P&gt;&lt;P&gt;I'm using ESX 6.5 and PowerCLI, so I'm not sure if it works for older versions, but I suspect it does.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to tap into vmWare's default net stacks, you have to name your custom stacks exactly as follows, case sensitive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vMotion = vmotion&lt;/P&gt;&lt;P&gt;Provisioning = vSphereProvisioning&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For those who could use some demo code, because I've literally spent 2 days slogging through poorly documented commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$vmhost = "EsxServer01"&lt;/P&gt;&lt;P&gt;$vsw = Get-vmHost $vmhost | Get-VirtualSwitch -standard&lt;/P&gt;&lt;P&gt;$portgroup1 = New-VirtualPortGroup -Name "vMotion" -VirtualSwitch $vsw -VLanID 100 -Confirm:$false&lt;/P&gt;&lt;P&gt;$portgroup2 = New-VirtualPortGroup -Name "vMigration" -VirtualSwitch $vsw -VLanID 101 -Confirm:$false&lt;/P&gt;&lt;P&gt;$vmk1 =&amp;nbsp; "vmk1"&lt;/P&gt;&lt;P&gt;$vmk2 = "vmk2"&lt;/P&gt;&lt;P&gt;$esxcli = Get-Esxcli -VMHost $vmhost&lt;/P&gt;&lt;P&gt;$esxcli.network.ip.netstack.add($null,"vmotion") &lt;/P&gt;&lt;P&gt;$esxcli.network.ip.interface.add($null,$null,$vmk1,$null,9000,"vmotion",$portgroup1.Name)&lt;/P&gt;&lt;P&gt;$esxcli.network.ip.netstack.add($null,"vSphereProvisioning") &lt;/P&gt;&lt;P&gt;$esxcli.network.ip.interface.add($null,$null,$vmk2,$null,9000,"vSphereProvisioning",$portgroup2.Name)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps someone.&amp;nbsp; And if you're looking to use a distributed switch, good luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Apr 2017 09:36:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801714#M175764</guid>
      <dc:creator>MikeStanton</dc:creator>
      <dc:date>2017-04-26T09:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling  - Editing System TCP/IP NetStack - vMotion</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801715#M175765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/519794"&gt;vMotion TCP/IP Stack- Created by Powercli&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply Mike - See attached thread I got there in the END yay !:P&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jul 2017 17:55:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Enabling-Editing-System-TCP-IP-NetStack-vMotion/m-p/1801715#M175765</guid>
      <dc:creator>cliffcahill</dc:creator>
      <dc:date>2017-07-10T17:55:41Z</dc:date>
    </item>
  </channel>
</rss>

