<?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: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine) in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50601#M7412</link>
    <description>Same here with 22.6.1 patch 1.1.&lt;BR /&gt;
Couple of X440-G2 stacks, all are ok but one.&lt;BR /&gt;
Policy (simple at the moment, not much rules, HTTP redirect, no qos yet qos enabled on each), telemetry.&lt;BR /&gt;
Telemetry was ok on all of these but on one I was receiving a lot of such logs, for different ACL entries:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;HAL.IPv4ACL: Slot-1: Mirroring instance EAN was disabled, hence mirror action in telemetry policy entry CITRIXICA was disabled on port 1:1&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
I've decided to re-add this telemetry source but was unsuccessful, not sure if because of an error in XMC like this (based on my browser history):&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;EXOS application attempting to install incompatible ACL: filter vlan *, port * (rule "bjnp", index 14)&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Rebooted the switch (btw after trying to add a telemetry source before the stack got config internally synced, it disappeared from a list of allowed devices, I had to reboot entire XMC eventually) and... ah (...), here we go again. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;
No luck with changing vlan-acl-precedence, no luck with removing qos meters and disabling/enabling CoS via Policy in XMC.&lt;BR /&gt;
&lt;BR /&gt;
Drop some CLI:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Slot-1 SW_STACK-1.45 # show access-list usage acl-slice port 1:1&lt;BR /&gt;Ports 1:1-1:24, 1:51, 1:52&lt;BR /&gt;Stage: INGRESS&lt;BR /&gt;Reserved slices:&lt;BR /&gt;Type           Used   Available&lt;BR /&gt;Policy P/D        1           1&lt;BR /&gt;Policy CoS        0           2&lt;BR /&gt;&lt;BR /&gt;Slices:         Used: 7 Available: 1&lt;BR /&gt;Virtual Slice * (physical slice 2) Rules:  Used:     0 Available:   256 Policy CoS reserved&lt;BR /&gt;Virtual Slice * (physical slice 3) Rules:  Used:     0 Available:   256 Policy CoS reserved&lt;BR /&gt;Virtual Slice * (physical slice 5) Rules:  Used:     0 Available:   256 Policy P/D reserved&lt;BR /&gt;Virtual Slice * (physical slice 6) Rules:  Used:     0 Available:   256&lt;BR /&gt;Virtual Slice 4 (physical slice 0) Rules:  Used:    14 Available:   242 system&lt;BR /&gt;Virtual Slice 5 (physical slice 1) Rules:  Used:     2 Available:   254 system&lt;BR /&gt;Virtual Slice 6 (physical slice 4) Rules:  Used:    76 Available:   180 Policy P/D reserved&lt;BR /&gt;Virtual Slice 7 (physical slice 7) Rules:  Used:     4 Available:   252 user/other&lt;BR /&gt;Stage: EGRESS&lt;BR /&gt;Slices:         Used: 0 Available: 4&lt;BR /&gt;Virtual Slice * (physical slice 0) Rules:  Used:     0 Available:   128&lt;BR /&gt;Virtual Slice * (physical slice 1) Rules:  Used:     0 Available:   128&lt;BR /&gt;Virtual Slice * (physical slice 2) Rules:  Used:     0 Available:   128&lt;BR /&gt;Virtual Slice * (physical slice 3) Rules:  Used:     0 Available:   128&lt;BR /&gt;Stage: LOOKUP&lt;BR /&gt;Reserved slices:&lt;BR /&gt;Type           Used   Available&lt;BR /&gt;Policy Profile    0           4&lt;BR /&gt;&lt;BR /&gt;Slices:         Used: 4 Available: 0&lt;BR /&gt;Virtual Slice * (physical slice 0) Rules:  Used:     0 Available:   128 Policy Profile reserved&lt;BR /&gt;Virtual Slice * (physical slice 1) Rules:  Used:     0 Available:   128 Policy Profile reserved&lt;BR /&gt;Virtual Slice * (physical slice 2) Rules:  Used:     0 Available:   128 Policy Profile reserved&lt;BR /&gt;Virtual Slice * (physical slice 3) Rules:  Used:     0 Available:   128 Policy Profile reserved&lt;BR /&gt;Stage: EXTERNAL&lt;BR /&gt;&lt;BR /&gt;Virtual Slice : (*) Physical slice not allocated to any virtual slice.&lt;BR /&gt;&lt;BR /&gt;* Slot-1 SW_STACK-1.46 # show access-list dynamic&lt;BR /&gt;Dynamic Rules: ((*)- Rule is non-permanent )&lt;BR /&gt;&lt;BR /&gt;(*)hclag_arp_2_4_96_9e_e3_41      Bound to 0 interfaces for application HealthCheckLAG&lt;BR /&gt;(*)policy.rule.df.1.16.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.10              Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.10.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.11.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.12.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.13              Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.13.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.14.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.15.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.16.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.17.22.8         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.18.22.8         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.19.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.2.16.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.20.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.21.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.22.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.23.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.24.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.25.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.26.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.27.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.28.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.29.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.3.16.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.30.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.31.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.32.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.33.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.34.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.35.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.36.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.37.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.38.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.39.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.4               Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.4.16.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.40.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.41.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.42.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.43.22.8         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.44.22.8         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.45.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.46.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.47.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.48.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.49.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.5               Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.5.18.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.50.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.51.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.52.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.53.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.54.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.55.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.56.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.57.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.58.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.59.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.6               Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.6.18.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.60.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.61.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.62.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.63.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.64.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.65.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.66.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.67.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.68.16.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.69.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.7.18.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.70.18.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.71.25.16        Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.8.18.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.rule.df.9.18.16         Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.webredir.server.13.0    Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.webredir.sock.13.0      Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.webredir.sock.13.1      Bound to 1 interfaces for application Policy&lt;BR /&gt;(*)policy.webredir.sock.13.2      Bound to 1 interfaces for application Policy&lt;BR /&gt;* Slot-1 SW_STACK-1.47 # show sflow hardware-utilization&lt;BR /&gt;&lt;BR /&gt;sFlow Hardware Table Utilization Statistics&lt;BR /&gt;&lt;BR /&gt;Slot: 1&lt;BR /&gt;Type: X440G2-48p-10G4&lt;BR /&gt;Resource Type          Current   Maximum   % Util.&lt;BR /&gt;--------------------   -------   -------   -------&lt;BR /&gt;MAC Entries                387     16384         2&lt;BR /&gt;Host Entries                16      4096         0&lt;BR /&gt;IPv4 Entries                 0      4096         0&lt;BR /&gt;IPv6 Entries                 0      2048         0&lt;BR /&gt;Long IPv6 Entries            0      2048         0&lt;BR /&gt;Total Routes                 2       512         0&lt;BR /&gt;IPv4 Neighbors               1       N/A       N/A&lt;BR /&gt;IPv6 Neighbors               0       N/A       N/A&lt;BR /&gt;IPv4 Routes                  2       N/A       N/A&lt;BR /&gt;IPv6 Routes                  0       N/A       N/A&lt;BR /&gt;ECMP Next Hops               0       N/A       N/A&lt;BR /&gt;ACL Ingress Entries         96      2048         4&lt;BR /&gt;ACL Ingress Counters         0      2048         0&lt;BR /&gt;ACL Ingress Meters           0      2048         0&lt;BR /&gt;ACL Ingress Slices           7         8        87&lt;BR /&gt;ACL Egress Entries           0       512         0&lt;BR /&gt;ACL Egress Counters          0       512         0&lt;BR /&gt;ACL Egress Meters            0       512         0&lt;BR /&gt;ACL Egress Slices            0         4         0&lt;BR /&gt;&lt;BR /&gt;Slot: 2&lt;BR /&gt;Type: X440G2-48t-10G4&lt;BR /&gt;Resource Type          Current   Maximum   % Util.&lt;BR /&gt;--------------------   -------   -------   -------&lt;BR /&gt;MAC Entries                388     16384         2&lt;BR /&gt;Host Entries                16      4096         0&lt;BR /&gt;IPv4 Entries                 0      4096         0&lt;BR /&gt;IPv6 Entries                 0      2048         0&lt;BR /&gt;Long IPv6 Entries            0      2048         0&lt;BR /&gt;Total Routes                 0       512         0&lt;BR /&gt;IPv4 Neighbors               0       N/A       N/A&lt;BR /&gt;IPv6 Neighbors               0       N/A       N/A&lt;BR /&gt;IPv4 Routes                  0       N/A       N/A&lt;BR /&gt;IPv6 Routes                  0       N/A       N/A&lt;BR /&gt;ECMP Next Hops               0       N/A       N/A&lt;BR /&gt;ACL Ingress Entries         95      2048         4&lt;BR /&gt;ACL Ingress Counters         0      2048         0&lt;BR /&gt;ACL Ingress Meters           0      2048         0&lt;BR /&gt;ACL Ingress Slices           7         8        87&lt;BR /&gt;ACL Egress Entries           0       512         0&lt;BR /&gt;ACL Egress Counters          0       512         0&lt;BR /&gt;ACL Egress Meters            0       512         0&lt;BR /&gt;ACL Egress Slices            0         4         0&lt;BR /&gt;&lt;BR /&gt;... up to the rest of slots&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
I've lost any clue for the moment based on the fact that couple of stacks have the same EXOS version and Policy domain and there are no issues with Telemetry. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
Did somebody get through it recently?&lt;BR /&gt;
&lt;BR /&gt;
Kind regards,&lt;BR /&gt;
Tomasz</description>
    <pubDate>Sun, 05 May 2019 06:10:00 GMT</pubDate>
    <dc:creator>Tomasz</dc:creator>
    <dc:date>2019-05-05T06:10:00Z</dc:date>
    <item>
      <title>Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50563#M7374</link>
      <description>Hello everybody&lt;BR /&gt;
&lt;BR /&gt;
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.&lt;BR /&gt;
&lt;BR /&gt;
Best regards, Yves&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Feb 2018 15:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50563#M7374</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-02-28T15:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50564#M7375</link>
      <description>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.</description>
      <pubDate>Wed, 28 Feb 2018 15:34:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50564#M7375</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2018-02-28T15:34:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50565#M7376</link>
      <description>Hi Oskar, I have the same Analytics version running. Do you have a configuration example or a documentation of this? Thank you.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Feb 2018 15:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50565#M7376</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-02-28T15:38:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50566#M7377</link>
      <description>Ok, some file editing is needed now to make it work.&lt;BR /&gt;
On XMC, copy sflow,pol.&lt;BR /&gt;
cp /usr/local/Extreme_Networks/NetSight/appdata/Purview/Fingerprints/sflow.pol /tftpboot/&lt;BR /&gt;
&lt;BR /&gt;
On Analytics, edit file /opt/appid/conf/appidconfig.xml and change interfaces to be like:&lt;BR /&gt;
&lt;I&gt;&lt;BR /&gt;
&lt;BR /&gt;
        &lt;I&gt;&lt;BR /&gt;
&lt;BR /&gt;
      &lt;BR /&gt;
&lt;BR /&gt;
Restart analytics or appid after this.&lt;BR /&gt;
&lt;BR /&gt;
On XMC go to analytics, configuration and on your engine add an application telemetry source (the switch) and enforce.&lt;BR /&gt;
&lt;BR /&gt;&lt;/I&gt;&lt;/I&gt;</description>
      <pubDate>Wed, 28 Feb 2018 16:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50566#M7377</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2018-02-28T16:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50567#M7378</link>
      <description>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.&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Feb 2018 16:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50567#M7378</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-02-28T16:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50568#M7379</link>
      <description>sflow together with a mirror config.&lt;BR /&gt;
