Zero Touch Deployment Workflow

  1. Unleashed register to UMM: For 200.8 Unleashed, you can provision the UMM IP to Unleashed during the setup wizard manually or you can provision by DHCP server option 43 automatically.
  2. When UMM receive the registration message from Unleashed, it checks whether the parameter 'Configure Template Name' is inside the message. For 200.8 Unleashed, you can provision the 'Configure Template Name' during the setup of the wizard manually or provision by DHCP server option 43 automatically.
  3. The 'Configure Template Name' is optional, Unleashed sends a blank 'Configure Template Name' to UMM if you do not provision this parameter.
  4. UMM matches the Zero Touch Deployment rule against the ‘Configure Template Name’.
  5. If UMM cannot match any Zero Touch Deployment rule, it stops the deployment and generate a 'ZTD config template mismatch' event to remind you. The Unleashed retry the registration after timeout.
  6. If UMM find any rule which contain the same 'Configure Template Name' , it pushes configuration file to Unleashed and move the unleashed to pre-defined group according to the configuration of the Zero Touch Deployment rule.
  7. UMM checks if the Unleashed is register to UMM for the first time.
  8. UMM matches the Zero Touch Deployment rule against the Unleashed AP's MAC address. This only apply to the Unleashed which is register to UMM for the first time. For example, Unleashed already register to UMM, and then customer restart 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.
  9. UMM check if Unleashed is in set-factory status.
  10. UMM check if Unleashed's software version is later than 200.7
  11. UMM apply the Default Rule only to the 200.8 or later Unleashed which is NOT in set-factory status. This is to avoid unintentional deployment. For example, if Unleashed is not in set-factory status which means the Unleashed has the setup already, then in this case we do not deploy the default configuration file to the Unleashed to avoid any mistake.
  12. UMM do not apply any Zero Touch Deployment rule and process the registration as usual.