RE: network port issue with Scientific Linux 6.3
Thanks. As suggested, I have disabled the NetworkManager and the issue that I faced is solved now -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Mark Stodola Sent: Wednesday, August 14, 2013 6:54 PM To: Scientific Linux Subject: Re: network port issue with Scientific Linux 6.3 On 08/14/2013 08:16 AM, Edison, Arul (GE Healthcare) wrote: Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:- *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:- * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 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) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4447027 (4.2 MiB) TX bytes:4447027 (4.2 MiB) /var/log/message file is as below:- ** Aug 17 11:54:42 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:46 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Aug 17 11:54:57 magic kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): carrier now ON (device state 2) Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): device state change: 2 - 3 (reason 40) Aug 17 11:54:57 magic NetworkManager[1612]: info
Re: network port issue with Scientific Linux 6.3
Ditch NetworkManager with a chainsaw.. In your /etc/sysconfig/network file, set NM_CONTROLLED=no and reboot, because NetworkManager is *bad* for stable configurations. You should have, ideally, settings in /etc/udev.d that tie MAC addresses of your hardware to specific network devices, and matching HWADDR address in /etc/sysconfig/network-scripts/ifcfg-eth*. Unfortunately, a lot of network configuration tools set one, and not the other, or don't bother to set it because the authors are simply unschoooled in the subtleties. NetworkManager is schooled in the subtleties. It simply gets many of them completely wrong. (Investigate KVM bridging and pair bonding for examples of NetworkManager's shortcomings.)
network port issue with Scientific Linux 6.3
Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:- *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:- * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 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) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4447027 (4.2 MiB) TX bytes:4447027 (4.2 MiB) /var/log/message file is as below:- ** Aug 17 11:54:42 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:46 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Aug 17 11:54:57 magic kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): carrier now ON (device state 2) Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): device state change: 2 - 3 (reason 40) Aug 17 11:54:57 magic NetworkManager[1612]: info Activation (eth0) starting connection 'eth1' Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0):
Re: network port issue with Scientific Linux 6.3
On 08/14/2013 08:16 AM, Edison, Arul (GE Healthcare) wrote: Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:- *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:- * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 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) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4447027 (4.2 MiB) TX bytes:4447027 (4.2 MiB) /var/log/message file is as below:- ** Aug 17 11:54:42 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:46 magic kernel: ttyS2: LSR safety check engaged! Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Aug 17 11:54:57 magic kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): carrier now ON (device state 2) Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): device state change: 2 - 3 (reason 40) Aug 17 11:54:57 magic NetworkManager[1612]: info Activation (eth0) starting connection 'eth1' Aug 17 11:54:57 magic NetworkManager[1612]: info (eth0): device state change: 3 - 4 (reason 0) Aug 17 11:54:57 magic NetworkManager[1612]: info Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Aug 17 11:54:57 magic NetworkManager[1612]: info Activation (eth0) Stage 1 of 5 (Device Prepare) started... Aug 17 11:54:57 magic NetworkManager[1612]: info Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Aug 17 11:54:57 magic
Re: network port issue with Scientific Linux 6.3
Have you had a chance to look over the udev logical devices for the adapters? Since both adapters are set to two different networks, have you check the route to communicate? On Wed, Aug 14, 2013 at 9:16 AM, Edison, Arul (GE Healthcare) aruljeyananth.jamesedi...@ge.com wrote: Hi , I am using the repacked version of Scientific Linux 6.3 My PC has a mother board , which has 2 Ethernet port eth0 is connected to a device IP configured for eth0 is 192.168.2.1 eth1 is connected to a hub. This is intern connected with another PC. IP configured for eth0 is 192.168.1.20 The issue here is eth0 IP Address is now got changed to the IP address of eth1 when the Device connected with eth0 become powered on . With this, eth0 eth1 has same IP address. Because of this the application running on Scientific Linux 6.3 PC is not able to communicate with the Device connected with eth0. I have enclosed the /var/log/message file below for the reference Please suggest me what is the configuration to be done for the same? ** ** ** ** /etc/sysconfig/network-scripts/ifcfg-eth0 file from system is as below:-** ** *** DEVICE=eth0 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.2.1 NETMASK=255.255.255.0 /etc/sysconfig/network-scripts/ ifcfg-eth1 file from system is as below:-* *** * DEVICE=eth1 BOOTPROTO=none #IPADDR=192.168.1.90 IPADDR=192.168.1.20 NETMASK=255.255.255.0 ** ** When the Scientific Linux 6.3 Pc is booted , the network configuration of the system is as below:- eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0** ** UP BROADCAST MULTICAST MTU:1500 Metric:1 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) Interrupt:16 Memory:fdbc-fdbe ** ** eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0* *** inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:381 errors:0 dropped:0 overruns:0 frame:0 TX packets:267 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:26234 (25.6 KiB) TX bytes:29696 (29.0 KiB) Interrupt:17 Memory:fddc-fdde ** ** loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 b) TX bytes:240 (240.0 b) ** ** When the Device that is connected to the eth0 is powered on and booted, the network configuration of the system changed as below:- * ** ** ** ** eth0 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A6 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0* *** inet6 addr: fe80::20b:abff:fe38:29a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:240 (240.0 b) TX bytes:9814 (9.5 KiB) Interrupt:16 Memory:fdbc-fdbe ** ** eth1 Link encap:Ethernet HWaddr 00:0B:AB:38:29:A7 inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0* *** inet6 addr: fe80::20b:abff:fe38:29a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6077 errors:0 dropped:0 overruns:0 frame:0 TX packets:4412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:427716 (417.6 KiB) TX bytes:287127 (280.3 KiB) Interrupt:17 Memory:fddc-fdde ** ** loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42683 errors:0 dropped:0 overruns:0 frame:0 TX packets:42683 errors:0 dropped:0 overruns:0 carrier:0
