Transcript Document

MASTERING (VIRTUAL) NETWORKS
A Case Study of Virtualizing Internet Lab
Avin Chen
Borokhovich Michael
Goldfeld Arik
1
Agenda
2

Introduction

Related Work

Virtualization

Virtual Lab Design

Students’ & Administrator’s

Conclusions & Future Work
Introduction

The need for computer networks lab
–
–
–
Computer engineering
Electrical engineering
Communication systems engineering
Internet
Router
Computer 1
Router
Router
Router
3
Computer 2
Working in Network Lab

Assignment document
–

Build network
Configure devices
–
–
IP Addresses
Routing protocols

Send messages

Capture messages
Take measurements

Related Work
5

Physical (real) lab

Simulation

Emulabs

Virtualization (MLN, VMware, Virtual PC)
Physical (real) laboratory

Pros:
–
–

Cons:
–
–
–
–
6
Real equipment
“Hands on”
Cost
Space
Time
Energy
Related Work
7

Physical (real) lab

Simulation

Emulabs

Virtualization (MLN, VMware, Virtual PC)
Simulation (NS2, OPNET…)

Pros:
–
–

Cons:
–
–
–
8
Scalable
Cost effective
Not a real equipment
Not a “hands on”
Simulation tools are complex
Related Work
9

Physical (real) lab

Simulation

Emulabs

Virtualization (MLN, VMware, Virtual PC)
Virtualization

One physical machine
Many independent operating systems
Operating system = Virtual machine

Virtualization Platforms:


Server 1
Utilization 15%
–
–
–
Server 2
Utilization 15%
Virtual PC
VMware
Xen
Server 3
Utilization 15%
Server 4
Utilization 15%
Server 5
Utilization 15%
Applications Applications
Virtualization
Operating
System 1
Operating
System 2
Applications
Operating
System N
Virtualization
Server Platform
Utilization 75%
Physical Host Hardware – CPU, Memory, Disk, Network
Virtualization Benefits
11

Increase utilization

Lower number of physical machines

Simple management

Isolation

Different operating systems on a single computer
Virtual Lab Design

“Mastering Networks” book of Liebeher and
El Zakri

Set of equipment:
–
–
–
12

4 PCs
4 Routers
8 Switches
We call this set - NetLab
Virtual Lab Design

Instead of real NetLabs – virtual NetLabs
Single physical server
Virtualization platform - Xen NETLAB

15 Virtual NetLabs


Virtualization
Xen allows many VM
Xen is freeware
NETLAB
NETLAB 1
2
PC1NETLAB Router1
PC1,PC2
PC3,PC4
Router1
Router2
Router3
Router4
PC1,PC2
PC3,PC4
PC2
PC3
SW x 8
SW1
SW2
PC3,PC4
SW3
SW4
Router2
Router1
Router2
Router3
Router4
SW5
SW6
SW7
SW8
Router3
Router4
Virtualization Platform - Xen
13
=
PC1,PC2
PC3,PC4
Router1
Router1Router2
Router2Router3
Router3
Router4
Router4
SW x 8 SW x 8
SW x 8
PC4
NETLAB 15
PC1,PC2
Physical Host Hardware
Students’ Perspective

14
Almost the same as real
NETLAB 1
NETLAB 2
NETLAB 15
PC1,PC2
PC3,PC4
PC1,PC2
PC3,PC4
PC1,PC2
PC3,PC4
Router1
Router2
Router3
Router4
Router1
Router2
Router3
Router4
Router1
Router2
Router3
Router4
SW x 8
SW x 8
SW x 8
Virtualization Platform - Xen
Physical Host Hardware
Students’ Perspective

Anytime, anywhere
Laboratory
Campus
Internet
15
Home
NETLAB 1
NETLAB 2
NETLAB 15
PC1,PC2
PC3,PC4
PC1,PC2
PC3,PC4
PC1,PC2
PC3,PC4
Router1
Router2
Router3
Router4
Router1
Router2
Router3
Router4
Router1
Router2
Router3
Router4
SW x 8
SW x 8
SW x 8
Virtualization Platform - Xen
Physical Host Hardware
Students’ Perspective

16
Building Networks
Students’ Perspective

Access
–
–
17
Virtual device – unique display number
Remote access - VNC
Students’ Perspective

Virtual PC
–
–

Virtual Router
–
–
–
18
Linux OS
Graphical Desktop
Linux OS
Quagga
CISCO like
Administrator’s Perspective

Topologies Preparation
–
Simple text file defines the topology
Administrator
pc1 sw1
pc2 sw2 troubleshooting
 Remote
router1 sw1 sw2
–
–
–
Restore VNC displays
Restart machines
Replace damaged machines
PC2
PC1
19
SW1
Router1
SW2
Student
Extended Topologies

NetLab_(x+1)
NetLab_(x+1)
NetLab_x
Physical Lab – Small Networks
eth0
10.0.1.11
PC1
AS 100
AS 200
eth0
10.0.1.1

eth0
10.0.1.11
eth0
10.2.1.12
Virtual Lab – Any Networks
PC1
Router1
eth1
10.0.2.1
eth0
10.2.1.1
PC2
switch
Router2
eth0 eth1
10.0.2.14
10.2.2.1
eth0
10.0.1.1
PC4
eth1
10.0.2.1
Router1

eth0
10.0.2.13
BGP lab
eth0
10.2.2.14
eth1
PC3
10.0.2.2
eth0
10.0.3.2
eth1
PC4
10.0.2.3
eth0
10.0.5.3
hub
Router2
Router1
NetLab_x

Multicast lab
eth0
10.0.3.12
PC2
eth0
10.0.5.11
hub
eth1
10.0.2.2
hub
eth1
10.2.2.2
AS 300
eth0
10.3.1.2
eth0
10.0.3.3
eth0
10.0.5.2
eth1
10.0.4.3
eth1
10.0.6.2
Router1
eth0
10.3.1.1
Router3
eth1
eth0
10.3.2.12
10.3.2.1
Router2
eth0
eth1
10.3.3.12
Router3
switch
switch
eth0
10.3.1.11
20
Router4
eth1
10.3.4.1
10.3.3.1
PC2
Router2
PC1
eth0
10.3.4.2
eth0
10.0.4.13
eth0
10.0.4.14
eth0
10.0.6.12
eth0
10.0.6.13
PC3
PC4
PC2
PC3
PC1
eth0
10.3.4.13
PC3
System Features
21

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

–
Lab Administrator

–
Install Linux, Xen, Virtual Machines
Basic Linux and Networks knowledge
Lab Instructor

Networking and Linux knowledge
Conclusions & Future Work

Conclusions
–
–
–
–

Future work
–
–
23
Excellent students’ feedbacks
Almost full “hands on” lab
Saving cost, space, time and energy
Easy administration
–
Further experiments developing
Increase system capacity
Graphical interface to create topologies
Thank You!
24
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


25

64 MB RAM
Quagga Routing Suite
Packet Tracing Software: Tcpdump, Wireshark