How to configure VLAN Interfaces and Static Routes on Omada Switches

Configuration Guide
Updated 06-27-2024 03:09:21 AM 4636
This Article Applies to: 

This article applies to: All Omada Smart, L2+ and L3 switches.

Contents

Objective

Requirements

Introduction

Configuration

Configuring VLAN Interfaces

Configuring Static Routes

Conclusion

Objective

This article introduces how to configure VLAN Interfaces and static routes on Omada switches, configuration steps on Omada Controller are then described.

Requirements

  • Omada Smart, L2+ and L3 series switches
  • Omada Controller (Software Controller / Hardware Controller / Cloud Based Controller, V5.9 and above)

Introduction

After configuring VLANs on a switch and assigning them to different ports, devices connected to these ports in different VLANs cannot communicate with each other due to VLAN isolation. To enable communication, we need to configure VLAN interfaces and static routes to establish connectivity between VLANs.

This article will introduce VLAN interface how to configure VLAN interfaces and static routes on Omada switches.

As shown in the figure below, the gateway is connected to the switch, which in turn is connected to multiple VLANs, each containing one or multiple terminal devices. For efficient network planning, we hope that devices in different VLANs have IPs in different network segments. For VLAN x, the network segment of the device should be 192.168.x.1/24. The DHCP server is enabled on the switch, and the switch is responsible for assigning IP addresses to all devices in the network as well as performing Layer 3 forwarding. The gateway communicates with the switch only through VLAN1, and the internet traffic of the terminal devices are all forwarded by the switch at Layer 3 to VLAN1, which then passes it to the gateway.

To ensure the devices in different VLANs obtain unique IP addresses within their VLANs and can communicate with each other as well as accessing the internet, we need to enable VLAN interfaces for each VLAN on the switch and activate DHCP services. To correctly forward traffic from terminal devices to the internet and ensure that external traffic returns to the correct devices, it is necessary to configure a pair of static routes on both the switch and the gateway. Here are the detailed steps and explanations, we take ER706W and SG3452XP as an example.

Configuration

Configuring VLAN Interfaces

Step 1. Adopt the gateway and the switch in the Omada Controller.

Step 2. Create VLAN 3 and VLAN 5, in Settings > Wired Networks > LAN, click Create New LAN. Here, if you select Purpose as VLAN, the interface will be enabled on the gateway by default. However, in this example, we need the switch to handle all Layer 3 forwarding, so choose Purpose as VLAN and Application as Switches Only. Then click Save.

Create VLAN 5 in the same way.

Now three networks have been created.

Note: By default, the VLAN 1 Interface is enabled and the DHCP server is on the gateway in this mode. You can choose to disable the DHCP server on the controller and enable the DHCP server for VLAN 1 on the switch responsible for Layer 3 forwarding. If VLAN1 is only used for communication with the gateway, no change needed.

Step 3. Enable the VLAN Interfaces on the Switch. Go to Devices, click on the switch to enter its private configuration page. In Config > VLAN Interface, enable the corresponding VLANs and click Apply to enable the interfaces.

Step 4. Configure VLAN Interfaces, click the Edit buttons to enter the configuration page. Set the interface's IP Address Mode to Static. In this example, set the IP address of VLAN 3 to 192.168.3.1/24.

Step 5. Configure DHCP Server. For the DHCP Mode, it is configured in the same page after configuring IP Address Mode. In this example we select DHCP Server, you can also choose None which means to disable DHCP server for this VLAN Interface or choose DHCP Relay as you need. Configure the DHCP Range, DNS, and Default Gateway, then click Apply to save the configuration.

Perform the same steps for VLAN 5.

Now, VLAN 3 and VLAN 5 are enabled on the switch with their respective DHCP servers configured.

Step 6. Change the port profiles. Go to Ports in the private configuration page of the switch, click the Action button for the corresponding ports and edit their Profile.

Click Apply, the devices connected to this port will communicate and obtain an IP address directly from the corresponding VLAN.

Configuring Static Routes

Configure Static Routes on both the switch and the gateway:

Step 1. Create static routes on the switch. Go to Config > Static Route in the configuration interface of the switch, click Add.

Tick to change the Status to Enable. Since we are dealing with all internet-bound traffic, you can set the Destination IP/Subnet to 0.0.0.0 and the Next Hop to the gateway at 192.168.0.1. For other traffic, more accurate default routes will be matched first, so just enter 1 for Distance, click Apply to save the configuration.

Now the static route has been added and applied on the switch.

Step 2. Create static routes on the gateway. Go to Settings>Transmission>Routing>Static Route, click Create New Route.

Since all received traffic needs to be forwarded to the switch and the format of all network segments in the LAN is 192.168.x.x, the Destination IP/Subnet should be configured as 192.168.0.0/16, set the Route Type as Next Hop and Next Hop as 192.168.0.2. Click Apply.

Now the static route has been created and applied to the gateway.

Conclusion

Here we have finished introducing how to configure VLAN Interface and static routes on Omada switches through Omada Controller.

Get to know more details of each function and configuration please go to Download Center to download the manual of your product.

Is this faq useful?

Your feedback helps improve this site.

Recommend Products

Community

TP-Link Community

Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.

Visit the Community >

From United States?

Get products, events and services for your region.