asus-esc8000-firmware-upgrade
Skill3 starsChanged yesterdayMITView on GitHub
Check and upgrade BMC firmware and BIOS on ASUS ESC8000-E12P (and similar ASMB12/AST2600 AMI-BMC ASUS servers) via Redfish and the BMC's HPM wizard API. Use when asked to check firmware/BIOS versions, update BMC or BIOS on ASUS GPU servers, or recover a BMC stuck in firmware-update/flash mode (login blocked, Redfish 503).
- Installs packages
In this repository31 other files it gives its agents.
- affix-domainsSkill
- apple-designSkill
- apwcli-pairSkill
- ask-always-on-agentSkill
- asus-esc8000-gpu-bios-tuningSkill
- build-stealth-rustdeskSkill
- chrome-cdp-setupSkill
- cua-macos-lume-sandboxSkill
- deploy-kimi-k26-on-rtx-pro-6000Skill
- deploy-kimi-k3-on-rtx-pro-6000Skill
- deploy-stealth-rustdeskSkill
- ghostty-terminfoSkill
- herdr-rename-hookSkill
- imsg-permissionsSkill
- llm-inference-benchmarkSkill
- lxd-docker-firewall-conflictSkill
- mac-mini-as-headless-serverSkill
- macos-app-multi-instancesSkill
- macos-smb-serverSkill
- mac-smb-automountSkill
- openclaw-diagnoseSkill
- paseo-profilesSkill
- private-fork-syncSkill
- refresh-claude-accountSkill
- ssh-claude-authSkill
- sync-claude-accountsSkill
- to-featuresSkill
- trusted-publishSkill
- ubuntu-lxd-gpu-serverSkill
- ubuntu-nvidia-gpu-enablementSkill
- ubuntu-zfs-mirror-installSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Update BMC first, then BIOS (paired releases).
- Distinctive: line 60
Use the KVM console (BIOS Setup Boot tab, or F8 at POST).
- Very specific: line 71
After every BIOS flash,: run efibootmgr in the OS and compare with efiboot-pre.txt.
- Very specific: line 90
After the wizard upload you MUST call PUT hpm/flash — without it the flash never starts and upgradestatus returns 500 code 1442 "Error in …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ASUS ESC8000 BMC/BIOS Upgrade
Validated end-to-end on ESC8000-E12P (ASMB12-iKVM, AMI SP-X gen13). BMC updates are host-safe; BIOS updates require the chassis powered OFF and a host reboot.
Quick start — check current + latest versions
export BMC_PASSWORD='...'
scripts/check_versions.sh <BMC_IP> # current BMC FW, BIOS, power state
scripts/check_versions.sh <BMC_IP> ESC8000-E12P # + latest versions from ASUS APIDownload zips from the URLs the ASUS API returns. BIOS zip → .HPM (BMC-flashable) + .CAP
(EzFlash only — don't use here). BMC zip → .hpm.
Workflow A — BMC firmware (host keeps running)
scripts/bmc_update.sh <BMC_IP> <BMC_fw.hpm>Does: preserve-config flags → Redfish multipart push → flash → BMC auto-reboot → version verify. ~10 min. Warning: after the BMC reboots, the host may power ON via power-restore policy — re-check chassis state before any subsequent BIOS work.
Workflow B — BIOS (chassis must be OFF)
- Save the OS boot entries while the OS is still up:
sudo efibootmgr -v > efiboot-pre.txt, and keep a copy off the host. The flash erases them (see the next section). Have the BMC KVM console working, and remove any USB stick from the host if you can. - Confirm with the operator that the host may go down; gracefully shut it down:
POST /redfish/v1/Systems/<id>/Actions/ComputerSystem.Reset {"ResetType":"GracefulShutdown"}and wait forPowerState: Off. - Flash (script enforces a power-off gate and exits update mode on any failure):
python3 scripts/bios_update.py --ip <BMC_IP> --file <BIOS.HPM> - Power on:
{"ResetType":"On"}. First POST takes 5–15 min (memory retraining).BiosVersionin Redfish flips mid-POST; then verify the OS comes back.
Update BMC first, then BIOS (paired releases). Do not run two flashes concurrently.
A BIOS flash erases the OS boot entries
Seen 2026-11-14, BIOS 0804 → 0901 with BIOS settings preserved. The settings survived, but every UEFI boot entry for an internal disk was gone. Only the entries the firmware finds by itself were left: the NIC PXE entries and any USB stick. So POST tried PXE ("Boot Error" in the SEL) and then booted a USB installer stick that was still plugged in.
- Symptom: the host never answers SSH on its tailnet or usual address, but its LAN IP answers
with a different SSH host key. That is the stick's live system, not your OS. Power the host off
(
ipmitool chassis power off) until you are ready, so nothing runs against the disks. - IPMI/Redfish one-time boot overrides do not help:
chassis bootdev diskbooted the stick again. Use the KVM console (BIOS Setup Boot tab, or F8 at POST). - Recovery: boot any Linux live system (the Ubuntu Server installer works: Help → Enter shell;
apt-get install efibootmgrif it lacks it), then recreate each entry fromefiboot-pre.txt:
Repeat per mirror disk. The installer'sefibootmgr -c -d /dev/nvme0n1 -p 1 -L "<label>" -l '\EFI\<path>\<loader>.EFI' -u "<args>" # e.g. ZFSBootMenu: -l '\EFI\ZBM\VMLINUZ.EFI' -u "zbm.import_policy=force zbm.set_hostid=0" efibootmgr -A <usb_entry> # deactivate the stick's entry efibootmgr # new entries first in BootOrderrebootmay hang (nouveau with many GPUs); useipmitool chassis power reset. - After every BIOS flash, run
efibootmgrin the OS and compare withefiboot-pre.txt.
If the BMC is bricked in flash mode (the "3ed" state)
Symptoms: web UI loads but login returns {"error":"Could not login","code":1348}
("Firmware update in progress hence login has been blocked"), Redfish 503, SSH/IPMI/KVM
ports closed. No remote fix exists once all sessions are gone — it never times out.
→ AC drain: unplug both PSU cords (or PDU outlets) 30 s, replug. BMC boots clean in ~3 min.
Prevention: never abandon the firmware wizard mid-flow; the scripts here always exit update
mode on failure, and hpm/exitupdatemode {"FWUPDATEID":N} works from ANY admin session.
Key gotchas (full details in REFERENCE.md)
Managers/Self&Systems/Selfare invalid — discover members (Managers/BMC_0,Systems/System_0).- BMC reset type is
ForceRestart; reset bounces the host ON via power-restore policy. - Redfish multipart needs THREE parts incl.
OemParameters={"ImageType":"HPM"}. - The Redfish
UpdateService/uploadpath CANNOT flash BIOS (demands an unsatisfiableBiosUpdateMethod) — use the HPM wizard API (Workflow B). - After the wizard upload you MUST call
PUT hpm/flash— without it the flash never starts andupgradestatusreturns 500code 1442 "Error in HPM Finish Firmware Upload". ipmitool hpm upgradedoes not work:0xD5refusal, and ~3 KB/s if it runs at all.- PreserveConfiguration flags default to FALSE — set them before BMC flash or lose network/users.
See REFERENCE.md for the complete API map, payloads, and error-code table.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

