Technical Tip: FortiManager High Availability DeviceDB changes on v7.2.5, v7.0 and older releases
| Description | This article describes the FortiManager High Availability behavior in FortiManager v7.2.5, v7.0, and older releases. |
| Scope | FortiManager v7.2.5, v7.0, and older releases. |
| Solution | In these releases, when a primary unit (unit A) is down and not reachable, a secondary unit (unit B) becomes the primary unit. When unit B is the only active unit, it is not possible to modify or perform any local changes like modifying already existing devices, registering new devices, modifying or creating Reports or Event handlers. In these cases, a 'Failed to edit device' notification pop-up appears.
In FortiManager v7.2.6 and v7.4.3, it is possible to perform modifications on a secondary unit while other units are not reachable.
To resolve this behavior, upgrade to FortiManager v7.2.6 or later versions.
Related article: |
