4402-50 ap question

Similar Questions

• question about configuration transfer 4402 WLC

  Hello world

  I am thinking to replace an AIR-WLC4402-25-K9, which runs on the code 4.2.61.0 with an AIR-WLC4402-50-K9 running on 7.0.116.0. Can I back up the configuration of the AIR-WLC4402-25-K9 and restore it on AIR-WLC4402-50-K9? Otherwise, what is the best way to set up the AIR-WLC4402-50-K9? What I have to set it up from scratch?

  Thanks for any input.

  Robert

  Hello

  Nope! many new features is different in the code! the best way is to upgrade the WLC 4.2 to atleast 5.2 and more... coz the format of config backup is completely different in the two entities...

  Let me know if that answers your question and please do not forget to note the useful messages!

  Concerning

  Surendra

• I can't resive on account 4402 e mails

  IK kan geen e-mail question of slim op windows live mail er staat 4402 bij nummer

  Hello

  Please select your language from the drop-down menu above to post your question in the language of your choice.

  The forum in which you've posted is for English only. If you can't find your language above, support for additional international sites options are by following the link below:

  http://support.Microsoft.com/common/international.aspx

  Hope this information is useful.

• 4402 controller, Gigabit Port is 10/100/1000TX?

  Hi, this is a simple question.

  The port gigabit port 4402 is 10/100/1000TX UO just 1000TX?

  TIA

  1000Base is supported. You can use the two TX or FX SFP. best regards, Michael

• General questions about Cluster 4400 WLC

  I have inherited some 4402 wireless LAN controllers and I am in charge of making their ship-shape. So I have a few general knowledge wireless, I have not worked with before wireless controllers and have a few issues with that I was wondering if someone could help me:

  (1) how can I check that the primary and secondary controllers are configured for failover without actually performing a test? Both have AP failback enabled, but I don't know what else to check.

  (2) they are running code 3.2.116.21. If I want with 3.2 or plan to move up to 4.X?

  Thanks to a bouquet. I'm slowly working my way through the docs and the answers to them would of course speed up things.

  Hi Johnny,.

  I hope things are well with you! The steps required to set up relief AP are detailed in the attached doc. I would always try to provide a Maintenance window to test this point, rather than not knowing for sure :)

  WLAN controllers to access tipping points light Configuration example

  http://www.Cisco.com/en/us/Tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml#C4

  Now, for your second question, it is likely that you will want to upgrade the WLC to a version more recent code. They have passed through 4.0.x, 4.1.x and newer 4.2.x. 3.2 is a fair way behind. Take a look at the WLC Release Notes;

  Series 4400 Cisco Wireless LAN controllers Release Notes

  http://www.Cisco.com/en/us/products/ps6366/prod_release_notes_list.html

  I hope this helps!

  Rob

• WLC-4402-50 load balancing

  Hello

  I'm about to migrate from a stand alone to a sustained WLC WLAN infrastructure. I'll install a 4402-50 and I have a question regarding AP-manager interfaces.

  I read that each port supports up to 48 25 APs best practice and that the APs will decide what port they will connect it to less connected APs. I wonder what will happen if I connect one of the ports of another fiber optic link and the other to a copper 100 Mbit/s link?

  Thank you.

  Of course, its all covered in the configuration guide

  http://www.Cisco.com/en/us/docs/wireless/controller/6.0/Configuration/Guide/c60mint.html

• Creating groups of mobility with 4402

  I am looking to place three 4402 controllers of production in the same mobility group.  Currently, there is no mobility group.  My question is, will this affect somehow customers when I add the controllers to the same group?  I'm sure not, but I wanted to just make sure.

  Yes, you're right, it will not adversely affect the customer.

  #Mobility Group is useful for roaming, anchor and AP aid smoothly. WLC restart is not required to add/configure mobility.

  #If you have similar wlan configured on all these customers and 3 WLCs tried to roaming, it probably makes roaming with delays dhcp failover. Given that it is already harming those clients, feel free to set up mobility.

  #If APs on these 4402 s sharing RF so don't forget to set up similar groups of RF to avoid each idetifying APs themselves as thieves.

• Question order AAA

  Hi can someone explain me how the WLC (4402) decides which server to use for AAA?

  I have two servers set up as servers AAA, one with an index of 1 server and the other with an index of 2

  Index 1 = x.x.x.70

  Index 2 = x.x.x.38

  AAA of one of my wireless networks tab I listed them as:

  Server 1 = x.x.x.38

  Server 2 = x.x.x.70

  This is the Index number that is the deciding factor? What is the order in which they are listed AAA tab in wlan config page?

  See you soon

  Dylan

  Hello

  There are two ways to set the priority of the Radius server. If you have servers Radius defined under the WLAN will serve first of all the server defined as server 1, Server 2 will be used then, and so forth. If you do not have the Radius servers, listed under the WLAN, they will be used in the order that they appear in the global configuration (index).

  Backup RADIUS configuration will come also into play.  If you have RADIUS rescue disabled when the Radius primary server goes down the startup using secondary controller, but it goes back to primary school up until high school fails or the controller is restarted. If you have activated the controller will start using the primary server when it becomes available again.

  So, in addition to my head, these are the things that are coming...

  Can you please check the logs failed on the server to make sure that there are not all messages concerning requests for the controller?  May be that the shared secret key is not matching or the controller is not defined in the server.

  Even try to ping the server of WLC and see the connectivity...

  or even...

  check if there is no firewall problem between the WLC and the RADIUS server.

  Let me know if this answers your question!

  Concerning

  Surendra

  ====

  Please do not forget to note the useful post that answered your question or was useful

• 4402 wireless controller and the 1130AG access points

  I have a bunch of 1130AG (35) and 1231 points of access. I just bought a controller 4402 so I could handle these much easier access points. I currently have the offline access points, so I could control. With the wireless in the mix controller, that I have to fix these to light mode or can I leave them offline.

  We know not the operating instructions so I can leave them in stand-alone mode. Most of them is in the rafters in our warehuse, and I didn't have to pull of these if I have to. If I can use them offline, how can I do that?

  Thanks much for any info!

  Dave

  Hi Dave,.

  A WLC manages autonomous APs.
  So if you want to centralize the management of your APs through the WLC, you will need to convert it to light and enter them on the WLC.

  To convert the lightweight access points, you can choose between several options:

  1. thanks to a specific upgrade tool that you could install on a PC:
  http://www.Cisco.com/en/us/partner/docs/wireless/access_point/conversion/LWAPP/upgrade/guide/lwapnote.html

  2. [the most evolutionary] by WCS, with a model of migration that could apply to several APs:
  http://www.Cisco.com/en/us/docs/wireless/WCS/7.0/Configuration/Guide/7_0apcfg.html#wp1054876

  3. [not in any book] by the following steps:
  3 (a) download the CEC lwapp recovery image and store it on a TFTP server.
  3 (b) Telnet to the stand-alone PA and issuing the following command:
  Archive Download-sw / overwrite/reload tftp: / // [lwapp recovery image file path]

  As a general recommendation, before to convert the lightweight access points, you can be sure that the wired infrastructure behind is ready to direct them to the WLC for recording.
  It's suggestions explained in the link on the above option #1.

  Hope this helps,

  Fede

  --
  If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.

• WLC4402 - Questions to upgrade the AP and controller

  Hello

  I just upgraded an AIR-WLC4402-12-K9 to version 7.0.98.0 of the software, and I have a few questions-

  1. I have no APs to connect yet but when I do I'll have to check what software they run and perhaps demote the controller to get access up to v7 points?  To join the WLC v7 since v3.2 I had to make a few intermediate upgrades and I wonder if I have been a little premature and should have done updates after the APs have been associated, has new software pushed from the controller and then performed the steps in upgrade of WLC so the WLC and APs were synchronized in terms of software.

  2 - the memory usage is sitting at 60% with no associated APs.  I have just connected 4402-12 running 5.1.151.0 and he's sitting at 33% use of memory with associated access 11 points.  Have I spent in a too recent version for this controller?  What is a figure of the memory use of a 4402?

  Thanks in advance,

  Jason.

  Jason,

  A question.  You should be fine.  When the AP detects the WLC, it will do a code audit.  If this isn't the right code, it can extract the correct image of the WLC.  As long as the AP you are supported in 7.0, the recovery on the access point image won't matter.

  For question 2.  sounds of 60% of normal for 7.0, depending on the amount of memory is on the device itself.  I woulnd't ' t be too concerned about the memory usage until you points upward in the high 80 years.

  See you soon,.
  Steve

  --

  If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.

