<?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: Unleashed R710s suspending Intermec hand held mobile computers in Unleashed</title>
    <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3977#M165</link>
    <description>Hi Bob,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; To be fair I need to give our partners and tech support experts the opportunity&lt;BR /&gt;to help diagnose and offer best advice.&amp;nbsp; I was a TSE here and worked Intermec/ZD&lt;BR /&gt;environments, and Unleashed is our "controller independant" brand that comes from &lt;BR /&gt;ZoneDirector base, and/so should be similar for troubleshooting the logs needed to &lt;BR /&gt;accurately understand what is happening.&amp;nbsp; Call and ask for a ticket, and ask for help&lt;BR /&gt;to track a known/problem (if you can identify one) scanner client activity.&amp;nbsp; They will &lt;BR /&gt;want to know if problems are seen around any one AP or area, etc too.&amp;nbsp; Waking up&lt;BR /&gt;a scanner before 30 minutes (def timeout) and after (to see if 500 is honored) might&lt;BR /&gt;be helpful.&amp;nbsp; And... are the Intermecs on their latest drivers is also important, thanks.&amp;nbsp;</description>
    <pubDate>Mon, 30 Apr 2018 20:32:28 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2018-04-30T20:32:28Z</dc:date>
    <item>
      <title>Unleashed R710s suspending Intermec hand held mobile computers</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3974#M162</link>
      <description>We have a dozen R710s running as an&amp;nbsp; Unleashed Network in a factory and warehouse.&amp;nbsp; There are 3 SSIDs on this.&amp;nbsp; One for corporate people, one for guests and the last for the RF barcode scanner users in the factory.&amp;nbsp; These bar code uses run a telnet session on Honeywell CK75 mobile computers.&lt;BR /&gt;&lt;BR /&gt;The devices connect to the Georgia Softworks Telnet Server running on Windows.&lt;BR /&gt;&lt;BR /&gt;There are about a dozen bar code users.&amp;nbsp; They connect and run fine for a while and then the session gets suspended in terms of the telnet connection.&amp;nbsp; This causes everything to stop until the user generates more activity to jump start the process forward again.&lt;BR /&gt;&lt;BR /&gt;The devices are set no to hibernate.&amp;nbsp; They do cause the screen to blank after 5 minutes but the radio stays connected to maintain the telnet session.&lt;BR /&gt;&lt;BR /&gt;The specific SSID has the inactivity timeout set to 500 minutes.&amp;nbsp; That was the default 10 minutes last week.&amp;nbsp; I changed it over the weekend but it does not appear to have fixed anything.&amp;nbsp; I assume these settings are dynamic and do not require a restart.&lt;BR /&gt;&lt;BR /&gt;As of this morning, the users of the mobile computers keep having their sessions get suspended.&amp;nbsp; Are their other settings for the SSID that might impact what I see?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Bob Brennan&lt;BR /&gt;IMS, Inc.</description>
      <pubDate>Mon, 30 Apr 2018 17:35:58 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3974#M162</guid>
      <dc:creator>bob_brennan_697</dc:creator>
      <dc:date>2018-04-30T17:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: Unleashed R710s suspending Intermec hand held mobile computers</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3975#M163</link>
      <description>Hi Bob,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Scanners running Telnet applications are very touchy, since Telnet is time sensitive.&lt;BR /&gt;You have increased the inactivity timeout correctly to maintain authorization, but there&lt;BR /&gt;may be other tweaks (DTIM, no AP background scanning) that might help further, as&lt;BR /&gt;described in this 2014 Ruckus/Intermec guide.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/answers/000004135" rel="nofollow" title="Link: https://support.ruckuswireless.com/answers/000004135"&gt;https://support.ruckuswireless.com/answers/000004135&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;I've just made this document visible, so it will appear on Support after the next 6hr update&lt;BR /&gt;period.</description>
      <pubDate>Mon, 30 Apr 2018 18:04:49 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3975#M163</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-04-30T18:04:49Z</dc:date>
    </item>
    <item>
      <title>Re: Unleashed R710s suspending Intermec hand held mobile computers</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3976#M164</link>
      <description>Thank you Michael,&lt;BR /&gt;&lt;BR /&gt;I will review these settings.&amp;nbsp; I know that we set the inactivity timeout to 500.&amp;nbsp; We stopped background scanning.&amp;nbsp; I need to look at the other suggestions.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Another weird bit to add.&amp;nbsp; We have a few clients in the suspended state as seen from the telnet server.&amp;nbsp; I would expect that if I send a PING to each of the suspended processes that it would wake up.&amp;nbsp; That does not seem to be the case and I am working with GSW to understand this mechanism better.&lt;BR /&gt;&lt;BR /&gt;We have a handful of warehouses deployed with the same gear except this one uses unleashed instead of a ZD.&amp;nbsp; My larger concern is that I have 3 more systems just like this ready to install.&amp;nbsp; I'd like to avoid this issue at these new site, if possible.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Bob&amp;nbsp;</description>
      <pubDate>Mon, 30 Apr 2018 20:16:23 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3976#M164</guid>
      <dc:creator>bob_brennan_697</dc:creator>
      <dc:date>2018-04-30T20:16:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unleashed R710s suspending Intermec hand held mobile computers</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3977#M165</link>
      <description>Hi Bob,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; To be fair I need to give our partners and tech support experts the opportunity&lt;BR /&gt;to help diagnose and offer best advice.&amp;nbsp; I was a TSE here and worked Intermec/ZD&lt;BR /&gt;environments, and Unleashed is our "controller independant" brand that comes from &lt;BR /&gt;ZoneDirector base, and/so should be similar for troubleshooting the logs needed to &lt;BR /&gt;accurately understand what is happening.&amp;nbsp; Call and ask for a ticket, and ask for help&lt;BR /&gt;to track a known/problem (if you can identify one) scanner client activity.&amp;nbsp; They will &lt;BR /&gt;want to know if problems are seen around any one AP or area, etc too.&amp;nbsp; Waking up&lt;BR /&gt;a scanner before 30 minutes (def timeout) and after (to see if 500 is honored) might&lt;BR /&gt;be helpful.&amp;nbsp; And... are the Intermecs on their latest drivers is also important, thanks.&amp;nbsp;</description>
      <pubDate>Mon, 30 Apr 2018 20:32:28 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-R710s-suspending-Intermec-hand-held-mobile-computers/m-p/3977#M165</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-04-30T20:32:28Z</dc:date>
    </item>
  </channel>
</rss>

