Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-14 Thread J Potter
I found under CentOS 4 a few years ago that the OS would only bring up virtual interfaces starting with 0:0 and increasing sequentially -- if there was a gap, it would stop at that gap point. I.e.: Good: eth0, eth0:0, eth0:1, eth0:2... Bad: eth0, eth0:0, eth0:2 (system

[CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Berend Dekens
With one problem down I still have another remaining. Since the installation of our primairy webserver we have had a problem with the network aliasses. Our server has 8 IP adresses so we used the tool provided in the GUI to specify (and name - for our own convinience) eth0 aliasses with the

Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Ralph Angenendt
Berend Dekens wrote: However, after a reboot, all aliasses are disabled: they are present in the configuration but they are not activated. I feared I did something wrong so I removed all addresses, tried to find more clues in the docs and now I'm back where I started. Go into

Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Berend Dekens
None of the files have ONBOOT but they do have ONPARENT... I'll add the ONBOOT param and reboot the server tonight to see if it worked. Cheers, Berend Ralph Angenendt wrote: Berend Dekens wrote: However, after a reboot, all aliasses are disabled: they are present in the configuration but

Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Kai Schaetzl
Ralph Angenendt wrote on Thu, 13 Nov 2008 12:16:22 +0100: If they have ONBOOT=YES change that to ONPARENT=YES. If they have neither, add ONPARENT=YES. FYI: I've been creating NIC aliases with ONBOOT=yes for quite some time without a problem as I wasn't aware of the ONPARENT directive. I

Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Berend Dekens
Update: Didn't help - but this time I was connected to a console so I could see the bootup and I get this: SIOCSIFFLAGS: Cannot assign requested address Strange thing is that I have multiple aliasses and only 3 errors... I tried Google with this error and I see lots of people with Ubuntu

Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Kai Schaetzl
or, at the same time while you are waiting for more replies, you could try starting up with only the first alias and if that succeeds try the next one and so on ... If you get less errors than you have aliases it's likely that some of the files have simply wrong values. Kai -- Kai Schätzl,

Re: [CentOS] Virtual NICs (aliases like eth0:1) won't come up after reboot

2008-11-13 Thread Berend Dekens
Kai Schaetzl schreef: or, at the same time while you are waiting for more replies, you could try starting up with only the first alias and if that succeeds try the next one and so on ... I was doing exactly that. And I was trying to figure out how the networking scripts work and what they do -