<?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: Adding Uplinks and VLANs on a new dHCI Install in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192650#M3237</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2165044"&gt;@PS-NP&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Perfect!&lt;/P&gt;
&lt;P&gt;We are glad to know you were able to resolve the issue and we appreciate you for keeping us updated.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Jul 2023 06:09:16 GMT</pubDate>
    <dc:creator>Sunitha_Mod</dc:creator>
    <dc:date>2023-07-24T06:09:16Z</dc:date>
    <item>
      <title>Adding Uplinks and VLANs on a new dHCI Install</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192448#M3234</link>
      <description>&lt;P&gt;We just set up a new dHCI install.&amp;nbsp; 3 DL360 hosts and one Alletra 6050 storage.&amp;nbsp; Long story short, we can successfully migrate a VM from an old vCenter (6.7) to the new (7.0.3).&amp;nbsp; But after the VM arrives, it cannot communicated back to the production network.&amp;nbsp; The same VLANs on the old vCenter are allowed on the ports on the 2 new Mellanox switches.&lt;/P&gt;&lt;P&gt;Where do I need to look at networking to allow the VM (static IP) to communicate back to existing production VLANs?&lt;/P&gt;&lt;P&gt;Do I need to do something with the TCP/IP stack, routing and gateways?&lt;/P&gt;&lt;P&gt;Should I create a port group in trunk mode, allow all VLANs and let the vmk IPs handle it; or create a port group for each VLAN (we have about 6 VLANs)?&lt;BR /&gt;&lt;BR /&gt;There are 2 additional NIC ports on each host we want to use for VM traffic and keep them off the management VLAN.&amp;nbsp; I can't seem the VM to communicate on a new vswitch using the aditional ports either.&amp;nbsp; Is it safe to add additional NICs to the default dHCI vswitch?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 13:40:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192448#M3234</guid>
      <dc:creator>PS-NP</dc:creator>
      <dc:date>2023-07-21T13:40:03Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Uplinks and VLANs on a new dHCI Install</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192542#M3236</link>
      <description>&lt;P&gt;Without writing a novel about our network configuration here's what the fix was/is.&lt;/P&gt;&lt;P&gt;I got our network guy on the line to step through a bunch of stuff.&amp;nbsp; We verified the Mellanox switch and core switch settings (no changes made).&amp;nbsp; Ping a few things and watched them die.&amp;nbsp; He and I are prety sure it's a VMware network issue.&lt;/P&gt;&lt;P&gt;So, I have him watch me set up a distributed virtual switch, add the physical NICs, set up a port group with the specific VLAN, and add the VMKs with the correct IPV4 settings.&amp;nbsp; Then I put the test VM on the new port group and it worked.&lt;/P&gt;&lt;P&gt;I don't know what I was doing incorrect previously, but now it's working.&amp;nbsp; Trunking didn't work, I had to create specific VLANs.&lt;BR /&gt;&lt;BR /&gt;Additionally, cross vCenter Motion was broken initially.&amp;nbsp; We had to allow the old vCenter management VLAN (different from the new one) specifically on the Mellanox dHCI management ports.&amp;nbsp; We also allowed other VLANs related to various, current VM traffic on both the Mellanox management ports and the ports the new vswitch uplinks use for VM traffic.&lt;BR /&gt;&lt;BR /&gt;For us, this seems to be resolved.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 13:40:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192542#M3236</guid>
      <dc:creator>PS-NP</dc:creator>
      <dc:date>2023-07-21T13:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: Adding Uplinks and VLANs on a new dHCI Install</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192650#M3237</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2165044"&gt;@PS-NP&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Perfect!&lt;/P&gt;
&lt;P&gt;We are glad to know you were able to resolve the issue and we appreciate you for keeping us updated.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 06:09:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/adding-uplinks-and-vlans-on-a-new-dhci-install/m-p/7192650#M3237</guid>
      <dc:creator>Sunitha_Mod</dc:creator>
      <dc:date>2023-07-24T06:09:16Z</dc:date>
    </item>
  </channel>
</rss>

