<?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: multiple sflow destinations in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/multiple-sflow-destinations/m-p/12063#M174</link>
    <description>It should send all samples to both</description>
    <pubDate>Wed, 11 Jul 2018 13:13:04 GMT</pubDate>
    <dc:creator>BenBeck</dc:creator>
    <dc:date>2018-07-11T13:13:04Z</dc:date>
    <item>
      <title>multiple sflow destinations</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/multiple-sflow-destinations/m-p/12062#M173</link>
      <description>When defining multiple sflow destinations, does the switch round robin between the two or does it send the same data to all configured destinations?&amp;nbsp; I can't seem to find this in the documentation.&amp;nbsp; Trying to figure out how to handle the load I'm getting from one switch on my sflow collector.&amp;nbsp; If it round robins then I can split the load in half by just adding one extra destination and having two collectors.</description>
      <pubDate>Sun, 01 Jul 2018 15:02:27 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/multiple-sflow-destinations/m-p/12062#M173</guid>
      <dc:creator>howardtopher</dc:creator>
      <dc:date>2018-07-01T15:02:27Z</dc:date>
    </item>
    <item>
      <title>Re: multiple sflow destinations</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/multiple-sflow-destinations/m-p/12063#M174</link>
      <description>It should send all samples to both</description>
      <pubDate>Wed, 11 Jul 2018 13:13:04 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/multiple-sflow-destinations/m-p/12063#M174</guid>
      <dc:creator>BenBeck</dc:creator>
      <dc:date>2018-07-11T13:13:04Z</dc:date>
    </item>
  </channel>
</rss>

