Nebula - Layer 3 [L3] Switching (Licensing & Configuring)

This step by step guide shows how to configure IPv4 static routes in the switches that support L3 static routing and IP interfaces.  At the time of writing, the following devices support IPv4 static routes on Nebula:

• XMG1930 Series
• XMG1930 Series
• XGS2200 Series
• XS1930 Series
• XGS1930 Series
• XS3800 Series

1. Creating the IP interface

2. Setting up the static route

1.Creating the IP interface (PRO)

In order to use static routes, the switch should have an IP interface on the subnet that includes the next hop to which the traffic will be forward.

Management VLAN interface and other VLAN interfaces (e.g. IGMP querier interface) can be used as IP interfaces for next hop in the static route.

To create a new IP interface, go into:

Site-wide > Configure > Switch > IP & routing

In the "IP interface" section, click add to create a new IP interface on the switch that requires L3 static routes:

Note: a single switch may not have two IP interfaces using the same subnet.

2. Setting up the the static route (PRO)

It is worth to mention that by default the switch will route client traffic to its default route learned from DHCP IP in the management VLAN. Hence, if the subnet you need to access it's behind the default gateway in the management VLAN, there's no need to configure any static route in the L3 switch (gateway static routes still need to be set up).

The use of static routes becomes meaningful when the next hop is located on a network that is not the default route.

As in below example, the network 192.168.20.0/24 is located behind a router different than the default gateway and a static route in the L3 switch will be needed to communicate it's local VLAN interface:

To create the static route, go into:

Site-wide > Configure > Switch > IP & routing

In the "Static route" section, click add to create a new static route:

The Destination should be the network to which the switch's local VLAN interface needs to access, in above example, 192.168.20.0/24. The next hop IP address must be a gateway which is within the IP interface created in step 1, in this case, 192.168.1.3.

The switch's local VLAN interface 192.168.10.0/24 should be able to communicate with the subnet 192.168.20.0/24 as soon as the router (192.168.1.3) has defined a route back.