VMware Esxi ScsiScan errors

Hello experts,

Please advice what should I check regarding the following errors from my vmware esxi log:

"2015-05-18T16:06:35.484Z: [netCorrelator] 31911517618024us: [vob.net.pg.uplink.transition.down] Uplink: vusb0 is down. Affected portgroup: IMM_Network0. 0 uplinks up. Failed criteria: 128
2015-05-18T16:06:37.002Z: [netCorrelator] 31911519144277us: [esx.problem.net.connectivity.lost] Lost network connectivity on virtual switch "vSwitchUSB0". Physical NIC vusb0 is down. Affected port groups: "IMM_Network0"
2015-05-18T16:08:36.488Z: [netCorrelator] 31911638622133us: [vob.net.pg.uplink.transition.up] Uplink:vusb0 is up. Affected portgroup: IMM_Network0. 1 uplinks up
2015-05-18T16:08:36.593Z: [netCorrelator] 31911638726214us: [vob.net.vmnic.linkstate.up] vmnic vusb0 linkstate up
2015-05-18T16:08:38.000Z: [netCorrelator] 31911640143214us: [esx.clear.net.connectivity.restored] Network connectivity restored on virtual switch "vSwitchUSB0", portgroups: "IMM_Network0". Physical NIC vusb0 is up

2015-05-18T16:08:36.487Z cpu2:33304)WARNING: LinNet: LinNet_CreateDMAEngine:3807: vusb0, failed to get device properties with error Not supported
2015-05-18T16:08:36.487Z cpu2:33304)WARNING: LinNet: LinNet_ConnectUplink:10927: vusb0: Failed to create DMA engine with error Not supported, it maybe a pseudo device
2015-05-19T15:30:28.419Z cpu2:2006329)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6005076040984ca81a45e8f31d58e90b" state in doubt; requested fast path state update...
2015-05-19T15:30:37.070Z cpu3:32937)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6005076040984ca81a45e8f31d58e90b" state in doubt; requested fast path state update...
2015-05-19T15:30:55.125Z cpu3:33285)WARNING: ScsiScan: 1408: Failed to add path vmhba0:C0:T0:L0 : Not found
2015-05-19T15:30:56.205Z cpu3:33270)WARNING: ScsiScan: 1408: Failed to add path vmhba0:C0:T0:L0 : Not found
2015-05-19T15:30:57.273Z cpu0:33282)WARNING: ScsiScan: 1408: Failed to add path vmhba0:C0:T0:L0 : Not found
2015-05-19T15:30:58.370Z cpu2:33284)WARNING: ScsiScan: 1408: Failed to add path vmhba0:C0:T0:L0 : Not found


2015-05-20T06:24:41.241Z cpu1:34334)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x85 (0x412e80860d40, 34334) to dev "naa.6005076040984ca81a45e8f31d58e90b" on path "vmhba0:C2:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2015-05-20T06:24:41.241Z cpu1:34334)ScsiDeviceIO: 2337: Cmd(0x412e80860d40) 0x85, CmdSN 0x68d6f7b from world 34334 to dev "naa.6005076040984ca81a45e8f31d58e90b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2015-05-20T06:24:41.241Z cpu1:34334)ScsiDeviceIO: 2337: Cmd(0x412e80860d40) 0x4d, CmdSN 0x68d6f7c from world 34334 to dev "naa.6005076040984ca81a45e8f31d58e90b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2015-05-20T06:24:41.241Z cpu1:34334)ScsiDeviceIO: 2337: Cmd(0x412e80860d40) 0x1a, CmdSN 0x68d6f7d from world 34334 to dev "naa.6005076040984ca81a45e8f31d58e90b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2015-05-20T06:54:41.254Z cpu3:2513459)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x85 (0x412e8089de00, 34334) to dev "naa.6005076040984ca81a45e8f31d58e90b" on path "vmhba0:C2:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2015-05-20T06:54:41.254Z cpu3:2513459)ScsiDeviceIO: 2337: Cmd(0x412e8089de00) 0x85, CmdSN 0x68d8c6e from world 34334 to dev "naa.6005076040984ca81a45e8f31d58e90b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2015-05-20T06:54:41.254Z cpu3:2513459)ScsiDeviceIO: 2337: Cmd(0x412e8089de00) 0x4d, CmdSN 0x68d8c6f from world 34334 to dev "naa.6005076040984ca81a45e8f31d58e90b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2015-05-20T06:54:41.254Z cpu3:2513459)ScsiDeviceIO: 2337: Cmd(0x412e8089de00) 0x1a, CmdSN 0x68d8c70 from world 34334 to dev "naa.6005076040984ca81a45e8f31d58e90b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2015-05-20T07:00:16.375Z cpu3:2513457)ata_scsi_media_change_notify not imiplemented
2015-05-20T07:00:26.686Z cpu3:34615)ata_scsi_media_change_notify not imiplemented
2015-05-20T07:00:53.117Z cpu3:2006327)ata_scsi_media_change_notify not imiplemented

2015-05-19T15:30:58.363Z cpu3:33284)ScsiScan: 976: Path 'vmhba0:C0:T0:L0': Vendor: 'IBM     '  Model: 'ServeRAID M5110e'  Rev: '3.24'
2015-05-19T15:30:58.363Z cpu3:33284)ScsiScan: 979: Path 'vmhba0:C0:T0:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
2015-05-19T15:30:58.370Z cpu2:33284)megasas_slave_configure: do not export physical disk devices to upper layer.
2015-05-19T15:30:58.370Z cpu2:33284)WARNING: ScsiScan: 1408: Failed to add path vmhba0:C0:T0:L0 : Not found"

See the attached files.

Thank you.

Kind regards.
Cristian
vmkernel.log
LVL 11
A. Cristian CsikiSenior System AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
any disks, LUNs, datastores missing ?
0
A. Cristian CsikiSenior System AdministratorAuthor Commented:
Everything fine now, but it lost the connectivity 2 days ago. I just need to be sure if is the raid, the mainboard or just a timeout in the pci-bus as noted here:

I have an LSI 9271-8i, when i got it I also got problems with the the drive connected to the controller going off line. After many days of google search I found adding "pcie_aspm=off disable_msi=1" to the kernel options in grub resolved the problem.

I believe the problem is related to the PCI-E bus going into a sleep mode and the LSI card not being able to recover correctly after being woken up.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You need to check, if your hardware is on the HCL, I guess not, is this a Lab machine or Production.

Storage Controllers, and their firmware do have issues with ESXi.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

A. Cristian CsikiSenior System AdministratorAuthor Commented:
It's a production machine unfortunately. I will plan to schedule an maintenance to update the firmwares, however it worked fine the last year, till latest days. Nothing changed in the host or hardware.. I don't think might fix something the firmware updates..

This week I have changed another mainboard on another server, same model, +/- same problem, but this one had Critical PCI-IOH..

Cristian
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Check HCL, Check with vendors if servers is supported.
0
A. Cristian CsikiSenior System AdministratorAuthor Commented:
I have another server that has same issues and this time is a Dell not an IBM. I'm guessing that might be a software related issue.

Anyway I have opened a case with IBM to check what's happening.

Thank you.

Kind regards
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.