• About WLC 4402 LDAP client authentication

  Hello

  I'm install a WLC 4402, the client wants to authenticate users with the LDAP and what he expected to use current users in AD, however

  I just read some documents as reference 'Local EAP authentication server on the Wireless LAN Controller with EAPFAST and LDAP
  Configuration example"and «Web authentication via LDAP on LAN Protocol wireless controllers (WLCs) example Configuration»

  Require both the then to define a new OU and define a new user and select anonymous feature of Bind.

  My question is, should I add all current on AD users on the new ORGANIZATIONAL unit in order to be authenticated as a wireless client?

  I hope that someone of you can clear my doubt

  Kind regards

  Note that LDAP with AD requires no methods EAP-mschapv2. If you can't do PEAP-mschapv2 with AD as LDAP backend. EAP-FAST EAP-FAST (GTC) and no EAP-FAST (mschapv2). It is a limitation due to the way in which AD works in LDAP mode.

  The anonymous bind is not required at all, that it is to be like this in the example. Usually, anonymous bind is not allowed by default on the current version of windows server.

  You are not forced to push all the users in an OU. Simply give a search base DN to the WLC where the WLC can reach all customers on AD. If all your users organizational units are at the root of your domain, you will need to give "DC = domain, DC = com" as base DN and it means that each search will arrive on your entire ad, which isn't super effective. That's all.

  Nicolas

• Amount of access points allowed on a 4402 (50 PA)?

  We habe a WLC 4402 race (SW Version 6.0.196.0) which is supposed to support access 50 points.

  It is a solution of WLAN of comments with 2 Wireless LANs that are tunneled through the FW to a WLC anchor that leads to the internet and 1 WLAN which is directly lead to the corporate network.

  For the moment, I have attached... access 47 points and my problem is, I can't tie up more than that.

  I tried to take one of the 47 offline and then I could attached a new. But the limit seems to be 47.

  What can be the reason why 3 AP licenses are taken?

  Here is the log of the AP, which tries to connect:

  * 09:38:15.711 Mar 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller
  * 09:38:15.000 Mar 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.132.193 peer_port: 5246
  * 09:38:15.001 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed State to
  * 09:38:16.406 Mar 23: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.1.132.193 peer_port: 5246
  * 09:38:16.408 Mar 23: % CAPWAP-5-SENDJOIN: send request to join 10.1.132.193
  * 09:38:16.408 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE
  * 09:38:16.414 Mar 23: % DTLS-5-ALERT: WARNING received: close notify alert from 10.1.132.193
  * 23 Mar 09:38:16.414: % PEER_DISCONNECT-5-DTLS: Peer 10.1.132.193 has closed the connection.
  * 09:38:16.414 Mar 23: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.1.132.193:5246
  * 09:38:16.685 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
  * 09:38:16.686 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
  * 09:38:16.700 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
  * 09:38:16.700 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
  * 09:38:16.714 Mar 23: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
  * 09:38:16.714 Mar 23: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to
  * 09:38:16.716 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
  * 09:38:16.745 Mar 23: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
  * 09:38:16.746 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
  * 09:38:26.713 Mar 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  Here is the log of the WLC:

  * 23 10:55:18.314 Mar: 00: 3A: 98:1 c: 50:60 join RESP: failed to encode the IPV4 of CAPWAP control address
  * 23 10:55:18.314 Mar: 00: 3A: 98:1 c: 50:60 failed code the response to 10.3.8.240:64388 join
  * 23 10:55:18.316 Mar: 00: 3A: 98:1 c: 50:60 Config response failure: failed to send response to join to 10.3.8.240:64388
  * 23 10:55:18.317 Mar: 00: 3A: 98:1 c: State 50:60 machine Manager: failed to process the msg = 3 State = 0 10.3.8.240:64388 type
  * 23 10:55:18.317 Mar: 00: 3A: 98:1 c: 50:60 impossible to analyze packets 10.3.8.240:64388 CAPWAP
  (* 23 10:55:18.320 Mar: 00: 3A: 98:1 c: 50:60 throw no - ClientHello Handshake or DTLS encrypted package to 10.3.8.240:64388) since DTLS session is not established
  * 23 10:55:18.399 Mar: 00: 3A: 98:1 c: 50:60 join priority Processing status = 0, priority 1 of incoming Ap, MaxLrads = 50, joined Aps = 47

  Hello

  Here is the bug, I guess that we are hitting... If please run the workaround and let me know if it works...

  http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtf57349

  Let me know if this answers your question!

  Concerning

  Surendra

