WLC 2504 LAG - Issue

Hello All,
I am having difficulty connecting via gui to my 2504 WLC controller, with code 7.4 VIA a Lag link. i have configured a tagged vlan (vlan 40) on the WLC ap-management port.
I have configured a port-channel on a C2960s
interface Port-channel2
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
I have configured the interfaces on the C2960S
interface range GigabitEthernet1/0/1 - 4
description BH-C2960SPSL24-01 connection to BH-C2504WLC-01
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 2 mode active
I can ping the interface, but cannot bring up a gui.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.01.17 22:27:37 =~=~=~=~=~=~=~=~=~=~=~=
show run
Building configuration...
Current configuration : 10532 bytes
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
boot-start-marker
boot-end-marker
no aaa new-model
switch 1 provision ws-c2960s-24ps-l
crypto pki trustpoint TP-self-signed-131252096
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-131252096
revocation-check none
rsakeypair TP-self-signed-131252096
crypto pki certificate chain TP-self-signed-131252096
certificate self-signed 01
3082023D 308201A6 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
30312E30 2C060355 04031325 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 31333132 35323039 36301E17 0D393330 33303130 30303830
355A170D 32303031 30313030 30303030 5A303031 2E302C06 03550403 1325494F
532D5365 6C662D53 69676E65 642D4365 72746966 69636174 652D3133 31323532
30393630 819F300D 06092A86 4886F70D 01010105 0003818D 00308189 02818100
D1D20BAE AE0D9EF4 049AF361 1FFAC404 33C7940F 0EC84FA3 52470085 11BE1B6F
EF7795D5 D81F0AD5 25D3668A 7004C157 BC4C4AE6 84A3302A CE774AAF E388A3BE
1249476C 396F042A 90DA38B8 5C413D4E 1C6A9405 80A12F74 50F6571E DC11306E
6AFFB6DF FB6E9292 96EE61A6 9EF87310 E4722DB3 3B10368D C737BAE4 93F3B759
02030100 01A36730 65300F06 03551D13 0101FF04 05300301 01FF3012 0603551D
11040B30 09820753 77697463 682E301F 0603551D 23041830 168014CE 95CAC648
8F3F96AE B382A38E 4AC7B6BF 9DEB9F30 1D060355 1D0E0416 0414CE95 CAC6488F
3F96AEB3 82A38E4A C7B6BF9D EB9F300D 06092A86 4886F70D 01010405 00038181
0063BCAE 64F7D969 244A07C3 B0D70FEF 00E78CF7 4EF017BE 72745FED 090AF5DA
7420B4BD EAB89849 C7241FAE A8496714 5BF6331F A6936762 A861756E A55A43D8
9366AAB5 C55DECEE F84AFC63 964834C0 E917FCF5 DA5B9043 FD0365B6 03351CA8
7C4EAB92 831BA642 DD210D4B 0C21E6A8 F0BDA231 3AF9652C D376DAC2 1E17ABFC DB
quit
spanning-tree mode pvst
spanning-tree extend system-id
auto qos srnd4
port-channel load-balance src-dst-ip
vlan internal allocation policy ascending
interface Port-channel1
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
interface Port-channel2
switchport trunk native vlan 99
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
interface FastEthernet0
no ip address
shutdown
interface GigabitEthernet1/0/1
switchport trunk native vlan 99
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 2 mode on
interface GigabitEthernet1/0/2
switchport trunk native vlan 99
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 2 mode on
interface GigabitEthernet1/0/3
switchport trunk native vlan 99
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 2 mode on
interface GigabitEthernet1/0/4
switchport trunk native vlan 99
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 2 mode on
interface GigabitEthernet1/0/21
description BH-C2960S-01 GI 1/0/21 trunk connection to Watchguard Firebox
switchport trunk native vlan 99
switchport mode trunk
interface GigabitEthernet1/0/22
description Switch connection to AP
interface GigabitEthernet1/0/23
description BH-2960S-01 GI 0/22-24 trunk connection to BH-HPJ9022A-01 gi 47-48
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet1/0/24
description BH-2960S-01 GI 0/22-24 trunk connection to BH-HPJ9022A-01 gi 47-48
switchport trunk allowed vlan 1,40,45,50,55,60
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet1/0/25
interface GigabitEthernet1/0/26
interface GigabitEthernet1/0/27
interface GigabitEthernet1/0/28
interface Vlan1
ip address 192.168.87.14 255.255.255.0
interface Vlan40
ip address 172.16.10.3 255.255.255.0
no ip http server
ip http secure-server
line con 0
exec-timeout 30 0
password admin
line vty 0 4
access-class vty_ports in
exec-timeout 30 0
password admin
login
length 0
line vty 5 15
access-class vty_ports in
exec-timeout 30 0
password admin
login
end

Similar Messages

WLC 2504 LAG is not working?

Hi All,
Yesterday i configured LAG on my New WLC using following configuration:
Enable LAG on controller > General
then reboot
On Neighbor Switch:
Interface range GigabitEthernet <Interfce ID>
Channel-group <id> mode on
no sh
Interface port-channel <id>
switchport trunk allowed vlan <id>
switchport mode trunk
no sh
i can see on switch trunk is established.
I also tag the LAG to my management vlan.
But still not working, can any one help me to find what going wrong.
I have HA device i configure same on that it worked. But not working on my primary
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 16.0
Build Type....................................... DATA + WPS
System Name......................................
System Location..................................
System Contact...................................
System ObjectID..................................
IP Address.......................................
IPv6 Address..................................... ::
Last Reset....................................... Software reset
System Up Time................................... 0 days 0 hrs 21 mins 0 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
--More-- or (q)uit
Configured Country...............................
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +28 C
External Temperature............................. +33 C
Fan Status....................................... 4300 rpm
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Burned-in MAC Address............................
Maximum number of APs supported.................. 75
System Nas-Id....................................
WLC MIC Certificate Types........................ SHA1

