All passwords inside the configuration file are in the encrypted form, not recoverable to clear text. This does NOT pull the Full Configuration, just the things configured by users (and good it is so). You can use either sys_config or fgt-config, this pulls the same configuration. You can back up either single or multiple-vdom configuration, just make sure your user has prof_admin profile. But at the very least, do the good old SCP backup which is available like forever.Įnable back up configuration via SCP pull: Also starting with 5.x firmware, we can schedule auto script to run backups. But many ways to back up are available, look into # execute backup. I use good old RANCID which does the job just great. Use some automated backup solution for insurance. There are no policy install or commit the change intermediate steps. Typing almost automatically " next/end" on the CLI implements the change, and for many commands just typing in activates them. Unlike many others (but like some other others too) there is not much of a foolproof mechanism when changing the configuration. While it is true for any gear, it is especially so for Fortigate.
Feel free to leave your comments below and/or share. All opinions are mine only and are not supported neither by Fortinet nor by my employer. Below are some tips based on my 10+ years working with Fortinet Fortigate firewalls for a Fortinet Gold Partner.
0 kommentar(er)
