After the installation completes, reboot the FI. Once back in the UCOS CLI (ucs-A#), verify the hardware identity:
ucs-A# scope chassis 1
ucs-A /chassis # show inventory
The asset or serial tag (like your example 8621000014sgn161) should appear. If your actual system uses that ID, you can now register it with Cisco Smart Licensing and apply the correct support entitlements. bootable ucsinstall ucos unrst 8621000014sgn161
To change or confirm the asset tag:
ucs-A# scope security
ucs-A /security # set asset-tag 8621000014sgn161
ucs-A /security # commit-buffer
Custom Script or Embedded System Command
Some industrial or network appliances have manufacturer-specific recovery shells where ucos is the OS name and unrst clears reset flags. After the installation completes, reboot the FI
Lab/Test Environment Key
Could be a one-time boot token for a locked device (e.g., “8621000014sgn161” as a challenge code). The asset or serial tag (like your example
If you're looking to develop a feature (possibly a software tool) that automates the creation of this bootable installation media, here are some steps: