Technical Tip: Autoscale sync behaviour change from secondary members in FortiGate
| Description | This article describes the FortiGate autoscale sync behaviour change from secondary members in v6.4.x or higher. |
| Scope | FortiGate-VM. |
| Solution | In v6.2.x, the autoscale feature did not allow changes on the secondary device (before called slave) to affect the primary device (called master).
In v6.4.x and v7.x+, all changes done on the secondary device DO affect the primary device. In the example below, the primary DNS was set to 1.1.1.1 on the secondary device (slave).
Checking the primary device (master), the DNS settings were updated.
Note: In v7.x+, the word 'master' was replaced by 'primary'.
|
