<?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: Synergy networks creation in HPE Synergy</title>
    <link>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7082818#M281</link>
    <description>&lt;P&gt;Hello Sanja1,&lt;/P&gt;&lt;P&gt;You may refer to the&amp;nbsp;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c05359383" target="_blank" rel="noopener"&gt;HPE Synergy 40Gb F8 Switch Module VLAN Configuration&lt;/A&gt; guide. for more information.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Mar 2020 11:33:38 GMT</pubDate>
    <dc:creator>TVVJ</dc:creator>
    <dc:date>2020-03-17T11:33:38Z</dc:date>
    <item>
      <title>Synergy networks creation</title>
      <link>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7082813#M280</link>
      <description>&lt;P&gt;We are in process building up our new synergy. We have two Virtual Connect SE 40Gb F8 Module connected to two TOR switches. Hosts are ESXi and vmware platform.&lt;/P&gt;&lt;P&gt;Recomendation was (from our HPE partner) to stack switches and crate vlans on those switches (we didn't have any), than to create networks on synergy with corresponding vlans.&lt;/P&gt;&lt;P&gt;Aren't we this way tagging our data twice?? What is the best pratice when crating networks. Is it better to do taggning on VC side or switch side?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2020 11:22:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7082813#M280</guid>
      <dc:creator>Sanja1</dc:creator>
      <dc:date>2020-03-17T11:22:11Z</dc:date>
    </item>
    <item>
      <title>Re: Synergy networks creation</title>
      <link>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7082818#M281</link>
      <description>&lt;P&gt;Hello Sanja1,&lt;/P&gt;&lt;P&gt;You may refer to the&amp;nbsp;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c05359383" target="_blank" rel="noopener"&gt;HPE Synergy 40Gb F8 Switch Module VLAN Configuration&lt;/A&gt; guide. for more information.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2020 11:33:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7082818#M281</guid>
      <dc:creator>TVVJ</dc:creator>
      <dc:date>2020-03-17T11:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: Synergy networks creation</title>
      <link>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7083639#M286</link>
      <description>&lt;P&gt;In most environments you will have at least a handful of VLANs already on the upstream Switches.&lt;/P&gt;&lt;P&gt;VMware Mgmt, maybe vMotion, Some VLANs for various App Servers (Physical and Virtual), etc.&lt;/P&gt;&lt;P&gt;You bring those from the Switches into the VC40 using VLAN Tagging.&lt;BR /&gt;This is not Tagging twice, this is more efficiently using the uplink to carry multiple VLANs at the same time.&lt;BR /&gt;VLAN Tagging is more like a Label, identifying which Frames are on which VLANs.&lt;/P&gt;&lt;P&gt;Otherwise you would have to bring in the VLANs each on their own uplink and if you had 20 VLANs, that would be quite a lot of uplink ports.&lt;BR /&gt;And you might find that VLAN 10's uplink is at maximum capacity while many others are only used a tiny amount.&lt;BR /&gt;Thus you send multiple VLANs down Multiple Uplinks and you get to share the bandwidth and carry easily 100 VLANs with no issues.&lt;/P&gt;&lt;P&gt;I hope this helps clarify.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 19:33:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/synergy-networks-creation/m-p/7083639#M286</guid>
      <dc:creator>DanRobinson</dc:creator>
      <dc:date>2020-03-27T19:33:40Z</dc:date>
    </item>
  </channel>
</rss>

