Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)

  • 1
  • 2
  • Question
  • Updated 3 months ago
  • Answered
Hello everybody

I would like to configure the Extreme Switches (x440-G2, with version 22.4) to sending sflow/netflow data direct to the Extreme Analytics. I heard this is now possible without having a flowcollector enginge like PV FC-180 installed. Is this true? Because I couldn't find any referenced documentation to this. Thank you very much for your feedback.

Best regards, Yves
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb

Posted 8 months ago

  • 1
  • 2
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
Hello, I have made this working in my lab using Analytics 8.1.1EA2 and it is possible,. Some manual actions are needed on XMC but after that it can work. You could run into problems due to ACL limitations on the X440G2 but it can work.
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb
Hi Oskar, I have the same Analytics version running. Do you have a configuration example or a documentation of this? Thank you.
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
Ok, some file editing is needed now to make it work.
On XMC, copy sflow,pol.
cp /usr/local/Extreme_Networks/NetSight/appdata/Purview/Fingerprints/sflow.pol /tftpboot/

On Analytics, edit file /opt/appid/conf/appidconfig.xml and change interfaces to be like:

<Interfaces>

    <Interface name="eth0" method="pmmap" SwitchType="ERSPAN"/>

  </Interfaces>

Restart analytics or appid after this.

On XMC go to analytics, configuration and on your engine add an application telemetry source (the switch) and enforce.
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb
Hi Oskar, it's me again. Are we talking here about sflow+ ? Because my workmate said, it has to run with sflow+ and not only with sflow.
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
sflow together with a mirror config.

TestAnalytics.1 # sh sflow
SFLOW Global Configuration
Global Status: enabled
Polling interval: 60
Sampling rate: 1024
Maximum cpu sample limit: 2000
SFLOW Configured Agent IP: 10.116.3.89 Operational Agent IP: 10.116.3.89
Collectors
Collector IP 10.116.2.209, Port 6343, VR "VR-Default"

SFLOW Port Configuration
Port      Status           Sample-rate         Subsampling       Sflow-type        
                       Config   /  Actual      factor        Ingress  /  Egress    
1         enabled     1024      /  1024         1          enabled   /  disabled
2         enabled     1024      /  1024         1          enabled   /  disabled
TestAnalytics.2 # sh mirror 

DefaultMirror   (Disabled)
    Description:    Default Mirror Instance, created automatically
    Mirror to port: -

EAN   (Enabled)
    Description:    
    Mirror to remote IP: 10.116.2.209       VR        : VR-Default
    From IP            : 10.116.3.89        Ping check: Off
    Status             : Up

Mirrors defined:          2 
Mirrors enabled:          1 (Maximum 4)
HW filter instances used: 0 (Maximum 128)
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb
I don't have a sflow.pol file.
And how/where can I add a "application telemetry source"?

What do I have to configure on the switch side?

Thank you
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
You add the app telemetry source under flow sources. 
Maybe the sflow.pol file is only created once you do a first enforce. 
On the switch I think all should be configured by Analytics.
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb
Okay, found it, thx.
I did an enforce (without adding a telemetry source) but the file isn't there yet.

I guess I have to test it first in the lab, before I add a switch to the Analytics on customer site. Because I have no idea how business critical this is.
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb
I tried it with "Application Telemetry Source" (I guess this is for SFlow+).
But I got the following errors when I add the source Switch.

