<?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: Switch port config for MLT in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/switch-port-config-for-mlt/m-p/106030#M2540</link>
    <description>&lt;P&gt;Hi Damief,&lt;/P&gt;&lt;P&gt;Sorry for my poor english but Im not sure if I understand all the topology, but in general, if you deploy a server is a good practise (my opnion)&amp;nbsp;use dual-homing, if you have two NICs in bounding configuration, each one in separates switches, so if one fails you have another link.&lt;/P&gt;&lt;P&gt;Now, Is necesary some kind of agregation in switches side? It depends that the server´s NIC team, for example, if you have active-passive it doesn´t.&lt;/P&gt;&lt;P&gt;But imagine that your NIC team need agregation in switches side, if you are using nortel/avaya/extreme VOSS or ERS, you must use SMLT (Split Mlt) for dual-homing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But for config SMLT you need create IST (on ERS) or vIST (on VOSS) (cluster) between both cores.&lt;/P&gt;&lt;P&gt;About add or link to an existing MLT, it is possible but I belive you must disable de MLT before.&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;EF&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jul 2024 10:09:40 GMT</pubDate>
    <dc:creator>EF</dc:creator>
    <dc:date>2024-07-12T10:09:40Z</dc:date>
    <item>
      <title>Switch port config for MLT</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/switch-port-config-for-mlt/m-p/106000#M2539</link>
      <description>&lt;P&gt;New to setting up MLT and wanted to get some experienced opinions.&lt;/P&gt;&lt;P&gt;We are migrating a security cam server (high bandwidth traffic) from a VM to a physical box.&amp;nbsp; This server sends data to 2 different NAS devices for viewing/archiving.&lt;/P&gt;&lt;P&gt;Currently the traffic goes through two separate switches into three teamed NICs on each NAS.&lt;/P&gt;&lt;P&gt;Switches each have MLT 10 for NAS A and MLT 11 for NAS B&lt;/P&gt;&lt;P&gt;Switch 1 has two ports in MLT 10 (1/45 and 1/46) going to NAS A.&amp;nbsp; Port 1/47 is in MLT 11 going to NAS B.&lt;/P&gt;&lt;P&gt;Switch 2 has one port in MLT 10 (1/45) going to NAS A and two ports in MLT 11 (1/46 and 1/47) going to NAS B.&lt;/P&gt;&lt;P&gt;With the new physical server we will have 4 ports divided into two NIC teams.&amp;nbsp; One pair each will go to Switch 1 and Switch 2.&lt;/P&gt;&lt;P&gt;Again, lack of experience here but we were thinking we would create a new MLT on both switches and apply two ports from each switch (would we want two MLT's?&amp;nbsp; One for each nic team on the new server?)&lt;/P&gt;&lt;P&gt;Last, would we need to do anything to group these new MLT ports to the existing ones that connect to NAS A and B (all ports are on a separate VLAN that only the security cam traffic uses)?&lt;/P&gt;&lt;P&gt;I have attached a quick diagram of the existing setup prior to us adding the new MLT(s) and connecting the 4 ports from the new server.&amp;nbsp; Let me know if further info will help.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 20:27:23 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/switch-port-config-for-mlt/m-p/106000#M2539</guid>
      <dc:creator>damienf</dc:creator>
      <dc:date>2024-07-11T20:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: Switch port config for MLT</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/switch-port-config-for-mlt/m-p/106030#M2540</link>
      <description>&lt;P&gt;Hi Damief,&lt;/P&gt;&lt;P&gt;Sorry for my poor english but Im not sure if I understand all the topology, but in general, if you deploy a server is a good practise (my opnion)&amp;nbsp;use dual-homing, if you have two NICs in bounding configuration, each one in separates switches, so if one fails you have another link.&lt;/P&gt;&lt;P&gt;Now, Is necesary some kind of agregation in switches side? It depends that the server´s NIC team, for example, if you have active-passive it doesn´t.&lt;/P&gt;&lt;P&gt;But imagine that your NIC team need agregation in switches side, if you are using nortel/avaya/extreme VOSS or ERS, you must use SMLT (Split Mlt) for dual-homing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But for config SMLT you need create IST (on ERS) or vIST (on VOSS) (cluster) between both cores.&lt;/P&gt;&lt;P&gt;About add or link to an existing MLT, it is possible but I belive you must disable de MLT before.&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;EF&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 10:09:40 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/switch-port-config-for-mlt/m-p/106030#M2540</guid>
      <dc:creator>EF</dc:creator>
      <dc:date>2024-07-12T10:09:40Z</dc:date>
    </item>
  </channel>
</rss>

