HPE ProLiant DL385 Gen11 Front GPU Cages: Removal and Replacement Example
The source shows an HPE ProLiant DL385 Gen11 GPU Configure-to-order Server with GPU cages at the front. Configurations differ; use the service guide and cable diagram for the actual installed hardware. Two overview photos with management labels are replaced here by unchanged official same-model English diagrams. Other original detail photographs remain in their source order.
1. Locate the front GPU cages
The official 8-SFF front view identifies cage 1 at callout 2 and cage 2 at callout 4, with drives between them. This establishes front-cage placement without reproducing the original management label:

The original cover label gives the removal/installation diagrams and slot map. It marks left-cage slots 9–12 and right-cage slots 13–16; use the physical label and exact configuration, including the shown 180-degree right-cage orientation:

2. Prepare and disconnect the cage
Before internal work, follow HPE’s service preparation: protect server data, shut down, disconnect every external power cord and peripheral cable, allow hot parts to cool, and apply ESD precautions. Remove the required access/middle covers, air baffle and fan cage as specified for the configuration. A T-10 Torx screwdriver is required for the referenced GPU replacement. This is not a hot-swap GPU procedure.
The source opens the blue release latch, disconnects the GPU power connections and GPU/riser-to-system-board connections, then slowly pushes the cage from the rear toward the front. Its annotated overview describes two information connections per cage and a further connection for each left/right cage; those are source-photo counts, not universal port identities. The official procedure requires disconnecting all applicable GPU and front-riser cables before withdrawal.

The replacement overview below is HPE’s GPU-riser auxiliary-power routing diagram, not a translation of the source photo’s signal-cable annotation. It shows the riser power branches for the illustrated configuration:

A separate official illustration shows the4-dual-width/6-single-width GPU auxiliary-power arrangement. Match actual connectors, cable PNs and installed GPU options to the service guide; color and position alone are insufficient:

The source blue latch and cover retaining screw are shown in this detail:

3. Open the removed GPU cage
The English instruction label on the GPU cage distinguishes single-width and double-width installations. The source calls this a CPU cage in prose, but the pictured label and operation concern the GPU cage:

Release the cover retaining screw and remove/unlock the cover through the applicable illustrated motion. The following photos show the cover screw and opened cage:


4. Remove the GPU fasteners and transfer the required support
Remove the front and rear GPU retaining screws for the fitted GPU type and keep them safely. Screw/bracket arrangements differ by GPU model; the following photos identify the source’s two ends:


The source transfers the rear metal support bracket to the replacement GPU. Retain the bracket and its specified screws when required by the matching replacement kit; do not discard them or assume every new GPU has identical mounting hardware:


5. Reassemble and verify the actual fault indication
Install the supported replacement, reconnect the verified cable paths and refit the fan assembly and other removed parts through the matching service procedure. Check each fan module is fully seated; an unseated fan can prevent normal power-on. Keep fingers clear of the dense cabling and thin CPU-heatsink fins, which can cause cuts.
The source suggests checking power cabling when error 490 is reported, but its actual capture says Insufficient Fan Solution followed by 490 - System Health Error. Treat 490 as the pictured general system-health indication and inspect the IML and the full fault text; it does not identify a power cable as the sole cause:

The stored source does not include a successful post-replacement test result. Verify the actual IML, fan population/seating, GPU detection, cabling and hardware health before returning the server to service. No physical work or server action was performed during translation.
References
- https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002294en_us&page=GUID-929CE995-6F92-424C-BB15-CBA68EBDE57A.html
- https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002294en_us&page=GUID-1A6C2FB8-CEE6-4A1B-AEF7-400825D026F8.html
- https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002294en_us&page=GUID-95BCCB0D-CB47-49D4-AFC7-95919770F05B.html
- https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002294en_us&page=GUID-E0065A7E-D281-4C64-8C0C-9DF49C64AE2C.html