Price: $1,799.00

Length: 2 Days
Print Friendly, PDF & Email

SDN OpenFlow Training, Software-Defined Networking (SDN) Training by TONEX

Software-Defined Networking (SDN) is an emerging architecture that is dynamic, manageable, cost-effective, and adaptable used in high-bandwidth, dynamic nature of today’s applications. SDN architecture decouples the network control and forwarding functions enabling the network control to become directly programmable and the underlying infrastructure to be abstracted for applications and network services. The OpenFlow™ protocol is a foundational element for building SDN solutions. OpenFlow is a communications protocol giving access to the forwarding plane of a network switch or router over the network. Learn how to use OpenDaylight framework to implement an open SDN controller and more.

Learn about modern networking , IT and telecom Trends such as Big Data, Mobile Traffic, 4G/5G Mobile, Cloud, IoT, QoS/QoE, SDN and NFV.

In despite to their differences, SDN and NFV (Network Function Virtualization) share many properties including:

  • SDN and NFV both try to move functions and features to software
  • They both use common hardware (COTS) without any properiatry solutions
  • They both use open APIs
  • They both try to create more efficient networks

SDN was born on the  campus networks with the key principle to seperate the control functions from forwarding.

OpenFlow was defined by Open Networking Forum (ONF) to define a model for flows and how traffic is organized into flows plus controlling the flows.  OpenDaylight Project also aims to advance open standards and SDN adoption by the Linux Foundation and other players.

NFV was created by ETSI and Service Providers to speed up deployment of new network services by using software appliances for network functions.

Other Modern Networking and Network Transformation Technologies Courses

COURSE NAMELENGTH
Certified SDN Engineer Certification | ONF OCSE Certification Preparation4 days
IMS NFV Training | IMS Network Functions Virtualization (NFV) Training2 days
Network Functions Virtualization (NFV) Training Bootcamp1 day
Network Functions Virtualization Training | NFV Training2 days
Network Transformation Training Bootcamp4 days
NFV and SDN Application Development Training for Service Providers4 days
NFV Application Development Training Bootcamp for Service Providers3 days
NFV Training for Non Engineers2 days
ONF Certified SDN Associate Certification | OCSA Certification2 days
SDN OpenFlow Training, Software-Defined Networking (SDN) Training2 days
SDN Training for Non-Engineers1 day

SDN OpenFlow training also covers Network Functions Virtualization (NFV) which is used for service providers. NFV will eventually transform the way the network operators architect their networks. NFV will be evolved as a standard IT virtualization technology to consolidate many network equipment into high performance, high volume servers, switches and storage, which could be located in Data Centers, Network Nodes and in the end user premises.

SDN OpenFlow training course covers Software-defined networking (SDN) as an approach to networking where the control is decoupled from hardware and given to a software application called a controller supporting a switching fabric across multi-vendor hardware and application-specific integrated circuits (ASICs).

OpenFlow  as the most popular specification for creating a software-defined network is an open standard allows network administrators remotely control routing tables and added as a feature to commercial Ethernet switches, routers and wireless access points

Course Objectives

Upon completing SDN OpenFlow training course, the attendees are able to:

  • Describe Software Defined Networking and OpenFlow concepts, motivation, benefits  and applications
  • Describe concepts behind Network Functions Virtualization (NFV)
  • Compare and contrast SDN and NFV
  • List principles behind cloud computing including IaaS, PaaS, SaaS
  • Understand target environments for SDN/Openflow
  • Describe SDN and OpenFlow building blocks, components, architectures and reference standards
  • Describe how SDN/Openflow work
  • Describe OpenFlow operation and OpenStack
  • Discuss network functions virtualization
  • Discuss SDN deployment models
  • Discuss Infrastructure as a service (IaaS)
  • List SDN Device Implementations
  • Compare OpenFlow, OpenStack and other related protocols and architectures

Course Content

SDN and Open Networking

  • What is Software-Defined Networking (SDN)?
  • What is OpenFlow?
  • key computing trends
  • Need for a new network paradigm
  • Changing traffic patterns
  • Physical separation of the control plane and the forwarding plane
  • SDN and Virtualization
  • Principles behind virtual networking
  • What is network virtualization?
  • What is network function virtualization?
  • Networking virtualization in 3GPP network
  • Principles behind Network Functions Virtualization (NFV)
  • Building Blocks of NFV
  • NFV and SDN integration
  • Integration of OpenStack and OpenDaylight

Basics of Network Functions Virtualization (NFV)

  • Understand the transition towards virtual core networks
  • How is NFV different from SDN?
  • Network Functions Virtualization (NFV) vs. Cloud technologies
  • Working with OpenStack to develop NFV and SDN applications
  • OpenNebula
  • Network Functions Virtualization vs. current network architectures
  • Software implementations (software programs) of the current network components
  • Network Functions Virtualization (NFV) Challenges
  • Mobile Core Network virtualization
  • Core network as a software
  • Lessons learned from implementing a virtualized 3GPP EPC
  • Mobile Core Network beyond EPC
  • Network Virtualization case studies in 3GPP networks
  • Virtualized Open IMS Core case study
  • Virtualized Open LTE/EPC case study
  • OpenIMSCore and OpenEPC

Why SDN/Openflow

  • Potential of SDN/Openflow
  • Benefits of SDN/openFlow
  • Application of SDN
  • Deployment Case Studies
  • Datacenter networking fabric
  • Routing core
  • Campus Edge devices
  • Programming SDNs

Overview of OpenFlow

  • Openflow components
  • Openflow protocol
  • Openflow implementation in network devices
  • Switches / network device
  • Ports and tables
  • Openflow implementations
  • Controllers
  • Management

SDN Architecture

  • SDN building blocks
  • OpenFlow components
  • Network Virtualization layer
  • Principles behind FlowVisor
  • SDN Building Blocks

OpenFlow Protocol Details

  • Openflow implementation details in network devices
  • TCAM, ASIC, matching, speeds
  • Flow tables, limitations, scale, issues
  • Potential vendor differences
  • Openflow implementation in controllers
  • Proactive and dynamic flow settings

OpenFlow components and building blocks

  • Monitoring/debugging tools
  • Applications
  • Controller
  • Openflow switches
  • Traffic generators
  • Slicing
  • Software

SDN Implementation

  • SDN Operation
  • OpenFlow controllers
  • Flowvisors
  • Global view and abstract view
  • Flow tables entries
  • SDN Controller Implementations
  • SDN deployment models
  • Symmetric vs asymmetric
  • Floodless vs flood-based
  • Host-based vs Network-centric
  • Basics flow table entries
  • Centralized vs Distributed Control OpenFlow
  • Flow Routing vs. Aggregation
  • OpenFlow Implementations (Switch and Controller)
  • OpenDaylight Framework

 

Who Should Attend

Technical and Non-Technical professionals who want to learn key concepts in Software Defined Networking (SDN) and OpenFlow with examples, cases studies and demos.

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.