The use of IP & Routing feature on Nebula switch (Pro pack required)

Options
Zyxel_Adam
Zyxel_Adam Posts: 350  Zyxel Employee
First Anniversary 10 Comments Friend Collector First Answer

This guide provides a comprehensive walkthrough on configuring IPv4 static routes and IP interfaces supported switches. Currently, the Nebula-compatible devices for the features include:

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

The configuration process included the followings steps:

  • For static routing, your switch must have an IP interface within the subnet of the next hop. This could be a Management VLAN interface or other VLAN interfaces.

  • To set up a new IP interface, navigate to Site-wide > Configure > Switch > IP & routing. In the "IP Interface" section, select 'add' to create a new IP interface on the switch for L3 static routes. Remember, a single switch cannot have two IP interfaces within the same subnet.

  • By default, the switch directs client traffic to its default route learned via DHCP IP in the management VLAN. Therefore, if you need to access a subnet behind this default gateway, configuring an additional static route on the L3 switch isn't necessary (Gateway must configure static routes as well).

  • The static route is essential when the next hop is located on a network that is not the default route. For instance, if the network 192.168.20.0/24 lies behind a different router than the default gateway, a static route in the L3 switch is required for communication with its local VLAN interface.

  • To configure this, go to Site-wide > Configure > Switch > IP & routing. In the "Static Route" section, click 'add' to set up a new static route.
  • The destination should be the network your switch's local VLAN interface needs to access (e.g., 192.168.20.0/24). The Next Hop IP Address should be a gateway's WAN IP address.

Once these steps are completed and the router at 192.168.1.3 has a route back (192.168.10.0/24 next hop =192.168.1.2), your switch’s local VLAN interface 192.168.10.0/24 should successfully communicate with the subnet 192.168.20.0/24.

Adam