Virtual LAN Management

Issues:

• Your LAN is separated in many segments (virtual lans), but VLAN are managed statically.
• Its is not easy to move a device to different VLAN? Or difficult to redefine the VLANs on physical LAN sockets where different VLAN needs keep appearing?
• To use any available Network Socket for any VLAN or system?
• A specific VLAN to be used by 'unknown visitors'?

VLAN management is easier using FreeNAC.

A VLAN is specified for each end-device, and this VLAN will be always used by this device, regardless of its geographical position within your premises. If you ever happen to have reorganization, you don’t need to adapt your switches’ configuration, since the network will adapt to your new organization (all ports are 'dynamic').

Changing VLAN associations is just a matter of selecting the VLAN to use from a drop-down list and you are done, lowering thus the amount of work for the system administrator when it comes to create VLAN memberships for specific projects.

You can override the default VLAN policy for specific LAN sockets (i.e. ports). For example the default policy might be to deny access to unknown devices, except in meeting rooms where visitors (unknown devices) are automatically allowed access to a Guest VLAN.

Location dependant VLANs: VLAN naming may not be uniform across all buildings/switches, or not all VLANs are available on all switches. For this scenario, FreeNAC allows you to map VLAN names for such switches.