[j-nsp] cspf to secondary loopback

[Lewis, Charles]

Another option to consider is defining the LSP and setting the install
option:

label-switched-path my-lsp {
    to <primary loopback on remote router>;
    install <secondary loopback on remote router>/32;
    }

This causes the secondary address to be injected into inet.3 and thus
any  BGP prefix advertised from the remote router with its secondary
loopback address as a nexthop will cause traffic to that prefix to
follow the appropriate LSP.  This allows you to utilize whatever cspf
features you might require without any difficulty.

CHL

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Stefan Mink
Sent: Wednesday, July 27, 2005 4:12 AM
To: Rafal Szarecki (WA/EPO)
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] cspf to secondary loopback


Rafal Szarecki (WA/EPO) wrote:
> 1. use no-cspf keworks under LSP definition, and creat ERO manualy

thats how Armin solved it, but you obviously loose options

> or,
> 
> 2. establish two LSP toward the same primary IP address, and use 
> policy under [routing-option forwarding-table] to select which LSP 
> should be use for particular packets/traffic.

that's an interesting one; I think whats not working here anymore is
that you can do TE on the BGP-nexthop basis, i.e. send all traffic for
BGP routes which have nexthop xyz into LSP A and for nexthop abc into
LSP B (which would work with the first solution).

   tschuess
             Stefan
-- 
Stefan Mink, Schlund+Partner AG (AS 8560)
Primary key fingerprint: 389E 5DC9 751F A6EB B974  DC3F 7A1B CF62 F0D4
D2BA