Zero Touch Deployment Workflow
- Registering Unleashed to UMM : For 200.8 Unleashed, you have the option to provision the UMM IP to Unleashed during the setup wizard, either manually or automatically through the DHCP server option 43.
- When UMM receives the registration message from Unleashed, it checks for the 'Configure Template Name' parameter. For 200.8 Unleashed, you have the flexibility to provision this name during the wizard setup, either manually or automatically using the DHCP server option 43.
- The 'Configure Template Name' is optional. If you do not provision this parameter, Unleashed sends a blank 'Configure Template Name' to UMM.
- UMM matches the Zero Touch Deployment rule against the 'Configure Template Name.'
- If UMM cannot match any Zero Touch Deployment rule, it stops the deployment and generates a 'ZTD config template mismatch' event as a reminder, and the Unleashed retries the registration after the timeout.
- If UMM finds any rule containing the same 'Configure Template Name,' it pushes the configuration file to Unleashed. It moves the Unleashed to a pre-defined group according to the configuration of the Zero Touch Deployment rule.
- UMM checks if the Unleashed is registered to UMM for the first time.
- UMM matches the Zero Touch Deployment rule against the Unleashed AP's MAC address. This only applies to the Unleashed, which registers to UMM for the first time. For example, if the Unleashed already registers to UMM, and then the customer restarts the Unleashed AP after start-up, the Unleashed will register to UMM again, but UMM won't apply the Zero Touch Deployment to the Unleashed since it's not the first time registration.
- UMM checks if the Unleashed is in set-factory status.
- UMM checks if the Unleashed software version is later than 200.7
- UMM applies the Default Rule only to the 200.8 or later Unleashed that is NOT in set-factory status. This is to avoid unintentional deployment. For example, if Unleashed is not in set-factory status, which means it has the setup already, then in this case, we do not deploy the default configuration file to Unleashed to avoid any mistake.
- UMM does not apply any Zero Touch Deployment rule and processes the registration as usual.
