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 PR
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
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:
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
>
> Al
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 pro
> 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 enou
Hey,
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.
Please note that you'll need a services pic for vt- interface.
Ch
table-label option in routing-instance must fix it
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Leigh Porter
Sent: Monday, June 18, 2007 2:05 PM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] BGP VPLS support
Hey folks,
When using MPLS on JUNOS
Hey folks,
When using MPLS on JUNOS a directly connected interface route on a PE
router is only assigned a label if there is a route on the PE router
that uses this interface (static or OSPF or BGP). When a route is
present that uses this interface then a label is assigned and the route
makes it i
ssage-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Monika M
> Sent: Thursday, June 14, 2007 6:26 AM
> To: juniper-nsp@puck.nether.net
> Subject: [j-nsp] BGP VPLS support
>
> As per BGP VPLS RFC 4761 section 3.2.2, "if the PE is connected to
> several
>
Monika M
Sent: Thursday, June 14, 2007 6:26 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] BGP VPLS support
As per BGP VPLS RFC 4761 section 3.2.2, "if the PE is connected to
several
u-PEs, it has a distinct VEID for each u-PE. It may additionally have a
VE
ID for itself, if it itself
As per BGP VPLS RFC 4761 section 3.2.2, "if the PE is connected to several
u-PEs, it has a distinct VEID for each u-PE. It may additionally have a VE
ID for itself, if it itself acts as a VE for that VPLS."
Does Juniper support connecting PE to many u-PEs?. I have this doubt as
Juniper allows only
12 matches
Mail list logo
