Hi mosaddek,
[QUOTE=mosaddek;29854]hi jmozdzen,
Thanks for response. I agree with you and I am trying to share the technical info. But one thing is really not working as you mentioned and expected - configuration will work after boot also. No its not working !
It is only working as temporary [setting IP from CLI] and not working after boot. I am not sure of the reason but also found interface related error messages in dmesg. now after ifstatus I find all these showing down [below]! [/QUOTE]
I see that there are a few problems that need to be addressed, see my comments below:
Just for reference, here’s the default content of /etc/sysconfig/network/ifcfg-lo:
[FONT=monospace][COLOR=#000000]# Loopback (lo) configuration [/COLOR]
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
BROADCAST=127.255.255.255
IPADDR_2=127.0.0.2/8
STARTMODE=auto
USERCONTROL=no
FIREWALL=no[/FONT][FONT=monospace]
“ifup lo” then should be able to start the interface, and it should come up during boot as well. If you don’t see according messages in /var/log/boot.msg (look for “[/FONT]Setting up loopback interface[FONT=monospace]”), then check if the boot.localnet service might have been disabled (“chkconfig boot.localnet” - this should report “on”).
[/FONT]
[QUOTE=mosaddek;29854]I see message in dmesg though hostfile and lo cfg file looks ok.
ls -l /etc/sysconfig/network/ifcfg-*
-rw-r–r-- 1 root root /etc/sysconfig/network/ifcfg-bond0
-rw-r–r-- 1 root root /etc/sysconfig/network/ifcfg-bond5
-rw-r–r-- 1 root root /etc/sysconfig/network/ifcfg-eth14
-rw------- 1 root root /etc/sysconfig/network/ifcfg-lo[/QUOTE]
This doesn’t look like the actual output - I’m missing time stamps and especially size info
somehost:~ # ls -l /etc/sysconfig/network/ifcfg-lo
-rw------- 1 root root 172 Jul 17 13:30 /etc/sysconfig/network/ifcfg-lo
somehost:~ #
… but what’s more important, I would have expected to see two more files, for eth4 and eth6 (the bonding slaves). These may have content similar to
[FONT=monospace][COLOR=#000000]BOOTPROTO='none' [/COLOR]
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='Ethernet controller'
NETMASK=''
NETWORK=''
PREFIXLEN='32'
REMOTE_IPADDR=''
STARTMODE='hotplug'
USERCONTROL='no'[/FONT]
Your bond0 configuration file looks good to me. Interestingly, it carries no IP address - are you using it as the uplink for a linux bridge?
QUOTE=mosaddek;29854the new thing I see one of interface only shows up broadcast but NOT ‘running’. Where to check? as I see lspci shows all Ethernet list and no other specific error in dmesg
eth7 Link encap:Ethernet HWaddr XX
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1 → ‘ifconfig eth7 up’ command does NOT help to bring up
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)[/CODE][/QUOTE]
Does “ethtool eth7” report that a link was detected? It could be a cabling problem or the switch port, the latter i.e. might be admin-down.
QUOTE=mosaddek;29854 another interesting msg after system boot
syslog-ng[7406]: syslog-ng starting up → not sure of syslog-ng location
firmware.sh[7650]: Cannot find firmware file ‘intel-ucode/06-2d-07’ -->may be as you mentioned wouldn’t mind these too much, the system will try to bring up the network interfaces, once detected[/QUOTE]
https://www.suse.com/support/kb/doc.php?id=7010705 Probably upgrading the microcode package would already help.
Regards,
Jens
That would use the same mechanisms as during boot, so if that works, it should work at boot time, too.