3 Replies Latest reply: Jun 8, 2018 11:38 AM by Romain Jourdan RSS

Does SteelConnect Gateway support statics routes on WAN Side?

Erick Munoz

Let's assume that I have this simple topology on a branch office.

 

I want to remove firewall device and instead of it, install a SteelConnect Gateway device as shown in image below.

 

I have not found any documentation releated to configure static routes on WAN side.

I understand the concept of 3rd party zone witch uses static routes, but this concept only apllies to LAN Side of SteelConnect Gateway

 

How should I tell the Gateway that it has to reach remote sites through the MPLS router without enabling dynamic routing?

 

In the deployment guide a similiar design is addressed, there is mentioned that OSPF is recommended but alsoi it is mentioned that we can use static routes.

 

 

The issue is that MPLS CE Router is usually carrier managed (not customer managed), so it is pretty difficult that carrier accepct to enabling dynamic routing and by the other hand this is a very simple design that easely could be managed wirh statics routes.

 

Thanks in advance.

 

.

  • Re: Does SteelConnect Gateway support statics routes on WAN Side?
    Romain Jourdan

    Hi Erick,

    It is indeed a very valid use case.

    For that to work, you would use Transfer Networks.

    Under Network Design > WAN, you have certainly created a MPLS WAN. You can define the subnets that are known on the MPLS WAN under Transfer Networks.

    Screen Shot 2018-06-07 at 5.16.30 PM.png

    Make sure you configure an IP address to ping check, a core router in the DC or a PE router on MPLS network would do the job.

    In addition, make sure you configure the uplink to use its Internal IPv4 address for AutoVPN (Network Design > Uplink, select your MPLS uplink for the site and go to the AutoVPN tab).

    Screen Shot 2018-06-07 at 5.15.55 PM.png

    • Re: Does SteelConnect Gateway support statics routes on WAN Side?
      Erick Munoz

      Thanks Jourdan

       

      Just to  comfirm...

       

      So, when I specify theese transfer networks under MPLS WAN, I'm telling the Gateway that when it receives a packet with destination IP address belong to remote site network, it should forward the packet to its ullink-mpls interface, is that correct? So this transfer networks acts like a static routes?

       

      no explicity stactic or dinamic routing is needed?

       

      But theese transfer networks also are know by the AutoVPN WAN because theese networks/zones exist in another sites insite the  same organization.

      (acording to my understanding, transfer networks are networks that aren't part of LAN zones iside the organization), as user guide explains here.

       

      So, if it works as expected, there are  two posible paths to reach romote sites networks.

      1. AutoVPN WAN

      2: MPLS WAN.

       

      Then I can perform traffic decisions (fail over or load balance) with the feature path selection (traffic rules), rigth?

      • Re: Does SteelConnect Gateway support statics routes on WAN Side?
        Romain Jourdan

        Hi Erick,

         

        Transfer networks will indeed work as static routes for the WAN, for the "underlay".

         

        If the destination IP is in a remote site equipped with Riverbed SDWAN, the route will be learned via the Overlay and the SteelConnect Manager. By default, Overlay network is always preferred.

         

        If the destination IP is in a remote site with a traditional router, the underlay will be used.

         

        With 2.11 coming up, you will have the ability to create a path rule that forces the traffic to go via the underlay

         

        HTH!

        Romain