1552 AP failing to join WLC

Hello All,
I am having difficulty joining a 1552 AP to the 5508 WLC. I am using the 3750 switch attached to the WAP as a DHCP server for the AP points.
The AP obtains a IP address from the DHCP server, however fails to join the WLC. i can telnet to the AP and ping the WLC and from the WLC i can ping the AP.
I am a little stumped on where to go next.

Is the port of the switch in trunk mode, which is the WLC connected to?
I used az internal DHCP of the WLC...
Notice: Take care about the setting of the region code, because it has to be compatible with the AP (you can find the nr. on the back of it, and you can see in its guide, which region code is compatible with that), but before you change it you have to turn the radio's off in WL settings...
Posted by WebUser Attila Valguth from Cisco Support Community App

Similar Messages

1131 LWAP not join WLC 4402

I am deploying WLC 4402 with LWAP 1131 but AP fail to join the WLC .The resone that I dont have DNS server.The error message in the AP is :
AP001d.451f.8582>
*Mar 1 00:00:38.005: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned D
HCP address 172.26.5.12, mask 255.255.255.0, hostname AP001d.451f.8582
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:00:49.371: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve
I tried to configure the Controller address in LAP but I fail ,The error when I tried to configure AP is below:
AP001d.451f.8582#lwapp ap controller ip address 172.26.5.10
ERROR!!! Command is disabled.
my question is :
is it possible to make LAP join WLC with out DNS,if yes how ?

Hi Yhab,
There are other ways besides DNS to help in the AP and WLC Discovery process. Have a look in this good doc;
Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC)
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml#topic2
For the Static entry problem;
If this AP was ever registered you can use this command from the LAP CLI to clear the LWAPP configuration on the LAP:
clear lwapp private-config
This allows you to use the AP LWAPP static configuration commands again.
Here is an example:
Enable (enter password)
AP1240#clear lwapp private-config
AP1240#lwapp ap hostname AP1240
AP1240#lwapp ap ip address 10.77.244.199 255.255.255.224
AP1240#lwapp ap ip default-gateway 10.77.244.220
AP1240#lwapp ap controller ip address 172.16.1.50
Note: You cannot use the clear lwapp private-config command when the LAP is registered with the controller.
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a00808e2d27.shtml#t2
Hope this helps!
Rob

Problem to join WLC (AP1131 && WISM)

Hello,
AP will not join WLC. Everytime, the AP try to join the WLC but...
CLI of AP :
May 18 08:02:51.194: status of voice_diag_test from WLC is false
May 18 08:02:51.194: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
May 18 08:02:51.195: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
May 18 08:02:51.196: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
May 18 08:02:51.201: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
May 18 08:02:51.227: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
May 18 08:03:01.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.2.243 peer_port: 5246
May 18 08:03:01.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
May 18 08:03:02.398: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.23.2.243 peer_port: 5246
May 18 08:03:02.400: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.2.243
May 18 08:03:02.400: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
May 18 08:03:07.399: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.2.243
May 18 08:03:07.400: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.23.2.243
May 18 08:03:07.400: %DTLS-5-PEER_DISCONNECT: Peer 172.23.2.243 has closed connection.
May 18 08:03:07.400: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.23.2.243:5246
May 18 08:03:07.459: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
May 18 08:03:07.459: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
May 18 08:03:07.525: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
May 18 08:03:07.525: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
May 18 08:03:07.526: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
May 18 08:03:07.556: status of voice_diag_test from WLC is false
May 18 08:03:18.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.2.243 peer_port: 5246
May 18 08:03:18.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
May 18 08:03:19.406: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.23.2.243 peer_port: 5246
May 18 08:03:19.408: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.2.243
May 18 08:03:19.408: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
May 18 08:03:24.406: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.2.243
May 18 08:03:24.408: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.23.2.243
May 18 08:03:24.408: %DTLS-5-PEER_DISCONNECT: Peer 172.23.2.243 has closed connection.
May 18 08:03:24.408: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.23.2.243:5246
May 18 08:03:24.467: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
May 18 08:03:24.467: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
May 18 08:03:24.533: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
May 18 08:03:24.533: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
If someone know how to resolve my problem ..
Thanks, Vincent A.

Hello,
The firmware of the controlers is : 7.0.116.0
The AP run the firmware c1130-rcvk9w8-tar.124-21a.JA2.tar and the model is AP1131.
results of 'dir' command :
AP001d.a1ee.1cbc#dir
Directory of flash:/
    2 -rwx       20380 May 18 2011 07:20:51 +00:00 event.log
185 drwx         128 May 17 2011 09:18:44 +00:00 c1130-rcvk9w8-mx
    4 -rwx        7192 May 18 2011 09:03:13 +00:00 private-multiple-fs
    5 -rwx         400 May 18 2011 07:26:15 +00:00 env_vars
    7 -rwx        1919 May 17 2011 09:19:13 +00:00 private-config
   10 drwx         320 May 18 2011 07:20:46 +00:00 c1130-k9w8-mx.124-23c.JA2
    6 -rwx           0 May 18 2011 07:18:08 +00:00 validate.txt
15740928 bytes total (8032256 bytes free)
AP001d.a1ee.1cbc#
On the controllers i can see that, but i don't understand why :
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 Msg Type = 3 Capwap state = 0
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 Join Request from 172.22.4.96:57804
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 Join request received from AP which is already present. Deleting previous connection
                        172.22.4.96:57804
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 Multiple Join Request: Join request received from AP which is already present. Deleting previous conne
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 Finding DTLS connection to delete for AP (172:22:4:96/57804)
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 Disconnecting DTLS Capwap-Ctrl session 0x136c2550 for AP (172:22:4:96/57804)
*spamReceiveTask: May 18 11:05:20.375: 00:1e:13:6f:47:f0 CAPWAP State: Dtls tear down
*spamReceiveTask: May 18 11:05:20.376: 00:1e:13:6f:47:f0 DTLS connection 0x136c2550 closed by controller
*spamReceiveTask: May 18 11:05:20.377: 00:1e:13:6f:47:f0 Deleting and removing AP 00:1e:13:6f:47:f0 from fast path
*spamReceiveTask: May 18 11:05:20.377: 00:1e:13:6f:47:f0 DTLS connection not found. Ignoring join request from 172.22.4.96:57804
*spamReceiveTask: May 18 11:05:20.377: 00:1e:13:6f:47:f0 State machine handler: Failed to process msg type = 3 state = 0 from 172.22.4.96:57804
*spamReceiveTask: May 18 11:05:20.377: 00:1e:13:6f:47:f0 Failed to parse CAPWAP packet from 172.22.4.96:57804
*spamReceiveTask: May 18 11:05:20.377: CAPWAP DTLS connection closed msg
*spamReceiveTask: May 18 11:05:20.377: 00:1e:13:6f:47:f0 DTLS connection closed event receivedserver (172:23:2:243/52
Thanks, Vincent A.

OEAP 600 cannot join WLC with auth-list enable

I've got a strange problem here. In the office, my OEAP 600 can join WLC if there is no MAC authentication. When i enable MAC authentication at WLC, AP will fail to register. However, I try it at home and it works with both MAC authentication enable or disable. I suspect it is because of firewall in my office, but there shouldn't have any different in discovery and joining procedure for AP with MAC authentication enable or disable. I'm confused here. Please help.

Justin,
Below is error summary from WLC:
Last Error Summary
Last AP Message Decryption Failure----
Last AP Connection Failure     ---------      Timed out while waiting for ECHO repsonse from the AP
Last Error Occurred                ---------      Lwapp join request rejected
Last Error Occurred Reason    ---------      RADIUS authorization is pending for the AP
The error reason is probaly because I haven't added AP MAC address to ACS. With the same AP, at home using ADSL link, i have no problem.
Thanks.

Node failed to join the cluster because it ould not send and receive failure detection network messages

One of my customers has a Windows Server 2008 R2 cluster for an Exchange 2010 Mailbox Database Availability Group. Lately, they've been having problems with one of their nodes (the one node that is on a different subnet in a different datacenter) where
their Exchange databases aren't replicating. While looking into this issue it seems that the problem is the Network Manager isn't started because the cluster service is failing. Since the issue seems to be with the cluster service, and not Exchange,
I'm asking here.
When the cluster service starts, it appears to start working, but within a few minutes the following is logged in the system event log.
FailoverClustering
1572
Critical
Cluster Virtual Adapter
Node 'nodename' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. ...
It seems that the problem is with the 169.254 address on the cluster virtual adapter. An entry in the cluster.log file says: Aborting connection because NetFT route to node nodename on virtual IP 169.254.1.44:~3343~ has failed to come up.
In my experience, you never have to mess with the cluster virtual adapter. I'm not sure what happened here, but I doubt it has been modified. I need the cluster to communicate with its other nodes on our routed 10. network. I've never experienced
this before and found little in my searches on the subject. Any idea how I can fix this?
Thanks,
Joe
Joseph M. Durnal MCM: Exchange 2010 MCITP: Enterprise Messaging Administrator, Exchange 2010 MCITP: Enterprise Messaging Administrator, MCITP: Enterprise Administrator

Hi,
I suspected an issue with communication on UDP port 3343. Please confirm the set rules for port 3343 on all the nodes in firewall and enabled all connections for all the profiles
in firewall on all the nodes are opened, or confirm the connectivity of all the node.
Use ipconfig /flushdns to update all the node DNS register, then confirm the DNS in your DNS server entry is correct.
The similar issue article:
Exchange 2010 DAG - NetworkManager has not yet been initialized
https://blogs.technet.com/b/dblanch/archive/2012/03/05/exchange-2010-dag-networkmanager-has-not-yet-been-initialized.aspx?Redirected=true
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

ACS express v5.0.1 fail to join AD

hi,
i try to integrate my ADE 1010 appliances running on ACS express v5.0.1.1 to my DC running on window 2008 server enterprise edition SP2.
as i fill in the info at domain configuration and test the connection, it's succeed. but once try to save and join it's failed to join the domain.
log extract from acsxp_adagent :
PMOACS AD-SCRIPTS: INFO AD script executed from IP: 10.169.2.100 script: /cgi/adjoindomain.pl/cgi/adjoindomain.pl args: DM=jpmosp.xxx.yy&UN=administrator&CN=OU%3DACS&PDC=jpmosp.xxx.yy&PW=******
PMOACS AD-SCRIPTS: INFO AD join container used: OU=ACS
PMOACS AD-SCRIPTS: INFO AD join Preferred Domain Server used: jpmosp.xxx.yy
PMOACS AD-SCRIPTS: INFO AD join container used: OU=ACS
PMOACS AD-SCRIPTS: INFO AD join Preferred Domain Server used: jpmosp.xxx.yy
PMOACS AD-SCRIPTS: INFO AD join command used: /opt/CSCOacsxp/adagent/bin/adjoin -u "administrator" -p "******" -z NULL --noconf "jpmosp.xxx.yy" -s "jpmosp.xxx.yy"
PMOACS AD-SCRIPTS: CRITICAL Unknown status returned from adjoin
PMOACS AD-SCRIPTS: WARN --- BEGIN FILE LOG FOR /opt/CSCOacsxp/temp/adjoindata.8870 ---
PMOACS AD-SCRIPTS: WARN Cannot resolve computer name "pmoacs" in DNS or /etc/hosts
PMOACS AD-SCRIPTS: WARN Please edit /etc/hosts or your DNS server to set your hostname correctly
PMOACS AD-SCRIPTS: WARN or use --name option to override this check.
what i did on my window 2008 server:
1. log in as the administrator, create a container name "acs", and inside of it create a computer name as "pmoacs"
2. appliance clock is tally with AD-DC server, no time skew problem.
what i did on my Cisco ADE 1010:
1. initial setup only.
thank you
N

Hi,
This is the relevant error message:
"WARN Cannot resolve computer name "pmoacs" in DNS or /etc/hosts"
Please make sure you have the acs hostname configured on the DNS server.
The ACS must be able to resolve its own hostname, otherwise this will fail.
HTH,
Tiago
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

Vlan mapping lost when fail to secondary WLC

Hello
I have two WLCs,The primary WLC mode 5508 ,running code is 7.4.100.60, The secondary WLC mode 4402,running code is 7.0.230.0.
When ap working on 5508 wlc,it use flexconnect mode, when ap working on 4402, it will h-reap mode
ap mode:1242、1142.
question:
When ap fail to secondary WLC(4402),some ap will lost their vlan mapping information.not all of ap. during fail over, ap will doanloading firmware.
is there any way to solve? thanks!

I understand. Two controllers, two different code levels. 4400 is locked in at 7.0 code and you need 7.4 for the 2600 ap.
In your orginal post you state when aps fail over from one controller to the other you lose vlans and aps code upgrade/down grade. This is not a support deisgn. You cant properly failover betwen different code versions.
If you want them to stop failing over and clients dont roam from aps on controler to 1 to aps on controller 2, simple remove the controllers from the shared mobility group and put the controllers in their own group.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

Failed to join cluster - Address already in use

Hi there,
 I'm trying to set up a cluster with WLS 7.0 on Linux (kernel 2.4.20). Apparently, the OS is configured correctly: the kernel is compiled with multicast support and multicast routes have been appropriately defined.
 The admin server starts correctly, and managed servers running on other OSs successfully join the cluster. However, when a I try to run a managed server on this linux, I get the following error:
 <Apr 29, 2003 12:27:52 AM CEST> <Error> <Cluster> <000116> <Failed to join cluster testcluster at address 237.0.0.1 due to : java.net.BindException: Address already in use
 java.net.BindException: Address already in use
 at java.net.PlainDatagramSocketImpl.bind(Native Method)
 at java.net.MulticastSocket.create(MulticastSocket.java:123)
 at java.net.DatagramSocket.<init>(DatagramSocket.java:135)
 at java.net.DatagramSocket.<init>(DatagramSocket.java:107)
 at java.net.MulticastSocket.<init>(MulticastSocket.java:99)
 at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:87)
 at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:110)
 at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:140)
 at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:51)
 at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:773)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
 at weblogic.Server.main(Server.java:32)
 >
 I have tried to change the multicast address but the error persists.
 Am I missing something? Any help would be muchly appreciated.


have you checked to see what is running before you start your oracle app server on your ports? you can use netstat for one

Server failed to join cluster after migration.

Hi
 
 After migration of weblogic server (wls1) from machine A (fwls1) to B (fwls2), wls1 logged the following: 
 Failed to join cluster wlscluster at address 239.192.2.1 due to: java.net.SocketException: Cannot assign
 requested address.
 java.net.SocketException: Cannot assign requested address. 
 Wls2 is part of wlscluster and it is working, so I think that multicast address must be fine. Does anyone know what can be reason for that exception ?
 
 
 Details:
 <ol>
 <li> Weblogic Server 9.2
 <li> wls1 is running at the fwls1 machine; wls2 is running at the fwls2 machine; wls1 and wls2 belong to cluster wlscluster
 <li> migrate wls1 to machine fwls2
 <li> in fwls2:/opt/.../wls1/logs/server.log I got an exception
 <li> fwls1 automatically stands up in fwls1
 </ol>
 Any help appreciated
 
 regards
 Lukas 
 WLS 9.2

hi
 the cluster adress includes ur manged servers listing adress and port number example
 10.192.11.12:6399 is managed1
 10.192.11.12:6400 is managed2
 then these servers under cluster the cluster adress is
 10.192.11.12:6399,10.192.11.12:6400
 multicast adress start from 237.0.0.0 if this used by some another user change this adress

Lync on Mac 10.8 fails to join meetings

Hello all,
I'm facing an issue since upgrading from OS X 10.6 to 10.8 that the Lync client 14.0.2 frequently fails to join meetings. If I retry enough times, usually I'm able to finally join. I rely on Lync meetings multiple times every day so this is a big issue for
me. Here's the error message I get:
"Unable to connect. Try connecting to the online meeting by using the web browser that is currently open."
Any ideas?
Thank you,
Evan

Thanks Rusty. It bothers me that this problem has existed for so long now.
If you all are not aware there is a fully functioning "workaround." Using lync, call into the meeting as if you were calling from into a regular concall, then put in the meeting pin. As soon as it realizes you are on lync the
meeting will be setup and it works fully, but it is really annoying to have to do each time.
I did install 14.0.4 as well today, no immediate change in behavior for me. Tried changing to external only manual sip/tls and it seems to be working in terms of creating meetings, but only if no others have joined at the time I create it. Joining
existing meetings does not work, like before you connect to the meeting, but the phone shows as a * (unconnected or issue I believe) and sharing sessions will not reliably start. After a minute, lync will show a random person from the meeting as calling
you. Answering does not join you to the conference.
So Microsoft still has some work to do to resolve this issue.
As for the rest with the keychain issues. Yep, the assigned one is expired from the outset. I went to a 10.7 system and checked, it was also set as expired there, so I'm not sure it matters but who knows. I've also tried allowing all certs
etc many times, but behavior was unreliable at best. The workaround above is the only thing that always works.

H-REAP LWAPs losing VLAN mapping when fail to secondary WLC's

Hello,
I have three 5508 WLCs, running code 7.0.98.0 supporting 100+ LWAPs in H-REAP mode. The LWAPs are servicing 2-3 WLANs each. Some are using central authentication and local switching, some are configured for central authentication and central switching. When the LWAPs fail from one WLC to another WLC, the LWAP's lose all of their VLAN mappings and pick up the VLAN of the management interface on the new WLC.
All WLANs are configured to use the management interface on the WLC and the VLAN mappings are configured per LWAP on the H-REAP properties tab. The WLAN ID numbers and all the WLAN settings are the same across all 3 WLC's. I have created AP groups on all 3 WLC's and the AP group config matches across the 3 WLCs.
I can get the LWAPs to keep their VLAN mapping by creating an interface on the WLC with the VLAN ID of the locally switched/remote site VLAN and then setting the interface for the WLAN to the new interface. However, then the WLAN doesn't work, because the centrally located WLC doesn't have the remote site VLAN. It also seems to keep the VLAN mapping if I create the locally switched/remote site VLAN interface on the WLC , and point the WLAN to the management interface. This shouldn't be a necessary step though... In H-REAP with local switching, the LWAPs aren't using the interface on the WLC.
I found a note in the 7.0 WLC config guide that explains why the VLANs are picking up the management interface VLAN, but that same note says the VLAN mappings can be changed per LWAP/WLAN!
From config guide:
For hybrid-REAP access points, the interface mapping at the controller for WLANs that is configured for H-REAP Local Switching is inherited at the access point as the default VLAN tagging. This mapping can be easily changed per SSID, per hybrid-REAP access point
Anyone using H-REAP and been able to get the LWAPs to keep the VLAN mapping when failing from one WLC to another?
Thanks!

Shawn,
I went back and reviewed everything and everything was duplicated , Except... WLAN_ID. The Wlan ID tags were different. I created a test and failled my two test AP's and they both came up on the backup controller with the proper vlan ID. now I know. When it was working for everyone else I was begining to wonder if I found a new bug or it was my config. This is one I wont forget ..
Thank you

Node fails to join the cluster

We are observing a problem where a node, after getting restarted, fails to join the cluster.
We run two coherence clusters across three boxes. Each box runs 8 java processes, 4 processes of one cluster, another 4 process
of the other cluster. They all run as windows NT services. Sometimes, some node goes down and gets restarted. But then it fails to join the cluster with following exception :
"com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=8, Name=DistributedFIIndicativeCacheWithPublishingCacheStore, Type=DistributedCache"
Has anyone experienced and addressed such a problem? If required, I can provide exact details of the cluster setup.
-Bharat

Hi Bharat,
This may be caused by a stuck or slow DistributedService thread on one of your nodes. Please log into http://support.oracle.com and take a look at [Note 845363.1|https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=845363.1] for more details. Additionally, consider upgrading to Coherence 3.5 as it includes the [Service Guardian for deadlock detection/resolution|http://blackbeanbag.net/wp/2009/07/20/coherence-3-5-service-guardian-deadlock-detection/].
Thanks,
Patrick

MDT : Failed to join domain

Hello,
I am receiving the below error bdd.log and after that zero touch installation is failing.
Error in the logs : “Failed to join domain. The account may not have permission The specified network name is no longer available. (Error: 80070040; Source: Windows)”
Please let me know how to solve it
Regards,
Boopathi S

Hi Boopathi,
As per the description, I understand that it's an issue about Microsoft Deployment Toolkit.
The error message above indicates that the network resource that you specified was either temporarily taken offline or is no longer available. It is possible that:
The share at the server might have been temporarily deleted;
The server that shared the resource might have been turned off;
The permissions might have been changed.
You might want to check above aspects. Also, please note that this is the forum to discuss questions and feedback for
Microsoft Office client. Since your query is directly related to
Microsoft Deployment Toolkit, I would suggest you to post in the forum of
Solution Accelerators>Microsoft Deployment Toolkit, where you can get more experienced responses:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Why LAP1131AG and LAP11412 cannot to join WLC 2504?

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

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected]
cisco AIR-LAP1142N-A-K9 (PowerPC405ex) processor (revision A0) with 90102K/40960K bytes of memory.
Processor board ID FGL1439S15W
PowerPC405ex CPU at 586MHz, revision number 0x147E
Last reset from reload
LWAPP image version 7.6.130.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: C8:4C:75:79:EB:E9
Part Number : 73-12836-03
PCA Assembly Number : 800-33767-03
PCA Revision Number : A0
PCB Serial Number : FOC14234D8Z
Top Assembly Part Number : 800-33775-02
Top Assembly Serial Number : FGL1439S15W
Top Revision Number : A0
Product/Model Number : AIR-LAP1142N-A-K9
cisco AIR-LAP1131AG-A-K9 (PowerPCElvis) processor (revision A0) with 27638K/5120K bytes of memory.
Processor board ID FTX1026T46E
PowerPCElvis CPU at 262Mhz, revision number 0x0950
Last reset from power-on
LWAPP image version 7.6.130.0
1 FastEthernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:18:18:FC:FD:58
Part Number : 73-8962-09
PCA Assembly Number : 800-24818-08
PCA Revision Number : A0
PCB Serial Number : FOC102513DE
Top Assembly Part Number : 800-25544-06
Top Assembly Serial Number : FTX1026T46E
Top Revision Number : A0
Product/Model Number : AIR-LAP1131AG-A-K9
Configuration register is 0xF

WLC 5760 - AP2600i failed to join ap-group after reboot

Hi,
We're deploying a couple of 2600i with an WLC 5760.
We've configured an AP group, named it "factory", and then issued the command ap name AP<ip mac address> ap-groupname factory for both APs. After the restart, both AP were on the AP-Group factory.
The problem is that is we reboot or power off the APs, one will join automatically the AP-Group factory and the other goes to default-group and requires the ap name APAPf872.ead7.31da ap-groupname factory to join the AP group factory again.
Any suggestion? Is it possible to forced the ap-group configuration directly on the cli of the AP?
WLC1#sh ap groups
Site Name: default-group
Site Description:
WLAN ID WLAN Name Interface
AP Name Slots AP Model Ethernet MAC Location Port Country Priority GroupName
Site Name: factory
Site Description:
WLAN ID WLAN Name Interface Radio
AP Name Slots AP Model Ethernet MAC Location Port Country Priority
APf872.eaa6.fc69 2 2602I f872.eaa6.fc69 default location Te1/0/1 PT 1
APf872.ead7.31da 2 2602I f872.ead7.31da default location Te1/0/1 PT 1
debug ap group
(AP joining the apgoup factory)
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 1 for ap APf872.eaa6.fc69 apgroup factory
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 2 for ap APf872.eaa6.fc69 apgroup factory
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 3 for ap APf872.eaa6.fc69 apgroup factory
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 4 for ap APf872.eaa6.fc69 apgroup factory
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 5 for ap APf872.eaa6.fc69 apgroup factory
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 6 for ap APf872.eaa6.fc69 apgroup factory
Sep 17 18:24:24.420: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 7 for ap APf872.eaa6.fc69 apgroup factory
(AP joining the default-group)
Sep 17 18:30:36.078: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 0 for apVapId 1 for ap APf872.ead7.31da apgroup default-group
Sep 17 18:30:36.078: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 0 for apVapId 2 for ap APf872.ead7.31da apgroup default-group
Sep 17 18:30:36.078: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 0 for apVapId 3 for ap APf872.ead7.31da apgroup default-group
Sep 17 18:30:36.078: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 7 for apVapId 4 for ap APf872.ead7.31da apgroup default-group
Sep 17 18:30:36.078: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 0 for apVapId 5 for ap APf872.ead7.31da apgroup default-group
Sep 17 18:30:36.078: apfRadioPolicySiteTableEntryGet: 1 wcm: found radio Policy 0 for apVapId 6 for ap APf872.ead7.31da apgroup default-group
Kind regards,
Vasco Costa

We've used a another group of 2600i APs and it seems that this problem only occous with AP "APf872.ead7.31da" so this is not a WLC problem.
closing case

1552 AP failing to join WLC

Similar Messages

Maybe you are looking for