<?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: AP3935i error message &amp;quot;BEACON_EVENT_SWBA_SEND_FAILED&amp;quot; in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53110#M5864</link>
    <description>If you check the uptime on the access points, do the APs appear to be rebooting? There is an issue with the current v10 firmware that causes the access points to reboot randomly when they experience a high volume of broadcast traffic. We received an early release of the new AP image and it's resolved that and other issues with a customer of ours.</description>
    <pubDate>Fri, 20 May 2016 21:46:00 GMT</pubDate>
    <dc:creator>Jeff_White1</dc:creator>
    <dc:date>2016-05-20T21:46:00Z</dc:date>
    <item>
      <title>AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53104#M5858</link>
      <description>We are deploying 3935i access points and having issues. Many of them are showing an error in the ap.log "BEACON_EVENT_SWBA_SEND_FAILED"&lt;BR /&gt;
&lt;BR /&gt;
It looks to me like a firmware issue. Any idea what it really means?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 20 May 2016 17:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53104#M5858</guid>
      <dc:creator>Brian_Harmon</dc:creator>
      <dc:date>2016-05-20T17:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53105#M5859</link>
      <description>Please provide the software version that is running on the controller.</description>
      <pubDate>Fri, 20 May 2016 18:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53105#M5859</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2016-05-20T18:00:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53106#M5860</link>
      <description>Intermittent messages usually ok  if no other symptoms.  If there is a flood, then there may be an issue.&lt;BR /&gt;
&lt;BR /&gt;
    Would be nice to see the ap.log to see the msg in context. Can get that from logs-&amp;gt;ap traces-&amp;gt;select the ap and retrieve trace.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 20 May 2016 18:45:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53106#M5860</guid>
      <dc:creator>Raffi</dc:creator>
      <dc:date>2016-05-20T18:45:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53107#M5861</link>
      <description>We were on 10.01.04 firmware, went back to 10.01.03 but no change. After the "Beacon Event" msg starts the access point reboots.&lt;BR /&gt;
&lt;BR /&gt;
May 19 23:07:24 kernel: ieee80211_wireless.c:5735-ieee80211_ioctl_setparam()-IEEE80211_PARAM_AUTHMODE error=0 origval=5 value=5&lt;BR /&gt;
May 19 23:07:29 hostapd0: 03083:m2TaskApp.c:355-m2CreateQue_cmn()-name=/tHostapd0 max=32 size=1500&lt;BR /&gt;
May 19 23:07:29 kernel: m2TaskDrv.c:1538-drvIoctl()-IOCTL_M2TASK_DRV_REGISTER: tid = 32&lt;BR /&gt;
May 19 23:07:29 kernel: m2TaskDrv.c:542-m2CreateQ()-dsttid 32&lt;BR /&gt;
May 19 23:07:29 kernel: m2TaskDrv.c:555-m2CreateQ()-FULL queue creation for tid = 32&lt;BR /&gt;
May 19 23:07:29 kernel: m2TaskDrv.c:580-m2CreateQ()-dsttid 32 tabtid 32 now initialized&lt;BR /&gt;
May 19 23:07:29 hostapd0: 03083:m2TaskApp.c:428-m2CreateQue_cmn()-m2CreateQue_cmn: tid 32 MDr 40 WDr 41 Devr 43 name /tHostapd0W&lt;BR /&gt;
May 19 23:07:38 kernel: [wifi1] FWLOG: [96609] VDEV_MGR_HP_START_TIME ( 0x2, 0x96c, 0x3d9f001 )&lt;BR /&gt;
May 19 23:07:38 kernel: [wifi1] FWLOG: [96609] RESMGR_OCS_GEN_PERIODIC_NOA ( 0x1 )&lt;BR /&gt;
May 19 23:07:38 kernel: [wifi1] FWLOG: [96609] RESMGR_OCS_GEN_PERIODIC_NOA ( 0x0 )&lt;BR /&gt;
May 19 23:07:38 kernel: [wifi1] FWLOG: [96609] VDEV_MGR_AP_TBTT_CONFIG ( 0x2, 0x96c, 0x0, 0x0 )&lt;BR /&gt;
May 19 23:07:41 kernel: [wifi0] FWLOG: [136052] WAL_DBGID_SECURITY_ENCR_EN ( 0x5ae0 )&lt;BR /&gt;
May 19 23:07:41 kernel: [wifi0] FWLOG: [136052] WAL_DBGID_SECURITY_MCAST_KEY_SET ( 0x1 )&lt;BR /&gt;
May 19 23:07:41 kernel: [wifi0] FWLOG: [136053] WAL_DBGID_SECURITY_ENCR_EN ( 0x5ae0 )&lt;BR /&gt;
May 19 23:07:41 kernel: [wifi0] FWLOG: [136053] WAL_DBGID_SECURITY_MCAST_KEY_SET ( 0x2 )&lt;BR /&gt;
May 19 23:07:41 kernel: [wifi0] FWLOG: [136053] WAL_DBGID_SECURITY_ENCR_EN ( 0x5ae0 )&lt;BR /&gt;
May 19 23:07:41 kernel: [wifi0] FWLOG: [136053] WAL_DBGID_SECURITY_MCAST_KEY_SET ( 0x1 )&lt;BR /&gt;
May 19 23:07:45 kernel: [wifi1] FWLOG: [97387] BEACON_EVENT_SWBA_SEND_FAILED (  )&lt;BR /&gt;
May 19 23:07:45 kernel: [wifi1] FWLOG: [98040] BEACON_EVENT_SWBA_SEND_FAILED (  )&lt;BR /&gt;
May 19 23:07:45 kernel: [wifi1] FWLOG: [98426] BEACON_EVENT_SWBA_SEND_FAILED (  )&lt;BR /&gt;
May 19 23:07:48 kernel: [wifi1] FWLOG: [99473] BEACON_EVENT_SWBA_SEND_FAILED (  )&lt;BR /&gt;
May 19 23:07:51 kernel: [wifi1] FWLOG: [99739] BEACON_EVENT_SWBA_SEND_FAILED (  )&lt;BR /&gt;
May 19 23:07:51 kernel: [wifi1] FWLOG: [100128] BEACON_EVENT_SWBA_SEND_FAILED (  )&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 20 May 2016 18:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53107#M5861</guid>
      <dc:creator>Brian_Harmon</dc:creator>
      <dc:date>2016-05-20T18:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53108#M5862</link>
      <description>It would be good to see the entire ap trace file ( the bundle contains many files ). Perhaps best way is to open a gtac case to track the issue, and attach the trace file of the problem ap(s) to the case.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 20 May 2016 19:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53108#M5862</guid>
      <dc:creator>Raffi</dc:creator>
      <dc:date>2016-05-20T19:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53109#M5863</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
