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

Trying to Add Cisco ISE (version: 3.1.0.518) to NCM (2023.1).

Hi,

I was able to add ISE node using SNMP V2, i test for snmp and gives me a success. Now i want to enable - Manage node with NCM, so i choose yes and then choose the connection profile i have,

Connection profile details,

Execute Commands and Scripts: SSH Auto

Config Request: SSH auto

Transfer Configs: SSH auto

However when i select the connection profile and click TEST, i get error - Test Failed. Connection Refused by <ISE IP add>

Do i have to enable anything on ISE ? The main purpose of adding ISE to NCM is to backup configs using the config backup job.

Find more posts tagged with

Accepted answers

nwadmin91

Thank you for your responses, the fix was to add the username/pass that NCM uses as a connection profile as a local admin account on ISE, so NCM could SSH and run config backup jobs

All comments

stuartd

I'd suggest you need to look at ACL's on the ISE - check their logs as well to see if there is any more help, but strongly smacks of the SolarWInds IP not being recognised by the ISE and getting rejected.

marcrobinson

I agree with @stuartd , and you can enable session trace logs in NCM which have more detail. Generate session trace logs for NCM and NPM modules (site.com)

I think It may catch errors before the node was entirely setup in NCM. But definitely useful to troubleshoot connection errors when NCM is enabled on a node.

nwadmin91

Thank you for your responses, the fix was to add the username/pass that NCM uses as a connection profile as a local admin account on ISE, so NCM could SSH and run config backup jobs