Skip to main content
NetApp Knowledge Base

NetApp Console shows inactive as agent IP range in 172.x.x.x conflict with docker network

  1. Last updated
  2. Save as PDF
Views:
2,272
Visibility:
Public
Votes:
2
Category:
cloud-manager
Specialty:
netapp_console
Last Updated:

Applies to

  • NetApp Console
  • Cloud Volumes ONTAP (CVO)

Issue

  • Agent deployment from Console to add on-prem network in Console is failing.
  • Possible conflict with the agent on the 172.17.0.0 and 172.18.0.0 subnets.
  • Deploying NetApp AWS Cloud Manager connector to add on prem NetApp to Cloud manager but connector status is in pending status.
  • EC2 is deployed but not showing as online in NetApp Console.
  • When setting configuration backup target from Console, the target on the cluster is changed to unreachable target URL.

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.