cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
335
Views
0
Helpful
3
Replies
Highlighted
Beginner

ASDM was unable to load the firewall's configuration.

Hello Experts,

 

Having a bit of a problem trying to use ASDM to manage ASA5525 with FirePOWER installed. Now I now that Cisco Bug ID CSCuw54048 fixed this with a release of SFR 6.1.0 version but I'm still getting the same error when I try to login to ASDM with SFR module running.

asdm.png

We are using the following versions of the software:

ASA: Cisco Adaptive Security Appliance Software Version 9.9(2)40
SFR OS: Firepower Extensible Operating System Version 2.3(1.131)

SFR SW: 6.2.3-4 VDB 290

ASDM: Device Manager Version 7.9(2)152

JAVA: 8u221 64-bit

OS: Windows Server 2016

 

Has anybody else encountered the same problem? workarounds or solutions you did to solve this kind of issue?

I don't think we can settle using older versions of Java or using a Windows 7 machine to login to ASDM to if anyone has ever solved this, appreciate if you could share it.

 

Thanks in advance.

Regards,

Rex

Everyone's tags (4)
3 REPLIES 3
Engager

Re: ASDM was unable to load the firewall's configuration.

hi,

are you connecting to ASDM via the MGMT interface?

is HTTP enabled on the ASA? post a show run http output and ensure there's a route/can ping to the PC/NMS IP.

Beginner

Re: ASDM was unable to load the firewall's configuration.

@johnlloyd_13 

We are connecting to ASDM via a dedicated interface. HTTP server is enabled and we can access this firewall ok. ASDM loads fine if we are using Java 8 update 51. But due to security concerns, we can't settle using an older version of Java so I'm wondering if Cisco has come up with fix or any other workaround on this particular case.

Hall of Fame Master

Re: ASDM was unable to load the firewall's configuration.

Is it an option for you to upgrade the Firepower module to a later build (like 6.2.3.14 if not the latest 6.4.0.3)? Perhaps temporarily using an older Java if that's possible.

I know the bugID indicates 6.1.0 (released August 2016) fixed the issue; but I suspect that it may still be broken in your 6.2.3.4 (released August 2018).