Please provide your feedback in this short Flings' survey.

Comment thread started by deccie on HCIBench

Jun 29, 2021

I have used HCIbench successfully in the past, but am having a problem this time. Our network is restricted to only IPV4 but my HCIbench deployment fails. In the logs I see this:

Not able to ping VMs ["hci-vdb-datastore-92-0-1"], try another time...
PING fe80::250:56ff:feb1:6c34(fe80::250:56ff:feb1:6c34) 56 data bytes
From fe80::250:56ff:feb1:caa4%eth0: icmp_seq=1 Destination unreachable: Address unreachable
From fe80::250:56ff:feb1:caa4%eth0: icmp_seq=2 Destination unreachable: Address unreachable
From fe80::250:56ff:feb1:caa4%eth0: icmp_seq=3 Destination unreachable: Address unreachable
From fe80::250:56ff:feb1:caa4%eth0: icmp_seq=4 Destination unreachable: Address unreachable
From fe80::250:56ff:feb1:caa4%eth0: icmp_seq=5 Destination unreachable: Address unreachable

--- fe80::250:56ff:feb1:6c34 ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 48ms
pipe 4
Not able to ping VMs ["hci-vdb-datastore-92-0-1"], try another time...
Can't Ping VMs ["hci-vdb-datastore-92-0-1"] by their IPs ["fe80::250:56ff:feb1:6c34"]

I don't see any choice in HCIbench setup to choose IPV4 or IPV6, but it seems it now is expecting IPV6 to properly switch in our network. How do I configure HCIbench to only use IPV4?

Thank you,

Tim

Jul 02, 2021

this seems like link-local ipv6, meaning your vms did not get ipv4 addr. check your dhcp server.