Showing results for 
Search instead for 
Did you mean: 

vSZ-D Tunnelling WLAN with VLAN Tag What i am missing

New Contributor II
The problem is when i create WLAN and tagged it with DATA VLAN ID 234 , (i used Tunnel WLAN traffic to the controller) my client can't get IP address from DATA VLAN, try it with static IP address assignment, my device still can't ping my DATA VLAN Gateway
 I look around the configuration and still not working. What i am missing
Vsz-H version
Vsz-D version
AP-R700 Router Cisco DHCP-SERVER and Gateway


Virtual :
Vsz-D Data interface IP
MGMT interface IP Vsz-H
MGMT interface IP

all port Trunk.
My Topology
Image_ images_messages_5f91c3e8135b77e2478dbdba_e0191ece132134584cbcb3f6f5be8101_RackMultipart2018022388768ygff-49f16fdf-ba64-4fee-85c1-6f2ee99a4ef8-1805950074.JPG1519380495

Esteemed Contributor II
Hi Lasha,

   I can see/understand your diagram, but it appears you are missing some things.

In VMware, you need to setup a new port group for the DataPlane.  You need to make this port
a trunk by allowing all VLANs.  Enable Promiscuous mode and then, since you are running a
vSwitch, you need to go to the vSZ-D Console, and configure the data interface to tag the data
VLAN for it.

The Client WLAN VLAN should be different than the data VLAN from the data interface.  You don't
want your client having access to that VLAN I'd assume.

To recap:

1 - Create new portgroup with All VLANs allowed and promiscuous mode accept in the security tab.
2 - Console to the vSZ-D and go to configure, interface data, VLAN 234 to tagthe data interface VLAN.
3 - Create a new VLAN for the clients and then configure that on the AP so thatthey get their IPs from there.  The vSZ-D data interface VLAN and theclient access VLAN should never be the same (not that they can't). 
4 - Ensure the switch port allows the newly created client VLAN.
5 - Ensure DHCP is set for the new VLAN, not VLAN 234 as that is the interfaceof the vSZ-D Data Interface.
6 - Ensure the AP can talk to the vSZ-D Data interface and the controlinterface.

For reference, from the AP to the vSZ-D Data Interface, by default, you should allow ports 23233 on both TCP and UDP.
From the AP to the control plane, you need port 22, 443, and any other port you may require for captive portals, see the firewall configuration guide on our support site under Best Practice Documents section. 

I hope this helps.

Micheal, can you explain better how to make the data interface be a trunk port ?
I was only able to ''tag'' one vlan on it, wit the command vlan "X".

This post helped me figure out the vSZ-D configuration.  My ap's have establed GRE tunnels back to the dataplane.  Thanks!

I will say that the ap's did not establish the GRE tunnel until after a wlan configured for tunneling was put in place.

New Contributor III
Thank you Michael, this should be in the documention, very helpful !!!
Can you clarify, because I not able to make my vSZ-DP, data interface be a trunk port... I can only "tag'' one vlan with the command vlan "X", and that is it, I tried different syntax but did not work....
So, how can I have differents ssid with differents vlan pools, and make it enter the data interface from my DP ??
I understand that I should have my vnic as a trunk port, but I do not understand how to make the data interface be a trunk port.
Here my config of it:
data iface:
name: pow0

vlan: 0
proto: static