Cisco 1231 join 2504 wlc

Similar Questions

• Cisco 1600i and 2504 Configuration problems

  Hello guys,.

  I need serious help, please!

  I'm having a devil of a problem getting my 3 device AIR-SAP-1602I-A-KP (stand-alone) to work with my WLC 2504

  Cisco said that the stand-alone version will also work with the controllers, but I can't seem to join the WLC.

  I can ping each AP the WLC and vice versa.

  Ideas please?

  You will need to convert your APs to run IOS on controller before the APs can join the WLC.

  This process is easy.  Go to Cisco's Web site and download the file with the "RRs" in the name of the file.  UN-pack TAR in the point of the file and let the AP boot this IOS and you should be fine.

• Access points join different WLC

  Hello

  I have a remote control module (NME-AIR-WLC25-K9) installed in a Cisco No. 2851 SRI, this configuration is in my remote site, we are connected through network of the MAN. In our main office, I have a cisco wireless controller 4402. so whenever I have install an access point in my remote instead of the remote site WLC joiining site, the access point joins my controller 4402 main office, I have no why this is the case, the AP does not even reach the remote site WLC... I do not set up high availability and these two controller are separate RF network.

  the version of the firmware in NME-AIR-WLC25-K9 is 7.0.98.0...

  the version to the other controller is 6.0.196.0

  Please let me know what else I need to check as soon as possible

  Thank you

  knockaert

  This is not the point.

  Assume that you have two controllers: WLC - a and WLC - B.

  You have an AP that interested in joining WLC - a but instead will join always WLC - B.

  The solution is to set up "High Avlailability" with details WLC - A entered as the PDC.  This will force the access point to the correct controller: WLC.-a.

  Does that answer your question?

• Upgradation in 2504 WLC

  Hi Experts,

  We are having 2504 WLC with 7.4.121.0 code and WAS code 1.0.0. We want to upgrade the code to 8.0.120.0, and in the recommendations, I have seen that we need to upgrade the code WAS 1.9 (1.0.20).

  Can I put the code directly WAS the recommended or should I have to upgrade to 1.7 (1.0.16) and the chain of upgrade.

  Kind regards

  Tamil

  Direct upgrade should work. Pls do the console & connect the output for reference

  Here are the release notes on this

  http://www.Cisco.com/c/en/us/TD/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html

  HTH

  Rasika

  Pls note all useful responses *.

• Impossible to 2504 WLC with new operating system

  Hello

  I got a cisco WLC 2504 with the version of the OS - 7.0.112.56. When I tried to upgrade to the new operating system, it gives below error.

  (Cisco Controller) > transfer download starts

  Mode............................................. TFTP
  Data Type........................................ Code
  TFTP Server IP... 192.168.1.1
  TFTP package Timeout... 6
  Attempts to TFTP Max... 10
  TFTP Path........................................ /
  Name of the TFTP file. Air-CT2500-K9-8-3-102-0.AES

  This can take some time.
  Are you sure you want to start? y (y/N)

  Transfer of TFTP boot Code.

  TFTP receive full... extraction of components.

  Failed version of image control. Version 8.3.102.2 not supported.

  Transfer failed: incompatibility of Version - the version of the image is not for this model

  TFTP failed while storing it in flash!

  Please help in this case if someone knows the question.

  Thanks in advance

  Version of the product... 7.0.112.56

  It could be a bug.  This is a special version of technology.

  Try to upgrade to, say, 7.0.252.0 and see if it works.  If so, then go directly to 8.3.X.

• GUI display in 2504 WLC on 8.3.102.0 problems and communication issues

  I had to take two of my WLC 2504 version 8.3.102.0 code to support the APs news with domain B. The WLC came with 7.6 which is postponed, so I tried both versions of ED last 8.2 and 8.3, but then the GUI is almost unusable. I can only reliable get in on the CLI but users at this location use the graphical interface of surveillance. Are there changes in the settings of browser required for the GUI work reliably?

  It's a problem with only a few of our controllers running 8.0 or 8.2. In general, I use Firefox like Chrome has this issue with me. IE and Edge seems to works fine too, but prefer Firefox. Any code your race to be honest. We always can understand this except to refresh the browser.  I run 8.3 at home and I have not touched any GUI question still.

  -Scott

  Please evaluate the useful messages *.

• APs (LAP1142N) disconnect after joining the WLC (5508)

  Hello

  We have a problem in the school I work at. There are 133 APs located on campus.

  They worked for 3.5 years without any problems.

  Recently, we have problems with APs disconnect randomly.

  He began the week last with just a couple. We've got them running again, but later the same day new ones had disconnected.

  This continued with several access points and it seems to happen randomly and it is never the same one that disconnects.

  We have a centralized support unit that helps us with stuff like that, but they have not found a solution, so I was hoping that someone here had seen this problem before.

  Today at 07:00 all access points were running, but at the time of this post, 6 of them were disconnected.

  AP (130):

  Product ID: AIR-LAP1142N-E-K9

  Version ID: V01

  Software version: 7.4.100.0

  Starting version: 12.4.18.3

  IOS: 15.2 (2) JB$

  Country code: Norway (NO)

  Regulatory domains: 802.11bg: EI 802. 11A: EI

  Controller:

  Cisco 5508 wireless controller

  Firmware: 7.4.100.0

  Version of recovery: 6.0.182.0

  Temp is running at 35 ° c.

  Memory to a stable of 50%

  Cores 0% / 2%, 4% / 2%, 3% / 2%, 4% / 1%, 3% / 3%, 5% / 2%, 0% / 0%, 1% / 1%, 0% / 0%, 1% / 1%

  Only 4 of the 1-4 controller ports

  Some error messages - I have found on the different access points that have disconnected:

  Application of discovery of layer 3 not received on the management of VLANS

  Discovery LWAPP rejected request

  Give me a shout if any other information is needed.

  -Hille

  Hello

  Please go to 7.4.110.0 and that should do it.

  "There is a known issue on this version between 1140 and 7.4.100.0.

  Please let me know if still face you the same problem after the upgrade.

• Cisco WLC 2504 - Access Points do not reach the controller

  Hello world

  We bougth a Cisco WLC 2504 with two AIR-AP2702I-UXK9 Access Points. The problem is that the AP do not join the WLC.
  The output from 'show join ap stats' shows the following:

  (Cisco Controller) > view join ap stats summary all the

  Database Mac EthernetMac AP AP name IP address Status
  00:35: 1a: B1:A9:60 00:f2:8 b: f4:1 has: 9 c AP00f2.8bf4.1a9c 192.168.10.23 joined not
  00:35: 1a: C9:99:B0 00:f2:8 b: 77:b7:fc AP00f2.8b77.b7fc not joined 192.168.10.24

  (Cisco Controller) > show join ap 00:35:1 detailed stats to: b1:a9:60

  Synchronization phase statistics
  -For the synchronization request has received... Does not apply
  -For the synchronization completed... Does not apply

  Discovery phase statistics
  -Applications received discovered... 114
  -Answers success of discovery... 114
  -Discovery failure processing... 0
  -Purpose of the last unsuccessful attempt of discovery... Does not apply
  -Attempt to finally successful discovery time... 20:15:40.106 16 June
  -Discovery attempt ultimately unsuccessful time... Does not apply

  Join the live statistics
  -Join applications received... 57
  -Join sent successful responses... 57
  -Processing of the join request without success... 0
  -Purpose of the last unsuccessful attempt to join... Does not apply
  -Attempt to join finally managed time... 20:15:50.414 16 June
  -Join finally failed time... Does not apply

  Configuration phase statistics

  -Configuration requests... 114
  -Answers configuration successful... 0
  -Processing configuration failed... 57
  -Purpose of the last unsuccessful attempt to Setup... Invalid license in the application configuration
  -Attempt to finally successful configuration time... Does not apply
  -Time finally failed configuration attempt... 20:15:50.810 16 June

  Last the decryption of the AP details failure messages
  -Last message decryption failure reason... Does not apply

  Details of recent disconnection AP
  -Last AP connection failure reason... Does not apply
  -Last reason for disconnection AP... Unknown failure reason

  Latest summary join error
  -Type of error that occurred in the last... Application of configuration rejected LWAPP
  -Reason for the error that took place the last... Invalid license in the application configuration
  -Time which occurred the last error to join... 20:15:50.810 16 June

  Details of sign-out AP
  -Last AP connection failure reason... Does not apply
  Ethernet Mac: c 00:f2:8 b: f4:1 has: 9 Ip address: 192.168.10.23

  Would be grateful for the help.

  Best regards
  Marc

  Hi Marc,

  Make sure first that your controller has software code 8.0.x or above, if first better it. Here's the code recommended by TAC

  http://www.Cisco.com/c/en/us/support/docs/wireless/wireless-LAN-Controller-software/200046-TAC-recommended-AireOS.html

  Then, try the UX above deployment guide to begin. Under Advanced tab WLAN, you need to enable "of the first universal ap' in order to use this app provisioning & connect to the AP.

  If you have more than 1 AP, then you must start 1AP using this application. Other access points that you can feed them upward, while AP original is also powered, so they'll use protocal called NDP & start them automatically

  Let us know how it goes

  HTH

  Rasika

  Pls note all useful responses *.

