<?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: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3823993#M93350</link>
    <description>&lt;P&gt;Hi Mats,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do a "sh pmk-cache &amp;lt;Philips_MAC_Address&amp;gt;" to see if the devices are showing up in the WLC's PMK cache.&amp;nbsp; This should facilitate "fast-roam-back" as long as the device offers a PMKID in the Reassociation Request.&amp;nbsp; How often is PEAP failing?&amp;nbsp; Can you disable DHCP Required?&lt;SPAN style="display: inline !important; float: none; background-color: transparent; color: #58585b; cursor: text; font-family: 'CiscoSans','Helvetica Neue',Helvetica,Arial,sans-serif; font-size: 16px; font-style: normal; font-variant: normal; font-weight: 300; letter-spacing: normal; line-height: 27.42px; orphans: 2; text-align: left; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;"&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 21 Mar 2019 23:51:40 GMT</pubDate>
    <dc:creator>wififofum</dc:creator>
    <dc:date>2019-03-21T23:51:40Z</dc:date>
    <item>
      <title>Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3799433#M93327</link>
      <description>&lt;P&gt;Hi collegues.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have been struggling to get Philips Intellivue MX40 and X2 to stay connected without any drops on a shared SSID using WPA2 AES EAP with PKC/OKC.&lt;/P&gt;
