Wireless VLan Problem

[ccadit]

We are in the process of setting up a new Wireless network, we have two sites on one of our sites we have successfully ripped out all of our Cisco AP's and replaced them with cloud Meraki AP's on our second site however we seem to be having an issue where clients can't access the Internet or even ping their local gateway when connected on the new APs i'm quite sure its an issue with VLANs as if I remove the VLAN from the SSID it works fine, some forum member were kind enough to give me some very useful suggestions that allowed me to setup the site that is working, and was wondering if anyone could help me again, to get the second site up and running.

 

this is the VLAN info from the edge switch that the AP is plugged into on Port 24

vlan 10

name "Wireless"

ip address 172.17.10.254 255.255.248.0

tagged 24,28

exit

 

this is the VLAN info from the core switch that the AP is plugged into on Port B23

vlan 10

name "Wireless"

ip helper-address 172.18.0.15

ip address 172.17.10.254 255.255.248.0

tagged A1,B23

exit

 

 

any help will be most appreciated.

[FN-GM]

Looks like a HP switch to me?

 

Remove the VLAN IP address settings from the edge switch. They are not required and there is a good chance it could be causing issue.

[ccadit]

It's a HP switch and I already tried that and it wasn't working without it in, so I decided to add it to see if it makes any kind of difference.

[FN-GM]

Right ok, I would keep it removed in that case. Is IP routing enabled on the switch? Do you have other VLANs on the switch? Does the client get an IP address?

[localzuk]

OK, a few things I can see

 

1. Get rid of the IP for the VLAN on the edge switch - the VLAN should only have 1 IP, on the switch which handles the routing for that VLAN.

2. Ensure that any VLANs that the APs use are tagged on the port it is plugged into.

3. Ensure that the 'management' vlan (ie. the VLAN which has the IP that the AP itself uses) is untagged on that port.

[ericscher]

I may be in error since I cannot see the full config and may be analyzing this incorrectly. However...

 

The switch needs an IP address for the management VLAN, which is typically VLAN 1, plus any other VLAN's on the switch. But those don't get applied to the individual interfaces.

 

The individual interfaces will get a much simpler config. I can't recall HP syntax off the top of my head but it should look something like this:

 

Switch(config)# interface fastethernet0/1

Switch(config-if)# switchport mode access

Switch(config-if)# switchport access vlan "X"

 

And of course you'll have to trunk up at least one of the ports to connect up to the next higher level device, but I assume that config is already there on the assumption that the switch in question is not new.

 

I hope that helps.