Service engine health degraded with DoS Attack Level Data error
search cancel

Service engine health degraded with DoS Attack Level Data error

book

Article ID: 439722

calendar_today

Updated On:

Products

VMware Avi Load Balancer

Issue/Introduction

  • A Service Engine (SE) may report a low health score with the reason "Security Threat Level Service Engine DoS Attack Level Data."
  • This usually occurs when high numbers of TCP Reset (RST) packets are detected, which can trigger an internal DDoS alert threshold even if legitimate traffic is flowing.
  • Service Engine health score is degraded.




Environment

  • VMware Avi Load Balancer

Cause

  • This issue occurs when the backend server sends an RST for a paired connection, the Service Engine must also send an RST to the client.
  • Every flow probe failure results in a packet drop, increasing the flow_rx_lookup_miss_drop counter. When these drops exceed internal thresholds, the SE triggers a DoS attack alert.
  • Service Engine Health tab indicates:
  • flowtablestat - Show High counts of rst_sent and flow_rx_lookup_miss_drop in SE metrics (high numbers of SE level rst_sent due to high flow probe failures )
  • dosstat - shows increments in non_syn_flood counter.

Resolution

To investigate and resolve the health degradation, follow these steps:

  1. Log in to the Avi Controller Shell
  2. Run the following command to check DoS statistics:
    show serviceengine <SE-Name> dosstat
    show serviceengine <SE-Name> flowtablestat
  3. Verify if the non_syn_flood counter is increasing.
  4. Review the packet captures to identify the source of the RST packets. For example, check if a small number of client IPs are responsible for the majority of resets.
  5. If the resets are coming from non-legitimate IPs, block them at the firewall / upstream gateway level.
  6. If the resets are expected behavior for your application, monitor the metrics.

    Note: Service Engine DoS attack-level metrics are a proactive measure and do not always mean traffic is being dropped incorrectly.

Additional Information

 

  • For more details on DDoS mitigation, see the .
  • To speak with a customer representative or a Support Engineer, see . Scroll to the bottom of the page and click on your respective region.