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
Robert Clemens
20 Posts
0
January 6th, 2014 07:00
This is 100% on Dell. Even if there are issues with Broadcom, they are not the ones pushing updates to the catalog which in turn is alerting Dell Software to know that an update is available.
If the Broadcom drivers had issues in the first place, not cataloging the update would keep Dell systems out of the know and thus no problem.
No way, no how, will this ever be assigned to Broadcom as their issue.
sunnysnair
5 Posts
0
January 6th, 2014 07:00
Yes, but, from our standpoint, we can't go to Broadcom? We are using a Dell product/service and we look to Dell to push the issue with whoever, as needed, and get us a resolution? I am sorry for the rant here - but this is just getting out of hand!
BPU
33 Posts
1
January 23rd, 2014 04:00
More than two weeks faded away and there is absolutely no information by DELL.
Makes me feel real sad.
BPU
33 Posts
0
February 10th, 2014 07:00
Is Dell working on this issue?
For months we didn't hear anything regarding this issue. I don't feel like anyone cares about this problem. Hope dies last.
Robert Clemens
20 Posts
0
February 10th, 2014 07:00
And during that time I've had other catalog issues arise such as a VRTX update appearing on my R420 servers (SAS RAID)......
DELL-Rob C
2 Intern
2 Intern
•
2.8K Posts
0
February 10th, 2014 14:00
ed:Duplicate post from my previous reply (sorry, forum said the post failed). Rob
Hi guys, I definitely understand the importance of the issue. Here is the latest I know of.
Note on these types of issues, there are often 3 things in the mix: the driver pack (BComm), the catalog, and OME. So we have multiple teams that need to keep the moving parts in sync. Certainly not an excuse, from a customer perspective: it's Dell. And that's correct. Internally, there can be a number of groups working to resolve....different release schedules, etc. As I said, not an excuse, just 'insight'.
Thanks,
Rob
DELL-Rob C
2 Intern
2 Intern
•
2.8K Posts
0
February 10th, 2014 14:00
Hi Robert...
Can I get more info on that bogus update showing up? SAS RAID (Firmware or drive and the full name).
I can try to tell the catalog team. But it would be helpful if you can open a ticket on this particular issue.
Thanks,
Rob
DELL-Rob C
2 Intern
2 Intern
•
2.8K Posts
0
February 10th, 2014 14:00
Hi guys, I definitely understand the importance of the issue. Here is the latest I know of.
Note on these types of issues, there are often 3 things in the mix: the driver pack (BComm), the catalog, and OME. So we have multiple teams that need to keep the moving parts in sync. Certainly not an excuse, from a customer perspective: it's Dell. And that's correct. Internally, there can be a number of groups working to resolve....different release schedules, etc. As I said, not an excuse, just 'insight'.
Thanks,
Rob
Robert Clemens
20 Posts
0
February 10th, 2014 14:00
http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=7W1YW
Windows 2008 R2 64 Bit Driver for VRTX controllers
My controller is Perc H710 but not VRTX. Update will not apply to this model.
BlakeRSK
58 Posts
0
February 11th, 2014 06:00
Thanks for the update Rob :)