1.

3 Introduction to Network Programmability

Traditional versus Software-Defined

Networks

Open Transcript

The Traditional Network

Control plane learns/computes forwarding decisions.

Data plane acts on the forwarding decisions.

The picture shows the type of network you have all worked on for the past 20+ years. Each device has a control
and data plane. It means that all devices are equally smart and can make decisions on their own since the control
plane exists. Of course, the data plane is what is responsible for the actual packet forwarding, for example, ASIC.
It is now referred to as the traditional network, but it still is the dominant network type deployed.
The Network As It Could Be…to an SDN ‘Purist’

Control plane becomes centralized

Physical device retains data plane functions only

As SDN first emerged, there was the thought that the control plane must be removed each device and that the
control plane must be centralized into what is called an SDN controller.

While there are a few benefits to this approach in that you can evolve the control plane protocols independently of
the hardware while now having a central point control, there was significant scaling problems with this approach.

The Network As It Could Be…In a ‘Hybrid SDN’

A Controller is centralized and separated from the Physical Device, but devices still retain localized Control
plane intelligence.

Another option is a combination of the best of both worlds. First, you can recognize that traditional routing
protocols work and scale well. If you remember, BGP is what makes the Internet work today! Also, if a controller
was used, it can still offer that single pane of glass and administration while offering an API. It would be a single
API to interface to the network as opposed to SSHing to N network device to make a change or retrieve data. If
you learned one thing in the industry over the past 10 years from when SDN emerged, it is that you need to get
better at network operations.

Why Change?

Familiar Manual, CLI-driven, device-by-device approach is inefficient

Increased need for programmatic interfaces which allow faster and automated execution of processes and
workflows with reduced errors

Need for a ‘central source of truth’ and touch-point

The SDN movement was started to re-architect packet forwarding techniques, but realized the real improvement
was needed in network operations. There is a drive now to eliminate access to CLI (and GUI) to minimize
touchpoints on the network. You need to stop managing devices one at a time and stop using commands that
return a “blob” of raw text. Rather, you need better programmatic interfaces, that offer a means to automate, while
working with structured objects such as XML or JSON.

Your Challenges:

Pace of Change – Technology & Competition

Globalization of the Marketplace

Proliferation of Social Networking

IT Budgets, Staffing, and Resources

Accelerated Pace of Consumerization, Virtualization, and XaaS Options

Consumption Economics

While every industry is different, there are new challengers emerging every day. Brick and Mortar are being
challenged by small companies that have no physical location and access to a global shipping system. These
companies are leveraging the full power of the cloud and software to the fullest—everything is being automated by
the upstarts. It is how you need to be thinking about networking to get control of the networks today before they
completely grow out of control!

The bottom line is, in order to remain competitive, you need to learn how to do more with less. If it means simply
checking inventory, serial numbers, or getting ready for anIPv6 migration, you need to start designing and thinking
about network management much differently.

Content Review Question

Which of the following are reasons to implement SDNs in the network. (Choose two.)

A device-by-device approach is more efficient

Increased need for programmatic interfaces which allow faster and automated execution of processes
and workflows with reduced errors

Decreased programmability and cost to deploy

Need for a ‘central source of truth’ and touch-point.

Submit