虚拟系统ESXi 群晖DSM组建 HA high availability集群
本帖最后由 zulinfi 于 2021-1-19 14:44 编辑在试过jun's loader 1.03b实体机创建3617xs,群晖HA能够成功. 双机为兼容x86组装机,intel82575双口千兆网卡,双核intel cpu,4g内存, u盘启动并隐藏引导盘，双机直连网口用的交叉千兆网线。因此对组建ha具备的条件，大致上是清楚的.有了实体机成功的经验，打算复制到虚拟平台上，于是选用尝试在ESXi7.0b虚拟环境下建立的两台虚拟机dsm并组建HA系统.先用映像转换格式,添加两虚拟sata硬盘01,虚拟网络直通pci网卡,并添加串口,两台赋予机子不同SN,vid/pid,mac地址,传统bios模式启动,隐藏引导盘并安装好相关的套件,根据实体机成功的经验来布置,两部虚拟dsm使用正常。在创建HA，最后一步 显示心跳网络连接不稳定,始终不能成功！查看var/log/ha.log,日志文件显示,所有检测都通过, ping 副机IP地址也能成功,均为最后一步提示心跳网络不稳定,百思不得姐，是否HA有关键的要求？
2021-01-17T05:49:05+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:207: Start polling on remote verification
2021-01-17T05:49:05+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:95: start do local checker
2021-01-17T05:49:05+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:105: start do remote checker
2021-01-17T05:49:05+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:115: start do cluster checker
2021-01-17T05:49:07+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:95: start do local checker
2021-01-17T05:49:09+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:105: start do remote checker
2021-01-17T05:49:09+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:115: start do cluster checker
2021-01-17T05:49:10+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:95: start do local checker
2021-01-17T05:49:10+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:105: start do remote checker
2021-01-17T05:49:10+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:115: start do cluster checker
2021-01-17T05:49:10+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:95: start do local checker
2021-01-17T05:49:13+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:105: start do remote checker
2021-01-17T05:49:14+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:115: start do cluster checker
2021-01-17T05:49:21+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:349: consistentRemoteVlan
2021-01-17T05:49:21+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:356: Check local interface(eth0) vlan
2021-01-17T05:49:21+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:356: Check local interface(eth1) vlan
2021-01-17T05:49:22+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:417: consistentRemoteMTU
2021-01-17T05:49:22+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:424: Check local interface(eth0) mtu
2021-01-17T05:49:22+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:402: Set remote interface(eth0) mtu
2021-01-17T05:49:23+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:424: Check local interface(eth1) mtu
2021-01-17T05:49:23+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:402: Set remote interface(eth1) mtu
2021-01-17T05:49:24+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:387: consistentGateway
2021-01-17T05:49:24+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:796: chkDefaultGatewayIF
2021-01-17T05:49:24+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:843: consistentDefaultGateway
2021-01-17T05:49:25+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: util/network.cpp:766: chkAllHAIFSettings
2021-01-17T05:49:27+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:95: start do local checker
2021-01-17T05:49:29+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:105: start do remote checker
2021-01-17T05:49:30+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:115: start do cluster checker
2021-01-17T05:49:40+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: ha_heartbeat.cc:828: Ask remote to prepare heartbeat with param: {"drbd_ip":"169.254.1.2","drbd_mtu":2000,"drbd_netmask":"255.255.255.252","interface":"eth1"}
2021-01-17T05:49:45+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: ha_heartbeat.cc:287: Save original MTU 2000
2021-01-17T05:49:51+08:00 mi-DSM3617xs /var/packages/HighAvailability/target/etc/UtilHeartbeatCheck.sh: /bin/ping 169.254.1.2 -s 2000 -I eth1 -c 5 -W 1
2021-01-17T05:49:51+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: ha_heartbeat.cc:868: Check script execute return: "5
"
2021-01-17T05:49:55+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: ha_heartbeat.cc:403: Restore MTU of eth1
2021-01-17T05:49:55+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: ha_heartbeat.cc:421: Original MTU is 2000
2021-01-17T05:49:56+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: net_set_mtu_eth.c:53 we temporarily do the eth up/down in sdk when setting MTU
2021-01-17T05:49:57+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: env_checker.cpp:2092: Found HeartbeatCheck error: check_network_unstable
2021-01-17T05:49:57+08:00 mi-DSM3617xs synoscgi_SYNO.SHA.Setup.Wizard_1_wizard_finally_total_check: webapi-SHA.cpp:117: Checker has been stopped on cluster checker:(not_supported_heartbeat_info)
时钟同步没有？ 时间没有问题，虚拟机上的时间本身不存在差异 说下具体原因：因为轻工作状态，家用，所以一般情况下只开一台实体主机，ESXi主机上有虚拟dsm及一些win平台虚拟主机于正常工作状态。只需在固定周期要同步资料时，才打开第二台dsm来同步，这样只大限度的保护了硬盘与机器 的寿命，既即保证了资料的安全，比raid1来，既节约了资源，又防止了硬盘寿命同时终寝的问题。还有一个原因是如果实体主机出现问题，可以平滑的迁移到另一个硬件平台上。
目前第一步是实验双实体机群晖组ha, 第二步,是ESXI平台的群晖HA,第三步是虚拟esxi平台的群晖与实体主机群晖组ha.
优点大家可以仔细斟酌一下。
页:
[1]