Unsolved
This post is more than 5 years old
58 Posts
0
178250
Broadcom 17.6 catalog Issue
Hey Guys,
I noticed an earlier forum post about this, but I have some further details. This is not related to the update from OME 1.1.1 to 1.2.
With the last catalog release, Broadcom version 17.6 drivers were made available for upgrade (dell seems to have finally gone with Broadcom's driver version numbering which is nice, saves the headaches, but seems to have caused a new issue).
Here's a screenshot from OME:
Here's a screenshot from the 17.6 release notes - note the actual driver version:
When checking the device inventory via OME, it is listing the driver at 7.6.2 as well as another entry for the driver being at 17.6
The screenshot I put was from a 2950 server, but it's occurring in approximately 19 other physical servers for me
My guess would be that either OME is looking at the wrong driver to update, or the versioning differences is messing it up
Blake
BlakeRSK
58 Posts
0
July 29th, 2013 13:00
Here's another example, this is from an M610:
Here's screenshots from the OME device inventory screen for this server, I attached each of the ones that have Broadcom in the name:
7.6.2 and 7.6.59 are both drivers as part of that driver family.
Blake
DELL-Abhijit P
Community Manager
Community Manager
•
711 Posts
0
July 29th, 2013 14:00
Hi Blake,
Your analysis is right. OME compares the version reported in inventory with the one available in catalog. It looks like the new catalog lists the version for this driver as 17.6 and inventory reports it as 7.6.2.0 and 7.6.59.0. We'll discuss this with the catalog team further.
Regards
Abhijit
steve815
24 Posts
0
July 29th, 2013 17:00
Thanks. I've been scratching my head on this exact issue. I installed the latest driver, but OME keeps telling me it's out of date.
DELL-Rey G
3 Apprentice
3 Apprentice
•
943 Posts
0
August 1st, 2013 10:00
All, this appears to be a problem with the catalog itself, CYKKJ is not applicable and does not have to be installed. We are aware of the issue and a new catalog will be created. No ETA at this time. The OME suggestion to update can be ignored, OR a catalog can be created using Repository Manager, and that package wont be included by default, which is as it should be.
R Koek
1 Message
0
August 2nd, 2013 03:00
Is this also the reason SCCM will not offer this update? SCCM does offer the firmware P32M4 which fails without the 17.6 drivers.
DELL-Rey G
3 Apprentice
3 Apprentice
•
943 Posts
0
August 2nd, 2013 07:00
That is very likely. SCCM scans down the catalog for an applicable firmware and it is hitting the CYKKJ first, so it believes that is the correct firmware, and will not scan further down catalog to see if there are other applicable files. basically, it found what it needed and ignores the rest.
Matt Benoit
1 Message
0
August 16th, 2013 20:00
Just downloaded the latest catalog and still having this issue.
BlakeRSK
58 Posts
0
August 19th, 2013 07:00
BlakeRSK
58 Posts
0
August 19th, 2013 07:00
ditto. Catalog 1VFYJ - release 8/16/2013 - issue remains
DELL-Rey G
3 Apprentice
3 Apprentice
•
943 Posts
0
August 19th, 2013 07:00
Can I get some screenshots please?
bobst_its
30 Posts
0
August 19th, 2013 11:00
We're on OME 1.2 and also experiencing this issue with the latest catalog from a few days ago. I did notice that our catalog source is, however, different from what is shown in the previous screenshot:
BlakeRSK
58 Posts
0
September 24th, 2013 07:00
Update - I have loaded the latest catalog for September and the issue remains:
Catalog details:
Release ID: 80G16
Release Date: 9/13/2013
Blake
cedrock
2 Posts
0
October 9th, 2013 06:00
I have a similar issue:
I had it on OME 1.1 and now on OME 1.2.1.0
On several Servers I'am not able to update the following components.
for example a Power Edge M610:
The log is like this:
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s5m8\Network_Firmware_P32M4_WN32_7.6.15.EXE /f /s /l=C:\Windows\TEMP\DUP.log
Date: 2013-10-09 11:10:05
=========================================================================
Release ID: P32M4X15-00
Update Package version: 7.3.0 (BLD_172)
User:
Collecting inventory...
Running validation...
The version of this Update Package is newer than the currently installed version. Software application name: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Package version: 7.6.15 Installed version: 6.2.16
The version of this Update Package is newer than the currently installed version. Software application name: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Package version: 7.6.15 Installed version: 6.2.16
Executing update...
Device does not impact TPM measurements.
Device: [0028] Broadcom BCM5709S NetXtreme II GigE #28, Application: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Firmware Update Failure Device: [0029] Broadcom BCM5709S NetXtreme II GigE #29, Application: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Firmware Update Failure
==============================> Update Result <==========================
Update was not applied
=========================================================================
Exit code = 1 (Failure)
2013-10-09 11:10:31
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s5m8\Network_Firmware_P32M4_WN32_7.6.15.EXE
Date: 2013-10-09 11:10:32
=========================================================================
Update Package finished. Exit code = 1
2013-10-09 11:10:32
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\slo\Network_Firmware_P32M4_WN32_7.6.15.EXE /f /s /l=C:\Windows\TEMP\DUP.log
Date: 2013-10-09 11:18:24
=========================================================================
Release ID: P32M4X15-00
Update Package version: 7.3.0 (BLD_172)
User:
Collecting inventory...
Running validation...
The version of this Update Package is newer than the currently installed version. Software application name: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Package version: 7.6.15 Installed version: 6.2.16
The version of this Update Package is newer than the currently installed version. Software application name: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Package version: 7.6.15 Installed version: 6.2.16
Executing update...
Device does not impact TPM measurements.
Device: [0028] Broadcom BCM5709S NetXtreme II GigE #28, Application: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Firmware Update Failure Device: [0029] Broadcom BCM5709S NetXtreme II GigE #29, Application: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Firmware Update Failure
==============================> Update Result <==========================
Update was not applied
=========================================================================
Exit code = 1 (Failure)
2013-10-09 11:18:50
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\slo\Network_Firmware_P32M4_WN32_7.6.15.EXE
Date: 2013-10-09 11:18:50
=========================================================================
Update Package finished. Exit code = 1
2013-10-09 11:18:50
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s4q8\Network_Firmware_P32M4_WN32_7.6.15.EXE /f /s /l=C:\Windows\TEMP\DUP.log
Date: 2013-10-09 13:04:28
=========================================================================
Release ID: P32M4X15-00
Update Package version: 7.3.0 (BLD_172)
User:
Collecting inventory...
Running validation...
The version of this Update Package is newer than the currently installed version. Software application name: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Package version: 7.6.15 Installed version: 6.2.16
The version of this Update Package is newer than the currently installed version. Software application name: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Package version: 7.6.15 Installed version: 6.2.16
Executing update...
Device does not impact TPM measurements.
Device: [0028] Broadcom BCM5709S NetXtreme II GigE #28, Application: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Firmware Update Failure Device: [0029] Broadcom BCM5709S NetXtreme II GigE #29, Application: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Firmware Update Failure
==============================> Update Result <==========================
Update was not applied
=========================================================================
Exit code = 1 (Failure)
2013-10-09 13:04:53
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s4q8\Network_Firmware_P32M4_WN32_7.6.15.EXE
Date: 2013-10-09 13:04:53
=========================================================================
Update Package finished. Exit code = 1
2013-10-09 13:04:53
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s34s\Network_Firmware_P32M4_WN32_7.6.15.EXE /f /s /l=C:\Windows\TEMP\DUP.log
Date: 2013-10-09 13:21:43
=========================================================================
Release ID: P32M4X15-00
Update Package version: 7.3.0 (BLD_172)
User:
Collecting inventory...
Running validation...
The version of this Update Package is newer than the currently installed version. Software application name: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Package version: 7.6.15 Installed version: 6.2.16
The version of this Update Package is newer than the currently installed version. Software application name: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Package version: 7.6.15 Installed version: 6.2.16
Executing update...
Device does not impact TPM measurements.
Device: [0028] Broadcom BCM5709S NetXtreme II GigE #28, Application: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Firmware Update Failure Device: [0029] Broadcom BCM5709S NetXtreme II GigE #29, Application: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Firmware Update Failure
==============================> Update Result <==========================
Update was not applied
=========================================================================
Exit code = 1 (Failure)
2013-10-09 13:22:10
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s34s\Network_Firmware_P32M4_WN32_7.6.15.EXE
Date: 2013-10-09 13:22:10
=========================================================================
Update Package finished. Exit code = 1
2013-10-09 13:22:10
===============> Update Package application started <===============
Command: C:\Users\\AppData\Local\Temp\s6rs\Network_Firmware_P32M4_WN32_7.6.15.EXE /f /s /l=C:\Windows\TEMP\DUP.log
Date: 2013-10-09 14:07:34
=========================================================================
Release ID: P32M4X15-00
Update Package version: 7.3.0 (BLD_172)
User:
Collecting inventory...
Running validation...
The version of this Update Package is newer than the currently installed version. Software application name: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Package version: 7.6.15 Installed version: 6.2.16
The version of this Update Package is newer than the currently installed version. Software application name: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Package version: 7.6.15 Installed version: 6.2.16
Executing update...
Device does not impact TPM measurements.
Device: [0028] Broadcom BCM5709S NetXtreme II GigE #28, Application: [0028] Broadcom BCM5709S NetXtreme II GigE #28 Firmware Update Failure Device: [0029] Broadcom BCM5709S NetXtreme II GigE #29, Application: [0029] Broadcom BCM5709S NetXtreme II GigE #29 Firmware Update Failure
==============================> Update Result <==========================
Update was not applied
=========================================================================
Exit code = 1 (Failure)
2013-10-09 14:07:59
===============> Update Package application started <===============
Command: C:\Users\1\AppData\Local\Temp\s6rs\Network_Firmware_P32M4_WN32_7.6.15.EXE
Date: 2013-10-09 14:07:59
=========================================================================
Update Package finished. Exit code = 1
2013-10-09 14:07:59
Our Catalog is the latest SUU ISO:
Any Hints?
best Regards
DELL-Abhijit P
Community Manager
Community Manager
•
711 Posts
0
October 9th, 2013 07:00
Hi,
Thanks for your post.
From the information you have posted, it might not be an issue with OME. The update is reporting failure while running. Is it possible for you to run this update package directly on the target server outside of OME? If you get the same error, most likely the firmware update package may have an issue and we can inform appropriate team.
Regards
Abhijit
cedrock
2 Posts
0
October 9th, 2013 08:00
Hi
Thanks for your reply.
I just found a way to install the package in OME. I imported the older catalog.xml (OM_721_SUU_Q12013_A00) and installed the firmware from there. It worked.
Now with the new catalog again I have only this driver left to be compliant:
This Driver I can install but he always left in the "select updates to apply" sector.
Regards