paulkbeyer
Contributor
Contributor

vmkping bust after update to 3.0.2 update 1?

Jump to solution

Upgraded to 3.0.2 update 1 at the weekend, did some reconfiguring of my net adapters this morning and found this when trying to confirm connectivity on my VMotion network after adapter swops..

Any thoughts anyone?

# vmkping 192.168.100.2

syscall version mismatch (compiled: 0x7616c4e3, kernel: 0x50f63116)

Regards

Paul

0 Kudos
1 Solution

Accepted Solutions
Anders
Expert
Expert

Hi.

This is a known issue, U1 is shipping with the 3.0.2 version of vmkping and ramcheck.

You can contact VMware support for the updated rpm or wait for an official fix that will ship shortly.

We expect to roll a new ISO and tar update script.

- Anders

View solution in original post

0 Kudos
2 Replies
RaBalder
Enthusiast
Enthusiast

I experience the same error.

On hosts without update01, vmkping works.

,

0 Kudos
Anders
Expert
Expert

Hi.

This is a known issue, U1 is shipping with the 3.0.2 version of vmkping and ramcheck.

You can contact VMware support for the updated rpm or wait for an official fix that will ship shortly.

We expect to roll a new ISO and tar update script.

- Anders

View solution in original post

0 Kudos