AP1852E Cisco Mobility Express Controller Issues

[bluecorvette86]

I have an AP1852E that I have started setting up.  It is connected to a local trunk port on my switch, with the management VLAN configured as the native VLAN.  When it first started up, the Cisco Mobility Express Provisioning ran just fine, I entered all of the revelvant information, and completed the setup.  Upon reboot, the controller never successfully boots back up.  I just keep seeing the following message form the console:

"waiting for uplink IP address and reachable default gateway"

I can see that the AP is pulling a DHCP address just fine, just like it did upon first setup.  I have tested this using an access port on the management VLAN and the controller will start up just fine, but that does me little good.  Any ideas what I need to do to get teh controller to boot up properly while connected to a trunk port?  Thanks!

[trey.s.grunDD]

So how to make sense of the deployment guide?  It contains information that primarily contradicts this statement, and includes a diagram clearly showing a traditional WLC.

http://www.cisco.com/c/en/us/td/docs/wireless/access_point/1850/hardware/guide/ap1850hwguide.pdf  (See p.20 and also p.12)

I do not understand what "Step 3" means by stating "Reconfigure the WLC so it is not the master", it's not clear whether this is a reference to the embedded WLC/ME capabilities or the WLC you just spent all of Step 2 associating the AP to.  This is VERY confusing.

I am experiencing the same issue with 5 new 1852i AP's "waiting for uplink IP address and reachable default gateway".  In addition to this thread, I found several bugs in the google search results.

[bluecorvette86]

I figured it out.  I had a misconfiguration in DHCP which was causing the issue.  Thanks for the help!

[timohara]

What was your misconfiguration?  I seem to be having the same issue, but I have a very simple DHCP config, basically sending a client a DHCP Address, DNS Server and Default Gateway...

[bluecorvette86]

I fat fingered my Default Gateway in DHCP.  If that isn't your issue, I would try setting a static IP on a client on the same VLAN and make sure they can route through the default gateway properly.

[timohara]

Thanks, but that's not my issue...  My DGW is correct in the DHCP scope, and other clients seem to be working just fine.  Like you it came up on the trunk port just fine when it came up to provision the AP, but now after reboot it won't pull an AP.  And it apparently isn't far enough along in the boot process to statically assign an IP/DGW either.... Ugh.

[Scott Fella]

Post the output from the console. That will tell us what is going on.

-Scott

[divjakv]

Just simply plug AP to network where DHCP service is installed and you will get an IP Address.

Vojko

[leofers78]

I have an 1850e AP with Mobility Express installed with an vWLC and the AP with the same issue, the VLAN where the AP was connected didn't deliver IP Addresses through DHCP, it seem that if the AP cant get a valid IP address the vWLC wont come UP.

I just configure my core Switch and DHCP server to deliver IP Address in the Vlan of the AP and now and the vWLC are working.