Message from log file for the nightly run:
WAE-CHN.arrisi.com (10.88.16.2):
ERROR: Cannot download Running config : Connection Refused. Device IP: 10.88.16.2
"Validate Login Information..." from the console results in a succesful login.
Average round trip time between the NCM server and device being backed up is 225ms.
NCM is successfully backing up at least a dozen other Cisco WAE devices.
NCM is successfully backing up two Cisco routers, 4 Cisco switches, and a Cisco firewall at this site.
ssh to the device, "terminal length 0", "show run" will result in the ssh session locking up.
I have tried many combinations. Here are the results:
windows 7 SP1, putty Release 0.60 and Release 0.61 – session locks up
windows 7 SP1, Tera Term Web 3.1 – session locks up
Windows Server 2008 R2 SP1, putty Release 0.60 – session locks up (NCM server, KIWI server)
Windows Server 2003 R2 SP2, putty Release 0.56 – session locks up.
Windows XP SP3, ,putty Release 0.60 – session does not lock up
Ssh from other Cisco devices (both local and remote to the site) – session does not lock up
I compared every putty setting I could find on the Windows XP SP3 machine with those on the Windows 7 SP1 machine. All putty settings I could find matched.
I'm trying to move from KIWI to NCM. So, I'm still running KIWI (on another server).
KIWI has no problem pulling the configuration from this device.
Solarwinds support said the fact the KIWI works with this device but NCM doesn't is interesting.
You might want to post that to thwack.
Running NCM V6.1
Anyone have any ideas on why NCM isn't working?
