Best practice to deploy with multiple VLANS?

kspickler
New Member

Best practice to deploy with multiple VLANS?

We want to deploy these APs in a network with multiple VLANs, guest and employees. Assuming both VLANs should be assigned to the switch interface, which VLAN should be tagged, and which VLAN should be used for the initial deployment?  I assume employee VLAN is untagged (native) and used for deployment?

3 Replies
Employee
Employee

Re: Best practice to deploy with multiple VLANS?

@kspickler For Instant ON AP's you have the ability to assign a VLAN to the Employee network in the configuration. When you create the Guest network it will create an internal VLAN and NAT all traffic through the default gateway of the AP. So if you configure your switch for the native VLAN you use for the employee's and all traffic will traverse that network.

You could create multiple employee networks on different VLAN's and name the second one Guest.

Example for an Aruba Switch

interface 1
   tagged vlan 20 (Guest)
   untagged vlan 10 (Employee)

0 Kudos
kspickler
New Member

Re: Best practice to deploy with multiple VLANS?

Thank you @GThiesen. If the guest network created in Instant On is NAT'd through the default gateway, can we use a DHCP for the guest network? Or would we need to create an additional "employee" network in order to use our own DHCP for that network? The idea is to keep employees and guests on different IP networks that we define.

0 Kudos
Employee
Employee

Re: Best practice to deploy with multiple VLANS?

@kspickler  For the Guest network DHCP is done via the AP only. Create a second Employee network for a different VLAN.