FortiManager is a centralized network security management solution developed by Fortinet. It provides administrators with a single platform to manage multiple Fortinet security devices, particularly FortiGate firewalls. Instead of configuring each FortiGate manually, FortiManager allows centralized control, saving time, reducing errors, and improving security consistency across the network.
Imagine you are managing hundreds of FortiGate firewalls spread across different locations. Configuring each firewall manually would be time-consuming, error-prone, and inefficient. With FortiManager, you can:
FortiManager offers several features that make it essential for large-scale Fortinet deployments:
Administrators can interact with FortiManager using three primary access methods:
The GUI is a web-based interface that provides an easy-to-use dashboard.
It includes the following key sections:
How to Access FortiManager GUI:
CLI provides a text-based command environment for advanced users.
It is useful for scripting, troubleshooting, and bulk configuration.
Administrators can access the CLI via:
Common CLI Commands:
Check system status:
get system status
View registered devices:
show device
Restart FortiManager:
execute reboot
The REST API (Representational State Transfer Application Programming Interface) allows administrators to automate tasks and integrate FortiManager with third-party applications.
It enables bulk configuration changes without manual intervention.
Example API request to fetch firewall policies:
curl -X GET "https://fortimanager-ip/api/v2/cmdb/firewall/policy"
Why Use the API?
Administrators must configure basic system settings before using FortiManager effectively.
The hostname is the unique identifier for the FortiManager device.
System time should be synchronized with NTP (Network Time Protocol) to ensure accurate log timestamps.
Example CLI command to configure NTP:
config system ntp
set server "pool.ntp.org"
set syncinterval 60
end
FortiManager must have a static IP address to be reachable.
Interfaces should be assigned to different network zones for security.
Configuration example:
config system interface
edit "port1"
set ip 192.168.1.100 255.255.255.0
next
end
Configure DNS servers to enable FortiManager to resolve domain names.
Static routes should be defined for proper network communication.
Example DNS setup:
config system dns
set primary 8.8.8.8
set secondary 8.8.4.4
end
FortiManager supports different administrator roles to enforce security and access control.
To practice FortiManager administration, you can set up a lab environment using one of the following methods:
https://192.168.1.100).The Dashboard provides an overview of:
[Screenshot: FortiManager Dashboard]
(I will generate an image representation for you upon request.)
FortiManager-Training).192.168.1.100).8.8.8.8).Lab Exercise:
Try to change the hostname in FortiManager and verify if it updates in the CLI.
Why use the CLI?
Open PuTTY or any SSH client.
Connect to FortiManager using:
ssh [email protected]
get system status
Expected Output:
show system interface
Expected Output:
config system interface
edit "port1"
set ip 192.168.1.100 255.255.255.0
set allowaccess ping http https ssh
next
end
Expected Output:
Lab Exercise:
Try to change the FortiManager IP address and verify it in the GUI and CLI.
Why use the API?
Open a terminal and execute:
curl -k -X GET "https://192.168.1.100/api/v2/cmdb/firewall/policy"
Expected Output:
Lab Exercise:
Try to create a new API user and retrieve FortiManager policies using an API request.
security_adminStrongPassword123Read-OnlyExpected Outcome:
Lab Exercise:
Log out and try logging in with the new administrator account. Check what functions are restricted.
Policy_ManagerLab Exercise:
Try creating another administrator with only read access and verify their permissions.
Why Use HA?
Connect to both FortiManager devices.
On the Primary Device (Active), run:
config system ha
set mode a-p
set group-name "FMG-HA"
set priority 200
end
config system ha
set mode a-p
set group-name "FMG-HA"
set priority 100
end
diagnose system ha status
Expected Outcome:
Lab Exercise:
Simulate an HA failover by shutting down the Primary device and checking if the Secondary device takes over.
What happens when workspace mode is enabled in an ADOM on FortiManager?
Changes to the configuration database require locking the ADOM before modifications can be made.
Workspace mode enforces change control in multi-administrator environments. An administrator must lock the ADOM before making policy or object changes. This prevents conflicting edits by other administrators. After modifications, the admin commits the changes, unlocking the ADOM so others can work. Without locking, configuration changes cannot be saved. This ensures database consistency and prevents overwriting changes during collaborative management.
Common mistake:
Candidates assume workspace mode only affects policy installation. It actually controls database editing access before installation.
Demand Score: 72
Exam Relevance Score: 82
Why might an administrator be unable to edit policies inside an ADOM even though they have administrator privileges?
The ADOM may already be locked by another administrator.
When workspace mode is active, only the administrator who locks the ADOM can edit policies and objects. Other administrators can view configurations but cannot modify them until the lock is released. This lock ensures that multiple administrators do not create conflicting changes simultaneously. If the lock remains active due to a disconnected session, it may need to be manually released by a super administrator.
Common mistake:
Candidates often assume this issue is related to RBAC permissions rather than ADOM locking.
Demand Score: 65
Exam Relevance Score: 80
Why would an organization deploy multiple ADOMs in FortiManager?
To separate management environments for different administrative domains.
Administrative Domains (ADOMs) allow FortiManager to manage multiple groups of devices independently. Each ADOM has its own policy database, objects, administrators, and configuration revisions. Organizations commonly use ADOMs to separate environments such as production vs staging, different customers in MSSP deployments, or regional network segments. This prevents configuration overlap and enforces access control. Administrators assigned to one ADOM cannot modify devices in another unless explicitly permitted.
Common mistake:
Thinking ADOMs only organize devices. They actually isolate entire policy databases and administrative permissions.
Demand Score: 70
Exam Relevance Score: 88
What is the primary purpose of revision history in FortiManager administration?
To track configuration changes and allow rollback to previous versions.
FortiManager automatically records configuration revisions whenever changes occur in the management database or when policies are installed. Each revision stores the configuration state at that time. Administrators can compare revisions, identify configuration differences, and revert to a known working state if a change causes issues. Revision history is essential for troubleshooting failed deployments and auditing configuration modifications in large environments.
Common mistake:
Some administrators think revision history only applies after policy installation. It actually tracks changes within the FortiManager database itself.
Demand Score: 63
Exam Relevance Score: 78