You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2023. It is now read-only.
Hi sebbastien,
I verified with engineering that this field is a read-only in the SMC API. I tried updating with smc-python directly and the update is ignored, even for engines that are not initialized.
Could you help me understand the use case for updating the POS? By default when an engine registers to SMC, the SMC will automatically bind the license based on the POS. If the licenses are imported the SMC should automatically attach it and update that field. Once the SMC does that the POS field under the engine properties is no longer editable.
The one use case I can think of where the POS (at least from the SMC's view) would be when using the cloud installation server and uploading the configuration directly for zero touch deployment.
I have to deploy more than 1000 standalone firewalls, with an external interface in DHCP. All configurations will be provisioned by Ansible and Python.
Using a USB boot drive with the engine.cfg file is not an option.
Using the server installation would allow a true ZTP deployment.
For tracking purposes, just wanted to let you know this will be possible in (upcoming) SMC 6.5.4. This field will only be writable when the engine is in initial or configuration state, similar to how it works with the SMC. The node.initial_contact has an option already for "install_on_server" which will then upload to the installation cloud. I will get you an example once I can validate on 6.5.4.
Hi David,
As far as I see, it is not possible to define engine's PoS with the ansible engine module.
I need this feature for ZTP provisioning.
Do you think an implementation on your side sould be possible or maybe I need to work on a workarround with smc-python?
Best regards,
The text was updated successfully, but these errors were encountered: