Static routes on XMG1915

vinetarius
vinetarius Posts: 2  Freshman Member
First Comment

At my core is a router on a stick configured FW with a separate managment vlan/subnet/physical interface. I want the 1915 to have a port on that management vlan and then a trunk port to the router on a stick interface, but it would require static routes to each vlan. When I enter route statements in the UI, I get a generic failure to add route message requesting I re-enter the settings. Route: 10.10.2.0, subnet 255.255.255.0, gateway 10.10.2.1, metric 2. what am i missing? I also tried to just add a vlan interface and do an SVI type link, but the vlan interfaces only apply to CPU, so that doesn't seem like it will work for me.

All Replies

  • Zyxel_Melen
    Zyxel_Melen Posts: 3,635  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @vinetarius

    What is the error message you encountered? Please help to provide it so we can know how to provide you a solution.

    Additionally, is your purpose to let each VLAN can access your switch? If that, you don't need to set anything. Your router should be able to route from other VLAN to your switch. You just need to ensure it have set default gateway as your router.

    Zyxel Melen


  • vinetarius
    vinetarius Posts: 2  Freshman Member
    First Comment

    The message is very generic, it simply says failure adding route, then the only option is to return to settings. I believe solved this - the device appears to only allow route statements to networks for which it has an IP interface. In my case, because the management interface is connected to a dedicated and isolated interface on my FW, I added a vlan interface with an ip on a non-routed transit subnet matching my router on stick and set the default route to the router on a stick gateway address. So far, this seems to be now working as I expected. I was concered that it would allow management of the device via the vlan interface address, but it appears it knows not to do that.

    route add screenshot.png Route add error.png