Skip to main content
NetApp Knowledge Base

SWS Agent does not automatically reconnect during a failover back

  1. Last updated
    Apr 4, 2025
  2. Save as PDF
Views:
61
Visibility:
Public
Votes:
0
Category:
data-infrastructure-insights
Specialty:
oci
Last Updated:
4/4/2025, 2:20:58 PM

Applies to

  • Metro Cluster (MCC)
  • Cloud Insight (CI)
  • Storage Workload Security (SWS)

Issue

  • After a switchover/failover back, the state of both data collectors (the source SVM and destination SVM) in ‘error’ status
  • Agent log (xxxxx-xxxx-xxxx-xxxx-xxxxx1 DC1, xxxxx-xxxx-xxxx-xxxx-xxxxx2 DC1-MCC):

[INFO] [prod] [xxxxx-xxxx-xxxx-xxxx-xxxxxxxx] [xxxxx-xxxxx-xxx-xxxx-xxxxxx] [agent-AgentDataSourceStateManagerActor] - All collector health status has been updated- stateMap: [Map(xxxx-xxxx-xxxx-xxx-xxxxx -> running, xxxxxx-xxxx-xxxx-xxxx-xxxxx2 -> error, xxxxx-xxxx-xxxx-xxxx-xxxxx1 -> error, xxxxx-xxxx-xxxx-xxxx-xxxxxx -> running, xxxxx-xxxx-xxxx-xxxx-xxxxxx -> error, xxxxx-xxxx-xxxx-xxxx-xxxxxx -> error)], statusMap: [Map(xxxxx-xxxx-xxxx-xxxx-xxxxxx -> Collector is running., xxxxx-xxxx-xxxx-xxxx-xxxxxx -> Connector is in error state. Service name: audit. Reason for failure: No valid data interface (role: data, data protocols: NFS or CIFS or both, status: up) found on the SVM., Service name: inventoryVolume. Reason for failure: Failed to refresh inventory for volume type of items. Reason: Connection error to Storage System <IP>: Connection timed out (Connection timed out), xxxxx-xxxx-xxxx-xxxx-xxxxxx -> Connector is in error state. Service name: audit. Reason for failure: No valid data interface (role: data, data protocols: NFS or CIFS or both, status: up) found on the SVM., xxxxx-xxxx-xxxx-xxxx-xxxxxx -> Collector is running., xxxxxx-xxxx-xxxx-xxxx-xxxxx2 -> Connector is in error state. Service name: audit. Reason for failure: No valid data interface (role: data, data protocols: NFS or CIFS or both, status: up) found on the SVM., Service name: inventoryVolume. Reason for failure: Failed to refresh inventory for volume type of items. Reason: Connection error to Storage System <IP>: Connection refused (Connection refused), xxxxx-xxxx-xxxx-xxxx-xxxxx1 -> Connector is in error state. Service name: audit. Reason for failure: External fpolicy server terminated.)]

 

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.