1

[Resolved]: The network cable had been connected to the integrated NIC physical interface, which although accessible, was no longer enabled. The problem was solved by connecting the cable to the additional I350 Gigabit adapter. Stupid as it sounds, as usual, a human mistake. Server running smooth and pleasantly.

Many thanks in advance for whoever comes up with an idea for this puzzle!

Please excuse the typing errors in the terminal output, but I can't dump from the iDRAC virtual console. I wish, then I wouldn't have a network problem...

The story short: I am setting up a new Dell EMC PowerEdge. Ubuntu 16.04.3 LTS installation has ran smoothly using iDRAC v8 with self-configured network profile.

Now, I try to bring up the additional Gigabit Ethernet interfaces (2xIntel I350) and I can't even see the device locally.

ifconfig shows me a fully configured interface (enp177s0f0) and ifup confirms this with RTNETLINK enp177s0f0 already configured.

Output of ifconfig:

ifconfig -a

    enp177s0f0 Link encap: Ethernet HWaddr xx:xx:xx:xx:xx:xx
    inet addr: 137.193.xx.aa Bcast: 137.193.xx.255 Mask: 255.255.255.0
    UP BROADCAST MULTICAT 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: ....

    enp177s0f1 Link encap: Ethernet HWaddr xx:xx:xx:xx:xx:xx
    BROADCAST MULTICAT 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: ...

    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:65636 Metric:1
    RX packets:399 errors:0 dropped:0 overruns:0 frame:0
    TX packets: 399 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1
    RX bytes:33576 (33.5 KB) TX bytes: 33576 (33.5 KB)

    virbr0 Link encap: Ethernet HWaddr yy:yy:yy:yy:yy:yy
    inet addrs: 137.193.xx.aa Bcast 137.193.xx.255 Mask: 255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 Tx bytes: 180

    virbr0-nic Link encap:Ethernet HWaddr yy:yy:yy:yy:yy:yy
    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 Tx bytes: 0

However RTNETLINK ip link show dev enp177s0f0 shows me the same interface in state "down". Trying to bring the link up (ip link set dev enp177s0f0 up) is doing literally nothing.

I have restarted, stopped and started the networking interfaces (/etc/init.d/networking restart) in all possible combinations. Reboots included. The /etc/network/interfaces contains a valid network configuration working on other servers.

The output of ethtool enp177s0f0 tells the link cannot be detected:

output of ethtool

Any ideas what could be happening? Anyone knows if Ubuntu may be lacking drivers for the I350 and if so, how to bring them on the server through iDRAC?

Could it be a speed negotiation issue with the switch? I am using an AT FS705EFC/SC with cat6a network cable.

I use a different IP address on the iDRAC and the Gigabit interfaces. To my knowledge, this isn't an issue, but I am happy to learn if I am missing something here.

In the "system network devices" tab of the idrac web interface, the following is listed for the i350 card: idrac listing for i350

  • 1
    Please insert the output of ifconfig into your question, so the question will still be valid when the remote image goes away. – Andrew Schulman Jan 17 '18 at 14:47
  • It would be nice, and I understand your point. But like I explained, from the iDRAC remote console I can't dump to file neither copy to the host. So, before I start hand-typing MAC addresses, I rather wait until someone comes with a hint. – Ela Jan 17 '18 at 14:52
  • Could you please confirm that the kernel module for i350 is loaded? modprobe igb then lsmod. This is not a a problem with your switch ot the links being down. – sfk Jan 18 '18 at 8:19
  • The modprobe -v igb has no output. With lsmod, igb shows up (size 196608) used by 0. – Ela Jan 18 '18 at 11:39
  • The i350 is an add-on pcie card or is it the onboard NDC (note: based on the ifconfig screenshot, it seem that your server has no em1/em2 interfaces thus i guess it is the latter case)? Also, is it visible with lspci, is it visible using the idrac (in the inventory section) ? – sfk Jan 18 '18 at 13:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.