Second Profile on NIC becomes INACTIVE at Startup. CentOS 5.5

Hi,
EXTREMELY novice Linux user. I have a CentOS 5.5 server that has two profiles attached to one NIC. Using Network Configuration tab, on server start device eth0 shows active. Device eth0:0 shows inactive and I have to click activate to start. Same NIC, two different address ranges. I have set Eth0:0 to "Activate device when parent device starts" and "Allow all users to enable" but this hasn't fixed the issue.
This is a VMWare VM if it makes a difference.

Also, can you provide me the correct syntax to set Eth0:0 to active using just the command line?

Thanks much.
adamant40Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

farzanjCommented:
To activate

ifup eth0:0


You have to show me the interface files

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


All interafaces should start at the run time with the command
service network restart

After this do
ip a

to see if all the interfaces came up.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
farzanjCommented:
Another important thing is that eth0:0 can only use static and should use one address in this file.  Range should not be used in a file with this name.  

To start at the boot time, the file should contain

ONBOOT=yes
0
adamant40Author Commented:
Dang, just left office. I will post the exact config info first thing in the AM. One thing I notice, these files are named for the alias instead of interface itself.
0
adamant40Author Commented:
Network person changed the config so the second NIC address is not necessary. Also no way to verify above solution so accepting. THanks.
0
adamant40Author Commented:
Config changed so I am unable to test solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.