Wlc-2504-k9 ap license upload issue
Hi i have 20 access points and wlc controller with 15 ap supported .I got 5 ap license but am not able to upload .
Temproray i have enabled evaluation license which is valid 12 weeks . but when i tried to upload the liecense its giving me error .
Can anybody help me the exact steps .
Hi Breeze,
I think its normal behaviour for Cisco WLCs.
Example: It happend with me.
Old licence was for 15APs
if you add 5 more ap licence to WLC then old Licence will go in inactive state but evaluation License will be in use.
After evaluation period you will get the total 20 AP licence in in use status.
This happend with me.
I think this guy I also have similer issue: https://supportforums.cisco.com/thread/2205144
If you still have doubts or issues then please go for TAC case.
Hope it helps.
Regards
Similar Messages
-
Hi,
I have installed WCS version 7.0.164.0 and have added Mobility Service Engine to WCS. The version of MSE is 7.0.105.0. I ahve uploaded license in WCS for supporting 200 APs. Then when i am trying to upload MSE liecnse, I am getting the below error.
MSE license file could not be installed. The total license limit has been met or exceeded for the MSE and all its services. Capacity is exceeded by 5%. Reduce the license count for one or more services to be within the capacity limit and for optimal performance.
Please let me know how should i proceed further.I'm going thru the same thing right now and this is a bit confusing. What I do know is that there are 2 types of licensing and depending on what it is you want to do you want one of the other or both. The licenses are explained below. I hope this helps.
Two types of Licenses:
•1. wIPS – Adaptive Wireless Intrusion Prevention
•a. Maintain a constant awareness of your RF environment to minimize legal liability, protect your brand reputation, and assure regulatory compliance.
•b. Cisco Adaptive Wireless Intrusion Prevention System (IPS) offers advanced network security for dedicated monitoring and detection of wireless network anomalies, unauthorized access, and RF attacks. Fully integrated with the Cisco Unified Wireless Network, this solution delivers integrated visibility and control across the network, without the need for an overlay solution.
•2. Context Aware – for locating wireless devices
•a. With Context-Aware Software, organizations can quickly locate rogue devices, interferers, Wi-Fi clients, tagged assets, and wired devices. This physical location information provides the insight needed to improve workflow, quickly troubleshoot mobile clients, and implement asset management solutions.
Sandi -
UCCX Enhanced License upload issues
I have a site that is under the gun to finish a UCCX migration from 4.0 to 7.0 We put in for the license upgrade using a PAK but when we load it the system tells us that it is not valid to upgrade using this file from "NONE" Generally that section tells you what files you already have if you add a feature license file.
We opened a case with TAC but in the meantime we loaded an NFR license file so we could start to configure the system. I then found a PAK for 4-5 to 7 for another site that is being closed. When I got that license file back and tried to run the set-up Wizard again, it tells me the new license is not a valid upgrade from Premium and will be ignored.
Does this mean I will never be able to get off the NFR license? Am I stuck on this license file even if I get my correct one tomorrow or the next day?
thanksYes, that is correct that you need the 4.x main system license plus the NEW upgrade license, but the main issue here was "What do I do if my system is running incorrect licensing?" And the answer is, you need to reset the flag for the Web GUI to Fresh Install and you need to delete the references to the existing license files. Both actions are done through the Windows on-board support tool accessed via Start-->Run
I would not recomend doing this the first time without TAC on the line, but if anyone else wants to provide the command you use to access this tool, feel free. It escapes me at the moment. -
This might be a really stupid question but I need to ask just so that I get a definitive answer. I have a customer that is using a WLC 2112 and has maxed out the licenses for the WLC. I have suggested for him to purchase a 2504 with 30 or 40 licenses to replace the existing 2112. He doesn't want to purchase 30 to 40 licenses and doesn't want to remove the 2112 from the network environment. He would rather purchase a WLC 2504 with 15 licenses and just add that into the network.
My question is, will there be a problem running a 2504 and a 2112 on the same network? Or can I just make one a primary and one a secondary?That should be fine. Just make sure the WLCs are running the same code version and everything should work fine. This is required for APs failover from one WLC to another. You don't want the APs upgrading or downgrading code versions every time the ap moves from the primary to the secondary WLC.
Sent from Cisco Technical Support iPhone App -
I have two WLC 2504 controllers. These controllers are for two different buildings. But they share a VLAN, and network address range.
How can I control the access points to the register selected only at a specific controller.
Example:
AP 1 -> WLC 1
AP 2 -> WLC 2
AP 3 -> WLC 1
Since the buildings also broadcast in different SSID.
The two controllers are in a mobility group.I also ran into an install similar to yours. My client had a flat network and each wlc had licenses for the amount of APs in a particular building. What I did to make sure the APs never join the other wlc, is to use a Mac list. This allowed me to enter the APs base Mac address on the wlc and I enabled under the ap policy to verify authorization using Mac list. You can also do what AA mentioned which is good practice, but you have a chance that APs might join the other wlc. If the other wlc has different configurations, it might cause issues until the ap falls back to its primary.
Sent from Cisco Technical Support iPad App -
WLC 2504 sudden network instability
Hello,
we're running a WLC 2504 with two SSIDs on it. It is connected to to a small PoE switch. Standard untagged vlan. A handfull APs connected to it. No DHCP, the APs have all static IP addresses.
All of a sudden we're having a number of issues with the network connection:
APs restarting
The APs restart every now and then reporting that their IP is being used by another device. Looking through the logs there are two MAC addresses that are reported as using the APs IP address. These two MAC addresses have unknown vendor IDs.
Warning: AP with Base Radio MAC f8:72:ea:7c:9d:e3 has found its IP Address 0.2.146.0 being used by a machine with MAC
Address 04:c6:f8:40:00:00 (The other mac that is reported is 04:cc:90:40:00:00)
AP 'AP5', MAC: 0c:68:03:dd:1b:80 disassociated previously due to Link Failure. Uptime: 4 days, 00 h 48 m 50 s . Reason: Capwap WTP Event request.
So: There are two MACs that use the IP addresses of 7 APs?!?! And there is no vendor to be found for these MACs?
Ping timouts on the webGUI and CLI
I have a ping running on the IP for managing the device. This is running fine for ages. As soon as I connect via webGUI or CLI I lose packets. Get timeouts etc. some packets get through some don't. More of the latter. So ping is fine but any other traffic seems to be impacted heavily.
What we have done for troubleshooting
Checked duplex/speed settings of the interfaces. Everything ok.
Connected to another switchport. Same.
Changed the IP address of the management port. Same.
Swapped places with a laptop with the same IP address --> Worked fine.
Plugged in a completely new device, installed the latest firmware (7.6) and uploaded the config from the other one. Same.
Restarted the default gateway for the subnet the controler is on.
So now we're at the end of our knowledge. It seems to be a non-physical network issue, but we're a small team and no one has changed anything they say :-/
Any ideas what we could check next?
KatHello,
thanks for your suggestions. It's hard to find those two MAC addresses. As they seem to be virtual I cannot get a hint from the vendor ID. A show mac-address table on the switch the WLC is connected to doesn't show those two
I found an error in the WLC AP config. AP1 had the same IP as AP5 and a wrong netmask. I changed that. Unfortunately that doesn't solve our problem.
Here are some more messages from the WLC's log:
AP 'AP3', MAC: 0c:68:03:dd:34:00 disassociated previously due to Link Failure. Uptime: 4 days, 15 h 04 m 15 s . Reason: Capwap WTP Event request.
AP Disassociated. Base Radio MAC:0c:68:03:dd:34:00
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:0c:68:03:dd:34:00 Cause=Heartbeat Timeout Status:NA
AP 'AP3', MAC: 0c:68:03:dd:34:00 disassociated previously due to Link Failure. Uptime: 4 days, 15 h 00 m 45 s . Reason: Capwap WTP Event request.
RF Manager updated TxPower for Base Radio MAC: 0c:68:03:dd:34:00 and slotNo: 0. New Tx Power is: 2
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:0c:68:03:dd:16:e0 Cause=Max Retransmission Status:NA
IDS Signature attack detected. Signature Type: Standard, Name: Deauth flood, Description: Deauthentication flood, Track: per-signature, Detecting AP Name: AP7, Radio Type: 802.11b/g, Preced: 9, Hits: 500, Channel: 6, srcMac: C2:9F:DB:21:47:60
This is the sh run-config of our WLC including one AP:
>show run-config
System Inventory
NAME: "Chassis" , DESCR: "Cisco 2500 Series Wireless LAN Controller"
PID: AIR-CT2504-K9, VID: V01, SN: PSZ17381EPZ
Burned-in MAC Address............................ 50:17:FF:27:12:80
Maximum number of APs supported.................. 15
System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.18
Field Recovery Image Version..................... 1.0.0
Firmware Version................................. PIC 16.0
Build Type....................................... DATA + WPS
System Name...................................... UK-BRI-WFAPC
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 172.17.128.12
Last Reset....................................... Power on reset
System Up Time................................... 4 days 0 hrs 46 mins 6 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +20 C
External Temperature............................. +25 C
Fan Status....................................... 4000 rpm
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 3
Number of Active Clients......................... 6
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 50:17:FF:27:12:80
Maximum number of APs supported.................. 15
AP Bundle Information
Primary AP Image Size
ap1g2 9568
ap3g1 11288
ap3g2 11196
ap801 7164
ap802 8568
c1130 5072
c1140 9416
c1250 6944
c1520 8044
c602i 3736
Secondary AP Image Size
ap3g1 5792
ap801 5192
ap802 5232
c1100 3084
c1130 4964
c1140 4992
c1200 3364
c1240 4812
c1250 5504
c1310 3136
c1520 6404
c3201 4324
c602i 3716
Switch Configuration
802.3x Flow Control Mode......................... Disable
FIPS prerequisite features....................... Disabled
secret obfuscation............................... Enabled
Strong Password Check Features:
case-check ...........Enabled
consecutive-check ....Enabled
default-check .......Enabled
username-check ......Enabled
Network Information
RF-Network Name............................. RFGROUP
Web Mode.................................... Disable
Secure Web Mode............................. Enable
Secure Web Mode Cipher-Option High.......... Disable
Secure Web Mode Cipher-Option SSLv2......... Disable
Secure Web Mode RC4 Cipher Preference....... Disable
OCSP........................................ Disabled
OCSP responder URL..........................
Secure Shell (ssh).......................... Enable
Telnet...................................... Disable
Ethernet Multicast Forwarding............... Disable
Ethernet Broadcast Forwarding............... Disable
AP Multicast/Broadcast Mode................. Multicast Address : 0.0.0.0
IGMP snooping............................... Disabled
IGMP timeout................................ 60 seconds
IGMP Query Interval......................... 20 seconds
MLD snooping................................ Disabled
MLD timeout................................. 60 seconds
MLD query interval.......................... 20 seconds
User Idle Timeout........................... 300 seconds
ARP Idle Timeout............................ 300 seconds
Cisco AP Default Master..................... Disable
AP Join Priority............................ Disable
Mgmt Via Wireless Interface................. Disable
Mgmt Via Dynamic Interface.................. Disable
Bridge MAC filter Config.................... Enable
Bridge Security Mode........................ EAP
Mesh Full Sector DFS........................ Enable
AP Fallback ................................ Enable
Web Auth CMCC Support ...................... Disabled
Web Auth Redirect Ports .................... 80
Web Auth Proxy Redirect ................... Disable
Web Auth Captive-Bypass .................. Disable
Web Auth Secure Web ....................... Enable
Fast SSID Change ........................... Disabled
AP Discovery - NAT IP Only ................. Enabled
IP/MAC Addr Binding Check .................. Enabled
CCX-lite status ............................ Disable
oeap-600 dual-rlan-ports ................... Disable
oeap-600 local-network ..................... Enable
mDNS snooping............................... Disabled
mDNS Query Interval......................... 15 minutes
Port Summary
STP Admin Physical Physical Link Link
Pr Type Stat Mode Mode Status Status Trap POE
1 Normal Forw Enable Auto 1000 Full Up Enable N/A
2 Normal Forw Enable Auto 100 Full Up Enable N/A
3 Normal Forw Enable Auto 1000 Full Up Enable Enable (Power Off)
4 Normal Disa Enable Auto Auto Down Enable Enable (Power Off)
AP Summary
Number of APs.................................... 7
Global AP User Name.............................. Not Configured
Global AP Dot1x User Name........................ Not Configured
AP Name Slots AP Model Ethernet MAC Location Port Country Priority
AP7 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9a:81 default location 1 GB 1
AP1 2 AIR-CAP1602I-E-K9 f8:72:ea:7c:9d:e3 default location 1 GB 1
AP3 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9c:57 default location 1 GB 1
AP6 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9a:90 default location 1 GB 1
AP2 2 AIR-CAP1602I-E-K9 f8:72:ea:7c:9b:63 default location 1 GB 1
AP4 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9a:9b default location 1 GB 1
AP5 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9a:cb default location 1 GB 1
AP Tcp-Mss-Adjust Info
AP Name TCP State MSS Size
AP7 disabled -
AP1 disabled -
AP3 disabled -
AP6 disabled -
AP2 disabled -
AP4 disabled -
AP5 disabled -
AP Location
Total Number of AP Groups........................ 0
Site Name........................................ default-group
Site Description.................................
NAS-identifier................................... UK-BRI-WFAPC
AP Operating Class............................... Not-configured
RF Profile
2.4 GHz band.....................................
5 GHz band.......................................
WLAN ID Interface Network Admission Control Radio Policy
1 corporate Disabled None
2 dirtynetwork Disabled None
3 dirtynetwork Disabled None
AP Name Slots AP Model Ethernet MAC Location Port Country Priority
AP7 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9a:81 default location 1 GB 1
AP1 2 AIR-CAP1602I-E-K9 f8:72:ea:7c:9d:e3 default location 1 GB 1
AP3 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9c:57 default location 1 GB 1
AP6 2 AIR-CAP1602I-E-K9 f8:72:ea:e4:9a:90 default location 1 GB 1
AP2 2 AIR-CAP1602I-E-K9 f8:72:ea:7c:9b:63 default location 1 GB 1
AP4 2 AIR-CAP1602I-E-K9 f8:
RF Profile
Number of RF Profiles............................ 0
Out Of Box State................................. Disabled
RF Profile Name Band Description 11n-client-only
AP Config
Cisco AP Identifier.............................. 15
Cisco AP Name.................................... AP7
Country code..................................... GB - United Kingdom
Regulatory Domain allowed by Country............. 802.11bg:-E 802.11a:-E
AP Country code..................
................ GB - United Kingdom
AP Regulatory Domain............................. -E
Switch Port Number .............................. 1
MAC Address...................................... f8:72:ea:e4:9a:81
IP Address Configuration......................... Static IP assigned
IP Address....................................... 172.17.128.24
IP NetMask....................................... 255.255.128.0
Gateway IP Addr.................................. 172.17.128.1
Domain...............
Name Server......................................
NAT External IP Address.......................... None
CAPWAP Path MTU.................................. 1485
Telnet State..................................... Disabled
Ssh State........................................ Disabled
Cisco AP Location................................ default location
Cisco AP Floor Label............................. 0
Cisco AP Group Name.............................. default-group
Primary Cisco Switch Name........................
Primary Cisco Switch IP Address.................. Not Configured
Secondary Cisco Switch Name......................
Secondary Cisco Switch IP Address................ Not Configured
Tertiary Cisco Switch Name.......................
Tertiary Cisco Switch IP Address................. Not Configured
Administrative State ............................ ADMIN_ENABLED
Operation State ....
............................. REGISTERED
Mirroring Mode .................................. Disabled
AP Mode ......................................... Local
Public Safety ................................... Disabled
AP SubMode ...................................... Not Configured
Remote AP Debug ................................. Disabled
Logging trap severity level ..................... informational
Logging syslog facility ..
....................... kern
S/W Version .................................... 7.4.110.0
Boot Version ................................... 15.2.2.0
Mini IOS Version ................................ 7.4.1.37
Stats Reporting Period .......................... 180
Stats Collection Mode ........................... normal
LED State........................................
Enabled
PoE Pre-Standard Switch.......................... Disabled
PoE Power Injector MAC Addr...................... Disabled
Power Type/Mode.................................. Power injector / Normal mode
Number Of Slots.................................. 2
AP Model......................................... AIR-CAP1602I-E-K9
AP Image...............................
.......... C1600-K9W8-M
IOS Version...................................... 15.2(2)JB2$
Reset Button..................................... Enabled
AP Serial Number................................. FGL1725W7F7
AP Certificate Type.............................. Manufacture Installed
AP User Mode..................................... AUTOMATIC
AP User Name..................................... Not Configured
AP Dot1x User Mode............................... Not Configured
AP Dot1x User Name............................... Not Configured
Cisco AP system loggi
ng host..................... 255.255.255.255
AP Up Time....................................... 3 days, 23 h 26 m 50 s
AP LWAPP Up Time................................. 0 days, 00 h 14 m 12 s
Join Date and Time............................... Tue Jan 28 18:11:43 2014
Join Taken Time.................................. 0 days, 00 h 11 m 41 s
Attributes for Slot 0
Radio Type................................... RADIO_TYPE_80211n-2.4
Administrative State ........................ ADMIN_ENABLED
Operation State ............................. UP
Radio Role .................................. ACCESS
Radio Mode .................................. Local
CellId ...................................... 0
Station Configuration
Configuration ............................. AU
TOMATIC
Number Of WLANs ........................... 3
Medium Occupancy Limit .................... 100
CFP Period ................................ 4
CFP MaxDuration ........................... 60
BSSID ..................................... 0c:68:03:dd:16:e0
Operation Rate Set
1000 Kilo Bits........................... MANDATORY
2000 Kilo Bits........................... MANDATORY
5500 Kilo Bits........................... MANDATORY
11000 Kilo Bits.......................... MANDATORY
6000 Kilo Bits........................... SUPPORTED
9000 Kilo Bits........................... SUPPORTED
12000 Kilo Bits.......................... SUPPORTED
18000 Kilo Bits.......................... SUPPORTED
24000 Kilo Bits.......................... SUPPORTED
36000 Kilo Bits.......................... SUPPORTED
48000 Kilo Bits.......................... SUPPORTED
54000 Kilo Bits.......................... SUPPORTED
MCS Set
MCS 0.................................... SUPPORTED
MCS 1.................................... SUPPORTED
MCS 2.................................... SUPPORTED
MCS 3.................................... SUPPORTED
MCS 4.................................... SUPPORTED
MCS 5.................................... SUPPORTED
MCS 6.................................... SUPPORTED
MCS 7.................................... SUPPORTED
MCS 8.................................... SUPPORTED
MCS 9.................................... SUPPORTED
MCS 10................................... SUPPORTED
MCS 11................................... SUPPORTED
MCS 12..
................................. SUPPORTED
MCS 13................................... SUPPORTED
MCS 14................................... SUPPORTED
MCS 15................................... SUPPORTED
MCS 16................................... DISABLED
MCS 17................................... DISABLED
MCS 18................................... DISABLED
MCS 19................................... DISABLED
MCS 20................................... DISABLED
MCS 21................................... DISABLED
MCS 22................................... DISABLED
MCS 23................................... DISABLED
Beacon Period ............................. 100
Fragmentation Threshold ................... 2346
Multi Domain Capability Implemented ....... TRUE
Multi Domain Capability Enabled ........... TRUE
Country String ............................ GB
Multi Domain Capability
Configuration ............................. AUTOMATIC
First Chan Num ............................ 1
Number Of Channels ........................ 13
MAC Operation Parameters
Configuration ............................. AUTOMATIC
Fragmentation Threshold ................... 2346
Packet Retry Limit ........................ 64
Tx Power
Num Of Supported Power Levels ............. 4
Tx Power Level 1 .......................... 16 dBm
Tx Power Level 2 .......................... 13 dBm
Tx Power Level 3 .......................... 10 dBm
Tx Power Level 4 .......................... 7 dBm
Tx Power Configuration .................... AUTOMATIC
Current Tx Power Level .................... 3
Tx Power Assigned By ...................... DTPC
Phy OFDM parameters
Configuration ............................. AUTOMATIC
Current Channel ........................... 6
Channel Assigned By ....................... DCA
Extension Channel ......................... NONE
Channel Width.............................. 20 Mhz
Allowed Channel List....................... 1,2,3,4,5,6,7,8,9,10,11,12,
......................................... 13
TI Threshold .............................. -50
Legacy Tx Beamforming Configuration ....... CUSTOMIZED
Legacy Tx Beamforming ..................... ENABLED
Antenna Type............................... INTERNAL_ANTENNA
Internal Antenna Gain (in .5 dBi units).... 8
Diversity.................................. DIVERSITY_ENABLED
802.11n Antennas
A....................................... ENABLED
B....................................... ENABLED
C....................................... ENABLED
Performance Profile Parameters
Configuration ............................. AUTOMATIC
Interference threshold..................... 10 %
Noise threshold............................ -70 dBm
RF utilization threshold................... 80 %
Data-rate threshold........................ 1000000 bps
Client threshold........................... 12 clients
Coverage SNR threshold..................... 12 dB
Coverage exception level................... 25 %
Client minimum exception level............. 3 clients
Rogue Containment Information
Containment Count............................
CleanAir Management Information
CleanAir Capable......................... No
Radio Extended Configurations
Beacon period.............................. 100 milliseconds
Beacon range............................... AUTO
Multicast buffer........................... AUTO
Multicast data-rate........................ AUTO
RX SOP threshold........................... AUTO
CCA threshold.............................. AUTO -
Acs 5.3 and wlc 2504 config with restricted network access
Hello,
i submit you the following issue that i'm actually facing:
i must configure a secured wireless network with access restriction based on SSID. the equipements are : cisco wlc 2504 (soft 7.3) cisco secure acs aplliance 1121 (soft 5.4) .
the users that will connect to the network are regrouped by identity groups, each identity group having it's own SSID. Clearly each group of users must access only one SSID.
i followed the procedure below to configure it:
-- creating user identity groups;
-- creating users and assigning them to the groups;
--- creating authorization profiles for each SSID under policy element/ authorization and permission/network access/authorization profiles and putting the Airespace-Wlan-Id(the SSID number) in the radius tab.
--- assigning the authorization profiles to the identity groups under access policies.
after all these config the users can access the network using there userid/password configured. But the problem is Every user can access every SSID, seems like the restriction is so not very well configured.
i found some documentation on this kind of config but the version of ACS used seems older than the one that i use, so menu are very different.
Please can someone provide with the right steps to follow to achieve this kind of config.
tkx in advanceYes.. you only have to add the end filter like what I posted... as far as the calling station id in the WLC security tab, it doesn't matter because that is not used when using 802.1x. I would also try to not enable everything that you have just to start from the basic and make sure it works first. The WAP Authentication Method might or might not work for you. Uncheck that for now and when you have a successful authentication, look at the monitor log and see what radius attributes are being sent, because those attributes is what you can use to build your policies.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered" -
WLC: 2504
Firmware: 7.6.100
Hello,
I'm getting very confused in how to set up redundancy with WLC 2504. Some sources talk about Client SSO, some about N+1.
But it seems that although I should use Client SSO with firmware 7.6, the WLC 2504 doesn't support it.
When I type config redundancy, I have no choice
>config redundancy ?
unit Configure redundancy unit [primary | secondary]
So I typed "config redundancy unit primary" on my 2504 and "config redundancy unit secondary" on my 2504-HA
And when I issue this command I have very little information
>show redundancy summary
Type of the Unit = Primary
Does someone has guidelines for redundancy with WLC 2504 on firmware 7.6 ?
Thank youHello,
Thank you both for your answers.
Something I didn't understand in the documentation is this.
Is there a replication of configuration between the WLC primary and the HA ? I did read that they should have different network settings (IP addresses) so I understand that there is not a total replication, what about the rest of the configuration ?
The only result I have when I issue a command on the WLC-HA is this
>show redundancy summary
Type of the Unit = Secondary
It doesn't look exactly what I see in the documentation.
Thank you -
Hi!!! Please help with the solution.
I have one WLC 2504, 4 Cisco 1141 APs and one AP 1602.
Yesterday, I upgrade the WLC with version 7.5.102 to version 7.6.100.
After the upgrade in Message Logs on the WLC at the same time see the following message:
*RRM-MGR-5_0-GRP: Jan 23 08:44:25.449: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 08:35:41.189: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 08:34:17.373: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 08:25:32.125: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 08:24:09.309: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 08:15:23.013: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 08:14:01.213: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 08:05:13.949: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 08:03:53.149: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 07:55:04.905: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 07:53:45.086: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 07:44:55.813: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 07:43:37.010: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 07:34:46.749: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 07:33:28.930: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 07:24:37.669: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 07:23:20.865: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 07:14:28.593: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 07:13:12.789: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 07:04:19.529: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 07:03:04.729: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 06:54:10.493: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 06:52:56.689: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 06:44:01.445: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 06:42:48.645: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.
*sntpReceiveTask: Jan 23 06:35:22.218: #LOG-4-Q_IND: debug.c:2636 Unhandled debug module 5005.[...It occurred 19 times.!]
*RRM-MGR-2_4-GRP: Jan 23 06:33:48.070: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 06:32:36.266: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 06:23:39.030: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 06:22:28.226: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 06:13:29.986: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 06:12:20.186: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 06:03:20.930: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 06:02:12.130: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 05:53:11.890: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 05:52:04.090: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 05:43:02.838: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 05:41:56.039: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 05:32:53.790: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 05:31:47.986: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 05:22:44.758: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 05:21:39.950: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 05:12:35.718: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 05:11:31.910: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 05:02:26.670: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 05:01:23.859: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 04:52:17.606: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 04:51:15.794: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 04:42:08.566: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 04:41:07.750: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 04:31:59.506: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 04:30:59.703: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 04:21:50.450: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 04:20:51.646: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 04:11:41.402: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 04:10:43.598: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 04:01:32.326: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 04:00:35.522: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 03:51:23.258: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 03:50:27.442: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 03:41:14.182: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 03:40:19.378: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 03:31:05.106: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 03:30:11.302: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 03:20:56.042: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 03:20:03.242: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 03:10:46.978: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 03:09:55.178: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 03:00:37.902: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 02:59:47.102: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 02:50:28.826: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 02:49:39.026: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 02:40:19.782: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 02:39:30.983: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 02:30:10.742: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 02:29:22.942: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 02:20:01.698: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 02:19:14.886: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 02:09:52.646: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 02:09:06.842: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 01:59:43.587: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 01:58:58.783: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 01:49:34.546: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 01:48:50.742: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 01:39:25.494: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 01:38:42.687: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 01:29:16.454: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 01:28:34.642: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 01:19:07.402: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 01:18:26.594: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 01:08:58.362: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 01:08:18.554: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 00:58:49.322: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 00:58:10.514: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 00:48:40.266: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 00:48:02.467: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 00:38:31.222: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 00:37:54.411: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 00:28:22.174: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 00:27:46.374: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 00:18:13.106: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 00:17:38.306: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 23 00:08:04.062: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 23 00:07:30.262: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 22 23:57:55.022: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 22 23:57:22.222: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 22 23:47:45.958: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 22 23:47:14.158: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 22 23:37:36.906: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 22 23:37:06.106: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 22 23:27:27.826: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 22 23:26:58.026: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 22 23:17:18.762: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 22 23:16:49.962: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 20 times/sec!.]
*RRM-MGR-2_4-GRP: Jan 22 23:07:09.686: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.[...It occurred 10 times/sec!.]
*RRM-MGR-5_0-GRP: Jan 22 23:06:41.870: #DEBUG-4-INVALID_MODULE: debug.c:2636 Unhandled debug module 5005.
With what may be the problem exists? Any suggestion?Have you upgraded the FUS to 1.8.0.0? What happens if you try to boot from v7.5 do you see the messages and maybe boot back to v7.6?
Here is what the doc mentions about the error
Error Message %DEBUG-4-INVALID_MODULE: Unhandled debug module [dec].
Explanation This module cannot be debugged.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
http://www.cisco.com/en/US/docs/wireless/controller/message/guide/msgs4.html#wp1000708
Sent from Cisco Technical Support iPhone App -
WLC 2504 - French characters for guest web login page
Good day,
I have recently installed a WLC 2504 and I have the following issue:
When I modify the text for the web login page (Under security/Web Auth/Web Auth page), if I use french caracters such as (é, è, à, etc...) in the message body, it does not show up correctly on users computers. As we're a bilingual country, I must put a bilingual text message. Are there any settings or workaround out there to rectify this?
We're on version 7.2.103.0
Thanks,
EricThanks Scott, I'll have a look at the documentation.
Right after sending this post, I tried typing the actual HTML code for the character instead and it seems to be working. I'm curious about custom webauth page, we may be able to customize it more than we thought we could do.
Cheers,
Eric -
WLC 2504 can't change WAP name or switch off CDP via WLC gui
Hi All,
Please can you assist? I have 1 x Cisco WLC 2504 & 2 x Cisco WAP AIR-CAP1602I-E-K9 running 7.4.100.60.
All three devices are installed and working correcty within a corporate environment. However, there are a few tweaks that I would like to do, to tidy up the configuration and switch certain elements on or off. For example, my core networking hardware is Huawei and I would like to switch off 'CDP' on the WAP's as the associated error messages are filling up my logging buffer on my switch. So, I https to my WLC, locate the WAP in question, goto 'interfaces' and untick the box for 'CDP state' hit apply, then I get the following error message "controller name is mandatory when controller ip address is configured" and then the tick reappears!
At present I have two WAP's. Both have static IP addresses and both are reachable on the network. The one WAP did allow me to change the name to something meaningful, but the other WAP would not let me and still has the default MAC address as its name. I have the same issue, when I try to change the name on the WAP it says "controller name is mandatory when controller ip address is configured"
I have also tried to CLI directly in to the WAP to make these alterations, but as soon as i launch 'putty' it quits out. I guess this is locked down once the WAP's associate with the WLC.
And around I go.... Someone must have been in this situation, what am i missing? Thanks in advance!Hi Andy,
By default SSH & Telnet is disabled for WLC controlled APs. So you have to enable it first via WLC GUI in order to access the AP via telnet or SSH.
Wireless -> Select your AP -> Advanced -> Tick Telnet/SSH boxes.
If you could not change AP name via WLC GUI (it may be a bug), but as I said earlier try to change it via WLC CLI (not AP CLI itself). SSH to your WLC & then try the following.Old AP name is the one with its mac address.
(WLC) >config ap name
(WLC) >save config
Are you sure you want to save? (y/n) y
Configuration Saved
HTH
Rasika
*** Pls rate all useful responses **** -
Cisco WLC 2504 and ways to authenticate users
Hi All,
What is the ways to make user authenticate to WLC 2504 and what is the best and simple way and what is the differences btw each method _i mean for example need radius server or something else to be exist_ ?
and any one can give me case study for this issue
System consist of Cisco 2504 and Cisco LAP 1140
ThanksTo implement radius based authentication is the best practice for the small & enterprise environment.
Information About RADIUS
Remote Authentication Dial-In User Service (RADIUS) is a client/server protocol that provides centralized security for users attempting to gain management access to a network. It serves as a backend database similar to local and TACACS+ and provides authentication and accounting services:
•Authentication—The process of verifying users when they attempt to log into the controller.
Users must enter a valid username and password in order for the controller to authenticate users to the RADIUS server. If multiple databases are configured, you can specify the sequence in which the backend database must be tired.
•Accounting—The process of recording user actions and changes.
Whenever a user successfully executes an action, the RADIUS accounting server logs the changed attributes, the user ID of the person who made the change, the remote host where the user is logged in, the date and time when the command was executed, the authorization level of the user, and a description of the action performed and the values provided. If the RADIUS accounting server becomes unreachable, users are able to continue their sessions uninterrupted.
RADIUS uses User Datagram Protocol (UDP) for its transport. It maintains a database and listens on UDP port 1812 for incoming authentication requests and UDP port 1813 for incoming accounting requests. The controller, which requires access control, acts as the client and requests AAA services from the server. The traffic between the controller and the server is encrypted by an algorithm defined in the protocol and a shared secret key configured on both devices.
You can configure multiple RADIUS accounting and authentication servers.For example, you may want to have one central RADIUS authentication server but several RADIUS accounting servers in different regions. If you configure multiple servers of the same type and the first one fails or becomes unreachable, the controller automatically tries the second one, then the third one if necessary, and so on.
For more Information : http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_security_sol.html#wp2149947 -
Hi Guys,
What configuration should I use in order to configure HA using 2x Cisco WLC 2504 ?
- Do I need to have licenses for 2x Controllers ? I have only one WLC with license installed.
At the moment I have the following scenario below.
AIR-CT2504-K9 – Primary (30 Aps Supported)
AIR-CT2504-HA-K9 – Secondary (0 license)
Software Version - 7.6.130.0 (Both Controllers)
Both controllers are going to be in the same place.
Can anyone help me please ?
Thanks,
EvertonThanks Scott Fella !
Just one more question.
Should I use a crossover cable to connect the primary controller to the secondary ? Or should I use a switch to connect them ?
Thanks,
Everton -
Query About Cisco WLC 2504 TDLS
Dear Friends,
One of my client want to encrypt data over the wireless. I have cisco WLC 2504 IOS Version 7.2.0.0.
Please help me on this. I think by-default data encrypt is enable. If not so how can I enable it. If I enable it is there any impact to my wireless user's.
Please help me out .....
Thanks & Regards,
Rahul WankhadeHow to enable:
http://www.cisco.com/c/en/us/support/docs/wireless/2500-series-wireless-controllers/113034-2500-deploy-guide-00.html#enable
Impact:
2500, WiSM2, WLC2—These platforms by default will not contain DTLS. To turn on data DTLS, you must install a license. These platforms will have a single image with data DTLS turned off. To use data DTLS you will need to have a license.
http://www.cisco.com/c/en/us/products/collateral/wireless/2500-series-wireless-controllers/data_sheet_c78-645111.html
AS per cisco: Encryption limits throughput at both the controller and the access point.
Regards
Dont forget to rate helpful posts -
Configure a second Wlan on WLC 2504
Hello,
I created a topic about this problem on the learningnetwork cisco site too. You can find it here: https://learningnetwork.cisco.com/thread/73201.
The problem is:
We have the Cisco WLC 2504 with a couple of access points. On this WLC we have a network connection via a radius server for our employees. The DHCP server for this connection is the server you see on the drawing. The connection from the switch to the WLC is connected on port 1 of the WLC. This connection works like a charm.
Now I want to create a second network (which is divorced from our internal network) for our guests, but it doesn’t work till now. What we have at the moment is:
A connection from the firewall via the router to the internet
A connected cable from the firewall to the WLC on port 2
A configured interface (port 2) on the WLC
A configured Wlan on the WLC (it is possible to connect to the guest Wlan with a static ip)
The SSID of the guest network is broadcasted via the AP’s which also broadcast the internal network SSID
The problem I have now is:
I have no connection between the WLC Port 2 (192.168.10.2) and the firewall (192.168.10.1). When I try to ping the firewall (192.168.10.1) I get a no reply received message.
How can I get this working? I hope someone can help me with this. Thanks in advance!
Screenshots:
Guest interface
Network layout
Show int sum
Show wlan sum
Wlan general
Wlan advancedFrank,
The issue is that the WLC will not route between VLANs. In order for the scenario that Rasika recommended to work, the switch needs to be a layer 3 switch or needs a layer 3 device attached to it to route between the VLANs.
In my WLC, I have a guest interface as well:
The gateway listed in the VLAN 50 Interface on my L3 Switch:
I then have a route established on my switch to send that traffic to my ASA:
Due to that, I can ping the ASA from my WLC:
Of course, my WLAN for guests only has access to the guest Interface Group:
Try these changes on your switch (or other Layer 3 Device) and let us know if it worked for you.
Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question. Otherwise, feel free to post follow-up questions.
Charles Moreton
Maybe you are looking for
-
I am just having problems finding a toolbar with the same features of the AIM toolbar. I simply want a toolbar with button links. Not one with the content feeds from social sites.
-
T400 screen brightness standby issue
When my T400 comes out of standby the screen brightness goes to 100% even though the Power Scheme prior to standby was lower than 100%. This causes me to have to manually adjust the screen brightness. Does anyone know how to prevent this from happe
-
Condition Records for Handling Units
Hi Experts, I want to add a new Key Combination into VV61 (Ship-to-party + Shipping Mat. Type) for a new Output Type. Please tell me how to do it. Thank you. Regards, David
-
hey i'm wondering what does the packaet data connectivity mean? can i connect my nokia to my home tcp/ip i.e wireless router? if so how? or is this the connect between the computer and the phone for i.e surfin on the computer thorugh gprs etc?
-
Customize transport bar and save changes?
Am I missing some here but if I customize the transport bar and make changes, close logic and open it again those changes are not there? Shouldn't my changes to the transport bar remain? How do I save them as standard for all projects? I just want th