Skip to main content
hagenaarsp
hagenaarsp
New Member
March 30, 2026
Question

Missing routing entry's in a routing template

  • March 30, 2026
  • 6 replies
  • 280 views

Hi all,

Has anyone experienced an issue where, after a FortiManager upgrade, routing entries were unexpectedly removed from a routing template?

In our case, four static routes (including the default route) disappeared from the routing template itself — not directly from the FortiGate configuration, but from the template in FortiManager. As a result, when templates were pushed, the routes were also removed from the managed devices, causing connectivity issues.

Additionally:

  • The routes were no longer present in the template database after the upgrade
  • Re-adding them led to conflicts during install (likely due to ordering or object inconsistencies)

I’m trying to determine whether this behavior is:

  • A known issue related to template migration during upgrade
  • A change in how routing templates are handled
  • Or a one-off corruption/inconsistency

Has anyone seen similar behavior or has insight into this?

Thanks!

6 replies

AEK
SuperUser
AEK
SuperUser
March 30, 2026

Hi

What was the initial version of FMG and to which version did you upgrade it?

AEK
hagenaarsp
hagenaarspAuthor
New Member
March 30, 2026

Hi 
The initial version of FMG was 7.4.10 and the FMG is now running 7.6.6
It concerns a FMG-VM64-VIO-CLOUD

AEK
SuperUser
AEK
SuperUser
March 30, 2026

The upgrade path is correct, and I don't find such symptom in the known issues on the release notes.

What is the FortiOS version?

AEK
hagenaarsp
hagenaarspAuthor
New Member
March 30, 2026

It's v7.2.12 build1761 (Mature)

mavill72
mavill72
New Member
March 30, 2026

What you’re describing lines up with bug 897157: “Unexpected changes in existing static routes created by static route template after upgrade” (listed as a known issue for FortiManager 7.4.0 and fixed in 7.4.1).

https://docs.fortinet.com/document/fortimanager/7.4.0/release-notes/454729/known-issues

https://docs.fortinet.com/document/fortimanager/7.4.1/release-notes/972111/resolved-issues

 

In practice we saw routes disappear/shift at the template level and then get pushed out, and reinstalling produced “conflicts” because the entry order/IDs no longer matched what FMG thought was on the device.

What worked for us was:

  • Upgrade to the fixed build (or at least get on a version where 897157 is resolved).
  • Take a good backup before any further ADOM upgrades/migrations.
  • If you must re-add routes, do an install preview and check for mismatched entry IDs in router static.
  • If the device DB feels “off”, retrieve from the FortiGate (and/or TAC-assisted DB sanity checks), then push again.

Given you lost the default route, I’d also treat it as a “open TAC case” moment so you don’t get bitten by a second corruption later.

SkylarDe
SkylarDe
New Member
March 31, 2026

That is definitely a strange one - routing templates are usually pretty straightforward until they decide to hide entries. Have you checked if there's a specific filter active or if the GUI is just failing to sync the backend config? Sometimes a quick logout/login or checking the CLI to see if the entries actually exist in the config helps narrow it down.

Terms & ConditionsAccessibility statement