HP830 multiple SSID

[M-Refaat]

Hi All,

i have a problem a confussion regarding the SSIDs

I have a HP 830 Unified wired wireless controller and HP 430 APs and HP 2530 POE switches

i need to create two SSIDs from what i know each SSID must be mapped to a certain VLAN

i created two wireless service but from the configuration of wireless service in web ortal i only can see untagged VLAN and default VLAN and delete VLAN there is no tagged vlan and i need tagged vlan to make each SSID map to a vlan

my concern is if i have two VLANs 10 and 20 and the connection as below

HP 430 AP  ------------------(untagged in VLAN 1)  HP 2530 Switch  (tagged in ALL VLAN)-------------(tagged in ALL VLAN) LSW  controller switch engine (tagged in ALL VLAN)----------------(tagged in ALL VLAN) UWW wireless controller engine

i nned to create two SSID mapped to different VLANs and don't allow communication between each other

appreciate any help regarding thi

[Emil_G]

Hello,

You dont need a tagged VLAN in the configuration of the SSID (or wireless service as it is called here). You can specify the the VLAN you want the SSID to be mapped to as untagged VLAN and default VLAN. This setting only specifies how the controller maps the SSID to a VLAN internally.

This setting doesnt specify how the controller sends the traffic in the wired VLAN. Thus it doesnt specify the configuration of the physical ports of the controller engine and switch engine.

You have to configure the tagged VLANs on the physical interfaces manually. The Bridge-Aggregation1 which connects the switch engine and controller engine is by default an access port in VLAN 1. You have to make it a trunk port and configure all the desired VLANs. This has to be done separatelly on both  -  the controller engine and switch engine.

The traffic flow from WLAN to LAN:  The AP MSM430 receives a wireless packet destined to the LAN. It is encapsulated in a tunnel and send to the controller in VLAN 1. All the switches between MSM430 and controller engine must support VLAN 1. Only the controller engine can terminate the tunnel. The controller receives the packet in VLAN 1, decapsulates and transforms the packet from WLAN to Ethernet format. Based on the SSID the controller assigns the packet to a VLAN (the VLAN you specified in the wireless service ). Then the controller sees that the VLAN is tagged member of Bridge-Aggregation 1 and it knows that the packet has to be tagged with the respective VLAN ID. The switch engine then forwardes the packet to the wired LAN.

This is a very basic explenation. There are also other options and details.

Also the tagged VLAN by itself doesnt always guarantee that the traffic of both VLANs will be separated. It will be separated at Layer 2, but if the default gateway of both VLANs is the same router, you have to additionally define ACLs on the router to deny the routing between the 2 VLANs.

Not sure whether my explenation is clear. Thats why I would like to recommend to consult the documentation as well.

WLAN configuration guide

http://h20566.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=5377832&docId=emr_na-c04406853&docLocale=en_US

This is a collection of configuration examples. All made via the CLI.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c04500628-1.pdf

If you are not confortable with the CLI here is the web based configuration guide. This guide has also configuration examples at the end of each chapter.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c04568112-3.pdf

You can find all the manuals for the device here

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/manualsResults/?sp4ts.oid=5377832&spf_p.tpst=psiContentResults&spf_p.prp_psiContentResults=wsrp-navigationalState%3Daction%253Dmanualslist%257Ccontentid%253DSetup-and-install-general%257Clang%253Den&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken