<?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: WiNG wireless syslog for a longer period of time in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90523#M8675</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In regards to your query, the log duration is finite at either 10000 or 100000 packets. Which would not meet your requirements.&lt;BR /&gt;&lt;BR /&gt;I would suggest if possible to choose the device that has the issue the most and conduct a constant ping to this device.&lt;BR /&gt;Next time the message shows you can confirm if ping traffic has stopped.&lt;BR /&gt;I would advise pinging both from local subnet of the wireless client and subnet application server is located.&lt;BR /&gt;&lt;BR /&gt;In case you have some weird firewall or routing related issue you would be able to quickly tell where traffic stops.&lt;BR /&gt;If you server is referenced by name you might want to make sure you DNS server is not having network issues either.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Sep 2020 00:32:29 GMT</pubDate>
    <dc:creator>Daren_E</dc:creator>
    <dc:date>2020-09-16T00:32:29Z</dc:date>
    <item>
      <title>WiNG wireless syslog for a longer period of time</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90522#M8674</link>
      <description>&lt;P&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000081692" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000081692&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to capture the data for long duration ?&amp;nbsp; The article solutions lasts for about 10-20 mins.&amp;nbsp; The issue is that we have a warehouse with 74 APs and 30 handheld units.&amp;nbsp; Throughout the day, the WMS app says “Network Disconnection” even though the client wireless has full signal strength.&amp;nbsp; I believe it’s a “generic app message” but no way to see if the device disconnects from the APs.&amp;nbsp; I want to capture the syslog for 1 day or 3 days?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2020 00:14:40 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90522#M8674</guid>
      <dc:creator>boy141</dc:creator>
      <dc:date>2020-09-16T00:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: WiNG wireless syslog for a longer period of time</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90523#M8675</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In regards to your query, the log duration is finite at either 10000 or 100000 packets. Which would not meet your requirements.&lt;BR /&gt;&lt;BR /&gt;I would suggest if possible to choose the device that has the issue the most and conduct a constant ping to this device.&lt;BR /&gt;Next time the message shows you can confirm if ping traffic has stopped.&lt;BR /&gt;I would advise pinging both from local subnet of the wireless client and subnet application server is located.&lt;BR /&gt;&lt;BR /&gt;In case you have some weird firewall or routing related issue you would be able to quickly tell where traffic stops.&lt;BR /&gt;If you server is referenced by name you might want to make sure you DNS server is not having network issues either.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2020 00:32:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90523#M8675</guid>
      <dc:creator>Daren_E</dc:creator>
      <dc:date>2020-09-16T00:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: WiNG wireless syslog for a longer period of time</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90524#M8676</link>
      <description>&lt;P&gt;The log size on Wing is not very large and depending on the syslog level, the logs could wrap in one day. I advise using an external syslog (many freeware available on the Internet), which will allow you to log as long as you wish.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2020 00:34:01 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90524#M8676</guid>
      <dc:creator>Extreme_Portal_</dc:creator>
      <dc:date>2020-09-16T00:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: WiNG wireless syslog for a longer period of time</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90525#M8677</link>
      <description>&lt;P&gt;Found the problem !&amp;nbsp; I used the suggestions above to reconcile the issue.&amp;nbsp; The application server was wonky while the network was fine.&amp;nbsp; We rebooted all the APs and that seemed to help too.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2020 21:56:59 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/wing-wireless-syslog-for-a-longer-period-of-time/m-p/90525#M8677</guid>
      <dc:creator>boy141</dc:creator>
      <dc:date>2020-09-25T21:56:59Z</dc:date>
    </item>
  </channel>
</rss>

