Search

VERSA SD-WAN HUB AND SPOKE

The many designs work as a hub and spoke. in the corporate world, there are headquarters and branches. Hub and Spoke topology have many advantages.

These advantages;

  • Cost Saving

  • Easy to Set up and Maintain

  • Centralized Policies

The most important issue for a network engineer is that it is easy to install and maintain :) Budget is not my topic right now :) Also, Centralized Policies are very important for security. We need the centralized police to keep up-to-date security updates at all sites.


Our topic today is to build the hub and spoke topology with Versa.





I am adding a hub device to our topology. The FlexVnf will be located as hub device at this topology.

We need to prepare a template for the hub device. All spokes will speak over the hub.


Hub Template;

Note-1: If you want branches to exit the Hub to the Internet, you must select DIA in the hub template.

Note-2: I choose the gateway option because it needs to be a hub.

Hub Device Template;

The hub device is ready for registering to Director.


This registration is the same as the registration process of the FlexVnf. Also, you can see the document.


Our command;

sudo /opt/versa/scripts/staging.py -l SDWAN-Branch@networktcpip.com -r Controller-1-staging@networktcpip.com -c 192.168.50.2 -w 0 -d

Now we have to create a spoke template. For this, we need to create a spoke group.



Spoke Template;

Spoke Device Template;


The Spoke device is ready for registering to Director.


This registration is the same as the registration process of the FlexVnf. Also, you can see the document.


Our command;

sudo /opt/versa/scripts/staging.py -l SDWAN-Branch@networktcpip.com -r Controller-1-staging@networktcpip.com -c 192.168.50.2 -w 0 -d

The latest status;

Troubleshooting;


Spoke1 interfaces;


The spoke's default route gateway is the hub device. Also, we can see the other spokes route


Spoke1 Lan routing instance table;

admin@Spoke1-cli> show route routing-instance networktcpip-LAN-VR

Routes for Routing instance : networktcpip-LAN-VR  AFI: ipv4  SAFI: unicast

Codes: E1 - OSPF external type 1, E2 - OSPF external type 2
IA - inter area, iA - intra area,
L1 - IS-IS level-1, L2 - IS-IS level-2
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
RTI - Learnt from another routing-instance
+ - Active Route

Prot   Type  Dest Address/Mask   Next-hop        Age      Interface name
----   ----  -----------------   --------        ---      --------------
BGP    N/A  +0.0.0.0/0           10.0.0.12       01:59:07 Indirect
conn   N/A  +192.168.127.0/24    0.0.0.0         01:59:32 vni-0/2.0
local  N/A  +192.168.127.254/32  0.0.0.0         01:59:32 directly connected
BGP    N/A  +192.168.128.0/24    10.0.0.12       01:54:07 Indirect
BGP    N/A  +192.168.129.0/24    10.0.0.12       01:52:51 Indirect
BGP    N/A  +192.168.147.0/24    10.0.0.12       01:59:07 Indirect


Routes for Routing instance : networktcpip-LAN-VR  AFI: ipv6  SAFI: unicast

When we do trace the other spokes on spoke1, we see the traffic flow over the hub.

Ping result from spoke1 to spoke2,spoke3, and Internet;



Thanks for Reading.





353 views0 comments