<?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 dynamic ACL Switch reboot Process Policy crashed in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/dynamic-acl-switch-reboot-process-policy-crashed/m-p/95391#M21845</link>
    <description>&lt;P&gt;Hello community,&lt;BR /&gt;we are currently testing dynamic ACLs in combination with X440-G2 switches and for this we followed the documentation in this GTAC article&lt;/P&gt;&lt;P&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000099716&amp;amp;q=exos%20dynamic%20acl" target="_blank"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000099716&amp;amp;q=exos%20dynamic%20acl&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In our tests with a X440-G2-12p switch everything worked fine.&lt;BR /&gt;Now we have enabled the configuration on multiple stacks and find that three stacks (2 and 3 units) reboot irregularly.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The coreDump shows that the process policy crashed.&lt;BR /&gt;core_dump_info storage: 8/5120 used [EMPTY]&lt;BR /&gt;failure: process crash&lt;BR /&gt;time: Tue Apr 4 09:51:26 2023&lt;BR /&gt;process policy&lt;BR /&gt;pid 2148&lt;BR /&gt;signal 6&lt;/P&gt;&lt;P&gt;The switches are running version 31.7.1.4-patch1-77&lt;/P&gt;&lt;P&gt;In the user guide for version 32.1 I have now read that IP address and port masking are supported only with release 32.1 (page 913)&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Beginning with Release 32.1, masking IPv4 addresses, L4 ports, and IP protocol numbers are supported.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;The mask is a required value and must be greater than zero and less than or equal to the maximum&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;number of bits in the field being masked. For example, an IPv4 address mask value must be between 1&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;and 32&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;In the above article, however, IP addresses are already masked in the dACL and 31.2 is specified as the minimum version.&lt;/P&gt;&lt;P&gt;Do I understand something wrong here and can a dACL bring a switch in the version 31.7.1.4-patch1-77 to the reboot?&lt;/P&gt;</description>
    <pubDate>Tue, 04 Apr 2023 10:29:18 GMT</pubDate>
    <dc:creator>StefanS</dc:creator>
    <dc:date>2023-04-04T10:29:18Z</dc:date>
    <item>
      <title>dynamic ACL Switch reboot Process Policy crashed</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/dynamic-acl-switch-reboot-process-policy-crashed/m-p/95391#M21845</link>
      <description>&lt;P&gt;Hello community,&lt;BR /&gt;we are currently testing dynamic ACLs in combination with X440-G2 switches and for this we followed the documentation in this GTAC article&lt;/P&gt;&lt;P&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000099716&amp;amp;q=exos%20dynamic%20acl" target="_blank"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000099716&amp;amp;q=exos%20dynamic%20acl&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In our tests with a X440-G2-12p switch everything worked fine.&lt;BR /&gt;Now we have enabled the configuration on multiple stacks and find that three stacks (2 and 3 units) reboot irregularly.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The coreDump shows that the process policy crashed.&lt;BR /&gt;core_dump_info storage: 8/5120 used [EMPTY]&lt;BR /&gt;failure: process crash&lt;BR /&gt;time: Tue Apr 4 09:51:26 2023&lt;BR /&gt;process policy&lt;BR /&gt;pid 2148&lt;BR /&gt;signal 6&lt;/P&gt;&lt;P&gt;The switches are running version 31.7.1.4-patch1-77&lt;/P&gt;&lt;P&gt;In the user guide for version 32.1 I have now read that IP address and port masking are supported only with release 32.1 (page 913)&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Beginning with Release 32.1, masking IPv4 addresses, L4 ports, and IP protocol numbers are supported.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;The mask is a required value and must be greater than zero and less than or equal to the maximum&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;number of bits in the field being masked. For example, an IPv4 address mask value must be between 1&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;and 32&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;In the above article, however, IP addresses are already masked in the dACL and 31.2 is specified as the minimum version.&lt;/P&gt;&lt;P&gt;Do I understand something wrong here and can a dACL bring a switch in the version 31.7.1.4-patch1-77 to the reboot?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2023 10:29:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/dynamic-acl-switch-reboot-process-policy-crashed/m-p/95391#M21845</guid>
      <dc:creator>StefanS</dc:creator>
      <dc:date>2023-04-04T10:29:18Z</dc:date>
    </item>
    <item>
      <title>Re: dynamic ACL Switch reboot Process Policy crashed</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/dynamic-acl-switch-reboot-process-policy-crashed/m-p/95393#M21846</link>
      <description>&lt;P&gt;This requires deeper investigation and possibly analysis of the core-dump file, so I suggest opening a case with GTAC to have this looked into.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2023 12:32:52 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/dynamic-acl-switch-reboot-process-policy-crashed/m-p/95393#M21846</guid>
      <dc:creator>Chris_H</dc:creator>
      <dc:date>2023-04-04T12:32:52Z</dc:date>
    </item>
  </channel>
</rss>

