Rebooted FortiManager and devices with a specific config did not reconnect

[adeboer]

Basically what the title states. I have a 5.0.10 adom and a 5.2.2 adom. I rebooted the FortiManager and the devices in the 5.2.2 did not reconnect to the FM and the only way I got them to reconnect is by logging into the devices and sending the request again.

Do I have a setting wrong on the 5.2.2 boxes or?

[scao_FTNT]

Is that 5.2.2 FGT behind NAT or directly reachable from FMG (or if FGT is using VIP?)

Thanks

Simon

[adeboer]

The FGTs are setup in transparent and they are sitting behind a router/modem. The FGTs on 5.0.10 did not have an issue reconnecting to the FM. The FGTs on 5.2.2 are the ones not reconnecting to the FM after the FM reboot. 

[adeboer]

Our domain name is still there and its showing not managed.

All these devices whether 5.0.10 or 5.2.2 are in the same environment. (remote locations behind modem/router)

[scao_FTNT]

so when you "logging into the devices and sending the request again.", did you still see FMG IP in FGT "Central Management" config page?

and from your described topology, seems FMG can not directly reach that 5.2.2 FGT? how about that working 5.0 FGT, also behind NAT?

Thanks

Simon

[scao_FTNT]

I see, it is for the FQDN address

I saw FOS side has a bug mentioned for when using FQDN (using IP is OK), can not re-connect to FMG, reported for FOS 5.2.0 and 5.2.2, but said OK for FOS 5.2.3, I will double check that issue status

Thanks

Simon

[adeboer]

Ahhh...I will test with our IP right now and see what happens. 

I'll reply back here shortly.

[adeboer]

Brilliant! Changed to IP/rebooted FM and the device stayed connected.

Thanks a ton!

[adeboer]

Let me know if you find that bug listed anywhere. I've been searching the release notes without any luck.

[scao_FTNT]

FOS 5.2.3 seems still has issue, and is tracking with FOS team for an update

Thanks

Simon