# Integrated SDN-NFV 5G Network Performance and Management-Complexity Evaluation
## 4 Evaluation and Result
### Manageability Evaluation  
In this test, four scenarios were used to evaluate the manageability of the SDN-NFV combination by calculating the duration of the test. The tests carried out were the integration between the SDN controller and the VM controller, adding an integrated policy for VM instances through the SDN controller and creating an endpoint group (EPG) on the SDN controller and port-group on the distributed virtual switch (DVS). (1) SDN and VM controller integration  
The first test is to integrate the SDN controller with the VM controller, which is the beginning to combine SDN and NFV, where the two environments can be connected to each other. The initial requirements of this test are that the first VM controller has been formed, and then the interconnection between the server and the leaf switch server has also been established. After these two requirements are satisfied, integration can be initiated. To integrate the SDN controller with the VM controller, we simply need to do so in the SDN controller dashboard. Here we will create a special domain to accommodate the VM controller to be integrated by completing some basic VM controller information to be input on the dashboard. This is performed only once in one SDN controller sub-menu. Based on the process flow described in Tables 7 and 8, we created a table of the estimated time required to complete each process, so that we could determine the estimated \begin{table}
\begin{tabular}{c c c c c} \hline \hline  & **Mean Legacy** & **Mean Proposed** & \
\begin{tabular}{c} **Deviation** \\ **Standard** \\ **Legacy** \\ \end{tabular} &
\begin{tabular}{c} **Deviation** \\ **Standard** \\ **Proposed** \\ \end{tabular} \\ \hline Server Leaf & 16.01 ms & 3.91 ms & 0.07 & 0.06 \\ Border Leaf & 65.53 ms & 48.24 ms & 0.21 & 0.52 \\ \hline \hline \end{tabular}
\end{table} 
Table 6: Legacy vs. proposed latency comparison table. Figure 17: Border leaf switch latency—All week comparison. total time required for each scenario. In Table 7, we can see that the estimated time needed to complete the integration scenario between the SDN controller and the VM controller is 3 min, including checking on the VM controller side. Whereas, if only SDN is used, the integration process becomes more complicated and takes longer, as shown in Table 8. This integration is also useful in the future, which will certainly make it easier for users when going to the process to set up the two environments. Table 9 compares the estimated time in minutes required to complete the scenario of adding a new instance with the increase in the number of instances. As the number of separate SDN and NFV environment instances increases, it takes more time than integrating SDN and NFV. \begin{table}
\begin{tabular}{c c c c} \hline \hline \multirow{2}{*}{**No**} & \multirow{2}{*}{**Process Name**} & \multirow{2}{*}{**Device**} & **Measure Time** \\  & & & **(Minutes)** \\ \hline \multirow{4}{*}{1} & Access the Virtual Networking menu on & & \\  & the SDN controller to integrate the VM & & \\  & controller via the VMM-Domain & & \\  & sub-menu & & \\  & Checking on the VM controller whether & & \\  & the integration folder has appeared & VM controller & 1 \\ \hline \hline \end{tabular}
\end{table} 
Table 7: New VM controller integration measurement time via SDN controller.