Community
cancel
Showing results for 
Search instead for 
Did you mean: 
YHdou
Beginner
1,494 Views

The Ethernet ports of the I350-F2 are not recognised

Hi,

We are trying to integrate the I350-F2 Ethernet card to our products, and we are facing to this problem: The I350-F2 is detected but the 2 Ethernet Ports are not recognised. It seems that there is a conflict between the 2 Ethernet ports of the motherboard and the 2 Ethernet port of the I350-F2.

Here is the output ifconfig:

__tmp370698911 Link encap:Ethernet HWaddr A0:36:9F:67:D3:C9

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)

__tmp1412522235 Link encap:Ethernet HWaddr A0:36:9F:67:D3:C8

BROADCAST MULTICAST MTU:1500 Metric:1

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

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

collisions:0 txqueuelen:1000

RX bytes:1856694 (1.7 MiB) TX bytes:1856694 (1.7 MiB)

eth0 Link encap:Ethernet HWaddr 0C:C4:7A:72:2E:9A

inet addr:192.168.3.200 Bcast:192.168.31.255 Mask:255.255.224.0

inet6 addr: fe80::ec4:7aff:fe72:2e9a/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

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

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

collisions:0 txqueuelen:1000

RX bytes:8426155 (8.0 MiB) TX bytes:81922 (80.0 KiB)

eth1 Link encap:Ethernet HWaddr 0C:C4:7A:72:2E:9B

inet addr:192.168.3.195 Bcast:192.168.31.255 Mask:255.255.224.0

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)

Here is the dmesg log:

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: eth0: (PCIe:5.0GT/s:Width x4) <6>igb 0000:02:00.0: eth0: MAC: a0:36:9f:67:d3:c8

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: eth0: PBA No: G15813-004

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: PCI INT B -> GSI 36 (level, low) -> IRQ 36

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: eth1: (PCIe:5.0GT/s:Width x4) <6>igb 0000:02:00.1: eth1: MAC: a0:36:9f:67:d3:c9

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: eth1: PBA No: G15813-004

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: eth2: (PCIe:2.5GT/s:Width x1) <6>igb 0000:07:00.0: eth2: MAC: 0c:c4:7a:72:2e:9a

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: eth2: PBA No: 013A00-000

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: eth2: (PCIe:2.5GT/s:Width x1) <6>igb 0000:08:00.0: eth2: MAC: 0c:c4:7a:72:2e:9b

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: eth2: PBA No: 011000-000

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

Kernel: 2.6.29.6

igb driver : 5.0.6

Is there a solution for this issue ?

If you need more info, don't hesitate to ask me.

Thank in advance.

0 Kudos
8 Replies
idata
Community Manager
129 Views

Hi Yassinehdouri,

 

 

Thank you for writing to Wired Communities. What is the brand and model of the motherboard where the I350-F2 was installed?

 

 

Are you encountering the same issue if you install the I350-F2 on another board model?

 

 

Looking forward to your reply. Thanks.

 

 

Regards,

 

Sharon T
YHdou
Beginner
129 Views

Hi Sharon,

 

The mothebroard is X10DRL-i. For more information, here is the user's Manual: ftp://ftp.supermicro.com/ISO_Extracted/CDR-X10_1.10_for_Intel_X10_platform/MANUALS/X10DRL-i.pdf

This motherboard has 6 PCIe slots. the problem happens with slots 2 to 6 that are connected to the CPU.

With the slot 1 which is connected to the chipset, the 2 Ethernet ports of the I350-F2 are detected and recognised correctly.

As you can see on the picture below:

  • Slot 2 to 6 are connected to the CPU
  • Slot 1 is connected to chipset PCH C612
  • LAN1 and LAN 2 are connected to the chipset PCH C612

The PCI bus sees the I350-F2 when it's connected to slot 2 to 6, and then the LAN1 and LAN2. I think this is why we have a conflicts.

@Sharon what do you think ?

Thanks in advance.

Best regards,

Hdouri Yassine

idata
Community Manager
129 Views

Hi Yassinehdouri,

 

 

Thank you for the information provided. Based on the information, we can conclude the I350-F2 is working fine since its ports are

 

