VMware 6.5: USB devices

Hi,

I am running a number of VMware servers with Windows VMs inside, which require a certain USB dongle.  This dongle device is by the manufacturer Kobil and it holds a SIM-card-type ID token that is required by the VM.
Never before have I run into trouble with this.

Now, on my first VMware 6.5 Essentials host, I am able to connect various USB-devices which I tried to test.  Flash-Sticks, Tape drives and other devices connect without trouble.  
When I try to connect his Kobil dongle, I get:

'path:0/3/0/2/1 version:2' kann nicht mit dieser virtuellen Maschine verbunden werden. Das Gerät wurde nicht gefunden.
which is German and translates to:
'path:0/3/0/2/1 version:2' cannot be connected to this virtual machine. The device was not found.

Does anyone know a work-around other than LAN USB-Server?

Thanks,
Ralph
LVL 2
Ralph ScharpingDigital TherapistAsked:
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.

Alex Green3rd Line Server SupportCommented:
Morning

apparently this happens when the USB Arbitrator doesn't start up correctly, you can restart this by doing restarting the hostd process by using services.sh in the SSH session of the host

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1039359

Yes, that's for 4.1 but should be valid for this issue.
0
Ralph ScharpingDigital TherapistAuthor Commented:
Hi Alex, other devices connect.  Do you still think this is the issue?
0
Alex Green3rd Line Server SupportCommented:
No in that case.....

Is it an encrypted key or does it require a password to access? If it's a licience dongle likelihood is it can't pass the authentication request to the VM....
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Ralph ScharpingDigital TherapistAuthor Commented:
This type of key connects fine in dozens of other installations under VMware 4.1 through 6.0.
Is there anything new in 6.5 in this regard?
0
Alex Green3rd Line Server SupportCommented:
OK in which case

https://communities.vmware.com/thread/429305?start=0&tstart=0

-----------------------------
The solution is, that the device is pluged in before you start
and to add "USB-device" after "USB-controller" is added!
 
 
1.     Plug USB-Device in VMware Server
     (The Datev USB-SimCard-Reader is a "Kobile-Type, SCM SCR 335 ")
 
2.     Add "USB-Controller" in VM
     ->Guest-OS is detecting USB-Controller but no device
 
3.     Add "USB-device" in VM
     ->Guest-OS is detecting "SCR 335", after some seconds
 
4.     Manual installation of the "mIdentity"  Datev-driver
     ->http://www.datev.de/portal/ShowPage.do?pid=dpi&nid=100610
     chose the correct one, installation is finished in 10 seconds!
 ------------------------------

This is also for a licence dongle which may be closer to a resolution
0
Ralph ScharpingDigital TherapistAuthor Commented:
This is the exact stick that I am trying to connect.
But I fail way before all of this.  The VM has a USB-controller.  It connects fine to any other USB device that I tried.
the Kobil stick is found by VMware, shown as available and can be added to the VM.  As you press "OK" to save, you get the above error message:  VMware refuses to add the device to the VM.  I have tried with more than one VM.
0
Alex Green3rd Line Server SupportCommented:
And you have the device already plugged in when you start the proceedure?

If so, I'm out of ideas, have you tried it on another host?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is your USB device on this LIST:-

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021345

if it's not in this Hardware Compatibility list IT'S NOT SUPPORTED

PLEASE NOTE JUST BECAUSE YOUR SERVER HAS A USB PORT

AND ESXi SUPPORTS USB PASSTHROUGH

DOES NOT MEAN THAT ANY USB DEVICE YOU CONNECT TO YOUR SERVER WILL WORK!


only devices on the supported list are guaranteed to work, not on the list good luck!

You may want to look at work arounds....

e.g. PCI Passthrough and add the USB controller to the VM, Use Fabultech USB over IP Software, or use USB Anywhere (hardware device) by Digi (this is what we use!).

USB passthrough is PANTS, and I wish VMware had never introduced it. It;'s rubbish!

Please read my EE Article, and ALL the comments

HOW TO: Add and Connect a USB Device to a Virtual Machine, hosted on VMware vSphere Hypervisor ESX 4.1 ESXi 4.1, ESXi 5.0

edit: I don't see your device in the list!
0
Ralph ScharpingDigital TherapistAuthor Commented:
Acknowledged.

