跳转到主内容

ONTAP仲裁丢失对SAN服务有何影响?

Views:
3
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

适用场景

ONTAP 9

问题解答

  • 有关仲裁和ep西 普龙在ONTAP中的工作原理的说明,请参见 关于仲裁和ep西 普龙
  • 如果没有集群仲裁、则无法进行集群管理、聚合和卷将报告未知状态。
    • 这包括无法管理LUN映射/取消映射、创建 或 修改 igroub以及其他此类管理任务。
  • 但是、只要scs刀片 未脱离仲裁、并且在接管中至少有一个节点在HA对中继续存在、SAN数据就会继续提供、即使集群本身已丢失仲裁且集群应用程序处于脱机状态也是如此。
  • 启动程序登录(包括现有的和新的)将有效、只要它们属于现有igro组 即可。
  • 如果scs刀片 确实超出仲裁范围(导致SAN中断)、则会在EMS中报告此问题:
[cluster-01: ThreadHandlerun: scsiblade.out.of.quorum:EMERGENCY]: This node is no longer in SAN quorum and will not provide any SAN service until cluster communications are restored.
  • 丢失 scsibblade仲裁还会触发AutoSupport、请参见SCSIBLade服务不可用
  • 在启动时、Scs刀片 恢复scs刀片 服务的仲裁/初始化状态时、将 在EMS中报告以下信息:
[cluster-01: BcomkaThr_02: scsiblade.online:notice]: This node has completed initialization of the SAN configuration cache. FCP and iSCSI traffic are enabled on this node.

追加信息

其他信息文本
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.