topic Cannot add manager in ASA in Network Security

Cannot add manager in ASA

eric.lo — Tue, 12 Mar 2019 13:02:53 GMT

I use the command "configure manager add" to add the device in Sourcefire.

After that, i see the error" could not establish a connection with sensor. Make sure the registration keys match, that the software version are compatible, and that network is not blocking the connection"

I have checked that the registration key match and the version of the ASA SF is 5.4.1.4 and that of the FireSight is 5.4.1.7. Also the network is not blocking.

Any suggestion for this issue?

Hi

yogdhanu — Thu, 23 Jun 2016 10:46:13 GMT

There can be multiple reasons for this. If you are sure that network is not blocking the traffic and registration key is right and there is no NAT in between, check the logs on both FMC and sensor.

Check the logs under /var/log/messages when you try to register from CLI

You might eventually need to open TAC case.

Rate if helps.

Yogesh

Hello,

adonadob — Wed, 06 Jul 2016 03:43:52 GMT

Hello,

Below I have listed some steps you can follow to identify the problem

Make sure that the management interface of the ASA is up
Verify connectivity between the FirePOWER module and the Management Center by using the "ping" command.
If hey are in different subnets, and the Default Gateway of the FirePOWER module is the ASA, the ASA could be blocking the connection either because a configured rule or an asymmetric routing. you can check the logs on the ASA, or run a packet-tracer to see how the traffic from the module is processed when going to the Management Center
If they are in the same subnet check the cabling, and the ARP caches of the devices since it could be a L2 issue

If after these steps you are still having problems to identify the issue, I will suggest you to open a TAC case

Hello Team,

Jetsy Mathew — Wed, 06 Jul 2016 05:24:41 GMT

Hello Team,

Does the ASA SFR version is wrong ? It should be 5.4.0.4 not the 5.4.1.4 .

Regards

Jetsy