<?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 I/G/C/B-Series Sflow Configuration Disappears over time in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/i-g-c-b-series-sflow-configuration-disappears-over-time/m-p/51734#M737</link>
    <description>Article ID: 13973 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
I-Series, firmware 6.42.01.0046 and higher&lt;BR /&gt;
G-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
C5-Series, firmware 6.41.00.0022 and higher&lt;BR /&gt;
C3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
B5-Series, firmware 6.41.00.0022 and higher&lt;BR /&gt;
B3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured sFlow as suggested in the &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;Configuration Guide&lt;/A&gt;, with the receiver timeout specified at &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;180000&lt;/PRE&gt;&lt;/DIV&gt; seconds:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set sflow receiver 1 owner enterasys&lt;/PRE&gt;&lt;/DIV&gt;  &lt;U&gt;&lt;/U&gt;&lt;PRE&gt;&lt;U&gt;timeout 180000&lt;/U&gt;&lt;/PRE&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
SFlow receiver timeout value continually decreases, as viewed in the output of a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show sflow receivers&lt;/PRE&gt;&lt;/DIV&gt;' command or possibly the output of a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show config sflow&lt;/PRE&gt;&lt;/DIV&gt;' command.&lt;BR /&gt;
Over time the sFlow config lines disappear from the switch configuration.&lt;BR /&gt;
 Lost sFlow configuration.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
The sFlow operation design contains an unusual feature, in that the sFlow receiver command includes a timeout value, specified in seconds. From the Configuration Guide:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set sflow receiver&lt;/PRE&gt;&lt;/DIV&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;index&lt;/I&gt;&lt;/PRE&gt;&amp;gt;  owner  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;owner-string&lt;/I&gt;&lt;/PRE&gt;&amp;gt;  &lt;U&gt;&lt;/U&gt;&lt;PRE&gt;&lt;U&gt;timeout&lt;/U&gt;&lt;/PRE&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;timeout&lt;/I&gt;&lt;/PRE&gt;&amp;gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;timeout - The time, in seconds, remaining before the receiver/Collector being configured and all associated samplers and pollers expire. The value can range from 0 to 4294967295 seconds.&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Once the timer set by this command expires, the receiver/Collector and all the samplers and pollers associated with this Collector expire and are removed from the switch's configuration. In order to start sending sample data to the Collector again, the Collector must be reconfigured with a new timeout value and samplers and pollers must be configured again. Therefore, you should consider setting the timeout value to the largest value that is reasonable for your environment.&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
The timer value "&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;180000&lt;/PRE&gt;&lt;/DIV&gt;" as shown in the Configuration Guide represents just over two days of elapsed time, so in that case the user would see the sFlow configurations disappear two days after configuring them, when the countdown timer has reached a zero value.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD).&lt;BR /&gt;
&lt;BR /&gt;
Set the timer for the desired operational period. If operation is expected to be permanent, then set the timer sufficiently high so that effectively it will never count down to zero. An initial timer value of &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;3153600000&lt;/PRE&gt;&lt;/DIV&gt; (100 years) would serve that purpose.&lt;BR /&gt;
&lt;BR /&gt;
See also: &lt;A href="http://bit.ly/1hTr0xy" target="_blank" rel="nofollow noreferrer noopener"&gt;13974&lt;/A&gt;.</description>
    <pubDate>Fri, 13 Jun 2014 17:39:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2014-06-13T17:39:00Z</dc:date>
    <item>
      <title>I/G/C/B-Series Sflow Configuration Disappears over time</title>
      <link>https://community.extremenetworks.com/t5/faqs/i-g-c-b-series-sflow-configuration-disappears-over-time/m-p/51734#M737</link>
      <description>Article ID: 13973 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
I-Series, firmware 6.42.01.0046 and higher&lt;BR /&gt;
G-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
C5-Series, firmware 6.41.00.0022 and higher&lt;BR /&gt;
C3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
B5-Series, firmware 6.41.00.0022 and higher&lt;BR /&gt;
B3-Series, firmware 6.03.00.0022 and higher&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured sFlow as suggested in the &lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;Configuration Guide&lt;/A&gt;, with the receiver timeout specified at &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;180000&lt;/PRE&gt;&lt;/DIV&gt; seconds:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set sflow receiver 1 owner enterasys&lt;/PRE&gt;&lt;/DIV&gt;  &lt;U&gt;&lt;/U&gt;&lt;PRE&gt;&lt;U&gt;timeout 180000&lt;/U&gt;&lt;/PRE&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
SFlow receiver timeout value continually decreases, as viewed in the output of a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show sflow receivers&lt;/PRE&gt;&lt;/DIV&gt;' command or possibly the output of a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show config sflow&lt;/PRE&gt;&lt;/DIV&gt;' command.&lt;BR /&gt;
Over time the sFlow config lines disappear from the switch configuration.&lt;BR /&gt;
 Lost sFlow configuration.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
The sFlow operation design contains an unusual feature, in that the sFlow receiver command includes a timeout value, specified in seconds. From the Configuration Guide:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set sflow receiver&lt;/PRE&gt;&lt;/DIV&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;index&lt;/I&gt;&lt;/PRE&gt;&amp;gt;  owner  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;owner-string&lt;/I&gt;&lt;/PRE&gt;&amp;gt;  &lt;U&gt;&lt;/U&gt;&lt;PRE&gt;&lt;U&gt;timeout&lt;/U&gt;&lt;/PRE&gt;  &amp;lt;&lt;I&gt;&lt;/I&gt;&lt;PRE&gt;&lt;I&gt;timeout&lt;/I&gt;&lt;/PRE&gt;&amp;gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;timeout - The time, in seconds, remaining before the receiver/Collector being configured and all associated samplers and pollers expire. The value can range from 0 to 4294967295 seconds.&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Once the timer set by this command expires, the receiver/Collector and all the samplers and pollers associated with this Collector expire and are removed from the switch's configuration. In order to start sending sample data to the Collector again, the Collector must be reconfigured with a new timeout value and samplers and pollers must be configured again. Therefore, you should consider setting the timeout value to the largest value that is reasonable for your environment.&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
The timer value "&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;180000&lt;/PRE&gt;&lt;/DIV&gt;" as shown in the Configuration Guide represents just over two days of elapsed time, so in that case the user would see the sFlow configurations disappear two days after configuring them, when the countdown timer has reached a zero value.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD).&lt;BR /&gt;
&lt;BR /&gt;
Set the timer for the desired operational period. If operation is expected to be permanent, then set the timer sufficiently high so that effectively it will never count down to zero. An initial timer value of &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;3153600000&lt;/PRE&gt;&lt;/DIV&gt; (100 years) would serve that purpose.&lt;BR /&gt;
&lt;BR /&gt;
See also: &lt;A href="http://bit.ly/1hTr0xy" target="_blank" rel="nofollow noreferrer noopener"&gt;13974&lt;/A&gt;.</description>
      <pubDate>Fri, 13 Jun 2014 17:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/i-g-c-b-series-sflow-configuration-disappears-over-time/m-p/51734#M737</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2014-06-13T17:39:00Z</dc:date>
    </item>
  </channel>
</rss>

