[j-nsp] Traffic Engineering via LSP

Ramanathan Sethuraman rsethuraman at juniper.net
Thu Jul 29 13:46:06 EDT 2010


Hi,

Can you try this policy and export it to your forwarding table? This will enable the prefix 10.152.42.0/25 to go via TIVIT_to_DIVEO.For other prefixes you need to map to another LSP.For this you need to have another LSP between Point A to B.


lab at r6# show policy-statement mapping
term 1 {
from route-filter 10.152.42.0/25;
then {
install-nexthop lsp TIVIT_to_DIVEO;
accept;
}
}
term 2 {
then 

install-nexthop lsp xxxxx;
accept
}

set forwarding-table export mapping

Thanks
Sethu

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Gabriel Farias
Sent: Thursday, July 29, 2010 7:16 AM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] Traffic Engineering via LSP

Hi members,


I need to do traffic engineering in backbone IP/MPLS from point A to point
B, but just need some prefixes, part of the traffic is sent via TE and I'm
seeing all traffic exiting via TE from point A to B. *What do I need to send
only the prefix 10.152.42.0/25 via TE and not all traffic*?



*Summary*:
Point B:10.251.255.74
Prefix must use the TE: 10.152.42.0/25
Name's VPN traffic: pb-dados
Another prefix you should not use the TE: 10.152.61.128/26

*Configuration used in point A*:

>protocols mpls



label-switched-path TIVIT_to_DIVEO {

    to 10.251.255.74;

    install 10.152.42.0/25 active;

    no-cspf;

    optimize-timer 1;

    primary TIVIT_to_DIVEO_Replica;

}

path TIVIT_to_DIVEO_Replica {

    10.251.0.122 strict;

}

interface lo0.0;

interface ge-3/0/2.0;

interface fxp0.0 {

    disable;

}

interface ae0.0;

interface xe-0/0/0.0;



>protocols rsvp



interface fxp0.0 {

    disable;

}
interface ge-3/0/2.0;

*Expected behavior*:

>show route 10.152.42.0



inet.0: 319 destinations, 319 routes (318 active, 0 holddown, 1 hidden)

+ = Active Route, - = Last Active, * = Both



10.152.42.0/25     *[RSVP/7] 20:35:39, metric 22

                    > to 10.251.0.122 via ge-3/0/2.0, label-switched-path
TIVIT_to_DIVEO



pb-dados.inet.0: 9783 destinations, 21974 routes (9783 active, 0 holddown, 0
hidden)

+ = Active Route, - = Last Active, * = Both



10.152.42.0/25     *[BGP/170] 20:35:39, MED 0, localpref 110, from
10.251.255.1

                      AS path: 65100 ?

                    > to 10.251.0.122 via ge-3/0/2.0, label-switched-path
TIVIT_to_DIVEO

                    [BGP/170] 20:35:39, MED 0, localpref 110, from
10.251.255.2



>traceroute 10.152.42.126 routing-instance pb-dados



traceroute to 10.152.42.126 (10.152.42.126), 30 hops max, 40 byte packets

 1  10.251.0.122 (10.251.0.122)  27.720 ms  27.543 ms  27.621 ms

     MPLS Label=799192 CoS=0 TTL=1 S=1

 2  10.251.40.66 (10.251.40.66)  28.318 ms *  27.481 ms


*Unexpected behavior:*:

>show route 10.152.61.189



pb-dados.inet.0: 9784 destinations, 21974 routes (9780 active, 4 holddown, 0
hidden)

+ = Active Route, - = Last Active, * = Both



10.152.61.128/26   *[BGP/170] 20:59:26, MED 0, localpref 110, from
10.251.255.1

                      AS path: 65100 ?

                    > to 10.251.0.122 via ge-3/0/2.0, label-switched-path
TIVIT_to_DIVEO



>traceroute 10.152.61.189 routing-instance pb-dados



traceroute to 10.152.61.189 (10.152.61.189), 30 hops max, 40 byte packets

 1  10.251.0.122 (10.251.0.122)  27.630 ms  27.527 ms  27.468 ms

     MPLS Label=799192 CoS=0 TTL=1 S=1
 2  10.251.40.66 (10.251.40.66)  27.522 ms *  27.837 ms
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



More information about the juniper-nsp mailing list