VERSA SD-WAN CONTROLLER NOTES-4
Controller Deployment;
I have finished the Director and Analytics installation. Next, I will deploy the Controller according to the following figure.
Controller default Credential;
Username:admin
Password:versa123
When you log in to the devices, you will see the FlexVNF. The same VOS ( Versa Operating System) runs on the Controller and Branches devices. You can configure the FlexVNF as the controller device or Branch device.
Set the northbound interface ip address ;
I set the northbound IP address, I will assign the soundboard interface IP address over Director.
To register Controller to Director, Workflow>Controller>+
The following figure comes up when pushing the + button;
Controller name(Required)
Create Organization (Required)
Analytic Cluster ( not required) if you didn't install the analytics. Do not need the selection.
Then Ok
For staging, I have to click the boxes (Do not forget this part). Write the controller northbound interface IP address at this step for communication between Director and Controller. If you have installed the Analytics, you can select(not required). Then continue
Set your location
This part is very important because of the control network. If this part is not properly configured, forget everything :). I will assign the controller southbound IP address at this part. The following figure shows;
for Number 4; if you want to run dynamic routing between controllers and service router, you can select the OSPF or BGP. if you select nothing. You will manually need to configure some routes.
I didn't select any option because I have only one controller and my topology is simple.
When I select the vni0/1 and vni0/2 interfaces, we can't see any created wan network. I have to create a wan network to connect to the transport domain. You can think of the transport domain as the VRF domain. I have the two Transport Domain is configured before.
vni0/1;
vni0/2;
I will assign the IP address according to my topology, click the Deploy button,
After clicking the Deploy button, Director will access the controller to push the configuration.
if you have done the correct installation. You will see the two green ticks.
Now Controller is ready for branch staging.
Monitor>networktcpip>
check with cli, the default name:versa-flexvnf changed to Controller-1.
Also, some interfaces appear the following output;
I have mentioned the vni and tvi interfaces before.
Controller routing table output;
admin@Controller-1-cli> show route
Routes for Routing instance : Analytics-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
---- ---- ----------------- -------- --- --------------
static N/A +0.0.0.0/0 169.254.0.2 00:01:38 tvi-0/603.0
conn N/A +169.254.0.2/31 0.0.0.0 00:01:37 tvi-0/603.0
local N/A +169.254.0.3/32 0.0.0.0 00:01:37 directly connected
Routes for Routing instance : Analytics-VR AFI: ipv6 SAFI: unicast
Routes for Routing instance : global AFI: ipv4 SAFI: unicast
Routes for Routing instance : global AFI: ipv6 SAFI: unicast
Routes for Routing instance : internet-Transport-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
---- ---- ----------------- -------- --- --------------
static N/A +0.0.0.0/0 192.168.60.1 00:01:39 vni-0/2.0
conn N/A +192.168.60.0/24 0.0.0.0 00:01:35 vni-0/2.0
local N/A +192.168.60.2/32 0.0.0.0 00:01:35 directly connected
Routes for Routing instance : internet-Transport-VR AFI: ipv6 SAFI: unicast
Routes for Routing instance : mpls-Transport-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
---- ---- ----------------- -------- --- --------------
static N/A +0.0.0.0/0 192.168.50.1 00:01:40 vni-0/1.0
conn N/A +192.168.50.0/24 0.0.0.0 00:01:36 vni-0/1.0
local N/A +192.168.50.2/32 0.0.0.0 00:01:36 directly connected
Routes for Routing instance : mpls-Transport-VR AFI: ipv6 SAFI: unicast
Routes for Routing instance : networktcpip-Control-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
---- ---- ----------------- -------- --- --------------
static N/A +0.0.0.0/0 0.0.0.0 00:01:39 Indirect
local N/A +10.0.0.0/32 0.0.0.0 00:01:40 directly connected
local N/A +10.0.0.1/32 0.0.0.0 00:01:40 directly connected
static N/A +10.0.0.128/25 0.0.0.0 00:01:41 Indirect
static N/A +10.0.1.0/25 0.0.0.0 00:01:41 Indirect
conn N/A +169.254.0.2/31 0.0.0.0 00:01:40 tvi-0/602.0
local N/A +169.254.0.2/32 0.0.0.0 00:01:40 directly connected
conn N/A +192.168.200.0/24 0.0.0.0 00:01:37 vni-0/0.0
local N/A +192.168.200.31/32 0.0.0.0 00:01:37 directly connected
Routes for Routing instance : networktcpip-Control-VR AFI: ipv6 SAFI: unicast
I see the routing instances in the controller routing table; These routing instances are from isolated each other.
mpls-Transport-VR
internet-Transport-VR
networktcpip-Control-VR
Thanks for reading.