v1.1.1

New Features

• proliant ilo/com/oneview reports memory: added a Vendor P/N column showing each DIMM's raw manufacturer part number (e.g. HMA82GR7CJR4N-WM), alongside the existing HPE-branded part number — useful when a DIMM's HPE part number shows as Unknown (e.g. on a server with broken inventory collection that was never HPE-branded), since the vendor's own part number is still available and lets you identify the actual module. Rows are now also grouped by the combination of HPE + vendor part number, so distinct physical modules that both happen to show Unknown for their HPE part number are no longer merged into a single misleading row.
• proliant ilo/com/oneview reports memory and proliant ilo/com servers describe: added a Status column showing each DIMM's health (OK, or a flagged state like Degraded/ConfigurationError/MapOutError in red). HPE's iLO Redfish implementation does not expose the standard MemoryMetrics resource (confirmed via a live 404 probe), so no live correctable/uncorrectable ECC error count is available through Redfish or OneView on this hardware — DIMMStatus is the closest available health signal, so this surfaces it instead of silently discarding it as before. The fleet report groups by part number, so a flagged group shows which distinct problem status(es) occurred and which server(s) had them.
• proliant ilo servers describe / proliant com servers describe (direct-iLO only — not reachable for OneView/Synergy-managed servers, whose compute-module iLOs only expose a link-local management address): added a Memory Events (IML) section listing any memory-related entries from the iLO's Integrated Management Log, newest first. This is the actual mechanism HPE uses to record discrete corrected/uncorrected memory-error events (e.g. "Corrected Memory Error (Processor 1, DIMM 3)"), and is the closest real substitute for a live ECC error count.

Bug Fixes

• proliant ilo reports memory/cpu/gpu: dropped the redundant list action these needed (e.g. proliant ilo reports memory list) — every other proliant ilo/com/oneview fleet report runs directly as reports <name> with no extra action layer, since a report has nothing else it could do. proliant ilo reports memory (optionally with a single server name or --hosts-from FILE) now works the same way proliant com reports memory and proliant oneview reports memory always have.
• proliant oneview reports memory: the "Servers" column now shows each server's assigned server profile name first, falling back to the OneView hardware bay label (e.g. Enclosure-01, bay 6) only when no profile is assigned — confirmed live: one server showed as a literal localhost (its OS was never given a real hostname beyond the install default) and another showed a raw bay label instead of its actual profile name bay7-6820-cna. The report previously used each server's own OS-reported serverName, which can be blank or a meaningless default and doesn't match how the OneView GUI or the rest of the CLI identify a server.

---