OV 8.6 / iLO5 2.98, 2.97 + SPP 2023.09.00.00 woes (portmap discovery, data exchange etc)

[sfrench-quilter]

We have experianced multiple issues with the latest HPE updates for OneView 8.6 and DL380/DL360 Gen10 plus incorporating the Broadcom P225p NetXtreme-E Dual-port 10Gb/25Gb Ethernet PCIe Adapter and the 2023.09.00 SPP for Gen10/Gen10+

Issues

1. Deploying the SPP 2023.09.00.00 fails to update the Power Management Controller Firmware from version 1.0.8 to 1.1.0 which then OneView complains about (firmware baselines inconsistent) 
The SPP contains both firmware packages but does not seem to deploy 1.1.0 on intel based systems. Manually updating the firmware to 1.1.0 makes OneView happy. 
https://support.hpe.com/connect/s/softwaredetails?softwareId=MTX_02e6d052f1fd4ad7a1619a8e5c&tab=releaseNotes
This appears to be a bug whereby SUM decides that 1.1.0 is not required? But OneView thinks it is?

2. After running the SPP on a DL380 Gen10+ OneView develops alarms for 'Unable to fully discover the port map information' and 'The appliance cannot communicate with the adapter in unknown due to a data exchange problem. (OneView 8.5 + iLO5 2.96).
Updating iLO to 2.97 does not seem to resolve the issue and I can see some device details such as 'part number and product version' is missing in OneView for the Broadcom P225p NetXtreme-E Dual-port 10Gb/25Gb Ethernet PCIe Adapter (firmware version 226.1.107.0). Updating iLO to 2.98 with OneView 2.60 appears to fix this, however the alarms remain and re-trigger on refresh.

3. Upgrading OneView from 8.5. to 8.6 we start getting spammed with emails every 10 mins with  'Remote support is unable to connect to HPE' Others have already commented on this in the forums so I won't repeat further.

All in all, sadly another disasterous set of updates from HPE - if you were my girlfriend I'd have broken up with you by now.

[Sebasbin · Accepted solution]

Hi,

Please find the below customer advisory related to the reported issue

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00135168en_us

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00135453en_us

[sfrench-quilter]

Hi Sebasbin,

Thank you for your reply, very useful to see these advisories.

Now I'll wait for the fixes - hopefully very soon.
Sadly we are too far down the road with patching/updates to roll back to a stable software/firmware combination.

Best wishes

[ChrisLynch]

Regarding #3, we will have a re-release of 8.60 to address that issue soon.  Needless to say, new functionality that we haven't enabled within OneView was causing an intermitant alert to be generated.  R&D has identified the cause, and are validating their gate tests as part of development account for this.  I'll post an update when 8.60 is re-released that addresses this inadvertant issue.

[sfrench-quilter]

Thanks Chris, that's good news!

[pirx]

@ChrisLynch 

What does re-release mean for people that already have updated? Will there be a new update package too?

[DanCernese]

Yes, a new update package will replace the existing one.  People who has already updated will simply use it as if it were the next release.

[sfrench-quilter]

Just a note to say that iLO5 version 2.99 resolves the portmap discovery problem - in case anyone else is tracking these issues.

Looking forward to an updated OneView release.

[pirx]

Maybe woth a note: HPE_OneView_8.60.01_update_Z7550-97733.bin

• Details
• Product Number:

  Z7550-63180
  Category:

  Free Software
  Product Family:

  HPE OneView
  Software Type:

  Software
  Version:

  -
  Nov 21, 2023

[ChrisLynch]

Correct.  I was going to post an update to this thread.  8.60.01 addreses the reported #3 issue by @sfrench-quilter,

3. Upgrading OneView from 8.5. to 8.6 we start getting spammed with emails every 10 mins with  'Remote support is unable to connect to HPE' Others have already commented on this in the forums so I won't repeat further.

[sfrench-quilter]

Thanks for the updates, I've upgraded our appliances and things are much better.

Much appreciated!

[pirx]

Not directly related to this thread, but I'm on latest OV, OV4VC, SPP version. And still get 3 different remediation results when updating 3 servers in same cluster with vLCM. Same hardware and firmware level. Two failed at different stages, only one was successful without any error. To me the whole orchestration/workflow with vLCM and OV4VC seems to be broken. In OV there is still a firmware update retry active, when the whole task has already failed in vLCM.