The test bed using SDN Technology and NVGRE VPN tunneling protocol. VIT Vellore presentation by Ankita Mandekar.

1. Presentation by:-
Ankita Vinod Mandekar (13MIT0108)
1st year MTech IT(Networking),
School of Information Technology and Engineering,
VIT University
Guided by:-
Dr. Krishna Chandramouli
Associate Professor,
Division of Enterprise and Cloud Computing,
School of Information Technology and Engineering,
VIT University
VIT,Vellore

2. Outline:
1. Traditional Network
2. Centralized network
3. Architecture
4. Software Defined Testbed Cloud
5. Network Virtualization Tunnelling Protocol
6. Conclusion
7. References

3. router
router
server
172.16.68.1
tracert vit.ac.in
115.248.50.1
218.100.48.152
182.19.48.240
Traditional Network
• Distributed Routing
• High latency
• Reduced throughput
• Unmanageable Network
• Ossification of network
• Congestion
• Network Infrastructure
complexities

4. Controller
Network Devices
Distributed Network
Centralized Network

5. Architecture of Software Defined Network Test
Bed

6. Components of SDT
1. SDT Cloud
2. Client Network

7. 1. SDT Cloud
1. 1 Domain Name Server
• Domain “sdt.sdntestbed.com”
• The Domain Controller and DNS is
on the Host_SDT_1
• Active Directory Domain System
Menu Bar of Server Manger
with DNS, AD DS, Hyper-V on
Host_SDT_1
Online System on
the domain
sdt.sdntestbed.com

8. 1.2 Hyper Visor
• Hyper-V is the software on the top of the operating
system of the server
• Software Based of Data link layer of Network
• In SDT cloud, on
Host_SDT_1,Host_SDT_2,Host_SDT_5,Host_SDT_6.
Microsoft Windows 2012 R2
server Hyper Visor
Virtual
Machine

9. 1.3 System Centre Virtual Machine Manager
VM_Client_1 VM_Client_2
SDT_Host_2
Cleint_1 VM Network
Client_2 VM Network
Customers Virtual
Machine on the
SDT cloud
Menu Bar SCVMM Showing the
topology of Virtual Machine
• Virtual Machine Manager
• Centralize the Cloud Network
• View Network Topology-
Maintenance
• Management
• Security
• Resource Management

10. 1.4 Open Flow Switch
• Separation of control plane from the
data plane
• Enabled with OpenFlow Protocol
with parameters:-
1. Header fields
2. Counters
3. Action

11. 2. Client Network
• Two Client Network Client_1 and Client_2
• Internet Service Provider with Following IP provided to cloud and customers
Host IP addresses
ONF_SDT_2 131.107.0.1
Host_SDT_3 131.107.0.30
Host_SDT_4 131.107.0.40
Host_SDT_5 131.107.0.2
Host_SDT_6 131.107.0.5

12. Methodology Used
1. Software Defined Network
• Centralizes the Cloud Network
• Flow based Forwarding using Open Flow Enabled Network Devices
• SCVMM Controller Manages, Maintains the Private Network Topology
• Access Control Plugin on Controller

13. 2. Network Virtualization Generic Routing Encapsulation
• Virtual Private Network
• Virtualization GRE tunnelling protocol
• Unique Virtual Subnet ID
• Unique Client ID
• Encapsulation at source
• Original Packet retrieval at Destination

14. Results
Software Defined Network
• Centralized Network on the
Single host Host_SDT_2 in
SDT cloud
• Secure from Single point
• Flow based Forwarding
using OpenFlow Protocol
• Manageable Virtual
Machine hosted in the
cloud

15. Virtual Private Network with NVGRE tunnelling protocol
• Successful reachable from Clients private
Network to the Virtual Machine hosted on SDT
Cloud
• Ping to the expected Virtual Machine
• Unique Client ID for Client identity
• Unique Subnet ID for the Private IP of Clients
Private Network

16. Conclusion
1. Centralized programmable device SCVMM Controller manages, monitor the physical as
well as virtual systems in the cloud.
2. The OpenFlow enabled Switch have flow table with attributes as matches, ingress port,
and decision flow. The traffic from same source and destination follows same topology.
Thus, the flow based forwarding increasing throughput.
3. Using this technology, the proper distribution of bandwidth is made to provide the
uniform and fast access to virtual Operating System located on the server.
4. Operating System Virtualization results in less infrastructure requirement which is cost
effective.
5. The NVGRE tunnelling protocol provides secure and specific reachability to the
destination on virtual network of cloud.

17. References
1. In Open Network Foundation: OpenFlow Switch Specification version 1.3.1 (wire
protocol) September 2012.
[https://www.opennetworking.org/images/stories/downloads/sdn-
resources/onf-specifications/openflow/openflow-spec-v1.3.1.pdf]
2. Enterasys Secure Network: Software Defined Network (SDN) in the Enterprise”,
June 2013.
[http://www.npgusa.com/images/Enterasys_Software_Defined_Networks.pdf]
3. Oren Laadan, Jason Nieh, “Operating System Virtualization: Practice and Experience,
May 2010.
[http://www.cs.columbia.edu/~orenl/papers/systor2010_osvirt.pdf]
4. Oren Laadan, Jason Nieh Test Lab Guide: “Windows Server 2012 R2Hyper-V Network
Virtualization with System
Center 2012 R2 VMM Operating System Virtualization: Practice and Experience.
[http://www.systemcentercentral.com/test-lab-guide-windows-server-2012-r2-hyper-
v-network-virtualization-with-system-center-2012-r2-vmm-2/]
5. Nick McKeown, Tom Anderson, and Hari Balakrishnan “OpenFlow: Enabling
Innovation in Campus Network” , December 2008.
[http://archive.openflow.org/documents/openflow-wp-latest.pdf]