• How to add additional capacity for WLC-4402-12-K9-V02

  Hello

  End-user has a WLC-4402-12-K9-V02 with 8 towers is currently working, in short time will need to add more towers that will be more than 12.

  How we can increase capacity to support 25 laps.

  concerning

  Hello

  The WLC we currently supports maximum 12 APs, if you want to support more then to buy a WLC that supports several APs...

  http://www.Cisco.com/en/us/prod/collateral/wireless/ps6302/ps8322/ps6307/product_data_sheet0900aecd802570b0_ps6366_Products_Data_Sheet.html

  Let me know if this answers your question!

  Concerning

  Surendra

• Cisco AIR-LAP1041N-E-K9 does not not with WLC 4402 version 7.0.116.0

  Hi all

  appreciate your support for a problem I started to deal with today. I have a Cisco WLC 4402 running the 7.0.116.0 version and it's great to work with 25 Cisco 1252 access points. We received a new 20 Cisco 1041N APs today and I installed one in our site, but it does not work. He well worked and loaded the flash image and obtained WLC ip through DHCP option address and began to show the below error:

  * 00:00:10.021 Mar 1: % SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: crypto IOS FIPS self-test passed

  * 00:00:10.033 Mar 1: * CRASH_LOG = YES

  * 00:00:10.333 Mar 1: 1 Port is not presentSecurity base.

  MAC Ethernet address of base: C8:9 C: 1 D: 53:57:5E

  * 00:00:11.373 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on Dot11Radio interface 0

  * 00:00:11.465 Mar 1: % LWAPP-3-CLIENTEVENTLOG: reading and initialized AP event log (contains, 1088 messages)

  * 00:00:11.494 Mar 1: State of the voice_diag_test of WLC is false

  * 00:00:12.526 Mar 1: % LINK-3-UPDOWN: Interface GigabitEthernet0, changed State to

  * 00:00:13.594 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed State to

  * 00:00:13.647 Mar 1: % SYS-5-RESTART: System restarted.

  Cisco IOS software, software C1040 (C1140-K9W8-M), Version 12.4 (23 c) JA2, VERSION of the SOFTWARE (fc3)

  Technical support: http://www.cisco.com/techsupport

  Copyright (c) 1986-2011 by Cisco Systems, Inc.

  Updated Thursday, April 13, 11 12:50 by prod_rel_team

  * 00:00:13.647 Mar 1: % SNMP-5-start COLD: SNMP agent on host APc89c.1d53.575e knows a cold start

  * 00:08:59.062 Mar 1: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 1 Mar 00:08:59.062: bsnInitRcbSlot: slot 1 has NO radio

  * 00:08:59.138 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

  * 00:08:59.837 Mar 1: % SSH-5-ACTIVATED: SSH 2.0 has been activated

  * 00:09:00.145 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

  * 00:09:09.136 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface GigabitEthernet0 assigned address DHCP 172.16.26.81, mask 255.255.255.0, hostname APc89c.1d53.575e

  * 00:09:17.912 Mar 1: % PARSER-4-BADCFG: unexpected end of the configuration file.

  * 00:09:17.912 Mar 1: State of the voice_diag_test of WLC is false

  * 00:09:17.984 Mar 1: message logging LWAPP to 255.255.255.255.

  * 00:09:19.865 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online

  * 00:09:19.886 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

  * 00:09:20.873 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

  * 00:09:20.874 Mar 1: % SYS-6-LOGGINGHOST_STARTSTOP: logging to host started 255.255.255.255 - initiated CLI

  Translate "CISCO-CAPWAP - CONTROLLER.atheertele.com"... the domain server (172.16.40.240)

  * 00:09:29.029 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.16.100.102 drive address obtained by DHCP

  * 08:27:02.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:02.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:03.175 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:03.177 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:03.177 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:03.329 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:03.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:03.333: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:03.333 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:03.378 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:03.378 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:03.378: bsnInitRcbSlot: slot 1 has NO radio

  * 25 May 08:27:03.448: State of the voice_diag_test of WLC is false

  * 08:27:14.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:14.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:15.185 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:15.186 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:15.186 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:15.330 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:15.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:15.334: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:15.334 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:15.379 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:15.379 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:15.379: bsnInitRcbSlot: slot 1 has NO radio

  * 25 May 08:27:15.450: State of the voice_diag_test of WLC is false

  * 08:27:26.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:26.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:27.182 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:27.183 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:27.184 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:27.329 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:27.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:27.333: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:27.333 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:27.377 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:27.377 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:27.377: bsnInitRcbSlot: slot 1 has NO radio

  * 08:27:27.433 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

  * 08:27:27.446 may 25: % PARSER-4-BADCFG: unexpected end of the configuration file.

  * 25 May 08:27:27.447: State of the voice_diag_test of WLC is false

  * 08:27:27.448 may 25: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

  * 08:27:27.456 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

  * 08:27:38.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:38.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:39.183 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:39.184 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:39.184 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:39.326 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:39.329 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:39.329: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:39.330 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:39.375 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:39.375 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:39.375: bsnInitRcbSlot: slot 1 has NO radio

  * 25 May 08:27:39.446: State of the voice_diag_test of WLC is false

  * 08:27:49.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:49.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:50.179 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:50.180 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:50.180 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:50.323 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:50.326 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:50.326: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:50.326 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:50.370 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:50.370 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:50.370: bsnInitRcbSlot: slot 1 has NO radio

  * 08:27:50.425 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

  * 08:27:50.438 may 25: % PARSER-4-BADCFG: unexpected end of the configuration file.

  I searched the difference in regulatory areas between AIR-LAP1041N -E- K9 and AIR-LAP1041N -A- K9 and no difference was found which may affect the operation of this access point.
  to cite our WLC configuration for regulatory areas is:
  Country set AR codes

   

  Area of regulation 802. 11A:-A

  802.11bg:-a

  My question is should I just include my country in the WLC (IQ) add the field of requlatry (-E) to solve this problem? or change the country will affect the operation of all APs workers?

  Appreciate your kind support,

  Patrick Q.

  Try adding a European country to your regulatory domain.

• 4402-25 and 25-5508 fault tolerance?

  We have a Cisco 4402-25 running the 7.0.98 software version and we are interested in getting a new controller of 5508.  My question is can I load balance between these two or an act as a master and the other a slave?  Thank you

  We have a Cisco 4402-25 running software version 7.0.98 and we are interested in getting a new 5508 controller.  My question is can I load balance between these two or can one act as a master and the other a slave?
  

  The most common scenario of those made the access point for joining WLC 1 as a main controller and set up WLC 2 as a secondary controller.  Cisco recommended (or admitted) this inter-controleur roaming should be avoided at all costs.

  Roaming inter-controleur, still at the stage of since 3.X, this is "early childhood" is always in perfect.

  I hope this helps.