Firmware Updates via S3/MinIO

Summary

Host firmware images and update manifests in an S3-compatible storage (Amazon S3 or built-in MinIO) for staged or immediate rollouts to your zTC fleet :contentReference[oaicite:0]{index=0}.

Prerequisites

• Firmware image files (.ima) and a corresponding manifest.json.
• An S3 bucket (Amazon S3 or MinIO) with public-read or signed-URL access to your files.
• zMAN Director configured with access to your S3/MinIO endpoint (credentials or public URLs).

Procedure

1. Upload files:
   • If using MinIO, go to **Repository → Files** and upload your .ima and manifest.json files.
   • If using Amazon S3, upload files via the AWS console or CLI and ensure the manifest URL is publicly accessible or signed.
2. Add manifest URL in MSP Admin (if used):

   https://<bucket-url>/manifest.json

3. In zMAN UI, navigate to **Firmware Updates → Add Manifest**:
   • Paste the manifest URL.
   • Click **Save**; zMAN fetches and lists available firmware versions.
4. Deploy to devices/groups:
   • Select one or more firmware entries.
   • Click **Actions → Deploy**; choose immediate or scheduled, then confirm.
5. Monitor rollout under **Tasks → Firmware**; tasks show success/failure per device.

Advanced Options

• Staged Rollout: target a pilot group first, verify stability, then expand to production groups.
• Delta Updates: if your manifest supports differential patches, enable “Delta Only” to minimize bandwidth.
• Rollback: schedule an earlier firmware version by redeploying its manifest to affected groups.

Troubleshooting

• Manifest fails to load: verify JSON syntax and that the URL is reachable from the zMAN host.
• Devices report “no update available”: ensure the manifest’s version field differs from the currently installed version on the zTC.
• Partial failures: check individual device logs under **Device Information → Metrics** for download or install errors.