Try to delete the config on switch and try this.
Switch config :
interface range <>
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan X,Y,Z
Channel-group <> mode on
Still not working then check if WLC is reachable via ssh or telnet!
if you have access via ash or telnet then reboot WLC by using "reset system" command .
hope it helps.
Regards
Dont forget to rate helpful posts

WLC 2504 Code Issue

Hey All:
Ran into a strange issue today, two 2504 controller's, one upgraded (from 7.2 to 7.0 due to 1310 not working) to the new firmware fine, the other chucks back a signauture issue, i've seen alot of post's about the 5508 having this issue, but not much about the 2504, anyone got any idea's
The unit not working has PSJ15 serial number which i believe is from 2011, the working unit has a PSJ16 serial number. Any idea's would be very helpful
I dont want to shoot the disty down until i have some input
Matt

Console into the 2504 and run the upgrade from the CLI:
transfer download serverip    ip address of tftp server
transfer download datatype code
transfer download filename   --filename of image
transfer download tftpMaxRetries 5
transfer download tftppktTimeout 3
debug transfer tftp enable   --shows transfer progress
transfer download start

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 advance

Yes.. 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"

Best practices for network design on WLC 2504 and 5508

Dear all:
I'm looking for some recommendations on WLC 2504 and 5508 about the the following:
Maximum amount of AP per port
The scenario when to use all ports in both WLC
Maximum number of clients(users) per port
Bandwidth comsumption of management vs data in order to assign one port for management
I've just found this:
Cisco 5508 controllers have eight Gigabit Ethernet distribution system ports, through which the controller can manage multiple access points. The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller. Cisco 5508 controllers have no restrictions on the number of access points per port. However, Cisco recommends using link aggregation (LAG) or configuring dynamic AP-manager interfaces on each Gigabit Ethernet port to automatically balance the load. If more than 100 access points are connected to the 5500 series controller, make sure that more than one gigabit Ethernet interface is connected to the upstream switch.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/6-0/configuration/guide/Controller60CG/c60mint.html
Thanks for your help.

The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller.
This is an old document. 5508 can now support up to 500 APs if you run firmware 7.X. 2504 can support up to 75 APs if you run firmware 7.4.X.
I'm looking for some recommendations on WLC 2504 and 5508 about the the following:
Best practice and recommendation is to LAG all ports so you will be able to form a link redundancy. If one link goes down, you have other link to push traffic.

WLC 2504 redundancy set up

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 you

Hello,
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

DEBUG-4-INVALID_MODULE on the WLC 2504 with version 7.6.100????

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,
Eric

Thanks 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
Thanks

To 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

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 advanced

Frank,
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

Two WLC 2504 in same Network

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

Cisco WLC 2504 sofware update

Dear Friends,
I am using Cisco WLC 2504 current software version is 7.0.220.0 and I want to upgrade it to the latest version which is 8.x.x.x.
Could you please help and advice the best way of doing it? Also can I upgrade direct to the latest version or do I have to upgrade step by step?
Thank you very much for your help and support.
Thanks
Umar

Hi
Could you please help and advice the best way of doing it? Also can I upgrade direct to the latest version or do I have to upgrade step by step?
Yes, you can go directly to 8.0.x from 7.0.x code. Refer below link
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn80mr1.html#68333
Make sure you refer the release notes for any known issues with this code. Also upgrade FUS to 1.9.0.0 as well. This will take around 30 min downtime as well.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
If you have different AP models, MSE, Prime products, refer this compatibility matrix as reference.
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
HTH
Rasika
**** Pls rate all useful responses ****

WLC - 2504

Hi people,
Does some body can help me, I'm setting a WLC 2504 HA (high availability) and after the tests I noticed that when the primary controller get down the AP (Access Points) take about 20 minutes to register on th secundary controller (I'm not sure if its correct).
There's an other point, when i log in on the SSID of the any AP (wireless net), I can't manage the controller and when a use net cable I can.
TKs

Hello,
To add the ability to manage your WLC via wireless you must enable the feature on the 2504.
Click Management > Mgmt Via Wireless. Check the mark and click Apply
For your HA issue, can you add a bit more information about your two controllers?
What version of code are both WLC's running? (show sysinfo)
Ensure your HA is configured on each AP. It sounds like you may be running two different codes or that the APs are not configured for HA properly.
Thank you

Iphones, Ipads face problem while shifting between diffrent WLAN on WLC 2504

Dear All,
I just create second SSID for different WLAN on my WLC 2504, all client other then Apple devices are successfully able to connect to new SSID a dnd can swap between two SSIDs but apple device unable to shift to new SSID, if any apple device is not connected to to any of SSID (Fresh connection) then that device is able to connect either of SSID but then unable to swap to other SSID. I enable Fast Transition on WLC as well but no improvement. can any one help me to sort out this issue
WLAN 10.10.10.0/24 SSID1
WLAN 10.10.20.0/24 SSID2
Thanks & Regards
Zohaib

Issue resolved :) by configuring fast SSID changing
got help on following link
https://supportforums.cisco.com/discussion/11527996/difficulty-apple-ios-devices

WLC 2504 LAG - Issue

Similar Messages

Maybe you are looking for