[j-nsp] L3VPN routes seem unresolvable

[Pedro Roque Marques]

Jeff S Wheeler writes:

> Dear list, I am having a great deal of trouble with L3VPN configured
> per Juniper examples in a simple topology.  JUNOS is 7.2R1.7 with no
> E-FPCs available.

> In particular, I can find no documentation to shed light on the
> `Indirect next-hop: 2 no-forward` condition reported on my VPN
> routes.

It means that the software has decided that it doesn't need to create
forwarding resources for that route. 

>  I would expect the routes to be hidden in this condition,
> but in fact they are active and installed into the PFE as discard
> routes.  I presume the discard next-hop is being installed because a
> valid next-hop cannot be computed by rpd.

rpd believes none is needed. Do you happen to have a forwarding-table
export policy ?

> In the below `show route ...` output, a default route is advertised
> by PE1 to PE2.  VPN label information seems to be correctly
> signalled, and a route to PE1's loopback interface is present in
> PE2's inet.3 table.  PE1 is connected directly to PE2 via ATM
> (at-2/2/0.33 on PE1 to at-0/3/0.33 on PE2); PE1's lo0.0 is numbered
> 1.2.3.4, PE2 1.2.3.5, for the purposes of the below example output.

> Any suggestions would be appreciated.

Do you mind providing me w/ a full config ?

thanks,
  Pedro.