Can't archive nexus 5010 configs (LMS 3.2)

Question

Using LMS 3.2 I can't archive configs from
our Nexus 5010 ( 4.2(1)N1(1) ) devices . I have installed
the   necessary device package Nexus.RME431.v2-4.zip. Following error occures:
*** Device Details for                          gf02na50050p                         ***
Protocol ==>                          Unknown / Not Applicable
Selected Protocols with order ==>                                                                                  SSH,SCP,TFTP,RCP,Telnet
Execution Result:
RUNNING
CM0151 PRIMARY RUNNING Config  fetch failed for gf02na50050p Cause: Failed to fetch config using  TFTPFailed to establish TELNET connection to 10.92.170.214 - Cause:  Connection refused.
Action: Check if protocol is  supported by device and required device package is installed. Check  device credentials. Increase timeout value, if required.
Telnet on device is disabled, SSH enabled.
with only SSH on RME   followig error:
*** Device Details for                          gf02na50050p                         ***
Protocol ==>                          Unknown / Not Applicable
Selected Protocols with order ==>                                                                                  SSH
Execution Result:
RUNNING
CM0151 PRIMARY RUNNING Config  fetch failed for gf02na50050p Cause: Failed to get the start  tag-Building Configuration ... in the configuration.  Action: Check if  protocol is supported by device and required device package is  installed. Check device credentials. Increase timeout value, if  required.
Thanks
Igor

Answer 1

RME 4.3.1; windows platform
with one customer I have the same issue with a Nexus 5020. Software version is :
Software
  BIOS:      version 1.3.0 [last: ]
  loader:    version N/A
  kickstart: version 4.2(1)N2(1)
  system:    version 4.2(1)N2(1)
  power-seq: version v1.2
  BIOS compile time:       09/08/09 [last: ]
  kickstart image file is: bootflash:///n5000-uk9-kickstart.4.2.1.N2.1.bin
  kickstart compile time:  7/28/2010 18:00:00 [07/29/2010 03:10:19]
  system image file is:    bootflash:/n5000-uk9.4.2.1.N2.1.bin
  system compile time:     7/28/2010 18:00:00 [07/29/2010 07:18:12]
Hardware
  cisco Nexus5020 Chassis ("40x10GE/Supervisor")
  Intel(R) Celeron(R) M CPU    with 2074284 kB of memory.
===============
following RME packages are installed:
    SharedNetshowSS      1.1.2      SharedNetshowSS device package
    SharedSwimMDS9000    1.6.3      SharedSwimMDS9000 device package
    SharedInventoryMDS   1.5.1      SharedInventoryMDS device package
    SharedDcmaSS         2.2.2      SharedDcmaSS device package
    Nexus                2.4        Nexus device package
===============
>>> I see the following problems with SSH instrumentation of the Nexus Platform when looking into the debug file. The file I got is more or less the same then the one Marc posted.
The customer does not have a banner configured so the standard login procedure shows the following when login is done manually. RME automatically interpretes the first line after "Login as: " as a banner...
login as: Nexus
Nexus 5000 Switch
Using keyboard-interactive authentication.
Password:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
devicename#
>>> and RME wants to take the last line as the prompt, resulting in a non-fatal java exception:
[line 1471 ff.]
[ Mon Aug 30  08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Learning prompt: sA[0] == 'http://www.opensource.org/licenses/lgpl-2.1.php'
[ Mon Aug 30  08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Learning prompt: sA[1] == ''
[ Mon Aug 30  08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,printStackTrace,51,stacktracecom.cisco.nm.lib.cmdsvc.CmdSvcException: Prompt learning failed: 'http://www.opensource.org/licenses/lgpl-2.1.php' && '' do not match.
    at com.cisco.nm.lib.cmdsvc.Session.tune(Session.java:904)
    at com.cisco.nm.lib.cmdsvc.Session.tune(Session.java:833)
    at com.cisco.nm.lib.cmdsvc.AuthHandler.connect(AuthHandler.java:267)
    at com.cisco.nm.lib.cmdsvc.OpConnect.invoke(OpConnect.java:56)
    at com.cisco.nm.lib.cmdsvc.SessionContext.invoke(SessionContext.java:299)
>> Ok, RME proceeds, but the SSH implementation (SharedDcmaSS ?) cannot extract the config and a java exception occures which leads to "Closing the session":
[ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Returning from Session.send('show startup-config
[ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,in trimPrompt(), prompt == ''
[ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator,fetchConfig,490,Failed to get the start tag-Building Configuration ... in the configuration.com.cisco.nm.xms.xdi.ags.config.ConfigTransportException: Failed to get the start tag-Building Configuration ... in the configuration.
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaSS.transport.SSCliOperator.extractConfig2Buffer(SSCliOperator.java:176)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator.fetchConfig(CliOperator.java:436)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator.fetchConfig(CliOperator.java:510)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation.performOperation(SimpleFetchOperation.java:61)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.ConfigOperation.doConfigOperation(ConfigOperation.java:111)
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaSS.transport.SSConfigOperator.fetchConfig(SSConfigOperator.java:65)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.updateArchiveForDevice(ConfigManager.java:1315)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.performCollection(ConfigManager.java:3291)
    at com.cisco.nm.rmeng.dcma.configmanager.CfgUpdateThread.run(CfgUpdateThread.java:27)
[ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation,performOperation,62,FetchStatus - FAILURE for Protocol SSH for device x.x.x.x
>> As telnet and tftp are not allowed the config cannot be archived (Customer reports no problems with telnet...)
The config itself starts and ends with the following lines:
devicename# show startup-config
!Command: show startup-config
!Time: Mon Sep  6 16:41:02 2010
!Startup config saved at: Mon Aug 16 15:41:39 2010
version 4.2(1)N2(1)
no feature telnet
no telnet server enable
no feature http-server
cfs eth distribute
feature udld
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature vtp
interface mgmt0
  shutdown force
  shutdown force
  no snmp trap link-status
  no snmp trap link-status
clock timezone MEZ 1 0
clock summer-time MEZS 5 sun mar 02:00 5 sun oct 03:00 60
line console
boot kickstart bootflash:/n5000-uk9-kickstart.4.2.1.N2.1.bin
boot system bootflash:/n5000-uk9.4.2.1.N2.1.bin
ip route 0.0.0.0/0 172.16.4.1
vtp mode transparent
vtp domain sap
logging server x.x.x.x 7 use-vrf default
logging server y.y.y.y 7 use-vrf default
devicename#
For me it looks like as a bug in the ssh implementation in RME, but I cannot find a bug id on CCO ....