[j-nsp] next-hop address on LAN

[Thomas Salmen]

Hello,

Can anybody suggest what the following might mean?


thomas at nct_ar3# run show route advertising-protocol bgp 172.16.8.2 extensive


orcon_vpn.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

* 10.78.1.0/30 (1 entry, 1 announced)
 BGP group internal type Internal
     Route Distinguisher: 65001:1001
     BGP label allocation failure: Need a nexthop address on LAN  <---- this
     Nexthop: Self
     Flags: Nexthop Change
     Localpref: 100
     AS path: I
     Communities: target: 65001:1001


I'm configuring a VPN between two M-series, cr2 and ar3. The VPN consists of
and ATM PVC connected to cr2 and a GE interface connected to ar3, static
routing only. 



ar3 is learning connected routes for the ATM interface from cr2:

thomas at nct_ar3# run show route table test_vpn 

orcon_vpn.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.78.1.0/30       *[Direct/0] 03:06:58
                    > via ge-1/3/0.205
10.78.1.1/32       *[Local/0] 03:07:00
                      Local via ge-1/3/0.205
10.240.1.0/30      *[BGP/170] 00:02:54, localpref 100, from 172.16.8.2
                      AS path: I
                    > to 172.16.9.4 via ge-1/3/0.200, label-switched-path
pe_nct_cr2




However cr2 isn't learning VPN routes from ar3:

thomas at nct_m02# run show route table test_vpn 

orcon_vpn.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.240.1.0/30      *[Direct/0] 2w4d 11:39:19
                    > via at-0/1/1.100
10.240.1.1/32      *[Local/0] 2w4d 11:39:26
                      Local via at-0/1/1.100




And I can't figure out why. ar3 Config:

rsvp {
    traceoptions {
        file log.rsvp;
        flag packets;
    }
    interface ge-1/3/0.200;
}
mpls {
    label-switched-path pe_nct_cr2 {
        to 172.16.8.2;
    }
    label-switched-path pe_nct_erx02 {
        to 172.16.8.15;
    }
    interface ge-1/3/0.200;
}
bgp {
    group internal {
        local-address 172.16.8.8;
        family inet {
            unicast;
        }
        family inet-vpn {
            unicast;
        }
        peer-as 65001;
        local-as 65001;
        neighbor 172.16.8.2 {
            import ibgp_reflector_import;
            export ibgp_reflector_export;
        }
    }
}

routing-instances {
    test_vpn {
        instance-type vrf;
        interface ge-1/3/0.205;
        route-distinguisher 65001:1001;
        vrf-target target: 65001:1001;
    }
} 


interfaces {
    ge-1/3/0 {
        vlan-tagging;
        mtu 9000;
        unit 200 {
            description "Core Interface";
            vlan-id 200;
            family inet {
                address 172.16.9.8/26;
            }
            family mpls;
        }
        unit 205 {
            description "Test Interface";
            vlan-id 205;
            family inet {
                address 10.78.1.1/30;
            }
        }
    }
    lo0 {
        unit 0 {
            family inet {
                filter {
                    input filter_re;
                }
                address 172.16.8.8/32;
                address 127.0.0.1/32;
            }
        }
    }               
}



Appreciate any advice.

Cheers,
Thomas