<?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: Standard Configuration for smlt-virtual-bmac and smlt-peer-system-id in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120344#M3066</link>
    <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Hello,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;I always do it this way.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;I try to design a address schema that, in the positions after 0049., includes all that is applicable like site ID, Rack location ID, the switch function and switch number in that location.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;First SMLT cluster member&lt;/FONT&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;system-id 0049.xxxx.xxx1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-virtual-bmac 0&lt;FONT size="4"&gt;&lt;U&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;:49:xx:xx:xx:x1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-peer-system-id 0049.xxxx.xxx2&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Second SMLT cluster member&lt;/FONT&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;system-id 0049.xxxx.xxx2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-virtual-bmac 0&lt;FONT size="4"&gt;&lt;U&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;:49:xx:xx:xx:x1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-peer-system-id 0049.xxxx.xxx1&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I use as "smlt-virtual-bmac" the "system-id" from the first cluster member and change the second character from "0" to "&lt;FONT size="4"&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/FONT&gt;", which makes the "smlt-virtual-bmac" a "locally administered" MAC address.&lt;/LI&gt;&lt;LI&gt;As "smlt-peer-system-id" the smlt partner "system-id" is used.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This makes the backbone MAC addresses recognizable.&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;</description>
    <pubDate>Wed, 24 Sep 2025 08:33:48 GMT</pubDate>
    <dc:creator>WillyHe</dc:creator>
    <dc:date>2025-09-24T08:33:48Z</dc:date>
    <item>
      <title>Standard Configuration for smlt-virtual-bmac and smlt-peer-system-id</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120339#M3063</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am trying to configure v-IST to a 7520 switch and I noticed that&amp;nbsp;smlt-virtual-bmac and smlt-peer-system-id is required on the configuration. What is the most efficient way to identify the values for both?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Sep 2025 09:42:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120339#M3063</guid>
      <dc:creator>rrrgamara</dc:creator>
      <dc:date>2025-09-23T09:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Standard Configuration for smlt-virtual-bmac and smlt-peer-system-id</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120344#M3066</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Hello,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;I always do it this way.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;I try to design a address schema that, in the positions after 0049., includes all that is applicable like site ID, Rack location ID, the switch function and switch number in that location.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;First SMLT cluster member&lt;/FONT&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;system-id 0049.xxxx.xxx1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-virtual-bmac 0&lt;FONT size="4"&gt;&lt;U&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;:49:xx:xx:xx:x1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-peer-system-id 0049.xxxx.xxx2&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Second SMLT cluster member&lt;/FONT&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;system-id 0049.xxxx.xxx2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-virtual-bmac 0&lt;FONT size="4"&gt;&lt;U&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;:49:xx:xx:xx:x1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;spbm 1 smlt-peer-system-id 0049.xxxx.xxx1&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I use as "smlt-virtual-bmac" the "system-id" from the first cluster member and change the second character from "0" to "&lt;FONT size="4"&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/FONT&gt;", which makes the "smlt-virtual-bmac" a "locally administered" MAC address.&lt;/LI&gt;&lt;LI&gt;As "smlt-peer-system-id" the smlt partner "system-id" is used.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This makes the backbone MAC addresses recognizable.&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;</description>
      <pubDate>Wed, 24 Sep 2025 08:33:48 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120344#M3066</guid>
      <dc:creator>WillyHe</dc:creator>
      <dc:date>2025-09-24T08:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: Standard Configuration for smlt-virtual-bmac and smlt-peer-system-id</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120355#M3071</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Forgot to include, for the "virtual" "VLACP SMLT -SYS-ID" I use (again) SMLT cluster unit one's "SYSTEM-ID" and change the seconf character to "&lt;FONT size="4"&gt;&lt;STRONG&gt;6&lt;/STRONG&gt;&lt;/FONT&gt;".&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;lacp smlt-sys-id 0&lt;FONT size="4"&gt;&lt;STRONG&gt;6&lt;/STRONG&gt;&lt;/FONT&gt;:49:xx:xx:cc:x1&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;hope it helps&lt;BR /&gt;WillyHe&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2025 11:59:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120355#M3071</guid>
      <dc:creator>WillyHe</dc:creator>
      <dc:date>2025-09-25T11:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: Standard Configuration for smlt-virtual-bmac and smlt-peer-system-id</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120379#M3079</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;This is a great help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 01:16:43 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/standard-configuration-for-smlt-virtual-bmac-and-smlt-peer/m-p/120379#M3079</guid>
      <dc:creator>rrrgamara</dc:creator>
      <dc:date>2025-09-29T01:16:43Z</dc:date>
    </item>
  </channel>
</rss>

