Skip to main content
NetApp Knowledge Base

404 Not Found Specified Cluster Is Unreachable error when locally adding SVM to OTV

  1. Last updated
  2. Save as PDF
Views:
14
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • ONTAP Tools for VMware vSphere (OTV) 10.x
  • VMware vCenter

Issue

  • When attempting to add an SVM to OTV via the vCenter plugin using local scope, the operation fails with errors such as:

Error occurred while adding storage backend: Unable to onboard storage backend, Error occurred while adding storage backend: Failed to add StorageBackend: https://<otv-service>/api/v1/storage/storage-backends. Error: The specified cluster is unreachable. 404 Not Found NotFound The requested URL was not found on this server.

  • In OTV application buffer.log:

[404 Not Found] during [GET] to [https://<svm-mgmt-LIF>/api/cluster?fields=version&max_records=50000&return_timeout=120] NotFound The requested URL was not found on this server.

  • Browser access to the same SVM REST API endpoint (/api/cluster) returns a 404 Not Found error.
  • All required certificates and SAN entries are correctly configured.
  • Network connectivity to SVM management LIF is confirmed (ping succeeds).

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.