The Catalog Team is aware of the issue and is working on correcting it.  

ok, i will try to patiently wait :)

Thanks,

blake

I hate to say this, but the catalog update has been pushed back to mid May (at least). I would suggest creating  your own repository using the Dell Repository Manager. What you would want to do is add the nic update package (dup) to the repository for the system(s) you own. the site below has videos on RM's usage, and the 6th video on the list I created to help people add packages to the bundles. This can then be used with the Lifecycle controller or as a Server Update utility (SUU).

en.community.dell.com/.../1767.dell-repository-manager.aspx

thanks for the update/info

Blake

Hi! Is there any progress on this? It is a bit annyoing to get a "non compliant" message for almost all of our servers... Furtermore I noticed another calatog bug: On Windows Server 2003 32bit at least the PERC 6/i RAID Controller driver is shown as outdated as the 32bit driver ends with 2.24.0.32 and the 64bit driver ends with 2.24.0.64. OME thinks that the 64bit driver is newer (because of the .64) and then tries to install a 64bit driver on a 32bit OS which fails for sure. So it still shows the PERC 6 as non compliant regarding the driver version which is a fault positive! This should also be corrected!

Best regards,

SG

Thanks for the information SG.

I hadn't heard about the 32/64 bit issue before. I'll get this across to the catalog team ASAP.

Regards

Abhijit

Can you give as any timeline when these bugs should be fixed and the catalog should be completely functional? Meanwhile there should be thousands of IT people using OME worldwide, so it's a bit frustrating to wait and wait...

Best regards,

 SG

Hi SG,

New catalog with this bug fix is in the process of final validations and should be posted online this week.

I understand the frustration and the catalog team is trying their best to resolve any issues as soon as possible. Since the catalog contains thousands of components and is consumed by multiple products, the validation cycle is little longer.

Regards

Abhijit

This broadcom issue was originally posted January 27th and after the newest catalog update, (06/22) - the issue still remains.  Can we please have a renewed push to get this fixed by the catalog team?  I have to constantly explain to my boss/peers why systems are showing as non-compliant when they are actually compliant.

thank you sir