AP doesnt find DHCP

Hi Steve.... well, i had everything all set and iu just had to fool with it. i had one ap set with a static ip and working fine, i had to move it b/c it wasnt reaching the offices it needed. once i plugged it in, i got the green/red/amber flashing lights, so it wasnt finding the wlc. i took it and connected to the console after several resets to default. problem is that i cant get in to global mode and none of my commands are being retained. can get in to exec mode, but when i type config t or configure it says invaklid command. i tried giving it a static ip and the controller name, but i dont know how to save config changes b/c there is no wr or copy run etc.... any idea how to best get this bad boy back up and connected? how do i get it back to factory defaults so i can just connect it to the network and config via gui like before?

getting this also...

Mar 1 00:15:56.991: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

Find more posts tagged with

Comments

hey tdean! The joys of working in IT breaking stuff yourself

Is it plugged into a different switchport now? The switchport configuration would be next place to look. The AP must have had a DHCP address, and it doesn't seem to be hitting the DHCP server. (Or it could be a DHCP Server issue, although that would present itself many other ways.)

Maybe plug in your laptop to the same wall port. It may ease the troubleshooting process.

yeah, different switchport.... i've tried a few. i dont understand why it would matter, everything else is up. i wonder how many other things i'll break trying to fix this!

is there a way to join the ap manually through the wlc?

tdean can you please tell us some more info. IP range of the DHCP server + WLC IP etc..
Did you put in in a different VLAN ? Different subnet range?
There are a lot of things that you have to check. As Steve said, put your PC and see if you get an IP address.

yeah, the ports work fine with my laptop. the other AP is working fine. we're using 172.22.1.0/24, no vlans. i cant even get to global mode when connected via console port. i get this...

AP588d.0909.37e5#configure terminal
............................^
% Invalid input detected at '^' marker.

what am i doing wrong?

So you plug the AP into a different port, it does not receive a DHCP address.
You plug your laptop into the same port and you do receive a DHCP address.

No VLANs... So when the LWAP broadcasts it should hit the DHCP, that seems to be the case with your laptop, so what makes this LWAP any different. Was anything special setup in the DHCP server for this LWAP?

If we get the LWAP an IP address it should fix the problem out-right. Since it's not receiving an IP address their is only some many things it could be. Are you able to check the DHCP server to see if sees anything from the LWAP, or maybe do a SPAN session on the switch to capture the data to see what's really flowing.

I'm almost tempted to say switch the non-working AP with the working AP, but without knowing everything I'd hate to ask to bring down a working AP.

correct, laptop yes, ap no.

i am connected via console... i dont understand why i cant manually assign an ip.

this ap was working fine. all i did was physically move it from one location to another on the same floor. at that point, it had a static ip in both the WLC and on our dhcp server. i plugged it in and it flashed the green/red/amber lights which i guess means it cant find the wlc. thats when i took it up to my office and tried connecting via console to manually assign an ip or wipe it out and start over. i removed it from the wlc and our dhcp server. now, its flashing the green light and its unable to contact our dhcp server.

worst case i can go to our other location, take the power injector from the other AP and connect it to my laptop via the 10.0.0.1 and configure it that way.

Well, i cant even get into this thing with a web browser. i have it connected directly, i gave myself an ip of 10.0.0.2.... fired up the browser to 10.0.0.1... nuthin. this is extremely frustrating.

Is it still in autonomous mode or LWAP?

SteveO86 wrote: »

Is it still in autonomous mode or LWAP?

hmmm....not sure, im guessing lwap.... maybe thats why i cant configure it via console? how do i tell? and how do i change it? last thing i did was move it from one wall jack to another and all this started. it was working fine.

If you still see CAPWAP messages in console then it's still lightweight.

The AP still doesn't get a DHCP address in a different location?

What console messages do you see while the AP is booting?

SteveO86 wrote: »

If you still see CAPWAP messages in console then it's still lightweight.

The AP still doesn't get a DHCP address in a different location?

What console messages do you see while the AP is booting?

correct.... still getting this:

%CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

i wish i could reset to factory defaults or something, or manually set it to autonomous.

This has been quite deflating, i guess wireless isnt my thing.

It's still in LWAPP mode, with a no IP address.

(Any other console messages look out of place?)

I wouldn't let this get you down (especially on a Friday), and I wouldn't count yourself out of wireless. (after all we are still on the wire here the real fun in Wireless comes when you have to trouble shoot the WLAN

)

I found this for reverting LWAP back to Autonomous not sure if it's still relevant but might be worth a look at. (Since it's back from '05)
Release Notes for Cisco Aironet 1130AG, 1200, 1230AG, and 1240AG Series Access Points for Cisco IOS Release 12.3(7)JX - Cisco Systems

tdean wrote: »

correct.... still getting this:

%CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

i wish i could reset to factory defaults or something, or manually set it to autonomous.

This has been quite deflating, i guess wireless isnt my thing.

There's a reset button near the console port somewhere that you can hold in at boot up to reset to factory defaults.

Hey guys, thanks for helping.

Steve, correct, its still in lwap mode, no ip. the only other message i get it that its assigning itself 10.0.0.1. then its the message i posted, over and over and over......i will try some things from that link.

Z,

I tried a few things, like holding the mode button while i plug the pwr in and the light turns blue, then to green.... i also held it in till it turned red. same result. Is there something else i can try?

Still cant get this thing to hold an IP. Any ideas on how to reset to defaults? Is the problem that it needs poe via the network that the wlc is on, therefore defaulting to lwap mode?

heres the log....

*Mar 1 00:00:06.904: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self t
est passed
*Mar 1 00:00:06.915: *** CRASH_LOG = YES
Security Core found.
Base Ethernet MAC address: 58:8D:09:09:37:E5
*Mar 1 00:00:08.212: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self
test passed on interface Dot11Radio 0
*Mar 1 00:00:08.718: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self
test passed on interface Dot11Radio 1
*Mar 1 00:00:08.761: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log
(contains, 844 messages)
*Mar 1 00:00:09.820: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state
to up
*Mar 1 00:00:10.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEth
ernet0, changed state to up
*Mar 1 00:00:10.944: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1140 Software (C1140-K9W8-M), Version 12.4(21a)JHB1, RELEAS
E SOFTWARE (fc1)
Technical Support: Support and Documentation - Cisco Systems
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Wed 11-Aug-10 15:45 by prod_rel_team
*Mar 1 00:00:10.944: %SNMP-5-COLDSTART: SNMP agent on host AP588d.0909.37e5 is
undergoing a cold start
*Mar 1 00:15:18.042: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:15:18.232: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:15:18.232: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:15:18.232: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:15:18.375: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r
eset
*Mar 1 00:15:18.375: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
eset
*Mar 1 00:15:19.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to down
*Mar 1 00:15:19.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
1, changed state to down
*Mar 1 00:15:37.753: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:15:46.918: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!
*Mar 1 00:15:47.918: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.
255 started - CLI initiated
*Mar 1 00:15:56.919: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!
*Mar 1 00:16:06.918: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!
*Mar 1 00:16:16.918: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!

Just tried plugging direct into the WLC poe ports and resetting, and still no luck.

Well the device is receiving is power because it's trying to boot.

How are you providing power to the device a PoE Switch or a Power Injector?

Are you able to statically put one?

Cisco Aironet 1240AG Series Access Point Hardware Installation Guide, OL-8371-05 - Troubleshooting 1240AG Series Lightweight Access Points [Cisco Aironet 1240 AG Series] - Cisco Systems

Configuring Controller Information

To manually configure controller information on a new (out-of -the-box) access point using the access point CLI interface, you can use these EXEC mode CLI commands:

AP# lwapp ap ip address <IP address> <subnet mask>
AP# lwapp ip default-gateway IP-address
AP# lwapp controller ip address IP-address
AP# lwapp ap hostname name
Where name is the access point name on the controller.

I tried POE via HP switch, WLC and also Pwr Injector. I havent been able to statically apply one, thats part of the problem. I have tried the config posted, but couldnt get into global mode b/c the command was unrecognized. I will try again in a minute and let you know.

I dont get it..... am i fat fingering something or just not reading this properly? This is driving me crazy!

All possible debugging has been turned off
AP588d.0909.37e5#lwapp ap ip address 172.22.1.227 255.255.255.0
You should configure Domain and Name Server from controller CLI/GUI.
AP588d.0909.37e5#lwapp ip default-gateway 172.22.1.240
^
% Invalid input detected at '^' marker.
AP588d.0909.37e5#lwapp ip def
AP588d.0909.37e5#lwapp ip default-g
AP588d.0909.37e5#lwapp ip default-gate
AP588d.0909.37e5#lwapp ip default-gateway ?
% Unrecognized command
AP588d.0909.37e5#lwapp ip default-gateway
^
% Invalid input detected at '^' marker.
AP588d.0909.37e5#lwapp ip ?
% Unrecognized command
AP588d.0909.37e5#lwapp ?
ap lwapp/capwap ap commands
AP588d.0909.37e5#lwapp a
*Mar 1 00:20:26.779: %CAPWAP-5-STATIC_TO_DHCP_IP: Could not discover WLC using
static IP. Forcing AP to use DHCP.

should i be going down this route instead of the lwapp commands?

AP588d.0909.37e5#capwap ap ip address 172.22.1.227 255.255.255.0
You should configure Domain and Name Server from controller CLI/GUI.
AP588d.0909.37e5#capwap ap ip def
AP588d.0909.37e5#capwap ap ip default-gateway 172.22.1.240
AP588d.0909.37e5#cap
AP588d.0909.37e5#capwap ap ?
controller lwapp/capwap primary controller
dot1x Configure the dot1x username and password
hostname Configure ap hostname
ip lwapp/capwap ap ip command
log-server Configure the syslog server where all LWAPP errors will be
logged
primary-base Primary Controller
primed-timer primed-timer enable/disable
secondary-base Secondary Controller
tertiary-base Tertiary Controller
AP588d.0909.37e5#capwap ap con
AP588d.0909.37e5#capwap ap controller ?
ip lwapp/capwap primary controller ip
AP588d.0909.37e5#capwap ap controller ip ?
address Configure primary Controller IP address
AP588d.0909.37e5#capwap ap controller ip address ?
A.B.C.D Controller IP address
AP588d.0909.37e5#capwap ap controller ip address 172.22.1.222
AP588d.0909.37e5#

Yes CAPWAP instead of LWAPP (good catch)

The reason it wasn't working in your earlier with LWAPP is you did have the ap keyword after lwapp

AP588d.0909.37e5#lwapp ip default-gateway 172.22.1.240
                       ^

SteveO86 wrote: »
Yes CAPWAP instead of LWAPP (good catch)

The reason it wasn't working in your earlier with LWAPP is you did have the ap keyword after lwapp
AP588d.0909.37e5#lwapp ip default-gateway 172.22.1.240
                       ^

yeah, i caught that "ap" thing.... OK, now i can assign the ip via capwap, but i cant "save" it. also, it still isnt showing up in the wlc. this is fun, huh Steve?

also, how do i reslove this?
You should configure Domain and Name Server from controller CLI/GUI.

Did you put in the controller address information?

AP# lwapp controller ip address IP-address

With an IP in the LWAP I would start pinging and see how far you can get. (trying to ping the WLC management IP, Default Gateway, neighboring switch)

SteveO86 wrote: »
Did you put in the controller address information?
AP# lwapp controller ip address IP-address
With an IP in the LWAP I would start pinging and see how far you can get. (trying to ping the WLC management IP, Default Gateway, neighboring switch)

yeah, i put that in. when i exit exec mode, the changes are lost though. theres no save. i tried wr, copy run etc etc...

How far can you ping with exiting exec mode.

I loaded up a spare LWAP changes the IP reloaded the AP and it kept the IP I put in.

Next thing would be to try and ping the LWAP from the WLC.

SteveO86 wrote: »

How far can you ping with exiting exec mode.

I loaded up a spare LWAP changes the IP reloaded the AP and it kept the IP I put in.

Next thing would be to try and ping the LWAP from the WLC.

cant ping anything from the ap and cant ping the ap from the wlc.

AP588d.0909.37e5#capwap ap ip address 172.22.1.227 255.255.255.0
You should configure Domain and Name Server from controller CLI/GUI.
AP588d.0909.37e5#ping 172.22.1.227
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.22.1.227, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
AP588d.0909.37e5#ping 172.22.1.222
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.22.1.222, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
AP588d.0909.37e5#

something is wrong with this thing.... i cant even assign a hostname?

AP588d.0909.37e5#capwap ap ?
controller lwapp/capwap primary controller
dot1x Configure the dot1x username and password
hostname Configure ap hostname
ip lwapp/capwap ap ip command
log-server Configure the syslog server where all LWAPP errors will be
logged
primary-base Primary Controller
primed-timer primed-timer enable/disable
secondary-base Secondary Controller
tertiary-base Tertiary Controller
AP588d.0909.37e5#capwap ap ho
AP588d.0909.37e5#capwap ap hostname ?
WORD AP name
AP588d.0909.37e5#capwap ap hostname AP1
ERROR!!! Command is disabled.
AP588d.0909.37e5#

I assign an IP, can ping it, then i assign controller and then cant ping either.

AP588d.0909.37e5#capwap ap ip address 172.22.1.227 255.255.255.0
You should configure Domain and Name Server from controller CLI/GUI.
AP588d.0909.37e5#dom
AP588d.0909.37e5#domain ?
% Unrecognized command
AP588d.0909.37e5#ping ?
WORD Ping destination address or hostname
ip IP echo
tag Tag encapsulated IP echo
<cr>
AP588d.0909.37e5#ping ip 172.22.1.227
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.22.1.227, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
AP588d.0909.37e5#ping ip 172.22.1.15
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.22.1.15, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
AP588d.0909.37e5#cap
AP588d.0909.37e5#capwap ap
AP588d.0909.37e5#capwap ap ?
controller lwapp/capwap primary controller
dot1x Configure the dot1x username and password
hostname Configure ap hostname
ip lwapp/capwap ap ip command
log-server Configure the syslog server where all LWAPP errors will be
logged
primary-base Primary Controller
primed-timer primed-timer enable/disable
secondary-base Secondary Controller
tertiary-base Tertiary Controller
AP588d.0909.37e5#capwap ap prim
AP588d.0909.37e5#capwap ap prima
AP588d.0909.37e5#capwap ap primary-base ?
WORD Controller Name
AP588d.0909.37e5#capwap ap primary-base hyannis_wlc
AP588d.0909.37e5#capwap ap controller ip add
AP588d.0909.37e5#capwap ap controller ip address ?
A.B.C.D Controller IP address
AP588d.0909.37e5#capwap ap controller ip address 172.22.1.222
AP588d.0909.37e5#ping ?
WORD Ping destination address or hostname
ip IP echo
tag Tag encapsulated IP echo
<cr>
AP588d.0909.37e5#ping
*Mar 1 00:28:45.948: %CAPWAP-5-STATIC_TO_DHCP_IP: Could not discover WLC using
static IP. Forcing AP to use DHCP.
Protocol [ip]: ?
% Unknown protocol - "?", type "ping ?" for help
AP588d.0909.37e5#ping ?
WORD Ping destination address or hostname
ip IP echo
tag Tag encapsulated IP echo
<cr>
AP588d.0909.37e5#ping hyannis_wlc
% Unrecognized host or address, or protocol not running.
AP588d.0909.37e5#ping 172.22.1.222
% Unrecognized host or address, or protocol not running.
AP588d.0909.37e5#ping 172.22.1.227
% Unrecognized host or address, or protocol not running.

I'm slightly curious as to why you can not ping the neighboring switch or default gateway from the LWAP.

This might sound stupid but have we tried different cables? Were talking about getting a LWAP a DHCP address, I don't think it should be this complicated.

Does a sh run or sh logg display anything abnormal?

SteveO86 wrote: »

I'm slightly curious as to why you can not ping the neighboring switch or default gateway from the LWAP.

This might sound stupid but have we tried different cables? Were talking about getting a LWAP a DHCP address, I don't think it should be this complicated.

Does a sh run or sh logg display anything abnormal?

i will display both in a seperate reply. i have tried many different cables and many different ports. i also connected directly to the WLC. Heres whats driving me nuts now. I assign an IP, can ping... Then suddenly cant b/c the AP goes looking for a dhcp, and then the damn thing reboots!!.

AP588d.0909.37e5#capwap ap ip address 172.22.1.227 255.255.255.0
You should configure Domain and Name Server from controller CLI/GUI.
AP588d.0909.37e5#ping 172.22.1.227
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.22.1.227, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
AP588d.0909.37e5#ping 172.22.1.227
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.22.1.227, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
AP588d.0909.37e5#
*Mar 1 00:33:44.959: %CAPWAP-5-STATIC_TO_DHCP_IP: Could not discover WLC using
static IP. Forcing AP to use DHCP.
AP588d.0909.37e5#ping 172.22.1.227
% Unrecognized host or address, or protocol not running.

Quick Links