10-24-2013 07:40 AM
I've just installed a new S2500 switch, hooked it up to my core stach (which is Cisco). I did the initial setup config and set up the initial default vlan. Since I only want the one vlan on this particular switch, I stopped there.
If I plug into the switch with my laptop, I pull a DHCP address, I can get out to the internet, I can pull up the aruba controller.
When I plug an access point into the same port on the switch, I get nothing. It powers up, the link shows as up. The DHCP server shows a lease issued in the correct subnet. It just never fully boots because it's not finding the controller. If I plug the AP into a different switch, it boots, loads, and talks just fine.
AP is a 225, switch is brand new. Any suggestions for what to check next?
10-24-2013 07:50 AM
10-30-2013 12:24 PM
Well... I finally figured it out.
In the DHCP scope for the vlan that this switch is using, there was no 003 Router option defined, so no default gateway.
Comparing the console output of the AP from the broken vlan to a working vlan showed that when it pulled an IP, there was no DG listed.
Adding the 003 option on the DHCP server solved the problem.
Why the laptop worked on DHCP in the same vlan, I don't understand.
This is what I get for using an old utility vlan that I created years ago and didn't bother fully re-checking, assuming I had set it up completely in the first place.