&lt;P&gt;Philips X3 models have no issues at all.&lt;/P&gt;
&lt;P&gt;PMK rekey negotiations seems to be problematic with these types.&lt;/P&gt;
&lt;P&gt;We did have similar issues with Spectralink earlier but these were resolved when they were exchanged to a later revision/version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I checked with collegues they all say that Philips X2/MX40 do not work on wireless EAP, and had to resort för PSK MAB.&lt;/P&gt;
&lt;P&gt;Later I heard of another hospital that had implemented these with success, but when I checked the story it became evident that they were using 2702i APs. They had a snaller zone with 2802i APs, and there is didn't work!&lt;/P&gt;
&lt;P&gt;Their settings were identical to ours except for the access points.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So it looks like the combination of Philips X2 and MX40 with Cisco 2802i running on AireOS 8.3.143.0 works badly causing disconnects and micro drops in the the telemetry data.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyone who has a working solution with above equipment?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here's the overall settings on the SSID:&lt;/P&gt;
&lt;P&gt;Network Name (SSID).............................. &amp;lt;SHARED-WLAN_X&amp;gt;&lt;BR /&gt;Status........................................... Enabled&lt;BR /&gt;MAC Filtering.................................... Disabled&lt;BR /&gt;Broadcast SSID................................... Enabled&lt;BR /&gt;AAA Policy Override.............................. Enabled&lt;BR /&gt;Network Admission Control&lt;BR /&gt;Client Profiling Status&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Radius Profiling ............................ Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DHCP ....................................... Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP ....................................... Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Profiling ............................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DHCP ....................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP ....................................... Disabled&lt;BR /&gt;&amp;nbsp; Radius-NAC State............................... Enabled&lt;BR /&gt;&amp;nbsp; SNMP-NAC State................................. Disabled&lt;BR /&gt;&amp;nbsp; Quarantine VLAN................................ 0&lt;BR /&gt;Maximum Clients Allowed.......................... Unlimited&lt;BR /&gt;Maximum number of Clients per AP Radio........... 200&lt;BR /&gt;ATF Policy....................................... 0&lt;BR /&gt;Number of Active Clients......................... 131&lt;BR /&gt;Exclusionlist Timeout............................ 60 seconds&lt;BR /&gt;Session Timeout.................................. 86400 seconds&lt;BR /&gt;User Idle Timeout................................ Disabled&lt;BR /&gt;Sleep Client..................................... disable&lt;BR /&gt;Sleep Client Timeout............................. 720 minutes&lt;BR /&gt;User Idle Threshold.............................. 70 Bytes&lt;BR /&gt;NAS-identifier................................... none&lt;BR /&gt;CHD per WLAN..................................... Enabled&lt;BR /&gt;Webauth DHCP exclusion........................... Disabled&lt;BR /&gt;Interface........................................ &amp;lt;Interface_name&amp;gt;&lt;BR /&gt;Multicast Interface.............................. Not Configured&lt;BR /&gt;WLAN IPv4 ACL.................................... unconfigured&lt;BR /&gt;WLAN IPv6 ACL.................................... unconfigured&lt;BR /&gt;WLAN Layer2 ACL.................................. unconfigured&lt;BR /&gt;WLAN URL ACL..................................... unconfigured&lt;BR /&gt;mDNS Status...................................... Enabled&lt;BR /&gt;mDNS Profile Name................................ &amp;lt;mdns-profile-name&amp;gt;&lt;BR /&gt;DHCP Server...................................... Default&lt;BR /&gt;DHCP Address Assignment Required................. Enabled&lt;BR /&gt;Static IP client tunneling....................... Disabled&lt;BR /&gt;Tunnel Profile................................... Unconfigured&lt;BR /&gt;PMIPv6 Mobility Type............................. none&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PMIPv6 MAG Profile........................... Unconfigured&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PMIPv6 Default Realm......................... Unconfigured&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PMIPv6 NAI Type.............................. Hexadecimal&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PMIPv6 MAG location.......................... WLC&lt;BR /&gt;Quality of Service............................... Platinum&lt;BR /&gt;Per-SSID Rate Limits............................. Upstream&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Downstream&lt;BR /&gt;Average Data Rate................................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Average Realtime Data Rate.......................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Burst Data Rate..................................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Burst Realtime Data Rate.........................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Per-Client Rate Limits........................... Upstream&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Downstream&lt;BR /&gt;Average Data Rate................................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Average Realtime Data Rate.......................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Burst Data Rate..................................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Burst Realtime Data Rate.........................&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;Scan Defer Priority.............................. 4,5,6&lt;BR /&gt;Scan Defer Time.................................. 1800 milliseconds&lt;BR /&gt;WMM.............................................. Allowed&lt;BR /&gt;WMM UAPSD Compliant Client Support............... Disabled&lt;BR /&gt;Media Stream Multicast-direct.................... Disabled&lt;BR /&gt;CCX - AironetIe Support.......................... Enabled&lt;BR /&gt;CCX - Gratuitous ProbeResponse (GPR)............. Disabled&lt;BR /&gt;CCX - Diagnostics Channel Capability............. Disabled&lt;BR /&gt;Dot11-Phone Mode (7920).......................... Disabled&lt;BR /&gt;Wired Protocol................................... None&lt;BR /&gt;Passive Client Feature........................... Disabled&lt;BR /&gt;Peer-to-Peer Blocking Action..................... Disabled&lt;BR /&gt;Radio Policy..................................... All&lt;BR /&gt;DTIM period for 802.11a radio.................... 1&lt;BR /&gt;DTIM period for 802.11b radio.................... 1&lt;BR /&gt;Radius Servers&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Authentication................................ &amp;lt;ISE-Server-01&amp;gt; 1812 *&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Authentication................................ &amp;lt;ISE-Server-02&amp;gt; 1812 *&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Accounting.................................... &amp;lt;ISE-Server-01&amp;gt; 1813 *&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Accounting.................................... &amp;lt;ISE-Server-02&amp;gt; 1813 *&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Interim Update............................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Interim Update Interval.................... 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Framed IPv6 Acct AVP ...................... Prefix&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Dynamic Interface............................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Dynamic Interface Priority.................... wlan&lt;BR /&gt;Local EAP Authentication......................... Disabled&lt;BR /&gt;Radius NAI-Realm................................. Disabled&lt;BR /&gt;Mu-Mimo.......................................... Enabled&lt;BR /&gt;Security&lt;BR /&gt;&amp;nbsp;&amp;nbsp; 802.11 Authentication:........................ Open System&lt;BR /&gt;&amp;nbsp;&amp;nbsp; FT Support.................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Static WEP Keys............................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; 802.1X........................................ Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Wi-Fi Protected Access (WPA/WPA2)............. Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; WPA (SSN IE)............................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; WPA2 (RSN IE).............................. Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TKIP Cipher............................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AES Cipher.............................. Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CCMP256 Cipher.......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; GCMP128 Cipher.......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; GCMP256 Cipher.......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; OSEN IE.................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Auth Key Management&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 802.1x.................................. Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PSK..................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CCKM.................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; FT-1X(802.11r).......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; FT-PSK(802.11r)......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PMF-1X(802.11w)......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PMF-PSK(802.11w)........................ Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; OSEN-1X................................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SUITEB-1X............................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SUITEB192-1X............................ Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; FT Reassociation Timeout................... 20&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; FT Over-The-DS mode........................ Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; GTK Randomization.......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SKC Cache Support.......................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CCKM TSF Tolerance......................... 1000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Wi-Fi Direct policy configured................ xconnect-not-allowed&lt;BR /&gt;&amp;nbsp;&amp;nbsp; EAP-Passthrough............................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; CKIP ......................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Web Based Authentication...................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Web Authentication Timeout.................... 300&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Web-Passthrough............................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Mac-auth-server............................... 0.0.0.0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Web-portal-server............................. 0.0.0.0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Conditional Web Redirect...................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Splash-Page Web Redirect...................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Auto Anchor................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; FlexConnect Local Switching................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; FlexConnect Central Association............... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; flexconnect Central Dhcp Flag................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; flexconnect nat-pat Flag...................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; flexconnect Dns Override Flag................. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; flexconnect PPPoE pass-through................ Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; flexconnect local-switching IP-source-guar.... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; FlexConnect Vlan based Central Switching ..... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; FlexConnect Local Authentication.............. Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; FlexConnect Learn IP Address.................. Enabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Client MFP.................................... Optional&lt;BR /&gt;&amp;nbsp;&amp;nbsp; PMF........................................... Disabled&lt;BR /&gt;&amp;nbsp;&amp;nbsp; PMF Association Comeback Time................. 1&lt;BR /&gt;&amp;nbsp;&amp;nbsp; PMF SA Query RetryTimeout..................... 200&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Tkip MIC Countermeasure Hold-down Timer....... 60&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Eap-params.................................... Disabled&lt;BR /&gt;AVC Visibilty.................................... Enabled&lt;BR /&gt;AVC Profile Name................................. None&lt;BR /&gt;Flow Monitor Name................................ NetFlow Monitor&lt;BR /&gt;Split Tunnel Configuration&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Split Tunnel................................. Disabled&lt;BR /&gt;Call Snooping.................................... Disabled&lt;BR /&gt;Roamed Call Re-Anchor Policy..................... Disabled&lt;BR /&gt;SIP CAC Fail Send-486-Busy Policy................ Enabled&lt;BR /&gt;SIP CAC Fail Send Dis-Association Policy......... Disabled&lt;BR /&gt;KTS based CAC Policy............................. Disabled&lt;BR /&gt;Assisted Roaming Prediction Optimization......... Disabled&lt;BR /&gt;802.11k Neighbor List............................ Disabled&lt;BR /&gt;802.11k Neighbor List Dual Band.................. Disabled&lt;BR /&gt;802.11v Directed Multicast Service............... Disabled&lt;BR /&gt;802.11v BSS Max Idle Service..................... Disabled&lt;BR /&gt;802.11v BSS Transition Service................... Disabled&lt;BR /&gt;802.11v BSS Transition Disassoc Imminent......... Disabled&lt;BR /&gt;802.11v BSS Transition Disassoc Timer............ 200&lt;BR /&gt;802.11v BSS Transition OpRoam Disassoc Timer..... 40&lt;BR /&gt;DMS DB is empty&lt;BR /&gt;Band Select...................................... Enabled&lt;BR /&gt;Load Balancing................................... Client-Count Based&lt;BR /&gt;Multicast Buffer................................. Disabled&lt;BR /&gt;Universal Ap Admin............................... Disabled&lt;BR /&gt;Broadcast Tagging................................ Disabled&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 16:50:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3799433#M93327</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2021-07-05T16:50:00Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3799581#M93329</link>
      <description>&lt;P&gt;Just want to confirm that the MX40 actually associates and authenticates to the SSID and then experiences drop outs?&lt;/P&gt;
