Forum Replies

  1. Hi Shaun,

    For CCNP ROUTE this will be enough. They expect you to have an "idea" what MPLS is about but you don't have to configure anything. If you want to learn what MPLS VPN is about, just follow all the lessons in this overview:

    https://networklessons.com/mpls-lessons

    It will explain all the MPLS VPN scenarios.

    Rene

  2. In the lesson CE <-> PE is BGP
    PE <-> P is ospf

    I tried to create a similar lab. I find that there is only a LSP if the router has a route for the destination.
    So how does the P router have an LSP for 5.5.5.5 and 1.1.1.1 ?

    PE1#show mpls forwarding-table 
    Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    
    Label      Label      or Tunnel Id     Switched      interface              
    16         17         4.4.4.4/32       0             Gi0/2      192.168.23.3
    17         Pop Label  192.168.34.0/24  0             Gi0/2      192.168.23.3
    18         Pop Label  3.3.3.3/32       0             Gi0/2      192.168.23.3

    There is no label rule for 5.5.5.5 so how do the packets get routed.
    I read the page many times but I just don't get it.

    PE1 knows to send packets for 5.5.5.5 via 4.4.4.4
    PE1 knows to get to 4.4.4.4 it has to send packets to 192.168.23.3

    somehow MPLS gets involved in the decision. This is a recursive route. It is like MPLS is checked at each stage of the route recursion. Is that what happens or is it some sort of magic interaction between MPLS and iBGP ?

    I tried to do the same thing with a static route

    Gateway of last resort is not set
    
         1.0.0.0/32 is subnetted, 1 subnets
    C       1.1.1.1 is directly connected, Loopback0
         2.0.0.0/32 is subnetted, 1 subnets
    D       2.2.2.2 [90/409600] via 172.16.12.2, 00:00:57, FastEthernet0/0
         3.0.0.0/32 is subnetted, 1 subnets
    D       3.3.3.3 [90/435200] via 172.16.12.2, 00:12:56, FastEthernet0/0
         4.0.0.0/32 is subnetted, 1 subnets
    D       4.4.4.4 [90/437760] via 172.16.12.2, 00:12:56, FastEthernet0/0
         172.16.0.0/24 is subnetted, 3 subnets
    D       172.16.34.0 [90/309760] via 172.16.12.2, 00:12:57, FastEthernet0/0
    D       172.16.23.0 [90/307200] via 172.16.12.2, 00:19:16, FastEthernet0/0
    C       172.16.12.0 is directly connected, FastEthernet0/0
    C    192.168.1.0/24 is directly connected, FastEthernet1/0
    S    192.168.3.0/24 [1/0] via 172.16.34.4
    R1#sh mpls for
    Local  Outgoing    Prefix            Bytes tag  Outgoing   Next Hop    
    tag    tag or VC   or Tunnel Id      switched   interface              
    16     17          3.3.3.3/32        0          Fa0/0      172.16.12.2  
    17     19          4.4.4.4/32        0          Fa0/0      172.16.12.2  
    18     18          172.16.34.0/24    0          Fa0/0      172.16.12.2  
    19     Pop tag     172.16.23.0/24    0          Fa0/0      172.16.12.2  
    20     Untagged    192.168.3.0/24    0          Fa0/0      172.16.12.2  
    21     Pop tag     2.2.2.2/32        0          Fa0/0      172

    S 192.168.3.0/24 [1/0] via 172.16.34.4
    18 18 172.16.34.0/24 0 Fa0/0 172.16.12.2
    20 Untagged 192.168.3.0/24 0 Fa0/0 172.16.12.2

    Why is 192.168.3.0/24 untagged ?

    Stuart

  3. Hi @kayoutoure

    It might help to think about this the other way around, let's say we don't use MPLS but BGP on all P and PE routers. This means that:

    • The P routers have to do a lookup in their routing tables for every destination.
    • The P routers have to know about every destination...this means you'll have to redistribute customer information into BGP.
    • iBGP has to be a full mesh so if you add another P router in your network, you'll have to establish neighbor adjacencies with all other iBGP routers. You can make your life a bit easier with route reflectors and confederations but it's still a lot more work than configuring a router with an IGP like OSPF + MPLS.

    There are a lot of different logical topologies you can run on top of MPLS. For example, services like E-line, E-tree and E-lan are also often used on top of MPLS.

  4. Hello Zaman

    MPLS functions on many vendors’ equipment as it is an open method of data-carrying. Cisco chooses to implement MPLS in combination with CEF because of their similarities in functions and the efficiency this introduces. Essentially, CEF functionality complements MPLS.

    MPLS is like CEF because it generates a table with mappings from incoming labels to outgoing labels and next hop. CEF on the other hand generates a table mapping the incoming packets destination to the outgoing interface and next hop. Both function based on the routing table and are generated on startup, allowing for very fast switching of packets.

    On Cisco devices, CEF and MPLS work together. On the ingress edge router the IP destination network of an unlabelled packet will be looked up in the CEF table which contains a mapping to the outgoing label. This is done for efficiency so that the destination doesn’t have to be looked up in the CEF table, then again in the label forwarding information base (LFIB).

    A Label Switched Path (LSP) defines a path in only one direction. This means that it allows data to flow in only one direction between two endpoints. Establishing two-way communications between endpoints requires a pair of LSPs to be established, one for each direction. Because two LSPs are required for connectivity, data flowing in the forward direction may use a different path from data flowing in the reverse direction. This is a similar concept to the fact that if routing is available from point A to point B, it is not necessarily true that routing exists from point B to point A. It must be explicitly defined.

    The pop label is very different than the untagged label. A popped label is when the penultimate (the second-to-last router) performs a pop of the outer label. The inner label is still there, so it forwards it based on that.

    The Untagged keyword shows up in the output of the show mpls forwarding-table command. What it means is that the router has no output label associated with the forwarding equivalence class (FEC … usually an IP prefix). Since there is no output label, the router cannot perform a label swap (or pop) but has to remove the whole MPLS header.

    In this case, the raw IP packet has to be forwarded based on the routing table and the prefixes found there.

    I hope this has been helpful!

    Laz

61 more replies! Ask a question or join the discussion by visiting our Community Forum