-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create device with PSK instead of serialnumbers #22
Comments
Correct, it’s not supported in the current build. I’ll have a look and see if it can be implemented easily. |
Thanks! We are going to roll out around 3000 Fortigates, so this would really help us out if it was possible :) |
sounds like an interesting project. i've made a quick test build here https://github.com/tmorris-ftnt/tmorris-ftnt.github.io/raw/master/ztptool-v1.0.15psk-beta-win.zip to use this in the Device_SN column put "PSK" then create a new column called "Device_PSK" and put the PSK you wish to use in there.. |
That worked really good, huge thanks :) However, it doesn´t seem to be able to assign a pre-run CLI template (FMG 7.0.4) and due to that the policy package fails to install. "Assign CLI Template "SV_PreRun_40F" successful" If we assign the prerun and policy package after the import, everything works but we then need to run the install wizard for the policy package. Thanks! |
does the task monitor with in FMG give you any clue as to why the policy package install fails? Is there an SD-WAN or VPN template or anything involved? |
Yes, it is depending on interfaces we create in pre-run scripts so it fails due to that not assigned. We also have a template group contain both CLI, System and SD-WAN. |
Ok, im not really sure with out looking at it. You can drop me a line via email (tmorris at fortinet.com) and send me more info (the xlsx file for example) or we can setup a screen share if you like. |
Can´t see it´s possible to create a device without serialnumber and instead use a key. Would that be possible somehow?
The text was updated successfully, but these errors were encountered: