Deployment Documentation.1.5v

VERSA HEAD END
COMPONENTS DEPLOYMENT
DATACIPHER SOLUTIONS PRIVATE LIMITED HYDERABAD

VERSA Head End components Deployment
Contents
Topology ................................................................................................................................................................................. 2
DIRECTORS DEPLOYMENT ...................................................................................................................................................... 3
Director-1 Deployment ...................................................................................................................................................... 3
Director-2 Deployment .................................................................................................................................................... 10
Director HA ....................................................................................................................................................................... 11
ROUTERS DEPLOYMENT AS SERVICE VNF............................................................................................................................ 16
Initial Deployment............................................................................................................................................................ 16
Tunnel Interfaces(Tvi) Configuration For Ipsec. .............................................................................................................. 27
Virtual Router Configuration ........................................................................................................................................... 30
Ipsec Configuration .......................................................................................................................................................... 35
IBGP Over Ipsec ................................................................................................................................................................ 39
Vrrp Configuration............................................................................................................................................................ 45
Exporting the Direct routes via BGP for reachability ...................................................................................................... 51
ANALYTICS CLUSTER DEPLOYMENT ..................................................................................................................................... 55
1st CLUSTER Deployment .................................................................................................................................................. 56
2nd CLUSTER Deployment ............................................................................................................................................... 62
CONTROLLERS DEPLOYMENT ............................................................................................................................................... 68
1|Page
Topology
2|Page
DIRECTORS DEPLOYMENT
Director-1 Deployment
➢ Log in to the VMware ESXi server.
➢ Deploy the Virtual Machine from an OVF or OVA File
3|Page
➢ Enter name for Virtual machine and Click to Select Files or Drag/Drop to upload the OVF and VMDK files.
4|Page
➢ Map the interface to the appropriate network, here it is mapped to the management network
5|Page
➢ Review the settings
6|Page
➢ Minimum two interfaces are needed for Director Setup.

❖ North Bound: Out of band management Interface
❖ South Bound: Control interface which connects other components
➢ When Director VM is deployed only one network adaptor is created, so another network adaptor needs to be
created.
Below is the method to create second network adaptor
❖ Network adaptor1: North bound (Out of bound Management)

❖ Network adaptor2: South bound (Control Network)
7|Page
➢ Power on the Director Virtual machine.
➢ After VM power’s on, login to the VM console
8|Page
➢ Default Login Credentials:

Username: admin
Password: versa123
➢ Run the startup script on the Director:
sudo /opt/versa/vnms/scripts/vnms-startup.sh
9|Page
Director-2 Deployment
Follow the similar procedure which is used to deploy Director-1
10 | P a g e
Director HA
➢ Login to the Director-1 GUI
11 | P a g e
✓ Default credentials:
Username: Administrator
Password: versa123
➢ Navigate to Administration-->System-->High Availability
➢ Provide the Master IP and Slave IP Address details

❖ Master IP Address: Director-1 Mgmt IP Address
❖ Slave IP Address: Director-2 Mgmt IP Address
12 | P a g e
➢ Click on the Tasks to check the progress.
➢ Click on Refresh to check the current status
13 | P a g e
➢ After Successful HA Deployment below output is seen in GUI
14 | P a g e
➢ CLI command to check the HA status on the Director.

Administrator@Versa-Director-1> request vnmsha actions get-vnmsha-postgres-status
➢ After successful HA configuration, below output is expected on the slave Director
15 | P a g e
ROUTERS DEPLOYMENT AS SERVICE VNF

Initial Deployment
Router-1 Deployment
✓ Note : For Router deployment Flexvnf is used. VM creation in the ESXI server is not shown below, for reference
look into the Director VM creation in the ESXI server which is shown in the starting of the document
➢ Add required number of network adaptors to the Router VM. Here for this router, total 5 network adaptors are
required.
16 | P a g e
➢ Power on the Router-1 VM
➢ Login to the console of Router-1
Default credentials:
Username: admin
Password: versa123
17 | P a g e
➢ Configure the out of management interface of Router-1

[admin@Router-1: ~] $ sudo nano /etc/network/interfaces
Note: To write the changes use CTRL+O and press ENTER. To discard the changes, use CTRL+X
18 | P a g e
➢ To Add Router-1 in the Director Navigate to Administrator-->Local-->Resource Pool
➢ Provide the Router name and Mgmt IP information
19 | P a g e
➢ To allocate the resources for the router, organization needs to be created
➢ Provide the Organization name and add the required number of interfaces.
20 | P a g e
➢ Associate the organization to the routers.
21 | P a g e
➢ Create the Parent organization
22 | P a g e
23 | P a g e
➢ Add the router in the Appliances
24 | P a g e
➢ Provide the IP details
25 | P a g e
26 | P a g e
Tunnel Interfaces(Tvi) Configuration For Ipsec.
➢ Two interfaces need to be created i.e. tvi-0/1 and tvi-0/2
27 | P a g e
28 | P a g e
29 | P a g e
Virtual Router Configuration
➢ Create VRs with the name of Control-VR and Transport-VR on the Router
❖ Add eth4 in Transport VR
❖ Add eth1, eth2 , eth3, tvi-0/1 and tvi-0/2 in Control-VR
Note: Click on Build before creating the VRs so that it doesn’t activate the changes
30 | P a g e
➢ Provide the VR name and add the interfaces into that VR
31 | P a g e
➢ Associate the newly configured VRs with the Provider organization
32 | P a g e
➢ Only required services needs to be enabled, rest needs to be unselected
33 | P a g e
➢ Issue Commit
34 | P a g e
Ipsec Configuration
➢ Site to Site IPSEC VPN tunnels need to be configured between (Router-1 to Router-3) and (Router-1 to Router-4)
✓ tvi-0/1: Router-1 to Router-3

✓ tvi-0/2: Router-1 to Router-4
➢ Provide the below details to create the IPSEC-VPN between Router-1 to Router-3
35 | P a g e
➢ Below output is seen after IPSEC VPN tunnel is created
36 | P a g e
➢ Provide the below details to create the IPSEC-VPN between Router-1 to Router-4
37 | P a g e
➢ Below output is seen after IPSEC VPN tunnel is created
38 | P a g e
IBGP Over Ipsec
➢ Full mesh IBGP is configured between Router-1 to Router-3 and Router-1 to Router-4 over existing Site to Site
IPSEC VPN
39 | P a g e
➢ Navigate to Peer Group to create BGP group
40 | P a g e
➢ Provide the neighbor tvi-0/1 IP address of Router-3 i.e. 172.16.101.2
41 | P a g e
➢ Similarly Provide the neighbor tvi-0/1 IP address of Router-4 i.e. 172.16.102.2
42 | P a g e
43 | P a g e
Router-2 Deployment
Follow the similar procedure of Router-1
Router-3 Deployment
Router-4 Deployment
44 | P a g e
Vrrp Configuration
Router-1 and Router-2 VRRP Configuration
On Router-1:
45 | P a g e
46 | P a g e
On Router-2:
47 | P a g e
Check if VRRP is properly configured
On Router-1
On Router-2
48 | P a g e
Static route configuration with VIP address as the gateway
➢ Configure the static route on below devices to reach other networks and gateway should be VIP IP of the router
▪ Director-1
▪ VAN-1
▪ VSN-1
▪ LCF-1
▪ LCF-2
➢ Static route command

▪ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.1.11
To check the routing table
admin@Versa-Director-1:~$ route -n
49 | P a g e
Router-3 and Router-4 VRRP configuration
Router-3 VRRP configuration
➢ Follow the similar procedure done on Router-1 and Router-2
Router-4 VRRP configuration
➢ Follow the similar procedure done on Router-1 and Router-2
Static route configuration with VIP address as the gateway
➢ Configure the static route on below devices to reach other networks and gateway should be VIP IP of the router
▪ Director-2
▪ VAN-2
▪ VSN-2
▪ LCF-3
▪ LCF-4
➢ Static route command

▪ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.11.11
➢ To check the routing table
admin@Versa-Director-2:~$ route -n
50 | P a g e
Exporting the Direct routes via BGP for reachability
Router-1 :
51 | P a g e
52 | P a g e
53 | P a g e
Router-2 :
Follow the same procedure as used in Router-1
Router-3 :
Router-4 :
54 | P a g e
ANALYTICS CLUSTER DEPLOYMENT

➢ Here in this setup two separate Analytics clusters will be deployed.
➢ Before we start the setup, we need to download van_cluster_config.tar file
van_cluster_config.t
ar
Copy the above file to the Director.
➢ Extract the contents of the file.

admin@Versa-Director-1:~$ tar -xvf van_cluster_config.tar
❖ Note : As 2 clusters are being deployed , 2 separate configuration files, cluster installer files and cluster
monitor files needs to be created based on clustersetup.conf , van_cluster_installer.py and
van_cluster_monitor.py which will be present at van-cluster-config/van_cluster_install location.
➢ For 1st Analytics cluster , below files are created.
VAC-1.conf VAC-1_cluster_insta VAC-1_cluster_moni

ller.py tor.py
➢ For 2nd Analytics cluster below files are created.
VAC-2.conf VAC-2_cluster_insta VAC-2_cluster_moni

ller.py tor.py
55 | P a g e
1st CLUSTER Deployment

➢ In this setup, 4 Analytics nodes are required
✓ 1 instance for Analytics personality.
✓ 2 instances for Log Collector and Forwarder personality.
Note: Here Analytics VM creation is not shown, for reference go through the Director VM creation steps.
➢ Login to the console of Analytics node personality from Cluster-1 and configure the interfaces
[versa@Analytics-Node-1: ~] $ sudo nano /etc/network/interfaces
auto eth0
iface eth0 inet static
address 10.192.114.11
netmask 255.255.0.0
gateway 10.192.0.1
auto eth1
address 172.16.2.1
netmask 255.255.255.0
auto eth2
address 172.16.1.6
netmask 255.255.255.0
56 | P a g e
➢ Login to the console of Search node Personality from Cluster-1 and configure the interfaces
[versa@Search-Node-1: ~] $ sudo nano /etc/network/interfaces

auto eth0
address 10.192.114.12
netmask 255.255.0.0
gateway 10.192.0.1
auto eth1
address 172.16.2.2
netmask 255.255.255.0
auto eth2
address 172.16.1.7
netmask 255.255.255.0
57 | P a g e
➢ Login to the console of 1st Log forwarder node from Cluster-1 and configure the interfaces
[versa@LCF-1: ~] $ sudo nano /etc/network/interfaces
# The primary network interface

auto eth0
address 10.192.114.13
netmask 255.255.0.0
gateway 10.192.0.1
auto eth1
address 172.16.1.4
netmask 255.255.255.0
auto eth2
address 172.16.2.3
netmask 255.255.255.0
58 | P a g e
Login to the console of 2nd Log forwarder node from Cluster-1 and configure the interfaces

auto eth0
address 10.192.114.14
netmask 255.255.0.0
gateway 10.192.0.1
auto eth1
address 172.16.1.5
netmask 255.255.255.0
auto eth2
address 172.16.2.4
netmask 255.255.255.0
59 | P a g e
➢ Login to the CLI of the Director and run the installer script of cluster-1
admin@Versa-Director-1:~$ cd van-cluster-config/van_cluster_install/
admin@Versa-Director-1:~/van-cluster-config/van_cluster_install$ python VAC-1_cluster_installer.py --force
➢ After the installation, script needs to be run for the second time for post-installation procedures
admin@Versa-Director-1:~/van-cluster-config/van_cluster_install$ python VAC-1_cluster_installer.py --post-setup --force
➢ Add Analytics cluster in the Director. Cluster-name should be the name of the actual cluster
60 | P a g e
➢ On all 4 nodes in the Analytics-Cluster-1 nodes static route needs to be added to reach the controllers , Gateway should
be VIP
[versa@Analytics-Node-1: ~] $ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.1.11
[versa@Search-Node-1: ~] $ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.1.11
[versa@LCF-1: ~] $ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.1.11
61 | P a g e
2nd CLUSTER Deployment
➢ In this setup, 4 Analytics nodes are required

