Network firmware update keeps reappearing

Can you help us with the following data to look further in this while we are passing this information to the update team:

1. What is the version shown in software inventory table of the device for which this update is shown as applicable?

2. Can you try running the Firmware & Driver inventory task on this target (only once) and check whether the version (step 1 above) is updated in software inventory table in device details page?

Thanks,
Vijay

Hello,

• This is what OMSA reports:
  Firmware Version Family 7.10.61 (Boot Code 5720-v1.36, PXE v17.0.1, iSCSI v17.0.0) 
  
  
• This is what I have in the software inventory:
  [0013] Broadcom NetXtreme Gigabit Ethernet #3   7.10.18
  
  
• And in the "Non-complient systems" tab:
  "server_name","Optional","In-band or Out-of-band","[0013] Broadcom NetXtreme Gigabit Ethernet #3","Firmware","7.10.18","Upgrade","7.10.61","Network_Firmware_PVRHM_WN64_7.10.61.EXE","true"

I tried your "step 2" but it didn't changed.

Hi,

Thanks for the update.

By looking at the details provided seems you have both OOB and In-Band discovered in OME. But one thing we would need to know that which method did you used to perform update was it In-Band or OOB? This you can confirm get it confirmed under System Update > Summary > Advanced Settings.

If it was set to In-Band(Default) can you confirm the OMSA version? and also try out restarting the OMSA services on the target server (there will be 4 services, starting with "DSM") and then delete the device from OME and re-discover it again. See if you notice any changes!

If it was set to OOB, can you confirm whether CSIOR was enabled on the target server?

Regards

Ranveer

We usually use in-band, but as we can't use DRM as catalog we did the updates manually. Servers are mostly using OMSA 8.1.0.1 and a few have 8.2.0. 

Test server has been deleted and rediscovered, this has fixed the issue. Thx. 

On a side note OME 2.1 gives us a lot of trouble, I'm thinking to roll-back, I don't want to spend anymore time trying to understand and debug the current version.

Glad to know that you figured out the fix for the issue.

You can use catalog created from DRM as catalog source in OME and compliance will be computed from the selected DRM catalog in this case.

Sorry to hear about the inconvenience you faced in using OME 2.1. I will suggest to open a support ticket 800-945-3355 for the issues you are facing with OME 2.1 which are not resolved, so that we can address them.

Many thanks.

Well... too bad, I'm already rolling back because all servers were, again, unclassified this morning. I have already spent too much time with support trying to fix this broken version.