Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2015-11-06 02:27:32 →
Size: 1204
Editor: localhost
Comment:
← Revision 3 as of 2015-11-17 15:18:22 → ⇥
Size: 1491
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
}}}

== MTU setting ==

Dell switches a MTU 9000 is actually (9 * 1024) = 9216. Ugh, so now I have set

 * 9000 MTU on the VSAN VMkernel on the vSphere host.
 * 9000 MTU on the VSAN VLAN on the Dell PowerConnect
 * 9216 MTU on the VSAN Physical Interface the Dell PowerConnect

故障域构造

您必须至少定义三个故障域，每个故障域可能包含一个或多个主机。故障域定义必须确认可能代表潜在故障域的物理硬件构造，如单个计算机柜。

如果可能，请使用至少四个故障域。使用三个故障域时，不允许使用特定撤出模式，Virtual SAN 也无法在故障发生后重新保护数据。在这种情况下，您需要一个使用三域配置时无法提供的备用容量故障域用于重新构建。

如果启用故障域，Virtual SAN 将根据故障域而不是单个主机应用活动虚拟机存储策略。

根据计划分配给虚拟机的存储策略中规定的“允许的故障数”属性，计算群集中的故障域数目。

number of fault domains = 2 * number of failures to tolerate + 1

如果主机不是故障域成员，Virtual SAN 会将其解析为单独的域。

删除磁盘原有分区

使用partedUtil工具 首先确认哪些磁盘被确认出来。 

esxcli storage core device list
# 获取 ID
partedUtil get /vmfs/xxx/xxx
1 2048 3xxx 0 0

# 删除分区
partedUtil delete /vmfs/xxx/xxx 1

MTU setting

Dell switches a MTU 9000 is actually (9 * 1024) = 9216. Ugh, so now I have set

  • 9000 MTU on the VSAN VMkernel on the vSphere host.

  • 9000 MTU on the VSAN VLAN on the Dell PowerConnect

  • 9216 MTU on the VSAN Physical Interface the Dell PowerConnect

désert/VMware/VSAN (last edited 2023-08-18 01:44:06 by merlyn)