Ruckus, VLANs and DHCP Scopes

[Divaldo]

I've just started working in a school with a Ruckus wifi network.

 

They have HP ProCurve switches throughout, but they had a company in over the Summer to re-cable their core switch and tidy up their server room cab. They have various DHCP scopes set up for each VLAN, but since the re-cabling, no devices connected to any of the SSIDs can get an IP address, unless the SSID is moved onto the default VLAN (ID 1).

 

For Example, on the switch I have got:

 

vlan 30

name "Wifi_Staff"

tagged

A1-A3,A5,A9,A13,A19,A21,B3,B19-B20,C1,C24,D10-D11,E1-E3,F1-F4,F12,F2

ip address 10.56.131.1 255.255.255.128

ip helper-address 10.56.132.10

 

 

The DHCP server is 10.56.132.10

 

On Ruckus I have a 'Staff' SSID with the VLAN ID set within advanced options.

Access VLAN VLAN ID:30

 

If I try to connect to the SSID, I can't get an IP address. If I change the VLAN ID back to 1 (default VLAN) it connects fine. The problem is that we soon run out of IP addresses when we put all the SSIDs onto the default VLAN.

 

I have different scopes set in DHCP with the router within scope options for each set as the IP address of the associated VLAN. This all worked fine before the recabling, now it's only the scope for the default VLAN which dishes out any IP adresses. The scope is the only one without a router IP address set.

 

I'm not sure where to begin the troubleshooting, any ideas? I guess the VLANs are all messed up somehow, maybe cables weren't plugged back into the right ports on the switch?

 

Any help would be greatly appreciated!

[ADMaster]

check the ports the APs are plugged into.

I have cisco so slightly different, but all my APs are on trunk ports.

I'd also put an access port on a wifi vlan and plug in a pc just to see if it communicates as it should.

 

I hope that gets you in the right direction.

[EricM_NetCtrl]

Hi Divaldo, a few things to check.

 

1. AP ports make sure there tagged for all the new vlans.

2. the subnet looks wrong for that vlan (255.255.255.128) thats only 128 devices is that right?

3. can the DHCP ping 10.56.131.1 ? if not whats the IP of the core switch? is the gw of the DHCP pointing to the IP address of the core switch is there in the same vlan.

 

if you want me to take a look over your full config send me a PM.

 

Eric

[supawat1]

I am not sure if you have got this issue fixed.

 

But to add more.

 

1. Ensure you have Zone Director and APs on the same VLAN

2. DHCP Relay is setup on Zone Director (this is under Configure menu)

3. Assign VLAN number to a relevant WLAN (if you click on Advanced option, you can see Access VLAN)

4. Enable DHCP option 82 and a Subopt

 

I hope this help

[Divaldo]

Thanks guys, I've been back on site there today.

 

It's tough to know which ports the access points are plugged into as the site is huge and a very old building. The cables disappear up into the ceiling and nothing anywhere is labelled. They all connect to satellite switches which then cable back to the core cabinet, again nothing there is labelled so i don't know which switch is going into which port on the core switch.

 

I have plugged a laptop into a cable that was attached to an AP, and I got an IP address and connectivity fine. I was on the default VLAN though, as it's only the Wifi SSIDs that are set to get an IP address from one of the other ranges.

 

From the DHCP server i can ping the Ruckus controller fine and they're on the same subnet. I can also ping each of the VLAN ip addresses on the core switch.

 

DHCP relay was already set in Ruckus and i tried enabling option 82, but i could still not get an IP address.

 

The running config of the core switch is below. As far as I can see, it shouldn't matter which ports the APs are connected to as the VLANs are set on each port, is that right? Ports which aren't mentioned do not have a cable in them:

 

Running configuration:

 

vlan 10

; Ver #0c:00.34.59.24.6b.ff.f7.fc.7f.ff.3f.ef:8a

hostname "HP-Switch"

module 1 type j8702a

module 2 type j8702a

module 3 type j8702a

module 4 type j8702a

module 5 type j8702a

module 6 type j8706a

ip ssh filetransfer

ip route 0.0.0.0 0.0.0.0 10.56.132.1

ip routing

snmp-server community "public" unrestricted

snmp-server host 10.56.132.11 community "public"

snmp-server host 10.56.132.220 community "public"

vlan 1

name "DEFAULT_VLAN"

untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F24

ip address 10.56.132.32 255.255.252.0

exit

name "Wifi_Stu"

tagged A1-A3,A5,A9,A13,A19,A21,B3,B19-B20,C1,C24,D10-D11,E1-E3,F1-F4,F12,F23-F24

ip address 10.56.128.1 255.255.254.0

ip helper-address 10.56.132.10

exit

vlan 20

name "Wifi_BYOD"

tagged A1-A3,A5,A9,A13,A19,A21,B3,B19-B20,C1,C24,D10-D11,E1-E3,F1-F4,F12,F23-F24

ip address 10.56.130.1 255.255.255.0

ip helper-address 10.56.132.10

exit

vlan 30

name "Wifi_Staff"

tagged A1-A3,A5,A9,A13,A19,A21,B3,B19-B20,C1,C24,D10-D11,E1-E3,F1-F4,F12,F23-F24

ip address 10.56.131.1 255.255.255.128

ip helper-address 10.56.132.10

exit

spanning-tree

no spanning-tree bpdu-throttle

spanning-tree priority 0

no tftp client

no tftp server

loop-protect A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F24

loop-protect trap loop-detected

loop-protect disable-timer 60

no autorun

no dhcp config-file-update

no dhcp image-file-update

[Divaldo]

Just looking at the switch config, I don't appear to have any trunk ports. Is this ok? I read somewhere that the Ruckus APs need to connect to trunk ports on the core switch.

[Divaldo]

All sorted now, thanks for the pointers guys.

The edge switches had been plugged into random ports on the core, some were tagged some weren't, it was a case of comparing live ports with tagged ports and see where they didn't match up, then move the cables.

 

All up and running.