{
    "DeviceClass": "79f0c163-0c13-4662-9dea-09235fef90cb", 
    "Devices": {
        "Device": [
            {
                "DeviceName": "HPE_MR416i-p_Gen11", 
                "FirmwareImages": [
                    {
                        "DelayAfterInstallSec": 0, 
                        "DirectFlashOK": true, 
                        "FileName": "HPE_MR416i-p_Gen11_52.30.3-5917_B.HPb", 
                        "InstallDurationSec": 360, 
                        "Order": 1, 
                        "PLDMImage": true, 
                        "ResetRequired": false, 
                        "ServerPowerOff": false, 
                        "SysPowerOn": true, 
                        "Type": "Firmware", 
                        "UEFIFlashable": false
                    }
                ], 
                "Target": "a6b1a447-382a-5a4f-1000-10e215900325", 
                "Version": "52.30.3-5917"
            }
        ]
    }, 
    "MinimumActiveVersion": "52.26.3.5487", 
    "Package": {
        "Category": [
            {
                "Lang": "en", 
                "Value": "Firmware - Storage Controller"
            }
        ], 
        "Description": [
            {
                "Lang": "en", 
                "Value": "Universal Firmware PLDM file for the HPE MR416i-p Gen11 Tri Mode Controller"
            }
        ], 
        "Divisions": [
            {
                "Divsion": [
                    {
                        "Lang": "en", 
                        "Value": "Storage"
                    }
                ]
            }, 
            {
                "Divsion": [
                    {
                        "Lang": "en", 
                        "Value": "Server"
                    }
                ]
            }
        ], 
        "Files": [
            {
                "Bytes": "7505273", 
                "DateModified": "2025-02-05T17:01:17", 
                "FileList": [
                    "HPE_MR416i-p_Gen11_52.30.3-5917_B.HPb", 
                    "HPE_MR416i-p_Gen11_52.30.3-5917_B.xml", 
                    "payload.json"
                ], 
                "MD5Sum": "76215b97964775f0810aa7b4c8117ef6", 
                "Name": "HPE_MR416i-p_Gen11_52.30.3-5917_B.fwpkg", 
                "Release": "2025-02-05T16:57:56", 
                "Revision": "B", 
                "SHA1Sum": "14d7580cc30166031d5ff3427b69f0e0071ca893", 
                "SHA256Sum": "6d0f3a5264c1e824b65a16868118f9f69abd14ad0a60da3cb139ae1a77fac545", 
                "Size": "7.16MB", 
                "TargetGUIDs": [
                    "a6b1a447-382a-5a4f-1000-10e215900325"
                ], 
                "TypeOfChange": "1", 
                "Version": "52.30.3-5917"
            }
        ], 
        "Id": {
            "Product": "b8cab2acffab4f63833f5213954deee9", 
            "Version": "dd8995ed36d5442da19b3f258e8ca789"
        }, 
        "Installation": {
            "Command": "", 
            "CommandParams": "", 
            "InstallCaps": {
                "NeedUserAction": "no", 
                "Silent": "no"
            }, 
            "PerDeviceInstallTimeSeconds": 360, 
            "RebootDetails": [
                {
                    "Lang": "en", 
                    "Value": "Reboot is not required after installation for updates to take effect and hardware stability to be maintained."
                }
            ], 
            "RebootRequired": "no", 
            "RebootRequirement": "No"
        }, 
        "InstallationDependency": {}, 
        "InstallationNotes": [
            {
                "Lang": "en", 
                "Value": "<p>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>localhost OS example:<br />\n<strong><em>ilorest flashfwpkg &lt;file_name.fwpkg&gt;&nbsp;</em></strong></p>\n\n<p>remote example:<br />\n<strong><em>ilorest flashfwpkg &lt;file_name.fwpkg&gt; --url &lt;iLO_IP_Address&gt; -u &lt;iLO_username&gt; -p &lt;iLO_password&gt;</em></strong></p>\n\n<p><br />\nThis firmware package can also be installed with the latest version of Smart Update Manager (SUM).</p>\n\n<p><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>\n\t<li>Place the Service Pack for ProLiant on a USB key using the&nbsp;<strong><a href=\"https://support.hpe.com/hpesc/public/home/driverHome?pmasr=0&amp;sp4ts.oid=1008862658\">USB Key Creator Utility</a></strong>.</li>\n\t<li>Place the desired&nbsp;firmware packages and components&nbsp;to be updated in the directory&nbsp;&quot;\\packages&quot; on the USB key.</li>\n</ul>\n\n<p>Update the firmware and software&nbsp;in the usual manner.</p>\n\n<p>&nbsp;</p>\n\n<p>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</ul>\n"
            }
        ], 
        "ManufacturerName": [
            {
                "Lang": "en", 
                "Value": "Hewlett Packard Enterprise"
            }
        ], 
        "Name": [
            {
                "Lang": "en", 
                "Value": "Firmware Package - HPE MR416i-p Gen11 Tri Mode Controller"
            }
        ], 
        "Prerequisites": {
            "RequiredDiskSpace": {
                "SizeKB": "8000"
            }, 
            "SupportedDevices": [
                {
                    "Dev": "10E2", 
                    "SubDev": "0325", 
                    "SubVen": "1590", 
                    "TargetGUID": "a6b1a447-382a-5a4f-1000-10e215900325", 
                    "Type": "pci", 
                    "Ven": "1000"
                }
            ], 
            "SupportedOperatingSystems": [
                {
                    "Major": "7", 
                    "Minor": "0", 
                    "Name": "VMware ESXi 7.0", 
                    "Platform": "vmware_esx_server", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "0", 
                    "Minor": "0", 
                    "Name": "Cross Operating System", 
                    "Platform": "oi", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "10", 
                    "Maximumbuild": "18999", 
                    "Minimumbuild": "17600", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2019", 
                    "Platform": "nt_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": "15", 
                    "Minor": "0", 
                    "Name": "SUSE Linux Enterprise Server 15", 
                    "Platform": "suse_linux_enterprise_server_x86_64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "10", 
                    "Maximumbuild": "25398", 
                    "Minimumbuild": "20317", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2022", 
                    "Platform": "nt_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": "8", 
                    "Minor": "0", 
                    "Name": "VMware ESXi 8.0", 
                    "Platform": "vmware_esx_server", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "10", 
                    "Minimumbuild": "25399", 
                    "Minor": "0", 
                    "Name": "Microsoft Windows Server 2025", 
                    "Platform": "nt_x86-64", 
                    "Sr": "OEM"
                }, 
                {
                    "Major": "9", 
                    "Minor": "0", 
                    "Name": "VMware ESXi 9.0", 
                    "Platform": "vmware_esx_server", 
                    "Sr": "OEM"
                }
            ], 
            "SupportedPlatforms": false
        }, 
        "ReleaseDate": "2025-03-04T08:22:28", 
        "RevisionHistory": [
            {
                "ReleaseNotes": [
                    {
                        "Enhancements": "<ul>\n\t<li>DMTF PLDM Redfish Device Enablement enhancements: Add support for Redfish Encryption (POST &amp; PATCH)</li>\n</ul>\n\n<p style=\"margin-left:80px\">o POST Storage.SetEncryptionKey</p>\n\n<p style=\"margin-left:80px\">o PATCH Storage[EncryptionMode]</p>\n\n<p style=\"margin-left:80px\">o PATCH/POST Volume[Encrypted]</p>\n\n<ul style=\"margin-left:80px\">\n\t<li>Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:</li>\n</ul>\n\n<p style=\"margin-left:120px\">a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)</p>\n\n<p style=\"margin-left:120px\">b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)</p>\n\n<p style=\"margin-left:120px\">c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)</p>\n\n<p style=\"margin-left:120px\">d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)</p>\n\n<p style=\"margin-left:120px\">e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)</p>\n\n<p style=\"margin-left:80px\">o POST Volume.ForceEnable</p>\n\n<p style=\"margin-left:80px\">o POST Drive.RevertToOriginalFactoryState</p>\n\n<p style=\"margin-left:80px\">o Note:</p>\n\n<ul>\n\t<li style=\"margin-left: 80px;\">PATCH Volume[Encrypted] can be issued only with option &lsquo;true&rsquo; on eligible volumes. PATCH Volume[Encrypted] with option &lsquo;false&rsquo; will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.</li>\n\t<li style=\"margin-left: 80px;\">During POST (Create) &lsquo;Encrypted&rsquo; option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.</li>\n\t<li style=\"margin-left: 80px;\">Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.</li>\n\t<li>Add MR408i-p support</li>\n\t<li>Added support for UBM10 backplanes</li>\n\t<li>Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update</li>\n\t<li>Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.</li>\n\t<li>NAND flash refresh improvements</li>\n</ul>\n\n<p style=\"margin-left:80px\">o The algorithm that posts the event &quot;System reset required&quot; after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:</p>\n\n<ul>\n\t<li style=\"margin-left: 80px;\">Before starting the Nand flash refresh: &ldquo;NAND refresh in progress: changing WB Logical Drives to WT&rdquo;</li>\n\t<li style=\"margin-left: 80px;\">After the completion of Nand flash refresh: &ldquo;NAND refresh complete: changing WT virtual disks to WB&rdquo;</li>\n\t<li style=\"margin-left: 80px;\">The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers</li>\n\t<li>RAID1 Consistency Check Event String Change</li>\n</ul>\n\n<p style=\"margin-left:80px\">o The Event String has been changed from &quot;Consistency Check found inconsistent parity on LD &lt;Ld Id&gt; at strip &lt;Strip Number&gt;&quot; to &quot;Consistency Check found inconsistency on LD &lt;Ld Id&gt; at strip &lt;Strip Number&gt;&quot;.</p>\n\n<ul>\n\t<li>Support a new controller property, &quot;Spin Down Drives At Shutdown&quot;, to control spindown of configured drives during shutdown</li>\n\t<li>Support for SCSI NVMe Translation Layer Specification version 1.14</li>\n\t<li>Added&nbsp;HPE ProLiant Compute DL380a Gen12 Server</li>\n\t<li>Support Decouple metadata&nbsp;</li>\n</ul>\n", 
                        "Fixes": "<ul>\n\t<li>Fix a00143232en_us: HPE MR Gen11 Controllers - The Component Integrity Status Is Shown As Not Supported in HPE ProLiant DL365/DL385 Gen11 Servers With AMD EPYC 9xx5 2P Configurations</li>\n\t<li>Fix a00144054en_us: HPE MR Gen10 Plus and Gen11 Storage Controllers - Updating the SAS/SATA/NVMe Drive Firmware May Not Succeed When the System Boots to the VMware ESXi Operating System</li>\n\t<li>Fix a00142857en_us: HPE MegaRAID Storage Administrator (MRSA) - Unexpected Information Displays in the HPE MRSA When Heavy I/Os Are Active</li>\n\t<li>Fix an issue that CM7 FIPS drives are not identified as SED capable drives. CM7 FIPSdrive Model Number: VO001920YXUHU,VO003840YXUHV,VO007680YXUJA,MO001600YXUJB, MO003200YXUJC, MO006400YXUJD, VV007680LYJKF,VV015360LYXMT, MV003200LYJKH, MV006400LYJKK.</li>\n\t<li>Fix an issue that foreign drives import with invalid security key with 5 attempts causing controller into infinite loop</li>\n\t<li>Fix an issue that controller may assert when there is MCTP traffic when PCI BAR update&nbsp;is in progress</li>\n\t<li>Fix an issue that Redfish Drive.CapableSpeedGbs shows as 22 instead of 22.5 for SAS4 drive</li>\n\t<li>Fix an issue that the number of logical drives created is less than the expected when creating multiple Logical Drive in the same command with ReuseTargetId option</li>\n\t<li>Fix an intermittent issue that pinned cache may not generate in multiple logical drive Config</li>\n\t<li>Fix a rare issue that offline drive firmware download timed out due to host taskmanagement but still generate download complete event</li>\n\t<li>Fix an issue that RAID5/50/6/60 logical drive performance may be lower when there is cache offload happened before server bootup</li>\n\t<li>Fix an issue that controller may fault and recovery with OCR (online controller reset) while running Patrol Read on NVMe drives</li>\n\t<li>Fix an issue that Maximum Write Same Length or Maximum Unmap Block Descriptor Count of NVMe JBOD drive may be overwritten and cause SCSI UNMAP or WRITE SAME command failed</li>\n\t<li>Fix a rare issue that UR (Unsupported Request) for PCIe Memory Read may occur when host configure PCIe BAR at run-time</li>\n\t<li>Fix an issue that SCSI UNMAP command using a parameter list length greater than 0 and less than 8 would fail with SCSI Sense key Illegal Request and Additional sense data of Invalid Field in Parameter List</li>\n\t<li>Fix a rare issue that controller may assert because PCI bar initialization timeouts waiting for boot message processing</li>\n</ul>\n", 
                        "Lang": "en"
                    }
                ], 
                "Version": "52.30.3-5917 (B)"
            }, 
            {
                "ReleaseNotes": [
                    {
                        "Enhancements": "<ul>\n\t<li>DMTF PLDM Redfish Device Enablement enhancements: Add support for Redfish Encryption (POST &amp; PATCH)</li>\n</ul>\n\n<p style=\"margin-left:80px\">o POST Storage.SetEncryptionKey</p>\n\n<p style=\"margin-left:80px\">o PATCH Storage[EncryptionMode]</p>\n\n<p style=\"margin-left:80px\">o PATCH/POST Volume[Encrypted]</p>\n\n<ul>\n\t<li style=\"margin-left: 80px;\">Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:</li>\n</ul>\n\n<p style=\"margin-left:120px\">a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)</p>\n\n<p style=\"margin-left:120px\">b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)</p>\n\n<p style=\"margin-left:120px\">c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)</p>\n\n<p style=\"margin-left:120px\">d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)</p>\n\n<p style=\"margin-left:120px\">e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)</p>\n\n<p style=\"margin-left:80px\">o POST Volume.ForceEnable</p>\n\n<p style=\"margin-left:80px\">o POST Drive.RevertToOriginalFactoryState</p>\n\n<p style=\"margin-left:80px\">o Note:</p>\n\n<ul style=\"margin-left:80px\">\n\t<li>PATCH Volume[Encrypted] can be issued only with option &lsquo;true&rsquo; on eligible volumes. PATCH Volume[Encrypted] with option &lsquo;false&rsquo; will befailed because a secure volume cannot be changed to an unsecurevolume in MR firmware.</li>\n\t<li>During POST (Create) &lsquo;Encrypted&rsquo; option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume [Encrypted = true] can be issued to create a secure JBOD.</li>\n\t<li>Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.</li>\n</ul>\n\n<ul>\n\t<li>Add MR408i-p support</li>\n\t<li>Added support for UBM10 backplanes</li>\n\t<li>Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update</li>\n\t<li>Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.</li>\n\t<li>NAND flash refresh improvements</li>\n</ul>\n\n<p style=\"margin-left:80px\">o The algorithm that posts the event &quot;System reset required&quot; after a specified&nbsp; number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:</p>\n\n<ul>\n\t<li style=\"margin-left: 80px;\">Before starting the Nand flash refresh: &ldquo;NAND refresh in progress:changing WB Logical Drives to WT&rdquo;</li>\n\t<li style=\"margin-left: 80px;\">After the completion of Nand flash refresh: &ldquo;NAND refresh complete:changing WT virtual disks to WB&rdquo;</li>\n\t<li style=\"margin-left: 80px;\">The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers</li>\n\t<li>RAID1 Consistency Check Event String Change</li>\n</ul>\n\n<p style=\"margin-left:80px\">o The Event String has been changed from &quot;Consistency Check found inconsistent parity on LD &lt;Ld Id&gt; at strip &lt;Strip Number&gt;&quot; to &quot;Consistency Check found inconsistency on LD &lt;Ld Id&gt; at strip &lt;Strip Number&gt;&quot;.</p>\n\n<ul>\n\t<li>Support a new controller property, &quot;Spin Down Drives At Shutdown&quot;, to control spindown of configured drives during shutdown</li>\n\t<li>Support for SCSI NVMe Translation Layer Specification version 1.14</li>\n</ul>\n", 
                        "Fixes": "<ul>\n\t<li>Fix a00143232en_us: HPE MR Gen11 Controllers - The Component Integrity Status Is Shown As Not Supported in HPE ProLiant DL365/DL385 Gen11 Servers With AMD EPYC 9xx5 2P Configurations</li>\n\t<li>Fix a00144054en_us: HPE MR Gen10 Plus and Gen11 Storage Controllers - Updating the SAS/SATA/NVMe Drive Firmware May Not Succeed When the System Boots to the VMware ESXi Operating System</li>\n\t<li>Fix a00142857en_us: HPE MegaRAID Storage Administrator (MRSA) - Unexpected Information Displays in the HPE MRSA When Heavy I/Os Are Active</li>\n\t<li>Fix an issue that CM7 FIPS drives are not identified as SED capable drives. CM7 FIPSdrive Model Number: VO001920YXUHU,VO003840YXUHV,VO007680YXUJA,MO001600YXUJB, MO003200YXUJC, MO006400YXUJD, VV007680LYJKF,VV015360LYXMT, MV003200LYJKH, MV006400LYJKK.</li>\n\t<li>Fix an issue that foreign drives import with invalid security key with 5 attempts causing controller into infinite loop</li>\n\t<li>Fix an issue that controller may assert when there is MCTP traffic when PCI BAR update&nbsp;is in progress</li>\n\t<li>Fix an issue that Redfish Drive.CapableSpeedGbs shows as 22 instead of 22.5 for SAS4 drive</li>\n\t<li>Fix an issue that the number of logical drives created is less than the expected when creating multiple Logical Drive in the same command with ReuseTargetId option</li>\n\t<li>Fix an intermittent issue that pinned cache may not generate in multiple logical drive Config</li>\n\t<li>Fix a rare issue that offline drive firmware download timed out due to host taskmanagement but still generate download complete event</li>\n\t<li>Fix an issue that RAID5/50/6/60 logical drive performance may be lower when there is cache offload happened before server bootup</li>\n\t<li>Fix an issue that controller may fault and recovery with OCR (online controller reset) while running Patrol Read on NVMe drives</li>\n\t<li>Fix an issue that Maximum Write Same Length or Maximum Unmap Block Descriptor Count of NVMe JBOD drive may be overwritten and cause SCSI UNMAP or WRITE SAME command failed</li>\n\t<li>Fix a rare issue that UR (Unsupported Request) for PCIe Memory Read may occur when host configure PCIe BAR at run-time</li>\n\t<li>Fix an issue that SCSI UNMAP command using a parameter list length greater than 0 and less than 8 would fail with SCSI Sense key Illegal Request and Additional sense data of Invalid Field in Parameter List</li>\n\t<li>Fix a rare issue that controller may assert because PCI bar initialization timeouts waiting for boot message processing</li>\n</ul>\n", 
                        "Lang": "en"
                    }
                ], 
                "Version": "52.30.3-5917"
            }
        ], 
        "SWKeys": [
            {
                "Name": "03251590", 
                "SWKeyExpectedPath": "firmware"
            }
        ], 
        "SchemaVersion": "2.0.0.0", 
        "SupportedProducts": [
            {
                "Family": "U71", 
                "Model": "HPE ProLiant Compute DL320 Gen12 Server"
            }, 
            {
                "Family": "U54", 
                "Model": "HPE ProLiant DL360 Gen11 Server"
            }, 
            {
                "Family": "U65", 
                "Model": "HPE ProLiant DL20 Gen11"
            }, 
            {
                "Family": "A55", 
                "Model": "HPE ProLiant DL365 Gen11 Server"
            }, 
            {
                "Family": "U68", 
                "Model": "HPE ProLiant Compute ML350 Gen12 Server"
            }, 
            {
                "Family": "U72", 
                "Model": "HPE ProLiant Compute DL380a Gen12 Server (U72)"
            }, 
            {
                "Family": "", 
                "Model": "HPE ProLiant DL380m Gen12"
            }, 
            {
                "Family": "U54", 
                "Model": "HPE ProLiant ML350 Gen11 Server"
            }, 
            {
                "Family": "A58", 
                "Model": "HPE ProLiant DL145 Gen11"
            }, 
            {
                "Family": "U63", 
                "Model": "HPE ProLiant DL320 Gen11 Server"
            }, 
            {
                "Family": "U54", 
                "Model": "HPE ProLiant DL380 Gen11 Server"
            }, 
            {
                "Family": "U58", 
                "Model": "HPE ProLiant DL380a Gen11"
            }, 
            {
                "Family": "U72", 
                "Model": "HPE ProLiant DL580 Gen12"
            }, 
            {
                "Family": "U68", 
                "Model": "HPE ProLiant Compute DL380 Gen12"
            }, 
            {
                "Family": "I46", 
                "Model": "HPE Synergy 480 Gen12 Compute Module"
            }, 
            {
                "Family": "U59", 
                "Model": "HPE ProLiant DL560 Gen11 Server"
            }, 
            {
                "Family": "U65", 
                "Model": "HPE ProLiant ML30 Gen11"
            }, 
            {
                "Family": "A55", 
                "Model": "HPE ProLiant DL385 Gen11 Server"
            }, 
            {
                "Family": "A56", 
                "Model": "HPE ProLiant DL325 Gen11 Server"
            }, 
            {
                "Family": "A56", 
                "Model": "HPE ProLiant DL345 Gen11 Server"
            }, 
            {
                "Family": "U58", 
                "Model": "HPE Alletra 4110 Server"
            }, 
            {
                "Family": "U71", 
                "Model": "HPE ProLiant Compute DL340 Gen12 Server"
            }, 
            {
                "Family": "U68", 
                "Model": "HPE ProLiant Compute DL360 Gen12"
            }, 
            {
                "Family": "U63", 
                "Model": "HPE ProLiant ML110 Gen11 Server"
            }, 
            {
                "Family": "U58", 
                "Model": "HPE Alletra Storage Server 4120"
            }
        ], 
        "UpgradeRequirements": "Recommended"
    }, 
    "PackageFormat": "FWPKG-v2", 
    "Type": "Firmware", 
    "UpdatableBy": [
        "Bmc"
    ]
}