What I was asking is:  Is there a fundamental difference between VMware 6.0 (where this works in dozens of installations) and VMware 6.5 (where this first server does not seem to like my device)?
Does the error message hint towards any thing in general that I could change to maybe make this work EVEN THOUGH it is not GUARANTEED to work?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's luck!

what does the usb.log or vmkernel.log state when you insert the USB device....

does it state anything like the following;-

2015-08-03T13:43:22.623Z cpu3:33553)<6>usb 1-1.2: device is not available for passthrough
2015-08-03T14:01:26.111Z cpu19:33553)<6>usb 2-1.2: device is not available for passthrough
2015-08-04T09:42:54.596Z cpu12:33553)<6>usb 1-1.2: device is not available for passthrough
2015-08-04T09:42:54.600Z cpu12:33553)<6>usb 1-1.2: device is not available for passthrough
2015-08-04T09:58:53.656Z cpu14:33553)<6>usb 2-1.2: device is not available for passthrough
2015-08-04T10:04:13.908Z cpu15:33553)<6>usb 1-1.5: device is not available for passthrough
2015-08-04T10:17:15.161Z cpu4:33553)<6>usb 1-1.5: device is not available for passthrough


I believe that VMware has some strange code, which prevents some USB devices from working....

It would be recommended to use a workaround as the solution.
0
Ralph ScharpingDigital TherapistAuthor Commented:
I don't recall the exact moment when I plugged it in, but it has to be in here somewhere:

