Motorola AP300 not picking up IP Address on DHCP
We have recently purchased a Motorola WS5100 switch and AP300 access points. I need to deploy the access points via a Layer 3 Network. Access points on the Layer 2 network pick up with no problem, however Access Points which are on a different network are not picking up a IP Address via DHCP. The access points are plugged into a Cisco 2960 switch, workstations and clients plugged into the same switch are picking up IP addresses from DHCP with no problem. The switch is on a different network and is connected via a 3750 switch which then routes back to a central core. I have configured the DHCP with option 189 which is supposed to forward the AP's to the wireless switch, but im convinced that the traffic is not getting as far as the DHCP server. Does anyone have any advice at all on this. I have been working on this problem for what seems like forever with no luck. Thanks in advance
ASKER
Both switches have ip helper addresses for the Vlan the access points are on. They are the same Ip address of 10.103.32.44
Hello,
We are actually going through this today. Try plugging the AP's that you are deploying on subnets not local to the WS5100, into the local subnet with the WS5100. They should do some blinking and end up with 1 green light blinking. This is the adoption process happening
Now try placing on the remote subnet and see if they can communicate with the WS5100.
Seems like they want to get adopted Layer 2 before being deployed.
We're still testing some sites and it's really a pain working with these AP300's since there is no local config or static ability.
We are actually going through this today. Try plugging the AP's that you are deploying on subnets not local to the WS5100, into the local subnet with the WS5100. They should do some blinking and end up with 1 green light blinking. This is the adoption process happening
Now try placing on the remote subnet and see if they can communicate with the WS5100.
Seems like they want to get adopted Layer 2 before being deployed.
We're still testing some sites and it's really a pain working with these AP300's since there is no local config or static ability.
ASKER
Hey there.
Well my layer 3 access points are now connecting. The firmware needed upgrading this was done and everything is fine. You need to also give them static ip addresses and add a option 189 in DHCP pointing to the controller.
See this,...
http://blog.michaelfmcnamara.com/2007/11/layer-3-access-port-adoption/
However all my ap's are now ok and when i try to connect a client it connects but i dont pick up a ip address and thus cant use it.
Any ideas anyone????
This is great in theory but in practise is a massive learning curve to get it functioning. Let me know how you get on?
Well my layer 3 access points are now connecting. The firmware needed upgrading this was done and everything is fine. You need to also give them static ip addresses and add a option 189 in DHCP pointing to the controller.
See this,...
http://blog.michaelfmcnamara.com/2007/11/layer-3-access-port-adoption/
However all my ap's are now ok and when i try to connect a client it connects but i dont pick up a ip address and thus cant use it.
Any ideas anyone????
This is great in theory but in practise is a massive learning curve to get it functioning. Let me know how you get on?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Please use the Request Attention link in the original question to ask an admin to re-open this, then award the points to FHCSD_IT. My comment was not really a solution and I don't want any points for it. I also think FHCSD_IT's comment is worth an A grade, since if followed it does completely solve the problem as originally stated.
Is it reaching the 3750, and is there a DHCP helper on that switch?