Jan Kalcic wrote:
Rudi Ahlers wrote:
Hi all
I wonder if someone can help me. I have a Gigabyte 8S661FXMP-RZ PIV
mobo with 10/100 onboard NIC (Sis900), which has been running happily
for more than 2 years on 192.168.0.6 on Suse 9.3. I recently upgraded
the machine to Suse 10.2 (fresh install 1 month ago), and it's been
working fine since yesterday. So, the NIC & the mobo works fine.
Now, I added a new NIC yesterday for heartbeat, and configured it on
192.168.100.2 (It's a D-Link DGE-528T)
The problem is, the moment I reboot the server, the onboard NIC looses
it's IP address, yet the PCI one doesn't.
scanpci outpout:
pci bus 0x0000 cardnum 0x04 function 0x00: vendor 0x1039 device 0x0900
Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
pci bus 0x0000 cardnum 0x09 function 0x00: vendor 0x1186 device 0x4300
D-Link System Inc DGE-528T Gigabit Ethernet Adapter
lspci
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
PCI Fast Ethernet (rev 90)
00:09.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit
Ethernet Adapter (rev 10)
I can see that the IP address is configured for the NIC, both when I
use YaST's Network Devices control panel & cat the config file via SSH:
ron:~ # cat /etc/sysconfig/network/ifcfg-eth-id-00\:0f\:ea\:c3\:3c\:55
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.0.6'
MTU=''
NAME='Giga-byte SiS900 PCI Fast Ethernet'
NETMASK='255.255.255.0'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
UNIQUE='rBUF.yJBPB64E8RC'
USERCONTROL='no'
_nm_name='bus-pci-0000:00:04.0'
PREFIXLEN=''
Any suggestions?
Hi,
What do you mean it loses the I address? Are the interfaces (eth0,
eth1...) created? During the boot are the interfaces activated correctly
or it gives you some error?
Regards,
Jan
Simple, I configure eth0 with 192.168.0.6, reboots, and then it doesn't
have an IP address
eth1 is configured with 192.168.100.2, and it keeps it upon reboot.
Scanning through /var/log/boot.msg doesn't yield much
I have noticed that udev renamed the eth devices, and if I rename eth0
to something like eth2 it works fine, but that's not really an option,
since some code (like iptables, smb, MySQL & heartbeat are bound to the
network devices. This is part of a cluster, so to change the ether
device names on 1 machine cold cause problems all over the LAN
<6>eth1: SiS 900 PCI Fast Ethernet at 0xa800, IRQ 225, 00:0f:ea:c3:3c:55.
<6>eth0 renamed to ethxx0
<6>eth1 renamed to eth0
<6>ethxx0 renamed to eth1
Kind Regards
Rudi Ahlers
CEO, SoftDux
Web: http://www.SoftDux.com
Forum: http://Forum.SoftDux.com
Join SA WebHostingTalk today, on http://www.WebHostingTalk.co.za
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