• Cisco WLC 2504 with AIR-AP1131AG-A-K9

  Hello

  Can you help me for some info about AIR-AP1131AG-A-K9.

  I have a wlc 2504, but I don't know if the AIR-AP1131AG-A-K9-supported 2504 wlc.

  Can work this WLC 2504 with AIR-AP1131AG-A-K9 solution?

  If so, guide.

  Thank you very much

  Gezimv

  Check out this link. As long as you have software version 8.0.x 2504 version you can use 1131 AP with it. Nothing beyond software fate is more a series of support 1131.

  http://www.Cisco.com/c/en/us/TD/docs/wireless/compatibility/matrix/compatibility-matrix.html#56735

  HTH

  Rasika

  Pls note all useful responses *.

• Join CISCO AP 1041N to a series of 2500 WLC

  Hello

  I have a problem to join CISCO 10 AP 1041N to a series of 2500 WLC.

  I have the following network architecture,

  A Windows Server 2012 R2 (DC, DHCP and DNS server) connected to the CISCO 2960-X Series (this switch is connected to 2 other switches, same model), 10 of the AP and the WLC are connected to the same switch, as I have 3 NIC on the server I use one for Internet between the firewall and the other three are teamed together and connected to the switch.

  I tried the following methods:

  -J' used the 43 Option on the DHCP server: does not work

  -J' added 2 DNS entries (cisco-capwap - controller.mydomain and cisco-lwapp - controller.mydomain): does not

  -UDP Ports CAPWAP and LPWAP are enabled on the Windows Firewall: does not

  My WLC is set mode controller Master, I see all of the AP in the DHCP server with IP addresses assigned by the server and the WLC as well, and they can ping each other.

  Furthermore, the WLC, I have one (management) interface with VLAN ID 0, the server has (VLAN by default) no assigned ID, the switch have VLAN ID 1 (default) and I tried to change all the on the same VLAN ID 1 (server, Switch, WLC) in this case the server is not able to communicate with each other and DHCP does not work.

  Thank you for your help.

  Oh, your APs are standalone, that is why they can't join the WLC. Convert into light! Here's a good guide - http://mrncciew.com/2012/10/20/lightweight-to-autonomous-conversion/

• Cisco WLC 2504

  I couldn't go to the graphical interface of 2504 WLC. I updated 192.168.99.24, defined DHCP 192.168.99.25 address IP of MGT. I put my interface on PC port to 192.168.99.26. Then I put my URL to 192.168.99.24 and I still couldn't to GUI. I plugged my Ethernet cable to port 2 on the controller.

  What port you defined as the mgmt port? Mgmt port you should be a different subnet, then your data traffic.

