[j-nsp] (no subject)

[Keegan Holley]

the first one is going to a IP next hop and packets require an IP look up.
 Either it's not using mpls or is only using the inner (vpn) label for that
hop.  The second is taking a real-live lsp and does not perform an IP
lookup, so no IP next hop is needed, just an LSP and a label to push.

On Fri, Apr 29, 2011 at 8:18 AM, Chuck Anderson <cra at wpi.edu> wrote:

> On Fri, Apr 29, 2011 at 01:12:22PM +0100, ibariouen khalid wrote:
> > show route :
> >
> > 10.41.2.32/30      *[OSPF/10] 18:49:01, metric 4
> >                       *to 10.41.144.6* via ge-1/1/0.0
> >                     > via so-1/3/1.0
> >
> > show route table GG_jk
> >
> > 10.160.31.10/32    *[BGP/170] 6d 01:17:54, localpref 100, from 10.41.0.1
> >                       AS path: I
> >                     > via so-1/3/1.0, label-switched-path
> fes22cr2-to-cascr1
> > Question :
> > would someone tell me why i have in the first one "to  X.X.X.X" and not
> for
> > other routes ??
>
> The second table looks like a l3vpn routing-instance with MPLS LSPs
> for next-hops.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>