&lt;BR /&gt;
TestAnalytics.1 # sh sflow&lt;BR /&gt;
SFLOW Global Configuration&lt;BR /&gt;
Global Status: enabled&lt;BR /&gt;
Polling interval: 60&lt;BR /&gt;
Sampling rate: 1024&lt;BR /&gt;
Maximum cpu sample limit: 2000&lt;BR /&gt;
SFLOW Configured Agent IP: 10.116.3.89 Operational Agent IP: 10.116.3.89&lt;BR /&gt;
Collectors&lt;BR /&gt;
Collector IP 10.116.2.209, Port 6343, VR "VR-Default"&lt;BR /&gt;
&lt;BR /&gt;
SFLOW Port Configuration&lt;BR /&gt;
Port      Status           Sample-rate         Subsampling       Sflow-type        &lt;BR /&gt;
                       Config   /  Actual      factor        Ingress  /  Egress    &lt;BR /&gt;
1         enabled     1024      /  1024         1          enabled   /  disabled&lt;BR /&gt;
2         enabled     1024      /  1024         1          enabled   /  disabled&lt;BR /&gt;
TestAnalytics.2 # sh mirror &lt;BR /&gt;
&lt;BR /&gt;
DefaultMirror   (Disabled)&lt;BR /&gt;
    Description:    Default Mirror Instance, created automatically&lt;BR /&gt;
    Mirror to port: -&lt;BR /&gt;
&lt;BR /&gt;
EAN   (Enabled)&lt;BR /&gt;
    Description:    &lt;BR /&gt;
    Mirror to remote IP: 10.116.2.209       VR        : VR-Default&lt;BR /&gt;
    From IP            : 10.116.3.89        Ping check: Off&lt;BR /&gt;
    Status             : Up&lt;BR /&gt;
&lt;BR /&gt;
Mirrors defined:          2 &lt;BR /&gt;
Mirrors enabled:          1 (Maximum 4)&lt;BR /&gt;
HW filter instances used: 0 (Maximum 128)&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Feb 2018 16:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50568#M7379</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2018-02-28T16:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50569#M7380</link>
      <description>I don't have a sflow.pol file.&lt;BR /&gt;
And how/where can I add a "application telemetry source"?&lt;BR /&gt;
&lt;BR /&gt;
What do I have to configure on the switch side?&lt;BR /&gt;
&lt;BR /&gt;
Thank you&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Feb 2018 16:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50569#M7380</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-02-28T16:14:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50570#M7381</link>
      <description>You add the app telemetry source under flow sources. &lt;BR /&gt;
Maybe the sflow.pol file is only created once you do a first enforce. &lt;BR /&gt;
On the switch I think all should be configured by Analytics.</description>
      <pubDate>Wed, 28 Feb 2018 16:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50570#M7381</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2018-02-28T16:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50571#M7382</link>
      <description>Okay, found it, thx.&lt;BR /&gt;
I did an enforce (without adding a telemetry source) but the file isn't there yet.&lt;BR /&gt;
&lt;BR /&gt;
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.&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Feb 2018 16:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50571#M7382</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-02-28T16:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50572#M7383</link>
      <description>I tried it with "Application Telemetry Source" (I guess this is for SFlow+).&lt;BR /&gt;
