It is about networks related information

1. Advanced Computer Networks
Lecture # 14

2. • Software Defined Networking
• Multi-protocol label switching (MPLS)
Contents

3. Software Defined Networking

4. Data flow is autonomously controlled by switches and routers
• F
Traditional Networking Infrastructure
 Control plane:
Routing algorithms
 Data plane:
Frame/Packet forwarding
 Management/App plane:
Configure basic activities

5. Realities of Traditional Networking
• Traditional IP networks are Complex and hard to manage
• Vendor Dependent
• Inconsistent Policies
• Network operator/Managers need to configure each individual
network device separately using vendor-specific commands
• Proprietary CLIs and APIs
• Provisioning of network services are manual, slow and prone to
errors.

6. what is Software Defined Networking?
• Software-Defined Networking (SDN) is an emerging networking
paradigm that gives hope to change the limitation of current
network infrastructure.
• The term Software Defined Networking first originated at
Stanford university in 2005 as a result of an advanced research
graduate project.
• SDN is physical separation of the network control (brain) from the
forwarding (muscle) plane.
• SDN is a step in the evolution towards programmable and active
networking
• SDN enables a network administrators to shape traffic and
deploy services to address changing business needs, without
having to touch each individual switch, router, firewall etc.

7. SDN Architecture and Components

8. • Changing Traffic Patterns:
• East-West traffic
• North-South traffic
• Traffic prioritization and QoS demands
• Varying traffic patterns
• Rising need of mobility
• The Rise of Cloud Services:
• Unprecedented growth of public and private cloud services.
• Consumerization of IT:
• Increased usage of corporate and public data via variety of devices demanding
secure infrastructure.
• “Big data” means more bandwidth
• Market research results 50 billion connected devices in 2020
Driving forces for SDN
Percentage
of
network
traffic

9. Need for SDN
• Facilitates Innovation in Network
• More flexibility with programmability
• Layered architecture with Standard Open Interfaces
• Independent innovation at each layer
• Experiment and research using non-bulky, non-expensive
equipment
• More accessibility since software can be easily developed by
more vendors
• Speed-to-market – no hardware fabrication cycles
• Ease of customization and integration with other software
applications
• Fast upgrades
• Program a network vs Configure a network

10. Where is SDN today
• Both technology and equipment are commercially available and adopted
by some huge operators including:
Google Facebook Amazon
NTT/NEC Japan Verizon Goldman sachs
• SDN is also being adopted on experimental basis by some large service
providers in conjunction with their existing legacy networks.
• Some very large equipment manufactures and networking market giants
have launched their new SDN and OpenFlow enabled switches and
routers, including:
Cisco Juniper NEC
HP Brocade Alcatel-Lucent
IBM Dell VMware

11. Future of SDN
• SDN is the future of networking.
• Every enterprise, telecom, Internet service provider–heck,
basically all big companies will eventually have to migrate
their infrastructure to an SDN.

12. Research areas in SDN
• Interoperability issues b/w SDN and Legacy Infrastructure
• Work on modification of SNMP to be used between SDN controller
and Legacy network infrastructure
• Security issues in SDN environment
• Secure transfer between SDN Layers
• Traffic engineering is SDN environment
• Optimization techniques and newer algorithms for traffic
management in:
• Datacenters (including Multitenant datacenters)
• Cloud computing
• Campus Networks
• Telecom Infrastructure
• WAN solutions
• Optimization of SDN interfaces and component
SDN controllers, switches, interfaces , Protocols , verification and
debugger tools.

13. Multi-protocol label switching (MPLS)

17. •Multi protocol: besides IP you can tunnel pretty much anything…IP,
IPv6, Ethernet, PPP, frame-relay, etc.
•Label switching: forwarding is done based on labels, not by looking
up the destination in the routing table.
What does multi protocol label switching mean?

26. MPLS Operation

27. MPLS Operation

29. What Is MPLS-Traffic Engineering
• Traffic engineering allows a network administrator to make the
path deterministic and bypass the normal routed hop-by-hop
paths. An administrator may elect to explicitly define the path
between stations to ensure QoS or have the traffic follow a
specified path to reduce traffic loading across certain hops.
• The network administrator can reduce congestion by forcing the
frame to travel around the overloaded segments. Traffic
engineering, then, enables an administrator to define a policy for
forwarding frames rather than depending upon dynamic routing
protocols.
• Traffic engineering is similar to source-routing in that an explicit
path is defined for the frame to travel. However, unlike source-
routing, the hop-by-hop definition is not carried with every frame.
Rather, the hops are configured in the LSRs ahead of time along
with the appropriate label values.

30. What Is MPLS-Traffic Engineering

31. What Is GMPLS
GMPLS (Generalized Multiprotocol Label Switching),
also known as Multiprotocol Lambda Switching, is a
technology that provides enhancements to Multiprotocol
Label Switching (MPLS) to support network switching
for time, wavelength, and space switching as well as for
packet switching. In particular, GMPLS will provide
support for photonic networking, also known as optical
communications

32. Thanks