NPM recognizes Cisco ASA 5506 as a wireless controller, not an ASA. How might one correct this problem?

I have had that happen in the past with newer models that were not properly recognized with the built in MIB.  They eventually corrected themselves after SolarWinds updated the MIBs with an update patch or new release.

You might look at the "View Type" on the edit page.  Maybe change it specifically to something like "Node Details - Summary".  then it should give more node details rather than faulty wireless controller details.

This is still an issue.  Do you know of a fix or better work around?

How about you, serena​ ?

Changing the View per your suggestion is useful, jhandberg​.  I've used it to good purpose.

I'm hoping instead that Solarwinds has a solution that doesn't require individually setting different display options for every different kind of device.  One would hope that simply adding the "Cisco ASA:  Advanced Cisco ASA Monitoring" option when editing a node in NPM would cause NPM to understand a node is an ASA to your way of thinking, and not first and foremost a wireless controller.

It has mapped the device type to the wireless controller view.  I don't know where the logic is that they use for that decision but you can over ride it by going to settings > view by device type and changing it there to the ASA view.   Out of the box unknowns, asa's, and several other device types get the wireless controller view when it seems like logic should dictate that unknown or uncategorized devices should default to the default node details view.

Agreed.  Hence my updated response and request for additional comment from others.

Thanks.

This one would be under cobrien​'s area of expertise

Looks like the current mibs database is from earlier this month: https://customerportal.solarwinds.com/info/MIB-Database

Would be curious if that sorts it (guessing not though)

rschroeder​, could you email me an SNMP walk?

Yes.  Low priority for now, but I'll get it to you when I get caught up with sixty ASA upgrades.

The solution appears to take things into one's own hands instead of relying on NPM to correctly identify the hardware and automatically set the appropriate View Type:

1. Settings
2. Manage Nodes
3. Sort by Machine Type
4. Select All ASA's
5. Edit Properties
6. Set View Type to the appropriate or desired view: