<?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: ICX 6610 - MsgAgeExpiry after increasing &amp;quot;system-max spanning-tree&amp;quot; in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-6610-MsgAgeExpiry-after-increasing-quot-system-max-spanning/m-p/20585#M817</link>
    <description>Hi Paulcian,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Increasing the spanning tree default values might not lead to MsgAgeExpiry logs. This is usually seen when a switch in a spanning tree domain notices a topology change indicating that a BPDU was not received by the port for the default max_age time.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Jijo &amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
    <pubDate>Sun, 12 Jul 2020 08:16:28 GMT</pubDate>
    <dc:creator>jijo_panangat</dc:creator>
    <dc:date>2020-07-12T08:16:28Z</dc:date>
    <item>
      <title>ICX 6610 - MsgAgeExpiry after increasing "system-max spanning-tree"</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-6610-MsgAgeExpiry-after-increasing-quot-system-max-spanning/m-p/20584#M816</link>
      <description>After increasing "system-max spanning-tree" from default of 32 to 64 we have seen multiple vlans at the same time have the 802-1w MsgAgeExpiry trigger.&amp;nbsp; Prior to this change there were no events.&lt;BR /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;CPU looks fine, no errors/CRCs on links, etc.&amp;nbsp; I can only assume this change caused the issue.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Any ideas?</description>
      <pubDate>Mon, 06 Jul 2020 14:33:04 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-6610-MsgAgeExpiry-after-increasing-quot-system-max-spanning/m-p/20584#M816</guid>
      <dc:creator>paul_cianciulli</dc:creator>
      <dc:date>2020-07-06T14:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: ICX 6610 - MsgAgeExpiry after increasing "system-max spanning-tree"</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-6610-MsgAgeExpiry-after-increasing-quot-system-max-spanning/m-p/20585#M817</link>
      <description>Hi Paulcian,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Increasing the spanning tree default values might not lead to MsgAgeExpiry logs. This is usually seen when a switch in a spanning tree domain notices a topology change indicating that a BPDU was not received by the port for the default max_age time.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Jijo &amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Sun, 12 Jul 2020 08:16:28 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-6610-MsgAgeExpiry-after-increasing-quot-system-max-spanning/m-p/20585#M817</guid>
      <dc:creator>jijo_panangat</dc:creator>
      <dc:date>2020-07-12T08:16:28Z</dc:date>
    </item>
  </channel>
</rss>

