Upgrading the WLC 2006 controller
i need to upgrade my WLC from 3. to 4. version but this is the first time i've had to upgrade a controller. So I'm not sure what to expect.
Any pointers I should know before going into that project?
Thanks
Should not be a big issue... check the upgrade path:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml
You need a tftp server to download from, that accepts large files, I use tftpd without any problem...
hth
Jerome
Similar Messages
-
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 -
AIR-CAP1602i cannot join a WLC 5508 controller
Hello,
I'm managing a large number of access points on a Cisco wlc 5508 controller.
We've recently purchased a bunch of new AIR-CAP1602I-E-K9.
note that we already have AIR-CAP1602I-E-K9 and other models in production.
These A.P are not able to join the controller for some reason, I've tried a lot of different things but I am now at a loss.
I have checked the regulatory domain, upgraded the FUS, manually upgraded the software version of the LAP to match the version on the other A.P.
I even downgraded/upgraded the WLC code (version 7.4.x and 8.0)
I use the dhcp option 43 to to send the controller IP.
Here are the info that can help:
errors:
#on A.P
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
#on WLC
Lwapp join request rejected (WLC version 7.6.130.0)
Failed to add database entry (WLC version 8.0)
WLC sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... XXX
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... XXX
Last Reset....................................... Software reset
System Up Time................................... 6 days 4 hrs 16 mins 27 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... Multiple Countries:CA,FR
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +41 C
External Temperature............................. +22 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 1977
Burned-in MAC Address............................ A4:93:4C:B0:E4:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 250
AP sh version
AP58f3.9cb8.3701#sh version
Cisco IOS Software, C1600 Software (AP1G2-K9W8-M), Version 15.2(4)JB6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 22-Aug-14 10:56 by prod_rel_team
ROM: Bootstrap program is C1600 boot loader
BOOTLDR: C1600 Boot Loader (AP1G2-BOOT-M) LoaderVersion 15.2(2)JAX, RELEASE SOFTWARE (fc1)
AP58f3.9cb8.3701 uptime is 31 minutes
System returned to ROM by power-on
System image file is "flash:/ap1g2-k9w8-mx.152-4.JB6/ap1g2-k9w8-mx.152-4.JB6"
Last reload reason:
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP1602I-E-K9 (PowerPC) processor (revision B0) with 229366K/32768K bytes of memory.
Processor board ID FGL1832X5QU
PowerPC CPU at 533MHz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.6.100.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 58:F3:9C:B8:37:01
Part Number : 73-14671-04
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC183171L4
Top Assembly Part Number : 800-38552-01
Top Assembly Serial Number : FGL1832X5QU
Top Revision Number : A0
Product/Model Number : AIR-CAP1602I-E-K9
AP sh inventory
NAME: "AP1600", DESCR: "Cisco Aironet 1600 Series (IEEE 802.11n) Access Point"
PID: AIR-CAP1602I-E-K9 , VID: V01, SN: FGL1832X5QU
Thanks for your help !Hi Olivier,
The error messages that you have on the debugs:
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
It is related to the bug: CSCuh46442
https://tools.cisco.com/bugsearch/bug/CSCuh46442/?referring_site=ss
This bug is resolved in version : 8.0.100.0
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn80.html#pgfId-1163951
Can you please paste here "show ap auth-list" from the controller CLI?
I suggest to enable MIC if it is not enabled, and then check if the AP's will join or not.
Kind Regards
Mohammad Setan -
I cannot seem to get past the "transfer download start" (CLI) or "download" (GUI) phase of the upgrade on a WLC-2006 -- from 3.2.171.5 to 4.2.209.0. The transfer consistently times out at about 76% complete and I receive an error message, either "error writing to flash" or "error writing output file" (or something similar). Any suggestions/recommendations would be greatly appreciated.
You can't upgrade from 3.X to 4.2.209 direct. You need to upgrade to 4.0.206.0 first before going anyware. It's specified in the Release Notes.
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn422090.html#wp233853 -
When I open iPhoto 9.2.1 it says that my library needs to be upgraded but when I upgrade the library I am trying to open (33 GB worth of pictures from 2006) the new application says it cannot read the files and how to find them on the system to reimport?! and then I'd like to erase the original files since the space requirement is huge!!!! Why is upgrading software iPhoto such a pain. I've gotta get a presentation done and all I get for my money is roadblock!!!
hello, it sounds like the library is damaged.
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. -
Is It Possible To Upgrade The Graphics Card In A Late 2006 MacBook (original)?
I have this Late 2006 Macbook, that still runs great and everything, but the only problem iv been running into, is video. So when i watch a video in QuickTime Player, or QuickView, or even YouTube, the video just randomly starts to flip out. So, is it possible to upgrade the Graphics Card?
Sorry, not possible.
-
*** WARNING *** Upgrade to 5.0 may require isolating LWAPs from the WLC
Before you run into the problem that we ran into when one of our larger customers upgraded from 4.2 to 5.0 and the result was that the controllers got caught in a loop during the upgrade and took the entire WLAN down.
Please be advised that Cisco recommends that you ISOLATE all lightweight access points from their controller during the upgrade of the controller from 4.2 to 5.0.
In part, this is due to a bug in 4.2.xx that starts upgrading the LWAP software images before the controller finishes updating/rebooting. This can cause interruption to the LWAPs as they upgrade their software from the controller when it reboots.
I have also heard of some situations where the LWAPs get corrupted to such a degree where you may have to out and physically access/reset the LWAPs that were interrupted during the upgrade process. I believe the worst-possible-case for this would be limited to no more than 10 LWAPs per controller
that can upgrade at a time)
In our case, the result was that the upgrade process hung up - with some LWAPs stuck, and all other LWAPs unable to pass traffic through the upgraded (ver 5.0) controller because they were at the previous revision (4.2).
In our case, this resulted in a system-twide WLAN outage.
As part of the call into Cisco TAC, the engineer said, in effect, 'why didn't you ignore the release notes instructions and isolate your controller from the LWAPs during the upgrade?'.
Our response was, we would have done so if it had been in the release notes (which it is not). So, after much cajoling by us, TAC finally agreed that it might be a good idea to include this additional step in the release notes.
Please reference the bug which requests an update to the 5.0 release note installation instructions: CSCso02420
TAC is aware of this problem and it is my understanding that there is discussion at Cisco regarding a maintenance release for 4.2 (since 4.2 is where the problem actually lies). The maintenance release would be applied to 4.2 controllers PRIOR to upgrading them to 5.0.
In the meantime, if you are still anxious to upgrade to 5.0, one workaround is to isolate the LWAPs from the controller either by:
1) Physically disconnecting the controller from the network during the upgrade and reconnecting it after its upgrade/reboot is complete.
or
2) Temporarily disabling the VLAN that carries the LWAP traffic to/from the LWAPs/Controller and re-enabling the VLAN after the upgrade/reboot of the controller.
I hope that this is helpful for anyone out there who is about to upgrade to 5.0.
I hope your upgrade goes smoother than our customer's did.
- John
(Please remember to rate helpful posts)FYI - I noticed these messages in the message log on a 4.0.179.11 controller, sourced from 4.2 controllers.
Fri Mar 14 17:14:36 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:36 2008 [ERROR] mm_listen.c 4157: Mobility packet IP-message IP mismatch: pkt: 172.20.48.68 msg: 215.42.227.2
Fri Mar 14 17:14:36 2008Fri Mar 14 17:14:33 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:33 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:32 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:32 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:32 2008 [ERROR] mm_listen.c 4157: Mobility packet IP-message IP mismatch: pkt: 172.20.48.6 msg: 215.42.227.24
Fri Mar 14 17:14:32 2008Fri Mar 14 17:14:29 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:29 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:26 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:26 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:23 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:23 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:22 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:22 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:19 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:19 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:16 2008 [ERROR] ethoip.c 305: ethoipSocketTask: ethoipRecvPkt returned error
Fri Mar 14 17:14:16 2008 [ERROR] ethoip.c 106: Eth-over-IP pkt too short; pkt size=82, expected min=66
Fri Mar 14 17:14:13 2008 [ERROR] mm_listen.c 4157: Mobility packet IP-message IP mismatch: pkt: 172.20.48.4 msg: 215.42.227.24 -
Upgraded the 4402 controller to version 6, gui doesn't work
I upgraded the 4402 to version 6 by upgrading to 4.1.192 mesh and then to 6. I could see 4.1.192 but after upgrading I could not get into the gui. I could telnet in but that was pretty brutal. What did I do wrong?
thanks
GaryActually when 6 installs it blows away the config. I had to come in and hook up the console cable. I usually hook one up to a laptop so I can always get to the controller but I didn't this time. I thought it was something I did but this controller proceeded to upgrade a controller in another building 20 miles away. The users complained they couldn't log in. When I got there and hooked up the console cable and rebooted version 6 got installed on there and the config was blown away. I had to tell it to boot from the secondary because I have some 1000 series APs still there. I had to recreate it and now everything is fine.
Gary -
Hi, I am setting up a WLC2006 with 2 AP1010's. I cannot get the controller to see either AP. When I place the AP's on a network with a WLC 4400, they are recogized immediately by the 4400 at Layer-2 LWAPP.
Since the WLC2006 only works at Layer-3 LWAPP, do I have an AP icompatibility issue with the AP1010's(since I can only get them to work at Layer-2 LWAPP)?
Any advice is greatly appreciated.
ChrisAccording to Cisco doc., L2 mode is supported by WLC 44xx & 41xx and not supported by WLC 2006. And the 1010 supports L2 mode only, so the 1010 cannot works w/ 2006. You have to upgrade the AP to 1200, 1130 or 1240 or the WLC to 4xxx. And, don't know is there any future IOS / firmware can support it. Hopes this help.
-
I'm wondering if there are any options I can try for the following situation:
Professional sports arena has a small wireless deployment intended for use by media during games for research and submitting updates. Currently four APs on a WLC2006 (4.2.61) with a dedicated DSL connection for internet access. Only about 20-30 users typically and other than game time very stable. WLAN setup with an open SSID using web-auth to keep from needing to deal with support for encryption for visiting people. But during games with all the spectators the associations go way up due to iphones, driods, etc.. Eventually the performance starts dropping to the point where web-auth stops working. On the console (web unresponsive) I got CPU utilization staying at 80-98% and client counts of up to 180.. Too much for a 2006 I'm going to assume?
A couple options off the top of my head:
Turn on some form of encyption to reduce the number of associations, but this possibly opens up a requirement for additional support that may be needed to get non-technical users connected that need to.
More powerful controller? I haven't really been able to find anything yet on scalability expectations for the WLCs for this situation. Also don't believe there is a budget for any serious upgrade right now.
Any other thoughts or ideas anyone has that might help?Hi David, 4.2.61 is one of the worst release to chose. In general the first release of a branch is not the best one.
4.2.209 is still the same code branch and is the most stable software out there. There has been a couple of bugs with web authentication not working under load.
Now you have another good point, that many clients on only 6 APs and a 2006 is a undersized network. 30 clients per AP is over recommendations. And the fact that some might stay in "web auth required" state means they have a special ACL applied and consume a lot of CPU on the WLC ...
The encryption is done by the AP, so WLAN encryption will not change anything to WLC CPU usage.
Regards,
Nicolas -
Upgrade two WLC 5508 with HA SSO from 7.5.102.0 to 7.6.130.0 combined with FUS 1.9
The running config is:
- Two WLC5508's in HA SSO setup running version 7.5.102.0
- about 130 x 2602i APs
I need to upgrade to 7.6.130.0 using the pre-download feature to minimize the network downtime.
Is it possible to transfer the 7.6 to the controllers and pre-download 7.6 to all APs, then do the FUS 1.9 upgrade and finally start the actual controller upgrade to 7.6.
So the steps would be:
1. Transfer 7.6 image to primary controller (do not reboot!), so still running 7.4 as active image.
2. Start pre-download of 7.6 image to all APs and wait till all APs have the new image (do not know how long it takes for 130 APs).
3. Upgrade both controllers with FUS 1.9 (HA should upgrade both controllers automatically) (takes about 45 minutes?)
4. Make 7.6 image the active/primary image on controllers and APs and reset controllers.
If the steps above will not work, I would need to upgrade FUS 1.9 which means 1 hour downtime and then start the pre-download to all APs. The pre-download can take a long time I heard, so I need to wait and wait before I can start the 7.6 upgrade, which means another 1 hour downtime.
This way I need two maintenance windows instead of one. So would it be possible to combine the pre-download and FUS?
Regards,
Bjorn>Do I need to upgrade the FUS 1.9 before the 7.6 image or can I do the FUS afterwards? If I can do it afterwards, I can do the upgrades in the same maintenance window. This way I can start the pre-download the day before, so I am pretty sure the APs have the image at the time of the maintenance window.
>I cannot find any remarks about the required order of installation (FUS -> image or image -> FUS).
Release Notes for Wireless LAN Controller Field Upgrade Software for Release 1.9.0.0 - p2 :
* This release of the Field Upgrade Software is applicable to CISCO WLC's that are installed with the controller software release 6.0 and later.
So strict reading implies that you have to run 7.6 first.
M. -
Does the 2006 WLC support LAG (i.e., logically connecting its 4 100 Mb/s ethernet ports together like EtherChannel)?
ThanksHi Friend,
Unfortunately this feature is not available on 2006 controller.
Only 4404, 4402 supports lag.
HTH
Ankur
*Pls rate all helpfull post -
Hello Guys,
I have converted ap 1131 from autonomous to lwapp successfully by using upgrade utility tool but the AP does not join the WLC 2106. I can see it as a neighbor on the switch with no IP address. please help me.
Thank youHello Scott,
Thank you for the reply
Please find the attached file for the config, i found out that i have not updated the time on WLC but i did update the time on WLC and tested for other AP and this one too wont join the WLC. The ap are located remote.
atsg-wl1#show run | incl hostname
hostname atsg-wl1
atsg-wl1#test pb display
Display of the Parameter Block
Total Number of Records : 7
Number of Certs : 6
Number of Keys : 1
atsg-wl1#term length 0
atsg-wl1#show version | include Cisco IOS
Cisco IOS Software, C1130 Software (C1130-K9W7-M), Version 12.3(7)JA3, RELEASE SOFTWARE (fc1)
atsg-wl1#show controller | include Radio AIR
Radio AIR-AP1131G, Base Address 0019.0737.02f0, BBlock version 0.00, Software version 5.80.15
Radio AIR-AP1131A, Base Address 0019.073b.02d0, BBlock version 0.00, Software version 5.80.15
atsg-wl1#show controllers d0 | include Current
Current Frequency: 2447 MHz Channel 8
Current CCK Power: 14 dBm
Current OFDM Power: 14 dBm
Current Rates: basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
atsg-wl1#show controllers d1 | include Current
Current Frequency: 5805 MHz Channel 161
Current Power: 17 dBm
Current Rates: basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0
atsg-wl1#show run | include station-role
station-role root
station-role root
atsg-wl1#test pb disp
Display of the Parameter Block
Total Number of Records : 7
Number of Certs : 6
Number of Keys : 1
atsg-wl1#show int F0 | include address
Hardware is PowerPCElvis Ethernet, address is 0019.555f.ccfa (bia 0019.555f.ccfa)
atsg-wl1#show int | include Dot11Radio
Dot11Radio0 is up, line protocol is up
Dot11Radio1 is up, line protocol is up
atsg-wl1#show sntp | exclude SNTP
10.148.0.1 16 1 never
172.16.21.57 16 1 never
Broadcast client mode is enabled.
atsg-wl1#show run
Building configuration...
Current configuration : 6025 bytes
! Last configuration change at 19:35:46 UTC Thu Jan 31 2013 by didata
! NVRAM config last updated at 19:13:48 UTC Fri Feb 1 2013 by didata
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime localtime
service password-encryption
hostname atsg-wl1
logging buffered informational
logging console informational
enable secret 5
ip subnet-zero
ip domain name aspentech.com
ip name-server 10.96.16.230
ip name-server 10.148.0.249
ip name-server 10.32.19.1
aaa new-model
aaa group server radius rad_eap
server 10.16.16.123 auth-port 1645 acct-port 1646
aaa authentication login default group tacacs+ local
aaa authentication login eap_methods group rad_eap
aaa authentication login mac_methods local
aaa authentication enable default group tacacs+ enable
aaa authorization exec default group tacacs+ local
aaa authorization commands 15 default group tacacs+ local
aaa accounting exec default start-stop group tacacs+
aaa accounting commands 15 default start-stop group tacacs+
aaa accounting system default start-stop group tacacs+
aaa session-id common
no dot11 igmp snooping-helper
dot11 ssid
authentication open eap eap_methods
authentication network-eap eap_methods
guest-mode
infrastructure-ssid optional
dot11 network-map
power inline negotiation prestandard source
usernamepassword 7
username privilege 15 password 7
usernamep rivilege 15 password 7
class-map match-all _class_Protocol_301_C351
match access-group name Voice_Over_IP_301
class-map match-all _class_8
match ip dscp cs1
class-map match-all _class_0
match ip dscp default
class-map match-all _class_48
match ip dscp cs6
class-map match-all _class_18
match ip dscp af21
class-map match-all _class_24
match ip dscp cs3
class-map match-all _class_16
match ip dscp cs2
class-map match-all _class_34
match ip dscp af41
class-map match-all _class_26
match ip dscp af31
class-map match-all _class_40
match ip dscp cs5
class-map match-all _class_46
match ip dscp ef
class-map match-all _class_56
match ip dscp cs7
class-map match-all _class_10
match ip dscp af11
class-map match-all _class_32
match ip dscp cs4
policy-map _policy_Voice_Over_IP_202
class _class_Protocol_301_C351
set cos 6
policy-map _policy_fallback_policy
class _class_0
set cos 0
class _class_8
set cos 1
class _class_10
set cos 1
class _class_16
set cos 2
class _class_18
set cos 2
class _class_24
set cos 3
class _class_26
set cos 3
class _class_32
set cos 4
class _class_34
set cos 4
class _class_40
set cos 5
class _class_46
set cos 5
class _class_48
set cos 6
class _class_56
set cos 7
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
shutdown
encryption mode wep mandatory mic key-hash
broadcast-key change 900
ssid
traffic-class background cw-min 5 cw-max 8 fixed-slot 2
traffic-class best-effort cw-min 5 cw-max 8 fixed-slot 6
traffic-class video cw-min 4 cw-max 6 fixed-slot 1
traffic-class voice cw-min 3 cw-max 7 fixed-slot 1
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
packet retries 32
fragment-threshold 2338
station-role root
rts threshold 2339
rts retries 32
world-mode legacy
no cdp enable
infrastructure-client
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface Dot11Radio1
no ip address
no ip route-cache
shutdown
encryption mode wep mandatory mic key-hash
broadcast-key change 900
ssid aspen100abcdefgh
speed basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0
station-role root
world-mode legacy
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface BVI1
ip address 10.148.0.7 255.255.255.0
no ip route-cache
ip default-gateway 10.148.0.1
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip tacacs source-interface BVI1
ip radius source-interface BVI1
ip access-list extended Voice_Over_IP_300
permit 119 any any
permit ip any any
ip access-list extended Voice_Over_IP_301
permit 119 any any
permit ip any any
logging facility local0
snmp-server view iso_view iso included
snmp-server community admin view iso_view RW
snmp-server community all4114all view iso_view RW
snmp-server community ddbos2000 RO
snmp-server location ATSG
snmp-server contact James Lee
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps tty
snmp-server enable traps disassociate
snmp-server enable traps deauthenticate
snmp-server enable traps authenticate-fail
snmp-server enable traps config
snmp-server enable traps syslog
snmp-server host 192.135.137.12 ddbos2000
tacacs-server host 10.16.16.123 key 7
tacacs-server host 10.96.16.245 key 7
tacacs-server directed-request
radius-server host 10.16.16.123 auth-port 1645 acct-port 1646 timeout 5 retransmit 3 key 7
radius-server deadtime 120
radius-server vsa send accounting
radius-server vsa send authentication
control-plane
bridge 1 route ip
line con 0
transport preferred all
transport output all
stopbits 1
line vty 0 4
exec-timeout 0 0
transport preferred all
transport input all
transport output all
line vty 5 15
exec-timeout 0 0
transport preferred all
transport input all
transport output all
end
atsg-wl1#show run | incl hostname
hostname atsg-wl1
atsg-wl1#arch down /over /create-space tftp://10.148.0.118/images/c1130-rcvk $over /create-space tftp://10.148.0.118/images/c1130-rcvk9 w8-tar.12 te-space tftp://10.148.0.118/images/c1130-rcvk9w8-tar.123 -11.JX1.t ftp://10.148.0.118/images/c1130-rcvk9w8-tar.123-11.JX1.ta r
examining image...
Loading images/c1130-rcvk9w8-tar.123-11.JX1.tar from 10.148.0.118 (via BVI1): !
extracting info (273 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1873920 bytes]
Image info:
Version Suffix: rcvk9w8-
Image Name: c1130-rcvk9w8-mx
Version Directory: c1130-rcvk9w8-mx
Ios Image Size: 1874432
Total Image Size: 1874432
Image Feature: WIRELESS LAN|LWAPP|RECOVERY
Image Family: C1130
Wireless Switch Management Version: 3.0.51.0
Extracting files...
Loading images/c1130-rcvk9w8-tar.123-11.JX1.tar from 10.148.0.118 (via BVI1): !
extracting info (273 bytes)
c1130-rcvk9w8-mx/ (directory) 0 (bytes)
extracting c1130-rcvk9w8-mx/c1130-rcvk9w8-mx (1867816 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
extracting c1130-rcvk9w8-mx/info (273 bytes)
extracting info.ver (273 bytes)!
[OK - 1873920 bytes]
Deleting current version...
Deleting flash:/c1130-k9w7-mx.123-7.JA3...done.
New software image installed in flash:/c1130-rcvk9w8-mx
Configuring system to use new image...done.
atsg-wl1#show archive status
SUCCESS: Upgrade complete.
atsg-wl1#write erase
Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]
[OK]
Erase of nvram: complete
atsg-wl1#dir flash:
Directory of flash:/
2 -rwx 2072 Jan 31 2013 19:36:18 +00:00 private-multiple-fs
149 drwx 128 Jan 31 2013 19:36:11 +00:00 c1130-rcvk9w8-mx
4 -rwx 342 Jan 31 2013 19:36:14 +00:00 env_vars
15998976 bytes total (14126080 bytes free)
atsg-wl1#dir nvram:
Directory of nvram:/
30 -rw- 0 startup-config
31 ---- 0 private-config
1 -rw- 0 ifIndex-table
2 ---- 12 persistent-data
32768 bytes total (30668 bytes free)
atsg-wl1#sh crypto ca trustpoints
atsg-wl1#sh crypto ca certificates
atsg-wl1#terminal length 0
atsg-wl1#show run | begin BVI1
interface BVI1
ip address 10.148.0.7 255.255.255.0
no ip route-cache
ip default-gateway 10.148.0.1
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip tacacs source-interface BVI1
ip radius source-interface BVI1
ip access-list extended Voice_Over_IP_300
permit 119 any any
permit ip any any
ip access-list extended Voice_Over_IP_301
permit 119 any any
permit ip any any
logging facility local0
snmp-server view iso_view iso included
snmp-server community admin view iso_view RW
snmp-server community all4114all view iso_view RW
snmp-server community ddbos2000 RO
snmp-server location ATSG
snmp-server contact James Lee
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps tty
snmp-server enable traps disassociate
snmp-server enable traps deauthenticate
snmp-server enable traps authenticate-fail
snmp-server enable traps config
snmp-server enable traps syslog
snmp-server host 192.135.137.12 ddbos2000
tacacs-server host 10.16.16.123 key 7
tacacs-server host 10.96.16.245 key 7
tacacs-server directed-request
radius-server host 10.16.16.123 auth-port 1645 acct-port 1646 timeout 5 retransmit 3 key 7
radius-server deadtime 120
radius-server vsa send accounting
radius-server vsa send authentication
control-plane
bridge 1 route ip
line con 0
transport preferred all
transport output all
stopbits 1
line vty 0 4
exec-timeout 0 0
transport preferred all
transport input all
transport output all
line vty 5 15
exec-timeout 0 0
transport preferred all
transport input all
transport output all
end -
I would like to allow client to access wireless lan based on the client mac-address.
How I config it on WLC 2006 locally (not using radius server)? If yes, How mnay mac-address can be configured on the wlc2006?
Thanks.
DouglasHi Douglas,
Just wanted to add a note to Ankurs good info;
Maximum MAC Filter Entries
The controller database can contain up to 2048 MAC filter entries for local netusers. The default value is 512. To support up to 2048 entries, you must enter this command in the controller CLI:
config database size MAC_filter_entry
where MAC_filter_entry is a value from 512 to 2048.
From this good doc;
http://www.cisco.com/en/US/products/ps6366/prod_release_note09186a0080813b1c.html#wp42756
MAC Filtering
http://www.cisco.com/en/US/products/ps6366/products_user_guide_chapter09186a00805a6ad0.html#wp1040588
Hope this helps!
Rob -
Rolling upgrade of WLC 4402 controllers and APs
In need to upgrade the software on two WLC 4402 controller in a hospital. Both WLCs have the same config and one is primary (has all APs connected) and the other backup (no APs connected.) The APs are placed so there is still coverage if one goes down in an area. My question - is it possible to do a rolling upgrade to have no downtime for the wireless clients? My plan would be to upgrade the backup WLC then selectively move APs to it. If I swap the primary and secondary controllers in the high availability tab on each AP, do I need to do a reset (General - Hardware Reset) or will it automatically reboot and connect to the upgraded backup controller? When I'm done, I'd upgrade the primary controller and now call that backup. Does this make sense?
I've done this same sort of thing on a slightly larger scale about 5 times now at the hospital I work at. Quick answer is "Yes, it is possible to do a rolling upgrade and have no downtime for wireless clients."
I've got 5 WLC's, and I use the high availability tab to move all the AP's off one, upgrade it, and move all the AP's from the next WLC over to it, upgrade that one, etc.
The thing you need to be careful of is your timing and your choice of APs to move.
It generally takes about a minute to move an AP between WLCs running the same version. But if there's a version change that makes the AP upgrade, you're looking at about 6 minutes.
I do them one at a time, and when they show up in the WLC as being up, running and happy for 1 minute, I do the next one. And so on. Takes me about 3 days to go through all 5 WLCs and 375 APs. Not once have I had a user notice the move.
Also, in order to test, after I do the first upgrade, I move just one area's APs into that WLC for a day and then test the various flavors of gear we have (phones, infusion pumps, laptops, etc.) to confirm that the new version doesn't have any trouble. Sometimes it does and I work with TAC to get things resolved before I do the whole hospital.
jh
Maybe you are looking for
-
LabView 7.1 SIT: how can I modify the LV-Simulink connections during execution?
Hi! I'm using LabView 7.1 (with the SIT toolkit) to make a user interface for a Simulink model. The problem I'm encountering is that the Simulink parameters aren't always linked to the same LV controls, depending on the options selected by the user.
-
Problem In Business Partner Creation
Hi to all, I have around 900 BP in BP master which i export from another company. Now i try to create a new BP it gives error that 'This entry already exists in the following tales business master OCRD message (131-183).I checked in dat
-
How to classify new and old user account from idm system using SPML
hi all, i can use SPML code to create new user on IDM system but, i can't classifying new or old user account any advise ? very thank you in advanced. athikom.
-
Using iPhoto '08 Library w/ Adobe Bridge?
How can import my iPhoto '08 Library into Adobe Bridge?
-
How do I customize the index page?
I can't seem to find out how to edit the default index page (ie content, banner, etc.) without it losing the theme or the css file, which i guess is somehow linked to it? The page points to "collaboration/css/serverhome_static.css" which doesn't seem