Skip to main content
NetApp Knowledge Base

Nblade.vscanNoScannerConn after upgrading to ONTAP version between 9.4 and 9.7

  1. Last updated
  2. Save as PDF
Views:
373
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP was upgraded to a version that is higher than or equal to 9.4 and lower than 9.7
  • Vscan
  • Domain name of privileged user for scanner-pool contains dot (e.g. xxx.yyy.zzz\user1)

Issue

  • Vscan fails to connect due to an error Nblade.vscanNoScannerConn in EMS log
  • The error shows truncated domain name at the first dot ( . )

Example: The actual domain name is "xxx.yyy.zzz", but it appears as "xxx" in error[?] Sun Nov 13 16:17:30 JST [cluster01: kernel: Nblade.vscanConnInvalidUser:notice]: For Vserver "svm1", the vscan connection request coming from client "<Client_IP>" is rejected because the logged-in user "xxx\user1" is not configured in any of the Vserver active scanner pools.
[?] Sun Nov 13 16:32:09 JST [cluster01: nblade2: Nblade.vscanNoScannerConn:EMERGENCY]: Vserver "svm1" has no virus scanner connection.

 

 

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.