<?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 S3 ACLs vs CISCO ACLs ... it seems something is not working as expected ... in ExtremeSwitching (EOS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60001#M1812</link>
    <description>I all ...&lt;BR /&gt;
&lt;BR /&gt;
we're trying to migrate a CISCO configuration to a S3 ...&lt;BR /&gt;
everything is going fine about L2 and L3, &lt;BR /&gt;
but we're facing some issues with ACLs ...&lt;BR /&gt;
&lt;BR /&gt;
we "copied" and "paste" from CISCO to the S3,&lt;BR /&gt;
changing some little stuff like protocol names and others ...&lt;BR /&gt;
&lt;BR /&gt;
the strange thing is that on the CISCO everything was working fine ...&lt;BR /&gt;
on the S3 instead, we had some issues ... we had to move some rules before others to make them work, but without a reason ... &lt;BR /&gt;
I mean ... for example ...&lt;BR /&gt;
- Rule A&lt;BR /&gt;
- Rule B&lt;BR /&gt;
- Rule C&lt;BR /&gt;
&lt;BR /&gt;
Rule C is the matching one, and rules A and B has NOTHING to share with rule C ...&lt;BR /&gt;
on CISCO everything was working perfectly ... and it worked for years with no rule changes ...&lt;BR /&gt;
on the S3 we had to move Rule C before Rule A to make it work ...&lt;BR /&gt;
&lt;BR /&gt;
I know it sounds "unreal", but is what we "experienced" for some rules ...&lt;BR /&gt;
&lt;BR /&gt;
is there any know best practice? anything we maybe forgot?&lt;BR /&gt;
any know "bug" or misbehavior?&lt;BR /&gt;
&lt;BR /&gt;
this is the firmware we have&lt;BR /&gt;
Chassis Firmware Revision:  08.32.02.0009&lt;BR /&gt;
&lt;BR /&gt;
please let us know&lt;BR /&gt;
&lt;BR /&gt;
best regards&lt;BR /&gt;
&lt;BR /&gt;
Stefano&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Tue, 18 Jul 2017 22:33:00 GMT</pubDate>
    <dc:creator>Stefano_Dall_Os</dc:creator>
    <dc:date>2017-07-18T22:33:00Z</dc:date>
    <item>
      <title>S3 ACLs vs CISCO ACLs ... it seems something is not working as expected ...</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60001#M1812</link>
      <description>I all ...&lt;BR /&gt;
&lt;BR /&gt;
we're trying to migrate a CISCO configuration to a S3 ...&lt;BR /&gt;
everything is going fine about L2 and L3, &lt;BR /&gt;
but we're facing some issues with ACLs ...&lt;BR /&gt;
&lt;BR /&gt;
we "copied" and "paste" from CISCO to the S3,&lt;BR /&gt;
changing some little stuff like protocol names and others ...&lt;BR /&gt;
&lt;BR /&gt;
the strange thing is that on the CISCO everything was working fine ...&lt;BR /&gt;
on the S3 instead, we had some issues ... we had to move some rules before others to make them work, but without a reason ... &lt;BR /&gt;
I mean ... for example ...&lt;BR /&gt;
- Rule A&lt;BR /&gt;
- Rule B&lt;BR /&gt;
- Rule C&lt;BR /&gt;
&lt;BR /&gt;
Rule C is the matching one, and rules A and B has NOTHING to share with rule C ...&lt;BR /&gt;
on CISCO everything was working perfectly ... and it worked for years with no rule changes ...&lt;BR /&gt;
on the S3 we had to move Rule C before Rule A to make it work ...&lt;BR /&gt;
&lt;BR /&gt;
I know it sounds "unreal", but is what we "experienced" for some rules ...&lt;BR /&gt;
&lt;BR /&gt;
is there any know best practice? anything we maybe forgot?&lt;BR /&gt;
any know "bug" or misbehavior?&lt;BR /&gt;
&lt;BR /&gt;
this is the firmware we have&lt;BR /&gt;
Chassis Firmware Revision:  08.32.02.0009&lt;BR /&gt;
&lt;BR /&gt;
please let us know&lt;BR /&gt;
&lt;BR /&gt;
best regards&lt;BR /&gt;
&lt;BR /&gt;
Stefano&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Jul 2017 22:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60001#M1812</guid>
      <dc:creator>Stefano_Dall_Os</dc:creator>
      <dc:date>2017-07-18T22:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: S3 ACLs vs CISCO ACLs ... it seems something is not working as expected ...</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60002#M1813</link>
      <description>Sorry you had an issue, because I would expect the logic of  the ACL to be identical to Cisco.  I am  not aware of any ACL issue related to ordering, and I double-checked the KB and  the release notes.&lt;BR /&gt;
&lt;BR /&gt;
        &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Jul 2017 23:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60002#M1813</guid>
      <dc:creator>Luke_French</dc:creator>
      <dc:date>2017-07-18T23:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: S3 ACLs vs CISCO ACLs ... it seems something is not working as expected ...</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60003#M1814</link>
      <description>Hi, &lt;BR /&gt;
that sound as we were thinking ... &lt;BR /&gt;
I mean, that the LOGIC between the 2 vendors should be the same ...&lt;BR /&gt;
We have to admit the ACL is a very ong one ...&lt;BR /&gt;
600 rules ... more or less ...&lt;BR /&gt;
any known "limit"?&lt;BR /&gt;
is there any best practice?&lt;BR /&gt;
&lt;BR /&gt;
thanks again&lt;BR /&gt;
&lt;BR /&gt;
Stefano&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Jul 2017 23:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60003#M1814</guid>
      <dc:creator>Stefano_Dall_Os</dc:creator>
      <dc:date>2017-07-18T23:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: S3 ACLs vs CISCO ACLs ... it seems something is not working as expected ...</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60004#M1815</link>
      <description>Limits from the release notes.&lt;BR /&gt;
&lt;BR /&gt;
ACLs  1,000 &lt;BR /&gt;
-Access Rules  5,000 &lt;BR /&gt;
-Access Rules – Per ACL  5,000 &lt;BR /&gt;
We do not have any best practices specific to EOS or the S-Series. &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Jul 2017 23:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/s3-acls-vs-cisco-acls-it-seems-something-is-not-working-as/m-p/60004#M1815</guid>
      <dc:creator>Luke_French</dc:creator>
      <dc:date>2017-07-18T23:24:00Z</dc:date>
    </item>
  </channel>
</rss>

