Fortinet FortiManager · Independent administration practice

FortiManager architecture, FGFM and onboarding

Why central management exists, how FortiManager is built (device, ADOM and policy databases), how the FGFM tunnel on TCP 541 works, how to onboard a FortiGate from either side and how to find out why one is not managed, with three hands-on labs.

90 min read9 chapters3 labs15 quiz8 scenarios15 interview Q&A

This first module is free: read the lesson and take the quiz. Labs need an account: sign up free to run up to 3 hands-on labs.

Log inStart free trial
This reading material cannot be printed. Read it on config.nwkings.com.
01

Why central management exists and what FortiManager is

What you will learn. Why managing FortiGate firewalls one by one stops working, what FortiManager is and what it is not, which words you need (device, ADOM, policy package, FGFM), and how this module is organised. Prerequisites: FortiGate basics. You can log in to a FortiGate CLI, you know what an interface, a firewall policy and an address object are, and you can read an IP address with a mask. Nothing about FortiManager is assumed.

Think of a chain of tea shops with three outlets. The owner decides a new rule: "every cup is served with a paper napkin". Without a head office, the owner phones each shop. One manager forgets, another hears "paper" as "plastic", and a month later a customer notices that the Madurai shop is different. A head office that writes the rule once and sends the same instruction to every shop fixes this. FortiManager is that head office for FortiGate firewalls.

The problem with one-by-one management

Our invented company, Kaveri Retail, has a head office in Chennai and branches in Madurai and Trichy. Each branch has its own FortiGate. Every FortiGate holds its own interfaces, address objects, firewall policies and VPN settings. With three devices you can log in to each. With three hundred, the same habit causes four problems.

ProblemWhat it looks like
DriftObject values and policy names differ a little between sites, so behaviour differs and nobody knows why.
Slow changeOne new policy means many logins; a security fix reaches the last site days later.
No single viewTo know which devices are reachable you check each one.
Weak auditNobody can easily show who changed what, where and when.

What FortiManager is

FortiManager is a separate system, often a virtual machine, that stores the intended configuration of many FortiGates and sends it to them. In this course the FortiManager is called FMG-1 and has the address 192.0.2.5. It keeps three kinds of data that you will meet in chapter 2: a list of managed devices, one or more administrative domains and the policies and objects inside them.

An ADOM (administrative domain) is a named container inside FortiManager. It holds devices and their policies, so that different teams or firmware versions can be kept apart. Kaveri Retail uses one ADOM called Kaveri. A policy package is a named set of firewall policies that can be installed to one or more FortiGates. FGFM (FortiGate to FortiManager protocol) is the management connection between the two systems; it runs over TCP port 541.

FMG-1192.0.2.5 HQ-FGT192.0.2.11 MDU-FGT192.0.2.12 TRY-FGT192.0.2.13 FGFM TCP 541

One FortiManager, three FortiGates, all on the management network 192.0.2.0/24.

What FortiManager is not

Two beliefs cause many wrong answers. First, FortiManager is not in the traffic path: user traffic from PC-MDU to the intranet never passes through FMG-1. Second, a FortiGate does not stop working when FortiManager is switched off. It keeps forwarding with the last configuration it received; you only lose central change and the single view.

Worked example. Kaveri needs the address object SRV-WEB (192.0.2.80/32) on both branches. By hand that is two logins and two chances for a typo. With FortiManager you create SRV-WEB once in the ADOM Kaveri and install it to both devices. One definition, two devices, no drift.

How this module is organised

Chapter 2 explains the architecture. Chapters 3 to 5 cover onboarding from the FortiGate side, from the FortiManager side, and finding out why a device is not listed. Chapters 6 to 8 walk through the three labs (fm-onboard, fm-add-fmg, fm-unauth-ts). Chapter 9 is the checklist.

Honest boundaries. The labs run in a simulator, not real FortiManager software. Actions such as authorize and import are GUI or API actions in the real product; the simulator offers them as execute fmgui ... commands and we say so each time. Serial numbers and build numbers are synthetic. This is independent training; it does not prepare you for a vendor exam.

The policy that reached only two of three branches

A retailer added a rule by hand on each FortiGate over two days. At Trichy the engineer typed the wrong subnet and nobody noticed for a month, until a branch user could not reach a server. With a central manager the rule is written once and the device status shows which devices already received it.

Lesson: central management removes mistakes by reducing how often a human types the same thing.

"Why would a company use FortiManager instead of logging in to every FortiGate?"

Consistency (one definition of objects and policy), speed (change once, install to many), visibility (one device list and status) and audit (revision history). Add that FortiManager is only the management plane: the FortiGates keep forwarding if it is down.

Key takeaways

  • Managing many FortiGates by hand causes drift, slow change, no single view and weak audit.
  • FortiManager stores intended configuration and sends it to managed FortiGates.
  • An ADOM is a container for devices and their policies; FGFM is the management tunnel on TCP 541.
  • FortiManager is not in the traffic path; devices keep working without it.
  • The labs are a simulator; authorize and import are execute fmgui commands there.

Upgrade to keep reading

The free plan lets you read chapter 1 of this module. Upgrade to open the remaining chapters.

  1. Architecture: three databases and the FGFM tunnel
  2. Onboarding from the FortiGate side
  3. Onboarding from the FortiManager side
  4. When a device is not listed: reading the clues
  5. Lab fm-onboard: bring the first FortiGate under management
  6. Lab fm-add-fmg: add a FortiGate from the FortiManager side
  7. Lab fm-unauth-ts: three FortiGates, three reasons they are not managed
  8. Summary and exam checklist

Join the community