cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1635
Views
3
Helpful
6
Replies

WLC name change

MinisterofIT
Visitor

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?

Will that cause SNMP issues? I notice I am unable to use SNMP like the other WLC 

1 Accepted Solution

Accepted Solutions

MinisterofIT
Visitor

Thank you everyone. It was resolve. There was block on the firewall. Thanks

View solution in original post

6 Replies 6

Saikat Nandy
Cisco Employee
Cisco Employee

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 'config prompt WLC04' in the CLI to change the CLI prompt name.
Also to answer your specific question, no it does not have any relation with SNMP. If you go to Management > SNMP > General, you should see 'WLC04' as the Name.

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

It will be a mistake in the credentials config on WLC or SNMP poller - so check the config on both sides.
If the config matches correctly then could be a firewall or ACL somewhere between the two blocking the traffic.
Use debugs and packet captures to identify what the problem is.
As the others have said the hostname and CLI prompt will not make any difference to SNMP operation.

Also make sure your software is up to date - refer to the TAC recommended link below.

------------------------------
Please click Helpful if this post helped you and Accept as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390

Leo Laohoo
Hall of Fame
Hall of Fame

@MinisterofIT wrote:
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?

Changing the prompt name impacts nothing.

srimal99
Level 5
Level 5

@MinisterofIT  You can add config sysname <name> after config prompt as well.

MinisterofIT
Visitor

Thank you everyone. It was resolve. There was block on the firewall. Thanks

Review Cisco Networking for a $25 gift card