Firepower 1010 HA not displaying "other node"

Hi all,

Don't know if this has been asked yet, but I'm running into a particularity that I'd like to get solved.

I'm not a Solarwinds administrator within the company, but a network engineer.

I want to have my firepower 1010's that are in active/standby failover mode to be able to display on eachother's page that they see the other node there. However they do show what each node separate is and the widget does show the checkmarks (config sync, status okay, etc.) but not the other node.

My configuration is correct, failover interfaces set, standby addresses set, snmp v3 works, but yet I can not have them display each other as other node. I did add one the regular way, and added the other under FW01's "add other node as monitored".

Yet they do not see each other on the page, is there a specific MIB or poller I would need to add to each to have them show it in the HA widget on each page? (SNMP poller is correct as well).

Thanks in advance,

With kind regards,

Eloy

Find more posts tagged with

asa

firepower

firepower1010

1010

Accepted answers

All comments

kaghy2

Currently I've been able to spin up 2 ASAv instances and configured failover between them, active/standby.

Been able to spin up a Solarwinds NPM eval machine/instance and in my deployment the above works somehow.

I think the deployment at the company is stopping something, but I would have no clue there.

So I'm once again, asking for help in the above, but with the added information.

stuartd

There is a long acknowledged Cisco "bug" where devices like ASA's, PIX and FirePowers in HA setups share the same SNMP EngineID. Cisco's answer was basically "meh, we don't care". It sounds like you might have hit this.

If you've fallen foul of this then from a NMS point of view it is easy to spot. ASA_Primary is scanned in and interfaces, etc are detected. Then ASA_Secondary is scanned in and that also appears just fine. However, when you go back to the Primary then either SNMP appears not to be working or the sub-aspects are greyed out.

First off, do you have separate management IPs for each node? If yes and that makes no difference then you have two other options. SNMP v2 may resolve the issue but I'm guessing you don't want to (or aren't allowed to) downgrade that so the other option is to manually edit the EngineID to make it unique.

Issue a show snmp engineid (IIRC) on each box and compare the results. Then edit with snmp-server engineID local engineid-string