Skip to main content
mhaneke
Explorer III
August 8, 2024
Question

FortiAnalyzer Cloud does not show a Fortigate although the device is connected

  • August 8, 2024
  • 2 replies
  • 5385 views

Hello,

 

a FortiAnalyzer Cloud7.4.3 b5573 does not show a FortiGate 7.4.3 b2573 although the device is connected. I checked the serial number of the cloud instance and it matches with that one connected to the Fortigate.

On the Fortigate I can switch in Log -> Forward Traffic to the Fortianalyzer and it presents all events. in the FortiAnalyzer Cloud account it says Quota is at 73%, but there are 0 devices shown.

But in the local events I see the most recent events which came from the Fortigate. Also in Log View -> Log Browse I can display the older logs from yesterday on back to archived logs from months ago.

In FortiView in Fortianalyzer Cloud it says Invalid params: No valid fabric member found.

 

But in CLI it says:

FAZVM64-VIO-CLOUD # diag log device
Device Name Device ID Used Space(logs / quarantine / content / IPS) Allocated Space Used%
FCTEMS882400XXXX FCTEMS882400XXXX 0.0KB( 0.0KB/ 0.0KB/ 0.0KB/ 0.0KB) unlimited n/a
FG100FTK2103XXX FG100FTK2103XXX 3.2GB( 3.2GB/ 0.0KB/ 0.0KB/ 0.0KB) unlimited n/a
FG100FTK2307XXX FG100FTK2307XXX 13.2GB( 13.2GB/ 0.0KB/ 0.0KB/ 0.0KB) unlimited n/aITP-FG61F FGT61FTK2101XXX 18.3GB( 18.3GB/ 0.0KB/ 0.0KB/ 0.0KB) unlimited n/a

 

best regards

Martin

2 replies

dbhavsar
Staff
Staff
August 8, 2024

Hello @mhaneke ,

Can you please share output of following command from FortiGate:
exec log fortianalyzer test-connectivity

 

mhaneke
mhanekeAuthor
Explorer III
August 8, 2024

Hello @dbhavsar 

 

(global) # execute log fortianalyzer test-connectivity
No FAZ is enabled.

and

 

(root) # execute log fortianalyzer test-connectivity
No FAZ is enabled.

But why does it show:

 

FortiAnalayzer0001.jpg

 

 

best regards

Martin

 

tpatel
Staff
Staff
August 8, 2024

Hello mhaneke
can you please provide output of below command.
exec log fortianalyzer-cloud test-connectivity
config log fortianalyzer-cloud setting
show full

mhaneke
mhanekeAuthor
Explorer III
February 25, 2025

AZVM64-VIO-CLOUD # diagnose dvm device list
--- There are currently 7 devices/vdoms managed ---
--- There are currently 7 devices/vdoms count for license ---

TYPE OID SN HA IP NAME ADOM IPS FIRMWARE HW_GenX
faz-managed 208 FCTEMS882400XXX - :: FCTEMS882400XXX root N/A 7.0 MR0 (0) N/A
|- STATUS: dev-db: unknown; conf: unknown; cond: unknown; dm: none; conn: unknown
|- vdom:[3]default flags:0 adom:root pkg:[never-installed]
faz-model 209 FG100FTK2103XXX - 10.95.13.30 FG100FTK2103XXX root N/A 7.0 MR4 (2662) N/A
|- STATUS: dev-db: unknown; conf: unknown; cond: unknown; dm: none; conn: unknown
|- vdom:[3]root flags:0 adom:root pkg:[never-installed]
|- vdom:[101]PolicyBased flags:0 adom:root pkg:[never-installed]
faz-model 205 FG100FTK23079XXX - 10.95.13.30 FG100FTK23079XXX root N/A 7.0 MR2 (1575) N/A
|- STATUS: dev-db: unknown; conf: unknown; cond: unknown; dm: none; conn: unknown
|- vdom:[3]root flags:0 adom:root pkg:[never-installed]
|- vdom:[101]PolicyBased flags:0 adom:root pkg:[never-installed]
faz-managed 192 FGT61FTK2101XXXX - 10.95.13.30 ITP-FG61F root N/A 7.0 MR4 (2573) N/A
|- STATUS: dev-db: modified; conf: unknown; cond: conflict; dm: unknown; conn: unknown
|- vdom:[3]root flags:0 adom:root pkg:[never-installed]
|- vdom:[102]PolicyBased flags:0 adom:root pkg:[never-installed]