FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
fredery
Staff
Staff
Article Id 243988
Description

In some cases with managed devices in FortiManager or FortiAnalyzer, a device is linked to a Serial Number no longer used in a cluster. This article describes typical causes and ways to resolve the issue (delete this serial number).

Scope FortiManager and FortiAnalyzer 7.X
Solution

Typical case:

There is a FortiGate HA cluster, the device was registered initially with the first FortiGate serial number FG81EP4Q00000000 and the second FortiGate Serial Number FG81EP4Q00000001.

Eventually bad luck, the first device failed and had to be replaced with a new one (RMA) with serial number FG81EP4Q00000011.

 

Instead of following the correct procedure (see related KB article:)

https://community.fortinet.com/t5/FortiManager/Technical-Note-How-to-replace-a-FortiGate-unit-in-the... )

the new device was just added to the cluster.

 

This results in the following :

 

fredery_0-1674762703559.png

 

A few remarks about this screenshot:

- Device #1 has no available action, i.e. It is not possible to delete it even if there are 2 other devices listed. This is the Device Manager normal behavior.

- It seems to indicate a 3 units cluster even if in fact there are 2 active units (#2 and #3, remember #1 is long gone back to Fortinet as it was broken).

 

 In CLI:

 

FAZ-MONTREAL # diagnose dvm device list QUEBEC
--- There are currently 17361 devices/vdoms managed ---
--- There are currently 17361 devices/vdoms count for license ---

TYPE OID SN HA IP NAME ADOM IPS FIRMWARE
faz-managed 824 FG81EP4Q00000000 a-p 192.168.245.9 QUEBEC root N/A 7.0 MR0 (418)
|- STATUS: dev-db: unknown; conf: unknown; cond: unknown; dm: none; conn: unknown
HA cluster member: FG81EP4Q00000000 (primary); conn: unknown
HA cluster member: FG81EP4Q00000001 (secondary 1); conn: unknown
HA cluster member: FG81EP4Q00000011 (secondary 2); conn: unknown
|- vdom:[3]root flags:0 adom:root (null)
...
--- End device list ---

 

Resolve the issue

 

To resolve the issue, execute the following steps:

- Take note of the serial number of an active unit and delete it under Device Manager -> [device name] -> Edit.

 

 
fredery_3-1674764412942.png

 

- In the CLI, use the command execute device replace sn <device name> <serial number> using the serial number just taken before deleting the unit.

 

fredery_6-1674764767159.png

Confirm success!

 

fredery_7-1674765397760.png

 

 

FAZ-MONTREAL # diagnose dvm device list QUEBEC
--- There are currently 17361 devices/vdoms managed ---
--- There are currently 17361 devices/vdoms count for license ---

TYPE OID SN HA IP NAME ADOM IPS FIRMWARE
faz-managed 824 FG81EP4Q00000011 a-p 192.168.245.9 QUEBEC root N/A 7.0 MR0 (418)
|- STATUS: dev-db: unknown; conf: unknown; cond: unknown; dm: none; conn: unknown
HA cluster member: FG81EP4Q00000011 (primary); conn: unknown
HA cluster member: FG81EP4Q00000001 (secondary 1); conn: unknown
|- vdom:[3]root flags:0 adom:root (null)
...
--- End device list ---