Routing

suppose 1.1.1.1/32 has 2 entry in inet.0

1: isis  1.1.1.1/32 15

2:rsvp 1.1.1.1/32   7

which one will be picked

Hi,

When you configure "traffic-engineering mpls-forwarding" , LSPs are used for forwarding but are excluded from route selection. So, in your case, ISIS route will be in the routing table as the active route, however RSVP route will be used to forward to the destination 1.1.1.1/32.

The following link explains clearly.

http://www.juniper.net/techpubs/en_US/junos12.2/topics/usage-guidelines/mpls-configuring-traffic-engineering-for-lsps.html

Regards,

Moses N

hi,Mose

in my understanding,the policy is for route selection,right?

Can you post the policy and where it is applied ?

it works

Hi,

Your policy will match the active route in the routing table. ( ISIS route , since you have traffic-engineering mpls-forwarding" configured).

How did you determine that RSVP route is matched by policy?

Can you show me the

"sh route  1.1.1.1/32 extensive "

sh route advertising-protocol bgp 100.100.100.5  1.1.1.1/32 extensive"

Rgds,

Moses N

it seems  this command  works in forwaording plane

No. ISIS route is active. Policy will match the active route.

 run show route 1.1.1.1 extensive

inet.0: 166 destinations, 435 routes (166 active, 0 holddown, 0 hidden)
1.1.1.1/32 (3 entries, 2 announced)
        State: <FlashAll CalcForwarding>
TSI:
KRT in-kernel 10.200.1.1/32 -> {Push 303472}
IS-IS level 2, SPF version 532, currentPage 0 idx 0 Type 1 val 91ac888
        @IS-IS  Preference: 18
                Level: 2
                Next hop type: Router
                Address: 0x9084558
                Next-hop reference count: 4
                Next hop: 10.2.2.6 via em2.25
                Next hop: 10.2.2.22 via em2.35, selected
                State: <Active Int>
                Local AS: 4012345678
                Age: 6:03       Metric: 10
                Task: IS-IS
                Announcement bits (4): 0-LDP 4-BGP RT Background 5-Resolve tree 4 6-Aggregate
                AS path: I
        #RSVP   Preference: 7/1
                Next hop type: Router, Next hop index: 1821
                Address: 0x91bbb98
                Next-hop reference count: 18
                Next hop: 10.2.2.22 via em2.35 weight 0x1, selected
                Label-switched-path r5-r1
                Label operation: Push 303472
                Label TTL action: prop-ttl
                State: <ForwardingOnly Int>
                Inactive reason: Forwarding use only
                Local AS: 4012345678
                Age: 5:40       Metric: 10
                Task: RSVP
                Announcement bits (1): 1-KRT
                AS path: I

great comment

Label distribution will be from the actual forwarding information.

That's the reason that you are seeing the RSVP label "Swap" operation.