But I got the following errors when I add the source Switch.&lt;BR /&gt;
&lt;BR /&gt;
-&amp;gt; if {! $OverallResult} {&lt;BR /&gt;
2018-03-02 15:51:52,183 INFO [stdout] Script failed : configure access-list sflow.pol any ingress&lt;BR /&gt;
2018-03-02 15:51:52,185 INFO [stdout] .&lt;BR /&gt;
2018-03-02 15:51:52,185 INFO [stdout] Error: ACL install operation failed - filter hardware full for vlan *, port *&lt;BR /&gt;
2018-03-02 15:51:52,185 INFO [stdout] * switchname.14 #&lt;BR /&gt;
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&lt;BR /&gt;
2018-03-02 15:51:52,192 ERROR [com.enterasys.netsight.appid.server.webapps.monitor.AppIdDwr] javax.script.ScriptException:&lt;BR /&gt;
*** Script Error ***&lt;BR /&gt;
Die command issued: Script failed : configure access-list sflow.pol any ingress&lt;BR /&gt;
.&lt;BR /&gt;
Error: ACL install operation failed - filter hardware full for vlan *, port *&lt;BR /&gt;
* switchname.14 #&lt;BR /&gt;
&lt;BR /&gt;
--&amp;gt; I've already run this command: "configure  access-list vlan-acl-precedence shared" and rebooted the switch.&lt;BR /&gt;
&lt;BR /&gt;
The configuration is a default setup.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Mar 2018 21:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50572#M7383</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-03-02T21:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50573#M7384</link>
      <description>Have the same problem on X440-G2:&lt;BR /&gt;
Error: ACL install operation failed - filter hardware full for vlan *, port *&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Mar 2018 23:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50573#M7384</guid>
      <dc:creator>Bernhard_Gruenw</dc:creator>
      <dc:date>2018-03-02T23:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50574#M7385</link>
      <description>this is a known CR, that will be fixed (if not already)&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Mar 2018 23:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50574#M7385</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2018-03-02T23:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50575#M7386</link>
      <description>Try to configure the access-list width to double.&lt;BR /&gt;
The command to do this is:&lt;BR /&gt;
&lt;BR /&gt;
 configure access-list width double &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Mar 2018 14:07:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50575#M7386</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2018-03-12T14:07:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50576#M7387</link>
      <description>Hi Oscar,&lt;BR /&gt;
&lt;BR /&gt;
I've also test this, but gets the same error as Yves &amp;amp; Bernhard. I've used 22.4.1.4-patch1-2, but we're also working with Policy enabled. So couldn't run the command:&lt;BR /&gt;
&lt;BR /&gt;
configure access-list width double slot 1&lt;BR /&gt;
&lt;BR /&gt;
WARNING: Configuration of double width access-list is not supported when Policy is enabled. Slots will remain in Single width mode.&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Apr 2018 15:02:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50576#M7387</guid>
      <dc:creator>Kevin_Beyers</dc:creator>
      <dc:date>2018-04-06T15:02:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50577#M7388</link>
      <description>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.&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Apr 2018 16:22:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50577#M7388</guid>
      <dc:creator>Yves_Haslimann</dc:creator>
      <dc:date>2018-04-06T16:22:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50578#M7389</link>
      <description>Hi Yves,&lt;BR /&gt;
&lt;BR /&gt;
Ok thanks for the information. The firmware 22.4.1.4-patch2-5 isn't yet available at the partner portal of Extreme Networks?&lt;BR /&gt;
&lt;BR /&gt;
Kind Regards,&lt;BR /&gt;
Kevin.</description>
      <pubDate>Fri, 06 Apr 2018 17:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50578#M7389</guid>
      <dc:creator>Kevin_Beyers</dc:creator>
      <dc:date>2018-04-06T17:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50579#M7390</link>
      <description>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. &lt;BR /&gt;
22.5 will also contain the fix once it is available (expected end of May).</description>
      <pubDate>Tue, 24 Apr 2018 13:20:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50579#M7390</guid>
      <dc:creator>OscarK</dc:creator>
      <dc:date>2018-04-24T13:20:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50580#M7391</link>
      <description>Hi Oscar,&lt;BR /&gt;
&lt;BR /&gt;
Ok thanks for the information, I will contact Extreme GTAC.&lt;BR /&gt;
&lt;BR /&gt;
Kind Regards,&lt;BR /&gt;
Kevin.</description>
      <pubDate>Tue, 24 Apr 2018 13:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50580#M7391</guid>
      <dc:creator>Kevin_Beyers</dc:creator>
      <dc:date>2018-04-24T13:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50581#M7392</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Just to let you know I'm running into this same problem using firmware version:&lt;BR /&gt;
&lt;BR /&gt;
22.5.1.7&lt;BR /&gt;
&lt;BR /&gt;
EMC = 8.1.3.65&lt;BR /&gt;
&lt;BR /&gt;
Error is:&lt;BR /&gt;
&lt;BR /&gt;
An error has occurred while adding a flow source to the selected engine. See details below for more information.&lt;BR /&gt;
 &lt;BR /&gt;
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 # -&amp;gt; if {! $OverallResult} &lt;BR /&gt;
&lt;BR /&gt;
Am also running policy on this X440G2 switch, so setting the double width I get the following message:&lt;BR /&gt;
&lt;BR /&gt;
* POC.1 # configure access-list width double &lt;BR /&gt;
WARNING: Configuration of double width access-list is not supported when Policy is enabled. Slots will remain in Single width mode.&lt;BR /&gt;
&lt;BR /&gt;
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:&lt;BR /&gt;
&lt;BR /&gt;
* POC.4 # enable policy &lt;BR /&gt;
Warning: Enabling Policy will cause some Netlogin settings (such as VLANs and dynamically created VLANs) to be cleared. &lt;BR /&gt;
ERROR: Hardware resources could not be reserved for Policy (count 0).&lt;BR /&gt;
Note that Policy cannot be enabled when double width access-list is configured or operational.&lt;BR /&gt;
&lt;BR /&gt;
Previously upgraded from version 22.4.1.4-patch1-2&lt;BR /&gt;
&lt;BR /&gt;
Post mentions this being fixed in version 22.5, so not sure what I am doing wrong or how to fix / get this working?&lt;BR /&gt;
&lt;BR /&gt;
Seen this command that could be used to adjust ACL usage, but not sure exactly the syntax to use that would help:&lt;BR /&gt;
&lt;BR /&gt;
configure policy resource-profile default profile-modifier [no-mac|no-ipv4|no-ipv6] enable&lt;BR /&gt;
&lt;BR /&gt;
I've tried removing no-ipv6, but no difference?&lt;BR /&gt;
&lt;BR /&gt;
Many thanks.</description>
      <pubDate>Tue, 03 Jul 2018 17:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50581#M7392</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-07-03T17:38:00Z</dc:date>
    </item>
    <item>
      <title>RE: Sending flow data from a switch direct to ExtremeAnalytics (without a flowcollector engine)</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50582#M7393</link>
      <description>Hi,&lt;BR /&gt;
can you show the output of "show sflow hardware-utilization"?&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Jul 2018 17:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/sending-flow-data-from-a-switch-direct-to-extremeanalytics/m-p/50582#M7393</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2018-07-03T17:38:00Z</dc:date>
    </item>
  </channel>
</rss>

