<?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: Portgroups and VLAN ID in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886383#M41226</link>
    <description>&lt;P&gt;Yes.&lt;BR /&gt;An Host can use vSS and vDS simultaneously. It helps if you have enough pNICs so that every vSwitch have atleast one Uplink &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@90D223CDF4C4491D7DFF693BB5C76865/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;We use a combination from&amp;nbsp; beginning with vSphere 4.0? since 2010 or so because for our IP based storage we would like to stay on vSS. All VMs and vMotion,FT use the vDS since then.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Joerg&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jan 2022 22:19:47 GMT</pubDate>
    <dc:creator>IRIX201110141</dc:creator>
    <dc:date>2022-01-04T22:19:47Z</dc:date>
    <item>
      <title>Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886332#M41219</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have the following concern:&lt;/P&gt;&lt;P&gt;You can create a portgroup that is associated with multiple VLAN IDs, for example a single portgroup with ID 20,30,50,70.&lt;/P&gt;&lt;P&gt;Because I have always created portgroups but with a VLAN ID, associated with each portgroup.&lt;/P&gt;&lt;P&gt;It is an environment with vCenter and ESXi, both 7.0&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 17:05:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886332#M41219</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-04T17:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886335#M41220</link>
      <description>&lt;P&gt;VLAN-Trunking - i.e. assigning multiple VLANs to a single port group - is available on Virtual Distributed Switches.&lt;/P&gt;
&lt;P&gt;Standard vSwitches allow only a single VLAN-ID&amp;nbsp; per port group. You may consider to assign VLAN-ID 4095, which however will pass traffic for all VLANs to the VMs&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 17:17:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886335#M41220</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-01-04T17:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886337#M41221</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Well currently the environment is a cluster of 4 nodes, in the four ESXi there are three vswitches, one for administration, another for vmotion and another for virtual machines.&lt;/P&gt;&lt;P&gt;The client has a vcenter enterprise plus license, which would allow me to create the vDS and create the trunking vlan.&lt;/P&gt;&lt;P&gt;However, I could have those 4 nodes simultaneously connected to the Distributed vswitch with the standard vswitch that are already configured in the four esxi?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 17:34:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886337#M41221</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-04T17:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886340#M41222</link>
      <description>&lt;P&gt;Each vSwitch - Standard and/or Distributed - needs its own uplinks (vmnics), so unless the hosts have unused network ports, you need to do a migration. As a side note, if the physical switches are the same for Management, vMotion, and VM traffic, you may consider to merge the different networks into one distributed switch.&lt;/P&gt;
&lt;P&gt;Please don't mind me asking, but what's the reason to move from virtual switch tagging to virtual machine tagging?&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 18:09:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886340#M41222</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-01-04T18:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886347#M41223</link>
      <description>&lt;P&gt;It is for a specific vm that needs to work with those VLAN IDs.&lt;/P&gt;&lt;P&gt;But as I said before, we have standard switches for the different services.&lt;/P&gt;&lt;P&gt;I don't know if the hosts have unused ports, in this case I would have to validate it.&lt;/P&gt;&lt;P&gt;Regarding assigning vlan ID 4095 in a portgroup, would it be the most recommended for this situation?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 19:01:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886347#M41223</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-04T19:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886353#M41224</link>
      <description>&lt;P&gt;Not necessarily the most recommended option (at least not in my opinion), because the VM will receive all tagged traffic from the vSwitch, which - besides the amount of traffic itself - could raise security concerns. However, in case of standard vSwitches that's the only option for VGT.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 19:12:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886353#M41224</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-01-04T19:12:23Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886362#M41225</link>
      <description>&lt;P&gt;ok ok I understand.&lt;/P&gt;&lt;P&gt;In case you have uplinks available on the ESXi, you could have those hosts simultaneously connected to a standard vswitch and a distributed vswitch&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 19:44:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886362#M41225</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-04T19:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886383#M41226</link>
      <description>&lt;P&gt;Yes.&lt;BR /&gt;An Host can use vSS and vDS simultaneously. It helps if you have enough pNICs so that every vSwitch have atleast one Uplink &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@90D223CDF4C4491D7DFF693BB5C76865/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;We use a combination from&amp;nbsp; beginning with vSphere 4.0? since 2010 or so because for our IP based storage we would like to stay on vSS. All VMs and vMotion,FT use the vDS since then.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Joerg&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 22:19:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886383#M41226</guid>
      <dc:creator>IRIX201110141</dc:creator>
      <dc:date>2022-01-04T22:19:47Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886662#M41234</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thanks for all your comments,&lt;/P&gt;&lt;P&gt;Seeing from another point of view, it could be feasible that at the physical switch level a trunk port is configured with those vlans and at the esxi level it can create the portgroups with their respective vlan id, I mean a portgroup for each vlan id&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 21:38:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886662#M41234</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-05T21:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886733#M41239</link>
      <description>&lt;P&gt;That's how this is usually done. Create port groups with the required VLAN-ID's, add additional virtual network adapters to your VM, and assign these network adapters to the port groups. Please note that the maximum number of virtual NICs per VM is 10.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 09:31:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886733#M41239</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-01-06T09:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886842#M41241</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;Ok ok, at the ESXi level I would do it like this, but at the physical switch level you should configure a trunk port with those allowed vlan.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 18:55:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886842#M41241</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-06T18:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886845#M41242</link>
      <description>&lt;P&gt;Yes, for this to work, the physical switch port(s) need to be configured as tagged (802.1Q) ports with the required VLANs allowed.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 19:15:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2886845#M41242</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-01-06T19:15:48Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2887955#M41314</link>
      <description>&lt;P&gt;Good afternoon,&lt;/P&gt;&lt;P&gt;again here, reviewing the recommendations that they indicated to me, and analyzing the scenarios.&lt;/P&gt;&lt;P&gt;I have two options to offer the client:&lt;/P&gt;&lt;P&gt;1- In the vm, add network adapters that are connected to the portgroups with their respective VLAN ID.&lt;/P&gt;&lt;P&gt;2- Create a portgroup with VLAN ID 4095, and in this case at the operating system level (linux appliances) of the vm, add those VLAN IDs, in vm with Windows I have done it, but I would like to know if a linux level, is VGT possible?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jan 2022 16:42:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2887955#M41314</guid>
      <dc:creator>virtualhelp</dc:creator>
      <dc:date>2022-01-13T16:42:06Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2887973#M41315</link>
      <description>&lt;P&gt;I guess that this is possible with all Linux distribution, but why don't you just go with option 1 and avoid additional/unnecessary guest network configurations? The configuration for the physical network port(s) is the same in both cases.&lt;/P&gt;
&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jan 2022 17:53:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2887973#M41315</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2022-01-13T17:53:56Z</dc:date>
    </item>
    <item>
      <title>Re: Portgroups and VLAN ID</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2966058#M45115</link>
      <description>&lt;P&gt;I am creating a virtual firewall and will have a virtualized network interface going to my Internet ISP. I am not planning on bringing this connection to a switch. I am just going to plug it into the physical NIC on my OPNsense server. On the virtual switch/port group side would I just use 0 for the vlan?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Apr 2023 13:05:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Portgroups-and-VLAN-ID/m-p/2966058#M45115</guid>
      <dc:creator>SteveFXP</dc:creator>
      <dc:date>2023-04-28T13:05:42Z</dc:date>
    </item>
  </channel>
</rss>