• Recommended configuration of WLC 2504 SSID with AD

  Hello

  I would ask, what oyou d think that is now the best practices and recommended solution how to configure SSDID on 2504 WLC for the following scenario. I'm new to WLC and would like to secure network.

  -any type of customer must be supported (08/07/10 win, mac, linux, iOS, android, windows mobile)

  -authentication on Win 2012 R2 NPS as RADIUS

  -any requirement of certificate client (we don't want PKI configuration for now), we want to just WLC certificate as an authentication point

  is enough [WPA2] [Auth (802. 1 X + CCKM)] who will have radius configured?

  Thank you

  Well Yes, check these

  http://www.Cisco.com/c/en/us/support/docs/wireless-mobility/WLAN-Securit...

  http://www.Cisco.com/c/en/us/TD/docs/wireless/controller/4-2/configurati...

  Eat local point concerns small size as a small office deployments.

• WLC 2504 UPGRADE AND LAP 2702

  Hello.

  We are going to upgrade a WLC: AIR-CT2504-15-K9 for free: 8.0.120

  This is a new installation and we will install 15 TOUR of this model: AIR-CAP2702E-A-K9.

  We went through the compatibility matrix and release WLC 8.0.120 correspond to LAP: 15.3 (3) JA4.

  the upgrade mention WLC process which, after the upgrade of the WLC, completed the upgrade of the TOUR begins automatically, so I have a few question:

  1. I need to plug all the way AROUND (15 LAP´s) to the cable network so they can be automatically upgraded?
  2. This release is selected automatically during the TOUR?
  3. Y at - it a GUI WLC option where I indicate where the exit for LAP (15.3 (3) JA4?)
  4. I tried to download version 8.0.120 for 2504 WLC but need a Partnert Lincense. Would you mind giving a link where I can download this version?
  5. We assume that, above all, he must perform a communication between the WLC with TOWER (15) using the current version, is this true?
  6. If the 2504 WLC and LAP 2702 have different (different version of matrix compatilibilty) is it possible to upgrade the version of the TOUR? can they communicate with each other so we can proceed with the upgrade?

  Thank you in advance your response earlier.

  Attn.

  Roger Majo

  Hi Roger,

  Please find below the details of my side which will be useful for you.

  I need to plug all the way AROUND (15 LAP´s) to the cable network so they can be automatically upgraded? Yes... Or whenever you connect to the network access point it will automatically connect to WLC through DHCP option

  This release is selected automatically during the TOUR? Controller of which is running

  Y at - it a GUI WLC option where I indicate where the exit for LAP (15.3 (3) JA4? > Show ap image all the )

  I tried to download version 8.0.120 for 2504 WLC but need a Partnert Lincense. Would you mind giving a link where I can download this version? Contact account executive-paper license (check you have valid Support Cisco)

  We assume that, above all, need a communication between the WLC with TOWER (15) using the current version, is - that true? No need... AP will automatically for the last reason that is available in the controller

  If the 2504 WLC and LAP 2702 have different (different version of matrix compatilibilty) is it possible to upgrade the version of the TOUR? Can they communicate with each other so we can proceed with the upgrade? Explained earlier

  Thank you

  Sam

• Trouble getting a Cisco 2600 series AP to stay connected to WLC 5508

  Hello

  I recently loaded the independent our old APs upgrade to LWAPs.  We have a WLC 5508 to our Virtual Co - Lo and I use Flexconnect to accommodate local switch and dhcp on our sites.  I have updated more than 50 APs and joined them to the controller.  These include only the 1130AG and 1240AG models.  However they work perfectly and stay connected to the controller.  I'm having is with a new batch of 2600 series APs stay connected to the controller.  I tried to do research in what may cause disconnect it but have yet to find a solution.  I use DNS to resolve queries for CAPWAP & LWAPP APs to the controller on our EXTENSIVE network.  Read other messages I thought that this is perhaps a problem with packages to drop but have had our provider that manages Sonicwalls at both ends of the WAN confirm for me that there is no packet loss.  Here are the logs that I collected through the puttty of the WLC & AP.  Any help would be greatly appreciated.

  AP, I do the test on:

  NAME: "AP2600', DESCR: 'Cisco Aironet 2600 Series (IEEE 802.11n) Access Point.

  PID: AIR-CAP2602I-A-K9, VID: V01, SN: FTX1740J8V1

  WLC in question:

  Name of the manufacturer... Cisco Systems Inc..

  Product name... Cisco controller

  Version of the product... 7.3.112.0

  Bootloader Version... 1.0.1

  Retrieving Image Version field... 6.0.182.0

  Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27

  Build Type....................................... DATA + WPS

  System name... wificontroller

  Location of the system... Corp

  Contact System... Net engineer

  ObjectID of system... 1.3.6.1.4.1.9.1.1069

  Redundancy mode... People with disabilities

  IP Address....................................... 10.250.32.8

  Last Reset....................................... Software reset

  Time system... 190 days 3 hours 34 minutes 24 seconds

  Location of the time zone of the system... (GMT - 5:00) Eastern (USA and Canada)

  The country is set... USA - United States

  Operating environment... Utilities (0 to 40 ° C)

  Limits the internal temperature alarm... 0 to 65 ° C

  -Other - or ITU (q)

  ... Internal temperature 38 C

  Outdoor temperature... + 20 C

  Fan Status....................................... Ok

  State of 802. 11 b network... Activated

  State of 802. 11A network... Activated

  Number of wireless LANs... 14

  Number of Active Clients... 71

  Built-in MAC address... C8:9 C: D: 8 1: 52:E0

  Power supply 1... Currently, OK

  Power supply 2... Absent

  Maximum number of taken access points supported... 100

  Here is the result which leaves on concluded that the AP joins the WLC for a short period and then goes offline

  WT-4thFlr-AP3 #.

  * 15:42:04.419 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST

  ., 3)

  * 15:42:11.443 Dec 14: EVT-4-AVT %: write flash: / done event.capwap

  * 15:42:11.483 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

  * 15:42:11.487 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

  * 15:42:11.487 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246

  * 15:42:11.571 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.

  * 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).

  * 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 15:42:12.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246

  * 15:42:14.303 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246

  * 15:42:14.303 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8

  * 15:42:15.127 Dec 14: "Promiscuous" from Ethernet mode

  * 15:42:15.535 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP

  * 15:42:15.667 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1

  * 15:42:15.667 Dec 14: AC setting hop first MAC: 0017.c575.a23c

  * 15:42:15.855 Dec 14: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller wificontroller

  * 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file

  * 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file

  * 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file

  * 15:42:15.915 Dec 14: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file

  * 15:42:15.915 Dec 14: % LWAPP-3-CLIENTERRORLOG: connected mode

  * 15:42:23.639 Dec 14: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled

  * 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 0 disabled

  * 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 1 disabled

  * 15:45:43.783 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST

  (. 11).

  * 15:45:43.787 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

  * 15:45:43.787 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

  * 15:45:43.787 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246

  * 15:45:43.867 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.

  * 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).

  * 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 15:45:44.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246

  * 15:45:46.315 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246

  * 15:45:46.315 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8

  * 15:45:46.487 Dec 14: "Promiscuous" from Ethernet mode

  * 15:45:49.903 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP

  * 15:45:50.031 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1

  * 15:45:50.031 Dec 14: AC setting hop first MAC: 0017.c575.a23c

  Here are the results of the client debugging capwap event about to access:

  WT-4thFlr-AP3 #debug capwap customer event

  Display debugging EVENT customer CAPWAP is on

  WT-4thFlr-AP3 #.

  * 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

  * 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

  * 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

  * 15:55:08.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:08 UTC 14 December 2013

  * 15:55:25.579 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:55:25.587 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:55:25.827 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:55:25.835 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

  * 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

  * 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

  * 15:55:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:56 UTC 14 December 2013

  * 15:56:25.735 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:56:25.743 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:56:25.983 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:56:25.991 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

  * 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

  * 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

  * 15:56:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:56:56 UTC 14 December 2013

  Here are the results of debug capwap client package in detail:

  WT-4thFlr-AP3 #.

  * 14 Dec 15:59:01.823: <   start="" of="" capwap="" packet ="">>

  * 15:59:01.823 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:01.823 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST

  * 15:59:01.823 Dec 14: Msg length: 0

  * 15:59:01.823 Dec 14: Msg SeqNum: 44

  * 14 Dec 15:59:01.823: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:01.831: <   start="" of="" capwap="" packet ="">>

  * 15:59:01.831 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:01.831 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:01.831 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE

  * 15:59:01.831 Dec 14: Msg length: 15

  * 15:59:01.831 Dec 14: Msg SeqNum: 44

  * 15:59:01.831 Dec 14:

  * 15:59:01.831 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11

  * 15:59:01.831 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:01.831 Dec 14:

  * 15:59:01.831 Dec 14:

  IE: UNKNOWN IT IS ABOUT 151

  * 15:59:01.831 Dec 14: IE length: 5

  * 15:59:01.831 Dec 14: decode the routine unavailable, Hex Dump printing

  * 15:59:01.831 Dec 14:

  52 80 46 00 AC

  * 14 Dec 15:59:01.831: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:20.931: <   start="" of="" capwap="" packet ="">>

  * 15:59:20.931 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:20.931 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

  * 15:59:20.931 Dec 14: Msg length: 93

  * 15:59:20.931 Dec 14: Msg SeqNum: 38

  * 15:59:20.931 Dec 14:

  * 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 89

  * 15:59:20.931 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:20.931 Dec 14:

  * 15:59:20.931 Dec 14:

  IE: RRM_NEIGHBOR_CTRL_PAYLOAD

  * 15:59:20.931 Dec 14: IE length: 83

  * 15:59:20.931 Dec 14: decode the routine unavailable, Hex Dump printing

  * 15:59:20.931 Dec 14:

  00 0 HAS FA 20 08 01 00 07 0A 20 08 03 00 01 FA F4

  01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7

  22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F

  53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00

  00 00 00 00 00 00 00 00 00 00 00 00 00 01 06 0B

  01 01 01

  * 14 Dec 15:59:20.931: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:20.931: <   start="" of="" capwap="" packet ="">>

  * 15:59:20.931 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

  * 15:59:20.931 Dec 14: Msg length: 8

  * 15:59:20.931 Dec 14: Msg SeqNum: 38

  * 15:59:20.931 Dec 14:

  * 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

  * 15:59:20.931 Dec 14: result of Code: CAPWAP_SUCCESS

  * 14 Dec 15:59:20.931: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:21.139: <   start="" of="" capwap="" packet ="">>

  * 15:59:21.139 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:21.139 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:21.139 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

  * 15:59:21.139 Dec 14: Msg length: 111

  * 15:59:21.139 Dec 14: Msg SeqNum: 39

  * 15:59:21.139 Dec 14:

  * 15:59:21.139 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 107

  * 15:59:21.139 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:21.139 Dec 14:

  * 15:59:21.139 Dec 14:

  IE: RRM_NEIGHBOR_CTRL_PAYLOAD

  * 15:59:21.139 Dec 14: IE length: 101

  * 15:59:21.139 Dec 14: decode the routine unavailable, Hex Dump printing

  * 15:59:21.143 Dec 14:

  01 0 TO FA 20 08 01 F4 00 07 0A 20 08 00 01 0C FA

  01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7

  22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F

  53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00

  00 00 00 00 00 00 00 00 00 00 00 00 00 24 28 2

  30 34 38 3 40 95 99 9 01 01 01 01 01 01 01 A1

  01 01 01 01 01

  * 14 Dec 15:59:21.143: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:21.143: <   start="" of="" capwap="" packet ="">>

  * 15:59:21.143 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:21.143 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

  * 15:59:21.143 Dec 14: Msg length: 8

  * 15:59:21.143 Dec 14: Msg SeqNum: 39

  * 15:59:21.143 Dec 14:

  * 15:59:21.143 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

  * 15:59:21.143 Dec 14: result of Code: CAPWAP_SUCCESS

  * 14 Dec 15:59:21.143: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.547: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.547 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:25.547 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST

  * 15:59:25.547 Dec 14: Msg length: 14

  * 15:59:25.547 Dec 14: Msg SeqNum: 45

  * 15:59:25.547 Dec 14:

  * 15:59:25.547 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

  * 15:59:25.547 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:25.547 Dec 14:

  * 15:59:25.547 Dec 14:

  IE: RRM_LOAD_DATA_PAYLOAD

  * 15:59:25.547 Dec 14: IE length: 4

  * 14 Dec 15:59:25.547: slot ccaLoad 0 rxLoad 0 txLoad 0 33

  * 14 Dec 15:59:25.547: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.555: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.555 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:25.555 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:25.555 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

  * 15:59:25.555 Dec 14: Msg length: 0

  * 15:59:25.555 Dec 14: Msg SeqNum: 45

  * 14 Dec 15:59:25.555: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.795: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.795 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:25.795 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST

  * 15:59:25.795 Dec 14: Msg length: 14

  * 15:59:25.795 Dec 14: Msg SeqNum: 46

  * 15:59:25.795 Dec 14:

  * 15:59:25.795 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

  * 15:59:25.795 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:25.795 Dec 14:

  * 15:59:25.795 Dec 14:

  IE: RRM_LOAD_DATA_PAYLOAD

  * 15:59:25.795 Dec 14: IE length: 4

  * 14 Dec 15:59:25.795: slot ccaLoad 1 rxLoad 0 txLoad 0 0

  * 14 Dec 15:59:25.795: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.803: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.803 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:25.803 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:25.803 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

  * 15:59:25.803 Dec 14: Msg length: 0

  * 15:59:25.803 Dec 14: Msg SeqNum: 46

  * 14 Dec 15:59:25.803: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:30.375: <   start="" of="" capwap="" packet ="">>

  * 15:59:30.375 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:30.375 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

  * 15:59:30.375 Dec 14: Msg length: 17

  * 15:59:30.375 Dec 14: Msg SeqNum: 40

  * 15:59:30.375 Dec 14:

  * 15:59:30.375 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 13

  * 15:59:30.375 Dec 14: the vendor identifier: 0 x 00409600

  SlotId: 0

  Mobile Mac Addr: BC:52:B7:E3:17:CB

  * 14 Dec 15:59:30.375: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:30.375: <   start="" of="" capwap="" packet ="">>

  * 15:59:30.375 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

  * 15:59:30.379 Dec 14: Msg length: 8

  * 15:59:30.379 Dec 14: Msg SeqNum: 40

  * 15:59:30.379 Dec 14:

  * 15:59:30.379 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

  * 15:59:30.379 Dec 14: result of Code: CAPWAP_SUCCESS

  * 14 Dec 15:59:30.379: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:30.387: <   start="" of="" capwap="" packet ="">>

  * 15:59:30.387 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:30.387 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:30.387 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

  * 15:59:30.387 Dec 14: Msg length: 0

  * 15:59:30.387 Dec 14: Msg SeqNum: 47

  * 14 Dec 15:59:30.387: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 16:00:00.387: <   start="" of="" capwap="" packet ="">>

  * 16:00:00.387 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 16:00:00.387 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST

  * 16:00:00.387 Dec 14: Msg length: 0

  * 16:00:00.387 Dec 14: Msg SeqNum: 48

  * 14 Dec 16:00:00.387: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 16:00:00.395: <   start="" of="" capwap="" packet ="">>

  * 16:00:00.395 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 16:00:00.395 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 16:00:00.395 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE

  * 16:00:00.395 Dec 14: Msg length: 15

  * 16:00:00.395 Dec 14: Msg SeqNum: 48

  * 16:00:00.395 Dec 14:

  * 16:00:00.395 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11

  * 16:00:00.395 Dec 14: the vendor identifier: 0 x 00409600

  * 16:00:00.395 Dec 14:

  * 16:00:00.395 Dec 14:

  IE: UNKNOWN IT IS ABOUT 151

  * 16:00:00.395 Dec 14: IE length: 5

  * 16:00:00.395 Dec 14: decode the routine unavailable, Hex Dump printing

  * 16:00:00.395 Dec 14:

  52 80 81 00 AC

  * 14 Dec 16:00:00.395: <  end="" of="" capwap="" packet ="">>

  Try reducing the mtu on ap 2600.

• WLC 2504 max AP support

  Hi all

  Anyone know what is the maximum number of points of access supported by Cisco 2504 WLC?

  According to the data sheet's 75:

  http://www.Cisco.com/en/us/prod/collateral/wireless/ps6302/ps8322/ps11630/data_sheet_c78-645111.html

  But according to the config guide, is 50:

  http://www.Cisco.com/en/us/docs/wireless/controller/7.3/configuration/guide/b_wlc-cg_chapter_01.html#ID263

  I believe that the correct number is 50, but I just want to be sure.

  Is this a limitation of the software?

  Yes, until 7.3 code only 50 APs are supported. 75 aPs are supported with 7.4 code.