Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • 'HTTP 400: Error getting root assets' when running setup-mnode
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/HTTP_400__Error_getting_root_assets_when_running_setup_mnode
      Applies to Management node (mNode) Element 11.3 and higher Issue When running /sf/packages/mnode/setup-mnode the following error appears: sfprime.MnodeCfgEzroz: Error: HTTP 400: Error adding root asse...Applies to Management node (mNode) Element 11.3 and higher Issue When running /sf/packages/mnode/setup-mnode the following error appears: sfprime.MnodeCfgEzroz: Error: HTTP 400: Error adding root asset. — Asset with name '<mnode_name>' already exists.[25137 ] Failed zo execute script setup mnode
    • Frequent disconnection to FPolicy server due to concurrent access from two different collectors
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Frequent_disconnection_to_FPolicy_server_due_to_concurrent_access_from_two_different_collectors
      Connection to the FPolicy server disconnects frequently [cluster-01: fpolicy: fpolicy.server.disconnect:error]: Connection to the FPolicy server "10.10.10.51" is broken ( reason: "FPolicy server is re...Connection to the FPolicy server disconnects frequently [cluster-01: fpolicy: fpolicy.server.disconnect:error]: Connection to the FPolicy server "10.10.10.51" is broken ( reason: "FPolicy server is removed from external engine." ). AUDIT-MLOG-TXT.GZ under ASUP shows the incoming fpolicy disable/enable ONTAPI request from 2 different servers Running the command vserver fpolicy show back-to-back may show inconsistent results in the status column
    • mNode unable to resolve monitoring.solidfire.com
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/mNode_unable_to_resolve_monitoring.solidfire.com
      Applies to Management node (mNode) Element cluster is not reporting to Active IQ Error in AIQ docker container: ERROR FAILED to fetch ListAPIMethodsToFetch : (6) Could not resolve host: monitoring.sol...Applies to Management node (mNode) Element cluster is not reporting to Active IQ Error in AIQ docker container: ERROR FAILED to fetch ListAPIMethodsToFetch : (6) Could not resolve host: monitoring.solidfire.com ERROR Error parsing result for ListAPIMethodsToFetch : No JSON object could be decoded ERROR FAILED to fetch AddCollectorData : (6) Could not resolve host: monitoring.solidfire.com nc -zvw5 monitoring.solidfire.com 443 from mNode returns failed to connect
    • FSx for NetApp ONTAP data collector for Storage Workload Security remains in error state: "No local IP address found on the connector"
      https://kb.netapp.com/Cloud/BlueXP/DII/FSx_for_NetApp_ONTAP_data_collector_for_Storage_Workload_Security_remains_in_error_state__No_local_IP_address_found_on_the_connector
      Applies to Storage Workload Security (SWS) Data Infrastructure Insights (formerly Cloud Insights) (DII) Amazon Web Services (AWS) File System for NetApp ONTAP (FSxN) Issue Using Storage Workload Secur...Applies to Storage Workload Security (SWS) Data Infrastructure Insights (formerly Cloud Insights) (DII) Amazon Web Services (AWS) File System for NetApp ONTAP (FSxN) Issue Using Storage Workload Security FSx for NetApp ONTAP data collector pointed at an AWS FSxN system, the collector remains in an error state. No local IP address found on the connector