Hello,
I am encountering network issue with ESXi 6 since last week (17th Oct). Because of some unknown reason, the network connection to the host breaks.
The warning messages in the vmkwarning.log are-
2016-10-22T12:50:46.470Z cpu1:33093)WARNING: LinuxSignal: 541: ignored unexpected signal flags 0x2 (sig 17)
2016-10-22T12:50:47.112Z cpu0:33126)WARNING: VMK_PCI: 715: device 0000:00:14.0 failed to allocate 5 MSIX interrupts
2016-10-22T12:50:47.112Z cpu0:33126)WARNING: LinPCI: LinuxPCI_EnableMSIX:862: 0000:00:14.0: Interrupt allocation failed with Not supported
2016-10-22T12:50:48.039Z cpu1:33122)WARNING: LinScsiLLD: scsi_add_host:573: vmkAdapter (usb-storage) sgMaxEntries rounded to 255. Reported size was 65535
2016-10-22T12:50:48.700Z cpu0:33122)WARNING: LinNet: LinNet_CreateDMAEngine:4009: vusb0, failed to get device properties with error Not supported
2016-10-22T12:50:48.700Z cpu0:33122)WARNING: LinNet: LinNet_ConnectUplink:11918: vusb0: Failed to create DMA engine with error Not supported, it maybe a pseudo device
2016-10-22T12:50:49.579Z cpu2:33122)WARNING: LinNet: LinNet_CreateDMAEngine:4009: vusb0, failed to get device properties with error Not supported
2016-10-22T12:50:49.579Z cpu2:33122)WARNING: LinNet: LinNet_ConnectUplink:11918: vusb0: Failed to create DMA engine with error Not supported, it maybe a pseudo device
2016-10-22T12:50:51.368Z cpu0:33046)WARNING: NetDVS: 658: portAlias is NULL
2016-10-22T12:51:00.163Z cpu0:33355)WARNING: Supported VMs 30, Max VSAN VMs 400, SystemMemoryInGB 8
2016-10-22T12:51:00.163Z cpu0:33355)WARNING: MaxFileHandles: 900, Prealloc 1, Prealloc limit: 32 GB, Host scaling factor: 4
2016-10-22T12:51:00.163Z cpu0:33355)WARNING: DOM memory will be preallocated.
2016-10-22T12:51:01.460Z cpu0:33410)WARNING: FTCpt: 476: Using IPv6 address to start server listener
Also, I have a doubt regarding vusb0. I have only two network adapters which are working fine, then why is this adapter being referred to as Physical NIC?
I would really appreciate inputs on how to resolve this problem.
Thanks
Are these by any chance IBM servers? There's a known bug/quirk with IBMs and the vUSB NIC showing up and randomly dropping off. The fix is to disable a certain feature in the IBM AMM. I forget the specifics but a quick google search will tell you. If its not IBM hardware disregard everything I just said
Even though for another issue but it describes on how to deactivate the feature if it is an IBM server.
Thank you for your suggestion. I disabled the feature but still I am encountering the same error.