Thank You for the answer, Yes I want implement destination based remote-triggered black holes, but with a twist.
For exaple
my local network is 10.10.0.0/24 advertised to the MX80 router by a core switch using OSPF
ISP 1 ==bgp== MX80 ===bgp==ISP 2
| 10.0.0.1/24
|
OSPF
|
| 10.0.0.2/24
CORE SWITCH -10.10.0.1/24
ISP 1 will black hole routes with community 123:666.
i Want to advertise 10.10.0.10/32 with community 1234:666 to MX80 by bgp from some internal peer, so it will readvertise this route only to ISP 1.
I need 10.10.0.10/32 still be rechable from ISP 2 and this is impossible if I import 10.10.0.10/32 directly and apply next-hop discard to it. Next-hop for 10.10.0.0/24 network is dynamic and I dont want to specify static next-hoop address for the 10.10.0.10/32 route.
I need MX80 to readvertize this route to some peers (this is easy) but don't install this route in to the forwarding engine and for 10.10.0.10 use less specyfic 10.10.0.0/24 route advertized by core
The route table on MX80 should be
10.10.0.10/32 next-hop discard [not installed]
10.10.0.10/24 next-hop 10.0.0.2
packets from iSP 2 for 10.10.0.10 should be forwarded to 10.0.0.2 not discarded
packets from iSP 1 for 10.10.0.10 should be discarded (ISP 2 got 10.10.0.10/32 with community 123:666)