OPERATIONAL DEFECT DATABASE
...
...
Node adding validation procedure failed with the error message similar to the following: "Network adapters vmnicX on host <ServiceTag> cannot communicate with other hosts on VLAN NNN and MTU NNNN. Please check network connectivity." short.term.log: # cat <path to short.term.log> |grep "microservice.nano-service" | grep "THOROUGH-VALIDATOR" "2023-05-02 20:30:59,554" microservice.nano-service "2023-05-02T20:30:58.738197513Z stdout F 2023-05-02 20:30:58,738 [ERROR] <Dummy-121:140325293870152> validator.py execute() (89): Validation errors: errors=[{'type': 'THOROUGH-VALIDATOR', 'field': 'hosts.<ServiceTag>.vsan.vmnicY.vlan.validation', 'code': 'E3100_VAL_73', 'placeholders': ('vmnicY', '<ServiceTag>', 200, 1500), 'message': 'Network adapters vmnicY on host <ServiceTag> cannot communicate with other hosts on VLAN 200 and MTU 1500. Please check network connectivity.'}]" "2023-05-02 20:32:41,546" microservice.nano-service "2023-05-02T20:32:41.249180429Z stdout F 2023-05-02 20:32:41,249 [ERROR] <Dummy-122:140325293870152> validator.py execute() (89): Validation errors: errors=[{'type': 'THOROUGH-VALIDATOR', 'field': 'hosts.<ServiceTag>.vmotion.vmnicX.vlan.validation', 'code': 'E3100_VAL_73', 'placeholders': ('vmnicX', '<ServiceTag>', 100, 1500), 'message': 'Network adapters vmnicX on host <ServiceTag> cannot communicate with other hosts on VLAN 100 and MTU 1500. Please check network connectivity.'}]" "2023-05-02 21:52:04,546" microservice.nano-service "2023-05-02T21:52:03.974415552Z stdout F 2023-05-02 21:52:03,974 [ERROR] <Dummy-153:140325293870152> validator.py execute() (89): Validation errors: errors=[{'type': 'THOROUGH-VALIDATOR', 'field': 'hosts.<ServiceTag>.vsan.vmnicY.vlan.validation', 'code': 'E3100_VAL_73', 'placeholders': ('vmnicY', '<ServiceTag>', 200, 1500), 'message': 'Network adapters vmnicY on host <ServiceTag> cannot communicate with other hosts on VLAN 200 and MTU 1500. Please check network connectivity.'}]" "2023-05-02 21:53:47,563" microservice.nano-service "2023-05-02T21:53:47.173597072Z stdout F 2023-05-02 21:53:47,173 [ERROR] <Dummy-154:140325293870152> validator.py execute() (89): Validation errors: errors=[{'type': 'THOROUGH-VALIDATOR', 'field': 'hosts.<ServiceTag>.vmotion.vmnicX.vlan.validation', 'code': 'E3100_VAL_73', 'placeholders': ('vmnicX', '<ServiceTag>', 100, 1500), 'message': 'Network adapters vmnicX on host <ServiceTag> cannot communicate with other hosts on VLAN 100 and MTU 1500. Please check network connectivity.'}]"
Network misconfiguration in customer's network.
Based on the information in the shortterm.log, the two vmnics experience issues with connectivity. VmnicX experiences issue only with vLAN 100. No other vmnic experiences an issue with that vLAN. VmnicY experiences issue only with vLAN 200. No other vmnic experiences an issue with that vLAN. The add node configuration has both vmnics (vmnicX and vmnicY) configured as standby uplinks for the mentioned vLANs. VmnicX is the standby for vLAN 100, and VmnicY is the standby for vLAN 200. This behavior points a network configuration issue on the customer's network. There is no routing for the traffic between TOR switches which is tagged vLAN 100 and 200. To confirm which hosts pings during the validation and how the pings pass, use following command: # cat <path to short.term.log> | grep -e "host_interface_network_update for device" -e "Ping result is:" -A 23 | grep -e "host_interface_network_update for device" -e "ipAddress" -e "HostAddr" -e "PacketLost" -e "Ping result is" -e "portgroup" -e "mtu"
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
