[j-nsp] BGP label allocation error...

[ADAM CALLIS]

One other supported solution is to use a vt interface. This allows the
router to process the incoming MPLS packet first, then to send the plain
IP packet back through the process. Note, this requires at least a tunnel
services pic, if not an adaptive services pic to do, and it is difficult to
support. I strongly recommend vrf-table-label. One note of caution, there
are some pics that do not support VRF Table Label. Be sure to check the tech
pubs for your version of software to verify if vrf-table-label is supported.
If the interface is not supported, it cannot be an MPLS facing interface
(family mpls). Example: on board gige pic on M7i didn't support it until 7.x
.

Thanks,
Adam Callis
JNCIE-M #159

On 4/10/06, Alexander Tarkhov <karabass at gmail.com> wrote:

> Hi Brian,
> One very strange static route should solve it.
> If there is no CE router in this VLAN, then you have to manually configure
> some host (/32) route inside the VRF (routing instance) pointing to
> itself.
> This is not well documented, so I can't say why. Here is an example
>
> http://www.juniper.net/techpubs/software/junos/junos75/swconfig75-vpns/html/vpnl3-trouble14.html
> This static route is only required for multiaccess vrf interfaces without
> directly connected CE router. Hope it helps.
>
> -Alexander
>
> P.S. Alternative way of solving this can be use of vrf-table-label
> command,
> which totaly changes label allocation, and brings other advantages too. I
> think it's better to go with simplest solution however.
>
>
>
> On 4/11/06, Brian W. Gemberling <brian at pulltheplug.com> wrote:
> >
> > Hello,
> >
> > I'm trying to help a friend with a problem.  They have a directly
> > connected VLAN on a GE port they want in a VRF.  They have added this
> > interface to the VRF and it works locally.  It, however, is not getting
> > passed via BGP to other routers.  Below is the route,
> >
> > * 65066:101:10.253.0.0/24 (1 entry, 1 announced)
> >   BGP group ibgp-route-reflector-clients type Internal
> >       Route Distinguisher: 65066:101
> >       BGP label allocation failure: Need a nexthop address on LAN
> >       Nexthop: Not advertised
> >       Localpref: 100
> >       AS path: I
> >       Communities: target:65066:101
> >
> >
> > I'm assuming the issue is "BGP label allocation failure: Need a nexthop
> > address on LAN".  I've never seen this error before.  Can anyone shed
> > some light on this for me?  Thanks!
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
>
> --
> * most punctuation intentionally omitted for your temperament.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>