{
    "DeviceClass": "79f0c163-0c13-4662-9dea-09235fef90cb", 
    "Devices": {
        "Device": [
            {
                "DeviceName": "HPE IB XDR/EN 2x400GbE 1P PCIe6x16 Adptr", 
                "FirmwareImages": [
                    {
                        "DelayAfterInstallSec": 0, 
                        "DirectFlashOK": true, 
                        "FileName": "40_49_1014-900-9X81E-00EX-ST0_Ax.pldm.signed", 
                        "InstallDurationSec": 900, 
                        "Order": 1, 
                        "PLDMImage": true, 
                        "ResetRequired": true, 
                        "ServerPowerOff": false, 
                        "SysPowerOn": true, 
                        "Type": "Firmware", 
                        "UEFIFlashable": false
                    }
                ], 
                "Target": "a6b1a447-382a-5a4f-15b3-102315b30002", 
                "Version": "40.49.1014"
            }
        ]
    }, 
    "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": "9672234", 
                "DateModified": "2026-06-25T07:58:17", 
                "FileList": [
                    "40_49_1014-900-9X81E-00EX-ST0_Ax.pldm.signed", 
                    "40_49_1014-900-9X81E-00EX-ST0_Ax.pldm.xml", 
                    "payload.json"
                ], 
                "MD5Sum": "bcb32096606befaaeb6fbcbd5c600af6", 
                "Name": "40_49_1014-900-9X81E-00EX-ST0_Ax.pldm.fwpkg", 
                "Release": "2026-06-25T07:55:42", 
                "Revision": "", 
                "SHA1Sum": "41cfc210bb26cbb6fb50234b0b9dabcb93381a8e", 
                "SHA256Sum": "96895d84b76e696d3a3be87b1067f4e3fa7c55bb9d17faec2f10e586ed1b2869", 
                "Size": "9.22MB", 
                "TargetGUIDs": [
                    "a6b1a447-382a-5a4f-15b3-102315b30002"
                ], 
                "TypeOfChange": "1", 
                "Version": "40.49.1014"
            }
        ], 
        "Id": {
            "Product": "e9a39e503f934c9b9e368c25f2781cd9", 
            "Version": "e929117212c144b688c5e1f2395d660a"
        }, 
        "Installation": {
            "Command": "", 
            "CommandParams": "", 
            "InstallCaps": {
                "NeedUserAction": "no", 
                "Silent": "no"
            }, 
            "PerDeviceInstallTimeSeconds": 900, 
            "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"
                }, 
                {
                    "Major": "10", 
                    "Minimumbuild": "25399", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2025", 
                    "Platform": "nt_x86-64", 
                    "Sr": "OEM"
                }
            ], 
            "SupportedPlatforms": false
        }, 
        "ReleaseDate": "2026-07-15T04:18:05", 
        "RevisionHistory": [
            {
                "ReleaseNotes": [
                    {
                        "Enhancements": "<p><strong>The following changes and new features have been inlcuded in version 40.49.1014:</strong></p>\n\n<ul>\n\t<li>Added support for Congestion-Control histogram collection in the PCC/ZTR-RTT algorithm. After enabling this capability, customers can read RATE and RTT histogram counters for PCC-managed flows.</li>\n\t<li>Added a new parameter to the ZTR_RTTCC algorithm to define the probepacket timeout threshold.</li>\n\t<li>Firmware now supports two LEDs per transceiver module on the GB300 OSFP board. When configured for multiple LEDs per module, LED control (including the Module LED Control Register and host-visible indications) drives the correct LED for the relevant module and lane. Boards with a single LED per module are unchanged when num_leds_per_module is set to 1.</li>\n\t<li>When powering down the OSFP port, the link up/down dmesg messages were previously sent only to the primary ASIC, they are now sent to the secondary ASIC as well.</li>\n\t<li>Added support for a new packet reformat type for PSP transport packets. This reformat removes the PSP trailer and the UDP + PSP transport headers, and updates the IP Protocol field based on the PSP next_header value.</li>\n\t<li>CRDT token behavior has changed and is now persistent. Previously, debug firmware was allowed only if a CRDT token was applied temporarily, meaning it was erased after reset, or if another debug firmware was already running. Once a user moved to production firmware, a new token was required to switch back to debug firmware. With the new behavior, the token is saved to flash, meaning it remains readable via MDSR even after reset. Once installed, the token allows the user to move between debug and production firmware until it is explicitly revoked using the MDSR set command.</li>\n</ul>\n", 
                        "Fixes": "<p><strong>The following issues&nbsp;have been fixed in version 40.49.1014:</strong></p>\n\n<ul>\n\t<li>CREATE_PARSE_GRAPH_NODE incorrectly applied validation intended for WA mode, in which header_length_field_offset is adjusted by firmware. Since ConnectX-8 and newer adapters use normal mode only, these checks were redundant and could reject valid input. Validation is now mode-specific: normal-mode rules are applied on ConnectX-8 and newer adapters, while WA-mode rules are applied on older adapters.</li>\n\t<li>The firmware did not enforce the adapter limit for the number of flow match samples per parse graph node across the device. As a result, creation could succeed even when the total exceeded the hardware-supported limit. Firmware now enforces this limit before allocating samples. Creating a parse graph node that would exceed the maximum number of hardware flow match samples now fails with a &ldquo;no resources&rdquo; error.</li>\n\t<li>When Flex Parser overwrite native arc was enabled, destroying or closing a parse graph node on a native protocol arc did not restore the native protocol parser. As a result, the native parser remained unavailable on the device until a reset or another recovery action was performed. Native protocol parsing is now restored as expected when the parse graph node is closed or destroyed. Native parsers are disabled only while the Flex Parser graph owns the arc.</li>\n\t<li>A corner-case race condition triggered by DSP resets, causing the link to be unresponsive.</li>\n\t<li>A DEAD IRISC assert that could occur during TLV NV_DATA flash access by suspending the watchdog while waiting for flash IPC (until timeout), preventing the assert on TLV access.</li>\n\t<li>In rare cases, certain module types experienced link-up failures.</li>\n\t<li>After toggling all ports, one port could become unresponsive in the Receiver Detect state.</li>\n\t<li>Repeatedly writing NVCONFIG TLVs could cause excessive NV_DATA partition swaps during garbage collection. This rapid cycling could accelerate flash wear (end-of-life at 100,000 erases) and potentially render the device inoperable. Firmware now avoids unnecessary physical writes by returning OK when the requested configuration already exists in flash, and increases the maximum supported NV_DATA partition swaps from 100,000 to 200,000.</li>\n\t<li>NSM did not function reliably in multihost configurations when a DMA physical function (PF) was present.</li>\n\t<li>ICM_RES_HW_DMFS_ENCAP_H_FW was allocated per GVMI, preventing some RTTs from using it.</li>\n\t<li>Queue pairs (QPs) created during a PCC process transition could miss congestion-control (CC) information, preventing them from being fully managed.</li>\n\t<li>The LAG layer steering table had only one strict-SQ entry, causing strict no-port-select traffic to be routed to a single default port. With LOAD_BALANCE_MODE_P1=3, this could lead to link flapping because LACP packets were transmitted only from that default port. The fix expands the LAG layer steering table and adds additional strict-port entries to distribute strict traffic correctly.</li>\n\t<li>RDMA traffic could stall in large-scale deployments for certain source IP and UDP source-port combinations when DOCA PCC was active and no congestioncontrol algorithm was configured in algorithm slot 0.</li>\n\t<li>The live migration target did not receive a port state change event on the resume VHCA command. The target now generates this event so software that depends on port state is notified of any changes.</li>\n\t<li>An issue during hitless upgrade where, after the SACK generation/handler fence, firmware could mark the old port configuration ID as invalid. If SACK causes were still active, a race could cause SACK ISRs to stop unexpectedly. The fix is to always return BUSY while handover is active.</li>\n\t<li>When using multiplane ZTRCC congestion control with multiple flows, the RTT timeout counter in the PPCC register could increase even when the network was not congested.</li>\n\t<li>A firmware race condition between packet receive and QP cleanup could move a QP to error when reopening the same QP and sending the same MSN. This could occur when interrupting traffic (e.g., Ctrl+C) and running many iterations until the same QP/MSN combination is reused.</li>\n\t<li>The FMT Static PF verifier did not account for the Tools PF when verifying the DMA PF.&nbsp;</li>\n\t<li>QPs established before loading DOCA PCC could exhibit inconsistent algorithm-selected behavior between ports in LAG mode after DOCA PCC is loaded.</li>\n\t<li>One-to-one RoCE traffic using a single QP might not achieve line rate on some platforms when using the default ROCE_CC_COMPATIBILITY_MODE setting in mlxconfig.</li>\n\t<li>In some configurations with ConnectX-8 connected to an MP3 switch, the link might fail to come up on the switch side after toggling ports. In these cases, ConnectX-8 reported opcode 14, indicating detected remote faults and that the partner was not bringing the link up.</li>\n\t<li>ACS errors could occur due to a race condition when performing LDE/SBR while MCTP traffic to the device was active.</li>\n\t<li>A potential routing error when IOVAs assigned to the NIC overlap with the PCIe address space. In certain configurations, an IOVA could fall into an &ldquo;unclaimed address&rdquo; range, within a PCIe switch&rsquo;s Upstream Port (USP) window but outside any Downstream Port (DSP) aperture. Note: Since this is a kernel issue, to ensure packets are routed correctly in these scenarios, users must enable the ACS Unclaimed Request Redirect bit in the PCIe bridges&rsquo; Access Control Services (ACS) capability via the kernel.</li>\n\t<li>Partially enabling ACS enhanced capability could cause unexpected driver and system behavior. ACS enhanced capability remains disabled and will not be enabled.</li>\n</ul>\n", 
                        "Lang": "en"
                    }
                ], 
                "Version": "40.49.1014"
            }, 
            {
                "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"
            }
        ], 
        "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"
    ]
}