Add Flow Redirect Health-Check Ping Success Option in ExtremeXOS User and Command Reference Guides
Configures the ping interval, miss count, and success for a nexthop in the flow redirection policy.
|flow_redirect_name||Specifies the name of the flow redirection policy.|
|ip_address||Specifies the IPv4 or IPv6 address of the nexthop.|
|seconds||Specifies the number of seconds between pings. The default is “2”.|
|number||Specifies the number of misses allowed. The default is “2”.|
|success||Specifies a number of consecutive ping successes required to declare that a nexthop is up.|
|successes||Sets the value for the number of consecutive successful pings to declare that a nexthop is up. Range is 1 to 256. The default is 4.|
The default for ping interval is 2 seconds.
The default for number of misses is 2.
The default for number of successes is 4.
Use this command to set a ping interval, miss count, and ping success. When the ping response is not received within the interval seconds * (number +1), the nexthop is considered to be dead and a new candidate is selected from the remaining active nexthops.
The following command configures a ping interval of 3 seconds, miss count of 3, and success count of 3 for the nexthop 10.1.1.1 in the flow redirection policy flow 3:
# configure flow-redirect flow3 nexthop 10.1.1.1 ping health-check interval 3 miss 3 success 3
This command was first available in ExtremeXOS 12.1.
Support for IPv6 flow-redirection policies was added in ExtremeXOS 12.7.
The success option was added in ExtremeXOS 16.2.5-Patch1-13.
This command is available for IPv4 and IPv6 flow-redirection policies on the platforms listed for the Policy Based Routing feature in the ExtremeXOS 16.2 Feature License Requirements document.