<?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: wireless telemetry devices monitoring system looses the connection in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43969#M7949</link>
    <description>Channelfly is off but background monitoring is running for both 2.4 and 5 ghz</description>
    <pubDate>Tue, 12 Nov 2013 12:09:28 GMT</pubDate>
    <dc:creator>chris_turner_61</dc:creator>
    <dc:date>2013-11-12T12:09:28Z</dc:date>
    <item>
      <title>wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43967#M7947</link>
      <description>I have some telemetry devices that connect wireless to a central server and display the data. It has been reported that it has started to drop the display and looses the telemetry device. I have found the below in the log for thew AP unit and wondered if any one could point me in the right direction for investigation 
&lt;BR /&gt;&lt;BR /&gt;
04:44:05 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=e0:f5:c6:78:44:0d,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=20,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(5293,644244,6197,6105909)
&lt;BR /&gt;
Nov 11 04:53:04 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=28,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(18314,20644420,25302,1040406)
&lt;BR /&gt;
Nov 11 04:53:15 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=29,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(27,22244,21,1153)
&lt;BR /&gt;
Nov 11 04:53:29 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=29,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(38,33832,31,1605)
&lt;BR /&gt;
Nov 11 04:54:50 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=27,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(168,179104,159,6645)
&lt;BR /&gt;
Nov 11 04:55:04 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=29,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(36,31272,30,1577)
&lt;BR /&gt;
Nov 11 04:55:15 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=30,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(30,26084,24,1285)
&lt;BR /&gt;
Nov 11 04:55:39 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=29,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(57,53168,50,2297)
&lt;BR /&gt;
Nov 11 04:57:17 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=6,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(1028,705448,1037,43207)
&lt;BR /&gt;
Nov 11 05:42:01 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:06:1b:b0,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=7,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(10475,6967052,12562,516680)
&lt;BR /&gt;
Nov 11 05:48:58 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:06:1b:b0,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=9,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(270,171618,319,13360)
&lt;BR /&gt;
Nov 11 06:32:02 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:06:1b:b0,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=10,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(6183,4074440,7534,310725)
&lt;BR /&gt;
Nov 11 06:37:34 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=31,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(11660,13130612,16107,661342)
&lt;BR /&gt;
Nov 11 06:37:49 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=31,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(39,35112,35,1729)
&lt;BR /&gt;
Nov 11 06:38:19 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=7,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(1425,869788,1605,67487)
&lt;BR /&gt;
Nov 11 07:01:52 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:06:1b:b0,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=6,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(5262,3512966,6436,263652)
&lt;BR /&gt;
Nov 11 07:04:55 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=9,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(595,418144,738,30906)
&lt;BR /&gt;
Nov 11 07:08:00 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=9,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(651,442908,801,33411)
&lt;BR /&gt;
Nov 11 07:14:15 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=9,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(1222,830954,1533,62268)
&lt;BR /&gt;
Nov 11 07:14:32 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=8,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(4,292,5,519)
&lt;BR /&gt;
Nov 11 07:40:41 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=8,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(3,233,5,783)
&lt;BR /&gt;
Nov 11 07:41:26 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=6,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(5,320,5,503)
&lt;BR /&gt;
Nov 11 07:42:38 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=11,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(6,360,4,465)
&lt;BR /&gt;
Nov 11 07:42:53 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=5,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(5,332,6,559)
&lt;BR /&gt;
Nov 11 07:59:59 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=0c:30:21:91:bc:de,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=5,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(4,190,2,96)
&lt;BR /&gt;
Nov 11 08:17:25 WH-AP-105 local2.alert syslog: IOCTL(89f8) failed for station  deletion -- No such file or directory(2).
&lt;BR /&gt;
Nov 11 08:19:06 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=8,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(772,806164,1327,56080)
&lt;BR /&gt;
Nov 11 08:19:18 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=10,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(16,2216,26,1409)
&lt;BR /&gt;
Nov 11 08:19:26 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=9,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(6,360,7,659)
&lt;BR /&gt;
Nov 11 08:20:17 WH-AP-105 daemon.warn Eved: MLME-REPLAYFAILURE.indication(wlan5 AES-CCM keyid=37 unicast RA:addr=c4:01:7c:45:9d:89 TA:addr=00:30:e6:05:b6:45) (pkt-rsc:0 k-&amp;gt;rsc[0]:0
&lt;BR /&gt;
Nov 11 08:54:33 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=0c:30:21:91:bc:de,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=14,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(89,7945,53,2972)
&lt;BR /&gt;
Nov 11 09:02:29 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=30,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(16556,18659979,23629,970860)
&lt;BR /&gt;
Nov 11 09:02:43 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=31,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(38,33832,31,1605)
&lt;BR /&gt;
Nov 11 09:03:30 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=32,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(98,100688,92,3997)
&lt;BR /&gt;
Nov 11 09:04:10 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:b3,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=32,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(89,90408,82,3629)
&lt;BR /&gt;
Nov 11 09:04:11 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:05:b6:45,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=35,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(7206,5783802,9010,375921)
&lt;BR /&gt;
Nov 11 09:04:12 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=8,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(491,322750,490,20651)
&lt;BR /&gt;
Nov 11 09:04:15 WH-AP-105 kern.warn kernel: ath_dump_rxactivity: jiffies=490712283 last=490712229 lastpanic=0 rxpanic=0 thr=10000 inactive=54 
&lt;BR /&gt;
Nov 11 09:04:15 WH-AP-105 kern.warn kernel: wifi0: ath_watchdog: hardware error; resetting
&lt;BR /&gt;
Nov 11 09:04:20 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:04:b6:d7,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=7,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(5,320,6,481)
&lt;BR /&gt;
Nov 11 09:23:41 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:06:1b:b0,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=13,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(4635,3015008,5560,228082)
&lt;BR /&gt;
Nov 11 09:54:42 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=0c:30:21:91:bc:de,func=ieee80211_input,line=1675,hint=received IEEE80211_FC0_SUBTYPE_DISASSOC,rx_rssi=13,ack_rssi=0,reason=0,freq=2437,chan=6,stats=(283,20700,91,6519)
&lt;BR /&gt;
Nov 11 09:58:06 WH-AP-105 daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:30:e6:06:1b:b0,func=ieee80211_input,line=1675,hint=received</description>
      <pubDate>Tue, 12 Nov 2013 09:53:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43967#M7947</guid>
      <dc:creator>chris_turner_61</dc:creator>
      <dc:date>2013-11-12T09:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43968#M7948</link>
      <description>You have ChannelFly ON or OFF?</description>
      <pubDate>Tue, 12 Nov 2013 11:42:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43968#M7948</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2013-11-12T11:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43969#M7949</link>
      <description>Channelfly is off but background monitoring is running for both 2.4 and 5 ghz</description>
      <pubDate>Tue, 12 Nov 2013 12:09:28 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43969#M7949</guid>
      <dc:creator>chris_turner_61</dc:creator>
      <dc:date>2013-11-12T12:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43970#M7950</link>
      <description>The telemetry device has a built in WLAN or are you using something to connect it to?
&lt;BR /&gt;&lt;BR /&gt;
Does ti have an ETH port?
&lt;BR /&gt;&lt;BR /&gt;
Which APs are you using?</description>
      <pubDate>Tue, 12 Nov 2013 13:55:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43970#M7950</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2013-11-12T13:55:41Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43971#M7951</link>
      <description>This one is bothersome: 
&lt;BR /&gt;&lt;BR /&gt;
Nov 11 09:04:15 WH-AP-105 kern.warn kernel: wifi0: ath_watchdog: hardware error; resetting</description>
      <pubDate>Tue, 12 Nov 2013 15:03:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43971#M7951</guid>
      <dc:creator>keith_redfield</dc:creator>
      <dc:date>2013-11-12T15:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43972#M7952</link>
      <description>they have built in wireless cards the AP are 7363</description>
      <pubDate>Tue, 12 Nov 2013 15:47:36 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43972#M7952</guid>
      <dc:creator>chris_turner_61</dc:creator>
      <dc:date>2013-11-12T15:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43973#M7953</link>
      <description>do you mean the point is bothersome as in faulty?</description>
      <pubDate>Tue, 12 Nov 2013 15:52:03 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43973#M7953</guid>
      <dc:creator>chris_turner_61</dc:creator>
      <dc:date>2013-11-12T15:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: wireless telemetry devices monitoring system looses the connection</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43974#M7954</link>
      <description>That's the most likely cause - so please open a support case.</description>
      <pubDate>Tue, 12 Nov 2013 17:29:34 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/wireless-telemetry-devices-monitoring-system-looses-the/m-p/43974#M7954</guid>
      <dc:creator>keith_redfield</dc:creator>
      <dc:date>2013-11-12T17:29:34Z</dc:date>
    </item>
  </channel>
</rss>

