cancel
Showing results for 
Search instead for 
Did you mean: 

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

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

Yves_Haslimann
New Contributor III
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
41 REPLIES 41

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)?

Anonymous
Not applicable
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?

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

Anonymous
Not applicable
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

Hi,
can you show the output of "show sflow hardware-utilization"?
GTM-P2G8KFN