Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

adding security appliance to NCM

I am having several problems adding the ASA's to the NCM

1. Added the device successfully via the ORION consule but its not showing up in NCM (asa5520)

2. The device show up in NCM but receiving error when try and downloading the config (unable to log into router : timeout . Device IP)

3. Having problems adding the device to NCM (asa5585) - I could however add the IPS's associated with the 5585 and download the configs without any problems.

Any help would be greatly appreciated

Find more posts tagged with

Accepted answers

All comments

scubabubbles

I did try and refresh the Node list in NCM but its not importing the newly added devices.

Also have problems with a old Pix firewall. Its in the node list in the Orion console but not in the NCM.

seigniory

The ASA has no concept of a "read only" SNMP string. Knowing that, it seems counterintuitive that the fix is so put the device's RW string in the RO field in NCM - and to leave the WR field in NCM blank.

Cheeseboard

I had the same problem and found the settings that worked for me were:

Enable Level: enable

Device Command Template: Cisco Adaptive Security Appliance

Execute Scripts/Request Configs Using/Transfer Configs Using: All set to SSH auto

I think the most important one was setting the Enable Level to just enable rather than the default of enable 15. I only realised this was the solution after I'd right clicked in the Device Details page and selected Vlaidate Logon Information and up popped the message advising that enable 15 wasn't supported on ASA's and that you should use straight enable. : )