Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

no compatible network adapters found - UCSC C220 M3S

Hi all

I am a little new at the Cisco servers so here is my question.

I have been trying to install esxi on our new C220 M3S server.

But after the installation I get to the esxi screen it says "No compatible network adapters found. Please consult ...... "

Any sugestions to what could be wrong ?

I have tried to install different versions of the esxi Cisco custom image (5.5 5.1 5.0) with the same result.

 

/Thomas

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Hi Thomas,It is possible that

Hi Thomas,

It is possible that the optionROM for the onboard adapter is not enable.  Try to enable it in the BIOS, you can do it via the CIMC (see cimc_enable_optionrom attached ). You also want to verify this option gets enable in the bios.  You can get into the bios by pressing f2 during boot up (see BIOS_Option_ROM attached)

 

  Also if these are disable you might need to run through the installation again.   See the Cisco custom image link below for ESXi 5.5.  I noticed that you are using ESXi 5.5 Update 1, but this is still not supported.

 

Download CISCO Custom Image for ESXi 5.5.0 GA

Download CISCO Custom Image for ESXi 5.5.0 GA

https://my.vmware.com/web/vmware/details?productId=353&downloadGroup=OEM-ESXI55GA-CISCO

17 REPLIES
VIP Green

Hi ThomasI assume this is a

Hi Thomas

I assume this is a standalone Server ? what is the Hardware configuration ? which Network adaptor ? VIC-1225 ?

ESXi has a the proper enic/fnic Driver bundled.

 

Hi wdeyYes you assume correct

Hi wdey

Yes you assume correct. This is a standalone server.

Hardware wise this is a C220 M3S with two E5-2620-V2. 4 x 8 GB RAM. 4 x 300 GB Disk set up to Raid-5 on the 2008M-8i Mezzanine Card. And finally this server was shipped with the Flexible Flash "module" (I cant even remember we ordered that, but it was in there ... so :-) )

No extra NICs where added, i just have the two onboard Gigabit ports (Intel I350 Ethernet controller as far as i know ?).

I have installed the ESXi on the Flash module.

In my opinion this ought to be pretty straight forward, and I just cant see what Im doing wrong.

The only thing i have been "playing" around with was the CIMC configuration.

The default configuration was set to Shared LOM EXT. I changed that to "dedicated" to use the specific mgmt port for CIMC. (I have also tried to change it back just in case.)

Furthermore I have updated "everything" : BIOS, CIMC,  2008M-8i Mezzanine Card bios and so on. Nothing has helped.

VIP Green

Depending on your CIMC

Depending on your CIMC settings, the CIMC can be accessed through the 1-GbE dedicated management port, the 1-GbE LOM ports, or a Cisco virtual interface card (VIC).

So I assume, that you have 2 network connections: one for mgt (CIMC), and another one  (LOM) for data ? And it seems, that ESXi doesn't see the latter one, because the proper driver is most likely missing ?

I agree that this seems to be

I agree that this seems to be the case. But should the driver for The LOM not be included in the Cisco Custom image ?
VIP Green

within ucs-cxxx-drivers.1.5

within ucs-cxxx-drivers.1.5.4e.iso you will find all drivers for ESXi (see attachment), including the Intel ones.

Is "NIC Redundancy" set to none ?

I will try to download the

I will try to download the driver iso and add the I350 driver to the standard esxi iso using the "ESXi Customizer" software.

The "NIC Redundancy" in CIMC is set to none.

Its the only option when selecting "dedicated".

But what I still dont get, is why this driver is not included in the Custom image. When the "Release Notes for the VMware Installable Cisco Custom ISO Image" seems to indicate that it shoud be.

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_26617.html 

 

VIP Green

Hi ThomasI was checking

Hi Thomas

I was checking with

http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

see attachment

and get this result for ESXi 5.5

Manufacturer     = Intel

Adapter Driver   = 5.0.5.1
Adapter Firmware = 1.6-3
Boot Code / BIOS = v1.5.43

Note 8: Boot from SAN requires Cisco Customized ISO image available for download at www.vmware.com.

The C220-M3(SFF) server requires release 1.5.(4)3 [use HUU 1.5.4-3].

The majority of customers are installing a additional CNA, most likely VIC-1225

In your case, it will be Ethernet 1G, no CNA, no FC;

of course I understand your situation.

I would open a TAC case

 

I wonder if the OP was trying

I wonder if the OP was trying to boot with UEFI?

I recently ran into this exact same issue with the C220M3 - if I attempt to install in UEFI mode, ESXi starts to load but eventually fails with the same error about a network card not being found.

If I go back to legacy BIOS and attempt with the exact same installation iso (the Cisco 5.5U1 ISO), it works 100%.

This is with the 2.0 firmware - I didn't try on any earlier versions.

I'm not sure if this is a bug or if I just need to flash the i350s with the UEFI boot image from Intel.  If the latter, I am not sure if this will be supported by Cisco or not...

The Intel i350 onboard LOM

