Quote:
Originally Posted by berndbausch
What do you mean by "eth0 and eth2 are same"? Same MAC address?
Post the ifcfg files here, and the output of ip a and ip r.
|
Strange thing is network interfaces become up but can't ping until we revert back to NM
eth0 and eth2 are same- means 70-persistent.rules is created with 4 entries and eth0 & eth2 share same settings like this
[root@eze-119 ~]# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:d7:fb:fe", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x10c9 (igb) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d8:d3:85:e5:ed:d3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:d7:fb:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x8086:0x10c9 (igb) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d8:d3:85:e5:ed:d2", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
I see igb and e1000e... does it means there are 2 drivers in action?
Here are the output of ip a, ip r and ifcfg-eth2 and ifcfg-eth3
[root@eze-119 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:26:55:d7:fb:fe brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:26:55:d7:fb:ff brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether d8:d3:85:e5:ed:d2 brd ff:ff:ff:ff:ff:ff
inet 119.82.251.230/24 brd 119.82.251.255 scope global eth2
inet6 fe80::dad3:85ff:fee5:edd2/64 scope link
valid_lft forever preferred_lft forever
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether d8:d3:85:e5:ed:d3 brd ff:ff:ff:ff:ff:ff
inet 23.1.1.191/24 brd 23.1.1.255 scope global eth3
inet6 fe80::dad3:85ff:fee5:edd3/64 scope link
valid_lft forever preferred_lft forever
[root@eze-119 ~]# ip r
119.82.251.0/24 dev eth2 proto kernel scope link src 119.82.251.230
23.1.1.0/24 dev eth3 proto kernel scope link src 23.1.1.191
169.254.0.0/16 dev eth2 scope link metric 1004
169.254.0.0/16 dev eth3 scope link metric 1005
default via 119.82.251.229 dev eth2 proto static
[root@eze-119 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
NAME="System eth0"
IPADDR=119.82.251.230
NETMASK=255.255.255.252
GATEWAY=119.82.251.229
PREFIX=24
IPV6INIT=no
USERCTL=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
DNS1=119.82.248.67
HWADDR=D8
3:85:E5:ED
2
LAST_CONNECT=1432011451
[root@eze-119 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth3
DEVICE=eth3
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
NAME="System eth1"
IPADDR=23.1.1.191
NETMASK=255.255.255.0
PREFIX=24
HWADDR=d8:d3:85:e5:ed:d3
IPV6INIT=no
USERCTL=no
GATEWAY=23.1.1.3
This is current working configs with NM. NetworkManager is really annoying...
Thanks.
.... some newbie installed server in gui and left it in that way... even lv_root has 55GB only and lv_home has 250 ... you can imagine how server was setup. When I got ssh access, it was running that way and I couldn't have done much.
