Overview

This test case validates the most critical function for managing a large fleet of devices: remote OS/firmware lifecycle management. It ensures that an administrator can safely and reliably deploy firmware updates from zMAN to keep devices secure and up-to-date.

The test covers the end-to-end process: adding new firmware to the management server, deploying it to devices (both immediately and on a schedule), and—most importantly—verifying the device’s built-in recovery mechanism in the event of a failed update. This confirms that the fleet can be maintained without requiring costly and time-consuming physical intervention. 🔄

zTC/zMAN Configuration (Firmware Preparation)

This setup is performed by a zMAN administrator or locally to make a new firmware version available for deployment.

1. Host the Firmware Files (On-Premises Method):

        Firmware Update from zMAN,

1. • Log into the zMAN MinIO console (e.g., https://<zMan-IP>:7080/minioconsole/login).
   • Create a new bucket (e.g., ztc-firmware) and set its access policy to public.
   • First, upload the new firmware image file (e.g., ztc-firmware-1.2.1378.bin) to the bucket.
   • After uploading, get the public share link for the .bin file.
   • Edit the corresponding manifest.json file and paste the link to the .ima file in the “path” field.
   • Upload the now-edited manifest.json file to the same bucket.
   • Get the public share link for the manifest.json file.

Firmware update from both local and from zMAN,

1. • Log into Amazon s3 cloud (e.g.,https://d1u6sykyq68ega.cloudfront.net/).
   •  Create a new bucket (e.g., with company name default will be Amzetta, zTC3150L/3350/amzetta/ ) and set its access policy to public.
   • First, upload the new firmware image file (e.g., ztc-firmware-1.2.1378.bin) to the bucket.
   • After uploading, get the public share link for the .bin file.
   • Edit the corresponding manifest.json file and paste the link to the .bin file in the “path” field.
   • Upload the now-edited manifest.json file to the same bucket.
   • Get the public share link for the manifest.json file.
2. Add Firmware to zMAN:
   • Log into the zMan MSP Admin site (e.g., https://<zMan-IP>:7080/).
   • Navigate to System Tools -> Firmware in the left-hand menu.
   • Add a new firmware version by pasting the URL of the manifest.json file you copied from MinIO (or the URL provided by AmZetta for cloud-based updates).

3rd Party Setup

No external third-party setup is required. This test is conducted entirely within the zTC and zMAN ecosystem. A dedicated, non-production zTC device is highly recommended for the “Failed Update” portion of the test.

Execution

1. Pre-Update Check: In the main zMAN Director UI, navigate to Device Management -> zTC Clients -> LIST. Select a target device and note its current Firmware Version.
2. Test Scheduled Update:
   • Navigate to Device Settings -> Firmware Update.
   • Use the filter or select a target device.
   • Initiate an update, select the new Target Version you added previously.
   • Choose the Schedule option and set a time a few minutes into the future.
   • Click YES to confirm. Observe the device at the scheduled time to ensure it reboots and begins the update.
3. Test Immediate Update:
   • Choose a different online device.
   • Follow the same steps as above, but select the Immediate option. The device should begin the update process within moments.
4. Test Offline Update:
   • Power off a target device.
   • Assign a firmware update to the offline device. The task in zMAN should show a “deferred” status.
   • Power the device back on and connect it to the network. Observe if it automatically starts the pending update task.
5. Test Failed Update and Recovery (Use a dedicated test device):
   • Initiate a firmware update.
   • During the flashing process (after the first reboot), interrupt the update by unplugging the device’s power cord.
   • Plug the power back in and observe the device’s boot behavior.

6. Test Firmware Update locally,

1. • Navigate to Start -> Applications -> snapOS Update.

                      Check For Update

1. • Tick check for update box and give OK.
   • The Check for Update feature will automatically search for available updates. If an update is available, a message indicating so will be displayed.
   • Once the update is downloaded, the device will reboot into recovery mode to perform the firmware update.
   • After the firmware update is complete, the system will reboot into the primary OS.

       Using URL

1. • This is the URL path field for the manifest.json file uploaded to AWS.
   • Once the path is provided, the system will download the manifest.json file and check for updates accordingly.

       Browse from Device

1. • You can copy the manifest.json file to a USB pendrive and use it to download the update.
   • Tick Browse from device box and give OK.
   • The USB media will appear under “Other Locations” in the SnapOS update UI.
   • Select the file and apply update.

 

Verification

• Firmware Deployment (Pass/Fail):
  • PASS: For both scheduled and immediate tasks, the zTC successfully downloads the firmware, reboots, applies the update, and comes back online. The new, correct version number is then reported in the zMAN Director’s device list.
  • FAIL: The update task fails in the zMAN queue, the device is unable to download the firmware file, or the update process completes but the device is still running the old firmware version.
• Scheduling and Offline Handling (Pass/Fail):
  • PASS: The scheduled update task executes precisely at the configured time. An update task assigned to an offline device correctly enters a “deferred” state and begins automatically once the device reconnects to zMAN.
  • FAIL: The scheduled task is ignored or runs immediately. The offline device ignores the pending update task when it comes back online.
• Rollback/Recovery (Pass/Fail):
  • PASS: After the simulated failed update, the device is not “bricked.” It automatically boots into the Device Recovery mode. From this safe mode, an administrator can successfully deploy a known-good firmware version (either from zMAN or locally via USB) to restore the device to a fully functional state.
  • FAIL: A failed update renders the device unresponsive and unable to boot into the safe recovery mode. The device requires manual re-imaging or physical replacement to become operational again.