From the course: Practical Software-Defined Networking: 1 SDN and OpenFlow Quick Start
Unlock this course with a free trial
Join today to access over 22,600 courses taught by industry experts.
White-box switching, part 1
From the course: Practical Software-Defined Networking: 1 SDN and OpenFlow Quick Start
White-box switching, part 1
(whooshing) (engaging music) - [Instructor] This is one of multiple videos discussing SDN, network programmability, network automation, overlays, and related technologies. For years, it's been common practice in compute or server deployments that you buy your hardware from one vendor which could be HPE or Dell. You get your operating system from another vendor. So for example, you may want to run Microsoft Windows, or Linux or VMware ESXi. And then you get your applications from a third vendor or perhaps use open-source software such as Apache. So you're getting your hardware from one vendor, your network operating system from another vendor, and your applications from a third vendor. In traditional networking, a monolithic proprietary stack is used. You buy your hardware, your Operating System, and your applications from a single vendor, which could be Cisco, it could be HPE, it could be Arista, it could be Juniper. You are locked in to a proprietary network stack. That was true in…
Contents
-
-
What are software-defined networks, OpenFlow, and automation?5m 25s
-
(Locked)
What are the NBI, SBI, abstraction, and PCEP?9m 47s
-
(Locked)
What is NFV?7m 59s
-
(Locked)
What is CORD?2m 8s
-
(Locked)
Which controller should I learn?4m 58s
-
(Locked)
White-box switching, part 16m 55s
-
(Locked)
White-box switching, part 24m 49s
-
(Locked)
What is SD-WAN?2m 58s
-
(Locked)
GNS3 talks: Why learn Open vSwitch?2m 49s
-
(Locked)
NETCONF theory and is SNMP bad?11m 47s
-
-
-
-
-
-
-
-