topic Java can certainly be in Network Security

Asdm does not allow for firepower module configuration

luisaneves — Tue, 12 Mar 2019 07:14:00 GMT

Hello,

I'm seeting up a brand new, out of the box 5516x, i've followed every step of the configuration guide, configured the module in the same subnet and VLAN as the inside, but when loading asdm, which seems to take forever, it shows the firepower tabs on the dashboard, with status up and running, but the configuration sections of the module show up empty - all of them. The compatibility matrix says everything is compliant, but to no avail. The module is not configurable!

And firesite was not sold 😞

Running asa 5516x with 9.5.1, asdm 7.5.1.8, fpower 5.4.1.

Java 8 update 71, java 7 also...

The customer is already complainting and thinking about replacing it with other manufacturer.

Any thoughts?

You need to setup the

Marvin Rhoads — Wed, 03 Feb 2016 03:58:29 GMT

You need to setup the FirePOWER module to use it, even via ASDM.

Have you done so? Please follow the Quick Start guide if you haven't already.

http://www.cisco.com/c/en/us/td/docs/security/asa/quick_start/sfr/firepower-qsg.html

Firepower communicates via

Philip D'Ath — Wed, 03 Feb 2016 04:55:44 GMT

Firepower communicates via the management port. Have you definitely got that plugged in?

Yes, as i said before. Both

luisaneves — Wed, 03 Feb 2016 07:14:17 GMT

Yes, as i said before. Both management and inside interfaces are connected on the same VLAN and subnet, both addresses reachable

Yes, all those steps were

luisaneves — Wed, 03 Feb 2016 07:18:25 GMT

Yes, all those steps were followed, several times. That was even one of the official sources used.

Could it be a java based problem?

Attached are the outputs from

luisaneves — Wed, 03 Feb 2016 11:17:31 GMT

Attached are the outputs from the asdm and the config. A I stated earlier, both management and inside interfaces are connected on the same VLAN and subnet, both addresses reachable

I have a hunch we can quickly

Marvin Rhoads — Wed, 03 Feb 2016 14:30:02 GMT

I have a hunch we can quickly confirm. I notice in your one screenshot and the config file that you've customized ASDM to use port 8443. Could you try reverting it back to the default (443) and seeing if that works?

I'm suspecting ASDM is having trouble connecting to the ASA on 8443 and FirePOWER module on 443 at the same time.

Marvi, I've tried it on 443

luisaneves — Wed, 03 Feb 2016 14:53:43 GMT

Marvi, I've tried it on 443 previously... do you think I should upgrade it to a 6.0?

You can try 6.0. I've managed

Marvin Rhoads — Wed, 03 Feb 2016 15:02:22 GMT

You can try 6.0. I've managed the Kenton models (5506/8/16) with ASDM on both 5.4 and 6.0 though.

I assume you've tried a reload / power cycle. Sorry if that's a stupid question but I've learned not to assume anything. 🙂

Have you configured the module at all outside of the ASDM wizard? If not, I wonder if it's waiting for EULA acknowledgement for first time management. You can session into it via the cli and check from there.

Since it's a new 5516-X do you have TAC support?

OK, another stupid java error

luisaneves — Sun, 07 Feb 2016 17:09:15 GMT

OK, another stupid java error without any Info reported on cisco documentation . The latest java you can use is 8 update 51 and it has to be 32 bits. Tried everything from 2009 till now, and it is the most recent one that works. Damn you java, shame on you cisco

Java can certainly be

Marvin Rhoads — Sun, 07 Feb 2016 19:24:31 GMT

Java can certainly be frustrating - I've been dealing with it with varying degrees of success for about 15 years.

With respect to ASDM and FirePOWER management though, I can confirm that the latest 64-bit Java (currently Version 8 Update 72) can work with ASDM.

That's what I have working on my PC and I have managed multiple ASAs (both with and without FirePOWER) using it. (open screenshot below in new tab to see it.)

When I run into one that has issues, a quick packet capture and analysis usually reveals what the issue is (if it's not already discernible from the error message returned during the launch process).