Skip to main content
NetApp Knowledge Base

Vscan server shows disconnected even though the vscan software engine service running on the vscan server

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

Applies to

  • ONTAP 9
  • McAfee/Trellix
  • Vscan

Issue

  • Vscan server shows disconnected and no disconnect reason mentioned when running the following command:

cluster1::> vserver vscan connection-status show-not-connected-vserver svm1-instance

Node: node1
Vserver: svm1
Server: 4.4.4.4
Server Status: disconnected
Server Disconnect Reason: -

  • Ping is successful between Vserver data LIF and Vscan server
  • ONTAP AV connector service is running from Vscan server
  • AV connector is able to poll the data LIFs and can confirm from avshim logs:
11/07/22-03:34:29.481Z Issuing REST API network query to 10.1.1.1 for LIF discovery.
11/07/22-03:34:29.700Z Successfully parsed JSON data. Number of records returned are 4
11/07/22-03:34:29.700Z [MgmtHost::FetchVlifs] vserver:[svm1], node:[node1], exists:[1]
11/07/22-03:34:29.700Z [MgmtHost::FetchVlifs] vserver:[svm1], node:[node1], exists:[1]
11/07/22-03:34:29.700Z [MgmtHost::FetchVlifs] vserver:[svm1], node:[node2], exists:[1]
11/07/22-03:34:29.700Z [MgmtHost::FetchVlifs] vserver:[svm1], node:[node2], exists:[1]

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.