Deployment Scenario 2 - WS and AP are in different subnets (port-based routing):
This deployment consists of a single WLAN switch connected to a L3 device
(router). APs are connected to the core with port-based routing. This configuration does
require L3 tunneling to accomplish seamless roaming across APs connected to different
L3 only ports on the core. Consider the MTU issue, services that require fast L3
roaming will need to be configured as L3 Tunneled VAPs to allow subnet roaming –
these services will be affected by the MTU issue in that either the MTU configuration of
the physical interfaces between the APs and the WLAN Switch must be increased by 20
bytes (or the client MTU decreased by 20 bytes), or the service must be expected to
transmit “smaller” sized packets. Services that do not require fast roaming across L3
boundaries can be configured to non-Tunneling in which case the MTU issue is not
observed for those services. If all devices in the network support increasing the MTU
size, and this are feasible to do, then all of the services can be configured for Tunneling
without any problems and fast roaming will be possible for all services.
WS1
AP1
AP2
Seamless Roaming
192.168.20.x
192.168.30.x
SSID:
Guest Network: VLAN 100
Employee: VLAN 200
Voice: VLAN 7 (L3 tunneling)
SSID:
Guest Network: VLAN 100
Employee: VLAN 200
Voice: VLAN 7 (L3 tunneling)
L3 Device
Scenario 2
