This article will assist you with troubleshooting discover using telnet or ssh.
Troubleshooting Questions:- Can you ping the device from the server you are having difficulty discovering?
- Can you ping the server from the device?
Note: If you can ping the devices, or may have discovered the device, but ping still does not work from within the application - Check to see if the device has the ICMP management interface. Managed Resources > right-click > Edit > click on Management Interface Tab. If the device is missing ICMP management, simply add the interface and resync the device.
- Is your system permitted access to the device (on the Access Control List)
- Are firewalls blocking access to the device(s)?
- Is any other software on the application server host causing a port conflict?
- Is SNMP is configured on the target device and read/trap, write community strings?
- Is SNMP correctly set up? see {Troubleshooting SNMP}
- Is Telnet or SSH configured on the target device and can you Telnet / SSH to the device through a command-line shell or an application like puTTY?
- Are authentications created in the Authentication portlet with protocols and passwords set correctly, with adequate timeout and retries configured for your network’s latency?
- Are Discovery Profiles using the created authentications?
- Did the device discover with Telnet or SSH and SNMP s successfully?
Verify Device Management Interface
Resources -> Managed Resources -> select the N2024P -> Edit > Click on Management Interface Tab
You should see something like this. The Management interfaces should list a CLI interface like Telnet or SSH
The Authentication tab will list the associated CLI credential

If missing, you can either add it here or delete and rediscover the device.
If still having issues, contact support