ShocKNetworK Blog

If you’re using autostart for your VMs. You’ll have to be very careful because it will SHUTDOWN your VMs!

The way autostart works in 3.0.x is that your autostart will automatically start the VMs with hostd and shutdown with hostd, so you don’t want to be restarting mgmt-vmware if you’re using autostart for your VMs.

Unexpected return result. Expect 1 sample, receive 2

and

“[NFC ERROR] NfcServerLoop: failed to continue send”

Obviously, these are network problems. First check name resolution – if the 2 ESX hosts can talk to each other by name. Then, you can check throughput. Just a quick scp will tell you the speed it copies the data at. If the speed isn’t good enough, it will timeout.

so in our case, throughput was at like 30Mbps when we need like 10MBps.

We changed the nic that the service console was using and we got:

NfcNewAuthdConnectionEx: Failed to connect to peer. Error: 511 Error connecting to /usr/sbin/vpxa process.

So we just needed to restart the mgmt-vmware – hostd/vpxa.]]>

xxx may be snapshot: disabling access. See resignaturing section in SAN …

We did a bunch of stuff including changing DisallowSnapshotLun to 1 and then rescanning. After that, we go the message:

When running ‘esxcfg-vmhbadevs -m’:

“Error: Invalid vmhba name at position 1″

uhhh … okay …

And when you try logging into VC, vpxa crashes and you get:

Failed to serialize result of method vmodl.query.PropertyCollector.waitForUpdates:

You get “Failed to serialize result” when logging into the host directly via the VIC as well, but it doesn’t crash vmware-hostd.

So now what???

Well, we checked the SAN and it showed that the LUNs were presented properly.

Then, we found that running:

killall -HUP vmkiscsid

and then running:

esxcfg-rescan vmhba40

got us going again.

Of course, we got the snapshot LUN problem again, so we just set the DisallowSnapshotLun to 0 and EnableResignature to 1 and then rescanned and it resignatured and changed the values back immediately after.]]>