PPP over Frame Relay PE/CE with MPLS Route Leaking

Is there a simpler way?

 

I've found it helpful to give myself a challenge of making connectivity from all devices at the end of a completed lab to the "Internet." The Internet in my case is simply a connection to R1's Fa0/1 interface where an FTP servers sits on the LAN to hand out the next LAB's configuration files so I don't do a whole bunch of copy and pasting.

Well, today was a bit more challenging than I expected for BB1. After finishing VOLII - Lab 3 Troubleshooting,  I proceeded to give the devices connectivity to the FTP server. This lab deals with MPLS VPNs, so I have to give most of the devices Internet Access. After learning the jist of how this works, I proceeded to configure. Here is what I came up with at the end:

 

Initial Traffic: BB1 --> R6 (Tunnel through SW4 MPLS) --> R4 --> R1 --> FTP Server [4 hops]

Return Traffic: FTP Server --> R1 --> R4 --> SW2 --> SW3 --> R5 (Tunnel through R4 and SW4 for MPLS) --> R6 [6 hops]

 

With the return traffic I could have gone from R4 to SW2 back to R4, but its still roundabout regardless. This happens because I can't advertise the 54.X.8.0 network into the Global Routing Table on R6. From what I read you are suppose to configure on R6: ip route 54.X.8.0 255.255.255.0 {attached VRF interface} {VRFnext-hop}. Well, the VRF interface on R6 is a virtual-template / virtual-access setup, and those interface types are not available in a static route. So in order for me to get the CE/PE network advertised, I configured this on R4 instead: ip route 54.X.8.0 255.255.255.0 f0/0 10.3.254.255. This sends traffic from the Internet (via R1, R4) to SW2, which is actually the opposite way of the direct path (R1, R4, [Tunnel through SW4], R6, BB1). It works, but I'm wondering if there is a command variation I can use on R6 to put the vrf virtual-template interface in the global routing table to use the direct path to BB1 for return traffic. 

 

Thanks

Comments

  • Can anyone tell me how to get a "customer" route in the global routing table when the VRF interface is a virtual-template?

    On Nov 17, 2011 9:43 PM, "ajCCIE2b" <[email protected]> wrote:

    Is there a simpler way?

     

    I've found it helpful to give myself a challenge of making connectivity from all devices at the end of a completed lab to the "Internet." The Internet in my case is simply a connection to R1's Fa0/1 interface where an FTP servers sits on the LAN to hand out the next LAB's configuration files so I don't do a whole bunch of copy and pasting.

    Well, today was a bit more challenging than I expected for BB1. After finishing VOLII - Lab 3 Troubleshooting,  I proceeded to give the devices connectivity to the FTP server. This lab deals with MPLS VPNs, so I have to give most of the devices Internet Access. After learning the jist of how this works, I proceeded to configure. Here is what I came up with at the end:

     

    Initial Traffic: BB1 --> R6 (Tunnel through SW4 MPLS) --> R4 --> R1 --> FTP Server [4 hops]

    Return Traffic: FTP Server --> R1 --> R4 --> SW2 --> SW3 --> R5 (Tunnel through R4 and SW4 for MPLS) --> R6 [6 hops]

     

    With the return traffic I could have gone from R4 to SW2 back to R4, but its still roundabout regardless. This happens because I can't advertise the 54.X.8.0 network into the Global Routing Table on R6. From what I read you are suppose to configure on R6: ip route 54.X.8.0 255.255.255.0 {attached VRF interface} {VRFnext-hop}. Well, the VRF interface on R6 is a virtual-template / virtual-access setup, and those interface types are not available in a static route. So in order for me to get the CE/PE network advertised, I configured this on R4 instead: ip route 54.X.8.0 255.255.255.0 f0/0 10.3.254.255. This sends traffic from the Internet (via R1, R4) to SW2, which is actually the opposite way of the direct path (R1, R4, [Tunnel through SW4], R6, BB1). It works, but I'm wondering if there is a command variation I can use on R6 to put the vrf virtual-template interface in the global routing table to use the direct path to BB1 for return traffic. 

     

    Thanks




    INE - The Industry Leader in CCIE Preparation

    http://www.INE.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
  • Can anyone tell me how to get a "customer" route in the global routing table when the VRF interface is a virtual-template?

    This discussion might help you, routing with global option?

    https://supportforums.cisco.com/thread/2053150

    HAPPY STUDY

    [:D]

  • A variation of this did work. I created a loopback interface with a host IP address, put it in the VRF and created a global static route pointing to it. I didn't have to specify the next hop. Once the packet is routed to the Loopback with is a part of the VRF, the next routing decision is made by the VRF's routing table. Thanks NNN.


    On Sat, Nov 19, 2011 at 10:27 AM, nnn <[email protected]> wrote:

    imageajCCIE2b:
    Can anyone tell me how to get a "customer" route in the global routing table when the VRF interface is a virtual-template?


    This discussion might help you, routing with global option?

    https://supportforums.cisco.com/thread/2053150

    HAPPY STUDY

    Big Smile




    INE - The Industry Leader in CCIE Preparation

    http://www.INE.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • A variation of this did work. I created a loopback interface with a host IP address, put it in the VRF and created a global static route pointing to it. I didn't have to specify the next hop. Once the packet is routed to the Loopback with is a part of the VRF, the next routing decision is made by the VRF's routing table. Thanks NNN.

    Good to know.

    HAPPY STUDY

    [:D]

Sign In or Register to comment.