[j-nsp] next-hop driving me crazy

[Christian]

Hello,
Use a ttl on the bgp session with the customer -
Rgds,

C.

Le 26/04/2013 16:26, Alex Arseniev a écrit :
> Works fine for me in the lab on MX80+JUNOS 12.3 ( I use BGP-LU though, 
> too busy to change to regular "inet unicast":-)
>
> [edit logical-systems MX2-RR]
> aarseniev at mx80# run show route logical-system MX2-RR protocol bgp 
> extensive
>
> inet.0: 29 destinations, 30 routes (27 active, 0 holddown, 2 hidden)
> 198.18.0.6/32 (1 entry, 1 announced)
> TSI:
> KRT in-kernel 198.18.0.6/32 -> {indirect(1048668)}
>        *BGP    Preference: 170/-101
>                Next hop type: Indirect
>                Address: 0x26e8010
>                Next-hop reference count: 6
>                Source: 198.18.0.11
>                Next hop type: Discard
>                Protocol next hop: 192.0.2.1
>                Push 299904
>                Indirect next hop: 29941d8 1048668 INH Session ID: 
> 0x280008
>                State: <Active Int Ext>
>                Local AS: 50928 Peer AS: 50928
>                Age: 5:14       Metric2: 0
>                Validation State: unverified
>                Task: BGP_50928.198.18.0.11+179
>                Announcement bits (2): 3-KRT 5-Resolve tree 2
>                AS path: 31133 50928 I (Looped: 50928)
>                Communities: 56666:56666
>                Accepted
>                Route Label: 299904
>                Localpref: 100
>                Router ID: 198.18.0.11
>                Secondary Tables: inet.3
>                Indirect next hops: 1
>                        Protocol next hop: 192.0.2.1 Metric: 0
>                        Push 299904
>                        Indirect next hop: 29941d8 1048668 INH Session 
> ID: 0x280008
>
> [edit logical-systems MX2-RR]
> aarseniev at mx80# show policy-options policy-statement set-nh
> term 1 {
>    from {
>        protocol bgp;
>        community 56666:56666;
>    }
>    then {
>        next-hop 192.0.2.1;
>        accept;
>    }
> }
> [edit logical-systems MX2-RR]
> aarseniev at sadok# show routing-options
> static {
>    route 192.0.2.1/32 discard;
> }
>
>
> ----- Original Message ----- From: "Eric Krichbaum" <eric at telic.us>
> To: <juniper-nsp at puck.nether.net>
> Sent: Friday, April 26, 2013 2:36 PM
> Subject: [j-nsp] next-hop driving me crazy
>
>
>> This should be simple but I can't get the behavior I want.
>>
>> Blackhole scenario.  Customer set community, I want to see that 
>> community
>> and set next-hop to an address I have with a discard.  I've tried both a
>> discard interface and a basic static route.  Those seem ok either way.
>>
>> set routing-options static route 192.0.2.1/32 discard
>>
>> Route comes in and is accepted by policy.  With no next-hop 192.0.2.1
>> action, I see it as a valid route so I know the policy is happening.  
>> When I
>> add the next-hop action, the route becomes "Next hop type: Unusable" 
>> with
>> "Inactive reason: Unusable path".  I don't see anything special about 
>> this
>> and what I translated from my cisco versions doesn't look all that 
>> different
>> from various black hole presentations I find.
>>
>> Anyone have a magic answer?
>>
>> Thanks,
>> Eric
>>
>>
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp