Open The-snOOpz opened 5 years ago
Hi @The-snOOpz Is QNA-T310G1S listed in pci list (output of lspci) ? If no, please try to install the latest TB3 firmware update. Most likely it is known issues and related to TB3 chipset
Hi @dbezrukovaquantia When I install W10 it's working fine. I can use the QNA-T310G1S.
On your requisite, I have upgraded the TB3 FW to v25 (I was previously on v18). And I tried to reinstall ESXi v6.7u2 with the net670-atlantic-v2.2.3.0-esxi1.5.x86_x64.vib I have the same thing with "lspci" & "esxcli hardware pci list" I see the TB3 controller :
0000:02:00.0
Address: 0000:02:00.0
Segment: 0x0000
Bus: 0x02
Slot: 0x00
Function: 0x0
VMkernel Name:
Vendor Name: Intel Corporation
Device Name: DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
Configured Owner: VMkernel
Current Owner: VMkernel
Vendor ID: 0x8086
Device ID: 0x1576
SubVendor ID: 0x0000
SubDevice ID: 0x0000
Device Class: 0x0604
Device Class Name: PCI bridge
Programming Interface: 0x00
Revision ID: 0x00
Interrupt Line: 0xff
IRQ: 255
Interrupt Vector: 0x00
PCI Pin: 0x00
Spawned Bus: 0x00
Flags: 0xf203
Module ID: -1
Module Name: None
Chassis: 0
Physical Slot: 0
Slot Description: SDXC Card Slot
Passthru Capable: false
Parent Device: PCI 0:0:28:4
Dependent Device:
Reset Method: Bridge reset
FPT Sharable: false
But not the QNA-T310G1S.
[root@nuc:~] lspci -pv
Segm:Bu:De.F Vend:Dvid Subv:Subd ISA/irq/Vect P M Module Name
Spawned bus
0000:00:00.0 8086:1910 8086:2064 V
0000:00:02.0 8086:193b 8086:2064 11/ / A V
0000:00:08.0 8086:1911 8086:2064 11/ / A V
0000:00:14.0 8086:a12f 8086:2064 11/ /0x31 A V vmkusb vmhba32
0000:00:14.2 8086:a131 8086:2064 11/ / C V
0000:00:16.0 8086:a13a 8086:2064 11/ / A V
0000:00:17.0 8086:a103 8086:2064 11/ /0x32 A V vmw_ahci vmhba0
0000:00:1c.0 8086:a110 0000:0000 11/ / A V PCIe RP[0000:00:1c.0]
01
0000:00:1c.4 8086:a114 0000:0000 11/ / A V PCIe RP[0000:00:1c.4]
02
0000:00:1d.0 8086:a118 0000:0000 11/ / A V PCIe RP[0000:00:1d.0]
3b
0000:00:1d.4 8086:a11c 0000:0000 11/ / A V PCIe RP[0000:00:1d.4]
3c
0000:00:1f.0 8086:a14e 8086:2064 V
0000:00:1f.2 8086:a121 8086:2064 V
0000:00:1f.3 8086:a170 8086:2064 11/ / A V
0000:00:1f.4 8086:a123 8086:2064 11/ / A V
0000:00:1f.6 8086:15b7 8086:2064 11/ /0x33 A V ne1000 vmnic0
0000:02:00.0 8086:1576 0000:0000 255/ / A V
00
[root@nuc:~]
I have the QNAP-T310G1S (SFP+) with Chipset AQC-100 working on my Intel Skull Canyon NUC with the net670-atlantic-v2.2.3.0-esxi1.6.x86_x64-offline-bundle.zip driver.
Hello OS system ESXI VER 6.7 Added QNA-UC5G1T (AQtion AQC111U) support thank
@ErikBussink
I have the QNAP-T310G1S (SFP+) with Chipset AQC-100 working on my Intel Skull Canyon NUC with the net670-atlantic-v2.2.3.0-esxi1.6.x86_x64-offline-bundle.zip driver.
I have tried to reinstall from scratch ESX6.7u2 RollUp or ESX6.7u3 on my Intel Skull Canyon NUC (NUC6I7KYK) and after this fresh install, I put the net670-atlantic-v2.2.3.0-esxi1.6.x86_x64-offline-bundle.zip but it's not working... And under my W10, it's working fine! I really don't understand why it's working for you and not for me under my 2 NUCs...
@ErikBussink
I have the QNAP-T310G1S (SFP+) with Chipset AQC-100 working on my Intel Skull Canyon NUC with the net670-atlantic-v2.2.3.0-esxi1.6.x86_x64-offline-bundle.zip driver.
I have tried to reinstall from scratch ESX6.7u2 RollUp or ESX6.7u3 on my Intel Skull Canyon NUC (NUC6I7KYK) and after this fresh install, I put the net670-atlantic-v2.2.3.0-esxi1.6.x86_x64-offline-bundle.zip but it's not working... And under my W10, it's working fine! I really don't understand why it's working for you and not for me under my 2 NUCs...
Putting the zip file where? I've been using 2.2.3.0 1.6 release for a while; it worked under 6.5 and 6.7 up to U3.
Hi, @The-snOOpz, please refer to the following article to update firmware of your NUC
Hi @frozenak, I have tried to install vib or the zip 2.2.3.0 1.6 : same result = not working Hi @dbezrukovaquantia, thx for the URL. My 2 NUCs are already up to date to the last FW for the BIOS & Thunderbolt3. Maybe it's incompatible with my Mikrotik CRS309-1G-8S+ or with the 10Gtek DAC cable. But when I install W10 it's working.
Hi, @The-snOOpz following this article, there is said that NUC Gen 7th and 8th support for thunderbolt devices on ESXi. I'm not sure but probably it is the reason why your NUC Gen6 may don't support it. Unfortunately, we don't have any NUCs to check it. Hi, @ErikBussink, may you please share more info about your NUC which looks working with QNAP-T310G1S?
Hi, new to github/totally out of my league/trying to figure out an issue - I have a little information, hope it helps someone out. VMware official word is that the AQC107 is listed as "community supported" only - I assume that means that it hasn't been tested, and any weird issues fall under "buyer beware". In my case, the esx6.7 hosts won't apply any critical updates past U2. We were planning on connecting it to a QNAP TS-73.
2019-10-13T21:12:23Z esxupdate: 2106192: esxupdate: ERROR: vmware.esximage.Errors.AcceptanceConfigError: VIB Aquantia_bootbank_net-atlantic_v2.2.3.0-esxi1.6's acceptance level is community, which is not compliant with the ImageProfile acceptance level partner
Hi, new to github/totally out of my league/trying to figure out an issue - I have a little information, hope it helps someone out. VMware official word is that the AQC107 is listed as "community supported" only - I assume that means that it hasn't been tested, and any weird issues fall under "buyer beware". In my case, the esx6.7 hosts won't apply any critical updates past U2. We were planning on connecting it to a QNAP TS-73.
2019-10-13T21:12:23Z esxupdate: 2106192: esxupdate: ERROR: vmware.esximage.Errors.AcceptanceConfigError: VIB Aquantia_bootbank_net-atlantic_v2.2.3.0-esxi1.6's acceptance level is community, which is not compliant with the ImageProfile acceptance level partner
Is the acceptance level on your host(s) set to CommunitySupported? I've updated from 6.5 all the way to 6.7U3 without issue. The message reads that the host(s) current acceptance level is set to Partner.
From SSH: esxcli software acceptance get
Thanks for letting me know. I’ve been speaking to vmware support and was told to lose the card and driver. I wasn’t aware that you could change the support level. I’ll go through the document you sent and mention it to vmware.
From: frozenak notifications@github.com Sent: Tuesday, October 15, 2019 1:29 AM To: Aquantia/AQtion-esxi AQtion-esxi@noreply.github.com Cc: Nicholas Ferraro nferraro@arcadiarecovery.com; Comment comment@noreply.github.com Subject: Re: [Aquantia/AQtion-esxi] AQC-100 doesn't work with ESX 6.7 (#4)
Hi, new to github/totally out of my league/trying to figure out an issue - I have a little information, hope it helps someone out. VMware official word is that the AQC107 is listed as "community supported" only - I assume that means that it hasn't been tested, and any weird issues fall under "buyer beware". In my case, the esx6.7 hosts won't apply any critical updates past U2. We were planning on connecting it to a QNAP TS-73.
2019-10-13T21:12:23Z esxupdate: 2106192: esxupdate: ERROR: vmware.esximage.Errors.AcceptanceConfigError: VIB Aquantia_bootbank_net-atlantic_v2.2.3.0-esxi1.6's acceptance level is community, which is not compliant with the ImageProfile acceptance level partner
Is the acceptance level on your host(s) set to CommunitySupported? I've updated from 6.5 all the way to 6.7U3 without issue. The message reads that the host(s) current acceptance level is set to Partner.
From SSH: esxcli software acceptance get
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Aquantia/AQtion-esxi/issues/4?email_source=notifications&email_token=ANPPYYT7VIAIWYND2LSGMXLQOVILJA5CNFSM4HIUFMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBHOZ3Q#issuecomment-542043374, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANPPYYTHUBTI6LZDG47WP53QOVILJANCNFSM4HIUFMOA.
Got sick of waiting, turned down the acceptance level on the server, slammed the card back in and it updated fine along with the others. Thanks for the help:)
From: frozenak notifications@github.com Sent: Tuesday, October 15, 2019 1:29 AM To: Aquantia/AQtion-esxi AQtion-esxi@noreply.github.com Cc: Nicholas Ferraro nferraro@arcadiarecovery.com; Comment comment@noreply.github.com Subject: Re: [Aquantia/AQtion-esxi] AQC-100 doesn't work with ESX 6.7 (#4)
Hi, new to github/totally out of my league/trying to figure out an issue - I have a little information, hope it helps someone out. VMware official word is that the AQC107 is listed as "community supported" only - I assume that means that it hasn't been tested, and any weird issues fall under "buyer beware". In my case, the esx6.7 hosts won't apply any critical updates past U2. We were planning on connecting it to a QNAP TS-73.
2019-10-13T21:12:23Z esxupdate: 2106192: esxupdate: ERROR: vmware.esximage.Errors.AcceptanceConfigError: VIB Aquantia_bootbank_net-atlantic_v2.2.3.0-esxi1.6's acceptance level is community, which is not compliant with the ImageProfile acceptance level partner
Is the acceptance level on your host(s) set to CommunitySupported? I've updated from 6.5 all the way to 6.7U3 without issue. The message reads that the host(s) current acceptance level is set to Partner.
From SSH: esxcli software acceptance get
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Aquantia/AQtion-esxi/issues/4?email_source=notifications&email_token=ANPPYYT7VIAIWYND2LSGMXLQOVILJA5CNFSM4HIUFMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBHOZ3Q#issuecomment-542043374, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANPPYYTHUBTI6LZDG47WP53QOVILJANCNFSM4HIUFMOA.
Hello, I have tested the vib on ESX 6.7 & 6.7u1 & 6.7u2 and it doesn't work with QNA-T310G1S (Chipset AQC100) on Skull Canyon NUC. I have tried DAC & RJ45 Module same result
I see the Thunderbold 3 correctly with "lspci" :
and the vib :
But nothing on the “esxcli system module list” & no light on the QNA-T310G1S Even if I tried to “--enabled” the module
Could you please do an update of the vib?