Confused interface setup

I have a network configuration on one server that currently works, but neither the configuration files nor ifconfig seem to agree. Confused interface setup

The server (CentOS 4) once used the primary IP 213.228.231.35 before a transition to a private VLAN and the IP block 83.233.102.192/27. The addresses .198 and .199 are currently up and pingable, and the old IP is unpingable. All is working as expected.

But then I take a look at ifconfig:

eth0 Link encap:Ethernet HWaddr 00:30:48:82:6C:98
inet6 addr: fe80::230:48ff:fe82:6c98/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:359497126 errors:0 dropped:0 overruns:0 frame:0
TX packets:262936080 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1551028372 (1.4 GiB) TX bytes:2665412715 (2.4 GiB)
Base address:0xb000 Memory:fb000000-fb020000

eth0:2 Link encap:Ethernet HWaddr 00:30:48:82:6C:98
inet addr:83.223.102.199 Bcast:83.223.102.255 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Base address:0xb000 Memory:fb000000-fb020000

eth1 Link encap:Ethernet HWaddr 00:30:48:82:6C:99
inet addr:83.223.102.198 Bcast:83.223.102.223 Mask:255.255.255.224
inet6 addr: fe80::230:48ff:fe82:6c99/64 Scope:Link
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)
Base address:0xd100 Memory:f9000000-f9020000
To my knowledge, eth1 has no link and should be inactive. Why does it claim to own the primary IP .198 and yet shows no data transfer? Stranger still, where has eth0:1 (which should own .198) gone?

Then take a look at the network scripts. To my knowledge, these haven't been changed since the last reboot.

[root@server1 ~]# ls -l /etc/sysconfig/network-scripts/ifcfg-eth0
-rw-r--r-- 3 root root 583 Aug 8 13:38 /etc/sysconfig/network-scripts/ifcfg-eth0
[root@server1 ~]# uptime
22:26:16 up 39 days, 17:56, 6 users, load average: 0.00, 0.02, 0.00

/etc/sysconfig/network-scripts/ifcfg-eth0:

DEVICE=eth0
BOOTPROTO=none
BROADCAST=213.228.231.255
HWADDR=00:30:48:82:6C:98
IPADDR=213.228.231.35
NETMASK=255.255.255.0
NETWORK=213.228.231.0
ONBOOT=yes
TYPE=Ethernet
GATEWAY=213.228.231.1

DEVICE=eth0:1
BOOTPROTO=none
BROADCAST=83.223.102.255
HWADDR=00:30:48:82:6C:98
IPADDR=83.223.102.198
NETMASK=255.255.255.224
NETWORK=83.223.102.192
ONBOOT=no
TYPE=Ethernet
GATEWAY=83.223.102.193

DEVICE=eth0:2
BOOTPROTO=none
BROADCAST=83.223.102.255
HWADDR=00:30:48:82:6C:98
IPADDR=83.223.102.199
NETMASK=255.255.255.224
NETWORK=83.223.102.192
ONBOOT=no
TYPE=Ethernet
GATEWAY=83.223.102.193
So, perhaps having the old IP as the interface's primary address confuses ifconfig? Fair enough. But why do both of the other interfaces have ONBOOT set to no, and yet are up and active? And the old IP has ONBOOT set to yes, and is down? Confused interface setup

ifcfg-eth1, for the curious:

DEVICE=eth1
HWADDR=00:30:48:82:6C:99
ONBOOT=no
TYPE=Ethernet
IPADDR=83.223.102.198
NETMASK=255.255.255.224
NETWORK=83.223.102.192
GATEWAY=83.223.102.193
So, erm. What's the best way out of this mess without causing downtime? Confused interface setup

 

 

 

 

Top