OneView OV 3.10.07 reports Profiles OK even when BIOS Settings and FW not actually compliant

[gobigted]

OV 3.10.07

OS Revision: ESXi 6.0

Environment : OneView 3.10.07 DL380 Gen9

We have a OneView Template with BIOS settings and firmware 2016.10 SPP.  Server Profiles will show up in "OK" status, but we have found many servers that don't actually have the BIOS settings in the template applied or specific firmware levels aren't at the proper levels to match what is in the SPP.  I opened a case with HPE and their plan of action was the following:

Perform a NVram clear on the affected server.

Steps are as follows:
1. Power down server.
2.Unassign profile.
3.Clear NVram
4.apply profile
5.Power On server.

We originally thought this was only seen in servers with a hardware replacement, but we have since discoverd that brand new servers have this issue.  For example, an elxnet NIC should have the 11.1.145.0 driver per the SPP, but actually has the 10.7.110.34 driver.  Server Profile shows up in OneView as "OK".

We rely on OneView to tell us we are compliant with BIOS settings and firmware.  Now that we have discovered this issue, we have to check other compliance reports to check firmware levels.  For BIOS, however, the only visibility into the real BIOS settings we have is to reboot the host, look and compare it to OneView.  

Has anyone else seen this issue?  Any suggestions.

[peyrache]

Hello
How did you update drivers ?