Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1,793 Views

Using QCU to config 4x10G on XL710-QDA2: QSFP+ Configuration modification is not supported by this adapter.

It takes us more than one week to fix this problem, but failed. Our server is built as belows

Motherboard: Intel S2600CW2R

CPU: E5 2660 V4

Network Adapter: XL710-QDA2

OS: Linux Ubuntu 16.04

We are using Intel QSFP Configuration Utility to config ports as 4x10G mode. All NVMs and drivers have been updated to the latest version. Here are the details of our log file. Anybody could give us some help? Thanks in advance.

tb-user@tbuser-S2600CWR:~/LinuxTool/Linux_x64$ sudo ./qcu64e /DEVICES

[sudo] password for tb-user:

Intel(R) QSFP+ Configuration Utility

QCU version: v2.27.10.01

Copyright(C) 2016 by Intel Corporation.

Software released under Intel Proprietary License.

NIC Seg:Bus Ven-Dev Mode Adapter Name

=== ======= ========= ======= ==================================================

1) 000:004 8086-1583 N/A Intel(R) Ethernet Converged Network Adapter XL710-

tb-user@tbuser-S2600CWR:~/LinuxTool/Linux_x64$ sudo ./qcu64e /NIC=1 /set=4x10

Intel(R) QSFP+ Configuration Utility

QCU version: v2.27.10.01

Copyright(C) 2016 by Intel Corporation.

Software released under Intel Proprietary License.

QSFP+ Configuration modification is not supported by this adapter.

tb-user@tbuser-S2600CWR:~/LinuxTool/Linux_x64$ ifconfig -a

enp1s0f0 Link encap:Ethernet HWaddr a4:bf:01:1b:89:9e

inet addr:150.236.28.199 Bcast:150.236.28.223 Mask:255.255.255.224

inet6 addr: fe80::5622:3a76:5c53:30f4/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:4079 errors:0 dropped:0 overruns:0 frame:0

TX packets:322 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:472072 (472.0 KB) TX bytes:38743 (38.7 KB)

Memory:91920000-9193ffff

enp1s0f1 Link encap:Ethernet HWaddr a4:bf:01:1b:89:9f

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Memory:91900000-9191ffff

ens261f0 Link encap:Ethernet HWaddr 00:16:f6:f6:10:0a

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ens261f1 Link encap:Ethernet HWaddr 00:16:f6:f6:10:0b

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:138 errors:0 dropped:0 overruns:0 frame:0

TX packets:138 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:12084 (12.0 KB) TX bytes:12084 (12.0 KB)

tb-user@tbuser-S2600CWR:~/LinuxTool/Linux_x64$ sudo ethtool ens3f2

Settings for ens3f2:

...

0 Kudos
3 Replies
Highlighted
Community Manager
30 Views

Hi Chinabanker,

 

 

Thank you for posting in Wired Communities. Can you share what is the SFP+ module brand and model used for the XL710-QDA2?

 

 

Thanks,

 

Sharon T
0 Kudos
Highlighted
Beginner
30 Views

Hi, Sharon

Thank you for the response first. We were using Dell's XL710-QDA2 and their QSFP+ modules. Today we replace them with Intel branded XL710. It's now all right to use Intel QCU to configure all the modes of ports.

Obviously, Intel QCU ONLY supports to Intel branded NIC. Although other OEM XL710 adapters are using same Intel XL710 chips, they are not working with Intel utilities. Ridiculous!

I wish this case could help others who suffer same problems as us.

0 Kudos
Highlighted
Community Manager
30 Views

Hi Chinabanker,

Thank you for the update and sharing the information. I am glad using the Intel XL710 works for you now. Apologize for any inconvenience and thanks again for the useful information.

Regards,

 

Sharon T
0 Kudos