2017-02-10T06:16:28.275Z cpu21:65598)ScsiDeviceIO: 2948: Cmd(0x439d008dc4c0) 0x1a, CmdSN 0x28a79 from world 0 to dev "mpx.vmhba1:C0:T4:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T06:19:52.291Z cpu14:66349)ScsiDeviceIO: 2948: Cmd(0x439d050d8780) 0x1a, CmdSN 0xa02 from world 67780 to dev "naa.60030057022f8400202252860bf410ea" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-02-10T06:19:52.343Z cpu13:65590)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d050d8780, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T06:19:52.343Z cpu13:65590)ScsiDeviceIO: 2962: Cmd(0x439d050d8780) 0x85, CmdSN 0xa04 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T06:49:52.413Z cpu22:65599)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d009c49c0, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T06:49:52.413Z cpu22:65599)ScsiDeviceIO: 2962: Cmd(0x439d009c49c0) 0x85, CmdSN 0xa0d from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T07:19:52.427Z cpu17:66349)ScsiDeviceIO: 2948: Cmd(0x439d05059d00) 0x4d, CmdSN 0xa0f from world 67780 to dev "naa.60030057022f8400202252650a05e876" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T07:19:52.480Z cpu14:65591)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d05059d00, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T07:19:52.480Z cpu14:65591)ScsiDeviceIO: 2962: Cmd(0x439d05059d00) 0x85, CmdSN 0xa16 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T07:49:52.495Z cpu20:66349)ScsiDeviceIO: 2948: Cmd(0x439d00927c40) 0x85, CmdSN 0xa1e from world 67780 to dev "naa.60030057022f8400202252860bf410ea" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T07:49:52.547Z cpu14:65591)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d00927c40, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T07:49:52.547Z cpu14:65591)ScsiDeviceIO: 2962: Cmd(0x439d00927c40) 0x85, CmdSN 0xa1f from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T07:56:28.274Z cpu22:65599)ScsiDeviceIO: 2948: Cmd(0x439d008210c0) 0x1a, CmdSN 0x291b7 from world 0 to dev "mpx.vmhba1:C0:T4:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T08:19:52.619Z cpu22:65599)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d009addc0, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T08:19:52.619Z cpu22:65599)ScsiDeviceIO: 2962: Cmd(0x439d009addc0) 0x85, CmdSN 0xa28 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T08:49:52.631Z cpu15:66349)ScsiDeviceIO: 2948: Cmd(0x439d05090f00) 0x1a, CmdSN 0x2956d from world 0 to dev "naa.60030057022f8400202252650a05e876" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-02-10T08:49:52.685Z cpu13:65590)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d05090f00, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T08:49:52.685Z cpu13:65590)ScsiDeviceIO: 2962: Cmd(0x439d05090f00) 0x85, CmdSN 0xa31 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T09:19:52.759Z cpu22:65599)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d0086e440, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T09:19:52.759Z cpu22:65599)ScsiDeviceIO: 2962: Cmd(0x439d0086e440) 0x85, CmdSN 0xa3a from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T09:36:28.273Z cpu12:65589)ScsiDeviceIO: 2948: Cmd(0x439d00934ac0) 0x1a, CmdSN 0x298ee from world 0 to dev "mpx.vmhba1:C0:T4:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T09:49:52.770Z cpu22:66349)ScsiDeviceIO: 2948: Cmd(0x439d05136c00) 0x85, CmdSN 0xa3f from world 67780 to dev "naa.60030057022f8400202252860bf410ea" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T09:49:52.820Z cpu21:65598)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d05136c00, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T09:49:52.820Z cpu21:65598)ScsiDeviceIO: 2962: Cmd(0x439d05136c00) 0x85, CmdSN 0xa43 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T10:19:52.892Z cpu21:65598)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d0093a5c0, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T10:19:52.892Z cpu21:65598)ScsiDeviceIO: 2962: Cmd(0x439d0093a5c0) 0x85, CmdSN 0xa4c from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T10:49:52.905Z cpu12:66349)ScsiDeviceIO: 2948: Cmd(0x439d00880dc0) 0x1a, CmdSN 0x29e1c from world 0 to dev "naa.60030057022f8400202252650a05e876" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-02-10T10:49:52.958Z cpu17:65594)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d00880dc0, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T10:49:52.958Z cpu17:65594)ScsiDeviceIO: 2962: Cmd(0x439d00880dc0) 0x85, CmdSN 0xa55 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T11:16:28.273Z cpu22:65599)ScsiDeviceIO: 2948: Cmd(0x439d05140980) 0x1a, CmdSN 0x2a003 from world 0 to dev "mpx.vmhba1:C0:T4:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T11:19:52.972Z cpu12:66349)ScsiDeviceIO: 2948: Cmd(0x439d0519bd00) 0x1a, CmdSN 0xa5c from world 67780 to dev "naa.60030057022f8400202252860bf410ea" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-02-10T11:19:53.023Z cpu2:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d0519bd00, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T11:19:53.023Z cpu2:65579)ScsiDeviceIO: 2962: Cmd(0x439d0519bd00) 0x85, CmdSN 0xa5e from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T11:49:53.089Z cpu10:65587)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d050a8900, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T11:49:53.089Z cpu10:65587)ScsiDeviceIO: 2962: Cmd(0x439d050a8900) 0x85, CmdSN 0xa67 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T12:19:53.102Z cpu13:66349)ScsiDeviceIO: 2948: Cmd(0x439d008eb2c0) 0x4d, CmdSN 0xa69 from world 67780 to dev "naa.60030057022f8400202252650a05e876" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T12:19:53.155Z cpu0:65577)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d008eb2c0, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T12:19:53.155Z cpu0:65577)ScsiDeviceIO: 2962: Cmd(0x439d008eb2c0) 0x85, CmdSN 0xa70 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T12:49:53.165Z cpu15:66349)ScsiDeviceIO: 2948: Cmd(0x439d008eeac0) 0x85, CmdSN 0xa78 from world 67780 to dev "naa.60030057022f8400202252860bf410ea" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T12:49:53.216Z cpu10:65587)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d008eeac0, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T12:49:53.216Z cpu10:65587)ScsiDeviceIO: 2962: Cmd(0x439d008eeac0) 0x85, CmdSN 0xa79 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T12:56:28.271Z cpu12:65589)ScsiDeviceIO: 2948: Cmd(0x439d008b8340) 0x1a, CmdSN 0x2a757 from world 0 to dev "mpx.vmhba1:C0:T4:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-02-10T13:19:53.276Z cpu13:65590)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d050b2300, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T13:19:53.277Z cpu13:65590)ScsiDeviceIO: 2962: Cmd(0x439d050b2300) 0x85, CmdSN 0xa82 from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T13:49:53.290Z cpu15:66349)ScsiDeviceIO: 2948: Cmd(0x439d05033c00) 0x1a, CmdSN 0x2aac5 from world 0 to dev "naa.60030057022f8400202252650a05e876" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-02-10T13:49:53.348Z cpu21:65598)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x85 (0x439d05033c00, 67780) to dev "naa.200049454505080f" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0. Act:NONE
2017-02-10T13:49:53.348Z cpu21:65598)ScsiDeviceIO: 2962: Cmd(0x439d05033c00) 0x85, CmdSN 0xa8b from world 67780 to dev "naa.200049454505080f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x26 0x0.
2017-02-10T14:04:11.270Z cpu12:65629)elxnet: elxnet_allocQueueWithAttr:4883: [vmnic1] RxQ, QueueIDVal:1
2017-02-10T14:04:11.270Z cpu12:65629)elxnet: elxnet_startQueue:5011: [vmnic1] RxQ, QueueIDVal:1
2017-02-10T14:04:16.272Z cpu12:65629)elxnet: elxnet_quiesceQueue:4969: [vmnic1] RxQ, QueueIDVal:1
2017-02-10T14:04:16.272Z cpu12:65629)elxnet: elxnet_freeQueue:4927: [vmnic1] RxQ, QueueIDVal:1

