[j-nsp] L3VPN routes seem unresolvable

[Jeff S Wheeler]

On Sun, 2005-05-01 at 12:31 -0400, C. Hagel wrote:
> Could you send in a copy of your configs as well as a "show route" from
> a CE device?

I have no routing protocols active to the CE device.  0/0 is a static
route in the vpna instance on PE1.  Below are the relavent portions of
PE1 and PE2 configurations.

Note that I've tried this with just RSVP signalling, with RSVP + LDP
tunneling, and with LDP only.  The first two cases are covered in
Juniper's L3VPN examples.  None of these config variations produced any
change to the routes learnt in PE2's bgp.l3vpn.0 or vpna.inet.0, or
installed a non-discard route in the PFE.  Also, lo0.0 is learnt by OSPF
via RIB export policy.  Adding lo0.0 to the OSPF config as an interface
w/configured metric has no impact other than changing the type of OSPF
route learnt by each router for the other's loopback, and decreasing the
route preference on said routes.

   ge-1/0/0.55    at-2/2/0.33 at-0/3/0.33
        v              V           v
CE1 ---------- PE1 ---------------------- PE2

[edit routing-instances vpna]
jsw at pe1# show
instance-type vrf;
interface ge-1/0/0.55;
route-distinguisher 1.2.3.4:999;
vrf-target target:999:0;
routing-options {
    static {
        route 0.0.0.0/0 {
            next-hop 10.0.0.1;
            community 55555:19;
        }
    }               
}

[edit routing-instances vpna]
jsw at pe2# show
instance-type vrf;
interface lo0.1;
route-distinguisher 1.2.3.5:999;
vrf-target target:999:0;


[edit protocols bgp group iBGPcore]
jsw at pe1# show 
type internal;
local-address 1.2.3.4;
/* import policy here not relavent to L3VPN config */
import BGP-core-import-1;
family inet {
    unicast;
}
family inet-vpn {
    unicast;
}
family l2vpn {
    unicast;
}
peer-as 12345;
neighbor 1.2.3.5 {
    description pe2;
}

[edit protocols bgp group iBGPcore]
jsw at pe2# show 
type internal;
local-address 1.2.3.5;
/* import policy here not relavent to L3VPN config */
import BGP-core-import-1;
family inet {
    unicast;
}
family inet-vpn {
    unicast;
}
family l2vpn {
    unicast;
}
peer-as 12345;
neighbor 1.2.3.4 {
    description pe1;
}


[edit interfaces ge-1/0/0 unit 55]
jsw at pe1# show 
description "VLAN to CE1";
vlan-id 55;
family inet {
    address 10.0.0.2/30;
}
/* should be unnecessary; same problem with or without family mpls */
family mpls;

[edit interfaces lo0 unit 1]
jsw at pe2# show 
family inet {
    address 1.2.3.6/32;
}


[edit protocols mpls]
jsw at pe1# show 
traffic-engineering bgp;
label-switched-path pe1-pe2 {
    to 1.2.3.5;
    ldp-tunneling;
    primary pe1-pe2;
}
path pe1-pe2;
interface at-2/2/0.33;
interface all;
interface ge-1/0/0.55;

[edit protocols mpls]
jsw at pe2# show 
traffic-engineering bgp;
label-switched-path pe2-pe1 {
    to 1.2.3.4;
    ldp-tunneling;
    primary pe2-pe1;
}
path pe2-pe1;
interface at-0/3/0.33;
interface all;


[edit protocols rsvp]
jsw at pe1# show 
interface at-2/2/0.33 {
    subscription 75;
}
interface all;

[edit protocols rsvp]
jsw at pe2# show 
interface at-0/3/0.33 {
    subscription 75;
}
interface all;


[edit protocols ldp]
jsw at pe1# show 
interface at-2/2/0.33;
interface all;
interface lo0.0;

[edit protocols ldp]
jsw at pe2# show 
interface at-0/3/0.33;
interface all;
interface lo0.0;


[edit protocols ospf]
jsw at pe1# show 
traffic-engineering;
/* for example purposes, accept from protocol direct */
export RIB_to_OSPF;
prefix-export-limit 1000;
area 0.0.0.0 {
    interface at-2/2/0.33 {
        metric 15;
    }
}

[edit protocols ospf]
jsw at pe2# show 
traffic-engineering;
/* for example purposes, accept from protocol direct */
export RIB_to_OSPF;
prefix-export-limit 1000;
area 0.0.0.0 {
    interface at-0/3/0.33 {
        metric 15;
    }
}