✓ 2 instances for Log Collector and Forwarder personality.
Note: Here Analytics VM creation is not shown, for reference go through the Director VM creation steps.
➢ Login to the console of Analytics node personality from Cluster-2 and configure the interfaces
[versa@Analytics-Node-2: ~] $ sudo nano /etc/network/interfaces
# MANAGEMENT INTERFACE
auto eth0
address 10.192.114.15
netmask 255.255.0.0
gateway 10.192.0.1
# CONTROLNET INTERFACE
auto eth1
address 172.16.12.1
netmask 255.255.255.0
# INTERNAL INTERFACE
auto eth2
address 172.16.11.6
netmask 255.255.255.0
62 | P a g e
➢ Login to the console of Search node Personality from Cluster-2 and configure the interfaces
[versa@Search-Node-2: ~] $ sudo nano /etc/network/interfaces

auto eth0
address 10.192.114.16
netmask 255.255.0.0
gateway 10.192.0.1
# CONTROL INTERFACE
auto eth1
address 172.16.12.2
netmask 255.255.255.0
# INTERNAL INTERFACE
auto eth2
address 172.16.11.7
netmask 255.255.255.0
63 | P a g e
➢ Login to the console of 1st Log forwarder node from Cluster-2 and configure the interfaces

auto eth0
address 10.192.114.17
netmask 255.255.0.0
gateway 10.192.0.1
auto eth1
address 172.16.11.4
netmask 255.255.255.0
auto eth2
address 172.16.12.3
netmask 255.255.255.0
64 | P a g e
➢ Login to the console of 2nd Log forwarder node from Cluster-2 and configure the interfaces

auto eth0
address 10.192.114.18
netmask 255.255.0.0
gateway 10.192.0.1
auto eth1
address 172.16.11.5
netmask 255.255.255.0
auto eth2
address 172.16.12.4
netmask 255.255.255.0
65 | P a g e
➢ Login to the CLI of the Director and run the installer script of cluster-2
admin@Versa-Director-1:~$ cd van-cluster-config/van_cluster_install/
admin@Versa-Director-1:~/van-cluster-config/van_cluster_install$ python VAC-2_cluster_installer.py –force
➢ After the installation , script needs to be run for the second time for post-installation procedures
admin@Versa-Director-1:~/van-cluster-config/van_cluster_install$ python VAC-2_cluster_installer.py --post-setup –force
➢ Add 2nd Analytics cluster in the Director. Cluster-name should be the name of the actual cluster
66 | P a g e
➢ On all 4 nodes in the Analytics-Cluster-2 nodes add static route to reach the controller , Gateway should be VIP
[versa@Analytics-Node-2: ~] $ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.11.11
[versa@Search-Node-2: ~] $ sudo route add -net 172.16.0.0 netmask 255.255.0.0 gw 172.16.11.11
67 | P a g e
CONTROLLERS DEPLOYMENT
Controller-1 Deployment:
Note: Here flexvnf VM creation is not shown, for reference go through the Director VM creation steps.
➢ Login to the console of the Controller-1
Default credentials
Username: admin
Password: versa
Configure the Management Interface:
[admin@Controller-1: ~] $ sudo nano /etc/network/interfaces
auto eth0
address 10.192.114.7
netmask 255.255.0.0
gateway 10.192.0.1
68 | P a g e
Next Login to the Director :
Navigate to workflows-->Infrastructure -->Controllers
69 | P a g e
70 | P a g e
NOTE: we are supposed to create 2 South bound interfaces. In below slide we are only creating one interface but in later
stage , another interface will be create
71 | P a g e
72 | P a g e
73 | P a g e
Create another south bound interface(control)
74 | P a g e
75 | P a g e
➢ Add the newly configured vni-0/1 interface in the respective Provider-control-VR and has to be associated in
limits and finally must be called in zones
➢ Click on build which is present on top right side and then Provider-Control-VR.
76 | P a g e
77 | P a g e
78 | P a g e
79 | P a g e
➢ After above steps completed , issue commit.
80 | P a g e
EBGP configuration
81 | P a g e
82 | P a g e
83 | P a g e
Similar EBGP configuration needs to be done on Router-1 and Router-2 as per in the topology.
84 | P a g e
➢ Follow similar steps which has been performed for controller-1 deployment.
85 | P a g e

