legacy-redirect-ip-action
Syntax
legacy-redirect-ip-action {
send;
receive;
}
Hierarchy Level
[edit protocols bgp group group-name family (inet | inet-vpn) flow], [edit protocols bgp group group-name neighbor address family (inet | inet-vpn) flow], [edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet-vpn) flow], [edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet-vpn) flow]
Description
Configure the legacy redirect to IP action for flow specification routes to provide traffic filtering options for DDos mitigation in service provider networks. You can choose to accept legacy redirect to IP action as 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, . You can also configure BGP to advertise the redirect to IP action as a legacy redirect attribute.
If legacy encoding configuration is modified, then use
the clear bgp neighbor soft command to reevaluate the routes
and for legacy encoding to take effect.
Options
| send | Advertise the redirect action as legacy redirect attribute. Specify this option to encode redirect to IP action as flow spec redirect to IP next-hop attribute and advertise the next-hop attribute with the redirect address. |
| receive | Accept legacy encoded redirect-to-ip action attribute. The legacy encoded redirect to IP action is ignored. Specify this option to accept and process the legacy encoded redirect to IP and to generate the redirect-to-ip community for sending to peers that support only new encoding of redirect to IP action. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 18.4R1.