HP Wireless: Problems with more than 2 VSC (aka SSID's)...

[Jontu Kontar]

Hardware:
[ul]
[li]HP E5413zl Switch Chassis[/li]
[li]HP MSM765 Wireless Controller[/li]
[li]HP MSM430 & HP MSM460[/li]
[/ul]

Config:
[ul]
[li]Switch[/li]
[ul]
[li]VLAN 1-13[/li]
[ul]
[li]VLAN 2 = Parts[/li]
[li]VLAN 3 = Service[/li]
[li]VLAN 10 = Guest[/li]
[/ul]
[/ul]
[ul]
[li]Port: B1-B6: Tagged 2, Tagged 3, Untagged 10, Tagged 13[/li]
[li]Port: K1-K2: Tagged 2, Tagged 3, Untagged 10, Tagged 13[/li]
[/ul]
[li]Wireless Controller[/li]
[ul]
[li]Internet Port: No Address[/li]
[li]VLANs mapped to Internet Port[/li]
[li]VSC's mapped to ingress at each VLAN[/li]
[/ul]
[/ul]

Issue

Today, I went to activate a 3rd VSC and found out that it doesn't work but I don't know why or how to fix it. The earlier 2 VSC's (SERVICE & GUEST) work perfectly. Someone associates with an SSID and they get access to the appropriate VLAN. (e.g. Join SERVICE and get resources on VLAN 3.) The 3rd (PARTS) VLAN acts oddly, if you associate with it, it will give you access to VLAN 1 (instead of VLAN 2).

So far as I can tell, all the VSC's and configs are correct. Anyone have a guess?

 

[Jontu Kontar]

Found the answer: The Web Interface LIES!!!

controlled network group "INSIDE"
  virtual ap binding "PARTS"
    egress vlan default
    egress vlan
    location aware INSIDE
   end
end

Even though I had specified it to use VLAN 2 (PARTS), it was using VLAN 1 (default) as the egress point for communication. After wading through the commandline, I changed "egress vlan default" to "egress vlan PARTS". A short sync later and everything is kosher!