jennifer rexford princeton university mw 11:00am-12:20pm sdn software stack cos 597e: software...
TRANSCRIPT
![Page 1: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/1.jpg)
Jennifer RexfordPrinceton University
MW 11:00am-12:20pm
SDN Software StackCOS 597E: Software Defined Networking
![Page 2: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/2.jpg)
2
Background: Enterprise Networks and VLANs
![Page 3: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/3.jpg)
Simple Enterprise Design• Single layer-two subnet– Hubs and switches– Gateway to the Internet– Single IP address block
• Local services–DHCP–DNS
3
S
S
S
G
SDHCP server
DNS server
1.2.3.1
1.2.3.76
1.2.3.51.2.3.150
Internet
1.2.3.0/24
0.0.0.0/0
![Page 4: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/4.jpg)
Limitations of Simple Design• Scalability– Large switch tables– Flooding overhead– Broadcast (ARP, DHCP)
• Performance– Spanning tree
• Security– No access control– No isolation
4
S
S
S
G
SDHCP server
DNS server
1.2.3.1
1.2.3.76
1.2.3.51.2.3.150
Internet
1.2.3.0/24
0.0.0.0/0
![Page 5: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/5.jpg)
5
Hybrid of Switches and Routers
R
R
R
R
Ethernet Bridging - Flat addressing - Self-learning - Flooding - Forwarding along a tree
IP Routing - Hierarchical addressing - Subnet configuration - Host configuration - Forwarding along shortest paths
R
1.2.3.192/26
1.2.3.128/26
1.2.3.0/26
1.2.3.64/26
Internet
![Page 6: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/6.jpg)
6
Virtual Local Area Networks
• Group related hosts– Same company – Same role (e.g., faculty vs. students)– All WiFi users
• Treat them as a single LAN– Single IP address block– Single broadcast domain– No access control
• Independent of their locationRewire the network in software!
![Page 7: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/7.jpg)
7
Example: Two VLANs
Red VLAN and Orange VLANSwitches forward traffic as needed
R
O
RO
R
R
R
OOOR OR R R
O
O
O
![Page 8: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/8.jpg)
8
Making VLANs Work
• Changing the Ethernet header– Adding a field for a VLAN tag– Implemented on the bridges/switches– … but can interoperate with old Ethernet cards
• Bridges/switches trunk links– Say which VLANs are accessible via which interfaces
• Approaches to mapping access links to VLANs– Each interface has a VLAN “color”– Each MAC address has a VLAN “color”
![Page 9: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/9.jpg)
9
VLANs in SDN
• Hybrid deployment– VLAN for SDN adopters– Remaining traffic using legacy protocols
• Switch-controller communication– Separate VLAN – Using legacy protocols
• Tagging of packets– VLAN header as a virtual “tag” on
packets
![Page 10: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/10.jpg)
10
Server Virtualizationand Virtual Switches
![Page 11: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/11.jpg)
11
Virtual Machines (VMs)
![Page 12: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/12.jpg)
12
Virtual Machine (VM)
• Virtual machine– Software implementation of a computer–With interface identical to bare hardware– Devices, interrupts, memory, page
tables, etc.
• Hypervisor (virtual machine monitor)– Creates and runs virtual machines–Manages execution of the guest OSes– Subdivides the hardware resources– Executes privileged instructions
![Page 13: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/13.jpg)
13
Motivations for VMs
• Diverse operating systems– Running software for obsolete platforms– Research, experimentation, and testing
• Sharing a single host– Server consolidation (lower cost, energy)– Isolation of applications or customers/tenants
• Fast provisioning of new servers• Snapshotting system state
– Backup and redeployment– Migrating a VM to a different host machine
• VM introspection– Track configuration settings– Identify configuration mistakes or compromises
![Page 14: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/14.jpg)
14
Virtual Switches
![Page 15: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/15.jpg)
15
SDN Software Stack
![Page 16: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/16.jpg)
16
SDN Software Stack
Network OS
Application
Switch
Switch
Switch
API
![Page 17: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/17.jpg)
17
SDN Software Stack
NOX
Application
OVS
OVS
OVS
OpenFlow
![Page 18: Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking](https://reader034.vdocument.in/reader034/viewer/2022051315/56649d9e5503460f94a882b6/html5/thumbnails/18.jpg)
18
Discussion
• What is a good “division of labor”?• Good design for the protocol?• Good abstractions for the NOS?• How apt is the “operating system”
analogy?• What parts of the system need
standards?• What are interesting SDN applications?