{
    "DeviceClass": "79f0c163-0c13-4662-9dea-09235fef90cb", 
    "Devices": {
        "Device": [
            {
                "DeviceName": "HPE IB XDR/EN 2x400GbE 1P PCIe6x16 Adptr", 
                "FirmwareImages": [
                    {
                        "DelayAfterInstallSec": 0, 
                        "DirectFlashOK": true, 
                        "FileName": "40_48_1000-900-9X81E-00EX-ST0_Ax.pldm.signed", 
                        "InstallDurationSec": 360, 
                        "Order": 1, 
                        "PLDMImage": true, 
                        "ResetRequired": true, 
                        "ServerPowerOff": false, 
                        "SysPowerOn": true, 
                        "Type": "Firmware", 
                        "UEFIFlashable": false
                    }
                ], 
                "Target": "a6b1a447-382a-5a4f-15b3-102315b30002", 
                "Version": "40.48.1000"
            }
        ]
    }, 
    "Package": {
        "Category": [
            {
                "Lang": "en", 
                "Value": "Firmware - Network"
            }
        ], 
        "Description": [
            {
                "Lang": "en", 
                "Value": "NVIDIA HPE signed PLDM Firmware Package for HPE InfiniBand XDR/Ethernet 2x400GbE 1-port OSFP PCIe6 x16 HHHL CX8 Crypto Adapter : HPE part number P79114-H21"
            }
        ], 
        "Divisions": [
            {
                "Divsion": [
                    {
                        "Lang": "en", 
                        "Value": "Networking"
                    }
                ]
            }, 
            {
                "Divsion": [
                    {
                        "Lang": "en", 
                        "Value": "Server"
                    }
                ]
            }
        ], 
        "Files": [
            {
                "Bytes": "9518335", 
                "DateModified": "2026-03-10T06:09:16", 
                "FileList": [
                    "40_48_1000-900-9X81E-00EX-ST0_Ax.pldm.signed", 
                    "40_48_1000-900-9X81E-00EX-ST0_Ax.pldm.xml", 
                    "payload.json"
                ], 
                "MD5Sum": "739f7ac330b1dd9aff47159f4015b78d", 
                "Name": "40_48_1000-900-9X81E-00EX-ST0_Ax.pldm.fwpkg", 
                "Release": "2026-03-10T06:06:15", 
                "Revision": "", 
                "SHA1Sum": "6e27756fcb7d0bfb51fcc8d6236b5b4f1d49f720", 
                "SHA256Sum": "cbd5748faa3d859d0d84e4947f031138ca27504cc392afc91c477d5be6c7e607", 
                "Size": "9.08MB", 
                "TargetGUIDs": [
                    "a6b1a447-382a-5a4f-15b3-102315b30002"
                ], 
                "TypeOfChange": "1", 
                "Version": "40.48.1000"
            }
        ], 
        "Id": {
            "Product": "e9a39e503f934c9b9e368c25f2781cd9", 
            "Version": "6238968e60504d448e427433b4e3bfab"
        }, 
        "Installation": {
            "Command": "", 
            "CommandParams": "", 
            "InstallCaps": {
                "NeedUserAction": "no", 
                "Silent": "no"
            }, 
            "PerDeviceInstallTimeSeconds": 360, 
            "RebootDetails": [
                {
                    "Lang": "en", 
                    "Value": "Reboot is required after installation for updates to take effect and hardware stability to be maintained."
                }
            ], 
            "RebootRequired": "yes", 
            "RebootRequirement": "Required"
        }, 
        "InstallationDependency": {}, 
        "InstallationNotes": [
            {
                "Lang": "en", 
                "Value": "<p>Flash the PLDM firmware using any below methods</p>\n\n<ol>\n\t<li>Flash using iLOrest tool&nbsp;</li>\n\t<li>Flash using&nbsp;Smart Update Manager (SUM).</li>\n\t<li>Flash from iLO GUI</li>\n</ol>\n\n<p>1. To flash this firmware package, use the following iLOrest command. &nbsp;See&nbsp;<a href=\"http://www.hpe.com/servers/resttool\">http://www.hpe.com/servers/resttool</a>&nbsp;to download the latest version of the iLOrest tool.</p>\n\n<p style=\"margin-left:40px\">localhost OS example:<br />\n<strong><em>ilorest flashfwpkg &lt;file_name.fwpkg&gt;&nbsp;</em></strong></p>\n\n<p style=\"margin-left:40px\">remote example:<br />\n<strong><em>ilorest flashfwpkg &lt;file_name.fwpkg&gt; --url &lt;iLO5_IP_Address&gt; -u &lt;iLO5_username&gt; -p &lt;iLO5_password&gt;</em></strong></p>\n\n<p>2. This firmware package can also be installed with the latest version of Smart Update Manager (SUM).</p>\n\n<p style=\"margin-left:40px\"><strong>Supplemental updates</strong>&nbsp;for supported ProLiant servers and options can be done by using&nbsp;SUM, which is found on the&nbsp;<strong><a href=\"http://www.hpe.com/info/spp\">Service Pack for ProLiant</a></strong>&nbsp;(SPP) ISO.</p>\n\n<ul style=\"margin-left:40px\">\n\t<li>\n\t<p>Place the Service Pack for ProLiant on a USB key using the&nbsp;<strong><a href=\"https://support.hpe.com/connect/s/softwaredetails?language=en_US&amp;softwareId=MTX_360731071b404454b454390208&amp;tab=revisionHistory\">USB Key Creator Utility</a></strong>.</p>\n\t</li>\n\t<li>\n\t<p>Place the desired&nbsp;firmware packages and components&nbsp;to be updated in the directory&nbsp;&quot;\\packages&quot; on the USB key.</p>\n\t</li>\n</ul>\n\n<p style=\"margin-left:40px\">Update the firmware and software&nbsp;in the usual manner.</p>\n\n<p style=\"margin-left:40px\">Reboot your system for the update to take effect immediately</p>\n\n<p>3.&nbsp;Flash from iLO GUI</p>\n\n<ul>\n\t<li>Browse iLO IP using any browser and login using the credential&nbsp;</li>\n\t<li>Make sure the PLDM supported adapter is present in the server</li>\n\t<li>Go to iLO GUI -&gt; Click on &quot;Firmware and OS software&quot; from left side&nbsp;&nbsp;-&gt; Click on &quot;Update Firmware&quot; -&gt; Click on &quot;Choose File&quot; and browse to the supported PLDM file -&gt; Then click on &quot;Flash&quot; button.&nbsp;</li>\n\t<li>Update status will be show in the Top and a log entry can be seen in Integrated Managenment Log (IML)&nbsp;</li>\n\t<li>Reboot the server for the firmware update to take effect.</li>\n</ul>\n"
            }
        ], 
        "ManufacturerName": [
            {
                "Lang": "en", 
                "Value": "Hewlett Packard Enterprise"
            }
        ], 
        "Name": [
            {
                "Lang": "en", 
                "Value": "NVIDIA Firmware Package (FWPKG) for HPE InfiniBand XDR/Ethernet 2x400GbE 1-port OSFP PCIe6 x16 HHHL CX8 Crypto Adapter : HPE part number P79114-H21"
            }
        ], 
        "Prerequisites": {
            "RequiredDiskSpace": {
                "SizeKB": "32000"
            }, 
            "SupportedDevices": [
                {
                    "Dev": "1023", 
                    "SubDev": "0002", 
                    "SubVen": "15B3", 
                    "TargetGUID": "a6b1a447-382a-5a4f-15b3-102315b30002", 
                    "Type": "pci", 
                    "Ven": "15B3"
                }
            ], 
            "SupportedOperatingSystems": [
                {
                    "Major": "10", 
                    "Maximumbuild": "17599", 
                    "Minimumbuild": "14393", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2016", 
                    "Platform": "nt_x86-64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "10", 
                    "Maximumbuild": "18999", 
                    "Minimumbuild": "17600", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2019", 
                    "Platform": "nt_x86-64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "10", 
                    "Maximumbuild": "25398", 
                    "Minimumbuild": "20317", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2022", 
                    "Platform": "nt_x86-64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "0", 
                    "Minor": "0", 
                    "Name": "Cross Operating System", 
                    "Platform": "oi", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "7", 
                    "Minor": "0", 
                    "Name": "Red Hat Enterprise Linux 7 Server", 
                    "Platform": "red_hat_enterprise_linux_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "8", 
                    "Minor": "0", 
                    "Name": "Red Hat Enterprise Linux 8 Server", 
                    "Platform": "red_hat_enterprise_linux_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "9", 
                    "Minor": "0", 
                    "Name": "Red Hat Enterprise Linux 9 Server", 
                    "Platform": "red_hat_enterprise_linux_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "12", 
                    "Minor": "0", 
                    "Name": "SUSE Linux Enterprise Server 12", 
                    "Platform": "suse_linux_enterprise_server_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "15", 
                    "Minor": "0", 
                    "Name": "SUSE Linux Enterprise Server 15", 
                    "Platform": "suse_linux_enterprise_server_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "16", 
                    "Minor": "0", 
                    "Name": "SUSE Linux Enterprise Server 16", 
                    "Platform": "suse_linux_enterprise_server_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "10", 
                    "Minor": "0", 
                    "Name": "Red Hat Enterprise Linux 10", 
                    "Platform": "Red_Hat_Enterprise_Linux_x86_64", 
                    "Sr": "OEM"
                }
            ], 
            "SupportedPlatforms": false
        }, 
        "ReleaseDate": "2026-04-03T10:15:18", 
        "RevisionHistory": [
            {
                "ReleaseNotes": [
                    {
                        "Enhancements": "<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>\n\n<ul>\n\t<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>\n\t<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>\n\t<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>\n\t<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>\n\t<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>\n\t<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>\n\t<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>\n\t<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>\n\t<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>\n\t<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>\n\t<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>\n</ul>\n", 
                        "Fixes": "<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>\n\n<ul>\n\t<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>\n\t<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>\n\t<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>\n\t<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>\n\t<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>\n\t<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>\n\t<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>\n\t<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>\n\t<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>\n\t<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>\n\t<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>\n\t<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>\n\t<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>\n\t<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>\n\t<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>\n\t<li>An issue where probe packets might not be sent under heavy traffic.</li>\n\t<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>\n\t<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>\n\t<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>\n</ul>\n", 
                        "Lang": "en"
                    }
                ], 
                "Version": "40.48.1000"
            }, 
            {
                "ReleaseNotes": [
                    {
                        "Enhancements": "<p><strong>New features and changes included in version 40.47.1026:</strong></p>\n\n<ul>\n\t<li>Added Scaling Factor &quot;read&quot; field. To obtain correct values in mlxlink, MFT version 4.33.0 or later is required.</li>\n\t<li>Lane Margin is a signal integrity diagnostic feature that measures the electrical &ldquo;eye margin&rdquo; of high-speed serial lanes, the physical data paths that carry bits over interfaces like PCIe, SerDes, or Ethernet links.</li>\n\t<li>Added a new NVLOG TLV type to support PCIe logger functionality. This enhancement enables logging and debugging of PCIe-related events through the NVLOG infrastructure, improving traceability and issue analysis.</li>\n\t<li>This enhancement enables seamless metadata propagation across layers, allowing flow steering rules and packet processing logic to share contextual information such as flow identifiers, source context, or policy tags. It improves coordination between NIC and E-Switch pipelines, enabling more flexible traffic handling and advanced offload capabilities.</li>\n\t<li>Access control was added to ensure that only the VHCA instance that created a DPA partition is permitted to modify or delete it.</li>\n\t<li>A new DPA Manifest mechanism was introduced to define and manage application permissions.</li>\n\t<li>DPA TIMER functionality has been exposed through the MTCTR access register, allowing direct access by applications.</li>\n\t<li>Added support for parallel suspend operations across multiple VFs.</li>\n\t<li>Added support for using the real-time clock to fill the request and response timestamps in hardware-generated RTT packets. To enable this feature, set REAL_TIME_CLOCK_ENABLE in mlxconfig and configure ROCE_CC_RTT_TIMESTAMP_FORMAT to 0x02 (REAL_TIME).</li>\n\t<li>Enables customers to specify the corresponding GNS values that will be forwarded to the DOCA PCC NP feature. When multiple slots are configured with IFA2, the GNS settings in pcc_config and pcc_np_config must be identical across all slots using IFA2.</li>\n\t<li>When a GGA QP encounters a memory access (address translation) issue in one VM or Function, it no longer enters an error state. Instead, the QP now recovers from the error, sends an error CQE to the software, and continues serving&nbsp;other VMs and Functions. Unlike RDMA QPs, the error CQE may redundantly reference a valid mkey, therefore, the software should reconstruct all mkeys that received error CQE notifications.</li>\n\t<li>Added the ability to enable or disable ECN in the upstream by allowing the MODIFY_CONG_STATUS and QUERY_CONG_STATUS commands in mlx5_fwctl.</li>\n\t<li>Enabled 50G per-lane link speed and improved LED behavior for clearer network status indication. Traffic LED now blinks when traffic is active and reflects accurate link status.</li>\n\t<li>Added a new API to write PSP Master Key. This API allows writing a new PSP Master Key, which will be used to generate new SPI/key pairs. The previous key remains valid for decryption until the key rotation process is completed.</li>\n\t<li>Firmware now allows the ADP-RETX timeout profile to be configured even when there are open QPs.</li>\n\t<li>PCI logs are now reported via the existing NC-SI OEM command Get Log Info (Command = 0x0, Parameter = 0x2F).</li>\n\t<li>Added support for Adaptive Hotplug System (AHS) alongside the existing NHP solution, enhancing hotplug flexibility and system adaptability.</li>\n\t<li>The ASO object pointer size has been increased from 24 bits to 32 bits, eliminating the previous limitation of ~16 million ASO objects per GVMI and enabling significantly greater scalability for future expansions.</li>\n\t<li>Added an NV configuration option to allow disabling XDR. Note: Disabling SDR or enabling configurations not supported by the INI file remains unsupported.</li>\n\t<li>Added support for MVCAP (Multi-Version Capability) functionality enabling improved compatibility and version management across multiple components.</li>\n</ul>\n", 
                        "Fixes": "<p><strong>The following issues have been fixed in version 40.47.1026:</strong></p>\n\n<ul>\n\t<li>The ZTR_RTTCC algorithm parameters AI and HAI did not support a sufficient range.</li>\n\t<li>Coalescing regular SX events with SX RTT events under ZTR_RTTCC would keep improper event fields, which would impact congestion control behavior.</li>\n\t<li>Issue in the ZTR_RTTCC algorithm where probe-abortion handling would behave improperly under high-stress network conditions, affecting proper congestion control and stable traffic performance.</li>\n\t<li>An assertion failure that would occur with the E-Switch uplink in specific configurations where the e-switch was disabled and Path Migration was active or GVMIs were using SRQ loopback in SQs. The issue occurred because the firmware attempted to perform cleanup operations when the uplink configuration lacked sufficient capacity. Now, when the E-Switch is disabled and no actions are available in the uplink STE, the firmware connects to the uplink STE instead of copying it.</li>\n\t<li>The ConnectX-8 downstream port failed to send a NACK when rejecting an L1 entry request from the upstream port.</li>\n\t<li>Invoking the resourcedump tool with segment type DPA_PROCESS_LST returned invalid data when the parameter n1 == 1 and no processes existed on the current vhca_id. The fix adds a proper check, and the resourcedump tool now reports the correct error in this scenario.</li>\n\t<li>During failover or restart, the SM sending a PortInfo MAD to the HCA firmware triggered reinitialization of port buffers, momentarily halting ingress traffic and causing packet drops. The firmware now avoids reconfiguring port buffers when the new configuration matches the current one.</li>\n\t<li>MFRL operations would fail due to a timeout.</li>\n\t<li>Under the ZTR_RTTCC algorithm, a flow that reached its minimum rate due to heavy congestion would not recover its rate once the congestion cleared.</li>\n\t<li>A missing interrupt from the module IO (Expander) would prevent the module from being raised.</li>\n\t<li>Reading debug registers would cause link BER (Bit Error Rate) degradation over time.</li>\n\t<li>Ports connected via 4 or 8 lanes and configured for 200G_2x (using only 2 lanes) would fail to link when using a mix of new firmware (with &ldquo;Non Tx-Squelch&rdquo; support) and older firmware versions.</li>\n</ul>\n\n<p style=\"margin-left:40px\">Note: Please make sure on both sides, switch (local device) and Switch/NIC (peer device) you:</p>\n\n<ul>\n\t<li style=\"margin-left: 40px;\">Deploy the new firmware release versions as a matched bundle on both Switch and NIC devices.</li>\n\t<li style=\"margin-left: 40px;\">Configure the port to use 2 lanes (instead of 4 or 8 lanes) while keeping the 200G_2x speed setting.</li>\n\t<li>Issue in Arch diagnostic data counters where the pcie_link_outbound_data_bytes counter was incorrectly returning only zero values.</li>\n\t<li>Multiple long-running process registers would cause aborted access and timeouts, the internal state is now properly handled.</li>\n\t<li>Enabling the CCMAD custom header on one PCC probe slot caused other slots to malfunction when multiple slots were configured.</li>\n</ul>\n\n<p style=\"margin-left:40px\">Note: If using firmware versions older than the 40.47.10xx GA release, disable the CCMAD custom header when multiple probe slots are enabled.</p>\n\n<ul>\n\t<li>A CQE error with vendor_syndrome RDE_MAL_WQE (0xd6) could cause traffic disruption on the affected QP.</li>\n</ul>\n", 
                        "Lang": "en"
                    }
                ], 
                "Version": "40.47.1026"
            }
        ], 
        "SWKeys": [
            {
                "Name": "Mellanox_NIC_PLDM_CX8-HHHL", 
                "SWKeyExpectedPath": "firmware:nic"
            }
        ], 
        "SchemaVersion": "2.0.0.0", 
        "SupportedProducts": [
            {
                "Family": "U72", 
                "Model": "HPE ProLiant Compute DL580 Gen12"
            }, 
            {
                "Family": "U71", 
                "Model": "HPE ProLiant Compute DL340e Gen12"
            }, 
            {
                "Family": "U66", 
                "Model": "HPE ProLiant Compute XD230 (U66)"
            }, 
            {
                "Family": "U70", 
                "Model": "HPE ProLiant Compute DL380a Gen12 (U70)"
            }, 
            {
                "Family": "U72", 
                "Model": "HPE ProLiant Compute DL380a Gen12 (U72)"
            }, 
            {
                "Family": "A59", 
                "Model": "HPE ProLiant Compute XD685"
            }, 
            {
                "Family": "U74", 
                "Model": "HPE ProLiant Compute XD230 (U74)"
            }, 
            {
                "Family": "A66", 
                "Model": "HPE ProLiant Compute DL345 Gen12 Server"
            }, 
            {
                "Family": "U68", 
                "Model": "HPE ProLiant Compute DL380 Gen12"
            }, 
            {
                "Family": "A66", 
                "Model": "HPE ProLiant Compute DL325 Gen12 Server"
            }, 
            {
                "Family": "U68", 
                "Model": "HPE ProLiant Compute DL360 Gen12"
            }
        ], 
        "UpgradeRequirements": "Recommended"
    }, 
    "PackageFormat": "FWPKG-v2", 
    "Type": "Firmware", 
    "UpdatableBy": [
        "Bmc"
    ]
}