Hello. We have a customer which runs vcenter server appliance 6.5 u1, twelve nodes running esxi 6.5 patch 2 build 7388607 and vsan vSAN 6.6.1 Patch 02.
This is stretched cluster configuration all flash with witness appliance in cloud. I have wrote static routes from data nodes of both sites toward the witness and from witness routes exists too. Cluster is functioning normally vsan is OK.BUT.
we have an warnings and errors in vsan health check.
vSAN: Basic (unicast) connectivity check
vSAN: MTU check (ping with large packet size
This errors are from witness to all 12 data hosts. and sometimes these warnings are gone away sometimes they are not 12 but 6 for example, but MTU error persists always. we have restarted vcenter and witness appliance but no result.
the customer have distributed switch configuration with lacp and nexus switches.
I have made lab configuration with witness appliance there are no error.
in vsanmgmt.log file in my lab ping tests are ok. here is my lab witness vsanmgmt log file fragment.
2018-08-29T11:34:20Z VSANMGMTSVC: INFO vsanperfsvc[782ef7de-ab7f-11e8] [VsanHealthPing::Ping] Run ping test for the hosts ['192.168.10.72', '192.168.10.73', '192.168.10.71', '192.168.10.76', '192.168.10.74', '192.168.10.75', '192.168.10.82', '192.168.10.81'] from local 172.17.2.52
2018-08-29T11:34:20Z VSANMGMTSVC: INFO vsanperfsvc[782ef7de-ab7f-11e8] [VsanHealthPing::PingTest] Pinger: all host response come back, ping done Seq:1, size:9000
2018-08-29T11:34:20Z VSANMGMTSVC: INFO vsanperfsvc[782ef7de-ab7f-11e8] [VsanHealthPing::Ping] Run ping test for the hosts ['192.168.10.72', '192.168.10.73', '192.168.10.71', '192.168.10.76', '192.168.10.74', '192.168.10.75', '192.168.10.82', '192.168.10.81'] from local 172.17.2.52
2018-08-29T11:34:20Z VSANMGMTSVC: INFO vsanperfsvc[782ef7de-ab7f-11e8] [VsanHealthPing::PingTest] Pinger: all host response come back, ping done Seq:2, size:9000
But on the customer side we have following warning in vsanmgmt.log file on the witness which is in cloud with complex network environment.
2018-08-29T10:35:21Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Run ping test for the hosts ['172.16.160.94', '172.16.160.191', '172.16.160.96', '172.16.160.193', '172.16.160.91', '172.16.160.196', '172.16.160.95', '172.16.160.192', '172.16.160.194', '172.16.160.195', '172.16.160.92', '172.16.160.93'] from local 172.16.252.100
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::PingTest] Pinger: select time out after waiting for 0.416111
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.191, size:9000, pingSeq:1
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.193, size:9000, pingSeq:1
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.91, size:9000, pingSeq:1
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.196, size:9000, pingSeq:1
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.95, size:9000, pingSeq:1
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.192, size:9000, pingSeq:1
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.194, size:9000, pingSeq:1
and
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Run ping test for the hosts ['172.16.160.94', '172.16.160.191', '172.16.160.96', '172.16.160.193', '172.16.160.91', '172.16.160.196', '172.16.160.95', '172.16.160.192', '172.16.160.194', '172.16.160.195', '172.16.160.92', '172.16.160.93'] from local 172.16.252.100
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::PingTest] Pinger: select time out after waiting for 0.417736
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.191, size:9000, pingSeq:2
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.193, size:9000, pingSeq:2
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.91, size:9000, pingSeq:2
2018-08-29T10:35:22Z VSANMGMTSVC: INFO vsanperfsvc[3aa4dc88-ab77-11e8] [VsanHealthPing::Ping] Pinger: ping timeout: target:172.16.160.196, size:9000, pingSeq:2
So please help to recover this errors and warnings. I ll very appreciate.
Thanks.