Deployment Documentation.1.5v

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deployment Documentation.1.5v

Uploaded by

Copyright:

Available Formats

VERSA HEAD END

DATACIPHER SOLUTIONS PRIVATE LIMITED HYDERABAD

➢ Log in to the VMware ESXi server.

➢ Deploy the Virtual Machine from an OVF or OVA File

➢ Review the settings

➢ Minimum two interfaces are needed for Director Setup.

Below is the method to create second network adaptor

❖ Network adaptor1: North bound (Out of bound Management)

➢ Power on the Director Virtual machine.

➢ After VM power’s on, login to the VM console

➢ Default Login Credentials:

➢ Run the startup script on the Director:

Follow the similar procedure which is used to deploy Director-1

➢ Login to the Director-1 GUI

➢ Navigate to Administration-->System-->High Availability

➢ Provide the Master IP and Slave IP Address details

➢ Click on the Tasks to check the progress.

➢ Click on Refresh to check the current status

➢ After Successful HA Deployment below output is seen in GUI

➢ CLI command to check the HA status on the Director.

➢ After successful HA configuration, below output is expected on the slave Director

ROUTERS DEPLOYMENT AS SERVICE VNF

➢ Power on the Router-1 VM

➢ Login to the console of Router-1

➢ Configure the out of management interface of Router-1

➢ To Add Router-1 in the Director Navigate to Administrator-->Local-->Resource Pool

➢ Provide the Router name and Mgmt IP information

➢ To allocate the resources for the router, organization needs to be created

➢ Associate the organization to the routers.

➢ Create the Parent organization

➢ Add the router in the Appliances

➢ Provide the IP details

Tunnel Interfaces(Tvi) Configuration For Ipsec.

➢ Two interfaces need to be created i.e. tvi-0/1 and tvi-0/2

Virtual Router Configuration

➢ Provide the VR name and add the interfaces into that VR

➢ Associate the newly configured VRs with the Provider organization

➢ Only required services needs to be enabled, rest needs to be unselected

✓ tvi-0/1: Router-1 to Router-3

➢ Below output is seen after IPSEC VPN tunnel is created

➢ Below output is seen after IPSEC VPN tunnel is created

IBGP Over Ipsec

➢ Navigate to Peer Group to create BGP group

➢ Provide the neighbor tvi-0/1 IP address of Router-3 i.e. 172.16.101.2

➢ Similarly Provide the neighbor tvi-0/1 IP address of Router-4 i.e. 172.16.102.2

Follow the similar procedure of Router-1

Follow the similar procedure of Router-1

Follow the similar procedure of Router-1

Router-1 and Router-2 VRRP Configuration

Check if VRRP is properly configured

Static route configuration with VIP address as the gateway

➢ Static route command

To check the routing table

Router-3 and Router-4 VRRP configuration

Router-3 VRRP configuration

➢ Follow the similar procedure done on Router-1 and Router-2

Router-4 VRRP configuration

➢ Follow the similar procedure done on Router-1 and Router-2

Static route configuration with VIP address as the gateway

➢ Static route command

➢ To check the routing table

Exporting the Direct routes via BGP for reachability

Follow the same procedure as used in Router-1

Follow the same procedure as used in Router-1