<?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: Controller connectivity in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4862079#M257453</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/327027"&gt;@susim&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;SPAN&gt;Although I have conducted some experiments&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Configuring the 9800 as a Layer 3 -&amp;nbsp; That is a very dangerous precedence.&amp;nbsp; Please share why (or what) is the business case to allow the 9800 to participate in the routing process because the machine may not have enough memory &amp;amp;/or CPU.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;This may work in a lab (or experiments), demo or in really small network sizes but it may have difficulties scaling in large to enterprise sized networks.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 25 Jun 2023 23:30:22 GMT</pubDate>
    <dc:creator>Leo Laohoo</dc:creator>
    <dc:date>2023-06-25T23:30:22Z</dc:date>
    <item>
      <title>Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859121#M257319</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In the&amp;nbsp; below&amp;nbsp; design guide&amp;nbsp; explains only layer 2 connectivity&amp;nbsp; ( wlc to the upstream switch )&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Please&amp;nbsp; guide&amp;nbsp; layer 3 implementation for the same&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 05:40:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859121#M257319</guid>
      <dc:creator>susim</dc:creator>
      <dc:date>2023-06-21T05:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859536#M257333</link>
      <description>&lt;P&gt;Dear Susim,&lt;/P&gt;&lt;P&gt;Please go through this link. Hope you found some information needed.&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/16-12/config-guide/b_wl_16_12_cg/m_config-wmi.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/16-12/config-guide/b_wl_16_12_cg/m_config-wmi.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;GoodLuck..&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 13:45:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859536#M257333</guid>
      <dc:creator>Gaurav  Kansal</dc:creator>
      <dc:date>2023-06-21T13:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859570#M257339</link>
      <description>&lt;P&gt;Refer the&amp;nbsp;Wireless management IP addressing section from the following c9800 best practices guide.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#WirelessmanagementIPaddressing" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#WirelessmanagementIPaddressing&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;CJ&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 14:21:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859570#M257339</guid>
      <dc:creator>jagan.chowdam</dc:creator>
      <dc:date>2023-06-21T14:21:48Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859861#M257363</link>
      <description>&lt;P&gt;WLC act as a L2 device, in that way you should have SVI for wireless management on a upstream switch and WLC need to trunk back to upstream switch.&lt;/P&gt;
&lt;P&gt;HTH&lt;BR /&gt;Rasika&lt;BR /&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 21:52:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859861#M257363</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2023-06-21T21:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859971#M257374</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/324872"&gt;@Rasika Nayanajith&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="wlc l3.JPG" style="width: 492px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/188172i4E3C5D6AD469F00F/image-size/large?v=v2&amp;amp;px=999" role="button" title="wlc l3.JPG" alt="wlc l3.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The above&amp;nbsp; solution given&amp;nbsp; by consultant . So far my implementation was like you said .&lt;/P&gt;&lt;P&gt;Previously, my implementation consisted of a distribution switch and core switch configuration. However, it has now transitioned to a collapsed core architecture based on your recommendation. The consultant's suggestion aligns with this approach, advocating for routing functionality to be centralized solely in the collapsed core.&lt;/P&gt;&lt;P&gt;Can you please advise&amp;nbsp; on the above topology&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2023 06:02:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4859971#M257374</guid>
      <dc:creator>susim</dc:creator>
      <dc:date>2023-06-22T06:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4861019#M257402</link>
      <description>&lt;P&gt;It is not possible to have /30 L3 links for WLC connectivity. It must be Trunk link which connect WLC &amp;amp; upstream switch. Here are the supported setup for SSO. That upstream switches should support VSS/vPC or HSRP in order to make it work.(red links are trunk links in below diagram)&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="Screenshot 2023-06-23 at 7.28.32 am.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/188300iCCD896703BE6FFD5/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2023-06-23 at 7.28.32 am.png" alt="Screenshot 2023-06-23 at 7.28.32 am.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Here is the good Ciscolive presentation if you like to go through WLC high availability configurations. You can watch recorded session from ciscolive.com (can create free account if you don't have one yet)&lt;BR /&gt;&lt;A href="https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2022/pdf/BRKEWN-2846.pdf" target="_self"&gt;https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2022/pdf/BRKEWN-2846.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;BR /&gt;Rasika&lt;BR /&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2023 21:32:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4861019#M257402</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2023-06-22T21:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4861948#M257448</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thank you for your valuable suggestions.I know that I can trust and rely on the advice of Mr. &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/324872"&gt;@Rasika Nayanajith&lt;/a&gt;&amp;nbsp;. There is no need for hesitation or doubt when considering his guidance.&lt;BR /&gt;Although I have conducted some experiments, such as implementing an L3 link between the WLC and the core, as per the earlier posted topology..."&lt;BR /&gt;All the ssid gateway's are on the wlc&lt;BR /&gt;static route made from core to vlans(ssid) to the wlc&lt;/P&gt;&lt;P&gt;So far accesspoints are registering (AP's are in local mode ) and ssid's are working as expected&lt;BR /&gt;It would be a great help if you can brief about the pros and cons for this approach&lt;BR /&gt;I would have a better understanding .&lt;/P&gt;&lt;P&gt;Thanks a million&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jun 2023 06:45:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4861948#M257448</guid>
      <dc:creator>susim</dc:creator>
      <dc:date>2023-06-25T06:45:25Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4862077#M257452</link>
      <description>&lt;P&gt;I believe you got a 9800 as WLC, is that really SSO pair ? Which interface is the WMI, typically that is the only SVI interface recommend to have on 9800. Refer following best practices&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#Generalcontrollersettings" target="_self"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#Generalcontrollersettings&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even though you can configure 9800 like a normal L3 switch, in the WLC context it is not acting as a L3 switch. You may encounter ARP/Asymmetric path routing/etc.&lt;/P&gt;
&lt;P&gt;Since I have not tested what you are doing, cannot comment what are all pro/cons&lt;/P&gt;
&lt;P&gt;HTH&lt;BR /&gt;Rasika&lt;BR /&gt;*** Pls rate all useful responses ***&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jun 2023 23:15:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4862077#M257452</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2023-06-25T23:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: Controller connectivity</title>
      <link>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4862079#M257453</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/327027"&gt;@susim&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;SPAN&gt;Although I have conducted some experiments&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Configuring the 9800 as a Layer 3 -&amp;nbsp; That is a very dangerous precedence.&amp;nbsp; Please share why (or what) is the business case to allow the 9800 to participate in the routing process because the machine may not have enough memory &amp;amp;/or CPU.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;This may work in a lab (or experiments), demo or in really small network sizes but it may have difficulties scaling in large to enterprise sized networks.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jun 2023 23:30:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-connectivity/m-p/4862079#M257453</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2023-06-25T23:30:22Z</dc:date>
    </item>
  </channel>
</rss>

