SCIENTIFIC-LINUX-USERS Archives

August 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Edison, Arul (GE Healthcare)" <[log in to unmask]>
Reply To:
Edison, Arul (GE Healthcare)
Date:
Fri, 16 Aug 2013 13:56:48 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (1 lines)
Thanks. As suggested, I have disabled the NetworkManager and the issue that I faced is solved now



-----Original Message-----

From: [log in to unmask] [mailto:[log in to unmask]] 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:fdbc0000-fdbe0000

>

> 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:fddc0000-fdde0000

>

> 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:fdbc0000-fdbe0000

>

> 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:fddc0000-fdde0000

>

> 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 NetworkManager[1612]: <info> Activation (eth0) 

> Stage 1 of 5 (Device Prepare) complete.

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 2 of 5 (Device Configure) starting...

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> (eth0): device 

> state

> change: 4 -> 5 (reason 0)

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 2 of 5 (Device Configure) successful.

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 3 of 5 (IP Configure Start) scheduled.

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 2 of 5 (Device Configure) complete.

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 3 of 5 (IP Configure Start) started...

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> (eth0): device 

> state

> change: 5 -> 7 (reason 0)

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 4 of 5 (IP4 Configure Get) scheduled...

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 3 of 5 (IP Configure Start) complete.

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 4 of 5 (IP4 Configure Get) started...

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 5 of 5 (IP Configure Commit) scheduled...

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 4 of 5 (IP4 Configure Get) complete.

>

> Aug 17 11:54:57 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 5 of 5 (IP Configure Commit) started...

>

> Aug 17 11:54:57 magic avahi-daemon[1624]: Withdrawing address record 

> for

> 192.168.2.1 on eth0.

>

> Aug 17 11:54:57 magic avahi-daemon[1624]: Leaving mDNS multicast group 

> on interface eth0.IPv4 with address 192.168.2.1.

>

> Aug 17 11:54:57 magic avahi-daemon[1624]: Interface eth0.IPv4 no 

> longer relevant for mDNS.

>

> Aug 17 11:54:57 magic avahi-daemon[1624]: Joining mDNS multicast group 

> on interface eth0.IPv4 with address 192.168.1.20.

>

> Aug 17 11:54:57 magic avahi-daemon[1624]: New relevant interface

> eth0.IPv4 for mDNS.

>

> Aug 17 11:54:57 magic avahi-daemon[1624]: Registering new address 

> record for 192.168.1.20 on eth0.IPv4.

>

> Aug 17 11:54:57 magic kernel: e1000e: eth0 NIC Link is Down

>

> Aug 17 11:54:58 magic NetworkManager[1612]: <info> (eth0): device 

> state

> change: 7 -> 8 (reason 0)

>

> Aug 17 11:54:58 magic NetworkManager[1612]: <info> Activation (eth0) 

> successful, device activated.

>

> Aug 17 11:54:58 magic NetworkManager[1612]: <info> Activation (eth0) 

> Stage 5 of 5 (IP Configure Commit) complete.

>

> Aug 17 11:54:58 magic NetworkManager[1612]: <info> (eth0): carrier now 

> OFF (device state 8, deferring action for 4 seconds)

>

> Aug 17 11:54:58 magic avahi-daemon[1624]: Registering new address 

> record for fe80::20b:abff:fe38:29a6 on eth0.*.

>

> Aug 17 11:55:00 magic NetworkManager[1612]: <info> (eth0): carrier now 

> ON (device state 8)

>

> Aug 17 11:55:00 magic kernel: e1000e: eth0 NIC Link is Up 1000 Mbps 

> Full Duplex, Flow Control: None

>

> Aug 17 11:57:39 magic kernel: device eth0 left promiscuous mode

>

> Thanks,

>

> Arul

>



Ditch NetworkManager.  It causes more headaches than it is worth.



-Mark





--

Mr. Mark V. Stodola

Senior Control Systems Engineer



National Electrostatics Corp.

P.O. Box 620310

Middleton, WI 53562-0310 USA

Phone: (608) 831-7600

Fax: (608) 831-9591


ATOM RSS1 RSS2