<?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: Same VLAN id on different UplinkSets in HPE Synergy</title>
    <link>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7190866#M1332</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You have one Ethernet LIG correct? You cannot have the same VLAN in two uplink sets in the same LIG. The only way to do this would be to create separate LIGs for each VC 100 F32 module. You would have to select "non-redundant (A-side only) and for one LIG and non-redundant (B-side only) for the second one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This configuration simulates how it was on c7000.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope that makes sense.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jun 2023 20:39:30 GMT</pubDate>
    <dc:creator>msobers22</dc:creator>
    <dc:date>2023-06-27T20:39:30Z</dc:date>
    <item>
      <title>Same VLAN id on different UplinkSets</title>
      <link>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7190860#M1331</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can we have same vlan id on different UplinkSet? We got an error while trying to add same vlan id to different uplink sets and would like to know if it's becasue some error on our configuration or a SYNERGY limitation.&lt;/P&gt;&lt;P&gt;We have same vlan id on different UplinkSet on C7000 without any problem. It help us to migrate ToR switches whithout downtime. It seems it's not possible to do so on SYNERGY and that's a limitation for me.&lt;/P&gt;&lt;P&gt;This is the scenario:&lt;/P&gt;&lt;P&gt;- 2 SYNERGY enclosures on the same LE and EG.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- 2 Composer firmware: 6.10.0.0-0437859&lt;/P&gt;&lt;P&gt;- 2 Virtual Connect SE 100Gb, one on each enclosure. Both VCs are on the same LI &amp;amp; LIG.&amp;nbsp;Virtual Connect SE 100Gb F32 Module firmware:&amp;nbsp;&lt;SPAN&gt;2.2.1.1002&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;- 2 UplinkSets created under the LI and LIG.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Adel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 04:10:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7190860#M1331</guid>
      <dc:creator>adel_g</dc:creator>
      <dc:date>2023-06-28T04:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Same VLAN id on different UplinkSets</title>
      <link>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7190866#M1332</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You have one Ethernet LIG correct? You cannot have the same VLAN in two uplink sets in the same LIG. The only way to do this would be to create separate LIGs for each VC 100 F32 module. You would have to select "non-redundant (A-side only) and for one LIG and non-redundant (B-side only) for the second one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This configuration simulates how it was on c7000.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope that makes sense.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jun 2023 20:39:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7190866#M1332</guid>
      <dc:creator>msobers22</dc:creator>
      <dc:date>2023-06-27T20:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Same VLAN id on different UplinkSets</title>
      <link>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7191079#M1338</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;msobers22, thank you for your quick response !!!!&lt;/P&gt;&lt;P&gt;Yes, we have one Ethernet LIG. The two&amp;nbsp;&lt;SPAN&gt;VC 100 F32 modules are linked to the current ethernet LIG.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Can we do wthat you suggest without downtime?&lt;/P&gt;&lt;P&gt;Is your topology still redundant? If one&amp;nbsp;&lt;SPAN&gt;C 100 F32 module fail or the uplink connected to it fail then all traffic will switch to the other side?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Adel&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 17:35:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7191079#M1338</guid>
      <dc:creator>adel_g</dc:creator>
      <dc:date>2023-06-30T17:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: Same VLAN id on different UplinkSets</title>
      <link>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7191080#M1339</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Please refer to the HPE Virtual Connect traffic flow with HPE Synergy Technical White paper. The configuration I described is called &lt;STRONG&gt;Classic Active-Active&lt;/STRONG&gt;. Here is the link to the pdf.&amp;nbsp;&lt;A title="HPE Virtual Connect traffic flow with HPE Synergy technical white paper" href="https://www.hpe.com/psnow/doc/a00042387enw" target="_blank" rel="noopener"&gt;https://www.hpe.com/psnow/doc/a00042387enw&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Downtime will be required to implement the changes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The best practice is the &lt;STRONG&gt;Muti-module link aggregation (MLAG)&lt;/STRONG&gt; configuration. It provides various levels of fault tolerance and load distribution for the Ethernet traffic.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2023 17:56:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/same-vlan-id-on-different-uplinksets/m-p/7191080#M1339</guid>
      <dc:creator>msobers22</dc:creator>
      <dc:date>2023-06-30T17:56:39Z</dc:date>
    </item>
  </channel>
</rss>

