Skip to main content
NetApp Knowledge Base

BlueXP on-premises connectors reported inactive on both SaaS and local UI

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

Applies to

  • BlueXP
  • Proxy credentials
  • Active Directory

Issue

  • All the on-premises BlueXP connectors associated with a BlueXP account are  reported inactive on SaaS UI
  • When switching to the connector Local UI, this shows the connector inactive as well
  • Manual curl commands to test BlueXP endpoints returns HTTP 407 error
  • podman ps / docker ps command run from connector CLI shows 0 containers running

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.