recognized when installed on slot 1. Just to double check:

 

 

1) Have you tried updating the board BIOS if this will make any changes?

 

 

2) As there are onboard NIC LAN1 and LAN2, have you tried disabling the onboard NICs?

 

 

3) Noticed the PBA number of I350-F2 is G15813-004, this is an OEM part number, the Intel retail version of I350-F2's PBA number

 

is G15814, you may refer to this link for reference:

 

https://www.intel.com/content/www/us/en/support/articles/000005612/network-and-i-o/ethernet-products...

 

Does this NIC came with the Supermicro system when purchased?

 

 

 

4) Have you checked with Supermicro this is a compatible NIC for their system? As this involved the slots on their board, you might

 

want to further check with them.

 

 

Regards,

 

Sharon T

 

YHdou
Beginner
129 Views

Hi Sharon,

Thank you for your reply. You can find below a reply to your questions:

1) Have you tried updating the board BIOS if this will make any changes?

[HY] Yes we have the latest update

2) As there are onboard NIC LAN1 and LAN2, have you tried disabling the onboard NICs?

[HY] When the LAN1 and LAN are disabled, the problem doesn't happen.

3) Noticed the PBA number of I350-F2 is G15813-004, this is an OEM part number, the Intel retail version of I350-F2's PBA number

is G15814, you may refer to this link for reference:

https://www.intel.com/content/www/us/en/support/articles/000005612/network-and-i-o/ethernet-products... https://www.intel.com/content/www/us/en/support/articles/000005612/network-and-i-o/ethernet-products...

Does this NIC came with the Supermicro system when purchased?

[HY] No, we bought this NIC from a local distributor.

4) Have you checked with Supermicro this is a compatible NIC for their system? As this involved the slots on their board, you might

want to further check with them.

[HY] Not yet. I will check with them if it's compatible with the X10DRL-i.

After some research, I found that many users have the same problem as us. Here is an example:

https://bugzilla.redhat.com/show_bug.cgi?id=224662 https://bugzilla.redhat.com/show_bug.cgi?id=224662

https://www.linuxquestions.org/questions/linux-networking-3/fc7-eth2-and-eth3-come-up-as-__tmp-60-of... https://www.linuxquestions.org/questions/linux-networking-3/fc7-eth2-and-eth3-come-up-as-__tmp-60-of...

https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/1458683_1.html https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/1458683_1.html

Thus, it's not a problem of incompatibility with the motherboard.

The workaround that other users found is to edit the "ifcfg-ethx" files and the udev rules.

Do you have other solution that we can use it on production environment ?

Is it possible to configure the NIC ROM in order to make the PCIe enumeration slower ?

Thank you in advance for your help.

Best regards,

Yassine

idata
Community Manager
129 Views

Hi Yassinehdouri,

 

 

Thank you for the information. Since there is no issue if you disabled the onboard LAN 1 and LAN2, you can check with Supermicro* if they have BIOS upgrade to address this and also check for compatibility issue. We do not have control over the OEM NIC since the OEM vendor might have modified the NIC which is not within our control. I will try help check on the ROM inquiry in case there is any information to share, since the issue occurred only when installed on the board, it is better to contact the board vendor for further suggestion.Thanks.

 

 

Regards,

 

Sharon T
YHdou
Beginner
129 Views

Thank you Sharon for your reply,

I want to share with you a script that I made quickly to bypass this problem. The python script and the script output are on the attachment file.

This script takes MAC info from lspci and /sys/class/net, and then a new ifcfg files are created with the right MAC order.

The script is compatible with dual and quad ports NIC.

Here is the output of ifconfig after running the script:

I'm waiting your reply about the NIC ROM.

Thank you Sharon,

Best regards.

Yassine

idata
Community Manager
129 Views

Hi Yassinehdouri,

 

 

Thank you for sharing your solution. With regards to the tool that configure the ROM, we required a NDA (Non-Disclosure Agreement) to avail the tool.

 

Since you are using an OEM card, please contact your OEM manufacturer for the availability of the tool. Hope this information clarified.

 

 

Thanks,

 

Sharon T
YHdou
Beginner
129 Views

Thank you Sharon.

Yassine

Reply