<?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 SMLT Square - Force traffic down VLAN UNI instead of SPB (NNI) links in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/smlt-square-force-traffic-down-vlan-uni-instead-of-spb-nni-links/m-p/73657#M994</link>
    <description>We are testing multiple p2p circuits between DC's for the sake of the test we have created VID 50 and placed an IP on these vlans to ping across this circuit for connectivity.&lt;BR /&gt;&lt;BR /&gt;The current DC has prod traffic that is being sent down existing NNI's 2/19 on either side.&lt;BR /&gt;&lt;BR /&gt;For a quick test we have configured a SMLT square between all 4 VSP's. As a consequence of this we have tied VID 50 to I-SID 50 (for SMLT).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Only vid 50 is on links 1/1 and 1/2 (SMLT)&lt;BR /&gt;&lt;BR /&gt;Question:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;How would you force traffic for VID 50 down this SMLT instead of the existing 2/19 (NNI) that is being used for prod traffic? - Any configuration on the prod links is trying to be avoided.&lt;BR /&gt;&lt;BR /&gt;This configuration isn't meant to stay in prod, it is just used as a quick connectivity check across these circuits. (the final configuration would just use NNI's between DC's&lt;BR /&gt;&lt;BR /&gt;Thanks,</description>
    <pubDate>Tue, 28 Jun 2022 17:31:39 GMT</pubDate>
    <dc:creator>AlexT</dc:creator>
    <dc:date>2022-06-28T17:31:39Z</dc:date>
    <item>
      <title>SMLT Square - Force traffic down VLAN UNI instead of SPB (NNI) links</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/smlt-square-force-traffic-down-vlan-uni-instead-of-spb-nni-links/m-p/73657#M994</link>
      <description>We are testing multiple p2p circuits between DC's for the sake of the test we have created VID 50 and placed an IP on these vlans to ping across this circuit for connectivity.&lt;BR /&gt;&lt;BR /&gt;The current DC has prod traffic that is being sent down existing NNI's 2/19 on either side.&lt;BR /&gt;&lt;BR /&gt;For a quick test we have configured a SMLT square between all 4 VSP's. As a consequence of this we have tied VID 50 to I-SID 50 (for SMLT).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Only vid 50 is on links 1/1 and 1/2 (SMLT)&lt;BR /&gt;&lt;BR /&gt;Question:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;How would you force traffic for VID 50 down this SMLT instead of the existing 2/19 (NNI) that is being used for prod traffic? - Any configuration on the prod links is trying to be avoided.&lt;BR /&gt;&lt;BR /&gt;This configuration isn't meant to stay in prod, it is just used as a quick connectivity check across these circuits. (the final configuration would just use NNI's between DC's&lt;BR /&gt;&lt;BR /&gt;Thanks,</description>
      <pubDate>Tue, 28 Jun 2022 17:31:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/smlt-square-force-traffic-down-vlan-uni-instead-of-spb-nni-links/m-p/73657#M994</guid>
      <dc:creator>AlexT</dc:creator>
      <dc:date>2022-06-28T17:31:39Z</dc:date>
    </item>
    <item>
      <title>Re: SMLT Square - Force traffic down VLAN UNI instead of SPB (NNI) links</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/smlt-square-force-traffic-down-vlan-uni-instead-of-spb-nni-links/m-p/73658#M995</link>
      <description>you are creating a loop if you connect vid 50 on both vIST pairs to isid 50.</description>
      <pubDate>Wed, 29 Jun 2022 14:47:23 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/smlt-square-force-traffic-down-vlan-uni-instead-of-spb-nni-links/m-p/73658#M995</guid>
      <dc:creator>Roger_Lapuh</dc:creator>
      <dc:date>2022-06-29T14:47:23Z</dc:date>
    </item>
  </channel>
</rss>

