vrf-table-label adds an IP lookup on top of mpls lookup. In other
words, you can process/examine the packet based on its encapsulated IP
header.

'discard' is not a physical next-hop, so if I did not misunderstand
your question, the answer is yes.

Cheers,
Erdem

On 6/19/07, Leigh Porter <[EMAIL PROTECTED]> wrote:
>
> So the vrf-table-label stick ALL routes in the vrf into the bgp.l3vpn
> table to be propagated to other PE routers?
>
> What happens if you want to originate a default route in say OSPF from a
> PE router to the CE router using OSPF and a static route with discard?
> The route will be propagated throughout the whole VPN wouldn't it?
>
> --
> Leigh
>
>
> Erdem Sener wrote:
> > Here are the limitations:
> >
> > http://www.juniper.net/techpubs/software/junos/junos83/swconfig83-vpns/id-10993840.html
> >
> > Cheers,
> > Erdem
> >
> > On 6/19/07, Manu Chao <[EMAIL PROTECTED]> wrote:
> >
> >> AFAIK vrf-table label only work on a broadcast interface
> >>
> >>
> >> On 6/18/07, Amos Rosenboim <[EMAIL PROTECTED]> wrote:
> >>
> >>> Hello,
> >>>
> >>> Another workaround which we used (and got from this list as well) is
> >>> to configure "dummy" static routes
> >>> Something like route 172.16.80.1/32 next-hop 172.16.80.1
> >>>
> >>> Also vrf-table label does not work on 100% of the pics, I don't have
> >>> a reference to the pic matrix, but I recall we had a problem with the
> >>> 10 X Channelized E1 pic.
> >>>
> >>> Regards
> >>>
> >>> Amos
> >>>
> >>> On Jun 18, 2007, at 6:21 PM, [EMAIL PROTECTED] wrote:
> >>>
> >>>
> >>>>>  You need to use eighter vrf-table-label in the routing instance, or
> >>>>> configure a vt- interface with family inet and mpls (no addresses)
> >>>>> and
> >>>>> put it in the instance to have your 'direct' route(s) installed in
> >>>>> your mpls cloud.
> >>>>>
> >>>> family mpls is not needed on the vt-interface, family inet is enough.
> >>>>
> >>>> Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
> >>>> _______________________________________________
> >>>> juniper-nsp mailing list juniper-nsp@puck.nether.net
> >>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>>>
> >>> _______________________________________________
> >>> juniper-nsp mailing list juniper-nsp@puck.nether.net
> >>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>>
> >>>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp@puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> >>
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to