The Intel i350 onboard LOM definitely is included in the customised image, and it is included in the non customised generic VMware image also.  I know because I have installed VMware with this controller both in my C220M as well as a whitebox with an i350 card.  It's not a cisco specific device, this Intel controller is widely used outside of UCS also.


It sounds like either (a) your server is faulty or (b) the onboard NICs not enabled in the BIOS somewhere.

 

Cisco Employee

Hi Thomas,It is possible that

Hi Thomas,

It is possible that the optionROM for the onboard adapter is not enable.  Try to enable it in the BIOS, you can do it via the CIMC (see cimc_enable_optionrom attached ). You also want to verify this option gets enable in the bios.  You can get into the bios by pressing f2 during boot up (see BIOS_Option_ROM attached)

 

  Also if these are disable you might need to run through the installation again.   See the Cisco custom image link below for ESXi 5.5.  I noticed that you are using ESXi 5.5 Update 1, but this is still not supported.

 

Download CISCO Custom Image for ESXi 5.5.0 GA

Download CISCO Custom Image for ESXi 5.5.0 GA

https://my.vmware.com/web/vmware/details?productId=353&downloadGroup=OEM-ESXI55GA-CISCO

There's a VMware Cisco Custom

There's a VMware Cisco Custom Image for 5.5.0 Update 1 as well:

https://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI55U1-CISCO&productId=353

Just to clarify - are you saying this is not supported?

 

Cisco Employee

Hi Reuben, With the latest

Hi Reuben,

 

With the latest firmware version available 1.5(4e) for this c-series server, ESXi 5.5 update 1 is still not in part of the compatibility matrix this will become supported after 1.5(5). See below documents

Cisco UCS compatibility Matrix

http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

 

Cisco UCS C240 M3 Rack Server Software

http://software.cisco.com/download/release.html?mdfid=284296254&flowid=31743&softwareid=283850974&release=1.5%284e%29&relind=AVAILABLE&rellifecycle=&reltype=latest

 

 

The option Roms for the

The option Roms for the onboard NICs where already enabled, and I veryfied with the BIOS.

But your screenshots got me thinking about the "PCIe Slotx Rom".

In my setup they where set to disabled. So just for fun I enabled them.

This seems to have done the trick ?!?!?!

A new installation of ESXi with the Cisco Custom Image worked.

Thank you all for your assistance.

New Member

Hi Manuel/ThomasI had same

Hi Manuel/Thomas

I had same issue, and is now RESOLVED using similar method. It took me a week to get through this with much reading of Release Notes, and Conpatibilty Guides etc to no avail.

 

Hardware:

Cisco UCS C240 M3S SFF

BIOS: 1.5(7c)

VMware: Cisco Custom Image for ESXi 5.5.0 Update 2 (Build 2068190)

 

I could successfully install ESXi onto the server (internal SD card), but whenever it booted up, it would say No network adapters found, even though the BIOS could see them fine.

 

ANSWER:

Two BIOS settings that needed to be changed:

1) Set Boot Mode to Legacy in BIOS web GUI (See 01_BIOS_Setting.jpg)

2) Needed to switch all the LOMs to Legacy Mode (See 02_BIOS_Setting.jpg)

Restart server, and all ok (See 03_Working_Config.jpg)

 

Hope this helps somebody out there and saves a week's worth of troubleshooting

 

Cheers

Darren

 

 

It's a shame you didn't see

It's a shame you didn't see this discussion first:

https://supportforums.cisco.com/discussion/12261621/ucs-c220m3-and-uefi-boot-failure-bug

and then:

https://tools.cisco.com/bugsearch/bug/CSCui85699

This bug is fixed in the latest HUU/firmware bundle 2.0(3)d for the C220 and others that came out in September.

If you were to load that firmware you wouldn't have had to revert to legacy/non-UEFI bios.

New Member

Thanks Reuben.Weirdly, I

Thanks Reuben.

Weirdly, I actually rolled back my BIOS to 2.0(3)d in the end anyway, because the newer 1.5(7)c broke my remote KVM connection (Java did not work with the newer BIOS, but that's probably in another thread altogether). I could physically get to the server but NICs were still not showing in ESXi.

But even when I downgraded to 2.0(3)d in order get KVM working, the NICs did not work in ESXi either unfortunately.

I also tried 2.0(1)a, with no luck, but hadn't tried going all the way back to 1.4.7

Can't believe that after the amount of searching I did, I had not come across either of those two links (maybe because I was looking specifically for C240 results, and not C220)

 

Thanks for the reply

Cheers

Darren

Hi DarrenDid you update all

Hi Darren

Did you update all images on the board to the versions in that HUU?  I suspect that the rather large change in the i350 ROM is what may have actually fixed the problem.

For me the change was black and white, as in worked straight away with that version, but none of the previous versions.  Maybe there was something else different about your setup..

Reuben

4851
Views
5
Helpful
17
Replies
CreatePlease login to create content