Loading...
Loading...
Node addition failing with " vmnicX on host x cannot communicate with other hosts on VLAN X " Issue may also occur during deployment. Error: "Host XXXXXXX network vsan VLAN validation Network adapters vmnic1 on host xxxxx cannot communicate with other hosts on VLAN x. Host XXXXXXX network vsan VLAN validation Network adapters vmnic0 on host xxxxx cannot communicate with other hosts on VLAN x." dayone.log: 2022-01-12-13:21:40 microservice.nano-service "2022-01-12 13:21:40,952 [INFO] <Dummy-147:140397515082568> vlan_live_validator.py get_device_to_test() (164): test pnics is ['vmnic1', 'vmnic0'] " 2022-01-12-13:21:40 microservice.nano-service "2022-01-12 13:21:40,952 [INFO] <Dummy-147:140397515082568> vlan_live_validator.py validate_vlan_connectivity() (220): testing the nicDevice vmnic1 " 2022-01-12-13:21:40 microservice.nano-service "2022-01-12 13:21:40,952 [INFO] <Dummy-147:140397515082568> vlan_live_validator.py validate_vlan_connectivity() (223): begin to setup Host Test Network for traffic vsan" 2022-01-12-13:23:01 microservice.nano-service "2022-01-12 13:23:01,462 [INFO] <Dummy-147:140397515082568> vlan_live_validator.py setup_host_test_network() (181): created vmknicName is vmk3" 2022-01-12-13:23:01 microservice.nano-service "2022-01-12 13:23:01,462 [INFO] <Dummy-147:140397515082568> do_network_repository.py update_vss_vmk_mtu() (222): update vmk3 mtu to 9000 on VSS." 2022-01-12-13:22:39 microservice.do-network "[2022-01-12 13:22:39,685: INFO/MainProcess] Ping result is:" 2022-01-12-13:22:39 microservice.do-network "(vim.EsxCLI.network.diag.ping.VMKPing) [" 2022-01-12-13:22:39 microservice.do-network " (vim.EsxCLI.network.diag.ping.VMKPing) {" 2022-01-12-13:22:39 microservice.do-network " dynamicType = <unset>," 2022-01-12-13:22:39 microservice.do-network " dynamicProperty = (vmodl.DynamicProperty) []," 2022-01-12-13:22:39 microservice.do-network " Summary = (vim.EsxCLI.network.diag.ping.VMKPingSummary) {" 2022-01-12-13:22:39 microservice.do-network " dynamicType = <unset>," 2022-01-12-13:22:39 microservice.do-network " dynamicProperty = (vmodl.DynamicProperty) []," 2022-01-12-13:22:39 microservice.do-network " Duplicated = 0," 2022-01-12-13:22:39 microservice.do-network " HostAddr = '172.21.xx.xx'," 2022-01-12-13:22:39 microservice.do-network " PacketLost = 100," short.term.log 2022-08-19-17:08:31 microservice.nano-service "2022-08-19 17:08:31,014 [INFO] <Dummy-119:140518802889544> vlan_live_validator.py run_ping_tests() (289): the result of 2 time runPingTests to xxx.xxx is False" 2022-08-19-17:08:31 microservice.nano-service "2022-08-19 17:08:31,014 [ERROR] <Dummy-119:140518802889544> vlan_live_validator.py validate_vlan_connectivity() (249): failed ping test nicDevices: vmnic1, mtu: 9000" Deployment scenario : dayone.log: "2023-03-15 16:40:05,812" microservice.nano-service "2023-03-15T16:40:05.604224542Z stdout F 2023-03-15 16:40:05,604 [INFO] <Dummy-143:140220536689736> vlan_live_validator.py validate() (131): testing the nic Device vmnic3 " "2023-03-15 16:40:05,812" microservice.nano-service "2023-03-15T16:40:05.604336999Z stdout F 2023-03-15 16:40:05,604 [INFO] <Dummy-143:140220536689736> vlan_live_validator.py validate() (134): begin to setup Hosts Test Network ""2023-03-15 16:26:12,812" microservice.nano-service "2023-03-15T16:26:12.598847873Z stdout F 2023-03-15 16:26:12,598 [INFO] <Dummy-143:140220536689736> vlan_live_validator.py setup_hosts_test_network() (283): created vmknic_name is vmk3" "2023-03-15 16:26:12,812" microservice.nano-service "2023-03-15T16:26:12.59889903Z stdout F 2023-03-15 16:26:12,598 [INFO] <Dummy-143:140220536689736> do_network_repository.py update_vss_vmk_mtu() (245): update vmk3 mtu to 9000 on VSS .""2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.56331993Z stderr F [2023-03-15 16:34:58,562: INFO/ForkPoolWorker-582] Ping result is:" "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563335099Z stderr F (vim.EsxCLI.network.diag.ping.VMKPing) [" "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563339053Z stderr F (vim.EsxCLI.network.diag.ping.VMKPing) {" "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563343148Z stderr F dynamicType = <unset>," "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563346709Z stderr F dynamicProperty = (vmodl.DynamicProperty) []," "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563349984Z stderr F Summary = (vim.EsxCLI.network.diag.ping.VMKPingSummary) {" "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563353219Z stderr F dynamicType = <unset>," "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563356171Z stderr F dynamicProperty = (vmodl.DynamicProperty) []," "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563359418Z stderr F Duplicated = 0," "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563362738Z stderr F HostAddr = '10.xx.xx.x'," "2023-03-15 16:34:59,000" microservice.do-network "2023-03-15T16:34:58.563365625Z stderr F PacketLost = 100 ," short.term.log ""Network adapters ['vmnic3'] on host 3 cannot communicate with other hosts on VLAN 16.""}, {'type': 'THOROUGH-VALIDATOR', 'field': 'co nfig.validation.shared.vsan.network.vlan.setup', 'code': 'E3100_VAL_58', Short.term.log may not show any errors related to MTU.
Configured hosts have mismatched MTU values for vSAN or vMotion or Management interface, causing this issue. From VxRail version 7.0.240, test node communications use ping with MTU. The ping MTU is retrieved from the current cluster's port group. For example, one of the host's vSAN interface MTU is 1500, but the others are 9000. In a deployment scenario, the switch VLANs may have mismatched MTU values for vSAN or vMotion or Management interfaces. Test node communications use ping with MTU.
To resolve this issue: Log in to the failing host as root. Change vSAN/vMotion/Management vmk MTU to be the same as its port group MTU value. For deployments: 1. Ensure that nodes vmnics are pointing to the correct switches by logging into the host DCUI and opening shell and running: lldpnetmap 2. Rerunning the validation using 1500 MTU can help verify if the misconfiguration is on the switch as it may pass successfully using 1500 instead of 9000. 3. Verify that the VLAN MTUs are correct/match on the switch compared to the VDS settings page.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.