Skip to main content
NetApp Knowledge Base

vscan scan_request_pending counter on a node stuck in a pending state

Views:
2
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • Vscan

Issue

A persistent value is observed in the scan_request_pending counter for a specific off-box Vscan instance, even when active scanning is functioning and no new scan requests are pending, as below

Cluster1::> statistics show-periodic -instance <svm_name> -interval 1 -iterations 10 -summary true -object offbox_vscan -counter connections_active|scan_latency|scan_request_dispatched|scan_request_pending|scan_request_timedout
Cluster1: offbox_vscan.<svm_name>: 6/29/2026 07:57:07
                           scan     scan    scan
connections     scan request  request request    Complete    Number of
     active latency dispatched  pending timedout Aggregation Constituents
----------- -------- ---------- -------- -------- ----------- ------------
          7  45912us          1       35       0      Yes      2
          7      0us          0       35       0      Yes      2
          7  39958us          2       35       0      Yes      2
          7      0us          0       35       0      Yes      2
          7  14415us          2       35       0      Yes      2
          7      0us          0       35       0      Yes      2
          7  14999us          6       35       0      Yes      2
          7      0us          0       35       0      Yes      2
          7      0us          0       35       0      Yes      2
          7      0us          0       35       0      Yes      2

Multiple remediation attempts, including the following, do not clear the pending count:

  • Restarting the Vscan engine on all antivirus servers
  • Disabling and re-enabling vscan
  • Performing a vscan reset

Despite these actions, the scan_request_pending counter continues to display the same value.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.