New thread on Cisco VRF route leak

Unanswered Question
May 26th, 2009
User Badges:

The purpose of this thread is to seek clarifications. The previous thread posted was too long and difficult to understand. So I thought I made the problem even simpler for understanding.

Following is how the switch, Sw1 is connected to the Core Sw.

Sw1 ----- Core Sw

Following contains the configuration :

** Sw1 **

ip classless

interface GigabitEthernet1/0/14

description TestVRF1

no switchport

ip address


ip route

Core sw

ip vrf clientA

rd 100:110

route-target export 100:110

route-target import 100:110

interface GigabitEthernet1/0/2


no switchport

ip vrf forwarding clientA

ip address

no cdp enable


ip route GigabitEthernet1/0/2

ip route vrf clientA lo1

What I do not understand is why I can't ping from Sw1. Help appreciated.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Harold Ritter Wed, 05/27/2009 - 10:18
User Badges:
  • Cisco Employee,

Try "ip route vrf clientA lo1" instead. It works for me.


alanchia2000 Wed, 05/27/2009 - 16:32
User Badges:

Curious,when I tried the proposed solution:

ip route vrf clientA lo1

I got this error message:

% For VPN routes, must specify a next hop IP address if not a point-to-point interface

Does a Cisco 3750 have anything to do the error?

Anyway, I tried another way which also did not work:

ip route vrf clientA Loopback1

Any clue?

Harold Ritter Thu, 05/28/2009 - 18:00
User Badges:
  • Cisco Employee,


My mistake. This is indeed the normal behavior. I had run my test using an IOS image of mine that didn't have this restriction.

Given this restriction, you will not be able to ping the loopback residing in the global. May I ask what it is that you are trying to achieve with that test?


alanchia2000 Thu, 05/28/2009 - 21:54
User Badges:

This was a simple set up to test the behaviour of VRF. In the actual set up, the loopback interface will not be there, rather, it will be a physcial interface. And what I was planning to achieve was to be assured that I easily diagnose issues with just ping test alone. However, it seems that the global interfaces cannot be ping-ed from the VRF zone. Which may make my diagnostic job a little tougher.


This Discussion