CentOS does not recognize the NIC cards (Server Edition Deployment) 2

[Guilherme1000]

Hi everybody,

I know this is a Linux or hardware issue but...

****** I don't have experience using linux systems******

I'm deploying a Server Edition with a HP Proliant ML110 Gen9 server. Both ethernet cards are recognized by the BIOS but the CentOS installed system does not displays it when powered on.

When I use the command ifconfig eth0, it says something like device not present. The Server Edition is already installed but is like the CentOS does not recognize the NIC cards.

Steps made
- checked the bios and enabled NICs
- download drivers .rpm from HP website and execute rpm -i (packages)
- installed the same server edition on virtual environment on my laptop and worked fine.
- installed windows server 2012 and installed drivers, fine.
- and many other little things.


Has anyone had this issue before?

 

[intrigrant]

Honestly, I am always stumped to hear about people installing stuff they know nothing about...
Better find a linux forum and proceed there or contact Avaya if you have a IPOSS contract on this (cost you deer i'm afraid)

 

[Guilherme1000]

Honestly, I think "don't have experience" is quite different from "know NOTHING about Linux", despite the fact that I have done the attempts mentioned on the post, I was sincerely waiting for someone who had a server edition installed without NIC cards been recognized by the system as I had.

Honestly, I think people who doesn't know how to help at all, should be quiet and look for another thread.

 

[kyle555]

Server Edition from the bootable ISO is not compatible with that hardware. Avaya's Server Edition CDs are tailored to the exact hardware Avaya supports.

Are you installing VMWare deploy the virtual appliance?

 

[intrigrant]

..not helpfull... top of the MVP's
read this
or try this:
Go into /etc/udev/rules.d and delete the 70-persistent-net.rules file.
Reboot the server.
Now you need to edit /etc/sysconfig/network-scripts/ifcfg-eth0 and manually update to the MAC of your new NIC card.
If there are two or more cards then they are named eth0, eth1 etc and edit the subsequent /etc/sysconfig/network-scripts/ifcfg-ethx with the correct MAC address

 

[tlpeter]

The ml110 is nog supporters so don't go that route.

BAZINGA!

I'm not insane, my mother had me tested!

 

[intrigrant]

read my first reply... but there may always be a change it will work supported or not

 

[Guilherme1000]

Kyle555, I'm installing on a physical server.

Intrigant, I've tried to configure manually the NICs configs using that method but at the first steps, it says the device is not present. I have also upgraded the BIOS and NICs firmware and drivers with success but it keeps saying it's not present.

Tlpeter, I'm seriously thinking of changing the whole server, unfortunly

 

[hairlessupportmonkey]

why not dump VMware on it first and use the VMWare OVA?

https://www.youtube.com/watch?v=9kd-iRMI_hE

ACSS - SME
General Geek

 

[intrigrant]

They are not visible because it is a hardened version CentOS, you either must dig deeper or use the OVA version on a virtualisation server.

 

[janni78]

This has already been said but it doesn't seem to sink in.
You shouldn't install Server Edition ISO on you own server, this is intended for Avaya provided servers. Although you could buy the same server Avaya uses from HP/Dell.

Even if you can get it to work adding drivers in CentOs the risk is that everything stops working again when you upgrade the system and it's certainly not supported by Avaya.

If you wanna use a custom server install VMWare on it and then install the OVA for Server Edition. This will save you and everybody here a lot of time and headaches.

On that note there is a license in CI that will allow you to install on custom hardware, but for reasons you're experiencing now that's not released yet.

"Trying is the first step to failure..." - Homer

 

[hairlessupportmonkey]

Also, download the custom HP VMWare install. it has all the correct drivers installed.

But, out of the Box your server is certified to run esxi 6

http://h17007.www1.hpe.com/us/en/enterprise/servers/supportmatrix/vmware.aspx#.VyIr9j9w3Wo

ACSS - SME
General Geek

 

[derfloh]

But IPO is not - officially - supported in ESXi6.0 ;-) So if you start with ESXi from scratch use 5.5

 

[tlpeter]

That is where Avaya is going down!
They do not support esxi 6.0 yet and no Windows 10 yet officially.
Both are around for a while already.


BAZINGA!

I'm not insane, my mother had me tested!

 

[Guilherme1000]

I chose to virtualize it, everthing is working fine. Thank you all for the suggestions!