Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
mhaneke
Contributor

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

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

best regards
Martin
best regardsMartin
11 REPLIES 11
mhaneke

Hello @tpatel ,

 

maybe I did not unterstand You right. Maybe You tell me what exactly I check in FAN cloud`s CLI.

As mentioned before the connection is setup. But I cannot see any device in FAN Cloud`s device manager. But I can see some logs from the Fortigate.

 

FAN Cloud Device manager.jpg

This happens also in all FortiView categories

FortiViewFortiView

But in Log browse it shows all logfiles from the Fortigate also the most recent logs.

log browselog browse

 

best regards

Martin

best regards
Martin
best regardsMartin
mhaneke
Contributor

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]

best regards
Martin
best regardsMartin
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors