Scribd Logo
Upload

Welcome to Scribd!

  • MPLS H Hassan

    Uploaded by

    Manuel Ferraz Monteiro
    11 views7 pages

    Original Title

    MPLS H HASSAN

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    11 views7 pages

    MPLS H Hassan

    Uploaded by

    Manuel Ferraz Monteiro

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    of 7
    What is MPLS? MPLS (Multi Protocol Label Switching). Multi protocol. you can tunnel anything...IP, IPv6, Ethernet, PPP, frame-relay, etc. Label switching: forwarding is done based on labels, not by looking up the destination in the routing table. 2.2.2.2 cust-1-b - customer 1 uses the ISP to have connectivity with the other site - eBGP —=>—CE (Customer Edge) and PE (Provider Edge) to exchange prefixes. so all internal (P) routers of the ISP have to run iBGP or they don’t know where to forward their packets to. ( we need to solve this problem ) - our goal is to have connectivity between two customer sites, so The only routers that need to know how to reach the customer sites are fhe PE routers Solution >> build any tunnel between the PE routers like > GRE - now we can have a BGP free core MPLS can do anything that any of the - only two places where we need BGP, eBGP between the PE and CE router. iBGP between two PE routers. other tunneling protocols support and it can do a lot more than that so we can replace the GRE tunnel with MPLS >> configure MPLS on all sp routers provider routers has no idea about 1.1.1.1 or 2.2.2.2 so Normally this traffic should be dropped .However, since we enabled MPLS we are now using labels for our forwarding decisions. The MPLS header is added in between the L2 and L3 header That’s why we call it a “layer 2.5" protocol CE. (last device in the customer’s network) could be a L2 or L3 device. This de dc t MPLS. PE . (owned by the ISP and sits at the edge of the ISP’s network). -it receives packets or frames from the customer and will then add a MPLS label to it and forwards towards the core. -called LER (Label Edge Router). P .(owned by the ISP and sits at the middle of the ISP’s network). it switches packets based on their labels or removes the labels. — called LSR (Label Switch Router) or transit router. three actions we can perform with labels. Label push: adding a label to a packet. Label swap. replacing a label with another value. Label pop: removing the label. called penultimate hop popping receive ip packet, 1 1 1 1 receive label push label receive ip packet, route it cust-1-a sending an pop it ip packet ISP i receive label Label Format. swap it ‘Label value. value of the label.20 bits i TTL: time to live 8 bits EXP: three experimental bits.used for QoS. 3 bits S. “bottom of stack” 1 bit. - set to one > last MPLS header. set to zero > one or more MPLS headers left. MPLS uses a protocol called LDP (Label Distribution Protocol) LDP is a protocol that automatically generates and exchanges labels between routers. Each router will locally generate labels for its prefixes and will then advertise the label values to its neighbors. It’s a standard, based on Cisco’s proprietary TDP (Tag Distribution Protocol). LDP first establishes a neighbor adjacency before it exchanges label information. 1- send UDP multicast hello packets to discover other neighbors. 2- build the neighbor adjacency using a TCP connection 3- use the TCP connection to exchange any label information. ~ The hello packets are sent to multicast address 224.0.0.2 using source/destination UDP port 646. - Each router has a unique ID called the LSR (Label Switch Router) ID. The two routers will send multicast hello packets on their physical ports Within this hello packet, they will advertise a transport Ip address. (loopback) This IP address is then used to establish the TCP connection between the two routers. ig0/0 multicast Idp hello gig0/1 wu st tcp connection lol <<>> neighbor adj oS 102 transport ip add - RiB is your routing table LDP only form a single neighbor adjacency - similar to BGP // When we use BGP we have to use the update-source command to select the source, LDP does it automatically. - FIB is your forwarding table with MPLS we use LDP, we locally generate a label for each prefix at the RIB, This information is then added to the LIB (Label Information Base). LIB is used to build the LFIB (Label Forwarding Information Base). When the router has to forward a packet with a label, it will use the LFIB for forwarding decisions. The LIB is similar to the RIB but it’s used to store labels for prefixes. The LFIB is similar to the FIB, it?s used for actual forwarding of MPLS packets. the routers will exchange the label information in their LIBs to tell each other what label values to use for different prefixes. MPLS L3 VPN. Layer 3.- customer will run any routing protocol with the service provider, VPN: routing information from one customer is completely separated from other customers and tunneled over the service provider MPLS network. TiPes oF Pek + Peev-so-Yeer Yoke to TON Col ue ovr Broke m Yo Fore HEIRS vedere us (Ast) oP rane aYers Conmecrion amd Brotocals For %u i aos” SPoktoSh iP SPF neIdW Nob Ker vauter ViPes of VPw:. -aVerlar:. See sre SMOKE ' TSP doesn't Prevvet HH aoe Connecktons For You ssn ost ar (i) — ub _» alSe Cob ale t1.29 2222 cust-1-b cust-1-a cust-2-b cus o-a - Each customer of the SP will use a different VRF. - So Instead of using a single global routing table, we use multiple routing tables. use can just use VRFs everywhere instead of MPLS. but there’s one downside for that. >>>>> all SP routers will have to participate with routing & VRFs - customer 1 wants to run OSPF between their two sites > we have to configure OSPF on all SP routers for their VRF. ~ This is not a scalable solution so we will configure the VRFs only on the PE routers. The core of the service provider network (P router) will only do switching based on labels. - we will use MPBGP between the PE routers >> share information from the VRFs. ISP Routers cust blue & red can use same subnets without any overlapping problem because we will use a RD (Route Distinguisher) to make the prefix unique — RD is carried along with a route via MP-BGP when exchanging VPN routes with other PE routers. new update net 1.1.1.1/32 lo1 -1.1/32 as15 to what-eust does this prefix belong? ipv4 prefix 32 bit 15.1 1.1.1.1/32 20.2 1.1.1.1/32 BGP vpnv4 unicast table . (Sr eee A route target. is kind of like a little tag that is 15.1.1.1.1.1/32 attached to a route 20.2.1.1.1.1/32 - can be used to share routes between VRFs. We can apply route targets to a VRF to control the import and export of routes among it and other VRFs. - 8 byte value that uses the same format as the RD (ASN.XX). 15.1.1.1.1.1/32 —S— 20:2:1.1.1.1/32 — i what vef will i export these VPNv4 routes We use a RT (Route Target) to decide in which VRF we import and export VPNv4 routes. Its advertised between PE routers by using a BGP extended community value The RT gives us a lot of control over our VPNv4 routes. Do you want to give customer 2 access to the networks behind customer 1 or not ? ~ VRFs, MP-BGP, RD and RT occurs on the control plane. - for data plane we use MPLS label (transport label) and VPN label - PE router needs a VPN label to decide whether to forward the packet to cust 1 or 2 ip packet, receive label abe | L-E-Td 2.2.2.2, wap ) cust-1l-a (IP)+(LABEL) (ct)

    You might also like