Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AQC-100 doesn't work with ESX 6.7 #4

Open
The-snOOpz opened this issue Apr 26, 2019 · 13 comments
Open

AQC-100 doesn't work with ESX 6.7 #4

The-snOOpz opened this issue Apr 26, 2019 · 13 comments
Labels
question Further information is requested

Comments

@The-snOOpz
Copy link

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" :

0000:02:00.0 Bridge PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
Class 0604: 8086:1576

and the vib :

esxcli software vib list | grep -i aqua
net-atlantic v2.2.3.0-esxi1.4 Aquantia CommunitySupported 2019-04-19

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?

@dimbez
Copy link
Collaborator

dimbez commented Apr 26, 2019

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

@dimbez dimbez added the question Further information is requested label Apr 26, 2019
@The-snOOpz
Copy link
Author

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:~] 

@ErikBussink
Copy link

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.

@paiBZIP
Copy link

paiBZIP commented Aug 13, 2019

Hello
OS system ESXI VER 6.7
Added QNA-UC5G1T (AQtion AQC111U) support
thank

@The-snOOpz
Copy link
Author

@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...

@frozenak
Copy link

@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.

@dimbez
Copy link
Collaborator

dimbez commented Sep 30, 2019

Hi, @The-snOOpz, please refer to the following article to update firmware of your NUC

@The-snOOpz
Copy link
Author

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.

@dimbez
Copy link
Collaborator

dimbez commented Oct 2, 2019

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?

@naf74
Copy link

naf74 commented Oct 14, 2019

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

@frozenak
Copy link

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

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.security.doc/GUID-751034F3-5337-4DB2-8272-8DAC0980EACA.html

@naf74
Copy link

naf74 commented Oct 15, 2019 via email

@naf74
Copy link

naf74 commented Oct 15, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

6 participants