DOCSLIB.ORG

Understanding MPLS Khurram Waheed Systems Engineer Session Goals

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Understanding MPLS Khurram Waheed Systems Engineer Session Goals Understanding MPLS Khurram Waheed Systems Engineer Session Goals • Understand the problems MPLS is addressing • Understand major MPLS technology components • Understand typical MPLS applications • Understand benefits of deploying MPLS Agenda • Introduction • MPLS Basics • MPLS Layer-3 VPNs • MPLS Layer-2 VPNs • MPLS Traffic Engineering • Summary Introduction Why Multi-Protocol Label Switching? • SP/Carrier perspective • Reduce costs (CAPEX/OPEX); consolidate networks and maximise utilisation of resources. • Consolidated network for multiple Layer-2/3 services over same infrastructure • Support increasingly stringent SLAs (Voice + Video etc.) • Enterprise/end-user perspective • Campus/LAN • Need for network segmentation (users, applications, etc.) What is MPLS? Brief Summary • It’s all about labels … • Use the best of both worlds • Layer-2: efficient forwarding and traffic engineering • Layer-3: flexible and scalable • MPLS forwarding plane • Use of labels for forwarding Layer-2/3 data traffic • Labeled packets are switched; instead of routed • Leverage layer-2 forwarding efficiency • MPLS control/signalling plane • Use of existing IP control protocols extensions + new protocols to exchange label information • Leverage layer-3 control protocol flexibility and scalability MPLS Basics Topics Basics of MPLS Signalling and Forwarding • MPLS Reference Architecture Service (Clients) • MPLS Labels Layer-3 VPNs Layer-2 VPNs • MPLS Signalling and Forwarding Operations Transport IP/MPLS (LDP/RSVP-TE/BGP) MPLS Forwarding MPLS Reference Architecture Different Types of Nodes in an MPLS Network • P (Provider) router • Label switching router (LSR) MPLS Domain • Switches MPLS-labeled packets P P • PE (Provider Edge) router CE PE PE CE • Edge router (LER) • Imposes and removes MPLS labels CE CE • CE (Customer Edge) router • Connects customer network to MPLS PE P P PE network Label switched traffic MPLS Labels Label Definition and Encapsulation MPLS Label • 4 Bytes (32Bits) in size 0 1 2 3 • Labels used for making forwarding decision 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 Label # – 20bits TC S TTL-8bits • Multiple labels can be used for MPLS packet encapsulation TC = Traffic Class: 3 Bits; S = Bottom of Stack; TTL = Time to Live • Creation of a label stack MPLS Label Encapsulation • Outer label always used for switching MPLS packets in network LAN MAC Label Header MAC Header Label Layer 3 Packet • Remaining inner labels used for services (VPNs etc.) MPLS Label Stack LAN MAC Label Header MAC Header Label Label S Layer 3 Packet Bottom of Stack Bit Set Basic MPLS Forwarding Operations How Labels are being used to establish End-to-End Connectivity • Label imposition (PUSH) Label Imposition Label Disposition Label Swap Label Swap • By ingress PE router; classify and label packets (Push) (PoP) • Based on Forwarding Equivalence Class (FEC) L1 L1 L2 L2 L3 L3 • Label swapping or switching L2/L3 (SWAP) Packet P P • By P router; forward packets using labels; CE PE PE CE indicates service class & destination • Label disposition (POP) CE CE • By egress PE router; remove label and forward original packet to destination CE PE P P PE Traffic Flow MPLS Path (LSP) Setup and Traffic Forwarding Overview • IGP (OSPF/ISIS) • Learns MPLS Loopback Interfaces (loopback0 IP MPLS etc.) Destination address based Label based Forwarding Forwarding table learned Forwarding table learned • LSP signalling from control plane from control plane • Either LDP or RSVP TTL support TTL support • Leverages IP routing (RIB from IGP) OSPF, IS-IS, BGP Control Plane OSPF, IS-IS, BGP LDP, RSVP • Exchange of labels Packet IP Header One or more labels • Label bindings Encapsulation • Downstream MPLS node advertises what label to use QoS 8 bit TOS field in IP header 3 bit TC field in label • MPLS forwarding OAM IP ping, traceroute MPLS OAM • MPLS Forwarding table (FIB) MPLS Path (LSP) Setup Signalling Options • LDP signalling LDP RSVP • Leverages existing routing (RIB) LSP or TE Tunnel Forwarding path LSP • RSVP signalling Primary and, optionally, backup Based on TE topology • Aka MPLS RSVP/TE database Forwarding Based on IP routing database Shortest-path and/or other • Enables enhanced capabilities, such as Fast Calculation Shortest-Path based Re-Route (FRR) constraints (CSPF calculation) Packet Single label One or two labels Encapsulation Initiated by head-end node towards tail-end node By each node independently Uses routing protocol Signalling Uses existing routing extensions/information protocols/information Supports bandwidth reservation Supports link/node protection IP Packet Forwarding Example Basic IP Packet Forwarding • IP routing information exchanged Forwarding Table Address Forwarding Table Forwarding Table I/F between nodes Prefix Address Address I/F I/F • Via IGP (e.g., OSFP, IS-IS) Prefix Prefix 128.89 0 128.89 128.89 1 0 … 171.69 1 171.69 1 … • Packets being forwarded based on … … destination IP address • Lookup in routing table (RIB) R3 128.89 0 R1 R2 0 128.89.25.4 Data 1 128.89.25.4 Data 1 128.89.25.4 Data 128.89.25.4 Data 171.69 R4 MPLS Path (LSP) Setup Step 1: IP Routing (IGP) Convergence • Exchange of IP routes • OSPF, IS-IS, etc. Forwarding Table Forwarding Table Forwarding Table In Address Out Out In Address Out Out In Address Out Out Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label 128.89 1 128.89 0 128.89 0 • Establish IP reachability 171.69 1 171.69 1 … … … … … … R3 0 128.89 R2 0 R1 1 You Can Reach 128.89 Thru Me You Can Reach 128.89 and 1 171.69 Thru Me Routing Updates You Can Reach 171.69 Thru Me R4 (OSPF, IS-IS, …) 171.69 MPLS Path (LSP) Setup Step 2A: Assign Local Labels • Each MPLS node assigns a local label to each route in local routing table Forwarding Table Forwarding Table Forwarding Table In Address Out Out In Address Out Out In Address Out Out • In label Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label - 128.89 1 20 128.89 0 30 128.89 0 - - 171.69 1 21 171.69 1 … … … … … … … … … … … … R3 0 128.89 0 1 0 R1 R2 1 R4 171.69 MPLS Path (LSP) Setup Step 2B: Assign Remote Labels • Local label mapping are sent to In Address Out Out In Address Out Out In Address Out Out connected nodes Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label - 128.89 1 20 20 128.89 0 30 30 128.89 0 - • Receiving nodes update forwarding - 171.69 1 21 21 171.69 1 36 table … … … … … … … … … … … … • Out label R3 128.89 R2 0 R1 1 0 Use Label 30 for 128.89 Use Label 20 for 128.89 and 1 Use Label 21 for 171.69 Label Distribution Use Label 36 for 171.69 R4 Protocol (LDP) 171.69 (Downstream Allocation) MPLS Traffic Forwarding Hop-by-Hop Traffic Forwarding Using Labels • Ingress PE node adds label to packet In Address Out Out In Address Out Out In Address Out Out (PUSH) Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label • Via forwarding table - 128.89 1 20 20 128.89 0 30 30 128.89 0 - - 171.69 1 21 21 171.69 1 36 • Downstream node use label for … … … … … … … … … … … … forwarding decision (SWAP) • Outgoing interface R3 0 128.89 0 R1 R2 • Out label 128.89.25.4 Data 1 30 128.89.25.4 Data • Egress PE removes label and 128.89.25.4 Data 20 128.89.25.4 Data 1 forwards original packet (POP) R4 Forwarding based on Label 171.69 MPLS Penultimate Hop Popping Forwarding Efficiency Gains with PHP • Downstream node signals POP label (Implicit NULL) In Address Out Out In Address Out Out In Address Out Out Label Prefix I’face Label Label Prefix I’face Label Label Prefix I’face Label • Last LSR (P) removes outer label - 128.89 1 20 20 128.89 0 POP POP 128.89 0 - before sending to LER (PE) R3 0 128.89 • Improves LER (PE) performance by 0 R1 R2 not performing multiple label lookups 128.89.25.4 Data 1 to forward to final packet POP 128.89.25.4 Data 128.89.25.4 Data 20 128.89.25.4 Data • Explicit-NULL can be used for QoS requirements Outer label removed (PHP) Implicit-NULL signaled (POP) Summary…So Far... Key Takeaways • MPLS networks consist of PE routers at in/egress and P routers in core • Traffic is encapsulated with label(s) at ingress (PE router) • Labels are removed at egress (PE router) • MPLS forwarding operations include label imposition (PUSH), swapping (SWAP), and disposition (POP) • Penultimate Hop Popping (PHP) is used to improve LER performance. • LDP and/or RSVP can be used for signalling label mapping information to set up an end-to-end Label Switched Path (LSP) MPLS Virtual Private Networks MPLS Virtual Private Networks Topics • Definition of MPLS VPN service Service (Clients) • Basic MPLS VPN deployment scenario Layer-3 VPNs Layer-2 VPNs • Technology options Transport IP/MPLS (LDP/RSVP-TE/BGP) MPLS Forwarding What is a Virtual Private Network? Definition • Set of sites which communicate with each other • Typically over a shared public or private network infrastructure • Defined by a set of administrative policies • Policies established by VPN customers themselves (DIY) • Policies implemented by VPN service provider (managed/unmanaged) • Different inter-site connectivity schemes possible • Full mesh, partial mesh, hub-and-spoke, etc. • VPN sites may be either within the same or in different organisations • VPN can be either intranet (same org) or extranet (multiple orgs) MPLS VPN Example Basic Building Blocks • VPN policies PE-CE VPN Signalling PE-CE • Configured on PE routers (manual operation) Link Link • VPN signalling PE P VPN P PE • Between PEs CE CE • Exchange of VPN policies VPN VPN Policy Policy VPN VPN • VPN traffic forwarding Policy Policy CE CE
Load more

Recommended publications
  • TR-221: Technical Specifications for MPLS in Mobile Backhaul Networks
    TECHNICAL REPORT TR-221 Technical Specifications for MPLS in Mobile Backhaul Networks Issue: 1 Amendment 2 Issue Date: September 2017 © The Broadband Forum. All rights reserved. Technical Specifications for MPLS in Mobile Backhaul Networks TR-221 Issue 1 Amendment 2 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Technical Report has been approved by members of the Forum. This Technical Report is subject to change. This Technical Report is copyrighted by the Broadband Forum, and all rights are reserved. Portions of this Technical Report may be copyrighted by Broadband Forum members. Intellectual Property Recipients of this Technical Report are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of this Technical Report, or use of any software code normatively referenced in this Technical Report, and to provide supporting documentation. Terms of Use 1. License Broadband Forum hereby grants you the right, without charge, on a perpetual, non-exclusive and worldwide basis, to utilize the Technical Report for the purpose of developing, making, having made, using, marketing, importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complying with the Technical Report, in all cases subject to the conditions set forth in this notice and any relevant patent and other intellectual property rights of third parties (which may include members of Broadband Forum). This license grant does not include the right to sublicense, modify or create derivative works based upon the Technical Report except to the extent this Technical Report includes text implementable in computer code, in which case your right under this License to create and modify derivative works is limited to modifying and creating derivative works of such code.
    [Show full text]
  • Disk Clone Industrial
    Disk Clone Industrial USER MANUAL Ver. 1.0.0 Updated: 9 June 2020 | Contents | ii Contents Legal Statement............................................................................... 4 Introduction......................................................................................4 Cloning Data.................................................................................................................................... 4 Erasing Confidential Data..................................................................................................................5 Disk Clone Overview.......................................................................6 System Requirements....................................................................................................................... 7 Software Licensing........................................................................................................................... 7 Software Updates............................................................................................................................. 8 Getting Started.................................................................................9 Disk Clone Installation and Distribution.......................................................................................... 12 Launching and initial Configuration..................................................................................................12 Navigating Disk Clone.....................................................................................................................14
    [Show full text]
  • Forest Quickstart Guide for Linguists
    Forest Quickstart Guide for Linguists Guido Vanden Wyngaerd [email protected] June 28, 2020 Contents 1 Introduction 1 2 Loading Forest 2 3 Basic Usage 2 4 Adjusting node spacing 4 5 Triangles 7 6 Unlabelled nodes 9 7 Horizontal alignment of terminals 10 8 Arrows 11 9 Highlighting 14 1 Introduction Forest is a package for drawing linguistic (and other) tree diagrams de- veloped by Sašo Živanović. This manual provides a quickstart guide for linguists with just the essential things that you need to get started. More 1 extensive documentation is available from the CTAN-archive. Forest is based on the TikZ package; more information about its commands, in par- ticular those controlling the appearance of the nodes, the arrows, and the highlighting can be found in the TikZ documentation. 2 Loading Forest In your preamble, put \usepackage[linguistics]{forest} The linguistics option makes for nice trees, in which the branches meet above the two nodes that they join; it will also align the example number (provided by linguex) with the top of the tree: (1) CP C IP I VP V NP 3 Basic Usage Forest uses a familiar labelled brackets syntax. The code below will out- put the tree in (1) above (\ex. requires the linguex package and provides the example number): \ex. \begin{forest} [CP[C][IP[I][VP[V][NP]]]] \end{forest} Forest will parse the above code without problem, but you are likely to soon get lost in your labelled brackets with more complicated trees if you write the code this way. The better alternative is to arrange the nodes over multiple lines: 2 \ex.
    [Show full text]
  • Metadata for Everyone a Simple, Low-Cost Methodology Timothy D
    SAS Global Forum 2008 Data Integration Paper 138-2008 Metadata for Everyone A Simple, Low-Cost Methodology Timothy D. Brown, Altoona, IA ABSTRACT In the context of Base SAS® programming, this paper uses “hardcoded” values as an introduction to “metadata” and the reasons for using it. It then describes a low cost and simple methodology for maintaining any kind of metadata. INTRODUCTION This discussion will take an indirect approach to defining metadata. It’ll describe the metadata which might be included, or hard-coded, in a Base SAS program and propose alternatives to storing and using the metadata. Outside of programs “data” and “code” are distinct. However within programs, the distinction gets blurred when data values, called “hardcoded” data, are included within the code. Hardcoded values include, but are not limited to: • Text constants, literals • Names of companies, people, organizations and places • Directory paths and file names • Parameters on SAS procedures such as WHERE, KEEP, DROP, RENAME, VARS, BY etc • Numeric constants including dates* • Statistical constants • Period begin and end dates • Mixed text and numeric values • Expressions in IF and WHERE clauses • What-if scenarios (* excluding dates which are derived logically using a SAS functions such as TODAY(), DATETIME(), INTNX and NXTPD) In addition, many small conversion, cross-reference and look-up tables, which might be hardcoded as SAS formats or read into a program from many different sources, work well as metadata and fit into this framework. Obviously, some hardcoded values might never change in the life of a program. So it might be prudent to leave some hardcoded values in the code.
    [Show full text]
  • Four Ways to Reorder Your Variables, Ranked by Elegance and Efficiency Louise S
    Order, Order! Four Ways To Reorder Your Variables, Ranked by Elegance and Efficiency Louise S. Hadden, Abt Associates Inc. ABSTRACT SAS® practitioners are frequently required to present variables in an output data file in a particular order, or standards may require variables in a production data file to be in a particular order. This paper and presentation offer several methods for reordering variables in a data file, encompassing both DATA step and procedural methods. Relative efficiency and elegance of the solutions will be discussed. INTRODUCTION SAS provides us with numerous methods to control all types of SAS output, including SAS data files, data tables in other formats, and ODS output. This paper focuses solely on output SAS data files (which may then be used to generate SAS data files and other types of output from SAS processes), and specifically on DATA step and PROC SQL methods. This short paper and presentation is suitable for all SAS practitioners at all levels of expertise. Attendees will gain a greater understanding of the processes by which SAS assigns variable attributes, including variable/column order within a data file, and how to obtain information on variable attributes – and in the process, learn how to reorder variables within a SAS data file. KNOW THY DATA It is always important to understand fully and explore the inputs to SAS-created output. SAS has provided users with a variety of possibilities in terms of determining locations of variables or columns (and other important details comprising metadata). These possibilities include, but are not limited to: 1. The CONTENTS Procedure 2.
    [Show full text]
  • MPLS Layer-2 Vpns • MPLS Traffic Engineering • Summary
    Understanding MPLS BRKMPL - 1101 Khurram Waheed Systems Engineer #clmel Session Goals • Understand the problems MPLS is addressing • Understand major MPLS technology components • Understand typical MPLS applications • Understand benefits of deploying MPLS BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public Agenda • Introduction • MPLS Basics • MPLS Layer-3 VPNs • MPLS Layer-2 VPNs • MPLS Traffic Engineering • Summary BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public Introduction Why Multi-Protocol Label Switching? • SP/Carrier perspective – Reduce costs (CAPEX/OPEX); consolidate networks and maximise utilisation of resources. – Consolidated network for multiple Layer-2/3 services over same infrastructure – Support increasingly stringent SLAs (Voice + Video etc.) • Enterprise/end-user perspective – Campus/LAN – Need for network segmentation (users, applications, etc.) BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public What is MPLS? Brief Summary • It’s all about labels … • Use the best of both worlds – Layer-2: efficient forwarding and traffic engineering – Layer-3: flexible and scalable • MPLS forwarding plane – Use of labels for forwarding Layer-2/3 data traffic – Labeled packets are switched; instead of routed • Leverage layer-2 forwarding efficiency • MPLS control/signalling plane – Use of existing IP control protocols extensions + new protocols to exchange label information • Leverage layer-3 control protocol flexibility and scalability BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public MPLS Basics Topics Basics of MPLS Signalling and Forwarding • MPLS Reference Architecture Service (Clients) • MPLS Labels Layer-3 VPNs Layer-2 VPNs • MPLS Signalling and Forwarding Operations Transport IP/MPLS (LDP/RSVP-TE/BGP) MPLS Forwarding BRKMPL-1101 © 2015 Cisco and/or its affiliates.
    [Show full text]
  • Command 3ME Banana Pepper Label
    24 (c) Special Local Need Label for Use on Banana Peppers EPA SLN No. MI-140007 EPA Reg. No. 279-3158 FOR DISTRIBUTION AND USE ONLY IN MICHIGAN This label for Command® 3ME Microencapsulated Herbicide is valid until May 13, 2024 or until withdrawn, canceled or suspended. IT IS A VIOLATION OF FEDERAL LAW TO USE THIS PRODUCT IN A MANNER INCONSISTENT WITH ITS LABELING. ALL APPLICABLE DIRECTIONS, RESTRICTIONS AND PRECAUTIONS ON THE EPA REGISTERED LABEL MUST BE FOLLOWED. THESE USE DIRECTIONS MUST BE IN THE POSSESSION OF THE USER AT THE TIME OF PESTICIDE APPLICATION. DIRECTIONS FOR USE For ground application of Command 3ME Microencapsulated Herbicide on banana pepper. Make a single broadcast herbicide application at 10.7 to 42.7 fl oz per acre (0.25 to 1 lb ai/A) in a minimum of 10 gallons of water per acre. Use the lower specified rate on course soils and the higher specified rate on fine soils. When applying Command 3ME Microencapsulated Herbicide as a pre-transplant soil treatment, place roots of transplants below the chemical barrier when transplanting. Observe all buffer restrictions noted in the Restrictions section. Additional use of labeled post-emerge herbicide applications may be required where existing grass weeds are present at the time of application. CROP PESTS RATE OF APPLICATION Banana Pepper Lambsquarters (herbicide resistant) Soil Broadcast Rates Pounds Active Ingredient Texture Per Acre* Per Acre Foxtail- Giant, Coarse (light) Soils: (10.7 – 21.3 fl oz) 0.25 - 0.5 Green (sand, loamy sand, sandy Robust loam) Goosegrass Medium Soils: (loam, silt, silt 0.5 – 0.75 loam, sandy clay, sandy clay (21.3 - 32 fl oz) Panicum – loam) Common Fine (heavy) Soils: (silty clay, clay 0.75 - 1 Fall loam, silty clay loam, clay) (32 – 42.7 fl oz) * Select lower to higher rates based on lighter to heavier soil types.
    [Show full text]
  • External Commands
    5/22/2018 External commands External commands Previous | Content | Next External commands are known as Disk residence commands. Because they can be store with DOS directory or any disk which is used for getting these commands. Theses commands help to perform some specific task. These are stored in a secondary storage device. Some important external commands are given below- MORE MOVE FIND DOSKEY MEM FC DISKCOPY FORMAT SYS CHKDSK ATTRIB XCOPY SORT LABEL 1. MORE:-Using TYPE command we can see the content of any file. But if length of file is greater than 25 lines then remaining lines will scroll up. To overcome through this problem we uses MORE command. Using this command we can pause the display after each 25 lines. Syntax:- C:\> TYPE <File name> | MORE C:\> TYPE ROSE.TXT | MORE or C: \> DIR | MORE 2. MEM:-This command displays free and used amount of memory in the computer. Syntax:- C:\> MEM the computer will display the amount of memory. 3. SYS:- This command is used for copy system files to any disk. The disk having system files are known as Bootable Disk, which are used for booting the computer. Syntax:- C:\> SYS [Drive name] C:\> SYS A: System files transferred This command will transfer the three main system files COMMAND.COM, IO.SYS, MSDOS.SYS to the floppy disk. 4. XCOPY:- When we need to copy a directory instant of a file from one location to another the we uses xcopy command. This command is much faster than copy command. Syntax:- C:\> XCOPY < Source dirname > <Target dirname> C:\> XCOPY TC TURBOC 5.
    [Show full text]
  • SAS Programming Tips
    TUESDAY TIPS – SAS PROGRAMMING Weekly Tip for Nov. 3, 2020 Your data dictionary contains some variables that can iterate - for example, the unknown # of COVID tests for an unknown # of infants. How do you manage documentation? A data dictionary for a file based on Electronic Medical Records (EMR) contains variables which represent an unknown number of COVID tests for an unknown number of infants – there is no way to know in advance how many iterations of this variable will exist in the actual data file. In addition, variables in this file may exist for three different groups (pregnant women, postpartum women, and infants), with PR, PP and IN prefixes, respectively. This Tuesday Tip demonstrates how to process such variables in a data dictionary to drive label (and value label) description creation for iterated (and other) labels using SAS functions, as well as other utilities. Using PROC CONTENTS and ODS OUTPUT on an imported data dictionary (example shown above) and a data file from a health care entity, the position ODS OUTPUT object is created, and the column variable is standardized using the UPCASE function. ************************************************************; *** Import Personal Data Dictionary one tab at a time ***; ************************************************************; %macro imptabs(tabn=1, tabnm=identifiers, intab=Identifiers, startrow=10, endcol=H); proc import dbms=xlsx out = temp datafile = " \file.xlsx" replace; RANGE="&intab.$A&startrow.:&endcol.999"; getnames=YES; run; . data labels&tabn.; length label
    [Show full text]
  • MPLS FAQ: Does "No Mpls Ip Propagate-Ttl" on the Ingress PE Router Also Apply to Ipv6 Packets in 6PE Or 6VPE Networks?
    MPLS FAQ: Does "no mpls ip propagate−ttl" on the ingress PE router also apply to IPv6 packets in 6PE or 6VPE networks? Document ID: 118697 Contributed by Luc De Ghein, Cisco TAC Engineer. Dec 23, 2014 Contents Introduction Does "no mpls ip propagate−ttl" on the ingress PE router also apply to IPv6 packets in 6PE or 6VPE networks? Introduction This document describes the impact of the command "mpls ip propagate−ttl" on IPv6 traffic. Does "no mpls ip propagate−ttl" on the ingress PE router also apply to IPv6 packets in 6PE or 6VPE networks? Answer: Yes, it does. This command hides the P routers from both an IPv4 and an IPv6 traceroute. Here is an IPv6 traceroute with "no mpls ip propagate−ttl" configured on the ingress Provider Edge (PE) router. CE1#trace Protocol [ip]: ipv6 Target IPv6 address: 2001:10:100:1::7 Source address: 2001:10:100:1::5 Insert source routing header? [no]: Numeric display? [no]: Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Priority [0]: Port Number [0]: Type escape sequence to abort. Tracing the route to 2001:10:100:1::7 1 2001:10:1:5::1 1 msec 1 msec 1 msec 2 2001:10:1:7::2 [AS 1] [MPLS: Label 23 Exp 0] 2 msec 1 msec 1 msec 3 2001:10:1:7::7 [AS 1] 2 msec 1 msec 2 msec The P routers are not present in the output of the traceroute. This proves that the propagation of Time To Live (TTL) from the IPv6 header to the Multiprotocol Label Switching (MPLS) header does not occur on the ingress PE router for IPv6 packets.
    [Show full text]
  • Copyrighted Material
    Index addresses Numbers & Symbols duplicate address detection, 89 ::/0 unicast address, 81 link-local, 285 ::1/28 unicast address, 81 addressing ::/128 unicast address, 81 classful addressing, 59 10 Gigabit Ethernet, 29 classless addressing, 59–60 10/100Base Ethernet, 29 Ethernet, 25–26 5620 SAM (Service Aware Manager), 7, 14 IPv6 7210 SAS (Service Access Switch), 12–13 anycast addresses, 80, 83–84 7450 ESS (Ethernet Service Switch), 11–12 multicast, 79, 82–83 7705 SAR (Service Aggregation unicast addresses, 79, 80–82 Router), 10–11 IPv4 address structure, 58–59 7750 SR (Service Router), 7, 9–10 IS-IS, 330–331 IP interface, configuration, 66–70 ND (Neighbor Discovery), 89 IS-IS behavior, 343 NSAP, 330 ports unicast addresses, 26, 58 access, 975 adjacencies network, 975 DR, 189–191 routing table, 121 IS-IS, establishing, 333–350 service components, 970 LDP peers, 535, 537 services configuration RSVP-TE Hello message, 623–629 components, 970–971 adjacency database, 124 customers, 971 administrative groups service identifiers, 971–972 CSPF algorithm and, 720–725 subscribers, 971 interfaces, 724 topologies recognized, 163 labs, 752–754 6over4 MPLS, 721 IPv6 packets and, 97–103 ring topology, 725–738 PE1 configuration, 99–100 Type 10 LSAs, 721–722 PE2 configuration, 102 administrative route tags, IS-IS, 421–428 6PE-IPv6 tunneling over MPLS, 648–656 advertising routers, 90 6VPE (IPv6 on VPN Router), 1191–1200 AFI (area format and identifier), 330 labs, 1208–1209 aggregate-prefix-match command, 587 AH (Authentication Header), 303 IPv6 header,
    [Show full text]
  • Release Notes for Cisco IOS Release 11.2(11) Software Feature Packs for Cisco 2500 Series Routers
    Doc. No. 78-4265-02 Release Notes for Cisco IOS Release 11.2(11) Software Feature Packs for Cisco 2500 Series Routers January 26, 1998 These release notes describe the Cisco Internetwork Operating System (Cisco IOS) Release 11.2(11)P feature packs for Cisco 2500 series routers. This document contains the following sections: • Platforms Supported on page 1 • What Is a Feature Pack? on page 2 • Using Cisco Feature Packs on page 2 • Loading Cisco IOS Release 11.2 Software on CiscoPro Routers on page 16 • Installation Tips on page 17 • Installing the Router Software Using a TFTP Server Application on page 18 • Related Documentation on page 22 • Cisco Connection Online on page 24 Platforms Supported The RSL supports the following Cisco 2500 series routers: • CiscoPro CPA2501, CPA2502, CPA2503, CPA2504, CPA2505, CPA2507, CPA2509, CPA2511, CPA2513, CPA2514, CPA2516, CPA2520, CPA2521, CPA2522, CPA2523, and CPA2524 • Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, AS2509-RJ, 2510, 2511, AS2511-RJ, 2512, 2513, 2514, 2515, 2516, 2520, 2521, 2522, 2523, 2524, and 2525 Note The Cisco AS2509-RJ and AS2511-RJ only support software images for Cisco IOS Release 11.2(5)P or later. Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Copyright © 1998 Cisco Systems, Inc. All rights reserved. 1 What Is a Feature Pack? What Is a Feature Pack? The heart of a Cisco IOS software feature pack is a CD-ROM that contains a software image and the Router Software Loader (RSL), a Windows 95 application that loads the image onto the access router or server.
    [Show full text]