<?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: WLC name change in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286330#M282855</link>
    <description>&lt;P&gt;Thank you. any suggestions why SNMP will not work on WLC04 but it will on WLC01. The settings are the same in snmp. I am using snmpv3&lt;/P&gt;</description>
    <pubDate>Tue, 29 Apr 2025 18:23:35 GMT</pubDate>
    <dc:creator>MinisterofIT</dc:creator>
    <dc:date>2025-04-29T18:23:35Z</dc:date>
    <item>
      <title>WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286319#M282853</link>
      <description>&lt;P&gt;Our WLC name in the command line is (Cisco Controller). But in the GUI it is WLC04. If I change it so it will be the same, what impact will it have on the network?&lt;/P&gt;&lt;P&gt;Will that cause SNMP issues? I notice I am unable to use SNMP like the other WLC&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 17:57:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286319#M282853</guid>
      <dc:creator>MinisterofIT</dc:creator>
      <dc:date>2025-04-29T17:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286325#M282854</link>
      <description>&lt;P&gt;I guess you are using an AireOS controller. Your WLC hostname in GUI is WLC04, whereas in CLI the prompt is (Cisco Controller). If my understanding is correct, then it is an expected behaviour. You need to run '&lt;SPAN class="s1"&gt;config prompt WLC04' in the CLI to change the CLI prompt name.&lt;BR /&gt;Also to answer your specific question, no it does not have any relation with SNMP. If you go to Management &amp;gt; SNMP &amp;gt; General, you should see 'WLC04' as the Name.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 18:07:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286325#M282854</guid>
      <dc:creator>Saikat Nandy</dc:creator>
      <dc:date>2025-04-29T18:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286330#M282855</link>
      <description>&lt;P&gt;Thank you. any suggestions why SNMP will not work on WLC04 but it will on WLC01. The settings are the same in snmp. I am using snmpv3&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 18:23:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286330#M282855</guid>
      <dc:creator>MinisterofIT</dc:creator>
      <dc:date>2025-04-29T18:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286385#M282857</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1570449"&gt;@MinisterofIT&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;SPAN&gt;Our WLC name in the command line is (Cisco Controller). But in the GUI it is WLC04. If I change it so it will be the same, what impact will it have on the network?&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Changing the prompt name impacts &lt;STRONG&gt;nothing&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 22:34:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286385#M282857</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-04-29T22:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286506#M282865</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1570449"&gt;@MinisterofIT&lt;/a&gt;&amp;nbsp; You can add config sysname &amp;lt;name&amp;gt; after config prompt as well.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 08:25:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286506#M282865</guid>
      <dc:creator>srimal99</dc:creator>
      <dc:date>2025-04-30T08:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286606#M282874</link>
      <description>&lt;P&gt;It will be a mistake in the credentials config on WLC or SNMP poller - so check the config on &lt;STRONG&gt;both&lt;/STRONG&gt; sides.&lt;BR /&gt;If the config matches correctly then could be a firewall or ACL somewhere between the two blocking the traffic.&lt;BR /&gt;Use debugs and packet captures to identify what the problem is.&lt;BR /&gt;As the others have said the hostname and CLI prompt will not make any difference to SNMP operation.&lt;/P&gt;
&lt;P&gt;Also make sure your software is up to date - refer to the TAC recommended link below.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 13:10:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286606#M282874</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2025-04-30T13:10:40Z</dc:date>
    </item>
    <item>
      <title>Re: WLC name change</title>
      <link>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286921#M282924</link>
      <description>&lt;P&gt;Thank you everyone. It was resolve. There was block on the firewall. Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2025 14:37:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-name-change/m-p/5286921#M282924</guid>
      <dc:creator>MinisterofIT</dc:creator>
      <dc:date>2025-05-01T14:37:00Z</dc:date>
    </item>
  </channel>
</rss>

