I have configured RME 4.0 to use SSH as its preferred protocol for all archiving (config, software etc). I constantly get errors logged and the action is to check the credentials and whether the device can be managed. All my devices are IOS and support SSH (all except one supports SSH 2.0).
The AAA config on each device is the same (from a script) so I know it works, I have even checked manually by logging into the devices using PuTTY SSH and using the User Account that CiscoWorks is configured to use.
Logged on all the devices that are failing are messages like this:
Oct 28 16:46:24.530: SSH2 0: Unexpected mesg type received
Oct 28 16:50:34.055: SSH2 2: Unexpected mesg type received
Re: LMS 2.5 - SSH 0: Unexpected mesg type received
I have given up with SSH on LMS 2.5 (or at least in RME 4). It was so intermittent it was not worth leaving it enabled. For the small number of hosts LMS 2.5 is managing I would get about 50% failing with the message logged on the device:
Nov 22 13:29:51: SSH2 3: Unexpected mesg type received
I have reset the protocol order in RME so that SSH is now last in the list and guess what? no more failures?
Cisco must know this is a problem with RME 4? Is it likely to be fixed in the forthcoming LMS 2.5(1) release?
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...