"Bad Parameter" error on Fault Tolerance with multiple NIC configuration
searchcancel
"Bad Parameter" error on Fault Tolerance with multiple NIC configuration
book
Article ID: 321316
calendar_today
Updated On: 11-24-2020
Products
VMware vSphere ESXi
Issue/Introduction
An ARP Flux issue may occur when the Fault Tolerance network is configured with multiple NICs in the same vmkernel subnet. As a result, a socket "Bad Parameter" error may occur in the vmkernel, which may break the connection between the Primary VM and Secondary VM, and unnecessary Fault Tolerance failover occurs.
In the /var/log/vmerkernel.log file of the ESXi host, you see entries similar to:
2020-08-28T05:11:52.518Z cpu56:144353014)WARNING: FTCpt: 5230: (25749962114582 pri) Error writing chunk header: Bad parameter 2020-08-28T05:11:52.518Z cpu56:144353014)WARNING: FTCpt: 5300: (25749962114582 pri) Error transmitting pages (15140 bytes, 1 ms elapsed): Bad parameter 2020-08-28T05:11:52.518Z cpu49:144353015)WARNING: FTCpt: 4079: (25749962114582 pri) Error on tx queue 1: Bad parameter 2020-08-28T05:11:52.518Z cpu49:144353015)WARNING: FTCpt: 8505: (25749962114582 pri) Error waiting for sending checkpoint data: Bad parameter 2020-08-28T05:11:52.518Z cpu49:144353015)WARNING: FTCpt: 8506: (25749962114582 pri) Remote not responding
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.