WLC 2504 firmware upgrade

Upgraded my Cisco 2504 from 7.0.220.0 to 7.4.111.0
and upgraded my field upgrade bootloader to 1.0.18.
Now I cannot configure my WLC from the web via IP. Had it configured properly with VLAN, switch and my ASA 5520.
Does this have to do with the ACL's on the WLC.
I've been looking for documentation can't find much in terms of best practices for traffic.
My CPU ACL on wired and wireless are disabled with no ACL for the CPU.
Any suggestions or help would be greatly appreciated.
Thank you
Carlos

Hello Scott,
     I figured it out. I had to do from CLI a reset system command. Once I did that everything came back up. I did not know that field upgrade and firmware upgrade took so long. The instructions say to just to a save and reboot. I found out that you need to do a reset system command again from the CLI.
Appreciate the assistance.

Similar Messages

  • WLC 5508 Firmware Upgradation

    Hi All,
    WLC 5508 - current firmware 7.0.116.0 is running on it. we need add couple of 2700 series AP. From the release notes i got know 2700 series supported on the 7.6.120.x and later. 
    http://www.cisco.com/c/en/us/td/docs/wireless/access_point/2700/quick/guide/ap2700getstart.html
    - whereas 7.6.120.x is the latest one in the train. can we have this firmware on the controller as its latest??
    - from the release notes - we can have a direct upgrade to 7.6.120.0., upgrading from 7.0.x.x to 7.6.120.x missing so many version in between. any potential problems i may get ??
    - FUS (Field upgrade software is necessary) which version and how it can be installed ??
    Regards,
    Channa

    Hi Channa,
    Go for the 7.6.130.0 (7.6MR3) when it is available to public. To be released within next couple of weeks.If you need to do this before 7.6MR3 comes then you can get pre-release of that code via TAC. Refer below for that.
    https://supportforums.cisco.com/document/12245186/76mr3-beta-availability
    Yes, you have to upgrade your FUS, It is recommended to go for v 1.9.0.0. Below will give you the upgrade procedure. Better to do it via CLI & allocate 30-45min downtime for this upgrade
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
    Feature wise there are lots of feature available in 7.6.x compare to 7.0.x.  But I do not expect any problem going from 7.0.x to 7.6.x as long as you upgrade your FUS first.
    Also read these compatibility matrix to see all your AP models are supporting by this 7.6.x code & any other PI or MSE compatibility if you have those.
    http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • 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

  • WLC 2504 Hangs after upgrading 7.4 firmware

    Hi All
    We have WLC2504 (  Upgraded to Firmware 7.4) and AP'S are AP 1602
    When Wirless Controller trying to Connects AP'S then they are hanging and same is happening for AP'S os we are not able to do configuration.
    Pinging continous is breaking for WLC IP Address.
    We have upgraded to Latest Firmware 7.4...
    I have read that this is Bug in  Firmware 7.4....What is the work around??
    Thanks

    Hi,
    Make sure your WLC 2504 is sync with the NTP Server.

  • Upgrade FUS WLC 2504

    Hi all,
    Eh updated the firmware of my WLC 2504 (FUS) from 1.0.0 to 1.8.0 
    I can again upgrade from 1.8.0 to 1.9.0 ?
    I have read that is recommended once the upgrade of FUS. It is true?

    Hi,
    yes, you can upgrade the firmware again from 1.8 to 1.9.
    it's recommended to upgrade the same firmware version only once.
    The FUS upgrade will take approximately about 30 minutes and it will reboot the WLC several times.
    it's advised to upgrade once the FUS because the WLC reboots and sometimes they will see that the FUS has not upgraded and upgrade again instead of waiting for 30 to 45 minutes.
    However, you can wait for the upgrade of FUS on the WLC to 1.8. once the WLC is stable you can upgrade the FUS again to 1.9.
    Hope this helps.
    Regards
    Salma

  • WLC Firmware upgrade

    I am working on a firmware upgrade on WLC 5508 and WLC 2100 from 7.2.111.3 to 7.4.121.  I have 10 forign controllers and 2 anchor controllers.  My question are:
    (1) Should I upgrade the forign controllers first or anchor controllers first?
    (2) Should I or do I need to upgrade Cisco NCS, 1.1.1.24, after the WLC firmware upgrade?
    (3) SHould I or do I need to upgrade CIsco MSE to latest version?
    Thanks,

    (1) Should I upgrade the foreign controllers first or anchor controllers first?
    Does not matter the order.
    Make sure you upgrade the FUS to 1.9.0.0 version as well
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
    (2) Should I or do I need to upgrade Cisco NCS, 1.1.1.24, after the WLC firmware upgrade?
    Refer the below link (table 4) compatibility matrix, you should have NCS/Prime 1.3.x
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp142297
    (3) Should I or do I need to upgrade CIsco MSE to latest version?
    Refer the table 7 of the above link, you should have MSE 7.4.121.0 as well for compatibility
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp142297
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • 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. 

  • 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 2112 and WLC 2504

    This might be a really stupid question but I need to ask just so that I get a definitive answer. I have a customer that is using a WLC 2112 and has maxed out the licenses for the WLC. I have suggested for him to purchase a 2504 with 30 or 40 licenses to replace the existing 2112. He doesn't want to purchase 30 to 40 licenses and doesn't want to remove the 2112 from the network environment. He would rather purchase a WLC 2504 with 15 licenses and just add that into the network.
    My question is, will there be a problem running a 2504 and a 2112 on the same network? Or can I just make one a primary and one a secondary?

    That should be fine. Just make sure the WLCs are running the same code version and everything should work fine. This is required for APs failover from one WLC to another. You don't want the APs upgrading or downgrading code versions every time the ap moves from the primary to the secondary WLC.
    Sent from Cisco Technical Support iPhone App

  • Compatible APs for Cisco WLC 2504

    Is the cisco wlc 2504 compatible with the AIR-CAP-3602l and if so what firmware would i need to be running on the WLC ? My firm rushed out and bought a mesh solution without doing their homework

    Hi Doug,
    Data sheet for 3602 access point shows it support 2500 series WLC. Please refer to the link below.
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps11983/data_sheet_c78-686782.html
    You may need firmware version above 7.2 to support 3602.
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
    Hope that  helps
    Regards
    Najaf
    Please rate when applicable or helpful !!!

  • 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 ****

  • Cisco 2504 FUS upgrade 1.0.0 to 1.0.9

    Hello everyone,
    I was curious as to if it were possible to upgrade a WLC 2504 running FUS 1.0.0 directly to 1.0.9?  I could not find any information on an upgrade path.  If someone could shed some light on this it would be appreciated.
    Cheers,
    Taylor

    Here is the release notes on FUS 1.9.0.0 upgrade
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • Why LAP1131AG and LAP11412 cannot to join WLC 2504?

    I have WLC 2504, Cisco LAP1131AG and then Cisco LAP1142N. Why LAP1131AG and LAP11412 cannot to join WLC 2504?
    this is error code at the Cisco LAP1131AG
    *Sep 12 19:30:27.730: %CAPWAP-3-ERRORLOG: Go join a capwap controller 
    *Sep 12 19:30:27.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.100.10 peer_port: 5246
    *Sep 12 19:30:57.001: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
    *Sep 12 19:31:27.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.100.10:5246
    *Sep 12 19:31:32.083: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Sep 12 19:31:32.083: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
    *Sep 12 19:31:32.085: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Sep 12 19:31:32.117: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !! 
    *Sep 12 19:31:32.118: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
    *Sep 12 19:31:33.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Sep 12 19:31:33.112: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Sep 12 19:31:33.117: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Sep 12 19:31:34.104: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
    *Sep 12 19:31:34.111: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Sep 12 19:31:34.142: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Sep 12 19:31:34.147: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
    *Sep 12 19:31:34.152: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Sep 12 19:31:35.141: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Sep 12 19:31:35.146: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Sep 12 19:31:35.170: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
    *Sep 12 19:31:36.171: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
    this is version LAP1131AG
    AP0018.18fc.fd58#sh version 
    Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.4(25e)JAO6, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2014 by Cisco Systems, Inc.
    Compiled Fri 22-Aug-14 10:07 by prod_rel_team
    ROM: Bootstrap program is C1130 boot loader
    BOOTLDR: C1130 Boot Loader (C1130-BOOT-M) Version 12.3(7)JA1, RELEASE SOFTWARE (fc1)
    AP0018.18fc.fd58 uptime is 9 minutes
    System returned to ROM by power-on
    System image file is "flash:/c1130-k9w8-mx.124-25e.JAO6/c1130-k9w8-mx.124-25e.JAO6"
    and then this is version WLC2504
    (Cisco Controller) >show 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................................. PIC 16.0
    Build Type....................................... DATA + WPS
    System Name...................................... Cisco_47:19:c4
    System Location.................................. 
    System Contact................................... 
    System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
    IP Address....................................... 192.168.100.10
    Last Reset....................................... Software reset
    System Up Time................................... 0 days 0 hrs 36 mins 45 secs
    System Timezone Location......................... 
    System Stats Realtime Interval................... 5
    System Stats Normal Interval..................... 180
    --More-- or (q)uit
    Configured Country............................... ID  - Indonesia
    Operating Environment............................ Commercial (0 to 40 C)
    Internal Temp Alarm Limits....................... 0 to 65 C
    Internal Temperature............................. +34 C
    External Temperature............................. +40 C
    Fan Status....................................... 4100 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............................ 24:E9:B3:47:19:C0
    Maximum number of APs supported.................. 5
    IP Address management WLC : 192.168.100.10/24
    IP Address LAP1142N :192.168.100.102/24
    IP Address LAP1131AG : 192.168.100.101/24
    Can anyone help my problem?

    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-LAP1142N-A-K9 (PowerPC405ex) processor (revision A0) with 90102K/40960K bytes of memory.
    Processor board ID FGL1439S15W
    PowerPC405ex CPU at 586MHz, revision number 0x147E
    Last reset from reload
    LWAPP image version 7.6.130.0
    1 Gigabit Ethernet interface
    2 802.11 Radios
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: C8:4C:75:79:EB:E9
    Part Number                          : 73-12836-03
    PCA Assembly Number                  : 800-33767-03
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC14234D8Z
    Top Assembly Part Number             : 800-33775-02
    Top Assembly Serial Number           : FGL1439S15W
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-LAP1142N-A-K9  
    cisco AIR-LAP1131AG-A-K9 (PowerPCElvis) processor (revision A0) with 27638K/5120K bytes of memory.
    Processor board ID FTX1026T46E
    PowerPCElvis CPU at 262Mhz, revision number 0x0950
    Last reset from power-on
    LWAPP image version 7.6.130.0
    1 FastEthernet interface
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:18:18:FC:FD:58
    Part Number                          : 73-8962-09
    PCA Assembly Number                  : 800-24818-08
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC102513DE
    Top Assembly Part Number             : 800-25544-06
    Top Assembly Serial Number           : FTX1026T46E
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-LAP1131AG-A-K9  
    Configuration register is 0xF

  • WLC 2504 sudden network instability

    Hello,
    we're running a WLC 2504 with two SSIDs on it. It is connected to to a small PoE switch. Standard untagged vlan. A handfull APs connected to it. No DHCP, the APs have all static IP addresses.
    All of a sudden we're having a number of issues with the network connection:
    APs restarting
    The APs restart every now and then reporting that their IP is being used by another device. Looking through the logs there are two MAC addresses that are reported as using the APs IP address. These two MAC addresses have unknown vendor IDs.
    Warning: AP with Base Radio MAC f8:72:ea:7c:9d:e3 has found  its IP Address 0.2.146.0 being used by a machine with MAC
    Address  04:c6:f8:40:00:00 (The other mac that is reported is 04:cc:90:40:00:00)
    AP 'AP5', MAC: 0c:68:03:dd:1b:80 disassociated previously due to Link Failure.  Uptime: 4 days, 00 h 48 m 50 s . Reason: Capwap WTP Event request.
    So: There are two MACs that use the IP addresses of 7 APs?!?! And there is no vendor to be found for these MACs?
    Ping timouts on the webGUI and CLI
    I have a ping running on the IP for managing the device. This is running fine for ages. As soon as I connect via webGUI or CLI I lose packets. Get timeouts etc. some packets get through some don't. More of the latter. So ping is fine but any other traffic seems to be impacted heavily.
    What we have done for troubleshooting
    Checked duplex/speed settings of the interfaces. Everything ok.
    Connected to another switchport. Same.
    Changed the IP address of the management port. Same.
    Swapped places with a laptop with the same IP address --> Worked fine.
    Plugged in a completely new device, installed the latest firmware (7.6) and uploaded the config from the other one. Same.
    Restarted the default gateway for the subnet the controler is on.
    So now we're at the end of our knowledge. It seems to be a non-physical network issue, but we're a small team and no one has changed anything they say :-/
    Any ideas what we could check next?
    Kat

    Hello,
    thanks for your suggestions. It's hard to find those two MAC addresses. As they seem to be virtual I cannot get a hint from the vendor ID. A show mac-address table on the switch the WLC is connected to doesn't show those two
    I found an error in the WLC AP config. AP1 had the same IP as AP5 and a wrong netmask. I changed that. Unfortunately that doesn't solve our problem.
    Here are some more messages from the WLC's log:
    AP 'AP3', MAC: 0c:68:03:dd:34:00 disassociated previously due to Link Failure.  Uptime: 4 days, 15 h 04 m 15 s . Reason: Capwap WTP Event request.
    AP Disassociated. Base Radio MAC:0c:68:03:dd:34:00
    AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:0c:68:03:dd:34:00  Cause=Heartbeat Timeout Status:NA
    AP 'AP3', MAC: 0c:68:03:dd:34:00 disassociated previously due to Link Failure.  Uptime: 4 days, 15 h 00 m 45 s . Reason: Capwap WTP Event request.
    RF Manager updated TxPower for Base Radio MAC: 0c:68:03:dd:34:00 and slotNo: 0.  New Tx Power is: 2
    AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:0c:68:03:dd:16:e0  Cause=Max Retransmission Status:NA
    IDS Signature attack detected. Signature Type: Standard, Name: Deauth flood,  Description: Deauthentication flood, Track: per-signature, Detecting AP Name:  AP7, Radio Type: 802.11b/g, Preced: 9, Hits: 500, Channel: 6, srcMac:  C2:9F:DB:21:47:60
    This is the sh run-config of our WLC including one AP:
    >show run-config
    System Inventory
    NAME: "Chassis"    , DESCR: "Cisco 2500 Series Wireless LAN Controller"
    PID: AIR-CT2504-K9,  VID: V01,  SN: PSZ17381EPZ
    Burned-in MAC Address............................ 50:17:FF:27:12:80
    Maximum number of APs supported.................. 15
    System Information
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.4.110.0
    Bootloader Version............................... 1.0.18
    Field Recovery Image Version..................... 1.0.0
    Firmware Version................................. PIC 16.0
    Build Type....................................... DATA + WPS
    System Name...................................... UK-BRI-WFAPC
    System Location..................................
    System Contact...................................
    System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
    IP Address....................................... 172.17.128.12
    Last Reset....................................... Power on reset
    System Up Time................................... 4 days 0 hrs 46 mins 6 secs
    System Timezone Location.........................
    System Stats Realtime Interval................... 5
    System Stats Normal Interval..................... 180
    Configured Country............................... GB  - United Kingdom
    Operating Environment............................ Commercial (0 to 40 C)
    Internal Temp Alarm Limits....................... 0 to 65 C
    Internal Temperature............................. +20 C
    External Temperature............................. +25 C
    Fan Status....................................... 4000 rpm
    State of 802.11b Network......................... Enabled
    State of 802.11a Network......................... Enabled
    Number of WLANs.................................. 3
    Number of Active Clients......................... 6
    Memory Current Usage............................. Unknown
    Memory Average Usage............................. Unknown
    CPU Current Usage................................ Unknown
    CPU Average Usage................................ Unknown
    Burned-in MAC Address............................ 50:17:FF:27:12:80
    Maximum number of APs supported.................. 15
    AP Bundle Information
    Primary AP Image    Size
    ap1g2            9568
    ap3g1            11288
    ap3g2            11196
    ap801            7164
    ap802            8568
    c1130            5072
    c1140            9416
    c1250            6944
    c1520            8044
    c602i            3736
    Secondary AP Image    Size
    ap3g1            5792
    ap801            5192
    ap802            5232
    c1100            3084
    c1130            4964
    c1140            4992
    c1200            3364
    c1240            4812
    c1250            5504
    c1310            3136
    c1520            6404
    c3201            4324
    c602i            3716
    Switch Configuration
    802.3x Flow Control Mode......................... Disable
    FIPS prerequisite features....................... Disabled
    secret obfuscation............................... Enabled
    Strong Password Check Features:
         case-check ...........Enabled
         consecutive-check ....Enabled
         default-check .......Enabled
         username-check ......Enabled
    Network Information
    RF-Network Name............................. RFGROUP
    Web Mode.................................... Disable
    Secure Web Mode............................. Enable
    Secure Web Mode Cipher-Option High.......... Disable
    Secure Web Mode Cipher-Option SSLv2......... Disable
    Secure Web Mode RC4 Cipher Preference....... Disable
    OCSP........................................ Disabled
    OCSP responder URL..........................
    Secure Shell (ssh).......................... Enable
    Telnet...................................... Disable
    Ethernet Multicast Forwarding............... Disable
    Ethernet Broadcast Forwarding............... Disable
    AP Multicast/Broadcast Mode................. Multicast   Address : 0.0.0.0
    IGMP snooping............................... Disabled
    IGMP timeout................................ 60 seconds
    IGMP Query Interval......................... 20 seconds
    MLD snooping................................ Disabled
    MLD timeout................................. 60 seconds
    MLD query interval.......................... 20 seconds
    User Idle Timeout........................... 300 seconds
    ARP Idle Timeout............................ 300 seconds
    Cisco AP Default Master..................... Disable
    AP Join Priority............................ Disable
    Mgmt Via Wireless Interface................. Disable
    Mgmt Via Dynamic Interface.................. Disable
    Bridge MAC filter Config.................... Enable
    Bridge Security Mode........................ EAP
    Mesh Full Sector DFS........................ Enable
    AP Fallback ................................ Enable
    Web Auth CMCC Support ...................... Disabled
    Web Auth Redirect Ports .................... 80
    Web Auth Proxy Redirect  ................... Disable
    Web Auth Captive-Bypass   .................. Disable
    Web Auth Secure Web  ....................... Enable
    Fast SSID Change ........................... Disabled
    AP Discovery - NAT IP Only ................. Enabled
    IP/MAC Addr Binding Check .................. Enabled
    CCX-lite status ............................ Disable
    oeap-600 dual-rlan-ports ................... Disable
    oeap-600 local-network ..................... Enable
    mDNS snooping............................... Disabled
    mDNS Query Interval......................... 15 minutes
    Port Summary
               STP   Admin   Physical   Physical   Link   Link
    Pr  Type   Stat   Mode     Mode      Status   Status  Trap     POE 
    1  Normal  Forw Enable  Auto       1000 Full  Up     Enable  N/A    
    2  Normal  Forw Enable  Auto       100 Full   Up     Enable  N/A    
    3  Normal  Forw Enable  Auto       1000 Full  Up     Enable  Enable  (Power Off)
    4  Normal  Disa Enable  Auto       Auto       Down   Enable  Enable  (Power Off)
    AP Summary
    Number of APs.................................... 7
    Global AP User Name.............................. Not Configured
    Global AP Dot1x User Name........................ Not Configured
    AP Name             Slots  AP Model              Ethernet MAC       Location          Port  Country  Priority
    AP7                  2     AIR-CAP1602I-E-K9     f8:72:ea:e4:9a:81  default location  1        GB       1
    AP1                  2     AIR-CAP1602I-E-K9     f8:72:ea:7c:9d:e3  default location  1        GB       1
    AP3                  2     AIR-CAP1602I-E-K9     f8:72:ea:e4:9c:57  default location  1        GB       1
    AP6                  2     AIR-CAP1602I-E-K9     f8:72:ea:e4:9a:90  default location  1        GB       1
    AP2                  2     AIR-CAP1602I-E-K9     f8:72:ea:7c:9b:63  default location  1        GB       1
    AP4                  2     AIR-CAP1602I-E-K9     f8:72:ea:e4:9a:9b  default location  1        GB       1
    AP5                  2     AIR-CAP1602I-E-K9     f8:72:ea:e4:9a:cb  default location  1        GB       1
    AP Tcp-Mss-Adjust Info
    AP Name              TCP State  MSS Size
    AP7                  disabled   -
    AP1                  disabled   -
    AP3                  disabled   -
    AP6                  disabled   -
    AP2                  disabled   -
    AP4                  disabled   -
    AP5                  disabled   -
    AP Location
    Total Number of AP Groups........................ 0   
    Site Name........................................ default-group
    Site Description.................................
    NAS-identifier................................... UK-BRI-WFAPC
    AP Operating Class............................... Not-configured
    RF Profile
    2.4 GHz band.....................................
    5 GHz band.......................................
    WLAN ID          Interface          Network Admission Control          Radio Policy
    1               corporate            Disabled                          None
    2               dirtynetwork         Disabled                          None
    3               dirtynetwork         Disabled                          None
    AP Name             Slots  AP Model             Ethernet MAC       Location          Port  Country  Priority
    AP7                  2     AIR-CAP1602I-E-K9    f8:72:ea:e4:9a:81  default location  1     GB       1
    AP1                  2     AIR-CAP1602I-E-K9    f8:72:ea:7c:9d:e3  default location  1     GB       1
    AP3                  2     AIR-CAP1602I-E-K9    f8:72:ea:e4:9c:57  default location  1     GB       1
    AP6                  2     AIR-CAP1602I-E-K9    f8:72:ea:e4:9a:90  default location  1     GB       1
    AP2                  2     AIR-CAP1602I-E-K9    f8:72:ea:7c:9b:63  default location  1     GB       1
    AP4                  2     AIR-CAP1602I-E-K9    f8:
    RF Profile
    Number of RF Profiles............................ 0
    Out Of Box State................................. Disabled
    RF Profile Name                    Band     Description                         11n-client-only
    AP Config
    Cisco AP Identifier.............................. 15
    Cisco AP Name.................................... AP7
    Country code..................................... GB  - United Kingdom
    Regulatory Domain allowed by Country............. 802.11bg:-E     802.11a:-E
    AP Country code..................
    ................ GB  - United Kingdom
    AP Regulatory Domain............................. -E
    Switch Port Number .............................. 1
    MAC Address...................................... f8:72:ea:e4:9a:81
    IP Address Configuration......................... Static IP assigned
    IP Address....................................... 172.17.128.24
    IP NetMask....................................... 255.255.128.0
    Gateway IP Addr.................................. 172.17.128.1
    Domain...............
    Name Server......................................
    NAT External IP Address.......................... None
    CAPWAP Path MTU.................................. 1485
    Telnet State..................................... Disabled
    Ssh State........................................ Disabled
    Cisco AP Location................................ default location
    Cisco AP Floor Label............................. 0
    Cisco AP Group Name.............................. default-group
    Primary Cisco Switch Name........................
    Primary Cisco Switch IP Address.................. Not Configured
    Secondary Cisco Switch Name......................
    Secondary Cisco Switch IP Address................ Not Configured
    Tertiary Cisco Switch Name.......................
    Tertiary Cisco Switch IP Address................. Not Configured
    Administrative State ............................ ADMIN_ENABLED
    Operation State ....
    ............................. REGISTERED
    Mirroring Mode .................................. Disabled
    AP Mode ......................................... Local
    Public Safety ................................... Disabled
    AP SubMode ...................................... Not Configured
    Remote AP Debug ................................. Disabled
    Logging trap severity level ..................... informational
    Logging syslog facility ..
    ....................... kern
    S/W  Version .................................... 7.4.110.0
    Boot  Version ................................... 15.2.2.0
    Mini IOS Version ................................ 7.4.1.37
    Stats Reporting Period .......................... 180
    Stats Collection Mode ........................... normal
    LED State........................................ 
    Enabled
    PoE Pre-Standard Switch.......................... Disabled
    PoE Power Injector MAC Addr...................... Disabled
    Power Type/Mode.................................. Power injector / Normal mode
    Number Of Slots.................................. 2
    AP Model......................................... AIR-CAP1602I-E-K9  
    AP Image...............................
    .......... C1600-K9W8-M
    IOS Version...................................... 15.2(2)JB2$
    Reset Button..................................... Enabled
    AP Serial Number................................. FGL1725W7F7
    AP Certificate Type.............................. Manufacture Installed
    AP User Mode..................................... AUTOMATIC
    AP User Name..................................... Not Configured
    AP Dot1x User Mode............................... Not Configured
    AP Dot1x User Name............................... Not Configured
    Cisco AP system loggi
    ng host..................... 255.255.255.255
    AP Up Time....................................... 3 days, 23 h 26 m 50 s
    AP LWAPP Up Time................................. 0 days, 00 h 14 m 12 s
    Join Date and Time............................... Tue Jan 28 18:11:43 2014
    Join Taken Time.................................. 0 days, 00 h 11 m 41 s
    Attributes for Slot  0
        Radio Type................................... RADIO_TYPE_80211n-2.4
        Administrative State ........................ ADMIN_ENABLED
        Operation State ............................. UP
        Radio Role .................................. ACCESS
        Radio Mode .................................. Local
        CellId ...................................... 0
        Station Configuration
          Configuration ............................. AU
    TOMATIC
          Number Of WLANs ........................... 3
          Medium Occupancy Limit .................... 100
          CFP Period ................................ 4
          CFP MaxDuration ........................... 60
          BSSID ..................................... 0c:68:03:dd:16:e0
          Operation Rate Set
            1000 Kilo Bits........................... MANDATORY
            2000 Kilo Bits........................... MANDATORY
            5500 Kilo Bits........................... MANDATORY
            11000 Kilo Bits.......................... MANDATORY
            6000 Kilo Bits........................... SUPPORTED
            9000 Kilo Bits........................... SUPPORTED
            12000 Kilo Bits.......................... SUPPORTED
            18000 Kilo Bits.......................... SUPPORTED
            24000 Kilo Bits.......................... SUPPORTED
    36000 Kilo Bits.......................... SUPPORTED
            48000 Kilo Bits.......................... SUPPORTED
            54000 Kilo Bits.......................... SUPPORTED
          MCS Set
            MCS 0.................................... SUPPORTED
            MCS 1.................................... SUPPORTED
            MCS 2.................................... SUPPORTED
            MCS 3.................................... SUPPORTED
            MCS 4.................................... SUPPORTED
            MCS 5.................................... SUPPORTED
            MCS 6.................................... SUPPORTED
            MCS 7.................................... SUPPORTED
            MCS 8.................................... SUPPORTED
            MCS 9.................................... SUPPORTED
            MCS 10................................... SUPPORTED
            MCS 11................................... SUPPORTED
            MCS 12..
    ................................. SUPPORTED
            MCS 13................................... SUPPORTED
            MCS 14................................... SUPPORTED
            MCS 15................................... SUPPORTED
            MCS 16................................... DISABLED
            MCS 17................................... DISABLED
            MCS 18................................... DISABLED
            MCS 19................................... DISABLED
            MCS 20................................... DISABLED
            MCS 21................................... DISABLED
            MCS 22................................... DISABLED
            MCS 23................................... DISABLED
          Beacon Period ............................. 100
          Fragmentation Threshold ................... 2346
          Multi Domain Capability Implemented ....... TRUE
          Multi Domain Capability Enabled ........... TRUE
          Country String ............................ GB
        Multi Domain Capability
          Configuration ............................. AUTOMATIC
          First Chan Num ............................ 1
          Number Of Channels ........................ 13
        MAC Operation Parameters
          Configuration ............................. AUTOMATIC
          Fragmentation Threshold ................... 2346
          Packet Retry Limit ........................ 64
        Tx Power
          Num Of Supported Power Levels ............. 4
          Tx Power Level 1 .......................... 16 dBm
          Tx Power Level 2 .......................... 13 dBm
          Tx Power Level 3 .......................... 10 dBm
          Tx Power Level 4 .......................... 7 dBm
          Tx Power Configuration .................... AUTOMATIC
          Current Tx Power Level .................... 3
          Tx Power Assigned By ...................... DTPC
        Phy OFDM parameters
          Configuration ............................. AUTOMATIC
          Current Channel ........................... 6
          Channel Assigned By ....................... DCA
          Extension Channel ......................... NONE
          Channel Width.............................. 20 Mhz
          Allowed Channel List....................... 1,2,3,4,5,6,7,8,9,10,11,12,
            ......................................... 13
          TI Threshold .............................. -50
          Legacy Tx Beamforming Configuration ....... CUSTOMIZED
          Legacy Tx Beamforming ..................... ENABLED
          Antenna Type............................... INTERNAL_ANTENNA
          Internal Antenna Gain (in .5 dBi units).... 8
          Diversity.................................. DIVERSITY_ENABLED
          802.11n Antennas
             A....................................... ENABLED
             B....................................... ENABLED
             C....................................... ENABLED
        Performance Profile Parameters
          Configuration ............................. AUTOMATIC
          Interference threshold..................... 10 %
          Noise threshold............................  -70 dBm
          RF utilization threshold................... 80 %
          Data-rate threshold........................ 1000000 bps
          Client threshold........................... 12 clients
          Coverage SNR threshold..................... 12 dB
          Coverage exception level................... 25 %
          Client minimum exception level............. 3 clients
        Rogue Containment Information
        Containment Count............................
        CleanAir Management Information
            CleanAir Capable......................... No
        Radio Extended Configurations
          Beacon period.............................. 100 milliseconds
          Beacon range............................... AUTO
          Multicast buffer........................... AUTO
          Multicast data-rate........................ AUTO
          RX SOP threshold........................... AUTO
          CCA threshold.............................. AUTO

  • PETITION: This is what I would like to see in a new firmware upgrade for the MTP ZEN TO

    FIXES:
    -Ensures correct playback on the player of Zencast audio content that has been transferred using Zencast organiser. Remaining time is displayed correctly, and rewind / fast-forward functions can be used
    - Allows users to transfer tracks between folders on the player when using a program such as Creative Mediasource [THIS IS NEEDED FOR ALL MTP PLAYERS]
    - Allows charging via USB when the player is not being used by a program or is low on battery [THIS FEATURE SEEMS TO HAVE BEEN REMOVED BY MTP UPGRADE]
    ENHANCEMENTS / ADDITIONAL FEAUTRES [I HAVE LISTED THESE BY MY PERSONAL ORDER OF PREFERENCE]:
    ) Allows the playback of Audible content types ,2,3,4 on the player, via a plug-in in Audible Manager
    2) Adds bookmarking feature to the player
    3) Adds SmartVolume EQ feature to the player
    4) Adds DJ menu to the player
    5) Allows user to partition a section of the player for data transfer
    6) Allows user to synchronise tasks from Outlook to the player
    7) Allows TXT files/ Ebooks to be stored/ viewed on the player
    8) Adds BassBoost EQ feature to the player
    PLEASE SIGN THIS PETITION TO URGE CREATIVE TO INTRODUCE AT LEAST SOME OF THESE FIXES / FEATURES IN A FIRMWARE UPGRADE FOR THE MTP ZEN TOUCH - also please feel free to add other suggestions that would improve the functionality of the Zen Touch
    Message Edited by joshua32 on <SPAN class=date_text>05-30-2006 <SPAN class=time_text>:7 PM
    Message Edited by joshua32 on 05-30-2006 :8 PM

    all of these would be awesome, as would lyrics support, I REALLY want that

Maybe you are looking for