<?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 Issue with AP failover in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/issue-with-ap-failover/m-p/1424802#M61925</link>
    <description>&lt;P&gt;I have a WLC (4402) running version 5.2.193.0.&amp;nbsp; The WLC used to have both interfaces connected to a single switch (LAG was enabled) with etherchannel on the switch end.&amp;nbsp; It was changed such that each port on the WLC is connected to a different switch (for protection against switch failure).&amp;nbsp; After I made the configuration changes, I tested by disconnecting port 1 of the WLC from the network.&amp;nbsp; I had a wireless client performing a continuous ping on the network.&amp;nbsp; When I disconnected the cable from port 1, the ping continued uninterrupted (which is what I expected).&amp;nbsp; When I looked at the WLC, the APs had switched over to port 2.&amp;nbsp; However, when I plugged the cable back into port 1, the wireless client could no longer access the network and was unable to access the network again until after I did a manual repair on the wireless adapter.&amp;nbsp; I did not expect that.&amp;nbsp; Any thoughts on why this happened?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For reference, I've attached a partial config output from the WLC (with any identifying info stripped out). &lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 01:37:44 GMT</pubDate>
    <dc:creator>sdavids5670</dc:creator>
    <dc:date>2021-07-04T01:37:44Z</dc:date>
    <item>
      <title>Issue with AP failover</title>
      <link>https://community.cisco.com/t5/wireless/issue-with-ap-failover/m-p/1424802#M61925</link>
      <description>&lt;P&gt;I have a WLC (4402) running version 5.2.193.0.&amp;nbsp; The WLC used to have both interfaces connected to a single switch (LAG was enabled) with etherchannel on the switch end.&amp;nbsp; It was changed such that each port on the WLC is connected to a different switch (for protection against switch failure).&amp;nbsp; After I made the configuration changes, I tested by disconnecting port 1 of the WLC from the network.&amp;nbsp; I had a wireless client performing a continuous ping on the network.&amp;nbsp; When I disconnected the cable from port 1, the ping continued uninterrupted (which is what I expected).&amp;nbsp; When I looked at the WLC, the APs had switched over to port 2.&amp;nbsp; However, when I plugged the cable back into port 1, the wireless client could no longer access the network and was unable to access the network again until after I did a manual repair on the wireless adapter.&amp;nbsp; I did not expect that.&amp;nbsp; Any thoughts on why this happened?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For reference, I've attached a partial config output from the WLC (with any identifying info stripped out). &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 01:37:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/issue-with-ap-failover/m-p/1424802#M61925</guid>
      <dc:creator>sdavids5670</dc:creator>
      <dc:date>2021-07-04T01:37:44Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with AP failover</title>
      <link>https://community.cisco.com/t5/wireless/issue-with-ap-failover/m-p/1424803#M61926</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well for one... the subnet mask for the management and ap-managers are different:)&amp;nbsp; MAnagement and ap-managet vlan should be set to '0' and the trunk port should be set to switchport mode trunk native vlan 133.&amp;nbsp; Best practice to put an ip address on the service port also, but make sure it is not routable in your network.&amp;nbsp; Still reviewing the config?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Mar 2010 16:52:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/issue-with-ap-failover/m-p/1424803#M61926</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2010-03-17T16:52:12Z</dc:date>
    </item>
  </channel>
</rss>

