Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
vpn_manager [2018/10/17 16:45]
hzheng
vpn_manager [2018/10/17 16:52] (current)
hzheng
Line 1: Line 1:
 ====== Background ====== ====== Background ======
-  At the early age of FortiManager , there a VPN Console which is a IPSec VPN Wizard across many FGT . Unless the "IPSec VPN Wizard"​ on FGT -- it is to configure a single FGT . FMG VPN Console try to handle higher level topology and generate configure file across many FGTs.  At 2011 , there a customer try to use VPN Console to configure a site to site , hub to spoke topology , total 200+ FGTs , they found the VPN Console need a week to generate configure and when add 201 FGT , all configure for all FGTs need regenerate again . The new Top3 case 1459 has been created to address the customer requirement . Later , Top3 case 1552 for Dialup topology and rename to VPN Manager ​+  At the early age of FortiManager , there a VPN Console which is a IPSec VPN Wizard across many FGT . Unless the "IPSec VPN Wizard"​ on FGT -- it is to configure a single FGT . FMG VPN Console try to handle higher level topology and generate configure file across many FGTs.  At 2011 , there a customer try to use VPN Console to configure a site to site , hub to spoke topology , total 200+ FGTs , they found the VPN Console need a week to generate configure and when add 201 FGT , all configure for all FGTs need regenerate again . The new Top3 case **1459** has been created to address the customer requirement . Later , Top3 case **1552** for Dialup topology and rename to VPN Manager ​ 
 +  * add cache feature , when add new VPN Node , only generate relate configure ​
   * add mode-cfg with forticlient support   * add mode-cfg with forticlient support
   * add dual-interface support   * add dual-interface support