-> if {! $OverallResult} {
2018-03-02 15:51:52,183 INFO [stdout] Script failed : configure access-list sflow.pol any ingress
2018-03-02 15:51:52,185 INFO [stdout] .
2018-03-02 15:51:52,185 INFO [stdout] Error: ACL install operation failed - filter hardware full for vlan *, port *
2018-03-02 15:51:52,185 INFO [stdout] * switchname.14 #
2018-03-02 15:51:52,188 ERROR [com.enterasys.netsight.appid.server.webapps.monitor.AppIdDwr] Error in step 2 of enabling SFlow+ source for 10.37.1.52
2018-03-02 15:51:52,192 ERROR [com.enterasys.netsight.appid.server.webapps.monitor.AppIdDwr] javax.script.ScriptException:
*** Script Error ***
Die command issued: Script failed : configure access-list sflow.pol any ingress
.
Error: ACL install operation failed - filter hardware full for vlan *, port *
* switchname.14 #


--> I've already run this command: "configure access-list vlan-acl-precedence shared" and rebooted the switch.

The configuration is a default setup.
Photo of Bernhard Gruenwald

Bernhard Gruenwald

  • 250 Points 250 badge 2x thumb
Have the same problem on X440-G2:
Error: ACL install operation failed - filter hardware full for vlan *, port *
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 12,562 Points 10k badge 2x thumb
this is a known CR, that will be fixed (if not already)
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
Try to configure the access-list width to double.
The command to do this is:

 configure access-list width double 
Photo of Kevin Beyers

Kevin Beyers

  • 80 Points 75 badge 2x thumb
Hi Oscar,

I've also test this, but gets the same error as Yves & Bernhard. I've used 22.4.1.4-patch1-2, but we're also working with Policy enabled. So couldn't run the command:

configure access-list width double slot 1

WARNING: Configuration of double width access-list is not supported when Policy is enabled. Slots will remain in Single width mode.
Photo of Yves Haslimann

Yves Haslimann

  • 898 Points 500 badge 2x thumb
Hello everybody: I got the following information: To use an ExtremeSwitching X440-G2 switch as an Application Telemetry source for ExtremeAnalytics, install firmware version 22.4.1.4-patch2-5 or higher.
Photo of Kevin Beyers

Kevin Beyers

  • 80 Points 75 badge 2x thumb
Hi Yves,

Ok thanks for the information. The firmware 22.4.1.4-patch2-5 isn't yet available at the partner portal of Extreme Networks?

Kind Regards,
Kevin.
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
Hello Kevin, 22.4.1.4-patch2-5 is a private patch and is not publically available. You can get this patch by opening a case. 
22.5 will also contain the fix once it is available (expected end of May).
(Edited)
Photo of Kevin Beyers

Kevin Beyers

  • 80 Points 75 badge 2x thumb
Hi Oscar,

Ok thanks for the information, I will contact Extreme GTAC.

Kind Regards,
Kevin.
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
Hi,

Just to let you know I'm running into this same problem using firmware version:

22.5.1.7

EMC = 8.1.3.65

Error is:

An error has occurred while adding a flow source to the selected engine. See details below for more information.
 
javax.script.ScriptException: *** Script Error *** Die command issued: Script failed : * POC.17 # configure access-list telemetry.pol any ingress . Error: ACL install operation failed - filter hardware full for vlan *, port * * POC.18 # -> if {! $OverallResult} 

Am also running policy on this X440G2 switch, so setting the double width I get the following message:

* POC.1 # configure access-list width double
WARNING: Configuration of double width access-list is not supported when Policy is enabled. Slots will remain in Single width mode.


If I disable policy I can then run the access-list width double command, but when I re-enable policy I then get the following error:

* POC.4 # enable policy
Warning: Enabling Policy will cause some Netlogin settings (such as VLANs and dynamically created VLANs) to be cleared.
ERROR: Hardware resources could not be reserved for Policy (count 0).
Note that Policy cannot be enabled when double width access-list is configured or operational.

Previously upgraded from version 22.4.1.4-patch1-2

Post mentions this being fixed in version 22.5, so not sure what I am doing wrong or how to fix / get this working?

Seen this command that could be used to adjust ACL usage, but not sure exactly the syntax to use that would help:

configure policy resource-profile default profile-modifier [no-mac|no-ipv4|no-ipv6] enable

I've tried removing no-ipv6, but no difference?

Many thanks.
(Edited)
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
Hi,
can you show the output of "show sflow hardware-utilization"?
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
Hi Stephane,

See output below:

POC.4 # show sflow hardware-utilization
sFlow Hardware Table Utilization Statistics
Resource Type           Current    Maximum    % Util.
--------------------    -------    -------    -------
MAC Entries                  11      16383          0
Host Entries                  0       4096          0
IPv4 Entries                  0       4096          0
IPv6 Entries                  0       2048          0
Long IPv6 Entries             0       2048          0
Total Routes                 16        512          3
IPv4 Neighbors                5        N/A        N/A
IPv6 Neighbors                0        N/A        N/A
IPv4 Routes                  16        N/A        N/A
IPv6 Routes                   0        N/A        N/A
ECMP Next Hops                0        N/A        N/A
ACL Ingress Entries          86       2048          4
ACL Ingress Counters         34       1024          3
ACL Ingress Meters            0       2048          0
ACL Ingress Slices            7          8         87
ACL Egress Entries            0        512          0
ACL Egress Counters           0        512          0
ACL Egress Meters             0        512          0
ACL Egress Slices             0          4          0

Thanks
(Edited)
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
you use 87% of the ACL Ingress Slices, so you may be using too much resources. You could see more info with that command:

sh access-list usage acl-slice port 1:1
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
Hi Stephane,

Thanks for posting back. I've currently disabled policy and re-run the Telemetry configuration via EMC, just to see it would take, which it did.

Problem is I can't enable Policy again because its out of resource. So least I know it works with one or the other but never both.

Here is were it stands at the moment with sflow telemetry enabled and policy disabled:

POC.2 # sh access-list usage acl-slice port 1
Ports 1-24, 51, 52
Stage: INGRESS
Slices:          Used: 4  Available: 4
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    256
Virtual Slice  4 (physical slice  4) Rules:   Used:     12  Available:    244 system
Virtual Slice  5 (physical slice  5) Rules:   Used:      2  Available:    254 system
Virtual Slice  6 (physical slice  6) Rules:   Used:    123  Available:    133 user/other
Virtual Slice  7 (physical slice  7) Rules:   Used:     71  Available:    185 user/other
Stage: EGRESS
Slices:          Used: 1  Available: 3
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128
Virtual Slice  3 (physical slice  3) Rules:   Used:      1  Available:    127 user/other
Stage: LOOKUP
Slices:          Used: 0  Available: 4
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128
Stage: EXTERNAL
Virtual Slice :  (*) Physical slice not allocated to any virtual slice.

If I disable the ACL's for telemetry (show config acl)

configure meter ingmeter2 committed-rate 1024 Kbps out-actions drop ports "Default (IRL.1)"
configure meter ingmeter3 committed-rate 2048 Kbps out-actions drop ports "Default (IRL.1)"
configure access-list telemetry any ingress
configure access-list telemetryegress any egress

i.e

unconfigure access-list telemetry
unconfigure access-list telemetryegress

and re-enable policy the ACL slices look like the following:

POC.7 # sh access-list usage acl-slice port 1
Ports 1-24, 51, 52
Stage: INGRESS
Reserved slices:
Type            Used    Available
Policy P/D         0            2
Policy CoS         0            2
Slices:          Used: 7  Available: 1
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    256 Policy CoS reserved
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    256 Policy CoS reserved
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    256 Policy P/D reserved
Virtual Slice  * (physical slice  6) Rules:   Used:      0  Available:    256 Policy P/D reserved
Virtual Slice  5 (physical slice  4) Rules:   Used:     12  Available:    244 system
Virtual Slice  6 (physical slice  5) Rules:   Used:      2  Available:    254 system
Virtual Slice  7 (physical slice  7) Rules:   Used:     64  Available:    192 user/other
Stage: EGRESS
Slices:          Used: 0  Available: 4
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128
Stage: LOOKUP
Reserved slices:
Type            Used    Available
Policy Profile     0            4
Slices:          Used: 4  Available: 0
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128 Policy Profile reserved
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128 Policy Profile reserved
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128 Policy Profile reserved
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128 Policy Profile reserved
Stage: EXTERNAL
Virtual Slice :  (*) Physical slice not allocated to any virtual slice.

With both policy and telemetry disabled:

* POC.9 # sh access-list usage acl-slice port 1
Ports 1-24, 51, 52
Stage: INGRESS
Slices:          Used: 3  Available: 5
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    256
Virtual Slice  * (physical slice  6) Rules:   Used:      0  Available:    256
Virtual Slice  5 (physical slice  4) Rules:   Used:     12  Available:    244 system
Virtual Slice  6 (physical slice  5) Rules:   Used:      2  Available:    254 system
Virtual Slice  7 (physical slice  7) Rules:   Used:     64  Available:    192 user/other
Stage: EGRESS
Slices:          Used: 0  Available: 4
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128
Stage: LOOKUP
Slices:          Used: 0  Available: 4
Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128
Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128
Stage: EXTERNAL
Virtual Slice :  (*) Physical slice not allocated to any virtual slice.

Is there anyway to see what's using those 3 slices when both policy and telemetry are disabled, maybe those meters?
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
for testing purposes, I'd try to disable the meters, and try to use a light Policy with Telemetry. If possible, can you make sure for your Policy TCI Overwrite is disabled as well as CoS (if not needed, of course)?
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
There are no TCi Overwrites configured and removed all the CoS settings, as can been seen in the screenshot below for one example I set the CoS to 'none' 




But even after an enforce the cos value stays persistent in the policy configuration on the switch?



So manually removed this but still no difference to amount of ACL slices used.
(Edited)
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
You should not see that line imho.
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
No worries. Thanks for helping out on this Stephane. It is quite a challenge, just doesn't seem a clear way to see what's using the slices. Even when policy is disabled and all the ACL config is removed 3 are still consumed, but not sure what?

Tried everything I can fined from compression, shared, dedicated, double ACLs, but nothing is effecting or reducing the values.

There is definitely a dark art to it somewhere :)
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
fwiw, you should be able to have telemetry and policy on the x440G2, but I doubt you can have CoS settings as well. You should check why you still have a cos configured. did you try without the meters?
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
Well..

I've disable CoS in policy and did an enforce, well I think that's what I've done - see below:



When you look on the switch there is a lot of config that policy originally added, and it doesn't get removed, even removing a CoS from a role (had to do that manually as previously stated):

configure ports group "Default (IRL.1)" add 1-52
configure ports group "Default (TXQ.0)" add 1-52
configure qosscheduler strict-priority ports "Default (TXQ.0)"
configure qosprofile QP1 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP2 maxbuffer 100 weight 1
configure qosprofile QP2 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP3 maxbuffer 100 weight 1
configure qosprofile QP3 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP4 maxbuffer 100 weight 1
configure qosprofile QP4 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP5 maxbuffer 100 weight 1
configure qosprofile QP5 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP6 maxbuffer 100 weight 1
configure qosprofile QP6 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP7 maxbuffer 100 weight 1
configure qosprofile QP7 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure qosprofile QP8 maxbuffer 100 weight 1 ports "Default (TXQ.0)"
configure dot1p type 0 qosprofile QP1 ingress-meter ingmeter0
configure dot1p type 1 qosprofile QP2 ingress-meter ingmeter1
configure dot1p type 2 qosprofile QP3 ingress-meter ingmeter2
configure dot1p type 3 qosprofile QP4 ingress-meter ingmeter3
configure dot1p type 4 qosprofile QP5 ingress-meter ingmeter4
configure dot1p type 5 qosprofile QP6 ingress-meter ingmeter5
configure dot1p type 6 qosprofile QP7 ingress-meter ingmeter6
configure dot1p type 7 qosprofile QP8 ingress-meter ingmeter7
configure vr VR-Default delete protocol mpls
configure cos-index 8 qosprofile QP4 replace-tos 64
configure meter ingmeter2 committed-rate 10000000 Kbps out-actions drop ports "Default (IRL.1)"
configure meter ingmeter3 committed-rate 10000000 Kbps out-actions drop ports "Default (IRL.1)"
configure access-list vlan-acl-precedence shared
configure access-list rule-compression port-counters shared

So apologies if this might seem like a daft question but do you know how I can fully remove all the CoS settings, perhaps just by manually removing all the config above?

I tried removing the meters but it complained about being in use elsewhere, probably the 'configure dot1p' command.

Before I start removing all the config, and its only a POC so its no big deal, I just wanted to see if there was an easier way and that I'm going about it correctly.

Many thanks.
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
A fresh x440G2 (default config) should use only 1 slice.

X440G2-24p-10G4.1 # show access-list usage acl-slice port 1

Ports 1-28

Stage: INGRESS

Slices:          Used: 1  Available: 7

Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    256

Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    256

Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    256

Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    256

Virtual Slice  * (physical slice  4) Rules:   Used:      0  Available:    256

Virtual Slice  * (physical slice  5) Rules:   Used:      0  Available:    256

Virtual Slice  * (physical slice  6) Rules:   Used:      0  Available:    256

Virtual Slice  7 (physical slice  7) Rules:   Used:     10  Available:    246 system

Stage: EGRESS

Slices:          Used: 0  Available: 4

Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128

Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128

Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128

Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128

Stage: LOOKUP

Slices:          Used: 0  Available: 4

Virtual Slice  * (physical slice  0) Rules:   Used:      0  Available:    128

Virtual Slice  * (physical slice  1) Rules:   Used:      0  Available:    128

Virtual Slice  * (physical slice  2) Rules:   Used:      0  Available:    128

Virtual Slice  * (physical slice  3) Rules:   Used:      0  Available:    128

Stage: EXTERNAL



Telemetry + Policy should leave you with 1 slice free.

You could try disabling diffserv examination and dot1p examination and turn off port qos (config port <p> qosprofile none).  If all else fails, you can reduce policy to just L2 rules via:

 

                config policy resource-profile default profile-modifier no-ipv4 enable

 

This will require disable/enable policy but will effectively reserve/consume only 2 slices (instead of 4) for policy.

Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
btw, you are not using double width ACL, right? You should not.
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
Thanks Stephane, shall try this out and post back. I haven't got double width enabled. I did try it, but removed it as I couldn't enable policy.
Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
So I've tried all the above and removed all the QoS config I can, but still the ACL slices will not budge, so no idea what's using them?

Think the only way I'm going to be able to straighten it out I think is wipe the switch and start again.


Thanks for all your effort anyway.
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,416 Points 10k badge 2x thumb
that's certainly a wise decision, playing all around with the ACL config as you did, you may have some leftovers.

Make sure CoS is disabled in Policy Manager, like that:

Photo of Martin Flammia

Martin Flammia

  • 6,326 Points 5k badge 2x thumb
For what its worth I tried added these commands to minimize use of the ACL slices:

configure access-list vlan-acl-precedence shared
configure access-list rule-compression port-counters shared

But made no difference?