<?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: SLX 20.1.1: Note SLXOS-37594 in Data Center (SLX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69491#M281</link>
    <description>&lt;P&gt;Thank you for clearing this and also for updating the article!&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jun 2020 23:24:43 GMT</pubDate>
    <dc:creator>joergkost</dc:creator>
    <dc:date>2020-06-15T23:24:43Z</dc:date>
    <item>
      <title>SLX 20.1.1: Note SLXOS-37594</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69489#M279</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am trying to understand the issue&amp;nbsp;SLXOS-37594 for our SLX setup.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The GT-article&lt;/P&gt;&lt;P&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000057650" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000057650&lt;/A&gt;&lt;/P&gt;&lt;P&gt;says, this issue has been fixed in SLX-OS 20.1.1 but in the release notes for 20.1.1 or 20.1.2a&amp;nbsp; I am not able to find / recognize the issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, has this been fixed and how do I know if “our”&amp;nbsp;SLX 18r2bd version is affected right now, too?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2020 15:29:13 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69489#M279</guid>
      <dc:creator>joergkost</dc:creator>
      <dc:date>2020-06-15T15:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: SLX 20.1.1: Note SLXOS-37594</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69490#M280</link>
      <description>&lt;P&gt;&lt;A href="https://ext.connectedcommunity.org/profile?UserKey=cd70c58e-5862-41af-89ad-9d238fcc212a" target="_self" rel="noreferrer"&gt;joergkost&lt;/A&gt;&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;I looked into the article and it appears rather misleading.&amp;nbsp; I investigated the case history as well as the notes from our SLX Sustaining team and found the following:&lt;/P&gt;  &lt;UL&gt;&lt;LI&gt;The issue is a non service affecting Display (CLI output) issue, IPv6 routes are not affected&lt;/LI&gt; 	&lt;LI&gt;SLXOS-37594 was filed as an “Improvement” and is not a Software Defect, which is why it is not listed in the RN under “Defects”&lt;/LI&gt; 	&lt;LI&gt;The display issue was caused by a HW SDK change which does not allow the command “show hw route-info” to read the compressed routes&lt;/LI&gt; 	&lt;LI&gt;The new command is available in 20.1.1 and is planned to be released in 18r.2.00c ~ETA July 2020&lt;/LI&gt; &lt;/UL&gt;&lt;P&gt;Thanks,&lt;/P&gt;  &lt;P&gt;Michael Morey&lt;BR /&gt; Principal Technical Support Engineer / Extreme Networks&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2020 20:23:43 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69490#M280</guid>
      <dc:creator>Michael_Morey</dc:creator>
      <dc:date>2020-06-15T20:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: SLX 20.1.1: Note SLXOS-37594</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69491#M281</link>
      <description>&lt;P&gt;Thank you for clearing this and also for updating the article!&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2020 23:24:43 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/slx-20-1-1-note-slxos-37594/m-p/69491#M281</guid>
      <dc:creator>joergkost</dc:creator>
      <dc:date>2020-06-15T23:24:43Z</dc:date>
    </item>
  </channel>
</rss>

