Juniper_ MT_ 路由器关键技术MPLS_HA_Security_Qos的部署.ppt

* * Primary point – JUNOS has always had the ability to restart RPD without resetting the PFE, which carries on forwarding during RE restart. This is not the same as RE failover or hitless failover cases, because only one RE is involved, not 2, where an RE failover is performed. Hitless RE failover refers to even further improvements to Routing Engine failover –. The key difference with Hitless RE failover is that the failover does not require the RE to reset the PFEs as well. This key difference allows forwarding to continue uninterrupted, and also enables hitless software upgrades. The benefits of Hitless RE failover are further discussed later under Graceful Restart. * The fundamental architecture of the Juniper Networks routing systems is a complete separation between the routing- and packet-forwarding functions. This implementation consists of two independent components: a Routing Engine and a Packet Forwarding Engine (PFE). The Routing Engine maintains the routing table and constructs the forwarding table. It is responsible for performing routing updates and system management. The Routing Engine maintains peer relationships, runs the routing protocols, builds the routing table and from that table, and creates the forwarding table that it exports to the PFE. The PFE is responsible for forwarding packets through the router. It is a high-performance, ASIC-based forwarding engine that is capable of forwarding 40 Mpps for all packet sizes under production conditions. The PFE learns the forwarding table from RE, copies packets from input interface to output interface and conducts incremental table updates without forwarding interruption. This separation ensures route instability does not impact the performance. Likewise, extremely large volumes of traffic do not impact the ability of the Routing Engine.. The clean separation of these two functions permits the delivery of both superior forwarding performance and a highly reliable system. This provider