Skip to main content
NetApp Knowledge Base

Element mNode's Docker swarm network deploys on the same subnet as the underlying management / infrastructure network

Last Updated:

Applies to

  • Element Management Node (mNode)
  • Hybrid Cloud Control (HCC)
  • Management Services 2.3 and above


When deploying or configuring Element mNode, one or more mNode or HCC functions experiences failures--often including connectivity-related errors--even after the underlying management network has been validated

For instance:

  • Name resolution fails for the mNode and/or containers
  • mNode collector fails to report cluster data to ActiveIQ  (AIQ)
    • AIQ container appears to fail to resolve hostnames
  • Compute and/or storage nodes aren't displayed in HCC
    • compute or storage nodes may have IP's that the mNode containers are also using
  • 'This site can't be reached' errors in HCC or Swagger
  • Initial mNode setup (/sf/packages/mnode/setup-mnode script) fails with 'could not reach API' error:

[config_util:1404] ERROR:Could not reach mNode API. Debug the issue or clean up the docker environment and try again.



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.