WLC 2112 - APs disassociating

I've found some discussion on this, but nothing that's helped resolve so I'm hoping someone can help. We recently purchased a 2112 WLC, running version 6.0.199.4. I have everything running through a single port on the controller, which is connected to a trunk port on our 3750 stack. Our management VLAN is vlan 40, and AP is plugged into another port on the same switch which is an access port in vlan 40. APs appear in the controller ok, receive an IP address, but we aren't able to connect to any of the WLANs and periodically the APs will disassociate with the following messages:
0
Thu Mar 22 09:47:51 2012
AP 'AP003a.99eb.702d', MAC: b8:62:1f:45:95:b0 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 35 m 52 s . Last reset reason: operator changed 11g mode
1
Thu Mar 22 09:47:39 2012
AP Disassociated. Base Radio MAC:b8:62:1f:45:95:b0
2
Thu Mar 22 09:47:39 2012
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:b8:62:1f:45:95:b0 Cause=New Discovery
I'm not sure if that's related to why we can't connect to the WLANs or not...
Another wrinkle is that if we plug in the AP directly to one of the PoE ports on the controller, it all works perfectly. Any ideas? I'm guessing its something switch-related since the only difference is that we're not going through the switch when it works.
Thanks in advance,
Matt

Both APs in the same switch and in different switches do the same thing. They don't reboot, just disassociate. Here is the status on one of them:
UP time: 2 hours+
Controller Associated Time: 6 minutes
Controller Association Latency: 14 seconds
They associate as soon as they come up, but then disassociate and reassociate. They have this message:
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:b8:62:1f:45:95:b0 Cause=New Discovery
in addition to sometimes showing a Heartbeat Timeout cause for the disassociation. In addition, sometimes it shows the cause being Max Retransmissions. I thought it was just the AP, but it happens with the second AP as well. Here are my switch port configs:
For AP:
interface GigabitEthernet7/0/14
description Test AP
switchport access vlan 40
switchport mode access
spanning-tree portfast
For WLC:
interface GigabitEthernet7/0/2
description WLC Management Port
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 40,55,82,94
switchport mode trunk
spanning-tree portfast trunk
It is detecting Rogue APs (these are the existing APs that we want to replace with this system). Could that be causing issues? I don't think so since it works just fine when plugged directly in to the WLC.
Could it be WLC software version?

Similar Messages

  • WLC 2112 with 1042 Mesh APs

    Hello everybody,
    I have a Mesh architecture with 2112 WLC and 1042 APs
    I want just to know if I can connect one 1310 AP to the ethernet port of a mesh 1042 AP with ethernet bridging enabled.
    thanks

    Hello benhamzagi,
    Thank you for contacting the Sales Acceleration Center (SAC) regarding your recent inquiry, Case Number 80931
    Case Description:
    WLC 2112 with 1042 Mesh APs
    Case Solution:
    Here is the compatibility Matrix link
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp118661
    Or the attach tables will help you base on Release, Controller, Mesh and AP
    Table 3 Controller Software Release and Controller Model Support Matrix
    Controller Model
    First Support
    Last Support
    2100
    4.2.x
    7.0.x
    2500
    7.0.x
    Cat3850
    3.2.0SE
    4400
    4.2.x
    7.0.x
    5500
    6.0.x
    5700
    3.2.0SE
    7500
    7.0.x
    8500
    7.3.x
    Virtual Controller
    7.3.x
    WiSM
    4.2.x
    7.0.x
    WiSM2 (1 DP)
    7.0.x
    WiSM2 (2 DP)
    7.2.x
    SRE
    7.0.x
    Table 4 Mesh and Controller Software Releases and the Supported APs
    Mesh and Controller Releases
    Supported Access Points
    7.4.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552EU, 1552CU, 1552S, 1130, 1240, 1250, 1260, 1600, 2600, 3500e, 3500i, 3500p, 3600e, 3600i, 1140, 600 OEAP, AP801, AP802
    7.3.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552EU, 1552CU, 1552S, 1130, 1240, 1250, 1260, 2600, 3500e, 3500i, 3600e, 3600i, 3500p, 1140, 600 OEAP, AP801, AP802
    7.2.11x.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552S, 1130, 1240, 1250, 1260, 2600, 3500e, 3500i, 3500p, 3600e, 3600i, 1140, 600 OEAP, AP801, AP802
    7.2.10x.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1552S, 1130, 1240, 1250, 1260, 3500e, 3500i, 3600e, 3500p, 3600i, 1140, 600 OEAP, AP801, AP802
    7.0.2x.x
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1130, 1240, 1250, 1260, 3500e, 3500i, 3500p, 1140, 600 OEAP, AP801, AP802
    7.0.116.0
    1522, 1524PS, 1524SB, 1552E, 1552H, 1552I, 1552C, 1130, 1240, 1250, 1260, 3500e, 3500i, 3500p, 1140, 600 OEAP, AP801, AP802
    7.0.98.x
    1522, 1524PS, 1524SB, 1130, 1240
    6.0.202.0
    1522, 1524PS, 1524SB, 1130, 1240
    5.2.193.0
    1522, 1524PS, 1130, 1240
    4.1.192.35M (Mesh Release 3)
    1505, 1510, 1522, 1524PS, 1130, 1240
    4.1.191.24M (Mesh Release 2)
    1505, 1510, 1522 (US, Canada, and RoW), 1130, 1240
    4.1.190.5 (Mesh Release 1)
    1505, 1510, 1522 (US and Canada)
    As per your confirmation, I am going to close the case for this specific inquiry. We strive to provide you with excellent service. Please feel free to reach out to me or any member of the SAC team if we can be of any further assistance or if you have any other related questions in the future. We value your input and look forward to serving you moving forward.

  • 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

  • WLC 2112 & MacBook or Apple Devices ???

    Dear All,
    Last week i succesfully configured the WLC 2112 with 12 AP ofcourse :)  with 3 SSIDs
    the issue i am facing is that users with MacBooks & Ipad's are having issues connecting to new wireless setup. where as all other Brand Laptops and PDAs are getting connected just fine.
    When i am trying to connect a MacBook to a SSID and when i enter the password after 10 or 15 sec the MacBook self assigns an IP address to itself intead of getting the password from WLC's DHCP.
    i have set  Authentication level is basic WEP key protection.
    Channel set to overlapping channel 10.
    Experts i need your Experties. will appriciate if i can get a Quick Response.

    Hi,
    Are the Mac and Apple devices configured to get a dynamic dhcp ? What is the Subnet from which these devices getting IP from ?
    Could you disable Aironet extenstions under wlan > advanced section and test as this enhances the third party clients to be able to connect to Cisco device.
    Regards,
    Madhuri

  • WLC 2112 with LAP 1042N

    Hi Guys.
    we are trying to configure WLC 2112 with LAP 1042 but getting following erros on LAP1042.
    It show the Ap is not supported in controller version 6.0.199.4
    *Jan  5 16:52:13.397: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.2.101 peer_port: 5246
    *Jan  5 16:52:13.398: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.2.101
    *Jan  5 16:52:13.399: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Jan  5 16:52:13.410: %CAPWAP-3-ERRORLOG: This AP is not supported in controller version 6.0.199.4
    *Jan  5 16:52:13.495: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Jan  5 16:52:13.496: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.2.101:5246
    *Jan  5 16:52:13.497: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Jan  5 16:52:13.498: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Jan  5 16:52:19.552: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is not established.
    *Jan  5 16:52:29.551: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    WLC 2112 software version 6.0.199.4
    LAP 1042 image version 7.0.94.21
    If any one can help me out then it wolud be great.
    Thanks in advance for all.

    You should upgrade your controller to 7.0.116.0 or 7.0.220.0
    Sent from Cisco Technical Support iPhone App

  • WLC 2112 is not accessable

    Hello Experts,
    I have a problem with my Cisco WLC 2112.
    Problems:
    1. I can not reach this WLC via GUI or CLI.
    2. Can not access via Console.
    3. Status LED is Dark Orange or Red.
    Can anybody help.
    Regards

    Hi,
    Status LED is Amber(ORANGE/RED)— Means Problem encountered during boot.
    http://www.cisco.com/en/US/docs/wireless/controller/2100/quick/guide/ctrl206q.html#wp39363
    Did u tried with these settings:
    9600 baud
    8 data bits
    No flow control
    1 stop bit
    No parity
    If the console is not responsive, then its a hardware failure and you should contact the TAC or You should RMA'd it.
    Be aware: WLC 2100 Series are EOL/EOS.
    http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps7206/ps7221/end_of_life_notice_c51-691053.html
    Regards
    Dont forget to rate helpful posts

  • APs disassociation from its WLC

    Hello,
    I have 2 WLC in my network and all APs are configured in H-REAP mode local switching, central authentication. The initial association occurs in the right way and the network works just fine, but suddenly without being espected every AP from the same VLAN lost connection with its default gateway. After review and test the gateway (in this case a L3 switch from other vendor) we found that every works fine; actually we connected a pc in a port with the same configuration used for AP and the PC works fine every time, even when the problem occurs.
    Solving the issue is easy; only have to plug and unplug the patchcord reseting the AP (works with PoE) and the AP again works fine, but there should be a deeper problem because the situation comes again and again. During the issue the AP show this log:
    *Apr 13 06:10:59.173: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    *Apr 13 06:13:09.215: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    *Apr 13 06:15:19.257: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    It looks like a DHCP problem, but after checking the DHCP server it is found that there are free IPs in the designated scope. Actually the AP mantains the original IP but as I said before, connection is lost between AP and its gateway.
    The log shows the following messages just before the disassociation:
    *Apr 13 06:06:38.403: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_ECHO_REQUEST
    ., 2)
    *Apr 13 06:06:38.403: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode
    *Apr 13 06:06:38.407: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
    *Apr 13 06:06:38.407: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.133.129.4:5246
    *Apr 13 06:06:39.084: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
    *Apr 13 06:06:39.087: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Apr 13 06:08:49.127: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    *Apr 13 06:10:54.412: %AAA-3-BADSERVERTYPEERROR: Cannot process authentication server type radius (UNKNOWN)
    *Apr 13 06:10:54.413: %DOT11-7-AUTH_FAILED: Station 0024.2ce5.2876 Authentication failed
    For detailed information about the AP, I attach the complete show tech.
    Thank you for ideas.
    Regards,
    Juan David Flórez

    It may be that you are missing option 43... The AP does not know how to find the controller or there is no ip connectivity from the AP ip address to the controller
    Sent from Cisco Technical Support iPhone App

  • DHCP setup help on AIR-WLC-2112 with LAP1042N

    I am new to wireless.  I would like to statically assign ip addresses for my controller(AIR_WLC-2112) and my access point (LAP1042N).  I would then like the controller to distribute dhcp addresses for users.  What is the best way in doing this? 

    Hi Mark,
    You can certainly setup your network for 2 VLANs for different wireless networks. You will only need to setup the switchports to the WLC as trunks. In other words, the APs will simply reside in the vlan you define (access switchports) and they will tunnel all traffic back to the controller, regardless of client vlan. The WLC will then determine which vlan the traffic needs to go on.
    You have 2 ways of setting your AP IP addresses as static -- you can statically assign them through the console during initial installation:
    capwap ap ip address
    capwap ap ip default-gateway
    capwap ap controller ip
    Or, you can simply let the APs start by using DHCP, and auto discovery of the WLCs via DNS lookup of "cisco-capwap-controller", or DHCP option 43. Once they join the controller you can assign them static addresses in the WLC AP settings.
    Now, onto the last question regarding your WAN sites. We do have options for you there as well -- the feature we're looking at would be H-REAP. Traditionally the APs tunnel all wireless traffic back to the controller. However, in H-REAP mode, you can specify the APs to put traffic on the network right at the local switch, so it wouldn't have to get tunneled across your WAN (depending on WAN bandwidth). You still configure the AP and manage it centrally. For more information on this feature, please check out the H-REAP deployment guide:
    http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080736123.shtml
    -Patrick Croak
    Wireless TAC

  • WLC 5508 APs showing Line Protocol Down

    I have a WLC 5508 (software version 7.5.102.0) and it has 175 APS (mixture of 1131, 1142, 1602, 2602).  Recently I've noticed that
    about 40 of those APs don't work on the 2.4G Dot11Radio0.  sh int dot11 0 shows me:
    Dot11Radio0 is up, line protocol is down
      Hardware is 802.11N 2.4GHz Radio, address is 1833.9d0c.2180 (bia 1833.9d0c.2180)
      MTU 1500 bytes, BW 54000 Kbit/sec, DLY 1000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input never, output 00:00:00, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/9355/42086/0 (size/max/drops/flushes); Total output drops: 3769399
      Queueing strategy: fifo
      Output queue: 0/30 (size/max)
      5 minute input rate 11000 bits/sec, 13 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         150800958 packets input, 597188558 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 input packets with dribble condition detected
         217132697 packets output, 1132963042 bytes, 0 underruns
         55238 output errors, 0 collisions, 8 interface resets
         0 unknown protocol drops
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    I've tried restarting the interface,to no avail, but rebooting the whole AP does bring it back up, but I expect that's a solution to the symptom, not the problem.

    Hi Sean,
    There are certain related bugs of this version. You may need to check whether you are hitting one these. I would suggest staying in 7.4.121.0 code would be a good idea unless you require new features available in 7.5 or 7.6.
    CSCui66891:Marvell-based radio goes down due to stuck multicast packets in driverSymptom:AP's radio interface goes down and does not recover on its own without an AP reboot.Conditions:With releases 7.2.103.0 - 7.2.115.2, 7.3.101.0 - 7.3.112.0, and 7.4.100.0 - 7.4.110.0, this bug applies to all Marvell-based 802.11n Cisco Aironet access points *except* the 1140, 1040, and certain mesh APs.With releases 7.5.90.0 - 7.5.102.0, this bug applies to *all* Marvell-based 802.11n Cisco Aironet access points.Workaround:None. Reboot the AP.
    Known Affected Releases(6)7.6(1.52)7.6(1.50)7.5(102.0)7.6(1.226)7.6(1.95)15.2(4)JA
    Known Fixed Releases(10)10.1(0.74)7.6(1.55)7.5(102.8)10.1(100.0)15.2(4)JN7.6(1.103)10.1(11.5)7.4(111.7)15.2(4)JB7.4(121.0)
    CSCum14069: AP1600/2600 radio down with 7.5.102.0 release  Symptom:[AIR-CAP1602I-Q-K9 (AC power supply) ]---------[Catalyst switch]------------[AIR-CT5508-K9 (7.5.102.0)][AIR-CAP1602I-Q-K9 (PoE) ]----[AIR-PWRINJ5=]-----[ Catalyst switch]------------[AIR-CT5508-K9 (7.5.102.0)][AIR-CAP1602I-Q-K9 (AC power supply) ]---------[non-Cisco non-PoE switch]------------[AIR-CT5508-K9 (7.5.102.0)]AP1600/2600 radios never go UP on above topology if the Catalyst switch was running older IOS such as c3750-ipservices-mz.122-25.SEB4
    Conditions:WLC release 7.5.102.0 specific issue.AP1600/2600 specific issue.Older Catalyst IOS software (e.g. 12.2(25)SEB4)non-Cisco 3rd party switch
    Workaround:Enable "Pre-standard 802.3af switches" option on AP from WLC GUI;WIRELESS => Access Points => All APs => target AP name => Advanced tab => Power Over Ethernet SettingsThis option is required to workaround this problem even if you don't have Pre-standard 802.3af switch nor you're using AC adapter/Power Injector.
    Known Affected Releases:(1)7.5(102.0)Known Fixed Releases:(1)7.5(102.18)
    HTH
    Rasika
    **** Pls rate all useful responses *****

  • 5508 WLC + 3702I APs /w a Windows 2012 DHCP Server

    All,
      I am in the process of a new WLC install with five 3702I APs.  The configuration was gone well up till now.....  I am having issues with DHCP pulling IPs from the correct scope. The WLC is in a different VLAN (10) than the APs (142).  What am I missing in the configuration?  We have multiple autonomous 1252s that pull the correct scope.  Any suggestions would be greatly appreciated. 
      Dave

    Are you  having issues with client getting IP when they connect to 3702 ? or AP itself not taking IP ?
    Either case I would check switch SVI is configured with "ip helper-address x.x.x.x" pointing to your DHCP server.
    Also for dynamic interface configuration of WLC I would check all interfaces correctly configured with DHCP server address.
    You can run " debug client <mac_address>" on WLC CLI for a single client & post that output if you still facing the issue
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • WLC+16 APS *THE WIFI CLIENTS DOES NOT ASSOCIATE TO THE STRONGEST AP SIGNAL

    hi, i am working with a WLC 4102, and i have about 16 aps (lwapp) installed in different locations, but i have a big problem, when a wifi client is already associated to and ap, this wifi client does not associatte to the ap with the bigger signal. how can i solve it?

    Roaming is primarily based in client decision. Try upgrading driver and firmware on the client.Different venodrs various stratagies for roaming. You should look for specific parameters on client.

  • 4 LAP1522, WLC 2112, 15dB antenna

    Hy,
    I have a problem with low power signal receive on antenna.
    If I stay near to antenna the signal power is to 50%.
    It's ok?
    I have 1 WLC Controller 2112, the TX signal power is set to 1.
    It's possible to miss some configuration on WLC?

    Make sure the AP has enough power. Lower power on the AP results in lower signal strength, which decreases the throughput.

  • WLC 4402 - APs last reboot reason power loss

    st1\:*{behavior:url(#ieooui) }
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Normale Tabelle";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    Hi,
    we have a Wireless LAN Controller WLC 4402, Software Version 4.1.192.22M (Mesh).
    At the moment there are 6 Access Points in one house, one of them is the root AP. The others are only connected via electrical socket.
    AP’s are: AIR-LAP1131AG-E-K9 / Boot Version 12.3.8.0 / IOS Version 12.4(3g)JMC1
    I think the configuration worked fine over a period of 2 years.
    Now the problem is that the number of access points connected to the controller is changing nearly every minute. At times there is only one AP connected to the controller. So it is impossible for the clients to build up a steady connection. They have to log in via the guest user web interface at short intervals or they can’t see the wireless lan.
    First we thought it would be a problem of one or two “defect” access points. But we replaced 4 of the 6 access points and the problem is still there.
    An example, yesterday:
    13:17 o’clock – 2 AP’s
    13:19 o’clock – 4 AP’s
    13:21 o’clock – 5 AP’s
    13:23 o’clock – 4 AP’s
    13:25 o’clock – 5 AP’s
    13:25 o’clock – 4 AP’s
    13:26 o’clock – 5 AP’s
    13:26 o’clock – 6 AP’s
    13:28 o’clock – 4 AP’s
    13:28 o’clock – 2 AP’s
    Eye-catching is the following message of the log, which appears often: “52       Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
    Also eye-catching is the AP up time. The Root AP is up for over 80 days. But all the other access points show an up time of a few minutes until some hours…but not more.
    Does anybody know what the problem could be?? I read some similar threads but no solution.
    In the following an abstract of the log:
    21        Mon May 16 13:25:43 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
    22        Mon May 16 13:25:30 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
    23        Mon May 16 13:25:30 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    24        Mon May 16 13:25:30 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    25        Mon May 16 13:25:05 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
    26        Mon May 16 13:24:10 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
    27        Mon May 16 13:24:10 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    28        Mon May 16 13:24:10 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    29        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    30        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    31        Mon May 16 13:23:59 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    32        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    33        Mon May 16 13:23:58 2011        AP 'AP001d.45d8.4ea6', MAC: 00:1d:71:e1:b2:20 disassociated previously due to AP Reset. Last reboot reason: power loss
    34        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    35        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    36        Mon May 16 13:23:31 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    37        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    38        Mon May 16 13:23:30 2011        AP 'AP001d.e557.6f0c', MAC: 00:1d:70:01:b5:a0 disassociated previously due to AP Reset. Last reboot reason: power loss
    39        Mon May 16 13:23:13 2011        Client Association: Client MAC:00:1d:71:e1:b2:2f Base Radio MAC :00:1d:70:01:bc:20 Slot: 1 User Name:c1130-001D45D84EA6
    40        Mon May 16 13:23:13 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
    41        Mon May 16 13:23:04 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:23:5e:49:9d:e0' from mesh node '00:1f:ca:cc:b7:40'.
    42        Mon May 16 13:22:57 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
    43        Mon May 16 13:22:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
    44        Mon May 16 13:22:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    45        Mon May 16 13:22:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    46        Mon May 16 13:22:39 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
    47        Mon May 16 13:22:17 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
    48        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    49        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    50        Mon May 16 13:21:57 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    51        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    52        Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
    53        Mon May 16 13:21:39 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
    54        Mon May 16 13:21:32 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
    55        Mon May 16 13:21:12 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:b5:a0'.
    56        Mon May 16 13:21:05 2011        Client Association: Client MAC:00:1d:70:01:bc:2f Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-001DE5576FD8
    57        Mon May 16 13:20:32 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
    58        Mon May 16 13:20:11 2011        Mesh child node '00:1d:70:01:bc:2f' is no longer associated with mesh node '00:1f:ca:cc:b7:40'.
    59        Mon May 16 13:20:06 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
    60        Mon May 16 13:19:57 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
    61        Mon May 16 13:19:57 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    62        Mon May 16 13:19:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    63        Mon May 16 13:19:49 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:bc:20
    64        Mon May 16 13:19:49 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
    65        Mon May 16 13:19:49 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
    66        Mon May 16 13:19:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
    67        Mon May 16 13:19:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
    68        Mon May 16 13:19:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
    69        Mon May 16 13:19:36 2011        AP Disassociated. Base Radio MAC:00:1d:71:e1:b2:20
    70        Mon May 16 13:19:36 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
    71        Mon May 16 13:19:36 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
    Greetings Lydia

    st1\:*{behavior:url(#ieooui) }
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Normale Tabelle";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    Hey,
    last week I tried to upgrade the controller step-by-step.
    Under the software 4.1.192.35M the problem was still there… access points were often disassociated from the controller.
    There were problems with Software 4.2.207.54M too. The access points couldn’t reach the download-status. The log of the access point said that it could not open the tar-file.
    So I went back to 4.1.192.35M. Of course the controller lost some of its configuration. I configured it new with the same settings as before.
    After it the wireless connection seemed to be a little bit more robust. I asked the users to test the connection at the weekend and this is the answer:
    “so we tested the WLAN during the weekend. The situation definitely improved with respect to before. Authetication is much faster and the connection (when active) is sensibly faster.
    However the connection is still very unstable and it is necessary every five-ten minutes to reconnect (especially for intense network traffic like when watching a streaming content or using VOIP applications. Actually switching off and on again the WLAN card (Airport) often a new authentication is not required. However, without doing so the connection would not resume alone to a working state.
    So what to say? Better than before (thanks) but far from being fixed. From last September to January we did not experience any problem, so it must be something that chronologically happened at the beginning of the year, it is not a systemic problem.
    But there were no changes or anything else at the beginning of the year.
    Do you mean it makes sense to resume upgrading? I’m a little bit afraid of more problems like under 4.2.207.54M
    Greetings Lydia

  • 2100 WLC 1130 APs - need some help please

    It's been about 5 years since I took my CCNA course and could use some help on a wireless set up for church.
    We have a Catalyst 3550 that is running fine, just a few VLANs, including 30 for public wireless.  I've then got a 2100 WLC and (3) 1130 AP's.  After much head banging, I've got the WLC set up correctly (i believe)
    VLAN 30 is a 10.0.3.x segment
    switch is 10.0.3.1
    WLC mgmt interface is 10.0.3.20 - connected to the switch on port 1
    WLC ap mgmt interface is 10.0.3.21
    APs pull 10.0.3.30, 31,32. - they are plugged directly into the switch
    I can obviously see the APs while in the WLC GUI. 
    The AP's SSID don't show up wirelessly.  The AP's circle is red/orange
    The detail on the AP in the WLC shows them operationally down.
    What additional information can I provide?
    Much thanks.

    flashfs[0]: 28 files, 8 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 15998976
    flashfs[0]: Bytes used: 6973952
    flashfs[0]: Bytes available: 9025024
    flashfs[0]: flashfs fsck took 28 seconds.
    Base ethernet MAC Address: 00:0a:b8:12:30:3c
    Initializing ethernet port 0...
    Reset ethernet port 0...
    Reset done!
    ethernet link up, 100 mbps, full-duplex
    Ethernet port 0 initialized: link is up
    Loading "flash:/c1130-k9w8-mx.124-23c.JA4/c1130-k9w8-mx.124-23c.JA4"...#########
    File "flash:/c1130-k9w8-mx.124-23c.JA4/c1130-k9w8-mx.124-23c.JA4" uncompressed a
    nd installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.4(23c)JA4, RELEASE
    SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Fri 27-Jan-12 19:52 by prod_rel_team
    Proceeding with system init
    Proceeding to unmask interrupts
    Initializing flashfs...
    flashfs[1]: 28 files, 8 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 15740928
    flashfs[1]: Bytes used: 6973952
    flashfs[1]: Bytes available: 8766976
    flashfs[1]: flashfs fsck took 4 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    Radio0  present A506 7100 E8000000 A0000000 80000000 3
    Radio1  present A506 6700 E8000100 A0040000 80010000 2
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    cisco AIR-LAP1131AG-A-K9   (PowerPCElvis) processor (revision A0) with 27638K/51
    20K bytes of memory.
    Processor board ID FTX1027T1S2
    PowerPCElvis CPU at 262Mhz, revision number 0x0950
    Last reset from power-on
    LWAPP image version 7.0.230.0
    1 FastEthernet interface
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:0A:B8:12:30:3C
    Part Number                          : 73-8962-09
    PCA Assembly Number                  : 800-24818-08
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC102618H2
    Top Assembly Part Number             : 800-25544-06
    Top Assembly Serial Number           : FTX1027T1S2
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-LAP1131AG-A-K9
    % Please define a domain-name first.
    Press RETURN to get started!
    *Mar  1 00:00:05.580: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self t
    est passed
    *Mar  1 00:00:07.185: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self
    test passed on interface Dot11Radio 0
    *Mar  1 00:00:08.783: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self
    test passed on interface Dot11Radio 1
    *Mar  1 00:00:08.860: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log
    (contains, 135 messages)
    *Mar  1 00:00:08.889:  status of voice_diag_test from WLC is false
    *Mar  1 00:00:10.995: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to
    up
    *Mar  1 00:00:11.052: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.4(23c)JA4, RELEASE
    SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Fri 27-Jan-12 19:52 by prod_rel_team
    *Mar  1 00:00:11.053: %SNMP-5-COLDSTART: SNMP agent on host CenterHall is underg
    oing a cold start
    *Mar  1 00:00:11.133: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Mar  1 00:00:11.312: %SSH-5-ENABLED: SSH 2.0 has been enabled
    *Mar  1 00:00:11.312: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar  1 00:00:11.312: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
    *Mar  1 00:00:11.552: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r
    eset
    *Mar  1 00:00:11.552: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
    eset
    *Mar  1 00:00:11.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
    et0, changed state to up
    *Mar  1 00:00:12.316: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
    0, changed state to down
    *Mar  1 00:00:12.316: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
    1, changed state to down
    *Mar  1 00:00:19.436: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned D
    HCP address 10.0.3.30, mask 255.255.255.0, hostname CenterHall
    *Mar  1 00:00:29.995:  status of voice_diag_test from WLC is false
    *Mar  1 00:00:30.070: Logging LWAPP message to 255.255.255.255.
    *Mar  1 00:00:30.123: %CDP_PD-2-POWER_LOW: All radios disabled - HIGH_POWER_CLAS
    SIC_NOT_CONFIGURED WS-C3550-12T (000a.8a97.f785)
    *Mar  1 00:00:31.123: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.
    255 started - CLI initiated
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (8.8.8.8)
    Translating "CISCO-LWAPP-CONTROLLER"...domain server (8.8.8.8)
    *Feb 11 15:46:42.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
    p: 10.0.3.21 peer_port: 5246
    *Feb 11 15:46:43.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
    wmmAC status is FALSE
    *Feb 11 15:46:44.672: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
    peer_ip: 10.0.3.21 peer_port: 5246
    *Feb 11 15:46:44.674: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.3.21
    *Feb 11 15:46:44.674: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Feb 11 15:46:45.449: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Feb 11 15:46:45.718: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
    *Feb 11 15:46:45.767: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller grace
    wireless
    *Feb 11 15:46:45.815: %LWAPP-3-CLIENTEVENTLOG: SSID GUMC_Guest added to the slot
    [0]
    *Feb 11 15:46:45.818: %LWAPP-3-CLIENTEVENTLOG: SSID GUMC_Guest added to the slot
    [1]
    *Feb 11 15:46:45.834: %WIDS-5-ENABLED: IDS Signature is loaded and enabled
    User Access Verification
    Username: Cisco
    Password:
    CenterHall>

  • Upgrade WLC and APs

    Hi,
    We have 3 WLCs (AIR-WLC4402-50-K9) running 6.0.196.0 code.
    There are ~55 APs shared among WLC1 and WLC2. WLC3 act as global backup for WLC1 and WLC2.
    APs on WLC1 are configured WLC1 as primary and WLC3 as secondary controller.
    APs on WLC2 are configured WLC2 as primary and WLC3 as secondary controller.
    Since we are planning to deploy few 3502 APs therefore we need to upgrade the WLCs to code 7.x
    I was planning the following:
    1. upgrade WLC3 first and use the new code as backup image first and the existing one as primary
    2. upgrade WLC2 in the same way as WLC3
    3. predownload the new code to the APs associated with WLC2 and swap the image to use the existing one as primary and the new one as backup
    4. upgrade WLC1 in the same way as WLC3
    5. predownload the new code to the APs associated with WLC1 and swap the image to use the existing one as primary and the new one as backup
    So far if either the WLC or AP restart for some reason come back with the original image.
    6. Change primary image to 7.x on WLC3 and reboot > WLC3 comes up with new image
    7. swap image for APs registered with WLC2 and Change primary image on WLC2 to 7.x
    8. Reboot APs with WLC2 and WLC2 as well > APs boot up with new image and go to WLC3 if WLC2 is not up yet or back to WLC2 itself
    9. Check if APs are on WLC3 if so reboot APs again to go back to WLC2
    9. Repeat step 7 for WLC1 >  APs boot up with new image and go to WLC3 if WLC1 is not up yet
    10. Check if APs are on WLC3 if so reboot APs again to go back to WLC1
    Is the above mentioned process sufficient or do somebody know a better/shorter one?
    Do anyone have some experience with such excercise?
    Thanks,
    Krisztian

    Hi Ven,
    OK thanks for the answer.
    However I would need sort of confirmation on the entire process .
    Suppose WLC1 and WLC2 are the primary and WLC3 is the backup controller for both WLC1 and WLC2. WLC3 has no APs associted with it.
    What I was planning:
    1. Load the new code to the backup WLC3 and swap image to use the existing image (6.x) as primary and the new code (7.x) as failover. Reload controller?
    2. Move the APs to backup controller WLC3 (in such a way you mentioned) and predownload backup image (7.x) (which is in fact going to be the new code eventually)
    3. Upgrade the primary controller WLC1 and use the new code (7.x) as primary image. Reboot controller. WLC1 comes up with new code (7.x).
    4. Swap the image on APs to use the new code (7.x) as primary and change the primary controller to the original one WLC1. Reboot APs.
    5. Move APs from WLC2 to WLC3 like did for WLC1. APs and WLC3 still runs old code (6.x).
    6. Predownload backup code to APs.
    7. Do step 3. for WLC2.
    8. Do step 4. for WLC2.
    9. Swap image on WLC3 to use 7.x as primary and 6.x as failover. Reboot WLC3. WLC3 comes up with new code.
    10. Relax have some beer and enjoy
    Is the above described the correct way?
    Thanks,
    Krisztian

Maybe you are looking for

  • How can I get my iPhone 4 repaired while away from home?

    I will be working in Manila in the Philippines for the next few months. My iPhone 4 has developed a hardware fault and needs to be repaired. It is out of warranty, but I am willing to pay for the cost of the repair myself. The Apple Authorized Servic

  • Here is whats new for me with pr1.3 so far...

    phone feels much faster and snappier, the email client opens emails way faster now, and syncs without errors, the web browser is way better, very fast, and very smooth, zooming in/out are faster, and there is a slight flash update, so now my flash fe

  • Please i need help to install the HP laserjet pro 100 color MFPm175 series

    hello sir,              please i need a help how to install hp laserjet pro 100 color mfp m175 series drive.              i just bought the printer today.

  • How to make Messages appear on a specific View?

    Hi, we are bulding a webdynpro application which uses several views in different components. We are using the IWDMessageManager to display messages. The strange thing is, that the messages do not always appear in the view You would expect. For exampl

  • Start_Service is Not Available in OWB Control Center Manager

    I am running OWB 10.2.0.1.0 I have one problem connecting to the Control Center Manager (RTC-5260,RTC-5301). RTC -5260: Failed to connect to Control Center. Please check you have provided the correct host, user, password, and service name. RTC - 5301