View Full Version : SLES 12 SP1 Intel X520 10GB Ethernet Controller did not come up

19-Jan-2017, 11:01

i have a Dell Poweredge R530 Server with Suse Enterprise Server 12 SP1 with an Intel X520 2 Ports 10Gbit/s DA/SFP+ Server Adapter, Low Profile Controller, the Driver Version is intel-ixgbe 4.3.13.

The Interface is allways down, if i try to bring the interface up with "ifup p3p1" i got allways

"p3p1 setup-in-progress"

systemctl status networt:

wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
Active: active (exited) since Wed 2017-01-18 14:51:34 CET; 20h ago
Main PID: 2893 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/wicked.service

Jan 18 14:51:34 zkmserv8 wicked[2893]: lo up
Jan 18 14:51:34 zkmserv8 wicked[2893]: em1 up
Jan 18 14:51:34 zkmserv8 wicked[2893]: p3p1 setup-in-progress
Jan 18 14:51:34 zkmserv8 wicked[2893]: p3p2 setup-in-progress
Jan 18 14:51:34 zkmserv8 systemd[1]: Started wicked managed network interfaces.

So what should i do to bring the interface up ?

Automatic Reply
25-Jan-2017, 06:30

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- Open a service request: https://www.suse.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot..

Good luck!

Your SUSE Forums Team

25-Jan-2017, 10:28
Hi it_team_ka,

just recently I met a similar case, where the interface setup didn't complete because there were redundant routing entries in /etc/sysconfig/network/routes and the interface-specific routes file (/etc/sysconfig/network/ifcfg-p3p1-routes. So this could easily be some configuration issue.

Anything popping in the journal during ifup processing?