&lt;P&gt;Are other devices also experiencing this?&lt;/P&gt;
&lt;P&gt;Do these devices drop out when they are not moving, or is it on a roam?&lt;/P&gt;
&lt;P&gt;Take it a wireless survey has been conducted to make sure that required data rates, SNR and RSSI is being achieved in the areas.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You have probably seen this but make sure you are meeting all the requirements of the install and service guide:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://incenter.medical.philips.com/doclib/enc/fetch/2000/4504/577242/577243/577247/582636/582882/MX40_B.0_Service_Guide.pdf?nodeid=10668578&amp;amp;ver" target="_self"&gt;http://incenter.medical.philips.com/doclib/enc/fetch/2000/4504/577242/577243/577247/582636/582882/MX40_B.0_Service_Guide.pdf?nodeid=10668578&amp;amp;ver&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 21:23:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3799581#M93329</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2019-02-11T21:23:48Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3800777#M93333</link>
      <description>Can you please run a 'debug client mac-address' on the WLC via SSH while one is connected and then try to roam or wait for the PMK to happen?&lt;BR /&gt;To turn debug off, issue 'debug disable-all'.&lt;BR /&gt;I wonder what will happen. &lt;BR /&gt;</description>
      <pubDate>Wed, 13 Feb 2019 10:20:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3800777#M93333</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-13T10:20:14Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3800815#M93335</link>
      <description>&lt;P&gt;Oh yes. The units do associate, but doing some debugging on the ISE gives more information since it seems the units fail to comply to PEAP standard. In the wlc debug client xxx the dropouts seems to coincide with EAP rekey auth and the reason was spot on when tracing the same client in ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I suspect this behavior is caused by the clients trying to enforce SKC instead of OKC/PKC. SKC is not supported due to its limitations on a large network.&lt;/P&gt;
