cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1508
Views
0
Helpful
2
Replies

NO DRIVERS FOR UCS BLADE B200 M4 ( missing ethernet controller) with W2012R2.

FedeSaraullo
Level 1
Level 1

We installed windows 2012 R2 64x image in a blade B200 M4 (2.2.7b). We installed all the drivers from Cisco web page, but only one driver CISCO VIC ETHERNET INTERFACE(20gbps) was found. The others Ethernet controller wasnt found in the .iso (ucs-bxxx-drivers-windows.2.2.7.iso). 

Can anybody help us with these drivers??

The part id is UCSB-MLOM-40G-03

Thanks 

1 Accepted Solution

Accepted Solutions

Kirk J
Cisco Employee
Cisco Employee

All the ethernet interfaces, that represent the vnics you created in your service profile, will use a single driver.  Make sure you have installed the intel chipset drivers from \ucs-bxxx-drivers-windows.2.2.7.iso\ChipSet\Intel\B200M4\W2K12R2\, and then confirm you have the the vic driver installed.  When the chipset and vic driver are installed, your ethernet interfaces should all just map as multiple network VIC adapters.

Also, make sure you haven't created dynamic vnics (which can show up like this in device manager) in your service profile, unless you are creating VM-Fex nics for your hyperV environment.  For VM-Fex/dynamic vnics, there is a specific process to create these, so the Windows hyperV host doesn't see these in device manager, and are only seen in hyperV guestVMs.

Thanks,

Kirk...

View solution in original post

2 Replies 2

Kirk J
Cisco Employee
Cisco Employee

All the ethernet interfaces, that represent the vnics you created in your service profile, will use a single driver.  Make sure you have installed the intel chipset drivers from \ucs-bxxx-drivers-windows.2.2.7.iso\ChipSet\Intel\B200M4\W2K12R2\, and then confirm you have the the vic driver installed.  When the chipset and vic driver are installed, your ethernet interfaces should all just map as multiple network VIC adapters.

Also, make sure you haven't created dynamic vnics (which can show up like this in device manager) in your service profile, unless you are creating VM-Fex nics for your hyperV environment.  For VM-Fex/dynamic vnics, there is a specific process to create these, so the Windows hyperV host doesn't see these in device manager, and are only seen in hyperV guestVMs.

Thanks,

Kirk...

Ok thanks for you help!!!

Regards,

Saraullo Federico

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card