VLANs

Ruckus Smart Zone controllers use VLANs to affect the network access for different sessions. FortiNAC creates interfaces for all the VLANs supported on a device.

It obtains those VLANs from each device it manages. The Ruckus controller does not require the configuration of a comprehensive list of supported VLANs, but it does allow for VLANs to be configured as part of a WLAN definition. Therefore, in order to create a list of supported VLANs on the controller that FortiNAC may access, you must create WLANs on the controller to define each VLAN you plan to use. These VLAN IDs can then be read by FortiNAC when the wireless controller is modeled in the database.

WLANs created exclusively as a placeholder for VLANs should be disabled. Only enable those that you choose to make accessible to connecting users. When a user connects to one of the enabled WLANs, FortiNAC assigns the appropriate VLAN to the session overriding any default value defined.

Create VLANs/WLANs that correspond to the host states you wish to enforce. These connection states include default (production) and isolation states including: registration, quarantine, authentication, and dead-end (disabled).

For WLANs that are created only as placeholders for VLANs, most of the WLAN configuration options are not important. The only WLAN parameters that must be configured for these are the name and the default Access VLAN ID. It is recommended that you also hide the SSID.