UNSOLVED
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
1266
0
Posted 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
1266
0
Posted 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.
1266
0
Posted 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.
1266
0
Posted 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.
1266
0
Posted 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.
1266
0
Posted August 16th, 2013 20:00
Just downloaded the latest catalog and still having this issue.
800
0
Posted August 19th, 2013 07:00
1266
0
Posted August 19th, 2013 07:00
ditto. Catalog 1VFYJ - release 8/16/2013 - issue remains
1266
0
Posted August 19th, 2013 07:00
Can I get some screenshots please?
BlakeRSK
58 Posts
1266
0
Posted 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