Skip to main content
Jeff_the_Network_Guy
New Member
August 8, 2018
Solved

Address objects cannot be displayed

  • August 8, 2018
  • 2 replies
  • 24046 views

I have two 300C Fortigates, both running v5.2.13,build762.  As of this morning I cannot access the Address objects via the web interface on either firewall.  I can access other items under the Objects node, like VIPs, or services.  If I try to access the Addresses screen under Policy and Objects I get the spinning progress indicator and it never goes away.  Neither firewall is reporting high resource utilization.  Has anyone else encountered this?  I'll probably just reboot tohe one firewall that isn't mission critical, but rebooting the other one will be tricky due the business demands.

Best answer by kphed

We have numerous devices of varying models (100Ds, 300Ds, 80Cs, 110Cs) demonstrating this issue.  It does not seem model or firmware specific as these devices are running either v5.2.11 or v5.4.x.  We have not been able to correlate any specific pattern or firmware.  We manage hundreds more devices of similar model/firmware which are not experiencing the issue.  We are leaning towards an a compatibility issue with Fortiguard services packs but unsure which specific one (IP reputation, AV/APP/IPS etc).

2 replies

Jeff_the_Network_Guy
New Member
August 8, 2018

I rebooted one of the firewalls, and the Addresses are still not visible.

Toshi_Esumi
SuperUser
SuperUser
August 8, 2018

Does it coincide with an upgrade to 5.2.13? Then likely a bug. You most likely need to downgrade to the previous version, or upgrade it to at least the next generation 5.4.x. 5.2 is already ancient. You have to migrate anyway.

Jeff_the_Network_Guy
New Member
August 8, 2018

Unfortunately, per my last conversation with Fortinet in October 2017, upgrading a 300C to 5.4 is not supported. The 300C is supported by Fortinet, just not on any "current" FortiOS.  And no, this did not coincide with the upgrade.  We upgraded almost three months ago to 5.2.13, and just started having the problem today.

Toshi_Esumi
SuperUser
SuperUser
August 8, 2018

I see. I didn't check if 5.4 supports 300C. Have you tried all possible browsers? If so this might have found a dead end.