there is similar known bug.&lt;BR /&gt;
Please open a case by the GTAC.&lt;BR /&gt;
&lt;BR /&gt;
Provide techsupport_all and from at leaset 3 AP's the AP Trace log.&lt;BR /&gt;
&lt;BR /&gt;
Please try reduce multicast and broadcast as a workaround.&lt;BR /&gt;
You can use rate limit on the switch port and also on the AP side.&lt;BR /&gt;
&lt;BR /&gt;
Change on the radios setting&lt;BR /&gt;
DTIM to 2 and in the Multicast Settings  &lt;BR /&gt;
Max % of non-unicast traffic per Beacon period&lt;BR /&gt;
set it to 10%.&lt;BR /&gt;
&lt;BR /&gt;
This should provide some stability.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
&lt;BR /&gt;
Umut&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 20 May 2016 19:18:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53109#M5863</guid>
      <dc:creator>Umut_Aydin</dc:creator>
      <dc:date>2016-05-20T19:18:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53110#M5864</link>
      <description>If you check the uptime on the access points, do the APs appear to be rebooting? There is an issue with the current v10 firmware that causes the access points to reboot randomly when they experience a high volume of broadcast traffic. We received an early release of the new AP image and it's resolved that and other issues with a customer of ours.</description>
      <pubDate>Fri, 20 May 2016 21:46:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53110#M5864</guid>
      <dc:creator>Jeff_White1</dc:creator>
      <dc:date>2016-05-20T21:46:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3935i error message "BEACON_EVENT_SWBA_SEND_FAILED"</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53111#M5865</link>
      <description>Thanks all, we have GTAC involved now and they are working on it.&lt;BR /&gt;</description>
      <pubDate>Mon, 23 May 2016 18:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3935i-error-message-quot-beacon-event-swba-send-failed-quot/m-p/53111#M5865</guid>
      <dc:creator>Brian_Harmon</dc:creator>
      <dc:date>2016-05-23T18:38:00Z</dc:date>
    </item>
  </channel>
</rss>

