LAP don't registered

Question

Hi, I have a wireleess lan controllers in the main branch and I have a lighweigh access point in a remote branch, the local aps joins in the wireless lan controllers (4400 serie), but the remote aps no enjoys. From the CLI of LAP I reach the wireless lan controllers but this ap no enjoy in the wireless lan controllers. Which is the problem?
LWAPP Static IP Configuration
IP Address 193.9.209.199
IP netmask 255.255.255.0
Default Gateway 193.9.209.1
The address of the wireless lan controllers is 193.9.212.100. Ping from the remote branch:
ap#ping 193.9.212.100
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 193.9.212.100, timeout is 2 seconds:
Success rate is 100chs percent (5/5), round-trip min/avg/max = 4/7/17 ms
These are the messagesof the remote access points:
*Mar 1 00:00:28.360: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:28.373: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:28.410: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:28.412: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down
*Mar 1 00:00:28.413: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:38.832: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:38.833: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:00:38.833: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Mar 1 00:00:39.833: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:39.833: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:43.833: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response
*Mar 1 00:00:43.833: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar 1 00:00:43.875: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
*Mar 1 00:00:43.875: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
The Arquitecture of the network is composed by extreme networks devices and nortel devices. This influences in the integration of the wireless lan controllers in the network. The Cisco devices are the wireless lan controllers 4402 and lighweight access point serie 1131.

Answer 1

Hi Ricardo,
As you mentioned the ip address anc controller information was entered into AP via GUI which means to me that your AP was first connected to the controller on local site and once configured you sent the AP to remote site? Correct me if I am wrong.
Also which section of GUI you used to enter controller ip address? I believe you must have gone to Ap detail page and under primary controller you might have defined the ip address?
If yes then we need not define controller ip address under primary controller but we have to define the controller name.
Even if your AP is having a static ip address but does not know the controller ip address it will still be able to ping from AP to controller but because AP does not which controller to join is the reason it is not able to join your controller and is the reason in debugs you see NO MORE AP MANAGER found and not able to get the join response.
I will recommend you to put this AP back to local site and configure your controller system name under primary controller name when you AP joins controller on local site.
HTH
Ankur