跳转到主内容

OTV10:由于集群间网络配置问题,无法发现阵列

Views:
8
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

适用于

  • ONTAP Tools for VMware (OTV) 10.x
  • NetApp ONTAP 9.14.1P7 及更高版本

问题

  • 尝试在 SRM 中发现存储阵列失败,出现错误:
    • 无法访问存储阵列的地址。
      存储阵列可能已关闭或输入的 IP 地址可能不正确。
      请确保存储阵列已启动且正在运行,并且可以通过命令行界面访问存储阵列的 IP 地址。
  • OTV 日志示例:
    •  getSnapMirrorRelationshipByUUIDFromPeeredSVM: Error while fetching SnapMirror Relationship from peered cluster ONTAP: [409 Conflict] ... Reason: Failed to contact peer cluster 
  • ONTAP EMS 日志示例:
    • [DALNCS400-09:mgwd:cpeer.addr.stable.down:error]: Stable address 10.131.177.146 of cluster PARNTERNCS400, in IPspace Default, cannot be contacted.
      [DALNCS400-09:CSM_BTLS:csm.createSessionFailed:debug]: ClusterSessionManager (CSM) failed to create session ... CSMerror CSM_CONNABORTED, low-level error, socket error 0, and TLS error 0.
  • 集群对等 Ping 输出:
    • TESTNCS400::> cluster peer ping -destination-cluster (ClusterName)
      Node: TESTNCS400-10 Destination Cluster: PARNTERNCS400
      Destination Node    IP Address     Status
      -----------------------------------------------------
      PARNTERNCS400-01      10.131.177.140   unreachable
      PARNTERNCS400-02      10.131.177.141   interface_reachable
      ...

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.