cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1966
Views
5
Helpful
4
Replies

Guest wireless EWC

ChrisChris
Level 1
Level 1

I have setup a Guest WLAN and profile policy using its own VLAN with DHCP from our firewall. This works fine when connected to our DELL switch stack with the port set trunk vlan 2 untagged (native) and vlan 50 tagged (guest wireless). In the EWC access policy VLAN is set to VLAN 50.

But when plugged into a port on our Cisco C9100 stack the internal WLAN work but the guest does not get DHCP so fails.

Port setting we have tried on C9200:

Configuration-Interface-Ethernet:

switch port mode trunk, allowed vlan 2,50, native 2

switch port mode trunk allowed all, native 2

switch port mode dynamic auto, access vlan 2, allowed all, native 2

We know VLAN 50 is accessible from the C9200 as was used with our mobility express wireless, setup very similar.

4 Replies 4

Mark Elsen
Hall of Fame
Hall of Fame

 

 - Why do you use both  switch port mode trunk, allowed vlan 2,50, native 2 and switch port mode trunk allowed all, native 2 ? Also verify the native vlan on the trunk port with  : show interface Gix/y switchport (e.g.)

  Whilst seemingly unrelated verify the EWC   configuration with the CLI command : show  tech   wireless , have the output analyzed by  https://cway.cisco.com/tools/WirelessAnalyzer/  , please note do not use classical show tech-support (short version) , use the command denoted in green for Wireless Analyzer.               Checkout all advisories!

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

Rich R
VIP
VIP

Show the actual config you've used on the EWC rather than describing it.

Did you configure the VLAN by name or by VLAN ID (number: 50)?  EWC is all flex local switching so you must specify the VLAN ID.  Using names requires a flex profile which defines those names for the AP.  Better/easier to simply use the ID.

There have also been a few bugs around this - what version of software are you using?

Hi, I have specified using VLAN ID. Software version is 17.8.0.144/17.08.01.0.1490

After further testing we have found if a client connects to one of the APs not running the controller both WLANs work fine but if the client connects to the controller AP only the internal WLAN works, the Guest VLAN does not get DHCP from our firewall and fails.

Rich R
VIP
VIP

Presume your EWC trunk port has vlan 50 allowed on switch port and vlan 50 defined on the EWC?
Can't say I've actually tried this but it should work.
17.8 is a limited support release (no fixes) - if you want to stay bleeding edge (or need new features) then use 17.9.1 which will get maintenance updates for extended support or revert to 17.6.4 for a more mature release (although no guarantee it will make any difference to this problem if it's a bug)

Review Cisco Networking for a $25 gift card