VMware Cloud Community
jherrewijnen
Contributor
Contributor
Jump to solution

PSOD PF Exception in world 14 2097292

A customer of ours receive a PSOD on 2 of the 3 new vSphere 6.7 servers.

I cannot really  find the root of the issue, is there somebody who can give me some advice?

Reply
0 Kudos
1 Solution

Accepted Solutions
SupreetK
Commander
Commander
Jump to solution

Looks like the hosts are crashing in the RSS and Load Balancer module. Can you disable RSS and monitor the hosts? You can run the below command for all the uplinks one by one and disable RSS -

esxcli network nic queue loadbalancer set --rsslb=false -n vmnicX

Cheers,

Supreet

View solution in original post

Reply
0 Kudos
8 Replies
SupreetK
Commander
Commander
Jump to solution

Can you share the complete screenshot of the PSOD screen?

Cheers,

Supreet

Reply
0 Kudos
jherrewijnen
Contributor
Contributor
Jump to solution

PSOD.png

This is the message we get.

Tried to access the log files within /var/core/ but this folder is empty!

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

Looks like the hosts are crashing in the RSS and Load Balancer module. Can you disable RSS and monitor the hosts? You can run the below command for all the uplinks one by one and disable RSS -

esxcli network nic queue loadbalancer set --rsslb=false -n vmnicX

Cheers,

Supreet

Reply
0 Kudos
jherrewijnen
Contributor
Contributor
Jump to solution

I applied the change and we will monitor it.

Thanks for the advice!

Reply
0 Kudos
j_townsend
Contributor
Contributor
Jump to solution

I looked through our KB and PR data to see if I could find anything close to what you are hitting but nothing was found for 6.7. If it happens again it would be a good idea to collect a log bundle and open up a support request to have the issue investigated further. Just make sure your core dump partition/dump collector is setup before hand. VMware Knowledge Base 

Reply
0 Kudos
jimtheitguyAPH
Contributor
Contributor
Jump to solution

Did you get any resolution on this, just had a host do the same thing with an identical error

Reply
0 Kudos
jherrewijnen
Contributor
Contributor
Jump to solution

For now we have applied the solution suggested and the error did not recur.

So this was the correct solution for us:

esxcli network nic queue loadbalancer set --rsslb=false -in vnic

Reply
0 Kudos
jimtheitguyAPH
Contributor
Contributor
Jump to solution

Seems its an undocument bug, yay another one, can i ask what model hardware/nics you are running?

Reply
0 Kudos