RME 4.2 FWSM Archive Config

We have noticed that on RME when collectoing Configs from FWSM devies that it opens 3 SSH connections to the FWSM.
After successful collection it closes 1 but leaves the other 2 connections open for an hour.
Why does it do 3 and why does it not terminate the other 2?
Many Thanks
Carl

There have been numerous issues with RME and stale TCP sockets.  I highly recommend you upgrade to LMS 3.2 SP1 to get all of the known bug fixes.  This is a free upgrade for you.
As for the number of TCP sockets, one is used to test for SSH and version (this is only a connection to tcp/22 and not an SSH session).  The second connection is for retrieving the config.  The third session is likely for context modules.  In this case, you're likely seeing CSCsy22242, which is fixed in LMS 3.2.

Similar Messages

  • Using LMS 3.2 to setup switches for archive config

    Is there a way in LMS 3.2 to setup switches for using the archive config feature such that the filename could be automatically set to be the switch mgmt address or hostname?
    So for the below example:
    archive
    log config
      logging enable
      notify syslog contenttype plaintext
    path disk0:switch01.archive
    write-memory
    time-period 1440
    Would there be a way to set (I'm guessing in netconfig) "path disk0:switch01.archive" with something like "path disk0:$HOSTNAME.archive" or "path disk0:$IP.archive" ?
    -Dave

    Nevermind. Figured out that there are variables in the path that I can use for this:
    $h - hostname
    $t - timestamp
    archive
    log config
      logging enable
      notify syslog contenttype plaintext
    path disk0:$h-Backup-$t
    write-memory
    time-period 1440

  • Archive config does not allow me to specify the bootflash as the path

    Hi,
    I am trying to setup up archive config on a couple of ASR 1000 routers but it wont let me specify the bootflash for path. Path to tftp works fine.
    emmansfi-1002-1#mkdir bootflash:/archive
    Create directory filename [archive]?
    Created dir bootflash:/archive
    emmansfi-1002-1#conf t
    emmansfi-1002-1(config-archive-log-cfg)# path bootflash:/archive/
    The path specified is not available
    emmansfi-1002-1#mkdir fpd:/archive
    Create directory filename [archive]?
    Created dir fpd:/archive
    emmansfi-1002-1#conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    emmansfi-1002-1(config)#archive                  
    emmansfi-1002-1(config-archive)# path fpd:/archive     
    The path specified is not available
    emmansfi-1002-1#show platform                       
    Chassis type: ASR1002             
    Slot      Type                State                 Insert time (ago)
    0         ASR1002-SIP10       ok                    3y19w         
     0/0      4XGE-BUILT-IN       ok                    3y19w         
    R0        ASR1002-RP1         ok, active            3y19w         
    F0        ASR1000-ESP5        ok, active            3y19w         
    P0        ASR1002-PWR-AC      ok                    3y19w         
    P1        ASR1002-PWR-AC      ok                    3y19w         
    Slot      CPLD Version        Firmware Version                        
    0         07120202            12.2(33r)XNC                        
    R0        08011017            12.2(33r)XNC                        
    F0        07091401            12.2(33r)XNB                        
    emmansfi-1002-1#dir
    Directory of bootflash:/
       11  drwx       16384   Aug 4 2010 08:45:04 +01:00  lost+found
       12  -rw-   208130308   Aug 4 2010 08:47:07 +01:00  asr1000rp1-adventerprisek9.02.03.02.122-33.XNC2.bin
    747777  drwx        4096   Aug 4 2010 08:46:59 +01:00  .installer
    97537  drwx        4096  Nov 11 2013 17:44:19 +00:00  core
    764033  drwx        4096   Aug 4 2010 09:14:31 +01:00  .prst_sync
    406401  drwx        4096   Aug 4 2010 09:14:39 +01:00  .rollback_timer
       13  -rw-           0   Aug 4 2010 09:15:05 +01:00  tracelogs.660
    520193  drwx        8192  Mar 19 2014 11:19:45 +00:00  tracelogs
    455169  drwx        4096  Mar 19 2014 11:02:25 +00:00  archive
    32513  drwx        4096  Mar 19 2014 11:02:35 +00:00  logging
    7860539392 bytes total (7044546560 bytes free)
    emmansfi-1002-1#

    Found this solution:
    The default "Save As" dialog in Acrobat DC is different than the dialog that you've had in earlier releases of Acrobat, it also allows you to save to the cloud and previous locations you've saved files to. It is possible that when Acrobat tries to connect to "the cloud", it runs into problems. You may want to try to turn this feature off to see if that brings your save as dialog back: Open up Acrobat's preferences, then go to the "General" category and deselect "Show online storage when saving files":

  • RME 4.3.1 not archiving configs on all devices

    As the part of the screen shot shown, I have a total of 1312 devices in the RME. The number of total devices RME tried to collect inventory adds up to that. However, the numbers it tried to archive configuration do not (581 + 116 + 23 + 58 = 778 = 1312 - 534).
    Why are so many devices missing there?
    An RME job deploying a configuration template failed on a large number of devices, which led me to discover that many devices don't have archived configuration.
    When I manually start a "Sync Archive" job from the Device Center on a device showing "Configuration Last Archived Time: No configuration archived yet", the job succeeds.
    This is a serious issue. My immediate concern is to get configuration archived on all devices. What do I need to do to get RME to do that?

    Thanks for the response.
    Yes, I have updated the device packages recently.
    Here is device package information for one of the devices that did not get config archived:
    1.
    1.3.6.1.4.1.9.1.516
    Cisco 3750 Stack
    CatGL3
    5.2
    When I try a device package update now on RME, I get "All the available package(s) at source location are already installed."
    When I try a device package update on all CiscoWorks modules, I only get one: DFMDeviceUpdates going from 17.0 to 18.0.

  • RME 4.0.6 - Archive Purge not working

    Hi,
    I have noticed that our archive purge job is failing completely, for all devices, and it appears to have been failing for some time now.
    Looking at the meesage apeparing in the Job Details for one of the devices I get:
    *** Device Details for mydevice ***
    Protocol ==> Unknown / Not Applicable
    Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings
    The Maximum time to wait for job results per device is set to 120 seconds.
    This may explain why the job takes several days to run if every device is timing out after 2 minutes.
    My assumption, obviously incorrect, is that the purge would just go through the database and look for any archives older than a year, which is what we have set the purge options to be. This message implies that RME is trying to connect to each device.
    Is it trying to connect to each device?
    Next question would be where do I start looking so that I can fix this.
    Regards
    Jeff

    Hi Joe
    Thanks for the response. I have made the change as suggested as disabled and then re-enabled the job, so I now have it running as 8597 instead of 1106.
    JobManager.properties:
    ConfigJobManager.jobFileStorage=/rme/jobs
    ConfigJobManager.debugLevel=0
    ConfigJobManager.enableCorba=true
    ConfigJobManager.heapsize=384m
    I set this running at 9:50 this morning, and with the time now at 4:14 in the afternoon, there does not seem to be a lot happening still. If I look at the job details, all devices are in the Pending list - no Successful, or failed.
    If I look at the ..\CSCOpx\files\rme\jobs\ArchivePurge\8597\1\log file i have:
    [ Mon May 24  09:50:08 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutor,getJobExecutionImpl,160, Executor implementation class com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor
    [ Mon May 24  09:50:08 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,setJobInfo,167,DcmaJobExecutor: Initializing 8597
    [ Mon May 24  09:50:10 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutor,,119,Job listener for daemon manager messages started
    [ Mon May 24  09:50:10 NZST 2010 ],INFO ,[8597],com.cisco.nm.rmeng.config.ccjs.executor.dmgtJobRunner,run,31, DMGT Job Listener running..
    [ Mon May 24  09:50:10 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,583,Notification policy is ON, recipients :
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,603,Execution policy is : Parallel Execution
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,616,Getting managed devices list from DM
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutionESSListener,run,55,ESS Message listener started
    [ Mon May 24  09:50:25 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,626,Num Threads = 1, Task = Purge Archive, Num Devices = 2696
    [ Mon May 24  09:50:25 NZST 2010 ],ERROR,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,sendMail,949,sendEmailMessage: Null recipient list
    [ Mon May 24  09:50:25 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,run,212,Job initialization complete, starting execution
    [ Mon May 24  09:50:25 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,,113,Constructing ExecutorThread DcmaJobExecThread 0
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,handleMultiDeviceExecution,143,JobExecutorThread - MultiDeviceExec DcmaJobExecThread 0 : Running
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,purgeArchive,706,Purging Archive....
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,177,PURGE SETTINGS: ByVersion = false ByAge = true PurgeLabelledFiles = false
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,201,Purge files between start time and Fri May 29 09:50:26 NZST 2009
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,207,Num Versions to keep = 0
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,208,Purge files older than 12 Months
    [ Mon May 24  10:33:50 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,handleMultiDeviceExecution,149,Completed executeJob(), updating Results
    [ Mon May 24  10:33:50 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,getNumCyclesToPoll,1018,getNumCyclesToPoll Function Started.
    [ Mon May 24  10:33:50 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,updateMultiDeviceExecResults,781,Awaiting Job results: req Id = 0 Poll time = 2022 min(s)
    [ Mon May 24  12:39:42 NZST 2010 ],INFO ,[Tibrv Dispatcher],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutionESSListener,onMessage,66,Listener waiting for message :
    [ Mon May 24  12:42:48 NZST 2010 ],INFO ,[Tibrv Dispatcher],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutionESSListener,onMessage,66,Listener waiting for message :
    Is this normal? Most of the other jobs at least give you an updated success or failure for the devcies.
    Regards
    Jeff

  • RME 4.0.5 - Archive Mgmt

    Hi All,
    I have RME 4.0.5
    My Manager said there is a possiblity to trigger a mail when a device take new backup.
    say example when there is any change then the device will be archived and create new version.
    Now when its creating new version, will it send any mail....
    Is there any ways we can configure to trigger a mail?
    Regards,
    Naidu.

    No, this is not possible.  You could configure your system config collection jobs with an email address, and you would receive email when they run, but you would not be able to see exactly which devices had a new archive entry added.  The same could be done with when the device sends a config change syslog, but again, you wouldn't know if a new archive revision was added.

  • LMS 3.2 RME 4.3.1 Archive Jobs hang

    LMS 3.2 Windows 2003 R2 8Gig RAM
    Managing ~4000 devices currently on LMS 3.1. Built new LMS3.2 server and patched to RME 4.3.1.
    Import from csv file works fine and RME inventory collection/ Campus Manager Data Collection all works perfectly.
    Archive Jobs hang (at random device #'s) after starting successfully.
    I have tried restarting ConfigMgmtServer process, rebooting, even reinit CMF, RME and ANI db and starting from scratch but issue persists.
    Are there any known issues with LMS 3.2 on Archive Jobs hanging or should I debug and open TAC case?

    Resolution Summary:Checked the dcmaService.log and found the following recurring statements.
    com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,406,Descr = 12.2(50)SE
    [ Tue Oct 26  15:58:45 CDT 2010 ],DEBUG,[main],com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,405,suppSysId = .1.3.6.1.4.1.9.1.927
    [ Tue Oct 26  15:58:45 CDT 2010
    Checked that the device IOS was well above the version specified in the logs, so thought may be an issue with the device packages.
    Checked the mdf version was 1.25 which came as default when we install LMS 3.2, so upgraded the mdf version to 1.45.
    Still the issue didn't got solved, so upgraded the RME device packages and now the archive job was successful.
    Message was edited by: Dheeraj Gera

  • Compare template with last archive config

    Hello every one,
    I would to know if there is a way to compare the last configuration of one/all equipment(s) with a template (User defined tasks)
    I explain why.
    In my compagny, if an equipements is out of service, some one replace the equipements.
    in the new equipement there is the minimal configuration for download the full configuration by remote access (netconfig job)
    but the problem is : the configuration evolve constantly, so we must uptdate templates, but we have to make sure in all templates there is the last configuration.
    thanks a lot

    Do you have any kind of network management platform, such as CiscoWorks or anything like that? Most of them do have reports/jobs you can run to compare configs.
    If you don't, then you might want to look into something like ExamDiff (http://www.prestosoft.com/ps.asp?page=edp_examdiff) to compare the configs against your template.
    Now, if you have a lot, that can get very tedious doing them one by one all the time. Its possible you could script something to automate this as well.

  • RME config archive problem - lms 3.2

    just wondering if anyone else has seen this.
    about a month or so ago, I grabbed about 6 or 7 patches for our ciscoworks machine, across cm, rme, and cs. (yeah, we were a little behind)
    after applying these patches, it seems, all of the 2960s and 4948s are failing the config archive with the following:
    cm00139: could not archive config:cause: action: verify that device is managed and credentials are correct. Increase timeout
    value if required.
    so I've triple checked the credential set applied to these devices, adjusted timeout and retry values, and have gotten nowhere.
    Deleting these devices doesn't seem to help, they are rediscovered just fine, but the config archive continues to fail.
    Other than maybe trying to reinstall the rme patches (or uninstall) that were recently applied, I'm out of ideas. This is LMS 3.2.1 with
    cm 5.2.2
    cs 3.3.1
    rme 4.3.2
    running on windows server 08.
    So if anyone may have seen this and/or has any advice, I'd appreciate it. Thanks - chris

    ok, so it's been a year and a half since last post. So in addition to the above mentioned archive failures with the 4948s, the 4948s were also showing up in config out of sync summary. The only difference that were showing between running and startup was the ntp clock period.
    I did see that the clock period statement was in the exclude list for routers and a bunch of other things, but not for the 4948s. I added this as an exclusion yesterday. Today when I checked, all 4948s are archiving now, and are off the out of sync report. Never would have crossed my mind to check there, but that exclusion seems to have done the trick. Maybe someone else can use this if they're seeing the same thing. - chris

  • RME Issues: Config Status & Config Archive

    Hi All,
    1. While trying to generate Device Manageability Status Report, I noticed that the Config Status of all devices is Failed. The reason for the failure on all the device is as follows:
    Failed to establish TELNET connection to 10.180.9.172 -Cause: Authentication  failed on device 3 times Failed to detect SSH version running on the device.
    Can anyone help with the solution to this?
    2. Also, the RME Collection Status as shown in the attachment shows that no archive was successfully collected on any of the devices. How can I resolve this issue?
    3. How do I generate a report of Configuration Changes performed by users from RME?
    Thank you in advance.

    This error typically means you have not filled in the correct credentials for the devices in DCR.  In order to fetch configs from devices you need to populate the SNMP read-write credentials and/or the telnet/SSH username, password, and enable password.
    Once you have configs getting archived, and assuming you're sending syslog messages from your devices to RME, you can run a Change Audit (within RME) report to see the config changes that have been made by your users.

  • RME 4.2 Inventory with no SNMP for FWSM

    Looking at trying to get Config Archives setup for FWSM and ACE modules however we have SNMP
    restricted in this portion of the network.
    I understand that inventory polling must be present to get the devices into RME - is there a way we can get around not having SNMP for this inventory - a manual method maybe or some loophole we can work around?
    Also will syslog work from these devices to RME?

    To get the config archives, you simply need the telnet or SSH credentials in the DCR. Not having SNMP access will restrict RME from gathering device information for inventory collection and the device type will show up as "?" in the DCR.  Syslog is used to trigger a sync archive if changes occurred but you will need to define the syslog server settings on the FWSM.

  • LMS 3.2: RME failed archive with Nexus 5010

    Hi,
    LMS 3.2, RME 4.3.1, dev packages updated, Windows.
    We would like to archive the configuration of the Nexus 5010 switches. Due to authentication with Radius based on tokens we're not able to use telnet/SSH and therefore we only can use SNMP WRite in combination with TFTP.  But, this is not working at all. Other systems like 3750 works fine. Is there a difference between Catalysts IOS and nexus NXOS?
    I searched the forum and found this:
    https://supportforums.cisco.com/message/663481#663481
    upgrade to LMS 2.6, archive config not working anymore
    We ship and start a TFTP server by default on Windows.  You must have an SNMP read-write community string configured on your devices, and entered in DCR for TFTP config fetches to work.  Additionally, udp/69 must be open between device and server.
    The easiest way to troubleshoot this kind of problem is to start a sniffer trace on the LMS server (using Device Center > Packet Capture).  Filter on all traffic to one of the failing devices.  Then, run a Sync Archive job for that same device.  When it fails, the sniffer trace will indicate what the problem is
    Regards
    Ad Olsthoorn

    Hi Lavramov,
    Yes I'm quite sure, I installed the required packages acoording to the Nexus.RME431.v2-2.readme.pdf manual. the manual tell me to install the following (see also attachement).
    To install the Cisco Nexus Series Package, you must install the following dependent packages:
    - SharedDcmaSS.RME431.v2-2.zip
    - SharedInventoryMDS.RME431.v1-5-1.zip
    - SharedSwimMDS9000.RME431.v1-6-1.zip
    - SharedNetshowSS.RME431.v1-1.zip
    regards
    Ad

  • LMS 3.2 - RME 4.3.1 Sync archive fails

    Hi,
    Sync archive fails for some of my devices.
    This is the message :
    *** Device Details for .... ***
    Protocol ==> Unknown / Not Applicable
    Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS
    Execution Result:
    CM00139 Could not archive config Cause: Action: Verify that device is managed and credentials are correct. Increase timeout value, if required.
    Check device credential is OK (Telnet + SNMP V2)
    This device is Cisco Systems WS-C6009.Cisco Catalyst Operating System Software, Version 7.4(3). (sysObjectID : enterprises.9.5.39)
    I have modified the "Maximum time to wait for Job Results per device (seconds):" to 240.
    What could be wrong?
    Thanks in advance

    Resolution Summary:Checked the dcmaService.log and found the following recurring statements.
    com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,406,Descr = 12.2(50)SE
    [ Tue Oct 26  15:58:45 CDT 2010 ],DEBUG,[main],com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,405,suppSysId = .1.3.6.1.4.1.9.1.927
    [ Tue Oct 26  15:58:45 CDT 2010
    Checked that the device IOS was well above the version specified in the logs, so thought may be an issue with the device packages.
    Checked the mdf version was 1.25 which came as default when we install LMS 3.2, so upgraded the mdf version to 1.45.
    Still the issue didn't got solved, so upgraded the RME device packages and now the archive job was successful.
    Message was edited by: Dheeraj Gera

  • Can't archive nexus 5010 configs (LMS 3.2)

    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

    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 ....

  • Config archive failed for devices no longer on DCR

    RME reported 30 devices failed config archive but this devices are already removed from DCR but RME keep reporting this devices. how I can clean up thiese devices from RME?
    Thanks

    You can contact TAC, and they can give you the procedure to surgically remove these device records from the RME database.

Maybe you are looking for