Lost connection on lan controller 2106

hi,
I have problem with access point air-lap1242ag-a-k9 work with lan controller air-wlc2106-k9.
the connection works well during a time but soon it is lost during few minutes and soon it raises automatic, this process repeats the day throughout. I have seen that valor AP ID in the LAN controller changes when this happens.
thanks for the aid
Marcos.

Hi Marcos,
So are you saying that the AP disapears from the controller for a little while, then comes back?
Are the APs in the same subnet as the management/ AP manager interfaces? I would do a debug lwapp events enable and check how many broadcast sources you have in this subnet. It happens that when there are too many sources of broadcast, APs get disconnected; isolating the APs in another subnet/VLAN usually solves the issue.
Tx
Jerome

Similar Messages

  • LAN controller (2106) not recognizing 1131AG Ap

    I am configuring my LAN controller and its not recognizing my 1131AG AP

    Errrr ... can you provide more info please?
    Firmware?
    Error logs?
    NTP configured?
    Power injector or PoE?

  • What happens if Local Mode LAP lost connection to Controller?

    Hey,
    I wonder what happens to the wireless client and LAP running in local mode if connection to wireless lan controller is down OR the controller itself is down? I do not think LAP will reboot by itself but will wireless client lost wifi connection and internet connection via the LAP?

    H-REAP/FlexConnect is different and it can keep clients connected depending on authentication methods. This will explain it better:
    http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_flexconnect.html#wp1224777
    Sent from Cisco Technical Support iPhone App

  • How to replace the certificate of Cisco 2106 wireless LAN controller for CAPWAP ?

    I have interested in CAPWAP feature and I download the open capwap project to make Access Controller (AC) and Wireless Terminal Point (WTP). I had built the AC which used PC and WTP which used Atheros AP. The CAPWAP feature work well when I enabled the CAPWAP that used my own AC  and WTP. When I got the Cisco 2106 wireless LAN controller (Cisco WLC), I configured the Cisco WLC to instead my own AC but I got the authorize fail in Cisco WLC side. It seem the Cisco WLC could not recognize the CAPWAP message which sent form my own WTP. I think this issue just need to synchronize the certificate between Cisco WLC and WTP.So I need to replace the Cisco WLC's certificate manually. Does anyone know how to replace the certificate manually with Cisco WLC ?
    Best Regards,
    Alan

    Unfortunately this Support Community is for Cisco Small Business & Small Business Pro product offerings.  The WLC2106 is a traditional Cisco product.  You can find this type of support on the Cisco NetPro Forum for all traditional Cisco products.
    Best Regards,
    Glenn

  • Can cisco CAP2702i connect to Cisco3850 switch with wireless LAN controller license via another switch ?

    If i connect cisco AP - CAP2702i to another switch, and use trunk port between Cisco3850 and the other switch , can the AP able to register with Cisco3850 with wireless LAN controller  ?   or the AP has to directly connect to Cisco3850 in order to register?

    The AP and 3850 wireless management are in same Vlan( vlan202). The AP is new unit and did not join MC before. 
    What i did on 3850 :
    input command - wireless management interface vlan 202
                              - ap cdp
                              - wireless mobility controller
    Is there any config i miss out on 3850 and any config need to be set on AP ?
    From Ap console output show me "could not discover WLC using dhcp ip". Is it due to AP dont have IP address? If AP register with WLC through layer 2 , i believe there is no related with IP.Correct me if i'm wrong.
    Due to the 3850 is not a POE, the AP unable directly connect to 3850  . I guess have to use power adapter to power on the AP.

  • MSI 890 GXM-G65 LAN Controller Issue

    Hello, Forum!
    I have had this motherboard for the past few years, loved it, and then the LAN controller suddenly decided to "stop working."  What I mean by that is that when I boot up, Windows loads, and then I have no network connection.  I have updated the Realtek drivers, flashed the latest BIOS, disabled/reenabled drivers, renewed IP address, statically assigned an IP address, flushed DNS, installed BC Edit.  The *one* thing that "solves" the problem is hitting F8 upon bootup and selecting "Disable Microsoft Driver Signature  Enforcement."  I'll have network connection again after that, but then it goes away upon the next boot up, so I have to do this *every* time I want to use the computer.  This gets kinda annoying, especially when I do leave it on during a download from Steam or something overnight, it needs to reboot for updates or part of the install process, then it boots back up and connection is lost, so download doesn't complete until the next day when I reboot it *again* and do the F8 routine.  Because I have a beast-sized graphics card and an audio card, I have no room for a separate NIC card. 
    Computer specs:
    The aforementioned mobo in the subject line
    AMD Phenom II x6 1055T
    12GB DDR3 RAM
    NVIDIA 550Ti 1GB
    ASUS Xonar DG sound
    Antec 450w Earthwatts power supply
    I have been trying to Google the problem and ask people who were formerly Microsoft tech support, but this has not help.  Can anyone help?

    I run Windows 7 x64.  I have a desktop and a laptop, both of which have had reinstalls done on them in the past (long before the LAN issue on the desktop happened), both had problems with reinstalling because it wouldn't let me re-use my product key. I then had to buy all new copies of Windows (I *really* try to stay away from torrenting).  This is not a hassle or expense that I wish to go through again unless I *know* it will fix the problem.
    Three things that I neglected to mention that I've tried are:
     - System Restore
     - Set to Last Known Good Configuration
     - Installing a USB wireless adapter - that doesn't work either without the whole F8 routine.

  • "Partially lost connectivity" error message

    We're conducting some load testing and when we reach a certain threshold in the test, Coherence will report this error:
    [2010-10-21 20:21:39,376] ERROR [Logger@9243969 3.5.3/465p7] (Log4j.CDB:3) - 2010-10-21 20:21:39.376/7166.760 Oracle Coherence GE 3.5.3/465p7 <Error> (thread=Cluster, member=6): This node appears to have partially lost connectivity: it receives responses from MemberSet(Size=2, BitSetCount=2, ids=[4, 7]) which communicate with Member(Id=5, Timestamp=2010-10-21 18:22:38.456, Address=10.13.9.35:13921, MachineId=3619, Location=site:int.qaload.lan,machine:bcla01,process:9977, Role=RNTCServerEmbedded, PublisherSuccessRate=0.9615, ReceiverSuccessRate=0.9879, PauseRate=0.0020, Threshold=1785, Paused=false, Deferring=false, OutstandingPackets=1, DeferredPackets=0, ReadyPackets=0, LastIn=91315ms, LastOut=3301ms, LastSlow=n/a), but is not responding directly to this member; that could mean that either requests are not coming out or responses are not coming in; stopping cluster service.
    We've verified that we're not approaching the capacity of the NIC on the server or the network itself. The CPUs on the servers are also well under maximum levels.
    Other than the obvious (i.e. a network connectivity problem), what would cause this error? In other words, under what circumstances is this error displayed?

    Hi Jeff,
    Not sure if you've seen the description of the message here ...
    http://coherence.oracle.com/display/COH35UG/TCMP+Log+Messages
    Cause : The communication link between this member and the member indicated by %s2 has been broken. However, the set of witnesses indicated by %s1 report no communication issues with %s2. It is therefore assumed that this node is in a state of partial failure, thus resulting in the shutdown of its cluster threads.
    Action : Corrective action is not necessarily required, since the rest of the cluster presumably is continuing its operation and this node may recover and rejoin the cluster. On the other hand, it may warrant an investigation into root causes of the problem (especially if it is recurring with some frequency).
    Thanks

  • Competition problem between Windows 8.1 and Windows 7 on Photosmart C5180 connected via LAN

    Hello everyone, I am writing because I need some advice / help on a problem last night while configuring a small network.
    The network is made up as follows:
    2 notebook: Windows 8.1 and Windows 7
    3 different printers:
    2 USB connected to the respective notebook,
    1 HP Photosmart C5180 network printer connected via LAN via a router.
    The situation is the following:
    both notebooks recognize the various printers and are able to send and print documents but,
    when the print command starts from both notebook SIMULTANEOUSLY or at a distance of a few seconds, the only document printed is ALWAYS the one sent from the notebook with WINDOWS 8.1. The other one submitted by WINDOWS 7 IS LOST without being reported.
    So if I ask of you is someone experienced in the print queues, print drivers, competition in the print jobs that can help me in solving this problem.
    Thanks in advance

    Hello cesco,
    Welcome to the HP Forums.
    I see that you are having a communication issue when attempting to print on two separate printers at the same time.
    This will be a communication issue for sure.  The computer can only send to one printer at a time. You will have to print to one printer, wait for it to finnish the print job and then send it to the other printer. 
    There is no way that you can print from one computer to two separate printers at the same time.
    Thanks for your time.
    Cheers, 
    Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    W a t e r b o y 71
    I work on behalf of HP

  • Issues after changing the AP Name on Wireless LAN Controller

    I recently changed the AP Name of all the Wireless Access Points in my branch office (which are all associated to the branch office Wireless LAN Controller(s)). After that I noticed that all branch office employees are unable to connect to the employee SSID. The employee SSID uses web authentication and employees are authenticated using Head Office AD via Cisco ACS, both located at the Head Office.
    There are other SSID's on the WLC which all work fine, but only employee SSID which uses AD authentication does not work. AD authenticaion is working fine because employee's in HO are successfully able to connect to the employee SSID at HO.
    The branch office is connected to the HO via a tunnel link. We noticed that if we restart both the ASA at either ends of the tunnel. The employee SSID starts working again but only temporarily for a day or so... what could be the issue? Can renaming the AP's cause issues? How can I fix this problem?
    Thanks in advance

    Thanks Elliott,
            I did the debug like you said and I am getting the following debug messages:
    *apfMsConnTask_0: Jun 20 08:18:14.580: Deleting the client immediatly since WLAN is changed
    and also
    *apfReceiveTask: Jun 20 05:25:11.857: 00:1f:3c:86:af:15 Orphan Packet from 192.168.52.34
    The logging on the WLC shows
    *apfReceiveTask: Jun 18 17:56:41.788: %MM-1-ANCHOR_UNAVAILABLE: mm_mobile.c:2155
    All export anchors are down. Cannot anchor the client.00:c0:a8:f3:cd:ae
    The DHCP pool for the employee users are configured on a guest WLC which sits behind an ASA

  • Unable to connect to LAN - Integrated 10/100BASE-T Ethernet LAN (RJ-45 connector)

    Unable to connect to LAN, downgraded laptop from Windows 8 to Windows 7 64-bit. Have tried using the HP device identifier, and installing all drivers under Network for the laptop on WIndows 7, though none of them showed as being for Local Area Network.I also tried following this thread: http://h30434.www3.hp.com/t5/Wireless-Internet-Home-Networking/Integrated-10-100BASE-T-Ethernet-LAN-RJ-45-connector/td-p/4040756Downloaded the suggested drivers there for the HP Envy 17t-j100I also tested downloading the drivers here for Windows 7: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=7&Level=5&Conn=4&DownTypeID=3&GetDown=false Neither worked, I am still only able to connect via Wi-Fi, but not via LAN with actual cable attached.In case necessary, hardware ID for the Realtek PCIe FE Family Controller:
    PCI\VEN_10EC&DEV_8136&SUBSYS_1854103C&REV_05PCI\VEN_10EC&DEV_8136&SUBSYS_1854103CPCI\VEN_10EC&DEV_8136&CC_020000PCI\VEN_10EC&DEV_8136&CC_0200

    Hi: You can use all of the W7 x64 drivers and software from the HP 2000t-2a00 on your model except the BIOS and firmware files. Make sure you install the Intel chipset installation utility first and reboot before trying to install the Realtek LAN driver. http://h22207.www2.hp.com/us-en/drivers/selfservice/hp-2000-2a00-notebook-pc-series/5259212/model/5275371

  • Cisco Wireless LAN Controller Always disconnect

    Dear All,
    Please help to assist my issue.I used Cisco Wireless LAN Controller model: 5508 with version 7.0.98.0 and I got issue with connection always disconnect ping always loss or some time client can't get DHCP from Controller. 
    - I configure as Internal DHCP Server with 1 SSID.
    http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html
    - DHCP least is not full and I also try to clear-lease all but still not work.

    1. Config dhcp proxy enable
    2. In case of internal Dhcp, try debug for clients
     using,
    debug client <MAC ADDRESS OF CLIENT>

  • 4404 wireless lan controller managment via wireless clients

    I am having an issue managing a 4404 wireless lan controller via wireless clients.
    I have checked the box "enable controller management to be accessible from wireless clients" under management. For some reason that does not seem to fix the problem (page cannot be displayed). I cannot ping the controller by IP but other devices on the same subnet respond. Everything else works fine.
    I CAN manage the controller when plugged in a wired connection.
    When I do a route print it is identical wireless or wired. The route simple points to my interface. If I modify the route on my computer to actually point to our gateway instead of the interface then everything works. But why should I have to do this only for my wireless connection and not my wired to manage this box?

    Thanks for the info. I narrowed the problem down to an ARP issue.
    In order for me to connect to the controller, I run a batch file that creates a static ARP entry on my laptop. I don't have to do this for any other device except the controller. Not sure what the underlying cause is, but that works as a workaround right now.

  • Wireless Lan Controller Issue

    Hi All,
    We have a Wireless Lan Controller 4402 with software version 4.0.155.5. On Friday we experience a problem where our clients wouldn't get redirected to the internal webpage for authentication. It would just come up with page not found. We know the page was working fine becasue we could manually type in the
    https://1.1.1.1/login.html and the
    page would come up and you could login successfully. The users who were already connected to the controller were not affected and continued to operate. We have 2 other WLC's at the same software revision and they were not affected so I don't think it has anything to to with software level. Its like the webserver in the wlc failed to work. We failed over the AP's to the 3rd WLC and rebooted WLC1. After the WLC1 restarted we failed one of the previous non-working AP's back to it and it works again.
    I know "now" there is debug commands to run at the time when the WLC wasn't working, but unfortunately I didn't know at the time. The WLC is running again fine and I was wondering if anybody has seen this issue before.
    Any ideas on a fix or reason would be greatly appreciated.
    Thanks,

    We are running WiSM 4.1.185.0 and we just had the similar problem with one controller. The other three controllers were fine when it happened. The exactly issue was the nslookup failed(timed out) from the client, so the web login page won't show when people lunch the browser. A reboot of the controller fixed the problem. We have been running Cisco LWAPP for more than a year (from 4.0.155.5 to 4.1.185.0) and it is the first time we see this problem. TAC is still investigating the cause.
    Zhenning

  • Wireless LAN Controller not broadcasting network to Access points

    Good Day Team,
    I am working with a 2100 series WLC controller and 1100 series access point.
    I noticed that the wireless lan controller is working. Also the access point is working.
    The issue is that there is no internet connection on the access point.
    What could be the error?
    Kindly advice

    Try do diagnose your problem following this steps:
    1) Connect to the wireless network
    2) Check your IP address with "ifconfig"
    3) Check if your gateway is set correctly with "route -n"
    4) Try to ping your gateway. Is it working?
    5) Try to ping an internet IP like google: "ping 74.125.234.115"
    6) Try to resolve names with "nslookup www.google.com" for example.
    7) Try to traceroute to an IP or name on internet. Check the result to see the last hop you reached.
    8) If you passed all those tests, try this: "telnet www.google.com 80"
    If everything works, but not the test #8, your problem could be related to some proxy configuration.

  • AIR-CAP3501I access point not joining the Cisco 2100 Wireless Lan controller.

    Hello All,
    I am installing a new LAP (AIR-CAP3501I ) through the wireless lan controller (AIR-WLC2112-K9) with software version 7.0. I have an external ADSL modem which will act as the DHCP server for the wireless clients and the LAP.
    Please find my network setup as below:
    The ISP ADSL modem , WLC and LAP are connected to a unmanaged POE switch. The LAP gets its power through the POE switch. When i connect the LAP and the WLC to the switch along with the ADSL modem, the LAPs are getting the ip address from the ADSL modem, however they are not joining the WLC for further process.
    ADSL Modem ip address: 192.168.1.254
    Management ip address on the LAP: 192.168.1.1 ( Assigned to port 1, untagged Vlan).
    Ap Manager ip address: 192.168.1.1 ( Assigned to the same port i.e port1, Untagged Vlan).
    The LAP is getting an IP address from the ADSL modem in the range of the DHCP scope.
    I will paste the logs very soon.
    Please let me know if i am doing anything wrong oe what will be the issue.
    Thanks in advance,
    Mohammed Ameen

    Hello All,
    Please find the logs for  "debug capwap event" from the WLC below:
    *spamReceiveTask: Sep 26 19:44:59.196: e8:04:62:0a:3f:10 Join Version: = 117465600
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join resp: CAPWAP Maximum Msg element len = 92
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join Response sent to 192.168.1.156:45510
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 CAPWAP State: Join
    *spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 capwap_ac_platform.c:1216 - Operation State 0 ===> 4
    *apfReceiveTask: Sep 26 19:44:59.198: e8:04:62:0a:3f:10 Register LWAPP event for AP e8:04:62:0a:3f:10 slot 0
    *spamReceiveTask: Sep 26 19:44:59.341: e8:04:62:0a:d1:20 DTLS connection not found, creating new connection for 192:168:1:158 (45644) 192:168:1:2 (5246)
    *spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 DTLS Session established server (192.168.1.2:5246), client (192.168.1.158:45644)
    *spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 Starting wait join timer for AP: 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.121: e8:04:62:0a:d1:20 Join Request from 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join Version: = 117465600
    *spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join resp: CAPWAP Maximum Msg element len = 92
    *spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 Join Response sent to 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 CAPWAP State: Join
    *spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 capwap_ac_platform.c:1216 - Operation State 0 ===> 4
    *apfReceiveTask: Sep 26 19:45:00.125: e8:04:62:0a:d1:20 Register LWAPP event for AP e8:04:62:0a:d1:20 slot 0
    *spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 Configuration Status from 192.168.1.158:45644
    *spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 CAPWAP State: Configure
    *spamReceiveTask: Sep 26 19:45:00.273: Invalid channel 1 spacified for the AP APf866.f2ab.24b6, slotId = 0
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP info for AP e8:04:62:0a:d1:20 -- static 0, 192.168.1.158/255.255.255.0, gtw 192.168.1.254
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP 192.168.1.158 ===> 192.168.1.158 for AP e8:04:62:0a:d1:20
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Setting MTU to 1485
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Finding DTLS connection to delete for AP (192:168:1:158/45644)
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Disconnecting DTLS Capwap-Ctrl session 0xa06d6a4 for AP (192:168:1:158/45644)
    *spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 CAPWAP State: Dtls tear down
    *spamReceiveTask: Sep 26 19:45:00.277: spamProcessGlobalPathMtuUpdate: Changing Global LRAD MTU to 576
    *spamReceiveTask: Sep 26 19:45:00.277: e8:04:62:0a:d1:20 DTLS connection closed event receivedserver (192:168:1:2/5246) client 192:168:1:158/45644).
    The Acess point joins the Controller for 2-3 seconds and then unjoins again. I am not sure what i am doing wrong here. The access points are getting the IPs from the ADSL modem through the switch, then it talks to the WLC, however it does not join the controller for further process.
    Note:
    The Managemnet interface and the AP manager interface are assigned to the same port 1 with unassigned Vlan as mention above.

Maybe you are looking for