Try to disable network manager on that interface On Mar 24, 2013 7:17 AM, "Joakim Ziegler" joakim@terminalmx.com wrote:
I do have ONBOOT=yes, yes. It comes up on boot (if there's a link), it just doesn't come up after the link goes down and comes back up.
-- Joakim Ziegler - Supervisor de postproducción - Terminal joakim@terminalmx.com - 044 55 2971 8514 - 5264 0864
On 23/03/13 21:13, Earl Ramirez wrote:
On Sat, 2013-03-23 at 20:27 -0600, Joakim Ziegler wrote:
I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card.
I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc.
Everything seems to work fine, with a single exception. If I reboot the Mac on the other end, causing the link state of the fiber interface to bounce, the network interface on the Linux box doesn't come back up when the link comes back up. That is, ifconfig shows it as having the link up, but it doesn't do the equivalent of "ifup eth2" when the link comes back, so it doesn't get an IP, the routing table doesn't get updated,
etc.
So, my question is, how can I make CentOS automatically configure this interface when the link comes back up? It's a bit annoying having to log in and do ifup eth2 every time...
Joakim,
Do you have ONBOOT=yes in the /etc/sysconfig/network-scripts/ifcfg-eth2?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos