25
1 MASTERING (VIRTUAL) NETWORKS A Case Study of Virtualizing Internet Lab Avin Chen Borokhovich Michael Goldfeld Arik
1
MASTERING (VIRTUAL) NETWORKSA Case Study of Virtualizing Internet Lab
Avin ChenBorokhovich Michael Goldfeld Arik
2
Agenda
Introduction Related Work Virtualization Virtual Lab Design Students’ & Administrator’s Conclusions & Future Work
3
Introduction
The need for computer networks lab– Computer engineering– Electrical engineering– Communication systems engineering
Computer 1 Computer 2
Router
Router
Router Router
Internet
Working in Network Lab
Assignment document– Build network
Configure devices– IP Addresses– Routing protocols
Send messages
Capture messages Take measurements
5
Related Work
Physical (real) lab
Simulation
Virtualization (MLN, VMware, Virtual PC)
Emulabs
6
Pros:– Real equipment– “Hands on”
Cons:– Cost– Space– Time– Energy
Physical (real) laboratory
7
Related Work
Physical (real) lab
Simulation
Virtualization (MLN, VMware, Virtual PC)
Emulabs
8
Pros:– Scalable– Cost effective
Cons:– Not a real equipment– Not a “hands on”– Simulation tools are complex
Simulation (NS2, OPNET…)
9
Related Work
Physical (real) lab
Simulation
Virtualization (MLN, VMware, Virtual PC)
Emulabs
Virtualization
Server 2Utilization 15%
Server 3Utilization 15%
Server 5Utilization 15%
Server 4Utilization 15%
Server 1Utilization 15%
ServerUtilization 75%
Virtualization
One physical machine Many independent operating systems Operating system = Virtual machine
Virtualization Platform
Physical Host Hardware – CPU, Memory, Disk, Network
Applications
Operating System 1
Applications
Operating System 2
Applications
Operating System N
Virtualization Platforms:– Virtual PC– VMware– Xen
11
Virtualization Benefits
Increase utilization
Lower number of physical machines
Isolation
Simple management
Different operating systems on a single computer
12
“Mastering Networks” book of Liebeher and El Zakri
Virtual Lab Design
Set of equipment:– 4 PCs– 4 Routers– 8 Switches
We call this set - NetLab
13
PC1 Router1
PC4
SW3
SW1
PC2
PC3
Router2
Router3
Router4
SW5
SW7
SW2
SW4
SW6
SW8
NETLAB
Virtual Lab Design
Instead of real NetLabs – virtual NetLabs
NETLAB
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
Virtualization Platform - Xen
NETLAB 2
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
NETLAB 15
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
NETLAB 1
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
Single physical server
Physical Host Hardware
Virtualization platform - Xen 15 Virtual NetLabs
Virtualization =Xen allows many VM
Xen is freeware
14
Students’ Perspective
Virtualization Platform - Xen
NETLAB 2
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
NETLAB 15
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
NETLAB 1
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
Physical Host Hardware
Almost the same as real
15
Students’ Perspective
Virtualization Platform - Xen
NETLAB 2
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
NETLAB 15
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
NETLAB 1
PC1,PC2PC3,PC4
Router1Router2Router3Router4
SW x 8
Physical Host Hardware
Internet
LaboratoryCampus
Home
Anytime, anywhere
16
Students’ Perspective
Building Networks
17
Students’ Perspective
Access– Virtual device – unique display number– Remote access - VNC
18
Students’ Perspective
Virtual PC– Linux OS– Graphical Desktop
Virtual Router– Linux OS– Quagga– CISCO like
19
Administrator’s Perspective
Topologies Preparation– Simple text file defines the topology
Remote troubleshooting– Restore VNC displays– Restart machines– Replace damaged machines
PC1
Router1
PC2
SW1 SW2
pc1 sw1pc2 sw2router1 sw1 sw2
Administrator Student
20
Extended Topologies
Physical Lab – Small Networks
Virtual Lab – Any Networks
BGP lab
Multicast lab
PC1
Router1
Router2 Router3PC2
PC3
Router4
PC1Router1 PC2 Router2
PC3 PC4
AS 100 AS 200
AS 300
eth010.0.1.1
eth110.0.2.1
eth010.0.1.11
eth010.0.2.13
eth110.0.2.2
eth010.2.2.14
eth010.2.1.12
eth010.2.1.1
eth110.2.2.1
eth110.2.2.2
eth010.3.4.2
eth010.3.4.13
eth110.3.4.1
eth010.3.3.1
eth110.3.3.12
eth010.3.2.12
eth110.3.2.1
eth010.3.1.1
eth010.3.1.2
eth010.3.1.11
NetLab_(x+1)
NetLab_xhub
hub hub
switch
switch switch
PC1
PC2
PC3 PC4 PC2 PC3
PC1
Router1
Router2 Router1
Router3 Router2
eth010.0.1.11
eth010.0.1.1
eth110.0.2.1
eth110.0.2.2
eth010.0.3.2
eth110.0.2.3
eth010.0.5.3
eth010.0.3.12
eth010.0.3.3
eth110.0.4.3
eth010.0.5.11
eth010.0.5.2
eth110.0.6.2
eth010.0.6.13
eth010.0.6.12
eth010.0.4.14
eth010.0.4.13
NetLab_xNetLab_(x+1)
PC4
eth010.0.2.14
21
System Features
Capacity – more than 200 virtual machines (15 NetLabs) Flexibility – any network topology Remote Access – anytime, anywhere Simple Administration Fast Failure Recovery - everyone can be a “root” In class lab sessions Open Source/Freeware Software
Lab Implementation
Equipment– One Physical Server
Staff– Linux Specialist
Install Linux, Xen, Virtual Machines– Lab Administrator
Basic Linux and Networks knowledge– Lab Instructor
Networking and Linux knowledge
23
Conclusions & Future Work
Conclusions– Excellent students’ feedbacks – Almost full “hands on” lab– Saving cost, space, time and energy– Easy administration
Future work– Further experiments developing– Increase system capacity– Graphical interface to create topologies
24
Thank You!
25
System Architecture
Single HW server– Intel Xeon Quad Core CPU x 2– 16 GB RAM– Hard Disks 250 GB x 4
Virtualization– Virtualization Platform - Xen– Hosting OS – Debian Linux 4.0– Guest OSs (Virtual Machines) – Debian Linux 4.0
64 MB RAM Quagga Routing Suite Packet Tracing Software: Tcpdump, Wireshark
