Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

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

Views:
322
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
hci
Last Updated:

Applies to

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

Issue

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 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.

 

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support