&lt;P&gt;(Please note that we don't use 2.4GHz but utilize 5GHz instead. but the requirements for Philips Intellivue have been validated by Philips technicians.)&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Philips MX40 - 00-09-fb-a5-52-71 unexpected renegotiation.PNG" style="width: 617px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/29996i0ECA5BC40299D44E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Philips MX40 - 00-09-fb-a5-52-71 unexpected renegotiation.PNG" alt="Philips MX40 - 00-09-fb-a5-52-71 unexpected renegotiation.PNG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Philips MX40 - 00-09-fb-a5-52-71 unexpected renegotiation_authz.PNG" style="width: 615px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/29997iD651B4025DA8D1D5/image-size/large?v=v2&amp;amp;px=999" role="button" title="Philips MX40 - 00-09-fb-a5-52-71 unexpected renegotiation_authz.PNG" alt="Philips MX40 - 00-09-fb-a5-52-71 unexpected renegotiation_authz.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will try and process the wlc debug on the same clients.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sincere Regards&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 11:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3800815#M93335</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2019-02-13T11:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3800986#M93337</link>
      <description>Thanks, I think that is not needed in this case, because if the radius sends a "Reject", then the client must be dropped. I guess it's also time to involve Philips for this issue.</description>
      <pubDate>Wed, 13 Feb 2019 14:24:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3800986#M93337</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-13T14:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801594#M93339</link>
      <description>&lt;P&gt;Yes, I have forwarded the debugs and traces to Philips to investigate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the debug I could find some code 17 from the access points that seemed out of scope since we use RF profiles that sets maximum clients to 200, but generates a trap when exceeding 12 clients per AP.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Feb 13 08:59:45.479 &amp;nbsp;&amp;nbsp; &amp;nbsp;*apfMsConnTask_5 &amp;nbsp;&amp;nbsp; &amp;nbsp;WLC/AP is sending an Association Response to the client with status code 17 = AP has reached the maximum supported clients&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;This must be a bug?&lt;/P&gt;
&lt;P&gt;Because the maximum client threshold is set in the high density tab; at lest I thought so...&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RF profile default RRM profile threshold.PNG" style="width: 279px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/30061iBAC57B127DB7F505/image-size/large?v=v2&amp;amp;px=999" role="button" title="RF profile default RRM profile threshold.PNG" alt="RF profile default RRM profile threshold.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Default RRM trap threshold (above)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RF profile applied RRM profile threshold.PNG" style="width: 663px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/30062i98987D8FCB46A12C/image-size/large?v=v2&amp;amp;px=999" role="button" title="RF profile applied RRM profile threshold.PNG" alt="RF profile applied RRM profile threshold.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Altered trap threshold (above) is the updated RF profile setting, but sholdn't the high density tab/parameters set the maximum client cap?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RF profile applied high density threshold.PNG" style="width: 551px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/30064i0E397CEE4C8B516E/image-size/large?v=v2&amp;amp;px=999" role="button" title="RF profile applied high density threshold.PNG" alt="RF profile applied high density threshold.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;May be this behavior is limited to 2802 access points?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 08:10:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801594#M93339</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2019-02-14T08:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801597#M93340</link>
      <description>Not sure, but the Traps threshold is only generating a trap and I thought it should not inform the client about it, only the SNMP receiver. In any case, increase the limit to 50, just to be sure.&lt;BR /&gt;Also make sure it's correctly configured in the SSID under Advanced -&amp;gt; Maximum allowed clients. Set it to 0 to have no limit.</description>
      <pubDate>Thu, 14 Feb 2019 08:29:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801597#M93340</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-14T08:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801598#M93341</link>
      <description>Forgot one thing.&lt;BR /&gt;&lt;BR /&gt;Make sure you have Client Load Balancing disabled on the SSID, or configure it differently under Wireless -&amp;gt; Advanced -&amp;gt; Load Balancing.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Feb 2019 08:31:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801598#M93341</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-14T08:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801616#M93342</link>
      <description>&lt;P&gt;Yes, thats what I thought, but since this is the ONLY difference I can find that can cause this anomaly I played this safe and updated the trap setting. In the SSID advanced settings are ok:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SSID maximum client setting.PNG" style="width: 246px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/30065i64A54CEFBC86B544/image-size/large?v=v2&amp;amp;px=999" role="button" title="SSID maximum client setting.PNG" alt="SSID maximum client setting.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;If I check the radio performance settings on the access point I find it does follow the trap settings in the RF profile and not the high density settings or the&amp;nbsp; the SSID settings!&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AP performance profile#12 client.PNG" style="width: 419px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/30066iC3915C3DB4BCC77E/image-size/large?v=v2&amp;amp;px=999" role="button" title="AP performance profile#12 client.PNG" alt="AP performance profile#12 client.PNG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AP performance profile.PNG" style="width: 389px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/30068iE6FBA36BF0F0C87B/image-size/large?v=v2&amp;amp;px=999" role="button" title="AP performance profile.PNG" alt="AP performance profile.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I also notice the the globally controlled setting has been omitted, but it does follow the settings in the RF profile RRM traps.&lt;/P&gt;
&lt;P&gt;Any idea why? No logic in this behavior...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 08:56:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801616#M93342</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2019-02-14T08:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801623#M93343</link>
      <description>I don't use those profiles, never have. Only manually configured each setting.</description>
      <pubDate>Thu, 14 Feb 2019 09:03:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801623#M93343</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-14T09:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801628#M93344</link>
      <description>&lt;P&gt;Unless we disable the load balancing setting, what do you recommend for client window size and denial count?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;/Mats&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 09:10:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801628#M93344</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2019-02-14T09:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801635#M93345</link>
      <description>I never liked load balancing, because it disrupts the client decision algorithm for roaming/attaching to an AP. In the end, it's always the client that decides when and where to roam and unless the driver of that client honors "weird" behavior of the AP, it will cause latency issues and sometimes no roamings at all.&lt;BR /&gt;&lt;BR /&gt;Because of this, I always left this feature disabled, together with client band select.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Feb 2019 09:18:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801635#M93345</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-14T09:18:44Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801659#M93346</link>
      <description>&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;I will consider doing this at the next change since any changes on the SSID will cause a short disruption.&lt;/P&gt;
&lt;P&gt;In the meantime I have increased the window size to 10.&lt;/P&gt;
&lt;P&gt;We do have Spectralink 2142 that after a firmware update works excellent with the same settings and infrastructure, but on a different site.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;/Mats&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll keep this thread updated for any progress regarding this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 09:47:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801659#M93346</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2019-02-14T09:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801674#M93347</link>
      <description>That reminds me, you have the SSID available on both frequencies (2.4 and 5 GHz), right? Otherwise you must disable Load Balancing if I remember correctly.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Feb 2019 10:00:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801674#M93347</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-14T10:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801780#M93348</link>
      <description>&lt;P&gt;No, it's dual band, but load balancing shouldn't be impaired using single radio policy; you wasn't thinking of band-select?&lt;/P&gt;
&lt;P&gt;I haven't heard this before. Are you sure?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 11:59:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801780#M93348</guid>
      <dc:creator>Mats Nilson</dc:creator>
      <dc:date>2019-02-14T11:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801795#M93349</link>
      <description>I think you're right and I mixed them up. In any case, here is the theory behind those two features: &lt;A href="https://community.cisco.com/t5/wireless-mobility-documents/load-balancing-and-band-select-on-the-cisco-wireless-lan/ta-p/3128513#toc-hId--86706536" target="_blank"&gt;https://community.cisco.com/t5/wireless-mobility-documents/load-balancing-and-band-select-on-the-cisco-wireless-lan/ta-p/3128513#toc-hId--86706536&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Feb 2019 12:24:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3801795#M93349</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-02-14T12:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Philips Intellivue MX40 and interoperability issues when using AP2802i and 802.1x</title>
      <link>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3823993#M93350</link>
      <description>&lt;P&gt;Hi Mats,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do a "sh pmk-cache &amp;lt;Philips_MAC_Address&amp;gt;" to see if the devices are showing up in the WLC's PMK cache.&amp;nbsp; This should facilitate "fast-roam-back" as long as the device offers a PMKID in the Reassociation Request.&amp;nbsp; How often is PEAP failing?&amp;nbsp; Can you disable DHCP Required?&lt;SPAN style="display: inline !important; float: none; background-color: transparent; color: #58585b; cursor: text; font-family: 'CiscoSans','Helvetica Neue',Helvetica,Arial,sans-serif; font-size: 16px; font-style: normal; font-variant: normal; font-weight: 300; letter-spacing: normal; line-height: 27.42px; orphans: 2; text-align: left; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;"&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2019 23:51:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/philips-intellivue-mx40-and-interoperability-issues-when-using/m-p/3823993#M93350</guid>
      <dc:creator>wififofum</dc:creator>
      <dc:date>2019-03-21T23:51:40Z</dc:date>
    </item>
  </channel>
</rss>

