1Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. Explicit Routing: the fish at 4+yrs Larry Dunn Manager, Advanced Architecture

Slides:



Advertisements
Similar presentations
MPLS VPN.
Advertisements

Traffic Engineering over MPLS
Identifying MPLS Applications
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Technology Introducing the MPLS VPN Routing Model.
Logically Centralized Control Class 2. Types of Networks ISP Networks – Entity only owns the switches – Throughput: 100GB-10TB – Heterogeneous devices:
Deployment of MPLS VPN in Large ISP Networks
Routing Basics.
Leading Edge Routing MPLS Enhancements to Support Layer 2 Transport Services Jeremy Brayley
1 © 2000, Cisco Systems, Inc. Integrated-ISIS Route Leaking.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—1 Implementing Cisco MPLS (MPLS) v2.2.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—8-1 MPLS TE Overview Introducing the TE Concept.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—2-1 Label Assignment and Distribution Introducing Convergence in Frame-Mode MPLS.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—2-1 Label Assignment and Distribution Introducing Typical Label Distribution in Frame-Mode MPLS.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—1-1 Module Summary BGP has reliable transport provided by TCP, a rich set of metrics called BGP.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Routing Working at a Small-to-Medium Business or ISP – Chapter 6.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 Routing Working at a Small-to-Medium Business or ISP – Chapter 6.
IPv4 and IPv6 Mobility Support Using MPLS and MP-BGP draft-berzin-malis-mpls-mobility-00 Oleg Berzin, Andy Malis {oleg.berzin,
Introducing MPLS Labels and Label Stacks
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 Provider Opportunities for Enterprise MPLS APRICOT 2006, Perth Matt.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—4-1 Implement an IPv4-Based Redistribution Solution Lab 4-1 Debrief.
Introduction to MPLS and Traffic Engineering Zartash Afzal Uzmi.
MPLS and Traffic Engineering
Kae Hsu Communication Network Dept. Redundant Internet service provision - customer viewpoint.
Introduction to MPLS and Traffic Engineering
© 2006 Cisco Systems, Inc. All rights reserved. Implementing Secure Converged Wide Area Networks (ISCW) Module 4: Frame Mode MPLS Implementation.
© 2006 Cisco Systems, Inc. All rights reserved. Implementing Secure Converged Wide Area Networks (ISCW) Module 4: Frame Mode MPLS Implementation.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—5-1 Implementing Path Control Lab 5-1 Debrief.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network Considering the Advantages of Using BGP.
MPLS L3 and L2 VPNs Virtual Private Network –Connect sites of a customer over a public infrastructure Requires: –Isolation of traffic Terminology –PE,
COS 420 Day 16. Agenda Assignment 3 Corrected Poor results 1 C and 2 Ds Spring Break?? Assignment 4 Posted Chap Due April 6 Individual Project Presentations.
Network-based IP VPNs using Virtual Routers Tim Hubbard.
Network based IP VPN Architecture using Virtual Routers Jessica Yu CoSine Communications, Inc. Feb. 19 th, 2001.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—1-1 MPLS Concepts Introducing Basic MPLS Concepts.
1 Multi-Protocol Label Switching (MPLS). 2 MPLS Overview A forwarding scheme designed to speed up IP packet forwarding (RFC 3031) Idea: use a fixed length.
Introduction to MPLS and Traffic Engineering Zartash Afzal Uzmi.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network BGP Attributes and Path Selection Process.
1 Multiprotocol Label Switching. 2 “ ” It was designed to provide a unified data-carrying service for both circuit-based clients and packet-switching.
End-to-end resource management in DiffServ Networks –DiffServ focuses on singal domain –Users want end-to-end services –No consensus at this time –Two.
© 2006 Cisco Systems, Inc. All rights reserved. 3.3: Selecting an Appropriate QoS Policy Model.
© 2006 Cisco Systems, Inc. All rights reserved. Optimizing Converged Cisco Networks (ONT) Module 3: Introduction to IP QoS.
MultiProtocol Label Switching (MPLS) July 29, 2000TECON 2000 Pramoda Nallur Alcatel Internetworking Division.
MPLS Forwarder Preliminary 1 Outline MPLS Overview MPLS Overview MPLS MRD MPLS Data Path HLD 48K MPLS Fwder HLD IPE MPLS Fwder HLD Issues Summary.
Chapter 9. Implementing Scalability Features in Your Internetwork.
Tag Switching Architecture Overview Qingfeng Zhuge Fangxia Li Xin Jiang.
The Network Layer Introduction  functionality and service models Theory  link state and distance vector algorithms  broadcast algorithms  hierarchical.
1MPLS QOS 10/00 © 2000, Cisco Systems, Inc. rfc2547bis VPN Alvaro Retana Alvaro Retana
1 MPLS: Progress in the IETF Yakov Rekhter
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—3-1 Implementing a Scalable Multiarea Network OSPF- Based Solution Lab 3-5 Debrief.
MPLS Concepts Introducing Basic MPLS Concepts. Outline Overview What Are the Foundations of Traditional IP Routing? Basic MPLS Features Benefits of MPLS.
Mr. Mark Welton.  WAN transportation method that formats data into frames and sent over a network controlled by a service provider  Frame Relay is often.
1. Tag Switching RFC Cisco systems Tag Switching architecture overview. Switching In IP Networks - B.Davie, P.Doolan, Y.Rekhter. Presnted By - Shmuel.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—3-1 Route Selection Using Policy Controls Filtering with Prefix-Lists.
Describe basic routing concepts. Routers Interconnect Networks Router is responsible for forwarding packets from network to network, from the original.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—1-1 Course Introduction.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network Lab 6-2 Debrief.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—3-1 Implementing a Scalable Multiarea Network OSPF- Based Solution Configuring and Verifying.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Lab 1-1 Debrief.
Internet Traffic Engineering Motivation: –The Fish problem, congested links. –Two properties of IP routing Destination based Local optimization TE: optimizing.
MULTI-PROTOCOL LABEL SWITCHING By: By: YASHWANT.V YASHWANT.V ROLL NO:20 ROLL NO:20.
Multi-protocol Label Switching
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Creating the Network Design Designing and Supporting Computer Networks – Chapter.
Multi-protocol Label Switching (MPLS) RFC 3031 MPLS provides new capabilities: QoS support Traffic engineering VPN Multiprotocol support.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 Routing Working at a Small-to-Medium Business or ISP – Chapter 6.
Working at a Small-to-Medium Business or ISP – Chapter 6
Requirements for LER Forwarding of IPv4 Option Packets
Working at a Small-to-Medium Business or ISP – Chapter 6
1 Multi-Protocol Label Switching (MPLS). 2 MPLS Overview A forwarding scheme designed to speed up IP packet forwarding (RFC 3031) Idea: use a fixed length.
Working at a Small-to-Medium Business or ISP – Chapter 6
Unit 7 EIGRP Chapter 13 Using EIGRP in Enterprise Networks
Presentation transcript:

1Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. Explicit Routing: the fish at 4+yrs Larry Dunn Manager, Advanced Architecture

22Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 2 Agenda Problem review Requirements Example topology General architecture/solution classes Example: Early binding Example: Late binding Invitation: routing working group

33Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 3 Problem review: “This old fish…” R8 R2 R6 R3 R4 R7 R5 R1 Flows from R8 and R1 Merge at R2 and Become Indistinguishable From R2, Traffic to R3, R4, R5 Use Upper Route Alternate Path may be required “by policy” for R1

44Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 4 Requirements Accommodate >1 class of traffic (e.g., Abilene- eligible, vs. not-eligible). Some have more classes (e.g., carrier selection). Amounts to overriding “normal IP routing” somewhere in the network Evaluation metrics: robustness/fragility, performance, complexity(for humans and routers), scalability, $$

55Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 5 Example topology School-D-eligible School-B-ineligible Destination School-E Abilene School-A-eligible Commodity ISP1 School-C-ineligible Gigapop Commodity ISP2

66Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 6 General Architecture Classes “Early binding” Decision made close(r) to the source Decision must be conveyed to the gigapop (VC, Label, DLCI, tunnel, TOS-overload, etc.) “Late binding” Gigapop router does multi-field classification (typically source-prefix) Everybody else just does “regular forwarding”

77Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 7 Example: Early binding #1: MPLS/VPNs School-A-eligible Commodity ISP1 School-C-ineligible Abilene Gigapop Commodity ISP2 School-D-eligible School-B-ineligible (tunnel FIB) (eligible, non-tunnel FIB, includes Abilene)

88Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 8 Ex: Early binding #2: generalized tunnels School-A-eligible Commodity ISP1 School-C-ineligible Abilene Gigapop Commodity ISP2 School-D-eligible School-B-ineligible (normal FIB for ineligible) (three trivial entries, one per ISP) Route server BGP to dist. routes; schools choose w/in policy, use tunnel(GRE, FR, MPLS, whatever) to deliver pkts to trivial FIBs. Ineligible schools just do “normal routing”.

99Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 9 Example: Late binding (at gigapop) School-A-eligible Commodity ISP1 School-C-ineligible Abilene Gigapop Commodity ISP2 School-D-eligible School-B-ineligible (ineligible FIB) (eligible FIB, includes Abilene) Schools do “normal routing”, gigapop router uses multi-field classification (typ. Src-prefix) to choose routing table

10 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 10 Invitation: routing working group Today, 5:00pm..7:45p(max), at conf. hotel Merit folks’ routing registry discussion Deeper discussion of architectural options Your thoughts/ideas (see yourself here?) More detailed presos from {Juniper,Cisco} (implementation, customer feedback, etc.)

11 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 11 Summary Fish problem: been around a long time Early solutions: multiple boxes, ATM Today: better understanding of possible architectures; getting field experience Advice: use the least complicated mechanism that will work for your environment ;-)

12 © 2001, Cisco Systems, Inc. All rights reserved. QoS Update

13 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 13 Routing w.g. Architecture follow-up Taxonomy/solution families Early binding: policy,security, other facets Late binding: policy, security Open discussion

14 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 14 Taxonomy/solution_families Generalized tunnels MPLS/VPNs TOS_overload Port-based Src-addr/5-tuple/else Early binding Late binding Notes: 1. Single-box, multiple-box decision is orthogonal 2. Combinations are possible/expected 3. Often, the “early-binding” solutions look like a distributed version of late-binding (Normal IP routing)

15 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 15 Early binding (gen. tunnels): policy, security, other facets School-A-eligible Commodity ISP1 School-C-ineligible Abilene Gigapop Commodity ISP2 School-D-eligible School-B-ineligible (normal FIB for ineligible) (three trivial entries, one per ISP) Route server BGP to dist. routes; schools choose w/in policy, use tunnel(GRE, FR, MPLS, whatever) to deliver pkts to trivial FIBs. Ineligible schools just do “normal routing”. Note: carried to extreme, gigapop starts to feel like an (indirect) L2-exchange

16 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 16 Late binding: policy, security School-A-eligible Commodity ISP1 School-C-ineligible Abilene Gigapop Commodity ISP2 School-D-eligible School-B-ineligible (ineligible FIB) (eligible FIB, includes Abilene) Schools do “normal routing”, gigapop router uses multi-field classification (typ. Src-prefix) to choose routing table

17 Joint-techs Boulder © 2002, Cisco Systems, Inc. All rights reserved. 17 Open discussion Is issue significant to you? Timeframe? Implementation stories? Your topology/complexity? Other useful models/hybrids?