Unable to configure 10 SSIDs on V2110+Hyper-V
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-10-2015 04:56 AM
Hello, everybody!
I have V2110 (9.21) with Hyper-V (2012 R2) installation. My task is to configure 10 different SSIDs for 10 teams, and every SSID have to be binded to a certain VLAN.
SSID (Team-1) have to be associated to VLAN10, SSID (Team-2) have to be associated to VLAN20, etc.
Could you please tell me, what kind of topologies I have to create in this case?
At the moment I have the following:
For each SSID I've created two topologies, for example:
VLAN10, B@EWC, VLANID 10, untag, port esa1, 192.168.10.1
VLAN10-S, B@AP, VLANID 10, tagged
It works only if on Hyper-V side I set "VLAN identification" for a certain interface. This limits me to creating only 2 SSID working simultaneously because of untagged traffic at V2110 side and Hyper-V limitations (where I can set only 1 VLAN per interface).
Please, help me to solve the problem!
Many thanks in advance.
I have V2110 (9.21) with Hyper-V (2012 R2) installation. My task is to configure 10 different SSIDs for 10 teams, and every SSID have to be binded to a certain VLAN.
SSID (Team-1) have to be associated to VLAN10, SSID (Team-2) have to be associated to VLAN20, etc.
Could you please tell me, what kind of topologies I have to create in this case?
At the moment I have the following:
For each SSID I've created two topologies, for example:
VLAN10, B@EWC, VLANID 10, untag, port esa1, 192.168.10.1
VLAN10-S, B@AP, VLANID 10, tagged
It works only if on Hyper-V side I set "VLAN identification" for a certain interface. This limits me to creating only 2 SSID working simultaneously because of untagged traffic at V2110 side and Hyper-V limitations (where I can set only 1 VLAN per interface).
Please, help me to solve the problem!
Many thanks in advance.
9 REPLIES 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-13-2015 11:16 AM
Please reference: https://gtacknowledge.extremenetworks.com/articles/Solution/Hyper-V-fails-to-pass-VLAN-tags-on-a-bri...
Doug Hyde
Director, Technical Support / Extreme Networks
Director, Technical Support / Extreme Networks
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-12-2015 04:03 PM
Hello, Ron!
The required infrastructure works only if both topologies are configured and enabled.
Would you please share this manual with me?)
Thank you.
The required infrastructure works only if both topologies are configured and enabled.
Would you please share this manual with me?)
Thank you.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-12-2015 04:03 PM
I believe the document Ron is referring to can be found on this page: https://extranet.extremenetworks.com/downloads/Pages/WirelessControllers.aspx
Look on the documentation page under Wireless Hardware and Gateway Guides -> Virtual Gateway V2110
Look on the documentation page under Wireless Hardware and Gateway Guides -> Virtual Gateway V2110
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-12-2015 11:34 AM
Regarding the screenshot - you either configure a bridge@EWC OR bridge@AP but not both.
As I've mentioned it comes down to the network design which method to use.
I'd recommend to read the manual "V2110 Virtual Appliance Installation Guide - MS Hyper-V Platform" page#13, there are the instructions to support tagged VLANs in Hyper-V which you need for bridge@EWC toplogies.
If you use bridge@AP the controller can't be the DHCP server - you'd need an external one.
-Ron
As I've mentioned it comes down to the network design which method to use.
I'd recommend to read the manual "V2110 Virtual Appliance Installation Guide - MS Hyper-V Platform" page#13, there are the instructions to support tagged VLANs in Hyper-V which you need for bridge@EWC toplogies.
If you use bridge@AP the controller can't be the DHCP server - you'd need an external one.
-Ron
