Skip to main content
NetApp Knowledge Base

Object store profiler fails with error wrong port or server is not reachable

  1. Last updated
  2. Save as PDF
Views:
202
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • FabricPool

Issue

  • Overall latency is observed within the cloud tier of a FabricPool aggregate. 
  • ONTAP reports below messaes in EMS.

[xybcs-202:Pool: wafl.ca.latency.threshold:notice]: Measured latency from cloud (17341 msec) more than threshold (5000 msec) (aggregate:"aggr",aggregate uuid: "bec-9f1a-463-b346-d223c49b71", object store: "object_name")


cluster1::>object-store profiler show
Error: command failed: Initializing the object store profiler on node "Node-01" for object store "object_store
failed. Reason: Wrong port or server is not reachable. Wait a few minutes and try the command 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.