Hi,

Thanks for your post.

You can use OME and 32 bit DUPs to update 64 bit drivers. DUP or Dell Update Package is a wrapper executable which can carry different types of payloads. In this case the 32 bit DUP carries the 64 bit driver as a payload and can update the 64 bit component. You will need WOW64 mode enabled on the 64 bit target so that the 32 bit DUP can execute. Typically that mode is enabled by default.

Regards

Abhijit

Thank you for the clarification.

Using OME, I scheduled the Broadcom Network card (BCM5722) driver update from 15.6.0.10 to 17.6.0.0/17.6.0.12. OME processed it successfully and the PET110 II server reported having processed the DUP successfully right on the scheduled time. So far so good.

I forced a server inventory and the server reported back the driver information. The Broadcom card stayed at 15.6.0.10. And system update reports the server non-compliant because the network driver is at 15.6.0.10 instead of 17.6.0.0.

I copied the DUP file on the server and executed it manually --> same result, i.e. 15.6.0.10 remains.

I tried the other format (regular unzip of installation files on the hard drive) and ran it manually --> same result, i.e. 15.6.0.10 remains.

Well ... what am I missing?

Thanks for the update.

32 bit Broadcome NIC driver update has an issue today where it doesn't run in WOW64 mode. We are working with the team to get a new update posted which will support this mode. In the meanwhile, you can run the native 64 bit update for this component on the target node outside of OME. That should get the driver updated.

Regards

Abhijit

Could you please direct me to where I can download the native 64-bit update?  The link from OME took me to a page with the 64-bit driver which didn't work, and also had the 32-bit driver, which didn't work.

Broadcom BCM5716C NetXtreme II GigE 7.6.2.0 -> 17.6.0.0

Broadcom NetXtreme I and NetXtreme II Driver Family 17.6.0 -> 17.6.0.0

Thanks.

Thanks for the update. To understand this correctly, you are saying you executed the update on the target node by directly running the EXE the update reported success but the driver version was not updated. Are you seeing the driver version in OME or are you seeing it directly on the target server. I would recommend opening a support ticket for this at 800-945-3355 so they can investigate furhter.

Regards

Abhijit

Hi,

I downloaded "Bcom_LAN_17.6.4.2_Windows_64_17.6.12.exe" from the Dell support website for PE T110 II using Windows Server 2012.

When run from the hard drive, this update completes successfully, but the driver remains at 15.6.0.10.

What would you suggest I do next?

Thanks for the update.

Can you post the URL you used for the update?

Regards

Abhijit

Hey there Myriaxis,

Can you tell us what exact driver filename you are trying to apply? (URL?)

And what error messages you see if any?  (assuming you are trying this now _outside_ of OME).

Thx!

Rob

Hi,

I ran the EXE on the target node and using Driver Manager I confirmed the driver is at 15.5.0.10 and not 17.6.0.0.

Unfortunately, I can't open a ticket since the server is no longer under Dell warranty (company policy, this server is not a production server).

Thanks,

One thing to note is that when the update package is applied, the individual driver versions may not be updated. the dups update the family version of the drivers, but if the individual driver was not updated, the properties for the nic may not show any changes. As long as the dup recognizes that the family version was changed, your update is complete. So to test this, run the dup again manually, if it says the nic drivers is already at the same version, you are done. There is a way to extract the driver package and find the readme so that you can see exactly which driver files will be updated by the dup.

Rey "looking for a job" Garza 

Hello Rey and Rob,

Here is the URL for the Dell Support download page:

http://www.dell.com/support/drivers/ca/en/cabsdt1/DriverDetails/Product/poweredge-t110-2?driverId=CYKKJ&osCode=MWS80&fileId=3214169537&languageCode=EN&categoryId=NI

There is a choice of a regular update EXE "Bcom_LAN_17.6.4.2_Windows_64_17.6.12.exe" and a DUP "Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12.EXE".

I tried both and both complete successfully (no error), but the NIC driver remains at 15.6.0.10.

As suggested by Rey, I looked into the Broadcom driver release.txt file. Here is what I found:

                            Broadcom (R) Corporation
                          Broadcom Ethernet Software Kit
                              RELEASE T7.6.4.2 Gold
                            (Thursday, March 28, 2013)
        

Software Compatibility
======================
This release of software supports:
- BCM5709C NetXtreme II Gigabit Ethernet Adapter
- BCM5709S NetXtreme II Gigabit Ethernet Adapter
- BCM5716C NetXtreme II Gigabit Ethernet Adapter
- BCM5718 NetXtreme Gigabit Ethernet Adapter
- BCM5719 NetXtreme Gigabit Ethernet Adapter
- BCM5720 NetXtreme Gigabit Ethernet Adapter
- BCM5722 NetXtreme Gigabit Ethernet Adapter
- BCM57711 NetXtreme II Gigabit Ethernet Adapter
- BCM57712 NetXtreme II Gigabit Ethernet Adapter
- BCM57800 NetXtreme II Gigabit Ethernet Adapter
- BCM57810 NetXtreme II Gigabit Ethernet Adapter
- BCM57840 NetXtreme II Gigabit Ethernet Adapter

Contents of the CD
==================
**** Release Version Information Table ****

Product                            Version

1.       Windows 2003/Windows 2008 Drivers
Windows Server 2008 x86/x64 (NX1)  15.6.0.10*
Windows 2008/R2 NDIS Driver (NX2)  7.6.51.0*       
iSCSI Crash Dump Driver            7.6.50
FCoE Crash Dump Driver             7.6.1 
bxDiag                             7.6.5.0*
VBD Driver                         7.6.2.0*
VBD Driver NX2_Ev                  7.6.59.0*
Windows iSCSI Driver NX2           7.6.2.0*
FCoE Offload Driver                7.6.3.0*

As you can see, Windows Server 2008 x86/x64 drivers are at 15.6.0.10. I suppose this also applies to Windows Server 2012. Seems the drivers were updated correctly.

This brings a new question. Why does OME flag a non-compliance with this driver? I updated the catalog from Dell Online (Release Id 0G4M0, date 2013-10-11).

Thanks for the updates. There is a known issue with this update. The reported version(17.6.0) does not match with the version listed in the catalog (17.6.0.0). We are working with the appropriate teams to get this resolved.

You can safely ignore this entry in OME. You can also generate a catalog using repository manager and exclude this update. That will show the server as compliant.

Regards

Abhijit

Thank you.

I'll wait for the next update.

I also raised an issue in the Dell Systems Management General Forum at http://en.community.dell.com/techcenter/systems-management/f/4469/t/19527842.aspx.

Can someone help me?

Thanks.

Hello Abhijit or Anyone from Dell,

Has this issue with the Broadcom DUP/drivers on 64 bit Windows, been resolved? It is the 13th of Dec and I just downloaded an updated bundle in DRM for my R710 that has a Broadcom. I ran the bundle, but the NIC drivers do not get updated. When is the fix expected?