Welcome to the Juniper Networks Introduction Series! If you’re like me, you’ve been networking for a while. Sooner or later, you will come across Juniper devices, and may find them to be quite different to what you’re used to. This series will build on the skill that you already have, to get you Juniper ready. It will also prepare you for the JNCIA-Junos exam, if that’s something that interests you. Each video is designed to be as short and to the point as possible. They are arranged into five categories; The Basics, Device Configuration, Architecture, Routing, and Monitoring/Troubleshooting. Each video comes with additional resources, including study notes, links for additional reading, labs, quizzes, and flashcards. #junipernetworks #networkdirection #networking #informationtechnology #junipernetworksintroduction
Curated by: Network Direction (21 videos)
Control and data planes are used to split the way traffic is forwarded The data plane is the logical name for the components that focus on forwarding traffic through the device. This traffic is called transit traffic, and is anything that passes through the router, switch, or firewall. The control plane is the logical name for the components that handle traffic that is sent to or from the device. This traffic is called exception traffic, and includes management traffic, routing protocol traffic, and others. The control plane uses the device’s CPU, while the data plane uses specialised hardware like an ASIC. The RE (Routing Engine) is part of the control plane. This handles exception traffic, manages the chassis, and runs Junos. The PFE (Packet Forwarding Engine) is part of the data plane, and focuses on forwarding traffic. Multiple PFE’s are connected with an internal switch fabric. In a modern device, the RE can hand off some of its functions to the PFE. There’s a special link that connects the RE and PFE internally. This is a literal mini-switch within the main device, with includes a special interface. This is often called fxp1. Fxp1 is a non-configurable interface, which is managed internally by Junos. Dynamic routing traffic is exception traffic, which is handled by the RE. The RE builds a routing table from this information. Therefore, the routing table is part of the control plane. The RE will take the best routes and build the forwarding table. This includes L3 routes, as well as L2 information like MAC addresses. The RE then pushes a copy of the forwarding table to the PFE. The forwarding table therefore is part of both the control plane and data plane. Study notes: https://networkdirection.net/study-notes/junos-architecture-planes Transcript: https://networkdirection.net/study-notes/introduction-to-juniper-transcripts/junos-architecture-control-and-data-planes Quizzes: https://networkdirection.net/labsandquizzes/quizzes/juniper-jncia/architecture-planes Labs: https://networkdirection.net/labsandquizzes/labs/jncia-labs/junos-architecture-planes Overview of this video: 0:00 Introduction 0:16 Control Plane and Data Plane 3:43 The RE and the PFE 7:49 The fxp Interface 9:30 Routing and Forwarding Patreon information: https://networkdirection.net/patreon/ Further Reading: An Informal Guide to the Engines of Packet Forwarding - https://forums.juniper.net/t5/Routing/An-Informal-Guide-to-the-Engines-of-Packet-Forwarding/ta-p/401192 Permanent Interfaces - https://www.oreilly.com/library/view/junos-enterprise-routing/9781449309633/ch04s01.html Junos Operating System Fundamentals(Part - 2) - http://juniper-basic.blogspot.com/2017/02 Understanding Internal Ethernet Interfaces - https://www.juniper.net/documentation/en_US/junos/topics/concept/interfaces-understanding-internal-ethernet-interfaces.html Routing engines and interface names (Routers only) - https://www.juniper.net/documentation/en_US/release-independent/junos/topics/reference/general/routing-engine-m-mx-t-series-support-by-chassis.html LET'S CONNECT 🌏 https://www.youtube.com/c/networkdirection 🌏 https://twitter.com/NetwrkDirection 🌏 https://www.patreon.com/NetworkDirection 🌏 https://www.networkdirection.net #NetworkDirection #networking #Juniper