LMS 3.2 not archiving configuration (Suspect SSH)

[shaanismath]

I have 8 devices added to RME 4.3.1 (LMS 3.2), 3 devices are running telnet and their configs are backed up fine. However the other 5 devices are running SSH and when i do sync archive, I get this message..

CM0151 PRIMARY STARTUP Config fetch failed for test-switch Cause: TELNET: Failed to establish TELNET connection to 10.150.208.7 - Cause: connect timed out. 
Failed to fetch the configuration. Check the dcmaservice.log for details. 
TFTP: Failed to fetch config using TFTP. 
Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.

I have added telnet ssh and tftp to the list of fetch protocols. Any suggestions on how I can go about troubleshooting this?

[Joe Clarke]

As the error says, it would be helpful to see the dcmaservice.log.  You should also check the basics.  Make sure the username, password, and enable password credentials are correct in DCR.  Go to Common Services > Device and Credentials > Device Management, and export the current DCR data.  Use those credentials to SSH to the devices in question from the LMS server.  Verify you can enter enable mode, and execute "show running" properly.

[shaanismath]

Sorry Joseph, I should have mentioned I checked them both without

finding much additional information.

This is the result of the device credentials check for the device in

question.

Device Name ReadCommunity Read WriteCommunity SNMPv3 Telnet Enable

by Telnet SSH Enable by SSH

test-sw2 Ok Ok No Value To Test Failed to connect. Did Not Try Ok(Primary

Successful) Ok(Primary Successful)

test-sw1 Ok Ok No Value To Test Failed to connect. Did Not Try Ok(Primary

Successful) Ok(Primary Successful)

I can install an SSH program on the LMS server and SSH to the device with

the credentails on the server straight into privileged mode and do show

running.

I have attached a sanitized version of the archive management debug for your

reference.

TIA

On Mon, Feb 7, 2011 at 12:40 AM, jclarke <

[Joe Clarke]

It looks like you do not have specific device support for this device in RME.  Go to Common Services > Software Center > Device Update, check the boxes next to Common Services and RME.  Download and install all available updates.  If that fails, you most likely have a string in your config that is fooling the parser into thinking there is an error.

[shaanismath]

Performing a device update did the trick. Thank you.

On Mon, Feb 7, 2011 at 11:06 AM, jclarke <