Home > Security and SD-WAN > Networks and Routing > Configuring VLANs on the MX Security Appliance

Configuring VLANs on the MX Security Appliance

As a network grows to include users in multiple physical locations it becomes necessary to segment the network into various virtual networks or VLANs. This article describes how to configure VLANs on the MX Security Appliance.

 

Ensure that the MX is configured to be in Routed mode on the Security & SD-WAN > Configure > Addressing & VLANs > Deployment Settings > Mode section. VLANs cannot be configured if the MX is in Passthrough or VPN Concentrator mode.

Enable VLANs on the Dashboard

vlans disabled.PNG

VLANs are disabled by default on the MX. They can be enabled from Security & SD-WAN > Configure > Addressing & VLANs > Routing by checking the Use VLANs box.

 

Configure VLANs

configure vlans.PNG

After VLANs have been enabled you can add additional VLANs by clicking Add VLAN.

In this example, the MX has three VLANs:

  • VLAN 1: 192.168.1.0/24
  • VLAN 2: 192.168.2.0/24
  • VLAN 3: 192.168.3.0/24

The Subnet is the network expressed using CIDR notation, the ID is the 802.1Q VLAN number, the Name is a description of the VLAN, the MX IP is the local MX VLAN interface IP, and the Group Policy shows the name of the group policy applied to the VLAN, if any. A VLAN can be removed by checking the box next to the VLAN and clicking the Delete button. Click here for more detailed information about settings on Addressing & VLANs. 

create VLAN.PNG

Configure LAN Ports

Next, the uplink ports to our switches will be configured as a trunk port to carry the VLANs that were configured in the previous step. Changes can be made to the MX LAN ports under Per-port VLAN Settings by selecting the check box beside the port number or by selecting multiple ports and clicking the Edit button.  

per-port vlan settings.PNG

 

The Type determines if the LAN port is an access or trunk port. When connecting the MX to a switch that will carry multiple VLANs, select trunk from the drop-down. Traffic without an 802.1Q tag will be dropped by default unless a native VLAN is defined from the Native VLAN field. You can specify specific VLANs that the trunk port will allow from Allowed VLANs or choose to allow all VLANs to pass on the link. Click here for more information about per-port VLAN configuration options.

per-port vlans.PNG

Other Considerations

In some cases it is necessary to restrict access between different VLANs. Please refer to the following knowledge base document which describes how to use outbound firewall rules to restrict traffic between VLANs.

Last modified

Tags

Classifications

This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 1429

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community