Hello, I just had to reboot the suse 9.3 server and ran into a problem. The system has two on board network (Ethernet) devices which are used and connected to the internal and external network. eth-id-00:02:b3:e9:d2:cc for external network and eth-id-00:02:b3:e9:d2:cd for internal network When the server started again the network interfaces were assigned the wrong way. instead of setting it up like this ----- eth0 device: Intel Corporation 82547GI Gigabit Ethernet Controller eth0 configuration: eth-id-00:02:b3:e9:d2:cc eth0 IP address: 192.168.10.10/24 eth1 device: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 10) eth1 configuration: eth-id-00:02:b3:e9:d2:cd eth1 IP address: 192.168.100.1/24 ----- it set it up like this ----- eth0 device: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 10) eth0 configuration: eth-id-00:02:b3:e9:d2:cd eth0 IP address: 192.168.100.1/24 eth1 device: Intel Corporation 82547GI Gigabit Ethernet Controller eth1 configuration: eth-id-00:02:b3:e9:d2:cc eth1 IP address: 192.168.10.10/24 done ---- so just external config with internal config swapped. The server basically doesn't work properly with this setup. Several reboots showed that most of the times the devices get the wrong config assigned. I thought that with the hotplug setup that should not matter but it did. Is there a way to make sure the server always get the correct configuration for the devices? My main concern is, when in case of electricity cuts the server get rebooted after the ups has done its work I can't guaranty the the server keeps functioning. Any help or hint would be appreciated. Ulf
On Tuesday 13 September 2005 11:04, Ulf Rasch wrote: <snip>
When the server started again the network interfaces were assigned the wrong way.
Hi Ulf, This topic has been addressed {yes, a pun] many times on SLE. :-) Here's a link to one of the more recent threads: http://marc.theaimsgroup.com/?l=suse-linux-e&m=112620101118660&w=2 hth & regards, - Carl
Ulf Rasch wrote:
Hello,
I just had to reboot the suse 9.3 server and ran into a problem.
The system has two on board network (Ethernet) devices which are used and connected to the internal and external network.
eth-id-00:02:b3:e9:d2:cc for external network and eth-id-00:02:b3:e9:d2:cd for internal network
Where are you using eth0 etc., that this is causing a problem? Your config info is contained i the various ifcfg files in /etc/sysconfig/network, so the IP addresses etc., should be fine. The SuSE firewall also uses the full interface name, which includes the MAC address. My firewall has 3 NICs and doesn't show any such problems.
On Tuesday 13 September 2005 18:42, James Knott wrote:
Ulf Rasch wrote:
Hello,
I just had to reboot the suse 9.3 server and ran into a problem.
The system has two on board network (Ethernet) devices which are used and connected to the internal and external network.
eth-id-00:02:b3:e9:d2:cc for external network and eth-id-00:02:b3:e9:d2:cd for internal network
Where are you using eth0 etc., that this is causing a problem? Your config info is contained i the various ifcfg files in /etc/sysconfig/network, so the IP addresses etc., should be fine. The SuSE firewall also uses the full interface name, which includes the MAC address. My firewall has 3 NICs and doesn't show any such problems.
Carl and James, thanks for you hints. I blamed it on the network setup. Was looking for any eth0 and eth1 in all the configs but couldn't find it. The problem was that not all the services started after the reboot and I was focusing on the device. Doooh. The devises get configured correctly. Only the order when they might get configured differs. Well, good thing is I learned quite a bit today. ;-) Thanks Ulf
participants (3)
-
Carl Hartung -
James Knott -
Ulf Rasch