< Return to Video

Software Defined Networking - CompTIA A+ 220-1101 - 2.2

  • 0:02 - 0:04
    The advent of cloud
    computing has changed
  • 0:04 - 0:06
    networking in many ways.
  • 0:06 - 0:08
    And if you're a
    network administrator,
  • 0:08 - 0:10
    you know that in the
    cloud, we don't usually
  • 0:10 - 0:13
    have physical routers, switches,
    and other infrastructure
  • 0:13 - 0:14
    devices.
  • 0:14 - 0:17
    Instead, we need to take
    these networking platforms we
  • 0:17 - 0:19
    use in the real
    world and move them
  • 0:19 - 0:22
    into the virtualized
    cloud-based world.
  • 0:22 - 0:24
    One way that we're
    able to do this
  • 0:24 - 0:27
    is through the advent
    of Software Defined
  • 0:27 - 0:29
    Networking or SDN.
  • 0:29 - 0:31
    With Software
    Defined Networking,
  • 0:31 - 0:34
    we take those devices like
    switches, routers, firewalls,
  • 0:34 - 0:37
    and other networking
    infrastructure devices
  • 0:37 - 0:41
    and we change them to be
    a software based platform
  • 0:41 - 0:43
    that we could use in the cloud.
  • 0:43 - 0:45
    This means that we might
    take something like a switch
  • 0:45 - 0:48
    and separate all of the
    functions of the switch
  • 0:48 - 0:50
    into individual pieces.
  • 0:50 - 0:52
    We can then take these
    pieces and then create
  • 0:52 - 0:56
    software versions that we
    can then run in the cloud.
  • 0:56 - 0:59
    There are commonly three
    layers or three ways
  • 0:59 - 1:01
    to separate these
    devices so that we
  • 1:01 - 1:05
    can create some consistency
    across all of these networking
  • 1:05 - 1:06
    components.
  • 1:06 - 1:09
    The first layer would be
    the infrastructure layer.
  • 1:09 - 1:11
    Sometimes we hear this
    referred to as the data
  • 1:11 - 1:13
    plane of that device.
  • 1:13 - 1:15
    So it's common that
    this data plane
  • 1:15 - 1:17
    would do the forwarding, the
    trunking, the encrypting,
  • 1:17 - 1:21
    the Network Address Translation,
    or anything else that needs
  • 1:21 - 1:23
    to occur at that packet level.
  • 1:23 - 1:26
    When our routers and switches
    need to forward this traffic
  • 1:26 - 1:29
    in the data plane, they
    need some type of reference
  • 1:29 - 1:31
    to know where this
    traffic will be going.
  • 1:31 - 1:35
    Most of those references will be
    in the control layer or control
  • 1:35 - 1:36
    plane of that device.
  • 1:36 - 1:39
    So if you have dynamic
    routing protocols,
  • 1:39 - 1:42
    a forwarding table in a switch,
    a Network Address Translation
  • 1:42 - 1:44
    table in a router,
    all of those are
  • 1:44 - 1:46
    contained in the control plane.
  • 1:46 - 1:48
    And of course, you
    or some other process
  • 1:48 - 1:51
    is in charge of
    managing that device.
  • 1:51 - 1:54
    To be able to manage it,
    we need to log in or access
  • 1:54 - 1:57
    the device via an API or
    Application Programming
  • 1:57 - 1:58
    Interface.
  • 1:58 - 2:00
    And all of that
    access is provided
  • 2:00 - 2:02
    at the application
    layer or management
  • 2:02 - 2:04
    plane of that device.
  • 2:04 - 2:07
    So when you SSH into a
    router, when you bring up
  • 2:07 - 2:09
    a graphical front
    end of a firewall,
  • 2:09 - 2:13
    you're managing that device
    from the management plane.
  • 2:13 - 2:16
    Let's see how this software
    defined networking would
  • 2:16 - 2:19
    apply to a physical device.
  • 2:19 - 2:21
    And in this case, this physical
    device appears to be a switch,
  • 2:21 - 2:24
    but this could be a
    router or firewall
  • 2:24 - 2:26
    or any other
    infrastructure device.
  • 2:26 - 2:29
    Let's start first with
    that infrastructure layer
  • 2:29 - 2:31
    or the data plane.
  • 2:31 - 2:33
    If you're connecting to a
    switch or you need traffic
  • 2:33 - 2:36
    forwarded between different
    interfaces on a switch,
  • 2:36 - 2:38
    that all occurs in
    that data plane.
  • 2:38 - 2:40
    This means we'll
    take anything that
  • 2:40 - 2:42
    may be forwarding this
    traffic on that device
  • 2:42 - 2:44
    and create a software
    version of that
  • 2:44 - 2:46
    that we call the data plane.
  • 2:46 - 2:50
    These devices also need the
    tables and forwarding structure
  • 2:50 - 2:52
    to be able to understand
    where traffic is coming from
  • 2:52 - 2:54
    and where you'll be
    forwarding it to,
  • 2:54 - 2:57
    and all that occurs in the
    control layer or the control
  • 2:57 - 2:58
    plane.
  • 2:58 - 3:01
    And lastly, you'll be
    managing this device probably
  • 3:01 - 3:02
    through a console
    port or management
  • 3:02 - 3:06
    interface to the device, and
    that section of the device
  • 3:06 - 3:08
    can be created as
    the management plane.
  • 3:08 - 3:10
    Obviously with software
    defined networking,
  • 3:10 - 3:12
    there is no physical
    device, but you
  • 3:12 - 3:15
    can see where the data plane,
    control plane, and management
  • 3:15 - 3:18
    plane are pulled from
    our physical devices
  • 3:18 - 3:23
    to create this software based
    networking infrastructure.
  • 3:23 - 3:25
    This now creates
    modular layers that you
  • 3:25 - 3:29
    can extend between devices or
    create new devices all based
  • 3:29 - 3:31
    on the Software
    Defined Networking.
  • 3:31 - 3:33
    If we start, for
    instance, at the bottom,
  • 3:33 - 3:35
    we know that
    network traffic will
  • 3:35 - 3:38
    be traversing different
    devices all at the data plane.
  • 3:38 - 3:41
    So communication between
    those can occur solely
  • 3:41 - 3:43
    between those particular layers.
  • 3:43 - 3:45
    A device may need
    to send or receive
  • 3:45 - 3:49
    dynamic routing protocols or
    create tables for forwarding,
  • 3:49 - 3:51
    and all of those can
    be done at the control
  • 3:51 - 3:54
    layer or the control plane of
    Software Defined Networking.
  • 3:54 - 3:57
    And the layer that you're going
    to manage these devices from
  • 3:57 - 3:59
    will be the management plane.
  • 3:59 - 4:01
    We usually access
    the management plane
  • 4:01 - 4:04
    through Secure Shell, Simple
    Network Management Protocol,
  • 4:04 - 4:07
    or an Application
    Programming Interface.
  • 4:07 - 4:09
    You can see that
    the Software Defined
  • 4:09 - 4:12
    Networking takes these very
    standard categorizations
  • 4:12 - 4:15
    and extends them across
    multiple networking devices
  • 4:15 - 4:18
    to create a very
    modular architecture.
  • 4:18 - 4:20
    This allows you to have
    a software based version
  • 4:20 - 4:23
    of these network devices that
    we use on our physical networks
  • 4:23 - 4:26
    and be able to deploy them
    and use them in a cloud-based
  • 4:26 - 4:29
    infrastructure.
Title:
Software Defined Networking - CompTIA A+ 220-1101 - 2.2
Description:

more » « less
Video Language:
English
Duration:
04:38

English subtitles

Revisions Compare revisions