Centos 7.0.1406 does not see FlexFabric NIC's during install

[msteele]

Hello,

We have an BladeSystem c7000 Enclosure G3 populated with Gen8 and Gen9 ProLiant BL460c blades. Each blade has HP FlexFabric 10Gb 2-Port 534FLB Adapter installed and we setup 8 NICs on each server. One of my blades that I am trying to add to my oVirt installation does not see all eight NIC's during the CentOS 7.0.1406 installation.  I have recently built three other blades, all the same configuration and ROM versions without issue.

The HP OA sees them fine, and the server profile has them added - however when I go to the networking tab of the CentOS installation, only ETH0 and ETH1 are showing.

Are there any settings in the BIOS of the blade that could prevent it from seeing the NIC's during OS installation? Any where else I should be looking to resolve this?

I have asked the company that I purchased the blade / adapter from to RMA the adapter first to see if it may be faulty.

System Info:

Blade Part No: 735151-B21
Blade ROM version: I31 06/01/2015
Virtual Connect for the blade reporting 'Configured for Virtual Connect'

Thank you for your assistance.

Mark Steele

[frenchy94]

Do you use VCM or Oneview to configure nic ?



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[msteele]

I'm not sure my replies are posting - I used VCM to configure the nics

[frenchy94]

And you configure 8 nic under VCM ?



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[msteele]

Yes,

The server profile for this blade has all the NIC's configured and it is exactly the same as the other 8 blades that are configured. This ONE blade is not seeing the NIC's during OS installation (the OA and VCM both see all the NIC's for this blade). That is why I am wondering if there is a BIOS setting that might be hindering the module from being seen at the OS level.

I can send screen shots if that is permitted somehow.

Mark

[frenchy94]

Does have same firmware and drivers versions ? (working no working ?)



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[msteele]

That is correct - all the blades have the same ROM / firmware versions and ILO versions

[frenchy94]

I' would say firmware/drivers versions for NIC nor blade itself



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[msteele]

That was my thought however the blades and nic all have the same firwmare  - this is the only blade that will not recognize the nics and only on OS installation - not in the OA.

Is there a firmware setting that precludes NIC's from being 'seen' on the blade?

[frenchy94]

Sure Firmware and drivers must match to display nic all os level



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[msteele]

Yep - I'm positive they all match.

[frenchy94]

Try swift boot device between blade to see if issue follow Balde or OS
please



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[Jimmy Vance]

If I recall there is a setting in the ROM whre the blade itself can override some OA / VC type settings.   I'd suggest using maintenance SW6 to reset the ROM to default

[msteele]

Thank you for the suggestion - I don't know what swift boot refers to. I also don't have any other blades that are not in production at this time.

I built two blades in the past 48 hours that match the same firmware / ROM - this is only this blade that is having the issue.

I could try moving it to another slot in the chassis to see if that makes a difference.

Are there any know BIOS settings that would cause a NIC to not be recognized by the OS during installation?

[msteele]

Thank you - is that accessed via the ILO web interface or via the BIOS / F9, etc.?

[frenchy94]

You see Nic0 and Nic1 so you see physical nic



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

[msteele]

That is correct - when I start to install the OS I can see eth0 and eth1  - but not the remaining nics.

[frenchy94]

Remaining nic are created by firmware/Virtual connect , that split 2
physical nic to up 8 virtual nic so

Problem can be

Nic

Firmware nic

Driver nic

Vc

That's all



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus