Traffic Redirect to IP Next Hop

BGP flow specification as described in BGP Flow-Spec Internet draft draft-ietf-idr-flowspec-redirect-ip-02.txt, Redirect to IP Action is supported. Redirect to IP action provides traffic filtering options for DDoS mitigation in service provider networks. This feature is required to support service chaining in virtual service control gateway (vSCG). Redirect to IP action allows you to divert matching flow specification traffic to a globally reachable address. To configure a static IPv4 flow specification route, include the redirect ipv4-address statement at the [edit routing-options flow route then] hierarchy level in the configuration. To configure a static IPv6 specification route, include the redirect ipv6-address statement at the [edit routing-options flow route then] hierarchy level in the configuration. 

Note: IPv6 is supported only in legacy redirect-to-Nexthop encoding mode. We do not support the new redirect-to-IP encoding format for IPv6.

Junos OS advertises redirect to IP flow specification action using the extended community by default. To configure legacy flow specification redirect to IP specified in the Internet draft draft-ietf-idr-flowspec-redirect-ip-00.txt, BGP Flow-Spec Extended Community for Traffic Redirect to IP Next Hop, include legacy-redirect-ip-action at the [edit group bgp-group neighbor bgp neighbor family inet flow] hierarchy level. To configure BGP to use VRF.inet.0 table to resolve VRF flow specification routes, include secondary-independent-resolution statement at the [edit protocols bgp neighbor family flow] hierarchy level.