Jumpstart dependency error on esxi screen

[FreddyFredFred]

Anyone ever see a jumpstart dependency error on the esxi screen after it finishes loading? The text is in red and only appears for a split second but if I press alt+F11 i can see the error (and it's in the vmkernel.log as well)

The full error is:

Jumpstart dependency error: Initialization barrier "vmkeventd" is not provided by any plugin but the following plugins require it: "psp-eql"

The psp-eql is a Dell EqualLogic thing (installed as part of MEM, I'm using the newest version 1.3 for ESXi 6). Dell can't reproduce the problem despite me getting this error on a clean install of ESXi with nothing else configured.

Does anyone know if this error is something I should be worried about or is it harmless?

Thanks

[fryc]

Hi,

We have the same issue.

In connection with this message are you having any issues? Like disconnecting host from cluster, or others?

In our environment host is disconnecting from cluster and we can't connect to host by vSphere Client.

[FreddyFredFred]

THis is a test host for me and is basically sitting idle at the moment with just a vcenter and psc on it (preparing for a migration). I didn't notice any disconnects but I haven't really pushed the host at all. I'll check when I'm in the office but I don't think I'll see much.

CAn can you give me a few details on your hardware, like model of your host and model of network cards and if this was a fresh install or upgrade and what version of MEM (did you install the 5.5 v1.3 one then upgrade to 6 or dresh install on 6 with 6v1.3?

just trying to find some common ground so I can try and see why Dell can't reproduce.

thanks

[fryc]

Our hardware:

- Serwer: Dell M610

- Network 1: Broadcom NetXtreme II BCM5709S 1000 Base-SX

- Network 2: Broadcom NetXtreme II BCM57711 10GB

- We performed an update do ESX 6 and

- Upgrade Mem from: 1.2 to 1.3

[LR_Brian]

I am also having this issue on all 3 of the hosts I upgraded.

I am running vSphere Enterprise and just upgraded from 5.5 to 6.0.  I am not seeing any connection issues with my hosts.

For hardware, I have:

3x Dell R620 hosts (each host has 1 Broadcom NetXtreme BCM5720 and 1 Broadcom NetXtreme BCM5719).

1x Dell PS6100X SAN

[FreddyFredFred]

Dell says they are able to reproduce the error. No idea if or when it will be fixed but Dell claims the error should not cause a problem.

Fryc, I checked my logs and didn't see any disconnects (although I suspect I would need much higher load to experience that kind of problem) so maybe something else is going on in your environment

[DanielOprea]

Hi,

Please, upload the FULL log for the esxi and we review.

Regards

Daniel

[unsichtbare]

We saw this on our HP BL460 G8's and it turned out that the message appeared after we set a static IPv4 address, but did not set an IPv6 address.

Once we disabled IPv6 and rebooted, no more jumpstart dependency error.

[FreddyFredFred]

Apparently this is a known issue and is actually documented in the release notes for MEM 1.3 (I guess we all missed it). So according to the release notes, the message can be safely ignored.