Routing WG Meeting 07/29/02 Policy Constrained Routing/Explicit Routing Ivan Gonzalez

Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential PCR/ER Overview Policy Constrained Routing, Explicit Routing Objectives Solve long standing “fish problem” by use of single router node to create multiple policies or “routing instances” Use more than destination as criteria for routing decision At minimum use Source (VPN membership or L3 Info) + Destination for route decision Technology evolution offers solution RFC 2547bis and MPLS 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential PCR/ER Overview REQUIREMENTS: -Send traffic from router “D” across router “F” -Send traffic from router “E” across router “G” -Routers “D” and “E” are connected to “A” 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential PCR/ER – The Challenge Both customers will use the single best path – Undesireable in this case Routes learned from EBGP Peers GRN and RED Router “A” learns routes through IBGP BGP Path Selection Process will run. ONE active path will be selected to get to the destination "yellow" network 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

PCR/ER – Solution – (Control Plane) 2547bis L3VPN Finer granularity can be achieved by using FBF + 2547bis/MPLS on customer facing ports Router “A” learns routes through IBGP Each VRF still has access to all routes; these routes can be set with different preference values Routes learned from EBGP Peers GRN and RED BGP Path Selection Process will run. An active path will be selected for each VRF to get to the destination "yellow" network 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential IPII Architecture Internet Processor II Incoming Interface Filter Incoming Interface Table Counters can be set to track filter matches Filter “in#1” Interface Action Filter “in#2” Filter “in#3” 1 2 Notifications sent to outgoing logical, Physical Interfaces 3 4 Next hop: outgoing interface “X” Packets arrive from incoming interfaces Protocol Table The Internet Processor II is capable of much more than its predecessor because of its ability to chain together its functional building blocks (ie route lookup, table lookup, filtering). For example, IP traffic can be directed by the incoming protocol table to a second incoming interface table. The operator can configure various “next actions” for each interface. The next action could be to apply a filter, or it could be to send the packet directly to the IP forwarding table. The next action could also be to redirect the packet to a particular interface (note that redirect functionality will not be available with the 4.0 release). After the lookup is performed, filters can be configured and applied for particular outgoing interfaces to filter traffic destined for particular next hops, before sending notifications to outgoing interfaces. Counters can be configured to track the number of matches for each filter. Protocol Action Outgoing Interface Filters IP MPLS IP Forwarding Table Filter “Output_#1” Filter “Output-#2” Filter “Output_Num_3” “Y” “Z” “W” 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

PCR/ER – Solution – (Forwarding Plane) MPLS LSP’s MPLS LSP’s are used to forward traffic 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Proof of Concept 7/01’ and 12/01’ July 2001 Learned more about policy requirements from Routing WG Successfully ran connectivity tests December 2001 Ran extended tests, focusing on performance and scalability Successfully ran connectivity and performance tests 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential PCR/ER – Topology 10 M10’s and 2 Agilent Router Testers 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Performance Results Sunnyvale POC, Dec.01’ Configuration M10 Routers in Sunnyvale Lab Released JUNOS code (JUNOS 4.4) 200K simulated Active Internet routes to VRF “A” 200K simulated Active Internet routes to VRF “B” 50K simulated ESNET routes to VRF “C” 10K partner routes to VRF “D” 1.8M RIB Entries Performance Line Rate traffic across OC-12’s. 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Juniper Networks Platforms Highest performance router available – designed for dense 10G applications T640 Industry's first 10G-class solution or ultra-high end access Industry's first true solution for high-performance access M160 M40/M40e Subscriber density and in-box redundancy in small footprint M-series robustness in space-efficient form factor M20 M5/M10 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential 11

Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential Recent Enhancements Juniper HW/SW Updates That affect PCR JUNOS 5.0+, Lowered Max FIB entries to 420K 1.8M RIB entries RE 3.0 Announced in 5.4, ups RAM from 768MB to 2.0GB 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Junos Internet Software System Architecture Routing Engine Maintains routing table and constructs forwarding table using knowledge of the network Packet Forwarding Engine Receives packet forwarding table from Routing Engine Copies packets from an input interface to an output interface Conducts incremental table updates without forwarding interruption Junos Internet Software Forwarding Table Update Internet Processor II Forwarding Table 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 (RE) and a Packet Forwarding Engine (PFE). The RE is responsible for performing routing updates and system management. The RE consists of routing-protocol software processes running inside a protected memory environment on a Pentium-based computer platform. It has a direct 100-Mbps connection to the PFE. The RE maintains peer relationships, runs the routing protocols, builds the routing table, and, from that table, 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 all production conditions (for example, with 80,000 unique destinations). This separation ensures that high levels of route instability do not impact the performance of the Packet Forwarding Engine. Likewise, extremely large volumes of traffic do not impact the ability of the Routing Engine to maintain peer relationships and calculate routing tables. The clean separation of these two functions permits the delivery of both superior forwarding performance and a highly reliable system. Switch Fabric I/O Card I/O Card 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

PCR/ER Status Juniper Implementation Juniper able to demonstrate a solution for this scenario in December 2001 Demonstrated this scenario with Multicast on a second logical interface Solution now available with Multicast inside RFC2547 VPN To help customers begin to make the transition, Juniper Networks has implemented a phased approach to introducing IPv6. Phase 1 (JUNOS 5.1 release) will be delivered in late 2001 and will include the fundamentals for initial deployment: addressing, IGP/EGP routing, and support on all M-series platforms and interfaces. The Next Phase includes enhancements, additional flexibility, and some of the maturing protocols such as OSPFv3. Next Phase spans JUNOS 5.2 and beyond and will be introduced in 1H01. 9/17/2018 Juniper Networks, Inc. Copyright © 2002 – Proprietary and Confidential

Thank You! www.juniper.net