JunOS separates the control plane and the forwarding (data) plane. The control plane contains the processes that control routing and switching protocols and the forwarding plane processes and forwards the frames and/or packets.
Routing Engine (RE): responsible for performing protocol updates and system management. JunOS runs these protocols and processes in protected memory. RE maintains the routing tables, bridging table, and the primary forwarding table which connects to the Packet Forwarding Engine (PFE)
Packet Forwarding Engine (PFE): Runs on ASICs for increased performance. PFE is focused on forwarding operations and not protocol updates and system management which provides reliability and high performance. The forwarding table (FT) is recieved from the RE through an internal link.
This architecture allows for high availability features such as graceful routing engine switch-over (GRES), nonstop active routing (NSR), unified in-service software upgrades (ISSU).
In the multi-pod EVPN design, I described a simple way to merge two EVPN
fabrics into a single end-to-end fabric. Here are a few highlights of that
desig...
1 day ago
0 comments:
Post a Comment