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. Cheers, Erdem On 6/18/07, Leigh Porter <[EMAIL PROTECTED]> wrote: > 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 into bgp.l3vpn.0 > > Is there a way of changing this behavior? I would like to plug some > servers directly into a PE router routing-instance and have then > reachable, but the interface routes do not make it to the l3vpn table, > even if I explicitly ask them to be with a policy. > > Thanks, folks, > Leigh Porter > > > _______________________________________________ > 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