I don't see anything in regard to USB...
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
well if you plugged it into the host, and that's the vmkernel.log at the time, that's worse!

the host does not see it!

not a hope in hells chance, if the host does not see it to pass through nothing!

is there a usb.log you can check.
0
Ralph ScharpingDigital TherapistAuthor Commented:
Well, the Host does see it, because it offers to connect it.
0
Ralph ScharpingDigital TherapistAuthor Commented:
USB-Log shows nothing for today, but for the attempts of the previous days I see this:

2017-02-04T09:19:01Z mark: storage-path-claim-completed
2017-02-04T09:19:06Z usbarb[66962]: VTHREAD initialize main thread 3 "usbArb" tid 66962
2017-02-04T09:19:06Z usbarb[66962]: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2017-02-04T09:19:06Z usbarb[66962]: DICT --- GLOBAL SETTINGS /usr/lib/vmware/settings
2017-02-04T09:19:06Z usbarb[66962]: DICT --- NON PERSISTENT (null)
2017-02-04T09:19:06Z usbarb[66962]: DICT --- HOST DEFAULTS /etc/vmware/config
2017-02-04T09:19:06Z usbarb[66962]: DICT                    libdir = "/usr/lib/vmware"
2017-02-04T09:19:06Z usbarb[66962]: DICT           authd.proxy.nfc = "vmware-hostd:ha-nfc"
2017-02-04T09:19:06Z usbarb[66962]: DICT        authd.proxy.nfcssl = "vmware-hostd:ha-nfcssl"
2017-02-04T09:19:06Z usbarb[66962]: DICT   authd.proxy.vpxa-nfcssl = "vmware-vpxa:vpxa-nfcssl"
2017-02-04T09:19:06Z usbarb[66962]: DICT      authd.proxy.vpxa-nfc = "vmware-vpxa:vpxa-nfc"
2017-02-04T09:19:06Z usbarb[66962]: DICT            authd.fullpath = "/sbin/authd"
2017-02-04T09:19:06Z usbarb[66962]: DICT --- SITE DEFAULTS /usr/lib/vmware/config
2017-02-04T09:19:06Z usbarb[66962]: USBArbRuleStore: Error in '/etc/vmware/usbarb.rules' at line 1:0, '[' or '{' expected near end of file.
2017-02-04T09:19:06Z usbarb[66962]: VMware USB Arbitration Service Version 15.1.11
2017-02-04T09:19:06Z usbarb[66962]: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.
2017-02-04T09:19:06Z usbarb[66962]: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket
2017-02-04T09:19:06Z usbarb[66962]: SOCKET connect failed, error 2: No such file or directory
2017-02-04T09:19:06Z usbarb[66962]: USBArb: Failed to connect to the existing arbitrator.
2017-02-04T09:19:13Z usbarb[66962]: USBArb: UsbArbPipeConnected: Connected to client, socket:12
2017-02-04T09:19:13Z usbarb[66962]: USBArb: Client 67089 connected (version: 7)
2017-02-04T10:42:42Z usbarb[66962]: USBArb: UsbArbPipeConnected: Connected to client, socket:13
2017-02-04T10:42:42Z usbarb[66962]: USBArb: Client 75055 connected (version: 7)
2017-02-04T12:46:47Z usbarb[66962]: USBArb: UsbArbPipeConnected: Connected to client, socket:14
2017-02-04T12:46:48Z usbarb[66962]: USBArb: Client 79708 connected (version: 7)
2017-02-04T14:09:52Z usbarb[66962]: USBArb: UsbArbPipeConnected: Connected to client, socket:15
2017-02-04T14:09:52Z usbarb[66962]: USBArb: Client 83279 connected (version: 7)
2017-02-04T14:32:40Z usbarb[66962]: USBArb: Closing client, error:2
2017-02-04T14:32:40Z usbarb[66962]: USBArb: Client 79708 disconnected
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
those errors do not look good....

I would reboot the host, USB stack looks broken.

You should see clear declaration of the USB device....

e.g.


2015-08-04T10:01:12.971Z cpu8:33553)<6>usb 1-1.4: new low speed USB device number 9 using ehci_hcd
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: New USB device found idVendor=0529 idProduct=0001
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: New USB device strings: Mfr=1 Product=2 SerialNumber=0
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: Product: HASP HL 3.25
2015-08-04T10:01:13.095Z cpu15:33553)<6>usb 1-1.4: Manufacturer: AKS
2015-08-04T10:01:13.096Z cpu15:33553)<6>usb 1-1.4: usbfs: registered usb0109

2015-08-04T10:06:09.969Z cpu18:33553)<6>usb 2-1.2: new low speed USB device number 8 using ehci_hcd
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: New USB device found idVendor=0529 idProduct=0001
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: New USB device strings: Mfr=1 Product=2 SerialNumber=0
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: Product: HASP HL 3.25
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: Manufacturer: AKS
2015-08-04T10:06:10.090Z cpu18:33553)<6>usb 2-1.2: usbfs: registered usb0208

2015-08-04T10:17:15.038Z cpu4:33553)<6>usb 1-1.5: new high speed USB device number 11 using ehci_hcd
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: New USB device found idVendor=19d2 idProduct=0103
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: New USB device strings: Mfr=3 Product=2 SerialNumber=4
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: Product: ZTE WCDMA Technologies MSM
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: Manufacturer: ZTE Incorporated
2015-08-04T10:17:15.155Z cpu4:33553)<6>usb 1-1.5: SerialNumber: P6zzzzzzzz000
2015-08-04T10:17:15.158Z cpu4:33553)<6>usb 1-1.5: Vendor: 0x19d2 Product: 0x0103 Revision: 0x0000
2015-08-04T10:17:15.158Z cpu4:33553)<6>usb 1-1.5: Interface Subclass: 0x06 Protocol: 0x50

2015-08-04T10:04:13.718Z cpu15:33553)<6>usb 1-1.5: new high speed USB device number 10 using ehci_hcd
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: New USB device found idVendor=2357 idProduct=f000
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: New USB device strings: Mfr=3 Product=2 SerialNumber=4
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: Product: TP-LINK HSPA+ Modem
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: Manufacturer: TP-LINK Incorporated
2015-08-04T10:04:13.836Z cpu15:33553)<6>usb 1-1.5: SerialNumber: 863zzzzzz34668
2015-08-04T10:04:13.903Z cpu15:33553)<6>usb 1-1.5: Vendor: 0x2357 Product: 0xf000 Revision: 0x0000
2015-08-04T10:04:13.903Z cpu15:33553)<6>usb 1-1.5: Interface Subclass: 0x06 Protocol: 0x50

but if you see this game over!

2015-08-03T13:43:22.623Z cpu3:33553)<6>usb 1-1.2: device is not available for passthrough
2015-08-03T14:01:26.111Z cpu19:33553)<6>usb 2-1.2: device is not available for passthrough
2015-08-04T09:42:54.596Z cpu12:33553)<6>usb 1-1.2: device is not available for passthrough
2015-08-04T09:42:54.600Z cpu12:33553)<6>usb 1-1.2: device is not available for passthrough
2015-08-04T09:58:53.656Z cpu14:33553)<6>usb 2-1.2: device is not available for passthrough
2015-08-04T10:04:13.908Z cpu15:33553)<6>usb 1-1.5: device is not available for passthrough
2015-08-04T10:17:15.161Z cpu4:33553)<6>usb 1-1.5: device is not available for passthrough

What server is this ?
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
Ralph ScharpingDigital TherapistAuthor Commented:
I'll give it a try.  Thanks a lot, Andrew.
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.